gutsy new kernal .9 broke zd1211rw

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Please run the command "sudo lsusb -v > lsusb-v.log" and attach the resulting file "lsusb-v.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

First time trying gutsy with this wireless device but I have the same problem...tried it on two laptops...

Attached is requested information.

Thanks sparc128.
To any of you two: what does iwconfig returns?

Here's the results from iwconfig (showing neighbour network)....while it had
errors in dmesg, I just discovered it connected to my hidden ssid wep
network fine....sorry about that, I would say this is non-bug....I orginally
tested it by connecting to neighbour wireless (bad test).....this wireless
device works out of the box on latest .9 kernel.

lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

eth1 IEEE 802.11b/g ESSID:"linksys" Nickname:"zd1211"
          Mode:Managed Frequency:2.437 GHz Access Point:
00:18:F8:5E:2A:D4
          Bit Rate=1 Mb/s
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

On 8/11/07, Paul Dufresne <email address hidden> wrote:
>
> Thanks sparc128.
> To any of you two: what does iwconfig returns?
>
> --
> gutsy new kernal .9 broke zd1211rw
> https://bugs.launchpad.net/bugs/130436
> You received this bug notification because you are a direct subscriber
> of the bug.
>

my bug report is very similar, when i upgraded to the new kernal in gutsy tribe 5, my drivers dont load, mainly my video driver, on a laptop as well.

I have A-LINK 54USB
Sometimes I have to reboot my machine many times if I want to use the internet. And sometimes wlan works a while and then not.
If I my machine is on and I power on my external adsl-wlan modem, I have to reboot to get the wlan work. So I have to always connect modem first, and then ubuntu-machine. In feisty I did't had this problem.

Wlan works at the moment but I get messages:

kern.log:
Oct 3 20:17:01 unelma-laptop kernel: [ 5731.260000] zd1211rw 4-3:1.0: error ioread32(CR_REG1): -110

syslog: (this kind of messages in every 4 minutes)
Oct 3 22:22:21 unelma-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Oct 3 22:22:29 unelma-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Oct 3 22:22:39 unelma-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Oct 3 22:22:50 unelma-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
Oct 3 22:22:52 unelma-laptop dhclient: No DHCPOFFERS received.
Oct 3 22:22:52 unelma-laptop dhclient: No working leases in persistent database - sleeping.
Oct 3 22:25:41 unelma-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Oct 3 22:25:47 unelma-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Oct 3 22:26:01 unelma-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Oct 3 22:26:12 unelma-laptop dhclient: No DHCPOFFERS received.
Oct 3 22:26:12 unelma-laptop dhclient: No working leases in persistent database - sleeping.

Time for some cleanup here, I am closing this bug.

Kousoto, the original poster, have never come back to give requested info.

Sparc128 finally discovered that "while it had errors in dmesg, I just discovered it connected to my hidden ssid wep network fine" suggesting to consider this a non bug.

donteatthefish, have a general modules not loading, which should probably open a new bug, or request help in forums or question zone.

mikko sorri seems to have a system that works, but that did not get IP address from DHCP, and DHCP kick in every 4 mins to try to get one, I could only supposed he configured manually some IP addresses. Or have an intermitent connexion problem, maybe because of bad wire!? Anyway I would suggest him to ask help on https://answers.launchpad.net/ubuntu/

Because of all these non convergent infos, I am closing this bug.