Bug#461924: 461924: iwlwifi fixed upstream - Debian

This is a discussion on Bug#461924: 461924: iwlwifi fixed upstream - Debian ; Or so they say. Is just following the upstream instructions at linuxwireless.org likely to work? Will it mess up things done "the debian way"? The other complication is that it sounds as if the fix is to the driver, not ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Bug#461924: 461924: iwlwifi fixed upstream

  1. Bug#461924: 461924: iwlwifi fixed upstream

    Or so they say. Is just following the upstream instructions at
    linuxwireless.org likely to work? Will it mess up things done "the
    debian way"?

    The other complication is that it sounds as if the fix is to the driver,
    not the firmware. The tarball doesn't appear to have any firmware in
    it. They say the 2.6.25 kerrnel will include the fixes, with
    linuxwireless.org having stuff for earlier versions.

    Ross



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Bug#461924: 461924: iwlwifi fixed upstream

    On Sat, Apr 05, 2008 at 08:54:04PM -0700, Ross Boylan wrote:
    > Or so they say. Is just following the upstream instructions at
    > linuxwireless.org likely to work? Will it mess up things done "the
    > debian way"?
    >
    > The other complication is that it sounds as if the fix is to the driver,
    > not the firmware. The tarball doesn't appear to have any firmware in
    > it. They say the 2.6.25 kerrnel will include the fixes, with
    > linuxwireless.org having stuff for earlier versions.


    we provide since long 2.6.25 images just read the DebianKernel
    debian wiki page for trunk apt line.



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  3. Bug#461924: 461924: iwlwifi fixed upstream


    On Sun, 2008-04-06 at 14:12 +0200, maximilian attems wrote:
    > On Sat, Apr 05, 2008 at 08:54:04PM -0700, Ross Boylan wrote:
    > > Or so they say. Is just following the upstream instructions at
    > > linuxwireless.org likely to work? Will it mess up things done "the
    > > debian way"?
    > >
    > > The other complication is that it sounds as if the fix is to the driver,
    > > not the firmware. The tarball doesn't appear to have any firmware in
    > > it. They say the 2.6.25 kerrnel will include the fixes, with
    > > linuxwireless.org having stuff for earlier versions.

    >
    > we provide since long 2.6.25 images just read the DebianKernel
    > debian wiki page for trunk apt line.

    Thanks for the tip. For those following, it's
    http://wiki.debian.org/DebianKernel.

    According to the upstream (intel wifi) bug, 2.6.25 rc5 has the fix; rc3
    didn't. rc5 is what's current from DebianKernel.

    I have mixed feelings about using the bleeding edge; I notice some
    kernels have been held out of testing for quite awhile, apparently
    because of significant problems.

    I don't quite know how the packaging works, but I assume
    http://kernel-handbook.alioth.debian.org/ and other docs referenced on
    the wiki page explain it.



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  4. Bug#461924: 461924: iwlwifi fixed upstream

    On Sun, Apr 06, 2008 at 10:25:37AM -0700, Ross Boylan wrote:
    >
    > On Sun, 2008-04-06 at 14:12 +0200, maximilian attems wrote:
    > Thanks for the tip. For those following, it's
    > http://wiki.debian.org/DebianKernel.
    >
    > According to the upstream (intel wifi) bug, 2.6.25 rc5 has the fix; rc3
    > didn't. rc5 is what's current from DebianKernel.


    no we have newer, running on
    Linux dual 2.6.25-rc8-amd64 #1 SMP Sat Apr 5 05:22:14 UTC 2008 x86_64
    GNU/Linux

    > I have mixed feelings about using the bleeding edge; I notice some
    > kernels have been held out of testing for quite awhile, apparently
    > because of significant problems.


    no held out of testings because of politics
    aka d-i release freezes

    > I don't quite know how the packaging works, but I assume
    > http://kernel-handbook.alioth.debian.org/ and other docs referenced on
    > the wiki page explain it.


    the etch state, newer no.



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

+ Reply to Thread