Bugzilla – Bug 117674
dvb firmware - not found due to symlink
Last modified: 2011-04-04 03:11:10 UTC
There is no signal on zapping to a dvb-s channel. There is a report in file:/var/log/messages saying Sep 13 21:01:39 linux kernel: dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw Sep 13 21:01:39 linux kernel: dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware checking into the place, we DO find an existing file /usr/lib/hotplug/firmware/dvb-ttpci-01.fw but it is a symlink to /usr/lib/hotplug/firmware/dvb-ttpci-01.fw-261f It does help to move the real file into the place of the symlink. Yes, it is very dubious why a symlink should be a problem but that is how I was able to fix the situation. Here is my current state of affairs: pc3:/var/log # ls -l /usr/lib/hotplug/firmware.orig/ insgesamt 244 drwxr-xr-x 2 root root 4096 2005-09-14 19:02 . drwxr-xr-x 4 root root 4096 2005-09-18 16:01 .. lrwxrwxrwx 1 root root 20 2005-09-14 19:02 dvb-ttpci-01.fw -> dvb-ttpci-01.fw-261f -rw-r--r-- 1 root root 234284 2005-09-03 13:42 dvb-ttpci-01.fw-261f pc3:/var/log # ls -l /usr/lib/hotplug/firmware insgesamt 244 drwxr-xr-x 2 root root 4096 2005-09-14 19:58 . drwxr-xr-x 4 root root 4096 2005-09-18 16:01 .. -rw-r--r-- 1 root root 234284 2005-09-03 13:42 dvb-ttpci-01.fw
is your /usr on a separate partition and therefore not available when the dvb module is loaded? The symlink always worked fine for me. IIRC my vdr machine is running 10.0 RC1 atm.
good question, but in this installation there is no /usr partition. Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 257888 0 257888 0% /dev/shm /dev/sda11 7882560 4033468 3448676 54% / /dev/sda1 186663 6268 170758 4% /boot /dev/sda6 7882560 5618900 1863244 76% /home And yes, I would be suprised to see the symlink being the problem but it did help to remove it. *sigh* So, atleast this bug report is a place to record such annoyances. The file itself looks fine just is the filesystem. Is there anything else that I could check about the path and/or file inode?
The installation on a different computer (after moving the dvb cards) did yield the exact same behavior. Worked around again by pushing a copy of the firmware in the correct file path. So this is reproducible according to my setup (one full dvb card, one budget dvb card, ext2 boot, ext3 root, suse RC1).
Created attachment 51311 [details] rcautofs - modifying sed to allow timeout settings
Comment on attachment 51311 [details] rcautofs - modifying sed to allow timeout settings IGNORE this patch - I was editing a different bug 117672 but it ended up here. It should not have!
Does this bug still persist on recent openSUSE releases?
The version with which you had the bug is now obsolete. I'll close this as NORESPONSE. If you can still reproduce it in current 11.4, please reopen the bug and move it to the appropriate version. Thanks!