peasth...@shaw.ca wrote: >> Does Lenny with backports count as contemporary Debian? > > Encouraging information. Yes, I'd say Lenny is a contemporary > Debian. In this case a difficulty appears to be that automation > introduced in X is not quite perfect; yet.
Lenny is old stable with old version of X - it needs xorg.conf squeeze is current stable - newer version of X. > > Will guess that you have tried later systems and found problems > large enough to deter back to Lenny. The problems are solvable. What really matters is what kind of video chip you have on the board. If it's buggy - and there are a lot of buggy sh*t sold for cents out there- it doesn't matter what kind of linux you have - it most probably has the same X server code and same issues. I would try ubuntu as it is debian (experimental) and they are doing a lot of work to overcome such issues there > > From: deloptes <delop...@yahoo.com> > Date: Thu, 24 Nov 2011 16:00:31 +0100 >> For some monitors and setups ... like TV out you need to create a custom >> xorg.conf. There are tons of howtos and infos out there on how to do it. >> ... >> i.e. for intel put into /boot/grub/menu.lst video=i915:modeset=1 >> >> this helps X discover the outputs automatically. > > I'm missing some elementary concepts. Do you assume just one > monitor works from startup to shutdown? Are the possibilities of > both monitors showing one display concurrently or of switching > monitors while the system is running, on the agenda? I'll guess > that these cases require multiple X server processes; one for each > screen Certainly it must be within the scope of X but I've never > tackled it. Anyone know of a howto or info for this? No the example above shows how you can disable the frame buffer driver and enforce the use of the frame buffer from the intel driver (i915). > > The observed switch from external to internal displays on this > ThinkPad seems weird. X is overriding my BIOS setting. ThinkPad sounds like intel video chip. Just drop me e-mail in private and I'll attach my config > >> Mostprobably you experience clash between fb and normal driver > > I have an idea of a fb as here. > http://en.wikipedia.org/wiki/Framebuffer > And I have an idea of the driver as here. > http://en.wikipedia.org/wiki/Device_driver > You mean that the device driver software is not appropriate to the video > hardware? Or something more? > > Thanks to everyone for the replies, ... Peter E. I mean you need xorg.conf with configuration options that will solve your problem (if it's not an X.org bug) So my proposal is: download and try ubuntu and write back or drop me an e-mail and I'll send you my xorg.conf - and you'll get idea of the config needed try man intel or man <your video driver> to see what options you have. The problem with all this stuff is that manufacturers are saving money, so they are producing functional sh*t they sell in masses. Same for monitors ... and both video chip and monitor do not follow standards and requirements ... but what is more important? To sell or to produce perfect goods behind the competition? So when you have a bad video chip and a bad chip in your monitor the one can not discover properly the other. Same happens if it is new monitor or video chip that does not have proper support in the x server or driver. I hope it helps regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jam4ap$4vh$1...@dough.gmane.org
