2.6.22-15.54 update removes 3rd party wireless drivers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: linux-source-2.6.22
Today's update (Jun 19, 2008) to
================
https:/
2.6.22-15.54
Published in gutsy-updates 9 hours ago
Published in gutsy-security 22 hours ago
linux-source-2.6.22 (2.6.22-15.54) gutsy-security; urgency=low
[Colin Ian King]
* usb-storage: always set the allow_restart flag
- LP: #193154
[Upstream Kernel Changes]
* [IA64] Fix unaligned handler for floating point instructions with base
update
* CVE-2007-6694: [POWERPC] CHRP: Fix possible NULL pointer dereference
* vm audit: add VM_DONTEXPAND to mmap for drivers that need it
(CVE-2008-0007)
* fix SMP ordering hole in fcntl_setlk() (CVE-2008-1669)
* Fix dnotify/close race (CVE-2008-1375)
* [TCP]: secure_
* hrtimer: check relative timeouts for overflow
* netdrvr: natsemi: Fix device removal bug
-- Ben Collins <email address hidden> Mon, 19 May 2008 23:03:41 +0000
Available diffs
* 2.6.22-14.52 to 2.6.22-15.54 (2.3 MiB)
============
Completely removed the Broadcom bcm43xx Wireless driver that was installed on a laptop that I updated today.
Machine reboots to 2.6.22-15.54 (generic) and I notice that the Dynex
PCMCIA wireless adapter isn't lighting up... at all. Check the
System|
driver is no longer activated. Click the little box to activate and what
pops up... click to load from a local file, or from the 3rd party url at
www.whatever. Well, I've no clue where the local file might be on this
machine so I click to load from www.whatever, only to realise that in
order to do this I need a working network connection. So I end up taking
the laptop to a wire, downloading the driver again via wired, and then
reboot... all is well again. However, had I not been able to connect via
a wire, I would have been dead in the water following the update reboot.
I find it unacceptable that a kernel update requires a wired connection to restore the existing installed 3rd party wireless drivers.
Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http:// www.ubuntu. com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!