[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#449272: linux-2.6: stop this farce, please

# 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

Package: linux-2.6
Version: 2.6.24-4
Followup-For: Bug #449272

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 controller seems to be
recognized now in 2.6.24, I think it wasn't before. Or at least lspci
lists the card correctly with 2.6.24.

The kernel messages I got with 2.6.24 were:

Mar  5 08:44:15 scorpio kernel: firewire_ohci: Added fw-ohci device 0000:05:02.0, OHCI version 1.0
Mar  5 08:44:15 scorpio kernel: firewire_core: created new fw device fw0 (0 config rom retries, S400)
Mar  5 08:44:36 scorpio kernel: firewire_core: giving up on config rom for node id ffc1
Mar  5 08:44:36 scorpio kernel: firewire_core: phy config: card 0, new root=ffc0, gap_count=5

Contrary to some other issues reported with the JuJu stack, but similarly
to the lack of firewire over ethernet, this is NOT a library or application
issue, it's a kernel problem.

I tried installing 2.6.22, couldn't use it because firewire did not work.
I tried installing 2.6.23, couldn't use it because firewire did not work.
Now I tried 2.6.24 and firewire is still not working.

Given that:

 * We're in soft freeze now [1]
 * JuJu is still listed as unsuitable for non-developers [2] and there's
   no saying when it will ever become stable enough; let alone when
   libraries and applications will have caught up
 * Lots of people have complained, are reverting to older kernel
   versions or rolling their own since the Debian kernel packages
   switched to JuJu

I request that the firewire stack be rolled back to the older stack.

Maximilian, vague statements that "next version" or "2.8.666-git2008 has
nice fixes" are no good.
We need actual working firewire in a release.



[1] http://lists.debian.org/debian-devel-announce/2008/03/msg00001.html,
    Message-id: <877igkrf1f.fsf@pindar.marcbrockschmidt.de>
[2] http://wiki.linux1394.org/JujuMigration


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (900, 'testing'), (10, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.20-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Reply to: