From: Roy-Magne Mo <rmo@sunnmore.net>
To: Willem Riede <wriede@home.com>
Cc: German Gomez Garcia <german@piraos.com>,
Dan Hollis <goemon@anime.net>,
Mailing List Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: More on the 760MP
Date: Wed, 17 Oct 2001 00:40:28 +0200 [thread overview]
Message-ID: <20011017004028.G8329@akkar.interpost.no> (raw)
In-Reply-To: <20011013102128.A1414@linnie.riede.org> <20011014164913.A1428@linnie.riede.org>
In-Reply-To: <20011014164913.A1428@linnie.riede.org>
On Sun, Oct 14, 2001 at 04:49:13PM -0400, Willem Riede wrote:
> I'm not having much luck with this :-(
>
> I also have a Tyan Tiger MP, and have built a 2.4.10-ac12 based kernel
> for it. Actually, I modified the Rawhide kernel SRPM to use linux-2.4.10
> and the ac12 patch, as I run ext3 and software raid installed by RedHat's
> Roswell beta, and I need to stay compatible with that; then made and
> installed the athlon-smp RPM.
>
> It contains 2.6.1 for i2c, and I generated the patch for lm_sensors
> 2.6.1 to replace the older patch for lm_sensors in the SRPM.
>
> The i2c-amd756 module hangs my kernel too, but you seem to have it
> work without it? I don't get anything detected without i2c-amd756.
> This is what the log messages say (but I have to reboot to read them):
>
> Oct 14 16:17:16 linnie kernel: i2c-amd756.o version 2.6.1 (20010830)
> Oct 14 16:17:16 linnie kernel: i2c-dev.o: Registered 'SMBus AMD7X6 adapter
> at 80e0' as minor 1
> Oct 14 16:17:16 linnie kernel: i2c-core.o: client [W83782D chip] registered
> to adapter [SMBus AMD7X6 adapter at 80e0](pos. 0).
> Oct 14 16:17:16 linnie kernel: i2c-core.o: client [W83782D subclient]
> registered to adapter [SMBus AMD7X6 adapter at 80e0](pos. 1).
> Oct 14 16:17:16 linnie kernel: i2c-core.o: client [W83782D subclient]
> registered to adapter [SMBus AMD7X6 adapter at 80e0](pos. 2).
>
> Or is it this module (i2c-amd756) that you say must be included in the
> kernel to make 'it' work (English is so ambiguous :-))?
>
> One more question if you don't mind: do you (still) have to first
> read the sensors in the BIOS before booting? If I do that, for some
> reason, I don't get my grub boot screen after exiting setup, instead
> the board tries to boot off the lan; I ctrl-atl-del out of that, and
> then things are back to normal, but that soft reset probably undid
> whatever reading the sensors in the bios changed :-(
> Any other settings in the bios that matter?
I've turned on APIC in bios and kernel, set all parallel ports and
serial ports to auto in BIOS and removed support parllel ports in the
kernel. I'm now able to insert the drivers unpatched from lm_sensors
cvs-version.
Seems like it's the autoprobing in the parallel driver that messes it
up.
--
carpe noctem
next prev parent reply other threads:[~2001-10-16 22:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011013102128.A1414@linnie.riede.org>
2001-10-14 20:49 ` More on the 760MP Willem Riede
2001-10-14 20:59 ` German Gomez Garcia
2001-10-14 21:45 ` Stephen Frost
2001-10-15 14:01 ` German Gomez Garcia
2001-10-15 14:32 ` Jan-Benedict Glaw
2001-10-16 22:40 ` Roy-Magne Mo [this message]
2001-10-09 21:00 German Gomez Garcia
2001-10-09 21:18 ` Dan Hollis
2001-10-09 21:32 ` German Gomez Garcia
2001-10-09 21:37 ` Dan Hollis
2001-10-09 22:20 ` German Gomez Garcia
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=20011017004028.G8329@akkar.interpost.no \
--to=rmo@sunnmore.net \
--cc=german@piraos.com \
--cc=goemon@anime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wriede@home.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