WebCam Apple A1023 firewire non reconnue

[Merayo]

Bonjour à tous,

J’ai récupéré une Webcam Apple Isight A1023 Firewire

Au boot système celle ci se met sous tension (clic caractéristique du moteur de zoom)

Ma carte Pci firewire est reconnue par mon systeme

root@Optiplex:/home/merayo# lspci
00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 82Q35 Express PCI Express Root Port (rev 02)
00:03.0 Communication controller: Intel Corporation 82Q35 Express MEI Controller (rev 02)
00:03.2 IDE interface: Intel Corporation 82Q35 Express PT IDER Controller (rev 02)
00:03.3 Serial controller: Intel Corporation 82Q35 Express Serial KT Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [NVS 300] (rev a2)
01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)
03:00.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 61)

Ma configuration

Linux Optiplex 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux

Isight-firmware-tools est installé avec le driver apple AppleUSBVideoSupport

Cheese reste en écran noir…

Je sèche…une idée ?

[mattotop]

03:00.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 61)

Alors non, lspci, c’est ton controleur firewire que ça t’indique.
Il est là, normal, il fonctionne bien.

Il faut plutôt un balayage de ta chaine usb avec lsusb pour avoir des infos (surtout l’ID) sur ta webcam.

A tous hasards aussi, tu as fait un update-usbids ?

[mattotop]

Et à vérifier aussi:
dmesg | grep -E -i “(1394|firewire)”

[Merayo]

Merci de ta réponse

Voici min lsusb

oot@Optiplex:/home/merayo# lsusb
Bus 002 Device 003: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 003: ID 03f0:134a Hewlett-Packard Optical Mouse
Bus 007 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 1a2c:0c23 China Resource Semico Co., Ltd
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Je ne vois rien concernant la webcam (elle est connectée en firewire)

Voici le résultats de update-usbids

root@Optiplex:/home/merayo# update-usbids
–2018-02-10 11:35:54-- http://www.linux-usb.org/usb.ids
Résolution de www.linux-usb.org (www.linux-usb.org)… 216.105.38.10
Connexion à www.linux-usb.org (www.linux-usb.org)|216.105.38.10|:80… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 593370 (579K) [text/plain]
Sauvegarde en : « /var/lib/usbutils/usb.ids.new »

/var/lib/usbutils/usb.ids.new 100%[============================================================================================>] 579,46K 671KB/s in 0,9s

2018-02-10 11:35:55 (671 KB/s) — « /var/lib/usbutils/usb.ids.new » sauvegardé [593370/593370]

Done.

Cela ne change rien à lsusb
J’essaye un HDD firewire pour confirmer la carte, il est reconnu et se monte normalement

Je reboot…

Le même bruit de l’optique qui se met sous tension
Une lampe verte s’allume quelques secondes sur la camera, puis se coupe (La webcam est parfaitement fonctionnelle sous macos, test du jour…)

Même résultat

[Merayo]

root@Optiplex:/home/merayo# dmesg | grep -E -i “(1394|firewire)”
bash: erreur de syntaxe près du symbole inattendu « ( »

J’essaye…

root@Optiplex:/home/merayo# dmesg | grep firewire
[ 1.344360] firewire_ohci 0000:03:00.0: added OHCI v1.0 device as card 0, 8 IR + 8 IT contexts, quirks 0x0
[ 1.856159] firewire_core 0000:03:00.0: created device fw0: GUID 0030bd051500603b, S400
[ 1.856178] firewire_core 0000:03:00.0: phy config: new root=ffc1, gap_count=5
[ 5.091874] firewire_core 0000:03:00.0: created device fw1: GUID 000a27000402be36, S400

[Merayo]

Après quelques recherches, j’ai installé coriander / webcam reconnue et fonctionnelle

Toujours écran noir sous Cheese…

[mattotop]

Quand tu lances coriander, il ne te dit pas sur quel device il agit ?
En ligne de commande, je vois qu’il est verbeux, il ne te parle pas d’un /dev/XXX que tu pourrais utiliser avec cheese --device=DEVICE peut être ?

[Merayo]

Voici ce qu’il m’affiche

root@Optiplex:/home/merayo# coriander
Gtk-Message: Failed to load module “canberra-gtk-module”

(coriander:4955): GnomeUI-WARNING **: While connecting to session manager:
None of the authentication protocols specified are supported.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(coriander:4955): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

canberra-gtk-module ne peut s’installer directement (impossible de trouver le paquet sur un apt-get)

Après recherche je tente un :

apt-get install libcanberra-gtk-module

Il s’installe avec en plus libcanberra-gtk0

Cette première ligne n’apparaît plus, le reste demeure inchangé

Rien de changé pour Cheese

[Merayo]

Dans Cheese, pour compléter, j’obtiens ceci

le menu “Periphérique” reste grisé sans choix possible…

Si je lance cheese par le terminal, j’obtiens ceci

root@Optiplex:/home/merayo# cheese

(cheese:5806): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion ‘G_IS_DBUS_CONNECTION (connection)’ failed

(cheese:5806): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: assertion ‘G_IS_DBUS_PROXY (proxy)’ failed

(cheese:5806): Gtk-WARNING **: Theme parsing error: cheese.css:7:35: The style property GtkScrollbar:min-slider-length is deprecated and shouldn’t be used anymore. It will be removed in a future version
** Message: cheese-application.vala:211: Error during camera setup: Aucun périphérique détecté

(cheese:5806): cheese-CRITICAL **: cheese_camera_device_get_name: assertion ‘CHEESE_IS_CAMERA_DEVICE (device)’ failed

(cheese:5806): GLib-CRITICAL **: g_variant_new_string: assertion ‘string != NULL’ failed

(cheese:5806): GLib-GIO-CRITICAL **: g_settings_schema_key_type_check: assertion ‘value != NULL’ failed

(cheese:5806): GLib-CRITICAL **: g_variant_get_type_string: assertion ‘value != NULL’ failed

(cheese:5806): GLib-GIO-CRITICAL **: g_settings_set_value: key ‘camera’ in ‘org.gnome.Cheese’ expects type ‘s’, but a GVariant of type ‘(null)’ was given

** (cheese:5806): CRITICAL **: cheese_preferences_dialog_setup_resolutions_for_device: assertion ‘device != NULL’ failed

(cheese:5806): dconf-WARNING **: failed to commit changes to dconf: La connexion est fermée