public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Steven A. DuChene" <sduchene@mindspring.com>
To: Thomas Hood <jdthood@mail.com>
Cc: linux-kernel@vger.kernel.org, sduchene@mindspring.com
Subject: Re: [PATCH] PnP BIOS -- bugfix; update devlist on setpnp
Date: Wed, 17 Oct 2001 04:10:14 -0400	[thread overview]
Message-ID: <20011017041014.B2015@lapsony.mydomain.here> (raw)
In-Reply-To: <1003288485.14282.100.camel@thanatos>
In-Reply-To: <1003288485.14282.100.camel@thanatos>; from jdthood@mail.com on Tue, Oct 16, 2001 at 11:14:44PM -0400

OK, I tried this with the Intel STL2 motherboard I also have and I got
a similar error when trying to load the correct i2c bus module when the
PnPBIOS stuff is compiled into the kernel.

modprobe i2c-piix4
/lib/modules/2.4.10-ac12pnp/kernel/drivers/i2c/i2c-piix4.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.10-ac12pnp/kernel/drivers/i2c/i2c-piix4.o: insmod /lib/modules/2.4.10-ac12pnp/kernel/drivers/i2c/i2c-piix4.o failed
/lib/modules/2.4.10-ac12pnp/kernel/drivers/i2c/i2c-piix4.o: insmod i2c-piix4 failed


dmesg
.
.
.
i2c-piix4.o version 2.6.1 (20010830)
i2c-piix4.o: Found OSB4 device
i2c-piix4.o: SMB region 0x580 already in use!
i2c-piix4.o: Device not detected, module not inserted.


cat /proc/ioports
.
.
.
04d0-04d1 : PnPBIOS PNP0c02
0580-058f : PnPBIOS PNP0c02
0840-084f : ServerWorks OSB4 IDE Controller
  0840-0847 : ide0
  0848-084f : ide1
0cd6-0cd7 : PnPBIOS PNP0c02
0cf8-0cff : PCI conf1
5000-50ff : ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC]
5400-543f : Intel Corporation 82557 [Ethernet Pro 100]
  5400-543f : eepro100
5440-547f : Intel Corporation 82557 [Ethernet Pro 100] (#2)
  5440-547f : eepro100
5800-58ff : Adaptec 7899P
6000-60ff : Adaptec 7899P (#2)
fe00-fe3f : PnPBIOS PNP0c02


So this is a problem on more than just those old Intel Lancewood L440GX
motherboards. The STL2 is a fairly recent dual processor motherboard
-- 
Steven A. DuChene	sad@ale.org
			linux-clusters@mindspring.com
			sduchene@mindspring.com

	http://www.mindspring.com/~sduchene/

  reply	other threads:[~2001-10-17  8:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-17  3:14 [PATCH] PnP BIOS -- bugfix; update devlist on setpnp Thomas Hood
2001-10-17  8:10 ` Steven A. DuChene [this message]
2001-10-17 13:35   ` Thomas Hood
2001-10-17 16:08     ` Steven A. DuChene
2001-10-17 16:04   ` Gunther Mayer
2001-10-17 20:58     ` Thomas Hood
  -- strict thread matches above, loose matches on Subject: below --
2001-10-13 15:40 Thomas Hood
2001-10-15  6:37 ` Jurgen Botz
2001-10-15  9:45   ` Stelian Pop
2001-10-15 12:01     ` Andrey Panin
2001-10-15 12:25       ` Alan Cox
2001-10-15 21:49         ` Thomas Hood
2001-10-15 14:15 ` Ion Badulescu
2001-10-17  2:48 ` Steven A. DuChene

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011017041014.B2015@lapsony.mydomain.here \
    --to=sduchene@mindspring.com \
    --cc=jdthood@mail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox