Bugzilla – Bug 131154
AVM Fritz!Box USB interface is not detected for network/Ethernet
Last modified: 2005-10-29 19:53:25 UTC
SuSE 10.0 does not detect the USB network interface of Fritz!Box. A manual load of the module usbnet is required to fix. I expect the problem come from the "2 function" of the interface. - CDROM with driver as content - CDC Ethernet interface. At 9.3 the CD-Rom had not been detected proper. 10.0 stops after the the CD is recognized. Only the manual load of usbnet "disconnects" the CD-part and activates the CDC-Ethernet. I expect 10.0 is failing, cause it detects the "usb" CD-ROM. I would be able to run a debug kernel if required/requested. Workaround possible: /etc/sysconfig/kernel MODULES_LOADED_ON_BOOT="usbnet" Christian See also: http://www.linux-club.de/viewtopic.php?t=43585#241982 (Bug might be related to bug 121817, but headline says fritz card for that bug ) Details will follow
Details lsusb -v: Bus 001 Device 003: ID 057c:3d00 AVM GmbH Fritz!Box Bus 001 Device 003: ID 057c:3d00 AVM GmbH Fritz!Box Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 2 Communications bDeviceSubClass 6 Ethernet Networking bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x057c AVM GmbH idProduct 0x3d00 Fritz!Box bcdDevice 1.00 iManufacturer 1 AVM iProduct 2 USB DSL Device iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 80 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 6 Ethernet Networking bInterfaceProtocol 0 iInterface 0 CDC Header: bcdCDC 1.10 CDC Ethernet: iMacAddress 4 00040E2934E9 bmEthernetStatistics 0x00000000 wMaxSegmentSize 1514 wNumberMCFilters 0x0000 bNumberPowerFilters 0 CDC Union: bMasterInterface 0 bSlaveInterface 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 250 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 10 Data bInterfaceSubClass 0 Unused bInterfaceProtocol 0 iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 10 Data bInterfaceSubClass 0 Unused bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0
Details from /var/log/messages: Oct 23 12:28:49 cvathome kernel: uhci_hcd 0000:00:14.2: UHCI Host Controller Oct 23 12:28:49 cvathome kernel: uhci_hcd 0000:00:14.2: new USB bus registered, assigned bus number 1 Oct 23 12:28:49 cvathome kernel: uhci_hcd 0000:00:14.2: irq 11, io base 0x00002840 Oct 23 12:28:49 cvathome kernel: hub 1-0:1.0: USB hub found Oct 23 12:28:49 cvathome kernel: hub 1-0:1.0: 2 ports detected Oct 23 12:28:49 cvathome kernel: piix4_smbus 0000:00:14.3: Found 0000:00:14.3 device Oct 23 12:28:49 cvathome kernel: usb 1-1: new full speed USB device using uhci_hcd and address 2 Oct 23 12:28:49 cvathome kernel: Device not ready. Make sure there is a disc in the drive. Oct 23 12:28:49 cvathome kernel: Device not ready. Make sure there is a disc in the drive. Oct 23 12:28:49 cvathome kernel: Initializing USB Mass Storage driver... Oct 23 12:28:49 cvathome kernel: scsi1 : SCSI emulation for USB Mass Storage devices Oct 23 12:28:49 cvathome kernel: usb-storage: device found at 2 Oct 23 12:28:49 cvathome kernel: usb-storage: waiting for device to settle before scanning Oct 23 12:28:49 cvathome kernel: usbcore: registered new driver usb-storage Oct 23 12:28:49 cvathome kernel: USB Mass Storage support registered. Oct 23 12:28:49 cvathome kernel: Vendor: AVM Model: FRITZ!Box CD-ROM Rev: 1.00 Oct 23 12:28:49 cvathome kernel: Type: CD-ROM ANSI SCSI revision: 00 Oct 23 12:28:49 cvathome kernel: sr1: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray Oct 23 12:28:49 cvathome kernel: Attached scsi CD-ROM sr1 at scsi1, channel 0, id 0, lun 0 Oct 23 12:28:49 cvathome kernel: Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0, type 5 Oct 23 12:28:49 cvathome kernel: usb-storage: device scan complete Oct 23 12:29:08 cvathome kernel: usb 1-1: USB disconnect, address 2 Oct 23 12:29:08 cvathome kernel: usb 1-1: new full speed USB device using uhci_hcd and address 3 Oct 23 12:29:09 cvathome kernel: eth1: register usbnet at usb-0000:00:14.2-1, CDC Ethernet Device, 00:04:0e:29:43:E9
Just to avoid question: Without MODULES_LOADED_ON_BOOT="usbnet" these messages do not come: Oct 23 12:29:08 cvathome kernel: usb 1-1: USB disconnect, address 2 Oct 23 12:29:08 cvathome kernel: usb 1-1: new full speed USB device using uhci_hcd and address 3 Oct 23 12:29:09 cvathome kernel: eth1: register usbnet at usb-0000:00:14.2-1, CDC Ethernet Device, 00:04:0e:29:43:E9
I can reproduce the missing usbnet detection and also that it is not loaded until you manually place it into MODULES_LOADED_ON_BOOT. But I do not see the CDROM detection here with a Fritz!Box SL,the lspci looks very similar only the idProduct differs (0x3701). Olaf do you have an idea why a mass storage is detected and why usbnet does not load automatically ?
The Fritz!Box SL has just a 2 MB flash. (always for SL ). The Fritzboxes and WLAN have a 4 MB flash. I suppose that's why no mass storage is found. There is no for SL. But it's interesting that the detection does not work for Ethernet interface only. Christian
run these commands and attach the files in /events/* ln -sv /dev/shm /events echo /sbin/hotplugeventrecorder > /proc/sys/kernel/hotplug unplug and replug the device.
No, this is a kernel bug, which I just fixed, I'll go dig up the duplicate bug number for this...
*** This bug has been marked as a duplicate of 105621 ***