nick thompson --> port-sparc64 (2007-02-08 21:22:18 -0600):
> I am wondering, how well supported is the blade 100?

Some weeks ago I installed -current on a SunBlade 100 and noticed
[1]problems related to more recent OBP versions; downgrading to 4.5.9
worked around these problems. But then I noticed data corruption while
running a GENERIC kernel - and found the following in the GENERIC
config file:

## Disable UDMA 4 which causes data corruption on the Acer Labs
## chipset on Sun Blade 100 and Netra X1 machines.
wd*     at atabus? drive ? flags 0x0000

Hmm, so this comment seems to be a demand note rather than a description
of the following device line... BTW: this [2]used to be `flags 0x0a00',
but was [3]reset [4]unintentionally. Shouldn't this be switched back?

However, IIRC downgrading to UDMA3 did not fix the problems either,
but I didn't even try to track this down because I was about to switch
to a Promise IDE controller. Until I noticed that pdcide(4) is not
supposed to work with NetBSD/sparc64 (see the man page)...


Regards, Jukka

[1] http://mail-index.netbsd.org/port-sparc64/2007/01/01/0000.html
[2] http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/sparc64/conf/GENERIC32.diff?r1=1.20&r2=1.21
[3] http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/sparc64/conf/GENERIC32.diff?r1=1.70&r2=1.71
[4] http://mail-index.netbsd.org/port-sparc64/2004/12/13/0007.html

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~