Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 674520 - sys-apps/systemd-240 together with openrc doesn't load necessary modules
Summary: sys-apps/systemd-240 together with openrc doesn't load necessary modules
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo systemd Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-04 17:31 UTC by Helmut Jarausch
Modified: 2019-01-31 14:55 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (xz-compressed) (emerge_info.xz,7.68 KB, application/x-xz)
2019-01-04 17:31 UTC, Helmut Jarausch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Helmut Jarausch 2019-01-04 17:31:49 UTC
Created attachment 559796 [details]
emerge --info  (xz-compressed)

Probably, I have a non-typical configuration.
I have (had) systemd installed as well as sys-apps/openrc and
I use openrc to initialize my system.

Up to version 2.39-r2 this worked just fine.
But with system-2.40-rx my system doesn't load any modules any more.
This breaks video and therefore X11 and the virtualbox modules aren't loaded
as well.

Is it still possible to have systemd installed when using openrc as init process.
What has to be changed on my system?

Many thanks for a hint,
Helmut.
Comment 1 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2019-01-04 17:38:45 UTC
sys-apps/systemd-2.40-rx is quite ambiguous.

Have you tried =sys-apps/systemd-240-r2 as well?
Comment 2 Mike Gilbert gentoo-dev 2019-01-04 18:02:03 UTC
I would expect systemd + openrc to work just fine, though I have not tested this in a long time.

I am not able to provide any advice since this is not a configuration I use or test regularly.

Please feel free to re-open if you can identify the problem more specifically and there is something for us to fix.
Comment 3 Helmut Jarausch 2019-01-05 15:53:40 UTC
(In reply to Mike Gilbert from comment #2)
> I would expect systemd + openrc to work just fine, though I have not tested
> this in a long time.
> 
> I am not able to provide any advice since this is not a configuration I use
> or test regularly.
> 
> Please feel free to re-open if you can identify the problem more
> specifically and there is something for us to fix.

The only information I do have is the following.
On the very same machine / Gentoo system / kernel (4.20.0-gentoo)
I have compared dmesg output and Xorg.0.log once with
systemd-239-r2 installed (which works fine)
and
systemd-240-r2 (or systemd-240-r1) which is broken.

On the broken system (with systemd-240) the following lines are missing (in comparison to system with systemd-239-r2)

[drm] DM_PPLIB: values for Engine clock
[drm] DM_PPLIB:   214000
[drm] DM_PPLIB:   387000
[drm] DM_PPLIB:   843000
[drm] DM_PPLIB:   995000
[drm] DM_PPLIB:   1062000
[drm] DM_PPLIB:   1108000
[drm] DM_PPLIB:   1149000
[drm] DM_PPLIB:   1224000
[drm] DM_PPLIB: Validation clocks:
[drm] DM_PPLIB:    engine_max_clock: 122400
[drm] DM_PPLIB:    memory_max_clock: 175000
[drm] DM_PPLIB:    level           : 8
[drm] DM_PPLIB: values for Memory clock
[drm] DM_PPLIB:   300000
[drm] DM_PPLIB:   625000
[drm] DM_PPLIB:   1750000
[drm] DM_PPLIB: Validation clocks:
[drm] DM_PPLIB:    engine_max_clock: 122400
[drm] DM_PPLIB:    memory_max_clock: 175000
[drm] DM_PPLIB:    level           : 8
[drm] Display Core initialized with v3.1.68!
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
[drm] UVD and UVD ENC initialized successfully.
[drm] VCE initialized successfully.
[drm] fb mappable at 0x80E28000
[drm] vram apper at 0x80000000
[drm] size 9216000
[drm] fb depth is 24
[drm]    pitch is 7680
fbcon: amdgpudrmfb (fb0) is primary device
input: Wacom Graphire4 4x5 Pen as /devices/pci0000:00/0000:00:07.1/0000:0a:00.3/usb5/5-3/5-3.1/5-3.1:1.0/0003:056A:0015.0001/input/input19
input: Wacom Graphire4 4x5 Pad as /devices/pci0000:00/0000:00:07.1/0000:0a:00.3/usb5/5-3/5-3.1/5-3.1:1.0/0003:056A:0015.0001/input/input21
wacom 0003:056A:0015.0001: hidraw0: USB HID v1.00 Mouse [WACOM CTE-440-U V4.0-3] on usb-0000:0a:00.3-3.1/input0
Console: switching to colour frame buffer device 240x75
amdgpu 0000:42:00.0: fb0: amdgpudrmfb frame buffer device
[drm] Initialized amdgpu 3.27.0 20150101 for 0000:42:00.0 on minor 0


and not surprising I get the following lines in Xorg.0.log on the broken system:

[    44.633] (II) AMDGPU: Driver for AMD Radeon:
	All GPUs supported by the amdgpu kernel driver
[    44.633] (--) using VT number 7

[    44.636] (EE) open /dev/dri/card0: No such file or directory
[    44.636] (WW) Falling back to old probe method for modesetting
[    44.636] (EE) open /dev/dri/card0: No such file or directory
[    44.636] (II) AMDGPU(1): [KMS] drm report modesetting isn't supported.
[    44.636] (EE) Screen 0 deleted because of no matching config section.
[    44.636] (II) UnloadModule: "modesetting"
[    44.636] (EE) Screen 0 deleted because of no matching config section.
[    44.636] (II) UnloadModule: "amdgpu"
[    44.636] (EE) Device(s) detected, but none match those in the config file.
[    44.636] (EE) 
Fatal server error:
[    44.636] (EE) no screens found(EE) 
[    44.636] (EE) 

This looks like systemd-240 disables loading of (at least some of) the 
following kernel modules

/lib/modules/4.20.0-gentoo/kernel/drivers/gpu/drm/{amd,readeon,scheduler,ttm}

Note, that the very same kernel is used. Just, switching between
the two version of systemd switches between are running and a broken system.

I hope this information helps a bit,
many thanks,
Helmut
Comment 4 Aidan Thornton 2019-01-07 21:12:50 UTC
I've been having the exact same issue with sys-boot/udev-240-r2 (and 240 too for that matter). Had to downgrade to 239 to get my system working properly again.
Comment 5 Mike Gilbert gentoo-dev 2019-01-07 21:21:01 UTC
I don't think this has anything to do with OpenRC. Are you able to reproduce the issue on a system without OpenRC installed?
Comment 6 Larry the Git Cow gentoo-dev 2019-01-24 14:53:30 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=55b9c69178b4518b06b29c3f156c2f1e33211224

commit 55b9c69178b4518b06b29c3f156c2f1e33211224
Author:     Mike Gilbert <floppym@gentoo.org>
AuthorDate: 2019-01-24 14:47:16 +0000
Commit:     Mike Gilbert <floppym@gentoo.org>
CommitDate: 2019-01-24 14:47:16 +0000

    sys-apps/systemd: backports for 240 based on v240-stable branch
    
    Bug: https://bugs.gentoo.org/674520
    Bug: https://bugs.gentoo.org/674292
    Bug: https://bugs.gentoo.org/674152
    Package-Manager: Portage-2.3.56_p3, Repoman-2.3.12_p50
    Signed-off-by: Mike Gilbert <floppym@gentoo.org>

 sys-apps/systemd/Manifest              |   1 +
 sys-apps/systemd/systemd-240-r4.ebuild | 457 +++++++++++++++++++++++++++++++++
 2 files changed, 458 insertions(+)
Comment 7 Helmut Jarausch 2019-01-26 16:29:48 UTC
(In reply to Larry the Git Cow from comment #6)
> The bug has been referenced in the following commit(s):
> 
> https://gitweb.gentoo.org/repo/gentoo.git/commit/
> ?id=55b9c69178b4518b06b29c3f156c2f1e33211224
> 
> commit 55b9c69178b4518b06b29c3f156c2f1e33211224
> Author:     Mike Gilbert <floppym@gentoo.org>
> AuthorDate: 2019-01-24 14:47:16 +0000
> Commit:     Mike Gilbert <floppym@gentoo.org>
> CommitDate: 2019-01-24 14:47:16 +0000
> 
>     sys-apps/systemd: backports for 240 based on v240-stable branch
>     
>     Bug: https://bugs.gentoo.org/674520
>     Bug: https://bugs.gentoo.org/674292
>     Bug: https://bugs.gentoo.org/674152
>     Package-Manager: Portage-2.3.56_p3, Repoman-2.3.12_p50
>     Signed-off-by: Mike Gilbert <floppym@gentoo.org>
> 
>  sys-apps/systemd/Manifest              |   1 +
>  sys-apps/systemd/systemd-240-r4.ebuild | 457
> +++++++++++++++++++++++++++++++++
>  2 files changed, 458 insertions(+)

Unfortunately, this doesn't resolve my issue.
With systemd-240-r4 AMDGPU is still not initialized, e.g.
in comparison with the working systemd-239-r3 the following entries
are missing in dmesg's output :

[drm] amdgpu kernel modesetting enabled.
[drm] initializing kernel modesetting (POLARIS11 0x1002:0x67FF 0x1458:0x22FF 0xCF).
[drm] register mmio base: 0x9F400000
[drm] register mmio size: 262144
[drm] add ip block number 0 <vi_common>
[drm] add ip block number 1 <gmc_v8_0>
[drm] add ip block number 2 <tonga_ih>
[drm] add ip block number 3 <gfx_v8_0>
[drm] add ip block number 4 <sdma_v3_0>
[drm] add ip block number 5 <powerplay>
[drm] add ip block number 6 <dm>
[drm] add ip block number 7 <uvd_v6_0>
[drm] add ip block number 8 <vce_v3_0>
[drm] UVD is enabled in VM mode
[drm] UVD ENC is enabled in VM mode
[drm] VCE enabled in VM mode
amdgpu 0000:42:00.0: No more image in the PCI ROM
ATOM BIOS: xxx-xxx-xxx
[drm] vm size is 256 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
amdgpu 0000:42:00.0: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
amdgpu 0000:42:00.0: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
[drm] Detected VRAM RAM=4096M, BAR=256M
[drm] RAM width 128bits GDDR5
[TTM] Zone  kernel: Available graphics memory: 32903998 kiB
[TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[TTM] Initializing pool allocator
[TTM] Initializing DMA pool allocator
[drm] amdgpu: 4096M of VRAM memory ready
[drm] amdgpu: 4096M of GTT memory ready.
[drm] GART: num cpu pages 65536, num gpu pages 65536
[drm] PCIE GART of 256M enabled (table at 0x000000F400900000).
[drm] Chained IB support enabled!
[drm] Found UVD firmware Version: 1.130 Family ID: 16
[drm] Found VCE firmware Version: 53.26 Binary ID: 3
[drm] DM_PPLIB: values for Engine clock
[drm] DM_PPLIB:   214000
[drm] DM_PPLIB:   387000
[drm] DM_PPLIB:   843000
[drm] DM_PPLIB:   995000
[drm] DM_PPLIB:   1062000
[drm] DM_PPLIB:   1108000
[drm] DM_PPLIB:   1149000
[drm] DM_PPLIB:   1224000
[drm] DM_PPLIB: Validation clocks:
[drm] DM_PPLIB:    engine_max_clock: 122400
[drm] DM_PPLIB:    memory_max_clock: 175000
[drm] DM_PPLIB:    level           : 8
[drm] DM_PPLIB: values for Memory clock
[drm] DM_PPLIB:   300000
[drm] DM_PPLIB:   625000
[drm] DM_PPLIB:   1750000
[drm] DM_PPLIB: Validation clocks:
[drm] DM_PPLIB:    engine_max_clock: 122400
[drm] DM_PPLIB:    memory_max_clock: 175000
[drm] DM_PPLIB:    level           : 8
[drm] Display Core initialized with v3.1.68!
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
[drm] UVD and UVD ENC initialized successfully.
[drm] VCE initialized successfully.
input: Wacom Graphire4 4x5 Pen as /devices/pci0000:00/0000:00:07.1/0000:0a:00.3/usb5/5-3/5-3.1/5-3.1:1.0/0003:056A:0015.0001/input/input19
input: Wacom Graphire4 4x5 Pad as /devices/pci0000:00/0000:00:07.1/0000:0a:00.3/usb5/5-3/5-3.1/5-3.1:1.0/0003:056A:0015.0001/input/input21
wacom 0003:056A:0015.0001: hidraw0: USB HID v1.00 Mouse [WACOM CTE-440-U V4.0-3] on usb-0000:0a:00.3-3.1/input0
[drm] fb mappable at 0x80E28000
[drm] vram apper at 0x80000000
[drm] size 9216000
[drm] fb depth is 24
[drm]    pitch is 7680
Comment 8 Mike Gilbert gentoo-dev 2019-01-26 16:53:44 UTC
Please retest with 241-rc1. If it is still broken, please submit an issue upstream.

https://github.com/systemd/systemd/issues
Comment 9 Helmut Jarausch 2019-01-31 14:54:33 UTC
(In reply to Mike Gilbert from comment #8)
> Please retest with 241-rc1. If it is still broken, please submit an issue
> upstream.
> 
> https://github.com/systemd/systemd/issues

I've just updated my system to systemd-241-rc2.
IT WORKS !

Many thanks,
Helmut