|[Home] [Credit Search] [Category Browser] [Staff Roll Call]||The LINUX.COM Article Archive|
|Originally Published: Tuesday, 24 October 2000||Author: Mike Baker|
|Published to: interact_articles_irc_recap/IRC Recap||Page: 1/1 - [Printable]|
Best of IRC for Tuesday, October 24th
It's time once again for another edition of Best of IRC. As always, we'll be taking an in-depth look at some of the questions asked on #Linuxhelp.If you haven't already been to #Linuxhelp, you'll find instructions on how to get there at the bottom of the Live! page; feel free to stop by and ask questions or possibly even answer a few. We appreciate any help we can get.
|Page 1 of 1|
isapnpWell, there's a how-to about anything ;-)
Expansion cards come in many forms, long and short, but did you know that there are different types of cards? I'm not talking about the difference between a video card and a sound card; I'm talking about the difference between ISA and PCI.
ISA (Industry Standard Adapter) is the precursor to PCI (Peripheral Connect Interface), and the source to many configuration headaches. ISA was one of the old original protocols designed in the days when you probably had a list of open ports taped to the inside of your PC. The original ISA cards had jumpers, and lots of them; designed to configure everything from IO to IRQ and in some cases even DMA. Configuration of these cards was downright confusing at times;thankfully, the idea of plug-and-play soon followed. ISA cards were now at least somewhat intelligent in that you could change the settings via software. Later PCI came along and suddenly everything automatically configured itself and even identified itself to the opperating system.
Unfortunately, we still need to deal with ISA at times, and to do that under Linux requires the use of a set of utilities called isapnp-tools. The isapnp-tools set consists of two items: pnpdump and isapnp. The basic idea to getting an ISApnp device working is to create an isapnp.conffile, run isapnp to load the settings then load the appropriate module. Let's take the example of setting up a Soundblaster Awe 32 card:
First, we need to create a configuration file for isapnp; this is basically a one-time thing that we only need to do when we're adding more ISA hardware.
The file format is simple; the only part you should need to concern yourself with is the individual card configuration. The card configuration starts at the CONFIGURE line; this includes a card identifier followed by a set of resources.Each resource is in the format (<type> <resource number> (<resource setting>)), and there will be comment lines before theresource setting to show you what the possible values are. You only need to change the settings if you find the settings generated by pnpdump's --config option didn't work.
The next thing you'll want to do is to try these settings by running isapnp. On most systems, the startup sequence will check for a /etc/isapnp.conf and automatically run isapnp, so there's no point changing the startup scripts. To avoid rebooting we'll just run isapnp ourselves, though.
At this point you'll see some nicely formatted output telling you your cards have been initalized; this is our queue to load the module. Since the example we're doing is the Soundblaster Awe 32, we need to load the sb.o module and tell it where to find the card. The settings are the same as from the isapnp.conf file which are printed out again when running isapnp.
At this point, the our example card should be working. To avoid having to modprobe the sb module on startup each time, we can add the following lines to /etc/modules.conf (occasionally called /etc/conf.modules by different versions)
And there, in a nutshell, we've covered the basics of isapnp. Go amaze your friends with your newfound knowledge of Linux. For more information on plug-and-play and its uses under Linux, please check out the Plug-and-Play HOWTO.
|Page 1 of 1|