[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Missing /dev/raw1394



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi. Up to date Sid, 2.6.22

The dvgrab program is trying to access /dev/raw1394, to pull data from 
my video camera (as if that wasn't implicit already).

Funny thing is, /dev/raw1394 doesn't exist.

I'm accustomed to having to fix permissions on it every once in a 
while, but it hasn't simply "not existed" before.

lsmod shows the following modules:
- ------------------
# lsmod | grep firewire
firewire_sbp2          12100  0
scsi_mod              136620  5 
sr_mod,firewire_sbp2,sd_mod,usb_storage,libata
firewire_ohci          16416  0
firewire_core          38784  2 firewire_sbp2,firewire_ohci
crc_itu_t               2144  1 firewire_core
- ------------------

According to the 2.6.22 release notes, these are the modules 
that "should" be loading, so it seems to be working ok at that level.

Google search results include lots of dmesg outputs with "/dev/raw1394 
device initialized" in them, but there is no such line in my dmesg. 

The following comes up when I put the camera online:
- --------------------
firewire_core: phy config: card 0, new root=ffc1, gap_count=5
firewire_core: phy config: card 0, new root=ffc1, gap_count=5
firewire_core: created new fw device fw1 (0 config rom retries)
- --------------------
so the kernel drivers are seeing the hardware, anyway.

Suggestions?

Curt-


- -- 
September 11th, 2001
The proudest day for gun control and central 
planning advocates in American history

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBRrXd3S9Y35yItIgBAQLNKQf/Zt3EXKyHwNBurFyQOEimcNpR/cY9H46+
VBwibwfZgo1rbaQskSl4x6PqvRxrfPYYwfUNCoIt+eW1jXHBgGyakA6cKH6V1tvg
oe1Um1tYqNnEUw5RePBOUu6r5ELaJmq+22IyBv+1Vzjhs0Bbfea5F0NKDjBC4kLe
2JSjvc6pyhndhL99WIydQfPUX60iWJ45iw0wsg3bNf1y0vp/7EBDRHD8c5I5VHtQ
n6qqk/0lPjNYpxa7qHmxzVVwNRu7C+M/M+4pCQo4gMuW7cgOtdsCr5kR27Xxk93j
Migxp+bMsAh0VGtVpUO5rIZhrn98BkHMEbGAqNcYN3IbtDYx+2bXFA==
=5HMI
-----END PGP SIGNATURE-----



Reply to: