Would like to use the Quickcam 9000 myself but it's not easy..
zanco
I do have the Quickcam laying around and I would like to connect it to
the Bifferboard.
The different webpages about this subject do not bring me to a
solution.
Here's the story:
When I received the Bifferboard I started with creating the Flash and
the rootfs from this URL:
http://sites.google.com/site/bifferboard/Home/legacy-firmware where I
did use the bb-bin-1.4.tar.bz2 to flash the Bifferboard and to create
the rootfs. With uname -r the board told me that it was running kernel
2.6.27.5. The webcam was noticed as USB device but not as UVC device.
I did notice in another message on the Bifferboard that it would
require kernel 2.6.30 and higher to have the V4L modules included to
be able to detect the UVC device. So I did walk around on the www and
found the Sunspot page:
http://www.sunspot.co.uk/Projects/Bifferboard/biffer_ready_made_files.html
where there was a link to the ready made files which made me assume
that that was what I needed for the quickcam.
So I downloaded http://bifferos.planetlee.eu/bb-bin-1.2.tar.bz2 and
flashed it to the Bifferboard. The Bifferboard rebooted and rebooted
and rebooted.
I tried another way to find the kernel 2.6.30 and found it at
http://cid-8a7b593a49903da5.skydrive.live.com/browse.aspx/linux/Bifferboard
I'm getting handy with flashing the Bifferboard so within 2 minutes
the board was flashed. At first I did try it with the rootfs from the
bifferboard 1.4.tar.bz2 but after booting the message " Booting linux
with: .......rootwait" there only appeared a single letter y after
which the Bifferboard had to be rebooted. The same thing happened, so
I decided to make the corresponding rootfs from the 2 zipped files
from the same URL. Too bad, same problem. Just one letter "y" about 20
seconds after the rootwait message. So, I tried the same without the
rootfs on usb (removed the usb stick) but about 20 seconds after
booting the "y" appears and there is no response anymore.
Flashed back to the 1.4 with the corresponding filesystem, the board
boots fine and is accessible.
However, as expected, still no regocnition of the USB camera.
Can someone give me the "missing link" ?
Thanks,
Ben
biff...@yahoo.co.uk
I can't help you with the webcam, but the 'y' happens half -way
through boot, as the console gets switched from early printk over to a
proper Linux serial device. That's it flushing out the transmit
buffer. So if this happens after a delay you can be pretty sure Linux
is booting. The reason you're not seeing any serial messages is
because your kernel command-line is not set to put the console on the
serial port. You need to have something like 'console=uart,io,0x3f8'
as command-line. This can be set via Biffboot, or hard-coded in the
kernel build.
regards,
Biff.
On Feb 4, 9:00 pm, zanco <benzands...@caiway.nl> wrote:
> Hi,
>
> I do have the Quickcam laying around and I would like to connect it to
> the Bifferboard.
> The different webpages about this subject do not bring me to a
> solution.
>
> Here's the story:
> When I received the Bifferboard I started with creating the Flash and
> the rootfs from this URL:http://sites.google.com/site/bifferboard/Home/legacy-firmwarewhere I
> did use the bb-bin-1.4.tar.bz2 to flash the Bifferboard and to create
> the rootfs. With uname -r the board told me that it was running kernel
> 2.6.27.5. The webcam was noticed as USB device but not as UVC device.
>
> I did notice in another message on the Bifferboard that it would
> require kernel 2.6.30 and higher to have the V4L modules included to
> be able to detect the UVC device. So I did walk around on the www and
> found the Sunspot page:http://www.sunspot.co.uk/Projects/Bifferboard/biffer_ready_made_files...
> where there was a link to the ready made files which made me assume
> that that was what I needed for the quickcam.
>
> So I downloadedhttp://bifferos.planetlee.eu/bb-bin-1.2.tar.bz2and
> flashed it to the Bifferboard. The Bifferboard rebooted and rebooted
> and rebooted.
>
> I tried another way to find the kernel 2.6.30 and found it at
>
> http://cid-8a7b593a49903da5.skydrive.live.com/browse.aspx/linux/Biffe...
Andrew Scheller
> the Bifferboard.
I've not got a webcam, but I'll try to provide a few pointers!
> I did notice in another message on the Bifferboard that it would
> require kernel 2.6.30 and higher to have the V4L modules included to
> be able to detect the UVC device.
Sounds reasonable ;) But I'm sure sunspot had his webcam working
before Biff ported 2.6.30 to the bifferboard
http://sunspot.co.uk/Projects/Bifferboard/biffer_build_root_files.html
> So I did walk around on the www and
> found the Sunspot page:
> http://www.sunspot.co.uk/Projects/Bifferboard/biffer_ready_made_files.html
> where there was a link to the ready made files which made me assume
> that that was what I needed for the quickcam.
I've not used any of the sunspot files - I prefer to stick with the
'official versions' at least for now - I used to run bb-bin-1.4, but
I'm now running slack13-rootfs-9.
(although I think it'd be great if sunspot tidied up some of his notes
and wrote them up on the BB wiki)
> I tried another way to find the kernel 2.6.30 and found it at
> http://cid-8a7b593a49903da5.skydrive.live.com/browse.aspx/linux/Bifferboard
> bifferboard 1.4.tar.bz2 but after booting the message " Booting linux
> with: .......rootwait" there only appeared a single letter y after
> which the Bifferboard had to be rebooted. The same thing happened, so
> I decided to make the corresponding rootfs from the 2 zipped files
> from the same URL. Too bad, same problem. Just one letter "y" about 20
> seconds after the rootwait message. So, I tried the same without the
> rootfs on usb (removed the usb stick) but about 20 seconds after
> booting the "y" appears and there is no response anymore.
http://public.bay.livefilestore.com/y1pQXPEmdmarUmO6vhVTPB9ppwT5kGMPPgawgAjmmhHCqOPn4185L-9h5hlgzTEkaWRuiptzYZdwUMDibIPBgHDgA/readme.txt
says:
"The serial port has been modified so that it only sends and receives
when you want it to
- so you can send and receive individual characters to an external PIC
micro or similar.
Kernel processes do not talk to the rs232 port"
So that'll be why you're not seeing any serial output - your
bifferboard is still happily booting though :)
> Can someone give me the "missing link" ?
Not much help I'm afraid, but I do know there's at least 3 people who
have got webcams working with bifferboard...
Lurch
d1savowed
A daft question, but do you have a great need to run OpenWRT or can
you use another distro? I know at least from a Debian perspective, the
module for the webcam is there and working. I've had a Quickcam Sphere
and a Lego Quickcam working on the bifferboard with no problems, even
using the mjpg-streamer software to view them in realtime.
I'm not 100% sure, but I thought that the OpenWRT-everything tarball I
posted on Sourceforge a while back had all of the USB webcam drivers
in. The release is a few months old (and I need to make a new one),
but it should all be there in the tarball for you.
Stu
Marco Bauer
i use the Quickcam 9000 with success on the Slackware Build (Kernel
2.6.30.5).
Mjpeg-streamer works to with it. With Slack there are no problems ..
Regards,
Marco
--------------------------------------------------
From: "d1savowed" <stu...@linux-depot.com>
Sent: Saturday, February 06, 2010 2:24 AM
To: "Bifferboard" <biffe...@googlegroups.com>
Subject: [bifferboard] Re: Would like to use the Quickcam 9000 myself but
it's not easy..
> --
> You received this because you are subscribed to the "Bifferboard" Google
> group - honest!
> To unsubscribe from this group, send email to
> bifferboard...@googlegroups.com
>
rolf
here is how I got a Webcam working (its a Logitech 5000 I suppose, but
the instructions apply to model 9000):
Got the openwrt-traball from:
svn co https://bifferboard.svn.sourceforge.net/svnroot/bifferboard/wrt
I think that's the 1.4-version.
The rest was done following exactly Grahams instructions at:
http://www.sunspot.co.uk/Projects/sweexproject.htm
Hope you will have success this way.
Rolf
On 4 Feb., 22:00, zanco <benzands...@caiway.nl> wrote:
> Hi,
>
> I do have the Quickcam laying around and I would like to connect it to
> the Bifferboard.
> The different webpages about this subject do not bring me to a
> solution.
>
> Here's the story:
> When I received the Bifferboard I started with creating the Flash and
> the rootfs from this URL:http://sites.google.com/site/bifferboard/Home/legacy-firmwarewhere I
> did use the bb-bin-1.4.tar.bz2 to flash the Bifferboard and to create
> the rootfs. With uname -r the board told me that it was running kernel
> 2.6.27.5. The webcam was noticed as USB device but not as UVC device.
>
> I did notice in another message on the Bifferboard that it would
> require kernel 2.6.30 and higher to have the V4L modules included to
> be able to detect the UVC device. So I did walk around on the www and
> found the Sunspot page:http://www.sunspot.co.uk/Projects/Bifferboard/biffer_ready_made_files...
> where there was a link to the ready made files which made me assume
> that that was what I needed for the quickcam.
>
> So I downloadedhttp://bifferos.planetlee.eu/bb-bin-1.2.tar.bz2and
> flashed it to the Bifferboard. The Bifferboard rebooted and rebooted
> and rebooted.
>
> I tried another way to find the kernel 2.6.30 and found it at
>
> http://cid-8a7b593a49903da5.skydrive.live.com/browse.aspx/linux/Biffe...
rolf
what software do you use with slackware? I was looking for mjpg-
streamer (which is running well under openwrt), but did not find it
for slackware.
Rolf
Marco Bauer
I use mjpeg-streamer. I can send you my Build for slackware.
Regards Marco
zanco
On 6 feb, 14:48, "Marco Bauer" <ma...@wtns.de> wrote:
> Hi Ben,
>
> i use the Quickcam 9000 with success on the Slackware Build (Kernel
> 2.6.30.5).
> Mjpeg-streamer works to with it. With Slack there are no problems ..
>
> Regards,
> Marco
>
Marco,
I did try the latest Slackware build including the image for the
flash. The board did flash OK, I did unpack the filesystem to the USB
stick, I did a reboot on the board without USB stick, booted without
problems and stated it was waiting for the filesystem.
Then, after putting in the USB stick the Kernel panicked.
sd 0:0:0:0: [sda] 15663104 512-byte hardware sectors: (8.01 GB/7.46
GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
List of all partitions:
0800 7831552 sda driver: sd
0801 7825423 sda1
No filesystem could mount root, tried: ext3
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(8,1)
Any idea what could be the problem ?
TnX,
Ben
Andrew Scheller
>
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
> block(8,1)
>
> Any idea what could be the problem ?
Sorry to ask the obvious, but is your USB stick definitely formatted to ext3 ?
If you've not already seen it, have a read of
http://sites.google.com/site/bifferboard/Home/desktop-linux-distributions/slackware/newbie-instructions
Lurch
Sunspot
people like me who want to *use* the board rather than develop Linux
on it -
For OpenWrt
http://sunspot.co.uk/Projects/Bifferboard/distro.html
For Debian
http://sunspot.co.uk/Projects/Bifferboard/Debian_distro.html
Both "distros" run the 9000 web cam "out of the box" - there are still
some functions missing but both seem stable for a user.
I have been running the Debian one for some months with a 9000 webcam
with no crashes.
I stick with Debian because it runs i2c bus read and write. OpenWrt
i2c writes and can control a PIC as a servo driver but fails to read
the bus. OpenWrt needs no swap space on the memory stick and the stick
may last longer - I am doing a Debian life test at present since I
need the i2c!
Please say if the download works if you try it.
On Feb 4, 9:00 pm, zanco <benzands...@caiway.nl> wrote:
> Hi,
>
> I do have the Quickcam laying around and I would like to connect it to
> the Bifferboard.
> The different webpages about this subject do not bring me to a
> solution.
>
> Here's the story:
> When I received the Bifferboard I started with creating the Flash and
> the rootfs from this URL:http://sites.google.com/site/bifferboard/Home/legacy-firmwarewhere I
> did use the bb-bin-1.4.tar.bz2 to flash the Bifferboard and to create
> the rootfs. With uname -r the board told me that it was running kernel
> 2.6.27.5. The webcam was noticed as USB device but not as UVC device.
>
> I did notice in another message on the Bifferboard that it would
> require kernel 2.6.30 and higher to have the V4L modules included to
> be able to detect the UVC device. So I did walk around on the www and
> found the Sunspot page:http://www.sunspot.co.uk/Projects/Bifferboard/biffer_ready_made_files...
> where there was a link to the ready made files which made me assume
> that that was what I needed for the quickcam.
>
> So I downloadedhttp://bifferos.planetlee.eu/bb-bin-1.2.tar.bz2and
> flashed it to the Bifferboard. The Bifferboard rebooted and rebooted
> and rebooted.
>
> I tried another way to find the kernel 2.6.30 and found it at
>
> http://cid-8a7b593a49903da5.skydrive.live.com/browse.aspx/linux/Biffe...
zanco
On 10 feb, 23:54, Andrew Scheller <ya...@loowis.durge.org> wrote:
>
> Sorry to ask the obvious, but is your USB stick definitely formatted to ext3 ?
>
> If you've not already seen it, have a read ofhttp://sites.google.com/site/bifferboard/Home/desktop-linux-distribut...
>
> Lurch
you rang, Madam ?
Thanks a BIG LOT for your reply.
At least you made a bell ring over here. I should be ashamed a lot.
When I plug in the USB stick into the openSuse system the sign "ext2"
should have made some bells ringing. Now, it's formatted Ext3, 2
partions, the rootfs is copied and the board boots AND recognized the
camera AND made a Video0 device.
There does rise one other question, for which I did try to search for
the answer on the board, but in Slackware, what is used instead of
opkg or ipkg ?
The command to start streaming seems to like the mjpg_streamer being
installed but both opkg and ipkg are not recognized and answered as
"command not found".
Thanks again.
Ben
M P
including a staticaly compiled mjpg-streamer for the 9000. I've been
using it for a few months and it works great. I just flashed a 8M
board with the kernel+initrd file and it still works perfectly:
The whole distro & kernel, including modules and so on is:
1726656 bytes. vmlinuz-full.bin
Add "rdinit=/linuxrc" to your kernel command line, the rest just all
work, including a dropbear ssh daemon.
Michael
biff...@yahoo.co.uk
> http://gitorious.org/minifs/
Note that since this is based on 2.6.32, you may experience stability
issues using the GPIO stuff, e.g. i2c, w1 using the patches I've
created. This is one of the reasons I've stuck with 2.6.30.5 for the
moment.
If you're only using USB + Ethernet, there should be no problem.
cheers,
Biff.
PS: Of course, if Michael has fixed these issues, then please ignore,
and I need to merge his patches into my Slackware distro!
Andrew Scheller
> the answer on the board, but in Slackware, what is used instead of
> opkg or ipkg ?
You want to use slapt-get, as explained on
http://sites.google.com/site/bifferboard/Home/desktop-linux-distributions/slackware
Lurch
zanco
On 11 feb, 06:03, Sunspot <fgmarsh...@sunspot.co.uk> wrote:
> I saved my backup files as a sort of "load it-run it distro" for
> people like me who want to *use* the board rather than develop Linux
> on it -
>
> For OpenWrthttp://sunspot.co.uk/Projects/Bifferboard/distro.html
>
> For Debianhttp://sunspot.co.uk/Projects/Bifferboard/Debian_distro.html
>
> Both "distros" run the 9000 web cam "out of the box" - there are still
> some functions missing but both seem stable for a user.
>
Cut
>
> Please say if the download works if you try it.
>
Hi,
Yesterday I did download and install the Debian filesystem and flashed
the image to the bifferboard.
It's working great !
I did manually change the IP address in the network settings to
192.168.0.44. I did enter the url to the board in the browser, choose
the script to start the webcam driver, which failed because it points
to 0.9, I did edit all scripts and html's and replaced the 0.9 by my
0.44 and tried it again. Then a webpage came up which allowed me to
turn on the webcam script and view the page. All the examples, static
and streaming, do work wel !
tar'ring the files for the rootfs did give an error "exitted with
previous error" message at the end but there was no error text, so I
did copy it to the USB stick (partioned 7 Gig Ext3 and 512 MB Swap)
and it did work without problems.
Now I'm going to try to start the 2nd webcam on an other port '-)
Webcam is temporarily online at http://www.pe2bz.nl/hamradio/test.html
Tnx and best regards,
Ben
zanco
>
>
> Tnx and best regards,
> Ben
Starting a second webcam is a story on its own...
When I try this:
/home/mjpg-streamer-r63/mjpg_streamer -i "/home/mjpg-streamer-r63/
input_uvc.so -d /dev/video1 -r 640x480" -b -o "/home/mjpg-streamer-63/
output_http.so -p 8081 -w /home/mjpg-streamer-r63/www" I get rewarded
with the following message:
enabling daemon modeforked to background (1722)
after which there is nothing available at port 8081.
I've been overlooking the webpages with parameters for the
input_uvc.so but I can't see what's wrong.
The camera at port 8080 keeps running, and the /dev/video1 is
available (it's a second webcam).
One other question: If I restart the Bifferboard the device which was
video0 becomes (not always, but sometimes) video1 and vice versa. Is
there a way to store these devices to have them link to the right
camera ?
TnX a lot,
Ben
Sunspot
I once ran it OK
I now forget the detail but you could study the files in the download
that is linked to that page
Sunspot
zanco
On 19 feb, 02:44, Sunspot <fgmarsh...@sunspot.co.uk> wrote:
> oops this pagehttp://johnarthur.wordpress.com/2008/03/25/a-high-resolution-ip-webcam/
>
> On Feb 19, 1:43 am, Sunspot <fgmarsh...@sunspot.co.uk> wrote:
>
>
>
> > This page refers to a 2 camera Slug system.
> > I once ran it OK
> > I now forget the detail but you could study the files in the download
> > that is linked to that page
>
Hi Graham,
Thanks for the url. I did find the example for a 3 camera system and
the solution was simple, the line to call the next video input is to
be connected to the previous line in the script with the & sign.
So, splitting the script in two separate command lines, one for each
camera, does not work. If I make a long command line where the line
for video0 has the & at the end and is followed by the command line
for video1 all works great.
TnX agn,
Ben
Andrew Scheller
> camera, does not work. If I make a long command line where the line
> for video0 has the & at the end and is followed by the command line
> for video1 all works great.
In the unix-world, bunging a & on the end of a command line means "run
this command in the background" (and return the shell to the
foreground).
Without the & (as in your example) it would run video0, and only when
that process died would it then run the command for video1.
Lurch
zanco
Thanks for the explanation. Indeed I did succeed once getting the
video1 started, by omitting the -b option from the command line
(making it not running on the background), run the script (at that
moment the one without the & at the end of the line) which started
video0 fine, than stopped it with ctrl-c, after which to my big
surprise video1 was started. Just as you described above.
I do have one other issue, with Samba, but I'll start a new topic for
that question.
Best regards,
Ben