Public SourceMage Discussion List

["Sergey A. Lipnevich" <sergeyli AT pisem.net>]

I'd turn to /proc for information, it lists PCI devices
and can provide insight into what does the PCI
subsystem acually "see". You should have certain files
in there, I don't remember now, that contain info.
The easy way out is to try one of the CD distributions,
I'm looking at knoppix and SoL right now, and see what
they say. You can also boot from SMGL CD and list
through /proc in the shell.
HTH.

--Sergey.

Spencer Ogden <spencero AT mail.utexas.edu>:

> Not sure if the mssage below got through, soory if it
some how comes
> through multiple times, I think I had the wrong
address....
>
> So I got SM installed on my laptop, I had to use the
harddrive transplant
> method as the laptop has no external drives.
>
> So far so good, it boots up on its own. I am unable
to get the built in
> ethernet working however.  I am pretty sure it is
based on the sis900
> chip, which I have compiled a module for. When I do a
`modprobe sis900` I
> get (paraphrased):
>
> ...sis900.o : init_module: No such device
> Hint: insmod errors can be caused by incorrect module
parameters, including
>
> invalid IO or IRQ parameters.
> ....
>
>
>
> So first question is, Are there tools in the base
install which would let
> me list the pci bus and try to find out what is on
what IRQ? Can this be
> done through /proc?
>
> Second, I see a lot mention of IRQ 11 being found and
being shared in
> dmesg. Is it possible a shared IRQ is causing the
problem? The BIOS in
> zero help interms of giving an IRQ listing at start
up or allow me to
> disable internal components.
>
> Would I be better off just trying to get my wireless
PC Card working first?
>
>
> Spencer
>
>
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>
> 



Sergey Lipnevich, MCSE, SCPJ,
Sr. Software Engineer,
New Age Network New York, Inc.,
+1-848-459-LIPN.