[driverloader] DriverLoader 2.66 not working with FC1, 2.6.5-1.322
Marc Boucher
marc at linuxant.com
Thu Apr 22 10:56:19 EDT 2004
Alex,
The 2.6.5-1.322 Fedora development kernel unfortunately had a packaging
bug preventing external modules from building properly.
If you upgrade it to the latest version (presently 2.6.5-1.326), the
modules should build.
But with this kernel it will probably still not work reliably, due to
the large stack requirements of Intel's 2200BG driver and the switch to
4K kernel stacks by default now in Fedora (the CONFIG_4KSTACKS option
has been removed so one can no longer easily revert to 8K stacks). You
could try rebuilding the kernel after making sure that both the Fedora
linux-2.6.5-nostack.patch and CONFIG_4KSTACKS option have been removed.
Due to the complexity of this procedure and the fact that it involves
heavily experimental development kernels, we cannot officially support
it though.
However we are working on adding a special mechanism to eliminate the
stack issue directly into DriverLoader, so I would suggest waiting
until that becomes available.
Marc
--
Marc Boucher
Linuxant inc.
On Apr 22, 2004, at 9:22 AM, Alex Ackerman wrote:
> Well, 2.66 isn't working for my kernel either. I've included the build
> code and rpm install output for your review. If anyone has any ideas,
> I'm game. Oh, and before anyone says it again, I've already checked.
> I
> don't have CONFIG_4KSTACKS built into my kernel (see attached kernel
> config). My system has recently been reloaded, so it's pretty much a
> stock Fedora Core 1 laptop. You can see the changes that were made to
> the system here: http://www.darkhonor.com/forum/viewtopic.php?t=10
>
> The relevant packages on my system:
> kernel-2.6.5-1.322
> kernel-source-2.6.5-1.322
> gcc-3.3.2-1
> gcc32-3.2.3-6
>
> I have tried using both compiler versions, the RPM, and the tar.gz
> file. All end with the same error:
> install: cannot stat `driverloader.ko': No such file or directory
>
> Anyway, here is the output of using the generic packages with source.
>
> Alex
>
> [...]
More information about the driverloader
mailing list