MAKEDEV warning with sysinstall ?

2000-05-08 Thread Erik de Zeeuw


I installed FreeBSD 5.0-2506-CURRENT on an AMD K6-2, 64Mb, 4Gb, and
when I first launch /stand/sysinstall after the system has start, the
following message appears :

... /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of
block devices

I searched the list archives and find some informations about this, but
nothing that helps me understand why I get this message.

The only time it happens is when I use sysinstall for the first time
after the PC has start. If I'm using sysinstall again without prior
reboot, there's no such message. But if I reboot and use sysinstall
again, the message shows up again.

I ran MAKEDEV all, but the message still appear. The messages I found
about this on the archives says to do a 'ls -l /dev | grep ^b', and
to remake all devices listed, but there's no device listed when I'm
doing the 'ls -l /dev | grep ^b'.

Any idea about what could cause this message to come up ?


Thanks,
Erik de Zeeuw


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



HighPoint UDMA66 ICRC READ ERROR

2000-04-03 Thread Erik de Zeeuw

Hi to all the -current people,

I'm running FreeBSD on an Abit BP6 motherboard, which
uses the HighPoint UDMA 66 controller. This is a SMP
machine, with the BP6 running two Celeron 500Mhz.

The hard drive is a Western Digital 7200rpm/DMA66, plugged
in the HPT66 controller. Here's what dmesg tells me :

...
atapci1: HighPoint HPT366 ATA66 controller port \
0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 \
irq 11 at device 19.0 on pci0
ata2: at 0xb000 on atapci1
atapci2: HighPoint HPT366 ATA66 controller port \
0xc400-0xc4ff,0xc000-0xc003,0xbc00-0xbc07 \
irq 11 at device 19.1 on pci0
...
ad4: 19574MB WDC WD205BA [39770/16/63] at ata2-master using UDMA66
...

I'm pretty satisfied with this, especially with the great
support for the DMA66 controller.

The only thing is I sometimes get messages like this :

gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39566319 retrying
gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39627167 retrying
gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39628463 retrying

If I'm not wrong, this has already been discussed a
while ago, that such messages could show up using a
-CURRENT 4.0, and that there was nothing to worry about.

As I upgraded to 4.0-RELEASE since, I just wanted to
make sure that there's still nothing to worry about
or if this could come from a hard disk problem.

Note that although getting such messages, everything
seems to work great, and all the disk operations which
makes the messages occurs seems to be done
perfectly ( say I'm making a huge .tar.gz, which
makes the messages show up, the .tar.gz is ok,
not event the shadow of the tail of a CRC error
in it ).

I know this could have been sent to -questions, but
I remind this has been discussed here, and I think the
people in charge for that kind of obscure behavior
might be found around -current :)

Anyway, thanks for the great work, FreeBSD really
is a great OS.

Erik


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message