| Summary: | kino 1.3.4 : Capture function ( /dev/raw1394! missing with new kernel) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | JeanClaude Garaud <garaud> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | davidwhodgins, marja11, yvesbrungard |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA1only | ||
| Source RPM: | kernel | CVE: | |
| Status comment: | |||
|
Description
JeanClaude Garaud
2012-03-06 00:03:53 CET
Hello is kernel-firmware-extra installed ? also have you more info if you run kino from a console ? Keywords:
(none) =>
NEEDINFO /usr/src/linux-2.6.38.8-10.mga/Documentation/ABI/removed/raw1394
indicates it's been removed from the kernel, and states ...
Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
firewire-core.
Are any /dev/fw* entries created? If so, can kino be configured to use
whatever device is created?CC:
(none) =>
davidwhodgins (In reply to comment #1) > Hello is kernel-firmware-extra installed ? Yes: kernel-firmware-extra version 20110517 revision 1.1.mga.nonfree > > also have you more info if you run kino from a console ? Yes: >> Leaving Editor >> Left Editor >> Starting Capture >> AV/C Activée >>> Using iec61883 capture >>> iec61883Reader::StartThread on port 0 >>> iec61883Reader::StartThread on port 0 (endless) (In reply to comment #1) > Hello is kernel-firmware-extra installed ? Yes: kernel-firmware-extra version 20110517 revision 1.1.mga.nonfree > > also have you more info if you run kino from a console ? Yes: >> Leaving Editor >> Left Editor >> Starting Capture >> AV/C Activée >>> Using iec61883 capture >>> iec61883Reader::StartThread on port 0 >>> iec61883Reader::StartThread on port 0 (endless) (In reply to comment #2) > /usr/src/linux-2.6.38.8-10.mga/Documentation/ABI/removed/raw1394 > indicates it's been removed from the kernel, and states ... > Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of > firewire-core. > > Are any /dev/fw* entries created? If so, can kino be configured to use > whatever device is created? $ ll /dev/fw* ls: impossible d'accéder à /dev/fw*: Aucun fichier ou dossier de ce type (file does not exist) I should say that on the same computer with Mandriva 2010.2 (Official) for x86_64, kino capture works for root, and for users after changing right permissions on raw1394 (when unchanged: $ ll /dev/raw1394 > >> crw-rw---- 1 root root 171, 0 2012-03-01 22:38 /dev/raw1394 is only allowed for root). Try running "modprobe firewire-core", check the syslog output as well as whether or not that creates /dev/fw* entries. (In reply to comment #5) > Try running "modprobe firewire-core", check the syslog output as > well as whether or not that creates /dev/fw* entries. # modprobe firewire-core # ll /dev/fw* ls: impossible d'accéder à /dev/fw*: Aucun fichier ou dossier de ce type (i.e.no file or directory of this type) # tail -f /var/log/syslog (is the content of this file you are looking for ?) There is absolutely no new line appearing in this file with the above commands or when kino capture is lauched. I've found some documentation on migrating from raw1394 to firewire at https://ieee1394.wiki.kernel.org/articles/j/u/j/Juju_Migration_e8a6.html If I understand correctly firewire-ohci is the module that will handle video devices. Try "modprobe firewire-ohci" instead of firewire-core. If that works then it's just a matter of getting the udev rules correct. If it doesn't, then this bug should be assigned to the kernel maintainer. it doesn't work: with "modprobe firewire-ohci" the result is the same as above with "modprobe firewire-core". Can you assign this bug to the kernel maintainer or should I do it myself ? (In reply to comment #8) > it doesn't work: with "modprobe firewire-ohci" the result is the same as above > with "modprobe firewire-core". > Can you assign this bug to the kernel maintainer or should I do it myself ? Done BTW, can you test with old kernel ? (in the live it's the 2.6.38.7-1) Keywords:
NEEDINFO =>
(none) (In reply to comment #9) > (In reply to comment #8) > > it doesn't work: with "modprobe firewire-ohci" the result is the same as above > > with "modprobe firewire-core". > > Can you assign this bug to the kernel maintainer or should I do it myself ? > > Done > > BTW, can you test with old kernel ? (in the live it's the 2.6.38.7-1) Sorry : I could'nt answer earlier. I did'nt succeed installing kernel-desktop-2.6.38.7-1. I tried twice. The first time, after installation of the package kernel-desktop-2.6.38.7-1.mga (x86-64) the PC hung during the shutdown. I had to switch it off. At boot, instead of the usual boot menu I had the Grub> prompt. I modified /boot/grub/menu.lst so that I could restore the usual boot menu and chose kernel-desktop-2.6.38.7-1, but the PC hung. Finally I started with kernel 2.6.38.8 but could'nt start X. The graphic card is "âGT215 [GeForce GTS 360M]" which only works with the _proprietary_ NVIDIA GeForce 6100 to GeForce 360 module (otherwise it hangs). As I did'nt succeed to reinstall it, I reinstalled Mageia 1. The second time I installed 2 packages, kernel-desktop-2.6.38.7-1.mga AND kernel-desktop-devel-2.6.38.7-1.mga (x86-64), shut down without problem, but when booting kernel 2.6.38.7-1 the system hung again. Apparantly downgrading the kernel has not been tested. What should I do now ? For my system I can connect my camescope witout problem in Kino. At connection, I get in messages: Jun 28 21:15:10 localhost kernel: firewire_ohci: Added fw-ohci device 0000:02:02.0, OHCI v1.0, 4 IR + 8 IT contexts, quirks 0x11 Jun 28 21:15:11 localhost kernel: firewire_core: created device fw0: GUID 0011066645695072, S400 The device created is /dev/fw0 I didn't need to put any parameter in Kino. However, the first time I have tried it, I get the messages indicated above in 5. Yves CC:
(none) =>
yves.brungard_mageia Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D With Mageia 2 the bug doesn't exist. Acquisition with kino works perfectly well.
Marja Van Waes
2012-07-09 10:57:26 CEST
CC:
(none) =>
marja11 This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad Status:
NEW =>
RESOLVED |