SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I am a linux newbie trying out my first kernel recompile.I downloaded the stable kernel 2.6.16.19 and compiled and made an image.But when I try to boot it I get the following error message
Uncompressig Linux.. Ok,booting the kernel
Red Hat nash version 4.1.18 starting
ata1:disabling port
ata2:disabling port
Enforcing mode requested but no policy loaded.Halting Now
Kernel Panic : No syncing : Attempted to kill init !
I have an IDE hdd and a P4 machine with 512MB ddr2 RAM.
Can anyone help me out here?Is more information needed?
Did you compile your kernel with support for your root file system? E.g. ext3 or ReiserFS?
Hi! (may be my problem was alredy discussed but iīm lazy to read 30 page thread :-))
I tried to compiled my first kernel yesterday (unbzip2ed it to /root/linux-2.6.16), probably messed up configuration settings, so after īmake installī command and reboot i alsa couldnīt detect my sound and network card, ntfs partitions were unavailable. I had to go back. I tried renaming vmlinuz.old (backed up old boot) to vmlinuz but it didnīt bring any result which made me desperate, i also tried by analogue inputting make and make install command in the old kerrnel directory, which only worked after i inputted make clean command in the new kernel directory. can i always use such method to restore to previous kernel, is it safe?
When building kernels, I modify Lilo to allow for backups. I copy my known good kernel to vmlinuz.safe and then make the following mods to the lilo config:
This give me a boot prompt that will let me switch back to the previous kernel without having to do anything fancy. Once I have a kernel I know is good for what I need, pop it to .safe and run.
Oh.. and for the audio question: Did you build it as a module? If so, did you do a "make modules_install"?
I created a new thread with this question, then I saw that probably was better to ask this question here....
I am trying to upgrade kernel of my old firewall (Slackware 9.1, 2.4.22) to new kernel.
After deflating tar, and after I changed the link, I tried make menuconfig, make xconfig and make oldconfig, always obtaining this answer.
HOSTCC scripts/fixdep
In file included from /usr/include/bits/posix1_lim.h:126,
from /usr/include/limits.h:144,
from /usr/lib/gcc-lib/i486-slackware-linux/3.3.1/include/limits.h:122,
from /usr/lib/gcc-lib/i486-slackware-linux/3.3.1/include/syslimits.h:7,
from /usr/lib/gcc-lib/i486-slackware-linux/3.3.1/include/limits.h:11,
from scripts/fixdep.c:105:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or directory
In file included from /usr/include/netinet/in.h:212, from scripts/fixdep.c:107:
/usr/include/bits/socket.h:305:24: asm/socket.h: No such file or directory
scripts/fixdep.c: In function `use_config':
scripts/fixdep.c:193: error: `PATH_MAX' undeclared (first use in this function)
scripts/fixdep.c:193: error: (Each undeclared identifier is reported only once
scripts/fixdep.c:193: error: for each function it appears in.)
scripts/fixdep.c:193: warning: unused variable `s'
scripts/fixdep.c: In function `parse_dep_file':
scripts/fixdep.c:289: error: `PATH_MAX' undeclared (first use in this function)
scripts/fixdep.c:289: warning: unused variable `s'
make[1]: *** [scripts/fixdep] Error 1
make: *** [scripts/fixdep] Error 2
I also tried to change gcc version and to find the files cited in the message, It seems that no real problem should raise.
One note worthy of mention (now that it's blown up in my face)... There's a new option in the 2.6.x kernels which is on by default called "Optimize for code size (beware broken compilers!)".
PAY ATTENTION TO THE OUTPUT as the modules are built. If you see the word "Warning" appear referring to any kind of symbol mismatch, flush what you've built so far with `make clean` and then turn that option off or you will not be happy at all with what those modules will do. It appears that our gcc (3.3.6) is finally showing it's age.
Can I omit make install?
Instead I want (and prefer) to manually copy kernel image,etc. to /boot
Actually I think that's the best way to go, by manually copying your kernel image, and the rest... at least I for one feel more comfortable and safe doing that :d.
Ok ,tnx.
Is it ok that I already installed udev094 package(from http://slackware.it/pb/)
in my slackware 10.2?
Because linux kernel 2.6.17 Changes file says that udev071 is one of the minimum requirement.
In all my years of using Linux, I have never compiled a kernel until now (I feel so dirty now! ). But anyways, I ran into a scenario with my Slack server that leaves me no choice to update the kernel. So I dug up some guides and stuff on how to compile the kernel (and even used some documentation from here) and now I am at a stand still. When I do a make bzlilo (someone recommended I do that over bzImage) I have been running into these sorts of errors:
Code:
net/ipv4/netfilter/ip_conntrack_core.c:1547: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [net/ipv4/netfilter/ip_conntrack_core.o] Error 1
make[2]: *** [net/ipv4/netfilter] Error 2
make[1]: *** [net/ipv4] Error 2
make: *** [net] Error 2
Slack version is 10.2....not sure what the gcc version is, it's whatever came with it basically.
I should mention, and I don't know how, but I somehow managed to get through the compiling process without any errors, editted lilo, rebooted, tried selecting the new kernel (which did not show up in the lilo menu for some reason), and nothing happened but a nice big black screen. I am now back on the original Slack 10.2 kernel (2.4.31 ...yes I know...old), going to give this another go...and again, I can't seem to make it through any of the compiling process without some sort of error like I mentioned previously. I am about tempted to try it from a not as new kernel...like a 2.5 version or something to see if I may have better success with it. Or do you feel my gcc might need to be updated first?
well, GCC in 10.2 was never updated after release, so what came on the CD is the most updated version for it... it's GCC 3.3.6 IIRC... so updating GCC shouldn't be necessary... maybe you can try reinstalling it...
i can confirm that 2.4 kernel compiles work fine for me on 10.2, though... been compiling 2.4 on 10.2 since 2.4.31 with no issues... i compiled 2.4.33.2 a few days ago on 10.2 with no problems... i'll be compiling 2.4.33.3 in a couple hours...
i'm not sure what's broken in your system, but something definitely is... do you get the same errors all the time, or do they vary?? i think segmentation faults can be a sign of bad RAM sometimes (anyone care to confirm that?)... is it possible for you to swap your RAM stick with a known-good one to see if it helps??
A part of me wondered if there may have been some hardware issue.
The errors vary...previously it's like it would error on a certain file...then the next time it'd make it a little further then error...then one time it actually seemed to work. But something happened during the whole process and I had to reinstall. And then since the reinstall, I have been getting those errors again, except this time, it doesn't make it nearly as far as it used to.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.