SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For first sorry for my bad english )
Well now I have installed slackware 10 creating of the bootdisk with the SATA.i rows found on Internet and after I have tried to install kernel the 2.6.7 but to the reboot I have received a kernel panic because as partition sees alone hde and not sda ok?
Hmmm. It's a little hard to understand you still but from what I gather, You used Bonecrushers sata.i disk to install Slackware 10. That worked just fine and you were able to boot up your Slackware for the first time and then get to your desktop. Then you installed the 2.6.7 kernel from Slackware disk and recompiled but now it wont boot stating that it see's your hard drive as HDA and not SDA?
If thats the case, it sounds as if you didn't enable SATA support in your kernel. That won't be checked by default. It's located in:
Device Drivers --->
SCSI device support --->
SCSI low-level drivers --->[*] Serial ATA (SATA) support
Put that little star next to SATA support and then put a star next to your hard drive controller. Look at the output of:
lspci
If you can still boot your old kernel.
If none of this applies to you, sorry. It's just hard to know whats going on by your posts other than "your computer won't start"...
I have a problem with a sata hard disk. I use slackware 10 / Kernel 2.4.26 and the promise driver so I have in my fstab /dev/sda1, /dev/sda2, ... Now I want to use the Kernel 2.6. I make the initrd with mkinitrd : mkinitrd -c -k 2.6.7 -m scsi_mod:libata:sata_promise -f ext3 -r /dev/sda7 -o initrd-2.6.7.img and when I boot I have these messages :
# Modules loaded successfully ...
ata1: SATA max UDMA/133
ata2: SATA max UDMA/133
ata1: no device found
scsi0: sata_promise
ata2: dev 0 ATA, max UDMA/133, ...
ata2: dev 0 configured for UDMA/133
scsi1: sata_promise
VENDOR: ATA MODEL: ST3120026AS REV: 3.05
TYPE: Direct-Access
mount: Mounting /dev/sda7 on /mnt failed: No such device or address
mount: Mounting /dev/sda7 on /mnt failed: Invalid argument
mount: Mounting /dev/sda7 on /mnt failed: Invalid argument
/boot/initrd.gz : exiting
pivot_root : Device or ressource busy
... and then I have a prompt and the system is not going to boot !
Originally posted by jong357 Hmmm. It's a little hard to understand you still but from what I gather, You used Bonecrushers sata.i disk to install Slackware 10. That worked just fine and you were able to boot up your Slackware for the first time and then get to your desktop. Then you installed the 2.6.7 kernel from Slackware disk and recompiled but now it wont boot stating that it see's your hard drive as HDA and not SDA?
If thats the case, it sounds as if you didn't enable SATA support in your kernel. That won't be checked by default. It's located in:
Device Drivers --->
SCSI device support --->
SCSI low-level drivers --->[*] Serial ATA (SATA) support
Put that little star next to SATA support and then put a star next to your hard drive controller. Look at the output of:
lspci
If you can still boot your old kernel.
If none of this applies to you, sorry. It's just hard to know whats going on by your posts other than "your computer won't start"...
i have enabled the sata support but without results see's alway as hde and not as sda
Originally posted by cris81 i have enabled the sata support but without results see's alway as hde and not as sda
Try this:
Code:
boot: noprobe=/dev/hde
What kind of chipset do you have? VIA perhaps?
-bc
PS:
The HDE is used here as whatever HD device is coming up for you. You want it to probe for sata device before IDE... Sometimes this has been known to work.
Yes i have via VT8237 well now it see's the dev as sdb beacuse during the boot it says this:
scsi device sda
sda unknow partition table
why?
help me please
Originally posted by cris81 Yes i have via VT8237 well now it see's the dev as sdb beacuse during the boot it says this:
scsi device sda
sda unknow partition table
why?
help me please
hmm, I am not sure whats wrong now. It all depends on how you compiled your kernel. Did you pick your particular partitions from partition area (in .config file) in configuration? Did you enable your filesystem(s) in the config? (make menuconfig and recompile.) It is more then likely something you did (or more to the point -didn't do) during config'ing your kernel...
bc
Last edited by bonecrusher; 07-18-2004 at 12:58 PM.
Nope .. still not there.. and I don't speak Italian so I am at a loss as to what it is saying. It almost looks like it says wait a moment... but as I said I don't speak It. so not sure. But at any rate the file(s) are not there.
And could you tell us what you did to get you install working?
For the record I tried the SATA.i on my VIA VT8237 controller and it worked like a champ. I was able to get fully installed without a hitch on my AMD 3000 64-bit and recompile my kernel and install it.
One thing that did happen is that during boot/install it detected the drives as /dev/sda and /dev/sdb
When I downloaded the source and recompiled my kernel to 2.6.7 it changed them to /dev/hde and /dev/hdg
Which is no big deal but I did have to go into fstab and change some things around so that my system would boot. So a word of warning ... keep the other kernel in lilo for a while
All I have to say is MAN this distro is fast. Faster than my Gentoo (and yes I know how to use the USE flags) was.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.