Re: Help requested: DMA, Seagate ST340014A, Kernel 2.4
Richard Cobbe wrote: Lo, on Sunday, August 15, James Vahn did write: Didn't know about lspci; thanks. If I'm reading the output correctly, though, I'm not using a VIA IDE interface: [nanny-ogg:~/mail/.spools]$ lspci 00:00.0 Host bridge: Advanced Micro Devices [AMD]: Unknown device 700c (rev 11) 00:01.0 PCI bridge: Advanced Micro Devices [AMD]: Unknown device 700d ... 00:07.1 IDE interface: Advanced Micro Devices [AMD]: Unknown device 7441 (rev 04) 00:07.3 Bridge: Advanced Micro Devices [AMD]: Unknown device 7443 (rev 03) 00:08.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev 01) The computer did come with a PCI IDE controller card (the "unknown mass storage controller" line above) that has another two controllers on it. I haven't yet tried switching controllers to see if that helps at all; I may attempt that later this afternoon. Alternatively, should the fact that lspci keeps saying "unknown device" worry me? No. This device works fine: kowari:~# lspci -s 00:09.0 :00:09.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 01) kowari:~# For a while my aged Pentium II wouldn't boot off the builtin IDE controllers, so I stuck the drive onto one of these and all was well (after reconfiguring the BIOS). -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help requested: DMA, Seagate ST340014A, Kernel 2.4
Rthoreau wrote: Richard Your lspci listing should not contain any unknown devices, for example below is my listing for my MP 2460. It really does not matter. All it means is the device is not in the PCI utilities database. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help requested: DMA, Seagate ST340014A, Kernel 2.4
Lo, on Monday, August 16, Rthoreau did write: > > Date: Yesterday 14:49:47 > > > Lo, on Sunday, August 15, Richard Cobbe did write: > > >> The computer did come with a PCI IDE controller card (the "unknown mass > >> storage controller" line above) that has another two controllers on it. > >> I haven't yet tried switching controllers to see if that helps at all; I > >> may attempt that later this afternoon. > > > Well, that didn't work. Moving it to the other controller should make > > the hard drive visible as /dev/hde, but the kernel couldn't find the > > root device, even when I specified `root=/dev/hde2' on the Lilo command > > line. The odd thing is, I've switched hard drives to this controller > > before, back when I was having strange trouble with the previous drive > > and trying to diagnose it. I don't remember exactly what incantation I > > had to mumble in order to get the kernel to find the partition, though, > > so I can't repeat the process. > > > Does anyone else have any suggestions? > > > Richard So I installed the latest 2.4 kernel image out of stable (kernel-image-2.4.18-1-k7). I'm not sure this is an improvement, although we'll see. > Your lspci listing should not contain any unknown devices, for example below > is my listing for my MP 2460. Still getting unknown devices in lspci; the output is the same as up-thread. Further, when I ran /sbin/hdparm -X66 -d1 -u1 -m16 -c3 /dev/hda I got a slightly-updated version of a standard error/warning message: ide0: unexpected interrupt, status=0x58, count=1 although things *appear* to be working fine for now. I'd still be a lot happier if I weren't getting that warning, though. However, and I don't know if this is related, the kernel image only supports a single processor; stable doesn't appear to have an SMP-enabled kernel prebuilt. As soon as the soruce installs, I'm going to rebuild it for SMP without making any other changes, just to see what happens. So, in short, better but not good. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help requested: DMA, Seagate ST340014A, Kernel 2.4
> Date: Yesterday 14:49:47 > Lo, on Sunday, August 15, Richard Cobbe did write: >> The computer did come with a PCI IDE controller card (the "unknown mass >> storage controller" line above) that has another two controllers on it. >> I haven't yet tried switching controllers to see if that helps at all; I >> may attempt that later this afternoon. > Well, that didn't work. Moving it to the other controller should make > the hard drive visible as /dev/hde, but the kernel couldn't find the > root device, even when I specified `root=/dev/hde2' on the Lilo command > line. The odd thing is, I've switched hard drives to this controller > before, back when I was having strange trouble with the previous drive > and trying to diagnose it. I don't remember exactly what incantation I > had to mumble in order to get the kernel to find the partition, though, > so I can't repeat the process. > Does anyone else have any suggestions? > Richard Your lspci listing should not contain any unknown devices, for example below is my listing for my MP 2460. 00:00.0 Host bridge Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] System Controller 11 00 00:01.0 PCI bridge Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] AGP Bridge 00 00 00:07.0 ISA bridge Advanced Micro Devices [AMD] AMD-766 [ViperPlus] ISA 02 00 00:07.1 IDE interface Advanced Micro Devices [AMD] AMD-766 [ViperPlus] IDE 01 8a 00:07.3 Bridge Advanced Micro Devices [AMD] AMD-766 [ViperPlus] ACPI 01 00 00:07.4 USB Controller Advanced Micro Devices [AMD] AMD-766 [ViperPlus] USB 07 10 00:0a.0 USB Controller OPTi Inc. 82C861 20 10 OPTi Inc. 82C861 00:0a.1 USB Controller OPTi Inc. 82C861 20 10 OPTi Inc. 82C861 00:0c.0 Ethernet controller Davicom Semiconductor, Inc. Ethernet 100/10 MBit 31 00 ARCHTEK TELECOM Corp 0008 00:0d.0 Multimedia audio controller C-Media Electronics Inc CM8738 10 00 C-Media Electronics Inc CMI8738/C3DX PCI Audio Device 01:05.0 VGA compatible controller nVidia Corporation NV11 [GeForce2 MX/MX 400] b2 00 CardExpert Technology 05de I do not remember exactly what chipset the mpx series use, but its AMD 760ish based. I would load a k7 kernel-image smp capable with apt-get and see what lspci says. Also knoppix, and other live cds are great to verify hardware setup, so you could give them a try. It might just be eaiser to just apt-get a kernel image and give it a try. Rthoreau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help requested: DMA, Seagate ST340014A, Kernel 2.4
Lo, on Sunday, August 15, Rthoreau did write: > I have used ext3, and assume you are using ext2, what kernel > parameters are you pasing to the kernel? Yes, ext2, although I'd be surprised if that makes a difference. As far as kernel parameters, the only one I'm using that looks at all relevant is `lba32' (simply because it's part of Debian's default lilo.conf file, and I've never needed to wonder if it's necessary). > Is their a reason you have not tried a 2.6 kernel? Well, as I understand the situation, I can't run 2.6 without upgrading to sarge, and I can't upgrade to sarge while running 2.2. Since 2.4 does not currently look to be an option, this causes a bit of a catch-22. Thanks, Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help requested: DMA, Seagate ST340014A, Kernel 2.4
> Date: Today 09:04:28 > > Greetings, all. > > I'm running Debian stable, and I've been running the 2.2 kernel series > for some time now, because I've never had very good luck getting DMA to > work for my hard drive under the 2.4 series. However, with sarge's > release appearing increasingly imminent, I need to try to get this > resolved. Google has, unfortunately, completely let me down on this. > The hard drive is a Seagate ST340014A, and it's plugged into the main > IDE controller on my motherboard, a Tyan Tiger MPX S2466. According to > the manufacturer, this uses the AMD-760 MPX chipset. As far as I can > tell, I've configured my kernel correctly, but I'm still having serious > problems that occasionally result in filesystem corruption. > > I would greatly appreciate any suggestions that anyone might have. > Thanks much, > Richard I feel you pain, but since I only have a Tyan mp 2460 our hardware is a little bit different. I am running testing with a 2.6 kernel, and am having no problems. That being said I also use a journaling file system. I have used ext3, and assume you are using ext2, what kernel parameters are you pasing to the kernel? I use the noapic and acpi=off with good results, but some people can not tell the difference. Is their a reason you have not tried a 2.6 kernel? I know you are using woody, but you might want to consider upgrading, if you decide to go to sarge. A while back I did have some weird problems with a 2.4.25 kernel, could never figure it out either, I was using a Reiserfs and got some corruption, but to be honest I believe its chipset related. Here is why, in this system I have a CrystalFontz LCD which I use to monitor different systems specs. My harddrive is on a single primary, and I have two other drives sharing another IDE, durring heavy system use, say I use unrar, burning a CD or something else, sometimes in my system logs and on screen I get, serial line busy and it shuts down my Crystal Fontz LCD. Then if I try to restart it, like normal it won't come up, I have to go to init1, even then it sometimes does not comeup, until I reboot. So it would not surprise me if the chipset is flakey, also do you use a usb mouse, or keyboard? I know for at least the mp 2460 just having this has been know to lock the system up. I would suggest trying a 2.6 kernel, if your using testing or sarge, and just apt-get the k7 smp kernel image and see how it works with your DMA settings. Also I know that some mp mpx motherboards do not like certain graphics cards, I had a Nvidia 5600 ultra, and worked in mine, but Tyan does not support the FX series on my board. http://forums.pcper.com/showthread.php?t=265196 since then I switched back to a geforce2, that I rebuilt, put that ultra in a single cpu system, which is used to play Doom3. As far as knowing a silver bullet for fixing DMA in 2.4, I am at a loss other than what I said above. Rthoreau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help requested: DMA, Seagate ST340014A, Kernel 2.4
Lo, on Sunday, August 15, Richard Cobbe did write: > The computer did come with a PCI IDE controller card (the "unknown mass > storage controller" line above) that has another two controllers on it. > I haven't yet tried switching controllers to see if that helps at all; I > may attempt that later this afternoon. Well, that didn't work. Moving it to the other controller should make the hard drive visible as /dev/hde, but the kernel couldn't find the root device, even when I specified `root=/dev/hde2' on the Lilo command line. The odd thing is, I've switched hard drives to this controller before, back when I was having strange trouble with the previous drive and trying to diagnose it. I don't remember exactly what incantation I had to mumble in order to get the kernel to find the partition, though, so I can't repeat the process. Does anyone else have any suggestions? Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help requested: DMA, Seagate ST340014A, Kernel 2.4
Lo, on Sunday, August 15, James Vahn did write: > Richard wrote: > > I'm running Debian stable, and I've been running the 2.2 kernel series > > for some time now, because I've never had very good luck getting DMA to > > work for my hard drive under the 2.4 series. > > > > The hard drive is a Seagate ST340014A, and it's plugged into the main > > IDE controller on my motherboard, a Tyan Tiger MPX S2466. According to > > the manufacturer, this uses the AMD-760 MPX chipset. > > If you check lspci, I'll bet you are using a VIA interface. I have the > same problem here. It's been suggested to me that this is a kernel bug in > the VIA driver. The same person suggested that another IDE card stands a > good chance of working, and he recommended HPT (HighPoint). > > ~$ lspci > :00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] ><.> > :00:04.1 IDE interface: VIA Technologies, Inc. >VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) Didn't know about lspci; thanks. If I'm reading the output correctly, though, I'm not using a VIA IDE interface: [nanny-ogg:~/mail/.spools]$ lspci 00:00.0 Host bridge: Advanced Micro Devices [AMD]: Unknown device 700c (rev 11) 00:01.0 PCI bridge: Advanced Micro Devices [AMD]: Unknown device 700d ... 00:07.1 IDE interface: Advanced Micro Devices [AMD]: Unknown device 7441 (rev 04) 00:07.3 Bridge: Advanced Micro Devices [AMD]: Unknown device 7443 (rev 03) 00:08.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev 01) The computer did come with a PCI IDE controller card (the "unknown mass storage controller" line above) that has another two controllers on it. I haven't yet tried switching controllers to see if that helps at all; I may attempt that later this afternoon. Alternatively, should the fact that lspci keeps saying "unknown device" worry me? Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Help requested: DMA, Seagate ST340014A, Kernel 2.4
Greetings, all.
I'm running Debian stable, and I've been running the 2.2 kernel series
for some time now, because I've never had very good luck getting DMA to
work for my hard drive under the 2.4 series. However, with sarge's
release appearing increasingly imminent, I need to try to get this
resolved. Google has, unfortunately, completely let me down on this.
The hard drive is a Seagate ST340014A, and it's plugged into the main
IDE controller on my motherboard, a Tyan Tiger MPX S2466. According to
the manufacturer, this uses the AMD-760 MPX chipset. As far as I can
tell, I've configured my kernel correctly, but I'm still having serious
problems that occasionally result in filesystem corruption.
I've tried three different invocations of hdparm:
1) /sbin/hdparm -X66 -d1 -u1 -m16 -c3 /dev/hda
2) /sbin/hdparm -X66 -d1 -u0 -m16 -c3 /dev/hda
3) /sbin/hdparm -X33 -d1 -u0 -m16 -c3 /dev/hda
I have used the first invocation with the 2.2 kernels for a couple of
years now with no filesystem problems. Under 2.4.26, however, it
doesn't work as well. The failure modes are somewhat complicated, but
they generally involve a message printed to the console immediately
after I run hdparm (which is one of the last things in my boot process).
In one scenario, I'll just get a warning message printed to the console:
hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
Things generally seem to work well subsequently, although I can end up
with transient failures later on, some of which require rebooting, and
some of which involve filesystem corruption. Unfortunately, I haven't
had one of these in a while, so I can't describe it more fully.
In another scenario, I'll get a longer message printed to the console
during hdparm's execution:
hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete
DriveRequest }
ide0: Drive 0 didn't accept speed setting. Oh, well.
At this point, the system hangs and is completely unresponsive to
keyboard input, and I have to hit the reset button. In the subsequent
fsck, I'll often find some filesystem errors that are relatively minor
but still require manual intervention to fix. (One of these left a
couple of things in /var/lost+found and clobbered /etc/motd.)
In the third scenario, I'll get this error during hdparm's execution:
EXT2-fs error (device ide0(3,2)): ext2_check_page: bad entry in
directory #452483: unaligned directory entry -- offset=0,
inode=16501003888, rec_len=59267, name_len=6
at which point the system automatically remounts / as read-only. Since
this happens before the boot procedure removes /etc/nologin, I have to
reboot, although in this case a ctrl-alt-del is sufficient. Again, this
requires an fsck on reboot, although I don't think this generally leads
to filesystem errors (other than non-zero sizes on FIFOs).
Out of the hdparm invocations given above, numbers 1 and 2 both lead to
these problems. Number 3, which I'm using currently, seems to be more
stable, although I do get console messages on startup as well:
hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
hda: CHECK for good STATUS
I've only been running this for a couple of days, though, so I'm not yet
sure that it'll be stable over the long term.
Since this worked under the 2.2 series, I'm pretty sure that it's a
software configuration issue rather than a hardware problem. As I say,
I believe that I've configured things correctly, but things still aren't
working. I've attached my kernel configuration file below; note that
I've tried this both with and without CONFIG_IDEDISK_MULTI_MODE enabled,
with no observable difference.
I would greatly appreciate any suggestions that anyone might have.
Thanks much,
Richard
config-2.4.26rc1
Description: Binary data
