On Tuesday 24 July 2007 20:03:04 Rajko M. wrote:
> On Monday 23 July 2007 22:41, [EMAIL PROTECTED] wrote:
> > On Sunday 22 July 2007 14:35:07 Rajko M. wrote:
> > > On Saturday 21 July 2007 22:24, you wrote:
> > > ....
> >
> > OK Rajko, I am going to trim this post quite a bit. All read over several
> > times and thoroughly digested. I hope that won't mess you up. I will
> > confine it to providing information and questions.
> >
> > OK, ran   ls /sys/bus/i2c/devices/9191-0290 and the following was listed
> > in that directory.
> >
> > [EMAIL PROTECTED]:~>  ls /sys/bus/i2c/devices/9191-0290
> > alarms           fan3_div            in2_max    in8_input   
> > temp1_max_hyst beep_enable fan3_input         in2_min      in8_max    
> > temp1_type beep_mask   fan3_min            in3_input   in8_min     
> > temp2_input bus               hwmon:hwmon0  in3_max    name        
> > temp2_max driver            in0_input            in3_min     power
> > temp2_max_hyst fan1_div       in0_max             in4_input    pwm1
> > temp2_type fan1_input    in0_min              in4_max     pwm2
> > temp3_input fan1_min      in1_input            in4_min      pwm3
> > temp3_max fan2_div       in1_max             in7_input   subsystem
> > temp3_max_hyst fan2_input    in1_min              in7_max     
> > temp1_input temp3_type fan2_min      in2_input            in7_min      
> > temp1_max uevent [EMAIL PROTECTED]:~>
> >
> > As you can see....there is no vrm and I guess is not compiled in
> > andsensors-s will never see it.
>
> OK.
> Than we can forget it for now.
>
> ....
>
> > > *** Missing ***
> > > We don't have sensors output with default values.
> >
> > Not absolutely sure but I think my first posting was from the default
> > values.
>
> OK.
>
> ....
>
> > OK I cut and pasted your suggested/trial parameters into the one line
> > sensors.conf and ran sensors -s. (as root) Got another error:
> >
> > EasyStreet:/ # sensors -s
> > Error: Line 4: Invalid keyword
> > General parse error
> >
> > I looked at until my eyes glazed over. I can't see it.
> >
> > Here are the first few lines from your suggested conf that reportedly
> > contains the error:
>
> Hmm... The only thing I can see is missing comments behind statemets in
> original sensors.conf, so it would be "sensors -s" parser problem. Try the
> same proposal when you remove all comments behind statements like in
> example below.
>
> chip "w83627thf-*"
> # Voltage section    
>     label in0 "VCore"
>       set in0_min 1.50    
>       set in0_max 1.56    
>
>     label in1 "+3.3V"
>       set in1_min 3.14
>       set in1_max 3.47
>
Rajko,

Nope. Didn't work. Got this:
EasyStreet:/ # sensors -s
Error: Line 4: Invalid keyword
flex scanner jammed

I think that I will just start all over again with my original sensors.conf 
including a new scan of the chip. Will let you know in a couple of days how I 
made out.

Bob S.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to