|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
Error in kernel 2.6.24 in ubuntu 8.10Hello everybody,
I have an USB wireless card with chip Zydas 1211rw using module zd1211rw. It used to run perfectly in Ubuntu 7.10, but I've upgraded to 8.04 (kernel 2.6.24) and it doesn't connect or show any wireless network. It also doesn't connect booting with desktop CD or upgrading from 7.10 to 8.04 without any CD. But if I start 8.04 version with 7.10 kernel (2.6.22) card connects perfectly, including with WAP encryption. It also connect if I boot with 7.10 desktop CD. I think it is a problem with driver or module zd1211rw in conjunction with new kernel. Typing "dmesg | grep zd" I get: [ 58.667458] zd1211rw 2-2.4:1.0: eth0 [ 58.667475] usbcore: registered new interface driver zd1211rw [ 67.326365] zd1211rw 2-2.4:1.0: firmware version 4605 [ 67.366327] zd1211rw 2-2.4:1.0: zd1211 chip 0ace:1211 v4721 high 00-02-e3 RF2959_RF pa0 g---- [ 68.365743] zd1211rw 2-2.4:1.0: error ioread32(CR_REG1): -110 Typing "lshw -C network" I get: *-network description: Wireless interface physical id: 1 logical name: eth0 serial: 00:02:e3:45:53:50 capabilities: ethernet physical wireless configuration: broadcast=yes multicast=yes wireless=IEEE 802.11b/g Typing "lsmod | grep zd" I get: zd1211rw 64008 0 ieee80211softmac 34688 1 zd1211rw ieee80211 38344 2 zd1211rw,ieee80211softmac usbcore 169904 5 zd1211rw,usblp,ehci_hcd,ohci_hcd Typing "lsusb" I get: Bus 002 Device 004: ID 0ace:1211 ZyDAS 802.11b/g USB2 WiFi Bus 002 Device 002: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub [ednet] Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 03f0:7604 Hewlett-Packard Deskjet 3940 Bus 001 Device 001: ID 0000:0000 ¿Somebody could help me? I've asked in ubuntu's foru, but nobody is able to help me. Thanks in advance |
|
|
Re: Error in kernel 2.6.24 in ubuntu 8.10I confirm this. There is a bug report opened here too:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/74362
|
|
|
Re: Error in kernel 2.6.24 in ubuntu 8.10Hello everybody,
I've solved the problem changing the stick from a hub port to a port connected directly to motherboard. It seems a problem with the hub instead with the driver of the stick. Thanks |
| Free Forum Powered by Nabble | Forum Help |