On Tue, Jun 03, 2003 at 08:38:01AM -0500, David wrote:
> I don't have that board, but now that you have gentoo-sources. Yes I would
> compile as a module for the kernel. And emerge i2c and lm_sensors.
>
> I believe the i2c emerge is for the user-mode tools or something like that.
No, there are no user-mode tools for the i2c package, only for lm-sensors.
If you're using the recent gentoo-sources, you shouldn't need to emerge i2c
at all. (I have it emerged because I didn't understand this until recently.)
> After all is said and done you can run 'sensors-detect' as root
>
> #sensors-detect
> [...]
>
> Follow thru the prompts, then it will tell you what to include in your
> /etc/config files. You will also need to make a folder called /etc/sysconfig
> and it will put a file called lm_sensors in there, that basically has just
> this:
> #MODULE_0=i2c-viapro
> MODULE_1=i2c-isa
> #MODULE_2=lm80
> #MODULE_3=eeprom
> MODULE_4=via686a
In the case of the A7V8X, the lines I got were:
MODULE_1=i2c-viapro
MODULE_2=w83781d
MODULE_3=smbus-arp
Unfortunately, the board doesn't seem to understand the eeprom driver; if
it does, it's at some odd address that isn't probed. And you have to use
the w83781d driver, which has the best attempt at supporting the as99127f
that is actually on board the Asus board. (And for which there are many
complaints about Asus' lack of provided documentation.)
> Then there is a file /etc/sensors.conf that you will have to configure your
> offsets and such to calibrate the readings and change names. Scroll thru to
> find your sensor stuff. I used the chip "via686a-*" section for mine. You
> might even find something like CPU and SYS temp switch (they will call it
> temp1 and temp2 you can edit how they display by changing the label:
> label temp1 "CPU Temp" ,,,,, you can also choose not to display one by:
> ignore temp3. The best thing is to figure out what you want to show,... then
> if you have a similar program in windows or in bios, see what everything is
> at idle and go back to /etc/sensors.conf and configure them to the same.
In the case of the A7V8X, the section you have to modify is the one
that starts with 'chip "as99127f-*"'. The labels you need are:
label temp1 "Board"
label temp2 "CPU"
label temp3 "Power"
label fan1 "CPU Fan"
label fan2 "Pwr Fan"
label fan3 "Cha Fan"
If you don't have thermal monitoring on the power supply, you can do
'ignore temp3' instead. Also, from the comparisons I've made with Asus'
own temperature algorithm in the BIOS, you need to use the alternate
computation algorithm for temperature 2:
compute temp2 (@*30/43)+25, (@-25)*43/30
This should already be in the sensors.conf file, just commented out.
Uncomment it, and comment out the first 'compute temp2' entry instead.
> On Tuesday 03 June 2003 03:59 am, Paulo Jorge de Oliveira Cantante de Matos
> wrote:
> > Hi Bryan,
> >
> > I had vanilla sources but I'll now compile gentoo-sources. Should I
> > compile everythingof i2c as modules? ou everything built in the kernel
> > or just the core? If I do this, do I still need to emerge i2c?
Build all of i2c as modules in the kernel. If you're using gentoo-
sources 2.4.20-r1 or higher, you shouldn't need to emerge i2c; as I said
before, I did emerge it, but I didn't understand that it shouldn't be
needed at the time.
> > Oh, thanks god someone has a A7V8X. Is your on board sound working? How?
> > What do you need to compile in the kernel?
I'm using ALSA for the on-board sound. So I compiled the basic 'Sound
card support' into the kernel, and nothing else. (In theory, the VIA
82c686 Audio Codec in the kernel will likely work, but I haven't tried
the OSS version.)
In ALSA, you just need the snd-via82xx driver (and all the ones it
will automatically include), along with the snd-mixer-oss and snd-pcm-oss
drivers for the OSS emulation.
There is one caveat: the 0.9.2 ALSA driver seems to not play well with
the SDL libraries. As I understand it, there's some problem with the way
it responds to timeouts on the select() call. This results in the sound
playing too fast and sounding somewhat rough. The 0.9.0_rc2 driver didn't
have this problem, and I haven't tried anything more recent yet, so I
can't say if it's been fixed. For programs like mplayer, you can usually
work around it by simply telling it not to use SDL; 'mplayer -ao alsa9 ...'
will work.
Unfortunately, the ALSA driver doesn't appear to have a simple
'ChangeLog' file that I can check.
---------------------------+---------------------------------------------------
Bryan Feir VA3GBF|"The professor holds the keys to the gates of
Home:[EMAIL PROTECTED] | knowledge; not to let the student in, but to let
| him get out and on to better things." -- Leacock
---------------------------+---------------------------------------------------
--
[EMAIL PROTECTED] mailing list
