🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.os.linux.hardware
1 messages
1 total messages Started by pimpi Thu, 09 Aug 2001 15:49
Secondary HD controller failure
#205
Author: pimpi
Date: Thu, 09 Aug 2001 15:49
92 lines
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.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads