[F26] Cannot log in with sddm (Plasma), sddm-helper[6948]: segfault
by Frédéric Bron
Hi,
Fresh install of F26.
First user created in the installation process, no issue.
2nd user created with kuser from 1st user session.
This second user cannot log in from sddm but he can log in from a
terminal and run startx which works fine.
Apparently, everytime he tries to login from sddm, we get this in dmesg:
[ 8867.558759] sddm-helper[6948]: segfault at 0 ip 00007f141e369b1e sp
00007ffca5cf19f0 error 4 in libc-2.25.so[7f141e2f7000+1c7000]
Frédéric
6 years, 8 months
- 1
- 0
I give up using Fedora ...
by Walter H.
F25 was running fine; after upgrade to F26 my VMware was broken,
now I have a VMware running with F26, which brings this:
"This host does not support "Intel EPT" hardware assisted MMU
virtualization.
This host does not support virtualizing real mode.
The Intel "VMX Unrestricted Guest" feature is necessary to run this
virtual machine on an Intel processor.
Module 'CPUIDEarly' power on failed.
Failed to start the virtual machine."
and the same machine runs the latest Win10 without problems(!)
this machine is an old HP wkst xw4600 with a Core2 Quad Q9300 CPU and 4
GByte RAM
Greetings,
Walter
6 years, 8 months
- 7
- 14
Radeon(Kaveri) missing firmware and lost HW video acceleration?
by lejeczek
hi fellas
I think I've lost HW video decoding acceleration on A10
PRO-7800B R7 with recent kernel/mesa.
My kodi was nicely using vdpau until recently, I cannot say
when exactly it happened. Now only SW decoding and high CPU
usage.
I think I have all needed packages installed but vaapi also
seems to be gone, when I do:
[entertainer@swir ~]$ vainfo
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_0_40
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.40 (libva )
vainfo: Driver version: mesa gallium vaapi
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
# end of output
and there should be more, right?
In dmesg I see:
....
[ 2.125588] [drm] initializing kernel modesetting (KAVERI
0x1002:0x130F 0x1849:0x130F 0x00).
[ 2.125619] [drm] doorbell mmio base: 0xD0000000
[ 2.125620] [drm] doorbell mmio size: 8388608
[ 2.125693] ATOM BIOS: 113
[ 2.125758] radeon 0000:00:01.0: VRAM: 2048M
0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
[ 2.125760] radeon 0000:00:01.0: GTT: 2048M
0x0000000080000000 - 0x00000000FFFFFFFF
[ 2.125763] [drm] Detected VRAM RAM=2048M, BAR=256M
[ 2.125764] [drm] RAM width 128bits DDR
[ 2.125885] [TTM] Zone kernel: Available graphics
memory: 7184660 kiB
[ 2.125887] [TTM] Zone dma32: Available graphics
memory: 2097152 kiB
[ 2.125887] [TTM] Initializing pool allocator
[ 2.125891] [TTM] Initializing DMA pool allocator
[ 2.125923] [drm] radeon: 2048M of VRAM memory ready
[ 2.125923] [drm] radeon: 2048M of GTT memory ready.
[ 2.125940] [drm] Loading kaveri Microcode
[ 2.126071] [drm] Internal thermal controller without fan
control
[ 2.128154] [drm] radeon: dpm initialized
[ 2.128175] radeon 0000:00:01.0: Direct firmware load for
radeon/bonaire_uvd.bin failed with error -2
[ 2.128177] radeon 0000:00:01.0: radeon_uvd: Can't load
firmware "radeon/bonaire_uvd.bin"
[ 2.128840] radeon 0000:00:01.0: Direct firmware load for
radeon/BONAIRE_uvd.bin failed with error -2
[ 2.128842] radeon 0000:00:01.0: radeon_uvd: Can't load
firmware "radeon/BONAIRE_uvd.bin"
[ 2.129030] radeon 0000:00:01.0: failed UVD (-2) init.
Could you tell your AMD APU(s) is still ok and working in
respect to UVD(video acceleration) in recentkernels/mesas ?
many thanks, L.
.
6 years, 8 months
- 3
- 8