LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Errors in dmesg (http://www.linuxquestions.org/questions/slackware-14/errors-in-dmesg-650705/)

ragebot 06-21-2008 07:26 AM
Errors in dmesg
 
Hi

Installed Slackware yesterday, so far so good!

been looking at dmesg to check for errors, etc. Found this and don't know what it means exactly and haven't found much explanation from my google searches:

scsi: <fdomain> Detection failed (no card)
Failed initialization of WD-7000 SCSI card!
rtc_cmos: probe of 00:03 failed with error -16
Failed initialization of WD-7000 SCSI card!

and...

Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.

From the bits i've read (if i've understood correctly) it looks like a driver, or lack of, for the 'WD-7000' problem.

I haven't a clue what the 'Intel ISA PCIC probe: not found' might be.

Would anyone be able to shed any light on this. If there's any problems with my system i want to fix them and i'm having difficulty troubleshooting this.

TIA

Jamie

snowtigger 06-21-2008 07:41 AM
The kernels shipped with Slackware have just about every driver compiled into them.

So as it boots up all these drivers search for whatever device they are designed for. They will either find them or not, as is your case.

If you really don't want these "errors" showing up then you will have to recompile you kernel with out the built in. They are not errors if you don't have the devices in your machine, however if you do actually have these devices then it is an error.

:)

T3slider 06-21-2008 07:51 AM
Quote:
Originally Posted by snowtigger
If you really don't want these "errors" showing up then you will have to recompile you kernel with out the built in.
...or switch to one of the generic kernels (preferably the generic-smp kernel) also included with Slackware to avoid compiling a kernel. Instructions for doing so are posted everywhere in these forums -- do a search. To use the generic kernel you must use an initrd (initial ramdisk). Read /boot/README.initrd for more information. A nice script that tries to determine the correct mkinitrd command automatically, written by Alien Bob, is located here. You should also read CHANGES_AND_HINTS.TXT on your install CD/DVD or at your favourite mirror for more information, like this:
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
Use one of the provided generic kernels for daily use. Do not report
bugs until/unless you have reproduced them using one of the stock
generic kernels. You will need to create an initrd in order to boot
the generic kernels - see /boot/README.initrd for instructions.
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
As stated earlier, it is recommended that you use one of the generic kernels
rather than the huge kernels; the huge kernels are primarily intended as
"installer" and "emergency" kernels in case you forget to make an initrd.
For most systems, you should use the generic SMP kernel if it will run,
even if your system is not SMP-capable. Some newer hardware needs the
local APIC enabled in the SMP kernel, and theoretically there should not be
a performance penalty with using the SMP-capable kernel on a uniprocessor
machine, as the SMP kernel tests for this and makes necessary adjustments.
Furthermore, the kernel sources shipped with Slackware are configured for
SMP usage, so you won't have to modify those to build external modules
(such as NVidia or ATI proprietary drivers) if you use the SMP kernel.

If you decide to use one of the non-SMP kernels, you will need to follow the
instructions in /extra/linux-2.6.24.5-nosmp-sdk/README.TXT to modify your
kernel sources for non-SMP usage. Note that this only applies if you are
using the Slackware-provided non-SMP kernel - if you build a custom kernel,
the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the
correct kernel source so long as you don't (re)move it.

If you decide to use one of the huge kernels anyway, you will encounter
errors like this:
kobject_add failed for uhci_hcd with -EEXIST, don't try to register
These occur because the respective drivers are compiled statically into the
huge kernels but udev tries to load them anyway. These errors should be safe
to ignore, but if you really don't want them to appear, you can blacklist the
modules that try to load in /etc/modprobe.d/blacklist. However, make sure you
remove them from the blacklist if you ever decide to use the (recommended)
generic kernels.

ragebot 06-21-2008 07:55 AM
I've not recompiled a kernel before but i have been reading the slackbook.org and it doesn't seem too complicated so i'm quite prepared to give it a go.

At risk of sounding stupid :o i'm not sure if i do have those devices installed or not. Any tips on how i can check that and what they are?

Jamie

ragebot 06-21-2008 08:00 AM
Thanks both. Just read your reply T3slider after i'd posted again. Will look into that, thanks for the advice.

Jamie


All times are GMT -5. The time now is 03:44 PM.