Slackware 14.2 graphical session manager doesn't get any keystroke

l0f4r0 · 07-23-2018, 11:45 PM

Quote:

Originally Posted by bassmadrigal

Did it run with any errors?

It ran with the following output:

Code:

Warning: LBA32 addressing assumed
Warning: Unable to determine video adapter in use in the present system
Warning: Video adapter does not support VESA BIOS extensions needed for display of 256 colors. Boot loader will fall back to TEXT only operation.
Added Linux *
3 warnings were issued.

It didn't seem there were errors then...

Quote:

Originally Posted by bassmadrigal

Do you know if you accidentally upgraded to -current?

How can I know it? Is there any command I can type please?
A priori the other day I only typed:

Code:

slackpkg update gpg
slackpkg update
slackpkg upgrade-all

It is not supposed to migrate me to current, is it?

Thank you very much.

bassmadrigal · 07-24-2018, 12:00 AM

Quote:

Originally Posted by l0f4r0

It ran with the following output:

Code:

Warning: LBA32 addressing assumed
Warning: Unable to determine video adapter in use in the present system
Warning: Video adapter does not support VESA BIOS extensions needed for display of 256 colors. Boot loader will fall back to TEXT only operation.
Added Linux *
3 warnings were issued.

It didn't seem there were errors then...

Those warnings are normal when you're chrooted, so it seems there's no problem with your lilo.

Quote:

Originally Posted by l0f4r0

How can I know it? Is there any command I can type please?

There's three ways. The first is to look at your /etc/slackware-version. If it contains a + symbol after the 14.2, then you're running -current. The other thing to check would be your /etc/slackpkg/mirrors file and see what mirror you enabled (which one has the # symbol removed. The final way is to verify what packages you have installed. One of the easiest would be the kernel. If you run the following command, if the version is 4.4.x, then you're on 14.2. If it is 4.14.x, then you're on -current (the 14.2 version uses kernels from the 4.4 series, while -current uses kernels from the 4.14 series).

Code:

ls -l /var/log/packages/kernel-huge-*

Quote:

Originally Posted by l0f4r0

A priori the other day I only typed:

Code:

slackpkg update gpg
slackpkg update
slackpkg upgrade-all

It is not supposed to migrate me to current, is it?

This all depends on what your slackpkg mirror was set to.

If it was set to -current, it would take a little extra effort to get everything working, but it's still certainly doable.

l0f4r0 · 07-24-2018, 03:33 PM

Hi bassmadrigal, all,

Thank you for your comprehensive but clear explanations.
Here are the results:

Quote:

Originally Posted by bassmadrigal

The first is to look at your /etc/slackware-version. If it contains a + symbol after the 14.2, then you're running -current.

Code:

# cat etc/slackware-version
Slackware 14.2

Quote:

Originally Posted by bassmadrigal

The other thing to check would be your /etc/slackpkg/mirrors file and see what mirror you enabled (which one has the # symbol removed.

Code:

# less etc/slackpkg/mirrors
...
http://mirror.switch.ch/ftp/mirror/slackware/slackware64-14.2/
...

Quote:

Originally Posted by bassmadrigal

The final way is to verify what packages you have installed. One of the easiest would be the kernel. If you run the following command, if the version is 4.4.x, then you're on 14.2. If it is 4.14.x, then you're on -current (the 14.2 version uses kernels from the 4.4 series, while -current uses kernels from the 4.14 series).

Code:

ls -l /var/log/packages/kernel-huge-*

Code:

# find bar/log/packages -iname '*kernel-huge-*'
var/log/packages/kernel-huge-4.4.132-x86_64-1

I suppose now I'm not using -current evidently but 14.2 64bits

Apart from this, it's weird because I've just ran:

Code:

# slackpkg update gpg
# slackpkg update
# slackpkg install-new

and I've gotten full packages like

Code:

amor-4.14.3-x86_64-2.txz
artikulate-4.14.3-x86_64-2.txz
...
umbrello-4.14.3-x86_64-2.txz
zeroconf-ioslave-4.14.3-x86_64-2.txz

Weird because we've seen earlier that this was really rare that new packages appeared for the stable version... More, it seems from ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt that they all refered to KDE and were rebuilt on 29/10/2015 (even though 14.2 version was released on 01/07/2016!)
Can somebody explain me please this behavior and which steps I should follow next?

Thanks.

bassmadrigal · 07-24-2018, 05:30 PM

Ok, you are definitely running 14.2. That's good. As far as the install-new, it will prompt for any packages that were added during the 14.2 process that are not currently installed. Based on the output, I'm guessing you left out the kde/ series. That shouldn't be an issue (it also won't hurt if you install them).

The next thing to check is if your kernel is fully installed and referenced properly. Can you provide us the output of the following commands?

Code:

ls -l /boot/
ls -l /var/log/packages/kernel-*

And can you provide the contents of your /etc/lilo.conf file?

l0f4r0 · 07-25-2018, 07:07 PM

Quote:

Originally Posted by bassmadrigal

As far as the install-new, it will prompt for any packages that were added during the 14.2 process that are not currently installed. Based on the output, I'm guessing you left out the kde/ series. That shouldn't be an issue (it also won't hurt if you install them).

Hummm... so 'slackpkg install-new command' will suggest me to install every package composing the 14.2 basic release that I refused to install initially + rare ones added for security reasons during the stable version lifecycle?

Quote:

Originally Posted by bassmadrigal

Can you provide us the output of the following commands?

Code:

ls -l /boot/

Code:

total 19412
drwxr-xr-x  3 root root    4096 Jul 23 05:00 .
drwxr-xr-x 22 root root    4096 Jul 25  2018 ..
lrwxrwxrwx  1 root root      38 Jul 14 22:34 README.initrd -> /usr/doc/mkinitrd-1.4.10/README.initrd
lrwxrwxrwx  1 root root      23 Jul 14 22:26 System.map -> System.map-huge-4.4.132
-rw-r--r--  1 root root 2742676 May 21 22:28 System.map-generic-4.4.132
-rw-r--r--  1 root root 3976823 May 21 22:39 System.map-huge-4.4.132
-rw-r--r--  1 root root     512 Jul  6 09:50 boot.0800
-rw-r--r--  1 root root     168 Jul  6 09:50 boot_message.txt
-rw-r--r--  1 root root     426 Apr 21  2016 coffee.dat
lrwxrwxrwx  1 root root      19 Jul 14 22:26 config -> config-huge-4.4.132
-rw-r--r--  1 root root  160097 May 21 22:28 config-generic-4.4.132
-rw-r--r--  1 root root  160097 May 21 22:39 config-huge-4.4.132
-rwxr-xr-x  1 root root  215987 Nov 20  2017 elilo-ia32.efi
-rwxr-xr-x  1 root root  237749 Nov 20  2017 elilo-x86_64.efi
drwxr-xr-x  2 root root    4096 Jun 13  2016 grub
-rw-r--r--  1 root root   22578 Apr 21  2016 inside.bmp
-rw-r--r--  1 root root     432 Apr 21  2016 inside.dat
-rw-------  1 root root  107008 Jul 23 05:00 map
-rw-r--r--  1 root root    6878 Apr 21  2016 onlyblue.bmp
-rw-r--r--  1 root root     424 Apr 21  2016 onlyblue.dat
-rw-r--r--  1 root root   15634 Mar 27  2011 slack.bmp
-rw-r--r--  1 root root   33192 Apr 21  2016 tuxlogo.bmp
-rw-r--r--  1 root root     423 Apr 21  2016 tuxlogo.dat
lrwxrwxrwx  1 root root      20 Jul 14 22:26 vmlinuz -> vmlinuz-huge-4.4.132
lrwxrwxrwx  1 root root      23 Jul 14 22:26 vmlinuz-generic -> vmlinuz-generic-4.4.132
-rw-r--r--  1 root root 4429168 May 21 22:28 vmlinuz-generic-4.4.132
lrwxrwxrwx  1 root root      20 Jul 14 22:26 vmlinuz-huge -> vmlinuz-huge-4.4.132
-rw-r--r--  1 root root 7697200 May 21 22:39 vmlinuz-huge-4.4.132

Quote:

Originally Posted by bassmadrigal

Can you provide us the output of the following commands?

Code:

ls -l /var/log/packages/kernel-*

Code:

-rw-r--r-- 1 root root   62119 Jul 14 22:26 /var/log/packages/kernel-firmware-20180518_2a9b2cf-noarch-1
-rw-r--r-- 1 root root     976 Jul 14 22:26 /var/log/packages/kernel-generic-4.4.132-x86_64-1
-rw-r--r-- 1 root root   25089 Jul 14 22:26 /var/log/packages/kernel-headers-4.4.132-x86-1
-rw-r--r-- 1 root root     972 Jul 14 22:26 /var/log/packages/kernel-huge-4.4.132-x86_64-1
-rw-r--r-- 1 root root  253534 Jul 14 22:27 /var/log/packages/kernel-modules-4.4.132-x86_64-1
-rw-r--r-- 1 root root 3479145 Jul 14 22:32 /var/log/packages/kernel-source-4.4.132-noarch-1

Quote:

Originally Posted by bassmadrigal

And can you provide the contents of your /etc/lilo.conf file?

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=1"
boot = /dev/sda

#compact        # faster, but won't work on all systems.

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and 
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux
  read-only
# Linux bootable partition config ends

bassmadrigal · 07-27-2018, 11:47 AM

Sorry for the delay, I didn't have any time yesterday to be on the computer.

Quote:

Originally Posted by l0f4r0

Hummm... so 'slackpkg install-new command' will suggest me to install every package composing the 14.2 basic release that I refused to install initially + rare ones added for security reasons during the stable version lifecycle?

Not exactly. It will only prompt for programs that were "added" in the development cycle. It won't necessarily include every package you didn't select during the initial install unless that package was added during the 14.2 development cycle.

As for everything else, it looks normal, so I'm at a loss on why you're running into this issue. Do you happen to have another computer (or even a phone) that you can use to ssh into the computer and look at dmesg output? That may help us figure out why it isn't working properly.

As an alternative, you could try building an initrd and switching to the generic kernel. You'd have to do this after booting up the installation disk and chrooting as you did before. Then you'd run something like the following to generate your initrd and place it into /boot/.

Code:

$(/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.132)

Once that is done, you'd simply make a new entry in your lilo.conf for the generic kernel and the initrd. Add the red text right above your current entry (the black text).

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.4.132
  initrd = /boot/initrd.gz
  label = Linux
  read-only
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux
  read-only
# Linux bootable partition config ends

Once done, save the file and then run lilo -v and paste the output here (just for us to verify what happened). If there's no errors (warnings are usually fine), go ahead and reboot and see if things work again.

l0f4r0 · 07-30-2018, 03:54 PM

Hello bassmadrigal,

Sorry as well for the delay

Quote:

Originally Posted by bassmadrigal

Not exactly. It will only prompt for programs that were "added" in the development cycle. It won't necessarily include every package you didn't select during the initial install unless that package was added during the 14.2 development cycle.

But I was told almost nothing was added between 2 stable versions (except for a security purpose which is really rare)...
Proof, I cannot see any additional stuff in the official ChangeLog (ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt) since the 14.2 x86_64 stable release.
Could you explain me again please?

Tell what? I definitely have a problem with booting because my GRUB is stuck with "Welcome to GRUB!". Nothing more is displayed and nothing will happen.
However, I didn't install or setup GRUB intentionally, I'm pretty sure because I don't want GRUB but LILO...
That's why I'm required to boot on the install DVD and then launch huge.s kernel manually and so on... Except that the next part doesn't work either as I'm stuck with the graphical session manager.
So to conclude, nothing works, no GRUB, no LILO, no huge.s manual launch. I can only boot on install DVD, type boot, select my keymap, login as root, chrooting etc.

Quote:

Originally Posted by bassmadrigal

As for everything else, it looks normal, so I'm at a loss on why you're running into this issue. Do you happen to have another computer (or even a phone) that you can use to ssh into the computer and look at dmesg output? That may help us figure out why it isn't working properly.

See my dmesg atttached (happy reading).

Quote:

Originally Posted by bassmadrigal

As an alternative, you could try building an initrd and switching to the generic kernel. You'd have to do this after booting up the installation disk and chrooting as you did before. Then you'd run something like the following to generate your initrd and place it into /boot/.

It's weird because

Code:

./mkinitrd_command-generator.sh

gave me

Code:

Modules for kernel 4.4.14 aren't installed.

Why does it specify kernel 4.4.14 whereas I'm using kernel 4.4.132? I don't understand...

bassmadrigal · 07-30-2018, 05:54 PM

Quote:

Originally Posted by l0f4r0

But I was told almost nothing was added between 2 stable versions (except for a security purpose which is really rare)...
Proof, I cannot see any additional stuff in the official ChangeLog (ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt) since the 14.2 x86_64 stable release.
Could you explain me again please?

Sorry for the confusion. The install-new will look over that whole changelog to look for added programs, not just since the release of 14.2, but since the development of 14.2 started (which was right after the release of 14.1).

Quote:

Originally Posted by l0f4r0

Tell what? I definitely have a problem with booting because my GRUB is stuck with "Welcome to GRUB!". Nothing more is displayed and nothing will happen.
However, I didn't install or setup GRUB intentionally, I'm pretty sure because I don't want GRUB but LILO...
That's why I'm required to boot on the install DVD and then launch huge.s kernel manually and so on... Except that the next part doesn't work either as I'm stuck with the graphical session manager.
So to conclude, nothing works, no GRUB, no LILO, no huge.s manual launch. I can only boot on install DVD, type boot, select my keymap, login as root, chrooting etc.

See my dmesg atttached (happy reading).

It's weird because

Code:

./mkinitrd_command-generator.sh

gave me

Code:

Modules for kernel 4.4.14 aren't installed.

Why does it specify kernel 4.4.14 whereas I'm using kernel 4.4.132? I don't understand...

When you boot off the install disk, it uses that kernel, not the one installed on your system. So, when you run mkinitrd_command_generator.sh, you need to specify a different kernel using the -k parameter:

Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.132

But if you're still booting up and seeing grub, then there's something up, because running lilo in your chroot should've replaced grub. Do you only have one harddrive or multiples? Looking over your dmesg, it looks like you have /dev/sda and /dev/sdb, but it looks like /dev/sdb is a thumbdrive (and that was added way after the bootup completed, possibly for you to save the output of dmesg to).

Basically, once you are chrooted and you run lilo, it should replace grub. Then when you reboot, it should show lilo and then allow you to boot up the proper kernel. You shouldn't need to create a initrd (although, it is recommended by Pat, but it does add some steps, so it might be easier to skip it for now). When you do run lilo, I'd suggest running lilo -v and paste the information here. If you still run into issues, that output could help us solve the issue.

l0f4r0 · 07-31-2018, 03:01 PM

Quote:

Originally Posted by bassmadrigal

Sorry for the confusion. The install-new will look over that whole changelog to look for added programs, not just since the release of 14.2, but since the development of 14.2 started (which was right after the release of 14.1).

Ok, so if I have quite understood, 14.2 development began just after 14.1 release and install-new command will look for every packages added during this development but not incorporated into stable 14.2. That's right?

Quote:

Originally Posted by bassmadrigal

Do you only have one harddrive or multiples? Looking over your dmesg, it looks like you have /dev/sda and /dev/sdb, but it looks like /dev/sdb is a thumbdrive (and that was added way after the bootup completed, possibly for you to save the output of dmesg to).

You're totally correct!

Quote:

Originally Posted by bassmadrigal

When you do run lilo, I'd suggest running lilo -v and paste the information here. If you still run into issues, that output could help us solve the issue.

Please see attached.

bassmadrigal · 07-31-2018, 03:15 PM

Quote:

Originally Posted by l0f4r0

Ok, so if I have quite understood, 14.2 development began just after 14.1 release and install-new command will look for every packages added during this development but not incorporated into stable 14.2. That's right?

Exactly!

Quote:

Originally Posted by l0f4r0

Please see attached.

That looks normal. So it seems like your /etc/lilo.conf and kernels are all working as they should. But it still doesn't work when you reboot? Do you still get grub or lilo when you boot? Do you have the boot priority selected properly in your BIOS/UEFI firmware?

bassmadrigal · 07-31-2018, 03:17 PM

I guess one other thing to check and verify is that /dev/sda does actually point to your harddrive and not your thumbdrive or cd drive. Can you provide the output of lsblk once in the chroot?

l0f4r0 · 07-31-2018, 03:45 PM

Quote:

Originally Posted by bassmadrigal

Can you provide the output of lsblk once in the chroot?

Code:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 465.8G  0 disk 
|-sda1   8:1    0     4G  0 part 
`-sda2   8:2    0 461.8G  0 part /
sdb      8:16   1  29.9G  0 disk 
`-sdb1   8:17   1  29.9G  0 part /mnt/memory
sr0     11:0    1   2.6G  0 rom

bassmadrigal · 07-31-2018, 03:52 PM

In case you missed my other questions...

Do you still get grub or lilo when you boot? Do you have the boot priority selected properly in your BIOS/UEFI firmware?

l0f4r0 · 07-31-2018, 04:02 PM

While I was on that, I've migrated to the generic kernel with initrd creation following those steps (tell me if I was wrong please):

1) creation of /etc/mkinitrd.conf with the following (thanks to the help of "/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.132" command):

Code:

SOURCE_TREE="/boot/initrd-tree"
CLEAR_TREE="1"
OUTPUT_IMAGE="/boot/initrd.gz"
KERNEL_VERSION="4.4.132"
KEYMAP="fr-latin9"
MODULE_LIST="usb-storage:ehci-hcd:ehci-pci:xhci-pci:ohci-pci:xhci-hcd:uhci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4" 
ROOTDEV="/dev/sda2"
ROOTFS="ext4"
RESUMEDEV="/dev/sda2"
RAID="0"
LVM="0"
UDEV="1"
MODCONF="0"
WAIT="1"

2) creation of initrd with "mkinitrd -F" command". Output:

Code:

OK: /lib/modules/4.4.132/kernel/drivers/usb/storage/usb-storage.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/usb/host/ehci-hcd.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/usb/host/ehci-hcd.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/usb/host/ehci-pci.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/usb/host/xhci-hcd.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/usb/host/xhci-pci.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/usb/host/ehci-hcd.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/usb/host/ohci-hcd.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/usb/host/ohci-pci.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/usb/host/xhci-hcd.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/usb/host/uhci-hcd.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/usbhid/usbhid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/i2c/i2c-core.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/i2c-hid/i2c-hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid-generic.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid-cherry.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid-logitech.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid-logitech-dj.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid-logitech-hidpp.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid-lenovo.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid-microsoft.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/4.4.132/kernel/drivers/hid/hid-multitouch.ko added.
OK: /lib/modules/4.4.132/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/4.4.132/kernel/fs/mbcache.ko added.
OK: /lib/modules/4.4.132/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/4.4.132/kernel/fs/mbcache.ko added.
OK: /lib/modules/4.4.132/kernel/fs/ext4/ext4.ko added.
/boot/initrd.gz created.
Be sure to run lilo again if you use it.

3) edition of lilo.conf as follows:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=1"
boot = /dev/sda

#compact        # faster, but won't work on all systems.

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and 
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.4.132
  initrd = /boot/initrd.gz
  root = /dev/sda2
  label = Linux-Generic
  read-only
image = /boot/vmlinuz-huge-4.4.132
  root = /dev/sda2
  label = Linux-Huge
  read-only
# Linux bootable partition config ends

4) launch of "lilo -v". Output:

Code:

LILO version 24.2 (released 22-November-2015)
  * Copyright (C) 1992-1998 Werner Almesberger  (until v20)
  * Copyright (C) 1999-2007 John Coffman  (until v22)
  * Copyright (C) 2009-2015 Joachim Wiedorn  (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software 
distributed under the BSD License (3-clause). Details can be found in 
the file COPYING, which is distributed with this software.

Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda
Warning: Unable to determine video adapter in use in the present system.
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/slack.bmp
Warning: Video adapter does not support VESA BIOS extensions needed for
  display of 256 colors.  Boot loader will fall back to TEXT only operation.
Calling map_insert_file

Boot image: /boot/vmlinuz-generic-4.4.132
Mapping RAM disk /boot/initrd.gz
The initial RAM disk will be loaded in the high memory above 16M.
Added Linux-Generic  +  *

Boot image: /boot/vmlinuz-huge-4.4.132
Added Linux-Huge

Writing boot sector.
/boot/boot.0800 exists - no boot sector backup copy made.
3 warnings were issued.

Quote:

Originally Posted by bassmadrigal

Do you still get grub or lilo when you boot?

I'm still getting GRUB which freezes at "Welcome to GRUB!"...

l0f4r0 · 07-31-2018, 04:27 PM

Quote:

Originally Posted by l0f4r0

I'm still getting GRUB which freezes at "Welcome to GRUB!"...

Erratum, GRUB eventually loads itself and prompt the following:

Code:

GNU GRUB version 2.00
Slackware 14.2 huge.s kernel
Slackware 14.2 huge.s kernel (use KMS console)
Detect/boot any installed operating system

I've selected 1st choice, it states "Loading huge.s kernel and installer initrd. Please wait..." but nothing changes or is displayed.

Maybe I could try to uninstall GRUB in order to give priority to LILO?

Quote:

Originally Posted by bassmadrigal

Do you have the boot priority selected properly in your BIOS/UEFI firmware?

I've searched on the internet but I don't succeed in accessing BIOS/UEFI on my Mac...
If somebody has got the proper key sequence to type, I'm taking it!
By the way, are we sure all my problems are not Mac related (I have a 2008 MacBook or something like that)? I'm skeptical with Mac, sometimes they lock down everything so you cannot do what you want...