Comment 29 for bug 930447

pae kernel running fine on my non-pae flag IBM Thinkpad T40 1.5 gHz Pentium M with Lubuntu precise pangolin 20120207 daily build install, and as daily updated since. I haven't tried Live or install since Feb 7 so I don't know if the

-in my case, totally unnecessary check for pae-

is back into the daily builds or not.

jerry@ThinkPad-T40:~$ ls /boot
abi-3.2.0-15-generic-pae grub memtest86+.bin System.map-3.2.0-15-generic-pae
config-3.2.0-15-generic-pae initrd.img-3.2.0-15-generic-pae memtest86+_multiboot.bin vmlinuz-3.2.0-15-generic-pae

jerry@ThinkPad-T40:~$ uname -a
Linux ThinkPad-T40 3.2.0-15-generic-pae #24-Ubuntu SMP Tue Feb 7 23:30:35 UTC 2012 i686 i686 i386 GNU/Linux

flags: fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 tm pbe up bts est tm2

jerry@ThinkPad-T40:~$ grep PAE /boot/config-3.2.0-15-generic-pae
CONFIG_X86_PAE=y

No, it's ATI doesn't do unity-3D which is a non-problem to me since I even run -2D on my notebook, netbook, tower that will run -3D. I don't like big fuzzy out of focus graphics. Now when HUD comes around I'll test that.

My experience I found a couple precise pangolin daily builds that checked for pae flag and refused to boot.

Perhaps the 20120207 doesn't check for the flag - so it goes on and runs live CD and installs and runs fine??

Did development test precise pangolin generic-pae would really fail?? Works fine on my T40.

"unable to boot" only becaue of the test for the pae flag?? Any way to convince development into changing the test to a

"warning, pae flag not present, may not run, do you want to continue Y/n"?? I'd say Y. Alpha/Beta/RC testing is risky anyway.

Anything I can test or report on for anyone?? (I'm not a developer, I don't do kernel "make".)

Jerry