LinuxQuestions.org
Review your favorite Linux distribution.
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 05-21-2016, 06:13 AM   #1
tano70
LQ Newbie
 
Registered: Oct 2013
Posts: 26

Rep: Reputation: Disabled
Alien bob Live 1.0.0 with persistence, problem with update kernel 4.4.11


Hello,i have installed in a usb pen the alien bob slackware live 1.0.0 (current-64-live-iso) with persistence, all work very well but when i update the system and upgrade-all, install the new kernel 4.4.11 and at reboot my system arrives at a graphical login screen, after a strange flicker with colored lines, and remains totally blocked (totally freeze)!! anyone have this problem?

EDIT: I'm afraid to do the same update in slackware system hard drive, which at the moment are still at 4.4.10 kernel

this is my hardware:
PC Manufacturer: LENOVO
Product Name: 34604LG

Motherboard Vendor: LENOVO X1 CARBON
Product Name: 34604LG

BIOS Vendor: LENOVO
Version: G6ET96WW (2.56 )
Release Date: 04/29/2013

Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz
Max Speed: 2500 MHz
Current Speed of Core 0:3070 MHz, 1:3000 MHz, 2:3000 MHz, 3:3000 MHz
Core Count: 2
Thread Count: 4

Phys 0 (coretemp) : +61.0 C (high = +87.0 C, crit = +105.0 C)
Core 0 (coretemp) : +57.0 C (high = +87.0 C, crit = +105.0 C)
Core 1 (coretemp) : +62.0 C (high = +87.0 C, crit = +105.0 C)

Memory Allocation:
Total RAM: 7797 MB

Last edited by tano70; 05-21-2016 at 06:42 AM.
 
Old 05-21-2016, 06:41 AM   #2
BigTig
Member
 
Registered: Aug 2015
Posts: 45

Rep: Reputation: Disabled
No mouse movement and caps lock light doesn't light up when you press it? I had the same problem because I hadn't updated lilo properly. Did you try booting into runlevel 3?
 
Old 05-21-2016, 06:44 AM   #3
tano70
LQ Newbie
 
Registered: Oct 2013
Posts: 26

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by BigTig View Post
No mouse movement and caps lock light doesn't light up when you press it? I had the same problem because I hadn't updated lilo properly. Did you try booting into runlevel 3?
exact, all locked, no typing, no mouse, then I'm sorry you need to give an update lilo if the system is in USB stick and that is the only kernel

Then explain to me how I can turn on the run level 3 if the system crashes after loading and not let me do anything

Last edited by tano70; 05-21-2016 at 06:46 AM.
 
Old 05-21-2016, 06:51 AM   #4
BigTig
Member
 
Registered: Aug 2015
Posts: 45

Rep: Reputation: Disabled
It should all be explained in the documentation Eric wrote:
http://docs.slackware.com/slackware:...ters_explained
 
Old 05-21-2016, 06:59 AM   #5
tano70
LQ Newbie
 
Registered: Oct 2013
Posts: 26

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by BigTig View Post
It should all be explained in the documentation Eric wrote:
http://docs.slackware.com/slackware:...ters_explained
let me know if you solve and how to solve. I feel with the help of the boot menu settings

EDIT: I tried to explore the boot menu settings but I have not figured out how to change the run level, by pressing the tab key is the only option that appears to me the line in which makes me change the keyboard layout, I noticed, however, that during the boot search of the 4.4.10 kernel modules which obviously is not, this is the reason for blocking. How you can resolve this situation? I'm not in any way get to the tty console but always loads automatically the graphics window where he remains all blocked

Last edited by tano70; 05-21-2016 at 07:37 AM.
 
Old 05-21-2016, 07:56 AM   #6
BigTig
Member
 
Registered: Aug 2015
Posts: 45

Rep: Reputation: Disabled
I'm not sure of the boot menu settings because I've been using a heavily modified version. I _think_ you need to type rescue to boot into a shell. From the error you got, I think you need to build a proper initrd. Did you run mkinitrd after upgrading?
 
Old 05-21-2016, 08:01 AM   #7
tano70
LQ Newbie
 
Registered: Oct 2013
Posts: 26

Original Poster
Rep: Reputation: Disabled
No after the upgrade I have not done anything. that I should do exactly as when I update my slackware on hd? ./mkinitrd_command_generator.sh /boot/vmlinuz-huge-4.4.11 ?? etc. etc? please explane
 
Old 05-21-2016, 04:43 PM   #8
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,240

Rep: Reputation: 3994Reputation: 3994Reputation: 3994Reputation: 3994Reputation: 3994Reputation: 3994Reputation: 3994Reputation: 3994Reputation: 3994Reputation: 3994Reputation: 3994
What you'll likely need to do is the same type of thing if you did it on a regular harddrive. You'll need to use an installation disc/usb drive to get you into the shell. Then you mount the root directory of the Slacklive (along with bind mounting /dev, /sys, and /proc), chroot the new mount, generate a new initrd (if he's using the generic kernel... I don't remember), verify/update lilo.conf, then run lilo to save your changes.

After this, you should be able to boot off your pendrive.

Keep in mind, I'm not terribly familiar with Slacklive, so I'm just treating it as a normal Slackware install (which it mostly is).
 
Old 05-21-2016, 06:12 PM   #9
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,736

Rep: Reputation: 6304Reputation: 6304Reputation: 6304Reputation: 6304Reputation: 6304Reputation: 6304Reputation: 6304Reputation: 6304Reputation: 6304Reputation: 6304Reputation: 6304
If you would install Slackware Live to a harddisk it would work exactly like Slackware when it would have been installed from the official media.
However, if you are running Slackware Live itself, you are booting it with a generic kernel (unmodified Slackware kernel) and a modified initrd image. The initrd is created using Slackware's "mkinitrd" program but then the regular "init" script inside that initrd image is replaced by a smarter version that knows how to boot a Live OS.

So, if you wanted to upgrade the kernel of a Slackware Live USB stick, you would have to replace the kernel and the initrd with new versions.
The kernel on the USB stick is the file "/boot/generic" and the initrd file is "/boot/initrd.img".
The initrd file is the tricky one to re-create. It needs to contain all the kernel modules that are used to assemble the Live filesystem and boot the Live OS. You could examine the "make_slackware_live.sh" script to see how that is done.
Or someone could come up with a script "update_live_kernel.sh" that will do this fully automatic... would be nice to add to the liveslak.
Incremental updates of (persistent or otherwise) Slackware Live Edition is on my TODO but it may remain on there for a long time if I make a move to do other things after the release of Slackware 14.2.
 
2 members found this post helpful.
Old 05-22-2016, 01:44 AM   #10
philanc
Member
 
Registered: Jan 2011
Posts: 236

Rep: Reputation: 192Reputation: 192
Quote:
Originally Posted by Alien Bob View Post
The initrd file is the tricky one to re-create. It needs to contain all the kernel modules that are used to assemble the Live filesystem and boot the Live OS. You could examine the "make_slackware_live.sh" script to see how that is done.
To make slackpkg usable on liveslak for regular updates/upgrades without this kernel update issue, I would recommend to blacklist the kernel packages in /etc/slackpkg. See file /etc/pkg/blacklist and uncomment the kernel package lines as below:
Code:
# Automated upgrade of kernel packages aren't a good idea (and you need to
# run "lilo" after upgrade). If you think the same, uncomment the lines
# below 
#
kernel-firmware
kernel-generic
kernel-generic-smp
kernel-headers
kernel-huge
kernel-huge-smp
kernel-modules
kernel-modules-smp
kernel-source
 
Old 05-22-2016, 07:14 AM   #11
tano70
LQ Newbie
 
Registered: Oct 2013
Posts: 26

Original Poster
Rep: Reputation: Disabled
it's what I've done to me yesterday, after the problem I had to reformat the stick, what I do not understand is where to set the new settings of the updated kernel, I have not found any lilo.conf or edit another file where the new settings for boot, it continues to look for 4.4.10 modules which obviously did not exist more since upgraded to 4.4.11. by the time I get blacklisted the kernel, but I would, however, a solution that allows me to update the kernel.
 
Old 05-22-2016, 07:18 AM   #12
tano70
LQ Newbie
 
Registered: Oct 2013
Posts: 26

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Alien Bob View Post
If you would install Slackware Live to a harddisk it would work exactly like Slackware when it would have been installed from the official media.
However, if you are running Slackware Live itself, you are booting it with a generic kernel (unmodified Slackware kernel) and a modified initrd image. The initrd is created using Slackware's "mkinitrd" program but then the regular "init" script inside that initrd image is replaced by a smarter version that knows how to boot a Live OS.

So, if you wanted to upgrade the kernel of a Slackware Live USB stick, you would have to replace the kernel and the initrd with new versions.
The kernel on the USB stick is the file "/boot/generic" and the initrd file is "/boot/initrd.img".
The initrd file is the tricky one to re-create. It needs to contain all the kernel modules that are used to assemble the Live filesystem and boot the Live OS. You could examine the "make_slackware_live.sh" script to see how that is done.
Or someone could come up with a script "update_live_kernel.sh" that will do this fully automatic... would be nice to add to the liveslak.
Incremental updates of (persistent or otherwise) Slackware Live Edition is on my TODO but it may remain on there for a long time if I make a move to do other things after the release of Slackware 14.2.
Perfect, I understand why it does not work the kernel update. I did not know what to go and change after we upgraded. however, it would be really great if you in the future slackware live put the possibility that this process can do so automatically every time you update your kernel. Thanks again Alien.

EDIT:However the problem is that when I go to give mikinitrd command makes me a "initrd.gz" and not initrd.image

Last edited by tano70; 05-24-2016 at 02:06 AM.
 
  


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
Alien Bob's last libreoffice open/save problem aszabo Slackware 8 01-06-2015 02:06 PM
[SOLVED] Alien BOB bmarley83 Slackware 29 01-24-2014 04:18 PM
Alien Bob - When will you be able to update your multilib collection? 1337_powerslacker Slackware 2 10-21-2013 07:13 PM
[SOLVED] Errors with downloading new splash screens, Alien Bob's KDE 4.8.0 + Virtuoso problem vdemuth Slackware 5 02-27-2012 02:36 PM
One for Alien Bob cwwilson721 Slackware 28 08-15-2006 05:26 PM

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

All times are GMT -5. The time now is 08:31 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