Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
X.org Lockups (part III)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 9, 10, 11, 12  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
poly_poly-man
Advocate
Advocate


Joined: 06 Dec 2006
Posts: 2477
Location: RIT, NY, US

PostPosted: Thu Jul 31, 2008 3:43 am    Post subject: Reply with quote

I'm up to almost 5 days - #2 in my uprecords.

The only difference? I didn't start fancontrol (I need to start it manually).

Does this mean anything? or total coincidence?

poly-p man
_________________
iVBORw0KGgoAAAANSUhEUgAAA

avatar: new version of logo - see topic 838248. Potentially still a WiP.
Back to top
View user's profile Send private message
notHerbert
Advocate
Advocate


Joined: 11 Mar 2008
Posts: 2228
Location: 45N 73W

PostPosted: Sun Sep 07, 2008 4:05 pm    Post subject: Reply with quote

Maybe this can help http://www.gentoo.org/doc/en/articles/hardware-stability-p2.xml#doc_chap2 :D
Back to top
View user's profile Send private message
.yankee
Apprentice
Apprentice


Joined: 24 Feb 2008
Posts: 194
Location: Polska

PostPosted: Tue Sep 30, 2008 11:55 am    Post subject: Reply with quote

Okay, so here's my record...

I do get the lockups from time to time (mostly in the version, that mouse can still move and CPU usage not very high). My observations are :

  • in a great majority of cases, it happens, while just browsing (I mostly use opera)
  • the suggestions with kernel options (i/o scheduler especially) and vm settings do help
  • one strange thing I've noticed lately, that it did NOT happen, when for quite some time I had no access to the Internet (even though I ran Opera, browsing local files)
  • almost always, the acpid is left as the only thing that CAN respond to events, so I created a helpful script, which:
    - is activated by the power-button
    - uses /usr/bin/chvt 1 to switch the active terminal - this is often enough to keep working without reboot
    - kills X and dm
    - if X cannot get killed in some number of tries, it goes into a try-hard-to-shutdown loop
    - if the button is pressed while no X nor *dm is running, then just shutdown


Has anyone had any experiences with a computer that was offline? I don't much believe in that being an important reason, but it won't hurt to check...

My computer:
- Dell Latitude C610 (Radeon M6 LY, 1200/800 MHz Pentium3-m)
- latest stable version (6.5.2-r1 now) mesa radeon drivers, with drm/dri
- same with xorg-server (1.3.0.0-r6 now) and xorg-x11 (7.2)
- AIGLX enabled, direct rendering etc.
- Xfce4 on top of Compiz, with Emerald as the decorator.
Back to top
View user's profile Send private message
reavertm
Developer
Developer


Joined: 05 Feb 2004
Posts: 264
Location: Wrocław

PostPosted: Fri Oct 03, 2008 5:55 pm    Post subject: Reply with quote

For anyone interested - don't use -ftree-vectorize - it breaks xorg-server (at least xorg-server-1.5.1 and xorg-server-9999) on gcc-4.3.1 and amd64 platform.
_________________
Maciek
Back to top
View user's profile Send private message
Joseph K.
Guru
Guru


Joined: 07 Jun 2006
Posts: 400
Location: Melbourne, Australia

PostPosted: Sun Oct 19, 2008 10:01 am    Post subject: Reply with quote

Forgive me if this one has already been mentioned, I did try searching for it beforehand.

After using X for a few hours, the keyboard suddenly develops a ~1 second lag between keypress and result. That is, if I type something at normal typing speed, nothing happens. A keypress has to be held for a second or so before X responds to it. Weird, no? This is ~amd64, so it's xorg-server-1.5.2. Not sure if it happened with 1.5.1 since I didn't use it for long, but it's been happening somewhat regularly now.

This is the relevant section from my xorg.conf:
Code:
Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Should I be using a different driver, like evdev or something? I switched my mouse over to evdev when I upgraded to 1.5, but otherwise my config file is pretty much as it was when I was running 1.3. Thanks, cheers.
Back to top
View user's profile Send private message
carpman
Advocate
Advocate


Joined: 20 Jun 2002
Posts: 2202
Location: London - UK

PostPosted: Mon Oct 20, 2008 9:18 pm    Post subject: Reply with quote

Joseph K. wrote:
Forgive me if this one has already been mentioned, I did try searching for it beforehand.

After using X for a few hours, the keyboard suddenly develops a ~1 second lag between keypress and result. That is, if I type something at normal typing speed, nothing happens. A keypress has to be held for a second or so before X responds to it. Weird, no? This is ~amd64, so it's xorg-server-1.5.2. Not sure if it happened with 1.5.1 since I didn't use it for long, but it's been happening somewhat regularly now.

This is the relevant section from my xorg.conf:
Code:
Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Should I be using a different driver, like evdev or something? I switched my mouse over to evdev when I upgraded to 1.5, but otherwise my config file is pretty much as it was when I was running 1.3. Thanks, cheers.


I have this same problem but as yet no solution?
_________________
Work Station - 64bit
Gigabyte GA X48-DQ6 Core2duo E8400
8GB GSkill DDR2-1066
SATA Areca 1210 Raid
BFG OC2 8800 GTS 640mb
--------------------------------
Notebook
Samsung Q45 7100 4gb
Back to top
View user's profile Send private message
Joseph K.
Guru
Guru


Joined: 07 Jun 2006
Posts: 400
Location: Melbourne, Australia

PostPosted: Mon Oct 20, 2008 11:16 pm    Post subject: Reply with quote

carpman wrote:

I have this same problem but as yet no solution?

Could we possibly have 1.5.0/1.5.1 back in the tree to test with? Where is the upstream X.org bugzilla/user forum?
Back to top
View user's profile Send private message
desultory
Administrator
Administrator


Joined: 04 Nov 2005
Posts: 8034

PostPosted: Tue Oct 21, 2008 5:23 am    Post subject: Reply with quote

Joseph K. wrote:
Could we possibly have 1.5.0/1.5.1 back in the tree to test with?
That is unnecessary.
Joseph K. wrote:
Where is the upstream X.org bugzilla/user forum?
https://bugs.freedesktop.org/
Back to top
View user's profile Send private message
Joseph K.
Guru
Guru


Joined: 07 Jun 2006
Posts: 400
Location: Melbourne, Australia

PostPosted: Tue Oct 21, 2008 12:15 pm    Post subject: Reply with quote

desultory wrote:
Joseph K. wrote:
Could we possibly have 1.5.0/1.5.1 back in the tree to test with?
That is unnecessary.
Joseph K. wrote:
Where is the upstream X.org bugzilla/user forum?
https://bugs.freedesktop.org/

Thanks. Can you elaborate on why it is unnecessary? I'm afraid that list of ebuilds is not very illuminating for me.
Back to top
View user's profile Send private message
desultory
Administrator
Administrator


Joined: 04 Nov 2005
Posts: 8034

PostPosted: Wed Oct 22, 2008 2:03 am    Post subject: Reply with quote

Reintroducing an old version to the tree for testing purposes would be pointless considering that everything necessary to install that version of that package is available to anyone interested. All that is required is downloading a few files and placing them in a local overlay, at which point the package would be available to that system just as it would be using an old snapshot of the tree or if the old version of the package was reintroduced to the tree.
Back to top
View user's profile Send private message
Joseph K.
Guru
Guru


Joined: 07 Jun 2006
Posts: 400
Location: Melbourne, Australia

PostPosted: Wed Oct 22, 2008 5:26 am    Post subject: Reply with quote

desultory wrote:
Reintroducing an old version to the tree for testing purposes would be pointless considering that everything necessary to install that version of that package is available to anyone interested. All that is required is downloading a few files and placing them in a local overlay, at which point the package would be available to that system just as it would be using an old snapshot of the tree or if the old version of the package was reintroduced to the tree.

Right, thanks. (I've not used an overlay before, so it's unfamiliar terrain for me.) So why, out of curiosity, are the old minor versions of xorg-server removed immediately like that? Compared with, say, dhcpcd or util-linux or even gentoo-sources?
Back to top
View user's profile Send private message
desultory
Administrator
Administrator


Joined: 04 Nov 2005
Posts: 8034

PostPosted: Wed Oct 22, 2008 5:48 am    Post subject: Reply with quote

Joseph K. wrote:
I've not used an overlay before, so it's unfamiliar terrain for me.
In itself, it is quite simple to do.
Joseph K. wrote:
So why, out of curiosity, are the old minor versions of xorg-server removed immediately like that? Compared with, say, dhcpcd or util-linux or even gentoo-sources?
That is entirely up to those maintaining the packages, outside of a specific set of packages which this is not a part of.
Back to top
View user's profile Send private message
Joseph K.
Guru
Guru


Joined: 07 Jun 2006
Posts: 400
Location: Melbourne, Australia

PostPosted: Mon Nov 03, 2008 7:12 am    Post subject: Reply with quote

carpman wrote:
Joseph K. wrote:
Forgive me if this one has already been mentioned, I did try searching for it beforehand.

After using X for a few hours, the keyboard suddenly develops a ~1 second lag between keypress and result. That is, if I type something at normal typing speed, nothing happens. A keypress has to be held for a second or so before X responds to it. Weird, no? This is ~amd64, so it's xorg-server-1.5.2. Not sure if it happened with 1.5.1 since I didn't use it for long, but it's been happening somewhat regularly now.

This is the relevant section from my xorg.conf:
Code:
Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Should I be using a different driver, like evdev or something? I switched my mouse over to evdev when I upgraded to 1.5, but otherwise my config file is pretty much as it was when I was running 1.3. Thanks, cheers.


I have this same problem but as yet no solution?

What version of xorg-server and xf86-input-keyboard are you using? I just realised that I upgraded xf86-input-keyboard from 1.1 to 1.3 around the same that I upgraded xorg-server from 1.3 to 1.5. I'm going to try downgrading xorg-server to see if it fixes the problem; do you want to try downgrading your xf86-input-keyboard?
Back to top
View user's profile Send private message
SHINODATT
n00b
n00b


Joined: 07 Jan 2006
Posts: 70
Location: Ontario, Canada

PostPosted: Wed Nov 12, 2008 7:55 am    Post subject: Reply with quote

Upgraded to the most recent kernel (and had filed a bug about the JMicron issue) and I'm still having to keep my JMicron controller disabled.
_________________
Board: Maximus Formula, Rampage conversion, BIOS 308
CPU: Q6600 G0 @ 3.47Ghz (385x9), CM Hyper 212 Cooler
RAM: 4x 2GB Kingston 667 @ 771Mhz, 2V
Video: ASUS GeForce 8800GTS 512MB
OS: Gentoo 2.6.29 x86_64
Back to top
View user's profile Send private message
unkulunkulu
n00b
n00b


Joined: 09 Oct 2007
Posts: 53
Location: Russia

PostPosted: Sun Nov 16, 2008 6:14 pm    Post subject: Reply with quote

Hello. I've been using ati hd 2006 pro with two monitors not configuring dual-head/xinerama and it was working fine.
But once I configured dual-head mode (using aticonfig + manually editing xorg.conf) I'm getting X locked when I try to stop it using C-M-BkSp (no mouse moving, keyboard leds don't react on pressing the corresponding keys and, consequently, I can't switch to terminals) It doesn't even matter whether I run startx and use fluxbox, or just the standalone X. Only Magic SysRq S(ync) U(mount) re(B)oot helps me out.

But! That's not all. I do can switch to a terminal and terminate X from there. But when I then try to start X again, it hangs and I'm unable to do SysRq re(B)oot and have to do a hardreset.

It definitely has something to do with that moment when the video driver switches between "mirroring"/"stripping" modes.
Back to top
View user's profile Send private message
unkulunkulu
n00b
n00b


Joined: 09 Oct 2007
Posts: 53
Location: Russia

PostPosted: Mon Nov 17, 2008 11:54 pm    Post subject: Reply with quote

Well, driver update did help, but the newer driver doesn't seem to support xinerama and this is sht
Back to top
View user's profile Send private message
GODhack
Guru
Guru


Joined: 26 Jan 2008
Posts: 389
Location: Lithuania

PostPosted: Mon Dec 22, 2008 1:07 pm    Post subject: Reply with quote

Today I had 2 lockups, both times in this scenario:
Quote:

wine 1.1.11 tram tam
turn off wine
firefox 2.0.0.19
5 minutes Ok
click on link and bum.

Strange :roll:
_________________
http://www.youtube.com/watch?v=4jtmOZaIvS0
Back to top
View user's profile Send private message
flacvest
Apprentice
Apprentice


Joined: 04 Jun 2008
Posts: 152
Location: San Jose, CA USA

PostPosted: Tue Mar 03, 2009 6:24 am    Post subject: I am having Xorg-server issues (1.5.3-r2) and logging out... Reply with quote

My X Server locks up whenever I try to log out of Xfce 4.4.3 (the only Desktop Environment I have installed) I have components of KDE and GNOME which I run as services. This never happened before installing Compiz-Fusion. But even with it turned off/unloaded and using Xfwm4 (compiled with XComposite) I get the logout lockups and have to do a HARD REBOOT.

Any Ideas?
_________________
.:{flacvest}:.
Back to top
View user's profile Send private message
stanislaw
n00b
n00b


Joined: 08 Jan 2008
Posts: 66

PostPosted: Fri Mar 13, 2009 8:51 pm    Post subject: Reply with quote

If I get it right, there is still no real solution for the X.org lockups?

After updating to KDE 4.2 / xorg-server 1.5 following the official guide I occasionally run into a xorg-lockup. I can move the mousepointer but nothing else happens. Logging in via ssh from a notebook I can see X consuming 100% of one of my two (hyperthreading) cpus (P4 3GHz). This is annoying as it is not able to work reliable on my system.

Is there any proved solution for this problem? Which is the standard information I shall provide?

Why didn't this happen with old xorg-server 1.3 (this was a rocking solid solution with KDE 3.5)?
Back to top
View user's profile Send private message
kacox
n00b
n00b


Joined: 17 Mar 2006
Posts: 39
Location: Raleigh, NC

PostPosted: Sat Mar 21, 2009 10:30 am    Post subject: Reply with quote

I'm having a strange issue, and I'll see if I can post my xorg.conf, but I have no access to my keyboard or mouse.


X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27-gentoo-r8 i686
Current Operating System: Linux localhost 2.6.27-gentoo-r8 #2 SMP PREEMPT Wed Mar 18 09:56:36 EDT 2009 i686
Build Date: 20 March 2009 02:40:44PM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 20 17:02:18 2009
(++) Using config file: "/root/xorg.conf.new"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/TTF/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/OTF" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/TTF/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/OTF" does not exist.
Entry deleted from font path.
(**) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/,
/usr/share/fonts/misc/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/,
built-ins
(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0

(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x9e0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
(II) Loader running on linux
(--) using VT number 7

(--) PCI:*(0@1:0:0) nVidia Corporation NV34M [GeForce FX Go5200 64M] rev 161, Mem @ 0xfc000000/0, 0xd0000000/0, BIOS @ 0x????????/131072
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "wfb"

(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) LoadModule: "glx"

(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 173.14.15 Fri Oct 31 16:29:34 PST 2008
(II) Loading extension GLX
(II) LoadModule: "dbe"

(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"

(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "record"

(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension RECORD
(II) LoadModule: "xtrap"

(II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
(II) Module xtrap: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DEC-XTRAP
(II) LoadModule: "dri"

(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "nv"

(II) Loading /usr/lib/xorg/modules/drivers//nv_drv.so
(II) Module nv: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 2.1.12
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 4.1
(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
GeForce4 420 Go 32M, GeForce4 460 Go, Quadro4 550 XGL,
GeForce4 440 Go 64M, Quadro NVS, Quadro4 500 GoGL,
GeForce4 410 Go 16M, GeForce4 MX 440 with AGP8X,
GeForce4 MX 440SE with AGP8X, GeForce4 MX 420 with AGP8X,
GeForce4 MX 4000, GeForce4 448 Go, GeForce4 488 Go, Quadro4 580 XGL,
Quadro4 NVS 280 SD, Quadro4 380 XGL, Quadro NVS 50 PCI,
GeForce4 448 Go, GeForce4 MX Integrated GPU, GeForce3,
GeForce3 Ti 200, GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600,
GeForce4 Ti 4400, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
GeForce FX 5600 Ultra, GeForce FX 5600, GeForce FX 5600XT,
GeForce FX Go5600, GeForce FX Go5650, Quadro FX Go700,
GeForce FX 5200, GeForce FX 5200 Ultra, GeForce FX 5200,
GeForce FX 5200LE, GeForce FX Go5200, GeForce FX Go5250,
GeForce FX 5500, GeForce FX 5100, GeForce FX Go5200 32M/64M,
Quadro NVS 55/280 PCI, Quadro FX 500/600 PCI,
GeForce FX Go53xx Series, GeForce FX Go5100, GeForce FX 5900 Ultra,
GeForce FX 5900, GeForce FX 5900XT, GeForce FX 5950 Ultra,
GeForce FX 5900ZT, Quadro FX 3000, Quadro FX 700,
GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE,
GeForce FX 5700VE, GeForce FX Go5700, GeForce FX Go5700,
Quadro FX Go1000, Quadro FX 1100, GeForce 6800 Ultra, GeForce 6800,
GeForce 6800 LE, GeForce 6800 XE, GeForce 6800 XT, GeForce 6800 GT,
GeForce 6800 GT, GeForce 6800 GS, GeForce 6800 XT, Quadro FX 4000,
GeForce 6800 GS, GeForce 6800, GeForce 6800 LE, GeForce 6800 XT,
GeForce Go 6800, GeForce Go 6800 Ultra, Quadro FX Go1400,
Quadro FX 3450/4000 SDI, Quadro FX 1400, GeForce 6600 GT,
GeForce 6600, GeForce 6600 LE, GeForce 6600 VE, GeForce Go 6600,
GeForce 6610 XL, GeForce Go 6600 TE/6200 TE, GeForce 6700 XL,
GeForce Go 6600, GeForce Go 6600 GT, Quadro FX 550, Quadro FX 550,
Quadro FX 540, GeForce 6200, GeForce 6500,
GeForce 6200 TurboCache(TM), GeForce 6200SE TurboCache(TM),
GeForce 6200 LE, GeForce Go 6200, Quadro NVS 285, GeForce Go 6400,
GeForce Go 6200, GeForce Go 6400, GeForce 6250, GeForce 6800,
GeForce 6800 LE, GeForce 6800 GT, GeForce 6800 XT, GeForce 6200,
GeForce 6200 A-LE, GeForce 7800 GTX, GeForce 7800 GTX,
GeForce 7800 GT, GeForce 7800 GS, GeForce 7800 SLI, GeForce Go 7800,
GeForce Go 7800 GTX, Quadro FX 4500, GeForce 7300 LE,
GeForce 7300 SE, GeForce Go 7200, GeForce Go 7300, GeForce Go 7400,
GeForce Go 7400 GS, Quadro NVS 110M, Quadro NVS 120M, Quadro FX 350M,
GeForce 7500 LE, Quadro FX 350, GeForce 7300 GS, GeForce 7600 GT,
GeForce 7600 GS, GeForce 7300 GT, GeForce 7600 LE, GeForce 7300 GT,
GeForce Go 7700, GeForce Go 7600, GeForce Go 7600 GT,
Quadro NVS 300M, GeForce Go 7900 SE, Quadro FX 550M, Quadro FX 560,
GeForce 7900 GTX, GeForce 7900 GT, GeForce 7900 GS,
GeForce Go 7900 GS, GeForce Go 7900 GTX, Quadro FX 2500M,
Quadro FX 1500M, Quadro FX 5500, Quadro FX 3500, Quadro FX 1500,
Quadro FX 4500 X2, GeForce 6150, GeForce 6150 LE, GeForce 6100,
GeForce Go 6150, GeForce Go 6100, GeForce 8800 GTX, GeForce 8800 GTS,
GeForce 8800 Ultra, Quadro FX 5600, Quadro FX 4600, GeForce 8600 GTS,
GeForce 8600 GT, GeForce 8600 GT, GeForce 8600 GS, GeForce 8400 GS,
GeForce 9500M GS, GeForce 8600M GT, GeForce 9650M GS,
GeForce 8700M GT, Quadro FX 370, Quadro NVS 320M, Quadro FX 570M,
Quadro FX 1600M, Quadro FX 570, Quadro FX 1700, GeForce 8400 SE,
GeForce 8500 GT, GeForce 8400 GS, GeForce 8300 GS, GeForce 8400 GS,
GeForce 8600M GS, GeForce 8400M GT, GeForce 8400M GS,
GeForce 8400M G, Quadro NVS 140M, Quadro NVS 130M, Quadro NVS 135M,
GeForce 9400 GT, Quadro FX 360M, GeForce 9300M G, Quadro NVS 290,
GeForce GTX 280, GeForce GTX 260, GeForce 8800 GTS 512,
GeForce 8800 GT, GeForce 9800 GX2, GeForce 8800 GS,
GeForce 8800M GTS, GeForce 8800M GTX, GeForce 8800 GS,
GeForce 9600 GSO, GeForce 8800 GT, GeForce 9800 GTX,
GeForce 9800 GTK+, GeForce 9800 GT, Quadro FX 3700, Quadro FX 3600M,
GeForce 9600 GT, GeForce 9600 GS, GeForce 9800M GTS,
GeForce 9700M GTS, GeForce 9800M GTS, GeForce 9500 GT,
GeForce 9600M GT, GeForce 9600M GS, GeForce 9600M GT,
GeForce 9500M G, GeForce 9300 GS, GeForce 8400 GS, GeForce 9300M GS,
GeForce 9200M GS, GeForce 9300M GS, Quadro NVS 150M, Quadro NVS 160M
(II) Primary Device is: PCI 01@00:00:0
(--) NV: Found NVIDIA GeForce FX Go5200 at 01@00:00:0
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) Loading sub module "int10"
(II) LoadModule: "int10"

(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Video Driver, version 4.1
(II) NV(0): Initializing int10
(II) NV(0): Primary V_BIOS segment is: 0xc000
(--) NV(0): Chipset: "GeForce FX Go5200"
(==) NV(0): Depth 24, (--) framebuffer bpp 32
(==) NV(0): RGB weight 888
(==) NV(0): Default visual is TrueColor
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"

(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 0.1.0
ABI class: X.Org Video Driver, version 4.1
(==) NV(0): Using HW cursor
(--) NV(0): Linear framebuffer at 0xD0000000
(--) NV(0): MMIO registers at 0xFC000000
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) NV(0): I2C bus "DDC" initialized.
(II) NV(0): Probing for analog device on output A...
(--) NV(0): ...can't find one
(II) NV(0): Probing for analog device on output B...
(--) NV(0): ...can't find one
(II) NV(0): Probing for EDID on I2C bus A...
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(II) NV(0): ... none found
(II) NV(0): Probing for EDID on I2C bus B...
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(II) NV(0): ... none found
(--) NV(0): CRTC 0 is currently programmed for DFP
(II) NV(0): Using DFP on CRTC 0
(--) NV(0): Panel size is 1400 x 1050
(II) NV(0): NOTE: This driver cannot reconfigure the BIOS-programmed size.
(II) NV(0): These dimensions will be used as the panel size for mode validation.
(II) NV(0): Panel is LVDS
(--) NV(0): VideoRAM: 65536 kBytes
(==) NV(0): Using gamma correction (1.0, 1.0, 1.0)
(II) NV(0): Monitor0: Using hsync range of 0.00-64.74 kHz
(II) NV(0): Monitor0: Using vrefresh range of 0.00-59.95 Hz
(II) NV(0): Estimated virtual size for aspect ratio 1.3333 is 1400x1050
(II) NV(0): Clock range: 12.00 to 350.00 MHz
(II) NV(0): Not using default mode "640x350" (vrefresh out of range)
(II) NV(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "640x400" (vrefresh out of range)
(II) NV(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "720x400" (vrefresh out of range)
(II) NV(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "640x480" (vrefresh out of range)
(II) NV(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "640x480" (vrefresh out of range)
(II) NV(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "640x480" (vrefresh out of range)
(II) NV(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "800x600" (vrefresh out of range)
(II) NV(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "800x600" (vrefresh out of range)
(II) NV(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "800x600" (vrefresh out of range)
(II) NV(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1024x768" (vrefresh out of range)
(II) NV(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1024x768" (vrefresh out of range)
(II) NV(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1152x864" (hsync out of range)
(II) NV(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1280x960" (hsync out of range)
(II) NV(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1280x1024" (hsync out of range)
(II) NV(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1280x1024" (hsync out of range)
(II) NV(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) NV(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) NV(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) NV(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) NV(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) NV(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1792x1344" (width too large for virtual size)
(II) NV(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1792x1344" (width too large for virtual size)
(II) NV(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1856x1392" (width too large for virtual size)
(II) NV(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1856x1392" (width too large for virtual size)
(II) NV(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1920x1440" (width too large for virtual size)
(II) NV(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1920x1440" (width too large for virtual size)
(II) NV(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "832x624" (vrefresh out of range)
(II) NV(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1400x1050" (hsync out of range)
(II) NV(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "1920x1440" (width too large for virtual size)
(II) NV(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "2048x1536" (width too large for virtual size)
(II) NV(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "2048x1536" (width too large for virtual size)
(II) NV(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode "2048x1536" (width too large for virtual size)
(II) NV(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(--) NV(0): Virtual size is 1400x1050 (pitch 1408)
(**) NV(0): *Driver mode "1400x1050": 101.0 MHz, 64.7 kHz, 59.9 Hz
(II) NV(0): Modeline "1400x1050"x59.9 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz)
(**) NV(0): *Default mode "1400x1050": 122.0 MHz, 64.9 kHz, 60.0 Hz
(II) NV(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz)
(**) NV(0): *Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(II) NV(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(**) NV(0): *Default mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz
(II) NV(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
(**) NV(0): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) NV(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(**) NV(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) NV(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(**) NV(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) NV(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
(**) NV(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
(II) NV(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(==) NV(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"

(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"

(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.2.1
ABI class: X.Org Video Driver, version 4.1
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) NV(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Scanline Image Writes
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(==) NV(0): Backing store disabled
(==) NV(0): Silken mouse enabled
(II) NV(0): DPMS enabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)




BTW, sorry for not using a url, and I'm sure I'll find a way to get the GLX extension working at a later date. For now, I just want my keyboard and mouse to work.
DELL 5150, 3.2HT 1G Ram 64Mb nVidia GeForce FX Go5200 Synaptics touchpad.
_________________
Typically I'd do all the work, but for now I'll let you do it.
Back to top
View user's profile Send private message
stanislaw
n00b
n00b


Joined: 08 Jan 2008
Posts: 66

PostPosted: Sat Mar 21, 2009 10:38 am    Post subject: Reply with quote

@kacox: It's not really clear, what's your problem? Does your screen lock, i.e. your not able to click on things any more but e.g. are able to move your cursor around or is instead everything working fine but you just cannot use keyboard and mouse/touchpad? For the latter case I suppose you have to search for HAL, evdev and X related problems (I am sure, you'll find enough). This seems to be the case if you've updated from an old Xorg 1.3 due to several changes in Xorg 1.5
_________________
Gentoo forums back to Google! http://www.google.com/search?q=site%3Aforums.gentoo.org
Back to top
View user's profile Send private message
kacox
n00b
n00b


Joined: 17 Mar 2006
Posts: 39
Location: Raleigh, NC

PostPosted: Sat Mar 21, 2009 2:45 pm    Post subject: Reply with quote

I can start X, but as soon as it starts the mouse and keyboard are disabled completely. There isn't a way to switch tty or perform a normal reboot. I have to hard reboot every time.

WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0

I disabled this by adding
Option "AllowEmptyInput" "False"

into serverflags and I can now access my X. Although I have a working X complete with nVidia GLX, my fresh install of KDE 4.2.1 (On a fresh system install and update) is giving me problems now. I attribute my woes to evdev bypassing some of my modules. I just don't know why that option is enabled by default.

Thanks!
_________________
Typically I'd do all the work, but for now I'll let you do it.
Back to top
View user's profile Send private message
HMC
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jul 2005
Posts: 76
Location: Australia

PostPosted: Sat Jul 18, 2009 1:51 pm    Post subject: Reply with quote

kacox wrote:
...the mouse and keyboard are disabled completely...
I disabled this by adding
Option "AllowEmptyInput" "False"...
I just don't know why that option is enabled by default.


I think that we are supposed to be using hal for input devices... It is a painless enough change.

Cheers
Back to top
View user's profile Send private message
Satoshi
Apprentice
Apprentice


Joined: 06 Nov 2006
Posts: 180
Location: Brazil

PostPosted: Wed Aug 05, 2009 11:12 pm    Post subject: Reply with quote

Hey, guys!


I was having lockups too. Not the KDE or the recoverable variations, the ones where it really stops working whatever the Window Manager, generally (but not necessarily) associated with high CPU load (such as during compilations).

There were two ways to make it stop:

Using maxcpus=1 as a kernel argument or

Using the nv driver instead of nvidia.


Both would cease the problem completely.

Now, the How-I-Fixed-It part you might be waiting for:

Updating to nvidia-drivers 180.60 did. Simple as that. I also updated glibc, but I am guessing this had nothing to do with it.

Code:
satoshi@sunless ~ $ uptime
 20:10:45 up 13:52,  3 users,  load average: 0.37, 0.32, 0.46


I know it's still kinda early to brag, but it never lasted more than five hours during before using both cpus and nvidia driver, so I guess this is already a very good guess that it worked.
Back to top
View user's profile Send private message
njcwotx
Guru
Guru


Joined: 25 Feb 2005
Posts: 514
Location: Texas

PostPosted: Wed Sep 02, 2009 10:16 pm    Post subject: Reply with quote

FWIW, i had some serious lockups in xorg 1.5 with compiz and various effects, even to the point i had to reemerge a few times. I solved it by removing the .kde/ and .kde3.5/ folders and re installing the profile AND I setup to use hald and dbus and evdev for mouse and keyboard. Runs smooth now.
_________________
Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page Previous  1, 2, 3 ... 9, 10, 11, 12  Next
Page 10 of 12

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum