Re: Memory requirements between releases

2005-08-13 Thread Peter Jeremy
On Fri, 2005-Aug-12 21:38:43 +0100, Chris wrote: 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

Re: cvs commit: src/sys/net80211 ieee80211.c ieee80211_input.c ieee80211_ioctl.c ieee80211_node.c ieee80211_node.h ieee80211_output.c ieee80211_proto.c ieee80211_proto.h ieee80211_var.h src/sys/dev/ath if_ath.c src/sys/dev/ipw if_ipw.c ...

2005-08-13 Thread Daniel O'Connor
On Saturday 13 August 2005 14:27, Sam Leffler wrote: [Not sure why you're sending this to cvs-all] Oops, freebsd-stable@ is probably better. Daniel O'Connor wrote: ipw is still broken [for me].. Sorry but that wasn't the question. I don't believe the commit you are responding to changed

Re: Memory requirements between releases

2005-08-13 Thread Michael Nottebrock
On Saturday, 13. August 2005 10:32, Peter Jeremy wrote: 24MB should be adequate as a SOHO wireless router/NAT box but doing compilations will stress it significantly (as you've noticed). Probably stating the obvious here, but that's where those fine binary packages FreeBSD builds from ports

Re: Too short ethernet frame...

2005-08-13 Thread Iva Hesy
Just now, I add date=2005.07.31.03.00.00 to my src cvsup sup-file and make kernel, too short ethernet frames are still sniffered. But when I add date=2005.07.22.03.00.00 to sup-file and cvsup and make kernel, the damn datagrams gone!!! ___

Re: cvs commit: src/sys/net80211 ieee80211.c ieee80211_input.c ieee80211_ioctl.c ieee80211_node.c ieee80211_node.h ieee80211_output.c ieee80211_proto.c ieee80211_proto.h ieee80211_var.h src/sys/dev/ath if_ath.c src/sys/dev/ipw if_ipw.c ...

2005-08-13 Thread Sam Leffler
Daniel O'Connor wrote: On Saturday 13 August 2005 14:27, Sam Leffler wrote: [Not sure why you're sending this to cvs-all] Oops, freebsd-stable@ is probably better. Not really, but whatever. Daniel O'Connor wrote: ipw is still broken [for me].. Sorry but that wasn't the question.

FreeBSD 5.4 pagedaemon abnormal loading

2005-08-13 Thread Weicheng Pan
Hi all: I have encountered a strange situation which my host went out of countrol out of peak time. top -S shows that CPU Sys. is over 90 %, and pagedaemon has very high loading, then the server died. Would anyone give me some advices to solve this queer problem? Thanks and have a nice

IRQ conflict between twa0 and skc0

2005-08-13 Thread Brandon Fosdick
So I'm having yet another problem with my AMD64x2/nforce4 system. Of the two builtin NICs 5.4-S is only recognizing the marvell gigabit chip, which wasn't a problem until I added a 3ware 9500S-12. With the 3ware card in the network doesn't work, take it out and it works. From the dmesg bits

Re: cvs commit: src/sys/net80211 ieee80211.c ieee80211_input.c ieee80211_ioctl.c ieee80211_node.c ieee80211_node.h ieee80211_output.c ieee80211_proto.c ieee80211_proto.h ieee80211_var.h src/sys/dev/ath if_ath.c src/sys/dev/ipw if_ipw.c ...

2005-08-13 Thread dmp
Quoting Sam Leffler [EMAIL PROTECTED]: The ipw and iwi drivers (at least) have never worked right so far as I can tell. At one point I tried the iwi driver and it kinda worked but failed in many common scenarios and in general was very fragile. I no longer have the facilities to even test

Re: IRQ conflict between twa0 and skc0

2005-08-13 Thread Mike Jakubik
On Sat, August 13, 2005 8:02 pm, Brandon Fosdick said: So I'm having yet another problem with my AMD64x2/nforce4 system. Of the two builtin NICs 5.4-S is only recognizing the marvell gigabit chip, which wasn't a problem until I added a 3ware 9500S-12. With the 3ware card in the network doesn't

Re: IRQ conflict between twa0 and skc0

2005-08-13 Thread Brandon Fosdick
Mike Jakubik wrote: The easiest thing would probably be to disable the onboard sk card, and put in an em (intel gigabit card). The marvell chipset and driver is known to be problematic. I had thought of that, but the motherboard only has 2 non-express PCI slots and they're both currently

Re: IRQ conflict between twa0 and skc0

2005-08-13 Thread Mike Jakubik
On Sun, August 14, 2005 12:47 am, Brandon Fosdick said: I had thought of that, but the motherboard only has 2 non-express PCI slots and they're both currently filled by the video card and the raid card. I could take the video card out, but then I wouldn't be able to see what I was doing. You

Re: IRQ conflict between twa0 and skc0

2005-08-13 Thread Mike Jakubik
On Sun, August 14, 2005 12:47 am, Brandon Fosdick said: I had thought of that, but the motherboard only has 2 non-express PCI slots and they're both currently filled by the video card and the raid card. I could take the video card out, but then I wouldn't be able to see what I was doing.

RE: IRQ conflict between twa0 and skc0

2005-08-13 Thread Darren Pilgrim
From: Brandon Fosdick Mike Jakubik wrote: The easiest thing would probably be to disable the onboard sk card, and put in an em (intel gigabit card). The marvell chipset and driver is known to be problematic. I had thought of that, but the motherboard only has 2 non-express PCI slots

Re: 4.11 to RELENG_6

2005-08-13 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Oliver Fromme [EMAIL PROTECTED] writes: : Björn König [EMAIL PROTECTED] wrote: : Randy Bush wrote: :any peculiarities/clues for upgrading an antique from 4.11 to :RELENG_6 beyond the To upgrade in-place from 5.x-stable to :current in

Re: IRQ conflict between twa0 and skc0

2005-08-13 Thread Brandon Fosdick
Mike Jakubik wrote: Forgot to mention. You can always buy a cheap pciE video card :) You're a big help :) I was fiddling and I noticed something odd. Previously, the ESCD screen at boot showed the raid controller and network controller both at IRQ 5. The dmesg I sent before showed both at

Re: Memory requirements between releases

2005-08-13 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Chris [EMAIL PROTECTED] writes: : 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 memory requirement really jump that much or is something : different being

Re: IRQ conflict between twa0 and skc0

2005-08-13 Thread Brandon Fosdick
Darren Pilgrim wrote: Try switching slots with the RAID and video cards. It's silly, but then so is PCI interrupt routing. Unbelievable. Who ever wrote the PCI spec should have been shot. I switched the cards and now the network card is sharing an interrupt with the video card, but neither