LinuxQuestions.org
Visit Jeremy's Blog.
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 12-14-2016, 04:24 AM   #16
D1ver
Member
 
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 598
Blog Entries: 3

Rep: Reputation: 194Reputation: 194

Quote:
Originally Posted by GazL View Post
Anyone tried 4.9 yet? I've just run through make oldconfig and got my local config file ready for a build. Surprisingly there weren't that many new options to set given how large a changeset 4.9 is.

update:
Code:
test@ws1:~$ uname -a
Linux ws1 4.9.0-local #1 SMP Tue Dec 13 14:25:08 GMT 2016 x86_64 Intel(R) Core(TM) i3-5157U CPU @ 2.50GHz GenuineIntel GNU/Linux
Well, if nothing else. It still boots. Nothing obviously untoward in the kernel log.
Awesome. I've been planning on giving 4.9 a try. I would love to be able to take a Pat config from testing/ but if there aren't that many new options I might just try myself

Supposedly skylake power management has been getting some love which might be good news on my laptop.
 
Old 12-14-2016, 05:09 AM   #17
GazL
LQ Veteran
 
Registered: May 2008
Posts: 6,873

Rep: Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982Reputation: 4982
If I remember rightly, I started with a fresh "make defconfig" around 4.7 and built on it from there. I'd share it, but it's a heavily trimmed down one so probably more harm then help to anyone else.

Just to be clear, when I said not many new options, I meant from 4.8 to 4.9. If you're starting with a config file earlier than that you'll probably have quite a few options to ponder.
 
1 members found this post helpful.
Old 12-14-2016, 08:30 AM   #18
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 15.0 + Multilib
Posts: 2,159

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
Quote:
Originally Posted by tronayne View Post

Quote:
One strange thing (well, two): something reported two fatal errors about couldn't find /lib/something 4.4.29 (when it was shutting down from init 6).
... and then ...

I keep a directory /usr/local/patches. I get the patch file(s) with wget:
Code:
wget ftp://ftp.osuosl.org/pub/slackware/slackware64-14.2/patches/packages/linux-4.4.38/*
upgradepkg *.t?z
:
<snip>
:
tronayne --

Maybe the missing 4.4.29 files were due to upgrading the kernel files ( which does a removepkg on the old kernel ) ?

Specifically, `upgradepkg kernel-modules` will delete the kernel modules on your running kernel !

As a rule, I apply all the kernel-related packages manually, some via upgradepkg but importantly, some via installpkg.

These packages are upgraded:
Code:
#
# these kernel updates are applied via `upgradepkg`
#
kernel-headers
kernel-firmware
These packages are installed
Code:
#
# these kernel updates are applied via `installpkg`
#
kernel-generic
kernel-huge
kernel-modules
kernel-source
Applying the second set of packages via `installpkg` leaves behind the previous version(s).

After applying the new kernel Packages, I ( usually but not always ) make a new initrd file and fix lilo.conf for the new kernel(s) ( I include the full vmlinuz file name in my lilo.conf file so that I can have multiple versions ) and reboot.

Note that for the Generic Kernels, I also generate versioned initrd files. Once again, so that I can keep an old one 'just in case'.

See the -a and -o options on /usr/share/mkinitrd/mkinitrd_command_generator.sh
Code:
#
# in lilo.conf, my image = lines look like this:
#
image = /boot/vmlinuz-huge-4.4.29
#
# instead of referencing the symlinks:
#
# NOT THIS:  image = /boot/vmlinuz-huge
#
# AND ESPECIALLY NOT THIS:  image = /boot/vmlinuz
#
# this way I can be sure of which kernel I am booting and I can always boot an 'old one'
#
From my Lilo.conf:

Code:
#
# <<snip>>
#
image = /boot/vmlinuz-generic-4.4.38
  label  = Generic-4438
  initrd = /boot/initrd-generic-4.4.38.gz
  root   = /dev/sda3
  read-only
image   = /boot/vmlinuz-huge-4.4.38
  root  = /dev/sda3
  label = Huge-4438
  read-only
image = /boot/vmlinuz-generic-4.4.29
  label  = Generic-4429
  initrd = /boot/initrd-generic-4.4.29.gz
  root   = /dev/sda3
  read-only
image   = /boot/vmlinuz-huge-4.4.29
  root  = /dev/sda3
  label = Huge-4429
  read-only
After all this, once I see that the new version is a keeper, I eventually go back and `removepkg` the older version(s) in the `installpkg` list and remove any old initrd files 'by hand'.

Clear as mudd ?

-- kjh
 
2 members found this post helpful.
Old 12-14-2016, 11:24 AM   #19
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541

Rep: Reputation: 1065Reputation: 1065Reputation: 1065Reputation: 1065Reputation: 1065Reputation: 1065Reputation: 1065Reputation: 1065
Quote:
Originally Posted by kjhambrick View Post
tronayne --

Maybe the missing 4.4.29 files were due to upgrading the kernel files ( which does a removepkg on the old kernel ) ?
I kind of figured that, just didn't know what it was and it was only on the system that has VirtualBox on it (so, I rebuilt VirtualBox just for the heck of it). I also rebuild some SBo packages (I have a shell program that does that) just to take advantage of kernel updates that might be handy.

I learned a long time ago to trust Pat and the developers; I don't mess with initrd, just lilo on un-fooled-around-with Slackware stable; when I install a new release I do a full install (everything), accept the default kernel and do some editing in [I]/etc/I] from a backup of the entire /etc directory, either merging or editing as I deem necessary. Everything works as expected.

Doing the kernel updates (two of 'em so far in 14.2) is pretty much the same -- upgradepkg and be done with it (I do not fiddle with the kernel, quit doing that about 10 years ago). I have to spread the kernel (and other) updates across multiple servers and, because every system is configured identically, it's a simple scp from the main system to the others and ssh into them and run upgradepkg.

It works for me, no troubles, no tweaking, no nothing.

Thanks for the input -- one of these days I might just have to fiddle and it's nice to know how.
 
1 members found this post helpful.
Old 12-15-2016, 07:05 AM   #20
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64-current
Posts: 338

Rep: Reputation: 156Reputation: 156
Quote:
Originally Posted by PROBLEMCHYLD View Post
How did you get your sleep/hibernation to work? I have been struggling with it.
Sleep (suspend to ram) works out of the box on the laptop used, ditto for hibernate but you need to set the resume kernel parameter as needed in Grub/Lilo config (resume=/dev/sdax, replace sdax with your resume partition).
 
Old 12-15-2016, 04:11 PM   #21
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 15.0 + Multilib
Posts: 2,159

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
Quote:
Originally Posted by tronayne View Post
I kind of figured that, just didn't know what it was and it was only on the system that has VirtualBox on it (so, I rebuilt VirtualBox just for the heck of it). I also rebuild some SBo packages (I have a shell program that does that) just to take advantage of kernel updates that might be handy.

I learned a long time ago to trust Pat and the developers; I don't mess with initrd, just lilo on un-fooled-around-with Slackware stable; when I install a new release I do a full install (everything), accept the default kernel and do some editing in [I]/etc/I] from a backup of the entire /etc directory, either merging or editing as I deem necessary. Everything works as expected.

Doing the kernel updates (two of 'em so far in 14.2) is pretty much the same -- upgradepkg and be done with it (I do not fiddle with the kernel, quit doing that about 10 years ago). I have to spread the kernel (and other) updates across multiple servers and, because every system is configured identically, it's a simple scp from the main system to the others and ssh into them and run upgradepkg.

It works for me, no troubles, no tweaking, no nothing.

Thanks for the input -- one of these days I might just have to fiddle and it's nice to know how.
You're welcome tronayne.

I agree with you about the HUGE Kernel and not fooling with an initrd, especially lately with the unusual Kernel churn the past few months.

-- kjh
 
Old 12-15-2016, 09:44 PM   #22
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 2,011

Rep: Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619
This is kind of random, but I didn't want to start a new thread on it.

In case someone is using the 4.8 series kernel and VirtualBox from SBo, you may have noticed that virtualbox-kernel does not compile. I made a SlackBuild with some patches to fix that, which you can get here. Other than applying the patches, only minor things like the tag and build number have been changed from the SBo version. Of course, I'm aware that there are other ways to run VirtualBox without resorting to this fix, but I thought I'd mention it just in case someone else ran into the same issue. It may work with 4.9 too, but I haven't tried.
 
Old 12-16-2016, 03:32 AM   #23
imjustkillingtime
LQ Newbie
 
Registered: May 2016
Distribution: Slackware
Posts: 27

Rep: Reputation: 4
thanks for the heads up hitest.
Code:
~$ uname -r
4.4.38-smp
thank you as well kjhambrick and tronayne for your posts, helpful to babies like me.
 
Old 12-16-2016, 07:00 AM   #24
slackb0t
Member
 
Registered: Apr 2005
Location: Canada
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 264

Rep: Reputation: 63
Quote:
Originally Posted by kjhambrick View Post
tronayne --

Maybe the missing 4.4.29 files were due to upgrading the kernel files ( which does a removepkg on the old kernel ) ?

Specifically, `upgradepkg kernel-modules` will delete the kernel modules on your running kernel !

As a rule, I apply all the kernel-related packages manually, some via upgradepkg but importantly, some via installpkg.

These packages are upgraded:
Code:
#
# these kernel updates are applied via `upgradepkg`
#
kernel-headers
kernel-firmware
These packages are installed
Code:
#
# these kernel updates are applied via `installpkg`
#
kernel-generic
kernel-huge
kernel-modules
kernel-source
Applying the second set of packages via `installpkg` leaves behind the previous version(s).

After applying the new kernel Packages, I ( usually but not always ) make a new initrd file and fix lilo.conf for the new kernel(s) ( I include the full vmlinuz file name in my lilo.conf file so that I can have multiple versions ) and reboot.

Note that for the Generic Kernels, I also generate versioned initrd files. Once again, so that I can keep an old one 'just in case'.

See the -a and -o options on /usr/share/mkinitrd/mkinitrd_command_generator.sh
Code:
#
# in lilo.conf, my image = lines look like this:
#
image = /boot/vmlinuz-huge-4.4.29
#
# instead of referencing the symlinks:
#
# NOT THIS:  image = /boot/vmlinuz-huge
#
# AND ESPECIALLY NOT THIS:  image = /boot/vmlinuz
#
# this way I can be sure of which kernel I am booting and I can always boot an 'old one'
#
From my Lilo.conf:

Code:
#
# <<snip>>
#
image = /boot/vmlinuz-generic-4.4.38
  label  = Generic-4438
  initrd = /boot/initrd-generic-4.4.38.gz
  root   = /dev/sda3
  read-only
image   = /boot/vmlinuz-huge-4.4.38
  root  = /dev/sda3
  label = Huge-4438
  read-only
image = /boot/vmlinuz-generic-4.4.29
  label  = Generic-4429
  initrd = /boot/initrd-generic-4.4.29.gz
  root   = /dev/sda3
  read-only
image   = /boot/vmlinuz-huge-4.4.29
  root  = /dev/sda3
  label = Huge-4429
  read-only
After all this, once I see that the new version is a keeper, I eventually go back and `removepkg` the older version(s) in the `installpkg` list and remove any old initrd files 'by hand'.

Clear as mudd ?

-- kjh
With a bit of polishing this should be a sticky. Pretty much the same way I do it after needing to read countless threads to figure it out.
 
  


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
Stable 13 kernel vs Current kernel in Stable system linus72 Slackware 6 04-01-2010 07:45 AM
what is the current stable Kernel for Slack 10.2? alex1986 Linux - Kernel 4 08-01-2006 04:38 PM
current branch: kde 3.4 and kdm tobyl Slackware 2 03-29-2005 12:15 PM
X11 6.8.1 in slack-current branch r_jensen11 Slackware 19 09-30-2004 05:49 AM
Gnome 2.6 in the current branch? (+Questions about Dropline) the who Slackware 6 05-06-2004 11:32 AM

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

All times are GMT -5. The time now is 05:59 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
Open Source Consulting | Domain Registration