[SOLVED] Cannot make kernel 3.2.x work on my old laptop, stuck at 2.6.38.7 -current

dc_eros · 07-16-2012, 07:52 AM

Hi there,

I got an old laptop which is -current up to date but still using the old kernel 2.6.38.7. It is a 32 bit Core duo with some VIA Chrome chipset (will post more details when needed).

I had no luck running the newest kernel since the machine simply crashes in the middle and turns off.

Probably I need to compile a custom kernel with custom config but I don't know where to start. I have an experience for several custom kernel compile during the pre-13.37 where an old config works on the newer kernels and I do that routine for several kernel updates until the stock kernel finally works before the 13.37 was released.

Where should I start?

TIA

wailingwailer · 07-16-2012, 01:25 PM

where/when does it crash? does lilo or grub finish loading the kernel? does it crash when it remounts the root filesystem? does it get as far as a login prompt?

also, when you're upgrading the stock kernels, make sure you read the /boot/README.initrd, you may already know, the smaller generic kernels require an initrd.gz with the new kernel modules.

also, have you tried booting to the huge kernel? it doesn't require an initrd.gz, is simpler to get running, and should support a wide range of hardware.

dc_eros · 07-16-2012, 06:25 PM

Hi,

I will get more information when I get home, so far here is what I've remembered.

I always boot with huge smp kernel in times like this (and settle with generic kernel when everything is set up). Lilo loads the kernel (shows 2 penguins

). I'm not sure if it reach the point that it mounts any filesystem but I guess it crashes on part where it says "init...", I'll try to take a look later (or even take a video).

What logs should I check for this? I will try to boot using a mini-iso when possible.

Thanks

TobiSGD · 07-16-2012, 06:48 PM

Are you sure that you have a Core Duo CPU? AFAIK, the Core Duo doesn't support PAE and therefore shouldn't run at all with the SMP kernel.

volkerdi · 07-17-2012, 01:51 PM

Quote:

Originally Posted by TobiSGD

Are you sure that you have a Core Duo CPU? AFAIK, the Core Duo doesn't support PAE and therefore shouldn't run at all with the SMP kernel.

All of the Intel Core CPUs support PAE. The common laptop CPU that doesn't support PAE is the Pentium M.

TobiSGD · 07-17-2012, 02:01 PM

The Intel site lists the PAE support for both, the Pentium M with 400MHz FSB (the ones without PAE) and the Core Solo/Duo as "32 bit", so I assumed that they both won't support PAE.

volkerdi · 07-17-2012, 02:28 PM

Quote:

Originally Posted by TobiSGD

The Intel site lists the PAE support for both, the Pentium M with 400MHz FSB (the ones without PAE) and the Core Solo/Duo as "32 bit", so I assumed that they both won't support PAE.

PAE is only used on 32-bit processors (or 64-bit processors when running in 32-bit mode). Although there were some Core Solo and Core Duo processors that lacked EM64T (aka x86_64) support, those did support PAE.

TobiSGD · 07-17-2012, 02:46 PM

Oh, you did get me wrong on that. Intel specifies both, the Pentium M without PAE and the Core Duo (with PAE?) as "PAE 32 bit":
Pentium M: http://ark.intel.com/products/27575/...he-400-MHz-FSB
Core Duo: http://ark.intel.com/products/27237/...Hz-667-MHz-FSB)
Have a look at the "Physical Address Extensions" entry under "Memory Specifications".

This is what Wikipedia has to say about the Core Dou's Yonah-core:

Quote:

There were two variants and one derivative of the Yonah, which did not bear the "Intel Core" brand name. A dual-core (server) derivative, code-named Sossaman, was released on 14 March 2006 as the Xeon (branded) LV (low-voltage). The Sossaman differed from the Yonah only in its support for dual-socket configurations (two CPUs - i.e. four cores - on board, like AMD Quad FX), and implementation of 36-bit memory addressing (PAE mode).

From my point of view this implies that the Core Duo does not support PAE.

whizje · 07-17-2012, 03:44 PM

All processors with XD-bit including the Core Duo's have PAE support, because it is needed for XD functionality.

dc_eros · 07-17-2012, 06:35 PM

Hi,

Sorry for not updating this thread. I haven't get some time to open the old machine due to my busy schedule (day job, night job). However, I'm sure that I have that Core Duo (not the Core 2) and I have used huge_smp and generic_smp for 2.6.38.7 and even older, from late 13.0 current up to the last working stock kernel 2.6.38.7.

(No I didn't do some tweaking with PAE, it just a 1GB memory anyway minus the shared graphics to its just 800MB or so).

I'm not really that good at fixing things but can you suggest which log can I check?

I'll get back to the old laptop once I get some time maybe later today.

Thanks

storkus · 07-17-2012, 08:46 PM

If you can, see if you can spot exactly where its crashing from what the kernel is spitting at you. If you're lucky, it's already writing to the drive and you can use a working live-CD (including the Slackware install CD/DVD) to read the logs; OTOH, if it's crashing before that point, all you can hope for is to catch it without blinking! :P

I have one possibility that no one else has mentioned: the VIA Chrome chip--is it still supported in newer kernels (or the newer kernels Pat is putting out)?

Finally, one seriously real observation, on the off chance you haven't discovered this yourself yet: laptops have VERY NON-STANDARD HARDWARE AND BIOSES! (Yes, I had to put that in all-caps.) I had to deal with this on my own laptop (that I'm writing to you on) yet again at a LUG meeting last week when I couldn't get the VGA-output to work until I disabled Nouveau and installed the Nvidia Blob. Other guys present were using netbooks with stock Ubuntu, so I was kinda snickered at...of course, THEY'RE all scared of the command line! :P

dc_eros · 08-07-2012, 07:21 AM

Hi all,

An update to this. I'm now happily running 3.2.23 from a custom kernel using Alien's guide/wiki of course.

Code:

Chess tonight.

lysender@darkstar:~$ uname -a
Linux darkstar 3.2.23-smp-custom #1 SMP PREEMPT Tue Aug 7 19:03:39 PHT 2012 i686 Genuine Intel(R) CPU           T2130  @ 1.86GHz GenuineIntel GNU/Linux
lysender@darkstar:~$

Don't know what made it work but I remember I set something like processor family (core 2/new xeon/whatever) then some preemp option, then I forgot the rest. I also used an initrd.

Thanks for all help.