linux1394-user Mailing List for IEEE 1394 for Linux (Page 421)
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: Andreas B. <and...@mu...> - 2001-01-02 21:15:05
|
On Tue, Jan 02, 2001 at 03:33:26PM +0100, Michiel Ronsse wrote: > > > Hi all, > > We recently bought a motionIO OHCI-104 FireWire card (PC/104-plus) we > are using with an SBC-MediaGX motherboard. The card and the motherboard > are working fine, but the FireWire card doesn't recognize an attached > Sony > DFW-VL500 digital video camera. > Attached you find a log file with the output > of 'dmesg', /proc/ohci1394 and 'testlibraw'. As you'll notice, the > FireWire > board is detected, but not the attached camera. The OHCI card is stuck in bus reset, since it doesn't seem to get any interrupts. That's where you'd have to look. Standard suggestion: if you have an AWARD BIOS, look for the option "PnP OS installed" and set it to No. If you have a different BIOS, look for a similar option and do the same. -- Andreas E. Bombe <and...@mu...> DSA key 0x04880A44 http://home.pages.de/~andreas.bombe/ http://linux1394.sourceforge.net/ |
From: Michiel R. <Mic...@ru...> - 2001-01-02 14:33:38
|
Hi all, We recently bought a motionIO OHCI-104 FireWire card (PC/104-plus) we are using with an SBC-MediaGX motherboard. The card and the motherboard are working fine, but the FireWire card doesn't recognize an attached Sony DFW-VL500 digital video camera. Attached you find a log file with the output of 'dmesg', /proc/ohci1394 and 'testlibraw'. As you'll notice, the FireWire board is detected, but not the attached camera. Any ideas on how to solve this? We are using kernel 2.4.0-test7 with the latest ieee1394 kernal patches and libraw1394-0.8.1 and libdc1394. Thanks in advance, Michiel Ronsse. +-- Michiel Ronsse ------- mi...@ro... --+ | Parallel Information Systems Group | | ELIS - Ghent University - Ghent, Belgium | | Phone: +32/9/264.33.67 Fax: +32/9/264.35.94 | +-------- http://www.michiel.ronsse.com --------+ In a train station the train stops, in a work station ... |
From: Damien D. <ddo...@te...> - 2001-01-02 08:40:35
|
Hi, I have taht card and it works fine under linux. Damien > samuel wrote: > > hello all, > Im considering an SIIG 1391 firewire pci card: > > 1) Chipset: TI 1394 PHY & LINK chips > > 2) Regulatory approval(s): FCC Class B (DoC)-NN2601 & CE > > 3) Port type: 3 IEEE 1394 ports > > 4) OS supported: Windows 98 Gold, Windows 98 Second Edition, Windows > 2000, Windows ME > > 5) IEEE 1394-1995, P1394a (rev.1.1) and OHCI Interface Specification > 1.0 compliant > > I think probably this might work, but has anyone had any experience > with it? > > thx for any feedback (seasons greetings), > samuel -- Damien Douxchamps URL : http://www.tele.ucl.ac.be/MEMBERS/Douxchamps_Damien_e.html |
From: Dan D. <dde...@co...> - 2001-01-02 05:17:35
|
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 |
From: samuel <sa...@nt...> - 2000-12-31 14:29:54
|
hello all, Im considering an SIIG 1391 firewire pci card: 1) Chipset: TI 1394 PHY & LINK chips=20 2) Regulatory approval(s): FCC Class B (DoC)-NN2601 & CE=20 3) Port type: 3 IEEE 1394 ports=20 4) OS supported: Windows 98 Gold, Windows 98 Second Edition, Windows = 2000, Windows ME=20 5) IEEE 1394-1995, P1394a (rev.1.1) and OHCI Interface Specification 1.0 = compliant=20 I think probably this might work, but has anyone had any experience with = it? thx for any feedback (seasons greetings), samuel |
From: Guilherme B. <gu...@in...> - 2000-12-31 02:02:05
|
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 |
From: Miha S. <mih...@so...> - 2000-12-29 21:49:42
|
I'm on the same page in life (buying a good 1394 card ;-)) We could compare notes. I've found cheap cards (WesternDigital has one with NEC chipset) that are 1394A compliant, but lack power to the 1394 bus. (For camcorder only its not realy needed, but Orange Micro 1394 camera needs power.) Computers on their own do not have a way to supply adequate power to the bus (40V 1.5A), but you can get 12V 1.5A if the card has additional power supply connector. Otherwise the card gets the power from PCI bus and this does not power the bus. One thing is true. Most cards are OHCI compliant, but do check before you buy. For the video editing software I can get back to you with some links, but if you search 1394 on WWW.SOURCEFORGE.NET you will get a lot of interesting links. Pete Toscano wrote: > Moin Andreas! > > Andreas Micklei schrieb am Donnerstag, den 28. Dezember 2000: > > > On Wed, Dec 27, 2000 at 01:18:48PM -0500, Pete Toscano wrote: > [snip] > > One problem you will encounter is, that there are not much useful applications > > for using a DV camcorder with Linux yet. So you should check if these > > applications suit your needs before buying a camcorder. Preferably you could > > contribute code. :-) > > i've heard of broadcast 2000. how's this? worse comes to worse, we'll > do what we need on my wife's windows box, but i'd really rather do it > with linux (or one of the bsds, actually). > > > > i see from the list and other docs that there is some support for pci > > > ieee 1394 cards, but i'm looking for a list of "known good" cards. > > > listing the working chipsets is nice, but afaik, vendors don't usually > > > list what chips they use. is there any known list like this? > > > > Somebody is working on that IMHO. What card do you intend to buy? Most cards > > are OHCI compliant these days and should generally work anyway. > > excellent. i didn't have any specific one in mind yet. the most > important aspect is "plays well with linux" so i was hoping to find one > or a few highly recommended ones and then i'd chose from there. > > since you say most are ohci compliant, is there maybe a black list of > cards that i should avoid? or do most of the ohci compliant cards > usually say on the box? > > thanks, > pete > > ------------------------------------------------------------------------ > Part 1.2Type: application/pgp-signature |
From: Pete T. <pe...@to...> - 2000-12-29 05:57:26
|
Moin Andreas! Andreas Micklei schrieb am Donnerstag, den 28. Dezember 2000: > And there is more to come. Have you tried Arne Schirmacher's link page? > http://www.schirmacher.de/cgi-bin/dclinks.cgi?action=3Dview_category&cate= gory=3DLinux+Software no, i hadn't yet. thanks. it looks interesting. > > excellent. i didn't have any specific one in mind yet. the most > > important aspect is "plays well with linux" so i was hoping to find one > > or a few highly recommended ones and then i'd chose from there. >=20 > You should find some positives in the mailing list archives. I use a > Unibrain card, but that is probably not what you want because it is > expensive, and as said before any other OHCI card should also do the > job. hmmm, what about the ads pyro basicdv card? i read in the archives somewhere that the ads pryro cards (http://www.adstech.com/products/pyro_basicdv_more.html) are ohci complient. anyone play with these puppies yet? they also have a cardbus version (http://www.adstech.com/products/pyrocardbus_more.html). anyone play with these? sorry to be such a pest, but i've been bitten with linux hardware incompatibilities before. thanks, pete |
From: Mark <to...@de...> - 2000-12-29 05:41:01
|
I have tried both Mainactor and Broadcast 2000. Broadcast 2000 will let you download video from a firewire card, but does not seem to let me import DV avi's. Mainactor, the program i use, is amazing. It has every feature i need. There is one problem, and that is with bugs. There is also a version for windows, which doesnt have bugs. I think a new release of mainactor will be out soon for linux, the new windows version is out. I have not yet been able to use dvgrab with my card. There are no errors, but both mainactor and broadcast refuse to recognize or load the file properly, so im stuck downloading dv in windows, then rebooting. just some info- mark to...@de... |
From: Andreas M. <and...@iv...> - 2000-12-29 03:04:59
|
On Wed, Dec 27, 2000 at 01:18:48PM -0500, Pete Toscano wrote: > i'm thinking of getting a sony dcr-trv20. i'd like to use it with my > linux pc and my linux laptop. i've heard that sometimes sony plays > dirty with standards and i'm concerned about being able to use it with > linux. anybody have any experiences with this? I have tried Sony camcorders and a Sony DV recorder and they obviously implement all relevant standards correctly. Same is true for the Panasonic devices I have tried so far. The situation seems to be far better than with other so called standards. This is what I like most about 1394. The specifications leave very little room for different interpretations and the vendors really implement them correctly. One problem you will encounter is, that there are not much useful applications for using a DV camcorder with Linux yet. So you should check if these applications suit your needs before buying a camcorder. Preferably you could contribute code. :-) > i see from the list and other docs that there is some support for pci > ieee 1394 cards, but i'm looking for a list of "known good" cards. > listing the working chipsets is nice, but afaik, vendors don't usually > list what chips they use. is there any known list like this? Somebody is working on that IMHO. What card do you intend to buy? Most cards are OHCI compliant these days and should generally work anyway. > finally, from the list of "known good" pcmcia cards, i get the feeling > that there are no 1394 cards for x86 laptops. is this true? if not, > what do you suggest? Someone else should comment on this one. There is support for PCMCI in the drivers so someone should be able to list a working configuration. -- Andreas Micklei IVISTAR Kommunikationssysteme AG Ehrenbergstr. 19 / 10245 Berlin http://www.ivistar.de |
From: Pete T. <pe...@to...> - 2000-12-29 03:04:20
|
Moin Andreas! Andreas Micklei schrieb am Donnerstag, den 28. Dezember 2000: > On Wed, Dec 27, 2000 at 01:18:48PM -0500, Pete Toscano wrote: [snip] > One problem you will encounter is, that there are not much useful applica= tions > for using a DV camcorder with Linux yet. So you should check if these > applications suit your needs before buying a camcorder. Preferably you co= uld > contribute code. :-) i've heard of broadcast 2000. how's this? worse comes to worse, we'll do what we need on my wife's windows box, but i'd really rather do it with linux (or one of the bsds, actually). > > i see from the list and other docs that there is some support for pci > > ieee 1394 cards, but i'm looking for a list of "known good" cards. > > listing the working chipsets is nice, but afaik, vendors don't usually > > list what chips they use. is there any known list like this? >=20 > Somebody is working on that IMHO. What card do you intend to buy? Most ca= rds > are OHCI compliant these days and should generally work anyway. excellent. i didn't have any specific one in mind yet. the most important aspect is "plays well with linux" so i was hoping to find one or a few highly recommended ones and then i'd chose from there. since you say most are ohci compliant, is there maybe a black list of cards that i should avoid? or do most of the ohci compliant cards usually say on the box? thanks, pete |
From: Nabil S. <ns...@sa...> - 2000-12-28 22:55:53
|
Andreas Micklei wrote: > > On Thu, Dec 28, 2000 at 09:35:57AM -0500, Pete Toscano wrote: > > i've heard of broadcast 2000. how's this? worse comes to worse, we'll > > I have not really used this yet. But seems to somehow do the job. I tried it and it suxx. It crashes constantly and the GUI is unsuitable. I hate proprietary software, but at the moment there doesnt seem to be an alternative to MainActor. Nevertheless dvgrab is doing a good job for the capturing part (I love the feature to capture each scene separately). -- Nabil Sayegh GPG-Key available at http://www.sayegh.de (see http://www.gnupg.org for details) |
From: Andreas M. <and...@iv...> - 2000-12-28 22:39:24
|
On Thu, Dec 28, 2000 at 09:35:57AM -0500, Pete Toscano wrote: > i've heard of broadcast 2000. how's this? worse comes to worse, we'll I have not really used this yet. But seems to somehow do the job. There is also a propreritary product called MainActor which should support 1394 soon (or does it already? The website is somehow unclear). The demo version I tried a year ago looked very promising (and of course the Amiga version is a classic. ;-))) And there is more to come. Have you tried Arne Schirmacher's link page? http://www.schirmacher.de/cgi-bin/dclinks.cgi?action=view_category&category=Linux+Software > do what we need on my wife's windows box, but i'd really rather do it > with linux (or one of the bsds, actually). You could also use Linux for grabbing DV streams from your camcorder and use windows for doing the editing. Btw.: You can't use Linux for putting your video back on DV tape via 1394 yet. So far you can only use it for the import of video data. But this should also change really soon now. > excellent. i didn't have any specific one in mind yet. the most > important aspect is "plays well with linux" so i was hoping to find one > or a few highly recommended ones and then i'd chose from there. You should find some positives in the mailing list archives. I use a Unibrain card, but that is probably not what you want because it is expensive, and as said before any other OHCI card should also do the job. > since you say most are ohci compliant, is there maybe a black list of > cards that i should avoid? or do most of the ohci compliant cards > usually say on the box? I don't know what most boxes look like. The easiest thing for you would be to look at thoses boxes and than ask on this list if anybody is using one of these cards. However if a box states OHCI, the chances are quite good that the card works. The only OHCI controllers that I am aware of that make trouble are the ones that are built into certains MACs and into certain Sony VAIO notebooks. The safest thing would probably be a card which uses the Texas Instruments OHCI chipset. If they print this on the box you can probably buy it. bye... Andreas Micklei -- Andreas Micklei IVISTAR Kommunikationssysteme AG Ehrenbergstr. 19 / 10245 Berlin http://www.ivistar.de |
From: Andreas B. <and...@mu...> - 2000-12-28 00:31:28
|
I put up a new patch for the 2.2 series' 2.2.18 kernel. It applies cleanly unlike the 2.2.17 patch and it fixes the issues with redefines caused by some of 2.4's macros and functions being backported (these are now simply not defined if version is detected as at least 2.2.18). (In fact the patch was available for some days now already.) This patch includes all recent changes and contains the current code in CVS. http://download.sourceforge.net/linux1394/ieee1394-2.2.18-20001223.gz or ftp://download.sourceforge.net/pub/sourceforge/linux1394/ieee1394-2.2.18-20001223.gz -- Andreas E. Bombe <and...@mu...> DSA key 0x04880A44 http://home.pages.de/~andreas.bombe/ http://linux1394.sourceforge.net/ |
From: Pete T. <pe...@to...> - 2000-12-27 18:18:45
|
i'm thinking of getting a sony dcr-trv20. i'd like to use it with my linux pc and my linux laptop. i've heard that sometimes sony plays dirty with standards and i'm concerned about being able to use it with linux. anybody have any experiences with this? i see from the list and other docs that there is some support for pci ieee 1394 cards, but i'm looking for a list of "known good" cards. listing the working chipsets is nice, but afaik, vendors don't usually list what chips they use. is there any known list like this? finally, from the list of "known good" pcmcia cards, i get the feeling that there are no 1394 cards for x86 laptops. is this true? if not, what do you suggest? support for the laptop would be good, but isn't really necessary (or practical probably). support for my pc would be a show stopper. thanks, pete |
From: matt n. <sp...@co...> - 2000-12-25 15:43:33
|
G'day, Are there a set of patches to bring 2.3.99-pre9 up to the latest ieee1394 code? I've tried the exact instructions ( for cvs ) on the linux1394.sourceforge.net page several times, but that mangles my kernel source leaving it unable to compile. I would try the 2.4.0-test series but unfortunetly with the most vanilla of options fail to boot on my dell inspiron 3700. Matt |
From: Miha S. <mih...@so...> - 2000-12-23 18:33:08
|
Can anyone confirm that any of these cards work under Linux: PROCOMP SpeedDeamon 400E or PROCOMP SpeedDeamon 400P or Western Digital Firewire Adapter. I'm looking for a Linux 1394 solution and these are the only cards that I know of that are sold in Slovenia(sorry to hear) |
From: Damien D. <ddo...@te...> - 2000-12-22 09:16:55
|
Hello, I have a Ratoc cardbus card working without major problems. I used a patch for this (see the archives of the mailing list), but I think the only 3 things you need to do are: 1) add these two paragraphs in the /etc/pcmcia/config file: device "ohci1394" class "ieee1394" module "cb_enabler", "ohci1394", "raw1394", "video1394" and something like: (depends on your card, see the .log files) card "RATOC IEEE-1394 OHCI CardBus Adapter CBFW2" version "RATOC Systems,Inc.", "IEEE1394 OHCI CBFW2" bind "ohci1394" 2) Also, in your /etc/modules.conf, add the following lines: alias char-major-171 raw1394 alias char-major-172 video1394 3) At last, add links to your modules in the /lib/modules/[kernel_version]/pcmcia directory. Good luck, Damien 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 -- Damien Douxchamps URL : http://www.tele.ucl.ac.be/MEMBERS/Douxchamps_Damien_e.html |
From: Andreas T. <to...@po...> - 2000-12-22 08:35:06
|
Hi, 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? I have 'some'experience with pcmcia-cs and firewire. I use a 'Cherri' FW card with this pci id's: pci 0x104c, 0x8019, (man-id, card-id). I bring it at least to the recognition. But not further, don't know why. Really. My platform is a Wallstreet Powerbook, kernel is plain 2.2.18 with ieee1394 patches (latest from cvs) and some mac specific things. I can insert/eject the card with cardinfo/cardctl with no problem. But I have a self-id receiving problem. Maybe it is endian related? Is your card recognized by the pci bus? (lspci -vv) If so, and your pci-id is different than the one above you can enter a section like this in /etc/pcmcia/config: card "your-card" pci man-id, card-id (from cb_alloc in /var/log/messages after starting the pcmcia service) bind "ohci1394_cb" (if it is really a ohci based and not a pcilynx one, otherwise you may can try to bind it to "pcilynx_cb" It is may not correct the id stuff, but having a look into ohci1394 should show you some id's as well. I'm not on the machine now, so some things may not be 100% correct. Andreas |
From: matt n. <sp...@te...> - 2000-12-21 20:17:47
|
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: Michele B. <mi...@po...> - 2000-12-21 09:57:32
|
i'm the same problems (i compiled the kernel 2 days ago, 2.2.18pre21 with the 1394 lates patch) i've a dlink fw card with a jvc dvm5. i've no experience on driver developing, so while i try to undestand smth, if you like to have some logs, please tell me. michele |
From: Tom B. <tb...@ba...> - 2000-12-21 09:01:05
|
stock kernel 2.2.17 with iee1394 driver from cvs, patches went fine ... D-link DFW-500 firewire card... uses TI chipset ohci driver... not that it's relevent but libraw version is current, and the test showed no errors, the gscanbus utility showed what I assumed was the host adapter ... it segfaulted on me once while starting the camera, but I couldn't get it to do that while I was tracing it with gdb ... ... from a userspace point of view, the machine locks up when the sony DCR-TRV210 digital video camera gets turned on... but if you're on the console it's a different matter, you can see the console messages rapidly scrolling by... The machine is an athlon tbird-800 on an a7v motherboard ... I pulled pretty much everything I didn't need out and disabled the secondary ide controller to free up an IRQ for the FW card, still no joy ... anyhow, syslog output follows... Dec 20 18:34:21 home kernel: raw1394: /dev/raw1394 device initialized Dec 20 18:34:46 home kernel: ieee1394: registered ohci1394 driver, initializing now Dec 20 18:34:46 home kernel: ohci1394: looking for Ohci1394 cards Dec 20 18:34:46 home kernel: ohci1394_0: Selfid buffer c6bd5000 not aligned on 8Kb boundary... may cause pb Dec 20 18:34:46 home kernel: ohci1394_0: remapped memory spaces reg 0xc8026000 Dec 20 18:34:46 home kernel: ohci1394_0: allocated interrupt 15 Dec 20 18:34:46 home kernel: ohci1394_0: soft reset finished Dec 20 18:34:46 home kernel: ohci1394_0: max packet size = 2048 bytes Dec 20 18:34:46 home kernel: ohci1394_0: 4 iso receive contexts available Dec 20 18:34:46 home kernel: ohci1394_0: 8 iso transmit contexts available Dec 20 18:34:46 home kernel: ohci1394_0: Receive DMA ctx=0 initialized Dec 20 18:34:46 home kernel: ohci1394_0: Receive DMA ctx=1 initialized Dec 20 18:34:46 home kernel: ohci1394_0: AT dma ctx=0 initialized Dec 20 18:34:46 home kernel: ohci1394_0: AT dma ctx=1 initialized Dec 20 18:34:46 home kernel: ohci1394_0: Receive DMA ctx=2 initialized Dec 20 18:34:46 home kernel: ohci1394_0: resetting bus on request Dec 20 18:34:46 home kernel: ieee1394: detected 1 ohci1394 adapter Dec 20 18:34:46 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:34:46 home kernel: ohci1394_0: SelfID process finished (phyid 0, root) Dec 20 18:34:46 home kernel: ohci1394_0: selfid packet 0x807f8456 rcvd Dec 20 18:34:46 home kernel: ieee1394: including selfid 0x56847f80 Dec 20 18:34:46 home kernel: ohci1394_0: This node self-id is 0x807f8456 Dec 20 18:34:46 home kernel: ohci1394_0: calling self-id complete which looks ok to me ... we then turn on the video camera and everything goes to HELL Dec 20 18:35:56 home kernel: ohci1394_0: Bus reset Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home kernel: ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home last message repeated 4 times Dec 20 18:35:56 home kernel: ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home last message repeated 5 times Dec 20 18:35:56 home kernel: ohci1394_0: SelfID process finished (phyid 0, not root) Dec 20 18:35:56 home kernel: ohci1394_0: selfid packet 0x807f8494 rcvd Dec 20 18:35:56 home kernel: ieee1394: including selfid 0x94847f80 Dec 20 18:35:56 home kernel: ohci1394_0: This node self-id is 0x807f8494 Dec 20 18:35:56 home kernel: ohci1394_0: calling self-id complete Dec 20 18:35:56 home kernel: ieee1394: SelfIDs failed root check Dec 20 18:35:56 home kernel: ieee1394: error in SelfID stage - resetting Dec 20 18:35:56 home kernel: ohci1394_0: resetting bus on request Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home kernel: ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home last message repeated 4 times Dec 20 18:35:56 home kernel: ohci1394_0: SelfID process finished (phyid 0, not root) Dec 20 18:35:56 home kernel: ohci1394_0: selfid packet 0x807f8494 rcvd Dec 20 18:35:56 home kernel: ieee1394: including selfid 0x94847f80 Dec 20 18:35:56 home kernel: ohci1394_0: This node self-id is 0x807f8494 Dec 20 18:35:56 home kernel: ohci1394_0: calling self-id complete Dec 20 18:35:56 home kernel: ieee1394: SelfIDs failed root check Dec 20 18:35:56 home kernel: ieee1394: error in SelfID stage - resetting Dec 20 18:35:56 home kernel: ohci1394_0: resetting bus on request Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home kernel: ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home last message repeated 4 times Dec 20 18:35:56 home kernel: ohci1394_0: irq_handler timeout event=0x00020000 Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home kernel: ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 Dec 20 18:35:56 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:35:56 home last message repeated 5 times Dec 20 18:35:56 home kernel: ohci1394_0: SelfID process finished (phyid 0, not root) Dec 20 18:35:56 home kernel: ohci1394_0: selfid packet 0x807f8494 rcvd Dec 20 18:35:56 home kernel: ieee1394: including selfid 0x94847f80 Dec 20 18:35:56 home kernel: ohci1394_0: This node self-id is 0x807f8494 Dec 20 18:35:56 home kernel: ohci1394_0: calling self-id complete <snip> things do recover when the camera is turned off... <snip> Dec 20 18:36:37 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:36:37 home last message repeated 5 times Dec 20 18:36:37 home kernel: ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 Dec 20 18:36:37 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:36:37 home last message repeated 5 times Dec 20 18:36:37 home kernel: ohci1394_0: SelfID process finished (phyid 0, not root) Dec 20 18:36:37 home kernel: ohci1394_0: selfid packet 0x807f8494 rcvd Dec 20 18:36:37 home kernel: ieee1394: including selfid 0x94847f80 Dec 20 18:36:37 home kernel: ohci1394_0: This node self-id is 0x807f8494 Dec 20 18:36:37 home kernel: ohci1394_0: calling self-id complete Dec 20 18:36:37 home kernel: ieee1394: SelfIDs failed root check Dec 20 18:36:37 home kernel: ieee1394: error in SelfID stage - resetting Dec 20 18:36:37 home kernel: ohci1394_0: resetting bus on request Dec 20 18:36:37 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:36:37 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:36:37 home kernel: ohci1394_0: SelfID process finished (phyid 0, root) Dec 20 18:36:37 home kernel: ohci1394_0: Error in reception of self-id packetsSelf-id count: 80180004 q[0]: Dec 20 18:36:37 home kernel: ohci1394_0: Timeout on self-id error reception Dec 20 18:36:37 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:36:37 home kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Dec 20 18:36:37 home kernel: ohci1394_0: SelfID process finished (phyid 0, root) Dec 20 18:36:37 home kernel: ohci1394_0: Error in reception of self-id packetsSelf-id count: 80180004 q[0]: Dec 20 18:36:37 home kernel: ohci1394_0: Timeout on self-id error reception that's the end of the syslog messages... /proc/ohci1394 after the above episode: IEEE-1394 OHCI Driver status report: bus number: 0x3ff Node ID: 0x0 ### Host data ### node_count: 0 node_id : 0000FFC0 irm_id : 0000FFFF busmgr_id : 0000FFFF initialized in_bus_reset ---Iso Receive DMA--- Current buf: 0 offset: 0 ---Async Receive DMA--- Ar req current buf: 2 offset: 400 AR resp current buf: 0 offset: 0 ---Async Transmit DMA--- AT req prg: 2 sent: 2 free: 32 branchAddrPtr: 00000000 AT req queue: first: 00000000 last: 00000000 AR resp prg: 0 sent: 0 free: 32 branchAddrPtr: 00000000 AT resp queue: first: 00000000 last: 00000000 ### HC Register dump ### Version : 01010000 GUID_ROM : 00000000 ATRetries : 00000822 CSRData : 00000000 CSRCompData : 00000000 CSRControl : 80000000 ConfigROMhdr: 04047cf8 BusID : 31333934 BusOptions : f07da002 GUIDHi : 37200856 GUIDLo : 00001e59 ConfigROMmap: 06bd6000 PtdWrAddrLo : 00000000 PtdWrAddrHi : 00000000 VendorID : 00000000 HCControl : 000e0000 SelfIDBuffer: 06bd5000 SelfIDCount : 80180004 IRMuChMaskHi: 00000000 IRMuChMaskLo: 00000000 IntEvent : 00780000 IntMask : 840300ff IsoXmIntEvnt: 00000000 IsoXmIntMask: 00000000 IsoRcvIntEvt: 00000000 IsoRcvIntMsk: 00000001 FairnessCtrl: 00000000 LinkControl : 00300200 NodeID : c800ffc0 PhyControl : 0000017f IsoCyclTimer: 9813ab75 AsRqFilterHi: ffffffff AsRqFilterLo: ffffffff PhyReqFiltHi: ffffffff PhyReqFiltLo: ffffffff PhyUpperBnd : 00000000 AsRqTrCxtCtl: 0000001e AsRqTrCmdPtr: 06b91002 AsRsTrCtxCtl: 00000000 AsRsTrCmdPtr: 00000000 AsRqRvCtxCtl: 00008409 AsRqRvCmdPtr: 06b9f001 AsRsRvCtxCtl: 00008400 AsRsRvCmdPtr: 06b99001 IntEvent : 00780000 IsoRCtxCtl00: d0008400 IsoRCmdPtr00: 06b51001 IsoRCxtMch00: f0000000 IsoRCtxCtl01: 00000000 IsoRCmdPtr01: 00000000 IsoRCxtMch01: 00000000 IsoRCtxCtl02: 00000000 IsoRCmdPtr02: 00000000 IsoRCxtMch02: 00000000 IsoRCtxCtl03: 00000000 IsoRCmdPtr03: 00000000 IsoRCxtMch03: 00000000 IsoTCtxCtl00: 00000000 IsoTCmdPtr00: 00000000 IsoTCtxCtl01: 00000000 IsoTCmdPtr01: 00000000 IsoTCtxCtl02: 00000000 IsoTCmdPtr02: 00000000 IsoTCtxCtl03: 00000000 IsoTCmdPtr03: 00000000 IsoTCtxCtl04: 00000000 IsoTCmdPtr04: 00000000 IsoTCtxCtl05: 00000000 IsoTCmdPtr05: 00000000 IsoTCtxCtl06: 00000000 IsoTCmdPtr06: 00000000 IsoTCtxCtl07: 00000000 IsoTCmdPtr07: 00000000 ---------- After removing and reloading the modules ------------------ IEEE-1394 OHCI Driver status report: bus number: 0x3ff Node ID: 0x0 ### Host data ### node_count: 1 node_id : 0000FFC0 irm_id : 0000FFFF busmgr_id : 0000FFFF initialized root ---Iso Receive DMA--- Current buf: 0 offset: 0 ---Async Receive DMA--- Ar req current buf: 0 offset: 16 AR resp current buf: 0 offset: 0 ---Async Transmit DMA--- AT req prg: 0 sent: 0 free: 32 branchAddrPtr: 00000000 AT req queue: first: 00000000 last: 00000000 AR resp prg: 0 sent: 0 free: 32 branchAddrPtr: 00000000 AT resp queue: first: 00000000 last: 00000000 ### HC Register dump ### Version : 01010000 GUID_ROM : 00000000 ATRetries : 00000822 CSRData : 00000000 CSRCompData : 00000000 CSRControl : 80000000 ConfigROMhdr: 04047cf8 BusID : 31333934 BusOptions : f07da002 GUIDHi : 37200856 GUIDLo : 00001e59 ConfigROMmap: 06b91000 PtdWrAddrLo : 00000000 PtdWrAddrHi : 00000000 VendorID : 00000000 HCControl : 000e0000 SelfIDBuffer: 06b90000 SelfIDCount : 0001000c IRMuChMaskHi: 00000000 IRMuChMaskLo: 00000000 IntEvent : 00100000 IntMask : 840300ff IsoXmIntEvnt: 00000000 IsoXmIntMask: 00000000 IsoRcvIntEvt: 00000000 IsoRcvIntMsk: 00000001 FairnessCtrl: 00000000 LinkControl : 00300200 NodeID : c800ffc0 PhyControl : 0000017f IsoCyclTimer: 0eebe26d AsRqFilterHi: ffffffff AsRqFilterLo: ffffffff PhyReqFiltHi: ffffffff PhyReqFiltLo: ffffffff PhyUpperBnd : 00000000 AsRqTrCxtCtl: 00000000 AsRqTrCmdPtr: 00000000 AsRsTrCtxCtl: 00000000 AsRsTrCmdPtr: 00000000 AsRqRvCtxCtl: 00008409 AsRqRvCmdPtr: 04506001 AsRsRvCtxCtl: 00008400 AsRsRvCmdPtr: 04526001 IntEvent : 00100000 IsoRCtxCtl00: d0008400 IsoRCmdPtr00: 0464e001 IsoRCxtMch00: f0000000 IsoRCtxCtl01: 00000000 IsoRCmdPtr01: 00000000 IsoRCxtMch01: 00000000 IsoRCtxCtl02: 00000000 IsoRCmdPtr02: 00000000 IsoRCxtMch02: 00000000 IsoRCtxCtl03: 00000000 IsoRCmdPtr03: 00000000 IsoRCxtMch03: 00000000 IsoTCtxCtl00: 00000000 IsoTCmdPtr00: 00000000 IsoTCtxCtl01: 00000000 IsoTCmdPtr01: 00000000 IsoTCtxCtl02: 00000000 IsoTCmdPtr02: 00000000 IsoTCtxCtl03: 00000000 IsoTCmdPtr03: 00000000 IsoTCtxCtl04: 00000000 IsoTCmdPtr04: 00000000 IsoTCtxCtl05: 00000000 IsoTCmdPtr05: 00000000 IsoTCtxCtl06: 00000000 IsoTCmdPtr06: 00000000 IsoTCtxCtl07: 00000000 IsoTCmdPtr07: 00000000 lspci -v report... ------------------------------------------- 00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02) Subsystem: Asustek Computer, Inc.: Unknown device 8033 Flags: bus master, medium devsel, latency 0 Memory at e4000000 (32-bit, prefetchable) Capabilities: [a0] AGP version 2.0 Capabilities: [c0] Power Management version 2 00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8305 (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: e1800000-e2dfffff Prefetchable memory behind bridge: e2f00000-e3ffffff Capabilities: [80] Power Management version 2 00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 22) Subsystem: Asustek Computer, Inc.: Unknown device 8033 Flags: bus master, stepping, medium devsel, latency 0 00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10) (prog-if 8a [Master SecP PriP]) Flags: bus master, medium devsel, latency 32 I/O ports at d800 Capabilities: [c0] Power Management version 2 00:04.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 15 I/O ports at d400 Capabilities: [80] Power Management version 2 00:04.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Flags: bus master, medium devsel, latency 32, IRQ 15 I/O ports at d000 Capabilities: [80] Power Management version 2 00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30) Flags: medium devsel Capabilities: [68] Power Management version 2 00:09.0 FireWire (IEEE 1394): Texas Instruments TSB12LV23 OHCI Compliant IEEE-1394 Controller (prog-if 10 [OHCI]) Subsystem: Texas Instruments: Unknown device 8010 Flags: bus master, medium devsel, latency 32, IRQ 15 Memory at e1000000 (32-bit, non-prefetchable) Memory at e0800000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 1 00:0a.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20) Subsystem: Netgear FA310TX Flags: bus master, medium devsel, latency 32, IRQ 12 I/O ports at a400 Memory at e0000000 (32-bit, non-prefetchable) 00:11.0 Unknown mass storage controller: Promise Technology, Inc.: Unknown device 0d30 (rev 02) Subsystem: Promise Technology, Inc.: Unknown device 4d33 Flags: bus master, medium devsel, latency 32, IRQ 10 I/O ports at a000 I/O ports at 9800 I/O ports at 9400 I/O ports at 9000 I/O ports at 8800 Memory at df800000 (32-bit, non-prefetchable) Capabilities: [58] Power Management version 1 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G100 [Productiva] AGP (rev 02) (prog-if 00 [VGA]) Subsystem: Matrox Graphics, Inc.: Unknown device ff01 Flags: bus master, stepping, medium devsel, latency 64, IRQ 11 Memory at e3000000 (32-bit, prefetchable) Memory at e2000000 (32-bit, non-prefetchable) Memory at e1800000 (32-bit, non-prefetchable) Expansion ROM at e2ff0000 [disabled] Capabilities: [dc] Power Management version 1 Capabilities: [f0] AGP version 1.0 In case it's relevent: [root@home ~]# hdparm /dev/hda /dev/hda: multcount = 0 (off) I/O support = 0 (default 16-bit) unmaskirq = 0 (off) using_dma = 1 (on) keepsettings = 0 (off) nowerr = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 26473/16/63, sectors = 26684784, start = 0 bus on request ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished (phyid 0, not root) ohci1394_0: selfid packet 0x807f8494 rcvd ieee1394: including selfid 0x94847f80 ohci1394_0: This node self-id is 0x807f8494 ohci1394_0: calling self-id complete ieee1394: SelfIDs failed root check ieee1394: error in SelfID stage - resetting ohci1394_0: resetting bus on request ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: irq_handler timeout event=0x00020000 ohci1394_0: SelfID process finished (phyid 0, not root) ohci1394_0: selfid packet 0x807f8494 rcvd ieee1394: including selfid 0x94847f80 ohci1394_0: This node self-id is 0x807f8494 ohci1394_0: calling self-id complete ieee1394: SelfIDs failed root check ieee1394: error in SelfID stage - resetting ohci1394_0: resetting bus on request ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished (phyid 0, not root) ohci1394_0: selfid packet 0x807f8494 rcvd ieee1394: including selfid 0x94847f80 ohci1394_0: This node self-id is 0x807f8494 ohci1394_0: calling self-id complete ieee1394: SelfIDs failed root check ieee1394: error in SelfID stage - resetting ohci1394_0: resetting bus on request ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished (phyid 0, not root) ohci1394_0: selfid packet 0x807f8494 rcvd ieee1394: including selfid 0x94847f80 ohci1394_0: This node self-id is 0x807f8494 ohci1394_0: calling self-id complete ieee1394: SelfIDs failed root check ieee1394: error in SelfID stage - resetting ohci1394_0: resetting bus on request ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished but NodeID not valid: 0800FFC0 ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished (phyid 0, not root) ohci1394_0: selfid packet 0x807f8494 rcvd ieee1394: including selfid 0x94847f80 ohci1394_0: This node self-id is 0x807f8494 ohci1394_0: calling self-id complete ieee1394: SelfIDs failed root check ieee1394: error in SelfID stage - resetting ohci1394_0: resetting bus on request ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished (phyid 0, root) ohci1394_0: Error in reception of self-id packetsSelf-id count: 80180004 q[0]: 00184bc1 ohci1394_0: Timeout on self-id error reception ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished (phyid 0, root) ohci1394_0: Error in reception of self-id packetsSelf-id count: 80180004 q[0]: 00184bc1 ohci1394_0: Timeout on self-id error reception ohci1394_0: soft reset finished ohci1394: removed ohci1394 module raw1394: /dev/raw1394 device initialized ieee1394: registered ohci1394 driver, initializing now ohci1394: looking for Ohci1394 cards ohci1394_0: remapped memory spaces reg 0xc8026000 ohci1394_0: allocated interrupt 15 ohci1394_0: soft reset finished ohci1394_0: max packet size = 2048 bytes ohci1394_0: 4 iso receive contexts available ohci1394_0: 8 iso transmit contexts available ohci1394_0: Receive DMA ctx=0 initialized ohci1394_0: Receive DMA ctx=1 initialized ohci1394_0: AT dma ctx=0 initialized ohci1394_0: AT dma ctx=1 initialized ohci1394_0: Receive DMA ctx=2 initialized ohci1394_0: resetting bus on request ieee1394: detected 1 ohci1394 adapter ohci1394_0: Got phy packet ctx=0 ... discarded ohci1394_0: SelfID process finished (phyid 0, root) ohci1394_0: selfid packet 0x807f8456 rcvd ieee1394: including selfid 0x56847f80 ohci1394_0: This node self-id is 0x807f8456 ohci1394_0: calling self-id complete |
From: Andreas B. <and...@mu...> - 2000-12-20 01:07:24
|
On Thu, Dec 14, 2000 at 09:51:50PM -0600, David Scott Page wrote: > Hi, > > I'm having some trouble at the "Testing" stage of getting started and > would appreciate any suggestions. The details are enclosed below. > -------------------------------------------------------------------------- > # cat /proc/ohci1394 > IEEE-1394 OHCI Driver status report: > bus number: 0x3ff Node ID: 0x3f > > ### Host data ### > node_count: 0 node_id : 00000000 <- node count 0 is discouraging > irm_id : 0000FFFF busmgr_id : 0000FFFF > initialized in_bus_reset > ... It doesn't seem to come out of bus reset. Since this is the first thing that needs interrupts, it's very probably the interrupts that don't seem to work. > # lspci > ... > 00:09.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8011 > ... 'lspci -v' would be more informative (especially wrt interrupt assignments). Anyway, my standard suggestion is to check the BIOS for a "PNP OS installed" or similar option and set it to "no". That often does the trick. -- Andreas E. Bombe <and...@mu...> DSA key 0x04880A44 http://home.pages.de/~andreas.bombe/ http://linux1394.sourceforge.net/ |
From: Mark <to...@to...> - 2000-12-16 06:50:49
|
OK, i figured out what was up with my bios patches and stuff. The Spacewalker HOT-591P mobo that I have has BIOS patches for DOS. Thank god. The maker of the IDE chips, Viatech, has some sort of specialty driver for windows. I don't know what it does or why it is necessary for windows, but it was not necessary for linux. Also, I am going to assume that dvgrab complaining about buffer underruns is ok, or at least more ok than the dropped packets problem i was having before. Can someone correct me if i am wrong? thanks mark to...@de... |
From: David S. P. <pa...@cs...> - 2000-12-15 03:51:51
|
Hi, I'm having some trouble at the "Testing" stage of getting started and would appreciate any suggestions. The details are enclosed below. -- Scott Page -------------------------------------------------------------------------- kernel version: 2.2.18 (2.2.17 patches applied - manual apply of two makefile hunk rejects, and removal of set_connect_state, BUG, get_order, dma_addr_t definitions from lunix22compat.h) -------------------------------------------------------------------------- ieee1394 version: CVS, December 13 (latest entry appears to be /ohci1394.c/1.49/Wed Dec 13 05:59:58 2000//) -------------------------------------------------------------------------- libraw version: libraw1394-0.7 driver: OHCI -------------------------------------------------------------------------- dmsg: raw1394: /dev/raw1394 device initialized ieee1394: registered ohci1394 driver, initializing now ohci1394: looking for Ohci1394 cards ohci1394_0: remapped memory spaces reg 0xc8095000 ohci1394_0: allocated interrupt 5 ohci1394_0: soft reset finished ohci1394_0: max packet size = 2048 bytes ohci1394_0: 4 iso receive contexts available ohci1394_0: 8 iso transmit contexts available ohci1394_0: Receive DMA ctx=0 initialized ohci1394_0: Receive DMA ctx=1 initialized ohci1394_0: AT dma ctx=0 initialized ohci1394_0: AT dma ctx=1 initialized ohci1394_0: Receive DMA ctx=2 initialized ohci1394_0: resetting bus on request ieee1394: detected 1 ohci1394 adapter -------------------------------------------------------------------------- # cat /proc/ohci1394 IEEE-1394 OHCI Driver status report: bus number: 0x3ff Node ID: 0x3f ### Host data ### node_count: 0 node_id : 00000000 <- node count 0 is discouraging irm_id : 0000FFFF busmgr_id : 0000FFFF initialized in_bus_reset ... -------------------------------------------------------------------------- Adapter hardware: ADS 1394 DV API-1394-PCI 260017-001-02 B1 98FLD7T TSB41LV03 97A0J1J TSB12LV23 F711958A -------------------------------------------------------------------------- # lspci ... 00:09.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8011 ... -------------------------------------------------------------------------- # ./testlibraw successfully got handle current generation number: 0 1 card(s) found nodes on bus: 0, card name: ohci1394 using first card found: 0 nodes on bus, local ID is 0 doing transactions with custom tag handler using standard tag handler and synchronous calls testing FCP monitoring on local node got fcp command from node 0 of 8 bytes: 01 23 45 67 89 ab cd ef got fcp response from node 0 of 8 bytes: 01 23 45 67 89 ab cd ef polling for leftover messages -------------------------------------------------------------------------- |