LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 07-14-2014, 10:03 AM   #16
BobKay
LQ Newbie
 
Registered: Jul 2014
Posts: 26

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by hitest View Post
Okay. I am not advising you to do this, but, you can edit /etc/slackpkg/mirrors and comment out your present version of Slackware (put a # in front of your present mirror) and then uncomment a -current mirror of your choice (remove the # in front of the mirror). Save and exit.

# slackpkg update gpg
# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all

Run lilo at the end of this. You will then be running Slackware-current after the reboot. You need to upgrade to Slackware-current if you're going to run a -current kernel. There are risks associated with this.
@hitest, I ended up following that exact procedure and it worked a charm!

@enorbet, what on earth makes you think I feel kernel building is "antiquated and useless"? I'm just trying to get a new system up and running with a minimum of muss and fuss and I don't want to go through the trouble of building a custom kernel if it's not absolutely necessary at this time. I've been using Slackware since 2.2.0.1 or perhaps earlier so yes I've done a fair amount of kernel building. Please forgive me for having an imperfect memory on the exact building commands and their sequence; it's been about a decade since the last time I built a kernel. The last time I tried to build a kernel it didn't work and I never put much effort into finding out why; obviously I did something wrong but since the out-of-the-box kernel worked just fine I didn't put a whole lot of effort into finding out what I was doing wrong. The previous dozen or so times I'd compiled kernels they worked fine.
 
Old 07-14-2014, 02:49 PM   #17
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,713

Rep: Reputation: 535Reputation: 535Reputation: 535Reputation: 535Reputation: 535Reputation: 535
Quote:
Originally Posted by enorbet View Post
Nobody compiling a kernel ever uses (and rarely ever used) "make config" and running "make clean" after it would destroy anything you did anyway by returning it to generic source
I see that you haven't run those commands in a while.

"make mrproper" is the command that nukes your configuration changes. Most people would run "make menuconfig" instead of "make config", but only because it's easier for humans to handle the menus versus the questions for each option.
 
Old 07-14-2014, 04:36 PM   #18
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware
Posts: 4,519

Rep: Reputation: 689Reputation: 689Reputation: 689Reputation: 689Reputation: 689Reputation: 689
Smile

Quote:
Originally Posted by BobKay View Post
@hitest, I ended up following that exact procedure and it worked a charm!
I'm glad it worked out for you.
I felt safe advocating the non-standard upgrade procedure as I had recently done it myself and knew that it was unlikely to hose your system.
However, if you were running an earlier version of Slackware it would make more sense to follow the recommended upgrade path.
 
Old 07-14-2014, 06:03 PM   #19
enorbet
Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware 14 is Main OpSys on Main PC, 2ndary are OpenSuSe 13 and SolydK
Posts: 800

Rep: Reputation: 393Reputation: 393Reputation: 393Reputation: 393
Quote:
Originally Posted by Richard Cranium View Post
I see that you haven't run those commands in a while.

"make mrproper" is the command that nukes your configuration changes. Most people would run "make menuconfig" instead of "make config", but only because it's easier for humans to handle the menus versus the questions for each option.

I'm well aware that "make mrproper" nukes any previous changes as does "make clean" which is why either comes BEFORE any manner of config. I have only ever used "make clean" on kernel source if I botched a kernel config. The major point was the sequence. The minor point was the choice of commands.

Sometimes making things easier is a bad tradeoff or at least one that must be considered carefully, however I see no advantage whatsoever to "make config" over "make menuconfig" and once I got over "posing 1337" I came to actually prefer "make xconfig".

Perhaps I somehow offended you to cause you to "point a finger" with the emboldened you but I honestly was trying to be polite but you are right.... it has been roughly 3 months since I last compiled something from source but my memory isn't that bad yet It was still accurate since "make clean" is only invoked if a config has errors and must be redone and never used on a trouble free build and in 14 years of using Linux I have never met one single person who compiles kernels with "make config". Then, come to think of it, I've never met Richard Stallman.... he might.
 
Old 07-14-2014, 06:26 PM   #20
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,713

Rep: Reputation: 535Reputation: 535Reputation: 535Reputation: 535Reputation: 535Reputation: 535
Quote:
Originally Posted by enorbet View Post
I'm well aware that "make mrproper" nukes any previous changes as does "make clean" which is why either comes BEFORE any manner of config. I have only ever used "make clean" on kernel source if I botched a kernel config. The major point was the sequence. The minor point was the choice of commands.

Sometimes making things easier is a bad tradeoff or at least one that must be considered carefully, however I see no advantage whatsoever to "make config" over "make menuconfig" and once I got over "posing 1337" I came to actually prefer "make xconfig".

Perhaps I somehow offended you to cause you to "point a finger" with the emboldened you but I honestly was trying to be polite but you are right.... it has been roughly 3 months since I last compiled something from source but my memory isn't that bad yet It was still accurate since "make clean" is only invoked if a config has errors and must be redone and never used on a trouble free build and in 14 years of using Linux I have never met one single person who compiles kernels with "make config". Then, come to think of it, I've never met Richard Stallman.... he might.
Maybe you should take my posting name. It seems to fit you better.

I haven't compiled a kernel in years. You can run "make clean" any damned time that you wish without worrying that it will remove the configuration that you have set via "make what-ever-the-eff-config" WHICH IS WHAT YOU BLOODY WROTE.

Quote:
[...] running "make clean" after it [E.B. "make config"] would destroy anything you did anyway by returning it to generic source.
You just end up compiling more stuff than perhaps you had to, but that is scarcely the "only" time that you can do so.

FWIW, I actually preferred "make xconfig", myself. Unless I was using ssh to recompile the kernel on a box with no monitor and did not want to *bleep* around with exporting an X display back to the machine upon which I was typing. Or didn't install the Nvidia blob for my desktop because (gasp) I hadn't recompiled my kernel yet.
 
Old 07-14-2014, 06:33 PM   #21
genss
Member
 
Registered: Nov 2013
Posts: 558

Rep: Reputation: Disabled
try make nconfig
ncurses one
 
Old 07-16-2014, 11:39 AM   #22
enorbet
Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware 14 is Main OpSys on Main PC, 2ndary are OpenSuSe 13 and SolydK
Posts: 800

Rep: Reputation: 393Reputation: 393Reputation: 393Reputation: 393
Quote:
Originally Posted by BobKay View Post
@hitest, I ended up following that exact procedure and it worked a charm!

@enorbet, what on earth makes you think I feel kernel building is "antiquated and useless"? I'm just trying to get a new system up and running with a minimum of muss and fuss and I don't want to go through the trouble of building a custom kernel if it's not absolutely necessary at this time. <snip>
My apologies BobKay (and everyone caught in the splatter) apparently I misunderstood. It does seem that I made a mountain out of a molehill. It's probably just the state I'm in with allergies and antihistamines - hard to tell which is worse, the problem or "the cure".

Last edited by enorbet; 07-16-2014 at 11:40 AM.
 
Old 07-18-2014, 04:15 AM   #23
gabytf
Member
 
Registered: Jun 2010
Location: Kota Kinabalu, Sabah, Malaysia
Distribution: Slackware64 14, -current
Posts: 163

Rep: Reputation: 1
If just for the kernel upgrade, I normally do commands as follow for my -current 64bit, but since you are at Slackware 14.1 you need to change the -current to 14.1(don't forget the . at the end is also part of the command):

1. bash-4.3# rsync -av rsync://slackware.org.uk/slackware/slackware64-current/slackware64/a/kernel-* .
2. bash-4.3# rsync -av rsync://slackware.org.uk/slackware/slackware64-current/slackware64/d/kernel-* .
3. bash-4.3# rsync -av rsync://slackware.org.uk/slackware/slackware64-current/slackware64/k/kernel-* .

open Terminal at the kernel downloaded directory,

next use pkgtool,select "install packages from the current directoty" to install the kernel-firmware, kernel-headers, kernel-huge, kernel-modules and kernel-source.

type "lilo" at the bash.
and, reboot your system.
 
  


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
[SOLVED] Upgrade to Kernel 3.2.45 - upgrade initrd and reinstall LILO? qlands Slackware 1 07-03-2013 02:15 AM
How to upgrade kernel in rhel6/centos6 with internet. manually download and upgrade. Gil@LQ Linux - Kernel 3 03-12-2012 05:07 PM
how to upgrade the Debian 3 kernel 2.4.18 to kernel 2.6 or bigmem- kernel chandu.bezawada Debian 6 11-12-2010 09:33 AM
apt-get upgrade does not upgrade my kernel halfpower Debian 5 12-11-2005 09:53 AM
What first upgrade kernel or upgrade slack 10.0 to current Kelean Slackware 7 01-16-2005 06:54 PM


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