[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 16 Jan 2014 21:22:19 +0400
From: Solar Designer <solar@...nwall.com>
To: owl-users@...ts.openwall.com
Subject: Re: Owl on HP ML350 G3
Hi,
On Tue, Jan 14, 2014 at 11:44:21PM -0200, J. Cesar Bertelli wrote:
> I had some troubles trying Owl 3.0-stable on my 'new' HP Compaq Proliant ML350 G3.
You'll likely prefer Owl-current over Owl 3.0-stable, especially if
you're going to build/use newer kernels anyway.
> raid controller : smartarray 641
The kernel on both Owl 3.0-stable and Owl-current includes the cciss
driver compiled in. However, as Gremlin correctly pointed out, the
pathnames to the resulting device files are unusual, which requires more
manual work during installation. You may also need to:
cd /dev
./MAKEDEV cciss0
both on the system you're installing from (the CD-booted one) and on the
newly installed system.
> ethernet NIC : BCM5702 (subsystem : NC7760)
According to:
http://www.broadcom.com/support/ethernet_nic/faq_drivers.php
this NIC is meant to be supported by the tg3 driver. Other Broadcom
NICs are supported by the bnx2 and bnx2x drivers. Out of these three
drivers, we have tg3 and bnx2 compiled in, and bnx2x built as a module
(you'd need to modprobe it if you had a 10G NIC of this type). If your
NIC was not recognized, then maybe the specific version of the tg3
driver that we have doesn't support it; if so, you may in fact have to
use a newer kernel to access that NIC.
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
