You are not logged in.

#126 2012-11-19 02:34:09

ArcRaven
Member
From: Germany
Registered: 2012-11-19
Posts: 2
Website

Re: Wayland on Arch Linux?

Hey guys,

just finished packaging work, please use and test it.
The xwayland-git package:
https://aur.archlinux.org/packages/xwayland-git/
And the xf86-video-intel-wayland-git package:
https://aur.archlinux.org/packages/xf86 … yland-git/

other drivers will follow soon (ATI, NVIDIA and wlshm).

Just have to test it on my own, if it's all working proberly.

cheers,

Michi

Offline

#127 2012-11-19 06:43:31

zAo
Member
Registered: 2012-11-01
Posts: 26

Re: Wayland on Arch Linux?

ArcRaven wrote:

Hey guys,

just finished packaging work, please use and test it.
The xwayland-git package:
https://aur.archlinux.org/packages/xwayland-git/
And the xf86-video-intel-wayland-git package:
https://aur.archlinux.org/packages/xf86 … yland-git/

other drivers will follow soon (ATI, NVIDIA and wlshm).

Just have to test it on my own, if it's all working proberly.

cheers,

Michi

Thanks, will try as soon as I can!

Offline

#128 2012-11-24 20:48:44

renegen
Member
Registered: 2010-09-08
Posts: 4

Re: Wayland on Arch Linux?

ArcRaven wrote:

Hey guys,

just finished packaging work, please use and test it.
The xwayland-git package:
https://aur.archlinux.org/packages/xwayland-git/
And the xf86-video-intel-wayland-git package:
https://aur.archlinux.org/packages/xf86 … yland-git/

other drivers will follow soon (ATI, NVIDIA and wlshm).

Just have to test it on my own, if it's all working proberly.

cheers,

Michi

Ok. I got the xwayland-xserver working stand-alone just now (on intel-graphics). Though, I needed to modify both of the pkgbuilds to make them compile and run:

The two respective lines containing "autogen" need to read "./autogen.sh --prefix=/usr".
The two respective lines containing "make install" need to read "make DESTDIR="$pkgdir/" install || return 1".

Also, after installation I had to manually set guid and suid on the Xorg executable file.

Now the next task'll be to get the xserver running inside weston. Don't know why it's not working yet....

Offline

#129 2012-11-24 21:02:19

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,092
Website

Re: Wayland on Arch Linux?

It's 2012. You don't need "|| return 1" after every line in a PKGBUILD.

Offline

#130 2012-11-24 21:02:45

Cdh
Member
Registered: 2009-02-03
Posts: 1,098

Re: Wayland on Arch Linux?

Last time I tried it I had to compile weston with

--enable-xwayland --with-xserver-path=/some/directory/xwayland/bin/X

and X really had to be not running when starting weston. But maybe that was a quirk back then.

edit: I tried to install xwayland alongside X. I had a little fight with the PKGBUILDS but then I got it together...

So this is
xwayland-git
xf86-video-intel-xwayland-git

And in weston-git I simply changed the autogen.sh arguments:

        ./autogen.sh --prefix=/usr --libexecdir=/usr/lib/weston --enable-xwayland --with-xserver-path=/opt/xwayland/bin/Xorg

So I can actually start xwayland with sudo /opt/xwayland/bin/Xorg (or /opt/xwayland/bin/Xorg :1 when my normal X is running).

But weston does not accept "--xserver" anymore. And of course weston-launch doesn't accept "-- --xserver"
It say here that this is the way you should do it: http://wayland.freedesktop.org/xserver.html
But I only get "fatal: unhandled option: --xserver" if I try to start weston with it. DISPLAY is not set automatically and xwayland is not starting automatically...

edit2: The one thing they really need to fix is getting stuck on either starting or exiting wayland/weston. Still: weston-launch from X, then sudo pkill weston. You are now stuck and need to use sysrq or ssh.

Last edited by Cdh (2012-11-24 23:46:00)


฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz

Offline

#131 2012-11-25 12:53:50

renegen
Member
Registered: 2010-09-08
Posts: 4

Re: Wayland on Arch Linux?

Cdh wrote:

...
But weston does not accept "--xserver" anymore. And of course weston-launch doesn't accept "-- --xserver"

Ok thanks for the pkgbuilds. Gonna try them later. Have you been able to actually run X-apps inside weston with older versions?

About the "--xserver" argument, it seems to be deprecated. The new syntax is described in the manpage for weston. IIRC it's now "weston-launch -- --modules=xwayland.so".
Having said that I didn't succeed in actually running any X-apps inside Weston. It seems the x-server weston tries to spawn just hangs, whether weston is running from tty or inside Xorg (and weston also becomes unresponsive, have to use sysrq-keys to recover).

Cdh wrote:

edit2: The one thing they really need to fix is getting stuck on either starting or exiting wayland/weston. Still: weston-launch from X, then sudo pkill weston. You are now stuck and need to use sysrq or ssh.

Ok, I had some luck in closing down Weston by simply not killing all the weston-processes at once. Instead do a "pgrep weston" and then kill the second PID in that list. See if that works....



Edit: Here's the Xorg-logfile of the rootless X-server that Weston tries to spawn but hangs. When it hangs, the Weston mouse cursor disappears and the screen is frozen until I press Alt-SysRq-I. Compared to a normal Xorg.0.log from my computer I can see that this one ends in the middle of the video-card's initialization. Maybe some wizard can tell if something's wrong or missing here....

[ 10010.678] 
X.Org X Server 1.13.0
Release Date: 2012-09-05
[ 10010.678] X Protocol Version 11, Revision 0
[ 10010.678] Build Operating System: Linux 3.6.6-1-ARCH x86_64 
[ 10010.679] Current Operating System: Linux mini 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64
[ 10010.679] Kernel command line: root=/dev/sda10 init=/bin/systemd rootfstype=ext4 rootflags=strictatime,rw rw
[ 10010.679] Build Date: 24 November 2012  08:32:56PM
[ 10010.679]  
[ 10010.679] Current version of pixman: 0.28.0
[ 10010.679] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[ 10010.679] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 10010.680] (==) Log file: "/usr/var/log/Xorg.1.log", Time: Sun Nov 25 14:31:03 2012
[ 10010.680] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 10010.680] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 10010.707] (==) No Layout section.  Using the first Screen section.
[ 10010.707] (==) No screen section available. Using defaults.
[ 10010.708] (**) |-->Screen "Default Screen Section" (0)
[ 10010.708] (**) |   |-->Monitor "<default monitor>"
[ 10010.708] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[ 10010.708] (==) Not automatically adding devices
[ 10010.708] (==) Not automatically enabling devices
[ 10010.708] (==) Automatically adding GPU devices
[ 10010.708] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 10010.708] 	Entry deleted from font path.
[ 10010.708] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 10010.708] 	Entry deleted from font path.
[ 10010.708] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 10010.708] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 10010.708] 	Entry deleted from font path.
[ 10010.709] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 10010.709] (==) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/Type1/
[ 10010.709] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 10010.709] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 10010.709] (II) Loader magic: 0x7fac40
[ 10010.709] (II) Module ABI versions:
[ 10010.709] 	X.Org ANSI C Emulation: 0.4
[ 10010.709] 	X.Org Video Driver: 13.0
[ 10010.709] 	X.Org XInput driver : 18.0
[ 10010.709] 	X.Org Server Extension : 7.0
[ 10010.711] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 10010.711] setversion 1.4 failed
[ 10010.713] (--) PCI:*(0:0:2:0) 8086:a011:1043:83ac rev 0, Mem @ 0xf7e00000/524288, 0xd0000000/268435456, 0xf7d00000/1048576, I/O @ 0x0000dc00/8
[ 10010.713] (--) PCI: (0:0:2:1) 8086:a012:1043:83ac rev 0, Mem @ 0xf7e80000/524288
[ 10010.713] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 10010.713] Initializing built-in extension Generic Event Extension
[ 10010.713] Initializing built-in extension SHAPE
[ 10010.713] Initializing built-in extension MIT-SHM
[ 10010.714] Initializing built-in extension XInputExtension
[ 10010.714] Initializing built-in extension XTEST
[ 10010.714] Initializing built-in extension BIG-REQUESTS
[ 10010.714] Initializing built-in extension SYNC
[ 10010.714] Initializing built-in extension XKEYBOARD
[ 10010.714] Initializing built-in extension XC-MISC
[ 10010.714] Initializing built-in extension XINERAMA
[ 10010.714] Initializing built-in extension XFIXES
[ 10010.714] Initializing built-in extension RENDER
[ 10010.714] Initializing built-in extension RANDR
[ 10010.714] Initializing built-in extension COMPOSITE
[ 10010.714] Initializing built-in extension DAMAGE
[ 10010.714] Initializing built-in extension MIT-SCREEN-SAVER
[ 10010.714] Initializing built-in extension DOUBLE-BUFFER
[ 10010.714] Initializing built-in extension RECORD
[ 10010.714] Initializing built-in extension DPMS
[ 10010.714] Initializing built-in extension X-Resource
[ 10010.714] Initializing built-in extension XVideo
[ 10010.714] Initializing built-in extension XVideo-MotionCompensation
[ 10010.715] Initializing built-in extension XFree86-VidModeExtension
[ 10010.715] Initializing built-in extension XFree86-DGA
[ 10010.715] Initializing built-in extension XFree86-DRI
[ 10010.715] Initializing built-in extension DRI2
[ 10010.715] (II) LoadModule: "glx"
[ 10010.716] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 10010.716] (EE) Failed to load /usr/lib/xorg/modules/extensions/libglx.so: /usr/lib/xorg/modules/extensions/libglx.so: cannot open shared object file: No such file or directory
[ 10010.716] (II) UnloadModule: "glx"
[ 10010.716] (II) Unloading glx
[ 10010.716] (EE) Failed to load module "glx" (loader failed, 7)
[ 10010.716] (II) LoadModule: "xwayland"
[ 10010.716] (II) Loading /usr/lib/xorg/modules/extensions/libxwayland.so
[ 10010.727] (II) Module xwayland: vendor="X.Org Foundation"
[ 10010.727] 	compiled for 1.13.0, module version = 1.0.0
[ 10010.727] 	ABI class: X.Org Server Extension, version 7.0
[ 10010.727] (==) Matched intel as autoconfigured driver 0
[ 10010.727] (==) Matched vesa as autoconfigured driver 1
[ 10010.727] (==) Matched modesetting as autoconfigured driver 2
[ 10010.727] (==) Matched wlshm as autoconfigured driver 3
[ 10010.727] (==) Matched fbdev as autoconfigured driver 4
[ 10010.727] (==) Assigned the driver to the xf86ConfigLayout
[ 10010.728] (II) LoadModule: "intel"
[ 10010.728] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 10010.737] (II) Module intel: vendor="X.Org Foundation"
[ 10010.737] 	compiled for 1.13.0, module version = 2.20.8
[ 10010.738] 	Module class: X.Org Video Driver
[ 10010.738] 	ABI class: X.Org Video Driver, version 13.0
[ 10010.738] (II) LoadModule: "vesa"
[ 10010.738] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 10010.753] (II) Module vesa: vendor="X.Org Foundation"
[ 10010.753] 	compiled for 1.13.0, module version = 2.3.2
[ 10010.753] 	Module class: X.Org Video Driver
[ 10010.753] 	ABI class: X.Org Video Driver, version 13.0
[ 10010.753] (II) LoadModule: "modesetting"
[ 10010.755] (WW) Warning, couldn't open module modesetting
[ 10010.755] (II) UnloadModule: "modesetting"
[ 10010.755] (II) Unloading modesetting
[ 10010.755] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 10010.755] (II) LoadModule: "wlshm"
[ 10010.756] (WW) Warning, couldn't open module wlshm
[ 10010.756] (II) UnloadModule: "wlshm"
[ 10010.756] (II) Unloading wlshm
[ 10010.756] (EE) Failed to load module "wlshm" (module does not exist, 0)
[ 10010.756] (II) LoadModule: "fbdev"
[ 10010.757] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 10010.768] (II) Module fbdev: vendor="X.Org Foundation"
[ 10010.768] 	compiled for 1.13.0, module version = 0.4.3
[ 10010.768] 	Module class: X.Org Video Driver
[ 10010.768] 	ABI class: X.Org Video Driver, version 13.0
[ 10010.768] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
	i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
	E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
	965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
	4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
	Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
	Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
	Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
	Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
	Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
	Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
	Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
	Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
	Haswell Server (GT2+), Haswell SDV Desktop (GT1),
	Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
	Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
	Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
	Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
	Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
	Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
	Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
	Haswell ULT Server (GT1), Haswell ULT Server (GT2),
	Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
	Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
	Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
	Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
	Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
	ValleyView PO board
[ 10010.771] (II) VESA: driver for VESA chipsets: vesa
[ 10010.771] flags 1, deleting
[ 10010.771] (II) UnloadModule: "vesa"
[ 10010.771] (II) Unloading vesa
[ 10010.771] (II) FBDEV: driver for framebuffer: fbdev
[ 10010.771] flags 0, deleting
[ 10010.771] (II) UnloadModule: "fbdev"
[ 10010.771] (II) Unloading fbdev
[ 10010.848] (II) intel(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[ 10010.848] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 10010.848] (==) intel(0): RGB weight 888
[ 10010.848] (==) intel(0): Default visual is TrueColor
[ 10010.848] (--) intel(0): Integrated Graphics Chipset: Intel(R) Pineview GM

Last edited by renegen (2012-11-25 13:49:45)

Offline

#132 2012-11-25 14:28:34

Cdh
Member
Registered: 2009-02-03
Posts: 1,098

Re: Wayland on Arch Linux?

renegen wrote:

Ok thanks for the pkgbuilds. Gonna try them later. Have you been able to actually run X-apps inside weston with older versions?

Yes.
A while ago I tried a browser. It was a bit buggy but it worked. I also tried xonotic and the mouse capture didn't quite work but opengl worked flawlessly.

renegen wrote:

About the "--xserver" argument, it seems to be deprecated. The new syntax is described in the manpage for weston. IIRC it's now "weston-launch -- --modules=xwayland.so".

Thanks!

renegen wrote:

Having said that I didn't succeed in actually running any X-apps inside Weston. It seems the x-server weston tries to spawn just hangs, whether weston is running from tty or inside Xorg (and weston also becomes unresponsive, have to use sysrq-keys to recover).

Well, mine doesn't start, no screens found. Possibly because it uses /etc/X11/xorg.conf.d/? And why is there a file not found error for the drm device?

[   106.498] 
X.Org X Server 1.13.0
Release Date: 2012-09-05
[   106.498] X Protocol Version 11, Revision 0
[   106.498] Build Operating System: Linux 3.7.0-1-mainline x86_64 
[   106.498] Current Operating System: Linux chrisl 3.7.0-1-mainline #1 SMP PREEMPT Sun Nov 18 18:01:27 CET 2012 x86_64
[   106.498] Kernel command line: root=/dev/disk/by-uuid/650b9f2f-d077-48e9-9fc2-7b6f2294599a ro init=/bin/systemd quiet radeon.pcie_gen2=1 initrd=../initramfs-linux-mainline.img 3 BOOT_IMAGE=../vmlinuz-linux-mainline 
[   106.498] Build Date: 25 November 2012  12:22:01AM
[   106.498]  
[   106.498] Current version of pixman: 0.28.0
[   106.499] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   106.499] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   106.499] (==) Log file: "/opt/xwayland/var/log/Xorg.0.log", Time: Sun Nov 25 15:19:32 2012
[   106.499] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   106.499] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   106.499] (==) No Layout section.  Using the first Screen section.
[   106.499] (==) No screen section available. Using defaults.
[   106.499] (**) |-->Screen "Default Screen Section" (0)
[   106.499] (**) |   |-->Monitor "<default monitor>"
[   106.499] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[   106.500] (**) |   |-->Device "Intel Graphics"
[   106.500] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   106.500] (==) Not automatically adding devices
[   106.500] (==) Not automatically enabling devices
[   106.500] (==) Automatically adding GPU devices
[   106.500] (==) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/OTF/,
	/usr/share/fonts/Type1/,
	/usr/share/fonts/100dpi/,
	/usr/share/fonts/75dpi/
[   106.500] (==) ModulePath set to "/opt/xwayland/lib/xorg/modules"
[   106.500] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   106.500] (II) Loader magic: 0x7f8c40
[   106.500] (II) Module ABI versions:
[   106.500] 	X.Org ANSI C Emulation: 0.4
[   106.500] 	X.Org Video Driver: 13.0
[   106.500] 	X.Org XInput driver : 18.0
[   106.500] 	X.Org Server Extension : 7.0
[   106.501] (II) config/udev: Adding drm device (/dev/dri/card0)
[   106.501] (II) config/udev: Adding drm device (/dev/dri/card1)
[   106.501] setversion 1.4 failed
[   106.502] (--) PCI:*(0:0:2:0) 8086:0166:1558:7102 rev 9, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[   106.503] (--) PCI: (0:1:0:0) 1002:6800:1558:7102 rev 0, Mem @ 0xe0000000/268435456, 0xf7b00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072
[   106.503] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   106.503] Initializing built-in extension Generic Event Extension
[   106.503] Initializing built-in extension SHAPE
[   106.503] Initializing built-in extension MIT-SHM
[   106.503] Initializing built-in extension XInputExtension
[   106.503] Initializing built-in extension XTEST
[   106.503] Initializing built-in extension BIG-REQUESTS
[   106.503] Initializing built-in extension SYNC
[   106.503] Initializing built-in extension XKEYBOARD
[   106.503] Initializing built-in extension XC-MISC
[   106.503] Initializing built-in extension XINERAMA
[   106.503] Initializing built-in extension XFIXES
[   106.503] Initializing built-in extension RENDER
[   106.503] Initializing built-in extension RANDR
[   106.503] Initializing built-in extension COMPOSITE
[   106.503] Initializing built-in extension DAMAGE
[   106.503] Initializing built-in extension MIT-SCREEN-SAVER
[   106.503] Initializing built-in extension DOUBLE-BUFFER
[   106.503] Initializing built-in extension RECORD
[   106.503] Initializing built-in extension DPMS
[   106.503] Initializing built-in extension X-Resource
[   106.503] Initializing built-in extension XVideo
[   106.503] Initializing built-in extension XVideo-MotionCompensation
[   106.503] Initializing built-in extension XFree86-VidModeExtension
[   106.503] Initializing built-in extension XFree86-DGA
[   106.503] Initializing built-in extension XFree86-DRI
[   106.503] Initializing built-in extension DRI2
[   106.503] (II) "glx" will be loaded by default.
[   106.503] (II) "xwayland" will be loaded by default.
[   106.503] (II) LoadModule: "dri2"
[   106.504] (II) Module "dri2" already built-in
[   106.504] (II) LoadModule: "glamoregl"
[   106.504] (WW) Warning, couldn't open module glamoregl
[   106.504] (II) UnloadModule: "glamoregl"
[   106.504] (II) Unloading glamoregl
[   106.504] (EE) Failed to load module "glamoregl" (module does not exist, 0)
[   106.504] (II) LoadModule: "glx"
[   106.504] (II) Loading /opt/xwayland/lib/xorg/modules/extensions/libglx.so
[   106.504] (II) Module glx: vendor="X.Org Foundation"
[   106.504] 	compiled for 1.13.0, module version = 1.0.0
[   106.504] 	ABI class: X.Org Server Extension, version 7.0
[   106.504] (==) AIGLX enabled
[   106.504] Loading extension GLX
[   106.504] (II) LoadModule: "xwayland"
[   106.505] (II) Loading /opt/xwayland/lib/xorg/modules/extensions/libxwayland.so
[   106.505] (II) Module xwayland: vendor="X.Org Foundation"
[   106.505] 	compiled for 1.13.0, module version = 1.0.0
[   106.505] 	ABI class: X.Org Server Extension, version 7.0
[   106.505] (II) LoadModule: "intel"
[   106.505] (II) Loading /opt/xwayland/lib/xorg/modules/drivers/intel_drv.so
[   106.505] (II) Module intel: vendor="X.Org Foundation"
[   106.505] 	compiled for 1.13.0, module version = 2.20.8
[   106.505] 	Module class: X.Org Video Driver
[   106.505] 	ABI class: X.Org Video Driver, version 13.0
[   106.505] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
	i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
	E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
	965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
	4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
	Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
	Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
	Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
	Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
	Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
	Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
	Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
	Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
	Haswell Server (GT2+), Haswell SDV Desktop (GT1),
	Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
	Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
	Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
	Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
	Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
	Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
	Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
	Haswell ULT Server (GT1), Haswell ULT Server (GT2),
	Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
	Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
	Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
	Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
	Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
	ValleyView PO board
[   106.561] (II) intel(0): SNA compiled from 2.20.8-18-g860e27c
[   106.561] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[   106.615] (EE) intel(0): [drm] Failed to open DRM device for pci:0000:00:02.0: No such file or directory
[   106.615] (EE) intel(0): Failed to become DRM master.
[   106.616] (II) UnloadModule: "intel"
[   106.616] (EE) Screen(s) found, but none have a usable configuration.
[   106.616] 
Fatal server error:
[   106.616] no screens found
[   106.616] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[   106.616] (EE) Please also check the log file at "/opt/xwayland/var/log/Xorg.0.log" for additional information.
[   106.616] (EE) 
[   106.616] Server terminated with error (1). Closing log file.

Last edited by Cdh (2012-11-25 14:29:53)


฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz

Offline

#133 2012-11-25 16:36:54

renegen
Member
Registered: 2010-09-08
Posts: 4

Re: Wayland on Arch Linux?

Cdh wrote:

Well, mine doesn't start, no screens found. Possibly because it uses /etc/X11/xorg.conf.d/? And why is there a file not found error for the drm device?

Looks like we are both having hiccups in our video-card drivers or something. Maybe in a few weeks the code will be in better shape.
The "no screens" message is something Xorg says when no functioning X video-driver can be found (i.e).

Offline

#134 2013-01-13 12:14:35

Cdh
Member
Registered: 2009-02-03
Posts: 1,098

Re: Wayland on Arch Linux?

xwayland in weston inside X works now.

taDIwOA

Trying to use opengl in xwayland in weston in X segfaults the xwayland Xserver.

Trying to use xwayland at all in weston on a tty segfaults the xwayland Xserver with intel.

So it's probably a driver issue… still!

edit: Great. When compiling xwayland and xf86-video-intel with -O0 -g3, then xwayland doesn't segfault when starting glxgears in xwayland in weston in X. Instead weston completely hangs.

Last edited by Cdh (2013-01-13 12:32:28)


฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz

Offline

#135 2013-01-14 22:06:27

blackout23
Member
Registered: 2011-11-16
Posts: 780

Re: Wayland on Arch Linux?

Displayserverception!

Offline

#136 2013-02-21 06:16:07

Berseker
Member
From: Near Lecco, Italy
Registered: 2008-04-24
Posts: 252

Re: Wayland on Arch Linux?

i wanted to try weston this way

 weston-launch --tty /dev/tty2

but I got the following error

 weston-desktop-shell: undefined symbol: cairo_egl_device_create

 
nothing on google about that.. any thoughts? I'm using mesa-git repo with an ATI 4250

$ yaourt -Qs | grep mesa-git
mesa-git/ati-dri-git 20130219-1
mesa-git/glamor 0.5-3
mesa-git/khrplatform-devel-git 20130219-1
mesa-git/libegl-git 20130219-1
mesa-git/libgbm-git 20130219-1
mesa-git/libgl-git 20130219-1
mesa-git/libglapi-git 20130219-1
mesa-git/libgles-git 20130219-1
mesa-git/mesa-git 20130219-1
mesa-git/osmesa-git 20130219-1
mesa-git/xf86-video-ati-git 20130128-1 (xorg-drivers xorg)

Offline

#137 2013-02-21 06:34:54

progandy
Member
Registered: 2012-05-17
Posts: 2,143

Re: Wayland on Arch Linux?

You need cairo from testing with libegl support. (or build it from git)

PS: weston works using only packages from testing and community-testing, mesa-git is not required.

Offline

#138 2013-02-21 18:56:35

Berseker
Member
From: Near Lecco, Italy
Registered: 2008-04-24
Posts: 252

Re: Wayland on Arch Linux?

i have testing and community-testing activated - cairo from testing is egl enabled, that doesn't seem to be the reason of the problem

Offline

#139 2013-02-24 14:40:30

shved
Member
Registered: 2012-12-11
Posts: 29

Re: Wayland on Arch Linux?

I have a big bang in my mind when I run weston-launch and shader compilator produced me that:

[18:23:14.957] shader info: 0:5(10): error: main() must return void
0:9(1): error: function `main' has non-void return type void, but no return statement

[18:23:14.963] shader info: 0:5(10): error: main() must return void
0:8(2): error: function `main' has non-void return type void, but no return statement

Before installing wayland I instaled mesa 9.1-1.
My video rtiver is xf86-video-intel 2.21.3-1
and intel-dri 9.0.2-1
maybe I have to install testing intel driver too?


Sorry for my english

Offline

#140 2013-02-24 18:28:54

D4ve
Member
Registered: 2012-08-02
Posts: 209

Re: Wayland on Arch Linux?

Berseker wrote:

but I got the following error

 weston-desktop-shell: undefined symbol: cairo_egl_device_create

Try to use cairo from testing, solved my problems.

EDIT: Ups, overlooked your other posts. Sorry.

Last edited by D4ve (2013-02-24 18:31:25)

Offline

#141 2013-02-25 18:50:41

D4ve
Member
Registered: 2012-08-02
Posts: 209

Re: Wayland on Arch Linux?

Question: Did anyone manage to start weston fullscreen without the need of X?

Every time i try this (with weston-launch), the screen freezes (can't even switch to another VT) and i must reset my pc.

Offline

#142 2013-02-25 20:22:31

shved
Member
Registered: 2012-12-11
Posts: 29

Re: Wayland on Arch Linux?

D4ve wrote:

Question: Did anyone manage to start weston fullscreen without the need of X?

Every time i try this (with weston-launch), the screen freezes (can't even switch to another VT) and i must reset my pc.

I had some problems like with some time ago. I don't know a solution, but you need to dig under the dri. I think, you have an Nvidia card?  Drivers from Nvidia has some problems with dri, try to use nouveau instead.

Last edited by shved (2013-02-25 20:23:05)


Sorry for my english

Offline

#143 2013-02-26 00:02:04

D4ve
Member
Registered: 2012-08-02
Posts: 209

Re: Wayland on Arch Linux?

shved wrote:

I had some problems like with some time ago. I don't know a solution, but you need to dig under the dri. I think, you have an Nvidia card?  Drivers from Nvidia has some problems with dri, try to use nouveau instead.

No, it's not an Nvidia card, just an AMD Fusion APU with integrated graphic (really slow and not for gaming, but enough for gnome-shell)

As far as i know weston requires KMS and the proprietary Nvidia driver does not have this feature, so it should be impossible to use weston with an proprietar Nvidia driver, right?

I'll try to get somehow an errorlog, maybe i will know more later.

EDIT: No matter what I try, I simply get no error-logs.

Last edited by D4ve (2013-02-26 16:07:45)

Offline

#144 2013-02-26 18:34:02

Berseker
Member
From: Near Lecco, Italy
Registered: 2008-04-24
Posts: 252

Re: Wayland on Arch Linux?

D4ve wrote:
Berseker wrote:

but I got the following error

 weston-desktop-shell: undefined symbol: cairo_egl_device_create

Try to use cairo from testing, solved my problems.

EDIT: Ups, overlooked your other posts. Sorry.

no you were actually right, I think I had some cairo-git compiled by me. My bad. Now Wayland \ Weston starts, it look soooooo smooth but saldy now basically anything works.. sad

Offline

#145 2013-02-26 19:05:34

drcouzelis
Member
From: Connecticut, USA
Registered: 2009-11-09
Posts: 3,404
Website

Re: Wayland on Arch Linux?

Berseker wrote:

Now Wayland \ Weston starts, it look soooooo smooth but saldy now basically anything works..

It looks smooth? I was wondering about that. Is there a noticeable difference between Wayland and X11? How about Wayland and X compositing?

I'm getting more and more excited to try it. big_smile

Online

#146 2013-02-26 19:24:52

Berseker
Member
From: Near Lecco, Italy
Registered: 2008-04-24
Posts: 252

Re: Wayland on Arch Linux?

It is simply noticeable, it is hard to describe it by words.
I am sure that a modern "graphic manager" is needed by modern linux desktops, X11 is too complex and built on ancient basis to be competititive on actual modern desktop needs in my opinion.

I didn't manage to try something like Xwayland or anything yet, I need time to get more informations about those!

Offline

#147 2013-02-26 21:19:01

D4ve
Member
Registered: 2012-08-02
Posts: 209

Re: Wayland on Arch Linux?

drcouzelis wrote:
Berseker wrote:

Now Wayland \ Weston starts, it look soooooo smooth...

It looks smooth? I was wondering about that. Is there a noticeable difference between Wayland and X11?

I'm getting more and more excited to try it. big_smile

For me it looks smooth too (better than X11). It's hard to describe, you should try it smile

Would be cool to modify the default shell to add server side decorations to have a toolkit-independent, basic desktop.

Offline

#148 2013-02-27 15:28:38

D4ve
Member
Registered: 2012-08-02
Posts: 209

Re: Wayland on Arch Linux?

Hey, did anyone try to use the tablet-shell (replacing the default desktop-shell) in weston?

I tried it a few times, but it always fails. The desktop never changes nor the behaviour of programs i launch (As far as i understand, tablet-shell has no normal windows, only maximized, fullscreen apps)

Seems like the weston-package from community-testing is a little "broken" or not created in the way i expect it.

Btw: Does anyone know a "how to get into weston-shell-hacking"? I want to play a little bit with the default shell, add a few features (if i can) but i need a place to start (i have really no idea).

Offline

#149 2013-03-03 11:53:04

Unia
Member
From: The Netherlands
Registered: 2010-03-30
Posts: 2,469
Website

Re: Wayland on Arch Linux?

Hey guys,

Since Wayland is installed by default now and I just switched to xf86-video-ati (thus gaining KMS support) I decided to give Weston a try.

However, it won't run:

┌─[jente @ lappy ~] 12:47:03 
└─■ weston-launch
Date: 2013-03-03 CET
[12:48:04.064] weston 1.0.5
               http://wayland.freedesktop.org/
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.0.5
               Build:  
[12:48:04.064] OS: Linux, 3.8.1-1-ARCH, #1 SMP PREEMPT Thu Feb 28 18:23:03 CET 2013, x86_64
[12:48:04.082] Loading module '/usr/lib/weston/drm-backend.so'
[12:48:04.084] initializing drm backend
[12:48:04.186] couldn't open /dev/dri/card0, skipping
[12:48:04.186] failed to initialize egl
[12:48:04.191] fatal: failed to create compositor

I did export EGL_DRIVER just to be sure, but still no dice. When I run it as root, my whole system hangs and I have to hold the power button to restart. Do you know what's wrong?


If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

Offline

#150 2013-03-03 11:57:37

Giselher
Member
From: Austria
Registered: 2010-02-02
Posts: 150
Website

Re: Wayland on Arch Linux?

Unia wrote:

Hey guys,

Since Wayland is installed by default now and I just switched to xf86-video-ati (thus gaining KMS support) I decided to give Weston a try.

However, it won't run:

┌─[jente @ lappy ~] 12:47:03 
└─■ weston-launch
Date: 2013-03-03 CET
[12:48:04.064] weston 1.0.5
               http://wayland.freedesktop.org/
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.0.5
               Build:  
[12:48:04.064] OS: Linux, 3.8.1-1-ARCH, #1 SMP PREEMPT Thu Feb 28 18:23:03 CET 2013, x86_64
[12:48:04.082] Loading module '/usr/lib/weston/drm-backend.so'
[12:48:04.084] initializing drm backend
[12:48:04.186] couldn't open /dev/dri/card0, skipping
[12:48:04.186] failed to initialize egl
[12:48:04.191] fatal: failed to create compositor

I did export EGL_DRIVER just to be sure, but still no dice. When I run it as root, my whole system hangs and I have to hold the power button to restart. Do you know what's wrong?


Did you try the steps described on the website?

For KMS/DRM output weston needs root permissions. You can accomplish this by making weston SUID root (sudo chown root weston; sudo chmod +s weston) or, with weston master, using weston-launch, which also requires SUID root, only works outside of X, and requires that you enable systemd session support for weston-launch (how?) or add yourself to the "weston-launch" group:

    $ sudo groupadd weston-launch
    $ sudo usermod -a -G weston-launch $USER
    $ # Log all the way out (of X, etc.)
    $ sudo chown root weston-launch
    $ sudo chmod +s weston-launch
    $ weston-launch

Offline

Board footer

Powered by FluxBB