Page 1 of 1
Firewire not working in Linux
Posted: Fri Apr 20, 2007 2:42 pm
by blenderfish
I have a z61m with Ubuntu 6.10 Edgy installed on it. I cannot seem to get Linux to recognize my firewire port. I have searched here, ThinkWiki, and the Ubuntu Forums to no avail. All I can find is Ubuntu install instructions that say that the firewire functionality is "untested".
lspci shows the following line for the firewire port:
Code:
Code: Select all
0000:15:00.1 FireWire (IEEE 1394): Texas Instruments: Unknown device 803a
As far as I can tell, when I plug my video camera in and switch it on, Ubuntu does nothing. When I open Kino, it does not appear to have recognized that the camera is there, and does not list any devices under DVControl in the options.
This all works fine in WinXP, so I am fairly sure that it is not a hardware problem.
Has anyone tested and used firewire on a Thinkpad in Ubuntu or any other Distro?
Posted: Mon Apr 23, 2007 8:41 am
by jtreble
blenderfish,
I use FireWire on CentOS 4.4 with a T23/T41p. No problem so far.
Posted: Mon Apr 23, 2007 8:53 am
by blenderfish
jtreble: What does your lspci output for the port? I'm a bit of a linux noob, so do you have any suggestions for how I could start to try and get this working?
Posted: Mon Apr 23, 2007 9:49 am
by jtreble
This is the lspci for a T23 + Lacie FW800 PCMCIA card:
[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.9-42.EL #1 Sat Aug 12 09:17:58 CDT 2006 i686 i686 i386 GNU/Linux
[root@localhost ~]# lspci
00:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge (rev 02)
00:01.0 PCI bridge: Intel Corporation 82830 830 Chipset AGP Bridge (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #1) (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #2) (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #3) (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 41)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 (rev 01)
00:1f.3 SMBus: Intel Corporation 82801CA/CAM SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801CA/CAM AC'97 Modem Controller (rev 01)
01:00.0 VGA compatible controller: S3 Inc. SuperSavage IX/C SDR (rev 05)
02:00.0 CardBus bridge: Texas Instruments PCI1420
02:00.1 CardBus bridge: Texas Instruments PCI1420
02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
02:08.0 Ethernet controller: Intel Corporation 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 41)
07:00.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01)
1394a/b also works for me **out of the box** on CentOS 4.4 with,
a.) T41p + Lacie FW800 PCMCIA
b.) T23 + Dock II + Lacie FW800 PCMCIA
c.) T41p + Dock II + Lacie FW800 PCMCIA
d.) T23/41p + Dock II + assorted PCI FireWire cards
Posted: Fri Apr 27, 2007 8:13 pm
by chubes
Please post output of 'dmesg'. For example on my system:
Code: Select all
admin@pepsi:~$ /bin/dmesg | grep 1394
ieee1394: Initialized config rom entry `ip1394'
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[16] MMIO=[d6004000-d60047ff] Max Packet=[2048] IR/IT contexts=[4/8]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023c010100b12b]
ieee1394: Node added: ID:BUS[0-01:1023] GUID[0020110114002c2d]
WARNING: The dv1394 driver is unsupported and will be removed from Linux soon. Use raw1394 instead.
ieee1394: raw1394: /dev/raw1394 device initialized
I don't like that it says 'unknown device' on your system. On my system:
Code: Select all
0a:0a.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
I capture video from my VCR using the module 'raw1394'. It works great. What does your 'lsmod' say?
Posted: Sat Apr 28, 2007 11:32 am
by Volker
People say that this firewire chipset is supported (but I don't have it personally). The subvendor id is not yet known to lspci, thats why you get the "Unknown device 803a". The driver can still work, though. Look at the output of lsmod and see if dv1394 is loaded. If not, try
and check /var/log/messages for any errors.
Volker