Slackware boot problem on Dedibox XC

TomToOmUch · 02-05-2015, 05:19 AM

Hi Slackers and not,

I finished a fresh install of an MLES, following this good HOWTO on a Dedibox XC :

Code:

[root@sd-69721:~] # lspci
00:00.0 Host bridge: Intel Corporation Avoton SSA-Cunit (rev 02)
00:01.0 PCI bridge: Intel Corporation Avoton PCIe Root Port 1 (rev 02)
00:02.0 PCI bridge: Intel Corporation Avoton PCIe Root Port 2 (rev 02)
00:03.0 PCI bridge: Intel Corporation Avoton PCIe Root Port 3 (rev 02)
00:0e.0 Host bridge: Intel Corporation Avoton RAS (rev 02)
00:0f.0 IOMMU: Intel Corporation Avoton RCEC (rev 02)
00:13.0 System peripheral: Intel Corporation Avoton SMBus 2.0 (rev 02)
00:14.0 Ethernet controller: Intel Corporation Avoton GbE x4 SGMII (rev 03)
00:14.1 Ethernet controller: Intel Corporation Avoton GbE x4 SGMII (rev 03)
00:16.0 USB controller: Intel Corporation Avoton USB Enhanced Host Controller (rev 02)
00:18.0 SATA controller: Intel Corporation Avoton AHCI SATA3 Controller (rev 02)
00:1f.0 ISA bridge: Intel Corporation Avoton PCU (rev 02)
00:1f.3 SMBus: Intel Corporation Avoton PCU SMBus (rev 02)
01:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 03)
02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)

I then create my initrd.gz with the /etc/mkinitrd.conf file :

Code:

# /etc/mkinitrd.conf
SOURCE_TREE="/boot/initrd-tree"
CLEAR_TREE="1"
OUTPUT_IMAGE="/boot/initrd.gz"
KERNEL_VERSION="$(uname -r)"
KEYMAP="fr"
MODULE_LIST="mbcache:jbd2:ext4" --> using /usr/share/mkinitrd/mkinitrd_command_generator.sh *
ROOTDEV="/dev/sda3"
ROOTFS="ext4"
RESUMEDEV="/dev/sda2"
RAID="0"
LVM="0"
UDEV="1"
MODCONF="0"
WAIT="1"

* when using mkinitrd_command_generator.sh, the system returns an error saying : "ls: impossible d'accéder à /sys/module/*_hcd/drivers/*: Aucun fichier ou dossier de ce type

Everything goes well running mkinitrd -F

I then adapt my /etc/lilo.conf file to run my Slackware system on the Generic Kernel 3.10.17 :

Code:

# /etc/lilo.conf
lba32
append="ipv6.disable=1 vt.default_utf8=1"
boot= /dev/sda
compact
message = /boot/boot_message.txt
change-rules
reset
vga = normal
image = /boot/vmlinuz-generic-3.10.17
  initrd = /boot/initrd.gz
  root = /dev/sda3
  label = MLES-14.1-64bit
  read-only

Running lilo returns me the usual video issue warning, nothing bad though.

I then reboot && exit and my Dedibox doesn't ping up again.
The only solution I found was configuring the bootloader back to use the huge Slackware kernel...I'd like to thin my kernel down to the strict minimum...

Could you please give me hints to how to handle this please ?

Didier Spaier · 02-05-2015, 12:33 PM

Salut et bienvenue à LQ,

I cannot give you a real explanation on what did go wrong but just a hint:

Quote:

Originally Posted by TomToOmUch

when using mkinitrd_command_generator.sh, the system returns an error saying : "ls: impossible d'accéder à /sys/module/*_hcd/drivers/*: Aucun fichier ou dossier de ce type

That's because this function in the script fails:

Code:

# Determine what USB Host Controller is in use
function add_usb_hcd() {
  local USBMOD
  for i in $(ls -Ld /sys/module/*_hcd/drivers/*); do 
    if ls -L $i | grep -q "[0-9a-f]*:" ; then
      USBMOD=$( echo $i | cut -f4 -d/ | tr "_" "-")
      [ -n "$MLIST" ] && MLIST="$MLIST:$USBMOD" \
                      || MLIST="$USBMOD"
    fi
  done
  echo $MLIST
}

The problem is that in recent kernels the layout of /sys has changed as pointed out in this post so the drivers are now exposed in the directories /sys/module/*_pci/drivers/

I'm not sure that your real problem be linked to that though.

Incidentally I don't think that thinning the kernel to the strict minimum provides much practical advantage (been there, done that long ago) but that's only my opinion.

TomToOmUch · 02-05-2015, 02:23 PM

Salut Didier and thanks a lot for your reply,

in fact, I'll try fixing the initrd problem anyway, at least to be thorough...

However, the server doesn't seem any slower running on the huge kernel !

I'll post further comments on the behavior of the bootloader after fixing the module/driver issue.
It's really weird 'cause in the logs, it seems the server just shutdown and then...nothing...

I'll keep you posted ! Merci encore !

kikinovak · 02-06-2015, 01:55 AM

Quote:

Originally Posted by TomToOmUch

Salut Didier and thanks a lot for your reply,

in fact, I'll try fixing the initrd problem anyway, at least to be thorough...

However, the server doesn't seem any slower running on the huge kernel !

I'll post further comments on the behavior of the bootloader after fixing the module/driver issue.
It's really weird 'cause in the logs, it seems the server just shutdown and then...nothing...

I'll keep you posted ! Merci encore !

Hi TomToOmUch,

Looks like you're not far from here. Call me, I'll help you get this sorted out.

TomToOmUch · 02-06-2015, 03:22 PM

Hi,

I solved the initrd issue...Merci Didier !
However it doesn't solve the bootloader issue...so I'll call Master kiki (yeah, you trained me Niki) and keep the thread updated.

'Til next time,
Cheers
Tom