Matthew == Matthew Wilcox [EMAIL PROTECTED] writes:
Matthew On Mon, Apr 04, 2005 at 10:51:30AM -0700, Greg KH wrote:
Then let's see some acts. We (lkml) are not the ones with the
percieved problem, or the ones discussing it.
Matthew Actually, there are some legitimate problems with some of
Your message dated Thu, 7 Apr 2005 09:37:48 +0200
with message-id [EMAIL PROTECTED]
and subject line Closing PowerEdge 1850/megaraid2 initrd-tools bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Thu, 7 Apr 2005 09:37:48 +0200
with message-id [EMAIL PROTECTED]
and subject line Closing PowerEdge 1850/megaraid2 initrd-tools bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Thu, 7 Apr 2005 09:37:48 +0200
with message-id [EMAIL PROTECTED]
and subject line Closing PowerEdge 1850/megaraid2 initrd-tools bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
On Thursday 07 April 2005 09:25, Jes Sorensen wrote:
[snip] I got it from Alteon
under a written agreement stating I could distribute the image under
the GPL. Since the firmware is simply data to Linux, hence keeping it
under the GPL should be just fine.
Then I would like to exercise my right
Le jeudi 07 avril 2005 10:04 +0200, David Schmitt a crit :
Then I would like to exercise my right under the GPL to aquire the source
code
for the firmware (and the required compilers, starting with genfw.c which is
mentioned in acenic_firmware.h) since - as far as I know - firmware is
Arjan van de Ven [EMAIL PROTECTED] writes:
On Tue, 2005-04-05 at 11:11 +0200, Christoph Hellwig wrote:
On Tue, Apr 05, 2005 at 09:49:25AM +0100, Ian Campbell wrote:
I don't think you did get a rejection, a few people said that _they_
weren't going to do it, but if you want to then go
On Thu, Apr 07, 2005 at 10:17:15AM +0200, Xavier Bestel wrote:
Le jeudi 07 avril 2005 à 10:04 +0200, David Schmitt a écrit :
Then I would like to exercise my right under the GPL to aquire the source
code
for the firmware (and the required compilers, starting with genfw.c which
is
Le jeudi 07 avril 2005 10:32 +0200, Olivier Galibert a crit :
On Thu, Apr 07, 2005 at 10:17:15AM +0200, Xavier Bestel wrote:
Le jeudi 07 avril 2005 10:04 +0200, David Schmitt a crit :
Then I would like to exercise my right under the GPL to aquire the source
code
for the firmware
Eric W. Biederman wrote:
Arjan van de Ven [EMAIL PROTECTED] writes:
On Tue, 2005-04-05 at 11:11 +0200, Christoph Hellwig wrote:
On Tue, Apr 05, 2005 at 09:49:25AM +0100, Ian Campbell wrote:
I don't think you did get a rejection, a few people said that _they_
weren't going to do it, but if you
On Tue, 05 Apr 2005 11:28:22 -0700, Steve Langasek wrote:
tags 291386 unreproducible moreinfo
thanks
Hi Eric,
I've tried to pin down this bug, but I find that the current version of
initrd-tools builds correct (matching) initrds whether or not the lvm10
package is installed. Is it
On Thu, Apr 07, 2005 at 05:34:56AM -0400, Jeff Garzik wrote:
For tg3 a transition period shouldn't be needed as firmware loading
is only needed on old/buggy hardware which is not the common case.
Or to support advanced features which can be disabled.
TSO firmware is commonly used these days.
Hi,
a colleague observed crashes in some heavily multi-threaded Python
applications. He is running Debian sarge with stock kernel
2.6.8-2-686. Using LD_ASSUME_KERNEL fixes the crash, so it seems
to be an NPTL issue. (Maybe stupid) questions:
- Is it relevant, whether Python is compiled on a
Package: kernel-image-2.6.11-1-686-smp
Severity: wishlist
Why it is not included? I compiled kernel 2.6.9 and 2.6.10
with this dirtier:
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=y
CONFIG_MEGARAID_MAILBOX=y
for LSI Logic / Symbios Logic MegaRAID 520 SCSI 320-1 Controller
It is working on
On Wed, Apr 06, 2005 at 01:22:36PM -0600, Eric W. Biederman wrote:
Arjan van de Ven [EMAIL PROTECTED] writes:
On Tue, 2005-04-05 at 11:11 +0200, Christoph Hellwig wrote:
On Tue, Apr 05, 2005 at 09:49:25AM +0100, Ian Campbell wrote:
I don't think you did get a rejection, a few people
Package: kernel-image-2.6.11-1-686
Version: 2.6.11-2
Severity: normal
hi all,
my network is not operational ; i did'nt had such problem with 2.6.10
I go back to 2.4 because i have also burning timeout problems with
2.6.10.
here is the corresponding /var/log/kern.log:
Apr 6 19:54:47 ile
David Schmitt wrote:
On Thursday 07 April 2005 09:25, Jes Sorensen wrote:
[snip] I got it from Alteon under a written agreement stating I
could distribute the image under the GPL. Since the firmware is
simply data to Linux, hence keeping it under the GPL should be just
fine.
Then I would
On Thu, 7 Apr 2005, Humberto Massa wrote:
David Schmitt wrote:
On Thursday 07 April 2005 09:25, Jes Sorensen wrote:
[snip] I got it from Alteon under a written agreement stating I
could distribute the image under the GPL. Since the firmware is
simply data to Linux, hence keeping it under the GPL
Richard == Richard B Johnson [EMAIL PROTECTED] writes:
Richard Last time I checked, GPL was about SOFTware, not FIRMware,
Richard and not MICROcode.
Oh be real, there's no real difference between them and you know it.
It's all about where the bits are stored and what they tend to do in a
Richard B. Johnson [EMAIL PROTECTED] writes:
Last time I checked, GPL was about SOFTware, not FIRMware, and
not MICROcode. If somebody has decided to rename FIRMware to
SOFTware,
Debian has undertaken to change the meaning of a whole lot of words,
including software and free.
This whole
Richard B. Johnson wrote:
Well it doesn't make any difference. If GPL has degenerated to where
one can't upload microcode to a device as part of its initialization,
without having the source that generated that microcode, we are in
a lot of hurt. Intel isn't going to give their designs away.
I
Le jeudi 07 avril 2005 à 09:03 -0400, Richard B. Johnson a écrit :
Well it doesn't make any difference. If GPL has degenerated to
where one can't upload microcode to a device as part of its
initialization, without having the source that generated that
microcode, we are in a lot of hurt. Intel
Your message dated Thu, 7 Apr 2005 16:36:52 +0200 (CEST)
with message-id [EMAIL PROTECTED]
and subject line Solved in 2.6.11
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Package: kernel-image-2.6.8-2-686
Version: 2.6.8-13
The configuration of the stock Debian kernels does not include
CONFIG_SOUND_AWE32_SYNTH. It should. Not all SB AWE32 sound cards
work with ALSA (cf. a post which I recently made to the alsa-user
mailing-list, which will be available as soon as
Oliver Neukum wrote:
As this has been discussed numerous times and consensus never
achieved and is unlikely to be achieved, I suggest that you keep this
discussion internal to Debian until at least you have patches which
can be evaluated and discussed. Until then Debian may do to its
kernel
Am Donnerstag, 7. April 2005 16:30 schrieb Humberto Massa:
I don't recall anyone asking Intel to give theirs designs away. This
thread is about:
1. (mainly) some firmware hexdumps present in the kernel source tree are
either expicitly marked as being GPL'd or unmarked, in which case one
Am Donnerstag, 7. April 2005 17:01 schrieb Humberto Massa:
Oliver Neukum wrote:
As this has been discussed numerous times and consensus never
achieved and is unlikely to be achieved, I suggest that you keep this
discussion internal to Debian until at least you have patches which
Am Donnerstag 07 April 2005 09:37 schrieb Loïc Minier:
Hi,
Yesterday, I successfully installed a PowerEdge 1850 server with
megaraid2 (the same type of machine I described in #299055) with
Debian Installer RC 3.
This was to be expected as I couldn't reproduce the initrd problems
Sven Luther [EMAIL PROTECTED] writes:
On Wed, Apr 06, 2005 at 01:22:36PM -0600, Eric W. Biederman wrote:
For tg3 a transition period shouldn't be needed as firmware loading
is only needed on old/buggy hardware which is not the common case.
Or to support advanced features which can be
On Thu, Apr 07, 2005 at 05:46:27AM -0600, Eric W. Biederman wrote:
Sven Luther [EMAIL PROTECTED] writes:
On Wed, Apr 06, 2005 at 01:22:36PM -0600, Eric W. Biederman wrote:
For tg3 a transition period shouldn't be needed as firmware loading
is only needed on old/buggy hardware which is
Subject: kernel-image-2.6.8-10-amd64-k8: Xfree86 fails to find a VESA chipset
Package: kernel-image-2.6.8-10-amd64-k8
Version: 2.6.8-11
Severity: important
*** Please type your report below this line ***
Hi,
I just installed Debian testing on a new Athlon64/nForce4 machine.
This machine boots
[W. Borgert]
- Is it relevant, whether Python is compiled on a system with 2.6
or 2.4 kernel? If so, how can I find out on which kernel the
Debian package has been built?
Might or might not be relevant - depends on whether the python build
scripts attempt to detect the kernel
Package: kernel-image-2.6.10-1-k7
Version: 2.6.10-6
Followup-For: Bug #296963
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
clone 296963 -1 -2
reassign -1 kernel-image-2.6.8-2-k7
reassign -2 kernel-image-2.6.11-1-k7
merge 296963 -1 -2
thanks
I've tested this on k-i-2.6.8-2-k7 and
On Tue, Apr 05, 2005 at 04:05:07PM +0200, Josselin Mouette wrote:
Le lundi 04 avril 2005 à 21:32 +0200, Adrian Bunk a écrit :
On Mon, Apr 04, 2005 at 09:05:18PM +0200, Marco d'Itri wrote:
On Apr 04, Greg KH [EMAIL PROTECTED] wrote:
What if we don't want to do so? I know I personally
On Tuesday 05 April 2005 08:56, Jefferson Cowart wrote:
Sorry for the delay in sending this. I ended up getting back later than
expected. In any case the hexdumps are below. Please let me know if you need
anything else.
also sorry for the delay :)
Under 2.6.5-bk1
===
On Thu, 07 Apr 2005, Daniel Ritz wrote:
On Tuesday 05 April 2005 08:56, Jefferson Cowart wrote:
Sorry for the delay in sending this. I ended up getting back later than
expected. In any case the hexdumps are below. Please let me know if you need
anything else.
also sorry for the delay :)
On Thu, Apr 07, 2005 at 12:33:53PM +0900, Horms wrote:
Normally this would just be a matter of waiting for the new versions
to filter down to testing, but as part of the attempts to get sarge
released, testing was fozen a little while ago, so changes aren't
propogating, while unstable marches
Thanks for the response.
maximilian attems - Let me know when the kernel is built and I'll go ahead
and try that.
Thanks
Jefferson Cowart
[EMAIL PROTECTED]
-Original Message-
From: maximilian attems [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 07, 2005 16:26
On Thu, Apr 07, 2005 at 11:05:05PM +0200, Sven Luther wrote:
On Thu, Apr 07, 2005 at 10:56:47PM +0200, Adrian Bunk wrote:
...
If your statement was true that Debian must take more care regarding
legal risks than commercial distributions, can you explain why Debian
exposes the legal risks
Hi Ted,
thanks for your detailed reply. If you could get the bk patches and send
them to this thread I will look into getting them reviewed and
the package built. I will also be at LCA, so I look forward to seeing
you there.
Best wishes
--
Horms
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Sven Luther [EMAIL PROTECTED] writes:
It sounds like you are now looking at the question of are the
huge string of hex characters the preferred form for making
modifications to firmware. Personally I would be surprised
but those hunks are small enough it could have been written
in
hello:
i configure a very small kernel, compile it and install,
when i reboot, it stop after print
Rebooting system...
i don't know what was missing from the kernel, can any body
help me?
linux kernel: 2.6.9
machine: IBM T23 laptop
lspci:
:00:00.0 Host bridge: Intel Corp. 82830 830
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.8.14
tags 291386 - unreproducible moreinfo
Bug#291386: creates initrd that cannot use lvm 2 volumes if both lvm2 and lvm10
are installed
Tags were: moreinfo unreproducible
Tags removed:
On Thu, Apr 07, 2005 at 12:05:31PM +0200, Eric Deplagne wrote:
On Tue, 05 Apr 2005 11:28:22 -0700, Steve Langasek wrote:
I've tried to pin down this bug, but I find that the current version of
initrd-tools builds correct (matching) initrds whether or not the lvm10
package is installed. Is
On Thu, Apr 07, 2005 at 05:31:01PM +0200, Timo Veith wrote:
Am Donnerstag 07 April 2005 09:37 schrieb Loïc Minier:
Hi,
Yesterday, I successfully installed a PowerEdge 1850 server with
megaraid2 (the same type of machine I described in #299055) with
Debian Installer RC 3.
On Tue, Apr 05, 2005 at 10:12:39AM +0200, Sven Luther wrote:
On Tue, Apr 05, 2005 at 05:04:20PM +0900, Horms wrote:
[snip]
Are there debian machines that are suitable for doing such a build
should the need arise? It seems that if it is just a matter of running
a build and watching bugs,
Processing commands for [EMAIL PROTECTED]:
reassign 296963 kernel-source-2.6.8
Bug#296963: USB mouse continuously disconnecting
Bug reassigned from package `kernel-image-2.6.10-1-k7' to `kernel-source-2.6.8'.
reassign 303652 kernel-source-2.6.8
Bug#303652: USB mouse continuously disconnecting
reassign 296963 kernel-source-2.6.8
reassign 303652 kernel-source-2.6.8
reassign 303653 kernel-source-2.6.8
merge 296963 303652 303653
thanks
The bug almost certainly lies in the source code, which is
contained in kernel-source-2.6.8, lets track it there
rather than fragmenting the bug report.
Hi Ted,
It seems that I missunderstood the preferences expressed
by Steve Langasek in my discussions with him. As it turns
out he feels that it would be best to get 0.37-2 ready,
as 0.37-1 is currently in sarge and has been beaten upon
by users quite a bit. This should mittigate most of
the need
49 matches
Mail list logo
