On Mon, Jan 21, 2002 at 07:28:02PM -0800, Linux Rocks ! wrote: > > wd0: soft error (corrected) is the message I see (dmesg)
One of my machines does this: wd0a: device fault reading fsbn 16 of 16-31 (wd0 bn 79; cn 0 tn 1 sn 16), retrying wd0: transfer error, downgrading to PIO mode 3 wd0(pciide0:0:0): using PIO mode 3 cd0(pciide0:0:1): using PIO mode 0, DMA mode 1 wd0a: device fault reading fsbn 16 of 16-31 (wd0 bn 79; cn 0 tn 1 sn 16), retrying wd0: soft error (corrected) It doesn't cause any problems though. Basically it means the kernel wants to use something "better" than PIO mode 3, but that's the "best" the disk can do reliably. > the network issue is still not resolved... my > guess is some bit of info needed was on a bad sector or something... when I > run sh /etc/netstart I get the messge > writing to routing socket: File exists This is expected. It's doing all the network, so loopback is being rewritten also, hence, the message. > is the network device driver loaded? how would I know? what file exists? > should it? what should I do about this file? OpenBSD uses one big kernel that has all the drivers statically compiled. You can check dmesg to see if the hardware was detected and a driver assigned to it. Try "grep ^ne /var/run/dmesg.boot". /var/run/dmesg.boot is a copy of `dmesg` from boot time, which is handy because many "messages" can make the dmesg command useless. -- <[EMAIL PROTECTED]>
