Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
|
03-22-2006, 01:07 PM
|
#1
|
Member
Registered: Mar 2004
Posts: 47
Rep:
|
SATA and Kernel 2.6.16
I am trying to get the 2.6.16 kernel to install on a dell SX280
The propblem is the SATA drive. [i get panic errors]
I have seached and seached but am not sure what is going on.
in the bios to get version 10.2 to install I had to enable the combined mode and I had use the sata.i image to install
I am not sure which option to enable r set as modules for this SATA drive.
Can anyone help?
|
|
|
03-22-2006, 02:51 PM
|
#2
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
I can.
1)Firsly, tell me what is your controller in motherboard for sata.
2)You can check if it is mentioned in kernel configuration.
3)If you found it, you should compile it into the kernel.
4)Disable all other not yours controllers because they all are arguing with each other and give kernel panics.
5)Enable scsi_sata support, disable ide_sata support (it is deprecated).
6)Compile your filesystem support into the kernel.
7)Edit fstab and change hd* to sd* (don't know if it really affects how system boots (and so kernel panics) but it would be very good to do after successful reboot). Maybe someone could enlighten me about this issue.
|
|
|
03-22-2006, 03:06 PM
|
#3
|
Member
Registered: Jun 2004
Distribution: gentoo 2008.desktop
Posts: 110
Rep:
|
Hi. Precisely the same problem here. I have no idea what my onboard controller is. My laptop is a Toshiba which has only basic details here: http://www.edmunds-enterprises.com/l...SIN/B000DT85ZK
Quote:
5)Enable scsi_sata support, disable ide_sata support (it is deprecated).
|
Where can I find these settings? I use make menuconfig.
- slacker
|
|
|
03-22-2006, 03:08 PM
|
#4
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
If I am right, they should be under device drivers. Scsi under scsi block and ide under ide block. Look carefully and you won't miss. Don't know about controller. Maybe Intel SATA controler would be appropriate. Don't know really. Maybe somebody else owns this laptop. Didn't you get any docs with your computer?
Last edited by Alien_Hominid; 03-22-2006 at 03:13 PM.
|
|
|
03-22-2006, 04:00 PM
|
#5
|
Member
Registered: Mar 2004
Posts: 47
Original Poster
Rep:
|
I did a search and i think this is the controller
Intel Corp. I/O Controller Hub SATA cc=ide
Class 0x1018f: Mass storage controller/IDE interface
this this part
7)Edit fstab and change hd* to sd* (don't know if it really affects how system boots (and so kernel panics) but it would be very good to do after successful reboot). Maybe someone could enlighten me about this issue.
goof up my existing kernel? it is set to look to hda2 and boots no problem
|
|
|
03-22-2006, 04:09 PM
|
#6
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
If your new sata enabled kernel will work, it will search for sda rather than hda.
|
|
|
03-22-2006, 04:11 PM
|
#7
|
Member
Registered: Mar 2004
Posts: 47
Original Poster
Rep:
|
does this then mean i should change it on lilo for both entires?
|
|
|
03-22-2006, 04:33 PM
|
#8
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
You can try setting sda for the new kernel and leaving hda for the old one. Here is mine:
Code:
boot = /dev/sda
default = Muvo
image = /boot/vmlinuz-2.6.16-rc5
root = /dev/sda3
label = Muvo
read-only
image = /boot/vmlinuz
root = /dev/hda3
label = Linux-Original
read-only
If it does not boot, use Slackware 1CD and restore previous values in lilo.
My fstab:
Code:
/dev/sda3 / ext2 defaults 1 1
/dev/sda1 /ntfs-c ntfs ro 1 0
/dev/sda5 /ntfs-d ntfs ro 1 0
/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
none /sys sysfs defaults 0 0
Last edited by Alien_Hominid; 03-22-2006 at 04:36 PM.
|
|
|
03-22-2006, 04:38 PM
|
#9
|
Senior Member
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,141
Rep:
|
With the Dell Optiplexes here, when the disk mode is set to combined, Slackware sees the drive as IDE (hda) and with the mode set to normal it sees it as sda. If you have problems with configuring lilo, try making sure that your kernel supports both and toggle the BIOS settings again.
|
|
|
03-22-2006, 04:41 PM
|
#10
|
Member
Registered: Jun 2004
Distribution: gentoo 2008.desktop
Posts: 110
Rep:
|
Ok here's an update on the situation. In lilo after selecting my kernel (2.6.16) I set root=/dev/sda4 as a parameter (which I can make permanent in lilo.conf) just to see if it would boot. The kernel panic went away! However, it fails to check disk! For some odd reason it STILL sees the partition as ext2! Even if I explicitly make an initrd for ext3!
Anyway after the check disk fails, also with a warning that swap doesn't exist (because fstab says its /dev/hda3 and not /dev/sda3), it allows me to login as root to "correct the problem" and tells me to run sbin/chkfs (im not sure of the spelling sorry) manually.
I do so, but using /dev/sda4 instead of /dev/hda4 and the checkdisk completes! However as soon as I exit the single user mode it reboots. So my questions are these:
1) how can I make it use ext3 and not ext2? I've already compiled IN ext2/3/jbd support!
2) how can I make checkdisk check sda4 and not hda4? This happens every boot.
3) how can I change fstab to use sdaX instead of hdaX and STILL retain the hdaX for my 2.4 kernel???
- slacker
EDIT: I'd just like to add that my BIOS has only "standard ide" and "enhanced ide (normal)". There is no mention of combined..
Last edited by alphisb0t; 03-22-2006 at 04:49 PM.
|
|
|
03-22-2006, 04:47 PM
|
#11
|
Member
Registered: Mar 2004
Posts: 47
Original Poster
Rep:
|
I have it set to combined and it does not see the hda for 2.6 but works fine for 2.4
if I HAVE tomess with fstab i will but i would prefer not too.
I even took a look at a suse 10 kernel config file [suse 10 was installed on another identical machine that works fine with its 2.6 kernel] I may just try and cimpile the kernel with that
if i had haor it would all be pulled out now
|
|
|
03-22-2006, 05:07 PM
|
#12
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
My hackish and bad solution: in your lilo.conf comment read only section after your new kernel. Then reboot. It will complain about not read only system but won't reboot.
I think that suse's configuration is slightly different from Slackware due their patched kernel.
Last edited by Alien_Hominid; 03-22-2006 at 05:08 PM.
|
|
|
03-22-2006, 09:26 PM
|
#13
|
Member
Registered: Jun 2004
Distribution: gentoo 2008.desktop
Posts: 110
Rep:
|
Ok here's another update. I've changed everything in fstab to point from hdaX to sdaX. This along with setting my lilo.conf to everything hdX to sdX has fixed all problems booting the 2.6 kernel.
What I have learned is that simply having a root=/dev/sda4 when booting 2.6 is NOT enough. The reason is because although it can see the partition, when it checks fstab it STILL uses the data there to do things such as fsck. And when fstab says hda and not sda there will be problems.
My 2.6 kernel boots perfectly now. I've even got ndiswrapper detecting my wireless card (although when I modprobe after turning it on the system hangs then reboots). But at least its being detected ;P
My current issue is finding those alleged sk98lin drivers for my Marvell Yukon WIRED card (yes I have a wired one too). Unfortunately EVERY single piece of information refers to a site which NO LONGER HAS those drivers. Apparently sky-whoever decided that supporting linux wasn't fun anymore.
I hope someone else can get their kernel up from my small but interesting finds.
- slacker
|
|
|
03-23-2006, 01:36 AM
|
#14
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
You can choose sk98lin driver from linux kernel (there is an option for it).
|
|
|
03-23-2006, 08:51 AM
|
#15
|
Member
Registered: Jun 2004
Distribution: gentoo 2008.desktop
Posts: 110
Rep:
|
Yes I've only recently noticed the drivers for Yukon chipsets there, as well as some newer ones above it. I didn't catch the "New yukon" or the other one simply because I had assumed it would start with "Marvell". I now have built in support for my wired ethernet card!
Wireless is now the issue ;P I have tried both ndiswrapper and ipw2200 with failures resulting in the dmesg log.
I'd just like to point out that the option to "allow firmware" does not exist, only its negative. "disallow firmware to be built" and some other negative. By unchecking them I assume that it has been enabled. Grepping the .config file reveals that CONFIG_FW_LOAD is =y. So it should be fine.
- slacker
|
|
|
All times are GMT -5. The time now is 03:08 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|