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.
I installed slackpkg plus and unchecked unchecked nearly every mirror and copied alienbobs suggested config for slackpkgplus. Ran several update,upgrade and gpg commands to get it working and then I saw a new kernel was installed. So I replaced the old file with the new one and now start x is broken again and won't start. I am using /X11/xorg.conf.d as my as xorg path. I receive a "
Code:
nal information. (EE) (EE) Server terminated with error (1). Closing lof file.tio
Xinit: giving up
Xinit: unable to connect to X server: Bad file discriptor
Xinit: server error
(II) LOADMODULE: 'FBDEV'
...WARNING COULDN'T LOAD 'FBDEV'
...(WW) WARNING, COULDN'T OPEN MODULE FBDEV
....vesa: driver for modsetting
.... (EE) open /dev/dri/card0: no such file or directory
(WW) Falling back to old prove method for modsetting
(EE) OPEN /dev/dri/card0: no file or directory
vesa: Refusing to run on UEFI
(EE) Screen 0 deleted because of no matching config setting
I know it has to do with the kernel and xorg conf files. What should i do?
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to copy the
kernel and initrd to the EFI System Partition.
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to copy the
kernel and initrd to the EFI System Partition.
initrd -- command not found
Eliloconfig -- no EFI system partition mounted on /boot/EFI
My /boot/efi is empty and in /boot there is config-generic-5.15.27.x86 and the respective huge keenel
Last edited by naarter; 04-20-2022 at 01:35 PM.
Reason: I am trying
tell you? My guess is it's not 5.15.27. The primary problem is that you upgraded stuff without reading the ChangeLog.txt first. The text in post #4 was from ChangeLog.txt. Because of that you did not run eliloconfig. Now you are probably running an old kernel (5.15.19 ?) but without corresponding modules.
Last edited by Petri Kaukasoina; 04-20-2022 at 01:57 PM.
tell you? My guess is it's not 5.15.27. The primary problem is that you upgraded stuff without reading the ChangeLog.txt first. The text in post #4 was from ChangeLog.txt. Because of that you did not run eliloconfig. Now you are probably running an old kernel (5.15.19 ?) but without corresponding modules.
This is the Slackware Security Advisory for the kernel 5.15.27 update: http://www.slackware.com/security/vi...ecurity.691827 You can find the command line to rebuild the initrd there, in the "Installation instructions".
I tried addressing the bios by changing some settings and now I camt boot into the OS. I MADE a few changes to the UEFI and boot settings. What are some issues that could contribute to this?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.