Re: Kernel 2.6.8 won't boot

From: Muhammad Reza (reza_at_mra.co.id)
Date: 01/03/05

  • Next message: Alan Chandler: "Re: Sarge" 
    Date: Tue, 04 Jan 2005 02:05:16 +0700
To: Eric Gaumer <gaumerel@ecs.fullerton.edu>

    Eric Gaumer wrote:

    >On Tue, 2005-01-04 at 01:23 +0700, Muhammad Reza wrote:
    >
    >
    >>Eric Gaumer wrote:
    >>
    >>
    >>
    >>>On Tue, 2005-01-04 at 00:44 +0700, Muhammad Reza wrote:
    >>>
    >>>
    >>>
    >>>
    >>>>Dear Lists,
    >>>>
    >>>>I'm stuck with compiling debian kernel-2.6.8 source at Sarge, this is
    >>>>what exactly i did...
    >>>>
    >>>>debian:/usr/src# ln -s kernel-source-2.6.8 linux
    >>>>debian:/boot# cd /usr/src/linux
    >>>>debian:/usr/src/linux# cp /root/config .config
    >>>>debian:/usr/src/linux#patch -p1 </root/bootsplash-3.1.6-2.6.8.diff
    >>>>debian:/usr/src/linux#make menuconfig
    >>>>debian:/usr/src#make-kpkg --initrd --revision=custom.1.0 kernel_image
    >>>>----sucess-----
    >>>>debian:/usr/src/linux# cd ../
    >>>>debian:/usr/src# ls
    >>>>kernel-image-2.6.8_custom.1.0_i386.deb kernel-patches
    >>>>kernel-source-2.6.8 kernel-source-2.6.8.tar.bz2 linux
    >>>>debian:/usr/src# dpkg -i kernel-image-2.6.8_custom.1.0_i386.deb
    >>>>---sucess---
    >>>>
    >>>>but new compile kernel wont boot with this error...
    >>>>
    >>>>RAMDISK: cramfs file system found at block 0
    >>>>RAMDISK: loading 3620 block [1 disk] into ramdisk done..
    >>>>Kernel Panic:VFS:unable to mount root fs on unknown_block(3.1)
    >>>>
    >>>>please help me...to solved this problem..
    >>>>here is .config and menu.lst in attach....
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>>Since you are using a ramdisk, it would be helpful if you could post the
    >>>contents of the loadmodules file on the ramdisk itself. You are most
    >>>likely missing some modules needed to mount the filesystem since (3,1)
    >>>is hda1.
    >>>
    >>>]$ mount -o loop /boot/initrd-xxx /mnt/tmp
    >>>]$ cat /mnt/tmp/loadmodules
    >>>
    >>>lspci may also help.
    >>>
    >>>What kernel are you currently running? Any special file system stuff
    >>>like RAID or SATA?
    >>>
    >>>
    >>>
    >>>
    >>>
    >>Thanks for good advice
    >>
    >>this differnet betwen 2.4.7 and 2.6.8 loadmodules..
    >>---2.4.7----
    >>debian:/mnt/tmp# cat loadmodules
    >>modprobe -k vesafb > /dev/null 2>&1
    >>modprobe -k fbcon 2> /dev/null
    >>modprobe -k unix 2> /dev/null
    >>modprobe -k pdc202xx_new > /dev/null 2>&1
    >>modprobe -k trm290 > /dev/null 2>&1
    >>modprobe -k triflex > /dev/null 2>&1
    >>modprobe -k siimage > /dev/null 2>&1
    >>modprobe -k adma100 > /dev/null 2>&1
    >>modprobe -k cs5530 > /dev/null 2>&1
    >>modprobe -k rz1000 > /dev/null 2>&1
    >>modprobe -k ns87415 > /dev/null 2>&1
    >>modprobe -k pdc202xx_old > /dev/null 2>&1
    >>modprobe -k alim15x3 > /dev/null 2>&1
    >>modprobe -k sc1200 > /dev/null 2>&1
    >>modprobe -k generic > /dev/null 2>&1
    >>modprobe -k opti621 > /dev/null 2>&1
    >>modprobe -k piix > /dev/null 2>&1
    >>modprobe -k hpt366 > /dev/null 2>&1
    >>modprobe -k hpt34x > /dev/null 2>&1
    >>modprobe -k serverworks > /dev/null 2>&1
    >>modprobe -k amd74xx > /dev/null 2>&1
    >>modprobe -k aec62xx > /dev/null 2>&1
    >>modprobe -k via82cxxx > /dev/null 2>&1
    >>modprobe -k sis5513 > /dev/null 2>&1
    >>modprobe -k slc90e66 > /dev/null 2>&1
    >>modprobe -k cy82c693 > /dev/null 2>&1
    >>modprobe -k atiixp > /dev/null 2>&1
    >>modprobe -k cmd640 > /dev/null 2>&1
    >>modprobe -k cmd64x > /dev/null 2>&1
    >>modprobe -k ide-detect
    >>modprobe -k ide-disk
    >>
    >>--2.6.8---
    >>modprobe -k unix 2> /dev/null
    >>modprobe -k ata_piix
    >>modprobe -k sd_mod
    >>modprobe -k cs5520 > /dev/null 2>&1
    >>modprobe -k cs5530 > /dev/null 2>&1
    >>
    >>I'm now confused, in my .config for 2.6.8 kernel (attach..) , all module
    >>that need it already enabled, fyi i get this .config from Suse-9.1
    >>
    >>I dont have spesial file system like you said, i just this kernel to be
    >>portable...
    >>
    >>
    >>
    >
    >Okay ata_piix leads me to believe you are using SATA. Is this correct?
    >The new API (libata) scans for drives on the SCSI bus. Try
    >root=/dev/sda1 (edit the grub entry at boot)
    >
    >
    >
    Sorry, is not correct, my drive is hda ...

    regards
    reza 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Alan Chandler: "Re: Sarge"

    Relevant Pages

    • [PATCH 18-rc2] Fix typos in /Documentation : N-P
      ... Again, if you're not gonna do synchronization with disk drives (dang, ... -the kernel. ... There are two options specific to PSX driver portion. ... The driver uses the settings from the EEPROM set in the SCSI BIOS ...
      (Linux-Kernel)
    • Re: disk speed regression kernel 2.6.29 and after
      ... When I installed kernel 2.6.30, ... I currently have 3 hard drives hooked up. ... ACPI: ... CPU: L2 Cache: 512K ...
      (Linux-Kernel)
    • Major SATA / EXT3 Issue?
      ... I am curious if anyone else has had major problems with SATA drives on ... basis for my kernel build and test processes. ... Because I focused on hardware as the reason for the failure I ... # AX.25 network device drivers ...
      (Linux-Kernel)
    • Re: Slow disks.
      ... Someone suggested we try an older kernel as if kernel 2.6.32 would not ... support DPO or FUA ...     Western Digital Caviar Green (Adv. ... Where it seems that WD simply says not to use these drives in a RAID. ...
      (Linux-Kernel)
    • Re: Weird kernel errors
      ... This may be related to the kernel error message: ... >> The second is that my hard disks won't accept DMA enabling, ... No DMA on any of the drives. ... > allotted partitions if they aren't "right"). ...
      (uk.comp.os.linux)