kernel update and it is dead

francesco bat · 10-23-2016, 09:28 AM

Hello !
I'm sorry for my bad english

I have slackware 14.1 stable 32 bit installed in my notebook acer extensa 5230e.
I update always my system with gslapt, but i've never update the kernel because it and others system files like glib etc. were disabled from gslapf to update.
After news about bug "dirty cow" i enebled these update and i updated the kernel.
After the reboot now it doesn't boot anymore.

After Lilo i get "Loading linux..." and it does not continue, or otherwise it goes in black screen and it does not continue.
From grub of peppermint 7 it loads but after it stop in this string:

Code:

pmcia_socket pmcia_socket0: cs: IO port probe 0x3e0-0x4ff:
excluding 0x3f0-0x3f7

What is it happened and what i solve ?
Bye
Francesco bat

STDOUBT · 10-23-2016, 01:19 PM

For us to help, you need to tell us a few things:

By what method did you update the kernel?
(please show specific commands)

Did you edit /etc/lilo.conf with new kernel infos and then run "lilo" as root afterwards?
(Please show us your /etc/lilo.conf)

Also, what kernel version did you use, and where did you download that kernel?

francesco bat · 10-23-2016, 02:04 PM

Hi !
The kernel is 3.10.103, downloaded from gslapt from slackware official repository .
I want add this: time ago i try to install others distro but new kernels 4 32 bit in last versions distro they does not work in my notebook.
I try many distro but i could not to install nothing.
Instead distro 64 bit works (indeed i installed peppermint 7 64 bit without problems).
I tried to install slackware 14.2 32 bit and it failed, therefore i installed recently slackware 14.1 and no 14.2).
Now installing the kernel 3.10.103 i would not that it is equivalent to new kernel 4

Bye
Francesco bat

bassmadrigal · 10-23-2016, 07:34 PM

Once you update a kernel, you need to ensure your /etc/lilo.conf is updated to match your new kernel. Once that is done, you need to run lilo to make sure your bootloader is updated. Once that is done, it should boot properly. To do that, you need to boot off your installation disk/usb drive, mount your drive, chroot your install, then update your lilo.conf and run lilo.

http://docs.slackware.com/howtos:sla...oot_from_media

francesco bat · 10-23-2016, 07:53 PM

Quote:

Originally Posted by bassmadrigal

Once you update a kernel, you need to ensure your /etc/lilo.conf is updated to match your new kernel. Once that is done, you need to run lilo to make sure your bootloader is updated. Once that is done, it should boot properly. To do that, you need to boot off your installation disk/usb drive, mount your drive, chroot your install, then update your lilo.conf and run lilo.

http://docs.slackware.com/howtos:sla...oot_from_media

Yes i know the Lilo question

Indeed when i start slackware from Lilo it stops in "Loading linux..." until everything is evident

The problem is i installed in dual boot peppermint 7 after slackware update, and if i boot slackware from peppermint 7 grub, it boots slackware without problems and slackware loads.
But after a few seconds what it is loading it stop to string:

Code:

pmcia_socket pmcia_socket0: cs: IO port probe 0x3e0-0x4ff:
excluding 0x3f0-0x3f7

and it does not provide more loading

bassmadrigal · 10-23-2016, 10:23 PM

Wait, so you have both lilo and grub? How do you select which bootloader is used, or did you install peppermint after lilo failed to boot Slackware back up?

And your Slackware lilo gets stuck shortly after the "Loading Linux" prompt? And your peppermint grub loads Slackware, but during the boot process you get that error and it ceases to finish booting?

Are you using a generic or huge kernel in Slackware? If you are using the symbolic links, you should ensure that /boot/vmlinuz points to the correct kernel (either generic or huge). If you are using the generic kernel, did you regenerate your initrd?

francesco bat · 10-24-2016, 07:50 AM

Quote:

Originally Posted by bassmadrigal

Wait, so you have both lilo and grub? How do you select which bootloader is used, or did you install peppermint after lilo failed to boot Slackware back up?

And your Slackware lilo gets stuck shortly after the "Loading Linux" prompt? And your peppermint grub loads Slackware, but during the boot process you get that error and it ceases to finish booting?

Are you using a generic or huge kernel in Slackware? If you are using the symbolic links, you should ensure that /boot/vmlinuz points to the correct kernel (either generic or huge). If you are using the generic kernel, did you regenerate your initrd?

OK, OK ! There's a bit of confusion

I have:

sda4 with Slackware 14.1 32 bit and Lilo Boot in sda4
sda3 with Peppermint 7 64 bit (installed after update Slackware) and Grub Boot in sda3

To boot with a boot loader i have GAG Boot Manager in MBR and if i select Slackware it start Lilo of Slackware, if i select Peppermint 7 it start grub of peppermint 7
Now i hope I explained myself

So, since I have installed peppermint 7 after slackware update, it detect last slackware kernel (and no like Lilo that i still have not configured).
The problem, now, is kernel boot and no Lilo

I want add this: in acer extensa 5230e i tried to install last versions of Manjaro Linux, Mageia, slackware 14.2 and other distro Linux all 32 bit and They crashes during installation.
Someone said me here's a bug in last kernels 32 bit for my notebook and they work just kernel 64 bit, and i installed slackware 14.1 (because it has old kernel) and it had installed in my pc without problems.
I didn't want to update kernel (i had not until to now) but the bug "dirty cow" made me do it.
Since the problem is very similar when i tried to install slackware 14.2 (it crashed so) i want to know if the kernel 3.10.103 is equivalent to last 4.8
Bye
Francesco bat

bassmadrigal · 10-24-2016, 08:12 AM

3.10.103 is still vulnerable to the dirty cow exploit. It has not been patched in any Slackware version yet (including -current). That kernel update for 14.1 was done back in August due to another kernel bug.

Code:

Mon Aug 29 22:51:27 UTC 2016
patches/packages/linux-3.10.103/*:  Upgraded.
  A flaw was found in the implementation of the Linux kernels handling of
  networking challenge ack where an attacker is able to determine the shared
  counter.  This may allow an attacker located on different subnet to inject
  or take over a TCP connection between a server and client without having to
  be a traditional Man In the Middle (MITM) style attack.

Ok, now that I understand your bootloader setup, let's dive into lilo for Slackware. Can you provide your /etc/lilo.conf and the output of ls -la /boot/ so we can see how that's set up?

francesco bat · 10-24-2016, 09:32 AM

I made the operations from peppermint 7 because slackware doesn't boot:

Code:

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

#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/sda4
  label = Linux
  read-only
# Linux bootable partition config ends

and

Code:

ls -la /media/francesco/6cc3c3d0-17b6-4fd7-a850-776658cc11cc/boot
totale 28124
drwxr-xr-x  2 root root    4096 ott 22 22:01 .
drwxr-xr-x 21 root root    4096 ott 22 22:05 ..
-rw-r--r--  1 root root     512 lug 10 23:05 boot.0804
-rw-r--r--  1 root root     168 lug 10 23:05 boot_message.txt
lrwxrwxrwx  1 root root      28 ott 22 22:01 config -> config-huge-smp-3.10.103-smp
-rw-r--r--  1 root root  140999 ago 29 23:16 config-generic-3.10.103
-rw-r--r--  1 root root  141909 ago 29 22:37 config-generic-smp-3.10.103-smp
-rw-r--r--  1 root root  140999 ago 29 23:24 config-huge-3.10.103
-rw-r--r--  1 root root  141909 ago 29 22:47 config-huge-smp-3.10.103-smp
-rwxr-xr-x  1 root root  217646 gen 10  2011 elilo-ia32.efi
-rwxr-xr-x  1 root root  250510 gen 10  2011 elilo-x86_64.efi
-rw-r--r--  1 root root   22578 ott 28  2013 inside.bmp
-rw-------  1 root root   91136 lug 10 23:05 map
-rw-r--r--  1 root root    6878 ott 28  2013 onlyblue.bmp
lrwxrwxrwx  1 root root      37 lug 10 22:44 README.initrd -> /usr/doc/mkinitrd-1.4.8/README.initrd
-rw-r--r--  1 root root   14174 feb 15  2010 slack.bmp
lrwxrwxrwx  1 root root      32 ott 22 22:01 System.map -> System.map-huge-smp-3.10.103-smp
-rw-r--r--  1 root root 1710969 ago 29 23:16 System.map-generic-3.10.103
-rw-r--r--  1 root root 1765327 ago 29 22:37 System.map-generic-smp-3.10.103-smp
-rw-r--r--  1 root root 2672311 ago 29 23:24 System.map-huge-3.10.103
-rw-r--r--  1 root root 2730442 ago 29 22:47 System.map-huge-smp-3.10.103-smp
-rw-r--r--  1 root root   33192 ott 28  2013 tuxlogo.bmp
lrwxrwxrwx  1 root root      29 ott 22 22:01 vmlinuz -> vmlinuz-huge-smp-3.10.103-smp
-rw-r--r--  1 root root 3100416 ago 29 23:16 vmlinuz-generic-3.10.103
-rw-r--r--  1 root root 3281904 ago 29 22:37 vmlinuz-generic-smp-3.10.103-smp
-rw-r--r--  1 root root 6007184 ago 29 23:24 vmlinuz-huge-3.10.103
-rw-r--r--  1 root root 6271264 ago 29 22:47 vmlinuz-huge-smp-3.10.103-smp

Bye
Francesco bat

bassmadrigal · 10-24-2016, 10:22 AM

Ok, your lilo.conf looks like it's set up properly. Now you should just need to chroot your root Slackware partition and write lilo to the mbr.

Code:

mount -o bind /dev /media/francesco/6cc3c3d0-17b6-4fd7-a850-776658cc11cc/dev
mount -o bind /proc /media/francesco/6cc3c3d0-17b6-4fd7-a850-776658cc11cc/proc
mount -o bind /sys /media/francesco/6cc3c3d0-17b6-4fd7-a850-776658cc11cc/sys
chroot /media/francesco/6cc3c3d0-17b6-4fd7-a850-776658cc11cc/
lilo

You'll probably get a warning about LBA32 that you can safely ignore. If you get any other warnings or errors, make note and post them here. If it completes successfully, reboot and try and boot Slackware with lilo.

francesco bat · 10-25-2016, 06:20 AM

Quote:

Originally Posted by bassmadrigal

Ok, your lilo.conf looks like it's set up properly. Now you should just need to chroot your root Slackware partition and write lilo to the mbr.

Code:

mount -o bind /dev /media/francesco/6cc3c3d0-17b6-4fd7-a850-776658cc11cc/dev
mount -o bind /proc /media/francesco/6cc3c3d0-17b6-4fd7-a850-776658cc11cc/proc
mount -o bind /sys /media/francesco/6cc3c3d0-17b6-4fd7-a850-776658cc11cc/sys
chroot /media/francesco/6cc3c3d0-17b6-4fd7-a850-776658cc11cc/
lilo

You'll probably get a warning about LBA32 that you can safely ignore. If you get any other warnings or errors, make note and post them here. If it completes successfully, reboot and try and boot Slackware with lilo.

Too late !
Yesterday i formatted pc and i reinstalled slackware 14.1.
In a short time i got my pc workiing with slakware 14.1

Bye
Francesco bat