Prev: ?: Directory checksum
Next: Installing Slackware Linux 12.0
From: +Alan Hicks+ on 22 Jan 2008 11:47
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Replying to the list for the OP because I think I remember/know-more
about what finally fixed the problem. :^)

On 2008-01-19, Jason161(a)gmail.com <Jason161(a)gmail.com> wrote:
> So after much help from #slackware(a)freenode, I have realized that
> since I had to do chmod -x rc.udev, to avoid getting the blackscreen
> at bootup after my initial installation, it seems that the firmware is
> having problems loading, and dmesg shows:
> Cannot read microcode reason: -2

The OP's laptop was hard-locking when udev ran. Robby, Fred, and I
were working on this pretty hard and heavy during the KDE 4 Release
Party. At first we suspected a module conflict of some sort, and
quickly banged up a script to test.

find /lib/modules/$(uname -r) -name "*.ko" | (while read MOD; do
i=$(basename $MOD .ko)
echo $i >> /root/mod_log
sync
modprobe $i
done)

The intention was to locate what module was the last to be loaded
before the system froze up. Unfortunately, this did not resolve the
issue. The script went through every module one by one and finally
completed, all without a single lock-up. This pointed us to a problem
with Slackware's udev or a kernel bug. Since other distros worked fine
with the laptop, we dis-missed the idea of a kernel bug.

Since we didn't want to spend too much time troubleshooting something
that might have been fixed in -current, we got the OP to install
- -current from an unofficial iso obtained from slackware.no. When this
failed to resolve the issue, we felt certain it was a bug in udev.
Running udev by hand from the shell prompt was successful, but when
rc.udev was 755, the system would lock-up before booting was completed.

At a loss of what else to do, we called in PiterPunk for some help. He
eventually traced the error down to 60-pcmcia.rules. While I am still
uncertain exactly what was done to fix the problem, Piter informed me
that when he serialized the udev rules rather than run them in
parrallel, everything worked properly. This of course, means that
rc.udev takes much longer to run, but it at least operates properly.

Hope that helps to explain things to everyone.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFHlh4qrZS6hX/gvjoRAtrtAKC/u3zcH8gBfJR+4tzwZ5Xp+PiALACfeKNh
K+211V0UPjEmoOD/jnNhTbU=
=Me+H
-----END PGP SIGNATURE-----
 | 
Pages: 1
Prev: ?: Directory checksum
Next: Installing Slackware Linux 12.0