Date: Fri, 25 May 2001 11:43:25 -0400 From: Seth <seth@psychotic.aberrant.org> To: Ron Klinkien <ron@zappa.demon.nl> Cc: freebsd-stable@freebsd.org Subject: Re: Athlon Power and FreeBSD-STABLE experiences. Message-ID: <20010525114325.A4857@psychotic.aberrant.org> In-Reply-To: <000d01c0e50e$dc7f3180$9601a8c0@denhartogh.nl>; from ron@zappa.demon.nl on Fri, May 25, 2001 at 01:35:24PM %2B0200 References: <000d01c0e50e$dc7f3180$9601a8c0@denhartogh.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm running -STABLE on an ASUS A7V133 with the 686B south bridge and have no problems (other than the fact that I can't find any utility to probe motherboard/cpu temps -- sigh). The 686B south bridge problems were (IIRC) related to PCI interrupt sharing. Latest BIOS revs from all major MB manufacturers claim to have resolved this issue. (I didn't experience it, so I didn't upgrade.) I don't do heavy disk-to-disk IDE transfers; in fact, none at all (my CDROM is SCSI). CPU is a 1GHz Thunderbird, by the way. After one hour of CPUburn, by temp (reported by BIOS) is 53C, motherboard is 35C. Normal CPU temp (mostly idle) is around 43-44. I've been assured that this is within spec. (I switched to a Volcano II from a Global Win due to noise. The Global Win was definitely cooler but too loud.) Surprisingly enough, I've seen "write failed" messages when there was a problem with the CD. I know it sounds strange, but reburning the CD and reinstalling fixed it. This was a couple years ago with one of the 3-releases. My onboard ATA100 controller works fine (getting UDMA5 on my Maxtor 40gig), but performance is a bit weak: 11MB/sec sustained writes (using dd and /dev/zero -- not the best benchmark, but still...) The other onboard controller, a Promise UltraATA100, also works fine. Sorry I can't validate your experiences. I've had good luck so far (again, with the two exceptions noted above: CPU/fan monitoring and disk write speed.) Seth. > > I then tried to install FreeBSD 4.3-RELEASE from CD, the install failed > when installing hunk 31 of the bin set. I got "write failed..." > > Tried an old FreeBSD 4.2-RELEASE CD and it installed fine > strange enough. But after rebooting I got "UDMA ICRC switching back to PIO4" > errors. ;-((((( > > Searching the fbsd archives I found alot of people with VIA 686 chips > which had the same problems. Forcing to PIO mode is a no-no for me, > -I didn't buy an UDMA100 disk/ctrl for nothing.- > And using spiffy new hardware and correct 80-wire cables and everything, > I decided to upgrade via cvsup to 4.3-STABLE, and build world/kernel, > this all went fine. (With PIO mode enabled temporary) > > And after rebooting all the UDMA problems were gone!! > > But I got one new problem; the infamous "microuptime() went backwards error" > came to the scene. > > Browsed the mailing archive again, setting apm0 to disabled didn't solve it. > I had to remove the apm0 line completely from my kernel config to get rid > of the error. > > After this (a few hours later), all worked fine, did a complete > build/install of ports XFree-4 > and Gnome-1.4 without any problems. > > But i'm a bit dissapointed that fbsd gave me so much problems installing and > forcing me to disabled parts of it's functionality... > > Maybe I upgrade to current someday to make use of the new apci code. > > Anyone have the same experiences? > > Regards, > Ron. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010525114325.A4857>