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 04-15-2005, 01:26 PM   #406
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 do not need to, Make, or have modules set.
If I am understanding the question, the answer to both is "maybe".

I don't use the command "make" all by itself. But that is following the rest of my method. You can use "make", and that is even the method outlined in the kernel documentation. Taking the steps you do now and simply eliminating "make" from them is a bad idea. It just won't work.

You can create a system with no modules if you like. It is called a monolithic kernel. I don't recommend it. You will get meaningless error messages when booting Slackware using a monolithic kernel. This seems to me that you are avoiding a meaningless compiler warning by incurring multiple meaningless runtime warnings. Furthermore, a monolithic kernel means that you will have less control over the hardware drivers (well, easy control, at least). Next issue, any possible driver confilicts become huge issues, as the drivers are always simultaneously loaded. Next issue, the now huge kernel is taking up precious memory. Unless you've got RAM to burn, this means you will experience heavier swapping. This means a slower system. Note that this is a big debate, modular vs. monolithic. You will probably find yourself much happier with a modular kernel.

Quote:
Read the second code window and see the actual intermodule.c file.
I have no clue what this even means.

Quote:
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.
Agreed. The compile options are the only difficult step in compiling a kernel. The rest are easily explained. Note that my post above outlines a kernel compile in just a few short lines. They can be copied and pasted. They will work.

Let's look at what you have noted is missing. The selection of compile option. I have previously pointed you to http://www.linuxquestions.org/questi...65#post1144265 where I take a great deal of time discussing the options and what I choose. That post is an attempt to point others in the right direction. Note the length of the post. This is without what I would consider excessive verbosity. Even this is not enough, as everyone will undoubtedly have different hardware and need different choices.

Quote:
Found the NIC problems
Yet have failed to post your solution so that others may learn.

Quote:
Discovered the intermodule.c issues (Finally) - From a alt.os.linux.slackware newsgroup no less.
I fail to see where in that newsgroup you "Discovered the intermodule.c issues". They were discovered by your compiler, just like everyone else. All I see on the newsgroup is others telling you the exact same thing you are hearing here, which is that intermodule.c causes compiler warnings that can safely be ignored.

An analogy. You are the passenger in a car. The low fuel light comes on. Are you out of gas? No. If you were, the car would stop. What can you as the passenger do? Nothing except tell the driver. If the driver already knows? They say, "Yeah, I know."

This is the situation with intermodule.c. When you run the compiler, a warning (low fuel light) appears. Is it broken (Are you out of gas)? No. If it was, the compiler would stop (the car would stop). What can you do? Nothing except tell the programers (tell the driver). There is no need, though, because I can assure you that the kernel developers already know.

Quote:
this time, no modules at all
Again, I really don't recommend that you attempt to build a monolithic kernel until you can at least build a modular one.

Quote:
that is what the intermodule.c file suggests.
No, it doesn't. Feel free to think it does, as I have no inclination to attempt to teach you how to program with c and gcc just so you can compile a kernel. A bit like using a bazooka to kill a fly.

Quote:
I never had before, that what is said here, is what is right
Then do yourself a huge favor and just follow the above instructions.

Quote:
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.
You might also want to copy and paste it to a text file that you keep open. You can copy and pate much of the instructions right to the command line.

Quote:
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.
This is bothersome to see that you believe this. No, with my method the modules are not created at any step other than "make modules_install". I do not use "make" by itself. This is the step where "they have done that for you." You are confusing yourself reading all the different methods. All the different methods are valid (i.e. they work), butr they are not, for the most part, interchangeable. To clarify, just because one method omits a step like "make modules" does not mean that all methods can omit that step.

Let us, thuogh, assume that you are correct. Then my method still does not break anything, as the modules would then simply be made twice.

Option 1 - use make modules

possibilty A) modules are created once
possibilty B) modules are created twice

Option 2 - do not use make modules

possibilty A) modules are created once
possibilty B) modules are not created

So, option 1 seems to be the clear method of choice. Why not do it my way. When it works, be happy you accomplished something. Then, go back and do it your way. If that works, make a new post detailing your better method. Everyone is always looking for a better method for compiling a kernel. Just look at the number of posts in every thread concerning kernel compiling.
 
Old 04-15-2005, 03:54 PM   #407
BenneJezzerette
Member
 
Registered: Mar 2005
Location: In a Box where Slackware Rocks
Distribution: Slackware 11 -current
Posts: 274

Rep: Reputation: 30
On - Make

On please explain all the make things here.


thank you.


The page is the actual intermodule.c file from the kernel directory. Not my programming.


Looked and is going to continue to look at your page, though it is considerably out dated, as this is all pertaining to the Linux 2.6.11.X Kernels.

NIC = Has the Disk tht comes with my NIC, copied the tulip.c file in to the tulip directory and it finds it automatically and loads for some reason.

Modules is definately a bad idea to leave out. It takes away a lot of things that you may want to have installed. At least this is what I have just discovered as of today.

Will seriously take some time and get some good reading materials on all of this before I make any new attempts, I think my hardware is somewhat out dated, and seemingly flaky. At least with this Kernel 2.4.29 it is stable.

Quote:
This is bothersome to see that you believe this. No, with my method the modules are not created at any step other than "make modules_install". I do not use "make" by itself. This is the step where "they have done that for you." You are confusing yourself reading all the different methods. All the different methods are valid (i.e. they work), butr they are not, for the most part, interchangeable. To clarify, just because one method omits a step like "make modules" does not mean that all methods can omit that step.

Let us, thuogh, assume that you are correct. Then my method still does not break anything, as the modules would then simply be made twice.

Option 1 - use make modules

possibilty A) modules are created once
possibilty B) modules are created twice

Option 2 - do not use make modules

possibilty A) modules are created once
possibilty B) modules are not created

So, option 1 seems to be the clear method of choice. Why not do it my way. When it works, be happy you accomplished something. Then, go back and do it your way. If that works, make a new post detailing your better method. Everyone is always looking for a better method for compiling a kernel. Just look at the number of posts in every thread concerning kernel compiling.


Ok thank you and you seem to have really hit it here. Something is still wrong and not even making now. I need to again redo this system as the compile now give me erros on the make error 1 and 2 and not very explanatory either. Maybe if I just wait till I get the book too and have time to read as I go then it could be beneficial, and your instructions could be included, as I really like a lot of the things you have done here. Like I said, though, I think I am sticking with what works and not going to break it again. Thank you for the time and patience. I made that decision and am going to stay with it. At least for now.
 
Old 04-15-2005, 04:00 PM   #408
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
If I am understanding the question, the answer to both is "maybe".
Ok took a long look here at your setup, and if you look at my as I did it list, it's basically the same excepting that it is for the newer Kernel. With a few differences as the Processor and Some IDE information maybe different.
 
Old 04-15-2005, 08:07 PM   #409
slackware1299
Member
 
Registered: Apr 2005
Location: USA
Distribution: Slackware 10.1
Posts: 46

Rep: Reputation: 15
shilo- i just decided to follow the instructions on the first page instead
and i went through everything, did make gconfig and changed all the stuff w/ wmlinuz

i changed lilo, did /sbin/lilo
and rebooted, however I restart computer
and first thing I see weird is that in LILO one of the options is Linux, I changed this in LIlo to slackware 10.1, so it didnt seem like it had changed what i had told it to( i put that as label) and then i did linux and I get the following error:

Code:
Boot:Linux
Loading Linux.........................
BIOS data check successful
Uncompressing Linux

invalid compressed format (err=1)

--System halted
at that point i cant do ctr alt del to restart computer or do anything. All I can do is just turn off computer.

Anyone know what has happened? I followed all the instructions, seems like maybe something with LILO

Last edited by slackware1299; 04-15-2005 at 08:39 PM.
 
Old 04-16-2005, 01:14 AM   #410
BenneJezzerette
Member
 
Registered: Mar 2005
Location: In a Box where Slackware Rocks
Distribution: Slackware 11 -current
Posts: 274

Rep: Reputation: 30
Found a new one today, this is a really fast one too

Not too sure how it works but.....


make defconfig

It scrolls so fast that you can't read it.
 
Old 04-16-2005, 06:47 PM   #411
slackware1299
Member
 
Registered: Apr 2005
Location: USA
Distribution: Slackware 10.1
Posts: 46

Rep: Reputation: 15
anyone know what I can do about the above problem?
do i have to reinstall linux again....
and anyone know what I did wrong, so that I dont do it again
 
Old 04-16-2005, 07:40 PM   #412
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
anyone know what I can do about the above problem?
do i have to reinstall linux again....
and anyone know what I did wrong, so that I dont do it again
I canunderstand your issue, I have had to reinstall this Slackware 5 maybe 6 times now with the instructions from here. No issues against the ones who posted, just the out dated information. Ifiled a bug for the new Linux Kernels http://bugzilla.kernel.org/show_bug.cgi?id=4504 and if you want you can vote on it too. Seems someone was kind enough to change just one thing and forget the balance of the files it affects when it is removed, and or modules are left out to stop the problems.


One thing, when you compiled your kernel, did you make sure the filesystem was the same as what you use by default? If not then this may be why your system crashed.

Now to fix this withoput reinstlaling Linux again. Slackware Disc 2 is an emergency Boot Disc and Will load the Drive and run it. then all you have to do is change the LmVolumz in the /boot directory to the old one. KDE makes it pretty simple. Open up the Control Center, then get to the last thing on the menu, System Admin and find the Lilo Boot Manager. Find the second tab and select it. Choose the Working Kernel off the list and make it default. Then apply it. Say ok, or yes to any messages that come up. Then restart your system, taking the cd out of the drive, test the system boot, it should work. If this works and you can get back to your Linux Box then be sure to vote for the bug on the new Kernels.
 
Old 04-17-2005, 03:49 AM   #413
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.

well Finally got the Linux 2.6.11.7 Installed and all but a few things are working. agpart and ide-scsi other than that all works. My console is old 80x40 style, big lettering, my sound is grumbly but will redo the alsa driver installer and then it should be fine. The system made the vmlinuz and system map into the main or very top root directory, so had to do some tricks for lilo to get it working finally. All in all this is one heck of an experience for me, I tried to cp the files but they were not in the places the instructions stated. So I think the make install is what did it. But at least now I have the Linux 2.6.11.7 working 98%, nic is good, sound and console display need some work. Other than that all is good.
 
Old 04-17-2005, 03:51 AM   #414
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
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.
Hi finally got 98% Linux 2.6.11.7 working NIC is good and the only things are the console and the sound. The sound I think I can fix. Something somewhere messed up, agpart and ide-scsi or scsi-ide did not load. No kernel panics either.
 
Old 04-17-2005, 01:44 PM   #415
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:
anyone know what I can do about the above problem?
do i have to reinstall linux again....
This is covered many times on the forum. No re-install required. Follow the directions here:

http://www.linuxquestions.org/questi...84#post1429784

There are a couple methods outlined. I prefer them in reverse order, i.e. I would try the last method first. Note also that he references /dev/hda2. You have to actually know where Slackware is installed.

Note that the error message you recieved is telling you that your kernel is not in the bz2 format. You are probably pointing to the wrong file. Why don't you have an option to boot into your old kernel? The method I posted at your request will ALWAYS leave you with an option to boot your old kernel.

Quote:
and anyone know what I did wrong, so that I dont do it again
The best guess is you made an error in /etc/lilo.conf. It can be confusing, which is why I took the time to make a new write up for you (that you decided not to follow). The reason I think most people get confused is simple. Symlinks. When you first install Slackware, you have a kernel. It's named something like /boot/vmlinuz-ide-2.4.29. There is a symlink pointing to it called /boot/vmlinuz. That can be tricky, because the /etc/lilo.conf you usually end up with from setup points to the symlink and not the actual kernel.

There are a couple different ways to handle this situation. My old method, as outlined in my guide and on my website, was to destroy the symlink, make a new symlink pointing to my new kernel, change the symlink reference in /etc/lilo.conf to the actual kernel, and add a new /etc/lilo.conf entry for the new kernel. I think that many people are confused by this, and it is also completely un-needed. I now recommend leaving the symlink in place, requiring no changes to /etc/lilo.conf other than the addition of the new kernel. This is the method I outlined for you at your request. I even added some extra stuff just to keep you from getting confused in a manner similar to BenneJezzerrette.

To summarize, look at the bottom section of /etc/lilo.conf and verify that each of the entries points to a valid kernel. Don't point to symlinks, as that tends to confuse people.

Quote:
No issues against the ones who posted, just the out dated information.
So you have a 1990 Chevy pickup truck. You have a 1989 manual. You can still use that manual. It's basically the same truck, as no changes were made. That is a great analogy.

The guide outlines how to compile a 2.6.7 kernel. You can use the same method for any 2.6 series kernel. The fact that there are other ways is irrelevant. Look, you followed the other methods (i.e. make, make install) and had to wonder why it didn't work.

Quote:
My console is old 80x40 style
If you don't like it, check out /etc/lilo.conf. Look for "vga =" and see the commented examples.

Quote:
agpart and ide-scsi other than that all works.
This is an incomplete sentence. What doesn't work about them? Making a total stab in the dark, what you are saying is that you get error messages at boot time about not being able to load these modules. Making another huge guess, based on the first huge guess, the reason is that you compiled agpgart and ide-scsi into the kernel instead of as modules. Recompile and change these two to get rid of the boot errors. Or ignore them, they aren't hurting anything.

Quote:
I tried to cp the files but they were not in the places the instructions stated. So I think the make install is what did it.
It would be helpful if you referenced which instructions you followed. Following my instructions and also using make install is just a bad idea.

Quote:
The system made the vmlinuz and system map into the main or very top root directory, so had to do some tricks for lilo to get it working finally.
It's not a good idea to "do some tricks for lilo". Just copy the kernel and the system map from the root directory into boot. No trickery required. This way, you don't have a system that is spread all over creation. That is a good thing when you ask for help, since then your system is set up just like everyone elses. In other words, if you drive a FIAT, don't be suprised when you can't find parts.

Quote:
Ifiled a bug for the new Linux Kernels
Have you read the response? Yeah, it's NOT A BUG!!!! The developer has been nice about the way he said it.

Quote:
did you make sure the filesystem was the same as what you use by default
This might just be poor phrasing, but it seems to imply that only one filesystem should be used. You need your root filesystem compiled into the kernel if you wish to boot without initrd. You are free to have ALL the filesystems, though. There is no limitation to just one.

Quote:
If not then this may be why your system crashed.
Not based on the error he recieved. The error message for that is distinctly differrent.

Quote:
KDE makes it pretty simple.
If it works. Otherwise, KDE makes the actual process pretty obscure, and you are left still wondering what to do.

Quote:
Found a new one today, this is a really fast one too

Not too sure how it works but.....


make defconfig

It scrolls so fast that you can't read it.
That's great. You've come full circle. One of your major complaints was the use of the defconfig file to set your compile options, and now you figured out how to manually load that file. To clarify, you have hit on the command to set up your kernel in exactly the manner that you have been complaining about. Before, it was simply loaded and you had the option to change the slelections, with the "make defconfig" method, you have skipped the part where you actually change the selections.

Tip: shift+PageUp when stuff scrolls by too fast.

Quote:
shilo- i just decided to follow the instructions on the first page instead
Well that's OK. I only posted the new instructions that you requested in attempt to improve my typing speed.
 
Old 04-17-2005, 03:10 PM   #416
BenneJezzerette
Member
 
Registered: Mar 2005
Location: In a Box where Slackware Rocks
Distribution: Slackware 11 -current
Posts: 274

Rep: Reputation: 30
hi, since have redone the install, Will be working out the details as I go. So far the Successful Install was more a real life test, than keeping it. This is one of the things Ifound that was also causing the problems.

Block Devices
Loopback - This is used to actually see and utilize the Ram Disk you make. If you do not use this, then things seriously go wrong, and this is from My EXPERIENCE with these trials. That is the one thing I made the change to, and it made all the difference in the world.

So now I have a lot better understanding of what I was doing wrong.

One other thing is I2O, this also needs to be enabled for the Alsa Drivers since it uses this function. Otherwise the sound is set off, or garbled as it was on mine.

So far these are the MAJOR things not covered here. Yes, know in your post you mentioned them, but did not set them. The newer Linux 2.6.11.X has to have this on to enable better I/O handling.

Graphics support in the Console

Suggestions --- Leave it off and you should get what Lilo says. I had tried some o fthe fonts and well, my mistakes told me not to. So this is why I suggest not to use the support exceptinng on the main Graphics and Character Settings. This is all for now, and with the help of shilo and several others, this list has been given freely to you so tha you can incorporate it into the new 2.6.11.X Instructions. You will find less crashes with this, and hopes that everyone enjoys the new Linux 2.6.11.X Kernels.
 
Old 05-03-2005, 11:52 PM   #417
ArmOrAttAk
Member
 
Registered: May 2005
Location: NYC
Distribution: Slackware, Gentoo
Posts: 30

Rep: Reputation: 15
I've read this whole thread.
 
Old 05-04-2005, 12:27 AM   #418
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 ArmOrAttAk
I've read this whole thread.
did you find it all informing and, did you get the latest Kernel or use the 2.6.0 they discuss mostly here? The Latest is Linux 2.6.11.8, just let out about 2 weeks now. I had it in the /usr/src but lost it since I have redone my whole system as a Linux format now, and no more FAT devices. I saved it to CD so I still have the 2.6.11.5, 2.6.11.6, 2.6.11.7, and the lasty 2.6.11.8. I will have to get it back into the system and start over with my recent edits to make the files point to the correct dirctories. The makefile and the instlal.sh files. When I re edit them I will post that information,.
 
Old 05-04-2005, 05:45 PM   #419
marinko
LQ Newbie
 
Registered: Mar 2004
Posts: 16

Rep: Reputation: 0
well people after forum search I can't find solution for my problem.

I have slackware 10.1 and problem is that picture is moved in right side of screen. in slax and knoppix this is everything OK. xorg.conf is same like I use it in 10, and in 9.1 slackware.

i have DTK 15" monitor and resolution is 1024x768@75 HZ. also when I use windows XP at same resolution and 85Hz picture has same position in Win and Linux and in that case there no problems. but when I use same refresh in win and linux problem persist.

I used xvidtune but after restart everything stays same like before.

sorry on bad English

and thanks
 
Old 05-04-2005, 08:12 PM   #420
ArmOrAttAk
Member
 
Registered: May 2005
Location: NYC
Distribution: Slackware, Gentoo
Posts: 30

Rep: Reputation: 15
Yes, I found it informative.

I followed the kernal install instructions just replacing 2.6.11.8 for the 2.6.5. Slackware version 10.1 came with kernal 2.4.29. I was very satisfied the the kernal compiled although no sound, or net.. So another crack at it and I found my nic, but still no sound. Attempt #3 found my sound hardware, but the net doesn't work again. Well this is getting tiresome taking 1-2 hours per. I decided to follow the instructions that came with the kernal. Why does a make install take 2 minutes while the make command alone takes 20? Strange.. something tells me it isn't doing what I want it to. So 3 more attempts with this alternate and still no net.

I'm not sure if the files are being overwritten. My nic is still installed as I see with lspci which is exactly the same with both kernals I'm tired.
 
  


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:05 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