Re: [expert] NFS mounts fail
On Thu, 06 Jul 2000, you wrote: On Wed, 05 Jul 2000, you wrote: I seem to have a problem between two NFS server, mounting each others stuff, the one is a SuSE6.1 machine running 2.2.16 (same with 2.2.13) and the other a Mandrake 7.0 machine, running 2.2.16 (same with 2.4.0test2) as well. Mounts located on the SuSE machine to the Mandrake machine work just fine, but v.v.: nogo.. on the Mandrake machine: /etc/exports: See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. #/usr/src/linux 192.168.0.0/255.255.255.0(ro) #,no_root_squash) #/usr/doc 192.168.0.0/255.255.255.0(ro) #/cdrom 192.168.0.0/255.255.255.0(ro) /usr/src *.thuis.nl(rw) /home/mbr/download *.thuis.nl(rw) #/mnt/cdrom2*.thuis.nl(ro) #/mnt/cdrom3*.thuis.nl(ro) #,no_root_squash) SuSE machine: /var/log/messages (during init): nfs_read_super: get root fattr failed nfsd_fh_init : initialized fhcache, entries=512 nfs: RPC call returned error 111 RPC: task of released request still queued! RPC: (task is on xprt_pending) nfs_read_super: get root fattr failed /etc/fstab: XXLTurboSlakkie:/usr/src/linux /usr/src/linux nfs noauto,nosuid,rsize=8192,timeo=14,intr,retry=1,bg,retrans=1,soft,acregmin=60,acregmax=1 XXLTurboSlakkie:/home/mbr/download /home/mbr/download nfs auto,nosuid,bg,soft,retry=1 #192.168.0.1:/home/mbr/download /home/mbr/download nfs // this one will also fail.. SuSE machine: root@TurboRouter:/etc knfsstat Server rpc stats: calls badcalls badauthbadclntxdrcall 0 0 0 0 0 Server nfs v2: null getattrsetattrroot lookup readlink 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Client rpc stats: calls retransauthrefrsh 0 0 0 Client nfs v2: null getattrsetattrroot lookup readlink 0 0% 2 100% 0 0% 0 0% 0 0% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Mandrake machine: [root@XXLTurboSlakkie mbr]# /usr/sbin/nfsstat Server rpc stats: calls badcalls badauthbadclntxdrcall 0 0 0 0 0 Server nfs v2: null getattrsetattrroot lookup readlink 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Client rpc stats: calls retransauthrefrsh 37 2 0 Client nfs v2: null getattrsetattrroot lookup readlink 0 0% 5 13% 0 0% 0 0% 26 70% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 6 16% 0 0% root@TurboRouter:/etc mount -a mount: wrong fs type, bad option, bad superblock on XXLTurboSlakkie::/usr/src/linux, or too many mounted file systems mount: wrong fs type, bad option, bad superblock on 192.168.0.1:/home/mbr/download,or too many mounted file systems Anyone an idea what's going on? 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' */ I've been having the same problem (one machine is able to mount, the other machine is not) and am avidly awaiting the replies hoping to learn what the problem is. My systems at present are both LM 7.1. So, it seems to be having something to do, with using spaces iso tabs in /etc/exports, maybe this will help... New problem with nfs (client/server both running 2.2.16 with build in nfs client/server support): I've putten this into /etc/exports:(server machine) # See exports(5) for a description. # This file contains a list of all
Re: [expert] NFS mounts fail
On Thu, 06 Jul 2000, you wrote: "Manuël Beunder" wrote: I seem to have a problem between two NFS server, mounting each others stuff, the one is a SuSE6.1 machine running 2.2.16 (same with 2.2.13) and the other a Mandrake 7.0 machine, running 2.2.16 (same with 2.4.0test2) as well. Mounts located on the SuSE machine to the Mandrake machine work just fine, but v.v.: nogo.. on the Mandrake machine: /etc/exports: See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. #/usr/src/linux 192.168.0.0/255.255.255.0(ro) #,no_root_squash) #/usr/doc 192.168.0.0/255.255.255.0(ro) #/cdrom 192.168.0.0/255.255.255.0(ro) /usr/src *.thuis.nl(rw) /home/mbr/download *.thuis.nl(rw) #/mnt/cdrom2*.thuis.nl(ro) #/mnt/cdrom3*.thuis.nl(ro) #,no_root_squash) SuSE machine: /var/log/messages (during init): nfs_read_super: get root fattr failed nfsd_fh_init : initialized fhcache, entries=512 nfs: RPC call returned error 111 RPC: task of released request still queued! RPC: (task is on xprt_pending) nfs_read_super: get root fattr failed /etc/fstab: XXLTurboSlakkie:/usr/src/linux /usr/src/linux nfs noauto,nosuid,rsize=8192,timeo=14,intr,retry=1,bg,retrans=1,soft,acregmin=60,acregmax=1 XXLTurboSlakkie:/home/mbr/download /home/mbr/download nfs auto,nosuid,bg,soft,retry=1 #192.168.0.1:/home/mbr/download /home/mbr/download nfs // this one will also fail.. SuSE machine: root@TurboRouter:/etc knfsstat Server rpc stats: calls badcalls badauthbadclntxdrcall 0 0 0 0 0 Server nfs v2: null getattrsetattrroot lookup readlink 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Client rpc stats: calls retransauthrefrsh 0 0 0 Client nfs v2: null getattrsetattrroot lookup readlink 0 0% 2 100% 0 0% 0 0% 0 0% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Mandrake machine: [root@XXLTurboSlakkie mbr]# /usr/sbin/nfsstat Server rpc stats: calls badcalls badauthbadclntxdrcall 0 0 0 0 0 Server nfs v2: null getattrsetattrroot lookup readlink 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Client rpc stats: calls retransauthrefrsh 37 2 0 Client nfs v2: null getattrsetattrroot lookup readlink 0 0% 5 13% 0 0% 0 0% 26 70% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 6 16% 0 0% root@TurboRouter:/etc mount -a mount: wrong fs type, bad option, bad superblock on XXLTurboSlakkie::/usr/src/linux, or too many mounted file systems mount: wrong fs type, bad option, bad superblock on 192.168.0.1:/home/mbr/download,or too many mounted file systems Anyone an idea what's going on? 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' */ Check /var/log/messages on the mandrake machine right after an attempted mount. The wildcards may ne causing problems, try writing out each host followed by (rw) followed by one space for those you want to access a mount point. End each of those mount point lines with two spaces and a \n (newline). Make certain those hostnames resolve in /etc/hosts and in /etc/hosts.allow Works for me. Civileme I didn't quite get what you were saying, but replacing the spaces by a single tab, fixed the problem (duh)... These are just those things, that drive you crazy sometimes... (had been experimenting with NBD as well and just installed a new kernel as well) Cheers, -- /* Manuël Beunder. (aka MBr) - http://how.to/sblive the SB L
[expert] NFS mounts fail
I seem to have a problem between two NFS server, mounting each others stuff, the one is a SuSE6.1 machine running 2.2.16 (same with 2.2.13) and the other a Mandrake 7.0 machine, running 2.2.16 (same with 2.4.0test2) as well. Mounts located on the SuSE machine to the Mandrake machine work just fine, but v.v.: nogo.. on the Mandrake machine: /etc/exports: See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. #/usr/src/linux 192.168.0.0/255.255.255.0(ro) #,no_root_squash) #/usr/doc 192.168.0.0/255.255.255.0(ro) #/cdrom 192.168.0.0/255.255.255.0(ro) /usr/src *.thuis.nl(rw) /home/mbr/download *.thuis.nl(rw) #/mnt/cdrom2*.thuis.nl(ro) #/mnt/cdrom3*.thuis.nl(ro) #,no_root_squash) SuSE machine: /var/log/messages (during init): nfs_read_super: get root fattr failed nfsd_fh_init : initialized fhcache, entries=512 nfs: RPC call returned error 111 RPC: task of released request still queued! RPC: (task is on xprt_pending) nfs_read_super: get root fattr failed /etc/fstab: XXLTurboSlakkie:/usr/src/linux /usr/src/linux nfs noauto,nosuid,rsize=8192,timeo=14,intr,retry=1,bg,retrans=1,soft,acregmin=60,acregmax=1 XXLTurboSlakkie:/home/mbr/download /home/mbr/download nfs auto,nosuid,bg,soft,retry=1 #192.168.0.1:/home/mbr/download /home/mbr/download nfs // this one will also fail.. SuSE machine: root@TurboRouter:/etc knfsstat Server rpc stats: calls badcalls badauthbadclntxdrcall 0 0 0 0 0 Server nfs v2: null getattrsetattrroot lookup readlink 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Client rpc stats: calls retransauthrefrsh 0 0 0 Client nfs v2: null getattrsetattrroot lookup readlink 0 0% 2 100% 0 0% 0 0% 0 0% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Mandrake machine: [root@XXLTurboSlakkie mbr]# /usr/sbin/nfsstat Server rpc stats: calls badcalls badauthbadclntxdrcall 0 0 0 0 0 Server nfs v2: null getattrsetattrroot lookup readlink 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Client rpc stats: calls retransauthrefrsh 37 2 0 Client nfs v2: null getattrsetattrroot lookup readlink 0 0% 5 13% 0 0% 0 0% 26 70% 0 0% read wrcachewrite create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlinkmkdir rmdir readdirfsstat 0 0% 0 0% 0 0% 0 0% 6 16% 0 0% root@TurboRouter:/etc mount -a mount: wrong fs type, bad option, bad superblock on XXLTurboSlakkie::/usr/src/linux, or too many mounted file systems mount: wrong fs type, bad option, bad superblock on 192.168.0.1:/home/mbr/download,or too many mounted file systems Anyone an idea what's going on? 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' */
[expert] Problems with multiple overlay Flashmovies with Netscape 4.7 Flash4 plugin (Mandrake 7.0)
Hi, There seems to be a problem with sites when using Netscape 4.7 (delivered with Mandrake 4.7) and the Flash4 plugin, when it comes to sites who use multi Flash-movies in an overlay.. Anyone an idea how to work around this? (If nessairy, the webmaster can alter the content of the site: http://www.brothers.nl) 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] X 4, PPP, and Emu10k1
On Mon, 03 Jul 2000, you wrote: Seanmay I share with you a short description of my approach to running new versions of Linux-Mandrake that I believe saves me from the kind of frustration that you are experiencing? I'm running my computer on 7.1, but my 7.0 installation still exists on the same hard drive as 7.1 is on and if something happens, even something cataclysmic, with my 7.1 installation I can immediately boot up on my old 7.0 installation and continue where I left off a month ago. When I installed 7.1 I did a new install on fresh partitions, not an upgrade over my old 7.0 installation. Then, after testing out the new 7.1 installation, I copied my 7.0 /home and /root directories to the 7.1 file system and reinstalled any extra software that still didn't work (/user /opt stuff mainly). After that I began to use the new 7.1 installation daily and abandoned the old 7.0 installation. But it's still there in case I need it and I'll leave it there till I erase the partitions and install 7.2 in its place. It took me a couple of hours to get 7.1 up to speed with my personal stuff, but at any time, if a problem would have occurred I could have simply gone back to my intact 7.0 system. I've been doing it this way (with some refinements) since version 5.2. I've never done an upgrade (too many horror stories). You could always spawn a copy of your distro with dd and 'experiment' on that copy.. (But I still have a copy of SuSE6.1 (which I didn't upgrade from my SuSE5.3 install) and RedHat 6.0 running as well, very handy when some stuff doesn't wants to compile etc.. just love locatedb, just hack/copy/steal go.. ;-) Alan Sean Middleditch wrote: [snip] [snip] Sorry for attitude, but for the last few days I've been seriously wishing I just kept my Mandrake 7.0 installation.. MDK 7.0 was the best, and 7.1 is really not impressing me. Again, sorry. I'll try and calm down a bit next time... :) Not your guys' fault, I know. Sean Middleditch 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 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' */
[expert] ATA/33-ATA66 HPT366 black list
From /usr/src/linux/drivers/block/ide-dma.c
/*
* bad_dma_drives() lists the model names (from "hdparm -i")
* of drives which supposedly support (U)DMA but which are
* known to corrupt data with this interface under Linux.
*
* This is an empirical list. Its generated from bug reports. That means
* while it reflects actual problem distributions it doesn't answer whether
* the drive or the controller, or cabling, or software, or some combination
* thereof is the fault. If you don't happen to agree with the kernel's
* opinion of your drive - use hdparm to turn DMA on.
*/
const char *bad_dma_drives[] = {"WDC AC11000H",
"WDC AC22100H",
"WDC AC32100H",
"WDC AC32500H",
"WDC AC33100H",
"WDC AC31600H",
NULL};
(WDC = Western Digital Corporation)
From /usr/src/linux/drivers/block/ide-dma.c
const char *bad_ata66_4[] = {
"WDC AC310200R",
NULL
};
const char *bad_ata66_3[] = {
"WDC AC310200R",
NULL
};
const char *bad_ata33[] = {
"Maxtor 92720U8", "Maxtor 92040U6", "Maxtor 91360U4", "Maxtor 91020U3",
"Maxtor 90845U3", "Maxtor 90650U2",
"Maxtor 91360D8", "Maxtor 91190D7", "Maxtor 91020D6", "Maxtor 90845D5",
"Maxtor 90680D4", "Maxtor 90510D3", "Maxtor 90340D2",
"Maxtor 91152D8", "Maxtor 91008D7", "Maxtor 90845D6", "Maxtor 90840D6",
"Maxtor 90720D5", "Maxtor 90648D5", "Maxtor 90576D4",
"Maxtor 90510D4",
"Maxtor 90432D3", "Maxtor 90288D2", "Maxtor 90256D2",
"Maxtor 91000D8", "Maxtor 90910D8", "Maxtor 90875D7", "Maxtor 90840D7",
"Maxtor 90750D6", "Maxtor 90625D5", "Maxtor 90500D4",
"Maxtor 91728D8", "Maxtor 91512D7", "Maxtor 91303D6", "Maxtor 91080D5",
"Maxtor 90845D4", "Maxtor 90680D4", "Maxtor 90648D3", "Maxtor 90432D2",
NULL
};
(afaik in xUn U stands for UDMA/66, D for UDMA(/33)
I hope this gives a better overview to people, which drives not to buy/use with
the Highpoint HPT366 (Abit HotRod) in UDMA/33 UDMA/66 mode
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] Mandrake 7.1 and BP6 hard drive optimizations
0220-022f : soundblaster 0330-0333 : MPU-401 UART 0376-0376 : ide1 0388-038b : Yamaha OPL3 03c0-03df : vga+ 03f6-03f6 : ide0 03f8-03ff : serial(auto) a400-a41f : eth1 a800-a8ff : eth0 ac00-acfe : aic7xxx b000-b007 : ide2 b402-b402 : ide2 b800-b807 : ide2 b810-b8ff : HPT366 c400-c407 : ide3 c410-c4ff : HPT366 f000-f007 : ide0 f008-f00f : ide1 If anyone can help me with this one I will send you a six pack of your favorite beer (provided you are of age of course :-). Thanks Paul recompile for 386 code, kernel and driver. The Seagate IDE drive is marginal at the timing and signal gating requirements of 586 code and often locks up. So do MOST WDs, though some of them will work without the Xxx parm and often run close to the UDMA66 speed required. Read kernel traffic in February to learn why. It has to do with the fact that drive and chipset mfgrs are assuming timing for 386 code instead of the "official" specs for the interface, and 586 code timing is tighter, hence reflections on signal gating lines that should NOT be there are being observed. IBMs, Maxtors, and Quantums in the same position on the same board seem to work just fine. Err, unfortiunatly no, both Diamond Max 6800 ATA/33 ATA/66 series (eg. 91000D8, 91360U4), seem to be affected with timing issues as well, on the HPT366... (though they seem to work okay on the Promise Ultra66 (PDC 20262). I also own an ATA/33 Seagate ST36531A with screwy DMA transfers on the HPT366 as well :-( Civileme 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] ATA/100 Fails
On Thu, 29 Jun 2000, you wrote: Gee, this must be a new bug. My brand new Duron Board won't work with ATA/100 on Mandrake 7.1 (of course it won't work at ATA 100 with RH, Caldera, FreeBSD, Windows (any flavor) or BeOS either) Where are these guys at? The Duron and ATA motherboards came out, available for sale on June 15 and no distro, not even Mandrake, supports them. It has been TWO WHOLE WEEKS And I had to search 28 vendors to find an ATA/100 drive, too ;-P Where do I sent the Bug reports? [EMAIL PROTECTED] (Andre Hedrick) Yes I really do have a Duron and I really do have ATA/100 rated equipment. I'll let you know in a few days whether it works at ATA 66 which is what I am shooting for. I just could not resist poking a bit of fun at the folks who thing UDMA66 not working out of the box is Mandrake's fault. There are too many variables to assume that. I frankly don't see any advantage to ATA/100 except if you buy stuff rated for 100 it might actually work stably at 66. Frankly, I also don't see any advantage of ATA/66 over ATA/33 (unless you are running a RAID config..) Civileme 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' */
[expert] backgrounding NFS mount
Hi, I use the next line in fstab to nfs-mount a cd-rom of my linux router box, the only problem is, that the router isn't online all the time and than it takes ages at startup / shutdown of the system to time-out.. How can I create a real background mount, so my init scripts won't be blocked by this? fstab: TurboRouter:/cdrom /mnt/nfs_cdrom nfs nosuid,rsize=8192,timeo=14,intr,retry=1,bg,retrans=1,soft,acregmin=60,acregmax=1 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 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] Promise ATA-66
On Fri, 16 Jun 2000, you wrote: tal amir wrote: Yes it is :-) Original Message On 6/15/00, 2:35:45 PM, "Cecil Watson" [EMAIL PROTECTED] wrote regarding [expert] Promise ATA-66: Is the Promise ATA-66 supported in 7.1? Thanks in advance, Cecil Yes, it is, BUT ABIT B_6 boards require special LILO settings for their installation on ATA66 to work properly Not correct, I use LILO without any options, just make a ~10MB boot partition and mount it under /boot and install LILO on it (when using older LILO versions, make sure it is located beneath the 1024th cilinder). Also, using the special LILO reverse options, can render some troubles with some PCI cards / SCSI controllers, like eg. the SB Live! (not sure if that is fixed now). Anything but the newest WD disks will give you all sorts of errors if you set them to DMA/UDMA Also using DMA for ATA-pi devices for the Highpoint HPT366 (HotRod) or Promise 20262 is not advisable (for playing DVD etc.). So make sure your DMA using ATA-pi devices are located on the Intel controller. Also many Maxtor drives won't work properly on the non-intel ATA66 controllers, the best option is to reprogram the drives to ATA33 and put them on the Intel controller. Some board chipsets do not work well with the PCI controller card. So, knowing those things, prepare for an education in BIOSes and HDDs and Disk controllers if you are in the 40% who need to do special things. Civileme 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' */
