On 14-Jan-2014 23:44:21 -0200, J. Cesar Bertelli wrote: > I had some troubles trying Owl 3.0-stable on my 'new' HP Compaq > Proliant ML350 G3. The relevant hardware is: > raid controller : smartarray 641 > ethernet NIC : BCM5702
That seems to be overseen by our kernel maintainers for a long time (since the Owl had to fit on a single CD and kernel had to fit in a 2.88Mb El Torito image). Despite of a golden rule "keep storage and communication modules compiled in", some of these critical modules are still kept outside. For servers which I administer (at least 30, or 1/3 of their total amount, are HP Proliants) I use my own build of the kernel: ftp://gremlin.people.openwall.com/pub/linux/Owl/SRPMS/kernel-2.6.32-ovz042stab059.7.g2.src.rpm (size: 88025248, sha512: ba57179ec1c5a47b410c9379962305e794cec174f41b84762efd7d5917cf05d921fb44d344c0bac6dc89993fec9e7aff8f080e6fcf8b05ce5cd153c9d011892e) Here's already compiled packages: ftp://gremlin.people.openwall.com/pub/linux/Owl/RPMS.x86_64/kernel-2.6.32-ovz042stab059.7.g2.x86_64.rpm (size: 8681527, sha512: 5cb5063af1d04c31b734d489678e326984f8744fbf89a6014c19e8171d460633f46c17652316d48f7cc154b64b749b4e8580064c221df102fb303d84d79e9405) ftp://gremlin.people.openwall.com/pub/linux/Owl/RPMS.x86_64/kernel-headers-2.6.32-ovz042stab059.7.g2.x86_64.rpm (size: 3694907, sha512: f0a7e5eba7e5f7897fb0fba5c2e0d38b4c2c782678b1b79d6b22e1c64468e6f8f8e7ebc137179108506ef7b6e534f36eb5c6364037c856cfe8d9c0f439352715) Fake package for OpenVZ containers: ftp://gremlin.people.openwall.com/pub/linux/Owl/RPMS.x86_64/kernel-fake-2.6.32-ovz042stab059.7.g2.x86_64.rpm (size: 1728, sha512: 87b8b9000bb709c4cd517f561743f085c1f4cf14508f7be448c85313b16a77785c766032e0d3ead053451dcd2f2a86ccc41deaaaf7cc9ef9fed6feaab26e584e) And even an installation USB flash image (quite old, but should do the job of primary installation; requires at least 2Gb flash): ftp://gremlin.people.openwall.com/pub/linux/Owl/INSTALL/Owl-current-20121029-x86_64-install-flash-2Gb.image.xz (size: 606120676, sha512: c3dd02b748b7f6c03c242f0a1bd7e58fc21580f4356f2757d7b034f15d058e2a705cc20edd8c1b18261dffd9b760fa4ab31b6af26a02ad2a8190d9f64b8878d2) > Owl actually boots, but it doesn't recognize the eth card, and > the installation stops in a blue fashioned screen when I attempt > to go to the first relevant step: partitioning the discs. Notice: > no messages - just the blue. (Seems that it stops when calling > the partition software. Well, I don't know.) The CCISS differs from the usual disk controllers, so you may like to partition, format and mount the will-be-root filesystem manually. That means, before running `settle` you should run `fdisk /dev/cciss/c0d0`, `mke2fs -j /dev/cciss/c0d0p1` and `mount /dev/cciss/c0d0p1 /owl` (and other filesystems as well, most likely "/owl/var" and "/owl/home"). > I never had any experience with RAID. I've read?? that the problem > could be related to some missing kernel modules - for the raid > (cciss) and the NIC (tg3 or bcm5700). Most likely it really is. -- Alexey V. Vissarionov aka Gremlin from Kremlin <gremlin ПРИ gremlin ТЧК ru> GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
pgpz2J4O3OSga.pgp
Description: PGP signature
