UPDATE [bootup kernel panic 2.6.x]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello again
Ive tried some advices you gave me, use hda=remap at boottime, puting this options CONFIG_PARTITIO_ADVANCED=y and CONFIG_LDM_PARTITION=y, taking out initrd suport. But I havnt had any improovment. But I am starting to thing it is about how my HD is managed. I have a SEGATE 20Gb drive. My BIOS does not recognize that amount of disk, so I use a program that is on MBR provided by Segate that makes the 20Gb abiavle. In kernel 2.4 it works just fine, but maybe that is the cause 2.6 can not boot... am I right? what else could I try?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAAF6cOGkG8a1Mf+oRAr8IAKCeiBNabvxPooIjcGf5d8s8JMPgMgCbBtKf xD6t1aB8VuAbm+Sal/J5Mmg=
=rVmA
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello again, after two days of trying to solve my problem I give up now. I tried lots of diferent configurations, so I do not know if it is a kernel BUG or what, because Ive seen similar threads in this mail-list and in other lists, irc chats...
I definitevily giveup of trying use 2.6.x in that computer, if someone wants to investigate what happened and need config files, logs or whatever, just tell me...
I am sure it is a kernel-hardware interactuation problem, because there is no configuration I can do for this to work... so... giveup...

Thanks anyway to all of you that took the time of reading this mail...

Pablo limon

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAANRjOGkG8a1Mf+oRAp05AJ4qQPYodLQs5xfTJ3sPcrS+5gCFtgCeM8XC 20HGVyBY8q3kB4jr6zfJJxI=
=M06e
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks for your answer, I use LILO but that root is refering to presisely the root partition, in my case it its /dev/hda5... It is well configured in lilo, I can enter with kernel 2.4... but not with 2.6...
if you want to know, the exact Kernel error at the begining is:

VFS: Cannot open root device "305" or hda5
Please append a correct "root=" boot option

Kernel panic: VFS: Unable to mount root fs on hda5

but I know hda5 is the partition, maybe there has something to be with the fact that the root partition is logical, in the extended partiton... I mean is not a primary partition... could this be true???

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAAN4SOGkG8a1Mf+oRAqD6AJ0UJi0lArcbh8SPk6b+z8jIdPULPwCgrTOE IeWde/UI3AjoojonFRtB9AY=
=YXTH
-----END PGP SIGNATURE-----

Thats an excellent question, unforch I don't know the definitive answer. But to put that fear to rest, my / partition is on /dev/hda7, and /root is on /dev/hda5. I would think that if thats a problem, I would have seen it, and I've been setup that way for the last 6 months or so.

That really shouldn't make any more difference than putting /usr on a seperate drive does, which is no diff, at least here.

Sorry Pablo, but I'm fresh out of ideas. But there may be enough clues here that someone else can chime in.

Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Hmm - no information at all?

Let me search the archives.

Aha. Boot, and give boot parameter "hda=remap63".

Andries

Im sorry, it didnt work...

Nevertheless that was the right answer.
(Or at least part of the right answer.)

Since you provide precisely zero information, it is impossible to provide any further assistance.