I_NEED_HELP Posted November 30, 2002 Report Share Posted November 30, 2002 Im trying to update my kernel. At present im using the default kernel but thought id try making it faster by taking out unneeded support and applying the low latency patch and the kernel patch. I got 2.4.19 kernel of a linux format cover DVD. Downloaded the low latency patch applied that using: gzip -dc /path/to/patch | patch -p1 All went succesfully, i then proceeded to apply the preempt patch used the same command it failed i relised my mistake. The File is just preempt.patch. It wasnt zipped. So i tried checking the man page as my experience has always been with zipped packages and the tried patch -p1 /path/to/patch The terminal does nothing no scrolling text as it performs the function just the cursor moving down to the next line blinking i dont even get a new bash prompt i can type in text but to no purpose. Ive compiled my own kernel a few times before but never experienced this problem before. Can anyone help me. Quote Link to comment Share on other sites More sharing options...
bvc Posted November 30, 2002 Report Share Posted November 30, 2002 The low-latency and preempt can not both be applied. Pick one. http://www.club-nihil.net/mub/viewtopic.ph...ight=lowlatency http://www.club-nihil.net/mub/viewtopic.ph...ight=lowlatency Quote Link to comment Share on other sites More sharing options...
Smigs Posted November 30, 2002 Report Share Posted November 30, 2002 you forgot the < before the patch file, i.e: patch -pnum <patchfile see `man patch` for more details :) Smigs Quote Link to comment Share on other sites More sharing options...
Guest RickFriedman Posted December 1, 2002 Report Share Posted December 1, 2002 So i tried checking the man page as my experience has always been with zipped packages and the tried patch -p1 /path/to/patch The terminal does nothing no scrolling text as it performs the function just the cursor moving down to the next line blinking i dont even get a new bash prompt i can type in text but to no purpose. Ive compiled my own kernel a few times before but never experienced this problem before. Can anyone help me. I believe you've forgotten the < sign. The statement should be: patch -p1 < /path/to/patch Otherwise, without the < it's expecting the input to patch to come from stdin. Rick Quote Link to comment Share on other sites More sharing options...
I_NEED_HELP Posted December 1, 2002 Author Report Share Posted December 1, 2002 I'll try that as soon as ive reinstalled mandrake, stupid me overwrite my old kernel (it was getting late i didnt know what i was doing) and my new kernel gave the error saying it was to big. Quote Link to comment Share on other sites More sharing options...
bvc Posted December 1, 2002 Report Share Posted December 1, 2002 too big for what?... a boot with a floppy?... it always says that, unless you take 70% out of the kernel. Quote Link to comment Share on other sites More sharing options...
I_NEED_HELP Posted December 1, 2002 Author Report Share Posted December 1, 2002 I cant remember the messasge exactly but it said the image was too large and refused to go any further. this was using bzimage. Im not a kernel expert so i just left it and decided to reinstall, it was a fresh new installation anyway so i didnt have much to lose Quote Link to comment Share on other sites More sharing options...
bvc Posted December 1, 2002 Report Share Posted December 1, 2002 Cool! Just a note: you do know it's bzImage, with a I not i, case sensitive? Just checking :) Quote Link to comment Share on other sites More sharing options...
I_NEED_HELP Posted December 1, 2002 Author Report Share Posted December 1, 2002 I did know it was with an I not an i. Otherwise it wouldnt have compiled at all because i have made that mistake a few times before. Quote Link to comment Share on other sites More sharing options...
bvc Posted December 1, 2002 Report Share Posted December 1, 2002 Oh, and I haven't read up on it recently, but does anyone know the final outcome of these patches in the new kernel-2.4.20? Quote Link to comment Share on other sites More sharing options...
I_NEED_HELP Posted December 1, 2002 Author Report Share Posted December 1, 2002 I think i read that theyve been added that the preempt and the low latency production teams were working together to compine both patches to ad the the 2.5 kernel. I thought the next kernel release was going to be 2.6. I cant remember were i read it it may have been in linux format. Quote Link to comment Share on other sites More sharing options...
bvc Posted December 1, 2002 Report Share Posted December 1, 2002 Yeah, I was hoping maybe mdk had increased it's mini-preempt or mini-lowlatency (don't remember which one) in the 2.4.20. Probably not a big diff even if they did. Quote Link to comment Share on other sites More sharing options...
chalex20 Posted December 1, 2002 Report Share Posted December 1, 2002 Otherwise, without the < it's expecting the input to patch to come from stdin. patch -p expects its input to come from stdin IN ANY CASE. It's just that with the < sign you REPLACE its stdin to come from a file and not from a console. Quote Link to comment Share on other sites More sharing options...
Guest RickFriedman Posted December 1, 2002 Report Share Posted December 1, 2002 Otherwise, without the < it's expecting the input to patch to come from stdin. patch -p expects its input to come from stdin IN ANY CASE. It's just that with the < sign you REPLACE its stdin to come from a file and not from a console. True. I made the mistake of automatically associating stdin with the console. I stand suitably corrected. :D Rick Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.