Well, I've been watching everyone argue about the value of interrupt
coalescing in the net drivers, so I decided to port terry's patch to 4.4 &
-current to see what the results are. The patch included applies cleanly
to 4.4's if_dc, and will apply to -current with a one line change.
Whitespace i
For the first time in as long as I can remember (several years at
least), I've backed my workstation at home down to -STABLE. The three
problems I'm having currently are just too much for me to put up with,
and at this point in my life I need something that works. Yes... I know
that this i
drwxr-xr-x 20 root wheel 1024 Oct 11 22:17 5.0-20011011-CURRENT
Come 'n get it. No warrantees stated or implied as to how far these
bits get you after you transfer them, of course. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
When was the last tragedy you were involved in? The next one could be the last!!
REMEMBER, 80% of sinister fatalities occur due to toxic gases and smoke inhalation.
OUR PRODUCT CAN SAVE YOUR LIFE OR THE LIFE OF A LOVED ONE
ORDER NOW ! Click HERE for more info :
http://www.life-protect.com/partn
I've posted (old version of) this patch before at cvs-committers, but
[EMAIL PROTECTED] is more appropriate list so I post a new version
of patch here.
***
Attached below is a patch to make more kernel-modularize installation
flopppies.
- Why need this?
Because we have very few space
Hi,
I was wondering if anybody has any suggestions about why this might
be happening in -current:
Booting [/boot/kernel/kernel]...
/boot/kernel/acpi.ko text=0x32f34 data=0xf9c+0x1028 syms=[0x4+0x49c0+0x4+0x61a]-
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 198
When was the last tragedy you were involved in? The next one could be the last!!
REMEMBER, 80% of sinister fatalities occur due to toxic gases and smoke inhalation.
OUR PRODUCT CAN SAVE YOUR LIFE OR THE LIFE OF A LOVED ONE
ORDER NOW ! Click HERE for more info :
http://www.life-protect.com/partn
>
> After the last cvsup (changes from 29 of september) i've got dead
> dc (21143 based NIC).
You have to tell us _exactly_ what card you have. Find the manufacturer
and model info. Look on the box the card came in. Look at the card itself.
Show us the output from pciconf -l so we can see the PC
In article
[EMAIL PROTECTED]>
you write:
>
>After the last cvsup (changes from 29 of september) i've got dead
>dc (21143 based NIC). LEDs are dead, but card is successfully probed and
>attached, so i have device but can't use it. What should i send to help
>investigate this problem?
>
>$FreeBSD:
From: "Brandon D. Valentine" <[EMAIL PROTECTED]>
> On Thu, 11 Oct 2001, Benjamin Close wrote:
> > I've now been using the FreeBSD winmodem driver (Available at:
> >http://www.geocities.com/wtnbkysh/) under -current for a few weeks now
> >and haven't noticed a single glitch. Whilst I know this is a
The latest installworld seems to not be happy with me in NIS-
I get:
Oct 11 09:47:39 quarm sshd[8160]: PAM pam_set_item: NULL pam handle passed
Oct 11 09:47:39 quarm sshd[8160]: PAM pam_set_item: NULL pam handle passed
Oct 11 09:47:39 quarm sshd[8160]: PAM pam_set_item: NULL pam handle passed
On 11-Oct-01 Gunnar Flygt wrote:
> cvsuped two days ago, and made buildworld today, which went OK. Tried
> make kernel (aka GENERIC). It fails at nfsclient code:
Already fixed two days ago.
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~joh
cvsuped two days ago, and made buildworld today, which went OK. Tried
make kernel (aka GENERIC). It fails at nfsclient code:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -W
missing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -an
si -g -nost
Hi,
Are Iomega Peerless USB drives supported in CURRENT?
I assume they can be recognised as a generic SCSI-over-USB drive, but want
to be sure they work OK.
Thanks,
Konstantin.
--
* * Konstantin Chuguev Francis House
* * Application Engineer 1
After the last cvsup (changes from 29 of september) i've got dead
dc (21143 based NIC). LEDs are dead, but card is successfully probed and
attached, so i have device but can't use it. What should i send to help
investigate this problem?
This is strings from working kernel:
$FreeBSD: src/sys/dev
"Kenneth D. Merry" wrote:
> If the receive ring for that packet size is full, it will hold off on
> DMAs. If all receive rings are full, there's no reason to send more
> interrupts.
I think that this does nothing, in the FreeBSD case, since the
data from the card will generally be drained much f
16 matches
Mail list logo
