neumoDVB

Updated neumodvb, updated drivers (neumo-drivers and also blindscan_kernel --> media_build from TBS's TBS6903X driver download centre.

The latter driver gives disabled TBS6903X's in frontends, as does building with neumo_media_build.

Reinstalling drivers with neumo-drivers re-enables TBS6903x.

Still can't tune any channels as before, no SNR in spectrum analysis page.

Perhaps I'm missing some driver updates?

Frontends using TBS6903x download.webp
Frontends using neumo-drivers.webp
 
Updated neumodvb, updated drivers (neumo-drivers and also blindscan_kernel --> media_build from TBS's TBS6903X driver download centre.

The latter driver gives disabled TBS6903X's in frontends, as does building with neumo_media_build.

Reinstalling drivers with neumo-drivers re-enables TBS6903x.

Still can't tune any channels as before, no SNR in spectrum analysis page.

Perhaps I'm missing some driver updates?

View attachment 170517
View attachment 170518
Llew, the modern drivers do not even use media_build and at some point neumodvb started requiring those modern drivers. How did you install the drivers?
 
Llew, the modern drivers do not even use media_build and at some point neumodvb started requiring those modern drivers. How did you install the drivers?
From blindscan_kernel folder for the TBS media_build when neumo_media_build failed to enable TBS6903X. I was suspicious of the TBS media_build because it seems hopelessly out of date, but proceeded as it's the official TBS6903X download.

I use neumo_drivers for 6.12.69-2-cachyos-lts. which builds successfully, but you informed me to update out-of-date drivers, which has obviously sent me on a wild-goose chase.
 
From blindscan_kernel folder for the TBS media_build when neumo_media_build failed to enable TBS6903X. I was suspicious of the TBS media_build because it seems hopelessly out of date, but proceeded as it's the official TBS6903X download.

I use neumo_drivers for 6.12.69-2-cachyos-lts. which builds successfully, but you informed me to update out-of-date drivers, which has obviously sent me on a wild-goose chase.
Well yes, but use the latest version (after git pull). What you used is more than 6 months old. Then please provide kernel logs if problems persist
 
Well yes, but use the latest version (after git pull). What you used is more than 6 months old. Then please provide kernel logs if problems persist
git pull error. Merge would overwrite existing neumo-frontend.h. Didn't want to do that as I guessed it might make my existing neumodvb unusable. At least neumodvb as it is now works with existing channels, despite the major problem of not tuning new frequencies.
Checked existing and new neumo-frontend.h files with Meld - reports them as identical. Strange, so didn't go ahead with the merge.

Decided to back up my existing neumo-drivers, even though it fails to tune any channels, and re-install.

Doesn't build successfully. Too many errors.

Can you check the kernel.log and build errors please?
 

Attachments

git pull error. Merge would overwrite existing neumo-frontend.h. Didn't want to do that as it might make my existing neumodvb unusable.
Checked existing and new file with Meld - reports them as identical. Strange, so didn't go ahead with the merge.

Decided to back up my existing neumo-drivers, even though it fails to tune any channels, and re-install.

Doesn't build successfully. Too many errors.

Can you check the kernel.log and build errors please?

You need to pull correctly first (if needed just remove the drivers and start fresh) before compiling. There is no risk of overwriting anything.
 
You need to pull correctly first (if needed just remove the drivers and start fresh) before compiling. There is no risk of overwriting anything.
I did start afresh with a new neumo-drivers, and got the build errors I've posted.
 
It seems that there was a problem on github causing a file to not be updated. It should work now, but best start from scratch.
 
It seems that there was a problem on github causing a file to not be updated. It should work now, but best start from scratch.
New start, still errors.
 

Attachments

New start, still errors.
It seems that the problem on github was a lot more complicated, which is also why compilation sometimes works and sometimes not, depending on history of cloning. I fixed it now. It is best to just remove the existing neumo-drivers and start completely fresh. Hopefully the fix is now fine.
 
It seems that the problem on github was a lot more complicated, which is also why compilation sometimes works and sometimes not, depending on history of cloning. I fixed it now. It is best to just remove the existing neumo-drivers and start completely fresh. Hopefully the fix is now fine.
I think there's just the two errors now deeptho, seem to be buffer errors?

In neumo-drivers/neumo/dvb-core/neumo-dmxdev-dvbapi 473,477.
 

Attachments

Llew,
that error must be specific to your kernel version . 6.12 is very old. In addition there was a bug that misdetected old kernels.

It is quite probable that this now works with your current kernel. If not, you will have to upgrade. Also please test if this compiles on your other computers (ubuntu and such)
 
that error must be specific to your kernel version . 6.12 is very old.
CachyOS jumped from 6.12 to 7.1 (rolling release). My kernel is an LTS, so I'm stuck on 6.12.

7.1 Anytime soon for neumodvb?

I shall try it inmy current kernal, then in Ubuntu and Manjaro, which uses 6.18 I believe.
 
Working fine now deeptho with my existing 6.12 kernel. Tunes, finds channel in Services, video up in Live TV

Thank you very much for your help on this :) CachyOS Reuters 15w.webp:)
 
You're welcome :->
 
@deeptho

Can you please add the package manager installer to the beginning of the Arch Linux dependency list in your neumodvb Installation document?

=> sudo pacman -S

Also, I forgot to append an 's' onto boost-lib in the dependencies.

TIA
 
I have made the changes. Please check
 
Back
Top