Re: Kernel 2.6.8 won't boot

[Muhammad Reza]

Eric Gaumer wrote:
On Tue, 2005-01-04 at 05:19 +0700, Muhammad Reza wrote:
 

Eric Gaumer wrote:
   

On Tue, 2005-01-04 at 02:16 +0700, Muhammad Reza wrote:
     

debian:/usr/src/linux# lspci
0000:00:04.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10)
  

       

This is a serial ATA chipset.
http://www.linuxmafia.com/faq/Hardware/sata.html
Make sure you have sata_via module listed in /etc/mkinitrd/modules and
then re-install the 2.6 kernel (this will create a new initrd image).
Then at boot time, edit grub so that root=/dev/sda1
I know 2.4 shows the drive as hda but 2.6 will see it as sda because
this is how libata works.

     

Almost give up...
I did exactly what this lists suggest...(recompile with sata modules, 
edit grub, and add entry in /etc/mkinitrd/modules)  but it's still 
produce same error when booting the new kernel.
Is there any clue...?

   

The initrd-tools package is a bit problematic these days. How about just
compiling the filesystem stuff directly into the kernel and not using a
ramdisk. This will surely fix things providing you've got everything you
need compiled into the kernel.
If you have any doubts what should be compiled in just add everything
from the loadmodules files on both 2.4 and 2.6. I would also make sure
the SCSI stuff and SATA stuff is in there as well. You could always fine
tune things once you get it booted and can actually see what your using.
Before you try this "long" approach, you may want to list every module
from the 2.4 loadmodules file in /etc/mkinitrd/modules and reproduce the
initrd. Try booting that and see what happens. You are obviously missing
a module somewhere and it's just a matter of finding out which one.
Don't give up now. This whole experience will strengthen your knowledge.
 

I'm suspicions in .config file that i copied from Suse-9.1 /proc/config.gz
The fastest solution that i do now, is install kernel image from source 
list.

regards
reza
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]