Re: Problems with Xorg after portupgrade
Anton Shterenlikht wrote: > On Wed, Apr 29, 2009 at 02:43:18PM +0200, Daniel C. Dowse wrote: > >> On Wed, 29 Apr 2009 13:38:10 +0100 >> Anton Shterenlikht wrote: >> >> >>> On Wed, Apr 29, 2009 at 08:24:05AM -0400, Robert Huff wrote: >>> Anton Shterenlikht writes: > > Section "DRI" > >Mode0666 > > EndSection > > what does this do? > Sets the permissions for some file. >>> which file? Is this something to do with allowing ordinary users >>> run X? >>> >>> >> Hi, Anton, >> >> it is in /etc/X11/xorg.conf >> > > yes, I got this from somebody's xorg.conf, but what does this do? > Is this a recommended setting? For what driver? > > thank you > anton > Permits access to Direct Rendering for all users. For details see this: http://dri.freedesktop.org/wiki/DriTroubleshooting ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
On Wed, Apr 29, 2009 at 02:43:18PM +0200, Daniel C. Dowse wrote: > On Wed, 29 Apr 2009 13:38:10 +0100 > Anton Shterenlikht wrote: > > > On Wed, Apr 29, 2009 at 08:24:05AM -0400, Robert Huff wrote: > > > > > > Anton Shterenlikht writes: > > > > > > > > Section "DRI" > > > > > Mode0666 > > > > > EndSection > > > > > > > > what does this do? > > > > > > Sets the permissions for some file. > > > > which file? Is this something to do with allowing ordinary users > > run X? > > > > Hi, Anton, > > it is in /etc/X11/xorg.conf yes, I got this from somebody's xorg.conf, but what does this do? Is this a recommended setting? For what driver? thank you anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
On Wed, 29 Apr 2009 13:38:10 +0100 Anton Shterenlikht wrote: > On Wed, Apr 29, 2009 at 08:24:05AM -0400, Robert Huff wrote: > > > > Anton Shterenlikht writes: > > > > > > Section "DRI" > > > >Mode0666 > > > > EndSection > > > > > > what does this do? > > > > Sets the permissions for some file. > > which file? Is this something to do with allowing ordinary users > run X? > Hi, Anton, it is in /etc/X11/xorg.conf greets D.Dowse -- The only reality is virtual! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
On Wed, Apr 29, 2009 at 08:24:05AM -0400, Robert Huff wrote: > > Anton Shterenlikht writes: > > > > Section "DRI" > > > Mode0666 > > > EndSection > > > > what does this do? > > Sets the permissions for some file. which file? Is this something to do with allowing ordinary users run X? many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
On Mon, Apr 20, 2009 at 03:58:10AM +0200, Polytropon wrote: > > Section "DRI" > Mode0666 > EndSection what does this do? thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
mv wrote: > On Sun, 19 April 2009 03:14:35 Manolis Kiagias wrote: > >> >> The default screen when not running a WM/DE is no longer the familiar >> screen pattern / X mouse pointer, but a black screen. Go figure... >> You maybe having a working X and not know it. >> >> > > I had the same issues starting and stopping X. I was looking at a pitch > black screen and did not know if the server was running properly or > not. After some digging around I found a new parameter which will > produce the traditional stipple with cursor in the center of the > screen: > >X -retro > > The above command plus the settings in xorg.conf about killing the > server with Ctrl+Atl+BS (specified elsewhere in this thread) will > produce a traditional startup and shutdown for X. > > Thank for all the useful tips > > Marek > > You can also use twm for testing. Have a look at http://www.freebsdgr.org/handbook-mine/x-config.html (soon to be integrated in the Handbook) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
On Sun, 19 April 2009 03:14:35 Manolis Kiagias wrote: > Ivan "Rambius" Ivanov wrote: > > Hello, > > > > This week upgraded my Acer TravelMate 4060 laptop from FreeBSD 7.0 > > to FreeBSD 7.1 and also csup'ed my ports and portupgraded them and > > I am not able to start X correctly. When I invoke startx, it tries > > to start it and then the screen goes blank and black, nothing is > > seen on it and I am no able to kill X using ctrl-alt-backspace or > > swtich to another terminal and I have to cold reboot my machine. > > > > uname -r shows 7.1-RELEASE-p4 > > > > The version of xorg metaport is 7.4_1, the version of xorg-server > > is 1.6.0,1. > > > > After I did the portupgrade I rebooted my machine and the KDE > > display manager failed to appear, so I disabled it from /etc/ttys > > for easier debugging. After I logged in to a shell, I called startx > > and the screen went blank and black. After I rebooted the machine I > > invoked > > > > X -configure > > > > as root and run > > > > X -config /root/xorg.conf.new > > > > and again the same problem. > > The default screen when not running a WM/DE is no longer the familiar > screen pattern / X mouse pointer, but a black screen. Go figure... > You maybe having a working X and not know it. > I had the same issues starting and stopping X. I was looking at a pitch black screen and did not know if the server was running properly or not. After some digging around I found a new parameter which will produce the traditional stipple with cursor in the center of the screen: X -retro The above command plus the settings in xorg.conf about killing the server with Ctrl+Atl+BS (specified elsewhere in this thread) will produce a traditional startup and shutdown for X. Thank for all the useful tips Marek > > I then tried to make ctrl-alt-backspace > > work and I added the following section at the end of > > /root/xorg.conf.new > > > > Section "ServerFlags" > > Option "DontZap" "off" > > EndSection > > This should definitely work. > > > and called X -config /root/xorg.conf.new again - same results and > > still could not kill ther server. I followed /usr/ports/UPDATING, > > entry from 20090123 and disabled moused and added > > > > Option "AllowEmptyInput" "off" > > Browsing your xorg.conf, you forgot to add the keyword "Option" in > front of "AllowEmptyInput". And actually this should also go the > "ServerFlags" section. > > > in the ServerLayout section. Again X refuses to start > > appropriately. > > > > I would be very grateful if you help me in resolving this issue. > > > > I am attaching my xorg.conf file and the logs from > > /var/log/Xorg.0.log and I will happily provide more information if > > needed. > > > > Thank you very much in advance. > > > > Regards > > Rambius > > You can download my working xorg.conf from here: > > http://store.itsyourftp.com/~sonic2000gr/freebsd/xorg.conf.tar.gz > > It even includes some comments. Give it a try. > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
On Mon, 20 Apr 2009 15:58:15 +0300 Manolis Kiagias wrote: >Jerry wrote: >> On Mon, 20 Apr 2009 03:58:10 +0200 >> Polytropon wrote: >> >> [snip] >> >> While CTRL+ALT+Backspace does not kill the X server, I can press CTRL+ALT+F1 or ALT+F1 to return to the text mode console. I then kill the X server via CTRL+C. >>> There's a new setting that needs to be put into xorg.conf: >>> >>> Section "ServerFlags" >>> Option "DontZap" "false" >>> EndSection >>> >>> Then you should be able to Ctrl+Alt+BkSpace to kill X. >>> >> >> Maybe I am reading this incorrectly; however, in my /etc/xorg.conf >> file, I have this notation. >> >> # Uncomment this to disable the server abort sequence >> # This allows clients to receive this key event. >> >> #Option "DontZap" >> >> It would seem the language is confusing. As I would understand it, >> uncommenting the line disables the sequence. Therefore, it would seem >> to indicate that leaving it commented out activates the sequence. >> Maybe the language should be cleaned up. >> >> >Heh, it can be quite confusing because it enables the system to *not* >do something, which is the reverse of what we usually think options do. >Using Option "DontZap" simply enables "DontZap" which prevents >CTRL+ALT+BSKP from being used. Hence disabling DontZap allows X-Server >to be... Zapped or killed by the key combination ;) I agree. I hate programmers who think they have to 'confuse' the end user. Setting something off to enable it, and vice versa is neither logical or intuitive. Maybe changing the option to: OPTION "EnableKill" "On" and then explaining the with it enabled the ++ key combination is enabled would make more sense. -- Jerry ges...@yahoo.com Good day to deal with people in high places; particularly lonely stewardesses. signature.asc Description: PGP signature
Re: Problems with Xorg after portupgrade
Jerry wrote: On Mon, 20 Apr 2009 03:58:10 +0200 Polytropon wrote: [snip] While CTRL+ALT+Backspace does not kill the X server, I can press CTRL+ALT+F1 or ALT+F1 to return to the text mode console. I then kill the X server via CTRL+C. There's a new setting that needs to be put into xorg.conf: Section "ServerFlags" Option "DontZap" "false" EndSection Then you should be able to Ctrl+Alt+BkSpace to kill X. Maybe I am reading this incorrectly; however, in my /etc/xorg.conf file, I have this notation. # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. #Option "DontZap" It would seem the language is confusing. As I would understand it, uncommenting the line disables the sequence. Therefore, it would seem to indicate that leaving it commented out activates the sequence. Maybe the language should be cleaned up. Heh, it can be quite confusing because it enables the system to *not* do something, which is the reverse of what we usually think options do. Using Option "DontZap" simply enables "DontZap" which prevents CTRL+ALT+BSKP from being used. Hence disabling DontZap allows X-Server to be... Zapped or killed by the key combination ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
On Mon, 20 Apr 2009 03:58:10 +0200 Polytropon wrote: [snip] >> While CTRL+ALT+Backspace does not kill the X server, I can press >> CTRL+ALT+F1 or ALT+F1 to return to the text mode console. I then >> kill the X server via CTRL+C. > >There's a new setting that needs to be put into xorg.conf: > > Section "ServerFlags" > Option "DontZap" "false" > EndSection > >Then you should be able to Ctrl+Alt+BkSpace to kill X. Maybe I am reading this incorrectly; however, in my /etc/xorg.conf file, I have this notation. # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. #Option "DontZap" It would seem the language is confusing. As I would understand it, uncommenting the line disables the sequence. Therefore, it would seem to indicate that leaving it commented out activates the sequence. Maybe the language should be cleaned up. -- Jerry ges...@yahoo.com Trying to get an education here is like trying to take a drink from a fire hose. signature.asc Description: PGP signature
Re: Problems with Xorg after portupgrade
On Mon, 20 Apr 2009, Polytropon wrote: On Sun, 19 Apr 2009 17:16:45 -0700, Charles Oppermann wrote: I'm having similar problems after upgrading an older machine to Xorg 7.4. The monitor blinks it's power light indicating no signal. While CTRL+ALT+Backspace does not kill the X server, I can press CTRL+ALT+F1 or ALT+F1 to return to the text mode console. I then kill the X server via CTRL+C. There's a new setting that needs to be put into xorg.conf: Section "ServerFlags" Option "DontZap" "false" EndSection Then you should be able to Ctrl+Alt+BkSpace to kill X. Really, it's an old option with a new default. Interestingly, if I restart the server (via Xorg, X, startx, etc), the screen will switch to graphics mode and briefly show the contents of the previous session, and then go blank. I believe I'm seeing the contents of the video memory after the mode switch and before the video memory is overwritten or erased. I've seen such a behaviour before, because X seemed to be unable to update the screen contents. I believe that Xorg is working fine, but somehow the video card is told to blank the screen (maybe via DPMS?) or is otherwise incorrectly programmed. Could be that the monitor is not seeing output it likes from the video card and auto-blanking. General notes: First try without an xorg.conf at all. xorg will autoconfig. If it gets it right, or almost right, you can pull the values for xorg.conf out of /var/log/Xorg.0.log. If autoconfig doesn't get things right, still try with a minimal xorg.conf. For instance, all you need in a monitor section is Section "Monitor" Identifier "Monitor0" EndSection Note in Xorg.0.log all the modules that load by default, and realize that you can pretty much leave out the Modules section. Repeating again that you don't need a ServerFlags section, those settings can go in ServerLayout. I'll also remove all the .xinitrc, .xsession, left over crud as well. You could be fine with a minimal .xinitrc and .xsession, both chmodded +x. with this content: ~/.xinitrc #!/bin/sh xset -dpms xterm & exec twm ~/.xsession #!/bin/csh source ~/.cshrc exec ~/.xinitrc Unnecessary, since /usr/local/lib/X11/xinit/xinitrc will be used if there is no user default. This is a machine using the VESA driver with an older Voodoo Banshee AGP card. VESA? Isn't there a driver for this card that gets automatically detected (hahaha) by X .-configure? There's a voodoo driver in ports; no idea if it works with that card. Recent copy of xorg.conf here: http://lists.freebsd.org/pipermail/freebsd-x11/2009-April/008206.html -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
On Sun, 19 Apr 2009 17:16:45 -0700, Charles Oppermann wrote: > I'm having similar problems after upgrading an older machine to Xorg > 7.4. The monitor blinks it's power light indicating no signal. > While CTRL+ALT+Backspace does not kill the X server, I can press > CTRL+ALT+F1 or ALT+F1 to return to the text mode console. I then kill > the X server via CTRL+C. There's a new setting that needs to be put into xorg.conf: Section "ServerFlags" Option "DontZap" "false" EndSection Then you should be able to Ctrl+Alt+BkSpace to kill X. > Interestingly, if I restart the server (via Xorg, X, startx, etc), the > screen will switch to graphics mode and briefly show the contents of the > previous session, and then go blank. I believe I'm seeing the contents > of the video memory after the mode switch and before the video memory is > overwritten or erased. I've seen such a behaviour before, because X seemed to be unable to update the screen contents. > I believe that Xorg is working fine, but somehow the video card is told > to blank the screen (maybe via DPMS?) or is otherwise incorrectly > programmed. Regarding DPMS, Section "Monitor" Option "DPMS" "false" EndSection comes into mind, as well as xset -dpms in ~/.xinitrc. This should eliminate every DPMS attempt of X. > I was using the DPMS screen saver modul via rc.conf, I will remove that > and check again. I don't think it has something to do with it, but maybe there's some kind of interference between the system and X... It's always wise to do testing with minimal settings applied. > I'll also remove all the .xinitrc, .xsession, left over crud as well. You could be fine with a minimal .xinitrc and .xsession, both chmodded +x. with this content: ~/.xinitrc #!/bin/sh xset -dpms xterm & exec twm ~/.xsession #!/bin/csh source ~/.cshrc exec ~/.xinitrc The incorporation of shell settings depends on the shell you use (C shell is the default shell). > This is a machine using the VESA driver with an older Voodoo Banshee AGP > card. VESA? Isn't there a driver for this card that gets automatically detected (hahaha) by X .-configure? In most cases, it's useful to delete all the many autodetected screens in your xorg.conf, only leaving present what you really have, nothing more. This should bypass every means of automatic detection. Of course, you should know what you have. :-) I hope it's okay when I attach an xorg.conf where these requirements are met, it's the one I'm using at the moment. Note that it doesn't conform to the new set of X settings yet, because I'm still using an older X. Maybe it helps you as a template or to get spare parts. :-) And finally, have a look at EE lines in /var/log/Xorg.0.log to see if any driver complains. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... # /etc/X11/xorg.conf # == Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Mouse0""CorePointer" InputDevice "Keyboard0" "CoreKeyboard" Option "SingleCard""true" EndSection #Section "ServerFlags" # Option "DontVTSwitch" "false" # Option "DontZap" "false" # Option "DontZoom" "false" # Option "Xinerama" "false" # Option "AIGLX" "true" #EndSection Section "Files" RgbPath "/usr/local/share/X11/rgb" ModulePath "/usr/local/lib/xorg/modules" FontPath"/usr/local/lib/X11/fonts/misc/" FontPath"/usr/local/lib/X11/fonts/TTF/" FontPath"/usr/local/lib/X11/fonts/OTF" FontPath"/usr/local/lib/X11/fonts/Type1/" FontPath"/usr/local/lib/X11/fonts/100dpi/" FontPath"/usr/local/lib/X11/fonts/75dpi/" FontPath"/usr/local/share/ghostscript/fonts/" FontPath"/usr/local/share/fonts/amspsfont/type1/" FontPath"/usr/local/share/fonts/cmpsfont/type1/" EndSection Section "Module" Load"GLcore" Load"dbe" Load"dri" Load"extmod" Load"glx" Load"record" Load"xtrap" Load"freetype" Load"type1" EndSection Section "DRI" Mode0666 EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "de" Option "AutoRepeat""250 30" EndSection Section "InputDevice" Id
Re: Problems with Xorg after portupgrade
Warren Block wrote: On Mon, 20 Apr 2009, Ivan "Rambius" Ivanov wrote: I even tried with Manolis's xorg.conf - same results. I use startx as a non-root user and I invoke startkde from .xinitrc, but kde does not appear. The screen just blinks once or twice. I also tried to enable xdm from /etc/ttys - same result. Indeed, I think the xorg.conf is OK and no errors appear in the log, but still I can not get it running. It's easier to test if you remove the big desktop manager from the equation. So rename or delete your .xinitrc, .xsession, and don't start X from /etc/ttys. Don't forget to kill -HUP 1 and kill xdm. Then try startx to just get the plain twm screen. I'm having similar problems after upgrading an older machine to Xorg 7.4. The monitor blinks it's power light indicating no signal. While CTRL+ALT+Backspace does not kill the X server, I can press CTRL+ALT+F1 or ALT+F1 to return to the text mode console. I then kill the X server via CTRL+C. Interestingly, if I restart the server (via Xorg, X, startx, etc), the screen will switch to graphics mode and briefly show the contents of the previous session, and then go blank. I believe I'm seeing the contents of the video memory after the mode switch and before the video memory is overwritten or erased. I believe that Xorg is working fine, but somehow the video card is told to blank the screen (maybe via DPMS?) or is otherwise incorrectly programmed. I was using the DPMS screen saver modul via rc.conf, I will remove that and check again. I'll also remove all the .xinitrc, .xsession, left over crud as well. This is a machine using the VESA driver with an older Voodoo Banshee AGP card. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
On Mon, 20 Apr 2009, Ivan "Rambius" Ivanov wrote: I even tried with Manolis's xorg.conf - same results. I use startx as a non-root user and I invoke startkde from .xinitrc, but kde does not appear. The screen just blinks once or twice. I also tried to enable xdm from /etc/ttys - same result. Indeed, I think the xorg.conf is OK and no errors appear in the log, but still I can not get it running. It's easier to test if you remove the big desktop manager from the equation. So rename or delete your .xinitrc, .xsession, and don't start X from /etc/ttys. Don't forget to kill -HUP 1 and kill xdm. Then try startx to just get the plain twm screen. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
Hello Manolis, On Sun, Apr 19, 2009 at 6:02 PM, Manolis Kiagias wrote: > Warren Block wrote: >> On Sun, 19 Apr 2009, Manolis Kiagias wrote: >> >>> Browsing your xorg.conf, you forgot to add the keyword "Option" in front >>> of "AllowEmptyInput". And actually this should also go the "ServerFlags" >>> section. I corrected this error but the screen is still blank and black. >> >> A ServerFlags section is optional; those entries can also go in the >> ServerLayout section. That simplifies xorg.conf a little. I also followed this advice - still no luck. >> >> -Warren Block * Rapid City, South Dakota USA > > Good to know, thanks. The Xorg upgrade was bumpy for me too - too many > changes at once. > I even tried with Manolis's xorg.conf - same results. I use startx as a non-root user and I invoke startkde from .xinitrc, but kde does not appear. The screen just blinks once or twice. I also tried to enable xdm from /etc/ttys - same result. Indeed, I think the xorg.conf is OK and no errors appear in the log, but still I can not get it running. Regards Ivan -- Tangra Mega Rock: http://www.radiotangra.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
Warren Block wrote: > On Sun, 19 Apr 2009, Manolis Kiagias wrote: > >> Browsing your xorg.conf, you forgot to add the keyword "Option" in front >> of "AllowEmptyInput". And actually this should also go the "ServerFlags" >> section. > > A ServerFlags section is optional; those entries can also go in the > ServerLayout section. That simplifies xorg.conf a little. > > -Warren Block * Rapid City, South Dakota USA Good to know, thanks. The Xorg upgrade was bumpy for me too - too many changes at once. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
On Sun, 19 Apr 2009, Manolis Kiagias wrote: Browsing your xorg.conf, you forgot to add the keyword "Option" in front of "AllowEmptyInput". And actually this should also go the "ServerFlags" section. A ServerFlags section is optional; those entries can also go in the ServerLayout section. That simplifies xorg.conf a little. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with Xorg after portupgrade
Ivan "Rambius" Ivanov wrote: > Hello, > > This week upgraded my Acer TravelMate 4060 laptop from FreeBSD 7.0 to > FreeBSD 7.1 and also csup'ed my ports and portupgraded them and I am > not able to start X correctly. When I invoke startx, it tries to start > it and then the screen goes blank and black, nothing is seen on it and > I am no able to kill X using ctrl-alt-backspace or swtich to another > terminal and I have to cold reboot my machine. > > uname -r shows 7.1-RELEASE-p4 > > The version of xorg metaport is 7.4_1, the version of xorg-server is 1.6.0,1. > > After I did the portupgrade I rebooted my machine and the KDE display > manager failed to appear, so I disabled it from /etc/ttys for easier > debugging. After I logged in to a shell, I called startx and the > screen went blank and black. After I rebooted the machine I invoked > > X -configure > > as root and run > > X -config /root/xorg.conf.new > > and again the same problem. The default screen when not running a WM/DE is no longer the familiar screen pattern / X mouse pointer, but a black screen. Go figure... You maybe having a working X and not know it. > I then tried to make ctrl-alt-backspace > work and I added the following section at the end of > /root/xorg.conf.new > > Section "ServerFlags" > Option "DontZap" "off" > EndSection > This should definitely work. > and called X -config /root/xorg.conf.new again - same results and > still could not kill ther server. I followed /usr/ports/UPDATING, > entry from 20090123 and disabled moused and added > > Option "AllowEmptyInput" "off" > > Browsing your xorg.conf, you forgot to add the keyword "Option" in front of "AllowEmptyInput". And actually this should also go the "ServerFlags" section. > in the ServerLayout section. Again X refuses to start appropriately. > > I would be very grateful if you help me in resolving this issue. > > I am attaching my xorg.conf file and the logs from /var/log/Xorg.0.log > and I will happily provide more information if needed. > > Thank you very much in advance. > > Regards > Rambius > > You can download my working xorg.conf from here: http://store.itsyourftp.com/~sonic2000gr/freebsd/xorg.conf.tar.gz It even includes some comments. Give it a try. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Problems with Xorg after portupgrade
Hello, This week upgraded my Acer TravelMate 4060 laptop from FreeBSD 7.0 to FreeBSD 7.1 and also csup'ed my ports and portupgraded them and I am not able to start X correctly. When I invoke startx, it tries to start it and then the screen goes blank and black, nothing is seen on it and I am no able to kill X using ctrl-alt-backspace or swtich to another terminal and I have to cold reboot my machine. uname -r shows 7.1-RELEASE-p4 The version of xorg metaport is 7.4_1, the version of xorg-server is 1.6.0,1. After I did the portupgrade I rebooted my machine and the KDE display manager failed to appear, so I disabled it from /etc/ttys for easier debugging. After I logged in to a shell, I called startx and the screen went blank and black. After I rebooted the machine I invoked X -configure as root and run X -config /root/xorg.conf.new and again the same problem. I then tried to make ctrl-alt-backspace work and I added the following section at the end of /root/xorg.conf.new Section "ServerFlags" Option "DontZap" "off" EndSection and called X -config /root/xorg.conf.new again - same results and still could not kill ther server. I followed /usr/ports/UPDATING, entry from 20090123 and disabled moused and added Option "AllowEmptyInput" "off" in the ServerLayout section. Again X refuses to start appropriately. I would be very grateful if you help me in resolving this issue. I am attaching my xorg.conf file and the logs from /var/log/Xorg.0.log and I will happily provide more information if needed. Thank you very much in advance. Regards Rambius -- Tangra Mega Rock: http://www.radiotangra.com xorg.conf.new Description: Binary data Xorg.0.log Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
