linux1394-user Mailing List for IEEE 1394 for Linux (Page 420)
Brought to you by:
aeb,
bencollins
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(29) |
Nov
(36) |
Dec
(46) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(60) |
Feb
(82) |
Mar
(46) |
Apr
(50) |
May
(89) |
Jun
(60) |
Jul
(80) |
Aug
(130) |
Sep
(104) |
Oct
(105) |
Nov
(123) |
Dec
(107) |
2002 |
Jan
(142) |
Feb
(105) |
Mar
(63) |
Apr
(117) |
May
(136) |
Jun
(75) |
Jul
(105) |
Aug
(103) |
Sep
(149) |
Oct
(149) |
Nov
(98) |
Dec
(144) |
2003 |
Jan
(161) |
Feb
(100) |
Mar
(118) |
Apr
(126) |
May
(157) |
Jun
(173) |
Jul
(156) |
Aug
(89) |
Sep
(83) |
Oct
(106) |
Nov
(84) |
Dec
(69) |
2004 |
Jan
(119) |
Feb
(233) |
Mar
(232) |
Apr
(104) |
May
(113) |
Jun
(132) |
Jul
(87) |
Aug
(129) |
Sep
(186) |
Oct
(88) |
Nov
(148) |
Dec
(180) |
2005 |
Jan
(223) |
Feb
(176) |
Mar
(148) |
Apr
(193) |
May
(188) |
Jun
(236) |
Jul
(144) |
Aug
(89) |
Sep
(44) |
Oct
(86) |
Nov
(114) |
Dec
(89) |
2006 |
Jan
(94) |
Feb
(97) |
Mar
(57) |
Apr
(117) |
May
(46) |
Jun
(63) |
Jul
(51) |
Aug
(72) |
Sep
(50) |
Oct
(142) |
Nov
(70) |
Dec
(52) |
2007 |
Jan
(60) |
Feb
(67) |
Mar
(80) |
Apr
(81) |
May
(78) |
Jun
(52) |
Jul
(64) |
Aug
(55) |
Sep
(40) |
Oct
(87) |
Nov
(70) |
Dec
(44) |
2008 |
Jan
(80) |
Feb
(12) |
Mar
(82) |
Apr
(64) |
May
(33) |
Jun
(53) |
Jul
(41) |
Aug
(26) |
Sep
(35) |
Oct
(21) |
Nov
(30) |
Dec
(42) |
2009 |
Jan
(17) |
Feb
(32) |
Mar
(10) |
Apr
(19) |
May
(19) |
Jun
(28) |
Jul
(41) |
Aug
(14) |
Sep
(5) |
Oct
(46) |
Nov
(23) |
Dec
(20) |
2010 |
Jan
(46) |
Feb
(13) |
Mar
(9) |
Apr
(2) |
May
(19) |
Jun
(28) |
Jul
(37) |
Aug
(23) |
Sep
(5) |
Oct
(32) |
Nov
(19) |
Dec
(18) |
2011 |
Jan
(23) |
Feb
(9) |
Mar
(19) |
Apr
(38) |
May
(83) |
Jun
(30) |
Jul
(46) |
Aug
(32) |
Sep
(6) |
Oct
(3) |
Nov
(25) |
Dec
(31) |
2012 |
Jan
(21) |
Feb
(12) |
Mar
(19) |
Apr
(7) |
May
(27) |
Jun
(7) |
Jul
(2) |
Aug
(15) |
Sep
(8) |
Oct
(11) |
Nov
|
Dec
(3) |
2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(14) |
Jul
(1) |
Aug
(3) |
Sep
(4) |
Oct
(5) |
Nov
|
Dec
|
2014 |
Jan
(14) |
Feb
(2) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
(7) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(14) |
Nov
(5) |
Dec
(18) |
2015 |
Jan
(3) |
Feb
(1) |
Mar
(3) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(4) |
Aug
|
Sep
(2) |
Oct
(11) |
Nov
(2) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
(5) |
Mar
(7) |
Apr
|
May
(4) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Matteo M. <mat...@ti...> - 2001-01-15 10:17:46
|
Hello, uhm, it looks like your problems come from using a customized kernel source, a kind of thing sometimes distributors ship. It seems to me that you have a "stripped-down" version of the source code (a Red Hat thing?), comprising only the x86-related code: it's missing the source specific to different architectures (see the "ppc" in your error messages? It stands for PowerPC). I'd suggest to you either to: - download (http://www.kernel.org or your preferred local mirror) and install a "stock" kernel (preferably somewhere else in your path, like /home/inoue/kernel/linux...), then patch, configure and recompile this one. You're done! or: - use the cvs at sourceforge (somewhere at http://linux1394.sourceforge.net): enter your /usr/src/linux/drivers directory as root and login and checkout the ieee1394 development tree. More instructions on site. This will take less time than downloading a whole kernel tarball, in case you've got a slow connection. Greetings, Matteo Katsuhiro Inoue wrote: > Hello, > > I am using the kernel 2.2.16-22 and tried to patch ieee1394 to it (the > latest version - 2.2.18-20001223), but during the process, the following > error occured and could not install the modules. > > (Error messages are in Japanese therefore they may somewhat different than > the exact English version messages) > > I did exactly in line with the instruction on > linux1394.sourceforge.net/start_install.html except in the following > situations. > > When pathcing: > > can't find patch in line 259. the text leading up to this was: > > diff -ruN linux-2.2.orig/arch/ppc/config.in linux-2.2/arch/ppc/config.in > > --- linux-2.2.orig/arch/ppc/config.in Sat Dec23 03:54:38 2000 > > --- linux-2.2/arch/ppc/config.in Sat Dec23 03:56:20 2000 > > I looked into the /usr/src directory and I found config.in under > /usr/src/linux-2.2/arch/i386. Therefore I put that path in the prompt ("FIle > to patch") then I could proceed. > > I executed xconfig and set the configuration and save & exit. > > When make dep: > > /usr/src/linux-2.2/Rules.make:259 the target "irport.o" were given several > times within the same rule. > > When make bzImage: > > make[2]: *** [ksyms.o] error 1 > > make[1]: *** [first_rule] error 2 > > make: *** [_dir_kernel] error 2 > > Then I could not proceed anymore. > > If anyone experienced the same kind of situation and got over it, please let > me know how it could be resolved. > > Thank you! > > Katsuhiro Inoue > |
From: Dan D. <dde...@co...> - 2001-01-15 10:02:21
|
I have a little program that displays the web/desktop cameras' video in a window--whoopee! I personally have the Orange Micro iBot. I'm interested in making these cameras work with Kino, and adding a play-n-grab feature to Kino to do stop-motion animation. Also, I am thinking it would not be difficult to make the camera output a JPEG image for use on a website. I just looked up the Nikon D1. In "Nikon Capture" mode it can out TIFF images. I'd have to view the raw isochronous stream in order to determine how it is packetizing the data. It's probably just a matter of taking consecutive packets of a single frame and wrapping it inside of a TIFF file. Right now, there is no app that can take advantage of it. I just saw it at a price of about US$5000; I can not afford that right now! +-DRD-+ Felix Tang wrote: > > All, > > I'd like to clarify something... are video cameras like the pyro which > send uncompressed data supported by any applications? I understand that > Sony also makes quite a few of these video cameras as well. Secondly, how > about digital cameras like the Nikon D1? It takes still pictures but can > also capture video... although in what format I'm not sure. > > Felix > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Dan D. <dde...@co...> - 2001-01-15 09:39:05
|
I've added a hardware compatibility list/application to the linux1394.sourceforge.net website. This is a user-driven list, so you need to add your devices. A couple notes: - Only host/cardbus adapters should specify a chipset. - Please take the time to look up the CSR ROM GUIDs for your device using gscanbus. We can use this to make gscanbus' database of devices more complete, and I imagine other applications may make use of this to allow the user to select a device with which to work. I've also added recently a changelog to the home page, a FAQ section, and a notice about the broken drivers in the 2.4.0 kernel. +-DRD-+ |
From: Felix T. <ta...@ee...> - 2001-01-15 04:26:02
|
All, I'd like to clarify something... are video cameras like the pyro which send uncompressed data supported by any applications? I understand that Sony also makes quite a few of these video cameras as well. Secondly, how about digital cameras like the Nikon D1? It takes still pictures but can also capture video... although in what format I'm not sure. Felix |
From: Dan D. <dde...@co...> - 2001-01-13 18:33:38
|
Katsuhiro Inoue wrote: > > Hello, > > I am using the kernel 2.2.16-22 and tried to patch ieee1394 to it (the > latest version - 2.2.18-20001223), but during the process, the following > error occured and could not install the modules. > > (Error messages are in Japanese therefore they may somewhat different than > the exact English version messages) > > I did exactly in line with the instruction on > linux1394.sourceforge.net/start_install.html except in the following > situations. > > When pathcing: > > can't find patch in line 259. the text leading up to this was: > > diff -ruN linux-2.2.orig/arch/ppc/config.in linux-2.2/arch/ppc/config.in > > --- linux-2.2.orig/arch/ppc/config.in Sat Dec23 03:54:38 2000 > > --- linux-2.2/arch/ppc/config.in Sat Dec23 03:56:20 2000 > > I looked into the /usr/src directory and I found config.in under > /usr/src/linux-2.2/arch/i386. Therefore I put that path in the prompt ("FIle > to patch") then I could proceed. I am quite certain that the -p0 switch should be used with the recent patches as opposed to -p1. I'll confirm this and update the site documentation as needed. > I executed xconfig and set the configuration and save & exit. > > When make dep: > > /usr/src/linux-2.2/Rules.make:259 the target "irport.o" were given several > times within the same rule. > This looks related to the Infrared Port driver. Disable the driver in the config and try again. > When make bzImage: > > make[2]: *** [ksyms.o] error 1 > > make[1]: *** [first_rule] error 2 > > make: *** [_dir_kernel] error 2 > > Then I could not proceed anymore. There could be a number of issues compiling the kernel. Were you able to compile the kernel before applying the patch. The safest route is to get a good working kernel from a non-patched kernel. Then, start applying patches. > > If anyone experienced the same kind of situation and got over it, please let > me know how it could be resolved. If you need to start over, you can save your configuration by keeping a copy of the .config file in your kernel source directory. > > Thank you! > > Katsuhiro Inoue > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Dan D. <dde...@co...> - 2001-01-13 18:13:08
|
Felix Tang wrote: > > All, > > Ok... I had no problems getting the linux1394 modules working and > detecting my SIIG card. Gscanbus can even tell when the Nikon D1 (anybody > else try using this?) is plugged in. It is common for people to use gscanbus to see if all of the nodes are being detected. However, sometimes cameras are not properly recognized, are given the ? icon, and the transport controls do not appear in the window when you click the icon. > > BUT, I don't have a clue as how to get dvgrab working. What would help me > understand how I should be trying to use dvgrab? > > Also, Kino doesn't compile on my Debian 2.2 system due to a complaint > about gnomeConf.sh missing. Would anybody have any hints on this? Hmm.. I'm running Helix GNOME with my Debian system by adding helixcode.com as an apt source. In that case, I had to apt-get install task-helix-gnome-dev. I'm not sure what a more vanilla system would require. > > I haven't really looked into it... but I just wanted to ask. Hopefully, a > little poking around will help me solve this. > > Lastly, as a sanity check... can I use the Nikon D1 as a video source? I'm > pretty sure that it can be used as such but I'd like to hear any comments. Is D1 referring to a model name? D1 is also a video standard that is different than DV, but I do not know much more. > > Thanks, > > Felix > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Felix T. <ta...@ee...> - 2001-01-13 18:12:13
|
OK... I see... I have that package installed but I'm using debian so I'll have to look into it again. Maybe, a source install straight from the gnome tar's will help. I assue that Arne is using an rpm based distro. For dvgrab, I understood the command line but I just have very little clue on how to debug and do sanity checks. The play button info is useful.. the Nikon D1 is a camera so I don't know what I can do about this. I think I'll test with one of theose little webcams... do you have to press play on those suckers? Can you? ;) Thanks, Felix On Fri, 12 Jan 2001, Perry Gilfillan wrote: > Felix, > > You'll get gnomeConf.sh when you install gnome-libs-devel. goto > http://rpmfind.net/linux/rpm2html/search.php?query=gnome-libs-devel > > The latest Kino_0.33 http://www.schirmacher.de/arne/kino/kino_0.33.tar.gz >^ has both capture and export functions now. Arne has incorporated dvgrab into kino. It captures NTSC and PAL, but I wasn't able to export to a Sony DCR-TRV310 (NTSC) Arne has PAL equip to test on, so we know it works in Europe. > > There is a little blurb on usage at the bottom of the README. The changes are on top, and I didn't scan to the end the first time I looked at it either. If you will do 'dvgrab --help' the options are pretty self explanitory. Start with './dvgrab --frames=10 filename' dvgrab does not do any thing to control the tape transport. ( it doesn't push <play> for you. > ) dvgrab will wait for the play button to be pushed. > > If you can push the play button on the Nikon D1, then you can use it as a video source. If you are recording Ink Blots, then yes, you can use it as a sanity check! > > Cherrio! > > Perry > > > > Felix Tang wrote: > > > All, > > > > Ok... I had no problems getting the linux1394 modules working and > > detecting my SIIG card. Gscanbus can even tell when the Nikon D1 (anybody > > else try using this?) is plugged in. > > > > BUT, I don't have a clue as how to get dvgrab working. What would help me > > understand how I should be trying to use dvgrab? > > > > Also, Kino doesn't compile on my Debian 2.2 system due to a complaint > > about gnomeConf.sh missing. Would anybody have any hints on this? > > > > I haven't really looked into it... but I just wanted to ask. Hopefully, a > > little poking around will help me solve this. > > > > Lastly, as a sanity check... can I use the Nikon D1 as a video source? I'm > > pretty sure that it can be used as such but I'd like to hear any comments. > > > > Thanks, > > > > Felix > > > > _______________________________________________ > > mailing list Lin...@li... > > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Perry G. <pe...@gi...> - 2001-01-13 03:51:57
|
Felix, You'll get gnomeConf.sh when you install gnome-libs-devel. goto http://rpmfind.net/linux/rpm2html/search.php?query=gnome-libs-devel The latest Kino_0.33 http://www.schirmacher.de/arne/kino/kino_0.33.tar.gz has both capture and export functions now. Arne has incorporated dvgrab into kino. It captures NTSC and PAL, but I wasn't able to export to a Sony DCR-TRV310 (NTSC) Arne has PAL equip to test on, so we know it works in Europe. There is a little blurb on usage at the bottom of the README. The changes are on top, and I didn't scan to the end the first time I looked at it either. If you will do 'dvgrab --help' the options are pretty self explanitory. Start with './dvgrab --frames=10 filename' dvgrab does not do any thing to control the tape transport. ( it doesn't push <play> for you. ) dvgrab will wait for the play button to be pushed. If you can push the play button on the Nikon D1, then you can use it as a video source. If you are recording Ink Blots, then yes, you can use it as a sanity check! Cherrio! Perry Felix Tang wrote: > All, > > Ok... I had no problems getting the linux1394 modules working and > detecting my SIIG card. Gscanbus can even tell when the Nikon D1 (anybody > else try using this?) is plugged in. > > BUT, I don't have a clue as how to get dvgrab working. What would help me > understand how I should be trying to use dvgrab? > > Also, Kino doesn't compile on my Debian 2.2 system due to a complaint > about gnomeConf.sh missing. Would anybody have any hints on this? > > I haven't really looked into it... but I just wanted to ask. Hopefully, a > little poking around will help me solve this. > > Lastly, as a sanity check... can I use the Nikon D1 as a video source? I'm > pretty sure that it can be used as such but I'd like to hear any comments. > > Thanks, > > Felix > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Felix T. <ta...@ee...> - 2001-01-13 00:16:51
|
All, Ok... I had no problems getting the linux1394 modules working and detecting my SIIG card. Gscanbus can even tell when the Nikon D1 (anybody else try using this?) is plugged in. BUT, I don't have a clue as how to get dvgrab working. What would help me understand how I should be trying to use dvgrab? Also, Kino doesn't compile on my Debian 2.2 system due to a complaint about gnomeConf.sh missing. Would anybody have any hints on this? I haven't really looked into it... but I just wanted to ask. Hopefully, a little poking around will help me solve this. Lastly, as a sanity check... can I use the Nikon D1 as a video source? I'm pretty sure that it can be used as such but I'd like to hear any comments. Thanks, Felix |
From: Katsuhiro I. <kat...@fl...> - 2001-01-12 21:08:04
|
Hello, I am using the kernel 2.2.16-22 and tried to patch ieee1394 to it (the latest version - 2.2.18-20001223), but during the process, the following error occured and could not install the modules. (Error messages are in Japanese therefore they may somewhat different than the exact English version messages) I did exactly in line with the instruction on linux1394.sourceforge.net/start_install.html except in the following situations. When pathcing: > can't find patch in line 259. the text leading up to this was: > diff -ruN linux-2.2.orig/arch/ppc/config.in linux-2.2/arch/ppc/config.in > --- linux-2.2.orig/arch/ppc/config.in Sat Dec23 03:54:38 2000 > --- linux-2.2/arch/ppc/config.in Sat Dec23 03:56:20 2000 I looked into the /usr/src directory and I found config.in under /usr/src/linux-2.2/arch/i386. Therefore I put that path in the prompt ("FIle to patch") then I could proceed. I executed xconfig and set the configuration and save & exit. When make dep: > /usr/src/linux-2.2/Rules.make:259 the target "irport.o" were given several times within the same rule. When make bzImage: > make[2]: *** [ksyms.o] error 1 > make[1]: *** [first_rule] error 2 > make: *** [_dir_kernel] error 2 Then I could not proceed anymore. If anyone experienced the same kind of situation and got over it, please let me know how it could be resolved. Thank you! Katsuhiro Inoue |
From: Perry G. <pe...@gi...> - 2001-01-12 04:16:39
|
Karthik, Jeff, Look at ieee1394_core.c:343, you will see a call to highlevel_host_reset(host); This function hasn't been implemented yet, so just cut or comment the line out. I made a tiny script, Pray, that does "sync; sleep 3; sync", so I always have a moment of silent meditation when loading unknown modules. Regards, Perry ======= What other people wrote about this subject on the ========== ======= lin...@li... list ========== Sebastien, just a quick note that I had the same result as you with 2.4.0. I commented out the call you refrence, and the pcilynx driver behaves pretty much the same as 2.2.18 with the CVS drivers. Still got troubles, but the machine doesn't die since you were quick to find the problem. Regards, Perry Sebastien Rougeaux wrote: > I think I found the problem. > > in ieee_core.c, there is a call to highlevel_host_reset(), which is > a function that is not defined. > > Andreas, why is there a call to such function ? Can you modify that > and see if it solves the problem with 2.4.0 kernel (seems to work > for me). > > Cheers, > > Sebastien Rougeaux Karthik Madathil wrote: > Summary of my setup: > kernel 2.4.0 on a Vaio F-250 Laptop, pcmcia-cs 3.1.23, OHCI compatible > PCMCIA 1394 adapter, 1394 drivers from kernel tree. > > No signs of trouble after boot in syslog and /proc/pci > > lsmod shows ohci1394_cb, ieee1394 and raw1394 loaded > > When I switch on my camcorder, an oops followed by a kernel panic > occurs. Same if the camcorder is on when I boot. > > I tried compiling the latest driver sources from CVS. They do not > compile > as they are, since a struct definition seems to have changed. I had to > edit guid.c and ohci1394.c to replace a couple of lines of the form > xxx->tq.next = NULL; > with > INIT_LIST_HEAD(xxx->tq.list); > I made the edits based on a diff of the kernel version with the > downloaded > version. > > With those changes, the drivers compile, but the panic still occurs, so > those changes in the kernel driver sources may be part of the problem. > > Can anyone suggest anything? > > (I've just joined the list and the archives only go till Dec 15, so I > don't > know if this has been discussed here before) > > Thanks, > Karthik > |
From: scott w. <swo...@ho...> - 2001-01-12 04:11:44
|
On Thu, Jan 11, 2001 at 08:55:31PM -0700, Jeff Lessem wrote: > I too am having the same problem with my camcorder and 2.4.0. The > problem also occured with 2.4.0-prerelease, if it makes any > difference. I am using a TI TSB12LV23 based OHCI Compliant card. > > If it would be helpful I can try to capture the oops and panic. This > will be difficult because the machine hangs, so I will have to attach > a serial console, etc. so I don't want to do this unless it will help > with debugging. > > In your message of: Thu, 11 Jan 2001 21:46:40 CST, you write: > >Summary of my setup: > >kernel 2.4.0 on a Vaio F-250 Laptop, pcmcia-cs 3.1.23, OHCI compatible > >PCMCIA 1394 adapter, 1394 drivers from kernel tree. > > > >No signs of trouble after boot in syslog and /proc/pci > > > >lsmod shows ohci1394_cb, ieee1394 and raw1394 loaded > > > > > >When I switch on my camcorder, an oops followed by a kernel panic > >occurs. Same if the camcorder is on when I boot. > > I have the same problem with a SIIG TI based 1394 card, Pyro WebCam and kernel 2.4.0. I have even tried Alan Cox's AC2 patch which has an update to ohci1394 with no luck. I haven't tried compiling the kernel with the Magic SysRequest option to try and recover from the OOP's. There a doc in linux/Documentation which talks about how to debug OOPs. Have you tried the 2.2.18 kernel + 1394 patch? That's what I am currently running and no OOPs. Modules load fine and it is able to talk to the device. Of course I don't have any software which works with the WebCam yet. good luck. scott worley swo...@ho... |
From: Jeff L. <Jeff.Lessem@Colorado.EDU> - 2001-01-12 03:55:08
|
I too am having the same problem with my camcorder and 2.4.0. The problem also occured with 2.4.0-prerelease, if it makes any difference. I am using a TI TSB12LV23 based OHCI Compliant card. If it would be helpful I can try to capture the oops and panic. This will be difficult because the machine hangs, so I will have to attach a serial console, etc. so I don't want to do this unless it will help with debugging. In your message of: Thu, 11 Jan 2001 21:46:40 CST, you write: >Summary of my setup: >kernel 2.4.0 on a Vaio F-250 Laptop, pcmcia-cs 3.1.23, OHCI compatible >PCMCIA 1394 adapter, 1394 drivers from kernel tree. > >No signs of trouble after boot in syslog and /proc/pci > >lsmod shows ohci1394_cb, ieee1394 and raw1394 loaded > > >When I switch on my camcorder, an oops followed by a kernel panic >occurs. Same if the camcorder is on when I boot. |
From: Karthik M. <kma...@ho...> - 2001-01-12 03:32:27
|
Summary of my setup: kernel 2.4.0 on a Vaio F-250 Laptop, pcmcia-cs 3.1.23, OHCI compatible PCMCIA 1394 adapter, 1394 drivers from kernel tree. No signs of trouble after boot in syslog and /proc/pci lsmod shows ohci1394_cb, ieee1394 and raw1394 loaded When I switch on my camcorder, an oops followed by a kernel panic occurs. Same if the camcorder is on when I boot. I tried compiling the latest driver sources from CVS. They do not compile as they are, since a struct definition seems to have changed. I had to edit guid.c and ohci1394.c to replace a couple of lines of the form xxx->tq.next = NULL; with INIT_LIST_HEAD(xxx->tq.list); I made the edits based on a diff of the kernel version with the downloaded version. With those changes, the drivers compile, but the panic still occurs, so those changes in the kernel driver sources may be part of the problem. Can anyone suggest anything? (I've just joined the list and the archives only go till Dec 15, so I don't know if this has been discussed here before) Thanks, Karthik |
From: Dan D. <dde...@co...> - 2001-01-10 21:40:00
|
Try Kino. It does capture and simple editing: http://www.schirmacher.de/arne/kino/ For more advanced editing load the AVIs from Kino into MainActor: http://www.mainconcept.com/ +-DRD-+ Guilherme Barile wrote: > > Anyone here experiences many crashes on Broadcast2000 when capturing from an > IEEE1394 device ? > I just can make it work on the default resolution (640x480) > I tried capturing video at 353x240, 29.97 fps (VCD) but it just leaves the > program and writes "Crash" on the terminal ... > Is there any other capturing/editing program for linux that supports firewire > or I will have to move do windows ? > > cheers > > gui > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/mailman/listinfo/linux1394-user |
From: Jonathan L. <jla...@pc...> - 2001-01-10 14:50:37
|
confirm 585461 _______________________________________________________ Are you a Techie? Get Your Free Tech Email Address Now! Many to choose from! Visit http://www.TechEmail.com |
From: Guilherme B. <gu...@in...> - 2001-01-09 01:33:35
|
Anyone here experiences many crashes on Broadcast2000 when capturing from an IEEE1394 device ? I just can make it work on the default resolution (640x480) I tried capturing video at 353x240, 29.97 fps (VCD) but it just leaves the program and writes "Crash" on the terminal ... Is there any other capturing/editing program for linux that supports firewire or I will have to move do windows ? cheers gui |
From: Dan D. <dde...@co...> - 2001-01-05 14:27:01
|
I have been using exclusively the SIIG 1394 boards because they are basically they same as the Pyro (typical TI-based design), but it's always a few dollars cheaper. They are quite inexpensive at buy.com ($48); however, I just checked their site again and the Pyro Basic DV is only $43 and in stock Arne is in germany, and surely uses one that's more popular and available to his market. These ADS and SIIG boards are "big enough name." It's the chipset and manufacturing process that matters, but both of these as well as many others use the venerable TI chips. +-DRD-+ ----- Original Message ----- From: "Felix Tang" <ta...@ee...> To: <lin...@li...> Sent: Thursday, January 04, 2001 5:50 PM Subject: Which ieee1394 boards do people actually own (intended for wearable computing application)? > I'm interested in getting a ieee1394 board and interfacing to some dv > cameras for wearable computing. What I want to know is which boards > people actually own and develop with? > > I have looked at the archives and pcilynx and ohci are both mentioned. It > seems that depending on what camp you're in, you can go with either. I'm > guessing that OHCI seems to be a bit more popular according to some > e-mails I read (i.e. windows 98 support). > > The pyro card from ADS was mentioned and given a relatively popular > review. However, I'd like to hear of any cards that people have used that > are a bit smaller and consume less power (without going pcmcia). Although, > not a strict reqiurement... I'd rather have a big card that's better > supported. ;) > > What card does Arne Schirmacher use to develop with (I use him as an > example due to the fact that he wrote the application I'm interested in)? > > Thanks, > > Felix > > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > |
From: Harald W. <la...@gn...> - 2001-01-05 11:36:20
|
Hi! I've made some RedHat 7.0 RPM packages of libraw1394. They are available from http://www.gnumonks.org/ftp/pub/rpms/redhat-7.0/RPMS/i386/libraw1394-0.8.1-1.i386.rpm http://www.gnumonks.org/ftp/pub/rpms/redhat-7.0/RPMS/i386/libraw1394-devel-0.8.1-1.i386.rpm http://www.gnumonks.org/ftp/pub/rpms/redhat-7.0/SRPMS/libraw1394-0.8.1-1.src.rpm or via ftp: ftp://ftp.gnumonks.org/pub/rpms/redhat-7.0/RPMS/i386/libraw1394-devel-0.8.1-1.i386.rpm` ftp://ftp.gnumonks.org/pub/rpms/redhat-7.0/RPMS/i386/libraw1394-0.8.1-1.i386.rpm ftp://ftp.gnumonks.org/pub/rpms/redhat-7.0/SRPMS/libraw1394-0.8.1-1.src.rpm Feel free to link them to the linux1394 homepage or add them to the linux1394 sourceforge repository. -- Live long and prosper - Harald Welte / la...@gn... http://www.gnumonks.org ============================================================================ GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M- V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*) |
From: Felix T. <ta...@ee...> - 2001-01-04 22:50:39
|
I'm interested in getting a ieee1394 board and interfacing to some dv cameras for wearable computing. What I want to know is which boards people actually own and develop with? I have looked at the archives and pcilynx and ohci are both mentioned. It seems that depending on what camp you're in, you can go with either. I'm guessing that OHCI seems to be a bit more popular according to some e-mails I read (i.e. windows 98 support). The pyro card from ADS was mentioned and given a relatively popular review. However, I'd like to hear of any cards that people have used that are a bit smaller and consume less power (without going pcmcia). Although, not a strict reqiurement... I'd rather have a big card that's better supported. ;) What card does Arne Schirmacher use to develop with (I use him as an example due to the fact that he wrote the application I'm interested in)? Thanks, Felix |
From: Guilherme B. <gu...@in...> - 2001-01-04 00:15:11
|
Ok Just compiled linux 2.2.18 with the 1394 patch. Camera is working fine now, dvgrab, capture and broadcast ... Only if broadcast crashed less :( Thanks for all of you gui |
From: <gal...@ma...> - 2001-01-03 22:47:43
|
The Newer Firewire 2 Go for the Mac is Lynx, the other one is OHCI. Will > -----Original Message----- > From: lin...@li... > [mailto:lin...@li...]On Behalf Of Richard > Akerman > Sent: Wednesday, January 03, 2001 2:28 PM > To: matt newcomb > Cc: lin...@li... > Subject: Re: PCMCIA firewire? > > > I thought the Newer Firewire 2 Go was a PCI-Lynx card, not OHCI. > > matt newcomb wrote: > > > > G'day, > > > > I've got a newer technolgies firewire 2 go pcmcia card (ohci based). > > It's on the list of supported cards from the pcmcia-cs folks, but with > > release 3.1.23 of the pcmcia package it does not appear to be > recognized. > > cardctl ident returns "no information" for that card. > > > > I'm wondering has anyone had success with a pcmcia firewire > card and if so > > what card, kernel, and pcmcia release are you using? > > > > Matt Newcomb > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/mailman/listinfo/linux1394-user |
From: Richard A. <rak...@hf...> - 2001-01-03 22:27:45
|
I thought the Newer Firewire 2 Go was a PCI-Lynx card, not OHCI. matt newcomb wrote: > > G'day, > > I've got a newer technolgies firewire 2 go pcmcia card (ohci based). > It's on the list of supported cards from the pcmcia-cs folks, but with > release 3.1.23 of the pcmcia package it does not appear to be recognized. > cardctl ident returns "no information" for that card. > > I'm wondering has anyone had success with a pcmcia firewire card and if so > what card, kernel, and pcmcia release are you using? > > Matt Newcomb |
From: Dan D. <dde...@co...> - 2001-01-03 14:06:29
|
You are correct that your messages log is not telling anything. Gscanbus definitely has problems with certain cameras, mine included. However, you continue to speak in generic terms when you say broadcast and capture. Are you simply pressing play and record on the camera? Part of your paragraph below does lead me to believe that you are using the Broadcast 2000 software program; is that correct? Broadcast is much more troublesome than dvgrab, so I suggest using something very simple like dvgrab before attempting to use something more sophisticated like Broadcast. In either case, there was a bug a while back (around September and October timeframe) in the ohci driver that caused Linux crashes when stopping capture regardless of the program. However, since you say you updated with the latest CVS, I am at a loss to explain why this could occur. +-DRD-+ ----- Original Message ----- From: "Guilherme Barile" <gu...@in...> To: <lin...@li...> Sent: Tuesday, January 02, 2001 5:13 PM Subject: Re: Pinnacle studio DV + SONY DCRTRV520 hanging ? > gscanbus shows the camera as "unknown"... i guess it looks like an > incompatibility problem with the camera. > when I start capture (or broadcast) it starts capturing - i can see video and > hear sound from the camera, but when I stop capturing (pressing stop on > broadcast or when capture finishes capturing, or even when I close capture's > window) linux crashes - one curious thing - if I unplug the camera before > closing any of these programs, linux doesn't crash. > > Some output of /var/log/messages (when it crashes it doesn't output anything, > just @^@^@^@^@^@^@^@^@^@^@^...) > > Jan 2 20:09:15 principia kernel: ohci1394_0: Bus reset > Jan 2 20:09:15 principia kernel: ohci1394_0: Got phy packet ctx=0 ... > discarded > Jan 2 20:09:15 principia kernel: ohci1394_0: SelfID process finished (phyid > 1, root) > Jan 2 20:09:15 principia kernel: ohci1394_0: selfid packet 0x807f0882 rcvd > Jan 2 20:09:15 principia kernel: ohci1394_0: selfid packet 0x817f8c74 rcvd > Jan 2 20:09:15 principia kernel: ohci1394_0: This node self-id is 0x817f8c74 > Jan 2 20:09:15 principia kernel: ohci1394_0: calling self-id complete > Jan 2 20:09:15 principia kernel: ieee1394: GUID request sent to node 0 > Jan 2 20:10:12 principia kernel: ohci1394_0: Bus reset > Jan 2 20:10:12 principia kernel: ohci1394_0: Got phy packet ctx=0 ... > discarded > Jan 2 20:10:12 principia kernel: ohci1394_0: SelfID process finished (phyid > 0, root) > Jan 2 20:10:12 principia kernel: ohci1394_0: selfid packet 0x807f8c56 rcvd > Jan 2 20:10:12 principia kernel: ohci1394_0: This node self-id is 0x807f8c56 > Jan 2 20:10:12 principia kernel: ohci1394_0: calling self-id complete > > I just cannot figure out what's happening. > > gui > > > What are you using to capture, not gscanbus, right? If you can see and > > hear things while capturing you must be using Broadcast 2000 or Kino > > 0.3. What happens when you using dvgrab? Also, you should immediately > > inspect the tail of /var/log/messages after a crash; it might be saying > > something. Please post the trailing messages for us to see. Your card is > > compatible and appears to be working good. > > +-DRD-+gscanbus shows the camera as "unknown"... i guess it looks like an > incompatibility problem with the camera. > when I start capture (or broadcast) it starts capturing - i can see video and > hear sound from the camera, but when I stop capturing (pressing stop on > broadcast or when capture finishes capturing, or even when I close capture's > window) linux crashes - one curious thing - if I unplug the camera before > closing any of these programs, linux doesn't crash. > > Some output of /var/log/messages (when it crashes it doesn't output anything, > just @^@^@^@^@^@^@^@^@^@^@^...) > > Jan 2 20:09:15 principia kernel: ohci1394_0: Bus reset > Jan 2 20:09:15 principia kernel: ohci1394_0: Got phy packet ctx=0 ... > discarded > Jan 2 20:09:15 principia kernel: ohci1394_0: SelfID process finished (phyid > 1, root) > Jan 2 20:09:15 principia kernel: ohci1394_0: selfid packet 0x807f0882 rcvd > Jan 2 20:09:15 principia kernel: ohci1394_0: selfid packet 0x817f8c74 rcvd > Jan 2 20:09:15 principia kernel: ohci1394_0: This node self-id is 0x817f8c74 > Jan 2 20:09:15 principia kernel: ohci1394_0: calling self-id complete > Jan 2 20:09:15 principia kernel: ieee1394: GUID request sent to node 0 > Jan 2 20:10:12 principia kernel: ohci1394_0: Bus reset > Jan 2 20:10:12 principia kernel: ohci1394_0: Got phy packet ctx=0 ... > discarded > Jan 2 20:10:12 principia kernel: ohci1394_0: SelfID process finished (phyid > 0, root) > Jan 2 20:10:12 principia kernel: ohci1394_0: selfid packet 0x807f8c56 rcvd > Jan 2 20:10:12 principia kernel: ohci1394_0: This node self-id is 0x807f8c56 > Jan 2 20:10:12 principia kernel: ohci1394_0: calling self-id complete > > I just cannot figure out what's happening. > > gui > > > What are you using to capture, not gscanbus, right? If you can see and > > hear things while capturing you must be using Broadcast 2000 or Kino > > 0.3. What happens when you using dvgrab? Also, you should immediately > > inspect the tail of /var/log/messages after a crash; it might be saying > > something. Please post the trailing messages for us to see. Your card is > > compatible and appears to be working good. > > +-DRD-+ > > > > Guilherme Barile wrote: > > > Hello > > > I just bought a pinnacle studio dv board (OHCI compliant), > > > installed it on my computer, but everytime I stop capturing video, linux > > > hangs. > > > I'm using the lastest (CVS) linux1394 source with kernel 2.2.17, > > > I must say that gscanbus shows the camera/1394 board and I can see video > > > and hear audio when I start "capture" .... but when I close it linux > > > hangs ... > > > I also tried capturing without seeing the video (just to > > > guarantee that it wasn't a display problem) but after the capture > > > finished, linux hanged again. I even compiled kernel 2.4.0 test 12, but i > > > couldn't even see the video on screen, so I switched back to 2.2.17. > > > > > > Is this a bug/incompatibility with my board and/or camera ? > > > > > > Thank you for anyone that can answer. > > > > > > gui > > > > > > _______________________________________________ > > > mailing list Lin...@li... > > > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > > > > _______________________________________________ > > mailing list Lin...@li... > > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > > > > Guilherme Barile wrote: > > > Hello > > > I just bought a pinnacle studio dv board (OHCI compliant), > > > installed it on my computer, but everytime I stop capturing video, linux > > > hangs. > > > I'm using the lastest (CVS) linux1394 source with kernel 2.2.17, > > > I must say that gscanbus shows the camera/1394 board and I can see video > > > and hear audio when I start "capture" .... but when I close it linux > > > hangs ... > > > I also tried capturing without seeing the video (just to > > > guarantee that it wasn't a display problem) but after the capture > > > finished, linux hanged again. I even compiled kernel 2.4.0 test 12, but i > > > couldn't even see the video on screen, so I switched back to 2.2.17. > > > > > > Is this a bug/incompatibility with my board and/or camera ? > > > > > > Thank you for anyone that can answer. > > > > > > gui > > > > > > _______________________________________________ > > > mailing list Lin...@li... > > > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > > > > _______________________________________________ > > mailing list Lin...@li... > > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > |
From: Guilherme B. <gu...@in...> - 2001-01-02 22:21:18
|
gscanbus shows the camera as "unknown"... i guess it looks like an incompatibility problem with the camera. when I start capture (or broadcast) it starts capturing - i can see video and hear sound from the camera, but when I stop capturing (pressing stop on broadcast or when capture finishes capturing, or even when I close capture's window) linux crashes - one curious thing - if I unplug the camera before closing any of these programs, linux doesn't crash. Some output of /var/log/messages (when it crashes it doesn't output anything, just @^@^@^@^@^@^@^@^@^@^@^...) Jan 2 20:09:15 principia kernel: ohci1394_0: Bus reset Jan 2 20:09:15 principia kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Jan 2 20:09:15 principia kernel: ohci1394_0: SelfID process finished (phyid 1, root) Jan 2 20:09:15 principia kernel: ohci1394_0: selfid packet 0x807f0882 rcvd Jan 2 20:09:15 principia kernel: ohci1394_0: selfid packet 0x817f8c74 rcvd Jan 2 20:09:15 principia kernel: ohci1394_0: This node self-id is 0x817f8c74 Jan 2 20:09:15 principia kernel: ohci1394_0: calling self-id complete Jan 2 20:09:15 principia kernel: ieee1394: GUID request sent to node 0 Jan 2 20:10:12 principia kernel: ohci1394_0: Bus reset Jan 2 20:10:12 principia kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Jan 2 20:10:12 principia kernel: ohci1394_0: SelfID process finished (phyid 0, root) Jan 2 20:10:12 principia kernel: ohci1394_0: selfid packet 0x807f8c56 rcvd Jan 2 20:10:12 principia kernel: ohci1394_0: This node self-id is 0x807f8c56 Jan 2 20:10:12 principia kernel: ohci1394_0: calling self-id complete I just cannot figure out what's happening. gui > What are you using to capture, not gscanbus, right? If you can see and > hear things while capturing you must be using Broadcast 2000 or Kino > 0.3. What happens when you using dvgrab? Also, you should immediately > inspect the tail of /var/log/messages after a crash; it might be saying > something. Please post the trailing messages for us to see. Your card is > compatible and appears to be working good. > +-DRD-+gscanbus shows the camera as "unknown"... i guess it looks like an incompatibility problem with the camera. when I start capture (or broadcast) it starts capturing - i can see video and hear sound from the camera, but when I stop capturing (pressing stop on broadcast or when capture finishes capturing, or even when I close capture's window) linux crashes - one curious thing - if I unplug the camera before closing any of these programs, linux doesn't crash. Some output of /var/log/messages (when it crashes it doesn't output anything, just @^@^@^@^@^@^@^@^@^@^@^...) Jan 2 20:09:15 principia kernel: ohci1394_0: Bus reset Jan 2 20:09:15 principia kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Jan 2 20:09:15 principia kernel: ohci1394_0: SelfID process finished (phyid 1, root) Jan 2 20:09:15 principia kernel: ohci1394_0: selfid packet 0x807f0882 rcvd Jan 2 20:09:15 principia kernel: ohci1394_0: selfid packet 0x817f8c74 rcvd Jan 2 20:09:15 principia kernel: ohci1394_0: This node self-id is 0x817f8c74 Jan 2 20:09:15 principia kernel: ohci1394_0: calling self-id complete Jan 2 20:09:15 principia kernel: ieee1394: GUID request sent to node 0 Jan 2 20:10:12 principia kernel: ohci1394_0: Bus reset Jan 2 20:10:12 principia kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Jan 2 20:10:12 principia kernel: ohci1394_0: SelfID process finished (phyid 0, root) Jan 2 20:10:12 principia kernel: ohci1394_0: selfid packet 0x807f8c56 rcvd Jan 2 20:10:12 principia kernel: ohci1394_0: This node self-id is 0x807f8c56 Jan 2 20:10:12 principia kernel: ohci1394_0: calling self-id complete I just cannot figure out what's happening. gui > What are you using to capture, not gscanbus, right? If you can see and > hear things while capturing you must be using Broadcast 2000 or Kino > 0.3. What happens when you using dvgrab? Also, you should immediately > inspect the tail of /var/log/messages after a crash; it might be saying > something. Please post the trailing messages for us to see. Your card is > compatible and appears to be working good. > +-DRD-+ > > Guilherme Barile wrote: > > Hello > > I just bought a pinnacle studio dv board (OHCI compliant), > > installed it on my computer, but everytime I stop capturing video, linux > > hangs. > > I'm using the lastest (CVS) linux1394 source with kernel 2.2.17, > > I must say that gscanbus shows the camera/1394 board and I can see video > > and hear audio when I start "capture" .... but when I close it linux > > hangs ... > > I also tried capturing without seeing the video (just to > > guarantee that it wasn't a display problem) but after the capture > > finished, linux hanged again. I even compiled kernel 2.4.0 test 12, but i > > couldn't even see the video on screen, so I switched back to 2.2.17. > > > > Is this a bug/incompatibility with my board and/or camera ? > > > > Thank you for anyone that can answer. > > > > gui > > > > _______________________________________________ > > mailing list Lin...@li... > > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > > Guilherme Barile wrote: > > Hello > > I just bought a pinnacle studio dv board (OHCI compliant), > > installed it on my computer, but everytime I stop capturing video, linux > > hangs. > > I'm using the lastest (CVS) linux1394 source with kernel 2.2.17, > > I must say that gscanbus shows the camera/1394 board and I can see video > > and hear audio when I start "capture" .... but when I close it linux > > hangs ... > > I also tried capturing without seeing the video (just to > > guarantee that it wasn't a display problem) but after the capture > > finished, linux hanged again. I even compiled kernel 2.4.0 test 12, but i > > couldn't even see the video on screen, so I switched back to 2.2.17. > > > > Is this a bug/incompatibility with my board and/or camera ? > > > > Thank you for anyone that can answer. > > > > gui > > > > _______________________________________________ > > mailing list Lin...@li... > > http://lists.sourceforge.net/mailman/listinfo/linux1394-user > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/mailman/listinfo/linux1394-user |