** Tags added: regression-release
--
dapper->hardy->intrepid upgrade path leaves user with unmaintained kernel
https://bugs.launchpad.net/bugs/353534
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
>From the kernel side we need to identify how you detect the capabilities
required to select an appropriate kernel. This work will be recorded on
the wiki page below:
https://wiki.ubuntu.com/KernelTeam/CPUFlavour
--
dapper->hardy->intrepid upgrade path leaves user with unsupported kernel
ht
In the karmic UDS discussions kernel selection based on the CPU
capabilities was discussed. It is highly likley that that work will fix
this issue for machines that end up on Karmic.
https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-karmic-
flavours
** Changed in: linux (Ubuntu)
If you want this fixed in update-manager I need instructions how to
detect (in a programmatic way) what kernel is suitable for what
/proc/cpuinfo - i.e. what cpu family/model/model name or flags to map to
what kernel.
I want to avoid switching users to a kernel that won't boot afterwards.
** Chan
** Changed in: update-manager (Ubuntu)
Importance: Undecided => High
** Changed in: update-manager (Ubuntu)
Status: New => Triaged
--
dapper->hardy->intrepid upgrade path leaves user with unsupported kernel
https://bugs.launchpad.net/bugs/353534
You received this bug notification becau
>From the configuration Dapper knew 3 flavours there
- 386 (CONFIG_M486 set)
- 686 (CONFIG_M686 set) and
- k7 (CONFIG_MK7 set)
In Hardy we have
- 386 (CONFIG_M486 set)
- generic (CONFIG_M586 set)
So the one question is, can we selectively move those which can go to
586 to generic and keep the one
I would agree that (a) sounds like a good way forward. We would need to
try and identify anything which is i686 and above capable and move those
to -generic. The starting point would be to fix the Jaunty update-
manager perhaps? The kernel team can help find the key to choose which
cpu's can be
I do not know enough details about the kernel flavors for a good
solution, but here are my alternatives:
a) We could have a special case in update-manager that checks
/proc/cpuinfo and based on what it reads (and what the kernel team
thinks is appropriate) switch users from linux-386 to linux-gene
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
dapper->hardy->intrepid upgrade path leaves user with unsupported kernel
https://bugs.launchpad.net/bugs/353534
You received this bug notification because you are a membe
