SlackwareThis Forum is for the discussion of Slackware Linux.
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.
New (n permanent) Slackware 11 (ibare 2.4 kernel) user. A few questions regarding kernel upgrade/patch (my 1st):
1.Got these (only) 2 failures while patching the 184.108.40.206 kernel with this patch from bytesex.org: patch-2_4_26-kraxel_gz ( want aviosys 7134 TV Tuner pci card drivers, also driver for bttv cards )
1.(Stripping trailing CRs from patch.)
patching file drivers/media/video/bttv-driver.c
Hunk #10 FAILED at 258.
1 out of 15 hunks FAILED -- saving rejects to file drivers/media/video/bttv-driver.c.rej
patching file drivers/media/video/bttv-if.c
Hunk #9 FAILED at 150.
1 out of 9 hunks FAILED -- saving rejects to file drivers/media/video/bttv-if.c.rej
Opened .rej and .c files in kwrite (saw the previous formatted text) and added (in bttv-driver.c) :
.v4l2_id = V4L2_STD_PAL_N,
.name = "PAL-N",
/* PAL-N */
Also, bttv-if.c.rej( there were no red and blue lines) contents (There were very few differences in .c.rej and .c....On a hunch i opened patch-2_4_26-kraxel_gz in kwrite and saw that below lines, referring to same file were in red with a - sign):
*** 144,352 ****
So deleted all these lines starting from:
/* I2C functions ....
Added these 2 lines at the end since they were in patch-2_4_26-kraxel_gz (not red) and not in bttv-if.c:
Please comment on whether what i did above was correct or not.
2.Since i want to recompile the kernel ,i would like to know which (where) are the incremental patches which can be d/l and tranferred on a floppy. I have the patches: from patch-220.127.116.11 to patch-18.104.22.168. I suppose these patches can't be applied as they are not incremental patches (i.e.patch-22.214.171.124 can be applied only to 2.4.33 to bring it up to 126.96.36.199) ???
Read for 2.6 kernel u can go back and then do an upgrade (but how?)..ex.from 188.8.131.52 to 2.6.17 and then to 2.6.18. Is it possible for kernel to be upgraded to 2.4.34 using only incremental patches or is it better/less trouble to stick with 184.108.40.206/220.127.116.11? (have Internet access only at cybercafe)
Hunks usually get rejected because the code to replace is not in the place the patch says it is. Someitmes you have to manully insert those hunks -stuff with the '-' is what gets removed and stuff with '+' is what gets added. You can sometimes jiggle the line lumbers in the patch to do the same thing. Try using 'patch -l' to ignore minor white-space differernces.
Usually grepping for the leading line of each hunk in the source file will help you find where the code is intended to go:
Thanks gnashley.I tried with -l switch-same outcome. I am quite sure i got the "driver" file right.
Also patched kernel with patch-18.104.22.168 Deleted the .rej's)
My Linux adventure continues.....