ndom_yarrow;
/* Then go looking for hardware */
#if defined(__i386__) && !defined(PC98)
if (via_feature_rng & VIA_HAS_RNG) {
*systat = random_nehemiah;
}
#endif
}
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debia
On 28/12/2013 18:29, David Suárez wrote:
>> /usr/include/x86_64-linux-gnu/sys/elf.h:22:3: error: #error This header is
>> unsupported on x86-64.
>> # error This header is unsupported on x86-64.
If is not supported on amd64, why is this header even present?
--
Robe
detected,
>> unless hw.nehemiah_rng_enable or hw.ivy_rng_enable are set to zero
>> to disable them.
>
> Remove, switch to kfreebsd 10. Either that, or backport the fix from
> kfreebsd 10.
I tend to favour removal. Releasing with two kernels is a PITA.
What does everyone else t
Forwarding to the other lists from original thread...
Original Message
Subject: Re: Fwd: possible /dev/random compromise (misplaced trust in RDRAND /
Padlock entropy sources)
Date: Sun, 15 Dec 2013 20:53:19 +0100
From: Yves-Alexis Perez
To: Robert Millan
CC: t
(sid):
All versions in Debian already have the fixed code, which replaces
random_adaptor_register() with live_entropy_source_register(), thereby
registering Via and Intel chips as "entropy sources" to be post
processed by Yarrow, rather than directly as &
2011/7/29 Moritz Mühlenhoff :
> We already asked you back in September 2009 to report this upstream.
He did, precisely in September 2009:
https://bugzilla.kernel.org/show_bug.cgi?id=14186
He still got no response though.
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-kernel-r
2011/6/18 Jonathan Nieder :
> Hi Robert,
>
> Robert Millan wrote:
>
>> When it comes to __attibute__((__unused__)), it's just a matter of
>> agreeing on whether to call it __attribute_unused__ or __unused.
>
> I don't agree. It's perfectly fine f
ersuade
Drepper to remove __unused from Glibc or Linux developers to remove
__unused from Linux.
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.o
Package: linux-image-2.6.38-2-loongson-2f
Version: 2.6.38-5
Severity: wishlist
Please Recommend libc6-loongson2f (see #601419).
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU c
Package: initramfs-tools
Version: 0.92o
Severity: normal
The "smc911x" in /usr/share/initramfs-tools/hook-functions looks like a typo.
I think it should be smc91x:
http://packages.debian.org/lenny/armel/linux-image-2.6.26-2-versatile/filelist
(or at least smc91x should be present in the list)
501153)
> - typhoon (closes: #502669)
Better late than never. Thanks.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your dat
packaged separately?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
--
To UNSUBSCRIBE, emai
you.
Thanks for considering,
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
--
To UNSUBSCRI
tags 494010 patch
thanks
Hi,
I'm attaching a patch for building the dsp56k firmware from source.
Note: the dsp56k_bootstrap.asm in this patch includes fixes provided separately
(and explained) in this bug log. I will send them to upstream as well.
--
Robert Millan
The DRM opt-in fa
Hi,
I just uploaded the a56 package. I'll provide a patch for this bug soon.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove yo
On Fri, Oct 17, 2008 at 08:45:06AM +0200, Robert Millan wrote:
>
> I can live without knowing why the code needs to run in that address; but
> I'm still puzzled by how is the code supposed to tell the assembler that the
> 0x7ea9 chunk really should be saved to 0x4f. We can&#
compiling the firmware used in Linux' dsp56k.c driver.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at
On Thu, Oct 16, 2008 at 04:50:11PM +0200, Robert Millan wrote:
>
> Ok, fixed that. I got a 100% code match now. The only remaining question is
> what's the deal with this section that's supposed to start at 0x7ea9 but
> actually starts at 0x4f (0xed in the file). My code
a9 but
actually starts at 0x4f (0xed in the file). My code adds a workaround for
that:
if (offset > 0x7000)
offset -= 0x7e5a;
which is really nasty. Anyone knows better?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you
> assemble.
I found an assembler, "a56" (see http://www.zdomain.com/a56.html), which seems
to be DFSG-free (BSD-style license). I'll see about packaging it.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may acces
. AFAICT this is for an m68k
processor. I suppose we have a command to assemble this code in
binutils-multiarch or so?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: w
Package: linux-2.6
Version: 2.6.26-5
Severity: serious
Hi,
drivers/net/tehuti_fw.h (licensed under GPLv2+) is entirely composed of
binary firmware, such as:
static u32 s_firmLoad[] = {
0x000f0002,
0x40718000,
[...]
Since this file is licensed under GPL, this could make i
Package: linux-2.6
Version: 2.6.26-5
Severity: serious
Hi,
drivers/net/starfire_firmware.h (licensed under GPLv2) is entirely composed
of binary firmware, such as:
static const u32 firmware_rx[] = {
0x010003dc, 0x,
0x04000421, 0x0086,
[...]
It's worth noting that the last chun
Package: linux-2.6
Version: 2.6.26-5
Severity: serious
Hi,
drivers/net/cassini.h (licensed under GPLv2+) contains two chunks of
binary firmware, such as:
/* firmware patch for NS_DP83065 */
typedef struct cas_saturn_patch {
u16 addr;
u16 val;
} cas_saturn_patch_t;
#if 1
cas_satu
It's unfortunate that we couldn't had a reasonable discussion over this. I
swear I tried.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you
low redistribution, shipping it is not illegal
> > but
> > is a DFSG violation.
>
> why?
DFSG #2.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom:
respect this flagging
I'd have to see the details, but I'm not very fond of the extra burden
this could mean to bootloader maintainers.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's thre
if someone has more information about them, and whether they have been
fixed or not (Nathanael mentions in the bug log that he was going to try).
Or, if someone has access to the affected hardware and can test things, I'd
like to know about that too.
Thanks
--
Robert Millan
The DRM o
On Sat, Aug 09, 2008 at 02:29:31PM +0200, Bastian Blank wrote:
> On Sat, Aug 09, 2008 at 01:18:10PM +0200, Robert Millan wrote:
> > I'll be working on a patch for this one today.
>
> Some advices:
> - Please make a minimal fix. As the firmwares are fix-only it may just
Hi,
I'll be working on a patch for this one today.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not a
On Fri, Aug 08, 2008 at 04:03:32PM +0200, Frederik Schueler wrote:
> Hi,
>
> I already waited for this.
>
> On Fri, Aug 08, 2008 at 12:21:45PM +, Robert Millan wrote:
> > drivers/net/e100.c (licensed under GPLv2) contains three chunks of binary
> > firmware, s
Package: linux-2.6
Version: 2.6.26-2
Severity: serious
Hi,
drivers/net/e100.c (licensed under GPLv2) contains three chunks of binary
firmware, such as:
//
/* Micro code for 8086:1229 Rev 8 */
/*
DFSG interpretation; -kernel sounds like the right place to
discuss a specific application of that interpretation, once a consensus is
built on it. -release does AFAICT have nothing to do with either of these
things.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We wil
wishlist bug... but we don't need to
spend time nitpicking about such things.
I'll proceed my inspection, and exclude problems that appear to fall in the
cathegory of "small chunk of non-code" from being filed as bugs.
Thanks,
--
Robert Millan
The DRM opt-in fallacy: &qu
nel; I think
it'd be good if you participate in the discussion in that thread:
http://lists.debian.org/debian-kernel/2008/08/msg00112.html
> than by unilaterally declaring them to be release-critical
> bugs.
As usual, my assesment of severities is "best-effort". If a severity is
stuff and are now full of confusion and (fortunately) closed.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access
Package: linux-2.6
Version: 2.6.26-1
Severity: serious
Hi,
drivers/media/dvb/frontends/tda8083.c (licensed under GPLv2+) contains a small
chunk of binary code:
static u8 tda8083_init_tab [] = {
0x04, 0x00, 0x4a, 0x79, 0x04, 0x00, 0xff, 0xea,
0x48, 0x42, 0x79, 0x60, 0x70, 0x52, 0x
Package: linux-2.6
Version: 2.6.26-1
Severity: serious
Hi,
drivers/char/drm/mga_ucode.h is entirely composed of binary code:
RegDesc script[] = {
[...]
There's no copyright header in this file. The comments say it's been
generated from "AF05BDA.sys (windows driver)", but they don't sp
Package: linux-2.6
Version: 2.6.26-1
Severity: serious
Hi,
drivers/media/dvb/frontends/tda10021.c (licensed under GPLv2+) contains a
small chunk of binary code:
static u8 tda10021_inittab[0x40]=
{
0x73, 0x6a, 0x23, 0x0a, 0x02, 0x37, 0x77, 0x1a,
0x37, 0x6a, 0x17, 0x8a, 0x1e, 0x86,
On Wed, Aug 06, 2008 at 08:16:44PM +0200, Robert Millan wrote:
> >
> > If you think one of the remaining firmwares is licensed in a way not
> > acceptable for main, please send in tested patches against the driver in
> > linux-2.6 fixing it to request the firmwar
es and (most specialy!) finding the hardware to test them.
My concern here is different (less important IMO, but still significant): Would
the release have to be delayed in case this approach is taken?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when
technically challenging to provide this solution, but if
you feel like help is needed, I'm willing to contribute to archieve it.
Thanks for listening
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nob
Package: linux-2.6
Version: 2.6.26-1
Severity: serious
Hi,
drivers/char/dsp56k.c (licensed under GPL2) includes a small section of
binary code:
/* DSP56001 bootstrap code */
static char bootstrap[] = {
0x0c, 0x00, 0x40, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
[...]
Since the l
Package: linux-2.6
Version: 2.6.26-1
Severity: serious
drivers/char/drm/radeon_microcode.h (licensed under BSD-style terms) is entirely
composed of binary code, such as:
/* production radeon ucode r1xx-r6xx */
static const u32 R100_cp_microcode[][2] = {
{ 0x21007000, 00 },
{ 0x200
Package: linux-2.6
Version: 2.6.26-1
Severity: serious
Hi,
drivers/char/drm/r128_cce.c (licensed under BSD-style terms) contains a small
buffer with code in binary form:
/* CCE microcode (from ATI) */
static u32 r128_cce_microcode[] = {
[...]
As per the comment, it appears to be copyrig
Package: linux-2.6
Version: 2.6.26-1
Severity: serious
Hi,
Now that it seems clear 2.6.26 will be the version used for the release, I'd
like to bring back attention on pruning it from code under DFSG violation,
GPL-incompatible, or unlicensed blobs.
Based on maks mail in:
http://bugs.debian.o
objections, of course).
--
Robert Millan
I know my rights; I want my phone call!
What good is a phone call… if you are unable to speak?
(as seen on /.)
http://www.gossamer-threads.com/lists/linux/kernel/936294
>From 23a46157c15badacb23332abb8f489a515d7733f Mon Sep 17 00:00:00 2001
Fro
Hi,
Any comments on this one?
--
Robert Millan
I know my rights; I want my phone call!
What good is a phone call… if you are unable to speak?
(as seen on /.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ing the default root parameter, before grub 0.97-40 migrates to testing
(if that is the case, I suggest you file an RC bug to stop it).
OTOH, I expect this will significantly reduce very common problems like the
one described in #475958.
[1] I mean initramfs-tools maintainers
--
Robert Millan
I
Package: linux-2.6
Version: 2.6.26~rc4-1~experimental.1
Severity: normal
This diff was extracted from OLPC branch. Without it, MMC cards are not
detected.
I'm not setting the patch tag since the last hunks look like a kludge
(specially the off-by-one thing).
Putting Andres Salomon on CC, as he
ware:
16K mmc/card/sdio_uart.ko
16K mmc/host/mmc_spi.ko
8,0Kmmc/host/ricoh_mmc.ko
16K mmc/host/tifm_sd.ko
20K mmc/host/wbsd.ko
Thanks
--
Robert Millan
I know my rights; I want my phone call!
What good is a phone call… if you are unable to speak?
(as seen on /.)
--
To U
GOANY supports OLPC
Previously, one would have to specifically choose CONFIG_OLPC and
CONFIG_PCI_GOOLPC in order to enable PCI_OLPC. That doesn't really work
for distro kernels, so this patch allows one to choose CONFIG_OLPC and
CONFIG_PCI_GOANY in order to build in OLPC support in a generic kernel
Package: initramfs-tools
Version: 0.85h
Severity: normal
Tags: patch
Please include drivers for mtd and mmc devices, to make it possible setting
up a root filesystem in them.
Patch attached.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architectur
iolations right now that need fixing?
>
> What does it gain to close the bug that contains the history of the
> problem ?
My guess is that this makes it easier to track the problems, by closing stuff
in changelog when a partial fix is done.
--
Robert Millan
I know my rights; I wa
On Sat, May 17, 2008 at 09:13:34AM +0200, Sven Luther wrote:
> On Sat, May 17, 2008 at 12:30:58AM +0200, Robert Millan wrote:
> > On Sat, May 17, 2008 at 12:03:39AM +0200, Robert Millan wrote:
> > > On Fri, May 16, 2008 at 08:31:40PM +0300, Markus Laire wrote:
> > > >
On Sat, May 17, 2008 at 12:03:39AM +0200, Robert Millan wrote:
> On Fri, May 16, 2008 at 08:31:40PM +0300, Markus Laire wrote:
> >
> > I'm not a maintainer, but I did have info that bug had not been
> > dealt with, so I reopened the bug with that info.
>
> I see
in the bug log.
I suggest you re-send it.
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call… if you are unable to speak?
(as seen on /.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
retitle 462529 please enable PS3 support in -powerpc64 build
thanks
On Thu, May 15, 2008 at 04:46:10PM +0200, Sven Luther wrote:
> On Thu, May 15, 2008 at 04:25:40PM +0200, Robert Millan wrote:
> >
> > Please provide a patch if you can.
>
> I already provided a patch, which
e provide a patch if you can.
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call… if you are unable to speak?
(as seen on /.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: linux-image-2.6.25-2-powerpc-miboot
Version: 2.6.25-2
Severity: grave
According to the description, this build is intended to be used with floppy
images. However, it doesn't seem to fit on a floppy. From:
http://people.debian.org/~wouter/d-i/powerpc-miboot/20080512-06:18/build_power
Package: linux-2.6
Severity: normal
Tags: patch
The UDF driver doesn't support revision 2.50, which is commonly used in
blu-ray disks.
A patch is available at:
http://sourceforge.net/tracker/?group_id=295&atid=300295
(I tested the 2.6.25rc1 one with linux-2.6-2.6.25 from debian)
and is in
On Thu, May 08, 2008 at 10:56:53PM +0200, maximilian attems wrote:
> On Wed, 09 Jan 2008, Robert Millan wrote:
>
> >
> > Sorry for the delay in repliing, but I was expecting a proper solution could
> > be found. Right now I find the situation hopeless.
>
>
lding, and how could one help getting it done.
Thanks!
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call… if you are unable to speak?
(as seen on /.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
mage
(because of this bug). Aurelien, does this address your concern wrt
removing the extra modules from kernel image?
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call… if you are unable to speak?
(as seen on /.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
rt.
I can ping this bug when it's done if you want.
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call… if you are unable to speak?
(as seen on /.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hp
Perhaps it's better to wait untill D-I support is complete (soon, I expect),
although in the end there's no way to avoid a short timeframe in which this
hack doesn't work.
So maybe the best would be to wait for current package to propagate to testing
instead?
Not a big deal anyw
Package: linux-image-2.6.24-1-versatile
Version: 2.6.24-4
Severity: normal
The following modules are built into the core image and
probably shouldn't be:
scsi_mod
sd_mod
ext3
ext2
jbd
SMC91X driver (don't know the module name, but config option is CONFIG_SMC91X)
-- System Information:
Debian Rel
h, ironicaly, was the arch whose requirements couldn't be specified
correctly (and still aren't).
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call… if you are unable to speak?
(as seen on /.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
. Perhaps it'd be a good idea
to document it or leave it open + wontfix or similar, so that others can
avoid (some of) the hassle.
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call, if you are unable to speak?
(as seen on /.)
--
To UNSUBSCRIBE, email to
On Wed, Dec 12, 2007 at 02:45:11PM +0100, Robert Millan wrote:
> Package: linux-2.6
> Severity: wishlist
> Tags: patch
>
> It seems that ADMtek ADM8515 chips report broken USB IDs under certain
> conditions. When I plug my usb-ethernet adaptor before the computer is
>
Package: linux-2.6
Severity: wishlist
Tags: patch
It seems that ADMtek ADM8515 chips report broken USB IDs under certain
conditions. When I plug my usb-ethernet adaptor before the computer is
powered on, it often reports a broken ID; at which point unplugging/replugging
would solve it.
I reprodu
nesday 12 September 2007 15:37, Robert Millan wrote:
> > > There isn't any patch that should be required here. There is already a
> > > script in the kernel team repo to be used for pruning non-free firmware
> > > from the tarball, and it appears that whoever produce
that actually degrade
> the user experience?
No, choosing what to spend your time on is every volunteer's option. You get
to spend your time ranting about this just like Nathanael gets to spend his
time ranting about that.
And I get to send a mail saying obvious things. Everyone is hap
t in the kernel team repo to be used for pruning non-free firmware from
> the tarball, and it appears that whoever produced the initial uploads of
> 2.6.21 and 2.6.22 for Debian omitted this step.
Why not running this script in debian/rules, causing builds to abort when the
non-free files a
tersection of
i386 arch and amd64 flavour has to be disabled (without disabling amd64,
that is), so I left i386 disabled for now.
--
Robert Millan
I know my rights; I want my phone call!
What use is a phone call, if you are unable to speak?
(as seen on /.)
diff -Nur -x debian linux-modu
On Mon, Aug 20, 2007 at 08:24:18AM +0200, Robert Millan wrote:
> > In the meanwhile try to use the generic vesa driver to see if the
> > crashes still happens. If they will not occur anymore, you can try with
> > the intel driver from unstable or experimental.
Btw, tried the
On Mon, Aug 20, 2007 at 12:21:12AM +0200, Cesare Leonardi wrote:
> Robert Millan wrote:
> >I've recently upgraded my hardware (motherboard + cpu + ram) and am now
> >getting Linux crashes in a variety of situations. I've detected them
> >when any of t
Package: linux-image-2.6.18-5-amd64
Version: 2.6.18.dfsg.1-13etch1
Severity: important
I've recently upgraded my hardware (motherboard + cpu + ram) and am now
getting Linux crashes in a variety of situations. I've detected them
when any of the following conditions are met:
- When starting a se
On Tue, Jul 24, 2007 at 08:13:33PM +0200, Daniel Baumann wrote:
> Robert Millan [ackstorm] wrote:
> > Ok, but #433525 seems to be a blocker for this. Will you include that fix
> > in next kqemu-source upload?
>
> the patch seems flawed, it did not build at all once i ap
ded...
Ok, but #433525 seems to be a blocker for this. Will you include that fix
in next kqemu-source upload?
--
Robert Millan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: linux-modules-extra-2.6
Severity: wishlist
Tags: patch
Attached patch adds kqemu modules.
Note: kqemu-source needed fixes to get this building, check its BTS entry.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
tags 401006 fixed-upstream
thanks
#401006: mm/msync leading to filesystem corruption
This has been fixed in Linux 2.6.19.2.
--
Robert Millan
My spam trap is [EMAIL PROTECTED] Note: this address is only intended for
spam harvesters. Writing to it will get you added to my black list.
--
To
compatibility with older filesystems? I think the
following options will do:
CONFIG_SQUASHFS_1_0_COMPATIBILITY
CONFIG_SQUASHFS_2_0_COMPATIBILITY
Thanks!
--
Robert Millan
ACK STORM, S.L. - http://www.ackstorm.es/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: linux-2.6
Severity: wishlist
Tags: patch
Please could you include BadRAM patch ? I missed it *a lot* when my RAM blew
up and I couldn't boot the system from disk or d-i CD because they all hang. :)
http://rick.vanrein.org/linux/badram/
Thanks!
-- System Information:
Debian Release:
Package: linux-image-2.6.17-2-k7
Severity: normal
Tags: patch
I've verified this image supports Sempron (in fact, 32-bit sempron can do up to
-march=athlon-xp). Could you add it to the description?
--- linux-2.6-2.6.17/debian/arch/i386/defines~ 2006-08-26 13:18:05.0
+0200
+++ linux-2.6
tags 384318 wontfix
thanks
On Wed, Aug 23, 2006 at 08:03:41PM +0200, Martin Michlmayr wrote:
> * Robert Millan <[EMAIL PROTECTED]> [2006-08-23 19:28]:
> > > fyi, the plan is to move etch to 2.6.17, so linux-2.6.16 will probably
> > > not be updated much, if at al
On Wed, Aug 23, 2006 at 11:11:48AM -0600, dann frazier wrote:
> On Wed, Aug 23, 2006 at 03:19:50PM +0200, Robert Millan wrote:
> > Package: linux-2.6.16
> > Severity: normal
> >
> > It seems that all OSS drivers have been disabled in this version. 2.6.17
> > bro
Package: linux-2.6.16
Severity: normal
It seems that all OSS drivers have been disabled in this version. 2.6.17
brought them back, but they're still missing in 2.6.16. Please could you
reenable them?
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (50
Package: kernel-image-2.6.8-3-686
Version: 2.6.8-16sarge3
Severity: critical
Tags: security
See: http://lists.grok.org.uk/pipermail/full-disclosure/2006-July/047907.html
Workaround is simple: mount /proc as nosuid
The linux-2.6 packages in unstable are not affected (since they don't include
a.ou
On Tue, Jun 20, 2006 at 11:46:36AM +0200, Frans Pop wrote:
> On Tuesday 20 June 2006 10:55, Robert Millan [ackstorm] wrote:
> > Upgrading from kernel-image-2.4.27-3-686 to linux-image-2.6.15-1-686
> > might break boot if /dev/hdb becomes /dev/sda. As fstab and menu.lst
> >
this? Or at least gracefuly
report that the root param is wrong (currently it just hangs on "Waiting for
root device").
--
Robert Millan
[EMAIL PROTECTED]
Departamento de Asistencia Técnica
Oficina central: (+34) 902 888 345
Asistencia técnica: (+34) 902 888 408
ACK STORM, S.L.
http://
tags 318120 patch
thanks
Hi,
It seems someone sent a patch for this bug, but it wasn't CCed to the BTS and
remained unnoticed:
http://lists.debian.org/debian-kernel/2006/04/msg00445.html
I've tested it and seems to work fine.
--
Robert Millan
[EMAIL PROTECTED]
Departamento de
On Wed, Oct 06, 2004 at 08:20:13AM +0200, maks attems wrote:
> > Then please reopen and add wontfix tags. Note, however, that #272063 and
> > #272067 (specialy #272067) are unrelated to the first one and a refusal from
> > the team to fix #272029 doesn't imply a refusal to fix the latter. I would
[ Delayed due to MTA problems ]
On Wed, Sep 29, 2004 at 06:53:52PM +0200, maks attems wrote:
> On Wed, 29 Sep 2004, Robert Millan wrote:
> > On Wed, Sep 29, 2004 at 05:36:30PM +0200, maks attems wrote:
> >
> > Have you read the bug reports? I haven't sent ANY patch fo
FYI.
The POSIX Test Suite is a free (as in speech) test suite with the goal of
performing conformance, functional, and stress testing of the IEEE
1003.1-2001 System Interfaces specification in a manner that is agnostic to
any given implementation.
On Fri, Oct 01, 2004 at 11:09:54PM -0400, De
On Wed, Sep 29, 2004 at 05:36:30PM +0200, maks attems wrote:
> retitle 272029 add xbox support to debians kernel
> thanks
>
> [...]
>
> well so keep 1 "bug" not 3.
> retitled, and i'll close the other 2.
Have you read the bug reports? I haven't sent ANY patch for Xbox support.
Why do you close
On Sat, Sep 25, 2004 at 12:16:55PM +0900, Horms wrote:
> tag 272029 +wontfix
>
> > It's not fixed. Add a wontfix and/or upstream tags if you like.
>
> This is not a bug in the kernel.
> It is a random feature request.
It is a wishlist request and is perfectly legitimate.
> We have offered the
reopen 272029
thanks
On Thu, Sep 23, 2004 at 10:03:06PM -0700, Debian Bug Tracking System wrote:
> On Wed, Sep 22, 2004 at 12:31:37PM +0100, Matthew Wilcox wrote:
> > On Wed, Sep 22, 2004 at 06:25:23PM +0900, Horms wrote:
> > > On Sun, Sep 19, 2004 at 09:21:12AM +0200, R
reassign 271269 kernel
thanks
Good point, although this bug doesn't belong to grub. I'm reassigning it..
On Sun, Sep 12, 2004 at 12:23:32PM +0300, Martin-?ric Racine wrote:
> Package: grub
> Severity: important
>
> I have been wondering for a long time why the menu.lst gets automatically
> upd
On Fri, Sep 17, 2004 at 08:38:56AM +0200, Christoph Hellwig wrote:
> tags 272029 +upstream
> thanks
>
> Please get feature-patches merged upstream before bugging us, thanks.
Upstream rejected them untill they're "a lot more commonly used", which can
also be read as "supported in major distributio
1 - 100 of 109 matches
Mail list logo
