Find the answer to your Linux question:
Page 1 of 4 1 2 3 4 LastLast
Results 1 to 10 of 40
My Kernal seems to not recognize my sata hd's when it gets to vfs it crash's. Im as fresh as they come to linux but i followed this site's direction ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jul 2005
    Posts
    15

    Kernel 2.6.10 won't recognize my sata HD I think


    My Kernal seems to not recognize my sata hd's when it gets to vfs it crash's. Im as fresh as they come to linux but i followed this site's direction in makeing it. http://www.linuxquestions.org/questions/answers/408


    heres my lilo file
    # LILO configuration file
    # generated by 'liloconfig'
    #
    # Start LILO global section
    boot = /dev/hda
    message = /boot/boot_message.txt
    prompt
    timeout = 1200
    # Override dangerous defaults that rewrite the partition table:
    change-rules
    reset
    # VESA framebuffer console @ 1024x768x256
    vga = 773
    # Normal VGA console
    # vga = normal
    # VESA framebuffer console @ 1024x768x64k
    # vga=791
    # VESA framebuffer console @ 1024x768x32k
    # vga=790
    # VESA framebuffer console @ 1024x768x256
    # vga=773
    # VESA framebuffer console @ 800x600x64k
    # vga=788
    # VESA framebuffer console @ 800x600x32k
    # vga=787
    # VESA framebuffer console @ 800x600x256
    # vga=771
    # VESA framebuffer console @ 640x480x64k
    # vga=785
    # VESA framebuffer console @ 640x480x32k
    # vga=784
    # VESA framebuffer console @ 640x480x256
    # vga=769
    # End LILO global section
    # Slack NEW begins
    image = /boot/vmlinuz-2.6.10
    root = /dev/hda1
    label = Slack_2.6.10
    read-only
    # Slack NEW ends
    # Slack OLD begins
    image = /boot/vmlinuz-old
    root = /dev/hda1
    label = Slack_OLD
    read-only
    # Slack OLD ends

  2. #2
    Linux Newbie
    Join Date
    Apr 2005
    Location
    CT --> PA
    Posts
    170
    ok that's a good faq to follow (never had any problems w/ it for me or anyone else i pointed it to), but i think the problem may lie within the options you chose (or didn't choose, more appropriately). Did you include things like the SATA modules in the kernel? If your system is dependant on them for things like booting, i would go and include them into the system as a compiled resource, rather than a module...prevents you from not loading them)
    Chicks dig giant mechanized war machines

  3. #3
    Just Joined!
    Join Date
    Jul 2005
    Posts
    15

    I might of found the kernal problem

    check this pic out if you think this is a problem. And can you say Dumb a$$.

    http://img341.imageshack.us/img341/8237/stooge4ao.png

  4. #4
    Linux Enthusiast puntmuts's Avatar
    Join Date
    Dec 2004
    Location
    Republic Banana
    Posts
    562
    SATA drivers are in the SCSI section, not the ATA section. You'll find them in the SCSI low-level drivers menu.
    I\'m so tired .....
    #200472

  5. #5
    Just Joined!
    Join Date
    Jul 2005
    Posts
    15

    hmm

    Well I did that.....

  6. #6
    Linux Newbie
    Join Date
    Apr 2005
    Location
    CT --> PA
    Posts
    170
    so you had the SATA libata drivers selected when you compiled that kernel? Do you recall if they compiled correctly? did you see any erros when you put them in? And are they loading correctly when you try to boot, or are you seeing errors there? (just trying to figure out if they're even in your kernel, or in there and not working)
    Chicks dig giant mechanized war machines

  7. #7
    Just Joined!
    Join Date
    Jul 2005
    Posts
    15

    ?????

    alright I tried rebuilding my kernal again and I selected the lowlevel scsi sata, and the sata labata. Well Now Im on re-install #5 with linux which is great way to learn but its pretty time consumeing. I read some where that in lilo you need to have it as sda1 instead of hda1???? I have a western digital 40 gb sata hd. Also the kernal Panick error was---VFS CANNOT OPEN ROOT DEVICE 301 OR UNKNOWN BLOCK 3,1. The only reason I think its not recognizeing my drive is because when it goes through the device init it shows my cd drive recognized but not my hd---on kernal 2.4 it shows it recognizeing my wdc drive. also as a side note upon reloading Sware 10 i choose the sata.i kernal load from setup. ??????

  8. #8
    Just Joined!
    Join Date
    Jul 2005
    Posts
    15

    maybe the prob

    Unless this came unchecked in the config file i dl'd i might have to have this unchecked because slackware uses udev?.My main problem Right now is I dont know what the hell im doing.

    File Systems --->
    Psedo File Systems --->
    [ * ] devfs support (OBSOLETE)
    [ * ] Automatically mount at boot

  9. #9
    Linux Enthusiast puntmuts's Avatar
    Join Date
    Dec 2004
    Location
    Republic Banana
    Posts
    562
    Udev is the successor of devfs. If you use kernel 2.6.x better use udev and leave out devfs which is unmaintained anyway.

    Since you use a scsi libata driver I guess the drive will be /dev/sda and the partition /dev/sda1 or something. Udev will take care of creating devicefiles for it in /dev .
    I\'m so tired .....
    #200472

  10. #10
    Just Joined!
    Join Date
    Jul 2005
    Posts
    15

    ok

    Round 6 well see what happens this time....
    also check this out. It Turns Out I have to do a setting in the bios . it looks like I have to change it back everytime i want to boot windows... I will see if it works. Thats what I get for being lazy and not building my own comp. If I can get Starcraft and half life 2 configured i wont need windows but thats probably in 5 more reloads.
    https://www.redhat.com/archives/fedo.../msg06567.html

Page 1 of 4 1 2 3 4 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •