I_NEED_HELP
Nov 30 2002, 05:03 PM
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.
bvc
Nov 30 2002, 06:57 PM
Smigs
Nov 30 2002, 09:45 PM
you forgot the < before the patch file, i.e:
CODE
patch -pnum <patchfile
see `man patch` for more details
Smigs
RickFriedman
Dec 1 2002, 11:24 AM
QUOTE
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:
CODE
patch -p1 < /path/to/patch
Otherwise, without the < it's expecting the input to patch to come from stdin.
Rick
I_NEED_HELP
Dec 1 2002, 02:27 PM
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.
too big for what?... a boot with a floppy?... it always says that, unless you take 70% out of the kernel.
I_NEED_HELP
Dec 1 2002, 02:36 PM
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
Cool!
Just a note: you do know it's bzImage, with a I not i, case sensitive? Just checking
I_NEED_HELP
Dec 1 2002, 02:42 PM
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.
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?
I_NEED_HELP
Dec 1 2002, 02:45 PM
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.
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.
chalex20
Dec 1 2002, 03:30 PM
QUOTE
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.
RickFriedman
Dec 1 2002, 03:51 PM
QUOTE
QUOTE
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.
Rick
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.