LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-04-2018, 06:48 PM   #31
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.2 & -current
Posts: 692

Original Poster
Rep: Reputation: 40

Quote:
Originally Posted by Didier Spaier View Post
The kernel name should match the name used in elilo.conf.
Code:
cat /boot/efi/EFI/Slackware/elilo.conf
chooser=simple
delay=1
timeout=1
#
image=vmlinuz
label=vvmlinux
read-only
append="root=/dev/sda5 vga=normal ro"
 
Old 11-04-2018, 06:51 PM   #32
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,426

Rep: Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206
If you want to stick with elilo, make sure you copy the kernel you compiled into the /boot/efi/EFI/Slackware directory. Then you would need to add an entry to your /boot/efi/EFI/Slackware/elilo.conf file to point to the new kernel.

Something like:

Code:
image=vmlinuz-4.19.1
        label=Slack-4.19.1
        read-only
Once done, this should allow you to boot into the new kernel. Since you're still running 14.2, it is likely your pci database is far enough out of date to not provide you the names of your devices (this is likely why you're getting "Intel Corporation Device [8026:3e92]" as your output instead of a device name). To update your pci database, run the following command as root.

Code:
update-pciids
 
2 members found this post helpful.
Old 11-04-2018, 06:51 PM   #33
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.2 & -current
Posts: 692

Original Poster
Rep: Reputation: 40
Quote:
Originally Posted by Didier Spaier View Post
Then your card would not be not supported at all but by a very generic driver, which look weird.

Are you using a kernel and modules as shipped by Slackware?

Then try this as root:
cd /etc/X11
cp xorg.conf-vesa xorg.conf

You will have a very limited display, but at least X should start.
Nope.
 
Old 11-04-2018, 07:03 PM   #34
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.2 & -current
Posts: 692

Original Poster
Rep: Reputation: 40
Quote:
Originally Posted by bassmadrigal View Post
If you want to stick with elilo, make sure you copy the kernel you compiled into the /boot/efi/EFI/Slackware directory. Then you would need to add an entry to your /boot/efi/EFI/Slackware/elilo.conf file to point to the new kernel.

Something like:

Code:
image=vmlinuz-4.19.1
        label=Slack-4.19.1
        read-only
My /boot/efi/EFI/Slackware/elilo.conf is this
Code:
chooser=simple
delay=1
timeout=1
#
image=vmlinuz
label=vmlinuz
read-only
appen="root=/dev/sda5 vga=normal ro"
Quote:
Once done, this should allow you to boot into the new kernel. Since you're still running 14.2, it is likely your pci database is far enough out of date to not provide you the names of your devices (this is likely why you're getting "Intel Corporation Device [8026:3e92]" as your output instead of a device name). To update your pci database, run the following command as root.

Code:
update-pciids
After doing that, I get the exact the same output from lspci.
 
Old 11-04-2018, 07:34 PM   #35
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.2 & -current
Posts: 692

Original Poster
Rep: Reputation: 40
It's broken, won't boot.
I fucked up...
 
Old 11-04-2018, 08:18 PM   #36
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,426

Rep: Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206
If you completed the kernel compile, did you copy the resulting kernel to your /boot/efi/EFI/Slackware/ directory as the filename vmlinuz? The kernel image filename needs to match what you put in the elilo.conf file. Also, I'm not sure if it was just a mistype, but you have your append as appen. That could cause your system to not boot if it is in the actual elilo.conf and not just a mistype.

Can you provide the output of the following command?

Code:
ls -l /boot/efi/EFI/Slackware

Also, what are the steps you took to compile the 4.19.1 kernel? Where did you get your config for the kernel from? It'd be easiest to grab it from -current's config, and that should work fine to build your kernel with the right options.
 
1 members found this post helpful.
Old 11-05-2018, 05:31 AM   #37
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.2 & -current
Posts: 692

Original Poster
Rep: Reputation: 40
Quote:
Originally Posted by bassmadrigal View Post
If you completed the kernel compile, did you copy the resulting kernel to your /boot/efi/EFI/Slackware/ directory as the filename vmlinuz? The kernel image filename needs to match what you put in the elilo.conf file. Also, I'm not sure if it was just a mistype, but you have your append as appen. That could cause your system to not boot if it is in the actual elilo.conf and not just a mistype.

Can you provide the output of the following command?
Code:
ls -l /boot/efi/EFI/Slackware
Sorry, I can't, because it won't boot (and no USB-bootstick - where is the fun in that?)

Tried a live-dvd and that shows that /boot/efi is empty???

So this is what I'm gonna do:
Reinstall (there's nothing lost, was a brand new installation, not even users were added) and make a new kernel.
Quote:
Also, what are the steps you took to compile the 4.19.1 kernel? Where did you get your config for the kernel from? It'd be easiest to grab it from -current's config, and that should work fine to build your kernel with the right options.
I followed this:

https://blog.paranoidpenguin.net/201...ackware-linux/
Been using Slack for almost 15 years and made dozens of installations, but I'm a complete noob with this EFI and elilo stuff.
The laptop that I'm working on right now, well I just turned secure boot off.
But this time I decided to go along with the modern times...
 
Old 11-05-2018, 06:14 AM   #38
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,581

Rep: Reputation: Disabled
Quote:
Originally Posted by adriv View Post
Reinstall (there's nothing lost, was a brand new installation, not even users were added) and make a new kernel.
  1. You card is not that new that you should need a new kernel, from an internet search with "8086:0126" as search argument.
  2. If you want one, just install the one shipped in -current with all the associated packages, especially kernel-modules.
  3. Don't forget to make a *full* installation first, the see what happens *before* installing a new kernel.
 
1 members found this post helpful.
Old 11-05-2018, 06:44 AM   #39
chrisVV
Member
 
Registered: Aug 2010
Posts: 322

Rep: Reputation: 139Reputation: 139
Quote:
Originally Posted by adriv View Post
Code:
ls -l /boot/efi/EFI/Slackware
Sorry, I can't, because it won't boot (and no USB-bootstick - where is the fun in that?)

Tried a live-dvd and that shows that /boot/efi is empty???
That is because after booting up your live-dvd, you need to mount your EFI System Partition (probably /dev/sda1) on /boot/efi or on some other mount point provided by the live-dvd. You don't need to do that with a normal boot-up after installation, because /boot/efi would be automounted from the relevant entry in /etc/fstab.

As someone else has said, I should just install the 4.19.1 kernel packages from slackware-current over your slackware-14.2 kernel, and if that isn't sufficient to get your card working, recompile xf86-video-intel from slackware64-current/source/x/x11/src/driver/xf86-video-intel-20180906_25c9a2fc.tar.xz. Make sure you copy the new /boot/vmlinuz to /efi/boot/EFI/Slackware/vmlinuz, or run eliloconfig again, and the new kernel should just work. And make a usb stick from slackware64-current/usb-and-pxe-installers/usbboot.img so you can more easily manipulate your slackware-14.2 installation in rescue mode should the need arise.

Edit: And try kernel-huge initially so that you don't have to make an initrd. First things first.

Last edited by chrisVV; 11-05-2018 at 07:12 AM. Reason: refer to initrd
 
2 members found this post helpful.
Old 11-05-2018, 08:15 AM   #40
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.2 & -current
Posts: 692

Original Poster
Rep: Reputation: 40
Quote:
Originally Posted by Didier Spaier View Post
  1. You card is not that new that you should need a new kernel, from an internet search with "8086:0126" as search argument.
  2. If you want one, just install the one shipped in -current with all the associated packages, especially kernel-modules.
  3. Don't forget to make a *full* installation first, the see what happens *before* installing a new kernel.
Well, the hardware is apparently too new: running Mint-live (year old) runs X (but not great) and no sound (like in SW 14.2).
Ubuntu-live (a month old) runs X fine, and I have sound!
So I have good hopes that a new kernel might do the trick.

But first things first: I have the feeling that something (also?) went wrong with elilo because I never get a menu of choise when i boot (have to do that via BIOS). Am I correct that elilo has to be installed into /dev/sda1?
gdisk -l /dev/sda
Code:
1   2048   206847  100MiB   EF00   EFI System partition

Last edited by adriv; 11-05-2018 at 08:20 AM. Reason: typo
 
Old 11-05-2018, 08:26 AM   #41
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,581

Rep: Reputation: Disabled
Quote:
Originally Posted by adriv View Post
But first things first: I have the feeling that something (also?) went wrong with elilo because I never get a menu of choise when i boot
In Slackware elilo is set to boot directly, without a prompt.
 
Old 11-05-2018, 08:27 AM   #42
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,581

Rep: Reputation: Disabled
Quote:
Originally Posted by adriv View Post
But first things first: I have the feeling that something (also?) went wrong with elilo because I never get a menu of choise when i boot
In Slackware elilo is set by default to boot directly, without a prompt.
 
1 members found this post helpful.
Old 11-05-2018, 10:56 AM   #43
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.2 & -current
Posts: 692

Original Poster
Rep: Reputation: 40
Quote:
Originally Posted by chrisVV View Post
As someone else has said, I should just install the 4.19.1 kernel packages from slackware-current over your slackware-14.2 kernel, and if that isn't sufficient to get your card working, recompile xf86-video-intel from slackware64-current/source/x/x11/src/driver/xf86-video-intel-20180906_25c9a2fc.tar.xz. Make sure you copy the new /boot/vmlinuz to /efi/boot/EFI/Slackware/vmlinuz, or run eliloconfig again, and the new kernel should just work. And make a usb stick from slackware64-current/usb-and-pxe-installers/usbboot.img so you can more easily manipulate your slackware-14.2 installation in rescue mode should the need arise.

Edit: And try kernel-huge initially so that you don't have to make an initrd. First things first.
So I would only need
Code:
a/kernel-huge-4.19.1-x86_64-1.txz and
a/kernel-modules-4.19.1-x86_64-1.txz
and install them with installpkg?
That's it?
a/kernel-huge-4.19.1-x86_64-1.txz and
a/kernel-modules-4.19.1-x86_64-1.txz.
The problem for me- is that there is so much information on the internet and a lot of it is old or plainly wrong.
Sigh...
 
Old 11-05-2018, 11:13 AM   #44
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,426

Rep: Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206Reputation: 3206
Quote:
Originally Posted by adriv View Post
So I would only need
Code:
a/kernel-huge-4.19.1-x86_64-1.txz and
a/kernel-modules-4.19.1-x86_64-1.txz
and install them with installpkg?
That's it?
a/kernel-huge-4.19.1-x86_64-1.txz and
a/kernel-modules-4.19.1-x86_64-1.txz.
I would also recommend at least kernel-source, in case you need to compile your own modules.

Quote:
Originally Posted by adriv View Post
The problem for me- is that there is so much information on the internet and a lot of it is old or plainly wrong.
Sigh...
Unfortunately, this will always be the case. We try and keep https://docs.slackware.com up-to-date as people point out inaccuracies, but I imagine most don't go there looking at everything just to try and find old information.
 
1 members found this post helpful.
Old 11-05-2018, 11:51 AM   #45
chrisVV
Member
 
Registered: Aug 2010
Posts: 322

Rep: Reputation: 139Reputation: 139
Quote:
Originally Posted by adriv View Post
So I would only need
Code:
a/kernel-huge-4.19.1-x86_64-1.txz and
a/kernel-modules-4.19.1-x86_64-1.txz
and install them with installpkg?
That's it?
a/kernel-huge-4.19.1-x86_64-1.txz and
a/kernel-modules-4.19.1-x86_64-1.txz.
The problem for me- is that there is so much information on the internet and a lot of it is old or plainly wrong.
Sigh...
That should do it, save for what I say below. Personally, I would also use upgradepkg rather than installpkg so simultaneously removing the old kernel packages for slackware64-14.2 when installing the new ones for slackware64-current, because I know how to reinstall the old ones under a rescue disk if I wanted to. Using installpkg makes it easier to back out if you have a problem with the slackware64-current kernel, at the cost of possibly causing you to get confused about what kernel is what.

In what I say below I assume that you have slackware64-14.2 working, except for your video card. If that is the case you should have the following already installed in /boot/efi/EFI/Slackware (this is based on slackware64-current but I imagine slackware64-14.2 is the same): an EFI binary 'elilo.efi', a configuration file 'elilo.conf' and a kernel image 'vmlinuz'; and you should also have an entry for 'elilo.efi' registered with the UEFI system boot manager (do 'efibootmgr -v' to check). If this is not the case then run 'eliloconfig' and it should do all this for you again (although to register an entry with the UEFI system boot manager, efivarfs must be mounted write-read - by default I think it is although I do not have slackware64-14.2).

Assuming all that to be true you should only need to copy the kernel image /boot/vmlinuz-huge-4.19.1 installed from kernel-huge-4.19.1-x86_64-1.txz to /boot/efi/EFI/Slackware/vmlinuz (as an actual file copy, not as a symbolic link, so overwriting the previously existing vmlinuz file in /boot/efi/EFI/Slackware/). If the boot stanza in /boot/efi/EFI/Slackware/elilo.conf has an initrd line, delete it because kernel-huge does not use an initrd (that would be a stale entry arising from your installation of a slackware64-14.2's kernel-generic). It should then work.

Edit: when you get everything working I would be inclined to update kernel-firmware as well.

Second edit: At one time slackware64-14.2's elilo could not boot kernel images as big as the one produced by /boot/vmlinuz-huge-4.19.1. If that is still the case (and I do not know if it is or it isn't) you will need to upgrade elilo to slackware64-current's version. Having done that, copy the file /boot/elilo-x86_64.efi installed from elilo-3.16-x86_64-8.txz to /boot/efi/EFI/Slackware/elilo.efi.

Last edited by chrisVV; 11-05-2018 at 12:01 PM.
 
2 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Xorg, no screens found; no devices found (after Virtualbox install) Archytas Linux - General 6 03-06-2013 04:41 PM
No Screens Found jrock SUSE / openSUSE 5 12-20-2006 03:05 AM
No screens found spoody_goon Linux - Hardware 10 10-10-2004 05:36 PM
Please Help, No Screens Found! FuriousGibbon Linux - Newbie 25 03-16-2004 05:39 AM
x - 'no screens found' stilez Linux - Newbie 2 02-13-2004 03:48 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:40 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration