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.
On 12/29/2010 08:00 PM, 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.
Hi Felix.
Two things, first always install the recommended -debuginfo package ( it doesn't slow down your computer, just use more place on disk, but they can provide a good backtrace to devs )
Otherwise, did you check also this bug from https://bugs.freedesktop.org/show_bug.cgi?id=30637 Michel Marek (comment 25, and see the lastest one )
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.
Two things, first always install the recommended -debuginfo package ( it doesn't slow down your computer, just use more place on disk, but they can provide a good backtrace to devs )
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
Otherwise, did you check also this bug from https://bugs.freedesktop.org/show_bug.cgi?id=30637 Michel Marek (comment 25, and see the lastest one )
I can't tell from looking at those if https://bugs.freedesktop.org/show_bug.cgi?id=32482 or something else got filed as a result, or if the former is related, but I'm using packages sent to the mirrors today to get my instant crashes on a fresh i845G install.
Re Hi Felix.
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.
On 12/30/2010 12:47 AM, 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.
Two things, first always install the recommended -debuginfo package ( it doesn't slow down your computer, just use more place on disk, but they can provide a good backtrace to devs )
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 )
Otherwise, did you check also this bug from https://bugs.freedesktop.org/show_bug.cgi?id=30637 Michel Marek (comment 25, and see the lastest one )
I can't tell from looking at those if https://bugs.freedesktop.org/show_bug.cgi?id=32482 or something else got filed as a result, or if the former is related, but I'm using packages sent to the mirrors today to get my instant crashes on a fresh i845G install.
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)?
On 12/31/2010 02:12 PM, Felix Miata wrote:
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?
No idea, hum time to try to install the lastest factory on my old sony laptop which has a intel chipset inside (852 I think) But it take lot's of time on this 10 years old machine. See If I can test it the next days.
I would expect they used i915 for the chipset, but I've not followed too much that gfx chipset
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)?
Yes they install the corresponding -debug package
like zypper install -C "debuginfo(build-id)=959f9db211e15ebc9c7251f5e93ee0d5e4369aff"
'libpixman-1-0-debuginfo' providing 'debuginfo(build-id) = 959f9db211e15ebc9c7251f5e93ee0d5e4369aff' is already installed.
(normal on my system, I've nearly every -debug packages installed :-)
On 2010/12/31 16:55 (GMT+0100) Bruno Friedmann composed:
Yes they install the corresponding -debug package
like zypper install -C "debuginfo(build-id)=959f9db211e15ebc9c7251f5e93ee0d5e4369aff"
'libpixman-1-0-debuginfo' providing 'debuginfo(build-id) = 959f9db211e15ebc9c7251f5e93ee0d5e4369aff' is already installed.
(normal on my system, I've nearly every -debug packages installed :-)
I turned the Xorg.0.log file into a script to do that, 17 lines in all, and got 17 "no provider" responses, even though Factory debug repo is enabled. :-(
Am 31.12.2010 19:18, schrieb Felix Miata:
I turned the Xorg.0.log file into a script to do that, 17 lines in all, and got 17 "no provider" responses, even though Factory debug repo is enabled. :-(
I also often had trouble getting the right debuginfo for xorg, but there is a way to do this (if you do not mind trying the very latest Xorg) http://en.opensuse.org/openSUSE:Bugreport_X#How_to_test_the_latest_Xorg
Ciao Bernhard M.
On 2011/01/05 07:24 (GMT+0100) Bernhard M. Wiedemann composed:
Felix Miata composed:
I turned the Xorg.0.log file into a script to do that, 17 lines in all, and got 17 "no provider" responses, even though Factory debug repo is enabled. :-(
I also often had trouble getting the right debuginfo for xorg, but there is a way to do this (if you do not mind trying the very latest Xorg) http://en.opensuse.org/openSUSE:Bugreport_X#How_to_test_the_latest_Xorg
Excellent! I don't see why anyone running Factory would object to using the latest Xorg, but now my GX260/Factory i845G actually seems to be working! Maybe patch(es) from any of
https://bugs.freedesktop.org/show_bug.cgi?id=26345 https://bugs.freedesktop.org/show_bug.cgi?id=27187 https://bugs.freedesktop.org/show_bug.cgi?id=27245 https://bugs.freedesktop.org/show_bug.cgi?id=30637 https://bugs.freedesktop.org/show_bug.cgi?id=32482
have worked. :-)
-
Bernhard M. Wiedemann -
Bruno Friedmann -
Felix Miata