Re: error in src/etc/rc.d/mountcritlocal

2008-04-29 Thread Mike Makonnen
Oliver Lehmann wrote: Hi Mike, with todays update I got version 1.12.2.4 of src/etc/rc.d/mountcritlocal for my RELENG_6 system today when I cvsuped my source. # $FreeBSD: src/etc/rc.d/mountcritlocal,v 1.12.2.4 2008/03/20 10:53:18 mtm Exp $ C src/etc/rc.d/mountcritlocal,v RELENG_6 . 2#871#110#1

Re: Packet-corruption with re(4)

2008-04-29 Thread Sean C. Farley
On Tue, 29 Apr 2008, Jeremy Chadwick wrote: I'd recommend staying away from Realtek NICs. Pick up an Intel Pro/1000 GT or PT. Realtek has a well-known history of issues. Just a note about the Intel Pro/1000 GT: it is on-sale[1] at NewEgg with free shipping. I just bought my third one to re

Re: freebsd 7 with sata drives

2008-04-29 Thread Brian
The board in question is an Asus M3A78-EMH HDMI. I have tried the instructions for a safe kernel compile in /usr/src/updating also. Even after that, the kernel starts to load, but the root partition cant be found, and I am left at a mountroot> prompt. If I go ufs:ad5s1a, that fails as well.

Re: Packet-corruption with re(4)

2008-04-29 Thread Jeremy Chadwick
On Tue, Apr 29, 2008 at 10:58:55PM +0200, Torfinn Ingolfsen wrote: > On Tue, 29 Apr 2008 05:08:34 -0700 > Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > > > I'd recommend staying away from Realtek NICs. Pick up an Intel > > Pro/1000 GT or PT. Realtek has a well-known history of issues. > > I hear

Re: Packet-corruption with re(4)

2008-04-29 Thread Torfinn Ingolfsen
On Tue, 29 Apr 2008 05:08:34 -0700 Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > I'd recommend staying away from Realtek NICs. Pick up an Intel > Pro/1000 GT or PT. Realtek has a well-known history of issues. I hear that story very often, so often that I almost think it's a fairy tale. :-) Most

Re: Packet-corruption with re(4)

2008-04-29 Thread Torfinn Ingolfsen
On Tue, 29 Apr 2008 13:18:10 +0200 Peter Ankerstål <[EMAIL PROTECTED]> wrote: > Hi, > > Im using a built in re(4) card and it seems like its causes data- > corruption as soon as it gets some load (or after a few hours online) IIRC, this is a known issue with if_re and 7.0-R. It is fixed in 7.0-

Re: bluetooth keyboards and /etc/rc.d/bluetooth

2008-04-29 Thread Torfinn Ingolfsen
On Tue, 29 Apr 2008 20:42:50 +0200 martinko <[EMAIL PROTECTED]> wrote: > I think you need to load vkbd (though I'm not 100% sure now). It can Yes, vkbd(4) is needed. See the man page for bthidd(8). -- Regards, Torfinn Ingolfsen ___ freebsd-stable@fre

Re: bluetooth keyboards and /etc/rc.d/bluetooth

2008-04-29 Thread martinko
Kevin Oberman wrote: From: "Ronald Klop" <[EMAIL PROTECTED]> Date: Mon, 28 Apr 2008 10:33:28 +0200 Sender: [EMAIL PROTECTED] On Sun, 27 Apr 2008 23:52:52 +0200, Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote: Hello, Today I set up a bluetooth keyboard on a FreeBSD machine for the first time.

Re: Packet-corruption with re(4)

2008-04-29 Thread Jeremy Chadwick
On Tue, Apr 29, 2008 at 02:30:27PM +0200, Peter Ankerstål wrote: > > On Apr 29, 2008, at 2:08 PM, Jeremy Chadwick wrote: >>> >> >> tcpdump reporting "bad cksum" can occur due to TX/RX checksum >> offloading. Do you not see this message normally, but only when the >> problem begins? >> >> Have you

Re: Packet-corruption with re(4)

2008-04-29 Thread Peter Ankerstål
On Apr 29, 2008, at 2:08 PM, Jeremy Chadwick wrote: tcpdump reporting "bad cksum" can occur due to TX/RX checksum offloading. Do you not see this message normally, but only when the problem begins? Have you tried turning off TX/RX offloading to see if the erroneous behaviour goes away? Hav

Re: Packet-corruption with re(4)

2008-04-29 Thread Jeremy Chadwick
On Tue, Apr 29, 2008 at 01:18:10PM +0200, Peter Ankerstål wrote: > Im using a built in re(4) card and it seems like its causes data-corruption > as soon as it gets some load (or after a few hours online) > > The machine is running FreeBSD 7.0R: > > FreeBSD ninja 7.0-RELEASE FreeBSD 7.0-RELEASE #0:

Packet-corruption with re(4)

2008-04-29 Thread Peter Ankerstål
Hi, Im using a built in re(4) card and it seems like its causes data- corruption as soon as it gets some load (or after a few hours online) The machine is running FreeBSD 7.0R: FreeBSD ninja 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Wed Apr 16 22:49:15 CEST 2008 [EMAIL PROTECTED]:/usr/obj/us