I think I'm losing my mind...

I've been trying to get a 2.6 kernel to boot on my laptop (Gateway 460E, Centrino system, 1.7GHz, 768 RAM, 40GB HD, dual booting with XP Pro) for some time now. I have some really great instructions, and every time I've tried it, I get the same problem.

When I boot from the Slackware 10.2 CD, and tell it to boot with the test26.s kernel, it boots, gets some distance past uncompressing, but quickly (and I mean quickly), after displaying the first two dozen lines of information, goes black and never comes back. Same thing happens with an installed kernel (same version).

Interestingly, I've had Ubuntu on the same laptop, running kernels 2.6.10, 2.6.15 and 2.6.17 without a lick of trouble. It's only when I try to do it with Slack that I get hosed. I'd not care, but I'd really like to get my Intel IPW2200 wireless working -- it's the only thing that doesn't work from a default 2.4.31 installation.

Does anyone have any hints for me?

Try disabling framebuffer by using test26.s vga=normal as LILO parameter.

No dice. That's what I've used, both vga=normal and vga=771 (which I used to have to use back when I was using Ubuntu Hoary to get the video to work)

Just tried again, and the last line I see references "isapnp" and then it goes dark.

I think you can pass the noisapnp argument at boot time. Then you might be able to boot. I would not think you have isa devices in your laptop anyway.

If this lets you boot you can investigate some more. From what I have read, i think the kernel may be having problems probing a sound or modem device.

the noacpi option may also enable you to boot far enough to investigate further.

tobyl

Would that be by adding "noisapnp" after the name of the kernel I'm loading at the "boot:" prompt in LILO? If so, still no dice.

If, after a failed boot like that, I boot into the 2.4 kernel, would there still be a copy of the messages that were displayed immediately before the lockup somewhere in /var/log for example?

ETA: Upgraded to 2.6.17.11 (stock kernel from -current) and got past the error with the isapnp. Now it kernel panics some time after that. I'll do more digging.

Okay, we put this one to bed. It was ACPI causing the problems, and I was passing the wrong parameter (noacpi didn't work, it had to be acpi=no).

Once I got past that, with the new, 2.6.17.11 kernel, all appears well. I'll post more once I get everything working.