ioscan on Linux

[Karthik S S]

Is there a ioscan equivalent available for Linux?? (I am not looking for lspci or cat /proc/devices).

Thanks,
Karthik S S

[Mark Grant]

No.

However, you can ... oh, you don't want that.

On the other hand, KDE has a rather funky information center that shows you all the hardware and information about it and I'm sure gnome does too. Don't expect to find any hardware paths though.

I might add that /proc is an extremely good interface into the kernel it is equivalent to "ioscan -fk"

[Steven E. Protter]

If there is going to be ioscan on Linux someone is going to have to write it.

If I were silly enough to bang my head on that one I'd be forced due to OS limitations to use the tools mentioned above as the underlying methodology for getting the hardware information.

Most distributions do come with a pretty decent gui point and click hardware tool now.

SEP

[Paul Cross_1]

It is amazing how often this question comes up..! If you are looking for the equiv to the HP/UX ioscan for linux it doesn't exist. however, there are lots of tools that do roughly the same thing. As I have mentioned before, hwinfo works very well, it is a suse only tool however. I'm sure RH has equivalents.

[Tim Sanko]

Karth,

Tools exist to show you what exists. I don't believe that there are tools that work with the kernels to configure devices yet.

Tim

[Martin P.J. Zinser · Accepted solution]

Hello Karthik,

howabout lshw at

http://ezix.sourceforge.net/software/lshw.html

This has an "ioscan like" output.

Greetings, Martin

[Karthik S S]

make returns the following error upon compilation of lshw and exits ,

c++ -g -Wall -c options.cc -o options.o
c++ -g -Wall -c lshw.cc -o lshw.o
c++ -g -Wall -c usb.cc -o usb.o
usb.cc: In function `string BCDversion (short unsigned int)':
usb.cc:216: `snprintf' undeclared (first use this function)
usb.cc:216: (Each undeclared identifier is reported only once for each
function it appears in.)
make: *** [usb.o] Error 1
[root@linux2 lshw-A.01.06]#

Pl. help.

Thanks,
Karthik S S

[Mark Grant]

Well, I find this hard to believe but if I were you, I'd have a look at "usb.cc" and see if it has a "#include " somewhere near the top, or includes another file that does.

[Karthik S S]

Thanks for the link Martin.

Mark:
You are great. Yes .. that file was missing the following line,

#include

it works great now ..!!!

Thanks again,
Karthik S S

[John Meissner]

wow... great work. I did a quick search for this and it works great! very good fix with the missing line too guys