Click to See Complete Forum and Search --> : Soundblaster Live for Debian
Radar
01-15-2001, 09:20 PM
I can't seem to get it right. I installed the kernel source and made a symbolic link to "linux" but it's not finding the version.h or the autoconf.h still (like before)
I think the header files are in there, but not version.h or autoconf.h - the README says to manually disable the KERNELVERSION option in the makefile, but I have no idea how much of it to comment out to override it.
Anyone else get this working in 'Potato' ?
------------------
Nothing Spoils the taste of peanut butter like unrequited love--Charlie Brown
smije
01-15-2001, 11:25 PM
I actually changed the name of the header file to linux, never had a problem with make after that.
DJ-dOoK
01-15-2001, 11:57 PM
When you installed the kernel source package, did you know that all it does it dump a tarbal in the /usr/src directory? Or did you download your source. Either way, it is better to rename your kernel source directory to linux-2.x.xx where x.xx is the version number, ie the kernel that comes with Debian 2.2 is 2.2.17. Then make a symbolic link to this folder.
So for example you would have:
linux-2.2.17
linux-2.2.17.tar.bz2
you would do a ln -s linux-2.2.17 linux and you would now have:
linux
linux-2.2.17
linux-2.2.17.tar.bz2
This is better just in case you wish to install a new kernel source so you just relink the linux symbolic link to the new source.
------------------
One day, the DJ declared! Let this OS be taken to the world, and Linux was introduced to many frustrated windows users!
Radar
01-16-2001, 09:23 AM
Originally posted by DJ-dOoK:
When you installed the kernel source package, did you know that all it does it dump a tarbal in the /usr/src directory? Or did you download your source. Either way, it is better to rename your kernel source directory to linux-2.x.xx where x.xx is the version number, ie the kernel that comes with Debian 2.2 is 2.2.17. Then make a symbolic link to this folder.
So for example you would have:
linux-2.2.17
linux-2.2.17.tar.bz2
you would do a ln -s linux-2.2.17 linux and you would now have:
linux
linux-2.2.17
linux-2.2.17.tar.bz2
This is better just in case you wish to install a new kernel source so you just relink the linux symbolic link to the new source.
What I did is apt-get installed the kernel source package, then I went into the /usr/src directory and untarred the bz2 file. then i did ln -s kernel-source-2.2.17 linux. then I tried to make install in the emu10k1 directory, but I still got the errors.
I'll try what you said tonight after school.
by smije: I actually changed the name of the header file to linux, never had a problem with make after that. Do you mean the source directory? because the file that contains the header files is called linux. I think it's /usr/src/kernel-source-2.2.17/include/linux.
Oh well, we'll see tonight - thanks!
------------------
Nothing Spoils the taste of peanut butter like unrequited love--Charlie Brown
Radar
01-16-2001, 10:45 PM
Ok I got the kernel source from kernel.org
and did make menuconfig and found that this
allowed me to get the sblive support (was not there in default deb. source)
I selected M and exited / saved, then did make dep
make modules / make modules_install. Then I added
the emu10k1 to modules.conf and did modprobe emu10k1.
I get this:
Note: /etc/modules.conf is more recent than /lib/modules/2.2.17/modules.dep
/lib/modules/2.2.17/misc/emu10k1.o unresolved symbol tqueue_lock
/lib/modules/misc/emu10k1.o: insmod /lib/modules/2.2.17.misc/emu10k1.o failed
What have I missed? .....Help?
------------------
Nothing Spoils the taste of peanut butter like unrequited love--Charlie Brown
veloctTX
01-17-2001, 02:06 PM
as root:
# depmod -a
That should fix that.
Radar
01-17-2001, 05:25 PM
Originally posted by veloctTX:
as root:
# depmod -a
That should fix that.
Actually, I did that before I did modprobe
and got alot of unresolved symbols. The problem is that the makefile looks different than the version that is referenced in the NHF so I'm SOL till I figure what to do. Maybe I'll try depmod again. Thx
------------------
Nothing Spoils the taste of peanut butter like unrequited love--Charlie Brown
DJ-dOoK
01-17-2001, 07:26 PM
Ok you might actually be better getting the source from ftp opensource.creative.com which always has the latest source.
Find the emu10k1 zip file with the newest date unpack it and read the instructions provided. I think that will solve your problems.
Good Luck!
------------------
One day, the DJ declared! Let this OS be taken to the world, and Linux was introduced to many frustrated windows users!
Radar
01-18-2001, 09:16 AM
Originally posted by DJ-dOoK:
Ok you might actually be better getting the source from ftp opensource.creative.com which always has the latest source.
Find the emu10k1 zip file with the newest date unpack it and read the instructions provided. I think that will solve your problems.
Good Luck!
Thanks DJ - The first post here is me trying to do just that. It was not finding the files it needed. autoconf.h and version.h. The README in the untarred directory said that you can manually disable the KERNELVERSION option in the makefile. I was'nt sure how much to comment out without messing up the makefile.
I actually tried it with the kernel.org source as well. The whole directory is called "linux" when you untar it, so I thought it would work.
I'll try some more stuff tonight. http://www.linuxnewbie.org/ubb/smile.gif
------------------
Nothing Spoils the taste of peanut butter like unrequited love--Charlie Brown
Radar
01-18-2001, 09:53 PM
I got the latest driver from creative, and it compiled fine (it had a fix for the version.h & autoconf.h), but I still get the same
unresolved symbol errors when I depmod -a. It seems like every module I opted for during install except floppy and ppp
is having unresolved symbol errors. I'm not sure what to do now.
I read the man pages for modules.conf, depmod, modprobe. None of them come out and say how to properly load the modules.
Modules.conf can't be edited directly because it is created by
update-modules. but update-modules gives unresolved symbol errors too.
What do I need to do in modutils to get the update-modules to do this right?
there has to be something missing. I can only follow the NHF to a point, the rest is outdated, or does not apply to debian.
The emu10k1 directory exists and contains the .o files. /lib/modules/2.2.17/misc
contains a copy of emu10k1.o. modules.conf does not have an alias entry for it because update-modules is supposed to do that.
What next?
------------------
Nothing Spoils the taste of peanut butter like unrequited love--Charlie Brown
[This message has been edited by Radar (edited 19 January 2001).]
DJ-dOoK
01-19-2001, 11:50 PM
Have you installed bin86 and autoconf?
------------------
One day, the DJ declared! Let this OS be taken to the world, and Linux was introduced to many frustrated windows users!
Radar
01-20-2001, 10:33 PM
Originally posted by DJ-dOoK:
Have you installed bin86 and autoconf?
Not that I know of, I'll research that.
------------------
Nothing Spoils the taste of peanut butter like unrequited love--Charlie Brown