Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Linux installation: IRQs and IORs and such




John Chambers wrote in a message to Mike Bilow:

 JC> While  contemplating  a  major  upgrade  of  this  linux, 
 JC> I've  been wondering:   Is  there a straightforward way to
 JC> get all the IRQ, IOR, and other such config information out
 JC> of the  current  linux  system?

cat /proc/interrupts
cat /proc/ioports

 JC> The  install  instruction 
 JC> seem to generally suggest that you use the W95 tools.  But
 JC> this seems to mean wandering  around  in  a  maze  of little
 JC> windows  (all  alike), writing things down by hand, and
 JC> never being sure that you've got it all.

You forgot "twisty."

 JC> Since the linux
 JC> kernel must  also know  all that stuff (else it couldn't
 JC> access the hardware), it seems that there oughta be a way to
 JC> dig it out and print out a copy for use in building the next
 JC> kernel.

There is a rich wealth of information in the /proc filesystem.

 JC> There are a few such numbers in /etc/boot.log, but  not 
 JC> nearly  all. I've dug around in various HOWTOs with no luck.

 JC> Another possibility, of course, is that W95 has a way  to 
 JC> produce  a summary  table.   But I haven't stumbled across a
 JC> clue that they ever thought of such a thing, and their
 JC> philosophy does seem to be one  of lots of little individual
 JC> config windows.

You can print some info from the Windows 95 Device Manager, found in System in
Control Panel.  Be aware that Linux and Windows 95 may not share the same view
of hardware, especially when devices are configurable in software as with PCI,
PnP, or PCMCIA.
 
-- Mike





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org