freezes under X with XFCE
in [Slackware]
|
Prev: Puppy Linux
Next: Firefox 3.0.15 breaks my email
From: Kevin Denis on 25 Nov 2009 08:36 Le 24-11-2009, barnabyh <invalid(a)address.org> a �crit�: >>> Maybe it would help to set >>> >>> Option "SWCursor" "false" >>> >>> in xorg.conf > Although it does not *need* an xorg.conf you can still have one, at > which point it will take settings from there. > I did: X -configure as root, then copy the file to /etc/X11/xorg.conf I saw the SWCursor option, I put False. When I launch X, mouse cursor doesn't appear. Then True. mouse cursor doens't appear neither. -- Kevin
From: Henrik Carlqvist on 25 Nov 2009 15:07 Kevin Denis <kevin(a)nowhere.invalid> wrote: > I saw the SWCursor option, I put False. When I launch X, mouse cursor > doesn't appear. Then True. mouse cursor doens't appear neither. Ouch, well at least it was worth a try. What if you replace the intel driver with vesa? With vesa you will lose some performance and might also not be able to use as high resolution and bit depth, but maybe the vesa driver will be good enough if it is capable of showing the cursor? regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost
From: Kevin Denis on 26 Nov 2009 03:41 Le 25-11-2009, Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> a �crit�: >> I saw the SWCursor option, I put False. When I launch X, mouse cursor >> doesn't appear. Then True. mouse cursor doens't appear neither. > > Ouch, well at least it was worth a try. > > What if you replace the intel driver with vesa? With vesa you will lose > some performance and might also not be able to use as high resolution and > bit depth, but maybe the vesa driver will be good enough if it is capable > of showing the cursor? > Another try, another FAIL :/ I did: mv /etc/X11/xorg.conf-vesa /etc/X11/xorg.conf I launch X, but screen is black. Nothing appears. From the network, I can log in, ps ax shows me every process right: 2978 tty1 S+ 0:00 /bin/sh /usr/bin/startx 2994 tty1 S+ 0:00 xinit /usr/lib/X11/xinit/xinitrc -- /usr/bin/X :0 -au (...) I can launch xeyes from the network without problem: 3043 pts/0 S 0:00 xeyes But my screen remains black.. In blind typing, I can do an alt-F2 (command box), then launch a process, which shows up in ps ax, but screen remains black. CTRL-ALT-BACKSPACE kills X, however. -- Kevin
From: Henrik Carlqvist on 27 Nov 2009 01:57 Kevin Denis <kevin(a)nowhere.invalid> wrote: > I did: > mv /etc/X11/xorg.conf-vesa /etc/X11/xorg.conf > > I launch X, but screen is black. What kind of monitor do you have? Does it give any kind of message about why it is going black? It could go black because there is no longer any signal and it could go black because the refresh rates are out of range. Another question is if you have more than one output from the graphics card? As you have intel graphics chipset I guess that the graphics card is builtin to the motherboard? If you have both VGA and DVI output it could be that the signal is sent out on VGA while the monitor is connedted to DVI. Even if you only have one single connector and that connector is DVI it could still be consiedered to be two different connectors. The DVI-I connector can have both (or rather either) digital signals or analog VGA signals by an adaptor. If you have lost the signal from the monitor, would it help to connect a VGA cable instead of a DVI cable? regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost
From: Kevin Denis on 27 Nov 2009 05:57
Le 27-11-2009, Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> a �crit�: >> I launch X, but screen is black. > > What kind of monitor do you have? TFT 17" Samsung syncmaster 930BF > Does it give any kind of message about > why it is going black? It could go black because there is no longer any > signal and it could go black because the refresh rates are out of range. > non. Still nothing in Xorg.log, except that it says: (II) VESA(0): Total Memory: 125 64KB banks (8000kB) (II) VESA(0): My Monitor: Using hsync range of 31.50-50.00 kHz (II) VESA(0): My Monitor: Using vrefresh range of 40.00-90.00 Hz (II) VESA(0): My Monitor: Using maximum pixel clock of 140.00 MHz (II) VESA(0): Not using built-in mode "1600x1200" (width too large for virtual size) (II) VESA(0): Not using built-in mode "1280x1024" (width too large for virtual size) (--) VESA(0): Virtual size is 1024x768 (pitch 1024) (**) VESA(0): *Built-in mode "1024x768" (**) VESA(0): *Built-in mode "800x600" (**) VESA(0): *Built-in mode "640x480" (**) VESA(0): Display dimensions: (380, 300) mm (**) VESA(0): DPI set to (68, 65) (**) VESA(0): Using "Shadow Framebuffer" > Another question is if you have more than one output from the graphics > card? no > As you have intel graphics chipset I guess that the graphics card is > builtin to the motherboard? yes > If you have both VGA and DVI output no > it could > be that the signal is sent out on VGA while the monitor is connedted to > DVI. > > Even if you only have one single connector and that connector is DVI it > could still be consiedered to be two different connectors. The DVI-I > connector can have both (or rather either) digital signals or analog VGA > signals by an adaptor. > > If you have lost the signal from the monitor, would it help to connect a > VGA cable instead of a DVI cable? > It's allready a VGA cable. -- Kevin |