Package: firmware-nonfree
Version: 0.17
Severity: important
Starting with Linux 2.6.30, the advansys firmware is not built into the kernel,
but loaded. This firmware is BSD-licensed so it's safe to put it in non-free
(it
has no source so it's not free).
These are the four files needed:
Package: firmware-linux
Version: 0.16
Severity: minor
The package description for firmware-linux currently reads:
This package contains the binary firmware for all firmwares which was
formally shipped in the Linux image.
Note subject-verb agreement problem (firmwares was) and sound-alike
word
guess the Social Contract really is a joke. I don't know why new applicants
are supposed to agree to it. Old members apparently violate it at will for
years
with no consequences.
It doesn't make me respect Debian very much.
--
Nathanael Nerode [EMAIL PROTECTED]
Read it and weep.
http
Yes, I can reproduce this bug with 2.6.18-3-686.
I've worked around it permanently by adding the line
blacklist ehci_hcd
to the file
modprobe.d/ncn
so if you need any testing you'll have to ask.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
Steve Langasek wrote:
With the conclusion of GR 2006-007[1], we now have a clear statement from the
Debian developers that it is acceptable to release etch with firmware that
does not meet our usual requirements for inclusion in main, subject to three
principal conditions:
1. the freedom of the
unless they are
considered insignificant to copyright. Now, it's likely that they *are*
insignificant-- they're *tiny*.
The e100 firmware in the BSDs originates from a Linux e100 driver release from
Intel, but a very old one (the 1.x series) which Intel is no longer
distributing.
--
Nathanael
are interchangable; no point in
deliberate
incompatibility.
Indeed. Do you agree that we can do this post-etch, as the current GRs
propose ?
Yes.
--
Nathanael Nerode [EMAIL PROTECTED]
A thousand reasons. http://www.thousandreasons.org/
Lies, theft, war, kidnapping, torture, rape, murder...
Get me
Package: linux-image-2.6.17-2-686
Version: 2.6.17-9
Severity: normal
In 2.6.15-*, my USB pen drive worked normally.
In 2.6.16-* and 2.6.17-*, if I 'rmmod ehci_hcd' before inserting
it, it works normally.
But if ehci_hcd is loaded, it flakes out badly. The way it
flakes out varies.
This is a
Package: linux-2.6
Severity: serious
Justification: copyright
OK. So the e100 microcode situation isn't as bad as we expected -- thanks
entirely
to OpenBSD.
I'm opening this bug to track this issue because I expect it will be resolved
relatively
quickly, and because the 'big bug' is getting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frederik Schueler wrote:
Hello,
On Mon, Sep 25, 2006 at 02:15:54PM -0400, Nathanael Nerode wrote:
Change this policy. You really must make two exceptions:
(1) Removal of material which Debian cannot legally distribute, if
upstream insists
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frederik Schueler wrote:
Hello,
On Mon, Sep 25, 2006 at 01:30:34PM -0400, Nathanael Nerode wrote:
I emailed the contact address at Intel about e100, but it seems to forward
to tech support. We'll see if anything comes back.
what did you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Luther wrote:
On Mon, Sep 25, 2006 at 05:55:22AM -0400, Nathanael Nerode wrote:
tg3 may follow, if there is
a good enough patch to do it nicely. This may come, either from someone like
you (but the patch has to be upstream-quality, which
likely to be sued over: the
company clearly didn't authorize this use.
--
Nathanael Nerode [EMAIL PROTECTED]
A thousand reasons. http://www.thousandreasons.org/
Lies, theft, war, kidnapping, torture, rape, murder...
Get me out of this fascist nightmare!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Luther wrote:
Or you could also help us on this in making sure the tg3 patch in question is
upstream-quality,
I think it is better than upstream. What can I say? :-)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Luther wrote:
The reality is not that the kernel team don't want those firmware in main, but
that in the current state of the debian technology, it is not feasible to do
it right, and it will take time, and will be best done during the etch+1
.
analysis he has done, but upto now, nobody gave any indication that they
are ready to help in this regard, and this includes you. So, what are you
going to do to help us make sure the non-free firmware finds an adequate
solution for etch+1 ?
--
Nathanael Nerode [EMAIL PROTECTED]
Bush
Sven Luther wrote:
Please add that information to the firmware wiki page, so that it is not
forgoten in a few days.
It was generated from Larry's page.
--
Nathanael Nerode [EMAIL PROTECTED]
Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet
Frederik Schueler wrote:
On Sun, Sep 24, 2006 at 11:25:15AM -0400, Nathanael Nerode wrote:
If the firmware-loading tg3 driver is present in the next kernel package
version, I will believe that the kernel team is acting in good faith to
try to satisfy the Social Contract.
According
is acting in good faith to try
to satisfy the Social Contract.
--
Nathanael Nerode [EMAIL PROTECTED]
Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
this distribution.
--
Nathanael Nerode [EMAIL PROTECTED]
Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
--
Nathanael Nerode [EMAIL PROTECTED]
Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
stuff? Quack, Quack? looks confused
I have a wild turkey living in my front yard, but no ducks.
DPL recall, assorted GRs for various stuff).
--
Nathanael Nerode [EMAIL PROTECTED]
Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet
AGP_INTEL is on by default for x86_64 in the current 2.6 Linux kernels.
--
Nathanael Nerode [EMAIL PROTECTED]
Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
recent version of the patch, I
would
greatly appreciate it.)
Thanks in advance.
--
Nathanael Nerode [EMAIL PROTECTED]
Read it and weep.
http://rawstory.com/news/2005/Text_of_Gore_speech_0116.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
not distribute this material.)
snip
There is not much time before the actual etch release is at hand, which is
Do I remember something to the effect of Debian releases when it is
ready? ;-)
--
Nathanael Nerode [EMAIL PROTECTED]
Bush admitted to violating FISA and said he was proud of it.
So why isn't he
affecting the
installation process, like remote root exploits. All other issues will
be addressed as needed in a security update and future point releases.
--
Nathanael Nerode [EMAIL PROTECTED]
Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet
[EMAIL PROTECTED] wrote:
On 08/02/06 22:17, Nathanael Nerode wrote:
Start with drivers/char/drm/mga_ucode.h. This is distributable, because
it's under
a BSD license, but it's not free software, because there's no source code.
There is no source code, because there never was any source code
, harder to ignore, and
better at holding patches and whatnot.
--
Nathanael Nerode [EMAIL PROTECTED]
Bush admitted to violating FISA and said he was proud of it.
So why isn't he in prison yet?...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
In linux.debian.kernel Nathanael Nerode [EMAIL PROTECTED] wrote:
What can be done about this?
Accept that most people do not consider this a problem?
First of all, this is false. Most Debian developers agree with me. You
think not? Prove it by proposing a GR. More importantly, the release
piece of firmware, which
might
at least make *someone* pay *some* attention.
--
Nathanael Nerode
[EMAIL PROTECTED]
This space intentionally left blank.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
to work.
--
Nathanael Nerode [EMAIL PROTECTED]
This space intentionally left blank.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sven Luther wrote:
No, i don't think this was the kind of framework i was refering to,
Well, another related issue is what format the firmware file should be stored
in -- I advocate a fixed endianness so it doesn't depend on the host CPU
details, for instance.
more of a
set of rules on how we
Kyle McMartin wrote:
The question is: when you remove the firmware from the driver, and all
it is, is a file sitting in /lib/firmware/; and it's contents are just
non-executable hex,
Sorry, it is executable. For instance, the tg3 code is simply MIPS binary
which can be disassembled with
Sven Luther wrote:
Hi all,
I am cross posting to debian-release and debian-boot, since this will
affect them too.
snip
Basically, the situation is like this :
1) there where drivers under implicit GPL licence with binary only
firmware. Since there was no explicit licence for this
Andreas Barth wrote:
As this is a release blocker, not release until this is fixed? (And try
to search for someone who can work on this issue,
Ping! Dispirited volunteer here!
perhaps also say
something in the next release update.)
--
ksig --random|
--
To UNSUBSCRIBE, email to [EMAIL
Bastian Blank wrote:
On Tue, Jan 10, 2006 at 09:13:27PM +0100, Sven Luther wrote:
how can you consider it as non-program. It is indeed composed of machine
code destined to run on the controller of the device the driver is
written for.
This is incorrect. I know firmware[tm] blobs which only
Andreas Barth wrote:
* Bastian Blank ([EMAIL PROTECTED]) [060111 12:57]:
On Tue, Jan 10, 2006 at 09:13:27PM +0100, Sven Luther wrote:
how can you consider it as non-program. It is indeed composed of
machine code destined to run on the controller of the device the driver
is written for.
Sven Luther wrote:
On Sun, Jan 08, 2006 at 11:52:20AM +0100, Andreas Barth wrote:
* Sven Luther ([EMAIL PROTECTED]) [060108 11:12]:
There where two fully independent issues here :
1) some (many) of those firmware using modules had a sloppy licencing
situation, which meant the
[EMAIL PROTECTED] wrote:
licenced modules. If we don't want to do that, the most honest way to
handle it is to get another GR out the door,explaining that this is not
easily possible or convenient at this time, and asking for an explicit
exception for kernel firmware. I would second such a GR.
I
to them.
--
Nathanael Nerode [EMAIL PROTECTED]
Make sure your vote will count.
http://www.verifiedvoting.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I retested this and I can't reproduce it with 2.6.15-1. So it seems to be
fixed. Perhaps I was confused, or perhaps there was some transitory thing
going on when I had both 2.6.15-1 and 2.6.14-1 installed.
:-)
--
Nathanael Nerode [EMAIL PROTECTED]
A thousand reasons. http
Also, could you please give us the output of ls -lR /etc/kernel
No such file or directory.
--
Nathanael Nerode [EMAIL PROTECTED]
This space intentionally left blank.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: linux-2.6
Severity: serious
Justification: Won't uninstall cleanly
It hangs on this line of the postrm script:
my $ret = purge();
I can get it to work by deleting this line. Perhaps this is because a
debconf routine is being called after stop has been called? I don't know,
but
close 325192
thanks
Marco d'Itri wrote:
On Sep 22, Nathanael Nerode [EMAIL PROTECTED] wrote:
Marco d'Itri wrote:
Please check if this bug has been fixed by 2.6.13, on my system the four
extra ttyS devices which were claimed by serial8250 are gone.
I'll be sure to do this. 2.6.13 isn't
Marco d'Itri wrote:
Please check if this bug has been fixed by 2.6.13, on my system the four
extra ttyS devices which were claimed by serial8250 are gone.
I'll be sure to do this. 2.6.13 isn't in unstable yet though, is it?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
- readdition of tg3 driver, as firmware license has been fixed
It's distributable, but only in non-free. No source code for the firmware
program. Sorry. :-P Ask debian-legal if you have further questions about
that.
If anyone's interested, I've got a patched version of the tg3 in Debian's
Taking off debian-legal, since this is so not legal discussion anymore.
Andres Salomon wrote:
I think they said they'd accept a patch which loaded the firmware but fell
back to firmware built into the kernel if it wasn't present, as a
transitional requirement. Ugh squared. But I can do
Andres Salomon wrote:
Yes, that's what I was thinking. Vendors will be taking care of
firmware file installation; kbuild should be handling it when running
modules_install. Perhaps a firmware_install target that takes care of
the various firmware blobs?
Sounds good.
I can do that, if
Andres Salomon wrote:
As I remember, upstream (jgarzik/davem) was not overly interested in such
a patch to tg3. Is this still the case, or are they amenable to such
changes?
Upstream was not interested in legal niceties like including copyright
statements, either. I suppose both are still the
driver to non-free in
this case, just the firmware. Remember that this one works for many cards
without the firmware, so people will certainly appreciate that.
--Nathanael Nerode
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Not really. That licence doesn't allow Debian to distribute whatever
it is that's being licenced. There's only permission for personal use.
Hmm. My initial reading was that you could
(1) create, test and provide programs for use with ALTEON network cards
(2) license the object code of such a
Warning: long. CC'ed to debian-legal in case anyone there knows anything more.
The source for the acenic driver is in fact in the source package for
the kernel.
The firmware is absent from Debian for *very* good reasons: the version in
the Linux kernel is distributed without proper copyright
It would help a lot if someone could include a pointer to the appropriate
thread(s) on lkml, or to something else which explained the purported
security hole. I can't find a description of it anywhere.
Nathanael Nerode wrote:
Some of them already *have* provided freely-licensed source (Advansys);
Thinko. Of course I meant Adaptec, with the aic7xxx driver.
The keyspan_pda module by Brian Warner (USB Keyspan PDA Single Port Serial
Driver, USB Xircom / Entregra Single Port Serial Driver
Joshua Kwan wrote:
Nathanael Nerode wrote:
* Since I actually have an advansys card to test on, I should be able to
convert this driver to userland firmware loading without the
annoyances of
a remote testing cycle.
But how do you expect people to install Sarge on systems where the only
mass
So, since nobody else was dealing with populating the upgrade-i386 directory,
I took a crack at it.
Background is in #241497. The essence is that woody users using real i386
boxes (not 486 or higher) need a patched kernel installed before they can
upgrade to woody. I have therefore made such a
Norbert Tretkowski wrote:
* Nathanael Nerode wrote:
I unflagged it and built my own kernel, and it appears to work just
fine.
Perhaps Debian should allow it to build; the card is rather common.
Mr. binary firmware is evil,
s/evil/non-free/, please.
did you realize that the advansys
Adam Majer wrote:
Nathanael Nerode wrote:
Adam Majer wrote:
As to the non-free binary blobs, these are to be moved to non-free.
There should be an automatic 'non-free removal patches' (not part of
the actual debian source).
To follow the X Strike Force model (which seems to work) I suggest
58 matches
Mail list logo
