Invalid Module Format - Githubissues

SchruteRampage commented 10 years ago

Hello, I seem to have everything running a built correctly except I am getting one error that I can't figure out.

When I run the 'sudo insmod usbtv.ko' command when I am located in the usbtv folder, I get the error: could not insert module usbtv.ko: invalid module format.

Any ideas?

gkaindl commented 10 years ago

"invalid module format" is usually the error message you get if you build a module for a different kernel (e.g. with different kernel headers and/or symbol file) than for the kernel you want to insert it into. make sure that the kernel headers/sources that you are using the build the module match the version of the kernel you are running.

the script I put in the "misc" folder works for me, but be aware that I just pulled this off a "gist" on github. If it doesn't install the right kernel headers for you, you can still pull them from the raspberry pi repository (they also keep the Module.symvers files for all their builds there).

SchruteRampage commented 10 years ago

So I am at the point where I will send you $10 bucks to your paypal if you just take a few minutes and talk me through getting this setup. I'm not a linux guru and I can't figure out the usbtv driver. I spend a lot of money on the LED strips and the other parts, so I would really like this to get running. The script in the misc folder you were talking about was the get-kernel-source right? So does that script download the necessary files with your PAL alterations and it just happens that his script downloads the wrong headers/sources, which don't match the kernel running on my pi which is 3.6.11+?? Please let me know if you have time to just help me out until I get it working.

andyclarke commented 10 years ago

I too am having this problem. Looking at dmesg and it is as you say, a version mismatch. I'm just not sure how.

SchruteRampage commented 10 years ago

He said it has something to do with the file in the misc folder called "get-kernel-source", but the actual code inside this script pulls the newest version or the kernel's headers and source files or something like that, but it refuses to match with the 3.6.11+ kernel version running on the pi. I've worked on it for days and have not been able to figure it out lol

mjseid commented 10 years ago

Are you guys still having this issue? I remember hitting this as well, and I can look through my notes and post maybe more verbose steps to run the script and insert the proper modules in the proper order.

SchruteRampage commented 10 years ago

Yeah still having the issue. And yes, your help would be awesome.

andyclarke commented 10 years ago

Yes, I'm still having issues as well. I've tried several times running updates at different times. It seems to compile it against 3.6.11 and not 3.6.11+ Any help most appreciated.

mjseid commented 10 years ago

I am running the 3.6.11+ kernel and using his script it does pull down and compile the right versions for me. The script gets the current kernel version from uname so it knows which one to pull down.

Here's what I did to get it going: cd /abmi-tv/misc/ chmod 755 get-kernel-source.sh ./get-kernel-source.sh

You can verify the version of kernel your running with "uname -r" and you can verify the source the script pulled down by the following command "more /lib/modules/3.6.11+/build/arch/arm/kernel/asm-offsets.s | grep 3.6".

Now make the usbtv driver: cd usbtv-driver/ make && make install

_not sure if these are necessary, I was trying to get things working so might not be required_* apt-get install v4l-utils ffmpeg libcunit1-dev v4l2loopback-dkms v4l2loopback-source v4l2loopback-utils dov4l

Now you're ready to load the modules: * make sure you load these kernel modules, in order, they are required for the usbtv module to load** modprobe spi-bcm2708 modprobe videobuf2-vmalloc modprobe videobuf2-core insmod usbtv.ko

That should be enough to get it working. I want to load the modules automatically at boot so I also did the following: **\ copy the usbtv driver ot the current kernel module path and rebuild module map cd /lib/modules/3.6.11+/kernel/drivers/media/video/ cp /ambi-tv/misc/usbtv-driver/usbtv.ko . depmod -a

and add the following lines to the end of /etc/modules so they are loaded automatically on boot: spi-bcm2708 videobuf2-vmalloc videobuf2-core usbtv

andyclarke commented 10 years ago

Thank you for taking the time to post that. It is pretty much what I have done.

The problem is still with trying to load the usbtv.ko module. pi@raspberrypi ~/ambi-tv/misc/usbtv-driver $ sudo insmod usbtv.ko Error: could not insert module usbtv.ko: Invalid module format And dmesg shows: _usbtv: disagrees about version of symbol modulelayout

I have tried both before and after running rpi-update (with complete fresh installs inbetween and running the included script to get the shouce).

The only thing you appear to have done which is different to what I did, is when building the module I just typed build and you say you typed make && make install.

Trying that I get this other error:

pi@raspberrypi ~/ambi-tv/misc/usbtv-driver $ make && make install
make -C /lib/modules/3.6.11+/build  M=/home/pi/ambi-tv/misc/usbtv-driver modules
make[1]: Entering directory `/usr/src/linux-source-3.6.11+'
  CC [M]  /home/pi/ambi-tv/misc/usbtv-driver/usbtv.o
/home/pi/ambi-tv/misc/usbtv-driver/usbtv.c:561:8: warning: initialization from incompatible pointer type [enabled by default]
/home/pi/ambi-tv/misc/usbtv-driver/usbtv.c:561:8: warning: (near initialization for âusbtv_ioctl_ops.vidioc_s_stdâ) [enabled by default]
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/pi/ambi-tv/misc/usbtv-driver/usbtv.mod.o
  LD [M]  /home/pi/ambi-tv/misc/usbtv-driver/usbtv.ko
make[1]: Leaving directory `/usr/src/linux-source-3.6.11+'
make -C /lib/modules/3.6.11+/build  M=/home/pi/ambi-tv/misc/usbtv-driver modules_install
make[1]: Entering directory `/usr/src/linux-source-3.6.11+'
mkdir: cannot create directory `/lib/modules/3.6.11': Permission denied
make[1]: *** [_emodinst_] Error 1
make[1]: Leaving directory `/usr/src/linux-source-3.6.11+'
make: *** [install] Error 2

Where it still looks like it is looking for a 3.6.11 directory not 3.6.11+, but I could be wrong.

Thanks again.

mjseid commented 10 years ago

I'm not sure why, but the "make install" part the script dumps the .ko file into the 3.6.11 branch instead of the 3.6.11+ branch. That's why you have to manually insmod the file instead of just calling modprobe, b/c the install is not putting it into the right path for modprobe to find.

It should still result in a working module though. The errors you saw are b/c you were not using sudo...I have a bad habit of always doing things as root :)

Here's an example of what I see: root@raspberrypi:/ambi-tv/misc/usbtv-driver_temp# make clean make -C /lib/modules/3.6.11+/build M=/ambi-tv/misc/usbtv-driver_temp clean make[1]: Entering directory /usr/src/linux-source-3.6.11+' CLEAN /ambi-tv/misc/usbtv-driver_temp/.tmp_versions CLEAN /ambi-tv/misc/usbtv-driver_temp/Module.symvers make[1]: Leaving directory/usr/src/linux-source-3.6.11+' root@raspberrypi:/ambi-tv/misc/usbtv-driver_temp# ls Makefile Makefile.orig usbtv.c usbtv.c.orig root@raspberrypi:/ambi-tv/misc/usbtv-driver_temp# make && make install make -C /lib/modules/3.6.11+/build M=/ambi-tv/misc/usbtv-driver_temp modules make[1]: Entering directory /usr/src/linux-source-3.6.11+' CC [M] /ambi-tv/misc/usbtv-driver_temp/usbtv.o /ambi-tv/misc/usbtv-driver_temp/usbtv.c:561:8: warning: initialization from incompatible pointer type [enabled by default] /ambi-tv/misc/usbtv-driver_temp/usbtv.c:561:8: warning: (near initialization for ‘usbtv_ioctl_ops.vidioc_s_std’) [enabled by default] Building modules, stage 2. MODPOST 1 modules CC /ambi-tv/misc/usbtv-driver_temp/usbtv.mod.o LD [M] /ambi-tv/misc/usbtv-driver_temp/usbtv.ko make[1]: Leaving directory/usr/src/linux-source-3.6.11+' make -C /lib/modules/3.6.11+/build M=/ambi-tv/misc/usbtv-driver_temp modules_install make[1]: Entering directory /usr/src/linux-source-3.6.11+' INSTALL /ambi-tv/misc/usbtv-driver_temp/usbtv.ko DEPMOD 3.6.11 make[1]: Leaving directory/usr/src/linux-source-3.6.11+'

root@raspberrypi:/ambi-tv/misc/usbtv-driver_temp# ls /lib/modules/3.6.11/extra/ usbtv.ko v4l2loopback.ko root@raspberrypi:/ambi-tv/misc/usbtv-driver_temp#

andyclarke commented 10 years ago

Thanks. Still no joy though.

For completeness, here are my versions. What does modinfo, vermagic say for you?

pi@raspberrypi ~/ambi-tv/misc/usbtv-driver $ modinfo usbtv.ko
filename:       /home/pi/ambi-tv/misc/usbtv-driver/usbtv.ko
license:        Dual BSD/GPL
description:    Fushicai USBTV007 Video Grabber Driver
author:         Lubomir Rintel
srcversion:     80355D8F592C82839914844
alias:          usb:v1B71p3002d*dc*dsc*dp*ic*isc*ip*in*
depends:        videobuf2-core,videodev,videobuf2-vmalloc
vermagic:       3.6.11 preempt mod_unload modversions ARMv6
pi@raspberrypi ~/ambi-tv/misc/usbtv-driver $ uname -r
3.6.11+
pi@raspberrypi ~/ambi-tv/misc/usbtv-driver $ more /lib/modules/3.6.11+/build/arch/arm/kernel/asm-offsets.s | grep 3.6
@ -I /usr/src/linux-source-3.6.11+/arch/arm/include
@ -include /usr/src/linux-source-3.6.11+/include/linux/kconfig.h

If I try running sudo make then it appears to try and compile the base source code??!

pi@raspberrypi ~/ambi-tv/misc/usbtv-driver $ sudo make
make -C /lib/modules/3.6.11+/build  M= modules
make[1]: Entering directory `/usr/src/linux-source-3.6.11+'
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
make[2]: `include/generated/mach-types.h' is up to date.
  CALL    scripts/checksyscalls.sh
  CC [M]  fs/9p/vfs_inode.o
  CC [M]  fs/9p/vfs_inode_dotl.o
  CC [M]  fs/9p/vfs_addr.o
  CC [M]  fs/9p/vfs_file.o
  CC [M]  fs/9p/vfs_dir.o
  CC [M]  fs/9p/vfs_dentry.o
  CC [M]  fs/9p/v9fs.o
  CC [M]  fs/9p/fid.o
  CC [M]  fs/9p/xattr.o
  CC [M]  fs/9p/xattr_user.o
  CC [M]  fs/9p/acl.o
  LD [M]  fs/9p/9p.o
  CC [M]  fs/btrfs/super.o
  CC [M]  fs/btrfs/ctree.o
^Cmake[3]: *** [fs/btrfs/ctree.o] Interrupt
make[2]: *** [fs/btrfs] Interrupt
make[1]: *** [fs] Interrupt
make: *** [all] Interrupt

All a bit odd. I'm sure it's something simple but it's beyond me at the moment!

gkaindl commented 10 years ago

the instructions posted by @mjseid above is also what I do, except that I now realize that that yes, make install will put it into 3.6.11, rather than 3.6.11+ – unfortunately, that's a problem with the kernel headers package, not the Makefile (which just relies on the module build environment). so yes, you could copy the resulting .ko into your modules directory (somewhere, doesn't really matter) and run sudo depmod 3.6.11+

Also, there is not just "one" 3.6.11+ kernel, there are lots of sub-releases: As an example, the output of uname -rv currently returns 3.6.11+ #494 PREEMPT Fri Jul 5 15:30:31 BST 2013 (note the #494).

For everyone struggling with this, I'd recommend to open a root shell via sudo -s, then delete the currently installed kernel headers rm -rf /usr/src/linux-source-3.6.11+, remove the modules build link rm /lib/modules/3.6.11+/build, then run the downloader script again bash get-kernel-source.sh. Then try building and inserting the module again.

If there's anything more to it than just having the wrong kernel headers, I'd really like to figure this out, so that I can fix this for future users. I'm pretty sure it's just a version mismatch, though. Anyway, I'm re-opening this for now, even if the solution might just be an additional "warning" line in the docs ;-)

SchruteRampage commented 10 years ago

So after removing the files and running the downloader script again, do we then build the usbtv make file and then use sudo depmod 3.6.11+ ? What directory do we have to be in to run that depmod command? I'm still getting the v4l2-grab failed to stat '/dev/video0' no such file or directory.

SchruteRampage commented 10 years ago

I got the insmod usbtv.ko to work without any errors. But when I go to run the command bin/ambi-tv -f sample.conf, I still am getting the v4l2-grab: failed to stat ' /dev/video0' : 2 (no such file or directory). Which means the /dev/video0 directory is not getting made correct? What command should make the /dev/video0 folder? And does the easycap device need to be plugged in during any of this? I am wondering because I need my keyboard and mouse plugged in for installation purposes, but then I have to unplug one or the other to plug in the easycap dongel.

andyclarke commented 10 years ago

@gkaindl Thanks for the reply. Your idea does sound like it should work but I gave it a quick try this morning before work and I still seemed to have the same problem. I will try again tonight. Talking about version numbers and mine is 3.6.11+ #528 after running rpi-update. Why is it so much newer than yours? Or have you not run update for a while. Could this be part of the problem? I did try before updating but will try again from fresh.

@SchruteRampage I'm pretty sure you will need it plugged in for it to load the video0 device. You don't need the mouse so you can use that port.

andyclarke commented 10 years ago

I've tried a fresh install tonight. Flashed the SD Card and it reported 3.6.11+ #474 I did an apt-get update/upgrade. Ran rpi-update which took it up to #528

When running the get-kernel-source script it says: Installing kernel source for revision a0c98fa6bc0f... Not sure if that is the right version, I don't know how to search the github repo for commit revisions.

Tried to make the usbtv driver and still getting the same problem :(

modinfo vermagic always says 3.6.11. I would have thought this should be 3.6.11+

root@raspberrypi:/home/pi/ambi-tv/misc/usbtv-driver# modinfo usbtv.ko
filename:       /home/pi/ambi-tv/misc/usbtv-driver/usbtv.ko
license:        Dual BSD/GPL
description:    Fushicai USBTV007 Video Grabber Driver
author:         Lubomir Rintel
srcversion:     80355D8F592C82839914844
alias:          usb:v1B71p3002d*dc*dsc*dp*ic*isc*ip*in*
depends:        videobuf2-core,videodev,videobuf2-vmalloc
vermagic:       3.6.11 preempt mod_unload modversions ARMv6

dmesg says: usbtv: disagrees about version of symbol module_layout

Any further suggestions most appreciated.

sn00zerman commented 10 years ago

I had the same problems …

make sure, that if you do a 'lsusb', you see a device in the list, with ID 1b71:3002 ...

This is what worked form me:

Started with a fresh Debian Wheezy f(2013-07-26 edition)
I did NOT do the update/upgrade thingy
from within the /home/pi folder, I did: wget https://github.com/gkaindl/ambi-tv/archive/master.zip
next step, I unzipped master.zip
I did go into the misc folder, and did: sudo bash get-kernel-source.sh
when this finished, I did go into the usbtv-driver folder and did: make
next I created a folder "extra" within /lib/modules/3.6.11+ and copied the usbtv.ko into this new folder
next: sudo depmod 3.6.11+
sudo modprobe videobuf2_core
sudo modprobe videobuf2_vmalloc
sudo modprobe usbtv
You should now have a "video0" in the /dev
If this is OK, then you can add the following lines to /etc/modules videobuf2_core videobuf2_vmalloc usbtv
Reboot RPI, eeh voila, ambi-tv should work fine :-)
After this, I did the update/upgrade thingy …

I have 260 LEDs up-and-running, didn't need to overclock my RPI. (I'm using a REV. A model for my ambi-tv)

good luck, Kris

-=(http://www.digitalplayground.be)=- Where fun meets technology

Op 23-aug.-2013, om 21:47 heeft Andy notifications@github.com het volgende geschreven:

I've tried a fresh install tonight. Flashed the SD Card and it reported 3.6.11+ #474 I did an apt-get update/upgrade. Ran rpi-update which took it up to #528

When running the get-kernel-source script it says: Installing kernel source for revision a0c98fa6bc0f... Not sure if that is the right version, I don't know how to search the github repo for commit revisions.

Tried to make the usbtv driver and still getting the same problem :(

modinfo vermagic always says 3.6.11. I would have thought this should be 3.6.11+

root@raspberrypi:/home/pi/ambi-tv/misc/usbtv-driver# modinfo usbtv.ko filename: /home/pi/ambi-tv/misc/usbtv-driver/usbtv.ko license: Dual BSD/GPL description: Fushicai USBTV007 Video Grabber Driver author: Lubomir Rintel srcversion: 80355D8F592C82839914844 alias: usb:v1B71p3002d_dc_dsc_dp_ic_isc_ipin depends: videobuf2-core,videodev,videobuf2-vmalloc vermagic: 3.6.11 preempt mod_unload modversions ARMv6 Any further suggestions most appreciated.

— Reply to this email directly or view it on GitHub.

andyclarke commented 10 years ago

Thanks Kris. I have no idea what was different but I followed your instructions and it now seems to have worked! Maybe it was not doing the apt-get update/upgrade, not sure. But it has now loaded. Awesome! :)

SchruteRampage commented 10 years ago

@sn00zerman , So I followed your directions exactly, but after doing sudo modprobe usbtv, there is no "video0" in the /dev directory. Also when did you run the make file inside the ambi-tv-master folder? Did you run it right after unzipping the master.zip archive ?? This is really getting on my nerves that the stupid video0 thing won't show up in my dev folder. And does the LED on your easycap dongle light up when its working? And do you have your white HDMI2AV box plugged into a laptop usb for power?

andyclarke commented 10 years ago

@SchruteRampage It doesn't really matter when you build the main program.

If you haven't already, add these lines to the end of /etc/modules

spi-bcm2708
videobuf2-vmalloc
videobuf2-core
usbtv

Then reboot with your EasyCap connected. If you still have problems please post the output from lsmod and also the last few lines from dmesg.

SchruteRampage commented 10 years ago

I added the lines to /etc/modules and the video0 is still not there.

Here is the lsmod output

module size used by usbtv 6366 0 videobuf2_core 26995 1 usbtv videodev 104342 2 usbtv,videobuf2_core media 13424 1 videodev videobuf2_vmalloc 2425 1 usbtv videobuf2_memops 2584 1 videobuf2_vmalloc spidev 5224 0 spi_bcm2708 4816 0 snd_bcm2835 16304 0 snd_pcm 77560 1 snd_bcm2835 snd_page_alloc 5145 1 snd_pcm snd_seq 53329 0 snd_seq_device 6438 1 snd_seq snd_timer 19998 2 snd_pcm,snd_seq snd 58447 5 snd_bcm2835,snd_timer,snd_pcm,snd_seq,snd_seq_device evdev 9426 2 leds_gpio 2235 0 led_class 3562 1 leds_gpio

And then the last few lines from dmesg

Linux media interface: v0.10 Linux video capture interface v2.00 usbcore: registered new interface driver usbtv smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1 bcm2835-cpufreq: switching to governor ondemand bcm2835-cpufreq: switching to governor ondemand Adding 102396k swap on /var/swap. Priority:-1 xtends:2 across:507900k SS

andyclarke commented 10 years ago

Could you do a lsusb as well please.

sn00zerman commented 10 years ago

It's almost 2 a.m. Here. Can you post your output of lsusb?

Verzonden van op mijn Acer Iconia Android tablet

SchruteRampage notifications@github.comschreef:

I added the lines to /etc/modules and the video0 is still not there.

Here is the lsmod output

module size used by usbtv 6366 0 videobuf2_core 26995 1 usbtv videodev 104342 2 usbtv,videobuf2_core media 13424 1 videodev videobuf2_vmalloc 2425 1 usbtv videobuf2_memops 2584 1 videobuf2_vmalloc spidev 5224 0 spi_bcm2708 4816 0 snd_bcm2835 16304 0 snd_pcm 77560 1 snd_bcm2835 snd_page_alloc 5145 1 snd_pcm snd_seq 53329 0 snd_seq_device 6438 1 snd_seq snd_timer 19998 2 snd_pcm,snd_seq snd 58447 5 snd_bcm2835,snd_timer,snd_pcm,snd_seq,snd_seq_device evdev 9426 2 leds_gpio 2235 0 led_class 3562 1 leds_gpio

And then the last few lines from dmesg

Linux media interface: v0.10 Linux video capture interface v2.00 usbcore: registered new interface driver usbtv smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1 bcm2835-cpufreq: switching to governor ondemand bcm2835-cpufreq: switching to governor ondemand Adding 102396k swap on /var/swap. Priority:-1 xtends:2 across:507900k SS

Reply to this email directly or view it on GitHub: https://github.com/gkaindl/ambi-tv/issues/7#issuecomment-23197755

SchruteRampage commented 10 years ago

Output of lsusb

Device 002: ID 0424:9512 Standard microsystems corp Device 001: ID 1d6b:0002 Linux foundation 2.0 root hub Device 003: ID 0424:ec00 Standard irosystems corp Device 004: ID 04d9:1603 Holtek semiconductor, inc. keyboard

andyclarke commented 10 years ago

From that, to me, it doesn't look like your EasyCap is plugged in. Is it? If it is, are you using an extension cable or hub?

SchruteRampage commented 10 years ago

Its plugged in, but its using the extender usb cable that came with it....that shouldn't matter should it?

Well it must of, I just plugged it directly in and the light is on now. I'm going to reboot and hopefully it should work now

andyclarke commented 10 years ago

It was causing problems for someone else. Can you try with out it? Or through a powered USB hub?

SchruteRampage commented 10 years ago

Ok, the program is now running and there is a "video0" ....So what commands do I have to run if the pi gets rebooted? Do I just need to run the ambi-tv program?

SchruteRampage commented 10 years ago

I'm still not getting any output from the LED's, but the program seems to be running fine. And just so I'm correct, only the video cable needs to be plugged into the HDMI2AV box correct? The red and white audio cables are not utilized right? If the program says its running, then does that mean I might have a wiring issues? Also, on the LED strip it says the two inner traces are the DI and CI...those stand for dat and clock correct?

And I also have 3 full meters of LED strip plugged in, so would I have to change anything in the sample.conf file to get the test to work? Or should the number of LED's not matter if it's only for testing ?

andyclarke commented 10 years ago

After a reboot you should just need to run the ambi-tvi program.

You are correct in that you only need the yellow video cable.

If the program is running and everything has power then I would guess it is a wiring problem. You could also try selecting the mood-light program (by pressing spacebar when ambi-tv is running to cycle through the different modes) to test your lights are working regardless of the video input.

You will need to change the configuration file to tell it how your lights are arranged. See the main docs for details on how the numbering system works.

sn00zerman commented 10 years ago

And you can also put the command to startup your ambi-tv software, including the path, into /etc/rc.local This makes you RPI run the ambi-tv, whenever the RPI starts up :-) (as a matter of fact, I have it running this way, so no need to attach a display to the RPI) If you connect it to your network, you can SSH to the pi, modify the config-file whenever you like, and remotely reboot :-)

best regards, Kris

-=(http://www.digitalplayground.be)=- Where fun meets technology

Op 24-aug.-2013, om 12:56 heeft Andy notifications@github.com het volgende geschreven:

After a reboot you should just need to run the ambi-tvi program.

You are correct in that you only need the yellow video cable.

If the program is running and everything has power then I would guess it is a wiring problem. You could also try selecting the mood-light program (by pressing spacebar when ambi-tv is running to cycle through the different modes) to test your lights are working regardless of the video input.

You will need to change the configuration file to tell it how your lights are arranged. See the main docs for details on how the numbering system works.

— Reply to this email directly or view it on GitHub.

SchruteRampage commented 10 years ago

I think I have finally discovered what is wrong with my setup. I have the Data and Clock pins connected to the wrong side of the LED strip. I have the PI connected to DO and CO which is clock output and data output. I'm going to undo the reel of LED's and connect to the DI and CI and hopefully my system should be up and running. That might be something you should put in the main wiki, because I just assumed the side hanging out of the plastic reel of LED's was the input side, but it wasn't.

SchruteRampage commented 10 years ago

My system is now up and running and the led's are running perfectly. Now I just need to alter my config file for my 42" and I will be set to go. Thanks for everyone's help. Sometimes in kinda fun when things don't work perfectly right out of the box.

SchruteRampage commented 10 years ago

Ok, it turns out I'm still having issues, I have changed the config file to the number of LED's on my setup, which is 96

this is what I have leds-top 18-45 leds-bottom 91-64 leds-left 17-0 leds-right 46-63

But when I execute the program, the colors seem to be changing correctly, but only LED's 0 through 7 are lightning up. Do you have any ideas on what issue would cause this?

SchruteRampage commented 10 years ago

Ok, so I did a fresh from scratch install and now all the LED's are lighting up, however, they are just flickering random colors in all three different programs (avg, edge, and mood). I don't see any errors in the code, so what might this issue be?

sn00zerman commented 10 years ago

If you use a separate power-supply for your RPI and your LED-strip, then you need to connect a wire between the GND of the LED-strip and your RPI GND-pin. (pin on the right of the SPI pins)

good luck, Kris

-=(http://www.digitalplayground.be)=- Where fun meets technology

Op 25-aug.-2013, om 02:48 heeft SchruteRampage notifications@github.com het volgende geschreven:

Ok, it turns out I'm still having issues, I have changed the config file to the number of LED's on my setup, which is 96

this is what I have leds-top 18-45 leds-bottom 91-64

— Reply to this email directly or view it on GitHub.

SchruteRampage commented 10 years ago

Oh ok, I will try that out and let you know. Thank you

SchruteRampage commented 10 years ago

@sn00zerman , thanks a ton, that fixed it. My system is working perfect now. Thank you to all of you for your help. It took a while, but it was definitely worth it. Looks awesome with the itunes visualizer in full screen.

eddiebishop commented 10 years ago

I bought the usb capture card from gkaindl's link, but I think I got unlucky and was sent a different chipset. The usbtv module compiled and loaded fine, but I get no video0 in /dev.

lsusb shows the following info on my capture card: Bus 001 Device 006: ID 1c88:0007 Somagic, Inc. SMI Grabber (EasyCAP DC60+ clone) (no firmware) [SMI-2021CBE]

I've ordered another usb cap card from amazon: http://www.amazon.com/gp/product/B00AH99L5O/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1

SchruteRampage commented 10 years ago

I am trying to calibrate the gamma values, and the red's and green's are pretty much spot on, but for navy blue, the color of the led is fairly turquoise. My current settings are red-1.55, green-1.6, and blue-1.62. Do you have any recommendations on how to adjust these numbers in more detail?

eddiebishop commented 10 years ago

The capture device I bought from my link works with gkaindl's driver. My EasyCAP that has the wrong chipset has a squared off s-video connector, while the correct EasyCAP's s-video is completely round. Hopefully this may help someone trying to find an EasyCAP with the right chipset, but with so many variations your mileage may vary.

hebaishi commented 10 years ago

@eddiebishop I have the exact same problem: my easycap device showed the same info as yours. Also ordered another easycap device from amazon. Really looking forward to getting everything working.

rocket59 commented 10 years ago

Hi, I'm hoping to put together one of these little units but have run into a major snag trying to set up the vidcap driver. I'm using the current image (2013-09-10) and followed the steps outlined by mjseid . I'm afraid I'm more a hardware than linux person so am hoping some one can point out what I've missed.

The get-kernel-source script ran fine and so did the make and make install (as root)

I loaded the modules: modprobe spi-bcm2708 modprobe videobuf2-vmalloc modprobe videobuf2-core

BUT when I tried loading the vidcap module: insmod usbtv.ko the whole thing simply crashed with the message: [1366.925247] Unable to handle kernel NULL pointer dereference at virtual address 00000004 [1366.937143] pgd = c4fb0000 [1366.943472] [00000004] *pgd=00000000 [1366.950690] Internal error: Oops: 5 [#] PREEMPT ARM

and a whole lot more information that I won't even pretend to understand.

The DC60 is of the correct type (fushicai, shows up correctly on running lsusb) and everything hangs off a powered hub.I can only assume that there's a conflict with something in the current raspbian image but have no idea as to what to do next unfortunately.

EDIT: There is definitely an issue with the most recent version of Raspbian and the vid cap driver. I managed to get the 2013-07-26 image from the RPi site archive and all is well.

nona00 commented 10 years ago

I can confirm that the usbtv.ko module crashes the whole system if raspbian 2013-09-10 is used.

Mrjohns42 commented 10 years ago

Get another SD card and try doing the exact same setup with 2013-07-26 version.

nona00 commented 10 years ago

@Mrjohns42: with 2013-07-26 the driver works

Mrjohns42 commented 10 years ago

Do you know if the kernel versions are the same in each image?

nona00 commented 10 years ago

2012-12-16 with all updates, Kernel 3.6.11+ #474 => compile warning (WARNING: "malloc_sizes" undefined!) and invalid module format after insmod 2013-07-26 without updates, Kernel 3.6.11+ #474 => works 2013-09-10 without updates, Kernel 3.6.11+ #538 => crash

nona00 commented 10 years ago

got the usbtv driver working with my raspbian 2012-12-16 installation (all updates installed, Kernel 3.6.11+ #474).

I had to replace the file /usr/share/doc/raspberrypi-bootloader/changelog.Debian.gz with the one contained in raspbian 2013-07-26. I executed get-kernel-source.sh and recompiled the driver. It seems that the changelog file does not match the installed (updated) kernel version.

Crafu commented 10 years ago

Hello everyone, I hope someone can help me, I've followed all the directions above and some of the ones on the other pages and I'm stuck. I've even bought a USB powerhub as a last ditch attempt to try and get it all running but I just can't get past the final hurdle when I try to run the AmbiTV program. Every time I get the following: lpd8806-spidev: failed to open device '/dev/spidev0.0' : 2 (No such file to directory). Main: failed to start initial program 'program_tv_edge_colour', aborting... I've followed Kris's instructions above and got past the issue I was having with the usbtv issue (turns out I had to use an older version o f Raspbian). If anyone can give me any pointers, I'd be really greatful. I can't help but feel I'm so close to getting this working. It's taken 4 days and a lot of late nights to get this far! Thanks in advance, Craig

gkaindl / ambi-tv

Invalid Module Format #7