SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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?
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.
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 02:13 PM.
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
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.
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???
EDIT: I'd just like to add that my BIOS has only "standard ide" and "enhanced ide (normal)". There is no mention of combined..
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
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 04:08 PM.
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.
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.