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 10-16-2013, 10:25 AM   #1
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 87

Rep: Reputation: Disabled
New Slacker: Some Observations


Hello

I have recently installed Slackware 14.0

History-

I had tried to initially install it around 2-3 months before.

First when I tried, I got kernel panics, but I searched for it and found that using rootdelay=10 solved that problem.

Then I couldnt get my wifi connection up and also couldnt use startx.

Then some days earlier I tried it again, and I thought, am I doing something wrong as startx: command not found ?

Perhaps I had downloaded a minimal edition?
Then I again went to the Get Slack page and saw that there were many CDs needed.
Using the first CD, it installed the basics, and even though I had selected the GUI, it didnt install it.(no warning)
So I downloaded the 2nd CD also, and reinstalled.

One question I ask- why use Lilo?
I has to reinstall lilo like 5-6 times. It (mostly)failed on its own.
Sometimes I got the following error-
"L 99 99 99 99 99 99 99 99 99 99 99 99"
and once-
"The kernel overlaps with...."
I had to reinstall it many times by using the install disk -> Select / partition -> Customise and reinstalled Lilo.

Solution-How about using syslinux? Its in the repos.

Secondly I cant work with the initrd..whenever I use it I get stuck in the initramfs while booting.
I created the initrd according to the installation instructions.
Now I dont know whether (perhaps) its because of Lilo not using the append rootdelay=10 for my second entry, or due to something else.

And third I cant find a volumeicon for my system tray.

Thanks.
PS. I mean them more like suggestions than criticism

Last edited by aaditya; 10-16-2013 at 10:39 AM. Reason: Added Lilo content
 
Old 10-16-2013, 11:18 AM   #2
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,190

Rep: Reputation: 548Reputation: 548Reputation: 548Reputation: 548Reputation: 548Reputation: 548
Welcome to the official Slackware forum. I suggest that you read the book. Many topics are covered: partitioning,installing software, etc.

http://www.slackbook.org/html/index.html
 
Old 10-16-2013, 11:54 AM   #3
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 87

Original Poster
Rep: Reputation: Disabled
Will have a look, thank you

Now that I have gotten myself to the forums, I will read the stickies as well as time permits.
 
Old 10-16-2013, 01:21 PM   #4
Bazzaah
Member
 
Registered: Mar 2007
Distribution: Slackware64-current, Slackware64 14
Posts: 327

Rep: Reputation: 49
Have a look here too

http://docs.slackware.com/slackware:beginners_guide
 
Old 10-16-2013, 08:49 PM   #5
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Mageia, Mint
Posts: 7,919

Rep: Reputation: 1494Reputation: 1494Reputation: 1494Reputation: 1494Reputation: 1494Reputation: 1494Reputation: 1494Reputation: 1494Reputation: 1494Reputation: 1494
There's also http://slackwiki.com/Main_Page
 
Old 10-16-2013, 10:07 PM   #6
zrdc28
Member
 
Registered: Dec 2007
Location: Alabama USA
Distribution: Slackware current
Posts: 250

Rep: Reputation: 40
If you will download and install from the dvd you will not have those problems. Do a full install and write lilo
to the mbr.
 
Old 10-19-2013, 06:18 AM   #7
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 87

Original Poster
Rep: Reputation: Disabled
Updates-

1.) Unable to get Syslinux working. So using Lilo

2.)Initrd problem I figured out-
The error I used to get was
Code:
No kernel modules compiled
http://i1198.photobucket.com/albums/.../slackware.png

So I again ran the command from the wiki in order to take a screenshot of it to post here, and I noticed something

http://i1198.photobucket.com/albums/...slackware2.png

Following the wiki, I was adding the following to lilo.conf
Code:
image = /boot/vmlinuz-generic-3.2.29
  initrd = /boot/initrd.gz # add this line so that lilo sees initrd.gz
  root = /dev/sda1
  label = Slackware
  read-only
But I noticed that the kernel modules were being complied for the smp-kernel, not the generic one!

So after I changed the entry in lilo that also works.

3.)volumeicon
I was able to install it from slackbuilds.org

However on trying to increase the root partition size, I may have damaged it.
So may need to re-install.

I have another question which is partitially answered-
4.)Can I do an inplace upgrade without the CDs, like Debian?
And on searching I found slapt-get, which may do the job
But I am a little unclear on this..for the update(upgrade?)to 14.1, will slackpkg update-all do?
Or will I have to use slapt-get?
Thanks!
 
Old 10-19-2013, 06:34 AM   #8
andrewthomas
Senior Member
 
Registered: May 2010
Location: Chicago Metro
Distribution: Arch, Gentoo, Slackware
Posts: 1,690

Rep: Reputation: 307Reputation: 307Reputation: 307Reputation: 307
Quote:
Originally Posted by aaditya View Post
But I noticed that the kernel modules were being complied for the smp-kernel, not the generic one!
This is because the generic (HUGE) kernel has many things built-in.
 
Old 10-19-2013, 07:27 AM   #9
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 85

Rep: Reputation: 26
Something sounds like it went very, very wrong with your install. Did you select a full install? It's usually best until you know how slackware is laid out. And the beginner's guide has actual, useful information. I've been using slackware for a good 10 years, and I still consult it. (Namely because it's information I forget--stuff you only use once a year or so when upgrading or reinstalling.)
 
Old 10-19-2013, 09:33 AM   #10
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 87

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by andrewthomas View Post
This is because the generic (HUGE) kernel has many things built-in.
Nope..I meant generic specifically by name, not by function

The kernel generic in function is the hugesmp, to which vmlinuz is symlinked.
However as given in the Configuration part of the wiki, its said to compile an initrd, and add to lilo the generic(striped-down) kernel + specific modules + initrd.

But as I said, in the wiki, addition to lilo is said for generic, not generic-smp.
(I will edit the wiki when I get an account there )

Quote:
Originally Posted by garpu View Post
Something sounds like it went very, very wrong with your install. Did you select a full install? It's usually best until you know how slackware is laid out. And the beginner's guide has actual, useful information. I've been using slackware for a good 10 years, and I still consult it. (Namely because it's information I forget--stuff you only use once a year or so when upgrading or reinstalling.)
Yes, initially I didnt download CD#2, and thrahed about somewhat, but I learned that as I said in my first post

I consulted the beginners guide, and as I said before, its given incorrect/incomplete there about adding which entry to /etc/lilo.conf after making an initrd, which I will amend when I get access


Edit-

4.) On reading more, I think I will have to use slack-apt to upgrade from 14.0 to 14.1
http://www.slackwiki.com/Upgrade_Using_Slapt-get

Last edited by aaditya; 10-19-2013 at 11:25 AM. Reason: slack-apt
 
Old 10-19-2013, 12:04 PM   #11
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,381

Rep: Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088
Quote:
Originally Posted by aaditya View Post
4.) On reading more, I think I will have to use slack-apt to upgrade from 14.0 to 14.1
http://www.slackwiki.com/Upgrade_Using_Slapt-get
No. Instead, just follow official instructions provided in file UPGRADE.TXT here. That's a lot safer, especially for Slackware newcomers.

Just re-read these instructions when Slackware-14.1 will be released as there could be some changes at that time.
 
Old 10-19-2013, 12:19 PM   #12
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 87

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
No. Instead, just follow official instructions provided in file UPGRADE.TXT here. That's a lot safer, especially for Slackware newcomers.

Just re-read these instructions when Slackware-14.1 will be released as there could be some changes at that time.
Ah, okay

And how to get the packages? Can I use slapt-get for that
 
Old 10-19-2013, 12:31 PM   #13
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,381

Rep: Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088Reputation: 1088
Quote:
Originally Posted by aaditya View Post
And how to get the packages? Can I use slapt-get for that
That's explained in the file itself, just read it.
 
Old 10-19-2013, 12:36 PM   #14
Toutatis
Member
 
Registered: Feb 2013
Posts: 32

Rep: Reputation: Disabled
I suggest that you use only the huge kernel. I never had problems with that.

I always download and install the new packages by hand. No slackXXX is necessary.

The result is that I never had to re-install everything (except on old computers when I moved from slackware to slackware64). Always I did only upgrade. This is a huge difference with other distributions.
 
Old 10-19-2013, 12:43 PM   #15
aaditya
Member
 
Registered: Oct 2013
Location: India
Distribution: Slackware
Posts: 87

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
That's explained in the file itself, just read it.
Sorry, seems like I wasnt paying enough attention

Edit-

Quote:
To do this, you'll need the Slackware 14.1 packages. If these are on a CD,
create a new directory to mount the CD on so that it doesn't get in the way
during the upgrade:

The packages don't have to be on a CD-ROM, as an alternative you could
copy the slackware directory (the one with the various package
subdirectories in it, basically the "slackware" or "slackware64" directory
from the install disc) to someplace like /root/slackware/. The important thing
is that you know where the slackware packages directory is.
The CD would contain other packages that which are required for upgrading, right? like the installer and so on..

So If I didnt want to download the CD, how should I go about it?
(Thats why I said slapt-apt to get the packages)

Quote:
Originally Posted by Toutatis View Post
I suggest that you use only the huge kernel. I never had problems with that.

I always download and install the new packages by hand. No slackXXX is necessary.

The result is that I never had to re-install everything (except on old computers when I moved from slackware to slackware64). Always I did only upgrade. This is a huge difference with other distributions.
Does this mean that Slackware(Stable) is partly rolling then, ie, apt-get dist-upgrade to go from ver 6 to ver 7 ?

Edit-
Sorry for the noob questions i will read some more.

Last edited by aaditya; 10-19-2013 at 12:58 PM.
 
  


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
new 13.1 install observations timetraveler Slackware 9 07-14-2010 07:47 PM
Observations on Slackware 13.0 thirteen_engines Slackware 14 09-26-2009 04:30 AM
/etc/issue observations Woodsman Slackware 4 11-05-2005 10:52 AM
observations of 9.3 irish rebel Suse/Novell 6 06-20-2005 01:28 PM
Gnome 2.8 Observations and Problems utanja Debian 2 11-23-2004 05:56 PM


All times are GMT -5. The time now is 06:44 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration