Hi,
FWIW I have packages ready with both the new juju stack and the old stack
enabled. Then you only need to blacklist one or the other, but you have the
option to choose, without recompiling, so you basically can stay with the
Debian kernels.
linux-2.6 (2.6.24-5~holger+1) unstable;
# This is not an upstream issue! The shipped firewire stack is a kernel
# maintainer's choice.
tags 449272 - upstream
# It's also not specific to linux-image-2.6.22-3-686
reassign 449272 linux-2.6
found 449272 2.6.24-4
thanks
Package: linux-2.6
Version: 2.6.24-4
Followup-For: Bug #449272
I have
On Wed, Mar 05, 2008 at 10:43:28AM +0100, Filip Van Raemdonck wrote:
I have a couple of external firewire disks that are essential to have a
working computer.
Ever since the firewire stack in the Debian kernel packages was switched
to JuJu, these harddisks are no longer working. The
Filip Van Raemdonck [EMAIL PROTECTED] writes:
Package: linux-2.6
Version: 2.6.24-4
[...]
I request that the firewire stack be rolled back to the older stack.
Uhm, I don't quite understand why I was CCed for this mail. Could you
explain what you suppose I should do?
Marc
--
BOFH #305:
Hi Marc,
On Wed, Mar 5, 2008 at 3:44 PM, Marc 'HE' Brockschmidt
[EMAIL PROTECTED] wrote:
Filip Van Raemdonck [EMAIL PROTECTED] writes:
Package: linux-2.6
Version: 2.6.24-4
[...]
I request that the firewire stack be rolled back to the older stack.
Uhm, I don't quite understand why I
On Wed, Mar 5, 2008 at 3:14 PM, Maximilian Attems [EMAIL PROTECTED] wrote:
On Wed, Mar 05, 2008 at 10:43:28AM +0100, Filip Van Raemdonck wrote:
Ever since the firewire stack in the Debian kernel packages was switched
to JuJu, these harddisks are no longer working. The controller seems to
6 matches
Mail list logo
