Seth Goodman wrote:
From: Wackojacko [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 22, 2005 11:02 AM
<...>
BTW, thanks for all the help. This forum is invaluable. If I can figure
out whatever is wrong, I will be very happy to document the whole mess in a
bug report for the group that is responsible for hardware detection.
No problem.
- add the modules that *aren't* for your motherboard to the blacklists
for hotplug and discover to prevent possible conflicts.
That sounds reasonable, but will take some research on my part before I can
do it. For each suspected "unneeded" module, I'd have to explore the source
to make sure that it isn't required due to some minor feature that it
happens to perform. I will also need to delve into the mobo hardware and
figure out what features are present in this particular stepping of both
Northbridge and Southbridge chips. I suspect it would get me there, but it
sounds like more of a last resort.
A quick look at the kernel-source (via make menuconfig) and google
suggest that PIIX could be the right module. I dont have this mobo so I
cant be sure.
- try the newer version of discover, called discover as opposed to
discover1.
This sounds interesting. In the Synaptic Package manager, I see that
discover1 (1.7.13) and discover1-data (1.2005.07.31) are installed. It
shows discover (2.0.7) and discover-data (2.2005.02.13-1) as being
available. This is curious. The version number of discover is higher than
that of discover1, but discover1-data appears to be more recent than
discover-data.
Assuming you recommend this, how do replace discover1 with discover without
breaking things? My guess would be to install discover and discover-data in
Synaptic and see if discover1 is removed. If not, would I then remove
discover1 and discover1-data? I know I can do the same thing with apt-get,
but this seems easier, unless there is some reason _not_ to use the Synaptic
tool.
They are conflicting packages so installing one will remove the other.
As for recommending it, I am beginning to think the module loading is
not the problem as dmesg picks up the CD, see below.
- compile the relevant modules into your own kernel, which is not that
bad if you use make-kpkg (Kernel-Package via apt-get). I have seen the
need to compile drivers into kernel to get them to work a few times on
this list so this may be why Knoppix works and Debian doesn't.
Sounds reasonable, but I would need to know what modules to include. I'm
not afraid of building a kernel, but I think identifying the appropriate
hardware modules would be a challenge.
See above.
Also have you had a look at /var/log to see if the kernel picks up the
cd on boot. Try 'dmesg|grep CD' or 'hdc' to see if it picks up the CD
and if there are any error messages.
I've attached the full output of dmesg from the most recent boot. It looks
like it finds and correctly identifies the CD (the model number appears
right), so I'm really at a loss.
If you still cant solve it post back as much detailed H/W information as
you can including the output of lspci.
Also attached.
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH: IDE controller at PCI slot 0000:00:1f.1
ICH: chipset revision 2
ICH: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfff0-0xfff7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xfff8-0xffff, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: Maxtor 52049H4, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: LTN485S, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
hda: max request size: 128KiB
hda: 39876480 sectors (20416 MB) w/2048KiB Cache, CHS=39560/16/63, UDMA(66)
hda: cache flushes not supported
<snip>
hdc: ATAPI 48X CD-ROM drive, 120kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
<snip>
0000:00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02)
All of the above suggests the ide controller is being detected properly
as is the CD ROM drive. As you can access the HDD OK I am begining to
suspect that it is not being mounted correctly. Please post your
/etc/fstab and/or details of how you try to mount the drive.
Dont give up just yet!
Wackojacko
PS dont worry about off list posts, it happens to most people at some
time or another.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
