Re: Installing 5.4-S on nvidia raid1?

2005-08-12 Thread Vladimir Botka
Hello, I am afraid the nvidia on-board raid controller is not supported. Take a look at hardware notes: http://www.freebsd.org/releases/5.4R/hardware-i386.html You will have to use either supported raid controller or use software raid: http://www.freebsd.org/cgi/man.cgi?query=vinumsektion=8

Crash on Alpha - 4.11-STABLE

2005-08-12 Thread Rob B
Hi there, This is the second time I've seen this crash in the past three weeks. I'm not sure what the root cause either. This box is just a home server with a single NFS exported directory and one NFS client. It is also a caching http proxy server for my home LAN (three machines). The

Why I can't disable ACPI?

2005-08-12 Thread Iva Hesy
I'm running a RELENG_6 (Beta2) as my desktop now. When I add hint.acpi.0.disabled=1 to /boot/loader.conf and reboot, system can't find my ATA disks and can't boot sucessfully... ___ freebsd-stable@freebsd.org mailing list

Too short ethernet frame...

2005-08-12 Thread Iva Hesy
OS: RELENG_6 (Beta2) NIC: vr0: VIA VT6105 Rhine III 10/100BaseTX # tcpdump -penv -i vr0 less 32 16:15:42.512701 [|ether] 16:15:44.523102 [|ether] 16:15:46.522495 [|ether] 16:16:00.540387 [|ether] 16:16:02.541834 [|ether] 16:16:08.550068 [|ether] 16:16:10.570483 [|ether] # snort -pev -i vr0 less 32

[RELENG_6] idle thread statistics not correct?

2005-08-12 Thread Xin LI
Hi, all, I got into a strange issue on a remote box I just upgraded to RELENG_6. [EMAIL PROTECTED] ~ ps aux | grep idle | grep -v grep root 11 92.5 0.0 0 8 ?? RL Thu03AM 0:00.00 [idle: cpu3] root 13 92.5 0.0 0 8 ?? RL Thu03AM 2293:59.13 [idle: cpu1] root

rc-ng problem with [procname] (e.g. kernel threaded procs)

2005-08-12 Thread Andy Hilker
Hi, i think I have found a problem with rc-ng scripts and procnames including brackets (e.g. kernel threaded, like mysqld). Brackets [] are ignored, process will not be found and is regarded as not running. This breaks stop+status functions of rcng. The following patch allows brackets in

Re: [RELENG_6] idle thread statistics not correct?

2005-08-12 Thread John Baldwin
On Friday 12 August 2005 05:38 am, Xin LI wrote: Hi, all, I got into a strange issue on a remote box I just upgraded to RELENG_6. [EMAIL PROTECTED] ~ ps aux | grep idle | grep -v grep root 11 92.5 0.0 0 8 ?? RL Thu03AM 0:00.00 [idle: cpu3] root 13 92.5 0.0 0

Re: [RELENG_6] idle thread statistics not correct?

2005-08-12 Thread Michael Nottebrock
On Friday, 12. August 2005 15:43, John Baldwin wrote: [ Grrr, stupid kmail smart quoting always screws up formatted output, wish I could turn it off ] Actually you can: Settings/Configure Kmail/Composer, on the General tab. I guess what you really want to turn off (sometimes) is Word Wrap at

Re: [RELENG_6] idle thread statistics not correct?

2005-08-12 Thread John Baldwin
On Friday 12 August 2005 10:26 am, Michael Nottebrock wrote: On Friday, 12. August 2005 15:43, John Baldwin wrote: [ Grrr, stupid kmail smart quoting always screws up formatted output, wish I could turn it off ] Actually you can: Settings/Configure Kmail/Composer, on the General tab. I

Re: Installing 5.4-S on nvidia raid1?

2005-08-12 Thread Christian Brueffer
On Thu, Aug 11, 2005 at 04:45:31PM -0700, Brandon Fosdick wrote: I have a DFI Lanparty nf4 Ultra-D with two 80GB drives configured as a raid1 array. The bios lists the array as scsi-0 and claims that its healthy. When I boot from the disc1 cd and try to do the usual install the only device

Re: Too short ethernet frame...

2005-08-12 Thread Brooks Davis
On Fri, Aug 12, 2005 at 02:37:04AM -0700, Iva Hesy wrote: OS: RELENG_6 (Beta2) NIC: vr0: VIA VT6105 Rhine III 10/100BaseTX # tcpdump -penv -i vr0 less 32 16:15:42.512701 [|ether] 16:15:44.523102 [|ether] 16:15:46.522495 [|ether] 16:16:00.540387 [|ether] 16:16:02.541834 [|ether]

Re: Installing 5.4-S on nvidia raid1?

2005-08-12 Thread Brandon Fosdick
Christian Brueffer wrote: It doesn't work because the ataraid code in 5.4 doesn't understand the NVIDIA MediaShield metadata format. It is supported on HEAD and the RELENG_6 branch that will result in FreeBSD 6.0-RELEASE. Take a look at the ataraid(4) manpage in HEAD and RELENG_6 for more

Re: Installing 5.4-S on nvidia raid1?

2005-08-12 Thread Christian Brueffer
On Fri, Aug 12, 2005 at 11:38:23AM -0700, Brandon Fosdick wrote: Christian Brueffer wrote: It doesn't work because the ataraid code in 5.4 doesn't understand the NVIDIA MediaShield metadata format. It is supported on HEAD and the RELENG_6 branch that will result in FreeBSD 6.0-RELEASE.

Memory requirements between releases

2005-08-12 Thread Chris
Hi The installation notes for 4.11 say, referring to i386 platform ...after installation, FreeBSD itself can be run in 4-8MB of RAM with a pared-down kernel The installation notes for 5.4 and 6 (the floppies README.TXT) say FreeBSD for the i386 requires ...at least 24 MB of RAM. Did the

Re: Memory requirements between releases

2005-08-12 Thread Chris
Chris wrote: Hi The installation notes for 4.11 say, referring to i386 platform ...after installation, FreeBSD itself can be run in 4-8MB of RAM with a pared-down kernel The installation notes for 5.4 and 6 (the floppies README.TXT) say FreeBSD for the i386 requires ...at least 24 MB of

Re: Memory requirements between releases

2005-08-12 Thread Arno J. Klaassen
hello, The installation notes for 5.4 and 6 (the floppies README.TXT) say FreeBSD for the i386 requires ...at least 24 MB of RAM. [ .. ] I have on old tosh 110CT laptop with 24mb memory I want to set up as a wireless router/NAT box but would prefer to use 6 or 5.4. I've run 5.X for about

Re: Memory requirements between releases

2005-08-12 Thread Kris Kennaway
On Fri, Aug 12, 2005 at 09:38:43PM +0100, Chris wrote: Hi The installation notes for 4.11 say, referring to i386 platform ...after installation, FreeBSD itself can be run in 4-8MB of RAM with a pared-down kernel The installation notes for 5.4 and 6 (the floppies README.TXT) say FreeBSD

Re: Too short ethernet frame...

2005-08-12 Thread Iva Hesy
On 8/12/05, Brooks Davis [EMAIL PROTECTED] wrote: Most likely, your cabling, duplex configuraion, nic, switch are misconfigured and a high traffic ap like rdesktop is pushing them over the edge. I'd check the duplex settings on each end and try another cable first. Then try a different nic