Ive been using Mandrake 10.1 for quite some time and Id like to install mandriva 2006 but i cant because my system wont boot a 2.6 kernel. When I installed mandrake 10.1 I had problems starting the installation process with the 2.6 kernel. Every time I tried to boot any installation cd from any distro that used the 2.6 kernel id encounter the same "hda: lost interrupt" problem. I just settled for the 2.4 kernel in mandrake 10.1 and everything works fine. I discovered that mandriva ditched the 2.4 kernel as an option for booting the install cd so now I cant upgrade. Does anybody know a way I could boot the mandriva 2005 installation CD with a 2.4 kernel?

What sort of machine won't boot a 2.6 kernel? Anyway, the 2.6 kernel in 2006 will be different. It might work just fine.

I've booted 2.6 kernels on every machine here, from p166's to p2's and p3's and p4's and k6's and semprons and athlon XP's and AMD64's with intel, nvidia, via, SiS chipsets and segate, WD, maxtor, hitachi/ibm, fujitsu drives... Interested to here about what sort of box it won't boot on.

same "hda: lost interrupt" problem

1st using
noapic option often fixes that issue.
When you start the Mandriva installation Disc Hit F1 (more Options)
type
'linux noapic'



if that fails you can still easiliy use a 2.4 kernel with 2006 (it's included on the disc)

When you start the Mandriva installation Disc Hit F1
from memory alt1 was the 2.4 kernel

follow the onscreen promtps

Its an old IBM Aptiva.
Celeron 667mhz, SiS 630

Ive never suceeded in booting any 2.6 kernel up untill about 10 minutes ago when i tried a LiveCD version of PuppyLinux

been using linux for 10 years?
Mandrake isnt bad is it

Dont you hate ignorant people that lash out at throwing Mandriva Newbie taunts.


If they cant understand a good distro im glad the fools spend more time setting up software than using it.

the other 2 popular distros Gentoo & Fedora.
are prime examples of poor user end distros

"been using linux for 10 years?
Mandrake isnt bad is it"

Not bad... Started with slack of course, then used RH, then started using the KDE beta's... Used the first mandrake since RH wouldn't put KDE on their distro. Used mandr* ever since and it's been fairly reliable for me. Not fussed on FC, but I have Suse 10 running on one system now and it's not too bad.

Mandr* is still my pick. I'm used to it anyway...

"Its an old IBM Aptiva.
Celeron 667mhz, SiS 630"

"Ive never suceeded in booting any 2.6 kernel up untill about 10 minutes ago when i tried a LiveCD version of PuppyLinux"

Good to hear. Actually I forgot about some of the issues I have had with some boxes and I've had to use the noapic opion of a PC here as well... VIA chipset I think... The later kernels may have fixed that issue a bit anyway. I'd try 2006 with the 2.6 first and try some of the suggestions from carl0ski...

Ill give the 2006 kernels a try and see how it goes. Everytime ive searched for a solution to the lost interrupt problem I was told to use kernel options (such as noapic, acpi=pci etc.). None of them have made a difference. On the PuppyLinux live CD (The first 2.6 kernel thats actually booted on my machine) there was a boot menu and one of the options was to load into ram and in brackets it said "no apci". Its making me wonder if the options that I pass to the kernel are ignored when I try to boot a Mandriva install CD. Another thing I recently discovered is that if i completely disable my hard drive in my BIOS the mandriva 2.6 kernels will boot fine but then (obviously) I cant actually install mandriva to my hard drive.

Ill give the 2006 kernels a try and see how it goes. Everytime ive searched for a solution to the lost interrupt problem I was told to use kernel options (such as noapic, acpi=pci etc.). None of them have made a difference. On the PuppyLinux live CD (The first 2.6 kernel thats actually booted on my machine) there was a boot menu and one of the options was to load into ram and in brackets it said "no apci". Its making me wonder if the options that I pass to the kernel are ignored when I try to boot a Mandriva install CD. Another thing I recently discovered is that if i completely disable my hard drive in my BIOS the mandriva 2.6 kernels will boot fine but then (obviously) I cant actually install mandriva to my hard drive.

if thats the case it isnt a driver issue since it would still bugger up.

your partition table on the suspect hdd is bodgy or corrupted.
(it happened to me once.)

completely wipe the hdd and MBR and start from scratch with a like new hdd again.

Pobably a typo.

There is something I discovered today as I was updating kernel versions (from 2.6.11-6 to 2.6.14-4) and while checking through the hits from a google search, one of them said that I needed to have ver 2.6.12-x before I could update Mandriva LE 2005 to LE 2006. Before upgrading the kernel, urpmi --auto-select reported none to update, and after the kernel install process, urpmi reported the same thing.

I wonder some times if that is all there is to it.

So, my 2 cents worth, is have a go, if it won't install, it hasen't broken anything yet, so keep trying other options.

Cheers!

urpmi --auto-select

by default ignores the core system including the kernel and urpmi itself


urpmi kernel --auto-select

That's what I would have hoped, too. Although, I don't use Gnome, but it gets updated anyway, and Apache, and a whole lot of other programs I hadn't installed before either.

There is a list in /etc/urpmi/ where you can exclude certain packages from being updated.

There's nothing worse than painstakingly installing the Ati 3D graphics drivers, only to have urpmi install a new kernel for you. I think the same goes for Xorg, config files getting set back to defaults. Seems no matter how diligent I am, Mandy is one step ahead of me. Now I have a bit more knowledge It is much smother.

At least I get plenty of experience, lol!

Thanks.

Hmm! That's a good one

the ati installer is a lot easier than it used to be

you can install it from x with a gui

./ati-installer.bin


i still use that instead of the Club Mandriva ati packages since the rpms dont support my ati radeon chipset