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 03-14-2005, 01:36 AM   #391
suraka
LQ Newbie
 
Registered: Mar 2005
Location: Australia
Distribution: Slackware 10.1
Posts: 6

Rep: Reputation: 0

thanks for taking the time to look through my site kornerr.. i was a little dissapointed to see so many "problems" but it is still constructive criciticism so i welcome it

im aware of the problem of the text running off of the screen.. thats a result of me using <pre> tag's for any code i want to add in. i cant really be bothered finding a fix for this.

as for "X Window", ill take your word on it. changed the header

i realise not everyone would want to change the default init level. its up to the reader whether or not he wants to follow that step or not. ive simply added it in for those who DO want to change it, so the quick and easy step is there. thats the kind of philosophy ive written everything under, on a "take what you need" basis. personally i dont touch the initlevel myself, but for the day i want to, i dont have to look any further than my guide.

Quote:
1)no info about topical sound problem with intel_sound_on_board
2)no info about duplex sound
i dont have intel on-board sound, so its not an issue for the hardware described at the top. however i do have a laptop with intel on-board sound, so if you know how to get it working id love to add it in. what do you mean by duplex sound? i just followed those instructions on my sblive! and it works wonderfully.

you're right about the web site being broken, you're the first person to tell me! who knows how long its been like that. i dont know what went wrong, i simply re-uploaded the pages and it worked. one of the files were missing, and the other one seemed to be corrupt (partially uploaded). oh well. its fixed now, cheers.

yes the guide is inappropriate for newbies. but if you have basic console skills, and know how to operate a text editor, i think you'll find thats all of the knowledge/skills you need to have in order to understand most of the steps. i did mention its not full-featured documentation before

well that sums up my reply.. thanks for your thoughts
 
Old 04-11-2005, 11:15 AM   #392
piete
Member
 
Registered: Apr 2005
Location: Havant, Hampshire, UK
Distribution: Slamd64, Slackware, PS2Linux
Posts: 465

Rep: Reputation: 44
I thought it'd be appropriate to add my own collection of bits & pieces I've learnt here. Forgive me if that's not the intention, I'm new here

www.kaear.co.uk

The large section on the left titled "Linux Notes" contains a few marginally coherent articles on Slack, that if one person finds useful, will have been worth while =)

To start as we mean to go on ... let's see if I can't help out!

To BenneJezzerette:

First of all, forgive me if I misunderstand your question.

"Will the new Kernal understand this [that I am using ReiserFS] or hose my system and make my drive a 528MB drive?"

When you build a new kernel, the rest of the system is unaffected. At worst, the new kernel doesn't work and you'll have to use a boot disk to try again ... not a problem, merely a mild inconvenience.

When you build a new kernel, be sure to include the ReiserFS partition support and nothing should change when you reboot using the new kernel.

I always keep lilo.conf set up like this:

Code:
# Linux bootable partition config begins

# This is the default kernel that comes with Slackware.  Handy if everything else fails.
image = /boot/vmlinuz-2.4.26
root = /dev/hda2
label = DefaultSlack
read-only

# Kernel under test.  ie:  The last kernel that was built & installed.
# Only valid for 2.6's "make install"
image = /boot/vmlinuz
root = /dev/hda2
label = KernelUT
read-only

# The old kernel that the above replaced, just in case.
# Again, only valid with 2.6 "make install"
image = /boot/vmlinz.old
root = /dev/hda2
label = OldKernel
read-only
I suspect you will have to make certain that "make install" is copying and moving the files around your system correctly. You'll find the "make install" script for 2.6 here: /usr/src/linux/arch/i386/boot/install.sh

I suspect that was all rather too much, but the long and the short of making new kernels is: always make sure your old kernel is available to boot from! You'll find my contact details on www.kaear.co.uk if you wanted a simpler set of instructions - or start a new thread, I'd be happy to help!

- Piete.
 
Old 04-11-2005, 01:01 PM   #393
resaguk
Member
 
Registered: Aug 2004
Location: Leamington Spa, UK
Distribution: Slackware
Posts: 66

Rep: Reputation: 15
Quote:
Originally posted by piete
contact details on www.kaear.co.uk
Hi Piete,

The website appears to be down...
 
Old 04-11-2005, 01:17 PM   #394
BenneJezzerette
Member
 
Registered: Mar 2005
Location: In a Box where Slackware Rocks
Distribution: Slackware 11 -current
Posts: 274

Rep: Reputation: 30
Quote:
Originally posted by resaguk
Hi Piete,

The website appears to be down...
Confirms, site down for me too
 
Old 04-12-2005, 06:59 AM   #395
piete
Member
 
Registered: Apr 2005
Location: Havant, Hampshire, UK
Distribution: Slamd64, Slackware, PS2Linux
Posts: 465

Rep: Reputation: 44
Wretched site works perfectly until someone goes to look at, I'm sure. Rats. It seems ok at the moment, but do tell me if it flops again.

BenneJezzerette: I'm going to write up some personalised instructions for you to follow, to make sure we're all on the same page, and then we'll go from there. Bear with me and try not to fret!

- Piete.
 
Old 04-12-2005, 08:00 AM   #396
piete
Member
 
Registered: Apr 2005
Location: Havant, Hampshire, UK
Distribution: Slamd64, Slackware, PS2Linux
Posts: 465

Rep: Reputation: 44
Hopefully the site will work ok now, but I didn't wish to clutter this thread much more than I've already done so!

www.kaear.co.uk/default.asp?pageID=36

I haven't had time to pretty it up, my apologies for that. I hope it's reasonably easy to read.

- Piete.
 
Old 04-12-2005, 12:19 PM   #397
BenneJezzerette
Member
 
Registered: Mar 2005
Location: In a Box where Slackware Rocks
Distribution: Slackware 11 -current
Posts: 274

Rep: Reputation: 30
Quote:
Originally posted by piete
Hopefully the site will work ok now, but I didn't wish to clutter this thread much more than I've already done so!

www.kaear.co.uk/default.asp?pageID=36

I haven't had time to pretty it up, my apologies for that. I hope it's reasonably easy to read.

- Piete.
Ok, it is working now, thank you.

I am going to look and see what I missed, I know it's something. Just can't get my finger on what it is.
 
Old 04-14-2005, 09:24 PM   #398
slackware1299
Member
 
Registered: Apr 2005
Location: USA
Distribution: Slackware 10.1
Posts: 46

Rep: Reputation: 15
hey, I am about to attempt to upgrade my kernel to 2.6.7.11
two questions
1) is there anyway of making a backup of the old kernel, and then making LILO have an option to boot to that, so that if the new kernel doenst work, I can always load the old kernel as a backup, and switch anything if I screwed up in it, so i have like options slackware-2.4.2 adn windows and slackware-2.6.7.11
2)i just downloaded the new kernel like 40 mb, and it came with two files, the kernel 35 mb, and a small patch file, do I have to run the patch file in any special way after I've installed the new kernel or anything with it, you didnt mention this in your tut, which is very nice

sorry if any of these 2 questions have been posed before, this is a huge thread and I was too lazy to look through it all, looked like mostly people talking about how great the tut was,

thanks for your help

~wsoprulz1299
 
Old 04-14-2005, 11:07 PM   #399
BenneJezzerette
Member
 
Registered: Mar 2005
Location: In a Box where Slackware Rocks
Distribution: Slackware 11 -current
Posts: 274

Rep: Reputation: 30
Quote:
Originally posted by slackware1299
hey, I am about to attempt to upgrade my kernel to 2.6.7.11
two questions
1) is there anyway of making a backup of the old kernel, and then making LILO have an option to boot to that, so that if the new kernel doenst work, I can always load the old kernel as a backup, and switch anything if I screwed up in it, so i have like options slackware-2.4.2 adn windows and slackware-2.6.7.11
2)i just downloaded the new kernel like 40 mb, and it came with two files, the kernel 35 mb, and a small patch file, do I have to run the patch file in any special way after I've installed the new kernel or anything with it, you didnt mention this in your tut, which is very nice

sorry if any of these 2 questions have been posed before, this is a huge thread and I was too lazy to look through it all, looked like mostly people talking about how great the tut was,

thanks for your help

~wsoprulz1299
take a look at the compile errors Linux 2.6.XX and read carefully the things that you are going to encounter as I just posted the information of where the errors come from, and now all I need to do is find the links, but it has to do with modules as they are becoming depreciated. Read please there are only two pages so far for the thread.
 
Old 04-14-2005, 11:07 PM   #400
shilo
Senior Member
 
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132

Original Poster
Rep: Reputation: 50
Quote:
I am about to attempt to upgrade my kernel to 2.6.7.11
I am going to assume that you mean 2.6.11.7.

In response to 1)

Yes. There are many ways to compile a kernel. Here's what I do to maintain control of the entire process.

Step 1

Get the kernel source. Get it from kernel.org or an official mirror. Note there are several ways you can get a new kernel. You can get the full source or one of a couple patches. The patches that I am refering to are for upgrading from an earlier kernel version. This should not be confused with other patches like the -mm or -ck patches. I recommend the full source for new kernel compilers. Less to do that way.

Now that is universal. The next parts can vary widely depending on who you ask. They can also differ for other distros, believe it or not. This way will work on Slackware, though, for sure. After youve got the source (something like linux-2.6.11.7.tar.bz2) place it in your /usr/src directory.

Step 2

Gonna go fast here. Gonna also asuume that you are using a stock Slackware kernel. As such, the config for your kernel will be in /boot/config-ide-2.4.29 (I'll assume that is the case, if not adjust accordingly).

Code:
cd /usr/src
tar -xvjf linux-2.6.7.tar.bz2
cp /boot/config-ide-2.4.29 /usr/src/linux-2.6.11.7/.config
rm linux
ln -s /usr/src/linux-2.6.11.7 /usr/src/linux
cd linux
make oldconfig # you will be prompted with a series of questions. "?" is the best answer. :)
make xconfig #or make menuconfig if you prefer.  Make your choices.  Pay attention.  This is the hard part.
make bzImage
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.11.7
make modules
make modules_install
cp System.map /boot/System.map-2.6.11.7
cp .config /boot/config-2.6.11.7
Now all that isn't what you asked about, but I include that because this method leaves lilo alone and allows you to name your kernel whatever you please. The next step is what is important. Open up /etc/lilo.conf in the editor that you are most comfortable with. Find a section that looks like this:

Code:
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.29
  root = /dev/hda1
  label = Linux-2.4.29
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
It's at the end. Mkae a copy of it, so it looks like this:

Code:
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.29
  root = /dev/hda1
  label = Linux-2.4.29
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.29
  root = /dev/hda1
  label = Linux-2.4.29
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
OK, with me so far? Now the top one is gonna need some editing, so make it look something like this:

Code:
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.11.7
  root = /dev/hda1
  label = Slk-2.6.11.7
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.29
  root = /dev/hda1
  label = Linux-2.4.29
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
You can use whatever you like for the label, but there is a size limit. Save and exit.

Now, run:

Code:
/sbin/lilo
Make sure there are no error messages. If there are, correct the errors before rebooting.

I am assuming that you already had an option to boot Windows. That will be unaffected by this, so long as you left it in tact. Note, the key is add to /etc/lilo.conf. Never take away.

A quick sidenote, most already have their computer setup to prompt them at boot time. If not, make sure you have some lines like the following towards the top of /etc/lilo.conf

Code:
prompt
timeout = 600
The value for the timeout is the number of (seconds x 10) that lilo should wait before booting the default kernel.

go ahead and reboot. If the new kernel doesn't work perfectly, just reboot and choose the old kernel. Then, feel free to start over again. Just change to /usr/src/linux and start with "make xconfig".

In response to 2)

The full source for 2.6.11.7 is like 35.4MB on my system. The patch file is most likely not needed. That would be used to patch older source. Since you already have the full new source, no need to apply the patch (it will do nothing). I would recommend sticking with the full source until you are comfortable. Then, you can move on to patching source.

***EDIT***

Feel free to ignore any compiler warnings that you may see. The only ones that matter stop the compile process, so the error will be the last line. If the last line tells you that bzImage is ready, you are A-OK.

Last edited by shilo; 04-14-2005 at 11:09 PM.
 
Old 04-14-2005, 11:17 PM   #401
BenneJezzerette
Member
 
Registered: Mar 2005
Location: In a Box where Slackware Rocks
Distribution: Slackware 11 -current
Posts: 274

Rep: Reputation: 30
Shilo, did you read?? I found it I found it. Yes successful compile with just the intermodule error and the post tellls you why. I will be back later if all is well and let you know. Everything looks good for the Linux 2.6.11.7 so far.
 
Old 04-14-2005, 11:22 PM   #402
shilo
Senior Member
 
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132

Original Poster
Rep: Reputation: 50
Yes, I read, though in all honesty, your writing style is difficult to understand and I assertained nothing from the post, other than you have some understanding of makefiles and c source files.

Congratulations, just the same. Don't be to sad if it doesn't work the first time. It's gonna all work real soon, I'm sure.

Read the above post on my methodology for compiling a kernel. It is important to ensure that your original kernel still boots in case of errors. That will save you MUCH headache, especially on slower hardware.
 
Old 04-15-2005, 12:15 AM   #403
BenneJezzerette
Member
 
Registered: Mar 2005
Location: In a Box where Slackware Rocks
Distribution: Slackware 11 -current
Posts: 274

Rep: Reputation: 30
Quote:
Originally posted by shilo
Yes, I read, though in all honesty, your writing style is difficult to understand and I assertained nothing from the post, other than you have some understanding of makefiles and c source files.

Congratulations, just the same. Don't be to sad if it doesn't work the first time. It's gonna all work real soon, I'm sure.

Read the above post on my methodology for compiling a kernel. It is important to ensure that your original kernel still boots in case of errors. That will save you MUCH headache, especially on slower hardware.
going to have to try again, something seems to have gotten lost, the Vmlinuz file got lost somewhere and everyone of them were 2.4.29 odd too since I did what was told. As for my writing style, well some just have problems reading it because it is lengthy, not short and limited. But then I guess coming from old school to now, well I jut have a long way of getting things done. Had to delete everything and will start over again. Reads again all the things and then will painstakingly go through and fix it again.
 
Old 04-15-2005, 02:45 AM   #404
shilo
Senior Member
 
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132

Original Poster
Rep: Reputation: 50
Quote:
the Vmlinuz file got lost somewhere
The beauty of simplicity. Translation: Man, I love using my kernel compile method. You know exactly where to find the kernel you just made.

Too late now, but I can tell you where you will most likely find a copy of that kernel you lost. There is most likely a copy in /usr/src/linux-2.6.11.7/arch/i386/boot. It's gonna be called bzImage. Just cp it to boot, but with a better name, like vmlinuz-2.6.11.7. If you already toasted that last attemt, though, the advice comes a litlle late.

Quote:
As for my writing style, well some just have problems reading it because it is lengthy, not short and limited.
Well, that is one view. Another would be that the reason it is difficult to read is because of grammatical errors and confrontational style. The latter should probably be worked on. The former is a tricky issue. While everyone has typos and such, you tend to have run-on sentances which make it near impossible to decipher their meaning. I don't mean that to sound harsh at all, but a simple example is this:

Quote:
going to have to try again, something seems to have gotten lost, the Vmlinuz file got lost somewhere and everyone of them were 2.4.29 odd too since I did what was told.
This makes very little sense. I am sure it makes sense to you, but (again no offense intended) from your screen name and writing style my first assumption was that you were not a native English speaker. To top it off, this also displays what I consider to be a confronational attitude of, "Hey, I am just following instructions. This is not my fault. Therefore it must be the fault of the instruction giver."

Quote:
Reads again all the things and then will painstakingly go through and fix it again.
Simplify. Follow the simple instructions that I posted just a few posts up. Then, you'll be on the same page as someone, instead of all alone with your unique method. If the above method fails for you, simply post stating where it has failed. Easy to do. Easy to help with.
 
Old 04-15-2005, 12:31 PM   #405
BenneJezzerette
Member
 
Registered: Mar 2005
Location: In a Box where Slackware Rocks
Distribution: Slackware 11 -current
Posts: 274

Rep: Reputation: 30
Thumbs up

Hello Shilo,

Well I thought it through, and from all instances of the error, it tells me that I do not need to, Make, or have modules set. Is that what you see there? Read the second code window and see the actual intermodule.c file. I did not write it.

Yes, I guess I can be confrontational. No, I was born in America, I have just had to learn things on myown, because the information others give me, seem to be good, but some is not acceptable. All the prints I have of the instructions here, seem to be of the former, and good information. They all basically explain the same thing, but leave out the actual part of Creating the Information that is stored in the BZImage ot VmLinuz File, or System Maps. This is an important part of the Building blocks to make this happen.

In my actions while figureing this out. I have:
Found the NIC problems
Discovered the intermodule.c issues (Finally) - From a alt.os.linux.slackware newsgroup no less.

Now, I am going to work this out again, and this time, no modules at all, at least that is what the intermodule.c file suggests. Please tell me if I am wrong. Before I actually make this happen, but I have a feeling this time, that I never had before, that what is said here, is what is right. My next compile trial and installshould actually work and have no flaws. I will re read the post of yours, and then write it, not print it, down and keep it nearby to make sure I make this work like you have suggested. Once again, thank you for this Chatter back and forth, as it has given both of us a lot to work with.

My punctuation, does need work. Someday I will make great strides in my written skills. Small steps right now. Be good and have a great day.


EDIT#1
Your Post Instructions
Read some of it, and notes, No need for make modules with the Linux 2.6.11.7 as they have done that for you.

Last edited by BenneJezzerette; 04-15-2005 at 12:36 PM.
 
  


Reply

Tags
kernel


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



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

All times are GMT -5. The time now is 01:13 PM.

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