Ticket #1352

Mark M. Hoffman mhoffman at lightlink.com
Tue Aug 5 00:51:35 CEST 2003


* Jean Delvare <khali at linux-fr.org> [2003-08-04 20:38:15 +0200]:
> 
> > For the BIOS, I have is the latest version. Therefore, this is not
> > the solution.
> 
> Wrong. You can have the latest BIOS and this BIOS can be dead broken.
> Wouldn't be the first time, nor the last. It's especially possible on
> recent hardware.
> 
> BTW, is there any monitoring information shown in the BIOS screens (boot
> time and setup)?
> 
> > I also tried the new 2.6.0-test2 kernel and I got some improvements : 
> > now it detects the SMBus but it says it is disabled.

Ugh.  That's too bad...

> > Here is the output of lspci -vv:
> > 
> > 00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016
> >     Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
> >     ParErr- 
> > Stepping- SERR- FastB2B-
> >     Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
> > <TAbort- <MAbort- >SERR- <PERR-
> >     Interrupt: pin B routed to IRQ 10
> >     Region 4: I/O ports at 1000 [disabled] [size=32]
> > 
> > The IRQ is 10 which is the same as the Firewire and the CardBus 
> > controllers. However, I didn't compile Firewire and CardBus in the 
> > kernel. Therefore, I don't think it is an IRQ conflict.

Do `cat /proc/ioports` to see if anything collides with 0x1000-0x101f.
If it's some device you don't use, try completely disabling that device
in the BIOS.  Otherwise (unless Jean's hints work) I think you're out of
luck, sorry.

> It could be linked to ACPI. Linux ACPI support includes an alternative
> IRQ routing system, which sometimes solves this kind of problems. If you
> don't use ACPI yet, I think it could be a good time to give it a try.
>   http://sourceforge.net/project/showfiles.php?group_id=36832
> Make sure you use the latest version. Note that real ACPI support
> doesn't exist in Linux 2.4 before 2.4.22-pre4 or so.
> 
> Likewise, if you *do* use ACPI on your laptop, you could try disabling
> it for a short time and test if lm_sensors then works, or pass some
> parameter to your kernel that change how ACPI works:
>   http://sdb.suse.de/en/sdb/html/81_acpi.html
> 
> I'm only guessing, maybe it won't help at all.

Regards,

-- 
Mark M. Hoffman
mhoffman at lightlink.com



More information about the lm-sensors mailing list