[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Question about the new kernel with PAE (Wheezy) - Report



On 21/06/11 18:52, Camaleón wrote:
On Tue, 21 Jun 2011 18:22:48 +0100, Dom wrote:


I'll find that out what apt does tomorrow when I try to upgrade my main
laptop which doesn't have pae support, and will report the results.

I'll give you some tips as I couldn't retain my self and performed the
dist-upgrade :-)

I'm not too worried, as I know it won't remove the old kernel and I can
reboot into that one and install the 486 version when it fails.


Well, if you agree with the update, the pae kernel installs despite it
warns about it will not work (and when you boot with it, it fails as
expected). You can still boot with the old kernel (good job!).

Now here's the thing. I did the install, got the warning from the meta-package (linux-image-2.6-686), and the kernel installed - as you said.

I then rebooted and... it works fine.

System details are:

dom@oz:~$ uname -r
2.6.39-2-686-pae
dom@oz:~$ cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 9
model name	: Intel(R) Pentium(R) M processor 1600MHz
(...)
flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 tm pbe up bts est tm2

No "pae" flag, as you can see.

So in the end you need to manually remove the pae kernel and install the
486, as Gilbert suggested.

I think I'll leave it there for now and upgrade manually when a new kernel revision is released.

I still think this should have been automagically done by the upgrade.
Why proceed with installing something that will not work and even set it
as the default boot option>:-P

apt/aptitude are just satisfying the dependencies of the meta-package, the one that fails with the warning. Possible the same code could be put into the actual kernel package, but that would mean re-writing the kernel package too, just for a (supposedly) one-off event.

What we need here is some sort of "dynamic depends", where the package generates a suitable dependency based on criteria at install time. I can, however, see many reasons why that would be a bad idea.

--
Dom


Reply to: