Bug#493096: xserver-xorg-video-intel: [855GM] External monitor unusable
> -Ursprüngliche Nachricht- > Von: "Julien Cristau" <[EMAIL PROTECTED]> > Gesendet: 31.07.08 18:00:04 > An: [EMAIL PROTECTED] > Betreff: Re: Bug#493096: xserver-xorg-video-intel: [855GM] External monitor > unusable > > ... > As far as I can tell, the only two changes that can affect your hardware > between -2 and -2+lenny1 are: > - "Improve FBC size checking" > - "Don't disable pipe A on 855 chips" > > The package at http://people.debian.org/~jcristau/493096/ reverts the > 855 force enable pipe a quirk, can you give it a try? > Today I was finally able to try out your package. And yes, I can confirm that displaying on external monitor works again with it. Thanks for the fix, Vivenzio ___ Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=00 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389010: Additional information
Just resent my mail since the I sent it to "389010-submitter" by mistake and thus it did not reach the maintainers. (I had better read the BTS-instructions carefully *before* sending the information for the first time; sorry for that.) regards, Vivenzio > I also had this problem and solved it by installing (more exactly: > self-compiling) > the eclips-3.2.1 packages from experimental on my machine. > > As far as I had figured out, the problem was indeed that gcj did not find > *usable* > versions of native libraries (like assumed by Michael Koch, stated in > Mike O'Connor's mail). > > In particular, the org.eclipse*so files generated under /tmp did already > exist (of course without that "sowtu7my" or similar "suffix"), but they > were linked against some libgcj.so* version that was not available anymore > on my system. As a consequence, the installed org.eclipse*.so files were not > usable and obviously gij tried to generate them. So to track down the problem, > check against which libgcj.so* library the org.eclipse*.so on your system are > linked against. > > I think the problem is caused by a "version mismatch" of the intalled version > of eclipse-*-gcj packages and the libgcj package, so just re-generating the > eclipse-3.1.2 packages may solve the problem. > > Alternatively, the eclipse 3.2.1 packages from experimental may be promoted to > unstable, if this is currently an option ;-) > > Kind regards, > Vivenzio __ "Ein Herz für Kinder" - Ihre Spende hilft! Aktion: www.deutschlandsegelt.de Unser Dankeschön: Ihr Name auf dem Segel der 1. deutschen America's Cup-Yacht!
Bug#389010: Additional information
I also had this problem and solved it by installing (more exactly: self-compiling) the eclips-3.2.1 packages from experimental on my machine. As far as I had figured out, the problem was indeed that gcj did not find *usable* versions of native libraries (like assumed by Michael Koch, stated in Mike O'Connor's mail). In particular, the org.eclipse*so files generated under /tmp did already exist (of course without that "sowtu7my" or similar "suffix"), but they were linked against some libgcj.so* version that was not available anymore on my system. As a consequence, the installed org.eclipse*.so files were not usable and obviously gij tried to generate them. So to track down the problem, check against which libgcj.so* library the org.eclipse*.so on your system are linked against. I think the problem is caused by a "version mismatch" of the intalled version of eclipse-*-gcj packages and the libgcj package, so just re-generating the eclipse-3.1.2 packages may solve the problem. Alternatively, the eclipse 3.2.1 packages from experimental may be promoted to unstable, if this is currently an option ;-) Kind regards, Vivenzio __ Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach! Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
