Re: Gnome 3 (gnome-shell) crash on initialization on an x61s with Intel 965 x3100 display
I may need to start following current. I'm seeing a theme in development where mesa has to be replaced and patched to address various problems... I wanted to fire up gnome3 so I can try using google drive as a filesystem. I may put this on hold and try it later. I'm pretty thrilled with the new WindowMaker.. On Fri, Jul 29, 2016 at 3:29 AM, Justin Haynes wrote: > I consolidated /usr/local onto /usr becuase of a sizing issue. Actually, > in liu of resizing, I moved files, deleted slices and then created a larger > /usr and smaller /home to accomodate more programs. So I just checked and > /usr doesn't have suid: > > ff18b54934f6a0f8.f /usr ffs rw,nodev 1 2 > > And speaking of permissions, I did check /etc/fbtab to amd made sure > /dev/drm0 was being owned by me so that drm would work in X: > > /dev/ttyC0 0600 > > /dev/console:/dev/wskbd:/dev/wskbd0:/dev/wsmouse:/dev/wsmouse0:/dev/ttyCcfg:/dev/drm0:/dev/drm1:/dev/drm2:/dev/drm3 > > and i confirmed with glxgears and other programs that demand 3d graphics > as well. During on one of my previous tests, I must not have started from > the first virtual terminal, so I was getting permissions errors on drm, and > graphics were running very slowly. This was why. > > -Justin > > On Fri, Jul 29, 2016 at 2:25 AM, David Dahlberg < > david.dahlb...@fkie.fraunhofer.de> wrote: > >> Am Freitag, den 29.07.2016, 00:26 -0500 schrieb Justin Haynes: >> >> > The problem is that when i attempt ot start Gnome using gdm, I get >> > nothing >> > but X Windows with a black background and the X mouse cursor. >> >> Had a similar problem lately. >> >> Please check fstab(5), whether you have nosuid configured to /usr/local. >> Seems something changed recently, such that slock, gnome-settings-daemon >> and (gnome|gdm)-session-something need suid. > > >
Re: Gnome 3 (gnome-shell) crash on initialization on an x61s with Intel 965 x3100 display
I consolidated /usr/local onto /usr becuase of a sizing issue. Actually, in liu of resizing, I moved files, deleted slices and then created a larger /usr and smaller /home to accomodate more programs. So I just checked and /usr doesn't have suid: ff18b54934f6a0f8.f /usr ffs rw,nodev 1 2 And speaking of permissions, I did check /etc/fbtab to amd made sure /dev/drm0 was being owned by me so that drm would work in X: /dev/ttyC0 0600 /dev/console:/dev/wskbd:/dev/wskbd0:/dev/wsmouse:/dev/wsmouse0:/dev/ttyCcfg:/dev/drm0:/dev/drm1:/dev/drm2:/dev/drm3 and i confirmed with glxgears and other programs that demand 3d graphics as well. During on one of my previous tests, I must not have started from the first virtual terminal, so I was getting permissions errors on drm, and graphics were running very slowly. This was why. -Justin On Fri, Jul 29, 2016 at 2:25 AM, David Dahlberg < david.dahlb...@fkie.fraunhofer.de> wrote: > Am Freitag, den 29.07.2016, 00:26 -0500 schrieb Justin Haynes: > > > The problem is that when i attempt ot start Gnome using gdm, I get > > nothing > > but X Windows with a black background and the X mouse cursor. > > Had a similar problem lately. > > Please check fstab(5), whether you have nosuid configured to /usr/local. > Seems something changed recently, such that slock, gnome-settings-daemon > and (gnome|gdm)-session-something need suid.
Re: Gnome 3 (gnome-shell) crash on initialization on an x61s with Intel 965 x3100 display
Am Freitag, den 29.07.2016, 00:26 -0500 schrieb Justin Haynes: > The problem is that when i attempt ot start Gnome using gdm, I get > nothing > but X Windows with a black background and the X mouse cursor. Had a similar problem lately. Please check fstab(5), whether you have nosuid configured to /usr/local. Seems something changed recently, such that slock, gnome-settings-daemon and (gnome|gdm)-session-something need suid.
Re: Gnome 3 (gnome-shell) crash on initialization on an x61s with Intel 965 x3100 display
Actually, this looks like it might be the problem: https://marc.info/?l=openbsd-bugs&m=145071127402451&w=2 It is late here, so i will quit for now, but Antoine, to answer your question, yes i did do the steps from pkg-readmes/gnome-* To start GDM, I simply let rc do it: $ cat /etc/rc.conf.local apmd_flags="-A" ## enables suspend and power mgmt hotplugd_flags="" ## needed to start hotplugd for toad multicast=YES pkg_scripts=${pkg_scripts} messagebus cupsd avahi_daemon gdm sshd_flags=NO $ I have also killed gdm and started it from the shell with the same result. Here is /var/log/gdm : # ls -alrt total 148 -rw-r--r-- 1 root _gdm653 May 15 13:10 :1.log.2 -rw-r--r-- 1 root _gdm653 May 15 13:10 :2.log -rw-r--r-- 1 root _gdm653 May 15 13:10 :3.log -rw-r--r-- 1 root _gdm653 May 15 13:10 :4.log -rw-r--r-- 1 root _gdm653 May 15 13:10 :5.log -rw-r--r-- 1 root _gdm532 Jul 28 21:27 :1-greeter.log.1 -rw-r--r-- 1 root _gdm 9473 Jul 28 21:27 :1.log.1 -rw-r--r-- 1 root _gdm567 Jul 29 00:34 :0-greeter.log.4 -rw-r--r-- 1 root _gdm341 Jul 29 00:35 :0-greeter.log.3 -rw-r--r-- 1 root _gdm249 Jul 29 00:35 :0.log.4 -rw-r--r-- 1 root _gdm 7814 Jul 29 00:43 :1.log -rw-r--r-- 1 root _gdm601 Jul 29 00:43 :1-greeter.log -rw-r--r-- 1 root _gdm249 Jul 29 00:44 :0.log.2 -rw-r--r-- 1 root _gdm791 Jul 29 00:45 :0-greeter.log.2 -rw-r--r-- 1 root _gdm 7814 Jul 29 00:45 :0.log.3 -rw-r--r-- 1 root _gdm 7814 Jul 29 01:24 :0.log.1 -rw-r--r-- 1 root _gdm599 Jul 29 01:24 :0-greeter.log.1 drwx--x--x 2 root _gdm512 Jul 29 01:24 . -rw-r--r-- 1 root _gdm666 Jul 29 01:25 :0-greeter.log -rw-r--r-- 1 root _gdm 7611 Jul 29 01:25 :0.log drwxr-xr-x 7 root wheel 1536 Jul 29 02:08 .. # cat \:0-greeter.log (gnome-settings-daemon:7028): media-keys-plugin-WARNING **: Unable to inhibit keypresses: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.login1 was not provided by any .service files gnome-session-binary[20542]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gnome-session-binary[20542]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (gnome-settings-daemon:7028): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 35 (Resource temporarily unavailable) on X server :0. gnome-session-binary[20542]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1 # cat \0.log cat: 0.log: No such file or directory # cat \:0.log (--) checkDevMem: using aperture driver /dev/xf86 (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) X.Org X Server 1.17.4 Release Date: 2015-10-28 X Protocol Version 11, Revision 0 Build Operating System: OpenBSD 5.9 amd64 Current Operating System: OpenBSD paddy.my.domain 5.9 GENERIC.MP#1888 amd64 Build Date: 26 February 2016 01:59:52AM Current version of pixman: 0.32.8 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: Fri Jul 29 01:24:10 2016 (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |-->Screen "Default Screen Section" (0) (**) | |-->Monitor "" (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. (==) Disabling SIGIO handlers for input devices (==) Automatically adding devices (==) Automatically enabling devices (==) Not automatically adding GPU devices (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ (==) ModulePath set to "/usr/X11R6/lib/modules" (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. (--) PCI:*(0:0:2:0) 8086:2a02:17aa:20b5 rev 12, Mem @ 0xf800/1048576, 0xe000/268435456, I/O @ 0x1800/8 (--) PCI: (0:0:2:1) 8086:2a03:17aa:20b5 rev 12, Mem @ 0xf810/1048576 (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.17.4, module version = 1.0.0 (==) AIGLX enabled (==) Matched intel as autoconfigured driver 0 (==) Matched vesa as autoconfigured driver 1 (==) Assigned the driver to the xf86ConfigLayout (II) Loading /usr/X11R6/lib/modules/drivers/intel_drv.so (II) Module intel: vendor="X.Org Foundation" compiled for 1.17.4, module version = 2.99.916 (II) Loading /usr/
Re: Gnome 3 (gnome-shell) crash on initialization on an x61s with Intel 965 x3100 display
On Fri, Jul 29, 2016 at 12:26:49AM -0500, Justin Haynes wrote: > List - > > I am having a problem starting Gnome 3 on my Thinkpad x61s, and I am not > sure what the cause is. I am reading mixed reviews on whether or not it is > necessary to have 3d support, and as nearly as i can tell i do have 3d > support on this Intel 965 x3100 display through the intel driver and the > i965 DRI driver in X-Windows. > > The problem is that when i attempt ot start Gnome using gdm, I get nothing > but X Windows with a black background and the X mouse cursor. > > Any other method I use yields either the entire root window in grey with > the text: > > "Oh no! something has gone wrong." > "A problem has occurred and the system can't recover. All extensions have > been disabled as a precaution." > > In summary I have tried the following: > > 1. GDM How did you install gnome? And did you do the steps in /usr/local/share/doc/pkg-readmes/gnome-* ? How do you start GDM ? Also a complete dmesg and the content of /var/log/gdm/* could be of interest. > 2. startx, with .xinitrc containing "exec /usr/local/bin/ck-launch-session > /usr/local/bin/gnome-session" > 3. From Window Maker: "/usr/local/bin/ck-launch-session > /usr/local/bin/gnome-session" > 4. reboot, and with boot -c, "disable inteldrm". Thinking that perhaps i > needed X to talk with the hardware without the kernel driver. > (machdep.allowaperture is already = 2) (with gdm) > 5. same as #4 without gdm > 6. same as 4, but with windowmaker like in 3. > > > I do have this appearing in my XOrg.log: > . > [ 1530.853] (II) intel(0): [XvMC] i965_xvmc driver initialized. > [ 1530.853] (II) intel(0): [DRI2] Setup complete > [ 1530.853] (II) intel(0): [DRI2] DRI driver: i965 > [ 1530.853] (II) intel(0): [DRI2] VDPAU driver: i965 > [ 1530.853] (II) intel(0): direct rendering: DRI2 enabled > . > > $ glxinfo | grep -i 3D > GL_3DFX_texture_compression_FXT1, GL_AMD_seamless_cubemap_per_texture, > GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, > GL_OES_surfaceless_context, GL_OES_texture_3D, GL_OES_texture_float, > > > I'll now send this message and gather more of the logs to make available, > starting with #1; GDM. -- Antoine
Gnome 3 (gnome-shell) crash on initialization on an x61s with Intel 965 x3100 display
List - I am having a problem starting Gnome 3 on my Thinkpad x61s, and I am not sure what the cause is. I am reading mixed reviews on whether or not it is necessary to have 3d support, and as nearly as i can tell i do have 3d support on this Intel 965 x3100 display through the intel driver and the i965 DRI driver in X-Windows. The problem is that when i attempt ot start Gnome using gdm, I get nothing but X Windows with a black background and the X mouse cursor. Any other method I use yields either the entire root window in grey with the text: "Oh no! something has gone wrong." "A problem has occurred and the system can't recover. All extensions have been disabled as a precaution." In summary I have tried the following: 1. GDM 2. startx, with .xinitrc containing "exec /usr/local/bin/ck-launch-session /usr/local/bin/gnome-session" 3. From Window Maker: "/usr/local/bin/ck-launch-session /usr/local/bin/gnome-session" 4. reboot, and with boot -c, "disable inteldrm". Thinking that perhaps i needed X to talk with the hardware without the kernel driver. (machdep.allowaperture is already = 2) (with gdm) 5. same as #4 without gdm 6. same as 4, but with windowmaker like in 3. I do have this appearing in my XOrg.log: . [ 1530.853] (II) intel(0): [XvMC] i965_xvmc driver initialized. [ 1530.853] (II) intel(0): [DRI2] Setup complete [ 1530.853] (II) intel(0): [DRI2] DRI driver: i965 [ 1530.853] (II) intel(0): [DRI2] VDPAU driver: i965 [ 1530.853] (II) intel(0): direct rendering: DRI2 enabled . $ glxinfo | grep -i 3D GL_3DFX_texture_compression_FXT1, GL_AMD_seamless_cubemap_per_texture, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_OES_surfaceless_context, GL_OES_texture_3D, GL_OES_texture_float, I'll now send this message and gather more of the logs to make available, starting with #1; GDM.