1. i'm getting an error when i boot my linux box, it says
PCI: no irq known for interupt pin a of device 00:12.0. Please try using pci=biosirq. can someone give more explanation on this problem; if not can someone atleast tell me how to edit a file and make this command pci=biosirg boot when i load the kernel.

2. i get another error
kmod: failed to exec /sbin/modprobe -s -k paride_protocol, errno = 2 how can i fix this, does it need fixin' ?

3. i'd like to make my onboard audio chip look like an isapnp device. is this possible, can i do it?

Well, I've had the "irq" error message in the past and have generally ignored it with no obvious ill effects. It looks like Linux is unable to assign
an IRQ to a PCI device for some reason, and wants you to append a
line that will tell your kernel to use the IRQs assigned by the BIOS. This
isn't necessarily safe to do, especially if you've got some funky, old
hardware that doesn't like to share IRQs.

However, if you really want to fix it, you need to learn a bit about your
boot loader. I'm assuming you use LILO since that's the default for
Slackware, so I'll concentrate my efforts on that.

LILO gives you the ability (as any good boot loader does) to "append"
some information to your kernel boot command line.
Just for fun, do the following:
cat /proc/cmdline

It will print out the exact command used to boot your kernel. Now, to add
an append to your boot command, you can do one of two things.
1) Every time you boot, interrupt LILO at the boot prompt, just before
boot and input the append line, which will be the same as below.
2) Add the append line to your /etc/lilo.conf file and re-install LILO.

1) is educational, but 2) is far more realistic.

To accomplish 2):
edit /etc/lilo.conf with your favorite TEXT editor.

Near the top of the file, there may be a line that says something like:

append="idebus=100"

You want to add your append to that:

append="idebus=100 pci=biosirq"

Otherwise, just add the above line to your lilo.conf, after the
boot=/dev/hda1 (or whatever) line, and after the delay=50 (or whatever)
line.

save your file, and then run:

lilo

If you get any errors, you'll need to figure out what is wrong with your
input. YOU MUST RUN lilo EVERY TIME YOU EDIT /etc/lilo.conf
Do a:
man lilo
which will give you a manual page on how to use lilo. Also, do a:
man lilo.conf
which will give you information on the syntax and setup of /etc/lilo.conf
You should read those before you go mucking about with your lilo.conf file
anyway, since if you screw it up, you can make your system unbootable,
and difficult (though not impossible) to fix.



About your second error:

It looks like you're trying to load a parallel IDE device. If you don't have
one of those, you have no need to load the module. To stop the loading
of said module, edit:
/etc/rc.d/rc.modules
and comment out the line that contains this module.
If it's being automagically loaded, you would need to edit:
/etc/modules.conf
and comment out the correct line.

If you have a parallel IDE device, then you probably need this module. I
don't have any parallel IDE devices, but I'm sure there is some help out
there. Maybe for starters, read:
/usr/src/linux/Documentation/paride.txt

the modules.conf file is empty and the rc.modules file seems to have everything commented out

i think that the modules may be loading from the default installation, when i recompiled i probably disabled or broke these modules in some way. how do i stop these modules from running?

When you recompiled the kernel, did you do (in this oder):

make (x|menu)config
make dep
make bzImage
make modules
make modules_install

If not, you didn't make the new kernel modules, or you didn't install the new kernel modules. This needs to be done or you will get (at least) failed dependencies.

The /etc/modules.conf file it empty by default, you need to add modules that you would like to be dynamic.
man modules.conf will give you information on how to get it working.


I just noticed that I didn't answer your third question. . .
Onboard audio can be a real pain. First, you need to find out what chipset it's using. Once you know your chipset, point your browser to: http://www.alsa-project.org/
They're doing a pretty good job of getting sound working for a variety of chipsets.