Sorry for the long mail, but i believe there is something important all the
way done, so if you cannot be bothered to read it all; please go down to the
point marked *IMPORTANT*.
On Tue, Jan 03, 2006 at 10:05:04PM -0800, Steve Langasek wrote:
You have been harranguing the ftp team to approve new
On Wed, Jan 04, 2006 at 08:58:09AM +0100, Andreas Barth wrote:
well, the kernel is definitly about the same level as the toolchain and
standard/base - changes can have very easily impact on the installer,
and it is not an option to remove the package if it is broken.
Nope, still it is more in
Package: linux-source-2.6.15
Version: 2.6.15-1
Severity: wishlist
Hi,
It's not really a bug report.
Using the same .config, I can compile the linux bcm43xx driver (
ftp://ftp.berlios.de/pub/bcm43xx/snapshots/ ) for vanilla kernel 2.6.15. But
the compilation fails for debian kernel source.
Best
Am Dienstag, 3. Januar 2006 23:24 schrieb [EMAIL PROTECTED]:
On Tue, Jan 03, 2006 at 08:09:45PM +0100, David Schmitt wrote:
Could you please retest this with a current linux image?
I'm on self built kernel-image-2.6.14 and everything seems OK.
(Same burner but different, freshly formated
bingo. that fixed it. so is this a yaird bug? or is it piix's fault?--garrett
try to use initramfs-tools?dma should work out of the box.--maks
Package: linux-2.6
Version: 2.6.15
When using make module_install with the makefile that comes with the kernel
(/lib/modules/2.6.15-1-686/build/Makefile) modules are not installed into
the correct location in /lib/modules. They build fine but are then installed
to /lib/modules/2.6.15 instead
On Wed, Jan 04, 2006 at 01:29:52AM -0800, Garrett Mclean wrote:
bingo. that fixed it. so is this a yaird bug? or is it piix's fault?
I believe it is an ide-generic / piix bug, which initramfs-tools works around,
and yaird tries to work around but fails. I don't believe the workaround is
the
On Wed, Jan 04, 2006 at 09:39:48AM +, Richard Burton wrote:
Package: linux-2.6
Version: 2.6.15
When using make module_install with the makefile that comes with the kernel
(/lib/modules/2.6.15-1-686/build/Makefile) modules are not installed into
the correct location in /lib/modules.
Congratulations, you are the first to file a bug report against linux
2.6.15 :)
Yay ;-)
Could you tell us exactly what you do to build the module, and check if
this
is not a bug in m-a or your module ?
The official recomended way of building modules is to build inside the
module
tree
On Wed, Jan 04, 2006 at 10:50:19AM +, Richard Burton wrote:
Congratulations, you are the first to file a bug report against linux
2.6.15 :)
Yay ;-)
Could you tell us exactly what you do to build the module, and check if
this
is not a bug in m-a or your module ?
The official
Package: linux-image-2.6.15-1-686
Version: 2.6.15-1
Severity: grave
Setting up linux-image-2.6.15-1-686 (2.6.15-1) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
initrd.img(/boot/initrd.img-2.6.15-1-686) points to
/boot/initrd.img-2.6.15-1-686
KDIR := /lib/modules/$(KVER)/build
modules: $(patsubst %.o,%.c,$(TP_MODULES))
$(MAKE) -C $(KDIR) M=$(PWD) modules
...
install: modules
rm -f /lib/modules/$(KVER)/kernel/$(MDIR)/{tp_base,tp_smapi}.ko
$(MAKE) -C $(KDIR) M=$(PWD) modules_install
We use $(MAKE)
* Sven Luther
| I believe it has also an influence on the place where the source package is
| ohold (alioth svn repo over whatever strange stuff ubuntu uses), and they said
| we should use their system.
yeah, git, really strange stuff in the world of Linux kernel
development. Available from
On Wed, Jan 04, 2006 at 11:40:25AM +, Richard Burton wrote:
KDIR := /lib/modules/$(KVER)/build
modules: $(patsubst %.o,%.c,$(TP_MODULES))
$(MAKE) -C $(KDIR) M=$(PWD) modules
...
install: modules
rm -f /lib/modules/$(KVER)/kernel/$(MDIR)/{tp_base,tp_smapi}.ko
On Wed, Jan 04, 2006 at 12:39:09PM +0100, Tollef Fog Heen wrote:
* Sven Luther
| I believe it has also an influence on the place where the source package is
| ohold (alioth svn repo over whatever strange stuff ubuntu uses), and they
said
| we should use their system.
yeah, git, really
also sprach Brian Nelson [EMAIL PROTECTED] [2006.01.04.0043 +0100]:
Why don't we use RHEL's kernel, or collaborate with them to maintain a
stable kernel tree, or something?
I doubt RH has the same concept of stability as we do, and I surely
don't want a plethora of potentially untested or buggy
[EMAIL PROTECTED] wrote:
OK, I've attached the requested information. I still have 2.6.14-2,
though, I can resubmit when .15 arrives.
2.6.15-1-686-smp just arrived. New outputs attached.
H
Linux version 2.6.15-1-686-smp (Debian 2.6.15-1) ([EMAIL PROTECTED]) (gcc
version 4.0.3 20051201
On Wed, Jan 04, 2006 at 12:23:31AM -0200, Felipe Augusto van de Wiel (faw)
wrote:
Perhaps the idea of maintain a kernel with other distros is not bad,
if Ubuntu shows up as a candidate, I would like to add Progeny, Linspire,
Xandros, DCC Alliance Fan Club and also other Debian
Calling 'make -C /lib/modules/2.6.15-1-686/build kernelrelease' shows
the
kernel release as 2.6.15, but shouldn't this show 2.6.15-1-686, (which
is
defined for UTS_RELEASE in version.h)?
can you give the output of :
dpkg -l | grep linux-header
[EMAIL PROTECTED]:~$ dpkg -l | grep
On Wed, Jan 04, 2006 at 01:51:17PM +0100, Gabor Gombas wrote:
snipp
Packaging at least -rc kernels for unstable might be a good idea for
Debian too. That would provide more testing coverage for -rc releases,
and this is what upstream needs the most.
the -rc kernels are build in experimental,
Package: initramfs-tools
Version: 0.47.1
Severity: grave
Justification: renders package unusable
Hi,
After upgrade my system and installing a new kernel my system would fail while
booting because the initramfs image was missing the klibc library.
The last version of libklibc has moved the
Maximilian Attems wrote:
severity 343686 normal
tags 343686 moreinfo
tags 343686 unreproducible
stop
downgrading severity as kernel-package doesn't yet build with debsums.
can you please tell how you hooked debsums into your image?
perhaps you are invoking debsums in apt's post install
* Gabor Gombas wrote:
Packaging at least -rc kernels for unstable might be a good idea for
Debian too. That would provide more testing coverage for -rc releases,
and this is what upstream needs the most.
We already had some -rc releases in experimental for 2.6.14 and
2.6.15.
Norbert
--
To
hello luk!
On Wed, Jan 04, 2006 at 09:50:15PM +0800, LUK ShunTim wrote:
This is triggered when I try to use reportbug to report a kernel bug.
ok reportbug checks if there are debsums for a packet,
currently we don't add them so i'm still curious where do you get them
from?
please post the
tags 345949 pending
stop
On Wed, Jan 04, 2006 at 02:41:45PM +0100, Arjan Oosting wrote:
Hi,
After upgrade my system and installing a new kernel my system would fail
while
booting because the initramfs image was missing the klibc library.
The last version of libklibc has moved the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 4 Jan 2006 15:28:04 +0100
Maximilian Attems [EMAIL PROTECTED] wrote:
On Wed, Jan 04, 2006 at 09:50:15PM +0800, LUK ShunTim wrote:
This is triggered when I try to use reportbug to report a kernel
bug.
ok reportbug checks if there
On Wed, Jan 04, 2006 at 03:19:47PM +0100, Maximilian Attems wrote:
indeed sorry for the trouble.
why on earth did my test work, anyway fix will be uploaded soonest.
as quick workaround install libklibc-dev,
then current initramfs-tools work too.
--
maks
--
To UNSUBSCRIBE, email to
initramfs-tools_0.48_i386.changes uploaded successfully to localhost
along with the files:
initramfs-tools_0.48.dsc
initramfs-tools_0.48.tar.gz
initramfs-tools_0.48_all.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
priority 345864 important
reassign 345864 linux-image-2.6-14-2-686
thanks
This one time, at band camp, Marco d'Itri said:
On Jan 04, Stephen Gran [EMAIL PROTECTED] wrote:
Marco, can you take a look at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345864 and see what you
think?
Blame
Hi David,
On Mon, Jan 02, 2006 at 09:19:45PM +0100, David Schmitt wrote:
Hi Florian!
Can you reproduce the problem with a current kernel (testing: 2.6.12,
unstable: 2.6.14)?
well, things have changed a little bit, but just a bit...
using either kernel, I now get an error message with
On Wed, Jan 04, 2006 at 02:26:51PM +0100, Maximilian Attems wrote:
the -rc kernels are build in experimental, staging area for unstable
and without any potential d-i breakage.
Ah, nice, I did not notice it. Perhaps it should get some more publicity
to attract more testers :-)
Gabor
--
On 1/4/06, Marco d'Itri [EMAIL PROTECTED] wrote:
On Jan 04, Stephen Gran [EMAIL PROTECTED] wrote:
Marco, can you take a look at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345864 and see what you
think?
Blame the kernel. When the event is sent, the drive is supposed to be
ready to
tags 345918 confirmed
thanks
I've reproduced that problem locally and will have a look at it tonight.
Best regards,
Jurij Smakov[EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--
To UNSUBSCRIBE, email to [EMAIL
On Wed, Jan 04, 2006 at 09:56:29AM -0800, Jurij Smakov wrote:
tags 345918 confirmed
thanks
I've reproduced that problem locally and will have a look at it tonight.
I think Bastian blank also investigated, and it may (or not) be fixed in SVN.
Friendly,
Sven Luther
--
To UNSUBSCRIBE,
On Wed, Jan 04, 2006 at 01:11:00PM -0500, Joey Hess wrote:
Sven Luther wrote:
For the installer, sure, but the generation of the d-i kernel .udebs is only
marginally of their relevance, and furthermore they don't want the
responsability associated with it, and as proof i can show you that
I'm trying to upgrade my Debian sarge 3.1 kernel 2.4 to the 2.6. Using
aptitude install kernel-image-xx.xx.xxx when I rebooted the system hung at the
prompt of sbin/init:432: cannot open dev/console: no such file.
I then used a knoppix 4.0 cd to boot from and mounted the root partition and
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
Nathanael Nerode wrote:
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
On Thu, Jan 05, 2006 at 12:34:06AM +0100, Cesare Leonardi wrote:
Nathanael Nerode wrote:
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
Sven Luther wrote:
It would be great if you could confirm the exact version of those two
packages, and could provide us some log of what is happening, as this bug
report doesn't seem to be very informative.
For me, i have provided information in bug #344767, as i explained in
the previous
I'm attempting to upgrade Debian 3.1 kernel version 2.4 to the latest 2.6
version. I understand I need to add a initrd command somewhere in this. How
do I pass this command and when (a link to a document would be a big help).
Thanks
Jon
On Thu, 2006-01-05 at 10:12 +0800, Jon Miller wrote:
I'm attempting to upgrade Debian 3.1 kernel version 2.4 to the latest 2.6
version. I understand I need to add a initrd command somewhere in this. How
do I pass this command and when (a link to a document would be a big help).
Thanks
Cesare Leonardi wrote:
I haven't tested 2.6.15 because it isn't available in my mirror yet. But
the Nathanael posts tell us that the problem is still present in the
latest kernel.
As soon as it will be available on the mirror i use, i'll test 2.6.15.
Ok, 2.6.15 is arrived.
I've tryed to
Hi,
I've looked at this bug and it appears that nothing is wrong with
linux-headers. Nothing is wrong in that case means that we did not
introduce any bugs compared to the previous versions, I've verified that
zaptel driver behaves the same way under 2.6.14.
It appears that most of the
Max:
maximilian attems wrote:
use initramfs-tools this shouldn't fail:
apt-get install initramfs-tools
add to /etc/kernel-img.conf
ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd
good luck ;)
I patched up my /etc/lvm/lvm.config and now the kernel package installs
clean. It
Max:
maximilian attems wrote:
use initramfs-tools this shouldn't fail:
apt-get install initramfs-tools
add to /etc/kernel-img.conf
ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd
good luck ;)
One other thing. When I try to --purge the package, I get this:
# dpkg --purge
On Thu, Jan 05, 2006 at 03:51:54AM +0100, Cesare Leonardi wrote:
Cesare Leonardi wrote:
I haven't tested 2.6.15 because it isn't available in my mirror yet. But
the Nathanael posts tell us that the problem is still present in the
latest kernel.
As soon as it will be available on the mirror
On Thu, Jan 05, 2006 at 10:12:06AM +0800, Jon Miller wrote:
I'm attempting to upgrade Debian 3.1 kernel version 2.4 to the latest 2.6
version. I understand I need to add a initrd command somewhere in this. How
do I pass this command and when (a link to a document would be a big help).
On Wed, Jan 04, 2006 at 10:58:43PM -0600, Bill Gatliff wrote:
Max:
maximilian attems wrote:
use initramfs-tools this shouldn't fail:
apt-get install initramfs-tools
add to /etc/kernel-img.conf
ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd
good luck ;)
One other thing.
On Wed, Jan 04, 2006 at 10:58:43PM -0600, Bill Gatliff wrote:
Max:
maximilian attems wrote:
use initramfs-tools this shouldn't fail:
apt-get install initramfs-tools
add to /etc/kernel-img.conf
ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd
good luck ;)
One other thing.
reassign 344767 grub
thanks
On Thu, Jan 05, 2006 at 01:19:17AM +0100, Cesare Leonardi wrote:
Sven Luther wrote:
It would be great if you could confirm the exact version of those two
packages, and could provide us some log of what is happening, as this bug
report doesn't seem to be very
On Wed, Jan 04, 2006 at 08:30:11PM -0800, Jurij Smakov wrote:
Hi,
I've looked at this bug and it appears that nothing is wrong with
linux-headers. Nothing is wrong in that case means that we did not
introduce any bugs compared to the previous versions, I've verified that
zaptel driver
On Thu, Jan 05, 2006 at 01:19:17AM +0100, Cesare Leonardi wrote:
Sven Luther wrote:
It would be great if you could confirm the exact version of those two
packages, and could provide us some log of what is happening, as this bug
report doesn't seem to be very informative.
For me, i have
53 matches
Mail list logo