Article View: comp.os.linux.hardware
Article #205Secondary HD controller failure
From: pimpi
Date: Thu, 09 Aug 2001 15:49
Date: Thu, 09 Aug 2001 15:49
92 lines
4917 bytes
4917 bytes
Hello!
I recently bought a second-hand motherboard and wanted to install a new
CDROM on the secondary controller.
However, any devices I try to connect to the secondary controller does
not get detected correctly.
The BIOS detection detects it as "ASUS" (on the primary, working
controller its labelled "ASUS S500 CD/DVD CD-ROM").
Under Windows 98, it does show up as drive D:, and when I open it while a
data CD is loaded, it contains a single audio "Track 01", double-click on
that produces an error "the disc is not in the drive".
Control Panel shows no HW conflicts.
(note: the cdrom does work on primary controller, the cable is OK,
master/slave jumpering changes nothing)
Under linux, if I try to mount a cdrom, I get this:
[wirligig]/root # mount /dev/hdd /mnt/test/
/dev/hdd: Input/output error
mount: block device /dev/hdd is write-protected, mounting read-only
/dev/hdd: Input/output error
mount: you must specify the filesystem type
[wirligig]/root # mount -t iso9660 /dev/hdd /mnt/test/
mount: block device /dev/hdd is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/hdd,
or too many mounted file systems
and the syslog shows this:
hdd: ATAPI 50X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
VFS: Disk change detected on device ide1(22,64)
VFS: Disk change detected on device ide1(22,64)
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 2
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 2
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 0
FAT bread failed
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 2
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 2
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 0
FAT bread failed
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 64
isofs_read_super: bread failed, dev=16:40, iso_blknum=16, block=32
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 64
isofs_read_super: bread failed, dev=16:40, iso_blknum=16, block=32
I use the correct modules, I have support for iso9660, and the problem is
independent from kernel version (currently 2.4.7), there are no conflicts
in /proc/interrupts or /proc/ioports
Trying to connect a harddrive, both OSes complain about incorrect
partition tables.
My conclusion: There is something wrong with the secondary controller.
But as it does report at least _something_ to the OSes, I figure it might
just be some configuration thing.
The Motherbaord is a Gigabyte GA6VX7+ F5 (latest BIOS), the onboard HD
controller is a VIA Apollo Pro Chipset (VIA vt82c596b chips)
Anyone who knows how to solve this?
Thx a lot
Pimpi
Note to users of German newsgroups:
Tschuldigung das es englisch ist, aber es is leichter zu cross-posten...
--
PS: please reply per email too where possible!!
-- -- --
The Information Revolution will be fought on the command line.
Technical Details
Message-ID:
<9ktm5f$5l6$1@fstgss02.tu-graz.ac.at>Path:
arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!wuff.zikzak.de!ictas.tu-graz.ac.at!news.tu-graz.ac.at!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 102b32,83a1fc44e78c9ea6,start X-Google-Attributes: gid102b32,public X-Google-Thread: 112e72,83a1fc44e78c9ea6,start X-Google-Attributes: gid112e72,public X-Google-Thread: fe50d,83a1fc44e78c9ea6,start X-Google-Attributes: gidfe50d,public X-Google-ArrivalTime: 2001-08-09 03:05:01 PST From: "pimpi" <pimpifax@gmx.ch> Newsgroups: comp.os.linux.hardware,de.comp.hardware.laufwerke.festplatten,at.tuwien.hardware Subject: Secondary HD controller failure Date: Thu, 09 Aug 2001 11:49:41 -0400 Organization: Technische Universitaet Graz, Austria Lines: 92 Message-ID: <9ktm5f$5l6$1@fstgss02.tu-graz.ac.at> NNTP-Posting-Host: chello213047181038.sc-graz.chello.at Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: fstgss02.tu-graz.ac.at 997350383 5798 213.47.181.38 (9 Aug 2001 09:46:23 GMT) X-Complaints-To: news@zid.tu-graz.ac.at NNTP-Posting-Date: 9 Aug 2001 09:46:23 GMT User-Agent: Pan/0.9.7 (Unix) Path: arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!wuff.zikzak.de!ictas.tu-graz.ac.at!news.tu-graz.ac.at!not-for-mail