Thought of a different way to get around my problem. Unless I hosed my Linux install trying to compile the driver, I should be able to remove the controller and attached drives and install Linux onto a different drive controlled by the motherboard. I could then upgrade the kernel & kernel-source, compile the commensurate driver and copy it off to floppy. I could then put the controller and attached drives back in and then manually setup the correctly compiled driver before upgrading the kernel again.
Kind of a pain, but it's the only way I can think to do this other than waiting for the vendor to release one. I'd just have to repeat this process every time RH releases a new kernel (yikes!). I'll post my results later today. Stuart > -----Original Message----- > From: Michael Fratoni [mailto:[EMAIL PROTECTED] > Sent: Friday, March 28, 2003 6:19 PM > To: [EMAIL PROTECTED] > Subject: Re: how difficult is compiling a driver? > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Friday 28 March 2003 01:58 pm, Douglas, Stuart wrote: > > Mike (all), > > > > Getting ready to try this out and I need some elaboration as I think > > I may have a problem. > > > > I'm currently running kernel 2.4.18-14 and have that kernel-source > > already installed. I need to compile the driver from the newest > > kernel- source...can this be installed onto a system with an older > > kernel? > > Yes, not a problem. > > > If so, when using up2date to install a newer kernel, does the update > > take effect immediately or after a boot (perhaps a dumb > question, but > > I'm from Windows-land where EVERYTHING takes a reboot). > I'm guessing > > a reboot is required. > > Install the updated kernel and kernel-source, but don't > reboot. You'll > still be running the old kernel at this point. You can then build the > module for the new kernel. Just define KERNELDIR=/usr/src/linux-2.4, > rather than the method I provided earlier. > > > If so, then I need to have the newer driver installed/loaded BEFORE > > the system, with the new kernel installed, is rebooted. Are drivers > > typically backwards compatible, or are the kernel specific based on > > their compilation? > > Hrmm, you need to LOAD the driver into the current kernel, before > rebooting? > > You'll need to build it twice, if that's the case. Build it > once before > upgrading the kernel-source package. Define > KERNELDIR=/lib/modules/`uname -r`/build and build the > modules. This will > build the modules for the current kernel. Copy the modules to > /lib/modules/{version}/someplace_reasonable. You should be > able to get > them loaded. > > Then, install the updates, run 'make clean' redefine KERNELDIR to > KERNELDIR=/usr/src/linux-2.4 in the Makefile (which should > force them to > build against the new kernel-source), and build them again. Copy the > modules to /lib/modules/{new-version}/someplace_reasonable. > > > Normally I'd just throw caution to the wind and try it, but > I'd like to > > avoid having to rebuild this box from the beginning if possible. > > Ouch, that shouldn't be required, I hope. > > - -- > - -Michael > > pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt > Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/ > - -- > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > > iD8DBQE+hNhUn/07WoAb/SsRAurAAJ99h9QioynmtqH+D3S0OIPYp2sOzQCgtxZg > bsN3tkorGK07HddD+7qB14I= > =cGJS > -----END PGP SIGNATURE----- > > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
