System freeze on login page on my multiboot machine

Gorštak · 03-24-2019, 05:27 PM

I have a slackware installed along with some others linux distros. I configured lilo, installed it on MBR on my sdb drive that is booted from bios. I can boot into slackware, but booting into other distros isnt working so far. I get to login screen, where system freeze and it is unresponsive to keyboard and mouse. I have to shut down the machine using the power button.

lilo.conf

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sdb

#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

# Append any additional kernel parameters:
append=" vt.default_utf8=1"
prompt
timeout = 50
# 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
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb7
  label = slackware
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb2
  label = fedora
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb3
  label = manjaro
# read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb6
  label = solus
# read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb8
  label = opensuse
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb9
  label = mageia
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb10
  label = calculate
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/sdb1
  label = w7
#  map-drive = 0x80
#   to = 0x81
#  map-drive = 0x81
#   to = 0x80
  table = /dev/sdb
# Windows bootable partition config ends

lilo-error.2972

Code:

Warning: LBA32 addressing assumed
Warning: /dev/sdb is not on the first disk
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.

business_kid · 03-25-2019, 06:06 AM

Are you booting in console mode (runlevel 3) or graphical (runlevel 4)? If that's the only system you have going, what's up with the others. Are you logged in when it freezes?

You can get in by booting on the install cd, log in as root, and then running

Code:

mount <your root drive> /mnt

Then check the logs (/mnt/var/log/messages) dmesg (/mnt/var/log/dmesg) and tell us errors. Resist the urge some get to post 2 miles of logs. We don't want them. Just the errors.

Gorštak · 03-26-2019, 04:53 AM

I can boot into slackware, it boots into console mode and i run startx manually. Other distros freezes on login/greeter screen, before I can enter login password. Cursor blinks for a few seconds in password field and then it stops too. Mouse and keyboard are unresponsive the whole time. Fedora freezes before login screen, on

Code:

Started GNOME Display Manager.

All distros can be booted using other grubs, only using slackware's lilo I can't pass the login screen.

business_kid · 03-26-2019, 08:00 AM

Well, if you can boot slackware, that's good. You're a Slacker

If you have a range of distros you want to get running, yopu can mount their root drives in slackware as in my last post and pore over the entrails of their logs there. You can also change their /etc/inittab, the initdefault line which says

Code:

id:<number>:initdefault

and set that to 3. Then run

Code:

startx >~/xerrors.log 2>&1

When it pukes, try Ctrl_Alt_Backspace, and go looking at the log. Post any errors and what it pukes on. That should work for most distros.

Gorštak · 03-27-2019, 03:09 AM

I have another drive with debian grub on its MBR, and from there I can boot into all inistalled distros, including slackware, so there isnt a problem in those distros itself. I can boot into any of the distro and browse trough its logs, but i dont know exactly what to look for, they dont have messages nor dmesg files.
I wanted to try slackware and I want to try LILO to check how it works with other distros, but so far it can only boot into slackware, win10 and win7. Every other distro freeze on login screen or before. It has to be something with LILO and the slackware boot method, because with grub it works fine.

Quote:

Originally Posted by business_kid

You can also change their /etc/inittab

Linux Mint, Debian, Ubuntu, they dont have an inittab. Fedora have one:

Code:

# inittab is no longer used.
#
# ADDING CONFIGURATION HERE WILL HAVE NO EFFECT ON YOUR SYSTEM.
#
# Ctrl-Alt-Delete is handled by /usr/lib/systemd/system/ctrl-alt-del.target
#
# systemd uses 'targets' instead of runlevels. By default, there are two main targets:
#
# multi-user.target: analogous to runlevel 3
# graphical.target: analogous to runlevel 5
#
# To view current default target, run:
# systemctl get-default
#
# To set a default target, run:
# systemctl set-default TARGET.target

For instance, logs from Linux Mint after unsuccessful boot using LILO (i checked last edited files):

Xorg0.log

Code:

[     8.964] 	GreenFieldPosition: 8
[     8.964] 	BlueMaskSize: 8
[     8.964] 	BlueFieldPosition: 0
[     8.964] 	RsvdMaskSize: 0
[     8.964] 	RsvdFieldPosition: 0
[     8.964] 	DirectColorModeInfo: 0
[     8.964] 	PhysBasePtr: 0xd0000000
[     8.964] 	LinBytesPerScanLine: 6912
[     8.964] 	BnkNumberOfImagePages: 1
[     8.964] 	LinNumberOfImagePages: 1
[     8.964] 	LinRedMaskSize: 8
[     8.964] 	LinRedFieldPosition: 16
[     8.964] 	LinGreenMaskSize: 8
[     8.964] 	LinGreenFieldPosition: 8
[     8.964] 	LinBlueMaskSize: 8
[     8.964] 	LinBlueFieldPosition: 0
[     8.964] 	LinRsvdMaskSize: 0
[     8.964] 	LinRsvdFieldPosition: 0
[     8.964] 	MaxPixelClock: 400000000
[     8.964] 
[     8.964] (II) VESA(0): Total Memory: 256 64KB banks (16384kB)
[     8.964] (II) VESA(0): <default monitor>: Using hsync range of 30.00-82.00 kHz
[     8.964] (II) VESA(0): <default monitor>: Using vrefresh range of 50.00-75.00 Hz
[     8.964] (II) VESA(0): <default monitor>: Using maximum pixel clock of 175.00 MHz
[     8.964] (WW) VESA(0): Unable to estimate virtual size
[     8.964] (II) VESA(0): Not using built-in mode "1400x1050" (no mode of this name)
[     8.964] (--) VESA(0): Virtual size is 1680x1200 (pitch 1680)
[     8.964] (**) VESA(0): *Built-in mode "1600x1200"
[     8.964] (**) VESA(0): *Built-in mode "1680x1050"
[     8.964] (**) VESA(0): *Built-in mode "1280x1024"
[     8.964] (**) VESA(0): *Built-in mode "1280x960"
[     8.964] (**) VESA(0): *Built-in mode "1024x768"
[     8.964] (**) VESA(0): *Built-in mode "800x600"
[     8.964] (**) VESA(0): *Built-in mode "640x480"
[     8.964] (**) VESA(0): Display dimensions: (500, 290) mm
[     8.964] (**) VESA(0): DPI set to (85, 105)
[     8.964] (**) VESA(0): Using "Shadow Framebuffer"
[     8.964] (II) Loading sub module "shadow"
[     8.964] (II) LoadModule: "shadow"
[     8.965] (II) Loading /usr/lib/xorg/modules/libshadow.so
[     8.965] (II) Module shadow: vendor="X.Org Foundation"
[     8.965] 	compiled for 1.19.6, module version = 1.1.0
[     8.965] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     8.965] (II) Loading sub module "fb"
[     8.965] (II) LoadModule: "fb"
[     8.965] (II) Loading /usr/lib/xorg/modules/libfb.so
[     8.966] (II) Module fb: vendor="X.Org Foundation"
[     8.966] 	compiled for 1.19.6, module version = 1.0.0
[     8.966] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     8.966] (==) Depth 24 pixmap format is 32 bpp
[     8.966] (II) Loading sub module "int10"
[     8.966] (II) LoadModule: "int10"
[     8.967] (II) Loading /usr/lib/xorg/modules/libint10.so
[     8.967] (II) Module int10: vendor="X.Org Foundation"
[     8.967] 	compiled for 1.19.6, module version = 1.0.0
[     8.967] 	ABI class: X.Org Video Driver, version 23.0
[     8.967] (II) VESA(0): initializing int10
[     8.967] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[     8.967] (II) VESA(0): VESA BIOS detected
[     8.967] (II) VESA(0): VESA VBE Version 3.0
[     8.967] (II) VESA(0): VESA VBE Total Mem: 16384 kB
[     8.967] (II) VESA(0): VESA VBE OEM: AMD ATOMBIOS
[     8.967] (II) VESA(0): VESA VBE OEM Software Rev: 15.42
[     8.967] (II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2010, Advanced Micro Devices, Inc.
[     8.967] (II) VESA(0): VESA VBE OEM Product: OLAND
[     8.967] (II) VESA(0): VESA VBE OEM Product Rev: 01.00
[     8.967] (II) VESA(0): virtual address = 0x7fcd5d63f000,
	physical address = 0xd0000000, size = 16777216
[     9.061] (II) VESA(0): Setting up VESA Mode 0x176 (1600x1200)
[     9.061] (II) VESA(0): VBESetVBEMode failed, mode set without customized refresh.
[     9.170] (==) VESA(0): Default visual is TrueColor
[     9.172] (==) VESA(0): Backing store enabled
[     9.172] (==) VESA(0): DPMS enabled
[     9.173] (==) RandR enabled
[     9.176] (II) SELinux: Disabled on system
[     9.176] (II) AIGLX: Screen 0 is not DRI2 capable
[     9.176] (EE) AIGLX: reverting to software rendering
[     9.247] (EE) AIGLX error: amdgpu does not export required DRI extension
[     9.258] (EE) GLX: could not load software renderer
[     9.258] (II) GLX: no usable GL providers found for screen 0

syslog

Code:

Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5764] dhcp-init: Using DHCP client 'dhclient'
Mar 27 09:16:22 t1500 nm-dispatcher: req:1 'hostname': new request (1 scripts)
Mar 27 09:16:22 t1500 nm-dispatcher: req:1 'hostname': start running ordered scripts...
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5782] Loaded device plugin: NMBondDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5783] Loaded device plugin: NMBridgeDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5783] Loaded device plugin: NMDummyDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5783] Loaded device plugin: NMEthernetDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5783] Loaded device plugin: NMInfinibandDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5784] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5784] Loaded device plugin: NMMacsecDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5784] Loaded device plugin: NMMacvlanDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5784] Loaded device plugin: NMPppDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5785] Loaded device plugin: NMTunDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5785] Loaded device plugin: NMVethDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5785] Loaded device plugin: NMVlanDeviceFactory (internal)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5785] Loaded device plugin: NMVxlanDeviceFactory (internal)
Mar 27 09:16:22 t1500 systemd[1]: Started Light Display Manager.
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.5998] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-team.so)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.6003] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.6026] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.6055] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.6057] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.6094] device (lo): carrier: link connected
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.6100] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.6163] modem-manager: ModemManager available
Mar 27 09:16:22 t1500 NetworkManager[881]: <info>  [1553674582.6165] manager: startup complete
Mar 27 09:16:22 t1500 systemd[1]: Started Disk Manager.
Mar 27 09:16:22 t1500 udisksd[760]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Mar 27 09:16:22 t1500 systemd[1]: Reached target Graphical Interface.
Mar 27 09:16:22 t1500 systemd[1]: Starting Update UTMP about System Runlevel Changes...
Mar 27 09:16:22 t1500 systemd[1]: Started Stop ureadahead data collection 45s after completed startup.
Mar 27 09:16:22 t1500 systemd[1]: Started Update UTMP about System Runlevel Changes.
Mar 27 09:16:23 t1500 avahi-daemon[778]: Server startup complete. Host name is t1500.local. Local service cookie is 1273308523.
Mar 27 09:16:23 t1500 systemd[1]: Created slice User Slice of lightdm.
Mar 27 09:16:23 t1500 systemd[1]: Starting User Manager for UID 111...
Mar 27 09:16:23 t1500 systemd[1]: Started Session c1 of user lightdm.
Mar 27 09:16:23 t1500 systemd[1]: Started Daily apt upgrade and clean activities.
Mar 27 09:16:23 t1500 systemd[1115]: Reached target Timers.
Mar 27 09:16:23 t1500 systemd[1115]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 27 09:16:23 t1500 systemd[1115]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 27 09:16:23 t1500 systemd[1115]: Listening on GnuPG network certificate management daemon.
Mar 27 09:16:23 t1500 systemd[1115]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 27 09:16:23 t1500 systemd[1115]: Reached target Paths.
Mar 27 09:16:23 t1500 systemd[1115]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 27 09:16:23 t1500 systemd[1115]: Starting D-Bus User Message Bus Socket.
Mar 27 09:16:23 t1500 systemd[1115]: Listening on D-Bus User Message Bus Socket.
Mar 27 09:16:23 t1500 systemd[1115]: Reached target Sockets.
Mar 27 09:16:23 t1500 systemd[1115]: Reached target Basic System.
Mar 27 09:16:23 t1500 systemd[1115]: Reached target Default.
Mar 27 09:16:23 t1500 systemd[1115]: Startup finished in 47ms.
Mar 27 09:16:23 t1500 systemd[1]: Started User Manager for UID 111.
Mar 27 09:16:23 t1500 systemd[1]: Startup finished in 3.508s (kernel) + 5.877s (userspace) = 9.386s.
Mar 27 09:16:23 t1500 systemd[1115]: Started D-Bus User Message Bus.
Mar 27 09:16:23 t1500 dbus-daemon[1157]: [session uid=111 pid=1157] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=111 pid=1154 comm="/usr/sbin/slick-greeter ")
Mar 27 09:16:23 t1500 dbus-daemon[1157]: [session uid=111 pid=1157] Successfully activated service 'ca.desrt.dconf'
Mar 27 09:16:23 t1500 /slick-greeter-check-hidpi: Window scale: 1
Mar 27 09:16:23 t1500 /slick-greeter-set-keyboard-layout: Current keyboard configuration: rules:      evdev#012model:      pc105#012layout:     us
Mar 27 09:16:23 t1500 /slick-greeter-set-keyboard-layout: Applying keyboard configuration: ['setxkbmap', '-model', 'pc105', '-layout', 'rs', '-variant', 'latin', '-option', '', '-v']
Mar 27 09:16:23 t1500 /slick-greeter-set-keyboard-layout: Result: Warning! Multiple definitions of keyboard model#012         Using command line, ignoring X server#012Warning! Multiple definitions of keyboard layout#012         Using command line, ignoring X server#012Trying to build keymap using the following components:#012keycodes:   evdev+aliases(qwerty)#012types:      complete#012compat:     complete#012symbols:    pc+rs(latin)+inet(evdev)#012geometry:   pc(pc105)
Mar 27 09:16:23 t1500 /slick-greeter-set-keyboard-layout: New keyboard configuration: rules:      evdev#012model:      pc105#012layout:     rs#012variant:    latin
Mar 27 09:16:23 t1500 dbus-daemon[1157]: [session uid=111 pid=1157] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.1' (uid=111 pid=1154 comm="/usr/sbin/slick-greeter ")
Mar 27 09:16:23 t1500 systemd[1115]: Starting Virtual filesystem service...
Mar 27 09:16:23 t1500 dbus-daemon[1157]: [session uid=111 pid=1157] Successfully activated service 'org.gtk.vfs.Daemon'
Mar 27 09:16:23 t1500 systemd[1115]: Started Virtual filesystem service.
Mar 27 09:16:23 t1500 gvfsd[1181]: fuse: device not found, try 'modprobe fuse' first
Mar 27 09:16:23 t1500 dbus-daemon[843]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.27' (uid=111 pid=1154 comm="/usr/sbin/slick-greeter ")
Mar 27 09:16:23 t1500 systemd[1]: Starting Daemon for power management...
Mar 27 09:16:23 t1500 dbus-daemon[843]: [system] Successfully activated service 'org.freedesktop.UPower'
Mar 27 09:16:23 t1500 systemd[1]: Started Daemon for power management.

auth.log

Code:

Mar 27 09:16:22 t1500 systemd-logind[792]: New seat seat0.
Mar 27 09:16:23 t1500 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Mar 27 09:16:23 t1500 lightdm: PAM adding faulty module: pam_kwallet.so
Mar 27 09:16:23 t1500 lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Mar 27 09:16:23 t1500 lightdm: PAM adding faulty module: pam_kwallet5.so
Mar 27 09:16:23 t1500 lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Mar 27 09:16:23 t1500 systemd-logind[792]: New session c1 of user lightdm.
Mar 27 09:16:23 t1500 systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Mar 27 09:16:23 t1500 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Mar 27 09:16:23 t1500 lightdm: PAM adding faulty module: pam_kwallet.so
Mar 27 09:16:23 t1500 lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Mar 27 09:16:23 t1500 lightdm: PAM adding faulty module: pam_kwallet5.so
Mar 27 09:16:23 t1500 lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "sloter"

kern.log

Code:

Mar 27 09:16:22 t1500 kernel: [    1.392086] tsc: Refined TSC clocksource calibration: 2925.999 MHz
Mar 27 09:16:22 t1500 kernel: [    1.392209] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2a2d33743a4, max_idle_ns: 440795298620 ns
Mar 27 09:16:22 t1500 kernel: [    2.392433] clocksource: Switched to clocksource tsc
Mar 27 09:16:22 t1500 kernel: [    3.436256] floppy0: no floppy controllers found
Mar 27 09:16:22 t1500 kernel: [    3.437096] scsi 0:0:0:0: Direct-Access     ATA      KINGSTON SV300S3 BBF1 PQ: 0 ANSI: 5
Mar 27 09:16:22 t1500 kernel: [    3.437619] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
Mar 27 09:16:22 t1500 kernel: [    3.437839] scsi 0:0:1:0: Direct-Access     ATA      WDC WD10EARS-00Y 0A80 PQ: 0 ANSI: 5
Mar 27 09:16:22 t1500 kernel: [    3.438105] sd 0:0:0:0: [sda] Write Protect is off
Mar 27 09:16:22 t1500 kernel: [    3.438217] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Mar 27 09:16:22 t1500 kernel: [    3.438222] sd 0:0:1:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Mar 27 09:16:22 t1500 kernel: [    3.438244] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 27 09:16:22 t1500 kernel: [    3.438306] scsi 1:0:0:0: Direct-Access     ATA      Hitachi HDS72302 A5Q0 PQ: 0 ANSI: 5
Mar 27 09:16:22 t1500 kernel: [    3.438415] sd 1:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Mar 27 09:16:22 t1500 kernel: [    3.438436] sd 1:0:0:0: [sdc] Write Protect is off
Mar 27 09:16:22 t1500 kernel: [    3.438437] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Mar 27 09:16:22 t1500 kernel: [    3.438449] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 27 09:16:22 t1500 kernel: [    3.440194] scsi 1:0:1:0: CD-ROM            Optiarc  DVD RW AD-7200S  1.83 PQ: 0 ANSI: 5
Mar 27 09:16:22 t1500 kernel: [    3.441051]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
Mar 27 09:16:22 t1500 kernel: [    3.441224] sd 0:0:1:0: [sdb] Write Protect is off
Mar 27 09:16:22 t1500 kernel: [    3.441343] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
Mar 27 09:16:22 t1500 kernel: [    3.441433] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 27 09:16:22 t1500 kernel: [    3.441798] sd 0:0:0:0: [sda] Attached SCSI disk
Mar 27 09:16:22 t1500 kernel: [    3.502310] sr 1:0:1:0: [sr0] scsi3-mmc drive: 32x/32x writer dvd-ram cd/rw xa/form2 cdda tray
Mar 27 09:16:22 t1500 kernel: [    3.502496] cdrom: Uniform CD-ROM driver Revision: 3.20
Mar 27 09:16:22 t1500 kernel: [    3.502694] sr 1:0:1:0: Attached scsi CD-ROM sr0
Mar 27 09:16:22 t1500 kernel: [    3.534504]  sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 sdc7 sdc8 sdc9 >
Mar 27 09:16:22 t1500 kernel: [    3.535908] sd 1:0:0:0: [sdc] Attached SCSI disk
Mar 27 09:16:22 t1500 kernel: [    3.542301]  sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 >
Mar 27 09:16:22 t1500 kernel: [    3.543729] sd 0:0:1:0: [sdb] Attached SCSI disk
Mar 27 09:16:22 t1500 kernel: [    3.543931] md: Waiting for all devices to be available before autodetect
Mar 27 09:16:22 t1500 kernel: [    3.544043] md: If you don't use raid, use raid=noautodetect
Mar 27 09:16:22 t1500 kernel: [    3.544449] md: Autodetecting RAID arrays.
Mar 27 09:16:22 t1500 kernel: [    3.544555] md: Scanned 0 and added 0 devices.
Mar 27 09:16:22 t1500 kernel: [    3.544659] md: autorun ...
Mar 27 09:16:22 t1500 kernel: [    3.544761] md: ... autorun DONE.
Mar 27 09:16:22 t1500 kernel: [    3.547235] EXT4-fs (sda2): couldn't mount as ext3 due to feature incompatibilities
Mar 27 09:16:22 t1500 kernel: [    3.549624] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Mar 27 09:16:22 t1500 kernel: [    3.549812] VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
Mar 27 09:16:22 t1500 kernel: [    3.550765] devtmpfs: mounted
Mar 27 09:16:22 t1500 kernel: [    3.552285] Freeing unused kernel memory: 1384K (ffffffff82561000 - ffffffff826bb000)
Mar 27 09:16:22 t1500 kernel: [    3.552470] Write protecting the kernel read-only data: 20480k
Mar 27 09:16:22 t1500 kernel: [    3.553291] Freeing unused kernel memory: 1572K (ffff880001c77000 - ffff880001e00000)
Mar 27 09:16:22 t1500 kernel: [    3.556395] Freeing unused kernel memory: 1492K (ffff88000228b000 - ffff880002400000)
Mar 27 09:16:22 t1500 kernel: [    3.835523] random: systemd urandom read with 89 bits of entropy available
Mar 27 09:16:22 t1500 kernel: [    4.113830] random: nonblocking pool is initialized
Mar 27 09:16:22 t1500 kernel: [    6.258734] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
Mar 27 09:16:22 t1500 kernel: [    7.182583] Adding 1873916k swap on /dev/sda6.  Priority:-1 extents:1 across:1873916k SS
Mar 27 09:16:22 t1500 kernel: [    7.961576] Adding 1583100k swap on /dev/sdb5.  Priority:-2 extents:1 across:1583100k

mrmazda · 03-27-2019, 03:29 AM

Loading only a kernel might work in Slack, but in Fedora, Mageia and openSUSE at least both kernel and initrd are needed. You may find only openSUSE and Mageia have the symlinks to the installed kernels you've named and their corresponding initrds that you've omitted from your lilo stanzas. Fedora doesn't have them unless you created them manually.

Logs in those others are accessed via their journalctl commands. Look in /var/log/journal/ for the directories containing the logging files.

What video device are you using?

Code:

inxi -Gxx

(run from within X to get complete info)

Why lilo when Grub works?

Gorštak · 03-27-2019, 02:42 PM

Quote:

Originally Posted by mrmazda

Why lilo when Grub works?

For testing purposes (read fun). I love testing various distros, so slackware gets its turn now. I wwnt to try out its native bootloader too.

Quote:

Originally Posted by mrmazda

at least both kernel and initrd are needed

First time working with lilo. Config was made by lilosetup, expert mode, without manual editing afterward. I thought it will be enough.

Ill post inxi output when i get back home.

EDIT: There is no inxi in slackware and I cant find a way to install it.

I tried editing lilo.conf and add initrd line, but so far none of the solutions I found on internet worked...

business_kid · 03-28-2019, 05:28 AM

Quote:

Originally Posted by Gorstak

I tried editing lilo.conf and add initrd line, but so far none of the solutions I found on internet worked...

Here's a lilo entry with an initrd in it.

Code:

image = /boot/vmlinuz-4.14.55
        label = "4.14.55-generic"
        root = /dev/sda3
        read-only
        initrd = /boot/initrd.gz-4.14.55

I used Lilo until I decided it was time to drag myself reluctantly into the 21st century. I've never tried lilosetup, just use a text editor. I think you can have a line in after the root line

Code:

 append = "resume=/dev/sda2 <any kernel boot line options you need>"

You may not actually require the quotes. As for inxi, there's rpm2targz and deb2tgz(?) which unpack rpms and debs, but you can call the utilities inxi runs: lspci;lsusb;uname -a etc. Usually you don't want all the stuff it throws up anyhow.

Gorštak · 03-28-2019, 07:05 AM

Quote:

Originally Posted by business_kid

Here's a lilo entry with an initrd in it. [

Thanks, I tried something like that, but i overlooked the part that says the initrd and vmlinuz files have to be copied in slacware boot folder. Apparently lilo cant call them from a different partition, or I dont know how that is done.
Im building a new lilo.conf, adding one distro at a time, copying initrd and vmlinuz files to slackware boot folder. So far they boot successfuly, exept for win xp, but ill leave that one for later, afet i check out all other linux distros.

Code:

image = /boot/vmlinuz
  root = /dev/sdb7
  label = slackware
  read-only  

image = /boot/mx/vmlinuz-4.14.0-3-rt-amd64
  root = /dev/sdc7
  label = mx
  read-only 
  initrd = /boot/mx/initrd.img-4.14.0-3-rt-amd64

image = /boot/mint/vmlinuz-4.15.0-46-generic
  root = /dev/sda2
  label = mint
  read-only  
  initrd = /boot/mint/initrd.img-4.15.0-46-generic

image = /boot/serbian/vmlinuz-4.19.0-4-amd64
  root = /dev/sda3
  label = serbian
  read-only  
  initrd = /boot/serbian/initrd.img-4.19.0-4-amd64 

image = /boot/elementary/vmlinuz-4.15.0-46-generic
  root = /dev/sda5
  label = elementary
  read-only  
  initrd = /boot/elementary/initrd.img-4.15.0-46-generic

business_kid · 03-29-2019, 04:43 AM

Disk access has teetotally transformed since I last read up on this. We were at the stage of MBR booting, and lilo would work out increments and kick the ball down the road appropriately (i.e it goes in on sector 0, you choose kernel and it's told to take up the reading at sector 573 - that sort of thing). Sorry I can't help you.

On your lilo.conf, if those don't work, get the subdirs out. There's nothing to stop you renaming the kernel. It looks good, and if it adds them, it will have checked them and rarely fails after that.