Re: Leap 15.0 Beta - problems within VirtualBox

[Linux Kamarada]

2018-02-03 0:51 GMT-02:00 Linux Kamarada <[hidden email]>:

> Hi everyone! I use openSUSE Leap 42.3.
>
> I downloaded openSUSE Leap 15.0 NET install to give it a try and
> created two virtual machines in VirtualBox: one for KDE and the other
> for GNOME.
>
> Both virtual machines render 640x480 and resizing the host window does
> not resize the guest screen. Bidirectional clipboard works, so I know
> VirtualBox guest additions is somehow working.
>
> From https://forums.virtualbox.org/viewtopic.php?f=3&t=84652#p402321 :
>
> "Hi, from other posts in the forums, it seems that there is an issue
> with VBox video driver and X11 1.19.x, the virtual machine will work
> but the video will not be able to be resized. We are awaiting any
> confirmation from development..."
>
> Regarding the GNOME installation, I'm not able to pass GDM: I enter
> username and password and when I hit Enter, the screen goes black and
> then it comes back to GDM.
>
> Is anyone aware of that?

Adding info from /var/log/Xorg.0.log (KDE VM):

...

[    26.329] (==) Matched vboxvideo as autoconfigured driver 0
[    26.329] (==) Matched modesetting as autoconfigured driver 1
[    26.329] (==) Matched fbdev as autoconfigured driver 2
[    26.329] (==) Matched vesa as autoconfigured driver 3
[    26.329] (==) Assigned the driver to the xf86ConfigLayout
[    26.329] (II) LoadModule: "vboxvideo"
[    26.343] (WW) Warning, couldn't open module vboxvideo
[    26.343] (II) UnloadModule: "vboxvideo"
[    26.343] (II) Unloading vboxvideo
[    26.343] (EE) Failed to load module "vboxvideo" (module does not exist, 0)

...

[    26.366] (**) FBDEV(1): claimed PCI slot 0@0:2:0
[    26.366] (II) FBDEV(1): using default device
[    26.366] (WW) Falling back to old probe method for vesa
[    26.366] (EE) Screen 0 deleted because of no matching config section.
[    26.366] (II) UnloadModule: "modesetting"
[    26.366] (II) FBDEV(0): Creating default Display subsection in
Screen section
       "Default Screen Section" for depth/fbbpp 24/32
[    26.366] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[    26.366] (==) FBDEV(0): RGB weight 888
[    26.366] (==) FBDEV(0): Default visual is TrueColor
[    26.366] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[    26.366] (II) FBDEV(0): hardware: VESA VGA (video memory: 1216kB)
[    26.366] (II) FBDEV(0): checking modes against framebuffer device...
[    26.366] (II) FBDEV(0): checking modes against monitor...
[    26.366] (--) FBDEV(0): Virtual size is 640x480 (pitch 640)

...

It seems that I'm actually using fbdev as Xorg driver.

The KDE VM works fine, except for the fact that the display cannot
resize from 640x480.

I'm afraid of that line:

[    26.343] (EE) Failed to load module "vboxvideo" (module does not exist, 0)

The GNOME VM does not even produce a /var/log/Xorg.0.log at all.


Antonio
The Linux Kamarada Project
http://kamarada.github.io/
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Andrei Borzenkov]

03.02.2018 06:13, Linux Kamarada пишет:
>
> The GNOME VM does not even produce a /var/log/Xorg.0.log at all.
>

Check /var/lib/gdm/.local/share/xorg for GDM Xerver, ~/.local/share/xorg
for your session Xserver. It also should go into journal.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Wolfgang Bauer]

Am Samstag, 3. Februar 2018, 01:13:42 schrieb Linux Kamarada:
> It seems that I'm actually using fbdev as Xorg driver.

Likely a problem with the guest additions, the kernel modules in particular.
It should normally use "modesetting", which of course needs the KMS kernel
module.

Check that virtualbox-guest-kmp-default is installed.

> The GNOME VM does not even produce a /var/log/Xorg.0.log at all.

That's probably because gdm run Xorg as non-root, which needs KMS, i.e. won't
work with fbdev. (and if it's the wayland session, it probably won't work with
fbdev anyway I think)

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Linux Kamarada]

Em Sáb, 2018-02-03 às 09:10 +0300, Andrei Borzenkov escreveu:
> 03.02.2018 06:13, Linux Kamarada пишет:
> >
> >
> > The GNOME VM does not even produce a /var/log/Xorg.0.log at all.
> >
>
> Check /var/lib/gdm/.local/share/xorg for GDM Xerver, ~/.local/share/xorg
> for your session Xserver. It also should go into journal.

/var/lib/gdm/.local/share/xorg/Xorg.0.log from the GNOME VM:

...

[    44.335] (==) Matched vboxvideo as autoconfigured driver 0
[    44.335] (==) Matched modesetting as autoconfigured driver 1
[    44.335] (==) Matched fbdev as autoconfigured driver 2
[    44.335] (==) Matched vesa as autoconfigured driver 3
[    44.335] (==) Assigned the driver to the xf86ConfigLayout
[    44.335] (II) LoadModule: "vboxvideo"
[    44.335] (WW) Warning, couldn't open module vboxvideo
[    44.335] (II) UnloadModule: "vboxvideo"
[    44.335] (II) Unloading vboxvideo
[    44.335] (EE) Failed to load module "vboxvideo" (module does not exist, 0)

...

[    44.336] (II) Module fbdevhw: vendor="X.Org Foundation"
[    44.336] compiled for 1.19.6, module version = 0.0.2
[    44.336] ABI class: X.Org Video Driver, version 23.0
[    44.336] (**) FBDEV(1): claimed PCI slot 0@0:2:0
[    44.336] (II) FBDEV(1): using default device
[    44.336] (WW) Falling back to old probe method for vesa
[    44.336] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    44.336] (EE) Screen 0 deleted because of no matching config section.
[    44.336] (II) UnloadModule: "modesetting"
[    44.336] (II) FBDEV(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    44.336] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[    44.336] (==) FBDEV(0): RGB weight 888
[    44.336] (==) FBDEV(0): Default visual is TrueColor
[    44.336] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[    44.336] (II) FBDEV(0): hardware: VESA VGA (video memory: 1216kB)
[    44.336] (II) FBDEV(0): checking modes against framebuffer device...
[    44.336] (II) FBDEV(0): checking modes against monitor...
[    44.336] (--) FBDEV(0): Virtual size is 640x480 (pitch 640)

...

Same as the KDE VM: it is using the fbdev Xorg driver.

~/.local/share/xorg/Xorg.0.log shows something different:

...

[    24.376] (==) Matched vboxvideo as autoconfigured driver 0
[    24.376] (==) Matched modesetting as autoconfigured driver 1
[    24.376] (==) Matched fbdev as autoconfigured driver 2
[    24.376] (==) Matched vesa as autoconfigured driver 3
[    24.376] (==) Assigned the driver to the xf86ConfigLayout
[    24.376] (II) LoadModule: "vboxvideo"
[    24.383] (WW) Warning, couldn't open module vboxvideo
[    24.383] (II) UnloadModule: "vboxvideo"
[    24.383] (II) Unloading vboxvideo
[    24.383] (EE) Failed to load module "vboxvideo" (module does not exist, 0)

...

[    24.412] (II) Module fbdevhw: vendor="X.Org Foundation"
[    24.412] compiled for 1.19.6, module version = 0.0.2
[    24.412] ABI class: X.Org Video Driver, version 23.0
[    24.412] (EE) open /dev/fb0: Permission denied
[    24.412] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    24.412] (EE) Screen 0 deleted because of no matching config section.
[    24.412] (II) UnloadModule: "modesetting"
[    24.412] (EE) Screen 0 deleted because of no matching config section.
[    24.412] (II) UnloadModule: "fbdev"
[    24.412] (II) UnloadSubModule: "fbdevhw"
[    24.412] (II) Loading sub module "vbe"
[    24.412] (II) LoadModule: "vbe"
[    24.413] (II) Loading /usr/lib64/xorg/modules/libvbe.so
[    24.413] (II) Module vbe: vendor="X.Org Foundation"
[    24.413] compiled for 1.19.6, module version = 1.1.0
[    24.413] ABI class: X.Org Video Driver, version 23.0
[    24.414] (II) Loading sub module "int10"
[    24.414] (II) LoadModule: "int10"
[    24.414] (II) Loading /usr/lib64/xorg/modules/libint10.so
[    24.415] (II) Module int10: vendor="X.Org Foundation"
[    24.415] compiled for 1.19.6, module version = 1.0.0
[    24.415] ABI class: X.Org Video Driver, version 23.0
[    24.415] (II) VESA(0): initializing int10
[    24.415] (EE) VESA(0): Cannot read int vect
[    24.415] (II) UnloadModule: "vesa"
[    24.415] (II) UnloadSubModule: "int10"
[    24.415] (II) Unloading int10
[    24.415] (II) UnloadSubModule: "vbe"
[    24.415] (II) Unloading vbe
[    24.415] (EE) Screen(s) found, but none have a usable configuration.
[    24.415] (EE)
Fatal server error:
[    24.415] (EE) no screens found(EE)
[    24.415] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[    24.415] (EE) Please also check the log file at "/home/kamarada/.local/share/xorg/Xorg.0.log" for additional information.
[    24.415] (EE)
[    24.419] (EE) Server terminated with error (1). Closing log file.

I didn't find helpful information on journalctl. Basically it contains those two log files.


Antonio
The Linux Kamarada Project
https://kamarada.github.io/


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Linux Kamarada]

Em Sáb, 2018-02-03 às 09:22 +0100, Wolfgang Bauer escreveu:
> Am Samstag, 3. Februar 2018, 01:13:42 schrieb Linux Kamarada:
> >
> > It seems that I'm actually using fbdev as Xorg driver.
>
> Likely a problem with the guest additions, the kernel modules in particular.
> It should normally use "modesetting", which of course needs the KMS kernel
> module.
>
> Check that virtualbox-guest-kmp-default is installed.

# zypper info virtualbox-guest-kmp-default
Loading repository data...
Warning:
Repository 'openSUSE-Leap-15.0-Update' appears to be outdated. Consider using a
different mirror or server.
Reading installed packages...


Information for package virtualbox-guest-kmp-default:
-----------------------------------------------------
Repository     : openSUSE-Leap-15.0-1               
Name           : virtualbox-guest-kmp-default       
Version        : 5.2.6_k4.12.14_lp150.4-lp150.1.2   
Arch           : x86_64                             
Vendor         : openSUSE                           
Installed Size : 646.7 KiB                          
Installed      : Yes (automatically)                
Status         : up-to-date                         
Source package : virtualbox-5.2.6-lp150.1.2.src     
Summary        : Guest kernel modules for VirtualBox
Description    :                                    
    VirtualBox is an extremely feature rich, high performance product
    for enterprise customers, it is also the only professional solution
    that is freely available as Open Source Software under the terms of the
    GNU Public License (GPL).

Yes, version 5.2.6 of virtualbox-guest-kmp-default is installed. 


Antonio
The Linux Kamarada Project
https://kamarada.github.io/


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Andrei Borzenkov]

03.02.2018 14:33, Linux Kamarada пишет:
>
> Yes, version 5.2.6 of virtualbox-guest-kmp-default is installed. 
>

Xorg.log complains about X11 driver vboxvideo, not kernel driver.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Andrei Borzenkov]

03.02.2018 14:15, Linux Kamarada пишет:
...
>
> ~/.local/share/xorg/Xorg.0.log shows something different:
...
> [    24.412] (EE) open /dev/fb0: Permission denied
> [    24.412] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support

Try using different DM like lightdm.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Linux Kamarada]

Em Sáb, 2018-02-03 às 15:15 +0300, Andrei Borzenkov escreveu:
> 03.02.2018 14:33, Linux Kamarada пишет:
> >
> >
> > Yes, version 5.2.6 of virtualbox-guest-kmp-default is installed. 
> >
>
> Xorg.log complains about X11 driver vboxvideo, not kernel driver.

Version 5.2.6 of virtualbox-guest-x11 is installed:

# zypper info virtualbox-guest-x11
Loading repository data...
Warning: Repository 'openSUSE-Leap-15.0-Update' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...


Information for package virtualbox-guest-x11:
---------------------------------------------
Repository     : openSUSE-Leap-15.0-1                      
Name           : virtualbox-guest-x11                      
Version        : 5.2.6-lp150.1.2                          
Arch           : x86_64                                    
Vendor         : openSUSE                                  
Installed Size : 6.3 MiB                                  
Installed      : Yes (automatically)                      
Status         : up-to-date                                
Source package : virtualbox-5.2.6-lp150.1.2.src            
Summary        : VirtualBox X11 drivers for mouse and video
Description    :                                          
    VirtualBox
    This package contains X11 guest utilities and X11 guest mouse and video drivers

Actually, both virtualbox-guest-kmp-default and virtualbox-guest-x11 are
installed on both KDE and GNOME VMs.


Antonio
The Linux Kamarada Project
https://kamarada.github.io/


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Wolfgang Bauer]

Am Samstag, 3. Februar 2018, 15:15:47 schrieb Andrei Borzenkov:
> 03.02.2018 14:33, Linux Kamarada пишет:
> > Yes, version 5.2.6 of virtualbox-guest-kmp-default is installed.
>
> Xorg.log complains about X11 driver vboxvideo, not kernel driver.

Sure, but it should rather be using "modesetting" in the first place.
And for this (KMS), the vboxvideo *kernel module* is needed.

The vboxvideo Xorg driver only supports UMS, and won't work if Xorg is not
running as root (as is the case with gdm).
And even if, it needed the "iomem=relaxed" kernel option since quite a while,
on Tumbleweed at least.
But here it's not found anyway.

I just had a quick look, and the vboxvideo kernel module is missing in the 5.2
guest-kmp package.

Maybe that has changed in VirtualBox 5.2 (it is still there in Leap 42.3's
virtualbox 5.1.32 guest packages). But I suppose a kernel module would still
be needed for KMS support...
IIRC, the module has been moved to the standard kernel, but maybe it's not in
the kernel version in Leap 15 yet?

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Wolfgang Bauer]

Am Samstag, 3. Februar 2018, 10:34:57 schrieb Linux Kamarada:
> Em Sáb, 2018-02-03 às 15:15 +0300, Andrei Borzenkov escreveu:
> > 03.02.2018 14:33, Linux Kamarada пишет:
> > > Yes, version 5.2.6 of virtualbox-guest-kmp-default is installed.
> >
> > Xorg.log complains about X11 driver vboxvideo, not kernel driver.
>
> Version 5.2.6 of virtualbox-guest-x11 is installed:

Well, AFAICS the virtualbox-guest-x11 package doesn't contain the Xorg driver
anymore.
But that may be on purpose, as it normally isn't used (and doesn't work)
anymore.

From the package changelog:
Fri Dec 29 19:19:22 UTC 2017 - [hidden email]

- File "fixes_for_4.14.patch" deleted - upstream fix.
  File "remove_vbox_video_build.patch" added as current versions of Xorg no
longer need this component.

The patch remove_vbox_video_build.patch disables the build of the vboxvideo
Xorg driver.

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Linux Kamarada]

Em Sáb, 2018-02-03 às 15:17 +0300, Andrei Borzenkov escreveu:

> 03.02.2018 14:15, Linux Kamarada пишет:
> ...
> >
> >
> > ~/.local/share/xorg/Xorg.0.log shows something different:
> ...
> >
> > [    24.412] (EE) open /dev/fb0: Permission denied
> > [    24.412] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
>
> Try using different DM like lightdm.

I installed lightdm using:

# zypper in lightdm

Then, using YaST's /etc/sysconfig Editor, I changed the DISPLAYMANAGER setting to "lightdm".

Rebooted.

GDM was started. I removed GDM using:

# zypper remove gdm

Rebooted once again. Just black screen with mouse cursor.

Using YaST's /etc/sysconfig Editor, I changed the DISPLAYMANAGER_AUTOLOGIN setting to "" (empty string).

Rebooted once more. This time LightDM showed up. But I entered username and password, hit Enter, and GNOME desktop did not show up. Just the wallpaper (maybe the background of LightDM itself).


Antonio
The Linux Kamarada Projecthttps://kamarada.github.io/


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Wolfgang Bauer]

Am Samstag, 3. Februar 2018, 10:56:47 schrieb Linux Kamarada:
> Then, using YaST's /etc/sysconfig Editor, I changed the DISPLAYMANAGER
> setting to "lightdm".

That's no longer respected since some months.
You need to use update-alternatives to set the default displaymanager.

> Rebooted once more. This time LightDM showed up.

Sure that it wasn't GDM again? ;-)

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Linux Kamarada]

Em Sáb, 2018-02-03 às 14:16 +0100, Wolfgang Bauer escreveu:
> Am Samstag, 3. Februar 2018, 10:56:47 schrieb Linux Kamarada:
> > Rebooted once more. This time LightDM showed up.
>
> Sure that it wasn't GDM again? ;-)

Sure it was LightDM:

https://paste.opensuse.org/48639806

https://paste.opensuse.org/30546577


Antonio
The Linux Kamarada Project
https://kamarada.github.io/


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Linux Kamarada]

2018-02-03 12:53 GMT-02:00 Wolfgang Bauer <[hidden email]>:
> Am Samstag, 3. Februar 2018, 12:28:24 schrieb Linux Kamarada:
>> Should I open two bugs, one for KDE and other for GNOME, or just one? I
>> believe they have the same cause, but they are somehow different.
>
> This is neither a bug in KDE nor GNOME.

Bug reported :D

https://bugzilla.opensuse.org/show_bug.cgi?id=1079221

>> /var/log/Xorg.0.log does not exist and journalctl does not show
>> useful information to debug why SDDM does not show up.
>
> What about systemctl status display-manager?

# systemctl status display-manager
● display-manager.service - X Display Manager
   Loaded: loaded (/usr/lib/systemd/system/display-manager.service;
enabled; vendor preset: enabled)
   Active: active (running) since Sat 2018-02-03 17:10:10 CET; 1min 9s ago
 Main PID: 1616 (sddm)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/display-manager.service
           └─1616 /usr/bin/sddm

Feb 03 17:10:08 localhost display-manager[1523]:
/usr/lib/X11/display-manager: line 132: type:
default-displaymanager_vars: not found
Feb 03 17:10:08 localhost display-manager[1523]: /etc/vconsole.conf available
Feb 03 17:10:08 localhost display-manager[1523]: KEYMAP: us
Feb 03 17:10:08 localhost display-manager[1523]: Command: localectl
set-keymap us
Feb 03 17:10:09 localhost display-manager[1523]: I: Using systemd
/usr/share/systemd/kbd-model-map mapping
Feb 03 17:10:10 localhost sddm[1616]: Initializing...
Feb 03 17:10:10 localhost sddm[1616]: Logind interface found
Feb 03 17:10:10 localhost sddm[1616]: Starting...
Feb 03 17:10:10 localhost display-manager[1523]: Starting service sddm..done
Feb 03 17:10:10 localhost systemd[1]: Started X Display Manager.

Looking only at that output, it seems like both SDDM and Xorg were
started. Confusing...

> Is the default target actually "graphical.target" or is it rather set to boot
> to text mode?
> "systemctl get-default"

# systemctl get-default
graphical.target

Thank you for your directions so far!


Antonio
The Linux Kamarada Project
http://kamarada.github.io/
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Wolfgang Bauer]

Am Samstag, 3. Februar 2018, 14:01:59 schrieb Linux Kamarada:

> Em Sáb, 2018-02-03 às 14:16 +0100, Wolfgang Bauer escreveu:
> > Am Samstag, 3. Februar 2018, 10:56:47 schrieb Linux Kamarada:
> > > Rebooted once more. This time LightDM showed up.
> >
> > Sure that it wasn't GDM again? ;-)
>
> Sure it was LightDM:
>
> https://paste.opensuse.org/48639806
>
> https://paste.opensuse.org/30546577

Well, I have absolutely no idea how either gdm or lightdm look like in Leap
15.0.
So your screenshots don't prove anything to me... ;-)

But ok, let's assume that it is lightdm.

My point was that changing DISPLAYMANAGER in /etc/sysconfig/displaymanager has
no effect, so whatever you set it to, you'd still get gdm.
But you actually uninstalled gdm to get lightdm, didn't you?
That's the "advantage" of using update-alternatives. Previously, the fallback
would have been xdm, if the configured displaymanager is not installed.

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Wolfgang Bauer]

Am Samstag, 3. Februar 2018, 14:14:40 schrieb Linux Kamarada:
> Looking only at that output, it seems like both SDDM and Xorg were
> started. Confusing...

Indeed.

Maybe it's just on a different tty?

Try pressing Ctrl+Alt+F1 to Ctrl+Alt+F9.

Kind Regards,
Wolfgang

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

[Linux Kamarada]

2018-02-03 14:50 GMT-02:00 Wolfgang Bauer <[hidden email]>:
> Am Samstag, 3. Februar 2018, 14:14:40 schrieb Linux Kamarada:
>> Looking only at that output, it seems like both SDDM and Xorg were
>> started. Confusing...
>
> Indeed.
>
> Maybe it's just on a different tty?
>
> Try pressing Ctrl+Alt+F1 to Ctrl+Alt+F9.

From F1 to F6, text console. From F7 to F9, just a blank underline on
a black background.

Let's wait for OBS to finish, so we can test the live image with the
patched virtualbox-guest-kmp-default :)


Antonio
The Linux Kamarada Project
http://kamarada.github.io/
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]