Re: Dell 2650 servers

2002-12-30 Thread Russell Coker
On Sat, 28 Dec 2002 12:16, J.H.M. Dassen (Ray) wrote:
> On Fri, Dec 27, 2002 at 20:21:29 +0100, Russell Coker wrote:
> > The Debian package bcm5700-source can be used to build a package of the
> > module.  However this does not support linking the module into the kernel
> > (for an nfs-root image).  This is a minor annoyance for me as I'd like to
> > setup an nfs-root recovery process for my servers...
>
> There's no need for that module if you use a sufficiently recent 2.4.x
> tree; CONFIG_TIGON3=y does the trick (tested with 2.4.20-ac1).

Thanks, I just implemented that with 2.4.20 and it works fine.

Did you get lm-sensors and a hardware watchdog working on the 2650?  If so 
what needs to be done?

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Dell 2650 servers

2002-12-28 Thread J.H.M. Dassen (Ray)
On Fri, Dec 27, 2002 at 20:21:29 +0100, Russell Coker wrote:
> The Debian package bcm5700-source can be used to build a package of the 
> module.  However this does not support linking the module into the kernel 
> (for an nfs-root image).  This is a minor annoyance for me as I'd like to 
> setup an nfs-root recovery process for my servers...

There's no need for that module if you use a sufficiently recent 2.4.x tree;
CONFIG_TIGON3=y does the trick (tested with 2.4.20-ac1).

Ray
-- 
Signs of world domination:
"Tonight on Celebrity Deathmatch: Tux takes on the BSD daemon"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Dell 2650 servers

2002-12-27 Thread Cameron Moore
* [EMAIL PROTECTED] (Russell Coker) [2002.12.27 11:02]:
> I'm currently working with some new Dell 2650 servers.  They seem quite nice, 
> 2*Gig-E on the motherboard, keyboard, monitor, and USB connectors both front 
> and back, 5*U160 hot-swap hard drives with hardware RAID, and redundant 
> hot-swappable PSU's.
> 
> The ones I've got have 73G hard drives (giving 220G of RAID-5 storage with one 
> hot-spare), 2* 1.8GHz P4 CPUs, and 4G of RAM.
> 
> One problem I have is that the PCI dual-ethernet cards don't seem to function 
> properly.  I've pasted in the dmesg output below.  What happens is that they 
> do very slow transfers (much slower than 10baseT) and seem to eat up lots of 
> CPU time (can make the entire machine uselessly slow).

I had to pleasure (this servers are powerful!) of configuring a few of
these a few months ago.  I had the same problem under RedHat 7.3.  I
ended up grabbing the latest version of ethtool and messing with the
setting a little.  I forgot exactly what I changed that fixed it, but
it's working fine now.  So give ethtool a shot, but make sure you have a
newer version.  Thanks
-- 
Cameron Moore
/ I think you can be an honest person and lie about any number \
\of things.  -- Dan Rather talking about President Clinton /


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Dell 2650 servers

2002-12-27 Thread Russell Coker
On Fri, 27 Dec 2002 18:23, Eric Jennings wrote:
> I have some clients running a couple of these servers in our cage.  I
> remember they mentioned that they had to find some external kernel
> module to get the gig-E NICs working correctly.  They were using Redhat
> 8.0 though, and so I dunno if Redhat had other modules/code installed
> to support it.  Redhat kernels can approach "bloat" sometimes, IMO.

The Debian package bcm5700-source can be used to build a package of the 
module.  However this does not support linking the module into the kernel 
(for an nfs-root image).  This is a minor annoyance for me as I'd like to 
setup an nfs-root recovery process for my servers...

> It sounds like you're having problems with NICs on a PCI card though,
> and not the motherboard network interfaces, right?

Correct.  It's Intel duel-100baseT network cards in the PCI slots.

It doesn't matter a lot for me though as most of the machines don't really 
need more than two Ethernet ports.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Dell 2650 servers

2002-12-27 Thread Eric Jennings
I have some clients running a couple of these servers in our cage.  I 
remember they mentioned that they had to find some external kernel 
module to get the gig-E NICs working correctly.  They were using Redhat 
8.0 though, and so I dunno if Redhat had other modules/code installed 
to support it.  Redhat kernels can approach "bloat" sometimes, IMO.

It sounds like you're having problems with NICs on a PCI card though, 
and not the motherboard network interfaces, right?

Eric

On Friday, December 27, 2002, at 09:00 AM, Russell Coker wrote:

I'm currently working with some new Dell 2650 servers.  They seem 
quite nice,
2*Gig-E on the motherboard, keyboard, monitor, and USB connectors both 
front
and back, 5*U160 hot-swap hard drives with hardware RAID, and redundant
hot-swappable PSU's.

The ones I've got have 73G hard drives (giving 220G of RAID-5 storage 
with one
hot-spare), 2* 1.8GHz P4 CPUs, and 4G of RAM.

One problem I have is that the PCI dual-ethernet cards don't seem to 
function
properly.  I've pasted in the dmesg output below.  What happens is 
that they
do very slow transfers (much slower than 10baseT) and seem to eat up 
lots of
CPU time (can make the entire machine uselessly slow).

Another thing is that these servers have a 100baseT network port on the
motherboard for something called "WebBIOS", has anyone got that 
working on a
Linux Server?


eth2: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:B3:81:ED, IRQ 16.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly a67265-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x24c9f043).
  Receiver lock-up workaround activated.
eth3: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:B3:81:EE, IRQ 17.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly a67265-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x24c9f043).
  Receiver lock-up workaround activated.
eth4: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:B3:7B:D1, IRQ 24.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly a67265-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x24c9f043).
  Receiver lock-up workaround activated.
eth5: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:B3:7B:D2, IRQ 25.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly a67265-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x24c9f043).
  Receiver lock-up workaround activated.

--
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux 
packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact 
[EMAIL PROTECTED]



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Dell 2650 servers

2002-12-27 Thread Russell Coker
I'm currently working with some new Dell 2650 servers.  They seem quite nice, 
2*Gig-E on the motherboard, keyboard, monitor, and USB connectors both front 
and back, 5*U160 hot-swap hard drives with hardware RAID, and redundant 
hot-swappable PSU's.

The ones I've got have 73G hard drives (giving 220G of RAID-5 storage with one 
hot-spare), 2* 1.8GHz P4 CPUs, and 4G of RAM.

One problem I have is that the PCI dual-ethernet cards don't seem to function 
properly.  I've pasted in the dmesg output below.  What happens is that they 
do very slow transfers (much slower than 10baseT) and seem to eat up lots of 
CPU time (can make the entire machine uselessly slow).

Another thing is that these servers have a 100baseT network port on the 
motherboard for something called "WebBIOS", has anyone got that working on a 
Linux Server?


eth2: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:B3:81:ED, IRQ 16.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly a67265-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x24c9f043).
  Receiver lock-up workaround activated.
eth3: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:B3:81:EE, IRQ 17.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly a67265-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x24c9f043).
  Receiver lock-up workaround activated.
eth4: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:B3:7B:D1, IRQ 24.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly a67265-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x24c9f043).
  Receiver lock-up workaround activated.
eth5: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:B3:7B:D2, IRQ 25.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly a67265-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x24c9f043).
  Receiver lock-up workaround activated.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]