LinuxQuestions.org
Help answer threads with 0 replies.
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 12-01-2008, 05:13 AM   #1
xtothat
Member
 
Registered: Sep 2008
Location: Middle of Nowhere, England
Distribution: Slackware 14.1, Ubuntu 13.10
Posts: 39

Rep: Reputation: 15
VIA EPIA SATA not appearing properly on Slackware with custom kernel.


Hi all. I'm having a few problems trying to get a SATA drive to run on a VIA EPIA EN15000G. I'm running Slack 10.2 with a custom 2.6.27.4 kernel. I have enabled all of the SATA kernel modules, and been through my configuration over and over again, but I'm getting the same problem every time.

During boot, I get all of the sda messages popping up in /var/log/messages, apparently showing that it has all worked ok... An example of one of these messages is below:

Code:
Dec  1 10:18:11 workshop0 kernel: sd 1:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
Dec  1 10:18:11 workshop0 kernel: sd 1:0:0:0: [sda] Attached SCSI disk
The problem is that when boot has finished, I try fdisk /dev/sda and what comes back is "Unable to open /dev/sda".

I have tried multiple SATA drives (of different brands), and recompiled the kernel a good few times just in case but I get the same result every time, so I'm positive it's a configuration issue. I'd rather get the the bottom of this rather than just go reinstalling things willy-nilly, as it's a production machine I'm working with.

If it helps I have the motherboard set to use the SATA in IDE mode rather than RAID mode (it seemed to be the sensible option, as I do not require RAID for this machine).

Any help is much much appreciated.

UPDATE: Looking in /sys/block/, I have a seemingly valid folder sda with a link of device to ../../devices/pci0000(...), a valid size file, ro is set to 0, removable is 0. The uevent file reads as follows:

Code:
MAJOR=8
MINOR=0
DEVTYPE=disk
PHYSDEVPATH=/devices/pci0000:00/0000:00:0f.0/host1/target1:0:0/1:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
Also, I've just noticed that on boot, it says that the "sd driver needs updating"

Thanks again!

X-T

Last edited by xtothat; 12-01-2008 at 05:23 AM.
 
Old 12-01-2008, 05:29 AM   #2
xtothat
Member
 
Registered: Sep 2008
Location: Middle of Nowhere, England
Distribution: Slackware 14.1, Ubuntu 13.10
Posts: 39

Original Poster
Rep: Reputation: 15
Sorry guys!

Hi all. I've actually fixed it. 2 mins after posting. Who'd have thought it!? The problem was that /dev/sda-h devices and the primary partitions of each of them didn't exist. All I had to do was go to /dev/ and run ./MAKEDEV sda, and it's all fine and dandy. Sorry for wasting anybody's time!

X-T
 
  


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
Slackware 11.0 - Custom Kernel 2.6.18 Question Old_Fogie Slackware 4 10-10-2006 08:25 PM
Installing Slackware on a custom kernel hsimah Slackware 21 05-17-2006 02:22 AM
Slackware 10, custom 2.6.7 kernel, lilo, loads kernel very slowly entropyv Slackware 3 08-19-2004 06:06 PM
Installing Slackware CD 9.1 using custom kernel (sata) bonecrusher Slackware - Installation 7 04-07-2004 01:34 AM

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

All times are GMT -5. The time now is 04: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