LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (https://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   Slack 11.0 not seeing HD when installing on a Dell 1501 (https://www.linuxquestions.org/questions/slackware-installation-40/slack-11-0-not-seeing-hd-when-installing-on-a-dell-1501-a-533291/)

BobTheSlackUser 02-28-2007 11:19 AM

Slack 11.0 not seeing HD when installing on a Dell 1501
 
Hey Guys,

I hope you can help me with this, but as you can tell from my subject description, Slackware 11 cannot recognize my hard drive when Iím trying to install. My computer is a new Dell Inspiron 1501 (can I just say that Truelife is a horrible invention) and I want to get away from Microsoft Vista as soon as I can.

I DO have a good lead on what the problem is however. If you go to this site (http://ubuntu1501.blogspot.com/search/label/sada) youíll see that this dude was able to get Ubuntu to recognize his hard drive by adding the line:

pci=nomsi

to his boot prompt. I think this may be the solution to my problem.

Now, here's where I come to the part that Iím ashamed to admit: I donít know the syntax I should use on Slackware for it to implement the pci=nomsi option. Iíve tried several ways of using this option at the Slackware Boot: prompt, but nothing has worked. But, I never tried copying down this other dudes exact syntax (Iím at work now, so I canít try it this instant anyway) since I figured it was Ubuntu specific Ė maybe that was wrong.

Anyway, if anyone could tell me the syntax to use Iíd appreciate it! By the way, Iíve already tried booting to most of the different kernel versions that comes with Slackware (like "huge," the "scsis" and so on) to no avail Ė just so youíll know.

Thanks again!

Bob

P.S. What does pci=nomsi tell Linux to do anyway?

bioe007 02-28-2007 02:30 PM

nomsi = no message signal interrupts -> MSI

I can't remember exactly how slack installs, to pass this option during slackware boot, when given chance to select kernel, pick:
Code:

huge26.s pci=nomsi
or, slack might first have you pick a kernel, then select options to pass, in which case you just select huge26.s, then at the 'options to pass' prompt, type 'pci=nomsi

BobTheSlackUser 02-28-2007 05:49 PM

Thanks bioe! I'll try that as soon as I get home tonight and post what happened.

BobTheSlackUser 02-28-2007 08:14 PM

DANG!! That didn't solve it. Heck, it seemed like that was the right answer. Oh well, there is a silver lining however. Bioe was right about how to send boot params to slackware. I was able to view the screen dump (when the system boots) and note that the "huge" kernel does recognise the command, but the regular "saia" kernal does not.

So, heck, at least I learned something. But I'm still no closer to solving this problem. Does anyone out there have any ideas?

Bob

BobTheSlackUser 02-28-2007 09:03 PM

Wow, now I'm really stumped.

I just tried the boot parameter "acpi=force irqpoll" which is the last suggestion I could find on the Internet, and, alas, it doesn't work.

I guess I could switch to trying Ubuntu, but I've used slack for a few years now (NOT an expert by ANY means) and I'm used to it, so I really don't want to trade up.

Ah well, if anyone can help, please do so.

Bob

H_TeXMeX_H 02-28-2007 09:22 PM

Did you try:

acpi=force irqpoll pci=nomsi

?

onebuck 03-01-2007 07:57 AM

Quote:

Originally Posted by BobTheSlackUser
Hey Guys,

I hope you can help me with this, but as you can tell from my subject description, Slackware 11 cannot recognize my hard drive when Iím trying to install. My computer is a new Dell Inspiron 1501 (can I just say that Truelife is a horrible invention) and I want to get away from Microsoft Vista as soon as I can.


Hi,

Boot using the Slackware 11 cd1 with the huge26 kernel. Once you boot;

Code:

#dmesg                #see what is going on at boot
#lspci -vv            #see what is recognized.

Please post the output of the above command. You can redirect the output to a file by 'lspci -vv >mylspci'. This file could be directed to the floppy or other media. I'm not sure what you have on the Dell. You should also post the hardware configuration of your machine. Post in the vbcode, use the # on reply and place the post between the tags. This would also help diagnose.

I think most Dell 1501 use a sata for hd media. By doing the 'lspci -vv' you will see the hardware recognized by the kernel. The 'dmesg' would present us with information to see the boot, we then can see what needs to be done.

BobTheSlackUser 03-01-2007 06:03 PM

Thanks for all your help guys!


H_TeXMeX_H
I did try that last night, again, with no luck. But thanks for the suggestion!

Onebuck
That is a great idea, and thanks fro being willing to help me in that much detail. Just so you'll know, however, today is my birthday and right now my wife is waiting by the door to take me to dinner, so I'll try to get that screen dump done tonight after we get back. But if I can't squeeze it in tonight I'll definitely get it posted tomorrow.

Thanks again!

Bob

H_TeXMeX_H 03-01-2007 10:14 PM

Happy Birthday man ! :D

bioe007 03-01-2007 11:48 PM

yeah, happy b-day...

Quote:

my wife is waiting by the door to take me to dinner
hopefully for your sake you'll have no energy to get the screen dump today :D

creativename 03-02-2007 06:20 PM

I would be much obliged if someone could answer his question, I also have a Dell Inspiron 1501, and have been struggling with the same problem. When I installed Slackware on my Dell Dimension 3000, I didn't have any problem. I think it's because the 1501 uses "sda" type drives and the 3000 uses "hda" type drives (which both probably have better names). It should be possible...

H_TeXMeX_H 03-02-2007 08:15 PM

you mean SATA vs. IDE ... yeah, technically, any kernel that supports sata should boot ... huge26.s, sata.i, test26.s, etc.

BobTheSlackUser 03-02-2007 09:55 PM

Oh, the sad paths assumption can take you -- the embarasment, the folly.

Dudes,

I have sovled the problem of Slackware not seeing the HD on the 1501. The truth is that Slack always did see the Hard Disk (whenever I used the "Huge26" Kernal in the past) it was "cfdisk" that could not -- for whatever reason.

As you can guess I've always used "cfdisk" to set up my partitions. I just figured it was a menu driven form of "fdisk." So they should all see the same things, right? Well, apparently NOT.

If one uses the "Huge26" Kernal, and the stndard line "fdisk /dev/sda" you'll see the HD just fine. Something else I learned is that the HD in the 1501 is a form of scsi drive (yet none of the scsi Kernals will let you see it, even with fdisk), thus the use of sda for a device specification.

Anyway, creativename, use the huge26 Kernal and fdisk and you should be on your way. If you have any problem using fdisk just post it here and I'll try to help.

Everyone: thank you for the help you did offer! And we'll see you around the forum.

Bob

H_TeXMeX_H 03-02-2007 10:45 PM

This is important ... I'll remember it. Use fdisk for SATA drives when installing.

Glad you found the answer :)

creativename 03-03-2007 04:44 AM

Quote:

Originally Posted by BobTheSlackUser
Anyway, creativename, use the huge26 Kernal and fdisk and you should be on your way. If you have any problem using fdisk just post it here and I'll try to help.

Bob

I'll be giving that a shot, thanks!


All times are GMT -5. The time now is 03:26 PM.