When I emerge net-dialup/fritzcapi (with fritcapi_cards=fcusb and also without) the fcusb.ko driver doesn't recognise my Fritzcard USB (Id: 057c:0c00). If plug in the the Fritzcard the module tells me: "Unknown device!" If I compile the kernel module by my self and copy the fcusb.ko to /lib/modules/ (everything else the stays the same), then the driver works. Reproducible: Always Steps to Reproduce: 1.FRITZCAPI_CARDS="fcusb" emerge net-dialup/fritzcapi 2.modprobe fcusb 3.plug in the adapter Actual Results: The kernel module tells me "Unknown device!". Expected Results: The module should recognise the adapter and after capiinit i can use it.
How do you compile it manually? Is there a difference in the way you build it and we build it in the ebuild? Did you set up /etc/capi.conf correctly? Can you please post your emerge info?
> How do you compile it manually? 1. untar the archiv fcusb-suse9.1-3.11-04.tar.gz 2. cd fritz 3. make 4. cp src/fcusb.ko /lib/modules/mykernel > Is there a difference in the way you build it and we build it in the ebuild? can't say now, I will look deeper into it later (when I have access to the maschine again) > Did you set up /etc/capi.conf correctly? Yes, I added a line "fcusb - - - - - -" and it runs with the self compiled module. > Can you please post your emerge info? will do so later (hope I have access in about 6 hours)
057c:0c00 is in the capi.usermap and it's in the capi-hotplug-script. /etc/capi.conf is not needed (should be only used if CAPI_HOTPLUG_USB=0 or =no depending on your capi4k-utils version). I have the fcusb2 (v2.0) card. It just works. Your card should also work out-of-the-box. So either there's something different on your system compiling it manually and via fritzcapi-ebuild or we have a completely different problem. Please do this: emerge latest capi4k-utils (best with ~x86 so you really get the latest in portage). Unload all capi/fcusb related stuff. Then switching to system-logger output (console 12 or just tail -f /var/log/messages). Then plugin your card and watching the messages. please post all releated messages.
Created attachment 56200 [details] output from emerge info This is the output from "emerge info" as requested.
Created attachment 56204 [details] the error in syslog
Created attachment 56205 [details] ok in syslog this message is captured when loading the hand made module
in general your setup looks sane. But something must be different. btw: your syslog output is complete? I attach a protocol of my fcusb2 card, just for reference. We now have to check, what's different between the ebuild and your manual compile. All I can say right now is, that the ebuild in general works for at least the Fritz!Card v2.x. But the other drivers are compiled equally. Please try to re-compile your driver manually with CFLAGS set (so it should produce the same output) and then check the sizes between the ebuild-made driver and your self-made driver.
Created attachment 56209 [details] syslog protocol for Fritz!Card USB v2.0 just or reference.
btw: modinfo fcusb filename: /lib/modules/2.6.11-gentoo-r6/extra/fcusb.ko license: Proprietary description: CAPI4Linux: Driver for AVM FRITZ!Card USB vermagic: 2.6.11-gentoo-r6 preempt K7 gcc-3.4 depends: kernelcapi,usbcore alias: usb:v057Cp0C00dl*dh*dc*dsc*dp*ic*isc*ip* -rw-r--r-- 1 root root 602062 14. Apr 00:26 /lib/modules/2.6.11-gentoo-r6/extra/fcusb.ko
my syslog output is smaller because I don't use hotplug and capidrv (adapter to i4l). capi20 and capifs messages are the same here, but I didn't include them. The Fritz USB 2.0 works here to, even with the problematic kernel-module. At the moment I have the problem, that I can't reproduce the error any more. I tried again to emerge fritzcapi an now the new compiled module (even with emerge) works (I tried before 4-5 times and it doesn't). I will clean up my computer from isdn relatet files this evening and try then to emerge this stuff again. If the error didn't show up again, i will close this bug. Hope that is ok.
can't reproduce the error anymore. bug closed. thanks.
