Results 1 to 3 of 3
I get this error message when I attempt to boot this kernel.
VFS:Cannot open root device on "303" or unknown block(3,3)
Please append a correct "root=" boot option
Kernel Panic: ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 09-08-2003 #1Just Joined!
- Join Date
- May 2003
- Posts
- 43
Kernel 2.6.0 - test4 Will not boot
I get this error message when I attempt to boot this kernel.
VFS:Cannot open root device on "303" or unknown block(3,3)
Please append a correct "root=" boot option
Kernel Panic: VFS: Unable to mount root fs on unknown-block(3,3)
I have searched google left and right and the only thing I found related to a problem that was fixed before test2 was released.
I have tried seting root to /dev/hda3, and 0303.
---------Lilo.conf file ----------
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
#append="hdc=ide-scsi"
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 120
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x64k
# vga = 791
# Normal VGA console
# vga = normal
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda3
label = Linux
read-only
image = /boot/2.6.0/bzImage
root = /dev/hda3
label = "Linux-2.6.0"
read-only
# Linux bootable partition config ends
------------End Lilo.conf File-------------
Note: The kernel I'm trying to load is /boot/2.6.0/bzImage.
here is my kernel configure file generated by gconfig (graphical configuration utility)
http://www.exoronet.net/files/.config
Any suggestions?
- 09-08-2003 #2
Seems like you have a few things missing this is my lilo.conf
And what partiton is your root partion?? (You can find out in /etc/fstab)Code:# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)', # --------------- `install-mbr(8)', `/usr/share/doc/lilo/', # and `/usr/share/doc/mbr/'. # +---------------------------------------------------------------+ # | !! Reminder !! | # | | # | Don't forget to run `lilo' after you make changes to this | # | conffile, `/boot/bootmess.txt', or install a new kernel. The | # | computer will most likely fail to boot if a kernel-image | # | post-install script or you don't remember to run `lilo'. | # | | # +---------------------------------------------------------------+ # Support LBA for large hard disks. # lba32 # Overrides the default mapping between harddisk names and the BIOS' # harddisk order. Use with caution. #disk=/dev/hde # bios=0x81 #disk=/dev/sda # bios=0x80 # Specifies the boot device. This is where Lilo installs its boot # block. It can be either a partition, or the raw device, in which # case it installs in the MBR, and will overwrite the current MBR. # boot=/dev/hda # Specifies the device that should be mounted as root. (`/') # root=/dev/hda2 # Enable map compaction: # Tries to merge read requests for adjacent sectors into a single # read request. This drastically reduces load time and keeps the # map smaller. Using `compact' is especially recommended when # booting from a floppy disk. It is disabled here by default # because it doesn't always work. # # compact # Installs the specified file as the new boot sector # You have the choice between: bmp, compat, menu and text # Look in /boot/ and in lilo.conf(5) manpage for details # install=/boot/boot-menu.b # Specifies the location of the map file # map=/boot/map # You can set a password here, and uncomment the `restricted' lines # in the image definitions below to make it so that a password must # be typed to boot anything but a default configuration. If a # command line is given, other than one specified by an `append' # statement in `lilo.conf', the password will be required, but a # standard default boot will not require one. # # This will, for instance, prevent anyone with access to the # console from booting with something like `Linux init=/bin/sh', # and thus becoming `root' without proper authorization. # # Note that if you really need this type of security, you will # likely also want to use `install-mbr' to reconfigure the MBR # program, as well as set up your BIOS to disallow booting from # removable disk or CD-ROM, then put a password on getting into the # BIOS configuration as well. Please RTFM `install-mbr(8)'. # # password=tatercounter2000 # Specifies the number of deciseconds (0.1 seconds) LILO should # wait before booting the first image. # delay=1 # You can put a customized boot message up if you like. If you use # `prompt', and this computer may need to reboot unattended, you # must specify a `timeout', or it will sit there forever waiting # for a keypress. `single-key' goes with the `alias' lines in the # `image' configurations below. eg: You can press `1' to boot # `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'. # # message=/boot/bootmess.txt prompt timeout=150 # prompt # single-key # delay=100 # timeout=100 # Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>) # # vga=ask # vga=9 # vga=normal # Kernel command line options that apply to all installed images go # here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in # the Linux kernel `Documentation' directory. # # append="" # Boot up Linux by default. # default=Linux image=/boot/bzImage-2.4.21 label=Linux read-only # restricted # alias=1 image=/boot/vmlinuz-2.2.20-idepci label=LinuxOLD read-only optional # restricted # alias=2 # If you have another OS on this machine to boot, you can uncomment the # following lines, changing the device name on the `other' line to # where your other OS' partition is. # # other=/dev/hda4 # label=HURD # restricted # alias=3
- 09-09-2003 #3Just Joined!
- Join Date
- May 2003
- Posts
- 43
I gave up on slaclware.. not only did it have problems runing this kernel I could not get my sound working..no matter what i did
so now I'm in mandrake. I've gotten sound working and I'm playing with 2.6.0..when I will try to get my vid card working.


Reply With Quote
