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.
I recently bought a couple of cisco aironet wlan pcmcia cards from a second hand shop, it was a bargain so i got them two.
Now today I installed kismet on a laptop and noticed in the readme that the driver in kernel 2.4.19+ are quite unstable. I then downloaded a 2.4.19 kernel so I could use the card properly. Now I just have realised that if they say 2.4.19+ then that might mean that 2.4.19 might have a bad driver too hmmmm.....
Anyway I configured the kernel, did make dep, all went ok. Then I ran make bzImage amd the whole thing came with some errors, I will post them later on since the laptop is busy downloading something at the moment.
Then I downloaded a 2.4.10 to see if that was gonna work. Did tar -xjvf linux-2.4.10..... I could see a lot of text scrolling on the screen and at the end .... well the extracted kernel sources couldn't be found anywhere!? Now I thought that I might not have any space left on the hard drive so tried downloading other things to see and they all came down ok... Oh by the way if someone knows a good command to check how much space is left on a hard drive, that would be warmly welcome, I tried with fdisk and other stuff but in vain.
Ok sorry if this is confusing but all that mess came up just right now and i'm gonna make some research on google, I posted this in the meantime just in case I can't find some helpful answers.
Oh by the way, I'm running slackware 11 with custom 2.6.18 kernel
Oh by the way if someone knows a good command to check how much space is left on a hard drive, that would be warmly welcome
df will show the free space on the disk, use the -h option to make the readout more human friendly. If your are running KDE there is a GUI tool as well.
Ok I've solved the tar thing, the problem was that it's been quite a long day =)
however here's what I get when typing make bzImage for kernel 2.4.12:
bash-3.1# make bzImage
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/split-include scripts/split-include.c
scripts/split-include include/linux/autoconf.h include/config
gcc -D__KERNEL__ -I/usr/src/linux-2.4.12/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -c -o init/main.o init/main.c
In file included from /usr/src/linux-2.4.12/include/linux/unistd.h:9,
from init/main.c:17:
/usr/src/linux-2.4.12/include/asm/unistd.h:347: warning: conflicting types for built-in function '_exit'
. scripts/mkversion > .tmpversion
gcc -D__KERNEL__ -I/usr/src/linux-2.4.12/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DUTS_MACHINE='"i386"' -c -o init/version.o init/version.c
make CFLAGS="-D__KERNEL__ -I/usr/src/linux-2.4.12/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 " -C kernel
make[1]: Entering directory `/usr/src/linux-2.4.12/kernel'
make all_targets
make[2]: Entering directory `/usr/src/linux-2.4.12/kernel'
gcc -D__KERNEL__ -I/usr/src/linux-2.4.12/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -fno-omit-frame-pointer -c -o sched.o sched.c
sched.c:212: error: conflicting types for 'reschedule_idle'
sched.c:209: error: previous declaration of 'reschedule_idle' was here
sched.c:212: error: conflicting types for 'reschedule_idle'
sched.c:209: error: previous declaration of 'reschedule_idle' was here
sched.c:357: error: conflicting types for 'wake_up_process'
/usr/src/linux-2.4.12/include/linux/sched.h:565: error: previous declaration of 'wake_up_process' was here
sched.c:357: error: conflicting types for 'wake_up_process'
/usr/src/linux-2.4.12/include/linux/sched.h:565: error: previous declaration of 'wake_up_process' was here
sched.c:395: error: conflicting types for 'schedule_timeout'
/usr/src/linux-2.4.12/include/linux/sched.h:155: error: previous declaration of 'schedule_timeout' was here
sched.c:395: error: conflicting types for 'schedule_timeout'
/usr/src/linux-2.4.12/include/linux/sched.h:155: error: previous declaration of 'schedule_timeout' was here
sched.c:750: error: conflicting types for '__wake_up'
/usr/src/linux-2.4.12/include/linux/sched.h:557: error: previous declaration of '__wake_up' was here
sched.c:750: error: conflicting types for '__wake_up'
/usr/src/linux-2.4.12/include/linux/sched.h:557: error: previous declaration of '__wake_up' was here
sched.c:760: error: conflicting types for '__wake_up_sync'
/usr/src/linux-2.4.12/include/linux/sched.h:558: error: previous declaration of '__wake_up_sync' was here
sched.c:760: error: conflicting types for '__wake_up_sync'
/usr/src/linux-2.4.12/include/linux/sched.h:558: error: previous declaration of '__wake_up_sync' was here
sched.c:770: error: conflicting types for 'complete'
/usr/src/linux-2.4.12/include/linux/completion.h:31: error: previous declaration of 'complete' was here
sched.c:770: error: conflicting types for 'complete'
/usr/src/linux-2.4.12/include/linux/completion.h:31: error: previous declaration of 'complete' was here
sched.c:780: error: conflicting types for 'wait_for_completion'
/usr/src/linux-2.4.12/include/linux/completion.h:30: error: previous declaration of 'wait_for_completion' was here
sched.c:780: error: conflicting types for 'wait_for_completion'
/usr/src/linux-2.4.12/include/linux/completion.h:30: error: previous declaration of 'wait_for_completion' was here
sched.c:815: error: conflicting types for 'interruptible_sleep_on'
/usr/src/linux-2.4.12/include/linux/sched.h:562: error: previous declaration of 'interruptible_sleep_on' was here
sched.c:815: error: conflicting types for 'interruptible_sleep_on'
/usr/src/linux-2.4.12/include/linux/sched.h:562: error: previous declaration of 'interruptible_sleep_on' was here
sched.c:826: error: conflicting types for 'interruptible_sleep_on_timeout'
/usr/src/linux-2.4.12/include/linux/sched.h:563: error: previous declaration of 'interruptible_sleep_on_timeout' was here
sched.c:826: error: conflicting types for 'interruptible_sleep_on_timeout'
/usr/src/linux-2.4.12/include/linux/sched.h:563: error: previous declaration of 'interruptible_sleep_on_timeout' was here
sched.c:839: error: conflicting types for 'sleep_on'
/usr/src/linux-2.4.12/include/linux/sched.h:559: error: previous declaration of 'sleep_on' was here
sched.c:839: error: conflicting types for 'sleep_on'
/usr/src/linux-2.4.12/include/linux/sched.h:559: error: previous declaration of 'sleep_on' was here
sched.c:850: error: conflicting types for 'sleep_on_timeout'
/usr/src/linux-2.4.12/include/linux/sched.h:560: error: previous declaration of 'sleep_on_timeout' was here
sched.c:850: error: conflicting types for 'sleep_on_timeout'
/usr/src/linux-2.4.12/include/linux/sched.h:560: error: previous declaration of 'sleep_on_timeout' was here
sched.c: In function `reparent_to_init':
sched.c:1255: error: syntax error before "__FUNCTION__"
sched.c: At top level:
sched.c:209: warning: 'reschedule_idle' declared `static' but never defined
make[2]: *** [sched.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.12/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.12/kernel'
make: *** [_dir_kernel] Error 2
df will show the free space on the disk, use the -h option to make the readout more human friendly. If your are running KDE there is a GUI tool as well.
Tried a 2.4.16 kernel since it seems to be the more stable one of the 2.4.10/18 range, got the same error message as above when trying to do a custom compile.
However this comes up when trying a default compile:
bash-3.1# make bzImage
scripts/split-include include/linux/autoconf.h include/config
gcc -D__KERNEL__ -I/usr/src/linux-2.4.16/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -c -o init/main.o init/main.c
In file included from /usr/src/linux-2.4.16/include/linux/sched.h:23,
from /usr/src/linux-2.4.16/include/linux/mm.h:4,
from /usr/src/linux-2.4.16/include/linux/slab.h:14,
from /usr/src/linux-2.4.16/include/linux/proc_fs.h:5,
from init/main.c:15:
/usr/src/linux-2.4.16/include/linux/smp.h:29: error: conflicting types for 'smp_send_reschedule'
/usr/src/linux-2.4.16/include/asm/smp.h:62: error: previous declaration of 'smp_send_reschedule' was here
/usr/src/linux-2.4.16/include/linux/smp.h:29: error: conflicting types for 'smp_send_reschedule'
/usr/src/linux-2.4.16/include/asm/smp.h:62: error: previous declaration of 'smp_send_reschedule' was here
In file included from /usr/src/linux-2.4.16/include/linux/unistd.h:9,
from init/main.c:17:
/usr/src/linux-2.4.16/include/asm/unistd.h:348: warning: conflicting types for built-in function '_exit'
make: *** [init/main.o] Error 1
Anyone who's been reading this post should ignore it, the driver on the old kernel is actually just as buggy on those as it is on the new ones. I should have spent more time on RTFM....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.