LinuxQuestions.org - 2.4.21 patches?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - 2.4.21 patches? (https://www.linuxquestions.org/questions/slackware-14/2-4-21-patches-143161/)

Finally got my wireless working with the Netgear MA521 card in slackware 9.1 thanks to the large WPC11V4 thread in wireless-networking....but this at the cost of dropping my kernel from 2.4.24 to 2.4.21..... now where might I go about finding the patches necessary to prevent something bad from happening to me? aka hacked or something of the sorts... more like annoyed. Any ideas?

http://www.kernel.org/pub/linux/kernel/v2.4/ Scroll down to the bottom. You want patch-2.4.22, patch-2.4.23 and patch-2.4.24

Well is this going to mess up the wirelsss beings it needs 2.4.21 to function?

What is it in 2.4.21 that it needs thats not in 2.4.24?

The module I compiled, RTL8180L for my MA521 needs a 2.4.21 kernel it won't work with 2.4.22+

Does it build correctly?
I just tried it on my system and got the following,

Code:

bern@beast bern $ cd '/home/bern/Downloads/SUPPORT/rtl8180_1.5'

bern@beast rtl8180_1.5 $ make

gcc -O6 -Wall -DMODULE -D__KERNEL__ -DLINUX -I /usr/src/linux-2.4.25-pre8/include/ -DRTL_IO_MAP -DRTL_LITTLE_ENDIAN -DRTL_ACT_AS_STA -DRTL8180_DRV_ON_PC -DENABLE_DBG_PRINT -c -o r8180_pci_init.o r8180_pci_init.c

In file included from r8180_pci_init.c:40:

r8180_type.h:62:1: warning: "ENABLE_DBG_PRINT" redefined

r8180_pci_init.c:1:1: warning: this is the location of the previous definition

gcc -O6 -Wall -DMODULE -D__KERNEL__ -DLINUX -I /usr/src/linux-2.4.25-pre8/include/ -DRTL_IO_MAP -DRTL_LITTLE_ENDIAN -DRTL_ACT_AS_STA -DRTL8180_DRV_ON_PC -DENABLE_DBG_PRINT -c -o r8180_if.o r8180_if.c

In file included from r8180_if.h:20,

                from r8180_if.c:43:

r8180_type.h:62:1: warning: "ENABLE_DBG_PRINT" redefined

r8180_if.c:1:1: warning: this is the location of the previous definition

--- Generate open part open_part.o ---



--- Generate rtl8180 linux driver  rtl8180_24x.o on 2.4.25-pre8 ---



bern@beast rtl8180_1.5 $

Yes it does... theres one on realteks FTP named rtl8180_linuxdrv_v13(gcc3.xx).zip which is some kind of source I am guessing, compiles fine and works flawlessly. I'd just like to keep the current kernel how it is and add whatever patches I need to secure it. No need to fix what isn't broken, kinda... I can't change the kernel version basically until theres a newer version of that driver from realtek.

Edit: BTW Happy Birthday Aussie :D

Quote:

Originally posted by Astro
Yes it does... theres one on realteks FTP named rtl8180_linuxdrv_v13(gcc3.xx).zip which is some kind of source I am guessing, compiles fine and works flawlessly.

Thats the one I just built on my 2.4.25-pre8 kernel, not having the hardware I can't test it though.

Quote:

Originally posted by Astro
I'd just like to keep the current kernel how it is and add whatever patches I need to secure it. No need to fix what isn't broken, kinda... I can't change the kernel version basically until theres a newer version of that driver from realtek.

Yes, well, in order to patch your kernel you have to apply the patches that have already been linked by Andrew, and then rebuild the kernel, so your going to either be running 2.4.24 or 2.6.2 - have you tried 2.6.2?

Quote:

Originally posted by Astro
Edit: BTW Happy Birthday Aussie :D

Thank You Astro :-)

I tested the module compiling with 2.4.24 and it threw a few errors when I compiled it. On insmodding the module all hell broke loose and it's a bad thing when my caps lock and scroll lock lights flash.. kernel panic! I tried lots of different compiles and none worked... went down to the 2.4.21, compiled the kernel, compiled the module, ./wlanup && dhcpcd -t 10 wlan0 and I was on the network fine, no crashes or anything. I'm just afraid that by patching by how you're saying will break the driver so it won't work. I'm not up to date at all on how kernel patches work or anything. I was thinking there is one patch for a vuln. and if that patch is applied it won't change the kernel version, just fix the problem. Requesting some enlightenment? (go dmb!)

No, all released kernel patches up the version number, thats how kernel patching works.

Well I guess then the only way for this wireless to work is for my kernel to be insecure?

Maybe not, you could always try with the new 2.6.2 kernel, and the fact that it compiled without any errors on my 2.4.25-pre8 kernel is a good sign.

Another option is ndiswrapper.

Quote:

Originally posted by Aussie
Maybe not, you could always try with the new 2.6.2 kernel, and the fact that it compiled without any errors on my 2.4.25-pre8 kernel is a good sign.

Another option is ndiswrapper.

it's not. I tried it a couple times and there were almost never any errors and yet it didn't work :(

i will try 2.6.2 with it just in case when I'm done testing my battery life and I'll post