You are not logged in.

#1 2009-10-06 12:01:35

Lexion
Member
Registered: 2008-03-23
Posts: 510

My self-compiled kernel doesn't see my harddrive

During boot, it says "waiting 10s for /dev/sda1" and then since it doesn't exist after 10s it brings me to the ramfs$ shell.  I ran:

$ echo dev/sda*
sda

There was not fdisk program, so I couldn't check if it was valid.  The default Arch kernel works fine so I'm guessing it's a problem with either my mkinitcpio.conf file for the selfbuild kernel or it's .config build configuration.

Does anybody have this problem or a way to fix it?

Last edited by Lexion (2009-10-06 12:02:01)


urxvtc / wmii / zsh / configs / onebluecat.net
Arch will not hold your hand

Offline

#2 2009-10-06 12:48:48

ngoonee
Forum Fellow
From: Between Thailand and Singapore
Registered: 2009-03-17
Posts: 7,356

Re: My self-compiled kernel doesn't see my harddrive

Hard to tell what exactly you're doing wrong when we can't see your mkinitcpio.conf.

Go install hwdetect, use it to find out what modules you need, compile them in and include them in mkinitcpio.conf if you're not using the autodetect hook.


Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

Offline

#3 2009-10-06 14:01:52

legolas558
Member
Registered: 2009-09-08
Posts: 97

Re: My self-compiled kernel doesn't see my harddrive

Use these hooks

HOOKS="base udev autodetect resume ide pata sata scsi filesystems"

it should work on most systems

Edit: you might also want to give a look to http://bbs.archlinux.org/viewtopic.php?id=81434

Last edited by legolas558 (2009-10-06 14:03:46)


.-.   ,---,---.--.
| |__  \ \ \ \`//.
`----'`--'`--'`--'

Offline

#4 2009-10-06 15:00:58

Lexion
Member
Registered: 2008-03-23
Posts: 510

Re: My self-compiled kernel doesn't see my harddrive

  1 # vim:set ft=sh
  2 # MODULES
  3 # The following modules are loaded before any boot hooks are
  4 # run.  Advanced users may wish to specify all system modules
  5 # in this array.  For instance:
  6 #     MODULES="piix ide_disk reiserfs"
  7 MODULES="ext3"
  8 
  9 # BINARIES
 10 # This setting includes, into the CPIO image, and additional
 11 # binaries a given user may wish.  This is run first, so may
 12 # be used to override the actual binaries used in a given hook.
 13 # (Existing files are NOT overwritten is already added)
 14 # BINARIES are dependancy parsed, so you may safely ignore libraries
 15 BINARIES=""
 16 
 17 # FILES
 18 # This setting is similar to BINARIES above, however, files are added
 19 # as-is and are not parsed in anyway.  This is useful for config files.
 20 # Some users may wish to include modprobe.conf for custom module options,
 21 # like so:
 22 #    FILES="/etc/modprobe.conf"
 23 FILES="/etc/modprobe.d/modprobe.conf"
 24 
 25 # HOOKS
 26 # This is the most important setting in this file.  The HOOKS control the
 27 # modules and scripts added to the image, and what happens at boot time.
 28 # Order is important, and it is recommended that you do not change the
 29 # order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
 30 # help on a given hook.
 31 # 'base' is _required_ unless you know precisely what you are doing.
 32 # 'udev' is _required_ in order to automatically load modules
 33 # 'modload' may be used in place of 'udev', but is not recommended
 34 # 'filesystems' is _required_ unless you specify your fs modules in MODULES
 35 # Examples:
 36 #    This setup specifies all modules in the MODULES setting above.
 37 #    No raid, lvm2, or encrypted root is needed.
 38 #    HOOKS="base"
 39 #
 40 #    This setup will autodetect all modules for your system and should
 41 #    work as a sane default
 42 #    HOOKS="base udev autodetect pata scsi sata filesystems"
 43 #
 44 #    This is identical to the above, except the old ide subsystem is
 45 #    used for IDE devices instead of the new pata subsystem.
 46 #    HOOKS="base udev autodetect ide scsi sata filesystems"
 47 #
 48 #    This setup will generate a 'full' image which supports most systems.
 49 #    No autodetection is done.
 50 #    HOOKS="base udev pata scsi sata usb filesystems"
 51 #
 52 #    This setup assembles an pata raid array with an encrypted root FS.
 53 #    Note: See 'mkinitcpio -H raid' for more information on raid devices.
 54 #    HOOKS="base udev pata raid encrypt filesystems"
 55 #
 56 #    This setup loads an lvm2 volume group on a usb device.
 57 #    HOOKS="base udev usb lvm2 filesystems"
 58 HOOKS="base udev autodetect pata scsi sata filesystems usb" # ORIGINAL
 59 #HOOKS="base udev sata" # MOD
 60 
 61 # COMPRESSION
 62 # Use this to compress the initramfs image. With kernels earlier than
 63 # 2.6.30, only gzip is supported, which is also the default. Newer kernels
 64 # support gzip, bzip2 and lzma.
 65 #COMPRESSION="gzip"
 66 #COMPRESSION="bzip2"
 67 #COMPRESSION="lzma"

my mkinitcpio.conf.

EDIT:  I tried your hooks, and it didn't work.  Same error.

Last edited by Lexion (2009-10-06 15:05:32)


urxvtc / wmii / zsh / configs / onebluecat.net
Arch will not hold your hand

Offline

#5 2009-10-07 11:39:12

Vamp898
Member
From: 東京
Registered: 2009-01-03
Posts: 907
Website

Re: My self-compiled kernel doesn't see my harddrive

Compile your filesystem driver directly into the kernel (not as module) and it should work

Offline

#6 2009-10-07 13:30:56

Army
Member
Registered: 2007-12-07
Posts: 1,784

Re: My self-compiled kernel doesn't see my harddrive

I had this problem as well once, here it was caused by a really crappy config wink

Offline

Board footer

Powered by FluxBB