Bugzilla – Bug 105623
detection: RT2570
Last modified: 2007-06-05 10:05:08 UTC
During installation and network configuration the RT2570 USB device is detected, but when attempting to edit the configuration Yast2 complains that no module for this device is present, and that it might have been compiled into the kernel. When continuing the configuration of the device, the device type has been set by default to "Ethernet", changing it to wireless and continuing configuration only results in a warning from Yast2 about the changed device type but no further problems. In the logs there is a warning that the rt2570 module is not supported by Novell. But I don't know if that would cause the above problem. The output of 'lsusb' does give a warning: #lsusb Duplicate product spec at line 2453 product 0846:4240 WG11 WiFi Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 148f:2570 Bus 001 Device 001: ID 0000:0000
Here's what I posted to the list yesterday. I've got exactly the same problem. I've recently updated to Beta 2 - (via the CDs, using the update as opposed to reformatting and reinstalling). From what I can tell, wireless still does not work properly. A bit of background: Card: Dell Truemobile 1300 (mini-pci, b+g) Driver: Linuxant Driverloader Network Device: eth1, wlan0 I've set it up on both devices. When I go to this card in the Yast - > "Network Card" -> "Network Card Configuration Overview", I see both my ethernet and my wireless card, detected properly. Using hwinfo gives all proper information about the card. The first red flag I get is when I go to edit the wireless device properties. The error is: "The device does not have a driver module. The driver may be built into the kernel." I assumed this wasn't a problem, as I had the driverloader software ready to go. However, when I go to change the device type from ethernet to wireless, I get this error: "You have changed the device type from the one that has been detected. This only makes sense if you know that the detection is wrong." Again, I understand the warning. I KNOW the device is wireless. I move to proceed. I still can not get an IP from my wirleess router. Another interesting thing to note - when I call "ifstatus wlan0" or any combination ifup or ifdown, I get this error: linux:/var/log # /sbin/ifdown wlan0 wlan0 no such interface ERROR: interface wlan0 is not available ERROR: interface wlan0 is not available /var/log/messages doesn't show me anything useful. I read in this bug report: https://bugzilla.novell.com/show_bug.cgi?id=103740 That pc card support "is in a broken state". However, my card is detected fine. Does the "PCI Device Driver" applet in Yast -> System need to be configured with the device and the driver? This has been tried as well to no avail
Created attachment 46674 [details] /var/log/messages for 8/18-8/19 This is the most recent /var/log/messages file I've got on file. I think I may have found something - specifically, in these last lines of the file (starting line 1051). From what I gather, eth1 IS actually finding the router and at least attempting to get an IP. However, there's an error with dhcpcd, and because of an "infinite ip lease", it won't allow it. I don't know what it's worth, but maybe it's a lead..
Ivo: I think the problem is that hwinfo doesn't know about rt2570 being a wlan driver. I'll fix that. Christopher: Yes, PC-Card support was broken, but you have a mini-PCI one, so you're not affected. I do not have any clue of the Linuxant Driverloader, though, so I can't help here. We can't support third party drivers anyway.
Card should be detected with RC1.