Bug#453358: Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
On Sun, Dec 16, 2007 at 03:58:28PM -0600, Steve M. Robbins wrote: Git repos are not relevant here. they are fucking important, but it seems that the firewire lib maintainers are quite lame. I, the lame lib maintainer, tried to compile coriander and one of his own applications, for the juju stack, git cloning libraw and svn co'ing libdc1394 and cvs co'ing coriander. I had to modify coriander slightly and my own application some more, because the API of libdc1394 is still changing. After it all compiled, I tried it on a computer with multiple IIDC camera's attached. The applications see all devices. However, you can only read out one device at a time, because ISO channel allocation is not implemented according to libdc1394. Second, the camera image is messed up, the first 10% is fine but the rest is junk. I'm not the upstream maintainer, I'm the Debian maintainer. I do not mind fixing little things myself, but fixing this is beyond my scope. Upstream is clearly not ready, I cannot package unreleased stuff from git/svn/cvs that is not working properly anyway. Again, for those Debian users who want a *working* FireWire stack, please enable the old modules again. You can build both the old and the new stack. You can blacklist the old modules by default so that only the modules for the new stack get loaded unless the user wants the old one back. -- Met vriendelijke groet / with kind regards, Guus Sliepen [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 13, 2007 at 09:50:56AM -0600, Steve M. Robbins wrote: On Thu, Dec 13, 2007 at 10:27:40AM +0100, maximilian attems wrote: On Wed, Dec 12, 2007 at 11:17:28PM -0600, Steve M. Robbins wrote: As noted by Guus Sliepen, switching from a functioning driver to an experimental driver with no library support is not going to cause the latter to be improved. It's simply annoying to the user. that is a pretty bold incompetent statement, for all relevant libraries patches exists. take them out of the corresponding git repos. By user, I meant Debian user. There is manifestly no library support for the Debian user. Git repos are not relevant here. Agreed. Clarification for Max: here relates to Debian user - they should _not_ need to mess with GIT! I cannot see how you think it improves things to produce a system (Debian Sid) with an unusable 1394 subsystem. It is clearly not being tested nor improved, since anyone who wants to use it is rebuilding the kernel with the old drivers again! I wholeheartedly agree. - Jonas - -- Jonas Smedegaard [EMAIL PROTECTED] http://www.jones.dk/~jonas/ IT-guide dr. Jones[EMAIL PROTECTED] http://dr.jones.dk/+45 40843136 Debian GNU/Linux[EMAIL PROTECTED] http://www.debian.org/ GnuPG(1024D/C02440B8): 9A98 C6EB C098 9ED0 3085 ECA9 9FB0 DB32 C024 40B8 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHYm6Tn7DbMsAkQLgRAgx5AKCR2o4wTdwaJciK05Qpx6VWWp3ctQCfXw34 saixF05OkBIoNM0sM46gbdY= =PAoP -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
On Wed, Dec 12, 2007 at 11:17:28PM -0600, Steve M. Robbins wrote: As noted by Guus Sliepen, switching from a functioning driver to an experimental driver with no library support is not going to cause the latter to be improved. It's simply annoying to the user. that is a pretty bold incompetent statement, for all relevant libraries patches exists. take them out of the corresponding git repos. The linux1394.org people say: At the time of this writing (12/2007), there are still multiple problems with the new FireWire kernel driver stack (alias Juju) compared to the old stack [...] Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux distributors (kernel packagers) as well as to regular users is: Build only the old IEEE 1394 drivers. http://wiki.linux1394.org/JujuMigration et ceterum censo aboves quote is from 1 of the 2 maintainers. the other maintainer considered it fit enough for fedora stable release 7 and 8. also lenny will not release with 2.6.22 nor 2.6.23, 2.6.23 superseeds 2.6.22 and for relevant testers out there 2.6.24-rc5 is available. aboves page has direct links to userspace patches, integrate them. the new stack has many advantages: - leaner codebase (less than 8k lines of code compared to 30k lines of code in the old stack) - cleaned-up and improved in-stack APIs (with the side effect of getting rid of a bunch of old bugs) - design (no kernel threads, compared to one subsystem thread and one thread per FireWire controller in the old stack) the switch to juju allowed to close a nr of *longstanding* reports, plus there is no known security problems unlike the old ieee1394 stack. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
On Thu, Dec 13, 2007 at 10:27:40AM +0100, maximilian attems wrote: On Wed, Dec 12, 2007 at 11:17:28PM -0600, Steve M. Robbins wrote: As noted by Guus Sliepen, switching from a functioning driver to an experimental driver with no library support is not going to cause the latter to be improved. It's simply annoying to the user. that is a pretty bold incompetent statement, for all relevant libraries patches exists. take them out of the corresponding git repos. By user, I meant Debian user. There is manifestly no library support for the Debian user. Git repos are not relevant here. The linux1394.org people say: At the time of this writing (12/2007), there are still multiple problems with the new FireWire kernel driver stack (alias Juju) compared to the old stack [...] Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux distributors (kernel packagers) as well as to regular users is: Build only the old IEEE 1394 drivers. http://wiki.linux1394.org/JujuMigration et ceterum censo aboves quote is from 1 of the 2 maintainers. the other maintainer considered it fit enough for fedora stable release 7 and 8. And the Fedora users are complaining as well. I cannot see how you think it improves things to produce a system (Debian Sid) with an unusable 1394 subsystem. It is clearly not being tested nor improved, since anyone who wants to use it is rebuilding the kernel with the old drivers again! the new stack has many advantages: - leaner codebase (less than 8k lines of code compared to 30k lines of code in the old stack) - cleaned-up and improved in-stack APIs (with the side effect of getting rid of a bunch of old bugs) - design (no kernel threads, compared to one subsystem thread and one thread per FireWire controller in the old stack) Those are all great theoretical advantages. None of them matter to me, as a user. What matters is a working system. And Debian is -- allegedly -- about the users. In that light, I would think that the best approach is: 1. Make sure all libraries are patched. 2. Switch the kernel module. Rather than the other way around. Best regards, -Steve signature.asc Description: Digital signature
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
On Thu, Dec 13, 2007 at 09:50:56AM -0600, Steve M. Robbins wrote: Git repos are not relevant here. they are fucking important, but it seems that the firewire lib maintainers are quite lame. put it that way any firewire lib that does not work with the juju stack warrants a rc bug. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
On Tue, Dec 11, 2007 at 05:32:36PM +0100, maximilian attems wrote: hello, On Tue, Dec 11, 2007 at 05:20:26PM +0100, Laurent Bonnaud wrote: another application stopped working after this kernel change. It is coriander. I do not know if all applications must be fixed or if a fix in the 1394 libraries is enough. Unfortunately libraries are not fixed yet, see bug #453358 : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453358 that is expected and thus the switch to juju is made early in the release cycle. enough time to fix those up. As noted by Guus Sliepen, switching from a functioning driver to an experimental driver with no library support is not going to cause the latter to be improved. It's simply annoying to the user. The linux1394.org people say: At the time of this writing (12/2007), there are still multiple problems with the new FireWire kernel driver stack (alias Juju) compared to the old stack [...] Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux distributors (kernel packagers) as well as to regular users is: Build only the old IEEE 1394 drivers. http://wiki.linux1394.org/JujuMigration Please consider enabling the working driver until userspace libraries exist for the new one. Thanks, -Steve signature.asc Description: Digital signature
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
Hi, another application stopped working after this kernel change. It is coriander. I do not know if all applications must be fixed or if a fix in the 1394 libraries is enough. Unfortunately libraries are not fixed yet, see bug #453358 : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453358 -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
hello, On Tue, Dec 11, 2007 at 05:20:26PM +0100, Laurent Bonnaud wrote: another application stopped working after this kernel change. It is coriander. I do not know if all applications must be fixed or if a fix in the 1394 libraries is enough. Unfortunately libraries are not fixed yet, see bug #453358 : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453358 that is expected and thus the switch to juju is made early in the release cycle. enough time to fix those up. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
clone 436267 -1 reassign -1 dvgrab retitle -1 relies on /dev/raw1394 severity -1 important stop On Mon, 06 Aug 2007, Curt Howland wrote: On Monday 06 August 2007, maximilian attems was heard to say: what are you missing in the yuyu stack? At least raw1394, to create an entry /dev/raw1394 so that dvgrab can access a video camera. I don't know what else might have been mixed into the stack to do the work. The camera shows up, dmesg shows the following when I plug it in: 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) But if /dev/raw1394 is gone with a good reason, such is life. You folks are the experts. fedora disabled due to the same concerns the old IEEE1394 stack. hmm yes, userspace seem to not have adapted yet. that's why we prefer to do such change early in the release process. /dev/raw1394 was already marked deprecated for quite some time. cloning the bugreport to the offending userspace. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
Package: linux-image-2.6.22-1-686 Version: 2.6.22-3 Severity: wishlist The IEEE1394 kernel drivers that have been built as modiles in prior kernels have not been built with the kernel in the linux-image-2.6.22-1-686 package. Having these modules available without compiling a custom kernel has been very useful in the past, would it be possible to enable the IEEE1394 as loadable modules again please? Here is the entire firewire section from /boot/config-2.6.22-1-686 # IEEE 1394 (FireWire) support # CONFIG_FIREWIRE=m CONFIG_FIREWIRE_OHCI=m CONFIG_FIREWIRE_SBP2=m # CONFIG_IEEE1394 is not set -- Package-specific info: ** Version: Linux version 2.6.22-1-686 (Debian 2.6.22-3) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Sun Jul 29 14:37:42 UTC 2007 ** Tainted: PFSRMB ** Kernel log: cs: IO port probe 0xc00-0xcff: clean. cs: IO port probe 0xa00-0xaff: clean. MC'97 1 converters and GPIO not ready (0xff00) drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed drivers/hid/usbhid/hid-core.c: timeout initializing reports input: Logitech Logitech Attack 3 as /class/input/input4 input: USB HID v1.10 Joystick [Logitech Logitech Attack 3] on usb-:00:03.0-2 usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Adding 1510068k swap on /dev/hda5. Priority:-1 extents:1 across:1510068k EXT3 FS on hda1, internal journal sonypi: Sony Programmable I/O Controller Driver v1.26. sonypi: please try the sony-laptop module instead and report failures, see also http://www.linux.it/~malattia/wiki/index.php/Sony_drivers sonypi: detected type2 model, verbose = 0, fnkeyinit = off, camera = off, compat = off, mask = 0x, useinput = on, acpi = on sonypi: enabled at irq=11, port1=0x1080, port2=0x1084 sonypi: device allocated minor is 63 input: Sony Vaio Jogdial as /class/input/input5 input: Sony Vaio Keys as /class/input/input6 device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] pcmcia: Detected deprecated PCMCIA ioctl usage from process: discover. pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools. pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details. NET: Registered protocol family 10 lo: Disabled Privacy Extensions hda: selected mode 0x45 hdc: selected mode 0x42 ACPI: Battery Slot [BAT1] (battery present) ACPI: Battery Slot [BAT2] (battery absent) ACPI: AC Adapter [ACAD] (on-line) input: Lid Switch as /class/input/input7 ACPI: Lid Switch [LID] input: Power Button (CM) as /class/input/input8 ACPI: Power Button (CM) [PWRB] lp0: using parport0 (interrupt-driven). ppdev: user-space parallel port driver ath0: no IPv6 routers present powernow: This module only works with AMD K7 CPUs ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 23 NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 18:21:22 PDT 2007 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: Putting AGP V3 device at :00:00.0 into 8x mode agpgart: SiS delay workaround: giving bridge time to recover. agpgart: Putting AGP V3 device at :01:00.0 into 8x mode sd 0:0:0:1: [sdb] 2001888 512-byte hardware sectors (1025 MB) sd 0:0:0:1: [sdb] Write Protect is off sd 0:0:0:1: [sdb] Mode Sense: 00 00 00 00 sd 0:0:0:1: [sdb] Assuming drive cache: write through sd 0:0:0:1: [sdb] 2001888 512-byte hardware sectors (1025 MB) sd 0:0:0:1: [sdb] Write Protect is off sd 0:0:0:1: [sdb] Mode Sense: 00 00 00 00 sd 0:0:0:1: [sdb] Assuming drive cache: write through sdb: sdb1 usb 4-1: USB disconnect, address 2 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) 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) usb 2-2: new full speed USB device using ohci_hcd and address 2 usb 2-2: configuration #1 chosen from 1 choice scsi2 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 1 alt 0 proto 2 vid 0x03F0 pid 0x2911 usbcore: registered new interface driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver usb-storage: device scan complete scsi 2:0:0:0: Direct-Access HP psc 2210 1.00 PQ: 0 ANSI: 2 sd 2:0:0:0: [sda] Attached SCSI removable disk drivers/usb/class/usblp.c: usblp0: removed usb 2-2: USB disconnect, address 2 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) firewire_core: phy config: card 0, new root=ffc1,
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
On Mon, Aug 06, 2007 at 01:32:15PM -0400, Curt Howland wrote: The IEEE1394 kernel drivers that have been built as modiles in prior kernels have not been built with the kernel in the linux-image-2.6.22-1-686 package. Having these modules available without compiling a custom kernel has been very useful in the past, would it be possible to enable the IEEE1394 as loadable modules again please? no they are the old firwire stack, that has been disabled due to security concern and general distrust. Here is the entire firewire section from /boot/config-2.6.22-1-686 # IEEE 1394 (FireWire) support # CONFIG_FIREWIRE=m CONFIG_FIREWIRE_OHCI=m CONFIG_FIREWIRE_SBP2=m # CONFIG_IEEE1394 is not set what are you missing in the yuyu stack? regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 06 August 2007, maximilian attems was heard to say: no they are the old firwire stack, that has been disabled due to security concern and general distrust. Oh crud. :^( what are you missing in the yuyu stack? At least raw1394, to create an entry /dev/raw1394 so that dvgrab can access a video camera. I don't know what else might have been mixed into the stack to do the work. The camera shows up, dmesg shows the following when I plug it in: - 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) - But if /dev/raw1394 is gone with a good reason, such is life. You folks are the experts. 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) iQEVAwUBRrdlLy9Y35yItIgBAQJa6gf+PHwMHysrCkgYxOH2Z+E1dbz9fP7e5HXH DmqER+1FJpT6KyU8BKvSeYL88b3c3F4ats6F/O5bB7F3ipOuP0l+AgVmgrMt7uyJ SponVi72S7RoeOVvJBYw5Q6caANDdQEwL2HNdiDKcoWEC0m5X6m1bX8CBq5/numv Wq4HWqgjABLzLZRBE9tzlaYV6DWrDrLj6Jm4ININPh3qHP7q13xtzzMz3n8Lb3wu QXkcRT29Kz8C8V4+tzTNfP80BM15bhbBoR9o19XyaZ73PU6Ks1ff0oPkpP1HlJAV nwDZJuVasH2dHDNqu0/t9BReio9yvQUsmoxapRQ/1Azi0sB48EdwmQ== =H7XK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
