Attempting to install 5.2 on two somewhat different i386 machines. Both 
unusable due to critical driver failures, so that built-in bug reporting 
mechanism can not be used. Both machines have recently tested to work correctly 
with freebsd, dragonflybsd, slackware linux, windows, and msdos.

Machine 1: Dual P3, VIA chipset.

(Bug#1)
Cd installer kernel boots, yet on subsequent post-install reboots clcs(4) 
driver detects Turtle Beach Santa Cruz but prints many boottime errors of the 
format
"clcs0: AC97 write fail (DCV!=0) for add=0x??"
with add equalling random hex byte values. The kernel then locks up when trying 
to mount sd0a. The only workaround found was to physically remove the 
soundcard. Then everything boots normally.

(Bug#2)
Asix ax88178 usb ethernet, driver axe(4) appears to load correctly, with no 
error messages, but in fact is completely unable to communicate. This was a 
known issue with (older) Asix linux drivers, which Asix recently corrected in 
their own linux driver release.

Machine 2: Athlon64, Nforce3 chipset, running 32bit installer anyways.

(Bug#1)
Drive sd0 on narrow channel of Symbios 53c896, and set as such in Symbios 
nvram. Cd installer kernel detects 53c896 as sym0 and correctly detects the 
drive, but can not later access the drive at all due to repeatedly attempting 
to set the drive to 16-bit scsi-wide and then failing with bogus parity errors 
when it can't because it's on the narrow channel. Therefore no installation 
possible.

(Bug#2)
Kernel detects 3cr990 ethernet card as txp0, but believes itself unable to 
download the card's firmware to it. End result, card not available for 
configuration. Strange, considering that TDR was the original author of the 
driver, and I would have guessed it would have been the last piece of hardware 
to have a problem with Openbsd.

-- 

Reply via email to