>> I have an AWE64 and I've been using the kernel patch for it ever since
>> I've had Linux. However, with my upgrade to hamm and the 2.0.34
>> kernel, I had to repatch and recompile my kernel. Along with that
>> upgrade, I got the newest version of the AWE patch, 0.4.2d. I
>> followed the direc
Sorry, I hit the wrong key and accidently set that last one just a tad
bit early...
-
The very same thing happened to me last week. I've attached a diff
which should take care of the problem for you. Here's what you need to
do (I'm assuming that /usr/local/src/awedrv-0.4.2d is where you unp
The very same thing happened to me last week. I've attached a diff
which should take care of the problem for you. Here's what you need to
do (I'm assuming that /usr/local/src/awedrv-0.4.2d is where you unpacked
awedrv into):
cd /usr/local/src
patch -p0 I have an AWE64 and I've been u
I have an AWE64 and I've been using the kernel patch for it ever since
I've had Linux. However, with my upgrade to hamm and the 2.0.34
kernel, I had to repatch and recompile my kernel. Along with that
upgrade, I got the newest version of the AWE patch, 0.4.2d. I
followed the directions in INSTAL
--- Begin Message ---
Thanks for your post. After starting with a clean kernel source and
following your instructions, the patch attempt still results in scads of
skipped hunks and .rej files. It seems clear there is a major problem
somewhere. I'm sure I haven't looked far enough to learn how to
I'm not an utter newbie, but I feel like it right now. I have a patch
(to support certain hardware) against 2.0.30 that I've successfully
applied. Good. But I guess I'm just clueless about how to apply the
pre-patch 2.0.31-1 through 2.0.31-7 (to gain support for the LS-120
drive). I've checked
6 matches
Mail list logo