Bug#449272: Alternative (buggy, incomplete) firewire stack shipped instead of the stable one
maks: i'm the *second* to holler due to ethernet over firewire! only the newer stack is built in kernel 2.6.23-1 - no blacklisting possible - no choice! regards, thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449272: Alternative (buggy, incomplete) firewire stack shipped instead of the stable one
On Sun, 04 Nov 2007, James Bromberger wrote: Alexandre Pereira Nunes wrote: 2007/11/4, maximilian attems [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: the switch has been made some time ago. you are the *first* to holler due to ethernet over firewire! Err. No. Not the first. http://lists.debian.org/debian-kernel/2007/10/msg00414.html well is also against old 2.6.22, check out the other bug reports 2.6.23 has latest firewire trunk and bug reporters are happy. checkout 2.6.23 trunk snapshot builds - http://wiki.debian.org/DebianKernel And I'll note that no one replied. Is the Debian-kernel list not the right place to discuss the... Debian Kernel? what are you insinuating?! see discussions on #441206, #441179 and switch announcement Message-ID: [EMAIL PROTECTED] I agree with Alexandre. Not a kernel bug; Juju is a DEVELOPMENT UNSTABLE stack. (Though I see from the kernel build that even further patches have been applied to the current SVN so maybe thats not so broken, however that is NOT in unstable/testing...). no complete wrong perspective. the old stack had a numerous nr. of problem and is disabled due to security concerns. also userspace has to adapt itself to the new stack. fedora 7 released 1/2 a year ago with the new stack and so did fedora 8. i agree that the juju stack is not yet feature complete, but improved already quite a lot since 2.6.22 inclusion. if you want to contribute test latest and holler upstream if that is not working - like #435062 -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449272: Alternative (buggy, incomplete) firewire stack shipped instead of the stable one
Package: linux-image-2.6.22-3-686 Version: 2.6.22-5 Severity: important Debian choose to ship the alternative firewire stack on recent kernels. Firewire maintainers are not recommending this (see http://wiki.linux1394.org/JujuMigration) yet, since this new firewire stack is incomplete. For instance, I can't do ethernet over firewire with 2.6.22, I have to go back to 2.6.18, which gives me other kind of trouble. -- Package-specific info: ** Version: Linux version 2.6.22-3-686 (Debian 2.6.22-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20071019 (prerelease) (Debian 4.1.2-17)) #1 SMP Mon Oct 22 22:11:56 UTC 2007
Bug#449272: Alternative (buggy, incomplete) firewire stack shipped instead of the stable one
On Sun, Nov 04, 2007 at 02:32:46PM -0200, Alexandre Pereira Nunes wrote: Debian choose to ship the alternative firewire stack on recent kernels. Firewire maintainers are not recommending this (see http://wiki.linux1394.org/JujuMigration) yet, since this new firewire stack is incomplete. For instance, I can't do ethernet over firewire with 2.6.22, I have to go back to 2.6.18, which gives me other kind of trouble. the switch has been made some time ago. you are the *first* to holler due to ethernet over firewire! please report bug upstream on bugzilla.kernel.org and let us know your bug nr, see bottom of page http://wiki.debian.org/DebianKernelReportingBugs regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449272: Alternative (buggy, incomplete) firewire stack shipped instead of the stable one
2007/11/4, maximilian attems [EMAIL PROTECTED]: On Sun, Nov 04, 2007 at 02:32:46PM -0200, Alexandre Pereira Nunes wrote: Debian choose to ship the alternative firewire stack on recent kernels. Firewire maintainers are not recommending this (see http://wiki.linux1394.org/JujuMigration) yet, since this new firewire stack is incomplete. For instance, I can't do ethernet over firewire with 2.6.22, I have to go back to 2.6.18, which gives me other kind of trouble. the switch has been made some time ago. you are the *first* to holler due to ethernet over firewire! please report bug upstream on bugzilla.kernel.org and let us know your bug nr, see bottom of page http://wiki.debian.org/DebianKernelReportingBugs regards -- maks What are you talking about? The support to the stable driver wasn't dropped from the kernel (just enable CONFIG_IEEE1394), the recommended policy upstream (from the maintainer's site, see the URL from my previous post) is to enable it, the maintainer's are well aware that the experimental stack only implement a limited subset of firewire functionality, so why should I file a bug there? Note that an upstream 2.6.22 make defconfig does the right thing of selecting the stable drivers and not the experimental one, having it the other way around was a debian decision. I'm not only talking about ip over firewire, there's at least another bug filed against firewire on debian's 2.6.22 (something about an external storage device). The experimental driver is not supposed to work yet (again, see the URL). This newer stack is not expected to get stable before 2.6.24, and in order to prevent further firewire reports on the meanwhile, CONFIG_IEEE1394 should be enabled (as well as the options it brings on the menu). The experimental driver should be disabled for now. The forementioned site points out that not even the userspace library is ready, so many firewire camera programs and such won't operate on the newer stack yet.
Bug#449272: Alternative (buggy, incomplete) firewire stack shipped instead of the stable one
Alexandre Pereira Nunes wrote: 2007/11/4, maximilian attems [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: On Sun, Nov 04, 2007 at 02:32:46PM -0200, Alexandre Pereira Nunes wrote: Debian choose to ship the alternative firewire stack on recent kernels. Firewire maintainers are not recommending this (see http://wiki.linux1394.org/JujuMigration) yet, since this new firewire stack is incomplete. For instance, I can't do ethernet over firewire with 2.6.22, I have to go back to 2.6.18, which gives me other kind of trouble. the switch has been made some time ago. you are the *first* to holler due to ethernet over firewire! Err. No. Not the first. http://lists.debian.org/debian-kernel/2007/10/msg00414.html And I'll note that no one replied. Is the Debian-kernel list not the right place to discuss the... Debian Kernel? please report bug upstream on bugzilla.kernel.org http://bugzilla.kernel.org and let us know your bug nr, see bottom of page http://wiki.debian.org/DebianKernelReportingBugs What are you talking about? snip I agree with Alexandre. Not a kernel bug; Juju is a DEVELOPMENT UNSTABLE stack. (Though I see from the kernel build that even further patches have been applied to the current SVN so maybe thats not so broken, however that is NOT in unstable/testing...). JEB -- James Bromberger | www.james.rcpt.to | james_AT_rcpt.to UK Cell: +44 7952042920 http://www.snapanumber.com/ | Perth/Au phone in London/UK: +61 8 6424 8325 http://www.snapanumber.com/ begin:vcard fn:James Bromberger n:Bromberger;James adr:;;;London;Greater London;;United Kingdom email;internet:[EMAIL PROTECTED] tel;cell:+447952042920 note:GPG: 3F2C F8FD B2D5 AA35 C81A F914 A5F2 7028 0917 A9E4 x-mozilla-html:FALSE url:http://www.james.rcpt.to version:2.1 end:vcard
