Things That Won't Run in -Current (21 April 2015).
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just install a FAT file system in that partition instead of the ntfs one before running setup. mkfs.fat is shipped in the installer. No need to change the partition type to do that.
Using mkfs.fat indeed "fixes" the issue and allows the ELILO boot manager to be installed. Thanks for the help on this.
Using mkfs.fat indeed "fixes" the issue and allows the ELILO boot manager to be installed. Thanks for the help on this.
You are welcome. Just for the sake of accuracy, what you did is modify the firmware's boot menu stored in NVRAM, adding an entry for Slackware in it, using the EFI image elilo-x86_64.efi (renamed elilo.efi) for booting the system. Somehow this image plays the role of a boot loader as would be installed by LILO, but in the latter case the menu is in the hard disk.
So elilo is not a boot manager, it is a provider of EFI images, that can be referred to in the firmware's boot menu thanks to efibootmgr.
Last edited by Didier Spaier; 05-03-2015 at 09:26 PM.
Reason: s/ROM/NVRAM/
Someone else with immediate X/KDE crash when steam-client is being launched?
Slackware64-current, multilib upgraded to the latest. I use the open source radeon driver, the card is Radeon R7 260. No issues before the massive upgrade (21.04.2015), I played some games.
I upgraded from a local mirror. As a first step I upgraded the AlienBob's KDE 4.14.3(6) with the slackware's one: upgradepkg --reinstall --install-new kde/*.t?z
After that I upgraded the rest with upgradepkg --install-new */*.t?z and removed the old packages (slackpkg clean-system).
Today I upgraded to the latest packages (Mesa 10.5.4, ...), the same issue.
I don't have xorg.conf and xorg.conf.d is empty.
Code:
glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD BONAIRE
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.5.4
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.5.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.5.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
Someone else with immediate X/KDE crash when steam-client is being launched?
Slackware64-current, multilib upgraded to the latest. I use the open source radeon driver, the card is Radeon R7 260. No issues before the massive upgrade (21.04.2015), I played some games.
Have you seen this post? It is about mesa for 32bit that needs recompiling. If your games need 32bit libraries that might be the reason...
The latest update to -current (Mon May 4 04:15:20 UTC 2015) comes with updated mesa and libdrm which solve the issue of the unresolved symbol in the i965 driver.
The repository with my multilib compat32 packages for -current has been updated as well. You could try if this fixes your errors.
The latest update to -current (Mon May 4 04:15:20 UTC 2015) comes with updated mesa and libdrm which solve the issue of the unresolved symbol in the i965 driver.
I have updated my multilib system to these packages, and yes that works fine
[nzel-server:~]# grep '(EE)' /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 103.995] (EE) systemd-logind: failed to get session: The name org.freedesktop.login1 was not provided by any .service files
[ 103.996] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
[ 104.010] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 104.164] (EE) NOUVEAU(0): [drm] failed to set drm interface version.
[ 104.164] (EE) NOUVEAU(0): [drm] error opening the drm
[ 104.164] (EE) NOUVEAU(0): 892:
[ 104.164] (EE) Screen(s) found, but none have a usable configuration.
[ 104.164] (EE)
[ 104.164] (EE) no screens found(EE)
[ 104.164] (EE)
[ 104.164] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 104.164] (EE)
[ 104.172] (EE) Server terminated with error (1). Closing log file.
I'm using my own kernel, tested with stock kernel still can not start.
done some research and found:
linux 4.0.1: drivers/gpu/drm/drm_ioctl.c, drm_ioctl_permit, L507
Quote:
if (unlikely((flags & DRM_MASTER) && !file_priv->is_master &&
!drm_is_control_client(file_priv)))
return -EACCES;
this code cause "failed to set DRM interface version 1.4: Permission denied",
checked mesa/libdrm/nouveau/xserver, can not found something related.
compared with Fedora 21/Ubunto 14.10, they are almost the same X-server version, and is running ok.
with Arch, system updated to today, is ok.
So, anything else I can make a try? or is slack packaging problem?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.