> A new thing I just noticed: the sb live module claims to load correctly upon
> boot (I put it in /etc/modules. I still get no sound, but it IS loading
> correctly.
>
> Question:
>1. How can I check to see if the module is loaded correctly (sb live)? Is
> there a test I can run?
you can
Here is what I did:
1. Untarred the kernel source (2.2.14)
2. Applied ppDev patch (for 2.2.14)
3. Applied ppSCSI patch (not for 2.2.14, for 2.2.10, I think.)
4. make xconfig; make dep; make clean; make bzImage; make modules; make
modules_install
5. untarred the Soundblaster Live! so
> I am getting 20+ 'unresolved symbol' errors after installing a custom kernel
> and modules under the potato freeze of Debian. Actually, now that I look at
> it, I get a lot more than 20, and the majority of them (I loose a lot from
> scrolling past the console buffer) are in /lib/modules/2.2.
Turns out that an upgrade to the latest version of Arla fixed
the symbol errors. That's the benefit (?) of using alpha software.
Max
You (Michael Beattie) wrote:
> Give `modprobe xfs` a go...
It says there aren't any dependencies.
Max
> On Fri, 30 Oct 1998, Max wrote:
> > I'm trying to compile a program (Arla) that creates a module called
> > xfs.o. When I try to load that module with insmod, I get the
> > following:
> >
>
Give `modprobe xfs` a go...
On Fri, 30 Oct 1998, Max wrote:
> I'm trying to compile a program (Arla) that creates a module called
> xfs.o. When I try to load that module with insmod, I get the
> following:
>
> xfs.o: unresolved symbol mod_use_count_
> xfs.o: unresolved symbol inode_setattr
>
6 matches
Mail list logo
