Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Ok, this is the second forum I'll be asking this question but oh well, I have to try.
Lately some pieces of hardware (processor, motherboard, ram) were changed on my comp. This caused Kernel panic on my previously installed Slackware 11 on kernel 2.4.x (it had problems with detecting the HDD). Not knowing what caused the problem and after several tries of making things work I tried to reinstall the system.
The thing is that the only kernel which detected my HDD and let me continue the installation process (on other kernels cfdisk showed that he cannot access the hdd) was test26.s. Changing to that kernel from bare.i didn't solve the problem. During installation when trying to choose the source media the cd-rom was not detected.
I tried passing various arguments to the kernel (hdx=cdrom, hdx=ide-scsi - I read about it somewhere but think it shouldn't be needed for 2.6.x kernels ) but nothing worked. I tried switching my SATA disk to Native mode in BIOS. All kernels detected it as hda but still none could read my cd-rom (and I mean none - even the scsi, and even with passing hdx=cdrom/hdx=ide-scsi parameters to the other ones).
My HDD: Seagate ST340016A, interface SATA currently set to Native and working as ATA
My CD-rom: LITE-ON LTR-52327S on IDE ATAPI
I have dmesg from sata.i and test.26.s to provide if it is needed.
Edit: of course on Windows the cd-rom and the hdd both work nicely so I don't think it could be a hardware issue. But I'm a total newbie when it coms to hardware so I may be wrong.
Sorry for all grammar mistakes.
Edit2: Argh, sorry for posting this in the wrong subforum - haven't noticed the one concerning issues with installation.. If some helpful mod could move this I would be very much grateful.
This won't help your situation necessarily but have you tried a live cd from another distro? If you do you could see what the kernel is seeing the cdrom drive as and try passing those kernel parameters.
So you used the test26.s and also installed all the modules, right ?
I guess if it works fine on Window$, everything is probably hooked up right, I'm not very good with hardware so I can't do much if it isn't hooked up right.
I dunno, maybe compile the newest kernel. It shouldn't matter tho, on google, people have been successfully running this drive on Linux even with 2.4.x kernels.
What's the output of:
Code:
ls /proc/ide
and the output of dmesg might be helpful as well
Code:
dmesg
Last edited by H_TeXMeX_H; 01-11-2007 at 09:50 PM.
if i understood it right you werent able to install, so you have not a working slackware system?
than you could consider to install slackware on a linuxpartition from another linuxpartition - its quick and easy (just copy the entire dvd to one partition and select it as source).
than you have a working linux system, probably without a working cd-rom-drive, but then we can go further ...
#dmesg |grep hd #what /dev/hd devices
#lspci -vv #get device information
Just curious, how is the cdrom configured on the ide channel? Do you have more than one device on that channel(ide0 or ide1)? Is the cdrom master or set as slave with the another device? If the cdrom is on ide0 as master then move the cdrom to ide1 as master. Set your boot order in the BIOS. What BIOS and level?
I'm not 100% sure but I think the cd-rom is on ide1 (I'm no good at hardware). It's set as slave, on the same ide I have a dvd drive set as master, and a hdd on sata on the other ide set as master.
(EDIT) Forgot to mention that I've successfully installed the system from a pre-mounted dir on fat partition. I have the test26.s kernel with up-to-date headers and modules (2.6.18). The cdrom is still not detected.
Another thing is that before changing the hardware on 2.4.x kernel my cd-rom drive was recognized as sr0 (SCSI emulation I think). Now neither /dev/sr0 nor /dev/cdrom exist.
Everything is New to Me : I want to Install Slackware
Hi,
I am new to all these. I have used Lilo and Slackware in the past with KDE. However everything was done for me. So I dont remember how to even install Slackware. Let me tell you my issues and I wish someone would be able to help me.
1. I have my old harddrive that has Lilo on it, but I dont remember the password, so I cant pass the log in page, So I want to re install Lilo and Slackware
2. Where can I get the Lilo software and complete "LAY MAN's" installation guide?
3. I can not burn a bootable CD from my burner, what could be the problem. Basically I have burned several CD's now and I have set my BIOS to boot from the CD-ROM, but the machine goes straight to Windows.
4. I have a 80GB hard drive, I have partitioned 50GB and installed WIN on it, but now I want to put Slackware with KDE guwi but I cant even get my machine to boot from the CD.
I tried passing 'hdb=cdrom', 'hdd=cdrom', 'hdb=scsi', 'hdd=scsi' (CD-ROM is set to slave) to the kernel - nothing. I have the option to set my HDD which is on SATA to be recognized as AHCI but what does that have to do with my cdrom?
I've read ide.txt but I don't have a clue what other options should I pass to the kernel aside from 'hsx=cdrom' and 'hdx=scsi'.
I didn't compile my own kernel, I use the standard one from Slackware 11 CD so most probably ide support is built into it.
I tried passing 'hdb=cdrom', 'hdd=cdrom', 'hdb=scsi', 'hdd=scsi' (CD-ROM is set to slave) to the kernel - nothing. I have the option to set my HDD which is on SATA to be recognized as AHCI but what does that have to do with my cdrom?
I've read ide.txt but I don't have a clue what other options should I pass to the kernel aside from 'hsx=cdrom' and 'hdx=scsi'.
I didn't compile my own kernel, I use the standard one from Slackware 11 CD so most probably ide support is built into it.
Hi,
You said earlier that you used the 2.4 kernel with this configuration. When you boot using the 2.4.33, what is the output for dmesg and lspci -vv? This could help in the diagnosis of the problem. The 2.4.33 kernel uses the ide-scsi module.
The 2.6 series kernel uses the ide-cd module. Different, apples and oranges. When you used the 2.4.33 kernel, how was the sata recognized?
The proper pass argument for the 2.6 would be;
'hdd=ide-cd'.
For the 2.4.33;
'hdd=ide-scsi'. That is if your device is /dev/hdd for both 2.4 and 2.6 kernels.
Sometimes the AHCI can create some odd boot behaviors.
Try to disable ahci and boot the slackware install cdrom with the huge26 kernel. Then do the dmesg and lspci -vv to get the device(s) information.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.