Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #13466
| From | Avoid9Pdf@gmail.com |
|---|---|
| Newsgroups | comp.os.linux.misc, alt.os.linux.slackware, alt.os.linux.debian |
| Subject | Re: Hk Cqvst wrote: nVidia + gamma !FIXED! |
| Date | 2015-01-20 18:47 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <m9m7sg$vs1$1@dont-email.me> (permalink) |
| References | <m9jf2n$pq3$2@dont-email.me> |
Cross-posted to 3 groups.
In article <m9jf2n$pq3$2@dont-email.me>, Rich <rich@example.invalid> wrote: > > xset s off > > xset -dpms > > 'fixed it' but before I die I want to KNOW why/what. > > > > Why should the <video driver> go from good after boot, to bad after > > the system is left unattended? And that <disable/prevent the > > sleep-mode> avoids the problem? > > A bug in the video driver code, related to how the driver enables > dpms[1] turn off/turn on, for your specific revision of the video chip. > There is likely some register value that your chip revision needs set a > certian way, and the driver simply is not setting it the right way. > > Determining any more of a "why" than the above will require you to: > > 1) start digging into the C code for the video driver for your chip; > 2) have available to detailed programming specs. from the > manufacturer for your specific model/revision, including all > erratta. > 3) hope that the documentation is complete and accurate > > > It's been running for 3 days beeootifully. > > > Is the video-driver inside the > > 4940304 2009-08-17 07:53 vmlinuz-huge-smp-2.6.29.6-smp > > or in the case of the few-months OLDER version which does NOT have the > > problem, inside the <initrd.gz> > > Part of the compiled binary of the driver is in one or the other. the > remainder is within the X server driver. The compiled binaries will do > you no good if you truly want to know "why". You'll have to dig into > the C code for the answer to that question. > > > [1] I point at dpms here because dpms is the mode that requires > programming the chipset to do something special. There's a bug there > somewhere from the sounds of things. Remember the other quirk: that their's no problem, when a CRT is plugged instead of the new LED:1920x1080. -- My Windows-using mate insists that the vga is bidirectional; ie. that the display informs the PC <what settings it needs>. Since the modern LED:1920x1080 is forced to comply with the OLD vga spec. [and pin-out}, I don't believe him.
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Hk Cqvst wrote: nVidia + gamma !FIXED! not.socialnetwork@gmail.com - 2015-01-19 13:43 +0000
Re: Hk Cqvst wrote: nVidia + gamma !FIXED! Rich <rich@example.invalid> - 2015-01-19 17:32 +0000
Re: Hk Cqvst wrote: nVidia + gamma !FIXED! Avoid9Pdf@gmail.com - 2015-01-20 18:47 +0000
Re: Hk Cqvst wrote: nVidia + gamma !FIXED! Jerry Peters <jerry@example.invalid> - 2015-01-20 21:16 +0000
Re: Hk Cqvst wrote: nVidia + gamma !FIXED! Unknown <dog@gmail.com> - 2015-01-21 11:59 +0000
Re: Hk Cqvst wrote: nVidia + gamma !FIXED! Rich <rich@example.invalid> - 2015-01-21 12:17 +0000
Re: Hk Cqvst wrote: nVidia + gamma !FIXED! no.top.post@gmail.com - 2015-01-27 19:25 +0000
Re: Hk Cqvst wrote: nVidia + gamma !FIXED! Jerry Peters <jerry@example.invalid> - 2015-01-21 21:18 +0000
Re: Hk Cqvst wrote: nVidia + gamma !FIXED! "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2015-01-20 16:50 -0500
csiph-web