Questions about Contributions / Licensing for X11
Thanks for response, mainly it sounds like the only criteria is that code is checked in under the MIT license. I've talked to other groups who do reviews of all patches/code before inclusion into the library. They also contact copyright owners when patches contain copyrighted code in order to obtain inclusion permission under the terms of the MIT license. ___ Bryant Lee, PMP®, SCPM IBM Certified Senior Project Manager Information Archive Development Mgr / Proj Mgr Email : brya...@us.ibm.com Phone: (408)927-2146 or tl: 457 - 2146___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Support for screen changes as vector graphics like Webex
On Thu, Jul 23, 2009 at 7:31 PM, Sandeep Khanna wrote: > With NeatX, X2Go, FreeNX, NoMachine NX, the real question is can these > solutions use an existing X session just like x11vnc > (http://www.karlrunge.com/x11vnc/) does and export the screen changes as > vector graphics similar what WebEx does. x11vnc just export the screen > changes by sending a snapshot of the entire screen (only the changed > portions ofcourse) back to the client which is the typical VNC protocol. I can't tell you specifics about how its protocol is built, but NX is not passive like VNC. I believe NX actually contains a complete X server in the client program, and uses its protocol for very efficient display. It is very much better than RDP or VNC. I've never used WebEx so I can't say, but NX is almost like you are sitting at the local terminal. Even smooth scrolling in Firefox looks normal over a slow DSL line. NX can also act as a proxy for RDP or VNC from one local machine to another, and use its protocol for that, though it is not as efficient as a native NX session. Nomachine.com used to have an example server you can connect to and give it a try. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Questions about Contributions / Licensing for X11
On Fri, Jul 24, 2009 at 10:55 AM, Bryant H Lee wrote: > > I'm currently working with my development team in consuming X11 for our > development and use with Mozilla Firefox and before including into my > product I needed to verify a couple items: > > 1. Is there a policy / procedure in place on how code is maintained? > Mainly need some assurances that code that we're using doesn't contain any > contaminated code or code that wasn't originally written by the developer. > > 2. Is there some verification (i.e. code scans) done to ensure that there > isn't any violation of your policies (assuming the answer to #1 is yes). > Hopefully someone from the board can give the "official" position. But I think the answer to both questions is mostly no. X.org is a 20 year old code base with contributions from all over, under various licenses and from companies that no longer exist or have been consumed by larger entities. Currently we only accept code under the MIT license and we take developers word that they aren't putting anything contaminated into the codebase. Q2. seems to be a bit pointless, how can we scan for something if we don't know what it is. Its not like they'll put the word CONTAMINATED in it the comments. Dave. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Questions about Contributions / Licensing for X11
I'm currently working with my development team in consuming X11 for our development and use with Mozilla Firefox and before including into my product I needed to verify a couple items: 1. Is there a policy / procedure in place on how code is maintained? Mainly need some assurances that code that we're using doesn't contain any contaminated code or code that wasn't originally written by the developer. 2. Is there some verification (i.e. code scans) done to ensure that there isn't any violation of your policies (assuming the answer to #1 is yes). Thanks in advance, Bryant ___ Bryant Lee, PMP®, SCPM IBM Certified Senior Project Manager Information Archive Development Mgr / Proj Mgr Email : brya...@us.ibm.com Phone: (408)927-2146 or tl: 457 - 2146___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Support for screen changes as vector graphics like Webex
With NeatX, X2Go, FreeNX, NoMachine NX, the real question is can these solutions use an existing X session just like x11vnc (http://www.karlrunge.com/x11vnc/) does and export the screen changes as vector graphics similar what WebEx does. x11vnc just export the screen changes by sending a snapshot of the entire screen (only the changed portions ofcourse) back to the client which is the typical VNC protocol. From: Paul Hartman To: xorg@lists.freedesktop.org Sent: Thursday, July 23, 2009 5:35:09 PM Subject: Re: Support for screen changes as vector graphics like Webex On Thu, Jul 23, 2009 at 4:24 PM, Pat Kane wrote: > Google seems to have their own version of NX: > > http://code.google.com/p/neatx/ Other versions of NX protocol implementation are: FreeNX: http://freenx.berlios.de/ x2go: http://www.x2go.org/ ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [Intel-gfx] [ANNOUNCE] xf86-video-intel 2.8.0
it fails to build with follow error: make[3]: Entering directory `/home/stephan/projects/OpenELEC.work/build.OpenELEC.intel.i386.uClibc/xf86-video-intel-2.8.0/uxa' CCuxa.o In file included from uxa.c:37: uxa-priv.h:46:35: error: X11/extensions/shmstr.h: No such file or directory In file included from uxa.c:37: uxa-priv.h:324: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'uxa_shm_funcs' uxa-priv.h:328: error: expected declaration specifiers or '...' before 'ShmFuncsPtr' uxa-priv.h:334: warning: parameter names (without types) in function declaration uxa.c: In function 'uxa_driver_init': uxa.c:527: error: 'uxa_shm_funcs' undeclared (first use in this function) uxa.c:527: error: (Each undeclared identifier is reported only once uxa.c:527: error: for each function it appears in.) uxa.c:527: error: too many arguments to function 'ShmRegisterFuncs' make[3]: *** [uxa.lo] Error 1 make[3]: Leaving directory `/home/stephan/projects/OpenELEC.work/build.OpenELEC.intel.i386.uClibc/xf86-video-intel-2.8.0/uxa' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/stephan/projects/OpenELEC.work/build.OpenELEC.intel.i386.uClibc/xf86-video-intel-2.8.0' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/stephan/projects/OpenELEC.work/build.OpenELEC.intel.i386.uClibc/xf86-video-intel-2.8.0' make: *** [system] Fehler 2 uxa/uxa-priv.h contains: #include #define NEED_EVENTS #include #ifdef MITSHM #define _XSHM_SERVER_ #include #endif in master Peter Hutterer has commited patch 0a4c4c5fe8ebad2dd13f5770bd90a194eebb2890 from 2009-07-18 to lets build against xextproto 7.1 that are not included in that release. Stephan -- ### OpenELEC.tv ### The free and open Mediacenter Distribution 4 you http://www.openelec.tv ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: GDM/Gnome confused about screen size
> > Yes, GNOME is trying to make sure you can see both panels in both monitors. > >> 09:07 a...@danny/x86_64 [linux-2.6-stable.git] >xrandr >> Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 4096 x 4096 >> VGA1 connected 1440x900+0+0 (normal left inverted right x axis y axis) >> 408mm x 255mm > Turn off VGA via the GNOME Display Preferences (or with xrandr -o VGA > --off) and GNOME will reposition the panels to align with the larger > remaining screen. Hmmm xrandr doesn't seem to be having any effect on Gnome, although if I turn on the second monitor I get a "No Signal" instead of a cloned output. 23:28 a...@danny/x86_64 [~] >xrandr --output VGA1 --off 23:30 a...@danny/x86_64 [~] >xrandr Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 2048 x 2048 VGA1 connected (normal left inverted right x axis y axis) 1440x900 59.9 + 1280x1024 75.0 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 640x48072.8 75.0 66.7 60.0 720x40070.1 DVI1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 459mm x 296mm 1680x1050 59.9*+ 1280x1024 75.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 640x48072.8 75.0 66.7 60.0 720x40070.1 Is there a setting I can add to my xorg.conf that will force the VGA1 to be off when the system first starts X? -- Alex, homepage: http://www.bennee.com/~alex/ http://www.half-llama.co.uk ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Support for screen changes as vector graphics like Webex
On Thu, Jul 23, 2009 at 4:24 PM, Pat Kane wrote: > Google seems to have their own version of NX: > > http://code.google.com/p/neatx/ Other versions of NX protocol implementation are: FreeNX: http://freenx.berlios.de/ x2go: http://www.x2go.org/ ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Support for screen changes as vector graphics like Webex
Google seems to have their own version of NX: http://code.google.com/p/neatx/ On Thu, Jul 23, 2009 at 3:27 PM, Joel Feiner wrote: > NoMachine's NX server and client is probably what you are looking for. > > ___ > xorg mailing list > xorg@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/xorg > ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Support for screen changes as vector graphics like Webex
NoMachine's NX server and client is probably what you are looking for. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Support for screen changes as vector graphics like Webex
Hi, I am looking for truly Webex like performance using the Linuxon the server-side and any client (Windows, Linux, Mac, etc). When using VNC (x11vnc + SSVNC), the immediate thing I notice is that UI seems to paint the changed portions of the screen from top to bottom but, using Webex it seems very natural and just like my own local desktop! That's probably because of Webex only sends the Vector graphicsof changed items only. Do you have any other software suggestions on the Linux platform to give the Vector graphic like updates as Webex? Or, is this some client viewer (vncviewer, ssvnc, etc) configuration when using the VNC protocol (vncserver or x11vnc on the server side). Does the current xorg X server support querying changes as vector graphics? If yes, does it have a WebEx like or VNC client/server product to go along with it? Thanks, Sandeep Khanna ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: amd64 no screens SOLVED
Alex Deucher wrote: > On Thu, Jul 23, 2009 at 1:36 PM, PJ wrote: > >> PJ wrote: >> >>> Adam K Kirchhoff wrote: >>> >>> PJ wrote: > I do now and it still does not work... > The xf86-input-keyboard & mouse drivers are installed; so is > xf86-video-fbdev (was not being loaded) > The screen goes black when testing with X & xorg.conf.new; > startx causes screen syncing with streking on screeen. > Neither permits me to opt out with ctl-alt-bkspace; have to reboot. > Don't understand why keyboard & mouse not loaded... also no directories > for fonts... could that be the problem? > > below is ...snip.. from "startx" log: > > (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 23 09:32:10 2009 > (II) Loader magic: 0x35e0 > (II) Module ABI versions: > � � X.Org ANSI C Emulation: 0.4 > � � X.Org Video Driver: 5.0 > � � X.Org XInput driver : 4.0 > � � X.Org Server Extension : 2.0 > (II) Loader running on freebsd > (--) Using syscons driver with X support (version 2.0) > (--) using VT number 9 > > (--) PCI:*(0...@1:0:0) ATI Technologies Inc Radeon Mobility X700 (PCIE) > rev > 0, Mem @ 0xc800/134217728, 0xc010/65536, I/O @ 0x9000/256, > BIOS @ 0x/65536 > (==) Using default built-in configuration (30 lines) > (==) --- Start of built-in configuration --- > � � Section "Device" > � � � � Identifier � �"Builtin Default ati Device 0" > � � � � Driver � �"ati" > � � EndSection > � � Section "Screen" > � � � � Identifier � �"Builtin Default ati Screen 0" > � � � � Device � �"Builtin Default ati Device 0" > � � EndSection > � � Section "Device" > � � � � Identifier � �"Builtin Default vesa Device 0" > � � � � Driver � �"vesa" > � � EndSection > � � Section "Screen" > � � � � Identifier � �"Builtin Default vesa Screen 0" > � � � � Device � �"Builtin Default vesa Device 0" > � � EndSection > � � Section "Device" > � � � � Identifier � �"Builtin Default fbdev Device 0" > � � � � Driver � �"fbdev" > � � EndSection > � � Section "Screen" > � � � � Identifier � �"Builtin Default fbdev Screen 0" > � � � � Device � �"Builtin Default fbdev Device 0" > � � EndSection > � � Section "ServerLayout" > � � � � Identifier � �"Builtin Default Layout" > � � � � Screen � �"Builtin Default ati Screen 0" > � � � � Screen � �"Builtin Default vesa Screen 0" > � � � � Screen � �"Builtin Default fbdev Screen 0" > � � EndSection > (==) --- End of built-in configuration --- > (==) ServerLayout "Builtin Default Layout" > (**) |-->Screen "Builtin Default ati Screen 0" (0) > (**) | � |-->Monitor "" > (**) | � |-->Device "Builtin Default ati Device 0" > (==) No monitor specified for screen "Builtin Default ati Screen 0". > � � Using a default monitor configuration. > (**) |-->Screen "Builtin Default vesa Screen 0" (1) > (**) | � |-->Monitor "" > (**) | � |-->Device "Builtin Default vesa Device 0" > (==) No monitor specified for screen "Builtin Default vesa Screen 0". > � � Using a default monitor configuration. > (**) |-->Screen "Builtin Default fbdev Screen 0" (2) > (**) | � |-->Monitor "" > (**) | � |-->Device "Builtin Default fbdev Device 0" > (==) No monitor specified for screen "Builtin Default fbdev Screen 0". > � � Using a default monitor configuration. > (==) Automatically adding devices > (==) Automatically enabling devices > (WW) The directory "/usr/local/lib/X11/fonts/TTF/" does not exist. > � � Entry deleted from font path. > (WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist. > � � Entry deleted from font path. > (WW) The directory "/usr/local/lib/X11/fonts/Type1/" does not exist. > � � Entry deleted from font path. > (WW) `fonts.dir' not found (or not valid) in > "/usr/local/lib/X11/fonts/100dpi/". > � � Entry deleted from font path. > � � (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/100dpi/"). > (WW) `fonts.dir' not found (or not valid) in > "/usr/local/lib/X11/fonts/75dpi/". > � � Entry deleted from font path. > � � (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/75dpi/"). > (==) FontPath set to: > � � /usr/local/lib/X11/fonts/misc/, > � � built-ins > (==) ModulePath set to "/usr/local/lib/xorg/modules" > (II) Cannot locate a core pointer device. > (II) Cannot locate a core keyboard device. > (II) The server relies on HAL to provide the list of input devices. > � � If no devices become available, reconfigure HAL or disable > AllowEmptyInput. > � �I'll look for hal configuration-- but I don't know what that could > do... > And where do I "disable AllowEmptyInput" ? > > > > > You would create an xorg.conf file and make sure you don't
Re: amd64 no screens SOLVED
On Thu, Jul 23, 2009 at 1:36 PM, PJ wrote: > PJ wrote: >> Adam K Kirchhoff wrote: >> >>> PJ wrote: >>> I do now and it still does not work... The xf86-input-keyboard & mouse drivers are installed; so is xf86-video-fbdev (was not being loaded) The screen goes black when testing with X & xorg.conf.new; startx causes screen syncing with streking on screeen. Neither permits me to opt out with ctl-alt-bkspace; have to reboot. Don't understand why keyboard & mouse not loaded... also no directories for fonts... could that be the problem? below is ...snip.. from "startx" log: (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 23 09:32:10 2009 (II) Loader magic: 0x35e0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0...@1:0:0) ATI Technologies Inc Radeon Mobility X700 (PCIE) rev 0, Mem @ 0xc800/134217728, 0xc010/65536, I/O @ 0x9000/256, BIOS @ 0x/65536 (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier "Builtin Default ati Device 0" Driver "ati" EndSection Section "Screen" Identifier "Builtin Default ati Screen 0" Device "Builtin Default ati Device 0" EndSection Section "Device" Identifier "Builtin Default vesa Device 0" Driver "vesa" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 0" Device "Builtin Default vesa Device 0" EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default ati Screen 0" Screen "Builtin Default vesa Screen 0" Screen "Builtin Default fbdev Screen 0" EndSection (==) --- End of built-in configuration --- (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default ati Screen 0" (0) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default ati Device 0" (==) No monitor specified for screen "Builtin Default ati Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default vesa Screen 0" (1) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default vesa Device 0" (==) No monitor specified for screen "Builtin Default vesa Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default fbdev Screen 0" (2) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default fbdev Device 0" (==) No monitor specified for screen "Builtin Default fbdev Screen 0". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/local/lib/X11/fonts/TTF/" does not exist. Entry deleted from font path. (WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist. Entry deleted from font path. (WW) The directory "/usr/local/lib/X11/fonts/Type1/" does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/100dpi/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/100dpi/"). (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/75dpi/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/75dpi/"). (==) FontPath set to: /usr/local/lib/X11/fonts/misc/, built-ins (==) ModulePath set to "/usr/local/lib/xorg/modules" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. I'll look for hal configuration-- but I don't know what that could do... And where do I "disable AllowEmptyInput" ? >>> You would create an xorg.conf file and make sure you don't have that >>> option. Your xorg.conf.new file, from what the other log file shows, >>> clearly has it enabled. >>> >>> >>> Alternatively, you could try starting up hald and trying X again. Add
Re: amd64 no screens SOLVED
PJ wrote: > Adam K Kirchhoff wrote: > >> PJ wrote: >> >>> I do now and it still does not work... >>> The xf86-input-keyboard & mouse drivers are installed; so is >>> xf86-video-fbdev (was not being loaded) >>> The screen goes black when testing with X & xorg.conf.new; >>> startx causes screen syncing with streking on screeen. >>> Neither permits me to opt out with ctl-alt-bkspace; have to reboot. >>> Don't understand why keyboard & mouse not loaded... also no directories >>> for fonts... could that be the problem? >>> >>> below is ...snip.. from "startx" log: >>> >>> (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 23 09:32:10 2009 >>> (II) Loader magic: 0x35e0 >>> (II) Module ABI versions: >>> X.Org ANSI C Emulation: 0.4 >>> X.Org Video Driver: 5.0 >>> X.Org XInput driver : 4.0 >>> X.Org Server Extension : 2.0 >>> (II) Loader running on freebsd >>> (--) Using syscons driver with X support (version 2.0) >>> (--) using VT number 9 >>> >>> (--) PCI:*(0...@1:0:0) ATI Technologies Inc Radeon Mobility X700 (PCIE) rev >>> 0, Mem @ 0xc800/134217728, 0xc010/65536, I/O @ 0x9000/256, >>> BIOS @ 0x/65536 >>> (==) Using default built-in configuration (30 lines) >>> (==) --- Start of built-in configuration --- >>> Section "Device" >>> Identifier"Builtin Default ati Device 0" >>> Driver"ati" >>> EndSection >>> Section "Screen" >>> Identifier"Builtin Default ati Screen 0" >>> Device"Builtin Default ati Device 0" >>> EndSection >>> Section "Device" >>> Identifier"Builtin Default vesa Device 0" >>> Driver"vesa" >>> EndSection >>> Section "Screen" >>> Identifier"Builtin Default vesa Screen 0" >>> Device"Builtin Default vesa Device 0" >>> EndSection >>> Section "Device" >>> Identifier"Builtin Default fbdev Device 0" >>> Driver"fbdev" >>> EndSection >>> Section "Screen" >>> Identifier"Builtin Default fbdev Screen 0" >>> Device"Builtin Default fbdev Device 0" >>> EndSection >>> Section "ServerLayout" >>> Identifier"Builtin Default Layout" >>> Screen"Builtin Default ati Screen 0" >>> Screen"Builtin Default vesa Screen 0" >>> Screen"Builtin Default fbdev Screen 0" >>> EndSection >>> (==) --- End of built-in configuration --- >>> (==) ServerLayout "Builtin Default Layout" >>> (**) |-->Screen "Builtin Default ati Screen 0" (0) >>> (**) | |-->Monitor "" >>> (**) | |-->Device "Builtin Default ati Device 0" >>> (==) No monitor specified for screen "Builtin Default ati Screen 0". >>> Using a default monitor configuration. >>> (**) |-->Screen "Builtin Default vesa Screen 0" (1) >>> (**) | |-->Monitor "" >>> (**) | |-->Device "Builtin Default vesa Device 0" >>> (==) No monitor specified for screen "Builtin Default vesa Screen 0". >>> Using a default monitor configuration. >>> (**) |-->Screen "Builtin Default fbdev Screen 0" (2) >>> (**) | |-->Monitor "" >>> (**) | |-->Device "Builtin Default fbdev Device 0" >>> (==) No monitor specified for screen "Builtin Default fbdev Screen 0". >>> Using a default monitor configuration. >>> (==) Automatically adding devices >>> (==) Automatically enabling devices >>> (WW) The directory "/usr/local/lib/X11/fonts/TTF/" does not exist. >>> Entry deleted from font path. >>> (WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist. >>> Entry deleted from font path. >>> (WW) The directory "/usr/local/lib/X11/fonts/Type1/" does not exist. >>> Entry deleted from font path. >>> (WW) `fonts.dir' not found (or not valid) in >>> "/usr/local/lib/X11/fonts/100dpi/". >>> Entry deleted from font path. >>> (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/100dpi/"). >>> (WW) `fonts.dir' not found (or not valid) in >>> "/usr/local/lib/X11/fonts/75dpi/". >>> Entry deleted from font path. >>> (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/75dpi/"). >>> (==) FontPath set to: >>> /usr/local/lib/X11/fonts/misc/, >>> built-ins >>> (==) ModulePath set to "/usr/local/lib/xorg/modules" >>> (II) Cannot locate a core pointer device. >>> (II) Cannot locate a core keyboard device. >>> (II) The server relies on HAL to provide the list of input devices. >>> If no devices become available, reconfigure HAL or disable >>> AllowEmptyInput. >>>I'll look for hal configuration-- but I don't know what that could >>> do... >>> And where do I "disable AllowEmptyInput" ? >>> >>> >>> >>> >> You would create an xorg.conf file and make sure you don't have that >> option. Your xorg.conf.new file, from what the other log file shows, >> clearly has it enabled. >> >> >> Alternatively, you could try starting up hald and trying X again. Add >> these lines to your /etc/rc.conf file: >> >> dbus_enable="YES" >> hald_enable="YES" >> >> And then run (as root or with sudo): >> >> /usr/lo
Re: status with the latest git xserver
Aaron Plattner wrote: > On Sat, Jul 18, 2009 at 12:07:17AM -0700, Justin P. Mattock wrote: > >> This is a status from over here: >> >> macbook pro ati chipset works perfectly >> with the latest git xserver, minor issue due to me >> getting a bit confused but nothing out of the ordinary. >> >> As for my other machine the imac nvidia chipset, well >> a bit of an ABI issue: >> >> (II) Loading extension DRI2 >> (II) LoadModule: "nvidia" >> (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so >> (II) Module nvidia: vendor="NVIDIA Corporation" >> compiled for 4.0.2, module version = 1.0.0 >> Module class: X.Org Video Driver >> WARNING WARNING WARNING WARNING >> This server has a video driver ABI version of 6.0 that is not >> supported by this NVIDIA driver. Please check >> http://www.nvidia.com/ for driver updates or downgrade to an X >> server with a supported driver ABI. >> = >> (WW) NVIDIA: The driver will continue to load, but may behave strangely. >> (WW) NVIDIA: This server has an unsupported input driver ABI version >> (have 7.0, need< 5.0). The driver will continue to load, but may >> behave strangely. >> (II) LoadModule: "kbd" >> >> soulution was(after googling a bit) >>startx -ignoreABI, >> > > startx has this dumb behavior where it will silently ignore any arguments it > doesn't recognize. To actually pass that option on to the X server, you have > to > do this: > > startx -- -ignoreABI > > Yes, that's a space, two dashes, another space, and then another dash. > > >> but for some reason this didn't do anything. >> I had to use in xorg.conf >> >> Section "ServerFlags" >> Option "IgnoreABI" "true" >> EndSection >> >> Hopefully we don't have to wait to long for nvidia.. >> > > Does it work? We have a policy of trying to support an ABI but not actually > marking it supported without -ignoreABI until after it has been declared > frozen > by the X.org release manager. > > >> Anyways nice work with the xserver xorg!! >> > > Hey alright, just grabbed the latest beta driver, compiles with 2.6.31-rc4 perfectly. (I owe you a thanks, as well as anybody else associated with nvidia). Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: amd64 no screens
Adam K Kirchhoff wrote: > PJ wrote: >> >> I do now and it still does not work... >> The xf86-input-keyboard & mouse drivers are installed; so is >> xf86-video-fbdev (was not being loaded) >> The screen goes black when testing with X & xorg.conf.new; >> startx causes screen syncing with streking on screeen. >> Neither permits me to opt out with ctl-alt-bkspace; have to reboot. >> Don't understand why keyboard & mouse not loaded... also no directories >> for fonts... could that be the problem? >> >> below is ...snip.. from "startx" log: >> >> (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 23 09:32:10 2009 >> (II) Loader magic: 0x35e0 >> (II) Module ABI versions: >> X.Org ANSI C Emulation: 0.4 >> X.Org Video Driver: 5.0 >> X.Org XInput driver : 4.0 >> X.Org Server Extension : 2.0 >> (II) Loader running on freebsd >> (--) Using syscons driver with X support (version 2.0) >> (--) using VT number 9 >> >> (--) PCI:*(0...@1:0:0) ATI Technologies Inc Radeon Mobility X700 (PCIE) rev >> 0, Mem @ 0xc800/134217728, 0xc010/65536, I/O @ 0x9000/256, >> BIOS @ 0x/65536 >> (==) Using default built-in configuration (30 lines) >> (==) --- Start of built-in configuration --- >> Section "Device" >> Identifier"Builtin Default ati Device 0" >> Driver"ati" >> EndSection >> Section "Screen" >> Identifier"Builtin Default ati Screen 0" >> Device"Builtin Default ati Device 0" >> EndSection >> Section "Device" >> Identifier"Builtin Default vesa Device 0" >> Driver"vesa" >> EndSection >> Section "Screen" >> Identifier"Builtin Default vesa Screen 0" >> Device"Builtin Default vesa Device 0" >> EndSection >> Section "Device" >> Identifier"Builtin Default fbdev Device 0" >> Driver"fbdev" >> EndSection >> Section "Screen" >> Identifier"Builtin Default fbdev Screen 0" >> Device"Builtin Default fbdev Device 0" >> EndSection >> Section "ServerLayout" >> Identifier"Builtin Default Layout" >> Screen"Builtin Default ati Screen 0" >> Screen"Builtin Default vesa Screen 0" >> Screen"Builtin Default fbdev Screen 0" >> EndSection >> (==) --- End of built-in configuration --- >> (==) ServerLayout "Builtin Default Layout" >> (**) |-->Screen "Builtin Default ati Screen 0" (0) >> (**) | |-->Monitor "" >> (**) | |-->Device "Builtin Default ati Device 0" >> (==) No monitor specified for screen "Builtin Default ati Screen 0". >> Using a default monitor configuration. >> (**) |-->Screen "Builtin Default vesa Screen 0" (1) >> (**) | |-->Monitor "" >> (**) | |-->Device "Builtin Default vesa Device 0" >> (==) No monitor specified for screen "Builtin Default vesa Screen 0". >> Using a default monitor configuration. >> (**) |-->Screen "Builtin Default fbdev Screen 0" (2) >> (**) | |-->Monitor "" >> (**) | |-->Device "Builtin Default fbdev Device 0" >> (==) No monitor specified for screen "Builtin Default fbdev Screen 0". >> Using a default monitor configuration. >> (==) Automatically adding devices >> (==) Automatically enabling devices >> (WW) The directory "/usr/local/lib/X11/fonts/TTF/" does not exist. >> Entry deleted from font path. >> (WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist. >> Entry deleted from font path. >> (WW) The directory "/usr/local/lib/X11/fonts/Type1/" does not exist. >> Entry deleted from font path. >> (WW) `fonts.dir' not found (or not valid) in >> "/usr/local/lib/X11/fonts/100dpi/". >> Entry deleted from font path. >> (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/100dpi/"). >> (WW) `fonts.dir' not found (or not valid) in >> "/usr/local/lib/X11/fonts/75dpi/". >> Entry deleted from font path. >> (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/75dpi/"). >> (==) FontPath set to: >> /usr/local/lib/X11/fonts/misc/, >> built-ins >> (==) ModulePath set to "/usr/local/lib/xorg/modules" >> (II) Cannot locate a core pointer device. >> (II) Cannot locate a core keyboard device. >> (II) The server relies on HAL to provide the list of input devices. >> If no devices become available, reconfigure HAL or disable >> AllowEmptyInput. >>I'll look for hal configuration-- but I don't know what that could >> do... >> And where do I "disable AllowEmptyInput" ? >> >> >> > > > You would create an xorg.conf file and make sure you don't have that > option. Your xorg.conf.new file, from what the other log file shows, > clearly has it enabled. > > > Alternatively, you could try starting up hald and trying X again. Add > these lines to your /etc/rc.conf file: > > dbus_enable="YES" > hald_enable="YES" > > And then run (as root or with sudo): > > /usr/local/etc/rc.d/dbus start > /usr/local/etc/rc.d/hald start > > > Finally, do you actually have the fonts installed? > > Adam > > The AllowEmptyInput is
Re: evdev+hal => Too many input devices.
On Thu, Jul 23, 2009 at 06:05:24AM -0700, Brian Rogers wrote: > OK, that didn't work. Calling device_move with a null new_parent > works the way I initially thought it did. I don't like the idea of > these things moving right before they are deleted, and neither does > HAL since it still doesn't remove the input devices properly in this > case. I think I'll go with the original strategy to ensure > everything gets removed from the same place it was first added. And > I might make it work without polling. > > The rfcomm and connection objects sticking around until some process > exits shouldn't harm anything since I believe a new connection will > be given a unique name to avoid a conflict. I'll be sure to check > this. What went wrong if the rfcomm was still inside the connection > when the connection was deleted? Kernel oops. See commit acea6852f3, the comment contains the pointer to my original bug report and the resulting discussion on lkml. Commit 8ac62dc773 also looks relevant. Gabor -- - MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences - ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: amd64 no screens
Adam K Kirchhoff wrote: > PJ wrote: >> >>> That combination should work just fine. I've used a handful of radeon >>> cards on FreeBSD/amd64. >>> >>> The driver that FreeBSD attaches to your video card (vga) is >>> completely independent of Xorg and should have absolutely nothing to >>> do with your problems. >>> >>> Without any /etc/X11/xorg.conf file, simply try starting X and show us >>> the resulting log file that is generated. >>> >>> Adam >>> >> >> (II) LoadModule: "ati" >> (WW) Warning, couldn't open module ati >> (II) UnloadModule: "ati" >> (EE) Failed to load module "ati" (module does not exist, 0) >> (II) LoadModule: "vesa" >> (II) Loading /usr/local/lib/xorg/modules/drivers//vesa_drv.so >> (II) Module vesa: vendor="X.Org Foundation" > > You do not have xf86-video-ati installed :-) > > Adam > I do now and it still does not work... The xf86-input-keyboard & mouse drivers are installed; so is xf86-video-fbdev (was not being loaded) The screen goes black when testing with X & xorg.conf.new; startx causes screen syncing with streking on screeen. Neither permits me to opt out with ctl-alt-bkspace; have to reboot. Don't understand why keyboard & mouse not loaded... also no directories for fonts... could that be the problem? (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 23 09:24:01 2009 (++) Using config file: "xorg.conf.new" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/local/lib/X11/fonts/TTF/" does not exist. Entry deleted from font path. (WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist. Entry deleted from font path. (WW) The directory "/usr/local/lib/X11/fonts/Type1/" does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/100dpi/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/100dpi/"). (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/75dpi/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/75dpi/"). (WW) The directory "/usr/local/lib/X11/fonts/TTF/" does not exist. Entry deleted from font path. (WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist. Entry deleted from font path. (WW) The directory "/usr/local/lib/X11/fonts/Type1/" does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/100dpi/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/100dpi/"). (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts/75dpi/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/75dpi/"). (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/misc/, built-ins (**) ModulePath set to "/usr/local/lib/xorg/modules" (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling Mouse0 (WW) Disabling Keyboard0 (II) Loader magic: 0x35e0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 below is ...snip.. from "startx" log: (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 23 09:32:10 2009 (II) Loader magic: 0x35e0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0...@1:0:0) ATI Technologies Inc Radeon Mobility X700 (PCIE) rev 0, Mem @ 0xc800/134217728, 0xc010/65536, I/O @ 0x9000/256, BIOS @ 0x/65536 (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier"Builtin Default ati Device 0" Driver"ati" EndSection Section "Screen" Identifier"Builtin Default ati Screen 0" Device"Builtin Default ati Device 0" EndSection Section "Device" Identifier"Builtin Default vesa Device 0" Driver"vesa" EndSection Section "Screen" Identifier"Builtin Default vesa Screen 0" Device"Builtin Default vesa Device 0" EndSection Section "Device" Identifier"Builtin Default fbdev Device 0" Driver"fbdev" EndSection Section "Screen" Identifier"Builtin Default fbdev Screen 0" Device"Builtin Default fbdev Device 0" EndSection Section "ServerLayout" Identifier"
Re: amd64 no screens
PJ wrote: > >> That combination should work just fine. I've used a handful of radeon >> cards on FreeBSD/amd64. >> >> The driver that FreeBSD attaches to your video card (vga) is >> completely independent of Xorg and should have absolutely nothing to >> do with your problems. >> >> Without any /etc/X11/xorg.conf file, simply try starting X and show us >> the resulting log file that is generated. >> >> Adam >> > > (II) LoadModule: "ati" > (WW) Warning, couldn't open module ati > (II) UnloadModule: "ati" > (EE) Failed to load module "ati" (module does not exist, 0) > (II) LoadModule: "vesa" > (II) Loading /usr/local/lib/xorg/modules/drivers//vesa_drv.so > (II) Module vesa: vendor="X.Org Foundation" You do not have xf86-video-ati installed :-) Adam ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: evdev+hal => Too many input devices.
Brian Rogers wrote:
> Gabor Gombas wrote:
>
>> Hi,
>>
>> On Wed, Jul 22, 2009 at 02:45:32PM -0700, Brian Rogers wrote:
>>
>>
>>
>>> @@ -118,14 +113,16 @@ static void del_conn(struct work_struct *work)
>>> if (!device_is_registered(&conn->dev))
>>> return;
>>>
>>> + /* wait for child devices to go away first */
>>> while (1) {
>>> struct device *dev;
>>>
>>> - dev = device_find_child(&conn->dev, NULL, __match_tty);
>>> + dev = device_find_child(&conn->dev, NULL, __match_any);
>>> if (!dev)
>>> break;
>>> - device_move(dev, NULL, DPM_ORDER_DEV_LAST);
>>> put_device(dev);
>>> +
>>> + msleep(100);
>>> }
>>>
>>> device_del(&conn->dev);
>>>
>>>
>> Won't this cause problems for rfcomm devices (again)? This code was added
>> for the reason in the comment you've deleted: the rfcomm device can
>> remain alive long after the connection is done, and it won't go away
>> until you find & manually kill the process that holds the device open.
>>
>
> The device_move action looked obsolete to me since the comment lead me
> to believe that device_move was moving the device to the root of /sys. I
> saw the input devices, which weren't being touched there, wind up in the
> root on their own when the connection was deleted so I assumed that had
> since become automatic. But now that I look at the device_move function,
> it looks like moving to null actually deletes the device.
>
> In that case, it's probably best to just delete everything right there
> and not wait for anything to close on its own. If that doesn't create
> any problems, that's what I'll do. Thanks for bringing this up.
>
OK, that didn't work. Calling device_move with a null new_parent works
the way I initially thought it did. I don't like the idea of these
things moving right before they are deleted, and neither does HAL since
it still doesn't remove the input devices properly in this case. I think
I'll go with the original strategy to ensure everything gets removed
from the same place it was first added. And I might make it work without
polling.
The rfcomm and connection objects sticking around until some process
exits shouldn't harm anything since I believe a new connection will be
given a unique name to avoid a conflict. I'll be sure to check this.
What went wrong if the rfcomm was still inside the connection when the
connection was deleted?
Brian
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: amd64 no screens
Robert Noland wrote: > On Thu, 2009-07-23 at 08:01 -0400, PJ wrote: > >> Is it possible there is some problem with xorg 7.4 on FreeBSD 7.2 >> running on an amd64 Turion portable. The error seems to be "no vga >> module" "no screens found" no drivers available. >> The default configuration shows the driver choses as "vesa" by ATI >> technologies "Radeon Mobility X700 (PCIE)" >> The dmesg.boot shows the driver as vga, generic. >> I have read all the documentation I could find and it appears that this >> particular configuration is not supported by FreeBSD...i.e. there is no >> reference to Radeon or X700 in their hardware listing. But what about Xorg? >> It is rather strange, but in my adventure in installing this stuff, at >> one point I was getting something of a screen running but there seemed >> to be a problem with a mouse or something like that... don't recall... >> but it seemed to me that it should be possilbe to make this beastie work. >> In my latest and greatest effort, I have installed everything from >> sources, but the driver is forced to be a vesa driver by xorg when the >> ordinary non-X screen boot-up indicates the driver as being vga... >> somebody has got things rather crossed up? >> What do we do now? >> TIA >> PJ >> > > That hardware should work fine. I expect that you didn't have the > radeon (xf86-video-ati) driver installed when you made the > configuration. > > robert. > > >> -- >> Hervé Kempf: "Pour sauver la planète, sortez du capitalisme." >> - >> Phil Jourdan --- p...@ptahhotep.com >>http://www.ptahhotep.com >>http://www.chiccantine.com/andypantry.php >> >> >> ___ >> xorg mailing list >> xorg@lists.freedesktop.org >> http://lists.freedesktop.org/mailman/listinfo/xorg >> Wouf... & duh!... do I feel stupid or what? I installed the minimal xorg files and just plain didn't think... toc...toc...toc... that's the sound of a blunt instrument smacking my forehead... I wonder what else I am missing besides the other part of the brain? Thanks robert btw, I just replied to Adam with snips of my log file... anything there that I should be dealing with... I did notice in my effort to start with "startx" some references to xinit and xauth that were not too promising - but those proggies are installer... oh, well, I'll try starting again & see what pops up... thanks again PJ -- Hervé Kempf: "Pour sauver la planète, sortez du capitalisme." - Phil Jourdan --- p...@ptahhotep.com http://www.ptahhotep.com http://www.chiccantine.com/andypantry.php ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: amd64 no screens
Adam K Kirchhoff wrote: > PJ wrote: >> Is it possible there is some problem with xorg 7.4 on FreeBSD 7.2 >> running on an amd64 Turion portable. The error seems to be "no vga >> module" "no screens found" no drivers available. >> The default configuration shows the driver choses as "vesa" by ATI >> technologies "Radeon Mobility X700 (PCIE)" >> The dmesg.boot shows the driver as vga, generic. >> I have read all the documentation I could find and it appears that this >> particular configuration is not supported by FreeBSD...i.e. there is no >> reference to Radeon or X700 in their hardware listing. But what about >> Xorg? >> It is rather strange, but in my adventure in installing this stuff, at >> one point I was getting something of a screen running but there seemed >> to be a problem with a mouse or something like that... don't recall... >> but it seemed to me that it should be possilbe to make this beastie >> work. >> In my latest and greatest effort, I have installed everything from >> sources, but the driver is forced to be a vesa driver by xorg when the >> ordinary non-X screen boot-up indicates the driver as being vga... >> somebody has got things rather crossed up? >> What do we do now? >> TIA >> PJ >> >> > > That combination should work just fine. I've used a handful of radeon > cards on FreeBSD/amd64. > > The driver that FreeBSD attaches to your video card (vga) is > completely independent of Xorg and should have absolutely nothing to > do with your problems. > > Without any /etc/X11/xorg.conf file, simply try starting X and show us > the resulting log file that is generated. > > Adam Thanks for the ultra fast response, Adam. Deleted old logfiles & this is sections relevant (otherwise it's rather redundant and far too long (would you believe - over 100,000 bytes)... to run tried bothe "startx" and just plain "X". This is excerpted from runnint "X" (with no params): Build Date: 22 July 2009 12:47:29PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 23 08:36:54 2009 (II) Loader magic: 0x35e0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0...@1:0:0) ATI Technologies Inc Radeon Mobility X700 (PCIE) rev 0, Mem @ 0xc800/134217728, 0xc010/65536, I/O @ 0x9000/256, BIOS @ 0x/65536 (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier"Builtin Default ati Device 0" Driver"ati" EndSection Section "Screen" Identifier"Builtin Default ati Screen 0" Device"Builtin Default ati Device 0" EndSection Section "Device" Identifier"Builtin Default vesa Device 0" Driver"vesa" EndSection Section "Screen" Identifier"Builtin Default vesa Screen 0" Device"Builtin Default vesa Device 0" EndSection Section "Device" Identifier"Builtin Default fbdev Device 0" Driver"fbdev" EndSection Section "Screen" Identifier"Builtin Default fbdev Screen 0" Device"Builtin Default fbdev Device 0" EndSection Section "ServerLayout" Identifier"Builtin Default Layout" Screen"Builtin Default ati Screen 0" Screen"Builtin Default vesa Screen 0" Screen"Builtin Default fbdev Screen 0" EndSection (==) --- End of built-in configuration --- (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default ati Screen 0" (0) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default ati Device 0" (==) No monitor specified for screen "Builtin Default ati Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default vesa Screen 0" (1) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default vesa Device 0" (==) No monitor specified for screen "Builtin Default vesa Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default fbdev Screen 0" (2) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default fbdev Device 0" (==) No monitor specified for screen "Builtin Default fbdev Screen 0". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/local/lib/X11/fonts/TTF/" does not exist. Entry deleted from font path. (WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist. Entry deleted from font path. (WW) The directory "/usr/local/lib/X11/fon
[ANNOUNCE] fixesproto 4.1
Adam Jackson (1): fixesproto 4.1 Alan Coopersmith (3): renamed: .cvsignore -> .gitignore Update XFixes protocol spec to match XFixes 4.0 Typo fixes in XFixes protocol spec Eric Anholt (1): Move fixes protocol description to the new canonical location/name. Julien Cristau (1): fixesproto: adjust to split xext headers Keith Packard (1): ChangeSaveSet with map=Unmap means 'unmap', not 'don't remap' Paulo Cesar Pereira de Andrade (1): Janitor: Correct make distcheck and dont distribute autogen.sh git tag: fixesproto-4.1 http://xorg.freedesktop.org/archive/individual/proto/fixesproto-4.1.tar.bz2 MD5: 157644edb3cd526f2cb164eb79c52bad fixesproto-4.1.tar.bz2 SHA1: 8b2e6009c629649556d45ef847d5b31591bb6f96 fixesproto-4.1.tar.bz2 http://xorg.freedesktop.org/archive/individual/proto/fixesproto-4.1.tar.gz MD5: c8dc868f8f23bb4b545e6b98aed375b4 fixesproto-4.1.tar.gz SHA1: cde450b04538c75c1b25acf329d0aa1887030a1e fixesproto-4.1.tar.gz - ajax signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: amd64 no screens
On Thu, 2009-07-23 at 08:01 -0400, PJ wrote: > Is it possible there is some problem with xorg 7.4 on FreeBSD 7.2 > running on an amd64 Turion portable. The error seems to be "no vga > module" "no screens found" no drivers available. > The default configuration shows the driver choses as "vesa" by ATI > technologies "Radeon Mobility X700 (PCIE)" > The dmesg.boot shows the driver as vga, generic. > I have read all the documentation I could find and it appears that this > particular configuration is not supported by FreeBSD...i.e. there is no > reference to Radeon or X700 in their hardware listing. But what about Xorg? > It is rather strange, but in my adventure in installing this stuff, at > one point I was getting something of a screen running but there seemed > to be a problem with a mouse or something like that... don't recall... > but it seemed to me that it should be possilbe to make this beastie work. > In my latest and greatest effort, I have installed everything from > sources, but the driver is forced to be a vesa driver by xorg when the > ordinary non-X screen boot-up indicates the driver as being vga... > somebody has got things rather crossed up? > What do we do now? > TIA > PJ That hardware should work fine. I expect that you didn't have the radeon (xf86-video-ati) driver installed when you made the configuration. robert. > -- > Hervé Kempf: "Pour sauver la planète, sortez du capitalisme." > - > Phil Jourdan --- p...@ptahhotep.com >http://www.ptahhotep.com >http://www.chiccantine.com/andypantry.php > > > ___ > xorg mailing list > xorg@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/xorg -- Robert Noland 2Hip Networks ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: amd64 no screens
PJ wrote: > Is it possible there is some problem with xorg 7.4 on FreeBSD 7.2 > running on an amd64 Turion portable. The error seems to be "no vga > module" "no screens found" no drivers available. > The default configuration shows the driver choses as "vesa" by ATI > technologies "Radeon Mobility X700 (PCIE)" > The dmesg.boot shows the driver as vga, generic. > I have read all the documentation I could find and it appears that this > particular configuration is not supported by FreeBSD...i.e. there is no > reference to Radeon or X700 in their hardware listing. But what about Xorg? > It is rather strange, but in my adventure in installing this stuff, at > one point I was getting something of a screen running but there seemed > to be a problem with a mouse or something like that... don't recall... > but it seemed to me that it should be possilbe to make this beastie work. > In my latest and greatest effort, I have installed everything from > sources, but the driver is forced to be a vesa driver by xorg when the > ordinary non-X screen boot-up indicates the driver as being vga... > somebody has got things rather crossed up? > What do we do now? > TIA > PJ > > That combination should work just fine. I've used a handful of radeon cards on FreeBSD/amd64. The driver that FreeBSD attaches to your video card (vga) is completely independent of Xorg and should have absolutely nothing to do with your problems. Without any /etc/X11/xorg.conf file, simply try starting X and show us the resulting log file that is generated. Adam ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: evdev+hal => Too many input devices.
Gabor Gombas wrote:
> Hi,
>
> On Wed, Jul 22, 2009 at 02:45:32PM -0700, Brian Rogers wrote:
>
>
>> @@ -118,14 +113,16 @@ static void del_conn(struct work_struct *work)
>> if (!device_is_registered(&conn->dev))
>> return;
>>
>> +/* wait for child devices to go away first */
>> while (1) {
>> struct device *dev;
>>
>> -dev = device_find_child(&conn->dev, NULL, __match_tty);
>> +dev = device_find_child(&conn->dev, NULL, __match_any);
>> if (!dev)
>> break;
>> -device_move(dev, NULL, DPM_ORDER_DEV_LAST);
>> put_device(dev);
>> +
>> +msleep(100);
>> }
>>
>> device_del(&conn->dev);
>>
>
> Won't this cause problems for rfcomm devices (again)? This code was added
> for the reason in the comment you've deleted: the rfcomm device can
> remain alive long after the connection is done, and it won't go away
> until you find & manually kill the process that holds the device open.
>
The device_move action looked obsolete to me since the comment lead me
to believe that device_move was moving the device to the root of /sys. I
saw the input devices, which weren't being touched there, wind up in the
root on their own when the connection was deleted so I assumed that had
since become automatic. But now that I look at the device_move function,
it looks like moving to null actually deletes the device.
In that case, it's probably best to just delete everything right there
and not wait for anything to close on its own. If that doesn't create
any problems, that's what I'll do. Thanks for bringing this up.
Brian
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
amd64 no screens
Is it possible there is some problem with xorg 7.4 on FreeBSD 7.2 running on an amd64 Turion portable. The error seems to be "no vga module" "no screens found" no drivers available. The default configuration shows the driver choses as "vesa" by ATI technologies "Radeon Mobility X700 (PCIE)" The dmesg.boot shows the driver as vga, generic. I have read all the documentation I could find and it appears that this particular configuration is not supported by FreeBSD...i.e. there is no reference to Radeon or X700 in their hardware listing. But what about Xorg? It is rather strange, but in my adventure in installing this stuff, at one point I was getting something of a screen running but there seemed to be a problem with a mouse or something like that... don't recall... but it seemed to me that it should be possilbe to make this beastie work. In my latest and greatest effort, I have installed everything from sources, but the driver is forced to be a vesa driver by xorg when the ordinary non-X screen boot-up indicates the driver as being vga... somebody has got things rather crossed up? What do we do now? TIA PJ -- Hervé Kempf: "Pour sauver la planète, sortez du capitalisme." - Phil Jourdan --- p...@ptahhotep.com http://www.ptahhotep.com http://www.chiccantine.com/andypantry.php ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Evdev touchscreen calibration?
Peter Hutterer wrote: > XI 1 gives you access to the valuators as well, so this should work in > principle if you register for DeviceButtonPress and friends. Ok, big sorry if I'm wrong, but to clarify: untranslated valuators are stored in valuators.data_raw, which is picked up solely by eventToRawEvent(), again used solely for Xi2 processing. So by inference Xi2 is the only option if you want raw coordinates (which are what evdev calibration needs). What am I missing? Cheers, Simon Disclaimer: I don't have an absolute device to test, nor do I fully grasp what's going on around GetPointerEvents(). But maybe it's worth looking at it again. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: GDM/Gnome confused about screen size
On Thu, Jul 23, 2009 at 09:14:33AM +0100, Alex Bennee wrote: > Since I finally got a working KMS build I have one final problem. GDM > gets confused about what the screen size actually is. Although there > is a display across the whole screen the menu bar and background image > take up the top 3/4 of the screen. > > When Gnome starts it's menubars are both shorter and the bottom menu > bar doesn't sit at the bottom of the physical screen. Interestingly if > I drag the menu bar lower it actually expands it's width to fill the > screen. I'm wondering if this is due to having my second monitor > plugged in (but turned off) to the VGA port. xrandr reports: Yes, GNOME is trying to make sure you can see both panels in both monitors. > 09:07 a...@danny/x86_64 [linux-2.6-stable.git] >xrandr > Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 4096 x 4096 > VGA1 connected 1440x900+0+0 (normal left inverted right x axis y axis) > 408mm x 255mm >1440x900 59.9*+ >1280x1024 75.0 >1024x768 75.1 70.1 60.0 >832x62474.6 >800x60072.2 75.0 60.3 56.2 >640x48072.8 75.0 66.7 60.0 >720x40070.1 > DVI1 connected 1680x1050+0+0 (normal left inverted right x axis y > axis) 459mm x 296mm >1680x1050 59.9*+ >1280x1024 75.0 >1152x864 75.0 >1024x768 75.1 70.1 60.0 >832x62474.6 >800x60072.2 75.0 60.3 56.2 >640x48072.8 75.0 66.7 60.0 >720x40070.1 Turn off VGA via the GNOME Display Preferences (or with xrandr -o VGA --off) and GNOME will reposition the panels to align with the larger remaining screen. > I'm willing to raise a bug but I'm not sure what it should be against. > Certainly both GDM and Gnome work fine when KMS is not enabled but is > it likely their bug or with the X side of things? How does Gnome > interrogate X to find out about these things? It either uses the RANDR or Xinerama extension to learn about the existence and position of various monitors. > Any ideas? Marius Gedminas -- As a rule of thumb, I reckon Python to be an order of magnitude more wasteful of CPU cycles and memory than my favourite low-level language, C++. -- Thomas Guest signature.asc Description: Digital signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: evdev+hal => Too many input devices.
On Thu, Jul 23, 2009 at 09:19:18AM +0200, Gabor Gombas wrote: > @@ -124,8 +119,18 @@ static void del_conn(struct work_struct *work) > dev = device_find_child(&conn->dev, NULL, __match_tty); That should be __match_any. Gabor -- - MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences - ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
GDM/Gnome confused about screen size
Hi, Since I finally got a working KMS build I have one final problem. GDM gets confused about what the screen size actually is. Although there is a display across the whole screen the menu bar and background image take up the top 3/4 of the screen. When Gnome starts it's menubars are both shorter and the bottom menu bar doesn't sit at the bottom of the physical screen. Interestingly if I drag the menu bar lower it actually expands it's width to fill the screen. I'm wondering if this is due to having my second monitor plugged in (but turned off) to the VGA port. xrandr reports: 09:07 a...@danny/x86_64 [linux-2.6-stable.git] >xrandr Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 4096 x 4096 VGA1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 408mm x 255mm 1440x900 59.9*+ 1280x1024 75.0 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 640x48072.8 75.0 66.7 60.0 720x40070.1 DVI1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 459mm x 296mm 1680x1050 59.9*+ 1280x1024 75.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 640x48072.8 75.0 66.7 60.0 720x40070.1 I'm willing to raise a bug but I'm not sure what it should be against. Certainly both GDM and Gnome work fine when KMS is not enabled but is it likely their bug or with the X side of things? How does Gnome interrogate X to find out about these things? Any ideas? -- Alex, homepage: http://www.bennee.com/~alex/ http://www.half-llama.co.uk ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Evdev touchscreen calibration?
2009/7/22 Florian Echtler :
> I've recently written an input event driver for a touchscreen, and it's
> working out-of-the box with the evdev driver. However, the scaling is a
> bit off, so I'd like to do a four-point calibration and set the "Evdev
> Axis Calibration" property accordingly. Is there a tool which does that?
> I've only found ts_calibrate so far, which is just for framebuffer
> devices.
I wrote some code a while back that should compute the calibration
parameters, and it's just running inside X (I'm attaching the code).
It doesn't actually set the parameters as that wasn't supported at the
time, but you should be able to do this in run-time these days.
Søren
/*
* Copyright © 2008 Soren Hauberg
*
* Permission to use, copy, modify, distribute, and sell this software
* and its documentation for any purpose is hereby granted without
* fee, provided that the above copyright notice appear in all copies
* and that both that copyright notice and this permission notice
* appear in supporting documentation, and that the name of Red Hat
* not be used in advertising or publicity pertaining to distribution
* of the software without specific, written prior permission. Red
* Hat makes no representations about the suitability of this software
* for any purpose. It is provided "as is" without express or implied
* warranty.
*
* THE AUTHORS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
* INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN
* NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY SPECIAL, INDIRECT OR
* CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
* OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
* NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
* CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*
* Authors:
* Soren Hauberg (haub...@gmail.com)
*/
/*
* This program performs calibration of a touchscreen that uses the 'usbtouchscreen'
* Linux kernel module. A calibration consists of finding the following parameters:
*
* 'flip_x'
* a boolean parameter that determines if the x-coordinate should be flipped.
*
* 'flip_y'
* same as 'flip_x' except for the y-coordinate.
*
* 'swap_xy'
* a boolean parameter that determines if the x and y-coordinates should
* be swapped.
*
* 'min_x', 'max_x', 'min_y', and 'max_y'
* the minimum and maximum x and y values that the screen can report. In principle
* we could get these parameters by letting the user press the corners of the
* screen. In practice this doesn't work, because the screen doesn't always have
* sensors at the corners. So, what we do is we ask the user to press points that
* have been pushed a bit closer to the center, and then we extrapolate the
* parameters.
*/
#include
#include
#include
#include
#include
/* Number of points the user should click */
const int num_points = 4;
/* Number of blocks. We partition we screen into 'num_blocks' x 'num_blocks'
* rectangles of equal size. We then ask the user to press points that are
* located at the corner closes to the center of the four blocks in the corners
* of the screen. The following ascii art illustrates the situation. We partition
* the screen into 8 blocks in each direction. We then let the user press the
* points marked with 'O'.
*
* +--+--+--+--+--+--+--+--+
* | | | | | | | | |
* +--O--+--+--+--+--+--O--+
* | | | | | | | | |
* +--+--+--+--+--+--+--+--+
* | | | | | | | | |
* +--+--+--+--+--+--+--+--+
* | | | | | | | | |
* +--+--+--+--+--+--+--+--+
* | | | | | | | | |
* +--+--+--+--+--+--+--+--+
* | | | | | | | | |
* +--+--+--+--+--+--+--+--+
* | | | | | | | | |
* +--O--+--+--+--+--+--O--+
* | | | | | | | | |
* +--+--+--+--+--+--+--+--+
*/
const int num_blocks = 8;
/* Names of the points */
enum {
UL = 0, /* Upper-left */
UR = 1, /* Upper-right */
LL = 2, /* Lower-left */
LR = 3 /* Lower-right */
};
/* Output ranges. The final output will be scaled to [0, range_x] x [0, range_y] */
const int range_x = 1023;
const int range_y = 1023;
/* The file to which the calibration parameters are saved. (XXX: is this distribution dependend?) */
const char *modprobe_conf_local = "/etc/modprobe.conf.local";
/* Prefix to the kernel path where we can set the parameters */
const char *module_prefix = "/sys/module/usbtouchscreen/parameters";
/* Names of kernel parameters */
const char *p_range_x = "range_x";
const char *p_range_y = "range_y";
const char *p_min_x = "min_x";
const char *p_min_y = "min_y";
const char *p_max_x = "max_x";
const char *p_max_y = "max_y";
const char *p_transform_xy = "transform_xy";
const char *p_flip_x = "flip_x";
const char *p_flip_y = "flip_y";
const char *p_swap_xy = "swap_xy";
/* Threshold to keep the same point from being clicked twice. Set to zero if you don't
* want this
Re: evdev+hal => Too many input devices.
Hi,
On Wed, Jul 22, 2009 at 02:45:32PM -0700, Brian Rogers wrote:
> @@ -118,14 +113,16 @@ static void del_conn(struct work_struct *work)
> if (!device_is_registered(&conn->dev))
> return;
>
> + /* wait for child devices to go away first */
> while (1) {
> struct device *dev;
>
> - dev = device_find_child(&conn->dev, NULL, __match_tty);
> + dev = device_find_child(&conn->dev, NULL, __match_any);
> if (!dev)
> break;
> - device_move(dev, NULL, DPM_ORDER_DEV_LAST);
> put_device(dev);
> +
> + msleep(100);
> }
>
> device_del(&conn->dev);
Won't this cause problems for rfcomm devices (again)? This code was added
for the reason in the comment you've deleted: the rfcomm device can
remain alive long after the connection is done, and it won't go away
until you find & manually kill the process that holds the device open.
How about this:
diff --git a/net/bluetooth/hci_sysfs.c b/net/bluetooth/hci_sysfs.c
index 95f7a7a..f709439 100644
--- a/net/bluetooth/hci_sysfs.c
+++ b/net/bluetooth/hci_sysfs.c
@@ -100,14 +100,9 @@ static void add_conn(struct work_struct *work)
hci_dev_hold(hdev);
}
-/*
- * The rfcomm tty device will possibly retain even when conn
- * is down, and sysfs doesn't support move zombie device,
- * so we should move the device before conn device is destroyed.
- */
-static int __match_tty(struct device *dev, void *data)
+static int __match_any(struct device *dev, void *data)
{
- return !strncmp(dev_name(dev), "rfcomm", 6);
+ return 1;
}
static void del_conn(struct work_struct *work)
@@ -124,8 +119,18 @@ static void del_conn(struct work_struct *work)
dev = device_find_child(&conn->dev, NULL, __match_tty);
if (!dev)
break;
- device_move(dev, NULL, DPM_ORDER_DEV_LAST);
+
+ /*
+* The rfcomm tty device will possibly retain even when conn
+* is down, and sysfs doesn't support move zombie device,
+* so we should move the device before conn device is destroyed.
+*/
+ if (!strncmp(dev_name(dev), "rfcomm", 6))
+ device_move(dev, NULL, DPM_ORDER_DEV_LAST);
+
put_device(dev);
+
+ msleep(100);
}
device_del(&conn->dev);
Gabor
--
-
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
-
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
