From: "Steven A. DuChene" <sduchene@mindspring.com>
To: Thomas Hood <jdthood@mail.com>
Cc: linux-kernel@vger.kernel.org, stelian.pop@fr.alcove.com,
ion@cs.columbia.edu, sduchene@mindspring.com, jurgen@botz.org
Subject: Re: [PATCH] PnP BIOS -- bugfix; update devlist on setpnp
Date: Tue, 16 Oct 2001 22:48:45 -0400 [thread overview]
Message-ID: <20011016224845.C1225@lapsony.mydomain.here> (raw)
In-Reply-To: <1002987648.764.23.camel@thanatos>
In-Reply-To: <1002987648.764.23.camel@thanatos>; from jdthood@mail.com on Sat, Oct 13, 2001 at 11:40:10AM -0400
Thomas:
Just to let you know I still have the same problem with a resource conflict
between the PnPBIOS code and the i2c/lm_sensors stuff at 1040 with this
latest patch. Again, this is on a Intel Lancewood (L440GX) motherboard.
I also have a system with a Intel STL2 motherboard (successor to the
Lancewood) so I will test that under the same conditions later tonight.
modprobe i2c-piix4
/lib/modules/2.4.10-ac12/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-ac12/kernel/drivers/i2c/i2c-piix4.o: insmod /lib/modules/2.4.10-ac12/kernel/drivers/i2c/i2c-piix4.o failed
/lib/modules/2.4.10-ac12/kernel/drivers/i2c/i2c-piix4.o: insmod i2c-piix4 failed
dmesg
.
.
.
i2c-piix4.o version 2.6.1 (20010830)
i2c-piix4.o: Found PIIX4 device
i2c-piix4.o: SMB region 0x1040 already in use!
i2c-piix4.o: Device not detected, module not inserted.
cat /proc/ioports
.
.
.
0c00-0c3f : Intel Corporation 82371AB PIIX4 ACPI
0c00-0c3f : PnPBIOS PNP0c02
0ca0-0ca3 : PnPBIOS PNP0c02
0cb8-0cbf : PnPBIOS PNP0c02
0cf8-0cff : PCI conf1
1000-103f : PnPBIOS PNP0c02
1040-105f : Intel Corporation 82371AB PIIX4 ACPI
1040-104f : PnPBIOS PNP0c02
.
.
.
--
Steven A. DuChene sad@ale.org
linux-clusters@mindspring.com
sduchene@mindspring.com
http://www.mindspring.com/~sduchene/
next prev parent reply other threads:[~2001-10-17 2:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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-16 3:27 ` [PATCH] PnP BIOS patch against 2.4.12-ac2 Thomas Hood
2001-10-16 7:58 ` Jörg Ziuber
2001-10-16 21:44 ` Thomas Hood
2001-10-17 6:28 ` Jörg Ziuber
2001-10-17 13:41 ` Thomas Hood
2001-10-17 14:43 ` Jörg Ziuber
2001-10-17 20:43 ` Thomas Hood
2001-10-15 14:15 ` [PATCH] PnP BIOS -- bugfix; update devlist on setpnp Ion Badulescu
2001-10-17 2:48 ` Steven A. DuChene [this message]
2001-10-17 3:14 Thomas Hood
2001-10-17 8:10 ` Steven A. DuChene
2001-10-17 16:04 ` Gunther Mayer
2001-10-17 20:58 ` Thomas Hood
2001-10-17 13:35 ` Thomas Hood
2001-10-17 16:08 ` 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=20011016224845.C1225@lapsony.mydomain.here \
--to=sduchene@mindspring.com \
--cc=ion@cs.columbia.edu \
--cc=jdthood@mail.com \
--cc=jurgen@botz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stelian.pop@fr.alcove.com \
/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
all inboxes | Powered by JetHome®