Re: [arch-general] Segmentation fault in X after last upgrade
Magnus Therning schrob: Anyone else seeing something the same behaviour? Not the exact same thing here but since the latest upgrade to X.org 1.7.1 and Nvidia 190.42 two days ago my X already crashed twice with no errors in /var/log/Xorg.0.log except the following backtrace (with segfault): Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x45cf48] 1: /usr/bin/X (0x40+0x59ea9) [0x459ea9] 2: /lib/libpthread.so.0 (0x7f2572faa000+0xe7e0) [0x7f2572fb87e0] 3: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f256eb4b000+0xa4aa2) [0x7f256ebefaa2] 4: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0xa6d2) [0x7f257361e6d2] 5: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0x352a9) [0x7f25736492a9] 6: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0x2f9ab) [0x7f25736439ab] 7: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0x37722) [0x7f257364b722] 8: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0x38a90) [0x7f257364ca90] 9: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0x2f6ba) [0x7f25736436ba] 10: /usr/lib/libpixman-1.so.0 (pixman_image_composite+0x17c) [0x7f25736444ec] 11: /usr/lib/xorg/modules/libwfb.so (wfbComposite+0x163) [0x7f256e71fc43] 12: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f256eb4b000+0x33e817) [0x7f256ee89817] 13: /usr/bin/X (0x40+0xc2780) [0x4c2780] 14: /usr/bin/X (0x40+0x9baf9) [0x49baf9] 15: /usr/bin/X (0x40+0x9bdc5) [0x49bdc5] 16: /usr/bin/X (0x40+0x110d86) [0x510d86] 17: /usr/bin/X (0x40+0x22726) [0x422726] 18: /usr/bin/X (MapWindow+0x153) [0x424893] 19: /usr/bin/X (0x40+0x45976) [0x445976] 20: /usr/bin/X (0x40+0x466a4) [0x4466a4] 21: /usr/bin/X (0x40+0x2202c) [0x42202c] 22: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f25720549ed] 23: /usr/bin/X (0x40+0x21bd9) [0x421bd9] Segmentation fault at address 0x7f258d399000 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting I don’t think that this really helps but at least you know that you are not alone. ;) Ed signature.asc Description: This is a digitally signed message part.
[arch-general] APM gets re-enabled after awake from suspend
Hi, my hard drive suffers from the clicking problem, therefore I deactivated the APM (Advanced Power Management) totally. I'm doing this using hdparm in the /etc/rc.local, making sure that it gets executed every time I boot up my machine. However I noticed that the APM gets re-enabled after I wake my machine up from Suspend-to-RAM, which makes the hard drive clicking again. I'm now wondering whether this is normal? I guess so, as the hard drive gets disabled during the suspend, and after a wake-up it gets re-enabled, so any changed made with hdparm don't get stored. Is this intention right? Secondly I want to know what would be the right file (place) to fix this. I'll have to execute the hdparm command again, but don't quite know where to put it, or at least where it should be put ;). -- Best regards, Karol Babioch ka...@babioch.de signature.asc Description: This is a digitally signed message part
Re: [arch-general] Segmentation fault in X after last upgrade
Lars Tennstedt schrieb: Hi, Xorg with nvidia-96xx for a GeForce 3 Ti 200 does not start anymore on my Arch Linux installation (i686). First I thought that it was a failure caused by SLiM because the error output on screen was respawning too fast and I switched from respawn to once but that did not help. Even standalone X does not start. I looked into the log file and there were messages about that freetype and kbd cannot be found. But both are installed. Are these problems connected to each other? http://mailman.archlinux.org/pipermail/arch-dev-public/2009-October/014167.html Or better: http://www.nvnews.net/vbulletin/showthread.php?t=139388 I don't know what you think, but I don't get the part where the nvidia dev says they plan to fix it, but he can't promise if and when. So they plan to fix it, but don't really know if they plan to fix it. So basically, you're screwed unless you plan on buying a GeForce 6 or newer. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Segmentation fault in X after last upgrade
Hi, Xorg with nvidia-96xx for a GeForce 3 Ti 200 does not start anymore on my Arch Linux installation (i686). First I thought that it was a failure caused by SLiM because the error output on screen was respawning too fast and I switched from respawn to once but that did not help. Even standalone X does not start. I looked into the log file and there were messages about that freetype and kbd cannot be found. But both are installed. Are these problems connected to each other? Bye Lars Edgar Kalkowski wrote: Magnus Therning schrob: Anyone else seeing something the same behaviour? Not the exact same thing here but since the latest upgrade to X.org 1.7.1 and Nvidia 190.42 two days ago my X already crashed twice with no errors in /var/log/Xorg.0.log except the following backtrace (with segfault): Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x45cf48] 1: /usr/bin/X (0x40+0x59ea9) [0x459ea9] 2: /lib/libpthread.so.0 (0x7f2572faa000+0xe7e0) [0x7f2572fb87e0] 3: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f256eb4b000+0xa4aa2) [0x7f256ebefaa2] 4: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0xa6d2) [0x7f257361e6d2] 5: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0x352a9) [0x7f25736492a9] 6: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0x2f9ab) [0x7f25736439ab] 7: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0x37722) [0x7f257364b722] 8: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0x38a90) [0x7f257364ca90] 9: /usr/lib/libpixman-1.so.0 (0x7f2573614000+0x2f6ba) [0x7f25736436ba] 10: /usr/lib/libpixman-1.so.0 (pixman_image_composite+0x17c) [0x7f25736444ec] 11: /usr/lib/xorg/modules/libwfb.so (wfbComposite+0x163) [0x7f256e71fc43] 12: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f256eb4b000+0x33e817) [0x7f256ee89817] 13: /usr/bin/X (0x40+0xc2780) [0x4c2780] 14: /usr/bin/X (0x40+0x9baf9) [0x49baf9] 15: /usr/bin/X (0x40+0x9bdc5) [0x49bdc5] 16: /usr/bin/X (0x40+0x110d86) [0x510d86] 17: /usr/bin/X (0x40+0x22726) [0x422726] 18: /usr/bin/X (MapWindow+0x153) [0x424893] 19: /usr/bin/X (0x40+0x45976) [0x445976] 20: /usr/bin/X (0x40+0x466a4) [0x4466a4] 21: /usr/bin/X (0x40+0x2202c) [0x42202c] 22: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f25720549ed] 23: /usr/bin/X (0x40+0x21bd9) [0x421bd9] Segmentation fault at address 0x7f258d399000 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting I don’t think that this really helps but at least you know that you are not alone. ;) Ed
Re: [arch-general] google wave
On 11/04/2009 01:18 AM, Sachiel wrote: Could I have an invitation, please? I've been following Weave for a long time :) sachiel2...@gmail.com sent. -- Ionut
Re: [arch-general] Segmentation fault in X after last upgrade
Thomas Bächler schreef: [ Xorg segfaults with Nvidia driver ] I don't know what you think, but I don't get the part where the nvidia dev says they plan to fix it, but he can't promise if and when. So they plan to fix it, but don't really know if they plan to fix it. So basically, you're screwed unless you plan on buying a GeForce 6 or newer. Maybe a good time to try the nouveau driver? I don't have a system with an Nvidia vga currently, but from waht i hear it's getting quite good. mvg, Guus
[arch-general] Mayday - Installed Fresh Archlinux on Laptop - Resolution stuck 1152x864, need 1440x900??
Listmates, New drive for my laptop so I dedicated it to Arch. Net install with 2009.08 went fine (although there really should be a warning when you leave install WITHOUT configuring the bootloader). [the /arch/setup menu autoadvances when you leave Configure System and if you click Done and downarrow anticipating moving to the next item, you can easily miss configuring the bootloader (I did ;-)] The problem I have is that my laptop is stuck in 1152x864 resolution. For the text install that is fantastic, but when you start kde -- not so good. (should be 1440x900) The card is an RS690M (radeon 1200) and the radeon driver was loaded by default. The modules configured are: 22:46 alchemy:~ lsmod | grep rad radeon716352 1 ttm43776 1 radeon drm 191392 2 radeon,ttm i2c_algo_bit6980 1 radeon i2c_core 25664 4 radeon,i2c_piix4,drm,i2c_algo_bit THE WEIRD PART... I have Arch on the drive I just took out and it goes to 1440x900 just fine. I am not using an xorg.conf, so I am pretty much at X's mercy. I use /etc/rc.d/kdm start from runlevel 3 to start kdm. It goes to 1152x864 instead of 1440x900. I don't understand how to control the new KMS stuff. I have check the kde4 settings for Display Size and Orientations, but the maximum allowed is 1152x864: http://www.3111skyline.com/download/bugs/kde4/kde4-syssettings-display.jpg http://www.3111skyline.com/download/bugs/kde4/kde4-syssettings-1164.png What is the trick? Also, when I try to start xdm from inittab with the default x:5:respawn:/usr/bin/xdm -nodaemon I get the disabling for 5 seconds, respawning too fast error. So, what's the trick here? I bet there related... I have put the Xorg.0.log on the server as well: http://www.3111skyline.com/download/bugs/kde4/Xorg.0.log It looks like the dang thing is using the vesa driver?? I'll add radeon to modules, but It's loaded already so I don't think that's going to help. Anybody know what's happening here? This is the first install where I haven't installed KDE3, so i don't know if that is a part of the issue either. Any help would be greatly appreciated. If you need to see anything else, just let me know. Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Re: [arch-general] google wave
On Wed, 2009-11-04 at 10:12 +0400, Jozsef wrote: On Wed, 04 Nov 2009, Ionut Biru wrote: On 11/04/2009 01:18 AM, Sachiel wrote: Could I have an invitation, please? I've been following Weave for a long time :) sachiel2...@gmail.com sent. -- Ionut May I have one invitation please? jozse...@gmail.com Thanks a lot! Could everyone who wants an invite PLEASE directly mail those offering instead of spamming arch-general. This is nothing to do with Arch.
Re: [arch-general] google wave
2009/11/2 Loui Chang louipc@gmail.com I agree. It's pretty damned ridiculous. People on this list can't seem to take a hint. Obviously not Seriously people: arch-general != google-wave
