Re: trying for 1920x1080 was: Re: Attempting to get an X11 server running
On Wed, Jul 20, 2011 at 01:15:07AM +, Dieter BSD wrote: > > > Have you tried: > > $ xset +dpms > > to use standby etc.? > > xset: unknown option +dpms > > I assume it needs more than the 5 coaxes to do dpms. > (It did appear to be working with the short cable that came > with the monitor.) I wonder if the monitor doesn't support the Energy Star stuff or it's not switched on. Try reading the manpage for xset and fiddling around with the dpms option. E.g: $ xset dpms force on $ xset +dpms You might also want to set the timings for when the monitor goes into standby etc. > > > Font for xterm: x11-fonts/inconsolata-ttf > > I installed package inconsolata-ttf-20090215.tbz > > caching, new cache contents: 24 fonts, 0 dirs > /var/db/fontconfig: cleaning cache directory > fc-cache: succeeded > > xset fp+ /usr/local/lib/X11/fonts/OTF > xset fp rehash > xterm -fn "-*-inconsolata-*-r-*-*-*-*-*-*-*-*-*-*" > xterm: cannot load font -*-inconsolata-*-r-*-*-*-*-*-*-*-*-*-* > > also xfontsel acts screwy if I select inconsolata. > The sample doesn't get updated, and it starts acting like > it needs backing store but doesn't have it. If I then > select some other family, then xfontsel starts acting > normally again. I've got this in ~.Xdefaults: XTerm*faceName: Inconsolata XTerm*faceSize: 16 > > > Pixels off screen: x11/xvidtune > > and "show" modeline once adjusted and stick it in xorg.conf > > That was easy, thanks! Glad that worked. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpXNtjUPKTcK.pgp Description: PGP signature
Re: trying for 1920x1080 was: Re: Attempting to get an X11 server running
> Have you tried: > $ xset +dpms > to use standby etc.? xset: unknown option +dpms I assume it needs more than the 5 coaxes to do dpms. (It did appear to be working with the short cable that came with the monitor.) > Font for xterm: x11-fonts/inconsolata-ttf I installed package inconsolata-ttf-20090215.tbz caching, new cache contents: 24 fonts, 0 dirs /var/db/fontconfig: cleaning cache directory fc-cache: succeeded xset fp+ /usr/local/lib/X11/fonts/OTF xset fp rehash xterm -fn "-*-inconsolata-*-r-*-*-*-*-*-*-*-*-*-*" xterm: cannot load font -*-inconsolata-*-r-*-*-*-*-*-*-*-*-*-* also xfontsel acts screwy if I select inconsolata. The sample doesn't get updated, and it starts acting like it needs backing store but doesn't have it. If I then select some other family, then xfontsel starts acting normally again. > Pixels off screen: x11/xvidtune > and "show" modeline once adjusted and stick it in xorg.conf That was easy, thanks! ___ 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: trying for 1920x1080 was: Re: Attempting to get an X11 server running
On Tue, Jul 19, 2011 at 09:41:27PM +, Dieter BSD wrote: > > Reducing the color depth to 16 allows the wimpy Rage XL (8 MiB) to > do 1920x1080. > > So then I moved the old slow X terminal out of the way and moved the > shiny new Dell ST2220T LCD into the prime spot in front of the > keyboard drawer... ...and the cable doesn't reach. Two HD-15 to BNC > cables back-to-back fixed that, but now it doesn't do the DCC/EDID > stuff, so I had to get it to use a modeline to get 1920x1080. And of > course it doesn't go into standby mode. sigh Have you tried: $ xset +dpms to use standby etc.? > > Still have some minor issues like finding a decent font for xterm, > and putting a window at +0+0 hides a few pixels off-screen, and > FreeBSD can't tell the difference between a Unix keyboard and a > pee-cee keyboard, but it is usable. > > Thanks for the help! Font for xterm: x11-fonts/inconsolata-ttf Pixels off screen: x11/xvidtune and "show" modeline once adjusted and stick it in xorg.conf HTH. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpi1npfovgSK.pgp Description: PGP signature
Re: trying for 1920x1080 was: Re: Attempting to get an X11 server running
Reducing the color depth to 16 allows the wimpy Rage XL (8 MiB) to do 1920x1080. So then I moved the old slow X terminal out of the way and moved the shiny new Dell ST2220T LCD into the prime spot in front of the keyboard drawer... ...and the cable doesn't reach. Two HD-15 to BNC cables back-to-back fixed that, but now it doesn't do the DCC/EDID stuff, so I had to get it to use a modeline to get 1920x1080. And of course it doesn't go into standby mode. sigh Still have some minor issues like finding a decent font for xterm, and putting a window at +0+0 hides a few pixels off-screen, and FreeBSD can't tell the difference between a Unix keyboard and a pee-cee keyboard, but it is usable. Thanks for the help! ___ 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: trying for 1920x1080 was: Re: Attempting to get an X11 server running
On Thu, 30 Jun 2011, Dieter BSD wrote: Section "Monitor" Identifier "Monitor2220" VendorName "Dell" ModelName "ST2220T" HorizSync 30.00-83.00 VertRefresh 56.00-76.00 Remove the HorizSync and VertRefresh settings, they are only needed if the monitor is ancient or has an incorrect EDID.___ 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: trying for 1920x1080 was: Re: Attempting to get an X11 server running
On 30/06/2011 23:42, Dieter BSD wrote: Now to see if I can get this wimpy rage xl to do 1920x1080. Please don't mess with modelines, it should not be needed any more. Just set the resolutions desired in the Screen/Display section. If modelines are really required, get them out of /var/log/Xorg.0.log. But they almost certainly are not. Though if you *really* wanted to, there's cvt(1): The cvt utility helpfully created a couple of modelines which I think should work, but Xorg doesn't appear to use it. I know it sees it, because if I put in a typo it complains. :-) But the modelines don't appear in the log file, even with Option "ModeDebug" and -logverbose 100. I do get these: (II) MACH64(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz) (II) MACH64(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz) but it doesn't use them: (II) MACH64(0):: Using hsync range of 30.00-83.00 kHz (II) MACH64(0):: Using vrefresh range of 56.00-76.00 Hz (II) MACH64(0):: Using maximum pixel clock of 170.00 MHz (II) MACH64(0): Estimated virtual size for aspect ratio 1.7778 is 1920x1080 (II) MACH64(0): Maximum clock: 124.00 MHz [ ... ] (II) MACH64(0): Not using driver mode "1920x1080" (bad mode clock/interlace/doublescan) (II) MACH64(0): Not using driver mode "1280x1024" (bad mode clock/interlace/doublescan) (II) MACH64(0): Not using driver mode "1920x1080" (bad mode clock/interlace/doublescan) (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to 1400x1050 (--) MACH64(0): Virtual size is 1400x1050 (pitch 1408) (**) MACH64(0): *Default mode "1400x1050": 122.0 MHz, 64.9 kHz, 60.0 Hz (II) MACH64(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz) What is this 124.00 MHz clock? Should I be using 124 or 170? The 1400x1050 being 122 makes me think it is using 124 as the limit. It isn't clear what it means by "bad mode clock/interlace/doublescan". Other rejections have reasons that make sense, "vrefresh out of range", "insufficient memory" and so on. If the pixel clock is the problem, would reducing the color depth help? It won't, it would help only if your card was short on memory. WARNING : from there on I am assuming (given the figures from xorg) that you are using an old CRT to play with. If it is an LCD screen, do not try any of the following modelines. LCD are tricky beast when it comes to modelines. Nonetheless even if the modelines I give should be safe, It is surprisingly easy to turn an old/cheap CRT monitor into an X-Ray emitting bomb. Sure it won't be emitting that much X-Ray, but if you spend hours right in front of it... So make sure that the monitor is not making strange noises, overheating, or accumulating static after you change the modelines. All this said : Pixel (or dot) clock is the "speed" at which the video card can provide data to the monitor. Specific time for sync and blanking must also be taken into account. Your only option would be to : - go for interlaced mode : Modeline "1920x1080@60i" 77.60 1920 1952 2240 2272 1080 1104 1110 1135 interlace - go for low low refresh rate (48hz - I won't give you the modeline as the probablity of damaging your screen are high) - And eventually decreasing the blanking time/sync time (But it is tricky to do, and it can damage monitors) A must read if you are tweaking monitors : http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/overd.html (Old, but the only place where they teach you in detail about dot clock problems) Basically in order to do 1920x1080@60hz you would need 183Mhz of pixel dot clock at the very least. If you are confident that your monitor can take a little bit of shaking (It should not harm it - but don't blame me if it does), you could try this : Modeline "1456x819@72" 124.00 1456 1488 1952 1984 819 834 844 860 If you have a good monitor that do not refuses this strange resolution right away, you should have a pretty nice picture. The xrandr utility doesn't help: xrandr --fb 1920x1080 -display :0 xrandr: screen cannot be larger than 1400x1050 (desired size 1920x1080) xrandr --size 1920x1080 -display :0 Size 1920x1080 not found in available modes Current xorg.conf: Section "ServerLayout" Identifier "X.org Configured" # Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" # need Option "AutoAddDevices" "Off" to avoid the non-working hald # run moused instead Option "AutoAddDevices" "Off" EndSection Section "Module" Disable "record" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse"
Re: trying for 1920x1080 was: Re: Attempting to get an X11 server running
2011-06-30 23:42, Dieter BSD skrev: Now to see if I can get this wimpy rage xl to do 1920x1080. You can't. Mach64 does not support that resulution. Please don't mess with modelines, it should not be needed any more. Just set the resolutions desired in the Screen/Display section. If modelines are really required, get them out of /var/log/Xorg.0.log. But they almost certainly are not. Though if you *really* wanted to, there's cvt(1): The cvt utility helpfully created a couple of modelines which I think should work, but Xorg doesn't appear to use it. I know it sees it, because if I put in a typo it complains. :-) But the modelines don't appear in the log file, even with Option "ModeDebug" and -logverbose 100. I do get these: (II) MACH64(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz) (II) MACH64(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz) but it doesn't use them: (II) MACH64(0):: Using hsync range of 30.00-83.00 kHz (II) MACH64(0):: Using vrefresh range of 56.00-76.00 Hz (II) MACH64(0):: Using maximum pixel clock of 170.00 MHz (II) MACH64(0): Estimated virtual size for aspect ratio 1.7778 is 1920x1080 (II) MACH64(0): Maximum clock: 124.00 MHz [ ... ] (II) MACH64(0): Not using driver mode "1920x1080" (bad mode clock/interlace/doublescan) (II) MACH64(0): Not using driver mode "1280x1024" (bad mode clock/interlace/doublescan) (II) MACH64(0): Not using driver mode "1920x1080" (bad mode clock/interlace/doublescan) (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to 1400x1050 (--) MACH64(0): Virtual size is 1400x1050 (pitch 1408) (**) MACH64(0): *Default mode "1400x1050": 122.0 MHz, 64.9 kHz, 60.0 Hz (II) MACH64(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz) What is this 124.00 MHz clock? Should I be using 124 or 170? The 1400x1050 being 122 makes me think it is using 124 as the limit. It isn't clear what it means by "bad mode clock/interlace/doublescan". Other rejections have reasons that make sense, "vrefresh out of range", "insufficient memory" and so on. If the pixel clock is the problem, would reducing the color depth help? If you set colour depth to 8 bit it can work. The xrandr utility doesn't help: xrandr --fb 1920x1080 -display :0 xrandr: screen cannot be larger than 1400x1050 (desired size 1920x1080) xrandr --size 1920x1080 -display :0 Size 1920x1080 not found in available modes Current xorg.conf: Section "ServerLayout" Identifier "X.org Configured" # Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" # need Option "AutoAddDevices" "Off" to avoid the non-working hald # run moused instead Option "AutoAddDevices" "Off" EndSection Section "Module" Disable "record" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Device" Identifier "Device0" Option "ModeDebug" EndSection Section "Monitor" Identifier "Monitor2220" VendorName "Dell" ModelName "ST2220T" HorizSync 30.00-83.00 VertRefresh 56.00-76.00 # cvt -v 1920 1080 57 # Warning: Refresh Rate is not CVT standard (50, 60, 75 or 85Hz). # 1920x1080 56.90 Hz (CVT) hsync: 63.67 kHz; pclk: 163.00 MHz Modeline "1920x1080_57.00" 163.00 1920 2040 2240 2560 1080 1083 1088 1119 -hsync +vsync # cvt -v -r 1920 1080 # 1920x1080 59.93 Hz (CVT 2.07M9-R) hsync: 66.59 kHz; pclk: 138.50 MHz Modeline "1920x1080R" 138.50 1920 1968 2000 2080 1080 1083 1088 +hsync -vsync EndSection ___ 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"
trying for 1920x1080 was: Re: Attempting to get an X11 server running
>>> Now to see if I can get this wimpy rage xl to do 1920x1080. >> >> Please don't mess with modelines, it should not be needed any more. >> Just set the resolutions desired in the Screen/Display section. If >> modelines are really required, get them out of /var/log/Xorg.0.log. >> But they almost certainly are not. > > Though if you *really* wanted to, there's cvt(1): The cvt utility helpfully created a couple of modelines which I think should work, but Xorg doesn't appear to use it. I know it sees it, because if I put in a typo it complains. :-) But the modelines don't appear in the log file, even with Option "ModeDebug" and -logverbose 100. I do get these: (II) MACH64(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz) (II) MACH64(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz) but it doesn't use them: (II) MACH64(0): : Using hsync range of 30.00-83.00 kHz (II) MACH64(0): : Using vrefresh range of 56.00-76.00 Hz (II) MACH64(0): : Using maximum pixel clock of 170.00 MHz (II) MACH64(0): Estimated virtual size for aspect ratio 1.7778 is 1920x1080 (II) MACH64(0): Maximum clock: 124.00 MHz [ ... ] (II) MACH64(0): Not using driver mode "1920x1080" (bad mode clock/interlace/doublescan) (II) MACH64(0): Not using driver mode "1280x1024" (bad mode clock/interlace/doublescan) (II) MACH64(0): Not using driver mode "1920x1080" (bad mode clock/interlace/doublescan) (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to 1400x1050 (--) MACH64(0): Virtual size is 1400x1050 (pitch 1408) (**) MACH64(0): *Default mode "1400x1050": 122.0 MHz, 64.9 kHz, 60.0 Hz (II) MACH64(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz) What is this 124.00 MHz clock? Should I be using 124 or 170? The 1400x1050 being 122 makes me think it is using 124 as the limit. It isn't clear what it means by "bad mode clock/interlace/doublescan". Other rejections have reasons that make sense, "vrefresh out of range", "insufficient memory" and so on. If the pixel clock is the problem, would reducing the color depth help? The xrandr utility doesn't help: xrandr --fb 1920x1080 -display :0 xrandr: screen cannot be larger than 1400x1050 (desired size 1920x1080) xrandr --size 1920x1080 -display :0 Size 1920x1080 not found in available modes Current xorg.conf: Section "ServerLayout" Identifier "X.org Configured" # Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" # need Option "AutoAddDevices" "Off" to avoid the non-working hald # run moused instead Option "AutoAddDevices" "Off" EndSection Section "Module" Disable "record" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Device" Identifier "Device0" Option "ModeDebug" EndSection Section "Monitor" Identifier "Monitor2220" VendorName "Dell" ModelName "ST2220T" HorizSync 30.00-83.00 VertRefresh 56.00-76.00 # cvt -v 1920 1080 57 # Warning: Refresh Rate is not CVT standard (50, 60, 75 or 85Hz). # 1920x1080 56.90 Hz (CVT) hsync: 63.67 kHz; pclk: 163.00 MHz Modeline "1920x1080_57.00" 163.00 1920 2040 2240 2560 1080 1083 1088 1119 -hsync +vsync # cvt -v -r 1920 1080 # 1920x1080 59.93 Hz (CVT 2.07M9-R) hsync: 66.59 kHz; pclk: 138.50 MHz Modeline "1920x1080R" 138.50 1920 1968 2000 2080 1080 1083 1088 +hsync -vsync EndSection ___ 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: Attempting to get an X11 server running
On Thu, 30 Jun 2011 16:12:28 +, Dieter BSD wrote: > Now to see if I can get this wimpy rage xl to do 1920x1080. If configuring this via X doesn't work, there's always xrandr which you can call from your ~/.xinitrc (or ~/.xsession respectively), like this: xrandr --fb 1920x1080 xrandr --size 1920x1080 I'm using this method since X.org can't get my CRT working at the desired mode 1400x1050 (which XFree86 perfectly did) and insists on running the insufficent mode 1152x864 only. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Attempting to get an X11 server running
> That is incorrect. Don't set AllowEmptyInput, just turn off AutoAddDevices. > http://www.wonkity.com/~wblock/docs/html/aei.html I reduced the config file to: Section "ServerLayout" Identifier "X.org Configured" # Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" Option "AutoAddDevices" "Off" EndSection Section "Module" Disable "record" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection and now the mouse works as expected. After more debugging, got it to see the keysymdb and now the keyboard works as well. Thank you! Now to see if I can get this wimpy rage xl to do 1920x1080. ___ 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: Attempting to get an X11 server running
This is what I use in my xorg.conf see below Notice the mode line for resolution, and HorizSync30-107 VertRefresh 48-120 Also in my /etc/rc.conf I put these lines hald_enable="YES" dbus_enable="YES" This sets up X for me every time and works great. Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/local" FontPath "/usr/share/fonts/TTF" FontPath "/usr/share/fonts/OTF" FontPath "/usr/share/fonts/Type1" FontPath "/usr/share/fonts/misc" FontPath "/usr/share/fonts/CID" FontPath "/usr/share/fonts/75dpi/:unscaled" FontPath "/usr/share/fonts/100dpi/:unscaled" FontPath "/usr/share/fonts/75dpi" FontPath "/usr/share/fonts/100dpi" FontPath "/usr/share/fonts/cyrillic" EndSection Section "Module" Load "extmod" Load "dri2" Load "glx" Load "dbe" Load "dri" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" HorizSync30-107 VertRefresh 48-120 EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "ShadowFB" # [] #Option "DefaultRefresh"# [] #Option "ModeSetClearScreen"# [] Identifier "Card0" Driver "vesa" VendorName "Unknown Vendor" BoardName "Unknown Board" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 1 Modes "1280x1024" "1152x864" "1024x768" EndSubSection SubSection "Display" Depth 4 Modes "1280x1024" "1152x864" "1024x768" EndSubSection SubSection "Display" Depth 8 Modes "1280x1024" "1152x864" "1024x768" EndSubSection SubSection "Display" Depth 15 Modes "1280x1024" "1152x864" "1024x768" EndSubSection SubSection "Display" Depth 16 Modes "1280x1024" "1152x864" "1024x768" EndSubSection SubSection "Display" Viewport 0 0 Depth24 Modes "1280x1024" "1152x864" "1024x768" EndSubSection EndSection > On Thu, 30 Jun 2011, Dieter BSD wrote: > >> google found >> http://www.daemonforums.org/showthread.php?p=27601 >> which suggests using moused instead of hald. Â moused runs, >> but I think I have to get Xorg to use a config file to set >> Â Option "AllowEmptyInput" "off" >> Â Option "AutoAddDevices" Â "off" >> so that it will work without hald. > > That is incorrect. Don't set AllowEmptyInput, just turn off > AutoAddDevices. > http://www.wonkity.com/~wblock/docs/html/aei.html > >> Question 1: why does "Xorg -configure" create a config file >> that doesn't work the same way as just running "Xorg" ? > > The defaults assumed when run are different from those in the generated > config file. I don't know why. > >> Question 2: how do I get a usable config file? > > Look for examples on the net. Realize that most of xorg.conf is > optional now, and you can leave out sections where the defaults are > correct. > >> Question 3: how do I get complete modeline info for what >> it is currently running? > > Please don't mess with modelines, it should not be needed any more. > Just set the resolutions desired in the Screen/Display section. If > modelines are really required, get them out of /var/log/Xorg.0.log. But > they almost certainly are not. > >> Question 5: how do I get hald to work? > > It's not used if you turn off AutoAddDevices or build the xorg-server > port with the HAL option disabled. > > > Learn more about Free hosting web here! > http://click.lavabit.com/bb55ie6fuepogc991stquo4wimf15odaskf4w43gft7r9en3g5rb/ > > _
Re: Attempting to get an X11 server running
On Jun 30, 2011, at 6:11 AM, Warren Block wrote: > On Thu, 30 Jun 2011, Dieter BSD wrote: > >> google found >> http://www.daemonforums.org/showthread.php?p=27601 >> which suggests using moused instead of hald. moused runs, >> but I think I have to get Xorg to use a config file to set >> Option "AllowEmptyInput" "off" >> Option "AutoAddDevices" "off" >> so that it will work without hald. > > That is incorrect. Don't set AllowEmptyInput, just turn off AutoAddDevices. > http://www.wonkity.com/~wblock/docs/html/aei.html > >> Question 1: why does "Xorg -configure" create a config file >> that doesn't work the same way as just running "Xorg" ? > > The defaults assumed when run are different from those in the generated > config file. I don't know why. > >> Question 2: how do I get a usable config file? > > Look for examples on the net. Realize that most of xorg.conf is optional > now, and you can leave out sections where the defaults are correct. > >> Question 3: how do I get complete modeline info for what >> it is currently running? > > Please don't mess with modelines, it should not be needed any more. Just set > the resolutions desired in the Screen/Display section. If modelines are > really required, get them out of /var/log/Xorg.0.log. But they almost > certainly are not. Though if you *really* wanted to, there's cvt(1): cvt - calculate VESA CVT mode lines > >> Question 5: how do I get hald to work? > > It's not used if you turn off AutoAddDevices or build the xorg-server port > with the HAL option disabled.___ > 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" -- Cheers, Devin Teske -> CONTACT INFORMATION <- Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> END TRANSMISSION <- _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ ___ 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: Attempting to get an X11 server running
On Jun 29, 2011, at 9:33 PM, Dieter BSD wrote: >> Q1: how do you start X? > > "Xorg" > (no config file) > > result: display works (1400x1050), but no keyboard or mouse > > "Xorg -configure" > (creates /root/xorg.conf.new) > "Xorg -config /root/xorg.conf.new" > > result: 1280x1024 which monitor doesn't like I've observed this behavior when the probed graphics driver (e.g., "nv") cannot produce the desired resolution, and switching to "vesa" does the job. However, that is not a universal truth. I've also observed situations where the probed graphics driver does just fine (e.g., "mach64" -- or nearly any of the ATI drivers). For the "nv" drivers (NOTE: I'm specifically talking about xf86-video-nv, not nvidia-driver), I often find myself doing this: 1. X -configure 2. sed -i.bak -e 's/nv/vesa/' /root/xorg.conf.new 3. X -config /root/xorg.conf.new Your mileage may var. > > I also tried "Xorg -keyboard Keyboard0 -pointer Mouse0" > with and without "-config /root/xorg.conf.new", same results. > I tried editing the config file, adding a 1400x1050 modeline, > same results. > >> Q2: Have you tried to start X without a config file? > > Yes, see above > >> Q3: Do you have consolekit installed? > > yes, consolekit-0.4.3 from .../amd64/packages-8.2-release/... > ___ > 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" -- Cheers, Devin Teske -> CONTACT INFORMATION <- Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> END TRANSMISSION <- _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ ___ 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: Attempting to get an X11 server running
On Thu, 30 Jun 2011, Dieter BSD wrote: google found http://www.daemonforums.org/showthread.php?p=27601 which suggests using moused instead of hald. moused runs, but I think I have to get Xorg to use a config file to set Option "AllowEmptyInput" "off" Option "AutoAddDevices" "off" so that it will work without hald. That is incorrect. Don't set AllowEmptyInput, just turn off AutoAddDevices. http://www.wonkity.com/~wblock/docs/html/aei.html Question 1: why does "Xorg -configure" create a config file that doesn't work the same way as just running "Xorg" ? The defaults assumed when run are different from those in the generated config file. I don't know why. Question 2: how do I get a usable config file? Look for examples on the net. Realize that most of xorg.conf is optional now, and you can leave out sections where the defaults are correct. Question 3: how do I get complete modeline info for what it is currently running? Please don't mess with modelines, it should not be needed any more. Just set the resolutions desired in the Screen/Display section. If modelines are really required, get them out of /var/log/Xorg.0.log. But they almost certainly are not. Question 5: how do I get hald to work? It's not used if you turn off AutoAddDevices or build the xorg-server port with the HAL option disabled.___ 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: Attempting to get an X11 server running
> Q1: how do you start X? "Xorg" (no config file) result: display works (1400x1050), but no keyboard or mouse "Xorg -configure" (creates /root/xorg.conf.new) "Xorg -config /root/xorg.conf.new" result: 1280x1024 which monitor doesn't like I also tried "Xorg -keyboard Keyboard0 -pointer Mouse0" with and without "-config /root/xorg.conf.new", same results. I tried editing the config file, adding a 1400x1050 modeline, same results. > Q2: Have you tried to start X without a config file? Yes, see above > Q3: Do you have consolekit installed? yes, consolekit-0.4.3 from .../amd64/packages-8.2-release/... ___ 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: Attempting to get an X11 server running
2011-06-30 02:12, Dieter BSD skrev: FreeBSD 8.2 packages: packages-8.2-release amd64 ATI Rage XL Dell ST2220T (1920x1080) "Xorg -configure" generates an xorg.conf file that somehow puts it into 1280x1024 mode and the monitor refuses to use it. I haven't found a way to get the full modeline info for whatever it is actually putting out. xdpyinfo just gives the resolution, not the timing data. I have not found a way to force it to use a modeline of my choosing, it appariently just ignores modelines added to the config file. Q1: how do you start X? Q2: Have you tried to start X without a config file? Q3: Do you have consolekit installed? "Xorg" puts it into 1400x1050 and the monitor accepts it. I can start a window manager and start an xterm window (from another terminal). But it does not listen to the keyboard or mouse. dbus seems to run ok, no errors observed. hald starts up but complains and dies: hald[61843]: 13:03:42.634 [E] ck-tracker.c:376: Error doing GetSeats on ConsoleKit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files hald[61843]: 13:03:42.634 [E] ck-tracker.c:820: Could not get seats and sessions hald[61843]: 13:03:42.634 [W] hald_dbus.c:5881: Could not initialize seats and sessions from ConsoleKit google found http://www.daemonforums.org/showthread.php?p=27601 which suggests using moused instead of hald. moused runs, but I think I have to get Xorg to use a config file to set Option "AllowEmptyInput" "off" Option "AutoAddDevices" "off" so that it will work without hald. Question 1: why does "Xorg -configure" create a config file that doesn't work the same way as just running "Xorg" ? Question 2: how do I get a usable config file? Question 3: how do I get complete modeline info for what it is currently running? Question 4: how do I force it to use a specific modeline? Question 5: how do I get hald to work? ___ 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"
Attempting to get an X11 server running
FreeBSD 8.2 packages: packages-8.2-release amd64 ATI Rage XL Dell ST2220T (1920x1080) "Xorg -configure" generates an xorg.conf file that somehow puts it into 1280x1024 mode and the monitor refuses to use it. I haven't found a way to get the full modeline info for whatever it is actually putting out. xdpyinfo just gives the resolution, not the timing data. I have not found a way to force it to use a modeline of my choosing, it appariently just ignores modelines added to the config file. "Xorg" puts it into 1400x1050 and the monitor accepts it. I can start a window manager and start an xterm window (from another terminal). But it does not listen to the keyboard or mouse. dbus seems to run ok, no errors observed. hald starts up but complains and dies: hald[61843]: 13:03:42.634 [E] ck-tracker.c:376: Error doing GetSeats on ConsoleKit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files hald[61843]: 13:03:42.634 [E] ck-tracker.c:820: Could not get seats and sessions hald[61843]: 13:03:42.634 [W] hald_dbus.c:5881: Could not initialize seats and sessions from ConsoleKit google found http://www.daemonforums.org/showthread.php?p=27601 which suggests using moused instead of hald. moused runs, but I think I have to get Xorg to use a config file to set Option "AllowEmptyInput" "off" Option "AutoAddDevices" "off" so that it will work without hald. Question 1: why does "Xorg -configure" create a config file that doesn't work the same way as just running "Xorg" ? Question 2: how do I get a usable config file? Question 3: how do I get complete modeline info for what it is currently running? Question 4: how do I force it to use a specific modeline? Question 5: how do I get hald to work? ___ 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"
