Lockup with startx

Hi,
I've been having this problem for about a week now, that when X starts, my screen switches off completely (power saving mode)
and the computer doesn't respond to anything anymore. The only way out is to do a cold reboot.
Since then I have done a fresh install (downloaded at ftp://ftp.belnet.be/packages/archlinux/ … -i686.iso). After setting it up, I ran an update of the system with "pacman -Syu", and then I installed X and hwd with "pacman -S xorg hwd". I used "hwd -x" to create a xorg.conf-file (I used xorg.conf.vesa, since I read somewhere that this should always work).
Anyway, here it is:
Section "ServerLayout"
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "CorePointer"
# Serial Mouse not detected
# USB Mouse not detected
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
Option "AutoAddDevices" "False"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
# FontPath "/usr/share/fonts/PEX"
## Additional fonts: Locale, Gimp, TTF...
# FontPath "/usr/share/fonts/cyrillic"
## FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
## FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
## True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
# FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/share/fonts/ttf/western"
# FontPath "/usr/share/fonts/ttf/decoratives"
# FontPath "/usr/share/fonts/truetype"
# FontPath "/usr/share/fonts/truetype/openoffice"
# FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
# FontPath "/usr/share/fonts/latex-ttf-fonts"
# FontPath "/usr/share/fonts/defoma/CID"
# FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "drm"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
# Load "type1"
Load "freetype"
# Load "record"
# Load "synaptics"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
Option "Buttons" "5"
EndSection
# Auto-generated by Archie mkxcfg
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
# 640x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
# 720x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
# 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
# 640x480 @ 72Hz (VESA) hsync: 37.9kHz
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
# 640x480 @ 75Hz (VESA) hsync: 37.5kHz
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
# 640x480 @ 85Hz (VESA) hsync: 43.3kHz
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
# 800x600 @ 56Hz (VESA) hsync: 35.2kHz
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
# 800x600 @ 60Hz (VESA) hsync: 37.9kHz
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
# 800x600 @ 72Hz (VESA) hsync: 48.1kHz
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
# 800x600 @ 75Hz (VESA) hsync: 46.9kHz
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
# 800x600 @ 85Hz (VESA) hsync: 53.7kHz
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
# 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
# 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
# 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
# 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
# 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
# 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
# 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
# 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
# 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
# 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
# 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
# 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
# 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
# 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
# Additional modelines
ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# Extended modelines with GTF timings
# 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
# 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
# 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
# 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
# 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
# 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
# 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
# 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
# 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
# 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
# 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
# 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
# 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
# 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
# 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
# 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
# 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
# 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
# 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
EndSection
# Auto-generated by Archie mkxcfg
Section "Device"
Identifier "Card0"
Driver "vesa"
VendorName "All"
BoardName "All"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 16
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
: Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
The output of lspci -v (the part about the video card):
02:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. Device 0320
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at d0000000 (32-bit, prefetchable) [size=128M]
I/O ports at c000 [size=256]
Memory at ff4f0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at ff4c0000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [80] MSI: Mask- 64bit+ Count=1/1 Enable-
Capabilities: [100] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Kernel modules: radeonfb
02:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
Subsystem: Micro-Star International Co., Ltd. Device 0321
Flags: bus master, fast devsel, latency 0
Memory at ff4e0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Express Endpoint, MSI 00
I would also post /var/log/Xorg.0.log, but there is a problem with that: the first time I did startx after the new install, a logfile was written. I then made some changes to xorg.conf and tried startx again. Before that, however, I deleted /var/log/Xorg.0.log, since I wanted to be absolutely sure that the logfile I would find there would be the new one. After crashing my computer with startx and rebooting: no logfile. I don't know if this is related to the lockup problem.
Also worthy of note. The problem is probably not caused by the xorg-server. Among the many things I tried this week before I did the fresh install was downgrading it and the problem was still there. Also, I think the latest xorg-server package has been installed for some time while X worked just fine. I remember because I also struggled with the input hotplugging thing a while ago.
I really hope somebody has some clue what's causing this problem

Perhaps this problem is related to another problem I'm having. Whenever a lot of text scrolls through the screen (let's say when compiling a kernel), the computer tends to freeze as well.
I noticed this when I was compiling kernel 2.6.27.10 in order to downgrade. The only way the compile would not freeze the computer was by quickly switching to another terminal with Alt-F2 when the compiling started.
Anyway, in the end my X seems to work fine with the older kernel. Guess I'll have to put 'kernel26' in my ignorepkg-list. I'm still not too happy about this, though. Does this mean I can never update my kernel again? Does this older kernel count as a custom kernel (all I did was change the number of the kernel version downloaded from 'ftp.kernel.org' and the patch version downloaded from 'ftp.archlinux.org', and the appropriate checksums)?

Similar Messages

570 GTX lockup with white squares

Card: MSI 570 GTX (N570GTX M2D12D5/OC)
Driver: Nvidia 270.61
Bios updated to latest (KK1)
According to MSI Afterburner I am running the stock settings: 988mV core voltage, 786MHz Core/1572MHz Shader/2100MHz Memory.
I have never overclocked the card beyond the stock OC that the card comes with.
When playing the game Rift after about an hour, sometimes less little white squares show up all over both of my monitors and then within a few seconds the computer locks up.
MSI Kombustor seems to work ok, I haven't run it indefinitely but it makes it through the default benchmark. I tried another stress program called OCCT. I ran that for about 20 minutes with default shader complexity (0) and it produced 1 error and no crashes. I tried it again with shader complexity 4 (out of 8) and every minute or two it would signal an error then after about half an hour I got the same lockup with the white squares. So far I have only seen this lockup occur in Rift and with OCCT. I beat Portal 2 in single player and Coop and played several hours of Shogun 2 with no issues.
This is actually my second 570. My original one started producing artifacts constantly and games were completely unplayable. I RMA'ed it a week or two ago and now this card is presenting a different problem.
Rest of my computer:
Windows 7 Home Premium (64bit)
Intel Core i5 760 at stock (2.80GHz)
8GB DDR3 Ram
750 Watt Silverstone power supply
Any suggestions on what to try next? Is the card bad? I didn't see any references to this exact problem when I tried searching the MSI forums. Though I did run across another forum where someone was having the same problem. I don't think they found a solution though.
Snapped a picture of the frozen screen with white squares:

Good to hear
Maybe Svet can make you a custombios, so you can flash your cards bios, then you dont have to use Afterburner all the time.
Hope he reacts

GNOME doesn't work correctly with startx only by GDM

This is driving me nuts, I'm having a bunch of problems because I'm starting my GNOME session using startx instead of GDM and this bugs me a lot because I prefer startx most of the times...
1) One of the problems is that the sound does not work with startx. Starting through GDM, the sound is ok. What's even more frustrating is that sometimes, it doesn't even work through GDM
2) I can't unlock anything in the "System » Administration" menu. All of the "unlock" buttons are grayed out and I can't click them. But it works on GDM. However, whatever setting I change (after unlocking) is not saved...

tandycorp wrote:But since your settings cannot be saved correctly you should first try to correct that problem, then the audio problem should be easy to resolve. In my case the settings are saved correctly (I first installed gdm then completely deleted it). You may want to look to the hal wiki and add your user in /etc/d-bus/system.d/hal.conf. It looks like a session problem.
I've read the wiki but I don't know what should I do to the hal.conf everything seems "normal" to me...
EDIT:
I don't know what I've done (changed lots of things lately and configuration files) but the sound seems to be working now... Not every time, but most of the time, it seems so. I have enabled the button sound (when you click a button) temporarily to see if the sound keeps working for the time being...
Also, the unlock button now is enabled and here's a thing I found about the settings not being saved. I open "Administration » Services", for instance, and click "unlock", input password, enable GDM, which was disabled of course and click "close". I open "Administration » Services" again and with everything disabled, I see that GDM is not checked, still, I click "unlock" again, the services list is unlocked and GDM is still unchecked. But, if I look inside /etc/rc.conf, I can see the gdm daemon was added to the list... If I reboot the computer, GDM will start automatically and if once again I go to "Administration » Services", now I see GDM checked. If I try to uncheck it, it will work, but I will only see the unchecked value in the "Services" window after another reboot. Is this normal?
Last edited by Nazgulled (2009-04-01 23:32:41)

[SOLVED] no sound with startx

Hi.
I use systemd and xmonad on my arch linux.
When starting xmonad with "startx" command, alsamixer doesn't work in urxvt while it works well under tty.
It seems to be a polkit problem.
My .xinitrc file has only one line:
exec xmonad
How can I make alsamixer work after "startx"?
Last edited by piaodan (2012-09-07 17:47:46)

WonderWoofy wrote:
piaodan wrote:
It seems to be a polkit problem.
My .xinitrc file has only one line:
exec xmonad
I think you already have your answer...
Actually I didn't find a way to have polkit work with systemd and startx.
When using sysvinit, "exec ck-launch-session xmonad" works well, but "ck-launch-session" reports an error with systemd.
What can replace "ck-launch-session" when using systemd?

[Xorg/startx] black screen with startx

I notice a strange bug with the new version of xorg packages if I use the "startx" method for running KDE4,
description of this bug :
1) I type "startx -- vt1"
2) KDE4 loads successfully
3) I run a 3D game ( or glxgears )
4) I choose the "logout" menu in KDE4
5) then I type again "startx -- vt1" to start again KDE4
6) KDE4 loads but if I move the mouse I get a black screen, but I can see the HDD led continues to light
this bug doesn't occur if I start KDE with KDM,
my system:
- archlinux 32 bits
- laptop with pentium 4 2.4 Ghz 1.2 Gb ram
- SIS645DX chipset
- ati radeon 9000 AGP ( I use DRI2 with KMS, xf86-video-ati driver )
Last edited by Potomac (2012-10-14 22:10:38)

Sorry, I will use code tag next time.
I deleted xorg.conf and it works.
It seems a little bit strange, because xorg.conf is generated automatically by X itself. Why xorg.conf does not work?

Gui program doesn't look good with startx

I did not install a DE in arch linux, just to keep it lightweight. However, my GUI application doesn't look good running with start x.
is there any package I can install to make it look better, like fonts, visuals, or the only way is to install either KDE or GNOME desktops?

If you did not install a desktop environment or one of the windows managers, and you are using startx without having created your very own ~/.xinitrc, then you are using a very simple WM called twm.
You may really want to look at the wiki documentation that was linked in your other thread -- If you are trying to stay light, there are other choices to Gnome or KDE. Look at i3, Openbox, xfce4, or any of the other beloved environments discussed at length of these forums.
Even with twm, you can install and run a screen shot program.

KDM refuses to log me in - but KDE/GNOME works fine with startx

I just updated to the newest kernel and another ~150 packages and I have a little bug!
Basically KDM starts fine, (i use the innitab method) - I log in and then black screen and straight back to KDM.
Using startx and the appropriate entry in xinitrc I can boot gnome or kde fine.
Anyone have any Idea? I'm lost.

this kdm.log -> Note that your system (i.e., not from libraries daemon.* syslog facility; file(s) it is logged. This is a pre-release It is not supported in any way. Bugs may be filed in Select the "xorg" Before reporting bugs latest version in the See http://wiki.x.org/wiki/GitPage X.Org X Server 1.6.3.901 Release Date: 2009-8-25 X Protocol Version 11, Revision 0 Build Operating System: Current Operating System: Build Date: 04 September 2009 Before reporting to make sure Markers: (--) probed, (++) from command (WW) warning, (==) Log file: "/var/lo (==) Using config file: (EE) RADEON(0): [dri] [dri] Disabling DRI. XRANDR name: DVI-1 Connector: DVI-I CRT2: INTERNAL_KLDSCP_DAC2 DFP1: INTERNAL_UNIPHY DDC reg: 0x7e60 XRANDR name: DVI-0 Connector: DVI-I CRT1: INTERNAL_KLDSCP_DAC1 DFP2: INTERNAL_KLDSCP_LVTMA DDC reg: 0x7e20 Dac detection success Unhandled monitor type 0 finished output detect: 0 finished output detect: 1 finished all detect before xf86InitialConfiguration Dac detection success Unhandled monitor type 0 after xf86InitialConfiguration Output DIG0 transmitter setup success Blank CRTC 0 success Disable CRTC 0 success Disable CRTC memreq 0 success Blank CRTC 1 success Disable CRTC 1 success Disable CRTC memreq 1 success mc fb loc is 010f00d0 (EE) RADEON(0): Acceleration Output DIG0 transmitter setup success Blank CRTC 0 success Disable CRTC 0 success Disable CRTC memreq 0 success Blank CRTC 1 success Disable CRTC 1 success Disable CRTC memreq 1 success Output DIG0 transmitter setup success Blank CRTC 0 success Disable CRTC 0 success Disable CRTC memreq 0 success Mode 1680x1050 - 2240 1089 6 freq: 146250000 best_freq: 146250000 best_feedback_div: 117 best_ref_div: 10 best_post_div: 8 Set CRTC 0 PLL success Set CRTC Timing success Set CRTC 0 Overscan success Not using RMX scaler 0 setup success Set CRTC 0 Source success crtc 0 YUV disable setup success Output DIG0 transmitter setup success Output DIG2 encoder setup success Output DIG2 encoder setup success Output DIG0 transmitter setup success Output DIG0 transmitter setup success Output DIG0 transmitter setup success Enable CRTC memreq 0 success Enable CRTC 0 success Unblank CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Disable CRTC memreq 1 success Output DIG0 transmitter setup success Blank CRTC 0 success Disable CRTC 0 success Disable CRTC memreq 0 success Mode 1680x1050 - 2240 1089 6 freq: 146250000 best_freq: 146250000 best_feedback_div: 117 best_ref_div: 10 best_post_div: 8 Set CRTC 0 PLL success Set CRTC Timing success Set CRTC 0 Overscan success Not using RMX scaler 0 setup success Set CRTC 0 Source success crtc 0 YUV disable setup success Output DIG0 transmitter setup success Output DIG2 encoder setup success Output DIG2 encoder setup success Output DIG0 transmitter setup success Output DIG0 transmitter setup success Output DIG0 transmitter setup success Enable CRTC memreq 0 success Enable CRTC 0 success Unblank CRTC 0 success Output DIG0 transmitter setup success Blank CRTC 0 success Disable CRTC 0 success Disable CRTC memreq 0 success Blank CRTC 1 success Disable CRTC 1 success Disable CRTC memreq 1 success Enable CRTC memreq 0 success Enable CRTC 0 success Unblank CRTC 0 success error setting MTRR Output DIG0 transmitter setup success Blank CRTC 0 success Disable CRTC 0 success Disable CRTC memreq 0 success Blank CRTC 1 success Disable CRTC 1 success Disable CRTC memreq 1 success mc fb loc is 010f00d0 (EE) RADEON(0): Acceleration Output DIG0 transmitter setup success Blank CRTC 0 success Disable CRTC 0 success Disable CRTC memreq 0 success Blank CRTC 1 success Disable CRTC 1 success Disable CRTC memreq 1 success Output DIG0 transmitter setup success Blank CRTC 0 success Disable CRTC 0 success Disable CRTC memreq 0 success Mode 1680x1050 - 2240 1089 6 freq: 146250000 best_freq: 146250000 best_feedback_div: 117 best_ref_div: 10 best_post_div: 8 Set CRTC 0 PLL success Set CRTC Timing success Set CRTC 0 Overscan success Not using RMX scaler 0 setup success Set CRTC 0 Source success crtc 0 YUV disable setup success Output DIG0 transmitter setup success Output DIG2 encoder setup success Output DIG2 encoder setup success Output DIG0 transmitter setup success Output DIG0 transmitter setup success Output DIG0 transmitter setup success Enable CRTC memreq 0 success
Enable CRTC 0 success
Unblank CRTC 0 success
Blank CRTC 1 success
Disable CRTC 1 success
Disable CRTC memreq 1 success
Output DIG0 transmitter Blank CRTC 0 success
Disable CRTC 0 success
Disable CRTC memreq 0 success
Mode 1680x1050 - 2240 1089 6
freq: 146250000
best_freq: 146250000
best_feedback_div: 117
best_ref_div: 10
best_post_div: 8
Set CRTC 0 PLL success
Set CRTC Timing success
Set CRTC 0 Overscan success
Not using RMX
scaler 0 setup success
Set CRTC 0 Source success
crtc 0 YUV disable setup success
Output DIG0 transmitter Output DIG2 encoder setup success
Output DIG2 encoder setup success
Output DIG0 transmitter Output DIG0 transmitter Output DIG0 transmitter Enable CRTC memreq 0 success
Enable CRTC 0 success
Unblank CRTC 0 success
(EE) XKB: No components [config/dbus] couldn't Output DIG0 transmitter Blank CRTC 0 success
Disable CRTC 0 success
Disable CRTC memreq 0 success
Blank CRTC 1 success
Disable CRTC 1 success
Disable CRTC memreq 1 success
Enable CRTC memreq 0 success
Enable CRTC 0 success
Unblank CRTC 0 success
KCrash: Application QThread::wait: Thread QThread: Destroyed error setting MTRR drkonqi: cannot connect Last edited by I moved the old log out of the way so this is fresh. I did an init 5, logged in with kdm, waited for it to black screen then restart and then copied the log over.
uses syslog. All of kdm's internally generated messages
and external programs/scripts it uses) go to the
check your syslog configuration to find out to which
PAM logs messages related to authentication to authpriv.*.
version of the X server from The X.Org Foundation.

the bugzilla at http://bugs.freedesktop.org/.
product for bugs you find in this release.
in pre-release versions please check the
X.Org Foundation git repository.
for git access instructions.
(1.6.4 RC 1)

Linux 2.6.30-ARCH x86_64
Linux holm 2.6.31-ARCH #1 SMP PREEMPT Tue Oct 13 11:33:39 CEST 2009 x86_64
05:45:43PM
problems, check http://wiki.x.org
that you have the latest version.
(**) from config file, (==) default setting,
line, (!!) notice, (II) informational,
(EE) error, (NI) not implemented, (??) unknown.
g/Xorg.0.log", Time: Wed Oct 14 22:18:08 2009
"/etc/X11/xorg.conf"
RADEONDRIGetVersion failed to open the DRM

initialization failed

(base = 0xd0000000, size = 0x10000000, type = 1) Invalid argument (22)

initialization failed

setup success
setup success
setup success
setup success
setup success
provided for device Virtual core keyboard
register object path
setup success
'kdmgreet' crashing...
tried to wait on itself
while thread is still running
(base = 0xd0000000, size = 0x10000000, type = 1) Invalid argument (22)
to X server :0.0
brendan (2009-10-14 21:21:05)

AEB + Mirror Lockup with a 5Dsr

Is it possible to configure a 5Dsr to use mirror lockup and AEB simultaneously? The behavior I want is: 1. Press shutter release button.2. Mirror is raised.3. After the interval selected in mirror lockup the requested number of AEB exposures are made automatically. Is this possible? If so, can someone point me to instructions? It appears from the manual and my testing that if I set both mirror lockup and AEB I must press the shutter release once for each AEB exposure. The best alternative I can think of is to dispense with mirror lockup and use AEB with silent multi-frame drive mode. Thanks for any suggestions.

Bazsl wrote:
Thanks for the answer although it is not what I was hoping to hear. There are many times when being able to complete an HDR sequence quickly is important and having to trigger each shot manually is a very slow process. Consider a one second mirror lockup delay and a half second reaction time for each shutter release after the first one. A five shot HDR sequence will take seven seconds ((5 x 1) + (4 x 0.5)). If the camera behaved as I described it would take two seconds, one second for the mirror lockup delay and one second for the five shutter cycles. I may be missing something, but I cannot think of any reason why I would want the camera to behave the way it does instead of the way I described. It is also an incredibly easy feature to implement since all it requires is an if statement at the beginning of the AEB routine to see if mirror lockup is enabled and if so call the mirror lockup function. At the end of the AEB function another if statement would check to see if the mirror is up and, if so, lower it. Am I the only one who would like to see this functionality?Can't you get the same effect with live view? For HDR sequences, you'll be using a tripod anyway, right?

Jukebox lockup with WMA &

When I have audio files of both MP3 and WMA on my 20G Jukebox 3 and using the latest firmware (.40.06p) my pplayer lock-up. At first I thought that I had hardri've problems. I did everything but reformat. Finally I removed the library and reloaded with mainly WMA (28) files with some MP3. I typically select a bunch of songs/artisits/albums and play in radmon mode. If I have MP3 files in my playlist my jukebox will lockup (freeze, stay powered-on but not playing and no response to any buttons). I have selected a group of WMA songs only and it plays all day no problem. I only started noticing this problem with the last two (?) versions of firmware.
I know that the firmware has not been updated in over a year so I assume that no one is working on it, but it would be nice to be able to mix music formats. I had almost stopped using my jukebox but decided to give it another try (I don't know why I decided to focus on music format as a potential issue, I think I had read somewhere that there were issues with WMA files and the jukebox locking up).

Maybe it was on your page that I saw that WMA cause lockup. I've been playing both WMA & MP3 for years. It maybe the transistion from MP3 to WMA that causes my lockup. I prefer the quality of WMA-28 over MP3-28 so all of my new ripping is WMA.
My solution now is not to mix the two formats and everything is fine. I'll convert my MP3 files to WMA (I know the quality may suffer a little) but now I can use my player.
Thanks.

[Solved] Lockups with newer Kernels

I noticed frequent lockups where REISUB would still work and I could even still switch workspaces, though nothing would load (sometimes I had a terminal open, but it would never show a prompt). It all started, I think, with the kernels > 3.17.
The lts kernel worked without a problem.
The program that triggered this most of the time is Kodi.
I'm using the -ck kernel from AUR optimized for my CPU, but the regular Arch kernel has the same issue. Recently in one of the other threads about freezes, someone suggested recompiling with, PREEMPT_VOLUNTARY. I did that and the problem was gone.
Now yesterday there was an update to kernel 3.19.3.-2 and now it seems PREEMPT_VOLUNTARY doesn't even cut it. So I checked what the lts kernel uses and it has preemption disabled, so I compiled with that set and am currently checking the results.
My question here really is as to why all that is: has it got to do with my machine?
Here are my specs:
Pentium Core2Duo E6700 3.2 GHz
4 GB Ram
NVIDIA Geforce GT 520
Edit: Solved, since it's not an issue anymore with kernels >4.0
Last edited by th3voic3 (2015-05-13 10:51:53)

I now know it can't be my system's config. Just bootstrapped ipxe.lkrn from syslinux and chose releng 64-bit 2012.08.07_04-00-01. As soon as it finished downloading files and started booting up - kaboom, a cold reboot as if the reset button was pressed.
I wonder if this problem is related to "3.3.5+ power regression still present"
https://bbs.archlinux.org/viewtopic.php?id=146851
EDIT: I've also tried 32-bit install ISO with the same results.
Last edited by MajorTom (2012-08-29 03:50:30)

Constant Lockup with Ipod Sync

Just to let you know before I explain my problem:
I am using Itunes 5.0 (although the problem happened in 4.9 too)
I have used the "restore" option multiple times to reset my ipod.
I have run a disk check on the ipod from debug menus
I am using a USB 2.0 connection.
I have an Ipod Photo 30gb
I am using Windows XP SP1
Whenever I try to put music onto my Ipod using automatic or manual update, disk mode or not, itunes locks up completely anywhere between 5-10 songs into copying. It doesnt matter what songs i'm copying, and no specific song is the culprit.
After itunes locks up, interestingly enough, I can neither end task on itunes nor restart by conventional means. When I choose start>shutdown>restart, it is inable to end itunes and just hangs. I have to hard reset it by flicking the power switch.
I recently tried syncing contacts from outlook. This instead gives me "The IPOD cannot be updated. An unknown error occured (-50)"
I have tried defragging my disk, reinstalling Itunes, restoring my ipod.
Anyone have any suggestions?

I have a similar problem with my iPod however the max I've ever got to is 8 songs. I've looked alot into this as it's really frustrating because my iPod was an Xmas present I was really excited about. I still have no solution to the problem however I have found out that it's not the iPod it's iTunes. Not much help I know, but it's something

Problem with startx

Hello everybody.
I used to use GDM as my Display Manager.
Now I changed to openbox and wanted to use the .xinitrc so i thought i need to use startx.
Well i deleted the gdm tag in the deamon line and thought everything will work now.
But now i'm not able to run startx.
I get following EEs
(EE) AIGLX error: dlsym for __DriCreateNewScreen_20050727 failed (/usr/lib/xorg/modules/dri/fglrx_dri.so: undifined symbol: __driCreateNewScreen_20050727)
(EE) AIGLX:reverting to software rendering
The xkeyboard keymap compiler (xkbcomp) reborts:
> WArning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
I hope somebody can help me.
Thanks in advance

Hello.
First of all thanks for your help, but how do you mean disable composite?
I don't really get it.
I have searched the xorg.conf for something like composite, but didn't find anything.
Nice Saturday
[EDIT] Solved my problem. Me = stupid, forgot to add exec openbox to the .xinitrc [/EDIT]
Last edited by basi18 (2007-10-13 16:34:33)

[SOLVED] Possible to load GDM with startx?

I currently boot into the command line and then
startx
to get into GNOME. Is it possible to load GDM in .xinitrc or by any other means when I load my desktop environment? The reason I ask is because I can't get a lock screen to work unless I enable gdm.service at boot, which I don't want. Thanks.
Last edited by barretme (2013-05-09 02:23:48)

barretme wrote:The reason I ask is because I can't get a lock screen to work unless I enable gdm.service at boot, which I don't want. Thanks.
Actually, if what you want is the ability to lock the screen you don't have to enable gdm.
Just add "gnome-screensaver &" to your .xinitrc (before "exec gnome-session").
The lock screen this way is rather shabby, but better than nothing.

PSCS2 lockup with 50% CPU usage - never comes back

Hi, I've been trying to solve this very frustrating problem with no luck so far.
When I'm using custom brushes, often Photoshop CS2 will lock up and just churn using about 50% CPU and never unlock. I have to kill the photoshop process in task manager.
The source images for the custom brushes are usually no larger than 150 to 200 pixels in diameter. Is this too large?
My computer is Intel Pentium IV with 1 Gig RAM running XP.
I really hope someone can help me with this. I haven't had any luck looking around the forums so far.
I've tried playing around with the preferences file doing things like reducing the number of history states, changing the memory allocation number, deleting the preferences file, etc. Nothing of that sort seems to work.
Thanks in advance,
--James

150 to 200 pixels in diameter. Is this too large?....
Intel Pentium IV with 1 Gig RAM running XP.
Well, on your computer it is very likely too large. Sorry to say so, but the machine seems seriously inadequate for any kind of PS work and I definitely think that using excessively large brushes would kill it because the engine cannot accumulate and blend the individual "daubs" in memory before propagating them to the canvas as a stroke. In clearer words: You need much more RAM.
Mylenium

Different font when I start with startx instead of gdm

Things affected:
Terminal
Chromium URL/Tabs
i3 workspace numbers
What do I need to put on xinitrc to have the same font. Also how do I know which font gdm is loading?

Safari>Preferences>General>Homepage
Safari>Preferences>General>Safari opens with a new window
Have your running programs relaunch on start.
Shutdown dialog:
>Sys Preferences>General

Lockup with startx

Similar Messages

Maybe you are looking for