Ticket #920

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm stumped.
If i2cdump works then i2c-voodoo3 is working fine.
Don't know what the scanline problem is either.
If you load eeprom instead of ddcmon, then look in
/proc/sys/dev/sensors/eeprom-i2c-2-50,
do you see the same data you saw in i2cdump?


Vesselin Dimitrov wrote:
> 
> On Monday 24 June 2002 04:26, you wrote:
> > sorry, I meant 2 not 0.
> >
> > Since i2cdump works (you can see "FLATRON" for example)
> > but ddcmon doesn't, the problem is in ddcmon.
> >
> > Sensors always says the same thing?
> > It doesn't ever work?
> >
> Always.
> I think that the problem may be in i2c-voodoo3.o because after
> # modprobe i2c-voodoo3
> some of the scanlines on the monitor are one pixel to the left of
> the others.



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux