kernel 2.6 problems with sata :(
 

I have been useing slackware for a few years. I have a computer with sata and when I install 10.2 (or 10.1) I use the stock bare.i kernew at install. it works great. I install the sata 2.4 at install its works great. but when I upgrade to the 2.6 kernel, no matter how, source, pkg, recompile pkg, one of 2 things happen. 1. about half way through init it just stops and gives me the # prompt. and i can type on the screen but no responce ot my commands. 2. i get kernel panic and cannot mound block device 302. and nothing works. press reset.
I have compiled the kernel at least a dozen times.
any ideas?
ty

Silly/dumb question first:

Did you compile support for your SATA controller into your kernel (NOT as a module)?

If you compiled it as a module, did you create a new ramdisk (see /boot/README.initrd)

when i compiled it i have tried with sata but it said it was depreciated and tried without. i have tried several combonations.
and yes i have made initrd. i can put this on an ide system and it works. but when i do it on this one (sata) i turn to uber noob. :(

welcome to my nightmare
 

Hey join the club, I got a new dell dimensin 9100 with sata harddrives and I can never get slackware to work correctly
Usually the slackware crashes halfway during install with the same error. Or a netwrk card doesnt work, something stupid like that. Wish I would of bought ide harddrives

What SATA chipset do you have?

have any of you tried using the test26 kernel. It should sata support for most devices.

when i install on my laptop. I install 2.4 bare.i it loads my sata controller in ide mode(which is terribly slow), then I have to build 2.6.**, make sure sata is enabled for my card. compile it, then log in with a live cd and change /etc/fstab and lilo. This is do to all my devices changing from /dev/hda to /dev/sda. Dont know if that's the same problem you are having or not.


soule

Its a pentium d with sata harddrives
 

I'll try that thanks

ok reinstalled and used the test26.s kernel and have same error. here it is.
VFS: Cannot open root decice "302" or unknown-block(3.2)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable ot mount root fs on unknown-block(3,2)
i have tried mkinitrd (as per README.initrd in /boot) and instead of /dev/hda2 (my root part) i put /dev/sda2 still same thing. i get this or just stop about there with a # prompt and nothing else.
im still working on this

im getting the mount /dev/sda1 is not a valid device - think after reading here i have found the issue - i thik all sata is set to be built as modules ;P

with initrd (depending on your fs and setup) should be mkinitrd -c -k 2.6.14.x -m ext2 /dev/hdxX (or sdx (or ext3/reiserfs)

i have never put the hard drive bit in and it always seems to know where to put it even when i have dual booted a sytem :)

tried both. /dev/sdaX and /dev/hdaX
this has got to be simple
grr this is gettign frustrating :/
thanks to everyone so far
im still trying will post what i find

im still getting the error wether i use m or built in - had theis with the cdrom and solved it by editing the link in /dev/ sata works on 2.4 but mu chipset isnt supported so everything is a bit slow and jerky :( anyone with any idears ?

Thanks

ok i wiped everything and started over again this time in fstab i added /dev/sda2 and all the normal input that follows. so i have /dev/hda2 in my fstab as my root. this is the way it was installed and setup. i ran mkinitrd exactly as it is in README.initrd for an ext3 fs. updated lilo. reboot and i got
mount: Mounting /dev/hda2 on /mnt failed: No such decice or address
ERROR: mount returned error code 1. Trouble ahead.
mount: Mounting /dev/hda2 on /mnt failed: Invalid argument
mount: Mounting /dev/hda2 on /mnt failed: Invalid argument
/boot/initrd.gz: exiting
pivot_root: pivot_root: Device or resource busy
Freeing unused kernel memory: 160k freed
#
at the pound mark above i have a bliniking curser and it appears to be a bare shell. some limited commands.
Oh by the way. I like the part about "Trobule ahead". ummm ....... ya think? :/
anyway im gonna try to change lilo to look for root in /dev/sda2 and see how it dies then.

well its obvious no one knows how to fix this but for some reason I wil keep posting here.
when my lilo.conf is like this
image = /boot/vmlinuz
root = /dev/hda2
label = Linux
read-only
i get this error
VFS: Cannot open root decice "302" or unknown-block(3.2)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable ot mount root fs on unknown-block(3,2)
now, when i change lilo.conf to
image = /boot/vmlinuz
root = /dev/sda2
label = Linux
read-only
i get this
VFS: Cannot open root decice "802" or unknown-block(8.2)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable ot mount root fs on unknown-block(8,2)
I thought it was being seen as scsi is why i changed from hda to sda. have same error just different number.
i cant help but think this has to be something simple
some has to know how or at least have an idea.

if your using 2.6 kernel u have to make a initrd so it knows what it has to use to boot

from a site i found

guessing its just a case of adding more modules to the initrd so it sees the sata drives, from the error you have posted about i have had and its because
a) initrd was not made
b) line in lilo/grub wasnt there

hth

http://www.linuxquestions.org/questi...d.php?t=365074 - read my post. Maybe it would help.