Re: AWE Kernel Patch Troubles
>> 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 INSTALL.awe but I just can't get it to >> work. I tried many variations, and played around, but I'm no kernel >> hacker and I haven't been successful. Everytime I attempt to patch my >> kernel source tree I get errors like those in the following >> typescript. I thought that it was probably just a minor malfunction >> and that specifying the files without the .old extension would make it >> work, but to no avail. I don't get any errors when actually compiling >> the kernel, but everytime I boot my newly compiled kernel (and >> modules) I get these messages: I couldn't get the latest (.2d) working (same problem) so I just used .2c version. The changes between c and d versions are very small AFAIK. --j -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: AWE Kernel Patch Troubles
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 unpacked awedrv into): cd /usr/local/src patch -p0 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 INSTALL.awe but I just can't get it to > work. I tried many variations, and played around, but I'm no kernel > hacker and I haven't been successful. Everytime I attempt to patch my > kernel source tree I get errors like those in the following > typescript. I thought that it was probably just a minor malfunction > and that specifying the files without the .old extension would make it > work, but to no avail. I don't get any errors when actually compiling > the kernel, but everytime I boot my newly compiled kernel (and > modules) I get these messages: > > sound /lib/modules/2.0.34/misc/sound.o: unresolved symbol unload_awe > sound /lib/modules/2.0.34/misc/sound.o: unresolved symbol attach_awe > > I really don't know where to go from here. Hopefully some of you can > help. diff -u awedrv-0.4.2d.orig/install.sh awedrv-0.4.2d/install.sh --- awedrv-0.4.2d.orig/install.sh Mon Jan 26 11:23:06 1998 +++ awedrv-0.4.2d/install.shMon Jun 15 17:18:12 1998 @@ -158,7 +158,7 @@ undef_condition AWE_OSS38 if [ ! -f $destdir/awe_wave.c ]; then echo "applying a patch to lowlevel directory" - patch -d $linuxroot < usslite-3.54-awe.diff + patch -p0 -d $linuxroot < usslite-3.54-awe.diff fi elif [ x$sound_version = xOSS ]; then
Re: AWE Kernel Patch Troubles
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 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 INSTALL.awe but I just can't get it to > work. I tried many variations, and played around, but I'm no kernel > hacker and I haven't been successful. Everytime I attempt to patch my > kernel source tree I get errors like those in the following > typescript. I thought that it was probably just a minor malfunction > and that specifying the files without the .old extension would make it > work, but to no avail. I don't get any errors when actually compiling > the kernel, but everytime I boot my newly compiled kernel (and > modules) I get these messages: -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
AWE Kernel Patch Troubles
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 INSTALL.awe but I just can't get it to work. I tried many variations, and played around, but I'm no kernel hacker and I haven't been successful. Everytime I attempt to patch my kernel source tree I get errors like those in the following typescript. I thought that it was probably just a minor malfunction and that specifying the files without the .old extension would make it work, but to no avail. I don't get any errors when actually compiling the kernel, but everytime I boot my newly compiled kernel (and modules) I get these messages: sound /lib/modules/2.0.34/misc/sound.o: unresolved symbol unload_awe sound /lib/modules/2.0.34/misc/sound.o: unresolved symbol attach_awe I really don't know where to go from here. Hopefully some of you can help. Thanks, Eric. (sorry for the long message) Script started on Mon Jun 29 22:18:11 1998 [EMAIL PROTECTED] /usr/src/awedrv-0.4.2d >install.sh Linux source root directory [/usr/src/linux] making symlink /usr/src/linux/include/asm rm -f include/asm ( cd include ; ln -sf asm-i386 asm) checking the version of installed sound driver.. sound driver is USS applying a patch to lowlevel directory patching file `Makefile' Hunk #1 succeeded at 101 with fuzz 2 (offset 95 lines). can't find file to patch at input line 17 Perhaps you should have used the -p or --strip option? The text leading up to this was: -- |*** drivers/sound/lowlevel/init.c.old Tue May 28 23:45:17 1996 |--- drivers/sound/lowlevel/init.c Wed Oct 30 21:02:02 1996 -- File to patch: drivesr rs/sound/lowlw evel/init.c patching file `drivers/sound/lowlevel/init.c' can't find file to patch at input line 54 Perhaps you should have used the -p or --strip option? The text leading up to this was: -- |*** drivers/sound/lowlevel/Config.tmpl.old Thu May 16 17:05:56 1996 |--- drivers/sound/lowlevel/Config.tmpl Wed Oct 30 21:02:02 1996 -- File to patch: drivers/sound/lowlevel/Config.tmpl patching file `drivers/sound/lowlevel/Config.tmpl' can't find file to patch at input line 64 Perhaps you should have used the -p or --strip option? The text leading up to this was: -- |*** drivers/sound/Config.in.oldWed Dec 11 18:19:41 1996 |--- drivers/sound/Config.inThu Dec 5 15:56:44 1996 -- File to patch: drivers/sound/Config.in patching file `drivers/sound/Config.in' Hunk #1 succeeded at 14 (offset -236 lines). can't find file to patch at input line 74 Perhaps you should have used the -p or --strip option? The text leading up to this was: -- |*** Documentation/Configure.help.old Sat Oct 5 18:13:56 1996 |--- Documentation/Configure.help Wed Oct 30 21:02:03 1996 -- File to patch: Documentation/Configure.help patching file `Documentation/Configure.help' Hunk #1 succeeded at 4053 (offset 368 lines). copying source files: awe_wave.c awe_hw.h awe_version.h awe_compat.h README.awe ChangeLog.awe copying header files: awe_voice.h copying config file done. Please configure and remake linux kernel (and modules). Answer YES to 'AWE32 synth support' under lowlevel support in Sound menu when configuring your kernel. Also, you should keep other SoundBlaster options, too. Script done on Mon Jun 29 22:20:27 1998 -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
[Fwd: Patch troubles]
--- 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 correct the .rej files or guess the underlying problem, but I just don't have the time. I'll wait for the 2.1 kernel to graduate to stable. Thanks again. -- C.L. Daugaard [EMAIL PROTECTED] __ Peter S Galbraith wrote: > > "Curtis L. Daugaard" wrote: > > > 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 the Kernel HowTo, documentation in the kernel > > sources, directories from which the patches were downloaded, man > page > > for patch, etc., but I the patches don't succeed. Even after a > fresh > > reinstall of the sources, patch repeatedly alerts me that it thinks > I'm > > trying to reapply a patch. So I guess my questions come to this: > > > > 1. What is needed to apply the pre-patches mentioned above? > > Just the pre-patch 2.0.31-7 in /usr/src/ > and clean 2.0.30 sources in /usr/src/linux/ > > cd /usr/src > gunzip -dc pre-patch-2.0.31-7 | patch -p1 -s -N -E -d /usr/src/linux > > > 2. Should the patch against 2.0.30 be applied before or after the > > pre-patches? > > Whatever works! > Look for .rej files when done and possibly edit them in by hand: > > find . -name "*.rej" > > > My thanks to anyone who can help. > > Hope it does. > -- > Peter Galbraith, research scientist > <[EMAIL PROTECTED]> > Maurice-Lamontagne Institute, Department of Fisheries and Oceans > Canada > P.O. Box 1000, Mont-Joli Qc, G5H 3Z4 Canada 418-775-0852 - FAX > 418-775-0546 --- End Message ---
Patch troubles
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 the Kernel HowTo, documentation in the kernel sources, directories from which the patches were downloaded, man page for patch, etc., but I the patches don't succeed. Even after a fresh reinstall of the sources, patch repeatedly alerts me that it thinks I'm trying to reapply a patch. So I guess my questions come to this: 1. What is needed to apply the pre-patches mentioned above? 2. Should the patch against 2.0.30 be applied before or after the pre-patches? My thanks to anyone who can help. -- C.L. Daugaard [EMAIL PROTECTED] __ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
