Re: X problem (?) after fresh install on old laptop
On Sun, 22 Apr 2012 11:57:05 -0700, Potato Jim wrote: Thanks for your advice! Camaleón wrote: Okay, so from now on you are using the nv driver, right? Yes, NV for now. Don't forget to give nouveau a whirl from a livecd media, it will be your better option in the future if you want expand the life of your old laptop :-) I realized that I now have one new issue, though not as bothersome as the original. When I CTRL+ALT+F* into a terminal window, or during the start-up/shut-down messages (when X is not running), the screen appears very dim, and has vertical lines that roll across it. Is there anything obvious that I can do to fix this? Hard to say... being your card quite old (for today standards, I mean) and the nv driver not maintained anymore, I bet there are not many documents out there you review :-(. You can try to set/tweak/play with whatever available options provides the nv driver that can be found in man nv. This does not happen when I boot into Recovery Mode -- only when I boot normally. Maybe because the recovery mode will boot with vesa/fb VGA driver instead nv (you can see check this point by reviewing your /var/log/Xorg.0.log, the driver in use is logged there) but that's a low level graphic driver used mostly as fallback when nothing more works but not convenient (meaning: less configurable, less options, less capable) if you are using a graphical environment. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jn3q5r$68l$2...@dough.gmane.org
Re: X problem (?) after fresh install on old laptop
On Sat, 21 Apr 2012 18:33:22 -0700, Potato Jim wrote: SOLVED. Great! :-) In my last response I had overlooked Sven's comment about having updated the wiki. I have now looked at the updated wiki and the suggested new xorg.conf file did the trick -- verbatim even, and I'm now using the NV driver. More precisely, I blacklisted nouveau in a blacklist-nouveau.conf file and created a new xorg.conf file, specifying the NV driver (I also re-blacklisted nvidiafb in /etc /modeprobe.d/fbdev-blacklist.conf ). Okay, so from now on you are using the nv driver, right? Camaleón and Sven, thank you both for your help! And thanks for bearing with my newbie faux pas. :) Glad you finally could solved it. Sven, you mentioned that neither NV nor Nvidia legacy will work whenever I eventually upgrade to Wheezy. Can you suggest what I prepare to do? Thanks again! Jim My guess is that your VGA is very old and that can be a problem. - NV driver is dropped (not present) since wheezy so this won't be an option for you. - Nouveau is the new and natural replacement for the open source driver but it can have problems with your hardware, so better if you can test it from a LiveCD of any recent distribution to see how it goes, though probably any error present in squeezy has been fixed in wheezy. - Nvidia legacy should also work, but maybe you need to get it from nvidia sources directly and compile by your own in the event they release a compatible version that works with newer xorg xserver packages. More information exposing the problematic can be found in a couple of Debian bugs reports, e.g.: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660158 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643584 Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jn0r3a$ha3$7...@dough.gmane.org
Re: X problem (?) after fresh install on old laptop
Thanks for your advice! Camaleón wrote: Okay, so from now on you are using the nv driver, right? Yes, NV for now. I realized that I now have one new issue, though not as bothersome as the original. When I CTRL+ALT+F* into a terminal window, or during the start-up/shut-down messages (when X is not running), the screen appears very dim, and has vertical lines that roll across it. Is there anything obvious that I can do to fix this? This does not happen when I boot into Recovery Mode -- only when I boot normally. Thanks again, Jim -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1335121025.61700.yahoomail...@web125301.mail.ne1.yahoo.com
Re: X problem (?) after fresh install on old laptop
On Fri, 20 Apr 2012 19:56:25 -0700, Potato Jim wrote: Potato Jim, please adjust your MUA to don't posting on the top, get right quoting (you forced me to delete the full message reference because it was poorly formatted ;-( ) and there's no need to send me a copy of the message, I read the list. Thank you Camaleón, The suggestions on that page about blacklisting nouveau to disable KMS did not work. What exactly did you try and what exactly did you get? Precision does matter. However, I noticed that if I comment out the blacklist nvidiafb line from /etc/modeprobe.d/fbdev-blacklist.conf, X/Gnome does sort of work again. I can see the contents of windows, but now the entire screen is a little wavy and shimmery (for lack of a better description). You mean that blacklisting nvidiafb (nvidia framebuffer driver) helps? Does this help identify my problem? Is there any command or log file output I can provide, or any other information? Xorg log can be of help, yes. It is located in /var/log/Xorg.0.log, you can upload the whole file to www.pastebin.com so we can review it. As you're in Squeeze, there's a set of VGA drivers you can use: - Nouveau - NV - Nvidia legacy But I'd like to see first the Xorg log :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jmu0d6$g9$7...@dough.gmane.org
Re: X problem (?) after fresh install on old laptop
On 2012-04-21 11:59 +0200, Camaleón wrote: On Fri, 20 Apr 2012 19:56:25 -0700, Potato Jim wrote: The suggestions on that page about blacklisting nouveau to disable KMS did not work. What exactly did you try and what exactly did you get? Precision does matter. It seems he tried to blacklist nouveau, but this does not actually help if there is no xorg.conf. I have updated the Wiki accordingly. However, I noticed that if I comment out the blacklist nvidiafb line from /etc/modeprobe.d/fbdev-blacklist.conf, X/Gnome does sort of work again. I can see the contents of windows, but now the entire screen is a little wavy and shimmery (for lack of a better description). You mean that blacklisting nvidiafb (nvidia framebuffer driver) helps? No, *un*blacklisting helped. With nvidiafb loaded, nouveau will not load, and X should use the fbdev driver then. As you're in Squeeze, there's a set of VGA drivers you can use: - Nouveau - NV - Nvidia legacy Using one of the latter two is probably the best in Squeeze, but nv is abandoned, and Nvidia has not published a 96xx legacy driver that works with X servers 1.10, neither of them will work after an upgrade to Wheezy. But I'd like to see first the Xorg log :-) Me too. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87hawdpdhe@turtle.gmx.de
Re: X problem (?) after fresh install on old laptop
I first tried blacklisting nouveau by issuing the following command: echo blacklist nouveau /etc/modprobe.d/blacklist-nouveau.conf ...this was per the instructions here: http://wiki.debian.org/KernelModesetting#Disabling_KMS Next, I did as Sven guessed and un-blacklisted nvidiafb by commenting out the blacklist nvidiafb line in /etc/modeprobe.d/fbdev-blacklist.conf And here is the /var/log/Xorg.0.log: http://pastebin.com/JEGgZ3aA Thanks, Jim -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1335029120.33456.yahoomail...@web125301.mail.ne1.yahoo.com
Re: X problem (?) after fresh install on old laptop
SOLVED. In my last response I had overlooked Sven's comment about having updated the wiki. I have now looked at the updated wiki and the suggested new xorg.conf file did the trick -- verbatim even, and I'm now using the NV driver. More precisely, I blacklisted nouveau in a blacklist-nouveau.conf file and created a new xorg.conf file, specifying the NV driver (I also re-blacklisted nvidiafb in /etc/modeprobe.d/fbdev-blacklist.conf ). Camaleón and Sven, thank you both for your help! And thanks for bearing with my newbie faux pas. :) Sven, you mentioned that neither NV nor Nvidia legacy will work whenever I eventually upgrade to Wheezy. Can you suggest what I prepare to do? Thanks again! Jim -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1335058402.63339.yahoomail...@web125306.mail.ne1.yahoo.com
X problem (?) after fresh install on old laptop
Hi Everyone, I installed Deb 6.0.4 on an old Dell Inspiron 2650 laptop and everything seemed to go well, except... I'll try to describe a problem I'm experiencing, evidently with X: The windows are all blank. Even at the login screen, I can't see the username,other selection list -- just a blank rectangle for the login window. The Debian starry desktop background picture does show up however. When I wave the mousepointer over the login window, it selectively shows -some- of the contents, enough that I can see to select my username, type my password and log in. Once logged in, it's more of the same in Gnome. I can see the starry desktop background picture, and I can see the menu bars, but I can't see the icons (Computer, Home, Trash) on the desktop until I waive the mouse pointer over them. I also cannot see the Applications, Places, and System menus on the left side of the top menu bar. But I can see the network, date, sound and window selector widgets on the right side of the menu bar. When I click on any of the Applications, Places or System menus, I don't see anything drop down -- but if I pause the mouse over where I expect the menu to be, tool-tips do appear, suggesting that the menu is there. I am able to ctrl+alt+f* into terminal windows and use them perfectly well. No problems at all here. When I was booted off the CD to install Debian, I didn't have any trouble with the GUI environment. Now I'm trying to figure out what is wrong with this fresh install. A little more info: I installed from a CD iso that I burned, and the laptop had a running network connection (ethernet) when I installed Debian. Additional packages were downloaded from the Internet. Again, the installation process didn't seem to have any problems. I'm somewhat of a Linux newbie (especially to Debian), but I can provide further information if anyone can suggest what commands to run and what output to provide. Also, because I'm having trouble describing my problem, I've also struggled to Google it and find existing information on the subject. If anyone has pointers, I would appreciate it. Thanks very much! Jim
Re: X problem (?) after fresh install on old laptop
On Fri, 20 Apr 2012 09:43:03 -0700, Potato Jim wrote: Hi Everyone, Hi, please, turn off html when posting to the mailing list. Thanks :-) I installed Deb 6.0.4 on an old Dell Inspiron 2650 laptop and everything seemed to go well, except... I'll try to describe a problem I'm experiencing, evidently with X: The windows are all blank. Even at the login screen, I can't see the username,other selection list -- just a blank rectangle for the login window. The Debian starry desktop background picture does show up however. When I wave the mousepointer over the login window, it selectively shows -some- of the contents, enough that I can see to select my username, type my password and log in. (...) Are you using a nvidia VGA card? If so, you can first try to disable KMS and see how it goes. Instructions can be found here: http://wiki.debian.org/KernelModesetting#Disabling_KMS Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jms4d3$o0u$1...@dough.gmane.org
Re: X problem (?) after fresh install on old laptop
Thank you Camaleón, The suggestions on that page about blacklisting nouveau to disable KMS did not work. However, I noticed that if I comment out the blacklist nvidiafb line from /etc/modeprobe.d/fbdev-blacklist.conf, X/Gnome does sort of work again. I can see the contents of windows, but now the entire screen is a little wavy and shimmery (for lack of a better description). Does this help identify my problem? Is there any command or log file output I can provide, or any other information? Thanks again, Jim - Original Message - From: Camaleón noela...@gmail.com To: debian-user@lists.debian.org Cc: Sent: Friday, April 20, 2012 12:54 PM Subject: Re: X problem (?) after fresh install on old laptop On Fri, 20 Apr 2012 09:43:03 -0700, Potato Jim wrote: Hi Everyone, Hi, please, turn off html when posting to the mailing list. Thanks :-) I installed Deb 6.0.4 on an old Dell Inspiron 2650 laptop and everything seemed to go well, except... I'll try to describe a problem I'm experiencing, evidently with X: The windows are all blank. Even at the login screen, I can't see the username,other selection list -- just a blank rectangle for the login window. The Debian starry desktop background picture does show up however. When I wave the mousepointer over the login window, it selectively shows -some- of the contents, enough that I can see to select my username, type my password and log in. (...) Are you using a nvidia VGA card? If so, you can first try to disable KMS and see how it goes. Instructions can be found here: http://wiki.debian.org/KernelModesetting#Disabling_KMS Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jms4d3$o0u$1...@dough.gmane.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1334976985.4403.yahoomail...@web125302.mail.ne1.yahoo.com
mitt x problem
nu vet ja iaf vart mitt problem ligger /usr/lib/gconf2.4 fick hjälp att läsa av skärmen iaf tror ja sökvägen va så något med master server
mitt x problem
nu vet ja iaf vart mitt problem ligger /usr/lib/gconf2.4 fick hjälp att läsa av skärmen iaf tror ja sökvägen va så något med master server
Re: Another No devices found in X problem
On Sat, 26 Feb 2011 13:12:40 -0800, Steve McCarthy wrote: (...) The vesa driver works fine. I've since removed it and fbdev trying to force the intel choice. Here's the resulting X.log: (...) (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so (II) Module intel: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.13.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (...) (EE) No devices detected. Fatal server error: no screens found Any advice? I've got 4 CPU's with nowhere to go. I wonder what is the current status for Sandy Bridge in current Debian releases :-? I've read that Intel X driver 2.14.0 does fully support that chipset (H67) but you seem to be using 2.13.0 and Xorg 1.7.7. Will that combo work? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.27.12.10...@gmail.com
Re: Another No devices found in X problem
On Sunday 27 Feb 2011, Camaleón wrote: I wonder what is the current status for Sandy Bridge in current Debian releases :-? I've read that Intel X driver 2.14.0 does fully support that chipset (H67) but you seem to be using 2.13.0 and Xorg 1.7.7. Will that combo work? Greetings, Oh, I forget to mention I'm running Sid. In all my searching I never found reference to Xorg / Sandy Bridge driver problems. Then again, I never found success stories either. Yes, I saw that driver in experiental, but the +exp suffix put me off. I'm out of ideas so I better read the changelog. Thanks, Steve -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201102271020.29623.newsdeb...@jetcity.org
Another No devices found in X problem
Hello,
I followed this topic in December when Celejar was having difficulty, but
that solution doesn't help me. I recently bought a motherboard w/ H67
chip-set and i5 processor. I managed to purchase it 8 hours before the
Intel recall was announced - lucky me.
Xorg seems determined to load/run the vesa driver no matter what I do. I
gen'd a kernel with i915 DRM support and added i915 to modules to force
loading. Here are the DRM entries in config:
CONFIG_DRM=m
CONFIG_DRM_KMS_HELPER=m
CONFIG_DRM_TTM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_RADEON_KMS=y
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_DRM_I915_KMS=y
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m
# CONFIG_DRM_VMWGFX is not set
CONFIG_DRM_NOUVEAU=m
CONFIG_DRM_NOUVEAU_BACKLIGHT=y
# CONFIG_DRM_NOUVEAU_DEBUG is not set
CONFIG_DRM_I2C_CH7006=m
This kernel produces these boot messages ('grep agp|drm'), but my reading
suggests I should see more:
[0.728270] Linux agpgart interface v0.103
[7.258235] [drm] Initialized drm 1.1.0 20060810
The vesa driver works fine. I've since removed it and fbdev trying to
force the intel choice. Here's the resulting X.log:
(II) LoadModule: dri2
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor=X.Org Foundation
compiled for 1.7.7, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(==) Matched intel as autoconfigured driver 0
(==) Matched vesa as autoconfigured driver 1
(==) Matched fbdev as autoconfigured driver 2
(==) Assigned the driver to the xf86ConfigLayout
(II) LoadModule: intel
(II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
(II) Module intel: vendor=X.Org Foundation
compiled for 1.7.7, module version = 2.13.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: vesa
(WW) Warning, couldn't open module vesa
(II) UnloadModule: vesa
(EE) Failed to load module vesa (module does not exist, 0)
(II) LoadModule: fbdev
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: fbdev
(EE) Failed to load module fbdev (module does not exist, 0)
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge,
Sandybridge, Sandybridge
(II) Primary Device is: PCI 00@00:02:0
(EE) No devices detected.
Fatal server error:
no screens found
Any advice? I've got 4 CPU's with nowhere to go.
Steve
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201102261312.41072.newsdeb...@jetcity.org
X problem after upgrade--help!
Hi. I just upgraded from testing to unstable, in order to get some updated packages I need. X is now not working, and i dont know why. There are no useful messages in /var/log/Xorg.0.log, that i can tell--no errors are reported adn the only thing that looks bad is SELinux: Disabled on system, not enabling in X server. There are no useful messages in /var/log/messages. In /var/log/gdm/:0.log I get an error RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM and then [dri] Disabling DRI.; but then perhaps better, Unhandled monitor type 0 after xf86InitialConfiguration Output LCD1 disable success. At the end of this log there is /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/extensions//libdri.so: undefined symbol: atiddxAbiDixLookupPrivate. This is on a Lenovo Thinkpad T60, so the monitor should be supported. But when I look at my xorg.conf file, there's almost nothing there (i had an autogenerated file). When I try to rerun it with dpkg-reconfigure -phigh xserver-xorg, it gives me the same thing. How can i get X working again? This is crucial for my system! If theres more info i can give ill give it! Thanks. Jen. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: X problem after upgrade--help!
[ Please wrap your lines at 80 characters or less for ordinary discussion. ] On Sun, May 17, 2009 at 08:29:42 -0700, Dr. Jennifer Nussbaum wrote: Hi. I just upgraded from testing to unstable, in order to get some updated packages I need. X is now not working, and i dont know why. There are no useful messages in /var/log/Xorg.0.log, that i can tell--no errors are reported adn the only thing that looks bad is SELinux: Disabled on system, not enabling in X server. There are no useful messages in /var/log/messages. In /var/log/gdm/:0.log I get an error RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM and then [dri] Disabling DRI.; but then perhaps better, Unhandled monitor type 0 after xf86InitialConfiguration Output LCD1 disable success. At the end of this log there is /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/extensions//libdri.so: undefined symbol: atiddxAbiDixLookupPrivate. It looks like your X is trying to use libdri.so from the fglrx-driver package together with the radeon driver; this cannot work. You either have to make X use the fglrx driver (provided that you can install it correctly) or you have to get rid of the fglrx-driver package (which should restore the normal libdri.so from Xorg). See also here: http://bugs.debian.org/528800 -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Strange X problem--right mouse kills X
On Wed, Oct 24, 2007 at 10:59:12 -0700, javi78 wrote: Today after upgrade my debian Sid, many keys of my keyboard didn't work properly. For example, Alt-Gr key had the enter function, when I pushed up direction key the Ksnapshot was launched, etc. Then I saw in this forum that the package xserver-xorg-input-evdev could have a problem with other modules related to xorg. To remove xserver-xorg-input-evdev with apt-get remove xserver-xorg-input-evdev solved my problem. Thank you very much for your help. It turns out the easier solution is to get rid of /usr/share/hal/fdi/policy/10osvendor/10-xx-input.fdi. It caused evdev to be used in X. It seems my latest update (in Sid) has removed the file from that location. Things are now back to normal again :-) /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus．therning＠gmail．com http://therning.org/magnus signature.asc Description: Digital signature
Xorg keyboard and mouse problems (was: Strange X problem--right mouse kills X)
On Wed, Oct 24, 2007 at 10:59:12 -0700, javi78 wrote: Today after upgrade my debian Sid, many keys of my keyboard didn't work properly. For example, Alt-Gr key had the enter function, when I pushed up direction key the Ksnapshot was launched, etc. Then I saw in this forum that the package xserver-xorg-input-evdev could have a problem with other modules related to xorg. To remove xserver-xorg-input-evdev with apt-get remove xserver-xorg-input-evdev solved my problem. It seems that this issue is fixed now, at least as far as the non-US keyboard layouts are concerned. Today I upgraded to hal 0.5.10-2 and reinstalled xserver-xorg-input-evdev (1:1.2.0~git20070819-3). My ES keyboard still works even when I force Xorg to load the evdev module. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange X problem--right mouse kills X
Today after upgrade my debian Sid, many keys of my keyboard didn't work properly. For example, Alt-Gr key had the enter function, when I pushed up direction key the Ksnapshot was launched, etc. Then I saw in this forum that the package xserver-xorg-input-evdev could have a problem with other modules related to xorg. To remove xserver-xorg-input-evdev with apt-get remove xserver-xorg-input-evdev solved my problem. Thank you very much for your help. Regards, Javier. Florian Kulzer-3 wrote: On Tue, Oct 23, 2007 at 09:41:08 +0100, Magnus Therning wrote: After updating my Sid system yesterday I've noticed a rather funky thing--X dies when I use my right mouse button. Are other people noticing the same thing? I found that non-US keyboard layouts were no longer working after this morning's upgrade. It seems that the combination of the newest version of hal (0.5.10-1) with xserver-xorg-input-evdev (1:1.2.0~git20070819-3) causes some problems with xorg input devices. In my case I found that either downgrading hal (and hal-info) or uninstalling xserver-xorg-input-evdev fixes the problem. You could try if one of these actions helps with your mouse issue. (There are a few mouse-related bug reports open against the xserver-xorg-input-evdev package, but I did not look at them more closely.) -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Strange-X-problem--right-mouse-kills-X-tf4675714.html#a13388810 Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Strange X problem--right mouse kills X
After updating my Sid system yesterday I've noticed a rather funky thing--X dies when I use my right mouse button. Are other people noticing the same thing? /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus．therning＠gmail．com http://therning.org/magnus signature.asc Description: Digital signature
Re: Strange X problem--right mouse kills X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/23/07 03:41, Magnus Therning wrote: After updating my Sid system yesterday I've noticed a rather funky thing--X dies when I use my right mouse button. Are other people noticing the same thing? I just clicked right-mouse and it worked fine. (It's a 2-button PS/2 mouse in 3-button emulation mode, using gpm. Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device /dev/psaux Option Protocol PS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection The (I think) relevant package is xserver-xorg-input-mouse 1.2.2-6. - -- Ron Johnson, Jr. Jefferson LA USA Give a man a fish, and he eats for a day. Hit him with a fish, and he goes away for good! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHHbO1S9HxQb37XmcRAjIlAJwNqmcVFW1Lsi6IYn9Ws3Osx4F2HwCcC0c+ xXV1/GV+3kF310HH03kbkaU= =QeFZ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange X problem--right mouse kills X
On Tue, Oct 23, 2007 at 09:41:08 +0100, Magnus Therning wrote: After updating my Sid system yesterday I've noticed a rather funky thing--X dies when I use my right mouse button. Are other people noticing the same thing? I found that non-US keyboard layouts were no longer working after this morning's upgrade. It seems that the combination of the newest version of hal (0.5.10-1) with xserver-xorg-input-evdev (1:1.2.0~git20070819-3) causes some problems with xorg input devices. In my case I found that either downgrading hal (and hal-info) or uninstalling xserver-xorg-input-evdev fixes the problem. You could try if one of these actions helps with your mouse issue. (There are a few mouse-related bug reports open against the xserver-xorg-input-evdev package, but I did not look at them more closely.) -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange X problem--right mouse kills X
On Tue, Oct 23, 2007 at 11:38:19 +0200, Florian Kulzer wrote: On Tue, Oct 23, 2007 at 09:41:08 +0100, Magnus Therning wrote: After updating my Sid system yesterday I've noticed a rather funky thing--X dies when I use my right mouse button. Are other people noticing the same thing? I found that non-US keyboard layouts were no longer working after this morning's upgrade. It seems that the combination of the newest version of hal (0.5.10-1) with xserver-xorg-input-evdev (1:1.2.0~git20070819-3) causes some problems with xorg input devices. In my case I found that either downgrading hal (and hal-info) or uninstalling xserver-xorg-input-evdev fixes the problem. You could try if one of these actions helps with your mouse issue. (There are a few mouse-related bug reports open against the xserver-xorg-input-evdev package, but I did not look at them more closely.) Yes, I did some testing and I suspect it's evdev that's messing with me. I have a Logitech cordless mouse and keyboard that go through the same USB connection. The confusing thing is that it seems the multimedia keys goes through the mouse channel rather than the keyboard channel. I suspect that's the cause for X thinking my mouse has 96 keys :-) I'll try rolling back to an earlier version later today and report back. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus．therning＠gmail．com http://therning.org/magnus pgpalkZWsblTK.pgp Description: PGP signature
Re: Strange X problem--right mouse kills X
Hi. I can confirm this problem,... yesterdays updates broke my X,... mouse settings and keyboard settings are no longer detected. Regards, Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Strange X problem--right mouse kills X
On Tuesday 23 October 2007 16:10, Christoph Anton Mitterer wrote: Hi. I can confirm this problem,... yesterdays updates broke my X,... mouse settings and keyboard settings are no longer detected. Regards, Chris. Can you give us more info on your system. I am going to try to help my friend because he lost is mouse too. He is on Etch -X86. I had a fast look at it yesterday: some setting were back to default setting: emulation of a 3 buttons mouse, maybe some other.. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X problem after upgrade
Hi I have a strange display problem after upgrading from Sarge to Etch. In X the screen is displaced 1 cm to the left (leftmost 1 cm of screen is out of display area and there is an 1 cm wide black stripe at the right edge of the display). This only happens with the native 1280x1024 resolution of the HP 1702 flat panel display. Lower resolutions work correctly. In Sarge I used vesa driver instead of i810, IIRC because the i810 driver in Sarge didn't support this graphics controller(Intel 82915G/GV/910GL). I tried using vesa driver now also, but it didn't change anything. I tried a Knoppix 5.0.1 CD and it has the same problem with the X configuration it probes(with vesa driver). Also the system is a dual boot system and in Windows XP everything works fine, so I'd guess it is not a hardware problem. Any ideas what is wrong? I've pasted the contents of my xorg.conf below Please cc me. I am not subscribed to the list. Tommi Lantta # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout fi EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons true EndSection Section Device Identifier Intel Corporation 82915G/GV/910GL Integrated Graphics Controller Driver i810 BusID PCI:0:2:0 EndSection Section Monitor Identifier hp L1702 Option DPMS HorizSync 30-81 VertRefresh 56-76 EndSection Section Screen Identifier Default Screen Device Intel Corporation 82915G/GV/910GL Integrated Graphics Controller Monitor hp L1702 DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse EndSection Section DRI Mode
Re: X problem after upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tommi Lantta wrote: Hi I have a strange display problem after upgrading from Sarge to Etch. In X the screen is displaced 1 cm to the left (leftmost 1 cm of screen is out of display area and there is an 1 cm wide black stripe at the right edge of the display). This only happens with the native 1280x1024 resolution of the HP 1702 flat panel display. Lower resolutions work correctly. In Sarge I used vesa driver instead of i810, IIRC because the i810 driver in Sarge didn't support this graphics controller(Intel 82915G/GV/910GL). I tried using vesa driver now also, but it didn't change anything. I tried a Knoppix 5.0.1 CD and it has the same problem with the X configuration it probes(with vesa driver). Also the system is a dual boot system and in Windows XP everything works fine, so I'd guess it is not a hardware problem. Any ideas what is wrong? [snip xorg.conf] I don't have the same monitor as you do, but I found that pushing the button on my monitor that autosets the display will fix that. Almost all monitors made in the last few years have such a button. Joe - -- Registerd Linux user #443289 at http://counter.li.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGAVgciXBCVWpc5J4RAjOkAKDKtxqy8c3hQQlQd1lAU4MYIQ+eoACfdAI/ PAYVPUwLhpvT0+UmZ2yPEy0= =lv+N -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem after upgrade
Joe Hart wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tommi Lantta wrote: Hi I have a strange display problem after upgrading from Sarge to Etch. In X the screen is displaced 1 cm to the left (leftmost 1 cm of screen is out of display area and there is an 1 cm wide black stripe at the right edge of the display). This only happens with the native 1280x1024 resolution of the HP 1702 flat panel display. Lower resolutions work correctly. In Sarge I used vesa driver instead of i810, IIRC because the i810 driver in Sarge didn't support this graphics controller(Intel 82915G/GV/910GL). I tried using vesa driver now also, but it didn't change anything. I tried a Knoppix 5.0.1 CD and it has the same problem with the X configuration it probes(with vesa driver). Also the system is a dual boot system and in Windows XP everything works fine, so I'd guess it is not a hardware problem. Any ideas what is wrong? [snip xorg.conf] I don't have the same monitor as you do, but I found that pushing the button on my monitor that autosets the display will fix that. Almost all monitors made in the last few years have such a button. Joe - -- Registerd Linux user #443289 at http://counter.li.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGAVgciXBCVWpc5J4RAjOkAKDKtxqy8c3hQQlQd1lAU4MYIQ+eoACfdAI/ PAYVPUwLhpvT0+UmZ2yPEy0= =lv+N -END PGP SIGNATURE- My monitor does not have that, but the principle is the same, i did it manually. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem after upgrade
On Wed, 21 Mar 2007, Joe Hart wrote: I don't have the same monitor as you do, but I found that pushing the button on my monitor that autosets the display will fix that. Almost all monitors made in the last few years have such a button. There is such a button and I think I have tried it with no results. Don't know if it actually did anything. There is also a button for accessing menu for manual adjustment, but it didn't work. I guess it's broken. Maybe the auto-adjust one is also. I'll have to check when I'm back at that machine. I was just wondering why would different operating systems require so different adjustments of the monitor for same resolution, especially when it is an LCD monitor. Well, maybe I shouldn't care. Tommi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem after upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tommi Lantta wrote: On Wed, 21 Mar 2007, Joe Hart wrote: I don't have the same monitor as you do, but I found that pushing the button on my monitor that autosets the display will fix that. Almost all monitors made in the last few years have such a button. There is such a button and I think I have tried it with no results. Don't know if it actually did anything. There is also a button for accessing menu for manual adjustment, but it didn't work. I guess it's broken. Maybe the auto-adjust one is also. I'll have to check when I'm back at that machine. I was just wondering why would different operating systems require so different adjustments of the monitor for same resolution, especially when it is an LCD monitor. Well, maybe I shouldn't care. Tommi Because of the drivers, and the frequency they use. Changing to a different video driver should yield different results. Eventually you should find one that works properly, or you will need to consider a new monitor. That of course is last resort. Joe - -- Registerd Linux user #443289 at http://counter.li.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGAiE2iXBCVWpc5J4RAmaGAKDCtoKrStUgMBmH4hIxMBFywORy4ACgn0Mb nPLQZHTNNo8o9kesx91WbJ8= =4OOI -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
forcedeth Netzwerktreiber und Kernel 2.6.17.x Problem.
Hallo, ich habe seit dem Einsatz der 2.6.17.Xer Serie starke Probleme mit meiner Onboard (NForce4-Ultra Chipsatz) Netzwerkkarte. Wenn ich Dateien aus dem Internet mit größerem Speed herunterlade (800kb - 1MB) steigt IOWait auf 100% und nach ca. 30s bricht der Download bis auf 0 zusammen. Anschliessend klettert er wieder auf knapp 1MB und das Spiel geht von vorne los. Habe bisher 2.6.17.4, .6 und .4-cs (Con's Patches) probiert. Überall das gleiche Verhalten. Im Augenblick setze ich wieder 2.6.16.16 ein, dort funktioniert alles Prima. Alle Kernel sind von Hand compiled mit gleicher Konfiguration. Ein Diff zwischen 6.16 und 17.6 ergab recht viele Änderungen: diff ./linux-2.6.17.6/drivers/net/forcedeth.c ./linux-2.6.16.16/drivers/net/forcedeth.c 105,109d104 *0.50: 20 Jan 2006: Add 8021pq tagging support. *0.51: 20 Jan 2006: Add 64bit consistent memory allocation for rings. *0.52: 20 Jan 2006: Add MSI/MSIX support. *0.53: 19 Mar 2006: Fix init from low power mode and add hw reset. *0.54: 21 Mar 2006: Fix spin locks for multi irqs and cleanup. 121c116 #define FORCEDETH_VERSION 0.54 --- #define FORCEDETH_VERSION 0.49 Jemand ähnliches beobachtet und eventuell Workarounds parat? Hat jemand mit einer NForce4-Ultra Chipsatz forcedeth Karte keine derartigen Probleme mit der 17er Reihe? -- Markus Schulz meine Spülmaschine heißt Nicole und arbeitet autonom... ansprechendes ergonomisches 3D-UI, sprachgesteuert, force-feedback... Force-Feedback? Ach so, sie tritt dir in den Arsch wenn du rumnölst sie müsste mal wieder spülen? eg [d.a.s.r]
Re: Anyone having X problem updating from testing to unstable.
On 5/7/06, Javier-Elias Vasquez-Vivas [EMAIL PROTECTED] wrote: On 5/6/06, Florian Kulzer [EMAIL PROTECTED] wrote: On Fri, May 05, 2006 at 15:11:17 -1000, Javier-Elias Vasquez-Vivas wrote: On 5/5/06, Florian Kulzer [EMAIL PROTECTED] wrote: [...] http://wiki.debian.org/Xorg69To7 [...] [...]. WDM doesn't seem to work here, and I've already edited /etc/X11/wdm/Xservers to point to /usr/bin/Xorg, but no success. I can live without it, but I'm wondering if there's something else that can be done. You might have found a new bug. Do you get any error messages when you restart wdm? After a failed log-in attempt, do find anything interesting in ~/.xsession-errors? Maybe you have an old config file somewhere with an incompatible setting; have you tried purging wdm and reinstalling it? -- Regards, Florian I had to admit I didn't tried purging, just removing and installing again. But I did the purge as well after you mentioned it. Nothing works still though. And weird thing I get NO error under .xsession-errors (I've moved old one somewhere else and created new one, and after wdm gets back to login nothing shows up under .xsession-errors). So somehow I'm unable to get an Xsession from wdm, :-(. I checked /etc/X11/wdm/Xstartup, and it was checking for /usr/bin/X11/xmessage, so I changed that for /usr/bin/xmessage, but that didn't change a thing either. So I'm kind of lost, there's must be a unconnected link somewhere, but I can figure out where. For now I'm removing wdm to avoid it at boot... Thanks, -- Javier -- I tried XDM, and XDM is working fine. So this must be an exclusive WDM issue then. The work around is to use XDM then, :-(. -- Javier --
Re: Urgent X Problem
Leonid Grinberg wrote: If your friend is using Gnome in Etch (testing), my previous post may help: http://lists.debian.org/debian-user/2006/04/msg04086.html Although GNOME is the display environment being used, it is not the one that's crashing. It's definitely X. Are you sure? I was able to run a KDE session after disabling gdm and running startx. Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Urgent X Problem
I was sure, but it starts up now. Instead, it says that there is an error in the configuration of the login manager, and that it will use the ``default command''. Is this /etc/gdm/gdm.conf? Should I post its contents here? -- Leonid
Re: Urgent X Problem
Leonid Grinberg wrote: Hello, I have a friend, who, after upgrading via dist-upgrade had his X display broken. Now, there is a blue screen that says that it cannot load the X server. [ ... ] If your friend is using Gnome in Etch (testing), my previous post may help: http://lists.debian.org/debian-user/2006/04/msg04086.html Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Urgent X Problem
If your friend is using Gnome in Etch (testing), my previous post may help: http://lists.debian.org/debian-user/2006/04/msg04086.html Although GNOME is the display environment being used, it is not the one that's crashing. It's definitely X.
Urgent X Problem
Hello, I have a friend, who, after upgrading via dist-upgrade had his X display broken. Now, there is a blue screen that says that it cannot load the X server. This happened to me before, and I remembered that # modprobe agpgart seemed to help. He appears to have an Intel vhip, but nothing is working. I do not have any way to provide you with the X log file. Does anyone have any ideas based off of this pathetic information? -- Leonid Grinberg [EMAIL PROTECTED] http://www.lgrinberg.org
Re: X Problem
Please don't claim urgency on public mailing lists: Lack of planning on your part doesn't constitute a crisis on ours. We're volunteers. If it really is urgent, please see http://debian.org/consultants/ instead. On Wednesday 10 May 2006 13:59, Leonid Grinberg wrote: I have a friend, who, after upgrading via dist-upgrade had his X display broken. Now, there is a blue screen that says that it cannot load the X server. his happened to me before, and I remembered thaTt What did the blue screen say? He appears to have an Intel vhip, but nothing is working. What does lspci tell you about it? You might want to read this for some ideas on how to troubleshoot a bit better. http://www.catb.org/~esr/faqs/smart-questions.html -- Paul Johnson Email and IM (XMPP Google Talk): [EMAIL PROTECTED] Jabber: Because it's time to move forward http://ursine.ca/Ursine:Jabber pgpIxTrrDhvzp.pgp Description: PGP signature
Re: Urgent X Problem
I don't know what distro you upgrade, but until sarge, you could use dpkg-reconfigure xserver-xfree86 to solve this kind of problems. On 5/10/06, Leonid Grinberg [EMAIL PROTECTED] wrote: Hello, I have a friend, who, after upgrading via dist-upgrade had his X display broken. Now, there is a blue screen that says that it cannot load the X server. This happened to me before, and I remembered that # modprobe agpgart seemed to help. He appears to have an Intel vhip, but nothing is working. I do not have any way to provide you with the X log file. Does anyone have any ideas based off of this pathetic information? -- Leonid Grinberg [EMAIL PROTECTED] http://www.lgrinberg.org
Re: Urgent X Problem
I don't know what distro you upgrade, but until sarge, you could use dpkg-reconfigure xserver-xfree86 to solve this kind of problems. This person is using Testing, and the error happened after an upgrade. We tried dpkg-reconfigure xserver-xfree86, mostly to change video drivers, but it is not working. -- Leonid Grinberg [EMAIL PROTECTED] http://www.lgrinberg.org
Re: Urgent X Problem
On 5/10/06, Leonid Grinberg [EMAIL PROTECTED] wrote: I don't know what distro you upgrade, but until sarge, you could use dpkg-reconfigure xserver-xfree86 to solve this kind of problems. This person is using Testing, and the error happened after an upgrade. We tried dpkg-reconfigure xserver-xfree86, mostly to change video drivers, but it is not working. Is the person really using xfree86, or maybe Xorg? I was using testing and I believe Xorg is the default. Can you verify? In such a case try the same thing but for xserver-xorg. -- Javier --
Re: Urgent X Problem
Oh, I'm sorry. No, the person is using xorg, and the command we ran was dpkg-reconfigure xserver-xorg. I accidentally typed xfree86. -- Leonid
Re: Urgent X Problem
Could you configure xorg to use vesa drivers as a temporary workaround? Leonid Grinberg wrote: Oh, I'm sorry. No, the person is using xorg, and the command we ran was dpkg-reconfigure xserver-xorg. I accidentally typed xfree86. -- Leonid -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Urgent X Problem
I've since directed the message to the list. It was my first ever reply to the mailing list and I stuffed it up. ;) Leonid Grinberg wrote: Could you configure xorg to use vesa drivers instead for a temporary workaround? I did not, and I will suggest it tomorrow. I assume that I could, since I could use any of the other ones, and vesa (I think) was in that list. BTW, should I redirect your answer to the rest of the list, or did you send it just to me on purpose? -- Leonid Grinberg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Anyone having X problem updating from testing to unstable.
On 5/6/06, Florian Kulzer [EMAIL PROTECTED] wrote: On Fri, May 05, 2006 at 15:11:17 -1000, Javier-Elias Vasquez-Vivas wrote: On 5/5/06, Florian Kulzer [EMAIL PROTECTED] wrote: [...] http://wiki.debian.org/Xorg69To7 [...] [...]. WDM doesn't seem to work here, and I've already edited /etc/X11/wdm/Xservers to point to /usr/bin/Xorg, but no success. I can live without it, but I'm wondering if there's something else that can be done. You might have found a new bug. Do you get any error messages when you restart wdm? After a failed log-in attempt, do find anything interesting in ~/.xsession-errors? Maybe you have an old config file somewhere with an incompatible setting; have you tried purging wdm and reinstalling it? -- Regards, Florian I had to admit I didn't tried purging, just removing and installing again. But I did the purge as well after you mentioned it. Nothing works still though. And weird thing I get NO error under .xsession-errors (I've moved old one somewhere else and created new one, and after wdm gets back to login nothing shows up under .xsession-errors). So somehow I'm unable to get an Xsession from wdm, :-(. I checked /etc/X11/wdm/Xstartup, and it was checking for /usr/bin/X11/xmessage, so I changed that for /usr/bin/xmessage, but that didn't change a thing either. So I'm kind of lost, there's must be a unconnected link somewhere, but I can figure out where. For now I'm removing wdm to avoid it at boot... Thanks, -- Javier --
Re: Anyone having X problem updating from testing to unstable.
On Fri, May 05, 2006 at 15:11:17 -1000, Javier-Elias Vasquez-Vivas wrote: On 5/5/06, Florian Kulzer [EMAIL PROTECTED] wrote: [...] Check out the Xorg transition wiki first; it has solutions for the most common problems related to the upgrade: http://wiki.debian.org/Xorg69To7 -- Regards, Florian Thanks a lot, this is pretty helpful. Actually what I was missing was /etc/X11/Xsession, as the wiki indicates. However there's something still not working any good yet. WDM doesn't seem to work here, and I've already edited /etc/X11/wdm/Xservers to point to /usr/bin/Xorg, but no success. I can live without it, but I'm wondering if there's something else that can be done. You might have found a new bug. Do you get any error messages when you restart wdm? After a failed log-in attempt, do find anything interesting in ~/.xsession-errors? Maybe you have an old config file somewhere with an incompatible setting; have you tried purging wdm and reinstalling it? -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Anyone having X problem updating from testing to unstable.
It looks like the modularized Xorg finally got into unstable, which is good news I believe. Only problem is that I moved from testing to unstable, and although I can start X up by running just X, now I can't get an X session from wdm for example neither startx. I'm sure I'm just missing some packages because in testing there's a monolitic X as opposed to the modularized one in unstable, but I have no idea which ones I'm missing. Can some one provide a list of basic packages now required to run X (xorg) sessions under unstable? Thanks, -- Javier --
Re: Anyone having X problem updating from testing to unstable.
On Fri, May 05, 2006 at 15:58:28 -0600, Javier-Elias Vasquez-Vivas wrote: It looks like the modularized Xorg finally got into unstable, which is good news I believe. Only problem is that I moved from testing to unstable, and although I can start X up by running just X, now I can't get an X session from wdm for example neither startx. I'm sure I'm just missing some packages because in testing there's a monolitic X as opposed to the modularized one in unstable, but I have no idea which ones I'm missing. Can some one provide a list of basic packages now required to run X (xorg) sessions under unstable? Check out the Xorg transition wiki first; it has solutions for the most common problems related to the upgrade: http://wiki.debian.org/Xorg69To7 -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Anyone having X problem updating from testing to unstable.
On 5/5/06, Florian Kulzer [EMAIL PROTECTED] wrote: On Fri, May 05, 2006 at 15:58:28 -0600, Javier-Elias Vasquez-Vivas wrote: It looks like the modularized Xorg finally got into unstable, which is good news I believe. Only problem is that I moved from testing to unstable, and although I can start X up by running just X, now I can't get an X session from wdm for example neither startx. I'm sure I'm just missing some packages because in testing there's a monolitic X as opposed to the modularized one in unstable, but I have no idea which ones I'm missing. Can some one provide a list of basic packages now required to run X (xorg) sessions under unstable? Check out the Xorg transition wiki first; it has solutions for the most common problems related to the upgrade: http://wiki.debian.org/Xorg69To7 -- Regards, Florian Thanks a lot, this is pretty helpful. Actually what I was missing was /etc/X11/Xsession, as the wiki indicates. However there's something still not working any good yet. WDM doesn't seem to work here, and I've already edited /etc/X11/wdm/Xservers to point to /usr/bin/Xorg, but no success. I can live without it, but I'm wondering if there's something else that can be done. Thanks again, -- Javier --
X Problem with Etch
I've just installed Etch and I can't get X up. Under Sarge I used VESA for my driver and that worked fine. The Etch installer doesn't seem to give me a choice.I changed /etc/X11/xorg.conf by hand to vesa but X will not recognize this.Any suggestions would be appreciated.
Re: X Problem with Etch
Clyde Wilson wrote: I've just installed Etch and I can't get X up. Under Sarge I used VESA for my driver and that worked fine. The Etch installer doesn't seem to give me a choice. I changed /etc/X11/xorg.conf by hand to vesa but X will not recognize this. Any suggestions would be appreciated. Insufficient information. What is your video card? What are the error messages that you are seeing? Are there any errors in /var/log/XFree86.0.log ? raju -- http://kamaraju.googlepages.com/cornell-bazaar http://groups.google.com/group/cornell-bazaar/about -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X Problem with Etch - Closed
Thanks Raju, I did dpkg-reconfigure xserver.org and everything works fine now. Thanks for the reply! --- kamaraju kusumanchi [EMAIL PROTECTED] wrote: Clyde Wilson wrote: I've just installed Etch and I can't get X up. Under Sarge I used VESA for my driver and that worked fine. The Etch installer doesn't seem to give me a choice. I changed /etc/X11/xorg.conf by hand to vesa but X will not recognize this. Any suggestions would be appreciated. Insufficient information. What is your video card? What are the error messages that you are seeing? Are there any errors in /var/log/XFree86.0.log ? raju -- http://kamaraju.googlepages.com/cornell-bazaar http://groups.google.com/group/cornell-bazaar/about -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X Problem with Etch
try dpkg-reconfigure xserver-xorg -p low this will tell it to ask you any possible questions, which have always included picking a video driver moduel when i ran that command good luck adam
Re: X Problem with Etch
Thanks Adam, I'll try it right now!ClydeAdam Black [EMAIL PROTECTED] wrote: try dpkg-reconfigure xserver-xorg -p lowthis will tell it to ask you any possible questions, which have alwaysincluded picking a video driver moduel when i ran that commandgood luckadam
X-Problem mit ATI X700 Pro
Hallo, ich hab' mir einen AMD 64 3700+ mit obiger Videokarte gegönnt und den Treiber von ATI installiert: $ dpkg -l | grep fglrx ii fglrx-4-3-08.21.7-2 X Window display driver for the ATI graphics Wenn ich versuche, den 64er Treiber zu installieren, bekomme ich jede Menge Fehlermeldungen. Habe alien benutzt, kompilieren habe ich nicht versucht, bin mir auch nicht sicher, dass das mehr bringt. Da ich zunächst kein X hatte (no screen found), hab' ich mir mit der XF86Config-4 von Knoppix beholfen. Klappt, aber wenn ich die Bildschirmauflösung mit Ctrl-Alt-+ ändere, werden Bilder miserabel angezeigt. Außerdem vermute ich, dass meine Behelfslösung nicht optimal ist. dpkg-reconfigure xserver-xfree86 schreibt aber keine Datei, ich hab's mehrfach versucht. Wie kann ich meine Videokarte optimal einstellen? Klaus
Re: X-Problem mit ATI X700 Pro
Am Freitag, den 03.02.2006, 22:27 +0100 schrieb Klaus Becker: ich hab' mir einen AMD 64 3700+ mit obiger Videokarte gegönnt und den Treiber von ATI installiert: $ dpkg -l | grep fglrx ii fglrx-4-3-08.21.7-2 X Window display driver for the ATI graphics Wenn ich versuche, den 64er Treiber zu installieren, bekomme ich jede Menge Fehlermeldungen. Habe alien benutzt, kompilieren habe ich nicht versucht, bin mir auch nicht sicher, dass das mehr bringt. Warum nimmst du nicht den ATI-Installer anstatt der RPM-Pakete? Soviel zu kompilieren ist doch da IMO gar nicht. In den Debian-Paketen stecken AFAIK auch einige Patches. Allerdings vermute ich aufgrund der X-Server-Version, dass du Sarge nutzt, so dass du die Debian-Pakete modifizieren müsstest (falls niemand Backports anbietet). Evtl. findest du auf der fglrx-Mailingliste [1] noch jemanden, der den fglrx-installer [2] noch unterstützt. Da ich zunächst kein X hatte (no screen found), hab' ich mir mit der XF86Config-4 von Knoppix beholfen. Klappt, aber wenn ich die Bildschirmauflösung mit Ctrl-Alt-+ ändere, werden Bilder miserabel angezeigt. Außerdem vermute ich, dass meine Behelfslösung nicht optimal ist. dpkg-reconfigure xserver-xfree86 schreibt aber keine Datei, ich hab's mehrfach versucht. Zig mal erfragt und zig mal erklärt (auch auf dieser Liste [3]). dpkg-reconfigure hilft dir bei den proprietären ATI-Treibern aber auch nicht weiter. Wie kann ich meine Videokarte optimal einstellen? man aticonfig aticonfig --help su -c aticonfig --initial Man-Seiten bekommst du von [4] oder mit den offiziellen Debian-Paketen. [1] http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html#mlist [2] http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html [3] http://groups.google.de/groups?as_q=dpkg-reconfigure+xserver-xfree86as_ugroup=linux.debian.user.german [4] http://cvs.wgdd.de/cgi-bin/cvsweb/fglrx_man/ MfG Daniel
Re: an X problem
Mark Fletcher wrote: On Tuesday 12 July 2005 18:45, Ivan Glushkov wrote: Hi List, Since I went from standart radeon driver to fglrx, Indeed, the problem is in the driver, when I remove it, gdm restarts properly when I issue: /etc/init.d/gdm restart Everything dissapiares, including the terminals (Ctrl+Alt+F1..). I swithed to kdm. The result was the same. I made dpkg-reconfigure xserver-xfree86, but nothing changed. The strange thing is that there is nothing interesting in /var/log/XFree86.0.log or in /var/log/messages.0 Any ideas are very welcome. Cheers, Ivan P.S.: In the moment the only way to stop/restart my laptop is by pushing the button.. I had a similar problem not so long ago, when I upgraded from woody to sarge. The cause was an innocent-looking option in the XF86Config-4 configuration file in /etc in the section that related to my graphics card. In the previous version of X under woody, this option hadn't done anything, but when I upgraded X was broken in exactly the way you describe and turning the option off fixed my problem. No error messages, nothing obviously wrong, nothing going wrong at the kernel level either -- just blank screen (actually my monitor went into power saving mode because the card stopped talking to it altogether!!!) The options available are dependent on the graphics card you have so I won't confuse you with the specific option that caused this for me. Instead, can you post your /etc/XF86Config-4 file to this list and we can see Find it attached... if there's anything dodgy about it. Cheers Mark === After rebooting, dmesg gives: Fire GL built-in AGP-support Based on agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 439M agpgart: Detected an Intel 855PM Chipset, no integrated grapics found. agpgart: Detected Intel i855PM chipset agpgart: AGP aperture is 256M @ 0xe000 Power management callback for AGP chipset installed [fglrx] AGP detected, AgpState = 0x1f000217 (hardware caps of chipset) AGP: Found 2 AGPv2 devices AGP: Doing enable for AGPv2 [fglrx] AGP enabled, AgpCommand = 0x1f000314 (selected caps) [fglrx] free AGP = 256126976 [fglrx] max AGP = 256126976 [fglrx] free LFB = 52719616 [fglrx] max LFB = 52719616 [fglrx] free Inv = 0 [fglrx] max Inv = 0 [fglrx] total Inv = 0 [fglrx] total TIM = 0 [fglrx] total FB = 0 [fglrx] total AGP = 65536 == After /etc/init.d/gdm stop, it says: mtrr: no MTRR for d000,40 found mtrr: no MTRR for d040,10 found mtrr: no MTRR for d050,8 found mtrr: no MTRR for d058,4 found mtrr: no MTRR for d05c,2 found mtrr: no MTRR for d05e,8000 found mtrr: no MTRR for d05e8000,1000 found (yes, MTRR option IS compiled in the kernel) == After /etc/init.d/gdm start : Unable to handle kernel NULL pointer dereference at virtual address 0067 printing eip: e08e4038 *pde = 1b4c8067 *pte = Oops: 0002 [#1] PREEMPT Modules linked in: ipw2200 ieee80211 ieee80211_crypt fglrx intel_agp agpgart CPU:0 EIP:0060:[e08e4038]Tainted: P VLI EFLAGS: 00213202 (2.6.12.2) EIP is at agp_backend_release+0x8/0x10 [agpgart] eax: 0023 ebx: 0001 ecx: edx: 0023 esi: e09c8c50 edi: dbb560c8 ebp: 40046463 esp: d87f5e8c ds: 007b es: 007b ss: 0068 Process XFree86 (pid: 3578, threadinfo=d87f4000 task=df20b0e0) Stack: e099ad19 0023 d82b20c0 e099ad47 0001 081f3460 004c e09c8c50 e09b031c 0001 004c d82b20c0 d87f5ee0 e09c8a60 e09c7f04 e09b0c46 e09c8c50 0001 bff35574 0004 e09c8a60 e09c8a60 e09c7f04 Call Trace: [e099ad19] __ke_agpgart_available+0x69/0x80 [fglrx] [e099ad47] __ke_agp_available+0x17/0xf0 [fglrx] [e09b031c] drm_agp_init+0x5c/0x90 [fglrx] [e09b0c46] _firegl_agp_acquire+0x76/0x360 [fglrx] [e09b0937] firegl_agp_acquire+0x77/0xa0 [fglrx] [e09a4530] firegl_umm_init+0x0/0x450 [fglrx] [e09b08c0] firegl_agp_acquire+0x0/0xa0 [fglrx] [e099c75d] firegl_ioctl+0x15d/0x1e0 [fglrx] [c01708b0] do_ioctl+0x70/0xb0 [c0170aa5] vfs_ioctl+0x65/0x200 [c0170c85] sys_ioctl+0x45/0x70 [c01031d5] syscall_call+0x7/0xb Code: c8 8e e0 31 c9 85 c0 89 c2 74 0c 8b 40 44 85 c0 75 05 ff 42 44 89 d1 5a 89 c8 c3 90 8d b4 26 00 00 00 00 8b 44 24 04 85 c0 74 03 ff 48 44 c3 8d 74 26 00 57 56 53 83 ec 04 bb 01 0 0 00 00 8b 35 = ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the ### BEGIN DEBCONF SECTION line above, and/or after the # ### END DEBCONF SECTION line below. # # To change things within the debconf section, run the
an X problem
Hi List, Since I went from standart radeon driver to fglrx, when I issue: /etc/init.d/gdm restart Everything dissapiares, including the terminals (Ctrl+Alt+F1..). I swithed to kdm. The result was the same. I made dpkg-reconfigure xserver-xfree86, but nothing changed. The strange thing is that there is nothing interesting in /var/log/XFree86.0.log or in /var/log/messages.0 Any ideas are very welcome. Cheers, Ivan P.S.: In the moment the only way to stop/restart my laptop is by pushing the button.. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: an X problem
On Tuesday 12 July 2005 18:45, Ivan Glushkov wrote: Hi List, Since I went from standart radeon driver to fglrx, when I issue: /etc/init.d/gdm restart Everything dissapiares, including the terminals (Ctrl+Alt+F1..). I swithed to kdm. The result was the same. I made dpkg-reconfigure xserver-xfree86, but nothing changed. The strange thing is that there is nothing interesting in /var/log/XFree86.0.log or in /var/log/messages.0 Any ideas are very welcome. Cheers, Ivan P.S.: In the moment the only way to stop/restart my laptop is by pushing the button.. I had a similar problem not so long ago, when I upgraded from woody to sarge. The cause was an innocent-looking option in the XF86Config-4 configuration file in /etc in the section that related to my graphics card. In the previous version of X under woody, this option hadn't done anything, but when I upgraded X was broken in exactly the way you describe and turning the option off fixed my problem. No error messages, nothing obviously wrong, nothing going wrong at the kernel level either -- just blank screen (actually my monitor went into power saving mode because the card stopped talking to it altogether!!!) The options available are dependent on the graphics card you have so I won't confuse you with the specific option that caused this for me. Instead, can you post your /etc/XF86Config-4 file to this list and we can see if there's anything dodgy about it. Cheers Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X problem as root
Hi everybody, i've got a problem whenever i become root and try to open a window in my user X session: for example: [EMAIL PROTECTED]:~$ su [EMAIL PROTECTED]:~$ eog Xlib: connection to :0.0 refused by server Xlib: No protocol specified Does anybody can diagnose the problem? Thanks, MC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem as root
Marco Calviani wrote: Hi everybody, i've got a problem whenever i become root and try to open a window in my user X session: for example: [EMAIL PROTECTED]:~$ su [EMAIL PROTECTED]:~$ eog Xlib: connection to :0.0 refused by server Xlib: No protocol specified Does anybody can diagnose the problem? It has to do with Xauthority files. I don't understand all the ins-and-outs of it; I just use sudo instead (as in sudo eog), which handles it automagically. I think sux (and perhaps another tool or two) might work as well. Or you can dig into the ins-and-outs, and figure out how to copy the Xauthority info from your normal user to root when you su. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem as root
Hello, You have to export the variable XAUTHORITY before invoke su export XAUTHORITY=~/.Xauthority su do not use the '-' in su command because this invoke the shell which read the .profile files and over write you XAUTHORITY variable. You will find a sample .bash_profile under /usr/share/docs/bash I hope it helped Pavlos Αρχικό μήνυμα από Marco Calviani [EMAIL PROTECTED]: Hi everybody, i've got a problem whenever i become root and try to open a window in my user X session: for example: [EMAIL PROTECTED]:~$ su [EMAIL PROTECTED]:~$ eog Xlib: connection to :0.0 refused by server Xlib: No protocol specified Does anybody can diagnose the problem? Thanks, MC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem as root
Hi Pavlos, thanks for your help, i've inserted the export command inside the .bashrc file. Thanks again, MC Pavlos Parissis wrote: Hello, You have to export the variable XAUTHORITY before invoke su export XAUTHORITY=~/.Xauthority su do not use the '-' in su command because this invoke the shell which read the .profile files and over write you XAUTHORITY variable. You will find a sample .bash_profile under /usr/share/docs/bash I hope it helped Pavlos Αρχικό μήνυμα από Marco Calviani [EMAIL PROTECTED]: Hi everybody, i've got a problem whenever i become root and try to open a window in my user X session: for example: [EMAIL PROTECTED]:~$ su [EMAIL PROTECTED]:~$ eog Xlib: connection to :0.0 refused by server Xlib: No protocol specified Does anybody can diagnose the problem? Thanks, MC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Strange keyboard/GUI login/restart X problem
I have the 2.4.18-bf2.4 kernel working and there is no problem. I also have the 2.6.8 custom kernel installed and working fine except for the GUI login. When the login screen comes up the keyboard does not respond. (KDM) I can only use the mouse to click on the drop down lists etc. THe solution I have found is to click on console login, wait at the prompt for about 60 seconds, and it will automatically return to the GUI login and the keyboard works!. I don't need to login in more than once a week but it is still a PIA and I am curious about why this is happening. Any explanations/solutions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem :(
timebandit said: Försökte precis starta X varken mus eller tangentbordet funkade så jag dödade alla processer som hade med X å göra via SSH Nu är bilden helt svart på skärmen till burken... Lyckas inte komma till console eller nått... helt svart Nån som kan ha några idéer att ev. få tillbaks bilden igen utan att starta om burken? chvt(1) är din vän. T.ex. ssh [EMAIL PROTECTED] chvt 1 eller eventuellt testa att starta X igen, kan hända att den initierar grafikkortet till ett bättre tillstånd igen. Antar att du redan testat ctrl-alt-backspace? (beroende på hur dött tangentbordet var förstås). Mvh, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem :(
Jag fick det problemet en gång, var tvungen att avinstalera GDM och köra bara i Bash tills jag kom på att musen gått och dött. On Fri, 1 Apr 2005, timebandit wrote: Försökte precis starta X varken mus eller tangentbordet funkade så jag dödade alla processer som hade med X å göra via SSH Nu är bilden helt svart på skärmen till burken... Lyckas inte komma till console eller nått... helt svart Nån som kan ha några idéer att ev. få tillbaks bilden igen utan att starta om burken?
Re: X problem :(
Är det så svårt att starta om systemet? Har du aldrig varit Windows användare?? timebandit wrote: Försökte precis starta X varken mus eller tangentbordet funkade så jag dödade alla processer som hade med X å göra via SSH Nu är bilden helt svart på skärmen till burken... Lyckas inte komma till console eller nått... helt svart Nån som kan ha några idéer att ev. få tillbaks bilden igen utan att starta om burken? Titta i någon logg-fil eller något. Förslagsvis: var/log/XFree86 -- Mvh, Per Blomqvist Web: http://phoohb.shellkonto.se Telnr: +46 70-3355632 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem :(
On Fri, Apr 01, 2005 at 16:01 CEST, timebandit [EMAIL PROTECTED] wrote: Försökte precis starta X varken mus eller tangentbordet funkade så jag dödade alla processer som hade med X å göra via SSH Nu är bilden helt svart på skärmen till burken... Lyckas inte komma till console eller nått... helt svart Nån som kan ha några idéer att ev. få tillbaks bilden igen utan att starta om burken? Kanske går det. Men jag skulle gissa på att du är tvungen att boota om. Dock kan det vara intressant att försöka spåra vad felet kan tänkas bero på. Kör du testing/unstable? Har du nyss gjort en (dist-)upgrade? Påverkades några drivrutiner för ditt grafikkort eller X-servern? Titta också i /var/log/XFree86.0.log för att se om du hittar några orsaker till felet. mvh -- +---+ | Johan Björklund [EMAIL PROTECTED] http://whero.net/ | | PGP = 813B 014F C0FA B56C FA70 31DC 1C11 3A20 B02B C881 | +---+ | The good thing about standards is that there are so many to choose from. | -- Andrew S. Tanenbaum + -- - --- -- - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem :(
Syns aboslut inget alls i den loggen... står bara info om när jag hade startartat och inga fel heller :( Har gjort några upgraderingar sedan senast jag körde X och kör testing Dock så kan jag tillägga att vncserver funkar men desktopen är helt förändrad :/ Inte längre KDE iaf.
Re: X problem :(
Varningen har bara att gra med att NVIDIAs drivrutin inte r fri mjukvara. Det borde inte gra ngon skillnad fr om X startar eller inte. Du glmde skriva om det fungerade. fre 2005-04-01 klockan 19:37 +0200 skrev timebandit: Testade ladda bort nvidia modulen sedan ladda den igen och dr finns ett litet problem som jag inte vet s mycket om Installing module nvidia. If the device isn't there, or isn't configured correctly, this could cause your system to pause for up to a minute. Warning: loading /lib/modules/2.4.29/kernel/drivers/video/nvidia.o will taint the kernel: non-GPL license - NVIDIA See http://www.tux.org/lkml/#export-tainted for information about tainted modules Module nvidia loaded, with warnings Installation succeeded. Please press ENTER when you are ready to continue. Fr vl ta kolla vad detta kan vara fr ntt... -- Vincent Lnngren [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem - desktop too big for screen size.
On Sat, Jan 01, 2005 at 05:35:50PM +1100, [EMAIL PROTECTED] wrote: Changed monitor and am back running X after a dpkg-reconfigure xserver-xfree86. Problem is the windows are way too big for the 1024 x 780 resolution, and the desktop does not fit into the screen. does the screen scroll when you move the mouse to the edge of it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem - desktop too big for screen size.
On Sat, Jan 01, 2005 at 05:35:50PM +1100, [EMAIL PROTECTED] wrote: Changed monitor and am back running X after a dpkg-reconfigure xserver-xfree86. Problem is the windows are way too big for the 1024 x 780 resolution, and the desktop does not fit into the screen. does the screen scroll when you move the mouse to the edge of it? Thanks Sam No it doesn't. I ended up working around it by setting the resolution to 1280x1024 then in gnome changing the screen resolution in desktop preferences. Not the result I wanted (each user has to set it individually) but it works. AG -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X problem - desktop too big for screen size.
Changed monitor and am back running X after a dpkg-reconfigure xserver-xfree86. Problem is the windows are way too big for the 1024 x 780 resolution, and the desktop does not fit into the screen. X is started from GDM If I startx -- -depth 24 as root its fine, just how it should be. Trying this from a normal user does not work, its the same result as logging in from GDM. Depth 24 is the default in /etc/XF86Config. Can someone point me to relevant doco about where to change this setting. Running testing/sarge. AG
X problem
Hello I have been having trouble with running X. I am running kernel 2.6.0 and sarge. I have Nvidia GForce2 MX graphic card. When I type startx the screen flickers and then goes black. I used apt-get to install gnome and the X packages like xfree86 and the others that it recomended. Thanks for the help in advance, Clyde This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.1.1 (Debian 4.2.1-12.1 20031003005825 [EMAIL PROTECTED]) / XWindow System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 October 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.21-rc1-ac1-cryptoloop i686 [ELF] Module Loader present 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/XFree86.0.log, Time: Sun Feb 1 16:26:28 2004 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Generic Video Card (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout se (**) XKB: layout: se (==) Keyboard: CustomKeycode disabled (**) |--Input Device Configured Mouse (WW) The directory /usr/lib/X11/fonts/CID does not exist. Entry deleted from font path. (WW) The directory /usr/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (**) FontPath set to unix/:7100,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000480c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0305 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 40 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card , rev 40 class 06,00,00 hdr 00 (II) PCI: 00:07:5: chip 1106,3058 card 1462,3300 rev 50 class 04,01,00 hdr 00 (II) PCI: 00:09:0: chip 1274,5000 card 4942,4c4c rev 00 class 04,01,00 hdr 00 (II) PCI: 00:0a:0: chip 10ec,8029 card , rev 00 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0111 card 1462,8829 rev b2 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.1.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) Host-to-PCI bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 00x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL:
Re: X problem
On Sun, Feb 01, 2004 at 08:50:50PM +0100, Bytor the Destroyer wrote: Hello I have been having trouble with running X. I am running kernel 2.6.0 and sarge. I have Nvidia GForce2 MX graphic card. When I type startx the screen flickers and then goes black. I used apt-get to install gnome and the X packages like xfree86 and the others that it recomended. Thanks for the help in advance, I've been having similar problems. X runs fine most of the time, but 2-3 times a week, it locks hard. While XFree is running, normally with the screen blanked, X will run away, using 98-99% of the CPU. I have to ssh in and kill XFree86, so any X apps I have running are killed as well. I have seen this on an MSI GeForce4 MX, which I then swapped with a GeForce2 MX, and have seen the same behavior exhibited. [EMAIL PROTECTED] storm]$ dpkg -l | grep nvidia ii nvidia-glx 1.0.4496-10NVIDIA binary XFree86 4.x driver ii nvidia-glx-dev 1.0.4496-10NVIDIA binary XFree86 4.x driver development ii nvidia-kernel- 1.0.4496-10+10 NVIDIA binary kernel module for Linux 2.4.23 ii nvidia-kernel- 1.0.4496-7 NVIDIA binary kernel module common files ii nvidia-kernel- 1.0.4496-10NVIDIA binary kernel module source [EMAIL PROTECTED] storm]$ dpkg -l | grep XFree ii xfree86-common 4.3.0-0pre1v5 X Window System (XFree86) infrastructure ii xlibmesa-dev 4.2.1-15 XFree86 Mesa development libraries pseudopac ii xlibmesa-dri 4.3.0-0pre1v5 Mesa 3D graphics library modules [XFree86] ii xlibmesa-gl4.3.0-0pre1v5 Mesa 3D graphics library [XFree86] ii xlibmesa-glu 4.3.0-0pre1v5 Mesa OpenGL utility library [XFree86] ii xprt 4.3.0-0pre1v5 X print server (XFree86 version) ii xserver-xfree8 4.3.0-0pre1v5 the XFree86 X server This has been going on for about 6 months, through XFree 4.2.1 and 4.3, and through the last three or four sets of nvidia drivers. This box is a 1GHz Athlon-C. I have a pair of Pentium III boxes at work (one dual 800 and a single 850) that don't seem to have the same problems. Has anyone got a fix for this? Could this be an Athlon-specific problem? I opened a support request with nVidia, but based on their generic response email, I don't expect a whole lot of help out of them. -- --Brad Bradley M. Alexander| gTLD SysAdmin, Security Engineer| storm [at] tux.org Key fingerprints: DSA 0x54434E65: 37F6 BCA6 621D 920C E02E E3C8 73B2 C019 5443 4E65 RSA 0xC3BCBA91: 3F 0E 26 C1 90 14 AD 0A C8 9C F0 93 75 A0 01 34 Do you think that when they asked George Washington for ID that he just whipped out a quarter? -- Steven Wright -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Blackbox/Mozilla/X Problem
als ich neulich von fvwm auf blackbox umsteigen wollte, begegnete mir ein Problem. Sobald ich Mozilla starte, und ein, zwei Seiten ansurfe, friert alles ein. Per remote Login kann ich zwar die Maschine resetten, aber der Bildschirm wechselt das Bild auch nach Neustart des kdm nicht. corefiles wurden soweit nicht geworfen. Interessanterweise tritt dieses Problem mit blackbox und fluxbox als WM auf, mit fvwm z.B. jedoch nicht. Konfiguration: xserver-xfree 4.2.1-11 (aber auch mit einer juengeren Version trat dies schon auf) Mozilla habe ich sowohl 1.4-4 (aus sid) als auch 1.0.0 (aus woody) probiert. ausserdem blackbox 0.65.0-1.1 bzw. fluxbox 0.1.14-1. mein kernel ist ein selbstgebauter 2.4.22 (ganz normaler vanilla-kernel). Desweiteren verwende ich eine GeForce 4 Ti mit dem nvidia-Treiber. Der riva-fb ist deaktiviert. Irgendwelche Ideen, wo ich suchen koennte? Ein Nachtrag noch: Es spielt dabei keine Rolle, ob ich agpgart oder das nvidia-agp-modul verwende. -- Petr Zavor -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Blackbox/Mozilla/X Problem
Hallo Liste, als ich neulich von fvwm auf blackbox umsteigen wollte, begegnete mir ein Problem. Sobald ich Mozilla starte, und ein, zwei Seiten ansurfe, friert alles ein. Per remote Login kann ich zwar die Maschine resetten, aber der Bildschirm wechselt das Bild auch nach Neustart des kdm nicht. corefiles wurden soweit nicht geworfen. Interessanterweise tritt dieses Problem mit blackbox und fluxbox als WM auf, mit fvwm z.B. jedoch nicht. Konfiguration: xserver-xfree 4.2.1-11 (aber auch mit einer juengeren Version trat dies schon auf) Mozilla habe ich sowohl 1.4-4 (aus sid) als auch 1.0.0 (aus woody) probiert. ausserdem blackbox 0.65.0-1.1 bzw. fluxbox 0.1.14-1. mein kernel ist ein selbstgebauter 2.4.22 (ganz normaler vanilla-kernel). Desweiteren verwende ich eine GeForce 4 Ti mit dem nvidia-Treiber. Der riva-fb ist deaktiviert. Irgendwelche Ideen, wo ich suchen koennte? -- Petr Zavor -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
re: irgendwer irgendein x problem :D
Solltest Du das Update aus X versucht haben, könnte ein; apt-get update apt-get upgrade aus der Konsole (ohne x auf einer anderen gestartet zu haben!) dein Problem lösen. Glaube ich. MfG, Wolfgang -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: X-Problem: client rejected
* Lutz Lennardt [EMAIL PROTECTED] wrote: [...] Wo liegt der Fehler? An dir. Warum benutzt du unstable, wenn du offensichtlich nicht damit zurecht kommst? -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
X-Problem: client rejected
Hallo, Ich habe (unter Debian unstable, regelmäßig upgedated) seit gestern (8.6.) ein merkwürdiges Problem: kdm startet nicht mehr. Es klickt dreimal, dann bin ich wieder auf der Kommandozeile. startx hat einen leeren Bildschirm zur Folge. Die Fehlermeldung lautet: --- AUDIT: X: client 1 rejected from local host AuthName: XDM-AUTHORIZATION-1 XDM-AUTHORIZATION ID:-1 Xlib: connection to :0.0 rejected by server Xlib: invalid XDM-AUTHORIZATION-1 (failed key comparison) -- Merkwürdigerweise kann ich xfce mit /usr/bin/startxfce starten. Wo liegt der Fehler? Gruß, Lutz -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
X-Problem (client rejected)
Ich habe seit heute (8.6.) ein merkwürdiges Problem: kdm startet nicht mehr. Es klickt dreimal, dann bin ich wieder auf der Kommandozeile. startx hat einen leeren Bildschirm zur Folge. Die Fehlermeldung lautet: --- AUDIT: X: client 1 rejected from local host AuthName: XDM-AUTHORIZATION-1 XDM-AUTHORIZATION ID:-1 Xlib: connection to :0.0 rejected by server Xlib: invalid XDM-AUTHORIZATION-1 (failed key comparison) -- Auch andere Windowmanager kann ich nicht starten (gnome, WindowMaker ..) DISPLAY=:0.0 und export DISPLAY helfen nicht (bin ja auch noch nicht unter X). /etc/hosts habe ich nicht verändert. Merkwürdigerweise kann ich (als User) xfce mit /usr/bin/startxfce aufrufen, der xserver ist also startbar.Wenn ich als User eingeloggt bin, kann ich das Display auch für Root freigeben. Wo könnte der Fehler liegen? Gruß, Lutz -- Mit freundlichen Grüßen, Lutz -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: X-Problem (client rejected)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 9. Juni 2003 10:32 schrieb Lutz Lennardt: Wo könnte der Fehler liegen? Wie oft willst Du die Frage noch stellen ? Das Problem ist GCC 3.3. Lies folgendes: http://www.debianplanet.org/node.php?id=966 Michael - -- Homepage: http://www.worldforge.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+5E7JWSOgCCdjSDsRAkiEAJ462F28KFbYA7mLSPYskxavWG60wQCeKpAB /+3KZtX5oafFdMVhMknn6m4= =7kYv -END PGP SIGNATURE- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: X-Problem (client rejected)
Lutz Lennardt, Montag, 9. Juni 2003 10:32: Ich habe seit heute (8.6.) ein merkwürdiges Problem: Habe ich zwar schon Matthias Siemering beantwortet, aber nochmal ein Zitat aus linux.debian.maint.x: Yes, XFree86 is broken. If you use ?dm, it won't start. If you've been bitten by this bug, you have three options: a) downgrade xserver-xfree86 to 4.2.1-6 b) downgrade xlibs to 4.2.1-6 c) tough it out Downgraden von xserver-xfree86 und xlibs hat bei mir geholfen. Christian kdm startet nicht mehr. Es klickt dreimal, dann bin ich wieder auf der Kommandozeile. startx hat einen leeren Bildschirm zur Folge. Die Fehlermeldung lautet: --- AUDIT: X: client 1 rejected from local host AuthName: XDM-AUTHORIZATION-1 XDM-AUTHORIZATION ID:-1 Xlib: connection to :0.0 rejected by server Xlib: invalid XDM-AUTHORIZATION-1 (failed key comparison) -- Auch andere Windowmanager kann ich nicht starten (gnome, WindowMaker ..) DISPLAY=:0.0 und export DISPLAY helfen nicht (bin ja auch noch nicht unter X). /etc/hosts habe ich nicht verändert. Merkwürdigerweise kann ich (als User) xfce mit /usr/bin/startxfce aufrufen, der xserver ist also startbar.Wenn ich als User eingeloggt bin, kann ich das Display auch für Root freigeben. Wo könnte der Fehler liegen? Gruß, Lutz -- Mit freundlichen Grüßen, Lutz -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: X-Problem (client rejected)
Hallo Christian, am Montag, 9. Juni 2003 11:41 schrieb Christian Blaesing: Lutz Lennardt, Montag, 9. Juni 2003 10:32: Ich habe seit heute (8.6.) ein merkwürdiges Problem: Habe ich zwar schon Matthias Siemering beantwortet, aber nochmal ein Zitat aus linux.debian.maint.x: Yes, XFree86 is broken. If you use ?dm, it won't start. If you've been bitten by this bug, you have three options: a) downgrade xserver-xfree86 to 4.2.1-6 b) downgrade xlibs to 4.2.1-6 c) tough it out Downgraden von xserver-xfree86 und xlibs hat bei mir geholfen. Danke für den Tip. Ich werde ihn anwenden, wenn ich weiter Probleme habe. Nach Michaels Kochs Hinweis auf die debianplanet-Homepage habe ich den kdm deaktiviert und auf gdm umgestellt, und das funktioniert erstmal wieder - auch mit XFree86 4.2.1-7. Gruß, Lutz -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: X-Problem: client rejected
Lutz Lennardt [EMAIL PROTECTED] writes: Hallo, Ich habe (unter Debian unstable, regelmäßig upgedated) seit gestern (8.6.) ein merkwürdiges Problem: kdm startet nicht mehr. Es klickt dreimal, dann bin ich wieder auf der Kommandozeile. Wo liegt der Fehler? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=196575 Gruß Markus -- http://www.nospam.please Scorefile adjusted mv *.spam /dev/null GPG Key available, send mail with subject:getpgp -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: X-Problem (client rejected)
On Monday 09 June 2003 11:41, Christian Blaesing wrote: Yes, XFree86 is broken. If you use ?dm, it won't start. If you've been bitten by this bug, you have three options: a) downgrade xserver-xfree86 to 4.2.1-6 b) downgrade xlibs to 4.2.1-6 c) tough it out Downgraden von xserver-xfree86 und xlibs hat bei mir geholfen. ist nicht mehr nötig, zumindest nicht, wenn man debian unstable verwendet! einfach ein $ apt-get update apt-get -uy upgrade machen. es ist nämlich bereits eine xlibs 4.2.1-8 -version verfügbar, die das problem der 4.2.1-7 -version behebt ... (zumindest bei mir) bb -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Switching to console mode from X problem almost solved
From someone else who's stuck with a S3 Trio as well - XFree86 4.1 doesn't support an accelerated S3 driver so I'm using XFree 3.3.6. Am guessing but maybe you are using XFree 4.1 - getting round the fact the driver isn't directly supported by using the svga module. The good news is XFree 4.2 supports the S3 Trio directly so upgrading to testing might solve the problems. On Sun, 2 Mar 2003 13:34:36 -0800 Sam Yuval [EMAIL PROTECTED] wrote: Several weeks ago I sent an email concerning my inability to switch from X windows to the virtual console using Ctrl+Alt+F1. I own a Viewsonic P810 21 monitor and an S3 Trio 2D/4X video adapter. It appears that the problem is cause the use of the wrong X server: when I started using xserver-svga instead of xserver-xfree86, the problem disappeared. I hope this is a helpful hint for other users who experienced the same problem I did.There is however, one unexplained problem: I have 8 MB of RAM on the adapter (according to Windows 98), but Linux-based probing software can only detect 4 Mb. Furthermore, when I set up X to use all 8192 Kb of ram on the card (using dpkg-reconfigure xserver-svga), my sprite turns into a usually white square. When I tell X to use only 4096 Kb of ram, the problem is solved, but the card cannot handle high refresh rates. Any ideas? __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Switching to console mode from X problem almost solved
Several weeks ago I sent an email concerning my inability to switch from X windows to the virtual console using Ctrl+Alt+F1. I own a Viewsonic P810 21" monitor and an S3 Trio 2D/4X video adapter. It appears that the problem is cause the use of the wrong X server: when I started using xserver-svga instead of xserver-xfree86, the problem disappeared. I hope this is a helpful hint for other users who experienced the same problem I did. There is however, one unexplained problem: I have 8 MB of RAM on the adapter (according to Windows 98), but Linux-based probing software can only detect 4 Mb. Furthermore, when I set up X to use all 8192 Kb of ram on the card (using dpkg-reconfigure xserver-svga), my sprite turns into a usually white square. When I tell X to use only 4096 Kb of ram, the problem is solved, but the card cannot handle high refresh rates. Any ideas?
Re: Switching to console mode from X problem almost solved
From someone else who's stuck with a S3 Trio as well - XFree86 4.1 doesn't support an accelerated S3 driver so I'm using XFree 3.3.6. Am guessing but maybe you are using XFree 4.1 - getting round the fact the driver isn't directly supported by using the svga module. The good news is XFree 4.2 supports the S3 Trio directly so upgrading to testing might solve the problems. On Sun, 2 Mar 2003 13:34:36 -0800 Sam Yuval [EMAIL PROTECTED] wrote: Several weeks ago I sent an email concerning my inability to switch from X windows to the virtual console using Ctrl+Alt+F1. I own a Viewsonic P810 21 monitor and an S3 Trio 2D/4X video adapter. It appears that the problem is cause the use of the wrong X server: when I started using xserver-svga instead of xserver-xfree86, the problem disappeared. I hope this is a helpful hint for other users who experienced the same problem I did.There is however, one unexplained problem: I have 8 MB of RAM on the adapter (according to Windows 98), but Linux-based probing software can only detect 4 Mb. Furthermore, when I set up X to use all 8192 Kb of ram on the card (using dpkg-reconfigure xserver-svga), my sprite turns into a usually white square. When I tell X to use only 4096 Kb of ram, the problem is solved, but the card cannot handle high refresh rates. Any ideas? __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X problem: mouse pointer shifted
Hi, I have a problem on my Acer TM210 laptop with integrated ALi (Trident) graphics (sorry, I don't have the exact name, it doesn't seem to show anywhere) on XFree86 4.2.1.1, but also on older versions. Regularly, after some time, the mouse pointer will shift and then be shown around 100 pixels to the right of the actual position (i.e. it will stop before reaching the left screen border and mouse clicks are to the left of the shown pointer position). It will sometimes switch back after a few hours. Has anybody experienced those problems, and is there a fix? TIA, ciao, Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem: mouse pointer shifted
On Wed, 11 Dec 2002 16:06:27 +0100, Jens Grivolla [EMAIL PROTECTED] wrote: Hi, I have a problem on my Acer TM210 laptop with integrated ALi (Trident) graphics (sorry, I don't have the exact name, it doesn't seem to show anywhere) on XFree86 4.2.1.1, but also on older versions. Regularly, after some time, the mouse pointer will shift and then be shown around 100 pixels to the right of the actual position (i.e. it will stop before reaching the left screen border and mouse clicks are to the left of the shown pointer position). It will sometimes switch back after a few hours. Has anybody experienced those problems, and is there a fix? Yes. From a post of mine dated 16th February 2002 in Debian user. I think you are the victim of the following bug, since your card is a trident. http://sdb.suse.de/en/sdb/html/wessels_trident_mouse.html Try putting Option sw_cursor in your /etc/X11/XF86Config-4 in the video card section. Somebody really ought to add this to the X documentation. It has been reported at least once to the Debian bug tracking system. Faheem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem: mouse pointer shifted
Faheem Mitha [EMAIL PROTECTED] writes: On Wed, 11 Dec 2002 16:06:27 +0100, Jens Grivolla wrote Regularly, after some time, the mouse pointer will shift and then be shown around 100 pixels to the right of the actual position[...] Yes. From a post of mine dated 16th February 2002 in Debian user. I think you are the victim of the following bug, since your card is a trident. http://sdb.suse.de/en/sdb/html/wessels_trident_mouse.html Yes, that sounds exactly like the problem I am having. Try putting Option sw_cursor in your /etc/X11/XF86Config-4 in the video card section. Done. Somebody really ought to add this to the X documentation. It has been reported at least once to the Debian bug tracking system. Oh, I should have found it then. I guess I didn't use the right key words. Thanks, Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem
On Tue, Dec 03, 2002 at 12:18:05PM -0700, Gary Hennigan wrote: Willi Dyck [EMAIL PROTECTED] writes: On Tue, Dec 03, 2002 at 01:17:18PM -0500, Bruce Park wrote: Your X server is refusing any connection from clients as long as authentication is enabled. Disable by 'xhost +'. Or as root, copy over No! The best solution I've seen for this problem, and the one I use, is after you su: xauth merge ~user/.Xauthority ;export DISPLAY=:0 replace user with whatever your login ID is. This is the correct solution. -rob msg17843/pgp0.pgp Description: PGP signature
X problem
Hello Debian users, I was wondering how I can fix this problem regarding the root user and X. Normally, I log into the machine as a regular user then use the su command to become root. Whenever I need to utilize X(xmms, emacs), I get an error stating the following: == Xlib: connection to :0.0 refused by the server Xlib: client is not authorized to connect to Server emacs: Cannot connect to X server :0.0 Check the DISPLAT environment variable or use `-d' Also use the xhost program to verify that it is set to permit connections fro your machine == I'm thinking that I need to add the root user to the Xlib somehow. Unfortunately, I'm a newbie when it comes to linux so bp _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem
as the regular user who logged in xhost + for more info man xhost there are security issues with this. Bruce Park wrote: Hello Debian users, I was wondering how I can fix this problem regarding the root user and X. Normally, I log into the machine as a regular user then use the su command to become root. Whenever I need to utilize X(xmms, emacs), I get an error stating the following: == Xlib: connection to :0.0 refused by the server Xlib: client is not authorized to connect to Server emacs: Cannot connect to X server :0.0 Check the DISPLAT environment variable or use `-d' Also use the xhost program to verify that it is set to permit connections fro your machine == I'm thinking that I need to add the root user to the Xlib somehow. Unfortunately, I'm a newbie when it comes to linux so bp _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 03 December 2002 6:17 pm, Bruce Park wrote: Hello Debian users, I was wondering how I can fix this problem regarding the root user and X. Normally, I log into the machine as a regular user then use the su command to become root. Whenever I need to utilize X(xmms, emacs), I get an error stating the following: before doing the su command type xhost localhost also I think (not sure) you need to edit /etc/X11/Xservers (or the one in /etc/kde3/kdm if usinging kdm) to take off the -nolisten tcp option off the line that is starting the server on display :0. - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE97P0nuFHxcV2FFoIRAoEaAKCX8150LU2MHswkSKu/Q/XZM51HRwCfcHHF W7nRtoZ323Le7njy9AvJMRY= =TPAe -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X problem
On Tue, Dec 03, 2002 at 01:17:18PM -0500, Bruce Park wrote: Hello Debian users, I was wondering how I can fix this problem regarding the root user and X. Normally, I log into the machine as a regular user then use the su command to become root. Whenever I need to utilize X(xmms, emacs), I get an error stating the following: == Xlib: connection to :0.0 refused by the server Xlib: client is not authorized to connect to Server emacs: Cannot connect to X server :0.0 Check the DISPLAT environment variable or use `-d' Also use the xhost program to verify that it is set to permit connections fro your machine == Your X server is refusing any connection from clients as long as authentication is enabled. Disable by 'xhost +'. Or as root, copy over the .Xauthority file from the users home directory. Cookies are stored in that file, without which, access to the X server is not allowed. Don't forget to set the DISPLAY varible 'export DISPLAY=:0.0'. For more info, read the Remote-X-Apps-HOWTO at linuxdocs.org. Regards, Willi -- never offend people with style when you can offend them with substance. Sam Brown msg16800/pgp0.pgp Description: PGP signature
Re: X problem
Willi Dyck [EMAIL PROTECTED] writes: On Tue, Dec 03, 2002 at 01:17:18PM -0500, Bruce Park wrote: Hello Debian users, I was wondering how I can fix this problem regarding the root user and X. Normally, I log into the machine as a regular user then use the su command to become root. Whenever I need to utilize X(xmms, emacs), I get an error stating the following: [snip] Your X server is refusing any connection from clients as long as authentication is enabled. Disable by 'xhost +'. Or as root, copy over the .Xauthority file from the users home directory. Cookies are stored in that file, without which, access to the X server is not allowed. Don't forget to set the DISPLAY varible 'export DISPLAY=:0.0'. For more info, read the Remote-X-Apps-HOWTO at linuxdocs.org. The best solution I've seen for this problem, and the one I use, is after you su: xauth merge ~user/.Xauthority ;export DISPLAY=:0 replace user with whatever your login ID is. Gary -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A serious X problem after Testing upgrade
On Wed, Nov 06, 2002 at 12:15:14PM +, Barry Samuels wrote: (==) Log file: /var/log/XFree86.0.log, Time: Wed Nov 6 11:51:21 2002 (==) Using config file: /etc/X11/XF86Config-4 (EE) MGA: Failed to load module mga_hal (module does not exist, 0) modprobe: Can't locate module mga [drm] failed to load kernel module mga (EE) MGA(0): [drm] DRIScreenInit failed. Disabling DRI. IceWM: Bad option: TaskBarShowPPPStatus IceWM: Bad option: IgnoreNoFocusHint IceWM: Bad option: ShowXButton IceWM: Bad option: WindowListFontName Does XFree86 4.2 require a new Matrox kernel module or something? Have you tried running X with the 'vesa' driver to see if that still freezes? -rob msg13432/pgp0.pgp Description: PGP signature
