linux1394-user

(no subject)

[Sivakumar S - C. Chennai. <siv...@hc...>]

Hi,
=20
I am developing an application in Linux that uses libraw1394 for raw =
packet
transmission, eth1394 for TCP/IP transmission and sbp-2 for bulk
transmission. When I have gone through the FAQ section, I found that =
eth1394
is neither fully implemented nor stable. Can I rely on eth1394? Is it =
stable
now?

Thanks,=20
Sivakumar
DISCLAIMER=20
This message and any attachment(s) contained here are information that =
is confidential, proprietary to HCL Technologies=20
and its customers. Contents may be privileged or otherwise protected by =
law. The information is solely intended for the=20
individual or the entity it is addressed to. If you are not the intended =
recipient of this message, you are not authorized to=20
read, forward, print, retain, copy or disseminate this message or any =
part of it. If you have received this e-mail in error,=20
please notify the sender immediately by return e-mail and delete it from =
your computer

Re: (no subject)

[Phillip M. J. <pm...@yo...>]

Sivakumar S - CTD, Chennai. wrote:
> I am developing an application in Linux that uses libraw1394 for raw packet
> transmission, eth1394 for TCP/IP transmission and sbp-2 for bulk
> transmission. When I have gone through the FAQ section, I found that eth1394
> is neither fully implemented nor stable. Can I rely on eth1394? Is it stable
> now?

I don't think any of linux1394 should be considered 'stable', which is 
why it's flagged as 'EXPERIMENTAL' in the kernel config. However, most 
problems seem to be hardware-dependent, a lot of people are running 
their gear without any trouble, while others simply cannot get their 
hardware to cooperate with Linux' 1394 drivers.

I've been running eth1394 for a few months now, (SUSE 9.2 kernel 2.6.8) 
and I haven't run into any trouble with it, but my needs are fairly 
moderate, although I do saturate the connection on a regular basis. I'm 
not sure how up-to-date the website is, but the eth1394 module has had 
adequate, if not full support for the IP-over-1394 RFC for a few months 
now, so you should even be able to talk to other operating systems.

~phil

(no subject)

[Bilbao J. <JB...@ik...>]

Hi,=20
Does anyone know any soft for Linux, that offers the possibility to
send the firewire data like an IP stream??

Re: (no subject)

[Dan D. <da...@de...>]

Bilbao Josu wrote:
> Hi, 
> Does anyone know any soft for Linux, that offers the possibility to
> send the firewire data like an IP stream??

It all depends on the data type. For DV and MPEG-2 TS, there are RFCs 
for RTP payloads. Fr DV, there is this project, for example:
http://www.sfc.wide.ad.jp/DVTS/.
MPEG-2 over IP is covered by quite a few projects, videolan included.

(no subject)

[Steffen G. <ste...@ua...>]

Hello Stefan,


> > I'm having problems getting my external hard disk to work. If I try
> to
> > copy a directory, some of the files get transferred (80-120 MB),
> after
> > which the transfer stops and "aborting sbp2" errors appear. I tried
> > using sbp2 with "modprobe sbp2 serialize_io=1", but this locked the
> > machine hard.
> 
> How exactly did this happen? Did you unload the module, then reloaded
> it 
> with the parameter? Or did you load it with the parameter after a
> reboot 
> without the sbp2 driver being loaded before? I do not remember any 
> previous report that serialize_io=1 could lock the machine. To me, it 
> appears more likely that some problem with scsi device addition or 
> removal was the actual cause.

I can't repeat the lock-up at the moment. I did use modprobe -r sbp2,
but I've repeated it (modprobe -r sbp2; modprobe sbp2 serialize_io=1)
and everything works much better (no crashes, slow transfers or transfer
lockups with either drive). I agree that it was more likely something to
do with device addition or removal.

Can anyone point me to where sbp2 is loaded in Suse 9.3 so that I can
have these parameters added automatically? I've checked some hotplugging
web pages but they mostly refer to kernel 2.4, and even then I can't
find an explicit 'modprobe sbp2' in the /etc/hotplug* directories.

Steffen

default module load parameters

[Stefan R. <st...@s5...>]

Steffen Graether wrote:
> Can anyone point me to where sbp2 is loaded in Suse 9.3 so that I can
> have these parameters added automatically? I've checked some hotplugging
> web pages but they mostly refer to kernel 2.4, and even then I can't
> find an explicit 'modprobe sbp2' in the /etc/hotplug* directories.

The hotplug agents are just told what type of device was added and 
select a matching kernel module on the fly.

The right place to permanently add kernel module parameters on Linux 2.6 
is either the file /etc/modprobe.conf or, if it does not exist, one or 
more files within /etc/modprobe.d/. You can freely choose the names of 
files in modprobe.d. Earlier versions of modprobe for Linux 2.5/ 2.6 
only used modprobe.conf; modprobe.d is still ignored if modprobe.conf 
exists. I do not know how it is organized in SuSE 9.3.

Add this line to one of those files:
options sbp2 serialize_io=1
-- 
Stefan Richter
-=====-=-=-= -=-= =----
http://arcgraph.de/sr/

(no subject)

[paulo.herman <pau...@ig...>]

Dear Sirs, I need help, and below i send the transcript of my last email 
with suport of Vipower Company, but, with no success... 

I'm sorry for this long long email.. 

-----------------------My problem... ----------------------- 

I need help on Linux RedHat 4. kernel-2.6.9-11 with firewire enabled. 

On tutorial from Oracle 
(http://www.puschitz.com/InstallingOracle10gRAC.shtml#ConfiguringFireWireBasedSharedStorage 
) 
and on the step bellow, its clear that firewire driver / firmware have to 
enable "Multiple Logins" like two or more micro-computers acessing the same 
hard-disk firewire, but i have the following messages/errors: 

============================ step from dmesg of my microcomputer "node2" 
================== 

ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00110666455573f4] 
NET: Registered protocol family 10 
Disabled Privacy Extensions on device c03694e0(lo) 
ieee1394: Node added: ID:BUS[0-01:1023]  GUID[00101003000024ab] 
ieee1394: The root node is not cycle master capable; selecting a new root 
node and resetting... 
IPv6 over IPv4 tunneling driver 
divert: not allocating divert_blk for non-ethernet device sit0 
ieee1394: Node changed: 0-01:1023 -> 0-00:1023 
ieee1394: Node changed: 0-00:1023 -> 0-01:1023 
scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices 
ieee1394: sbp2: Error querying logins to SBP-2 device - timed out 
ieee1394: sbp2: Device does not support any more concurrent logins 
sbp2: probe of 00101003000024ab-0 failed with error -16 
scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices 
ieee1394: sbp2: Error querying logins to SBP-2 device - timed out 
ieee1394: sbp2: Device does not support any more concurrent logins 
sbp2: probe of 00101003000024ab-0 failed with error -16 
ACPI: Power Button (FF) [PWRF] 
ACPI: Sleep Button (CM) [SLPB] 
EXT3 FS on hda5, internal journal 
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm...@uk... 
cdrom: open failed. 

=========================================== END 
=================================== 


I have based my install on the following tutorial bellow 


= Oracle Tutorial to enable a Oracle RAC with hard-disk firewire === 

Configuring FireWire-based Shared Storage 

First make sure that the experimental kernel for FireWire drives was 
installed and that the server was rebooted (see Upgrading the Linux Kernel 
for FireWire Shared Disks Only): 


# uname -r 
2.4.21-15.ELorafw1 


To load the kernel modules/drivers for the FireWire drive(s), add the 
following entry to the /etc/modules.conf file: 


alias ieee1394-controller ohci1394 
post-install ohci1394 modprobe sd_mod 


The alias directive ieee1394-controller is used by Red Hat during the boot 
process. When you check the /etc/rc.d/rc.sysinit file, which is invoked by 
/etc/inittab during the boot process, you will find the following code that 
searches for the ieee1394-controller stanza in /etc/modules.conf: 


if ! strstr "$cmdline" nofirewire ; then 
   aliases=`/sbin/modprobe -c | awk '/^alias ieee1394-controller/ { print $3 
}'` 
   if [ -n "$aliases" -a "$aliases" != "off" ]; then 
      for alias in $aliases ; do 
        [ "$alias" = "off" ] && continue 
        action $"Initializing firewire controller ($alias): " modprobe 
$alias 
      done 
      LC_ALL=C grep -q "SBP2" /proc/bus/ieee1394/devices 2>/dev/null && \ 
                modprobe sbp2 >/dev/null 2>&1 
   fi 
fi 

This means that all the kernel modules for the FireWire drive(s) will be 
loaded automatically during the next reboot and your drive(s) should be 
ready for use. 

To load the modules or the firewire stack right away without rebooting the 
server, execute the following commands: 


su - root 
modprobe ieee1394-controller; modprobe sd_mod 


If everything worked fine, the following modules should be loaded: 


su - root 
# lsmod |egrep "ohci1394|sbp2|ieee1394|sd_mod|scsi_mod" 
sbp2                   19724   0 
ohci1394               28008   0  (unused) 
ieee1394               62884   0  [sbp2 ohci1394] 
sd_mod                 13424   0 
scsi_mod              104616   5  [sbp2 sd_mod sg sr_mod ide-scsi] 
# 


And when you run dmesg, you should see entries similar to this example: 


# dmesg 
... 
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[11]  MMIO=[f2000000-f20007ff]  Max 
Packet=[2048] 
ieee1394: Device added: Node[00:1023]  GUID[0010b9f70089de1c]  [Maxtor] 
scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices 
blk: queue cf172e14, I/O limit 4095Mb (mask 0xffffffff) 
ieee1394: ConfigROM quadlet transaction error for node 01:1023 
ieee1394: Host added: Node[02:1023]  GUID[00110600000032a0]  [Linux 
OHCI-1394] 
ieee1394: sbp2: Query logins to SBP-2 device successful 
ieee1394: sbp2: Maximum concurrent logins supported: 3 
ieee1394: sbp2: Number of active logins: 0 
ieee1394: sbp2: Logged into SBP-2 device 
ieee1394: sbp2: Node[00:1023]: Max speed [S400] - Max payload [2048] 
  Vendor: Maxtor    Model: OneTouch          Rev: 0200 
  Type:   Direct-Access                      ANSI SCSI revision: 06 
blk: queue cd0fb014, I/O limit 4095Mb (mask 0xffffffff) 
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0 
SCSI device sda: 398295040 512-byte hdwr sectors (203927 MB) 
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 
> 


In this example, the kernel reported that the FireWire drive can be shared 
concurrently by 3 servers (see "Maximum concurrent logins supported:"). It 
is very important that you have a drive with a chipset and firmware that 
supports concurrent access for the nodes. The "Number of active logins:" 
shows how many servers are already sharing/using the drive before this 
server added the drive to its system. 


If everything worked fine, you should be able to see now your FireWire 
drive(s): 


su - root 
# fdisk -l 

Disk /dev/sda: 255 heads, 63 sectors, 30515 cylinders 
Units = cylinders of 16065 * 512 bytes 

   Device Boot    Start       End    Blocks   Id  System 
/dev/sda1             1      6375  51207156   83  Linux 
/dev/sda2          6376     12750  51207187+  83  Linux 
... 

=============================== END ========================= 



Please Sirs i need help but anyone on Vipower company answer my queryes by 
e-mail and i think that i have a 
bad product (VP9054 unit and VP9008 Smart-Cable) on my hands... 

Atenciosamente, 



Paulo Herman 

(no subject)

[Vincenzo R. <sma...@ba...>]

confirm 228300

(no subject)

[Aapo R. <be...@va...>]

Hi Dan, thanks for your reply

I double checked everything and yes, you were right. I did not have the
proper rights to write to /dev/dv1394/0 (argh... sorry). I could of sworn
that I had set the rights properly. Do I have to set them every time agai=
n
after I reboot?

Now kino works perfectly and I even get couple of flashes on the camcorde=
r
screen with cinelerra.

I have the libiec61883 installed but I tested with the test-dv (compiled
it from the tarball). It doesn't work. I dont know if this might relate t=
o
the problem with cinelerra.

When I connect the camcorder to the firewire I get:

[root@localhost .libs]# dmesg
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ieee1394: Node resumed: ID:BUS[0-00:1023]  GUID[00804580314d6835]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023

Then I try to use test-dv:

[root@localhost .libs]# ./test-dv -
/data/media/vankkutreenit/vt22005.09.10_18-29-51.dv
Starting to transmit PAL
done.

test-dv returns immediately and nothing happens. Theres no additional
messages in dmesg.

Best Regards:
  Aapo Romu

Re: (no subject)

[Mark <to...@de...>]

Karthikeyan Madathil wrote:
> 
> Hi,
> 
> I've been consistently running into this
> problem while trying to capture DV: after
> a few frames (20 seconds or so), dvgrab
> hangs. I see a message in /var/log/message
> saying
> ohci1394_0: waking up dma cxt 2, processing
> is probably too slow.
> 
> I tried increasing the iso buffer to 16MB,
> with no improvement.
> 
> I tried compiling the drivers with 1394_VERBOSE_DEBUG on.
> 
> The problem goes away,
> but I see a lot of frames dropped and buffer
> underrun messages from dvgrab. I tried compiling
> without VERBOSE_DEBUG, and changed the DBGMSG
> in insert_dma_buffer to always
> print a message. This time, the problem appears
> later (after 3 minutes or so). In the meanwhile,
Do you have DMA turned on? /sbin/hdparm -d1 /dev/hdx


> I still see occasional "waking up dma cxt 2" messages
> interspersed with normal dma insertion messages.

-- 
Mark
to...@de...

-- Support your government, give Echelon / Carnivore something to parse
--
classfield top-secret government restricted data information project CIA
KGB GRU DISA DoD defense systems military systems spy steal terrorist
Allah Natasha Gregori destroy destruct attack democracy will send
Russia bank system compromise international own rule the world ATSC RTEM
warmod ATMD force power enforce sensitive directorate TSP NSTD ORD DD2-N
AMTAS STRAP warrior-T presidental elections policital foreign embassy 
takeover