Re: pending linux-2.6 changes

2006-04-04 Thread Jurij Smakov
On Tue, 4 Apr 2006, Bastian Blank wrote: - sparc headers packages lacks sparc64 headers, who is responsible for sparc? That should be fixed by the commit 6370. I'm running the test build now. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www

Bug#360773: linux-image-2.6.16-1-686: p4-clockmod does not work anymore

2006-04-04 Thread Giuseppe D'Angelo
On Tue, 4 Apr 2006, Mattia Dongili wrote: can you try acpi_cpufreq with 2.6.16? I don't remember where I read p4_clockmod refuses to load on some chips in favour of acpi_cpufreq. It didn't work: alien:~# uname -a Linux alien 2.6.16-1-686 #1 Mon Apr 3 12:53:40 UTC 2006 i686 GNU/Linux alien:~#

Bug#360681: marked as done (kernel: NIC: Unknow symbol mii_*)

2006-04-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 Apr 2006 22:37:12 +0200 with message-id <[EMAIL PROTECTED]> and subject line kernel: NIC: Unknow symbol mii_* 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 r

Bug#360809: kernel: SCSI emulation for SATA drives fails on NVIDIA-2 chip sets

2006-04-04 Thread Frank J Niertit
Package: kernel Version: N/A; reported 2006-04-04 Severity: important Unable to recognize SATA drives on NVIDIA-2 chip sets if SCSI emulation is turned on. Recompiling the kernel without SCSI support recognizes the drives as /dev/hd?. The same drives are recognized and mapped to SCSI drives under

Bug#360773: linux-image-2.6.16-1-686: p4-clockmod does not work anymore

2006-04-04 Thread Mattia Dongili
On Tue, Apr 04, 2006 at 05:49:45PM +0200, Giuseppe D'Angelo wrote: > Package: linux-image-2.6.16-1-686 > Version: 2.6.16-5 > Severity: normal > > Hi. After upgrading to a 2.6.16 kernel the module p4-clockmod doesn't > work anymore: > > # modprobe p4-clockmod > FATAL: Error inserting p4_clockmod

Re: Backports of linux-2.6 and dependencies

2006-04-04 Thread Kilian Krause
Hey Bastian, > To implement this solution, we need help from both the backport and the kernel > team: we need autobuilders and we need someone for every arch to verify and > approve the packages for the archive. as I was on the kernel-archive team since the first minute, sure you can count me in

Re: Modules packaging policy - call for discussion

2006-04-04 Thread Eduard Bloch
#include * Jurij Smakov [Tue, Apr 04 2006, 09:34:29AM]: > On Tue, 4 Apr 2006, Bastian Blank wrote: > > >On Mon, Apr 03, 2006 at 10:37:43PM -0700, Jurij Smakov wrote: > > > >There is already one available on > >svn://svn.debian.org/pkg-voip/zaptel-modules/trunk/debian. > >or > >http://svn.debian.o

Re: Backports of linux-2.6 and dependencies

2006-04-04 Thread Norbert Tretkowski
* Bastian Blank wrote: > The backports.org archive carries current versions of most needed > packages to run new kernels on Sarge but some of them (eg > initramfs-tools) are outdated, That's because backports.org is based on testing, not unstable. It's the same reason why 2.6.16 isn't available o

Re: Modules packaging policy - call for discussion

2006-04-04 Thread Jurij Smakov
On Tue, 4 Apr 2006, Bastian Blank wrote: On Mon, Apr 03, 2006 at 10:37:43PM -0700, Jurij Smakov wrote: There is already one available on svn://svn.debian.org/pkg-voip/zaptel-modules/trunk/debian. or http://svn.debian.org/wsvn/pkg-voip/zaptel-modules/trunk/debian/ Great! I'll have a look, than

Bug#360773: linux-image-2.6.16-1-686: p4-clockmod does not work anymore

2006-04-04 Thread Giuseppe D'Angelo
Package: linux-image-2.6.16-1-686 Version: 2.6.16-5 Severity: normal Hi. After upgrading to a 2.6.16 kernel the module p4-clockmod doesn't work anymore: # modprobe p4-clockmod FATAL: Error inserting p4_clockmod (/lib/modules/2.6.16-1-686/kernel/arch/i386/kernel/cpu/cpufreq/p4-clockmod.ko): No su

Bug#360758: linux-image-2.6.16-1-vserver-k7: module binary incompatibility between 2.6.16-4 and 2.6.16-5 ?

2006-04-04 Thread Bastian Blank
tags 360758 confirmed thanks On Tue, Apr 04, 2006 at 03:48:38PM +0200, Andreas Beckmann wrote: > After upgrading linux-image-2.6.16-1-vserver-k7 from 2.6.16-4 to 2.6.16-5 > I had to rebuild the third party modules. I checked the changes and found a change in a core structure of the vserver suppor

Processed: Re: Bug#360758: linux-image-2.6.16-1-vserver-k7: module binary incompatibility between 2.6.16-4 and 2.6.16-5 ?

2006-04-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 360758 confirmed Bug#360758: linux-image-2.6.16-1-vserver-k7: module binary incompatibility between 2.6.16-4 and 2.6.16-5 ? There were no tags set. Tags added: confirmed > thanks Stopping processing here. Please contact me if you need assistance

Backports of linux-2.6 and dependencies

2006-04-04 Thread Bastian Blank
Hi folks As requested and discussed several times since the release of Sarge, we are planning to provide a complete solution for the issue of outdated kernels in Sarge. The backports.org archive carries current versions of most needed packages to run new kernels on Sarge but some of them (eg init

Bug#360763: linux-image-2.6.16-1-vserver-686: No description of what "vserver" is

2006-04-04 Thread Daniel Schepler
Package: linux-image-2.6.16-1-vserver-686 Version: 2.6.16-5 Severity: minor As the subject says: the package description of linux-image-2.6.16-1-vserver-686 is exactly the same as the package description of linux-image-2.6.16-1-686, giving no indication of what's different in the vserver packag

Bug#360758: linux-image-2.6.16-1-vserver-k7: module binary incompatibility between 2.6.16-4 and 2.6.16-5 ?

2006-04-04 Thread Andreas Beckmann
Package: linux-image-2.6.16-1-vserver-k7 Version: 2.6.16-5 Severity: normal After upgrading linux-image-2.6.16-1-vserver-k7 from 2.6.16-4 to 2.6.16-5 I had to rebuild the third party modules. Errors reported when inserting the old modules were: kernel: nvidia: disagrees about version of symbo

Processed: Re: Bug#358580: linux-2.6: cannot build modules against 2.6.16

2006-04-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 358580 normal Bug#358580: linux-2.6: cannot build modules against 2.6.16 Severity set to `normal'. > reassign 358580 linux-headers-2.6.16-1-686 Bug#358580: linux-2.6: cannot build modules against 2.6.16 Bug reassigned from package `linux-2.6'

Re: pending linux-2.6 changes

2006-04-04 Thread Bastian Blank
On Fri, Mar 31, 2006 at 08:28:44PM +0200, Bastian Blank wrote: I just detected, that the modules support lacks some things. > I intend to do the following changes: - The modules source packages needs to build depend on linux-support-* as they sometimes uses makefiles from there. - The modules g

Re: pending linux-2.6 changes

2006-04-04 Thread Bastian Blank
On Mon, Apr 03, 2006 at 09:22:12PM -0700, Jurij Smakov wrote: > AFAICT, the linux-support package does not contain any arch-dependent > files. Is there a good reason why it is 'Architecture: any', and not > 'all'? Read the commit logs. It is fixed in trunk and won't be backported to sid. Bastia

Processed: Re: Bug#358580: linux-2.6: cannot build modules against 2.6.16

2006-04-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > close 358580 2.6.16-5 Bug#358580: linux-2.6: cannot build modules against 2.6.16 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 2.6.16-5, send any further explanations to Richard Antony Burton <[

Re: Modules packaging policy - call for discussion

2006-04-04 Thread Bastian Blank
On Mon, Apr 03, 2006 at 10:37:43PM -0700, Jurij Smakov wrote: > Hi, > > In the discussion I've seen so far most people tend to favor the system, > in which each individual module package builds the binary packages > matching the current kernels. Based on that I've written a very > preliminary d

Bug#353790: marked as done (linux-image-2.6.15-1-686: SATA lockups)

2006-04-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 Apr 2006 09:27:43 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug fixed in 2.6.16-1-686 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 responsi