LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-14-2010, 08:24 PM   #1
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 181

Rep: Reputation: 5
Slack 13.1 Donīt Connect Sata


In fact I donīt like number 13 and perhaps itīs the reason Iīve been worried about changing slack 13 version! However, I downloaded an iso-dvd-13.1 from official website (http://www.slackware.com/getslack / torrents). It occurred a twice and I recorded it using k3b, CDBurnerXP and Poweriso. Then I changed speeds in a way of take off recording disfunctions or panics in the media ... Unfortunatelly I didnīt get success to install the system so my 80G seagate sata hd is not recognized. Thereby I changed hds, cables, memory and nothing! I' m using an Asus A8V-mx motherboard (AMI BIOS, WfM 2.0, SM BIOS 2.3 and CHIPSET VIA K8M800 / VIA VT82510).In it sata hdd is on during boot loader, but after that dvd disk hugesmp.s 2.6.33-smp kernel break donw and I donīt connect sata and neither go ahead a full install. I tryed :

fdisk /dev/sd*;
cfdisk (fatal error: can not open disk drive) and
# ls -l /dev/sd* returns
/bin/ls: can not access /dev/sd*. No such file or directory


I wish an easy fresh install. In this system if I use slack 12.2 version itīs ok. Can someone help me?
 
Old 09-14-2010, 10:32 PM   #2
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŪ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Hi,

What do you see with 'fdisk -l' for default boot of the Install media?

 
Old 09-15-2010, 04:16 AM   #3
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
I recommend what I usually do when SATA HDDs are not detected: go into BIOS options and put the SATA controller in AHCI mode. This is probably even more relevant because you have a VIA chipset, not well supported by the drivers.
 
Old 09-15-2010, 08:20 AM   #4
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 181

Original Poster
Rep: Reputation: 5
Iīm trying to correct pci=nomsi boot parameter ( MSI - Message Signaled Interrupt ). I am studying this topic http://www.linuxquestions.org/questi...drives-791147/ and http://ubuntuforums.org/showthread.php?t=837835. How can I recompile kernel before instalation?
 
Old 09-15-2010, 08:24 AM   #5
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
You don't have to recompile the kernel, just add that as a boot parameter, so when it says boot put:

Code:
boot: huge.s pci=nomsi
 
Old 09-15-2010, 08:23 PM   #6
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 181

Original Poster
Rep: Reputation: 5
Itīs very strange! It was possible install slack using parameter

hugesmp.s pci=nomsi

But, now Iīm having kernel panic. Iīm "googling" and I think itīs a common message.

VFS: Cannot open root device 801 or unknown block (8,1)

Is this a Via-chiset problem? What to do?
 
Old 09-16-2010, 04:13 AM   #7
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
You have to make sure that it will keep using this option to boot the kernel. I'm sorry, I should have mentioned that, but I forgot. I think during the lilo install it may have asked you to add append options to boot the kernel.

Well, here's some possible fixes:

You can run the setup program again from the DVD and skip straight to installing lilo in expert mode with the append option of:
Code:
append=" vt.default_utf8=0 pci=nomsi"
OR do it the other way:

1) Put in the Slackware DVD and reboot.
2) login to root
3) run these commands:
Code:
mount /dev/sda1 /mnt
chroot /mnt
nano /etc/lilo.conf
here /dev/sda1 should be your root partition.
4) Using nano you edit lilo.conf to modify this:
Code:
append=" vt.default_utf8=0 pci=nomsi"
5) Now just run
Code:
lilo
then reboot with Ctrl-Alt-Del and remove the DVD.

Last edited by H_TeXMeX_H; 09-16-2010 at 04:16 AM.
 
Old 09-16-2010, 08:54 AM   #8
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 181

Original Poster
Rep: Reputation: 5
Really Iīm a slacker. By the way, yesterday I googled a lot and during reading I suspected a lilo problem. Then, I decided to reboot using Slackware DVD and run parameters:

boot: huge.sms.s pci=nomsi root=/dev/sda1 rdinit= ro


Then was possible to skip kernel panic and go on system login. After that I run vi /etc/lilo.conf and there are:

boot= /dev/sda


image= /boot/vmlinuz
root= /dev/sda1
label= Linux
read-only


1)Below commander also can be used to correct this install problem?

huge.sms.s pci=nomsi root=/dev/sda1 rdinit= ro

2)I donīt see append options in lilo.conf. Then I should insert this complete line in lilo.conf?

append=" vt.default_utf8=0 pci=nomsi"

3)Updating kernel in slack current can be a way to solve it?

Last edited by vivanguarda; 09-16-2010 at 09:22 AM.
 
Old 09-16-2010, 10:28 AM   #9
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
Yeah you should add the append line in lilo.conf, it stores arguments to be passed to the kernel when booting. Put in just append=" vt.default_utf8=0 pci=nomsi", not the rest (that part is already in there).

I don't know if upgrading to current will help.
 
Old 09-16-2010, 11:07 PM   #10
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 181

Original Poster
Rep: Reputation: 5
Hi_Tex_ Mex_H your info is Perfect! Thanks a lot!!! Now, this is solved topic!!!
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Connect 3.5" SATA HDD to Laptop directly over SATA into bay (not Firewire and USB) browny_amiga Linux - Hardware 15 12-07-2012 04:33 PM
Package created with makepkg don`t show slack-desc GWagner Slackware 5 11-29-2008 02:56 PM
How to chown -R don.lab * for don.users Hans Zilles Linux - Newbie 3 11-15-2005 07:53 AM
Suse dontīt boot X; donīt ask for root passwd, YAST donīt work... carrie Linux - Newbie 4 10-08-2004 07:46 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:05 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration