Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 22 Nov 2006 01:55:59 +0300
From: Solar Designer <>
Subject: Re: SATA controller


On Mon, Nov 20, 2006 at 10:10:39AM +0500, vlad wrote:
> Unfortunately, your advice have not brought due result. :(

This is because you've failed to follow some of the instructions that
were given to you, please see below:

> At attempt to load for the controller I receive the module
> Numerous abuse on "unresolved symlink"

You must have meant "unresolved symbol", not "symlink".  This suggests
that you did not apply some of the patches from under /usr/src/kernel as
I had suggested in another posting.  In order for you to be able to load
modules into the CD-booted kernel, those modules have to be from a
kernel patched and configured in _exactly_ the same way as the kernel on
the CD.  This means that you must apply all of the patches under
/usr/src/kernel (for Owl 2.0, that's linux-2.4.32-ow1 and
patch-cryptoloop-jari-2.4.32-ow1) _and_ use /boot/.config off the CD
(your enabling the compilation of some drivers as modules must be the
only change).

> The question (partially) was solved switching of a disk on other controller of a same payment,
> Which has earned at once, but has given speed of work with a disk
> hdparm-t/dev/hdb1 ~ 3.3 MB/sec
> And it on a SATA-disk!

Well, the name /dev/hdb1 suggests that your system sees this as an IDE
drive, and this low transfer rate is normal for 16-bit PIO mode (this
happens when you have an IDE controller - or one pretending to be IDE -
for which there's no driver in the running kernel).

> But the most interesting, it after installation of system on a disk,
> I at once could load the necessary module for the first controller!

I am guessing that you had used your newly-built kernel for this
installed system.  So you finally had the kernel and the module match.

> I plan to put Openwall as a platform for several servers,


> Whether there is what that the list configurations of the equipment,
> To avoid similar difficulties?

We do not have a "hardware compatibility list", although it might be a
good idea for us to start maintaining one for the next release.

For now, you'll have to refer to the default CD kernel configuration in
/boot/.config to find out what drivers are enabled (without you having
to build/load a module).

Alexander Peslyak <solar at>
GPG key ID: 5B341F15  fp: B3FB 63F4 D7A3 BCCC 6F6E  FC55 A2FC 027C 5B34 1F15 - bringing security into open computing environments

Was I helpful?  Please give your feedback here:

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.