RE: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
> -Original Message- > From: Joey Hess [mailto:[EMAIL PROTECTED] > Sent: 27 August 2004 22:59 > To: debian-release@lists.debian.org; debian-boot@lists.debian.org; > debian-kernel@lists.debian.org > Subject: Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge > > > Raphael Hertzog wrote: > > Quoting Joey Hess: > > > 15. Get ftp-master to remove kernel udebs for the old kernel version > > > from testing. This will *break* some old released install media > > > (floppy, netboot, not cdrom), but it's necessary before release. > > > > Why is this necessary ? I'm a bit worried that rc1 netinst > images do no more > > work when sarge is released ... those images are widespread due to the > > testing, and it's a pity to make them useless if we don't > really need to. > > GPL compliance mostly. > > -- > see shy jo > surely if you are not going to remove the udebs you would not remove the debs or sources either so there would be no gpl compliance problem --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.737 / Virus Database: 491 - Release Date: 11/08/2004
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
Norbert Tretkowski wrote: [snip] > > > I'm going to upload an updated kernel-image-2.4.26-alpha package next > > > weekend, please make sure you're using this one, because it'll be > > > build against kernel-source-2.4.26 2.4.26-6, which fixes some security > > > issues. > > > > ... not kernel-image-2.4.27-alpha? > > There was no final decision if we ship 2.4.27 with sarge. > > If you now build and upload linux-kernel-di-alpha 0.62 with 2.4.27, > you have to build 0.63 that downgrades linux-kernel-di-alpha back to > 2.4.26 if we don't use 2.4.27 for sarge. 0.61 can't be used for sarge > because it was built with kernel-source-2.4.26 2.4.26-2.1 which has > some security problems which were fixed later. AFAICS it would be rather something like 0.61sarge1 for sarge, and it is then independent from the decision about 2.4.27. Thiemo
initrd-tools_0.1.74_i386.changes ACCEPTED
Accepted: initrd-tools_0.1.74.dsc to pool/main/i/initrd-tools/initrd-tools_0.1.74.dsc initrd-tools_0.1.74.tar.gz to pool/main/i/initrd-tools/initrd-tools_0.1.74.tar.gz initrd-tools_0.1.74_all.deb to pool/main/i/initrd-tools/initrd-tools_0.1.74_all.deb Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian.
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
Raphael Hertzog wrote: > Quoting Joey Hess: > > 15. Get ftp-master to remove kernel udebs for the old kernel version > > from testing. This will *break* some old released install media > > (floppy, netboot, not cdrom), but it's necessary before release. > > Why is this necessary ? I'm a bit worried that rc1 netinst images do no more > work when sarge is released ... those images are widespread due to the > testing, and it's a pity to make them useless if we don't really need to. GPL compliance mostly. -- see shy jo signature.asc Description: Digital signature
Bug#267006: Bug#267014: I think it's a hardware bug
Matthew Wilcox wrote: On Fri, Aug 20, 2004 at 05:15:36PM -0700, Mike Fedyk wrote: Matthew Wilcox wrote: 32-bit PCI cards should work without problems in 64-bit slots, though. That's what I thought, but I have an Adaptec 2940UW card that causes instability reliably in 64bit pci slots. Maybe the card can't handle 66Mhz? Does 64bit pci always mean 66Mhz? Nope, 64-bit and 66-MHz are independent features. Unless the card lies (by claiming to do 66MHz when it can't), putting a 33MHz card on a 66MHz bus will simply cause the entire bus to run at 33MHz. This time the 32bit AHA-2940UW was removed, and I had a 64bit gigabit ethernet card in there that uses the ns83820 module. These oopses happened overnight on "fileserver" that is a nfs, mail, samba & ldap server. Later that day the screen kept scrolling oopses during a nfs transfer. After that the 64bit ethernet card had been removed also and the machine has been working good for a day and a half. I don't have lspci output for the card since it's not in any machines right now. Unable to handle kernel NULL pointer dereference at virtual address printing eip: c020e209 *pde = Oops: [#1] PREEMPT Modules linked in: loop smbfs appletalk nfsd exportfs af_packet autofs ipv6 nfs lockd sunrpc raid1 dm_mod capability commoncap eepro100 mii rtc ext3 jbd mbcache reiserfs sd_mod aic7xxx scsi_mod raid5 md xor unix font vesafb cfbcopyarea cfbimgblt cfbfil lrect CPU:0 EIP:0060:[]Not tainted EFLAGS: 00010246 (2.6.7-1-686) EIP is at sock_recvmsg+0x29/0xc0 eax: ebx: 0040 ecx: f6fccce0 edx: f6fd5190 esi: f6fccce0 edi: f6fd1f10 ebp: esp: f6fd1da0 ds: 007b es: 007b ss: 0068 Process named (pid: 7223, threadinfo=f6fd task=f6fd5190) Stack: f6fd1db4 f6fccce0 f6fd1f10 1000 0040 f89c368d 0001 f6f974c8 f6fd5190 0246 c0353520 f69702e0 f6970040 1f2f8547 0040 Call Trace: [] svc_sock_enqueue+0x13d/0x2b0 [sunrpc] [] tcp_send_delayed_ack+0xd6/0x100 [] recalc_task_prio+0xa8/0x1a0 [] copy_from_user+0x42/0x70 [] verify_iovec+0x3c/0xa0 [] sys_recvmsg+0x146/0x200 [] schedule_timeout+0xb5/0xc0 [] unqueue_me+0x57/0xb0 [] futex_wait+0x147/0x1a0 [] find_extend_vma+0x29/0x90 [] get_futex_key+0x42/0x190 [] update_process_times+0x44/0x50 [] update_wall_time+0x16/0x40 [] copy_from_user+0x42/0x70 [] sys_socketcall+0x25b/0x260 [] syscall_call+0x7/0xb Code: 8b 00 00 d0 00 00 00 b8 01 00 00 00 89 44 24 20 8b 9c 24 d4 <1>Unable to handle kernel NULL pointer dereference at virtual address printing eip: c020e209 *pde = Oops: [#2] PREEMPT Modules linked in: loop smbfs appletalk nfsd exportfs af_packet autofs ipv6 nfs lockd sunrpc raid1 dm_mod capability commoncap eepro100 mii rtc ext3 jbd mbcache reiserfs sd_mod aic7xxx scsi_mod raid5 md xor unix font vesafb cfbcopyarea cfbimgblt cfbfil lrect CPU:0 EIP:0060:[]Not tainted EFLAGS: 00010246 (2.6.7-1-686) EIP is at sock_recvmsg+0x29/0xc0 eax: ebx: ecx: f7fac720 edx: f7198bd0 esi: f7fac720 edi: f7983f34 ebp: esp: f7983dd0 ds: 007b es: 007b ss: 0068 Process syslogd (pid: 802, threadinfo=f7982000 task=f7198bd0) Stack: 41fac720 0065 3ccbf2ae 0001 f793c188 0010 0fff f7cc0a30 f7198bd0 f7cc0a30 f7983ea8 0010 f7983e2c f7983e4c eaf287d4 Call Trace: [] buffered_rmqueue+0xf5/0x1d0 [] schedule+0x2bb/0x4d0 [] sockfd_lookup+0x1c/0x80 [] sys_recvfrom+0xb2/0x120 [] schedule_timeout+0xb5/0xc0 [] poll_freewait+0x44/0x50 [] do_select+0x1af/0x2d0 [] sys_recv+0x33/0x40 [] sys_socketcall+0x164/0x260 [] syscall_call+0x7/0xb Code: 8b 00 00 d0 00 00 00 b8 01 00 00 00 89 44 24 20 8b 9c 24 d4 <5>statd: server localhost not responding, timed out nsm_mon_unmon: rpc failed, status=-5 lockd: cannot unmonitor 10.0.0.2
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
Quoting Joey Hess: > 15. Get ftp-master to remove kernel udebs for the old kernel version > from testing. This will *break* some old released install media > (floppy, netboot, not cdrom), but it's necessary before release. Why is this necessary ? I'm a bit worried that rc1 netinst images do no more work when sarge is released ... those images are widespread due to the testing, and it's a pity to make them useless if we don't really need to. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
* Steve Langasek wrote: > On Fri, Aug 27, 2004 at 01:26:37PM +0200, Norbert Tretkowski wrote: > > * Steve Langasek wrote: > > > I should be able to get linux-kernel-di-alpha done and uploaded by > > > Monday. > > > I'm going to upload an updated kernel-image-2.4.26-alpha package next > > weekend, please make sure you're using this one, because it'll be > > build against kernel-source-2.4.26 2.4.26-6, which fixes some security > > issues. > > ... not kernel-image-2.4.27-alpha? There was no final decision if we ship 2.4.27 with sarge. If you now build and upload linux-kernel-di-alpha 0.62 with 2.4.27, you have to build 0.63 that downgrades linux-kernel-di-alpha back to 2.4.26 if we don't use 2.4.27 for sarge. 0.61 can't be used for sarge because it was built with kernel-source-2.4.26 2.4.26-2.1 which has some security problems which were fixed later. Norbert
Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software
reassign 268392 dvd+rw-tools
tags 268392 +patch
thanks
> growisofs
> ---
> INFO: ISO-8859-15 character encoding detected by locale settings.
> Assuming ISO-8859-15 encoded filenames on source filesystem,
> use -input-charset to override.
> :-( unable to PREVENT MEDIA REMOVAL: Operation not permitted
GPCMD_PREVENT_ALLOW_MEDIUM_REMOVAL is explicitly allowed for writeable
fds. But growiso opens it for readonly. Try rebuilding ddvd+rw-tools
with the patch below - OTOH after reading through the code I wouldn't
want it to be anywhere near my computers.
--- dvd+rw-tools-5.20.4.10.8/growisofs.c~ 2004-08-27 22:35:08.400657200
+0200
+++ dvd+rw-tools-5.20.4.10.8/growisofs.c2004-08-27 22:36:33.443728688
+0200
@@ -504,10 +504,10 @@
*/
#endif
-if ((in_fd = open64 (device,O_RDONLY)) < 0)
+if ((in_fd = open64 (device,O_RDWR)) < 0)
if (!(errno == ENOMEDIUM || errno == EMEDIUMTYPE) ||
- (in_fd = open64 (device,O_RDONLY|O_NONBLOCK)) < 0)
- fprintf (stderr,":-( unable to open64(\"%s\",O_RDONLY): ",device),
+ (in_fd = open64 (device,O_RDWR|O_NONBLOCK)) < 0)
+ fprintf (stderr,":-( unable to open64(\"%s\",O_RDWR): ",device),
perror (NULL), exit (FATAL_START(errno));
#ifdef GET_REAL
@@ -521,8 +521,8 @@
if (!S_ISBLK(sb.st_mode))
{ setuid(uid);/* drop all privileges */
close (in_fd); /* reopen as mortal */
- if ((in_fd = open64 (device,O_RDONLY)) < 0)
- fprintf (stderr,":-( unable to re-open64(\"%s\",O_RDONLY): ",
+ if ((in_fd = open64 (device,O_RDWR)) < 0)
+ fprintf (stderr,":-( unable to re-open64(\"%s\",O_RDWR): ",
device),
perror (NULL), exit (FATAL_START(errno));
open_rw:
Processed: Re: Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software
Processing commands for [EMAIL PROTECTED]: > reassign 268392 dvd+rw-tools Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software Bug reassigned from package `kernel-source-2.6.8' to `dvd+rw-tools'. > tags 268392 +patch Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software Tags were: sarge sid Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processing of initrd-tools_0.1.74_i386.changes
initrd-tools_0.1.74_i386.changes uploaded successfully to localhost along with the files: initrd-tools_0.1.74.dsc initrd-tools_0.1.74.tar.gz initrd-tools_0.1.74_all.deb Greetings, Your Debian queue daemon
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
On Fri, Aug 27, 2004 at 01:26:37PM +0200, Norbert Tretkowski wrote: > * Steve Langasek wrote: > > I should be able to get linux-kernel-di-alpha done and uploaded by > > Monday. > I'm going to upload an updated kernel-image-2.4.26-alpha package next > weekend, please make sure you're using this one, because it'll be > build against kernel-source-2.4.26 2.4.26-6, which fixes some security > issues. ... not kernel-image-2.4.27-alpha? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software
2.6.8-4 makes situation better. It's working now in root-mode. User mode in k3b is still not working. One of my burners is still only recognised as reading-device and burning stops with debug message below. But this looks like a "wanted" (how strange things can be) result as I'm reading the kernel discussions... So its time for the app-developer to come up with a solution. Don't think they are happier than I. Maybe it's done by simply adding a conflict to the package. Thanks for your fast response. Cheers Helmut System --- K3b Version:0.11.14 KDE Version: 3.3.0 QT Version: 3.3.3 growisofs --- INFO: ISO-8859-15 character encoding detected by locale settings. Assuming ISO-8859-15 encoded filenames on source filesystem, use -input-charset to override. :-( unable to PREVENT MEDIA REMOVAL: Operation not permitted growisofs comand: --- /usr/bin/growisofs -Z /dev/hdc -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=dao -dvd-compat -speed=4 -gui -graft-points -volid KK -volset -appid K3B THE CD KREATOR VERSION 0.11.14 (C) 2003 SEBASTIAN TRUEG AND THE K3B TEAM -publisher -preparer K3b - Version 0.11.14 -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-heli/k3bUUtCoa.tmp -rational-rock -hide-list /tmp/kde-heli/k3b9q7A7a.tmp -joliet -hide-joliet-list /tmp/kde-heli/k3b1qQN8a.tmp -udf -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-heli/k3bxklNcc.tmp Sven Luther wrote: On Fri, Aug 27, 2004 at 03:29:53PM +0200, Toplitzer Helmut wrote: Package: kernel-source-2.6.8 Version: 2.6.8-3 Tags: sarge, sid The new kernel breaks all CD bruning software in one or another way. Tested this with K3B and its making problems even in root-only mode. Other kernel-versions (<=2.6.7) are working without problems. This seems to be at least partially fixed in kernel-source 2.6.8-4, and you should never have even seen that 2.6.8-3 package you are referencing, since it never reached any archive. Can you please try the latest kernels, and verify that this is indeed fixed for you ? Friendly, Sven Luther
Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software
Another stange thing: Comparing the disk and the data on the HD with k3b shows differences. "cmp"-ing the corresponding files in the filesystem on the DVD and local drive don't show any changes. Sven Luther wrote: On Fri, Aug 27, 2004 at 03:29:53PM +0200, Toplitzer Helmut wrote: Package: kernel-source-2.6.8 Version: 2.6.8-3 Tags: sarge, sid The new kernel breaks all CD bruning software in one or another way. Tested this with K3B and its making problems even in root-only mode. Other kernel-versions (<=2.6.7) are working without problems. This seems to be at least partially fixed in kernel-source 2.6.8-4, and you should never have even seen that 2.6.8-3 package you are referencing, since it never reached any archive. Can you please try the latest kernels, and verify that this is indeed fixed for you ? Friendly, Sven Luther
Bug#244640: marked as done (Kernel oops with GNOME)
Your message dated Fri, 27 Aug 2004 21:40:26 +0200 with message-id <[EMAIL PROTECTED]> and subject line Fixes in 2.4.27 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 reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 19 Apr 2004 08:44:40 + >From [EMAIL PROTECTED] Mon Apr 19 01:44:40 2004 Return-path: <[EMAIL PROTECTED]> Received: from postfix4-1.free.fr [213.228.0.62] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BFUOO-0007vR-00; Mon, 19 Apr 2004 01:44:40 -0700 Received: from onesicrite (lns-p19-4-82-65-253-47.adsl.proxad.net [82.65.253.47]) by postfix4-1.free.fr (Postfix) with ESMTP id C66DBDFCF4 for <[EMAIL PROTECTED]>; Mon, 19 Apr 2004 10:44:37 +0200 (CEST) Date: Mon, 19 Apr 2004 10:44:36 +0200 From: nicolas <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Kernel oops with GNOME Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; Format=Flowed; DelSp=Yes; charset=ISO-8859-15 Content-Disposition: inline X-Mailer: Balsa 2.0.16 Lines: 56 Content-Transfer-Encoding: quoted-printable Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_30,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Score: 1 Package: kernel-image-2.4.24-1-k7 Version: 2.4.24-3 For GNOME: Package: gnome-core Version: 49 It's GNOME 2.4.1 For X: Package: xserver-xfree86 Version: 4.3.0-7 System: updated Sarge (upgraded from minimal Woody) Yesterday and this morning, I wanted to change my wallpaper with =20 wmsetbg or xsetbg, they segfaulted and I got this in my log: Apr 19 07:49:26 onesicrite kernel: <1>Unable to handle kernel NULL =20 pointer dereference at virtual address Apr 19 07:49:26 onesicrite kernel: printing eip: Apr 19 07:49:26 onesicrite kernel: c0119b87 Apr 19 07:49:26 onesicrite kernel: *pde =3D Apr 19 07:49:26 onesicrite kernel: Oops: Apr 19 07:49:26 onesicrite kernel: CPU:0 Apr 19 07:49:26 onesicrite kernel: EIP:0010:[__wake_up+39/112]=20 Not tainted Apr 19 07:49:26 onesicrite kernel: EFLAGS: 00010097 Apr 19 07:49:26 onesicrite kernel: eax: 24448b53 ebx: c013f540 ecx: =20 edx: 24448b53 Apr 19 07:49:26 onesicrite kernel: esi: d71003fc edi: 0001 ebp: =20 de6a1e8c esp: de6a1e70 Apr 19 07:49:26 onesicrite kernel: ds: 0018 es: 0018 ss: 0018 Apr 19 07:49:26 onesicrite kernel: Process bouncingcow (pid: 26740, =20 stackpage=3Dde6a1000) Apr 19 07:49:26 onesicrite kernel: Stack: e615 0001 =20 0286 e0ee1580 c37a5580 d5c64580 0014 Apr 19 07:49:26 onesicrite kernel:c01bf88f c37a5580 =20 7fff e0ee1580 e780e3f7 e0ee1580 Apr 19 07:49:26 onesicrite kernel:0001 0013 de6a1ec4 =20 ddc6e780 d5c64580 ff91 0013 d71005e0 Apr 19 07:49:26 onesicrite kernel: Call Trace:[sock_def_readable=20 +95/112] [usb-uhci:__insmod_usb-uhci_O/lib/modules/2.4.24-1-k7/kernel/=20 drivers/+-1510409/128] [sys_connect+125/176] [sock_map_fd+265/352] =20 [sys_socket+61/96] Apr 19 07:49:26 onesicrite kernel: [sys_socketcall+165/608] =20 [sys_newuname+56/96] [system_call+51/56] Apr 19 07:49:26 onesicrite kernel: Apr 19 07:49:26 onesicrite kernel: Code: 8b 01 85 c7 75 19 8b 02 89 d3 =20 89 c2 0f 0d 00 39 f3 75 ea ff I tried to launch Gimp or the wallpaper GNOME applet and they crashed =20 the same way. I relaunched GNOME and X and the issue disappeared (my uptime is =20 saved). Yay! nicolas --- Received: (at 244640-done) by bugs.debian.org; 27 Aug 2004 19:40:29 + >From [EMAIL PROTECTED] Fri Aug 27 12:40:29 2004 Return-path: <[EMAIL PROTECTED]> Received: from verein.lst.de (mail.lst.de) [213.95.11.210] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C0maK-0008KT-00; Fri, 27 Aug 2004 12:40:28 -0700 Received: from verein.lst.de (localhost [127.0.0.1]) by mail.lst.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i7RJeR95000962 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <[EMAIL PROTECTED]>; Fri, 27 Aug 2004 21:40:27 +0200 Received: (from [EMAIL PROTECTED]) by verein.lst.de (8.12.3/8.12.3/Debian-6.6) id i7RJeQAC000960 for [EMAIL PROTECTED]; Fri, 27 Aug 2004 21:40:26 +0200 Date: Fri, 27 Aug 2004 21:40:26 +0200 From: Christoph Hellwig <[
For Otto's Shop Customers!
Dear customer! We updated our programs list, and now we offer you more new software items Visit our full catalog and check new software titles here: http://www.softbetterone.info/?collet With best regards, Product Manager Geoffrey Stinson
kernel-patch-powerpc-2.6.8_2.6.8-3_powerpc.changes ACCEPTED
Accepted: kernel-build-2.6.8-power3-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power3-smp_2.6.8-3_powerpc.deb kernel-build-2.6.8-power3_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power3_2.6.8-3_powerpc.deb kernel-build-2.6.8-power4-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power4-smp_2.6.8-3_powerpc.deb kernel-build-2.6.8-power4_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power4_2.6.8-3_powerpc.deb kernel-build-2.6.8-powerpc-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-powerpc-smp_2.6.8-3_powerpc.deb kernel-build-2.6.8-powerpc_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-powerpc_2.6.8-3_powerpc.deb kernel-headers-2.6.8_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-headers-2.6.8_2.6.8-3_powerpc.deb kernel-image-2.6.8-power3-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-power3-smp_2.6.8-3_powerpc.deb kernel-image-2.6.8-power3_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-power3_2.6.8-3_powerpc.deb kernel-image-2.6.8-power4-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-power4-smp_2.6.8-3_powerpc.deb kernel-image-2.6.8-power4_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-power4_2.6.8-3_powerpc.deb kernel-image-2.6.8-powerpc-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-powerpc-smp_2.6.8-3_powerpc.deb kernel-image-2.6.8-powerpc_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-powerpc_2.6.8-3_powerpc.deb kernel-image-power3-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-power3-smp_2.6.8-3_powerpc.deb kernel-image-power3_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-power3_2.6.8-3_powerpc.deb kernel-image-power4-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-power4-smp_2.6.8-3_powerpc.deb kernel-image-power4_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-power4_2.6.8-3_powerpc.deb kernel-image-powerpc-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-powerpc-smp_2.6.8-3_powerpc.deb kernel-image-powerpc_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-powerpc_2.6.8-3_powerpc.deb kernel-patch-powerpc-2.6.8_2.6.8-3.dsc to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-3.dsc kernel-patch-powerpc-2.6.8_2.6.8-3.tar.gz to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-3.tar.gz kernel-patch-powerpc-2.6.8_2.6.8-3_all.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-3_all.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 268359 Thank you for your contribution to Debian.
Processing of kernel-patch-powerpc-2.6.8_2.6.8-3_powerpc.changes
kernel-patch-powerpc-2.6.8_2.6.8-3_powerpc.changes uploaded successfully to localhost along with the files: kernel-patch-powerpc-2.6.8_2.6.8-3.dsc kernel-patch-powerpc-2.6.8_2.6.8-3.tar.gz kernel-patch-powerpc-2.6.8_2.6.8-3_all.deb kernel-headers-2.6.8_2.6.8-3_powerpc.deb kernel-image-power3_2.6.8-3_powerpc.deb kernel-image-2.6.8-power3_2.6.8-3_powerpc.deb kernel-build-2.6.8-power3_2.6.8-3_powerpc.deb kernel-image-power3-smp_2.6.8-3_powerpc.deb kernel-image-2.6.8-power3-smp_2.6.8-3_powerpc.deb kernel-build-2.6.8-power3-smp_2.6.8-3_powerpc.deb kernel-image-power4_2.6.8-3_powerpc.deb kernel-image-2.6.8-power4_2.6.8-3_powerpc.deb kernel-build-2.6.8-power4_2.6.8-3_powerpc.deb kernel-image-power4-smp_2.6.8-3_powerpc.deb kernel-image-2.6.8-power4-smp_2.6.8-3_powerpc.deb kernel-build-2.6.8-power4-smp_2.6.8-3_powerpc.deb kernel-image-powerpc_2.6.8-3_powerpc.deb kernel-image-2.6.8-powerpc_2.6.8-3_powerpc.deb kernel-build-2.6.8-powerpc_2.6.8-3_powerpc.deb kernel-image-powerpc-smp_2.6.8-3_powerpc.deb kernel-image-2.6.8-powerpc-smp_2.6.8-3_powerpc.deb kernel-build-2.6.8-powerpc-smp_2.6.8-3_powerpc.deb Greetings, Your Debian queue daemon
Re: Console corrupted during boot in 2.6.8, will it be included in Sarge?
On Fri, 2004-08-27 at 11:48, Norbert Tretkowski wrote: > * Svante Signell wrote: > > I have a problem with the 2.6.x, x>4 kernels when booting my Dell > > Inspiron 4100 laptop. When the console output during boot switches > > from 24 lines on the screen to a much higher number of lines, the > > font colors appears to be set to black on black background or the > > console is corrupted. The change of console mode is triggered by a screen blanking: The output after this starts with fsck something (for a normal boot). The messages are not able to see from the screen ouput since it scrolls away, and not all screen outputs are logged in the logfiles. > Which graphic chip is used in your Dell? lspci -v: :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (prog-if 00 [VGA]) Subsystem: Dell: Unknown device 00e4 Flags: bus master, VGA palette snoop, stepping, 66MHz, medium devsel, latency 32, IRQ 11 Memory at e000 (32-bit, prefetchable) [size=128M] I/O ports at c000 [size=256] Memory at fcff (32-bit, non-prefetchable) [size=64K] Expansion ROM at [disabled] [size=128K] Capabilities: [58] AGP version 2.0 Capabilities: [50] Power Management version 2 > > Since the release of Sarge is imminent, it would be bad if this > > happens to other people with Dell laptops. > > The default kernel for sarge is 2.4, 2.6 will be shipped too. > OK > > For now I can cope by using 2.4.x series kernels (2.4.27 is default > > I beleive) but sooner or later I will change to a 2.6-series kernel > > too. Advantages would be e.g. to have alsa and lm-sensors kernel > > modules included, without having to download them (2.4.26) or build > > them (2.4.27). > > There are precompiled modules for i2c and lm-sensors for 2.4 kernels. OK good to hear. Any alsa modules for 2.4.27? > Norbert
Bug#268359: marked as done (kernel-image-2.6.8-powerpc: Please turn off BLK_DEV_IDE_PMAC_BLINK)
Your message dated Fri, 27 Aug 2004 13:47:17 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#268359: fixed in kernel-patch-powerpc-2.6.8 2.6.8-3 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 reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 27 Aug 2004 10:41:32 + >From [EMAIL PROTECTED] Fri Aug 27 03:41:32 2004 Return-path: <[EMAIL PROTECTED]> Received: from dep.oprit.rug.nl [129.125.36.9] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C0eAm-Bn-00; Fri, 27 Aug 2004 03:41:32 -0700 Received: from client44-3.kabelA.oprit.rug.nl (GN-HE001-COM03-200-159.kabela.oprit.rug.nl [129.125.200.159]) by dep.oprit.rug.nl (8.12.10.Beta2/8.12.10.Beta2) with SMTP id i7RAf1S1003370; Fri, 27 Aug 2004 12:41:01 +0200 (MEST) Message-Id: <[EMAIL PROTECTED]> Received: by client44-3.kabelA.oprit.rug.nl (sSMTP sendmail emulation); Fri, 27 Aug 2004 12:39:49 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Siep Kroonenberg <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-image-2.6.8-powerpc: Please turn off BLK_DEV_IDE_PMAC_BLINK X-Mailer: reportbug 2.64 Date: Fri, 27 Aug 2004 12:39:49 +0200 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-7.3 required=4.0 tests=BAYES_00,HAS_PACKAGE, MSGID_FROM_MTA_HEADER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kernel-image-2.6.8-powerpc Version: 2.6.8-2 Severity: wishlist This blinking LED for hd activity gets on my nerves, and is, at least for my hardware, unnecessary since hd activity is quite audible. Alternatively, if there is an option to turn it off in a compiled kernel, include documentation for it. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.8-powerpc Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to C) Versions of packages kernel-image-2.6.8-powerpc depends on: ii initrd-tools 0.1.73 tools to create initrd image for p ii module-init-tools 3.1-pre5-5 tools for managing Linux kernel mo -- no debconf information --- Received: (at 268359-close) by bugs.debian.org; 27 Aug 2004 17:53:22 + >From [EMAIL PROTECTED] Fri Aug 27 10:53:22 2004 Return-path: <[EMAIL PROTECTED]> Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1C0kug-0008Lw-00; Fri, 27 Aug 2004 10:53:22 -0700 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1C0kon-00087E-00; Fri, 27 Aug 2004 13:47:17 -0400 From: Jens Schmalzing <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.51 $ Subject: Bug#268359: fixed in kernel-patch-powerpc-2.6.8 2.6.8-3 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Fri, 27 Aug 2004 13:47:17 -0400 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Source: kernel-patch-powerpc-2.6.8 Source-Version: 2.6.8-3 We believe that the bug you reported is fixed in the latest version of kernel-patch-powerpc-2.6.8, which is due to be installed in the Debian FTP archive: kernel-build-2.6.8-power3-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power3-smp_2.6.8-3_powerpc.deb kernel-build-2.6.8-power3_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power3_2.6.8-3_powerpc.deb kernel-build-2.6.8-power4-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power4-smp_2.6.8-3_powerpc.deb kernel-build-2.6.8-power4_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power4_2.6.8-3_powerpc.deb kernel-build-2.6.8-powerpc-smp_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-powerpc-smp_2.6.8-3_powerpc.deb kernel-build-2.6.8-powerpc_2.6.8-3_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-powerpc_2.6.8-3_powerpc.
Processed: reassign 267936 to kernel
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.4 > reassign 267936 kernel Bug#267936: INSTALL REPORT (sarge) Bug reassigned from package `installation-reports' to `kernel'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#259031: #259031 ioctl FBIOGET_CON2FBMAP: Invalid argument on CONFIG_FRAMEBUFFER_CONSOLE=m kernel
Christoph Hellwig wrote: > The FBIOGET_CON2FBMAP is only implemented for builtin framebuffer > console and isn't easily implementable for modular framebuffer console. > > If nessecary and there's enough space left on the bootdisks we could > ship a builin framebuffer console. Please start a discussion on > debian-kernel on that ASAP as all architecture maintainers need to be > involved. As far as I know, this bug only affected the 2.6.6 kernel, and is ok in 2.6.7. Been a while since I tried a 2.6.7 japanese install though. -- see shy jo signature.asc Description: Digital signature
Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software
On Fri, Aug 27, 2004 at 03:29:53PM +0200, Toplitzer Helmut wrote: > Package: kernel-source-2.6.8 > Version: 2.6.8-3 > Tags: sarge, sid > > The new kernel breaks all CD bruning software in one > or another way. Tested this with K3B and its > making problems even in root-only mode. > Other kernel-versions (<=2.6.7) are working without problems. This seems to be at least partially fixed in kernel-source 2.6.8-4, and you should never have even seen that 2.6.8-3 package you are referencing, since it never reached any archive. Can you please try the latest kernels, and verify that this is indeed fixed for you ? Friendly, Sven Luther
Bug#259031: #259031 ioctl FBIOGET_CON2FBMAP: Invalid argument on CONFIG_FRAMEBUFFER_CONSOLE=m kernel
On Fri, Aug 27, 2004 at 12:33:41PM -0400, Joey Hess wrote: > Christoph Hellwig wrote: > > The FBIOGET_CON2FBMAP is only implemented for builtin framebuffer > > console and isn't easily implementable for modular framebuffer console. > > > > If nessecary and there's enough space left on the bootdisks we could > > ship a builin framebuffer console. Please start a discussion on > > debian-kernel on that ASAP as all architecture maintainers need to be > > involved. > > As far as I know, this bug only affected the 2.6.6 kernel, and is ok in > 2.6.7. Been a while since I tried a 2.6.7 japanese install though. I've looked at 2.6.8 and the code looks like this: #ifdef CONFIG_FRAMEBUFFER_CONSOLE case FBIOGET_CON2FBMAP: if (copy_from_user(&con2fb, argp, sizeof(con2fb))) return -EFAULT; ... #endif /* CONFIG_FRAMEBUFFER_CONSOLE */
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
Sven Luther wrote:
fwiw I noticed something very like this between 2.2 and 2.4 when 2.4 was
new: 2.2 was faster on my Pentium system. I think it was a earlier
version of the same chipset.
Here are results on 2.6.7-1-k7:
/dev/hda:
Timing buffered disk reads: 108 MB in 3.02 seconds = 35.78 MB/sec
/dev/hdg:
Timing buffered disk reads: 120 MB in 3.01 seconds = 39.93 MB/sec
kowari:/etc#
Both drives are WD120 Gb (different models), hdg is on an Abit hotrod66
(promise chips).
And how much you would get in 2.4 ?
Sorry.
kowari:~# hdparm -t /dev/hd{a,g}{,}
/dev/hda:
Timing buffered disk reads: 152 MB in 3.02 seconds = 50.33 MB/sec
/dev/hda:
Timing buffered disk reads: 152 MB in 3.02 seconds = 50.33 MB/sec
/dev/hdg:
Timing buffered disk reads: 120 MB in 3.02 seconds = 39.74 MB/sec
/dev/hdg: Timing buffered disk reads: 120 MB in 3.00 seconds = 40.00 MB/sec
kowari:~# uname -r
2.4.26-1-k7
kowari:~#
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
Bug#268436: kernel-source-2.4.27: make xconfig fails
Package: kernel-source-2.4.27 Version: 2.4.27-4 Severity: normal Last release of kernel-source-2.4.27 broke make xconfig, which exit with the error: ./tkparse < ../arch/i386/config.in >> kconfig.tk drivers/net/Config.in: 274: unknown command make[1]: *** [kconfig.tk] Error 1 make[1]: Leaving directory /usr/src/kernel-source-2.4.27-poggio-nf-k7/scripts' make: *** [xconfig] Error 2 I guess tkparse does not like the line HAVE_SOME_FW_LOADER=y trying to set the value of a variable. I did not rate this grave because make menuconfig works fine. bye Giacomo -- System Information Debian Release: 3.0 Kernel Version: Linux stampace 2.4.26-poggio-nf-p4 #1 SMP lun lug 26 15:19:45 CEST 2004 i686 unknown Versions of the packages kernel-source-2.4.27 depends on: ii binutils 2.12.90.0.1-4 The GNU assembler, linker and binary utiliti ii bzip2 1.0.2-1A high-quality block-sorting file compressor ii fileutils 4.1-10 GNU file management utilities coreutils Not installed or no info
Bug#268188: a workaround...
regarding the bug report I had previously sent about serial ata modules having unresolved symbols, I narrowed down the bug and found a workaround. The problem arose with CONFIG_SCSI_SATA_VITESSE=y and all other SCSI_SATA options selected as modules, i.e. ONFIG_SCSI_SATA=y CONFIG_SCSI_SATA_SVW=m CONFIG_SCSI_SATA_PROMISE=m CONFIG_SCSI_SATA_SX4=m CONFIG_SCSI_SATA_SIL=m CONFIG_SCSI_SATA_SIS=m CONFIG_SCSI_SATA_VIA=m I then changed CONFIG_SCSI_SATA_VITESSE to build as a module as well, and the problem went away. It seems that if CONFIG_SCSI_SATA_VITESSE is built into the kernel then libata.o does not get build nor installed as a module, causing all other SCSI_SATA modules to have unresolved symbols. This should not happen, or at least it should be documented. In particular, if the problem cannot be fixed quickly I suggest to add in the README.Debian file a note saying that SCSI_SATA drivers must be either compiled _all_ as modules or _all_ into the kernel, to avoid this problem. Bye, thanks Giacomo -- _ Giacomo Mulas <[EMAIL PROTECTED]> _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _
Re: piix module in 2.4.27 doesn't work
Le Thu, 26 Aug 2004 16:47:05 +0200, Sven Luther <[EMAIL PROTECTED]> a
écrit :
> On Thu, Aug 26, 2004 at 04:17:02PM +0200, Frédéric BOITEUX wrote:
> > Le Thu, 26 Aug 2004 13:36:11 +0100, Martin Michlmayr <[EMAIL PROTECTED]> a
> > écrit :
> >
> > > * Frédéric BOITEUX <[EMAIL PROTECTED]> [2004-08-26 11:34]:
> > > > Yes, it's a known bug, see #266510 and #266538. It seems to impact
> > > > all IDE drivers (all I tested at least !) The bug remains in last
> > > > 2.4.27-4 source package...
> > >
> > > Eww, that's pretty serious. No IDE DMA means everything is dog
> > > slow... I've no idea if this is a kernel bug or something in
> > > initrd-tools... however, if we cannot find out, we should go with
> > > 2.4.26 for sarge... (hah, getting annoyed about all the .26 vs .27
> > > yet? ;-).
> > > --
> >
> > I'm agree with you ! Either you have IDE without DMA, annoying
> > to install lot of packages on the hard disk, either you don't see your
> > disks,
> > much annoying ;-P !
> > Alas, I'm not a Linux Kernel guru to know if it's a pristine kernel
> > bug or
> > related to Debian packaging...
>
Hello,
I've run some tests about the IDE / DMA problem with Debian 2.4.27 kernel,
and
I found that :
- Debian kernel 2.4.26-6 :
* ide chipsets detected correctly (piix and cmd64x on my host)
* DMA activated
* pseudo-files /proc/ide/ exist
- Debian kernel 2.4.27-2 :
* ide chipsets don't detected (no messages in dmesg, piix and cmd64x
modules are 'unused' for lsmod)
* DMA *not* activated
* pseudo-files /proc/ide/ don't exist
- pristine kernel 2.4.27 :
* ide chipsets detected correctly (piix and cmd64x on my host)
* DMA activated
* pseudo-files /proc/ide/ don't exist
- pristine kernel 2.4.28-pre2 :
* ide chipsets detected correctly (piix and cmd64x on my host)
* DMA activated
* pseudo-files /proc/ide/ don't exist
- alongside, the USB2 bug (#266621) is always present even in 2.4.28-pre2
version.
It seems that some patches of Debian kernel-source-2.4.26 (in
kernel-source-2.4.26_2.4.26-6.d
iff.gz) for ide-probe.c or ide-proc.c (and perhaps others)
has disappeared in kernel-source-2.4.27_2.4.27-4.diff.gz, and the resulting
files are a bit different :
diff kernel-source-2.4.26-2.4.26/drivers/ide/ide-probe.c
/usr/src/linux-2.4.27/drivers/ide/
1428,1432c1428
<
< ide_xlate_1024_hook = ide_xlate_1024;
< #ifdef CONFIG_BLK_DEV_IDEPCI
< ide_scan_pcibus();
< #endif /* CONFIG_BLK_DEV_IDEPCI */
---
>
1437c1433
< ide_driver_module(1);
---
> ide_xlate_1024_hook = ide_xlate_1024;
The 'ide_scan_pcibus();' call seems to have disappeared...
diff kernel-source-2.4.26-2.4.26/drivers/ide/ide-proc.c
/usr/src/linux-2.4.27/drivers/ide/
898,907d897
< static inline void create_pci_proc_entry(ide_pci_host_proc_t *p)
< {
< if (p->name == NULL || p->set != 1 || p->get_info == NULL)
< return;
<
< p->parent = proc_ide_root;
< create_proc_info_entry(p->name, 0, p->parent, p->get_info);
< p->set = 2;
< }
<
921,923d910
<
< if (proc_ide_root)
< create_pci_proc_entry(p);
947c934,939
< create_pci_proc_entry(p);
---
> if (p->name != NULL && p->set == 1 && p->get_info != NULL)
> {
> p->parent = proc_ide_root;
> create_proc_info_entry(p->name, 0, p->parent,
> p->get_info); p->set = 2;
> }
The call 'if (proc_ide_root) create_pci_proc_entry(p); ' is no more present
... Perhaps it can
explain the /proc/ide/ disparition...
My 2¢,
Fred.
Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software
close 268392 thanks Hi, Toplitzer Helmut writes: > Package: kernel-source-2.6.8 > Version: 2.6.8-3 > The new kernel breaks all CD bruning software in one or another way. Upgrade to revision 2.6.8-4. It contains a fix backported from 2.6.9-rc1. > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266089 Instead of opening a new bug, you could have reassigned that one. Regards, Jens. -- J'qbpbe, le m'en fquz pe j'qbpbe! Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
Processed: Re: Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software
Processing commands for [EMAIL PROTECTED]: > close 268392 Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Toplitzer Helmut <[EMAIL PROTECTED]> > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#268392: [kernel-source-2.6.8]: Kernel breaks CD burning software
Package: kernel-source-2.6.8 Version: 2.6.8-3 Tags: sarge, sid The new kernel breaks all CD bruning software in one or another way. Tested this with K3B and its making problems even in root-only mode. Other kernel-versions (<=2.6.7) are working without problems. See also: http://k3b.plainblack.com/index.pl/news2 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266089 etc.
For Silver's Shop Customers!
Dear customer! We updated our programs list, and now we offer you more new software items Visit our full catalog and check new software titles here: http://www.softbetterone.info/?allusive With best regards, Product Manager Victoria Riddle
Bug#268359: kernel-image-2.6.8-powerpc: Please turn off BLK_DEV_IDE_PMAC_BLINK
On Fri, Aug 27, 2004 at 01:21:21PM +0200, Jens Schmalzing wrote: > Hi, > > Siep Kroonenberg writes: > > > This blinking LED for hd activity gets on my nerves, and is, at > > least for my hardware, unnecessary since hd activity is quite > > audible. > > I feel the same about this. In fact, I wonder why it got enabled in > the first place. Because some said : please add it. > > Alternatively, if there is an option to turn it off in a compiled > > kernel, include documentation for it. > > There isn't. But it could be implemented. I will look into this. Friendly, Sven Luther
Bug#268352: 2.6.* radeonfb regression
Benh, just so you are in the loop. Friendly, Sven Luther On Fri, Aug 27, 2004 at 11:45:07AM +0200, Francesco P. Lovergine wrote: > Package: kernel > Severity: normal > > 2.4 series radeonfb (1.8-benh) works perfectly (also modular). > 2.6 series new radeonfb never worked (since 2.6.0 at least), it does not sync > here (laptop XSVGA). > After loading, fbset reports 1400x1050-60, as for the 2.4 version, but screen > is blank and stay in normal text mode 80x25. I need to switch on and back to > X in order to > see screen content again. That's for loading it modular of course, I have to > do yet test > for static version. > > :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility > M6 LY > > :01:00.0 0300: 1002:4c59 > Subsystem: 0e11:b11b > Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop+ ParErr- > Stepping+ SERR+ FastB2B+ > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > SERR- Interrupt: pin A routed to IRQ 9 > Region 0: Memory at d800 (32-bit, prefetchable) [size=128M] > Region 1: I/O ports at 2000 [size=256] > Region 2: Memory at d010 (32-bit, non-prefetchable) [size=64K] > Expansion ROM at [disabled] [size=128K] > Capabilities: > > In dmesg: > > Aug 18 19:06:41 localhost kernel: radeonfb: Retreived PLL infos from BIOS > Aug 18 19:06:41 localhost kernel: radeonfb: Reference=27.00 MHz (RefDiv=60) > Memory=166.00 Mhz, System=143.00 MHz > Aug 18 19:06:42 localhost kernel: radeonfb: Monitor 1 type LCD found > Aug 18 19:06:42 localhost kernel: radeonfb: EDID probed > Aug 18 19:06:42 localhost kernel: radeonfb: Monitor 2 type no found > Aug 18 19:06:42 localhost kernel: radeonfb: panel ID string: Samsung > LTN150P1-L02 > Aug 18 19:06:42 localhost kernel: radeonfb: detected LVDS panel size from > BIOS: 1400x1050 > Aug 18 19:06:42 localhost kernel: radeondb: BIOS provided dividers will be > used > Aug 18 19:06:42 localhost kernel: radeonfb: Power Management enabled for > Mobility chipsets > Aug 18 19:06:42 localhost kernel: radeonfb: ATI Radeon LY DDR SGRAM 32 MB > > This is with current 2.6.8 in debian, but that's true with _all_ other > previous versions (2.6.0+). > > fbset return right mode, as set in /etc/fb.modes too: > > mode "1400x1050-60" > # D: 108.003 MHz, H: 63.983 kHz, V: 60.191 Hz > geometry 1400 1050 1400 1050 8 > timings 9259 136 40 10 0 112 3 > rgba 6/0,6/0,6/0,0/0 > hsync high > vsync high > accel true > endmode > > I tried to fbset explicitly the mode after module loading too, but without > results. > I'll return results with static compiled in module when possible. > > > -- System Information: > Debian Release: 3.1 > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') > Architecture: i386 (i686) > Kernel: Linux 2.4.27-1-686 > Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] > > > -- > Francesco P. Lovergine > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Bug#258082: advansys kernel module now totally gone in 2.6.8
Seems it's been flagged broken in 2.6.8... Sigh. signature.asc Description: This is a digitally signed message part
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
On Fri, Aug 27, 2004 at 07:10:55PM +0800, John Summerfield wrote: > Sven Luther wrote: > > >>All here who have 2.4 and 2.6 kernels on ppc should try disk speed tests > >>with hdparm: I found my new Athlon (well the mobo's new, CPU's not) is > >>30% faster with the 2.4 kernel. > >> > >> > > > >Have you reported a bug report on this ? And with which 2.6 kernel was it > >? > > > > > I haven't. I planned on discussing it on debian-user first, and I > mentioned it in passing in another thread and someone else was going to > tell me what I did wrong. > > I posted further details, but there's been no response. > > The kernel is 2.6.7-1-k7; it may be a day or so before I could try 8 as > I'm on dialup and my modem's rather busy atm. > > the mobo's a Gigabyte GA-7S748-L - SiS 748 chipset, LAN. > > fwiw I noticed something very like this between 2.2 and 2.4 when 2.4 was > new: 2.2 was faster on my Pentium system. I think it was a earlier > version of the same chipset. > > Here are results on 2.6.7-1-k7: > /dev/hda: > Timing buffered disk reads: 108 MB in 3.02 seconds = 35.78 MB/sec > > /dev/hdg: > Timing buffered disk reads: 120 MB in 3.01 seconds = 39.93 MB/sec > kowari:/etc# > > Both drives are WD120 Gb (different models), hdg is on an Abit hotrod66 > (promise chips). And how much you would get in 2.4 ? > >>If something like this is true of ppc too, you wouldn't want to drop 2.4 > >>kernels. > >> > >> > > > >Well, it should be fixed instead. None of upstream (all the linux-ppc > >devleopers) have any interest left for 2.4, so there is really no sane way > >to > >keep the support going unless we do it all ourselves. > > > > > > It's worth testing; if you find no problem you have no problem:-) Well, for that i would need to reboot into 2.4, which is not practical right now. Friendly, Sven Luther
Bug#268359: kernel-image-2.6.8-powerpc: Please turn off BLK_DEV_IDE_PMAC_BLINK
Hi, Siep Kroonenberg writes: > This blinking LED for hd activity gets on my nerves, and is, at > least for my hardware, unnecessary since hd activity is quite > audible. I feel the same about this. In fact, I wonder why it got enabled in the first place. > Alternatively, if there is an option to turn it off in a compiled > kernel, include documentation for it. There isn't. Regards, Jens. -- J'qbpbe, le m'en fquz pe j'qbpbe! Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
On Fri, Aug 27, 2004 at 12:00:47PM +0200, Matthias Klose wrote: > Christoph Hellwig writes: > > On Fri, Aug 27, 2004 at 10:47:29AM +0200, Matthias Klose wrote: > > > > It will be 2.6.8. > > > > > > If you write 2.6.8, do you mean 2.6.8.1? Or is the diff to .1 included > > > in the Debian packages? I cannot find a hint and the version number is > > > misleading. > > > > Given the diff to .1 is tiny and four-digit version numbers are breaking > > lots of things (there's even rumors of breaking the nptl detection in > > glibc, but given that debian _still_ doesn't have a tls-capable > > toolchain on ppc I couldn't test it) we've decided to stay with 2.6.8. > > please make this decision explicit, document it in a prominent place, > i.e. package description, README.Debian. The changelog entries maybe ? Friendly, Sven Luther
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
Sven Luther wrote: All here who have 2.4 and 2.6 kernels on ppc should try disk speed tests with hdparm: I found my new Athlon (well the mobo's new, CPU's not) is 30% faster with the 2.4 kernel. Have you reported a bug report on this ? And with which 2.6 kernel was it ? I haven't. I planned on discussing it on debian-user first, and I mentioned it in passing in another thread and someone else was going to tell me what I did wrong. I posted further details, but there's been no response. The kernel is 2.6.7-1-k7; it may be a day or so before I could try 8 as I'm on dialup and my modem's rather busy atm. the mobo's a Gigabyte GA-7S748-L - SiS 748 chipset, LAN. fwiw I noticed something very like this between 2.2 and 2.4 when 2.4 was new: 2.2 was faster on my Pentium system. I think it was a earlier version of the same chipset. Here are results on 2.6.7-1-k7: /dev/hda: Timing buffered disk reads: 108 MB in 3.02 seconds = 35.78 MB/sec /dev/hdg: Timing buffered disk reads: 120 MB in 3.01 seconds = 39.93 MB/sec kowari:/etc# Both drives are WD120 Gb (different models), hdg is on an Abit hotrod66 (promise chips). If something like this is true of ppc too, you wouldn't want to drop 2.4 kernels. Well, it should be fixed instead. None of upstream (all the linux-ppc devleopers) have any interest left for 2.4, so there is really no sane way to keep the support going unless we do it all ourselves. It's worth testing; if you find no problem you have no problem:-) -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
* Steve Langasek wrote: > I should be able to get linux-kernel-di-alpha done and uploaded by > Monday. I'm going to upload an updated kernel-image-2.4.26-alpha package next weekend, please make sure you're using this one, because it'll be build against kernel-source-2.4.26 2.4.26-6, which fixes some security issues. Norbert
Bug#261893: kernel-image-2.6.6-1-generic: Kernel bug at mm/slab.c:1530
* Norbert Tretkowski wrote: > * Christoph Hellwig wrote: > > Jan-Jaap van der Heijden wrote: > [...] > >> 2.6.7 doesn't lock up anymore when it hits the PCI bus. The CIA > >> issue is solved. > >> > >> But the oops is still there. Here's the trace: > > > > Hmm, the stacktrace is pretty unreadable. Can you try to reproduce > > this again once kernel-image-2.6.8-alpha-2.6.8-2 is release > > (hopefully in a day or two), as that one has kernel-based ksymoops > > support which should be more reliable. > > I'm going to build and upload kernel-image-2.6.8-alpha 2.6.8-2 as > soon as kernel-source-2.6.8 2.6.8-3 is available. http://people.debian.org/~nobse/kernel/kernel-image-2.6.8-alpha/ They are currently sitting in incoming, and will be moved into the regular archive in a few hours. Norbert
Bug#268361: ATI Radeon IGP 340M fb support
Package: kernel Severity: wishlist Tags: +upstream - Forwarded message from "Francesco P. Lovergine" <[EMAIL PROTECTED]> - Date: Fri, 20 Aug 2004 17:31:23 +0200 From: "Francesco P. Lovergine" <[EMAIL PROTECTED]> To: ajoshi, benh Subject: radeonfb support User-Agent: Mutt/1.4.1i This is an apparently missing card available on some Compaq Presario 2700 series laptops. :01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP 340M (prog-if 00 [VGA]) Subsystem: Hewlett-Packard Company: Unknown device 002a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- :01:05.0 0300: 1002:4337 Subsystem: 103c:002a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- -- Francesco P. Lovergine - End forwarded message - -- Francesco P. Lovergine
Bug#268359: kernel-image-2.6.8-powerpc: Please turn off BLK_DEV_IDE_PMAC_BLINK
Package: kernel-image-2.6.8-powerpc Version: 2.6.8-2 Severity: wishlist This blinking LED for hd activity gets on my nerves, and is, at least for my hardware, unnecessary since hd activity is quite audible. Alternatively, if there is an option to turn it off in a compiled kernel, include documentation for it. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.8-powerpc Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to C) Versions of packages kernel-image-2.6.8-powerpc depends on: ii initrd-tools 0.1.73 tools to create initrd image for p ii module-init-tools 3.1-pre5-5 tools for managing Linux kernel mo -- no debconf information
Bug#261195: Acknowledgement (kernel-source-2.6.7: Cannot mount disk images from hfs[plus] partitions)
On Sat, Jul 24, 2004 at 02:18:03AM -0700, Debian Bug Tracking System wrote: > Thank you for the problem report you have sent regarding Debian. > This is an automatically generated reply, to let you know your message has > been received. It is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian kernel team > > If you wish to submit further information on your problem, please send > it to [EMAIL PROTECTED] (and *not* to > [EMAIL PROTECTED]). > > Please do not reply to the address at the top of this message, > unless you wish to report a problem with the Bug-tracking system. > > Debian bug tracking system administrator > (administrator, Debian Bugs database) This bug report seems to have disappeared from the face of the earth. The problem still exists with a stock 2.6.8 powerpc kernel. What gives? -- Siep Kroonenberg
Re: Bug#258061: marked as done ([PATCH] ACPI initialization hangs on Compaq Presario 2100)
On Fri, Aug 27, 2004 at 12:13:16AM +0200, Sven Luther wrote: > > > > BTW, there is exactly the same problem with 2.4 series (at least 2.4.25 > > which was > > available when I did a few tests with this kind of laptops). > > Sorry, I did not point this soon... > > Can you test wit h2.4.26/2.4.27, and fill a new bug report if the problem is > still present ? > I'll do that ASAP, i.e. when that laptop will be available again under my hands. -- Francesco P. Lovergine
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
Christoph Hellwig writes: > On Fri, Aug 27, 2004 at 10:47:29AM +0200, Matthias Klose wrote: > > > It will be 2.6.8. > > > > If you write 2.6.8, do you mean 2.6.8.1? Or is the diff to .1 included > > in the Debian packages? I cannot find a hint and the version number is > > misleading. > > Given the diff to .1 is tiny and four-digit version numbers are breaking > lots of things (there's even rumors of breaking the nptl detection in > glibc, but given that debian _still_ doesn't have a tls-capable > toolchain on ppc I couldn't test it) we've decided to stay with 2.6.8. please make this decision explicit, document it in a prominent place, i.e. package description, README.Debian. Thanks, Matthias
Bug#268352: 2.6.* radeonfb regression
Package: kernel Severity: normal 2.4 series radeonfb (1.8-benh) works perfectly (also modular). 2.6 series new radeonfb never worked (since 2.6.0 at least), it does not sync here (laptop XSVGA). After loading, fbset reports 1400x1050-60, as for the 2.4 version, but screen is blank and stay in normal text mode 80x25. I need to switch on and back to X in order to see screen content again. That's for loading it modular of course, I have to do yet test for static version. :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY :01:00.0 0300: 1002:4c59 Subsystem: 0e11:b11b Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping+ SERR+ FastB2B+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=128K] Capabilities: In dmesg: Aug 18 19:06:41 localhost kernel: radeonfb: Retreived PLL infos from BIOS Aug 18 19:06:41 localhost kernel: radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=166.00 Mhz, System=143.00 MHz Aug 18 19:06:42 localhost kernel: radeonfb: Monitor 1 type LCD found Aug 18 19:06:42 localhost kernel: radeonfb: EDID probed Aug 18 19:06:42 localhost kernel: radeonfb: Monitor 2 type no found Aug 18 19:06:42 localhost kernel: radeonfb: panel ID string: Samsung LTN150P1-L02 Aug 18 19:06:42 localhost kernel: radeonfb: detected LVDS panel size from BIOS: 1400x1050 Aug 18 19:06:42 localhost kernel: radeondb: BIOS provided dividers will be used Aug 18 19:06:42 localhost kernel: radeonfb: Power Management enabled for Mobility chipsets Aug 18 19:06:42 localhost kernel: radeonfb: ATI Radeon LY DDR SGRAM 32 MB This is with current 2.6.8 in debian, but that's true with _all_ other previous versions (2.6.0+). fbset return right mode, as set in /etc/fb.modes too: mode "1400x1050-60" # D: 108.003 MHz, H: 63.983 kHz, V: 60.191 Hz geometry 1400 1050 1400 1050 8 timings 9259 136 40 10 0 112 3 rgba 6/0,6/0,6/0,0/0 hsync high vsync high accel true endmode I tried to fbset explicitly the mode after module loading too, but without results. I'll return results with static compiled in module when possible. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] -- Francesco P. Lovergine
Re: Console corrupted during boot in 2.6.8, will it be included in Sarge?
* Svante Signell wrote: > I have a problem with the 2.6.x, x>4 kernels when booting my Dell > Inspiron 4100 laptop. When the console output during boot switches > from 24 lines on the screen to a much higher number of lines, the > font colors appears to be set to black on black background or the > console is corrupted. Which graphic chip is used in your Dell? > Since the release of Sarge is imminent, it would be bad if this > happens to other people with Dell laptops. The default kernel for sarge is 2.4, 2.6 will be shipped too. > For now I can cope by using 2.4.x series kernels (2.4.27 is default > I beleive) but sooner or later I will change to a 2.6-series kernel > too. Advantages would be e.g. to have alsa and lm-sensors kernel > modules included, without having to download them (2.4.26) or build > them (2.4.27). There are precompiled modules for i2c and lm-sensors for 2.4 kernels. Norbert
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
On Fri, Aug 27, 2004 at 10:47:29AM +0200, Matthias Klose wrote: > > It will be 2.6.8. > > If you write 2.6.8, do you mean 2.6.8.1? Or is the diff to .1 included > in the Debian packages? I cannot find a hint and the version number is > misleading. Given the diff to .1 is tiny and four-digit version numbers are breaking lots of things (there's even rumors of breaking the nptl detection in glibc, but given that debian _still_ doesn't have a tls-capable toolchain on ppc I couldn't test it) we've decided to stay with 2.6.8.
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
On Fri, Aug 27, 2004 at 10:47:29AM +0200, Matthias Klose wrote: > Sven Luther writes: > > On Fri, Aug 27, 2004 at 07:53:09AM +0200, Christian Perrier wrote: > > > > > > > > Based on discussions on the debian-kernel list[1], I'd like to > > > > > propose > > > > > that we use 2.4.27 as the 2.4 kernel for all architectures with 2.4 > > > > > kernels > > > > > in sarge. The strongest arguments for 2.4.27, as opposed to 2.4.26 > > > > > were noted > > > > > by tbm [3]. > > > > > > > > One thing to bear in mind when making this kind of decision it that it > > > > seems to take d-i about 2 weeks to transition to a new kernel once the > > > > > > What are the plans regarding 2.6 ? > > > > It will be 2.6.8. > > If you write 2.6.8, do you mean 2.6.8.1? Or is the diff to .1 included > in the Debian packages? I cannot find a hint and the version number is > misleading. The package is named 2.6.8, but it includes the 2.6.8.1 diffset, i don't know the details, plus some other backports. Exact detail can be found at : http://svn.debian.org/viewcvs/kernel/trunk/kernel/source/kernel-source-2.6.8-2.6.8/debian/patches Friendly, Sven Luther
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
Sven Luther writes: > On Fri, Aug 27, 2004 at 07:53:09AM +0200, Christian Perrier wrote: > > > > > > Based on discussions on the debian-kernel list[1], I'd like to propose > > > > that we use 2.4.27 as the 2.4 kernel for all architectures with 2.4 > > > > kernels > > > > in sarge. The strongest arguments for 2.4.27, as opposed to 2.4.26 > > > > were noted > > > > by tbm [3]. > > > > > > One thing to bear in mind when making this kind of decision it that it > > > seems to take d-i about 2 weeks to transition to a new kernel once the > > > > What are the plans regarding 2.6 ? > > It will be 2.6.8. If you write 2.6.8, do you mean 2.6.8.1? Or is the diff to .1 included in the Debian packages? I cannot find a hint and the version number is misleading.
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
On Fri, Aug 27, 2004 at 02:06:46PM +0800, John Summerfield wrote: > Steve Langasek wrote: > > >> Various tasks are in a hold pattern until this decision is made (ensuring > >>that d-i uses the proper kernel, removal of other kernel packages from > >>sarge, rebuilding of some packages to fix build-dep issues[4]), so I'd > >>like to uncover any problems with this proposal quickly. > >> > >> > > > >Because this gives us a shot at having all architectures on the same > >version for sarge (where 2.4.26 does not due to arm), I agree that this > >is the way to go. > > > >I should be able to get linux-kernel-di-alpha done and uploaded by > >Monday. > > > >Sven, how far out are the 2.4.27 powerpc debs? If these aren't > >receiving enough attention because 2.6 is such a priority, I think we > >need to seriously consider dropping the 2.4 kernels completely for > >powerpc instead of giving them half-hearted support that will delay the > >release. > > > > > > > > All here who have 2.4 and 2.6 kernels on ppc should try disk speed tests > with hdparm: I found my new Athlon (well the mobo's new, CPU's not) is > 30% faster with the 2.4 kernel. > > If something like this is true of ppc too, you wouldn't want to drop 2.4 > kernels. And BTW, just ran hdparm -tT, seems to be similar from what i remember from 2.4 days. Friendly, Sven Luther
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
On Fri, Aug 27, 2004 at 02:06:46PM +0800, John Summerfield wrote: > Steve Langasek wrote: > > >> Various tasks are in a hold pattern until this decision is made (ensuring > >>that d-i uses the proper kernel, removal of other kernel packages from > >>sarge, rebuilding of some packages to fix build-dep issues[4]), so I'd > >>like to uncover any problems with this proposal quickly. > >> > >> > > > >Because this gives us a shot at having all architectures on the same > >version for sarge (where 2.4.26 does not due to arm), I agree that this > >is the way to go. > > > >I should be able to get linux-kernel-di-alpha done and uploaded by > >Monday. > > > >Sven, how far out are the 2.4.27 powerpc debs? If these aren't > >receiving enough attention because 2.6 is such a priority, I think we > >need to seriously consider dropping the 2.4 kernels completely for > >powerpc instead of giving them half-hearted support that will delay the > >release. > > > > > > > > All here who have 2.4 and 2.6 kernels on ppc should try disk speed tests > with hdparm: I found my new Athlon (well the mobo's new, CPU's not) is > 30% faster with the 2.4 kernel. Have you reported a bug report on this ? And with which 2.6 kernel was it ? > If something like this is true of ppc too, you wouldn't want to drop 2.4 > kernels. Well, it should be fixed instead. None of upstream (all the linux-ppc devleopers) have any interest left for 2.4, so there is really no sane way to keep the support going unless we do it all ourselves. Friendly, Sven Luther
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
On Thu, Aug 26, 2004 at 09:48:00PM -0700, Steve Langasek wrote: > On Wed, Aug 25, 2004 at 05:35:16PM -0600, dann frazier wrote: > > Based on discussions on the debian-kernel list[1], I'd like to propose > > that we use 2.4.27 as the 2.4 kernel for all architectures with 2.4 kernels > > in sarge. The strongest arguments for 2.4.27, as opposed to 2.4.26 were > > noted > > by tbm [3]. > > > All 2.4 architectures have 2.4.27 kernel images built. alpha, mips > > and s390 have 2.4.27 images already in sarge. hppa, m68k, i386, ia64, > > and mips have images available in sid. arm, powerpc, and sparc have images > > awaiting approval in the NEW queue. > > > linux-kernel-di is at 2.4.26 for alpha, sparc, s390, m68k, and i386. > > These > > packages will need to be updated, and will need to go through the NEW queue. > > linux-kernel-di for arm, hppa and powerpc are on 2.4.25, so will also need > > to > > be updated. ia64, mips and mipsel already have 2.4.27 linux-kernel-di > > packages. > > > Various tasks are in a hold pattern until this decision is made (ensuring > > that d-i uses the proper kernel, removal of other kernel packages from > > sarge, rebuilding of some packages to fix build-dep issues[4]), so I'd > > like to uncover any problems with this proposal quickly. > > Because this gives us a shot at having all architectures on the same > version for sarge (where 2.4.26 does not due to arm), I agree that this > is the way to go. > > I should be able to get linux-kernel-di-alpha done and uploaded by > Monday. > > Sven, how far out are the 2.4.27 powerpc debs? If these aren't Well, i have something that may work, only one hunk doesn't apply correctly, which means maybe a broken rivafb. I asked benh to have a look at it, but when he hears 2.4, he goes away running. This should be no major problem though, since offb would always work for pmac owners, and they should use 2.6 in any case. > receiving enough attention because 2.6 is such a priority, I think we > need to seriously consider dropping the 2.4 kernels completely for > powerpc instead of giving them half-hearted support that will delay the > release. No, 2.4 has to stay, since there are still a few cases where 2.6 has some trouble, in particular with some oldworld pmacs. In the major cases, 2.6.8 is the way to go, now that the CD/DVD burning problems seem to be solved (i still cannot burn RW media though, but that may not be kernel related). Friendly, Sven Luther
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
On Fri, Aug 27, 2004 at 07:53:09AM +0200, Christian Perrier wrote: > > > > Based on discussions on the debian-kernel list[1], I'd like to propose > > > that we use 2.4.27 as the 2.4 kernel for all architectures with 2.4 > > > kernels > > > in sarge. The strongest arguments for 2.4.27, as opposed to 2.4.26 were > > > noted > > > by tbm [3]. > > > > One thing to bear in mind when making this kind of decision it that it > > seems to take d-i about 2 weeks to transition to a new kernel once the > > What are the plans regarding 2.6 ? It will be 2.6.8. The plans regarding this have been made by the debian-kernel team over a mont h ago now, and the 2.6.7 kernel has been almost abandoned since then. And we are not over enjoyed to be told to have to backport all this amount of work to 2.6.7, plus who know how many fixes where in mainline 2.6.8. Furthermore many of the debian specific 2.6.7 patches have been submitted upstream for 2.6.8. > Yesterday, I installed a HP Proliant DL240, with Broadcom Gigabit > Ethernet controllers2.6.7 tg3 module does not seem to support > these while I've been told that 2.6.8 does. Yes, tg3 is one of the things that got fixed in 2.6.8. hotplug and sub don't play well together with my pegasos box on 2.6.7 too, and we gained at least s390 as new 2.6 arch with 2.6.8, maybe sparc and m68k too, depending on deadline. > So, at least regarding such (quite widespread?) machines, I would > support the use of 2.6.8. > > PS : this machine installed well with 2.4.26, however, so I'm later > able to switch to 2.6.8 by just waiting it to enter sarge. Ok. Friendly, Sven Luther
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
Steve Langasek wrote: Various tasks are in a hold pattern until this decision is made (ensuring that d-i uses the proper kernel, removal of other kernel packages from sarge, rebuilding of some packages to fix build-dep issues[4]), so I'd like to uncover any problems with this proposal quickly. Because this gives us a shot at having all architectures on the same version for sarge (where 2.4.26 does not due to arm), I agree that this is the way to go. I should be able to get linux-kernel-di-alpha done and uploaded by Monday. Sven, how far out are the 2.4.27 powerpc debs? If these aren't receiving enough attention because 2.6 is such a priority, I think we need to seriously consider dropping the 2.4 kernels completely for powerpc instead of giving them half-hearted support that will delay the release. All here who have 2.4 and 2.6 kernels on ppc should try disk speed tests with hdparm: I found my new Athlon (well the mobo's new, CPU's not) is 30% faster with the 2.4 kernel. If something like this is true of ppc too, you wouldn't want to drop 2.4 kernels. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
Re: [PROPOSAL] 2.4.27 as default 2.4 kernel for sarge
> > Based on discussions on the debian-kernel list[1], I'd like to propose > > that we use 2.4.27 as the 2.4 kernel for all architectures with 2.4 kernels > > in sarge. The strongest arguments for 2.4.27, as opposed to 2.4.26 were > > noted > > by tbm [3]. > > One thing to bear in mind when making this kind of decision it that it > seems to take d-i about 2 weeks to transition to a new kernel once the What are the plans regarding 2.6 ? Yesterday, I installed a HP Proliant DL240, with Broadcom Gigabit Ethernet controllers2.6.7 tg3 module does not seem to support these while I've been told that 2.6.8 does. So, at least regarding such (quite widespread?) machines, I would support the use of 2.6.8. PS : this machine installed well with 2.4.26, however, so I'm later able to switch to 2.6.8 by just waiting it to enter sarge.
