This happens only in the amd64, but no in the x86, with the same kernel configuration, every module (except the hardware stuff, processor type, etc). As you can see in one of my previous posts, it detects perfectly the DVB stick at boot I would like to think that, but in the amd64 it's not that way.
Afatech af9015 driver#
If the driver is built-in and you insert it before the filesystem is mounted (read: the device is there at boot), it's impossible for it load the firmware, because it's on the yet-to-be-mounted filesystem. It has nothing to do with architecture, it's one thing and only one thing: Do you insert the device before or after the filesystem is mounted. The only explanation is it is built into kernel. I compiled the kernel module as "module" and now it works properly. I didn't find the reason why the amd64 loads it and the x86 don't. I still havn't got a /dev/dvb0/ but that's probably to do with setting the module options and I'll see whether I can find the answer first. config file of the kernel of the new one to compile the old one (I change all the hardware stuff, of course).
Afatech af9015 Pc#
The only difference is that this other PC is an amd64, instead of a x86. rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1.3/rc/rc0Īs I can see, this other PC detects it in warm state, but the first one in cold state.
Afatech af9015 how to#
Please learn how to denote units correctly!īut it's kinda strange, because I have another PC which loads it perfectly: When kernel loads root is not mounted yet and firmware cannot be accessed. dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected. dvb-usb: schedule remote query interval to 500 msecs. tda18218: NXP TDA18218HN successfully identified. DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T).
DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick)
Afatech af9015 software#
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-2: New USB device found, idVendor=15a4, idProduct=9016 usb 1-2: new high speed USB device number 3 using ehci_hcd dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. usb 1-2: USB disconnect, device number 2 In fact, if after booting, I unplug and plug it again, it loads correctly: The firmware file is in /lib/firmware/ (it's dvb-usb-af9015.fw). usbcore: registered new interface driver dvb_usb_af9015 dvb_usb_af9015: probe of 1-2:1.0 failed with error -2 (dvb-usb-af9015.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. dvb-usb: did not find the firmware file. dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware I am also having a similar issue with an afatech DVB USB stick. Make tuner-xc2028 a module if it isn't already. Last edited by Robyn Hood on Sun 12:50 pm edited 1 time in total Who calls a man "good" unless he likes being good? I suppose that is it now configured to look somewhere else, but I've no idea how to find out where. My previous kernel used to find it in /lib/firmware/ Posted: Tue 11:15 am Post subject: Firmware - Solved Gentoo Forums Forum Index Kernel & Hardware Gentoo Forums :: View topic - Firmware - Solved
0 kommentar(er)
