stable-digest V5 #784
owner-freebsd...@freebsd.org
stable-digest Tuesday, February 4 2003 Volume 05 : Number 784
In this issue:
Re: "ping: sendto: No buffer space available"
Re: "ping: sendto: No buffer space available"
Re: recommendations on the newfs of a 1.0TB fs...
Re: "ping: sendto: No buffer space available"
Re: "ping: sendto: No buffer space available"
Re: "ping: sendto: No buffer space available"
Re: "ping: sendto: No buffer space available"
Re: "ping: sendto: No buffer space available"
Re: "ping: sendto: No buffer space available"
Re: "ping: sendto: No buffer space available"
Re: "ping: sendto: No buffer space available"
Re: "ping: sendto: No buffer space available"
Re: recommendations on the newfs of a 1.0TB fs...
Re: recommendations on the newfs of a 1.0TB fs...
Re: recommendations on the newfs of a 1.0TB fs...
Re: "ping: sendto: No buffer space available"
bin/45754: vnconfig(8) fails to return correct exit status
Re: "ping: sendto: No buffer space available"
Re: HEADS UP: OpenSSH 3.5p1
HP/Compaq DL580 G2
Re: HP/Compaq DL580 G2
Re: HP/Compaq DL580 G2
Re: HP/Compaq DL580 G2
Re: "ping: sendto: No buffer space available"
Re: HP/Compaq DL580 G2
Re: HP/Compaq DL580 G2
Re: HP/Compaq DL580 G2
Re: problem with fxp interface in promisc mode
Re: recommendations on the newfs of a 1.0TB fs...
Re: filesystem disappeared following 4.2 -> 4.7 upgrade
IBM x335 Broadcom BCM5703 NICs not detected by 4.7-R
Re: IBM x335 Broadcom BCM5703 NICs not detected by 4.7-R
FreeBSD set up on Compaq Proliant 5500
Re: FreeBSD set up on Compaq Proliant 5500
[none]
----------------------------------------------------------------------
Date: Mon, 03 Feb 2003 17:06:13 -0500
From: Bill Moran <wmo...@potentialtech.com>
Subject: Re: "ping: sendto: No buffer space available"
Peter Radcliffe wrote:
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
>
> I see this occasionally on my -stable box and havn't had a good
> explanation of why and what buffer. Searching isn't turning up
> anything useful.
>
> Is there something I can tweak to make this less likely ?
What kind of interface are you pinging through?
I've seen this on a VPN where the VPN was running out of entropy
(from /dev/random). I think it was a tun# interface.
Could also be an MBUF thing. Does netstat -m say anything scary?
- --
Bill Moran
Potential Technologies
http://www.potentialtech.com
------------------------------
Date: Mon, 03 Feb 2003 16:10:29 -0600
From: Larry Rosenman <l...@lerctr.org>
Subject: Re: "ping: sendto: No buffer space available"
- --On Monday, February 03, 2003 17:06:13 -0500 Bill Moran
<wmo...@potentialtech.com> wrote:
> Peter Radcliffe wrote:
>> ping: sendto: No buffer space available
>> ping: sendto: No buffer space available
>>
>> I see this occasionally on my -stable box and havn't had a good
>> explanation of why and what buffer. Searching isn't turning up
>> anything useful.
>>
>> Is there something I can tweak to make this less likely ?
>
> What kind of interface are you pinging through?
>
> I've seen this on a VPN where the VPN was running out of entropy
> (from /dev/random). I think it was a tun# interface.
>
> Could also be an MBUF thing. Does netstat -m say anything scary?
I've seen it with NMAP over my WI0 card (Linksys V3).
MBUF's didn't show anything useful, unfortunately.
LER
>
> --
> Bill Moran
> Potential Technologies
> http://www.potentialtech.com
>
>
> To Unsubscribe: send mail to majo...@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
- --
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: l...@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
------------------------------
Date: Mon, 03 Feb 2003 17:11:56 -0500
From: Bill Moran <wmo...@potentialtech.com>
Subject: Re: recommendations on the newfs of a 1.0TB fs...
Dag-Erling Smorgrav wrote:
> Bill Moran <wmo...@potentialtech.com> writes:
>
>>Do the math. df -hi will tell you the number of bytes and inodes used.
>>Do a simple bytes/inodes and add about 10% just to be sure.
>>That should take care of you.
>
> You should *subtract* to be sure. Specify to newfs an average file
> size which is slightly lower than the measured average file size, so
> it creates slightly more inodes than you need.
Yes ... what he said ...
(This may explain why I can never balance my checkbook ...)
- --
Bill Moran
Potential Technologies
http://www.potentialtech.com
------------------------------
Date: Mon, 3 Feb 2003 17:30:50 -0500
From: Peter Radcliffe <p...@pir.net>
Subject: Re: "ping: sendto: No buffer space available"
Bill Moran <wmo...@potentialtech.com> probably said:
> What kind of interface are you pinging through?
I've seen it on various interfaces, in this case a Cisco 350 wireless
card.
> I've seen this on a VPN where the VPN was running out of entropy
> (from /dev/random). I think it was a tun# interface.
I have ipf enabled on that interface, no VPN and nothing that should
require entropy.
> Could also be an MBUF thing. Does netstat -m say anything scary?
I'll take a look when I can provoke it again.
P.
- --
pir pir...@pir.net pir...@net.tufts.edu
------------------------------
Date: Tue, 04 Feb 2003 10:03:12 +1100
From: Gregory Bond <g...@itga.com.au>
Subject: Re: "ping: sendto: No buffer space available"
> ping: sendto: No buffer space available
I've seen odd things like this when ipfw rules forbid the ping packets.
------------------------------
Date: Mon, 3 Feb 2003 18:05:03 -0500
From: Peter Radcliffe <p...@pir.net>
Subject: Re: "ping: sendto: No buffer space available"
Gregory Bond <g...@itga.com.au> probably said:
> I've seen odd things like this when ipfw rules forbid the ping packets.
no ipfw, and ipmon says the packets are not being blocked (they get
through most of the time, too).
P.
- --
pir pir...@pir.net pir...@net.tufts.edu
------------------------------
Date: Tue, 4 Feb 2003 00:35:54 +0100 (CET)
From: Mats Larsson <myr...@marvin.sko.mh.se>
Subject: Re: "ping: sendto: No buffer space available"
On a 4.4 box I got this error using some old ep(4) card, a card switch
Solved my problems back then. If you have the possible then test with a
different card.
// Mats
On Mon, 3 Feb 2003, Peter Radcliffe wrote:
> ping: sendto: No buffer space available
> ping: sendto: No buffer space available
>
> I see this occasionally on my -stable box and havn't had a good
> explanation of why and what buffer. Searching isn't turning up
> anything useful.
>
> Is there something I can tweak to make this less likely ?
>
> P.
>
> --
> pir pir...@pir.net pir...@net.tufts.edu
>
>
> To Unsubscribe: send mail to majo...@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
------------------------------
Date: Tue, 4 Feb 2003 10:47:39 +1100 (EST)
From: Peter Hoskin <pet...@criten.org>
Subject: Re: "ping: sendto: No buffer space available"
I have this same issue on a PPTP interface invoked by MPD. I haven't been
able to work it out, though it doesn't appear to be causing any
problems... just error messages. *shrug*
Regards,
Peter Hoskin
On Tue, 4 Feb 2003, Mats Larsson wrote:
> Date: Tue, 4 Feb 2003 00:35:54 +0100 (CET)
> From: Mats Larsson <myr...@marvin.sko.mh.se>
> To: sta...@FreeBSD.ORG
> Subject: Re: "ping: sendto: No buffer space available"
>
>
> On a 4.4 box I got this error using some old ep(4) card, a card switch
> Solved my problems back then. If you have the possible then test with a
> different card.
>
> // Mats
>
>
>
> On Mon, 3 Feb 2003, Peter Radcliffe wrote:
>
> > ping: sendto: No buffer space available
> > ping: sendto: No buffer space available
> >
> > I see this occasionally on my -stable box and havn't had a good
> > explanation of why and what buffer. Searching isn't turning up
> > anything useful.
> >
> > Is there something I can tweak to make this less likely ?
> >
> > P.
> >
> > --
> > pir pir...@pir.net pir...@net.tufts.edu
> >
> >
> > To Unsubscribe: send mail to majo...@FreeBSD.org
> > with "unsubscribe freebsd-stable" in the body of the message
> >
>
> To Unsubscribe: send mail to majo...@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
------------------------------
Date: Mon, 3 Feb 2003 19:01:08 -0500
From: Peter Radcliffe <p...@pir.net>
Subject: Re: "ping: sendto: No buffer space available"
Mats Larsson <myr...@marvin.sko.mh.se> probably said:
> On a 4.4 box I got this error using some old ep(4) card, a card
> switch Solved my problems back then. If you have the possible then
> test with a different card.
A different card isn't much use - it's the built in wireless.
P.
- --
pir pir...@pir.net pir...@net.tufts.edu
------------------------------
Date: Mon, 3 Feb 2003 16:27:58 -0800 (PST)
From: Matthew Dillon <dil...@apollo.backplane.com>
Subject: Re: "ping: sendto: No buffer space available"
:Mats Larsson <myr...@marvin.sko.mh.se> probably said:
:> On a 4.4 box I got this error using some old ep(4) card, a card
:> switch Solved my problems back then. If you have the possible then
:> test with a different card.
:
:A different card isn't much use - it's the built in wireless.
:
:P.
:
:--
:pir pir...@pir.net pir...@net.tufts.edu
Check the queue statistics. It could be a queue overflow due to
stalls in the wireless card accepting new packets, due to
excessive collisions on a hard line.
test2:/home/dillon> sysctl -a | fgrep ip.intr_qu
net.inet.ip.intr_queue_maxlen: 50
net.inet.ip.intr_queue_drops: 0
Queue drops can also occur if you are using large TCP buffers.
-Matt
Matthew Dillon
<dil...@backplane.com>
------------------------------
Date: Mon, 3 Feb 2003 19:28:03 -0500
From: "Administrator" <ad...@govital.net>
Subject: Re: "ping: sendto: No buffer space available"
Greetings,
I have seen this occur on numerous occasions from our network as it spans the city via wireless
links. I see this most when we get interference on the same channel as someone else when they try
to use the channels we are on, causing the access points to go a little crazy. Almost in all cases
i have seen it has been from interference from other sources causing the interface to temporally
loose link for a few breif seconds or loss of the access point completely due to interference. (We
have some companies around here that don't like to play nice, and we have a very crowded radio
space.) Just thought i would throw in my two cents. :-)
On Mon, 03 Feb 2003 16:10:29 -0600, Larry Rosenman wrote
> --On Monday, February 03, 2003 17:06:13 -0500 Bill Moran
> <wmo...@potentialtech.com> wrote:
>
> > Peter Radcliffe wrote:
> >> ping: sendto: No buffer space available
> >> ping: sendto: No buffer space available
> >>
> >> I see this occasionally on my -stable box and havn't had a good
> >> explanation of why and what buffer. Searching isn't turning up
> >> anything useful.
> >>
> >> Is there something I can tweak to make this less likely ?
> >
> > What kind of interface are you pinging through?
> >
> > I've seen this on a VPN where the VPN was running out of entropy
> > (from /dev/random). I think it was a tun# interface.
> >
> > Could also be an MBUF thing. Does netstat -m say anything scary?
> I've seen it with NMAP over my WI0 card (Linksys V3).
>
> MBUF's didn't show anything useful, unfortunately.
>
> LER
>
> >
> > --
> > Bill Moran
> > Potential Technologies
> > http://www.potentialtech.com
> >
> >
> > To Unsubscribe: send mail to majo...@FreeBSD.org
> > with "unsubscribe freebsd-stable" in the body of the message
> >
>
> --
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 972-414-9812 E-Mail: l...@lerctr.org
> US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
>
> To Unsubscribe: send mail to majo...@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
- --
Chris Demers
ad...@govital.net
www.govital.net
www.govitalhosting.com
------------------------------
Date: Tue, 04 Feb 2003 02:19:41 +0100
From: Marko Zec <z...@tel.fer.hr>
Subject: Re: "ping: sendto: No buffer space available"
Matthew Dillon wrote:
> :Mats Larsson <myr...@marvin.sko.mh.se> probably said:
> :> On a 4.4 box I got this error using some old ep(4) card, a card
> :> switch Solved my problems back then. If you have the possible then
> :> test with a different card.
> :
> :A different card isn't much use - it's the built in wireless.
>
> Check the queue statistics. It could be a queue overflow due to
> stalls in the wireless card accepting new packets, due to
> excessive collisions on a hard line.
>
> test2:/home/dillon> sysctl -a | fgrep ip.intr_qu
> net.inet.ip.intr_queue_maxlen: 50
> net.inet.ip.intr_queue_drops: 0
Hmm... the issue here is with interface _outbound_ buffers, not with the IP
inbound queue. Despite ping / ip_output() claiming ENOBUFS,
net.inet.ip.intr_queue_drops will probably remain unchanged. netstat -s /
netstat -i would probably offer better diagnostics in this case.
Marko
------------------------------
Date: Mon, 3 Feb 2003 20:37:26 -0800
From: David Schultz <dsch...@uclink.Berkeley.EDU>
Subject: Re: recommendations on the newfs of a 1.0TB fs...
Thus spake Ryan Dooley <ry...@third-man.com>:
> I'm looking for recommendations on the newfs options for a 1.0TB file system
> for say /home (it's a fileserver for 52000+ accounts that range from having
> 4k to 40GB in their directories.)
>
> When I initally created the file system, the options I set are: block size of
> 65536 and a fragsize of 8192.
IIRC, block sizes greater than 16384 can cause significant buffer
cache fragmentation, which can reduce I/O performance. Moreover,
blocks that large will waste space and I/O bandwidth unless most
of the files on the disk are very large. A smaller setting,
e.g. the default, is probably more appropriate.
------------------------------
Date: Mon, 3 Feb 2003 21:06:31 -0800
From: Ryan Dooley <ry...@third-man.com>
Subject: Re: recommendations on the newfs of a 1.0TB fs...
> IIRC, block sizes greater than 16384 can cause significant buffer
> cache fragmentation, which can reduce I/O performance. Moreover,
> blocks that large will waste space and I/O bandwidth unless most
> of the files on the disk are very large. A smaller setting,
> e.g. the default, is probably more appropriate.
The default wasted too much disk space (we didn't get that 1.0TB of
usable space out of it (it was more like 893GB of total usable space.)
I do think I am wasting a bit of space. We have under 300 users with more
than 150MB of used disk. The rest of the users have between 4k and 100MB worth
of materials. Most things are web pages and images (what about 8k a page and
16k for a good png or 64k or a good jpg?)
This is kind of why I'm asking.
As for performance impacts, I've not seen too much in the way of that. This
is one of the fastest file systems I've got in production. The two other
"big" file systems are two raids formated with Linux's reiserfs which are
pretty darn fast when it comes to smaller files.
Overall, I'm really impressed by FreeBSD's stability and scaleablity. The
file server has just done more than I would have ever expected and with
over a year worth of uptime since our last, um, issue, it's gone
the distance... you definatly don't get that from Linux or any MS product.
The only thing I'd want from FreeBSD is clustering and HA (with failover
for NFS and SAMBA :-)
To the development team: Keep up the great work!
Cheers,
Ryan
------------------------------
Date: Mon, 3 Feb 2003 21:31:33 -0800
From: David Schultz <dsch...@uclink.Berkeley.EDU>
Subject: Re: recommendations on the newfs of a 1.0TB fs...
Thus spake Ryan Dooley <ry...@third-man.com>:
> > IIRC, block sizes greater than 16384 can cause significant buffer
> > cache fragmentation, which can reduce I/O performance. Moreover,
> > blocks that large will waste space and I/O bandwidth unless most
> > of the files on the disk are very large. A smaller setting,
> > e.g. the default, is probably more appropriate.
>
> The default wasted too much disk space (we didn't get that 1.0TB of
> usable space out of it (it was more like 893GB of total usable space.)
>
> I do think I am wasting a bit of space. We have under 300 users with more
> than 150MB of used disk. The rest of the users have between 4k and 100MB worth
> of materials. Most things are web pages and images (what about 8k a page and
> 16k for a good png or 64k or a good jpg?)
When you say ``the default wasted too much disk space'', do you
mean that when you formatted the filesystem, you had less space
than you expected, or do you mean that there was less space left
after you put all of your data on it? Smaller block sizes mean
more space for free block bitmaps, which are allocated at
filesystem creation time, but overall they are a win in terms of
space because of reduced internal fragmentation. Consider what
happens when you put a 10K file on the disk. Depending on whether
the filesystem is optimizing for space or time, that file will
take up 16K or 64K in your 64/16 filesystem, but substantially
less with a 16/2 FS. So unless you are expecting most of your
files to be rather large, a smaller block size may be beneficial.
Note, however, that I'm not an FFS expert; other factors such as
fragmentation may be relevant.
> As for performance impacts, I've not seen too much in the way of that. This
> is one of the fastest file systems I've got in production. The two other
> "big" file systems are two raids formated with Linux's reiserfs which are
> pretty darn fast when it comes to smaller files.
That's good to know. I remember that Matt pointed out the buffer
cache fragmentation issue some time ago, but nothing seems to have
changed in terms of buffer sizes since then. Perhaps it isn't as
big an issue as originally thought. (Does anyone know if it's
possible to tune BKVASIZE easily, and if there are any caveats?)
I would also be interested in knowing how FFS and reiserfs compare
with respect to filesystem age. Does performance drop
significantly after a year? If the research I've seen is right,
FFS performance shouldn't drop more than 20% unless the filesystem
is nearly full, and reiserfs has a cleaner...
------------------------------
Date: 04 Feb 2003 01:16:15 +0000
From: Wes Peters <w...@softweyr.com>
Subject: Re: "ping: sendto: No buffer space available"
On Tue, 2003-02-04 at 01:19, Marko Zec wrote:
> Matthew Dillon wrote:
>
> > :Mats Larsson <myr...@marvin.sko.mh.se> probably said:
> > :> On a 4.4 box I got this error using some old ep(4) card, a card
> > :> switch Solved my problems back then. If you have the possible then
> > :> test with a different card.
> > :
> > :A different card isn't much use - it's the built in wireless.
> >
> > Check the queue statistics. It could be a queue overflow due to
> > stalls in the wireless card accepting new packets, due to
> > excessive collisions on a hard line.
> >
> > test2:/home/dillon> sysctl -a | fgrep ip.intr_qu
> > net.inet.ip.intr_queue_maxlen: 50
> > net.inet.ip.intr_queue_drops: 0
>
> Hmm... the issue here is with interface _outbound_ buffers, not with the IP
> inbound queue. Despite ping / ip_output() claiming ENOBUFS,
> net.inet.ip.intr_queue_drops will probably remain unchanged. netstat -s /
> netstat -i would probably offer better diagnostics in this case.
In particular, this is the warn() on line 786 of ping.c (4.7-R):
777 i = sendto(s, (char *)outpack, cc, 0, (struct sockaddr
*)&whereto,
778 sizeof(whereto));
779
780 if (i < 0 || i != cc) {
781 if (i < 0) {
782 if (options & F_FLOOD && errno ==
ENOBUFS) {
783 usleep(FLOOD_BACKOFF);
784 return;
785 }
786 warn("sendto");
787 } else {
788 warn("%s: partial write: %d of %d
bytes",
789 hostname, i, cc);
790 }
791 }
The sendto() on line 777 failed because there is insufficient buffer
space to buffer any more icmp packets. The usual reason for this is the
machine you're attempting to ping can't be reached via whatever route
you're using.
- --
Where am I, and what am I doing in this handbasket?
Wes Peters w...@softweyr.com
------------------------------
Date: Tue, 04 Feb 2003 17:37:53 +0700
From: Eugene Grosbein <eu...@kuzbass.ru>
Subject: bin/45754: vnconfig(8) fails to return correct exit status
Hi!
Please review a patch in this PR:
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=bin/45754
Correct scripting is very hard when system utility returns wrong
exit status.
Eugene Grosbein
------------------------------
Date: Tue, 04 Feb 2003 11:43:16 +0100
From: Dag-Erling Smorgrav <d...@ofug.org>
Subject: Re: "ping: sendto: No buffer space available"
Peter Radcliffe <p...@pir.net> writes:
> Bill Moran <wmo...@potentialtech.com> probably said:
> > What kind of interface are you pinging through?
> I've seen it on various interfaces, in this case a Cisco 350 wireless
> card.
Interference is preventing the card from transmitting, causing packets
to accumulate in the outgoing queue.
DES
- --
Dag-Erling Smorgrav - d...@ofug.org
------------------------------
Date: Tue, 04 Feb 2003 12:56:29 +0100
From: Dag-Erling Smorgrav <d...@ofug.org>
Subject: Re: HEADS UP: OpenSSH 3.5p1
Dmitry Parfenov <di...@itn.ru> writes:
> Feb 4 11:00:58 P1 sshd[48147]: pam_start: malloc failed for pam_conv
> Feb 4 11:00:58 P1 sshd[48147]: fatal: PAM: initialisation failed
> Feb 4 11:01:37 P1 sshd[53308]: pam_start: malloc failed for pam_conv
> Feb 4 11:01:37 P1 sshd[53308]: fatal: PAM: initialisation failed
That has already been fixed. I tested on a different machine than the
one I committed from, and left out one last-minute patch before
committing. The irony is that the patch in question did get committed
to -CURRENT, where it's not needed...
DES
- --
Dag-Erling Smorgrav - d...@ofug.org
------------------------------
Date: Tue, 4 Feb 2003 14:50:09 +0000
From: Geoff Buckingham <geo...@chuggalug.clues.com>
Subject: HP/Compaq DL580 G2
Anybody got the Broadcom NIC provides with these systems to work with 4.7?
or at all?
------------------------------
Date: Tue, 4 Feb 2003 16:38:05 +0200
From: Ruslan Ermilov <r...@freebsd.org>
Subject: Re: HP/Compaq DL580 G2
- --EuxKj2iCbKjpUGkD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Feb 04, 2003 at 02:50:09PM +0000, Geoff Buckingham wrote:
> Anybody got the Broadcom NIC provides with these systems to work with 4.7?
>=20
> or at all?
>=20
Gigabit one?
Cheers,
- --=20
Ruslan Ermilov Sysadmin and DBA,
r...@sunbay.com Sunbay Software AG,
r...@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
- --EuxKj2iCbKjpUGkD
Content-Type: application/pgp-signature
Content-Disposition: inline
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE+P9BNUkv4P6juNwoRAgkSAJ4inDHnN0/4MgiJXjQOUhyRmseY/wCfRy3c
uCnBYbKgiLIJVGTZodF95tQ=
=5tp/
- -----END PGP SIGNATURE-----
- --EuxKj2iCbKjpUGkD--
------------------------------
Date: Tue, 4 Feb 2003 15:36:47 +0000
From: Geoff Buckingham <geo...@chuggalug.clues.com>
Subject: Re: HP/Compaq DL580 G2
On Tue, Feb 04, 2003 at 04:38:05PM +0200, Ruslan Ermilov wrote:
> On Tue, Feb 04, 2003 at 02:50:09PM +0000, Geoff Buckingham wrote:
> > Anybody got the Broadcom NIC provides with these systems to work with 4.7?
> >
> > or at all?
> >
> Gigabit one?
>
I have bee looking into this, the machine is a loaner,
it contains three em's which I can see fine, an fxp
and a bge which I can not.
The two nics I cant see are not listed as unknown devices either,
they seem to be hidden behind the compaq hotplug pci controller
(0xa0f7)
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002
ro...@builder.freebsdmall.com:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium 4 (1599.95-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf11 Stepping = 1
Features=0x3febfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,<b28>,ACC>
real memory = 2147459072 (2097128K bytes)
avail memory = 2086514688 (2037612K bytes)
Preloaded elf kernel "kernel" at 0xc050f000.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pci0: <unknown card> (vendor=0x0e11, dev=0xb203) at 2.0 irq 3
pci0: <unknown card> (vendor=0x0e11, dev=0xb204) at 2.2 irq 5
pci0: <ATI Mach64-GR graphics accelerator> at 3.0
isab0: <PCI to ISA bridge (vendor=1166 device=0201)> at device 15.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <ServerWorks CSB5 ATA100 controller> port 0x2000-0x200f,0x374-0x377,0x1
70-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
ohci0: <OHCI (generic) USB controller> mem 0xeefe0000-0xeefe0fff irq 10 at devic
e 15.2 on pci0
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 4 ports with 4 removable, self powered
pcib1: <Host to PCI bridge> on motherboard
pci1: <PCI bus> on pcib1
ciss0: <Compaq Smart Array 5i> port 0x3000-0x30ff mem 0xf01f0000-0xf01f3fff,0xf0
2c0000-0xf02fffff irq 11 at device 1.0 on pci1
ciss0: using 256 of 1024 available commands
ciss0: 1 logical drive configured
ciss0: firmware 1.80
ciss0: 2 SCSI channels
ciss0: signature 'CISS'
ciss0: valence 1
ciss0: supported I/O methods 0xe<simple,performant,MEMQ>
ciss0: active I/O method 0x3<simple>
ciss0: 4G page base 0x00000000
ciss0: interrupt coalesce delay 1000us
ciss0: interrupt coalesce count 16
ciss0: max outstanding commands 1024
ciss0: bus types 0x2<ultra3>
ciss0: server name ''
ciss0: heartbeat 0x30000058
ciss0: 1 logical drive
ciss0: logical drive 0: RAID 5, 34304MB online
pcib2: <Host to PCI bridge> on motherboard
pci2: <PCI bus> on pcib2
em0: <Intel(R) PRO/1000 Network Connection, Version - 1.3.14> mem 0xf2bd0000-0xf
2bdffff,0xf2be0000-0xf2bfffff irq 10 at device 1.0 on pci2
em0: Speed:N/A Duplex:N/A
em1: <Intel(R) PRO/1000 Network Connection, Version - 1.3.14> mem 0xf2b90000-0xf
2b9ffff,0xf2ba0000-0xf2bbffff irq 5 at device 2.0 on pci2
em1: Speed:N/A Duplex:N/A
pci2: <unknown card> (vendor=0x0e11, dev=0xa0f7) at 30.0 irq 3
pcib3: <Host to PCI bridge> on motherboard
pci3: <PCI bus> on pcib3
pcib4: <Host to PCI bridge> on motherboard
pci4: <PCI bus> on pcib4
pcib5: <Host to PCI bridge> on motherboard
pci5: <PCI bus> on pcib5
pcib6: <Host to PCI bridge> on motherboard
pci6: <PCI bus> on pcib6
em2: <Intel(R) PRO/1000 Network Connection, Version - 1.3.14> mem 0xf7cd0000-0xf
7cdffff,0xf7ce0000-0xf7cfffff irq 10 at device 2.0 on pci6
em2: Speed:N/A Duplex:N/A
pci6: <unknown card> (vendor=0x0e11, dev=0xa0f7) at 30.0 irq 10
pcib7: <Host to PCI bridge> on motherboard
pci7: <PCI bus> on pcib7
pcib8: <Host to PCI bridge> on motherboard
pci8: <PCI bus> on pcib8
eisa0: <EISA bus> on motherboard
mainboard0: <CPQ0736 (System Board)> on eisa0 slot 0
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff,0xcc000-0xcd7ff,0xc
d800-0xcefff,0xee000-0xeffff on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
ppc0: parallel port not found.
ata0-slave: ATA identify retries exceeded
acd0: CDROM <COMPAQ CD-ROM SN-124> at ata0-master PIO4
Mounting root from ufs:/dev/da0s1a
da0 at ciss0 bus 0 target 0 lun 0
da0: <COMPAQ RAID 5 VOLUME OK> Fixed Direct Access SCSI-0 device
da0: 135.168MB/s transfers
da0: 34719MB (71106240 512 byte sectors: 255H 32S/T 8714C)
------------------------------
Date: Tue, 4 Feb 2003 17:16:17 +0200
From: Ruslan Ermilov <r...@freebsd.org>
Subject: Re: HP/Compaq DL580 G2
- --3MwIy2ne0vdjdPXF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Feb 04, 2003 at 03:36:47PM +0000, Geoff Buckingham wrote:
> On Tue, Feb 04, 2003 at 04:38:05PM +0200, Ruslan Ermilov wrote:
> > On Tue, Feb 04, 2003 at 02:50:09PM +0000, Geoff Buckingham wrote:
> > > Anybody got the Broadcom NIC provides with these systems to work with=
4.7?
> > >=20
> > > or at all?
> > >=20
> > Gigabit one?
> >=20
>=20
> I have bee looking into this, the machine is a loaner,=20
> it contains three em's which I can see fine, an fxp
> and a bge which I can not.
>=20
> The two nics I cant see are not listed as unknown devices either,
> they seem to be hidden behind the compaq hotplug pci controller
> (0xa0f7)
>=20
Sorry, ENOCLUE. What I know is that our bge(4) driver is
buggy with some old firmware cards, like the one we had
here, so it may or may not work for you.
> Copyright (c) 1992-2002 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002
> ro...@builder.freebsdmall.com:/usr/obj/usr/src/sys/GENERIC
> Timecounter "i8254" frequency 1193182 Hz
> CPU: Pentium 4 (1599.95-MHz 686-class CPU)
> Origin =3D "GenuineIntel" Id =3D 0xf11 Stepping =3D 1
> Features=3D0x3febfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,=
PGE,MCA,C
> MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,<b28>,ACC>
> real memory =3D 2147459072 (2097128K bytes)
> avail memory =3D 2086514688 (2037612K bytes)
> Preloaded elf kernel "kernel" at 0xc050f000.
> Pentium Pro MTRR support enabled
> md0: Malloc disk
> npx0: <math processor> on motherboard
> npx0: INT 16 interface
> pcib0: <Host to PCI bridge> on motherboard
> pci0: <PCI bus> on pcib0
> pci0: <unknown card> (vendor=3D0x0e11, dev=3D0xb203) at 2.0 irq 3
> pci0: <unknown card> (vendor=3D0x0e11, dev=3D0xb204) at 2.2 irq 5
> pci0: <ATI Mach64-GR graphics accelerator> at 3.0
> isab0: <PCI to ISA bridge (vendor=3D1166 device=3D0201)> at device 15.0 o=
n pci0
> isa0: <ISA bus> on isab0
> atapci0: <ServerWorks CSB5 ATA100 controller> port 0x2000-0x200f,0x374-0x=
377,0x1
> 70-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0
> ata0: at 0x1f0 irq 14 on atapci0
> ata1: at 0x170 irq 15 on atapci0
> ohci0: <OHCI (generic) USB controller> mem 0xeefe0000-0xeefe0fff irq 10 a=
t devic
> e 15.2 on pci0
> usb0: OHCI version 1.0, legacy support
> usb0: SMM does not respond, resetting
> usb0: <OHCI (generic) USB controller> on ohci0
> usb0: USB revision 1.0
> uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 4 ports with 4 removable, self powered
> pcib1: <Host to PCI bridge> on motherboard
> pci1: <PCI bus> on pcib1
> ciss0: <Compaq Smart Array 5i> port 0x3000-0x30ff mem 0xf01f0000-0xf01f3f=
ff,0xf0
> 2c0000-0xf02fffff irq 11 at device 1.0 on pci1
> ciss0: using 256 of 1024 available commands
> ciss0: 1 logical drive configured
> ciss0: firmware 1.80
> ciss0: 2 SCSI channels
> ciss0: signature 'CISS'
> ciss0: valence 1
> ciss0: supported I/O methods 0xe<simple,performant,MEMQ>
> ciss0: active I/O method 0x3<simple>
> ciss0: 4G page base 0x00000000
> ciss0: interrupt coalesce delay 1000us
> ciss0: interrupt coalesce count 16
> ciss0: max outstanding commands 1024
> ciss0: bus types 0x2<ultra3>
> ciss0: server name ''
> ciss0: heartbeat 0x30000058
> ciss0: 1 logical drive
> ciss0: logical drive 0: RAID 5, 34304MB online
> pcib2: <Host to PCI bridge> on motherboard
> pci2: <PCI bus> on pcib2
> em0: <Intel(R) PRO/1000 Network Connection, Version - 1.3.14> mem 0xf2bd0=
000-0xf
> 2bdffff,0xf2be0000-0xf2bfffff irq 10 at device 1.0 on pci2
> em0: Speed:N/A Duplex:N/A
> em1: <Intel(R) PRO/1000 Network Connection, Version - 1.3.14> mem 0xf2b90=
000-0xf
> 2b9ffff,0xf2ba0000-0xf2bbffff irq 5 at device 2.0 on pci2
> em1: Speed:N/A Duplex:N/A
> pci2: <unknown card> (vendor=3D0x0e11, dev=3D0xa0f7) at 30.0 irq 3
> pcib3: <Host to PCI bridge> on motherboard
> pci3: <PCI bus> on pcib3
> pcib4: <Host to PCI bridge> on motherboard
> pci4: <PCI bus> on pcib4
> pcib5: <Host to PCI bridge> on motherboard
> pci5: <PCI bus> on pcib5
> pcib6: <Host to PCI bridge> on motherboard
> pci6: <PCI bus> on pcib6
> em2: <Intel(R) PRO/1000 Network Connection, Version - 1.3.14> mem 0xf7cd0=
000-0xf
> 7cdffff,0xf7ce0000-0xf7cfffff irq 10 at device 2.0 on pci6
> em2: Speed:N/A Duplex:N/A
> pci6: <unknown card> (vendor=3D0x0e11, dev=3D0xa0f7) at 30.0 irq 10
> pcib7: <Host to PCI bridge> on motherboard
> pci7: <PCI bus> on pcib7
> pcib8: <Host to PCI bridge> on motherboard
> pci8: <PCI bus> on pcib8
> eisa0: <EISA bus> on motherboard
> mainboard0: <CPQ0736 (System Board)> on eisa0 slot 0
> orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff,0xcc000-0xcd=
7ff,0xc
> d800-0xcefff,0xee000-0xeffff on isa0
> fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
> fdc0: FIFO enabled, 8 bytes threshold
> fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
> atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
> kbd0 at atkbd0
> psm0: <PS/2 Mouse> irq 12 on atkbdc0
> psm0: model IntelliMouse, device ID 3
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> sc0: <System console> at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=3D0x300>
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A
> sio1: configured irq 3 not in bitmap of probed irqs 0
> ppc0: parallel port not found.
> ata0-slave: ATA identify retries exceeded
> acd0: CDROM <COMPAQ CD-ROM SN-124> at ata0-master PIO4
> Mounting root from ufs:/dev/da0s1a
> da0 at ciss0 bus 0 target 0 lun 0
> da0: <COMPAQ RAID 5 VOLUME OK> Fixed Direct Access SCSI-0 device
> da0: 135.168MB/s transfers
> da0: 34719MB (71106240 512 byte sectors: 255H 32S/T 8714C)
>=20
>=20
> To Unsubscribe: send mail to majo...@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
- --=20
Ruslan Ermilov Sysadmin and DBA,
r...@sunbay.com Sunbay Software AG,
r...@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
- --3MwIy2ne0vdjdPXF
Content-Type: application/pgp-signature
Content-Disposition: inline
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE+P9lBUkv4P6juNwoRAuOZAKCMFekdmPs8hXlj7Gg+Vyzp1fNwXACfdeRc
w4O9Hi5E9Kyl9f4MvwGppjw=
=SA5t
- -----END PGP SIGNATURE-----
- --3MwIy2ne0vdjdPXF--
------------------------------
Date: Tue, 04 Feb 2003 07:18:55 -0800
From: Michael Sierchio <ku...@tenebras.com>
Subject: Re: "ping: sendto: No buffer space available"
Dag-Erling Smorgrav wrote:
> Interference is preventing the card from transmitting, causing packets
> to accumulate in the outgoing queue.
Dummynet queues with RED might help -- changing the behavior from tail
dropping to early detection may improve performance.
------------------------------
Date: Tue, 4 Feb 2003 16:29:18 +0100
From: Thomas Quinot <tho...@cuivre.fr.eu.org>
Subject: Re: HP/Compaq DL580 G2
Speaking of Broadcom hardware, does anyone have
information/specs/whatever that could allow the implementation of a
driver for their WiFi cards (Dell Truemobile 1180, specifically)?
Thomas.
- --
Thomas...@Cuivre.FR.EU.ORG
------------------------------
Date: Tue, 4 Feb 2003 16:22:57 +0000
From: Geoff Buckingham <geo...@chuggalug.clues.com>
Subject: Re: HP/Compaq DL580 G2
On Tue, Feb 04, 2003 at 03:40:52PM -0000, Alex Trull wrote:
> (Potentialy a double mail - if so, please excuse me.)
>
> Ah, I had this problem with a system which arrived earlier this year, it was
> a Compaq G3. (the G3s have alot more in common with the G2s than the 2s do
> with the first gens)
>
> Anyway.. I had to hack the bge drivers to recognise the deviceid of my lan
> adapters (see dmesg for unrecognised pci devices), I rebuilt this on the
> 4.7-Release (i.e. the first cd's sources).. at which point it actually
> worked, although it found 256xmedia according to dmesg - I then cvsupped to
> the latest releng_4 , rebuilt and found some kind soul had by then added
> real (non-hack) support. It went back to 1xmedia :).
>
Wich unknown device? The four in the dmesg all seem to be accounted for:
> > pci0: <PCI bus> on pcib0
> > pci0: <unknown card> (vendor=0x0e11, dev=0xb203) at 2.0 irq 3
> > pci0: <unknown card> (vendor=0x0e11, dev=0xb204) at 2.2 irq 5
these are the managment device RiLO/iLO thing.
> > pci2: <unknown card> (vendor=0x0e11, dev=0xa0f7) at 30.0 irq 3
this is listed as a hot-plug pci controller.
> > pci6: <unknown card> (vendor=0x0e11, dev=0xa0f7) at 30.0 irq 10
this is the same.
------------------------------
Date: Tue, 4 Feb 2003 16:41:57 +0000
From: Geoff Buckingham <geo...@chuggalug.clues.com>
Subject: Re: HP/Compaq DL580 G2
On Tue, Feb 04, 2003 at 04:22:57PM +0000, Geoff Buckingham wrote:
Stranger and Stranger, having read some the documentation for
this machine, the three em NICs that are detected are in the
PCI-X hotplug slots, on two seperate PCI busses.
The missing fxp0 and bge0 are in the non-hotplug slots which
seem to be on the same bus. It looks like that bus is not being
probed for some reason.
------------------------------
Date: Tue, 4 Feb 2003 17:10:05 +0100
From: Michael Hostbaek <mi...@freebsdcluster.org>
Subject: Re: problem with fxp interface in promisc mode
Tom Beer (tom) writes:
> On Sat, Jan 25, 2003 at 02:57:23PM +0100, Michael Hostbaek wrote:
>
>
> unfourtunately the fxp thread ended there:
>
> Will this fix the problem?
I have not expirienced any problems after the upgrade - and I have used
tcpdump & friends heavily.. So, yes, if fixed my problem.
/mich
- --
Best Regards,
Michael Landin Hostbaek
FreeBSDCluster.org - an International Community
*/ PGP-key available upon request /*
------------------------------
Date: Tue, 4 Feb 2003 08:40:34 -0800
From: Ryan Dooley <ry...@third-man.com>
Subject: Re: recommendations on the newfs of a 1.0TB fs...
> When you say ``the default wasted too much disk space'', do you
> mean that when you formatted the filesystem, you had less space
> than you expected, or do you mean that there was less space left
> after you put all of your data on it? Smaller block sizes mean
> more space for free block bitmaps, which are allocated at
> filesystem creation time, but overall they are a win in terms of
> space because of reduced internal fragmentation. Consider what
> happens when you put a 10K file on the disk. Depending on whether
> the filesystem is optimizing for space or time, that file will
> take up 16K or 64K in your 64/16 filesystem, but substantially
> less with a 16/2 FS. So unless you are expecting most of your
> files to be rather large, a smaller block size may be beneficial.
> Note, however, that I'm not an FFS expert; other factors such as
> fragmentation may be relevant.
The formatted file system had less total available space left on it. Now
it was like 5am and I'd been up for the past 24 hours setting things up
two years ago so it's a bit fuzzy :-)
Right now the FS is optimizing for time.
I had read some where (I'll see if I can dig up my notes), but I remember
getting the distinct feeling that the larger block size was what I wanted,
but like I said, it's all a bit fuzzy.
> I would also be interested in knowing how FFS and reiserfs compare
> with respect to filesystem age. Does performance drop
> significantly after a year? If the research I've seen is right,
> FFS performance shouldn't drop more than 20% unless the filesystem
> is nearly full, and reiserfs has a cleaner...
I'll see about running some dbench marks or bonnie and see how things
shape up.
Cheers,
Ryan
------------------------------
Date: Tue, 04 Feb 2003 11:51:48 -0600
From: Oscar Ricardo Silva <osi...@scuff.cc.utexas.edu>
Subject: Re: filesystem disappeared following 4.2 -> 4.7 upgrade
At 08:23 PM 2/2/2003 -0600, Mike Meyer, you wrote:
>In <20030202202...@kearneys.ca>, Brent Kearney <br...@kearneys.ca>
>typed:
> > What if this system were an all-IDE system? I was planning to update
> > one soon, and will no doubt run into this problem. The root
> > filesystem device node will change names, and according to this
> > thread:
> >
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=2388792+2394647+/usr/local/www/db/text/2003/freebsd-questions/20030112.freebsd-questions
>
>No, devices *may* change names. They don't have to. The article you
>quoted changed names drastically because he wasn't using the onboard
>IDE controller, but had all his drives on the Promise card (would you
>verify that for me, Oscar)? One solution to the question asked in that
>message is to disable the IDE on the motherboard so that the Promise
>controller becomes ata0, and the first drive on it becomes ad0. That
>also frees up a couple of IRQs, and may be worth doing in any
>case. It's probably better to try changing /boot/loader.conf to set
>root_disk_unit to solve the problem, though.
Welllll ... yes and no. I wasn't putting the drive on the first and second
IDE controllers. The motherboard had two additional IDE controllers,
Promise ATA66, on it.
On some BIOS, you can direct the machine to look at slot devices before
onboard devices, that might help your situation.
Not that it's any kind of solution, but in the end, while attempting to do
another install on the system, I accepted the default sizes for the
filesystems and it worked. Creating a / filesystem of 128MB ... and from
there it booted fine.
Oscar
------------------------------
Date: Tue, 4 Feb 2003 13:00:11 -0500 (EST)
From: Mike Lambert <lam...@jeol.com>
Subject: IBM x335 Broadcom BCM5703 NICs not detected by 4.7-R
Greetings,
I am attempting to configure FreeBSD 4.7-RELEASE to run on an IBM
xSeries 335. The two motherboard Broadcom Gigabit Ethernet devices are
not detected by the kernel. Relevant output of 'boot -v'...
pcib2: <Host to PCI bridge> on motherboard
found-> vendor=0x14e4, dev=0x16a7, revid=0x02
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=a, irq=11
map[10]: type 1, range 64, base f5ff0000, size 16
found-> vendor=0x14e4, dev=0x16a7, revid=0x02
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0 secondarybus=0
intpin=a, irq=3
map[10]: type 1, range 64, base f5fe0000, size 16
pci3: <PCI bus> on pcib2
pci3: <unknown card> (vendor=0x14e4, dev=0x16a7) at 1.0 irq 11
pci3: <unknown card> (vendor=0x14e4, dev=0x16a7) at 2.0 irq 3
and 'pciconf -lv'...
none1@pci3:1:0: class=0x020000 card=0x026f1014 chip=0x16a714e4
rev=0x02 hdr=0x00
vendor = 'Broadcom Corporation'
device = 'BCM5703X Gigabit Ethernet'
class = network
subclass = ethernet
none2@pci3:2:0: class=0x020000 card=0x026f1014 chip=0x16a714e4
rev=0x02 hdr=0x00
vendor = 'Broadcom Corporation'
device = 'BCM5703X Gigabit Ethernet'
class = network
subclass = ethernet
I fiddled with BIOS settings (no "PnP OS" option) and tried a stripped
down kernel with no success. Installing a 3c905 PCI card works fine, but
I would prefer to use the built in NICs.
Any suggestions?
Regards,
Mike Lambert
------------------------------
Date: Tue, 4 Feb 2003 12:11:03 -0800
From: James Long <sta...@museum.rain.com>
Subject: Re: IBM x335 Broadcom BCM5703 NICs not detected by 4.7-R
On Tue, Feb 04, 2003 at 01:00:11PM -0500, Mike Lambert wrote:
>
> I am attempting to configure FreeBSD 4.7-RELEASE to run on an IBM
> xSeries 335. The two motherboard Broadcom Gigabit Ethernet devices are
> not detected by the kernel. Relevant output of 'boot -v'...
I have a Compaq ML310 with a Broadcom Gigabit NIC which also was not
detected by 4.7-REL. I dropped in an Intel NIC, cvsupped to 4.7-STABLE,
and the newer kernel recognized the Broadcom.
------------------------------
Date: Tue, 4 Feb 2003 13:02:50 -0800
From: "vizion communication" <viz...@ixpres.com>
Subject: FreeBSD set up on Compaq Proliant 5500
I am obviously doing something wrong which is causing
difficulty installing freebsd 4.7 in the following
circumstances:
Quad Processor Compaq Proliant with 3200 Raid (2 Channel
LVD/SE Scsi Array Controller)
Prior to installing FreeBSD using the Compaq SmartStart
utility I created a raid (Array A) on the first raid channel
using four physical drives each of 18.2G using RAID 5.
Array A is divided into 11 logical Drives each with the
following number of 512 sectors:
Logical #1,8,10 ------4194240
Logical #2,7------- 8364000
Logical #3,4------- 16776960
Logical #5--------- 2097120
Logical #6--------- 6291360
Logical #9--------- 8380320
Logical#11-------- 27050400
The 11 logical drives reported by Compaq Raid Controller on
POST and no errors are reported when Compaq Array Diagnostic
Utility is run.
On Boot up using FreeBSD 4.7 CD FreeBSD Reports drives A
thru J
In the FreeBSD select drives drives utility the following
drives are identified:
idad0, 4194240 Sectors (2047MB)
idad1, 8364000 Sectors (4083MB)
idad2, 16776960 Sectors (8191MB)
idad3 16776960 Sectors (8191MB)
None of the other logical drives are identified by the
install utility.
Whilst it may only be a coincidence it seems odd that
FreeBSDis only "seeing" the first logical raid partitions
and that there are four physical drives. Do I need some kind
of driver installed so that FreeBSD can recognize the
logical raid partitions?
Help appreciated
Thanks
David
------------------------------
Date: Tue, 4 Feb 2003 23:58:06 +0200
From: "Ventsislav Velkov" <ve...@evrocom.bg>
Subject: Re: FreeBSD set up on Compaq Proliant 5500
You could create the missing manually,
$cd /dev
$sh MAKEDEV idad4 .... etc.
for each logical drive.
- ----- Original Message -----
From: "vizion communication" <viz...@ixpres.com>
To: <sta...@FreeBSD.ORG>
Sent: Tuesday, February 04, 2003 11:02 PM
Subject: FreeBSD set up on Compaq Proliant 5500
> I am obviously doing something wrong which is causing
> difficulty installing freebsd 4.7 in the following
> circumstances:
>
> Quad Processor Compaq Proliant with 3200 Raid (2 Channel
> LVD/SE Scsi Array Controller)
> Prior to installing FreeBSD using the Compaq SmartStart
> utility I created a raid (Array A) on the first raid channel
> using four physical drives each of 18.2G using RAID 5.
>
> Array A is divided into 11 logical Drives each with the
> following number of 512 sectors:
> Logical #1,8,10 ------4194240
> Logical #2,7------- 8364000
> Logical #3,4------- 16776960
> Logical #5--------- 2097120
> Logical #6--------- 6291360
> Logical #9--------- 8380320
> Logical#11-------- 27050400
>
> The 11 logical drives reported by Compaq Raid Controller on
> POST and no errors are reported when Compaq Array Diagnostic
> Utility is run.
>
> On Boot up using FreeBSD 4.7 CD FreeBSD Reports drives A
> thru J
>
> In the FreeBSD select drives drives utility the following
> drives are identified:
>
> idad0, 4194240 Sectors (2047MB)
> idad1, 8364000 Sectors (4083MB)
> idad2, 16776960 Sectors (8191MB)
> idad3 16776960 Sectors (8191MB)
>
> None of the other logical drives are identified by the
> install utility.
>
> Whilst it may only be a coincidence it seems odd that
> FreeBSDis only "seeing" the first logical raid partitions
> and that there are four physical drives. Do I need some kind
> of driver installed so that FreeBSD can recognize the
> logical raid partitions?
>
> Help appreciated
>
> Thanks
>
> David
>
>
>
>
>
>
>
> To Unsubscribe: send mail to majo...@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
>
------------------------------
Date: Wed, 5 Feb 2003 08:43:22 +0900
From: "Noritaka Fukuo" <no-f...@nifty.com>
Subject: [none]
subscribe freebsd-stable
subscribe cvs-all
------------------------------
End of stable-digest V5 #784
****************************
To Unsubscribe: send mail to majo...@FreeBSD.org
with unsubscribe freebsd-stable-digest in the body of the message