Hi there
glad to know you are able to use your card with hardy, closing this report due
your last comment, thanks again for taking the time to report this issue and
help to make Ubuntu better, please feel free to report any future bugs you
might find.
** Changed in: linux-source-2.6.22 (Ubuntu
Well made a live CD and tried but it didn't recognize the MA521 card.
Remembering I had to use a WinXP driver and ndiswrapper to get it to
work I decided to just upgrade the Omnibook 6000 to 8.04 alpha 6
directly and see what happens.
IT WORKS!
--
Bootup Kernel Panic with Netgear MA521 PCMCIA W
Hi there
Could you please try to reproduce this issue with the live environment of the
Desktop CD of the development release - Hardy Heron, and include the log files
with the card plugged in.
Thanks
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided => Medium
--
Bootup Kerne
Same thing here. All worked fine in version 6.0x Ubuntu but when I
upgraded to ver. 7.xx it panics on bootup if the ma521 is in. If I unplg
the card, bootup and log in, then use wifi to log in, it works fine from
there on. But next boot is the same story. I have to use wifi controls
to login every
I am having exactly the same problem but more. My Gutsy freezes
regardless of when I connect the card. It would be nice if a fix is
provided for this bug. My card is fine as it works with other OS.
--
Bootup Kernel Panic with Netgear MA521 PCMCIA Wifi card
https://bugs.launchpad.net/bugs/155360
lspci-vvnn.log attached
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/10171706/lspci-vvnn.log
--
Bootup Kernel Panic with Netgear MA521 PCMCIA Wifi card
https://bugs.launchpad.net/bugs/155360
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Output from "uname -a"
Linux Ubuntu-laptop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
GNU/Linux
dmesg.log attached
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/10171689/dmesg.log
--
Bootup Kernel Panic with Netgear MA521 PCMCIA Wifi card
https://bugs.laun
Hi there
Could you please include the following information:
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
