All of lore.kernel.org
 help / color / mirror / Atom feed
From: mail@hiereinwerfen.de (Torsten)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Implementation of FSCSCY?
Date: Sat, 18 Feb 2006 16:57:58 +0000	[thread overview]
Message-ID: <43F75216.9040309@hiereinwerfen.de> (raw)

Hello,

I'm really new to linux, so please be patient... ;)

I've got a FSC Dual-Mainboard (D1306) on which I'm trying to setup a
server-system based on the actual Ubuntu ("Breezy Badger"). So the
kernel must be a 2.6.

The board contains a "Scylla"-chip, which is found by sensors-detect. As
far as I found within the docs, this must be ok, because the developer
of the required module "fscscy" notes, the driver is "beta" but
well-tested on exactly THIS board.

Anyway, sensors-detect wants to load "fscscy" in modules.conf, but this
module doesn't exist!
The only module next to piix4 ist "eeprom" which doesn't seem to be very
useful...

I searched the whole drive, but only found the note mentioned above.
Google didn't come out with more and I couldn't find an open bug/ticket...

Where can I get it and why is it missing?

PS: Another strange thing, when installing piix4, the bootlog shows
something about "unusual config register value" and I should set
"fix_hstcfg=1". When I do so, sensors-detect searches longer and finds
more... Anyway, the only new modules to load are smbus-arp (for which
the doc reads "if you don't know what this is you don't need it"???) and
another unsupported chip called Philips "PCA9556". :-(

cu/2
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3635 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060218/ea2b79f6/smime.bin

             reply	other threads:[~2006-02-18 16:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18 16:57 Torsten [this message]
2006-02-24 19:42 ` [lm-sensors] Implementation of FSCSCY? Tom
2006-03-05 20:24 ` Rudolf Marek
2006-03-06 22:07 ` Tom
2006-03-23 22:31 ` Rudolf Marek
2006-03-25 13:16 ` Tom

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=43F75216.9040309@hiereinwerfen.de \
    --to=mail@hiereinwerfen.de \
    --cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.