Slack 13.1 doesn't detect IDE HDD on old Toshiba Satellite 2140CDS
Good morning...
I'm not a distro hopper, but I have an old laptop at home (a Toshiba Satellite 2140CDS with AMD K6-2 processor, 192 MB RAM, and 20 GB IDE HDD) that I dropped Tiny Core Linux to see if it would run. And run it did, so I figured I would install Slackware (same as my desktop) onto the hard drive. I had to use the huge.s kernal since hugesmp.s complains about a missing function and then stops booting. The problem is Slack 13.1 doesn't even recognize the hard drive (or CD drive it would seem). There's nothing under /dev that looks like sd* (or hd*). Nothing in /etc/fstab either. I don't have the dmesg of either Slack 13.1 install CD or tiny core handy, but I noticed in TC's dmesg it referred ide_pci_generic just before showing the hard drive and CD drive info. Nothing like that in Slack's dmesg. I looked through some of the doc's and I understand all drives are now SCSI (real or emulated) so I should see sda and sdb (for my HDD and CD) but I don't. Both TC and Slack complained about some PCI memory conflict but I don't have the specifics handy. None-the-less, TC was able to see my drives so I don't think that's the problem (in this case). Anyone have any ideas what I need to do to get Slack 13.1 to see my drives? Thanks, |
In my Slackware 13.1 IDE drive is recognized as /dev/sda and CD-ROM drive is recognized as /dev/sr0. Assuming you suspect the problem with your Toshiba Satellite 2140CDS is caused by new kernel you could try Slackware 13.0 which recognizes IDE drive as /dev/hda. It's just idea. I can't guarantee the positive result of that experiment.
|
the problem is this you did not give me your install steps. you mean slackware does not see your drive to install? little help.
huge.s acpi=off Quote:
you mean you are unable to see the drives in GUI. or CLI your unable to mount drives? put a disk in and in CLI cd /media/cdrom for gui you need to make sure your user has permission hard drive as root type fdisk -l you will se them. I run current on a tosh 2125 and i use xfce4 and built lxde from sbopkg 13.0 for it.whopping 96 mb ram. fluxbox runs ok to. |
I'll try 13.0
Quote:
|
Can't even see drive to install!!!
Quote:
I'll see what happens if I boot with huge.s acpi=off, thanks for the help. |
With my old Toshiba1410, I needed to use the "pci=nomsi" boot option.
|
Thanks for the suggestion
Quote:
|
Did you try Slackware-13.0? I think it should work. If you already downloaded it, then try booting from it, after that switch the disk to 13.1 and install it. Then just start the newly installed system with slackware-13.0 disk and compile your own kernel without libata (but with your driver for ide ;-) ).
|
X-mas project
Quote:
|
Detailed info from Slack 13.0 vs. Slack 13.1
I've got some dmesg, lsmod, lspci -vv, uname -a, and procs/interrupts generated by the Slack 13.0 boot CD (which can see my hard drive and CD) and the Slack 13.1 boot CD (which cannot see my IDE drives).
Slack130.tgz Slack131.tgz Any ideas what I can do to get 13.1 to see my IDE drives? Or is alekow's suggestion the only way to go? Thanks, |
same problem was to me to an pentium 3,cann install debian (tried with lenny (detect hda) and squeeze(detect sda))but not slackware,
only chance was to make an BIOS update and after this i cann install slackware |
Some comparisons in my dmesg and lspci from 13.0 to 13.1
I've done a stare & compare and I've noticed the following differences.
In my dmesg 13.0 vs 13.1 I can see the Uniform Multi-Platform E-IDE driver being loaded and detecting the drives: dmesg 13.0 Code:
loop: module loaded Code:
loop: module loaded lspci 13.0 Code:
00:10.0 IDE interface: Toshiba America Info Systems Extended IDE Controller (rev 34) (prog-if f0) Code:
00:10.0 IDE interface: Toshiba America Info Systems Extended IDE Controller (rev 34) (prog-if f0) Any ideas on how I can get 13.1 to load the driver? Thanks, |
Quote:
|
Changing diapers
Quote:
What about compiling just the pci_ide driver and using the generic kernel with the pci_ide driver in the initrd? What are your thoughts on re-compiling with stock kernel (2.6.33.4) vs. getting the sources for the latest kernel (2.6.36.2)? Could that break other stuff in the system, causing me to have re-compile other parts of Slackware too? I've been looking for tutorials and they're all great at outlining the basic steps but none of the considerations. Thanks, |
Quote:
Quote:
Good luck! :-) |
All times are GMT -5. The time now is 10:36 PM. |