On Sat, Aug 14, 2004 at 07:37:27PM -0600, dann frazier wrote:
> On Sat, Aug 14, 2004 at 12:28:59PM -0600, dann frazier wrote:
> > On Fri, Aug 13, 2004 at 03:08:45PM +0100, Matthew Wilcox wrote:
> > > I think you're mistaken. The known bug in the DV scsi core was fixed
> > > 9 weeks ago (according
Rejected: kernel-image-2.4-586tsc_2.4.26-6_i386.deb: old version (2.4.27-1) in
unstable >= new version (2.4.26-6) targeted at unstable.
Rejected: kernel-image-2.4-686_2.4.26-6_i386.deb: old version (2.4.27-1) in
unstable >= new version (2.4.26-6) targeted at unstable.
Rejected: kernel-pcmcia-mod
Accepted:
kernel-doc-2.4.26_2.4.26-6_all.deb
to pool/main/k/kernel-source-2.4.26/kernel-doc-2.4.26_2.4.26-6_all.deb
kernel-patch-debian-2.4.26_2.4.26-6_all.deb
to
pool/main/k/kernel-source-2.4.26/kernel-patch-debian-2.4.26_2.4.26-6_all.deb
kernel-source-2.4.26_2.4.26-6.diff.gz
to pool/main/
kernel-image-2.4.26-i386_2.4.26-6_i386.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.4.26-i386_2.4.26-6.dsc
kernel-image-2.4.26-i386_2.4.26-6.tar.gz
kernel-headers-2.4.26-1_2.4.26-6_i386.deb
kernel-pcmcia-modules-2.4.26-1-386_2.4.26-6_i386.deb
kernel-ima
kernel-source-2.4.26_2.4.26-6_i386.changes uploaded successfully to localhost
along with the files:
kernel-source-2.4.26_2.4.26-6.dsc
kernel-source-2.4.26_2.4.26-6.diff.gz
kernel-patch-debian-2.4.26_2.4.26-6_all.deb
kernel-tree-2.4.26_2.4.26-6_all.deb
kernel-doc-2.4.26_2.4.26-6_all.deb
tags 266882 + woody security
Security Team, what is going on with respect to updating 2.4.18 in
woody? There are numerous CAN entries outstanding.
On Thu, Aug 19, 2004 at 04:37:05PM +0200, boud wrote:
> Package: kernel-source-2.4.18
> Version: 2.4.18-14.3
> Severity: important
>
>
>
> -- Syste
(new) kernel-build-2.6.8-1_2.6.8-1_sparc.deb optional devel
Headers for building modules for Linux 2.6.8
This package provides kernel header files for building modules for the
precompiled kernel images on the 64-bit SPARC architecture (uniprocessor and
multiprocessor.)
(new) kernel-headers-2.6.8
kernel-image-2.6.8-sparc_2.6.8-1_sparc.changes uploaded successfully to
localhost
along with the files:
kernel-image-2.6.8-sparc_2.6.8-1.dsc
kernel-image-2.6.8-sparc_2.6.8-1.tar.gz
kernel-headers-2.6.8-1_2.6.8-1_sparc.deb
kernel-image-2.6-sparc64_2.6.8-1_sparc.deb
kernel-headers-2.6.8-1-
Hi,
I have uploaded kernel-source 2.4.26-6 and
kernel-image i386 2.4.26-6 to debian.org.
There was a minor change over the previous
test packages posted to this list with regards to
some symbol problems in the tg3 dirver
which I was able to test myself.
A complete changelog can be found at
http:
On Thu, Aug 19, 2004 at 10:16:31AM -0400, Andres Salomon wrote:
> On Thu, 19 Aug 2004 12:56:08 +0900, Horms wrote:
>
> > Hi,
> >
> > I am wondering what the reaction to uploading a p4-smp kernel
> > for kernel-image-2.4.26-i386 would be. This would allow hyperthreading
> > to be enabled on p4 pro
Your message dated Thu, 19 Aug 2004 21:47:58 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#262870: fixed in kernel-source-2.4.26 2.4.26-6
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 cas
Your message dated Thu, 19 Aug 2004 21:47:58 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#264202: fixed in kernel-source-2.4.26 2.4.26-6
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 cas
there's a lot of work still to be done: it's mostly a reverse
engineering effort from scratch because rtl won't say how the chip
works.
the 8211 chips is also used in one of the mini wireless boxes so
yes they will at some time.
On Thu, Aug 19, 2004 at 06:41:13PM +0200, Christoph Hellwig wrote:
On Thu, Aug 19, 2004 at 08:34:23PM +0200, Frodo Looijaard wrote:
> On Thu, Aug 19, 2004 at 12:24:09PM +0900, Horms wrote:
> > On Tue, Aug 17, 2004 at 10:11:14PM +0200, Frodo Looijaard wrote:
>
> > > When compiling 2.4.27 I get some unresolved symbols in the tg3 driver:
> > >
> > > depmod:
On Wed, Aug 18, 2004 at 12:16:04AM +0200, Christoph Hellwig wrote:
> On Wed, Aug 18, 2004 at 01:13:08AM +0300, Shaul Karl wrote:
> > On Tue, Aug 17, 2004 at 04:02:32PM +0200, Christoph Hellwig wrote:
> > > On Tue, Aug 17, 2004 at 02:17:11PM +0300, Shaul Karl wrote:
> > > > The description of kern
On Thu, Aug 19, 2004 at 06:37:13PM -0400, Bharath Ramesh wrote:
> I have 2.6.7 kernel on my Compaq laptop. I compiled the ndiswrapper
> downloading from sourcforge. But whenever I try to run ifup on my device
> I get a Kernel Panic. I am attaching the a part of the kernel messages
> when it panics.
I have 2.6.7 kernel on my Compaq laptop. I compiled the ndiswrapper
downloading from sourcforge. But whenever I try to run ifup on my device
I get a Kernel Panic. I am attaching the a part of the kernel messages
when it panics. Any help on this is appreciated. I am not subsribed to
this list, pleas
reassign 266954 cdrecord
merge 266912 266954
thanks
On Thu, Aug 19, 2004 at 11:26:04PM +0200, Jean-Luc Coulon (f5ibh) wrote:
> Package: kernel-source-2.6.8
> Version: 2.6.8-2
> Severity: normal
>
> Hi,
>
> I use a CD burner with cdrecord and the ATAPI transport.
> with 2.6.7 (as well as previous
Processing commands for [EMAIL PROTECTED]:
> reassign 266954 cdrecord
Bug#266954: kernel-source-2.6.8: breaks usage of cdrecord with non root user
Bug reassigned from package `kernel-source-2.6.8' to `cdrecord'.
> merge 266912 266954
Bug#266912: kernel-image-2.6.8: Kernel 2.6.8 breaks DVD-Writing
Package: kernel-source-2.4.18
Version: 2.4.18-14.3
Severity: important
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux adjani 2.4.18 #1 Fri Aug 6 14:11:00 CEST 2004 i686
Locale: LANG=pl_PL.ISO-8859-2, LC_CTYPE=pl_PL.ISO-8859-2
Versions of packages kernel-source-2.4.18
Package: kernel-source-2.6.8
Version: 2.6.8-2
Severity: normal
Hi,
I use a CD burner with cdrecord and the ATAPI transport.
with 2.6.7 (as well as previous releases), it was possible to burn a CD with
a non root user.
With 2.6.8, I've an "operation non permitted" message. If I boot my
backup 2.
Package: kernel-source-2.4.26
Version: 2.4.26-5
Severity: important
Justification: fails to build from source
CONFIG_PARPORT_PC and CONFIG_PARPORT works without problems.
Adding CONFIG_PARPORT_SERIAL=y triggers the problem:
# make dep && bzImage
[ lots of inappropriate messages ]
drivers/parpor
Frederik Schueler <[EMAIL PROTECTED]> writes:
> Hi,
>
> in order to have at least a minimal support for amd64 in sarge, we need
> a sponsor to upload kernel-image-2.6.7-amd64 2.6.7-6, built on a i386
> host with gcc 3.4.1-6 (hitting the archive tonight).
Thats gcc 3.4.1-7 (will be superceeded by
Len Brown (ACPI) maintainer pointed me to the final fix for this in
Linus' BK tree. I'll add it to out tree.
package: kernel-image-2.6.8-1-686-smp
Just upgraded from 2.6.7-1-686-smp, and I get the following error
messages during boot. From dmesg:
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
hw_random: RNG not detected
ichxrom ichxrom_init_one(): Unable to register resource
0xff00-0xff
Hi,
in order to have at least a minimal support for amd64 in sarge, we need
a sponsor to upload kernel-image-2.6.7-amd64 2.6.7-6, built on a i386
host with gcc 3.4.1-6 (hitting the archive tonight).
With that kernel image available, users can run 64bit binaries on their
i386 debian system, usin
Your message dated Thu, 19 Aug 2004 20:52:59 +0200
with message-id <[EMAIL PROTECTED]>
and subject line (no subject)
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 responsibility to reo
Do you have an url to the original patch and any discussio it triggered?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Workaround:
Disable "Build Adapter firmware Kernel Build"
(CONFIG_AIC7xxx_BUILD_FIRMWARE) and the problem is gone.
(Tried with kernel 2.6.7 build from package kernel-source-2.6.7)
- --
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux
On Thu, Aug 19, 2004 at 12:24:09PM +0900, Horms wrote:
> On Tue, Aug 17, 2004 at 10:11:14PM +0200, Frodo Looijaard wrote:
> > When compiling 2.4.27 I get some unresolved symbols in the tg3 driver:
> >
> > depmod: release_firmware_R33934162
> > depmod: request_firmware_R38c
Processing commands for [EMAIL PROTECTED]:
> reassign 255199 initrd-tools
Bug#255199: missing files
Bug reassigned from package `kernel' to `initrd-tools'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debia
reassign 266912 crerecord
thanks
2.6.8 fixed a security issue in the SG_IO interface. cdrecord needs a
patch to not drop privilegues after opening the device file.
On Thu, Aug 19, 2004 at 08:04:59PM +0200, Sven Luther wrote:
> kernel developer consensus seems to be that this is not a kernel bug, but a
> bug in the userland. Christoph, do you think we should split this bug report
> and fill it against cdrecord or all other CD burning packages ?
I've reassign
Processing commands for [EMAIL PROTECTED]:
> reassign 266912 crerecord
Bug#266912: kernel-image-2.6.8: Kernel 2.6.8 breaks DVD-Writing
Warning: Unknown package 'crerecord'
Bug reassigned from package `kernel-image-2.6.8-1-686' to `crerecord'.
> thanks
Stopping processing here.
Please contact me
On Thu, Aug 19, 2004 at 07:16:49PM +0200, Andreas Neudecker wrote:
> Package: kernel-image-2.6.8-1-686
> Version: 2.6.8-1
> Severity: normal
> File: kernel-image-2.6.8
>
> After upgrading to kernel 2.6.8 I could suddenly not burn DVDs any more.
> On the homepage of 'K3B', my buring tool, I found a
Package: kernel-image-2.6.8-1-686
Version: 2.6.8-1
Severity: normal
File: kernel-image-2.6.8
After upgrading to kernel 2.6.8 I could suddenly not burn DVDs any more.
On the homepage of 'K3B', my buring tool, I found a note saying that
actually a new bug in the kernel prevents this from working. An
Your message dated Thu, 19 Aug 2004 18:55:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line not reproducible
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 responsibility to
does this still happen with 2.6.8?
Processing commands for [EMAIL PROTECTED]:
> severity 258043 wishlist
Bug#258043: kernel-patch-debian-2.6.7: doesn't list which patches are
incorporated: kernel-patch-debian-2.6.7, kernel-image-2.6.7: doesn't list which
patches are incorporated
Severity set to `wishlist'.
> thanks
Stopping proc
Your message dated Thu, 19 Aug 2004 18:38:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line #257624 Ritek usb-pen does not work with kernel >= 2.6.5
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 t
severity 261684 wishlist
tags 261684 +wontfix
thanks
If you want the driver included please tell the author to submit it
upstream. From looking at the code this will need significant polishing
to meet the kernel code quality guidelines.
Well, you normally shouldn't rebuild firmware. I don't want to add a
depency for kernel-source on one of the berkely-db -dev packages because
unless you turn on this mostly useless option you don't need it.
Processing commands for [EMAIL PROTECTED]:
> severity 261684 wishlist
Bug#261684: kernel-image-2.6: GPL version of Wireless Driver for ADM8211 chips
available (belkin etc)
Severity set to `wishlist'.
> tags 261684 +wontfix
Bug#261684: kernel-image-2.6: GPL version of Wireless Driver for ADM8211
Your message dated Thu, 19 Aug 2004 18:26:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line (no subject)
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 responsibility to reo
reassign 259901 initrd-tools
thanks
MD autodetection only works when the MD driver is built into the kernel,
but we buil it modularly. For this and other reasons kernel-level
autodection is strongly deprecated by the upstream MD maintainer.
I'm a bit surprised mkinitrd doesn't perform the nessec
Processing commands for [EMAIL PROTECTED]:
> reassign 259901 initrd-tools
Bug#259901: kernel does not like persistent superblocks
Bug reassigned from package `kernel' to `initrd-tools'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system admin
Your message dated Thu, 19 Aug 2004 18:06:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line kernel doesn't do persistant device naming
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
This looks like a missing initrd to me. Can you please post the full
dmesg?
Does this still happen with 2.6.8?
retitle 260163 no APM BIOS found on some notebook
thanks
As Matthew said this has nothing to do with CONFIG_EMBEDDED.
Does 2.4 find an apm bios? If yes can you please post dmesg output
for a kernel that does find it and one that does not.
If you don't have any kernel that finds and APM bios your
Processing commands for [EMAIL PROTECTED]:
> retitle 260163 no APM BIOS found on some notebook
Bug#260163: kernel: CONFIG_EMBEDDED=y blocks APM
Changed Bug title.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
debian-kernel team,
I'm not sure if people are interested in hearing about users'
feelings about 2.6.8, (or the right place to send this), but aside from
all the reasons discussed here, I _really_ want to see 2.6.8 in sarge.
2.6.8 includes proper lvm snapshot support (most importantly,
in
I talked to David Woodhous (MTD maintainer) and he said the mtd drivers
that deal with bios flash should better be disabled in distro kernels,
these drivers are:
CONFIG_MTD_AMD76XROM
CONFIG_MTD_ICHXROM
CONFIG_MTD_SCB2_FLASH
CONFIG_MTD_TSUNAMI
CONFIG_MTD_L440GX
On Thu, Aug 19, 2004 at 05:17:21PM +0200, Louis-David Mitterrand wrote:
> Package: kernel-source-2.6.8
> Version: 2.6.8-2
> Severity: important
> Tags: patch
>
> A kernel panic is triggered when loading fiaif with htb scheduler
> support.
>
> Please see attached message from lkml with patch for d
Processing commands for [EMAIL PROTECTED]:
> reassign 262715 initrd-tools
Bug#262715: kernel: Setting up kernel-image-2.4.18-1-686-smp (2.4.18-13.1)
fails with / being on LVM
Bug reassigned from package `kernel' to `initrd-tools'.
>
End of message, stopping processing here.
Please contact me if
Processing commands for [EMAIL PROTECTED]:
> tags 262715 +woody
Bug#262715: kernel: Setting up kernel-image-2.4.18-1-686-smp (2.4.18-13.1)
fails with / being on LVM
There were no tags set.
Tags added: woody
>
End of message, stopping processing here.
Please contact me if you need assistance.
D
Package: kernel-source-2.6.8
Version: 2.6.8-2
Severity: important
Tags: patch
A kernel panic is triggered when loading fiaif with htb scheduler
support.
Please see attached message from lkml with patch for details.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy:
On Thu, Aug 19, 2004 at 07:54:27AM -0700, Matt Zimmerman wrote:
> Is it possible to have ACPI disabled in the kernel until acpid starts, and
> enable it then? Or must this decision be made very early in the boot
> process?
Back at Caldera we hacked acpi to be a loadable module. These days it's
n
hi,
My apologies if this is a naive question, but it seems to me
that the bug admin system may have a bug, since on the page:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=pkg&data=kernel&archive=no
as well as on
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kernel&archive=yes
i find
Is it possible to have ACPI disabled in the kernel until acpid starts, and
enable it then? Or must this decision be made very early in the boot
process?
--
- mdz
Sven Luther wrote:
[snip]
> > 2.6 cobalt needs AFAIK some further porting work as well. I plan to do
> > kernel-patch-2.6.8-mips post sarge, and hope the cobalt support is good
> > enough by then.
>
> Just a question, why post-sarge ? Apart from not enough time or such, is there
> technical reason
On Thu, 19 Aug 2004 12:56:08 +0900, Horms wrote:
> Hi,
>
> I am wondering what the reaction to uploading a p4-smp kernel
> for kernel-image-2.4.26-i386 would be. This would allow hyperthreading
> to be enabled on p4 processors that support it. I can also supply
> a suitable patch to debian-instal
On Thu, Aug 19, 2004 at 02:45:49PM +0200, Thiemo Seufer wrote:
> severity 266839 wishlist
> thanks
>
> Wouter van Reeven wrote:
> > Package: kernel-source-2.6.7
> > Version: 2.6.7-4
> >
> > After downloading the kernel-source package I unzipped and untarred it.
> > Then I ran make menuconfig and
severity 266839 wishlist
thanks
Wouter van Reeven wrote:
> Package: kernel-source-2.6.7
> Version: 2.6.7-4
>
> After downloading the kernel-source package I unzipped and untarred it.
> Then I ran make menuconfig and checked and verified the correct
> architecture and machine specs were loaded. Th
Processing commands for [EMAIL PROTECTED]:
> severity 266839 wishlist
Bug#266839: Error while compiling mips kernel 2.6.7 on Cobalt Qube2
Severity set to `wishlist'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administra
Package: kernel-source-2.6.7
Version: 2.6.7-4
After downloading the kernel-source package I unzipped and untarred it.
Then I ran make menuconfig and checked and verified the correct
architecture and machine specs were loaded. Then I quit with saving
changes.
Next I ran "make" which exited with thi
short summary:
* ~10mb changes from 2.6.7 to 2.6.8
* to about 70% that's bugfixes
* cd writing is broken both in 2.6.7 and 2.6.8 in different ways
* told since almost a month that the debian kernel team really wanted
to have 2.6.8 for sarge.
* as do the folks at redhat and suse that are at 2..8
Horms wrote:
On Tue, Aug 17, 2004 at 11:48:36AM +0200, Helmut Toplitzer wrote:
Package: kernel-source-2.4.26
Version: 2.4.26-5
Compiling the kernel for a stable-System with the enclosed kernel.config
results in a kernel-oops after loading the SMART2 drivers.
Mainline Kernel is working without probl
Helllo,
I'm experiencing the same problem (no DMA set, unable to set after with
hdparm)
on computers with Intel IDE 82801BA IDE U100 chipset ; the piix module is
loaded but
don't appear as usual in /proc/ide/ ...
Fred.
Hello,
I've tried the 2.4.27-2 kernel on two computers with USB2 interfaces (an
Intel ICH4 and
a VIA) and the kernel do an oops and a kernel panic when trying to load USB2
driver (ehci-hdc)
[bug #266621]. The problem is that When you need USB (like USB
keyboards...), the USB2 interface
d
Hello,
It looks like due to a few ugly bugs with sparc assembly and a tg3.c
typo, it's looking like we'll need a kernel-source-2.4.27-4 soon.
Currently I'm not quite sure if tg3 will work with the firmware, due to
a stray & that caused an invalid pointer type warning.
For the rest, this revision
71 matches
Mail list logo
