amsn webcam not working anymore
Topic: amsn webcam not working anymore
started by: jls legalize
Posted by jls legalize on April 21 2008,23:01In amsn My aiptek webcam is not working anymore.
In earlier dsl version it was functioning properly
legalize cannabis, coke,..
Posted by roberts on April 22 2008,03:47Please post your working lsmod vs non-working lsmod.
Posted by jls legalize on May 08 2008,20:24lsmod from dsl-3.4.11
lsmod from dsl 4.3
legalize cannabis, coke...
Posted by roberts on May 08 2008,21:49Looks like stv680 and videodev are missing from your lsmods
Both stv680 and videodev can be found in < the extra modules > misc-driver-modules.tgz
Posted by jls legalize on May 09 2008,13:15I putted the file misc-driver-modules.tgz in mydsl/modules directory and I see at dsl startup that the system loads that file, but then it is not working.
I looked in the directory /KNOPPIX/lib/modules/2.4.31/kernel/drivers
and I see that the modules were not added, so I uncompressed the
misc-driver-modules.tgz and manually copied the needed modules in the proper direrctories, then I runned
sudo update modules
Then I tryed again amsn but nothing, so I manually loaded the needed modules issuing the commands
sudo modprobe videodev
sudo modprobe stv680
tryed again amsn and this time it worked.
legalize cannabis, coke..
Posted by roberts on May 09 2008,16:08The extra_modules are not mydsl extensions, that is why they are not located in the repository. The reason for this, is that typically, one would need only one to two of said modules.
The mechanism for auto loading modules is to place individual modules in the modules directory which is located under the mydsl directory. Then upon boot each module found in .../mydsl/modules/ will be insmod'ed at boot.
Of course one can also use /opt/bootlocal.sh for finer control of module handling.
Posted by jls legalize on May 09 2008,22:44can u please give an example on what to put in ths in modules directory?
Theory is good, but examples are better
Anyway, I can manually copy this two modules in the above mentioned directories and add them to /opt/.filetool.lst so they'll go in backup.
but can I put
update-modules in /opt/bootlocal.sh ?
Another problem is that videodev and stv680 modules in dsl-3.4.11 where automatically loaded when needed, now it seems I have to manually load them
legalize cannabis, etc.
Posted by roberts on May 10 2008,02:50The auto scanned modules directory has been around since v3.2 see Notes section of the website.
An example was posted in 4.2.5 release candidate section. I am copying it here:
Because I have to support both legacy and unionfs, the auto scanned module will be insmod and not modprobed. So YMMV, could be just need the right combination and order of modules that insmod would suffice. Otherwise, the manual method as you have done will be necessary.
Alternately the said extension could be rebuilt with the necessary modules included and insmod'ed in the correct order.
In fact, if indeed, a tiny core, will ever succeed one needs to become familiar with this process.
Including every conceivable module, even when rarely needed just consumes too much space.
Posted by jls legalize on May 10 2008,11:51so, I placed stv680.o and videodev.o in mydsl/modules/ directory, and I can see they are loaded in the boot process, but then issuing lsmod I can't see the stv680 module loaded, I think cause it must be loaded after the videodev one.
legalize cannabis, coke...
Posted by roberts on May 10 2008,12:32I hear you. The hassle is because I am still supporting legacy style booting.
If I wasn't then I could be using modprobe in the auto boot loader and life would be good. But I have too many users still using legacy to drop its support.
What happens if you rename videodev.o to 01-videodev.o so that it is insmod'ed first? I know it is a kludge but this is what I have to work with.
That is why I stated YMMV and that your manual via /opt/bootlocal.sh is likely best for your situation.
With the new version of DSL I won't be faced with the hassle of trying to support legacy style booting.