** Attachment added: dmesg.log
http://launchpadlibrarian.net/12355516/dmesg.log
--
Intel wireless 4965 stopped working with an update
https://bugs.launchpad.net/bugs/197753
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/12355515/lspci-vvnn.log
--
Intel wireless 4965 stopped working with an update
https://bugs.launchpad.net/bugs/197753
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It stopped working after after installing 2.6.24-11. If I switch to this
kernel, my Intel® PRO/Wireless 3945ABG is not detected anymore. In
2.6.24-10 (the kernel I type this message from) my wireless works
correctly.
--
Intel wireless 4965 stopped working with an update
** Attachment added: dmesg-2.6.24-10
http://launchpadlibrarian.net/12355951/dmesg-2.6.24-10
--
Intel wireless 4965 stopped working with an update
https://bugs.launchpad.net/bugs/197753
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: dmesg-2.6.24-11
http://launchpadlibrarian.net/12355954/dmesg-2.6.24-11
--
Intel wireless 4965 stopped working with an update
https://bugs.launchpad.net/bugs/197753
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
uname -a output:
Linux frodo 2.6.24-10-generic #1 SMP Fri Feb 22 18:26:06 UTC 2008 x86_64
GNU/Linux
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/12355970/lspci-vvnn.log
--
Intel wireless 4965 stopped working with an update
https://bugs.launchpad.net/bugs/197753
You
Forget about my bug report, I forgot to install 'linux-ubuntu-
modules-2.6.24-11-generic', sorry for the trouble. :)
--
Intel wireless 4965 stopped working with an update
https://bugs.launchpad.net/bugs/197753
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Marking as invalid.
Thanks to Jaap-Jan I found out what was the problem for me as well: For
some reason a -386 kernel without modules had snuck onto my system and
was being booted by default, while only -generic had all packages etc.
Removing all traces of -386 solved it all.
Still don't know
