On Wed, Jan 10, 2007 at 10:38:37PM -0500, David Shultz wrote:
it looks like fb_nvidia_i2c came in 2.6.12 per:
http://www.mailarchives.org/list/debian-kernel/msg/2005/04040
so it should be in etch
I'll try etch then. If still have the problem then will try sid. Thanks to
all forum
David Shultz wrote:
Sorry for late reply.
On 1/9/07, Wackojacko [EMAIL PROTECTED] wrote:
Install the package lm-sensors and run sensors-detect, it will even
write the modules to /etc/modules for you
That's nice, but if hardware is not autodetected at boot or at very least during
Debian
On 1/10/07, Marty [EMAIL PROTECTED] wrote:
The graphics card obvious has to participate, but I don't see the driver
for the graphics card i2c. It may be there but I don't know what it's
called. I think in my case it's called fb_radeon_i2c, so I would expect
to see something like fb_nv_i2c.
So
modprobe fb_nvidia_i2c
On 1/10/07, David Shultz [EMAIL PROTECTED] wrote:
On 1/10/07, Marty [EMAIL PROTECTED] wrote:
The graphics card obvious has to participate, but I don't see the driver
for the graphics card i2c. It may be there but I don't know what it's
called. I think in my case it's
David Shultz([EMAIL PROTECTED]) is reported to have said:
On 1/10/07, Marty [EMAIL PROTECTED] wrote:
The graphics card obvious has to participate, but I don't see the driver
for the graphics card i2c. It may be there but I don't know what it's
called. I think in my case it's called
modprobe fb_nvidia_i2c
I did exactly that it gives an error message:
FATAL: Module fb_nvidia_i2c not found.
I may have missed it. What kernel are you running?
I'm using kernel 2.6.8-3-386
David Shultz wrote:
modprobe fb_nvidia_i2c
I did exactly that it gives an error message:
FATAL: Module fb_nvidia_i2c not found.
I may have missed it. What kernel are you running?
I'm using kernel 2.6.8-3-386
I don't see it for 2.6.8 although there is an fb_riva_i2c, which is probably
On Wed, Jan 10, 2007 at 06:26:43PM -0500, Marty wrote:
David Shultz wrote:
modprobe fb_nvidia_i2c
I did exactly that it gives an error message:
FATAL: Module fb_nvidia_i2c not found.
I may have missed it. What kernel are you running?
I'm using kernel 2.6.8-3-386
I don't see it
it looks like fb_nvidia_i2c came in 2.6.12 per:
http://www.mailarchives.org/list/debian-kernel/msg/2005/04040
so it should be in etch
I'll try etch then. If still have the problem then will try sid. Thanks to
all forum members for their help. I really appreciate it.
Marty wrote:
David Shultz wrote:
On 1/7/07, Marty [EMAIL PROTECTED] wrote:
I see where the Display Data Channel (or DDC protocol, which IDs your
monitor) module (ddc) is loaded, but none of the output. Maybe you
are missing the I2C drivers for your motherboard or the graphics card
drivers,
Sorry for late reply.
On 1/9/07, Wackojacko [EMAIL PROTECTED] wrote:
Install the package lm-sensors and run sensors-detect, it will even
write the modules to /etc/modules for you
Okay, I did that and:
lsmod | grep i2c
i2c_sensor 2944 2 w83627hf,eeprom
i2c_isa
On 1/7/07, Marty [EMAIL PROTECTED] wrote:
I see where the Display Data Channel (or DDC protocol, which IDs your
monitor) module (ddc) is loaded, but none of the output. Maybe you
are missing the I2C drivers for your motherboard or the graphics card
drivers, both of which are required. I would
David Shultz wrote:
On 1/7/07, Marty [EMAIL PROTECTED] wrote:
I see where the Display Data Channel (or DDC protocol, which IDs your
monitor) module (ddc) is loaded, but none of the output. Maybe you
are missing the I2C drivers for your motherboard or the graphics card
drivers, both of which are
On Sat, 06 Jan 2007 22:18:25 -0500
Paul Bransford [EMAIL PROTECTED] wrote:
LCD monitors have a fade time between pixel changes, usually
measured along the order of 8-10 ms (100 ms in a second)
Typo: you missed a 0. There are 1000 ms in a second.
Regards,
Andrei
--
If you can't explain it
David Shultz wrote:
[..]
I really want it to be resolved and use debian. Is there anything else I
need to
do?
--David
Try to understand if direct render is properly working
Have a look to xorg log file !
--
The difference between theory and practice is not as great in theory as
in pratice
On Sat, Jan 06, 2007 at 09:36:32PM -0500, David Shultz wrote:
I'm a newbie and having a bit of problem. I have a debian sarge
system(amd64 3400, 1gb RAM and MSI K8T Neo-FIS2R mobo and samtron
76V crt monitor) with visiontek's xtasy 6564 powered by nvidia geforce3
Ti200(64mb ddr
On 1/7/07, Chris Bannister [EMAIL PROTECTED] wrote:
Did you dpkg-reconfigure xserver-xfree86, maybe the monitor is not
detected correctly
Yes I did dpkg-reconfigure xserver-xfree86 and used the vertical
and horizontal sync rate from LG's website(given below):
David Shultz wrote:
On 1/7/07, Hal [EMAIL PROTECTED] wrote:
Have a look to xorg log file !
I don't find anything maybe because i'm a newbie. if you could look at my
XFree86.0.log I would appreciate it:
I see where the Display Data Channel (or DDC protocol, which IDs your monitor)
module
I'm a newbie and having a bit of problem. I have a debian sarge
system(amd64 3400, 1gb RAM and MSI K8T Neo-FIS2R mobo and samtron
76V crt monitor) with visiontek's xtasy 6564 powered by nvidia geforce3
Ti200(64mb ddr memory). Also had installed nvidia driver. Recently
I've replaced that monitor
On Sat, 2007-01-06 at 21:36 -0500, David Shultz wrote:
I'm a newbie and having a bit of problem. I have a debian sarge
system(amd64 3400, 1gb RAM and MSI K8T Neo-FIS2R mobo and samtron
76V crt monitor) with visiontek's xtasy 6564 powered by nvidia
geforce3
Ti200(64mb ddr memory). Also had
First of all, thanks for your reply.
Doesn't sound so much like a video problem as you are experiencing a
trait of LCD monitors.
LCD monitors have a fade time between pixel changes, usually measured
along the order of 8-10 ms (100 ms in a second)
This is paticularly visible if you move your
21 matches
Mail list logo
