freezes under X with XFCE
Kevin Denis
I just did a fresh install on a PC of a slack13.
Everything was installed, except KDE.
I launched xfce for graphical environment. It freezes very often (4th times
this afternoon after install).
I don't know why it freezes, once it was under xcreensaver.
Strangely, the mouse still works (!!) I can move the mouse everywhere (but
mouseclicks doesn't do anything).
The keyboard is completely stucks.
mouse and keyboard are PS/2.
The network works fine. The /var/log/Xorg.0.log doesn't show anything.
The graphic card is a
00:02.0 VGA compatible controller: Intel Corporation
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
I'm stuck under this freezes, and I'm forced to reboot from the
network.
Any body have any idea?
Thanks.
--
Kevin
Henrik Carlqvist
> I'm stuck under this freezes, and I'm forced to reboot from the
> network.
>
> Any body have any idea?
If the mouse or keyboard are dead, maybe you could try any of the
following from the network login to see if it gets you mouse or keyboard
functionality back:
killall X
chvt 2
Or from the X console, what would happen if you connect a USB keyboard and
a USB mouse? Would you be able to use them? On working systems extra
connected USB input devices usually work directly.
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@localhost postmaster@localhost
Lew Pitcher
(ke...@nowhere.invalid) wrote:
> Hello
>
> I just did a fresh install on a PC of a slack13.
> Everything was installed, except KDE.
>
> I launched xfce for graphical environment. It freezes very often (4th
> times this afternoon after install).
>
> I don't know why it freezes, once it was under xcreensaver.
>
> Strangely, the mouse still works (!!) I can move the mouse everywhere (but
> mouseclicks doesn't do anything).
> The keyboard is completely stucks.
> mouse and keyboard are PS/2.
>
> The network works fine. The /var/log/Xorg.0.log doesn't show anything.
/var/log was going to be my first suggestion. So, next...
What does ~/.xsession-errors have in it, when your X session freezes?
> I'm stuck under this freezes, and I'm forced to reboot from the
> network.
Hmmmm... <ctrl><alt><f6> doesn't take you to a console with logon?
Does <ctrl><alt><backspace> kill X for you (or did Pat V disable that with
the new X server)?
> Any body have any idea?
> Thanks.
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------
allend
Support for Intel graphics is problematic with Slackware 13.
Your best hope is to upgrade to a newer kernel (2.6.31.4)or later) and
also install a newer intel driver (2.9.0 or later).
Even then, that 82845G may be a problem.
http://www.linuxquestions.org/questions/slackware-14/testing-request-xorg-in-current-yes-again-742820/page12.html
Kevin Denis
>> I'm stuck under this freezes, and I'm forced to reboot from the
>> network.
>>
>> Any body have any idea?
>
> If the mouse or keyboard are dead
No, the mouse still works (!).
> maybe you could try any of the
> following from the network login to see if it gets you mouse or keyboard
> functionality back:
>
> killall X
>
> chvt 2
>
> Or from the X console, what would happen if you connect a USB keyboard and
> a USB mouse?
Don't have any of them.
> Would you be able to use them? On working systems extra
> connected USB input devices usually work directly.
>
Nope, even after killing X, it doesn't work;
But, I have found something else.
When X is frozen everything is really slow. (it takes about 10mn to
install a pkg). loadavg is at 0.
If I kill X, I don't have anything back (except network of
course), but installpkg can install package in seconds. Strange.
--
Kevin
Kevin Denis
>> I just did a fresh install on a PC of a slack13.
>> Everything was installed, except KDE.
>>
>> I launched xfce for graphical environment. It freezes very often (4th
>> times this afternoon after install).
>>
>> I don't know why it freezes, once it was under xcreensaver.
>>
>> Strangely, the mouse still works (!!) I can move the mouse everywhere (but
>> mouseclicks doesn't do anything).
>> The keyboard is completely stucks.
>> mouse and keyboard are PS/2.
>>
>> The network works fine. The /var/log/Xorg.0.log doesn't show anything.
>
> /var/log was going to be my first suggestion. So, next...
>
> What does ~/.xsession-errors have in it, when your X session freezes?
>
>> I'm stuck under this freezes, and I'm forced to reboot from the
>> network.
>
> Hmmmm... <ctrl><alt><f6> doesn't take you to a console with logon?
>
no
> Does <ctrl><alt><backspace> kill X for you (or did Pat V disable that with
> the new X server)?
>
no
ctrl-alt-del doesn't reboot the PC.
--
Kevin
Kevin Denis
>> The graphic card is a
>> 00:02.0 VGA compatible controller: Intel Corporation
>> 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
>>
Ok. Bad.
> Your best hope is to upgrade to a newer kernel (2.6.31.4)or later) and
> also install a newer intel driver (2.9.0 or later).
> Even then, that 82845G may be a problem.
So, it's related to that video card? I can't switch that card.
> http://www.linuxquestions.org/questions/slackware-14/testing-request-xorg-in-current-yes-again-742820/page12.html
>
Argh! In other words, it means no hope?
--
Kevin
Kevin Denis
>>> The graphic card is a
>>> 00:02.0 VGA compatible controller: Intel Corporation
>>> 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
>>>
>> Support for Intel graphics is problematic with Slackware 13.
>
> Ok. Bad.
>
http://wiki.archlinux.org/index.php/Intel_Graphics
--
Kevin
Henrik Carlqvist
> When X is frozen everything is really slow. (it takes about 10mn to
> install a pkg). loadavg is at 0.
> If I kill X, I don't have anything back (except network of
> course), but installpkg can install package in seconds. Strange.
Does dmesg give any clue about what is going on?
Jerry Peters
> Kevin Denis <ke...@nowhere.invalid> wrote:
>> When X is frozen everything is really slow. (it takes about 10mn to
>> install a pkg). loadavg is at 0.
>> If I kill X, I don't have anything back (except network of
>> course), but installpkg can install package in seconds. Strange.
>
> Does dmesg give any clue about what is going on?
>
> regards Henrik
Also take a look at /var/log/Xorg.0.log.
Jerry
Mikhail Zotov
Kevin Denis <ke...@nowhere.invalid> wrote:
No, it doesn't.
Install the latest 2.6.31.x kernel as suggested by allend and it is
likely the problem will be solved. Earlier, I reported a similar
problem with this Intel video chipset on AOLS and it being solved
with a 2.6.31.x kernel.
--
Mikhail
Kevin Denis
> Install the latest 2.6.31.x kernel as suggested by allend and it is
> likely the problem will be solved.
The file CHANGE_AND_HINT gives a clue:
If you want to try the new kernel mode setting (KMS), you don't have to
build a custom kernel; add this to your kernel's lilo stanza:
append = "i915.modeset=1"
So I did. It seems to work really better (so far +1hour working without
freeze) but the mouse cursor is gone! It work (I can click my menus)
but cursor doesn't show up...
I tried to deactive vga=xxx in lilo.conf -> no luck.
I tried to update the last xf86-video-intel in
slackware-13.0/extra/xf86-video-intel-alternate/ without luck.
> Earlier, I reported a similar
> problem with this Intel video chipset on AOLS and it being solved
> with a 2.6.31.x kernel.
>
I read that with newer kernel, the KMS is on by default.
Maybe this explains that ?
--
Kevin
Henrik Carlqvist
> but the mouse cursor is gone! It work (I can click my menus)
> but cursor doesn't show up...
> I tried to update the last xf86-video-intel in
> slackware-13.0/extra/xf86-video-intel-alternate/ without luck.
Maybe it would help to set
Option "SWCursor" "false"
in xorg.conf
Kevin Denis
>> I tried to update the last xf86-video-intel in
>> slackware-13.0/extra/xf86-video-intel-alternate/ without luck.
>
> Maybe it would help to set
>
> Option "SWCursor" "false"
>
> in xorg.conf
>
autoprobed, or configured through hal.
So, where do I put this option?
Thanks
--
Kevin
jo...@wexfordpress.com
> Le 23-11-2009, Henrik Carlqvist <Henrik.Carlqv...@deadspam.com> a écrit :>> I tried to update the last xf86-video-intel in
> >> slackware-13.0/extra/xf86-video-intel-alternate/ without luck.
>
> > Maybe it would help to set
>
> > Option "SWCursor" "false"
>
> > in xorg.conf
>
> There's no xorg.conf in the slackware13. Everything should be either
> autoprobed, or configured through hal.
> So, where do I put this option?
> Thanks
> --
> Kevin
My suggestion:
Either copy /etc/X11/xorg.conf-vesa to xorg.conf or do what I did,
copy the old xorg.conf from a working 12.2 partition.
Autoprobing adds no functionality to my system. Once I set up
xorg.conf the way I want then nothing needs to be changed.
John Culleton
barnabyh
Although it does not *need* an xorg.conf you can still have one, at
which point it will take settings from there.
Barnaby
--
5 years of Linux only - and loving it.
Kevin Denis
>>> Maybe it would help to set
>>>
>>> Option "SWCursor" "false"
>>>
>>> in xorg.conf
> which point it will take settings from there.
>
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
Henrik Carlqvist
> 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?
Kevin Denis
>> 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?
>
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
Henrik Carlqvist
> 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?
Kevin Denis
>> 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
Grant
>Le 27-11-2009, Henrik Carlqvist <Henrik.C...@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
. ^^^^^^^^^^^^^^
Limit above to 59-61 Hz for LCD monitor (nominal 60Hz).
Henrik Carlqvist
>>(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
> Limit above to 59-61 Hz for LCD monitor (nominal 60Hz).
Yes, edit xorg.conf and look for lines looking something like this:
HorizSync 24-94
VertRefresh 49-86
Then edit those ranges to match the exact specifications of your monitor.
Grant
>Grant <g_r_a...@bugsplatter.id.au> wrote:
>>>(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
>
>> Limit above to 59-61 Hz for LCD monitor (nominal 60Hz).
>
>Yes, edit xorg.conf and look for lines looking something like this:
>
> HorizSync 24-94
> VertRefresh 49-86
>
>Then edit those ranges to match the exact specifications of your monitor.
I found sometimes using exact range for LCD sometimes didn't work as
xorg would try to sync at 59Hz or close but not equal to 60Hz. Hence I
reccommend the small vertical range.
As far as horizontal range goes, if you don't have your LCD manual it's
okay to leave horizontal range wide -- more important is to specify the
narrow vertical range and the correct (native resolution) LCD X by Y
pixels -- xorg should then calculate the correct horizontal value.
The x startup log would indicate if the resolution numbers attempted
go out of range for your screen.
Grant.
--
http://bugsplatter.id.au