Re: [expert] UDMA66 problem
On Sat, 01 Jul 2000, you wrote: Dave Cotton wrote: I also have spent a frustrating week with UDMA problems including a totally unreadable disk (corrupted superblock). With Mandrake 7.0 and a UDMA 33 motherboard HDPARM reported 16MB/s with my WD205AA now with 7.1 this is down to less than 5MB/s. With the drive on my UDMA66 motherboard this drops to 3.5MB/s If I use DMA etc. I get a corrupted superblock. I cut the speed of the bus by 5% and that seems to have stopped the corruption. If you run hdparm -t /dev/hda with dma set there is a stream of seek and crc errors until the system resets the controller and disables dma. My question is what is your processor and motherboard. I have AMD 400 and 500s and DFI P5BV3+ and K6XV3+/66 mbs. Dave Cotton Linux Autrement Avignon France +33 (0)4 90 16 07 89 If you search the archives for UDMA66 problems, you will find most complaints involve WD drives. There is a reason. WD drives have unusual timing requirements. 7.1 is the first MAndrake distro to support UDMA66 out of the box, and the timing might be a little too tight for the WDs. Also, WD does not actually use Cyclic Redundancy Check (CRC) protocol but rather fakes it and blows it off. The result is that there is nothing in the HDD hardware/firmware to block a data stream corrupted by timing chatter from being written to disk. THere is a program that sets WD drives for UDMA66 available for DL from WD, which might(tm) help. In the mean time, on kernel traffic, the discussion crops up from time to time that a possible solution is to restrict WD drives to PIO upon recognition. No conclusion has been reached, but the fact that such discussion is taking place should indicate something to everyone. Civileme And of course Promise has actually made a driver available for the HPT366 in source code. The driver may still need a few bugs located, but the future looks brighter for stable UDMA66. Promise making a Linux driver for Highpoint, err??? Cheers, -- /* Manuël Beunder. (aka MBr) - http://how.to/sblive the SB Live! Linux page - 'You must be the change you wish to see in this world. -Gandi' */
Re: [expert] UDMA66 problem
I also have spent a frustrating week with UDMA problems including a
totally unreadable disk (corrupted superblock).
With Mandrake 7.0 and a UDMA 33 motherboard HDPARM reported 16MB/s with
my WD205AA now with 7.1 this is down to less than 5MB/s. With the drive
on my UDMA66 motherboard this drops to 3.5MB/s If I use DMA etc. I get a
corrupted superblock. I cut the speed of the bus by 5% and that seems to
have stopped the corruption.
If you run hdparm -t /dev/hda with dma set there is a stream of seek and
crc errors until the system resets the controller and disables dma.
My question is what is your processor and motherboard. I have AMD 400
and 500s and DFI P5BV3+ and K6XV3+/66 mbs.
Subject: Re: [expert] UDMA66 problem
Date: Wed, 28 Jun 2000 10:01:59 -0500
From: "Norvell Spearman" [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
In what way could the hard drive not be up to spec? The original post said
the problem didn't exist with Mandrake 7.0.
Not trying to butt in, but I also have an IDE device which did work with
7.0 but does not with 7.1.
---Norvell Spearman
John Aldrich wrote:
On Wed, 28 Jun 2000, you wrote:
Hi,
I've got a WD136BA hard disk on my hpt366 controller. If I try to use
DMA for disk access, my system freezes. This problem didn't exist with
Mandrake 7.0, but it appeared when I installed 7.1. I tried to upgrade
my bios. Nothing changed. After that, I compiled another kernel
(2.3.45). Same problem. I compiled 2.2.15 and 2.3.45 in 386 code
instead
of 586. Always the same problem.
Probably due to the hard drive not being up to spec.
John
Dave Cotton
Linux Autrement
Avignon France
+33 (0)4 90 16 07 89
Re: [expert] UDMA66 problem
Dave Cotton wrote: I also have spent a frustrating week with UDMA problems including a totally unreadable disk (corrupted superblock). With Mandrake 7.0 and a UDMA 33 motherboard HDPARM reported 16MB/s with my WD205AA now with 7.1 this is down to less than 5MB/s. With the drive on my UDMA66 motherboard this drops to 3.5MB/s If I use DMA etc. I get a corrupted superblock. I cut the speed of the bus by 5% and that seems to have stopped the corruption. If you run hdparm -t /dev/hda with dma set there is a stream of seek and crc errors until the system resets the controller and disables dma. My question is what is your processor and motherboard. I have AMD 400 and 500s and DFI P5BV3+ and K6XV3+/66 mbs. Dave Cotton Linux Autrement Avignon France +33 (0)4 90 16 07 89 If you search the archives for UDMA66 problems, you will find most complaints involve WD drives. There is a reason. WD drives have unusual timing requirements. 7.1 is the first MAndrake distro to support UDMA66 out of the box, and the timing might be a little too tight for the WDs. Also, WD does not actually use Cyclic Redundancy Check (CRC) protocol but rather fakes it and blows it off. The result is that there is nothing in the HDD hardware/firmware to block a data stream corrupted by timing chatter from being written to disk. THere is a program that sets WD drives for UDMA66 available for DL from WD, which might(tm) help. In the mean time, on kernel traffic, the discussion crops up from time to time that a possible solution is to restrict WD drives to PIO upon recognition. No conclusion has been reached, but the fact that such discussion is taking place should indicate something to everyone. Civileme And of course Promise has actually made a driver available for the HPT366 in source code. The driver may still need a few bugs located, but the future looks brighter for stable UDMA66.
Re: [expert] UDMA66 problem
Hi, To answer your questions about my configuration: ABIT BP6 with HPT366 onboard 2xCel466 (not overclocked) 64MB SDRAM PC100 ATI Mach64 (quite old) 3DFx Voodoo2 Ethernet PCI 10/100 Realtek 8139 SB PCI 128 Modem ISA 56k CDROM Actima 50x on hda CDRW Creative 2224 on hdc WD136BA 7200rpm on hde Philippe Civileme wrote: Actually the big change, AFAIK, is that UDMA66 is set up to work out of the box. This would suggest that it is specific to the HPT366 Controller/WD setup. Go to http://forum.mandrakesoft.com and look under UDMA66 Solved. I think you might yet be able to make it work, though it might not work at 66. I wasn't joking yesterday. I am really buying ATA/100 equipment to see if it will work at ATA/66. And even if it does work at 66, the missing error-checking feature would make me distrust my own system. WD drives really do blow off the CRC. So what is your board--Is the HPT366 integral or a card? Civileme
Re: [expert] UDMA66 problem
OK, When the Blue High Point BIOS screen shows, Does your Drive show " Mode 4" ? If not then your Hard Drive is not configured correctly.Western Digital Drives work very well with the BP6 mainboard when set properly. Western Digital provides a floppy disk to set the drives in UDMA66 mode. My System ABIT BP6 with HPT366 onboard Driver 1.2 2xCelerons 466 (sometimes overclocked) 256MB SDRAM PC133 ATI AGP Rage 128 32 MB RAM SB AWE 64 ISA LinkSys PCI NIC running ADSL Memorex 48X on IDE1 Western Digital 20.5 GB IDE3 (HDE) NT4.0 Western Digital 15.5 GB IDE3 (HDF) Mandrake 7.0 ttyl, Don On Fri, 30 Jun 2000, you wrote: Hi, To answer your questions about my configuration: ABIT BP6 with HPT366 onboard 2xCel466 (not overclocked) 64MB SDRAM PC100 ATI Mach64 (quite old) 3DFx Voodoo2 Ethernet PCI 10/100 Realtek 8139 SB PCI 128 Modem ISA 56k CDROM Actima 50x on hda CDRW Creative 2224 on hdc WD136BA 7200rpm on hde Philippe Civileme wrote: Actually the big change, AFAIK, is that UDMA66 is set up to work out of the box. This would suggest that it is specific to the HPT366 Controller/WD setup. Go to http://forum.mandrakesoft.com and look under UDMA66 Solved. I think you might yet be able to make it work, though it might not work at 66. I wasn't joking yesterday. I am really buying ATA/100 equipment to see if it will work at ATA/66. And even if it does work at 66, the missing error-checking feature would make me distrust my own system. WD drives really do blow off the CRC. So what is your board--Is the HPT366 integral or a card? Civileme
Re: [expert] UDMA66 problem
Don wrote: OK, When the Blue High Point BIOS screen shows, Does your Drive show " Mode 4" ? If not then your Hard Drive is not configured correctly.Western Digital Drives work very well with the BP6 mainboard when set properly. Western Digital provides a floppy disk to set the drives in UDMA66 mode. Yes, it shows udma mode 4. Btw, it works fine with windows (I get 18MB/s). Philippe
Re: [expert] UDMA66 problem
On Thu, 29 Jun 2000, you wrote: I am wondering what the normal speed for UDMA66? I just got about 14M/second, as fast as UDMA33. What do you mean with "normal-speed"? What are the normal speeds of a 5-lane and a 3-lane highway? I dunno.. it depends.. A drive that only supports ATA/33 which runs at 7200 rpm can easily outrun a drive that supports ATA/66 which runs at 5400 rpm (provided they have the same amount of cache on the drive's internal controller). An ATA/66 drive that run on 7200 rpm, with only 256kb cache (WD), can easily be outrun by a ATA/66 drive (running in ATA/33) mode that runs on 5400 rpm with an optimized 2048kb cache.. (Maxtor). Just because newer generation drives often run faster than older drives and also support ATA/66 or ATA/100, doesn't mean ATA/66 drives are by default faster than ATA/33, because those two facts are not related. ATA/66 is only interresting in ATA-RAID configurations and I haven't seen a drive yet, who can some close to 33MiB/s data-transfer speed (ATA/33) (burst-speeds not accounted, but they are not interresting for the overal performance..) From: Civileme [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [expert] UDMA66 problem Date: Thu, 29 Jun 2000 08:09:30 -0800 Philippe Wautelet wrote: Civileme wrote: 7.0 didn't really support UDMA/66 without a lot of tweaking. My guess is that your WD drive cannot do UDMA66 even though it was advertised to do such. Not impossible, but my drive doesn't work with any DMA mode in 7.1 (and it worked in 7.0 and in MSWindows). Another question directly related to that problem is what are the software or config files which have or could have an influence on the drive performances? I'm nearly certain that my problem doesn't come from the kernel. I know also that it's not hdparm (I tried the version included in 7.0). Philippe Actually the big change, AFAIK, is that UDMA66 is set up to work out of the box. This would suggest that it is specific to the HPT366 Controller/WD setup. Go to http://forum.mandrakesoft.com and look under UDMA66 Solved. I think you might yet be able to make it work, though it might not work at 66. I wasn't joking yesterday. I am really buying ATA/100 equipment to see if it will work at ATA/66. And even if it does work at 66, the missing error-checking feature would make me distrust my own system. WD drives really do blow off the CRC. So what is your board--Is the HPT366 integral or a card? Civileme Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com Cheers, -- /* Manuël Beunder. (aka MBr) - http://how.to/sblive the SB Live! Linux page - 'You must be the change you wish to see in this world. -Gandi' */
Re: [expert] UDMA66 problem
On Wed, 28 Jun 2000, you wrote: Hi, I've got a WD136BA hard disk on my hpt366 controller. If I try to use DMA for disk access, my system freezes. This problem didn't exist with Mandrake 7.0, but it appeared when I installed 7.1. I tried to upgrade my bios. Nothing changed. After that, I compiled another kernel (2.3.45). Same problem. I compiled 2.2.15 and 2.3.45 in 386 code instead of 586. Always the same problem. DMA support is very buggy, to say at least, for the Promise ata66 (PDC 20262) and Abit HotRod (Highpoint hpt366). This is especially true for ATA-pi devices. Your best bet would be, to put your regular CD-ROM player, ZIP-drive and other devices that won't really need DMA support on your ata-66 compatible controller and put your other devices (HD's, CDR's, DVD-players) on your main (Intel) controller. (Don't forget that some ATA/66 compatible HD's (Like Maxtor) required to be set to ATA/33 in the firmware, in order to function properly...) Mandrake 7.0 didn't had DMA support for the hpt366, afaik, so that's why you didn't ran into trouble.. Philippe Cheers, -- /* Manuël Beunder. - http://how.to/sblive the SB Live! Linux page - 'You must be the change you wish to see in this world. -Gandi' */
Re: [expert] UDMA66 problem
I don't have the optimisations enabledI have tried everything to get it going...it's been frusterating to the nth degreeI have a standard floppy...like I said it works fine in 7.0 after doing the fix (cd /dev rm cdrom ln -s scd0 cdrom) no problems at allbut install 7.1 and it refuses to work...removes the drive from bios locks on and I can't even eject the darn thing until I power completely down.I dunno guyit's about to drive me nuts...LOL Jim The information that it works in 7.0 and doesn't in 7.1 is suggestive of something else. The creative CDRW 4224 is enabled for DMA, and 7.1 would likely use it by default. Now I do assume you are trying to open a data disk and not an audio disk (because the audio disk doesn't use "files" per se) and it freezes on you. This suggests it might be overdriven or be treated as a HDD. I have a Creative CDRW (same model) on my K6-2 500 system and 7.1 worked the first time, but I did NOT choose during the install to enable hard disk optimisations. I later enabled them for the hard drive alone using the hdparm command. (and besides man hdparm, there is VERY useful discussion of it at http://forum.mandrakesoft.com) If you enabled them during the 7.1 install, that might be something to back off a notch and see what happens. Nexxt question--do you have a standard floppy or an LS120/LX120? Special considerations apply to those little demons, but there are workarounds. I just moved from an LS120 to a regular floppy--no duplication. I don't understand why I am unable to duplicate the behavior here. What else is different in our systems? I just moved the CDRW to another computer with a K6-2 300 and a VIA MVP3 chipset. The other was a VIA MVP4. Still no duplication. My drive works under 7.0 and 7.1. This is most odd. I will try reinstall tomorrow and enable HD optimisation and see if it makes a difference. Actually 7.0 should introduce a problem with a CDRW. The 'append="ide-scsi"' is set up and the module loaded but the ln -s /dev/sr0 /dev/cdrw is NOT performed. So you cannot access it under 7.0 til you tweak. That problem was corrected in 7.1. I'll let you know if I duplicate the behavior under 7.1 that you are experiencing. Civileme
Re: [expert] UDMA66 problem
Civileme wrote: 7.0 didn't really support UDMA/66 without a lot of tweaking. My guess is that your WD drive cannot do UDMA66 even though it was advertised to do such. Not impossible, but my drive doesn't work with any DMA mode in 7.1 (and it worked in 7.0 and in MSWindows). Another question directly related to that problem is what are the software or config files which have or could have an influence on the drive performances? I'm nearly certain that my problem doesn't come from the kernel. I know also that it's not hdparm (I tried the version included in 7.0). Philippe
Re: [expert] UDMA66 problem
Hi! Anyone has successful installed UDMA 66 with 7.1 and HPT366 on his BP6? My problem starts when installer makes ide-scsi detection it hangs.. any workaround to disable detecting? (export mode doesn`t work..) bye, Torben
Re: [expert] UDMA66 problem
On Wed, 28 Jun 2000, you wrote:
Is anybody getting substantially better than 142 mb/sec and 22
mb/sec from 'hdparm -tT' ?? ATA/33 is capable of that 'cause
those are my numbers, and one (slave) HHD's a WD Caviar 8.4. ...
and is it worth all that hoops y'all seem to be jumpin thru to get
it workin? .. reliab'ly? and is it reliable ?
just askin what I seem to never hear about in conjunction with
ata/66 and performance. seems a better motherboard would do all
y'all /66'rs more good
I'm not even getting THAT...at least not on my EIDE drive
('course it's one that's been around a couple years, so
it's not optimized for UDMA...only an 850 meg drive G)
Now, just for giggles, I"m gonna see what I get on my UW
SCSI drive...
IDE:
[root@slave1 /root]# hdparm -tT /dev/hda
/dev/hda:
Timing buffer-cache reads: 128 MB in 3.18 seconds = 40.25 MB/sec
Timing buffered disk reads: 64 MB in 36.08 seconds = 1.77 MB/sec
SCSI:
Same exact specsmust be my motherboard can't handle
anything faster. :-/ Heh, course I'm only using a dual-PPro
system here... :-)
John
Re: [expert] UDMA66 problem
On Wed, 28 Jun 2000, you wrote: I saved and printed your message and the next time I decide to abuse myself with 7.1 I'll give that a try. I have reinstalled 7.0 because I got tired of not having a working cd... Well, the IDE CDRW setup should be the same in 7.0. If it's not working then it's LIKELY a problem with something in your system -- i.e. an incompatibility with timing or something like that. From what I"ve read since you brought this up, Mandrake 7.02 didn't support UDMA/66, so it would make a LOT of sense that hardware that worked in Mandrake 7.02 won't work in 7.1, at least not at UDMA/66. Hardware specs are everything, and if the manufacturer doesn't follow the specs, you're SOL. As someone else suggested -- ditch the IDE CDRW and get SCSI. That's what I did -- I went out and bought myself a SCSI CDRW and it's been pure pleasure to just open up XCDRoast and tell it where to find the ISO I want to burn and then let it go. :-) John
Re: [expert] UDMA66 problem
On Wed, 28 Jun 2000, you wrote: Those things are done automagically in 7.1 But with some drives supermount can interfere with burning. Basically, your drive MUST be unmounted to burn. Most drives unmount with a complaint when supermount is active and complain again when the burner program exits, but the complaints do not prevent business as usual. With a few drives, the complaint stops the show... While you have 7.0 running, let's see what lspcidrake and dmesg shows and maybe someone will be able to say "Oh, yes,m with that configuration you avoid the problem with" Ahh...well, I guess I'll find out what these things are like next time I upgrade... I fully intend to make Mandrake my distro of choice, now that Mandrake folks seem to have worked out some of the bugs they were having coming up with their own, COMPLETELY separate distro. :-) John
Re: [expert] UDMA66 problem
On Thu, 29 Jun 2000, you wrote: John Aldrich wrote: Hmm...Ok. My bad. I didn't see that bit about it working in 7.0 but not in 7.1. There have been reports (on this list and others) about some brands of hard drives NOT being up to the UDMA 66 spec, and causing problems, especially if there are other brands of hard drive in the system / on the same drive chain. The drive is alone on the HPT366 controller. My *guess* is that the HD is NOT up to spec. WD drives, I've read here (and other lists) are particularly prone to having problems with the specs, as well as "signal reflection". YMMV, but that's what I've read. I can't confirm or deny, as my hardware doesn't support UDMA xfers. :-) John
Re: [expert] UDMA66 problem
Philippe Wautelet wrote: Civileme wrote: 7.0 didn't really support UDMA/66 without a lot of tweaking. My guess is that your WD drive cannot do UDMA66 even though it was advertised to do such. Not impossible, but my drive doesn't work with any DMA mode in 7.1 (and it worked in 7.0 and in MSWindows). Another question directly related to that problem is what are the software or config files which have or could have an influence on the drive performances? I'm nearly certain that my problem doesn't come from the kernel. I know also that it's not hdparm (I tried the version included in 7.0). Philippe Actually the big change, AFAIK, is that UDMA66 is set up to work out of the box. This would suggest that it is specific to the HPT366 Controller/WD setup. Go to http://forum.mandrakesoft.com and look under UDMA66 Solved. I think you might yet be able to make it work, though it might not work at 66. I wasn't joking yesterday. I am really buying ATA/100 equipment to see if it will work at ATA/66. And even if it does work at 66, the missing error-checking feature would make me distrust my own system. WD drives really do blow off the CRC. So what is your board--Is the HPT366 integral or a card? Civileme
Re: [expert] UDMA66 problem
I am wondering what the normal speed for UDMA66? I just got about 14M/second, as fast as UDMA33. From: Civileme [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [expert] UDMA66 problem Date: Thu, 29 Jun 2000 08:09:30 -0800 Philippe Wautelet wrote: Civileme wrote: 7.0 didn't really support UDMA/66 without a lot of tweaking. My guess is that your WD drive cannot do UDMA66 even though it was advertised to do such. Not impossible, but my drive doesn't work with any DMA mode in 7.1 (and it worked in 7.0 and in MSWindows). Another question directly related to that problem is what are the software or config files which have or could have an influence on the drive performances? I'm nearly certain that my problem doesn't come from the kernel. I know also that it's not hdparm (I tried the version included in 7.0). Philippe Actually the big change, AFAIK, is that UDMA66 is set up to work out of the box. This would suggest that it is specific to the HPT366 Controller/WD setup. Go to http://forum.mandrakesoft.com and look under UDMA66 Solved. I think you might yet be able to make it work, though it might not work at 66. I wasn't joking yesterday. I am really buying ATA/100 equipment to see if it will work at ATA/66. And even if it does work at 66, the missing error-checking feature would make me distrust my own system. WD drives really do blow off the CRC. So what is your board--Is the HPT366 integral or a card? Civileme Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: [expert] UDMA66 problem
On Thu, 29 Jun 2000, you wrote: "Jim P." wrote: I saved and printed your message and the next time I decide to abuse myself with 7.1 I'll give that a try. I have reinstalled 7.0 because I got tired of not having a working cd... Jim The information that it works in 7.0 and doesn't in 7.1 is suggestive of something else. The creative CDRW 4224 is enabled for DMA, and 7.1 would likely use it by default. If y'all don't mind me buttin in here, I believe the "suggestive of something else" is correct. I have a Plextor 8432 IDE and had to use the fix at http://www.linux-mandrake.com/en/demos/Tutorial/CDburner/pages/ to get it workin with 7.0. 7.1 set it up automagically, MOF 7.1 setup everything jus' right ;) Now I do assume you are trying to open a data disk and not an audio disk (because the audio disk doesn't use "files" per se) and it freezes on you. This suggests it might be overdriven or be treated as a HDD. I've got some data cdr's with 9,000 files (.jpg's) on 'em. They take a while to come up, but never freeze. An 'ls' at a console takes just as long as 'kfm', maybe a little longer. Once those cdr's are 'loaded' tho, file access is almost instant. Winblows is just the opposite. I have a Creative CDRW (same model) on my K6-2 500 system and 7.1 worked the first time, but I did NOT choose during the install to enable hard disk optimisations. I later enabled them for the hard drive alone using the hdparm command. (and besides man hdparm, there is VERY useful discussion of it at http://forum.mandrakesoft.com) If you enabled them during the 7.1 install, that might be something to back off a notch and see what happens. I didn't enable HDD opt during install either, mainly 'cause I just plain missed it. I added my usual hdparm lines to rc.local for the HDD's, but also had to add for my Cdrom and the Plex also. Both were extremely slow without enabling 32 bit and DMA, now they're fine again hdparm -m64 -c1 -u1 -d1 -k1 -a128 /dev/hda -- IBM dpta hdparm -m16 -c1 -u1 -d1 -k1 -a128 /dev/hdb -- WD Caviar hdparm -c1 -d1 -k1 /dev/hdc -- Plex cd-rw hdparm -c1 -d1 -k1 /dev/hdd -- BCD 40x cd -- ~~ Tom Brinkman[EMAIL PROTECTED]
Re: [expert] UDMA66 problem
On Thu, 29 Jun 2000, you wrote:
On Wed, 28 Jun 2000, you wrote:
Is anybody getting substantially better than 142 mb/sec and 22
mb/sec from 'hdparm -tT' ?? ATA/33 is capable of that 'cause
those are my numbers, and one (slave) HHD's a WD Caviar 8.4. ...
and is it worth all that hoops y'all seem to be jumpin thru to get
it workin? .. reliab'ly? and is it reliable ?
just askin what I seem to never hear about in conjunction with
ata/66 and performance. seems a better motherboard would do all
y'all /66'rs more good
I'm not even getting THAT...at least not on my EIDE drive
('course it's one that's been around a couple years, so
it's not optimized for UDMA...only an 850 meg drive G)
Now, just for giggles, I"m gonna see what I get on my UW
SCSI drive...
IDE:
[root@slave1 /root]# hdparm -tT /dev/hda
/dev/hda:
Timing buffer-cache reads: 128 MB in 3.18 seconds = 40.25 MB/sec
Timing buffered disk reads: 64 MB in 36.08 seconds = 1.77 MB/sec
/dev/hda:
Timing buffer-cache reads: 128 MB in 0.88 seconds = 145.45 MB/sec
Timing buffered disk reads: 64 MB in 2.88 seconds = 22.22 MB/sec
that's an IBM-DPTA-371360 7200 rpm, 2mb cache on ata/33 IDE with
hdparm -m64 -c1 -u1 -d1 -k1 -a128 /dev/hda in rc.local
/dev/hdb:
Timing buffer-cache reads: 128 MB in 0.85 seconds =150.59 MB/sec
Timing buffered disk reads: 64 MB in 6.19 seconds = 10.34 MB/sec
that's a WD AC38400L 5400rpm, 256k cache on ata/33 IDE with
hdparm -m16 -c1 -u1 -d1 -k1 -a128 /dev/hdb in rc.local
I just ran those, many runs yields about 142+ for both HDD's.
The 22.2 for the IBM is normal and constant. For the life of me I
can't get the WD to run any better (info hdparm suggests a lower
-mvalue for WD's), it's disc reads vary from 10.3 to 11.1
Motherboard's a Soyo 6ba+III (ata/33) oc'd at 135mhz FSB, but I
doubt the oc enhances HDD performance. The pci bus is 135/4 (damn
near spec of 33.3mhz), so I'm sure it doesn't hurt HDD performance
either. Single p3-450 cpu at 4.5x135 (608mhz)
SCSI:
Same exact specsmust be my motherboard can't handle
anything faster. :-/ Heh, course I'm only using a dual-PPro
system here... :-)
John
I know I must sound sort'a snippish 'bout this, but I really
think the best way to run ata/66 is to install an old 40 wire IDE
cable and disable it ;-) It's been shown that ata/66 only improves
burst speeds and that 'real world' performance is more times hurt
more than the little bit /66 helps. Maybe you can guess i've never
been a scuzzy fan either ;)
'bout the only time ata/66 performance is impressive is when
running HDtach on Winblows, all it does is measure burst rates
--
~~ Tom Brinkman[EMAIL PROTECTED]
Re: [expert] UDMA66 problem
If you are using a Western Digital drive, make sure that the Mode is set to UDMA66. They provide a floppy disk to do that with. If this is not done the drive can behave differently. This system is using two 7200RPM WD drives on the UDMA66 IDE3 port. Don On Thu, 29 Jun 2000, you wrote: Civileme wrote: 7.0 didn't really support UDMA/66 without a lot of tweaking. My guess is that your WD drive cannot do UDMA66 even though it was advertised to do such. Not impossible, but my drive doesn't work with any DMA mode in 7.1 (and it worked in 7.0 and in MSWindows). Another question directly related to that problem is what are the software or config files which have or could have an influence on the drive performances? I'm nearly certain that my problem doesn't come from the kernel. I know also that it's not hdparm (I tried the version included in 7.0). Philippe
Re: [expert] UDMA66 problem
What kind of main board are you using? Don On Thu, 29 Jun 2000, you wrote: John Aldrich wrote: Hmm...Ok. My bad. I didn't see that bit about it working in 7.0 but not in 7.1. There have been reports (on this list and others) about some brands of hard drives NOT being up to the UDMA 66 spec, and causing problems, especially if there are other brands of hard drive in the system / on the same drive chain. The drive is alone on the HPT366 controller. Further, it's said that you have to have a special cable for DMA transfers. I don't know this from personal experience, again, not having the hardware to test. And I've the special cable. Philippe
Re: [expert] UDMA66 problem
"Jim P." wrote: I don't have the optimisations enabledI have tried everything to get it going...it's been frusterating to the nth degreeI have a standard floppy...like I said it works fine in 7.0 after doing the fix (cd /dev rm cdrom ln -s scd0 cdrom) no problems at allbut install 7.1 and it refuses to work...removes the drive from bios locks on and I can't even eject the darn thing until I power completely down.I dunno guyit's about to drive me nuts...LOL Jim About to drive _you_ nuts? I was away from the list for a while... but I do have the phenomenon in mind. I think the drive to make me nuts would be the shorter rideBG The hardware I have is very similar to yours. PLease let me see the output of dmesg cat /proc/pci lspcidrake cat /etc/fstab (AFTER you try installing 7.1 again) And I am very curious also why /dev/scd0 would work. CDRWs are normally assigned /dev/sr0, /dev/sr1 Could THAT be it? Is your CDRW acting like ONLY a CD-R? You did a manual /dev/scd0 in 7.0 but the 7.1 install would have done a symbolic link to /dev/sr0 They should both be block-major-11 but if the W portion isn't working I have no idea what that effect would be. Civileme
Re: [expert] UDMA66 problem
Civileme [EMAIL PROTECTED] wrote: dmesg cat /proc/pci lspcidrake cat /etc/fstab (AFTER you try installing 7.1 again) And I am very curious also why /dev/scd0 would work. CDRWs are normally assigned /dev/sr0, /dev/sr1 Could THAT be it? Is your CDRW acting like ONLY a CD-R? You did a manual /dev/scd0 in 7.0 but the 7.1 install would have done a symbolic link to /dev/sr0 They should both be block-major-11 but if the W portion isn't working I have no idea what that effect would be. I have a CD-RW drive in a new Dell that I recently installed 7.1 on, and MDK set up a link from /dev/cdrom to /dev/scd0, not to /dev/sr0. Both /dev/scd0 and /dev/sr0 exist, but I note that the owner/groups are carver/disk and root/cdwriter, respectively (where carver is the current logged in user). I have not gotten around to burning any CDs yet, but we have found that it cannot properly read CD-RWs (reads normal CDs, CD-Rs, and music CDs fine). Could this have something to do with the device link? The supermount info in fstab refers to /dev/cdrom. Also, when I just did dmesg, I simply get a bunch of lines like: sr0: CDROM not ready. Make sure there is a disc in the drive. followed by sr0: disc change detected. So something is strange here--cdrom linked to scd0, but clearly getting messages related to sr0. [Also, why is dmesg simply showing me these messages and not the bootup info that is in /var/log/dmesg. I don't see these sr0 messages in any log file. Where are they being stored?] Thanks, Norm
[expert] UDMA66 problem
Hi, I've got a WD136BA hard disk on my hpt366 controller. If I try to use DMA for disk access, my system freezes. This problem didn't exist with Mandrake 7.0, but it appeared when I installed 7.1. I tried to upgrade my bios. Nothing changed. After that, I compiled another kernel (2.3.45). Same problem. I compiled 2.2.15 and 2.3.45 in 386 code instead of 586. Always the same problem. Philippe
Re: [expert] UDMA66 problem
On Wed, 28 Jun 2000, you wrote: Hi, I've got a WD136BA hard disk on my hpt366 controller. If I try to use DMA for disk access, my system freezes. This problem didn't exist with Mandrake 7.0, but it appeared when I installed 7.1. I tried to upgrade my bios. Nothing changed. After that, I compiled another kernel (2.3.45). Same problem. I compiled 2.2.15 and 2.3.45 in 386 code instead of 586. Always the same problem. Probably due to the hard drive not being up to spec. John
Re: [expert] UDMA66 problem
In what way could the hard drive not be up to spec? The original post said the problem didn't exist with Mandrake 7.0. Not trying to butt in, but I also have an IDE device which did work with 7.0 but does not with 7.1. ---Norvell Spearman John Aldrich wrote: On Wed, 28 Jun 2000, you wrote: Hi, I've got a WD136BA hard disk on my hpt366 controller. If I try to use DMA for disk access, my system freezes. This problem didn't exist with Mandrake 7.0, but it appeared when I installed 7.1. I tried to upgrade my bios. Nothing changed. After that, I compiled another kernel (2.3.45). Same problem. I compiled 2.2.15 and 2.3.45 in 386 code instead of 586. Always the same problem. Probably due to the hard drive not being up to spec. John
Re: [expert] UDMA66 problem
Philippe Wautelet wrote: Hi, I've got a WD136BA hard disk on my hpt366 controller. If I try to use DMA for disk access, my system freezes. This problem didn't exist with Mandrake 7.0, but it appeared when I installed 7.1. I tried to upgrade my bios. Nothing changed. After that, I compiled another kernel (2.3.45). Same problem. I compiled 2.2.15 and 2.3.45 in 386 code instead of 586. Always the same problem. Philippe Please read http://kt.linuxcare.com/kernel-traffic/kt2214_54.epl (2nd item) 7.0 didn't really support UDMA/66 without a lot of tweaking. My guess is that your WD drive cannot do UDMA66 even though it was advertised to do such. There are a few tweaks you can try--see "UDMA 66 solved" at http://forum.mandrakesoft.com. But WD drives ARE a hardware problem and likely will be for some time to come. They do not do what they are supposed to in several categories, and UDMA66 is showing it up grandly. Of course, the recompilation in 386 code should(tm) have cleared most of the problems, but it is not guaranteed to clear them all. Civileme
Re: [expert] UDMA66 problem
Norvell Spearman wrote: In what way could the hard drive not be up to spec? The original post said the problem didn't exist with Mandrake 7.0. Not trying to butt in, but I also have an IDE device which did work with 7.0 but does not with 7.1. ---Norvell Spearman John Aldrich wrote: On Wed, 28 Jun 2000, you wrote: Hi, I've got a WD136BA hard disk on my hpt366 controller. If I try to use DMA for disk access, my system freezes. This problem didn't exist with Mandrake 7.0, but it appeared when I installed 7.1. I tried to upgrade my bios. Nothing changed. After that, I compiled another kernel (2.3.45). Same problem. I compiled 2.2.15 and 2.3.45 in 386 code instead of 586. Always the same problem. Probably due to the hard drive not being up to spec. John Run hdparm on 7.0 and see what mode it was running--bet it was udma33 . 7.1 does UDMA66 out of the box and a LOT of cheap drives are out of spec for that, even ones advertised to be UDMA66, and ESPECIALLY Western Digital, not by poor quality but by poor and cheap design. read it all here http://kt.linuxcare.com/kernel-traffic/kt2214_54.epl @nd item. Civileme
Re: [expert] UDMA66 problem
On Wed, 28 Jun 2000, you wrote: In what way could the hard drive not be up to spec? The original post said the problem didn't exist with Mandrake 7.0. Not trying to butt in, but I also have an IDE device which did work with 7.0 but does not with 7.1. Hmm...Ok. My bad. I didn't see that bit about it working in 7.0 but not in 7.1. There have been reports (on this list and others) about some brands of hard drives NOT being up to the UDMA 66 spec, and causing problems, especially if there are other brands of hard drive in the system / on the same drive chain. Further, it's said that you have to have a special cable for DMA transfers. I don't know this from personal experience, again, not having the hardware to test. John
Re: [expert] UDMA66 problem
On Wed, 28 Jun 2000, John Aldrich wrote: Further, it's said that you have to have a special cable for DMA transfers. I don't know this from personal experience, again, not having the hardware to test. John You do. An ATA/66 cable has the same 40 pins as any other IDE cable, but has 80 conducting wires in it. I *think* the extra 40 (every other wire) are just tied to ground, so as to reduce crosstalk between the wires. Thus, you can get better tranfer rates. -Matt Stegman [EMAIL PROTECTED]
Re: [expert] UDMA66 problem
IDE devices seem to be a major problem with 7.1 I have been seeking help with a cdrom/burner for over a month...and it still doesn't workmandrake support has been 0 help as wellI keep saying it's a bug...but seems that word is only associated with mickeysoftbut it's a bug they NEED to address Jim In what way could the hard drive not be up to spec? The original post said the problem didn't exist with Mandrake 7.0. Not trying to butt in, but I also have an IDE device which did work with 7.0 but does not with 7.1. ---Norvell Spearman John Aldrich wrote: On Wed, 28 Jun 2000, you wrote: Hi, I've got a WD136BA hard disk on my hpt366 controller. If I try to use DMA for disk access, my system freezes. This problem didn't exist with Mandrake 7.0, but it appeared when I installed 7.1. I tried to upgrade my bios. Nothing changed. After that, I compiled another kernel (2.3.45). Same problem. I compiled 2.2.15 and 2.3.45 in 386 code instead of 586. Always the same problem. Probably due to the hard drive not being up to spec. John
Re: [expert] UDMA66 problem
What types of problems are we talking about Jim? I haven´t had any problems at all with my HDs, CDROM, and burner under 7.0 or 7.1. My HDs are UDMA66 and the CDs are regular IDEs. Let me know, maybe I can help. B On Wed, 28 Jun 2000, you wrote: IDE devices seem to be a major problem with 7.1 I have been seeking help with a cdrom/burner for over a month...and it still doesn't workmandrake support has been 0 help as wellI keep saying it's a bug...but seems that word is only associated with mickeysoftbut it's a bug they NEED to address Jim In what way could the hard drive not be up to spec? The original post said the problem didn't exist with Mandrake 7.0. Not trying to butt in, but I also have an IDE device which did work with 7.0 but does not with 7.1. ---Norvell Spearman John Aldrich wrote: On Wed, 28 Jun 2000, you wrote: Hi, I've got a WD136BA hard disk on my hpt366 controller. If I try to use DMA for disk access, my system freezes. This problem didn't exist with Mandrake 7.0, but it appeared when I installed 7.1. I tried to upgrade my bios. Nothing changed. After that, I compiled another kernel (2.3.45). Same problem. I compiled 2.2.15 and 2.3.45 in 386 code instead of 586. Always the same problem. Probably due to the hard drive not being up to spec. John -- *** Virginia Polytechnic Institute and State University Computer Engineering E-MAIL: [EMAIL PROTECTED] ***
Re: [expert] UDMA66 problem
On Wed, 28 Jun 2000, you wrote: IDE devices seem to be a major problem with 7.1 I have been seeking help with a cdrom/burner for over a month...and it still doesn't workmandrake support has been 0 help as wellI keep saying it's a bug...but seems that word is only associated with mickeysoftbut it's a bug they NEED to address Just out of curiosity, have you tried setting it up using ide-scsi and all that? I use a SCSI CDRW myself, so I can't be much help. IIRC, though, at least in previous versions of Mandrake (and RedHat) you needed to load the ide-scsi module as well as adding 'append="hdX=ide-scsi"' to your lilo.conf in order to get an IDE CDR/RW to work in Linux. John
Re: [expert] UDMA66 problem
"Jim P." wrote: IDE devices seem to be a major problem with 7.1 I have been seeking help with a cdrom/burner for over a month...and it still doesn't workmandrake support has been 0 help as wellI keep saying it's a bug...but seems that word is only associated with mickeysoftbut it's a bug they NEED to address Jim In what way could the hard drive not be up to spec? The original post said the problem didn't exist with Mandrake 7.0. Not trying to butt in, but I also have an IDE device which did work with 7.0 but does not with 7.1. ---Norvell Spearman John Aldrich wrote: On Wed, 28 Jun 2000, you wrote: Hi, I've got a WD136BA hard disk on my hpt366 controller. If I try to use DMA for disk access, my system freezes. This problem didn't exist with Mandrake 7.0, but it appeared when I installed 7.1. I tried to upgrade my bios. Nothing changed. After that, I compiled another kernel (2.3.45). Same problem. I compiled 2.2.15 and 2.3.45 in 386 code instead of 586. Always the same problem. Probably due to the hard drive not being up to spec. John Jim, what precisely is your problem with the IDE CD-RW? I know that CD-RWs work with the exception of one brand where the cdrecord author says it is a hardware otu of spec and the manufacturer of the CD-RW says "We only support Windows". Send the output of lspcidrake cat /proc/pci dmesg And maybe you can get some help from some of the volunteers here. Speaking as one experienced in the matters of identifying bugs, I like to report what I am able to find, but I hesitate on claiming it to be a bug. Often, far too often for my own self-image, I have found the bug had its hands on my keyboard. Anyway, let's get some data and work on the problem, then decide what it is. If it is a bug that needs attention, I'll submit it too. Civileme
Re: [expert] UDMA66 problem
"Jim P." wrote: I saved and printed your message and the next time I decide to abuse myself with 7.1 I'll give that a try. I have reinstalled 7.0 because I got tired of not having a working cd... Jim - Original Message - From: "John Aldrich" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 28, 2000 4:28 PM Subject: Re: [expert] UDMA66 problem On Wed, 28 Jun 2000, you wrote: IDE devices seem to be a major problem with 7.1 I have been seeking help with a cdrom/burner for over a month...and it still doesn't workmandrake support has been 0 help as wellI keep saying it's a bug...but seems that word is only associated with mickeysoftbut it's a bug they NEED to address Just out of curiosity, have you tried setting it up using ide-scsi and all that? I use a SCSI CDRW myself, so I can't be much help. IIRC, though, at least in previous versions of Mandrake (and RedHat) you needed to load the ide-scsi module as well as adding 'append="hdX=ide-scsi"' to your lilo.conf in order to get an IDE CDR/RW to work in Linux. John Those things are done automagically in 7.1 But with some drives supermount can interfere with burning. Basically, your drive MUST be unmounted to burn. Most drives unmount with a complaint when supermount is active and complain again when the burner program exits, but the complaints do not prevent business as usual. With a few drives, the complaint stops the show... While you have 7.0 running, let's see what lspcidrake and dmesg shows and maybe someone will be able to say "Oh, yes,m with that configuration you avoid the problem with" Civileme
Re: [expert] UDMA66 problem
"Jim P." wrote: I saved and printed your message and the next time I decide to abuse myself with 7.1 I'll give that a try. I have reinstalled 7.0 because I got tired of not having a working cd... Jim The information that it works in 7.0 and doesn't in 7.1 is suggestive of something else. The creative CDRW 4224 is enabled for DMA, and 7.1 would likely use it by default. Now I do assume you are trying to open a data disk and not an audio disk (because the audio disk doesn't use "files" per se) and it freezes on you. This suggests it might be overdriven or be treated as a HDD. I have a Creative CDRW (same model) on my K6-2 500 system and 7.1 worked the first time, but I did NOT choose during the install to enable hard disk optimisations. I later enabled them for the hard drive alone using the hdparm command. (and besides man hdparm, there is VERY useful discussion of it at http://forum.mandrakesoft.com) If you enabled them during the 7.1 install, that might be something to back off a notch and see what happens. Nexxt question--do you have a standard floppy or an LS120/LX120? Special considerations apply to those little demons, but there are workarounds. I just moved from an LS120 to a regular floppy--no duplication. I don't understand why I am unable to duplicate the behavior here. What else is different in our systems? I just moved the CDRW to another computer with a K6-2 300 and a VIA MVP3 chipset. The other was a VIA MVP4. Still no duplication. My drive works under 7.0 and 7.1. This is most odd. I will try reinstall tomorrow and enable HD optimisation and see if it makes a difference. Actually 7.0 should introduce a problem with a CDRW. The 'append="ide-scsi"' is set up and the module loaded but the ln -s /dev/sr0 /dev/cdrw is NOT performed. So you cannot access it under 7.0 til you tweak. That problem was corrected in 7.1. I'll let you know if I duplicate the behavior under 7.1 that you are experiencing. Civileme
