On 2010/12/30 15:55 (GMT+0100) Bruno Friedmann composed:
Just seen today, on factory we are moving from xorg 7.5 to xorg 7.6 Perhaps most of your trouble will go away with that update.
After seeing your reply, without really thinking about it, I loaded up a repo in a web browser tab to watch for this to take place. After several reloads since that time I now realize the original load already had 7.6 (which is what I had last dup'd to) - except for several video drivers, intel-legacy among them. Is the 845G not using intel-legacy?
Felix Miata wrote:
On 2010/12/29 20:16 (GMT+0100) Bruno Friedmann composed:
Felix Miata wrote:
Can anyone tell from http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-37rc7.i845-t2240.txt and/or http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-37rc512.i845-t2240.txt whether these are i845G, kernel, or general Intel? https://bugzilla.novell.com/show_bug.cgi?id=658802 is the only similar open bug I've found so far.
I installed: xorg-x11-server-debuginfo-7.4-65.2.i586 libpciaccess0-debuginfo-7.4-27.3.i586 libpixman-1-0-debuginfo-0.16.0-3.4.i586 xorg-x11-driver-video-debuginfo-7.4-92.1.i586
but that doesn't seem to have helped. It's asking for a lot more complicated debuginfo zypper ins: http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-37rc7.i845.t2240+debug.txt
Just copy and paste the suggested -debuginfo ( it's how to call zypper with capacity )
Pure copy & paste of those strings would actually do something besides error? Seeing what I saw {...ginfo(build-id)=####...} I expected I needed to discover specific "(build-id)"s that I knew nothing about finding. What is zypper "capacity" (not found in 11.4 of zypper man page)? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org