Processing of linux-2.6_2.6.24-5_m68k.changes
linux-2.6_2.6.24-5_m68k.changes uploaded successfully to localhost along with the files: linux-image-2.6.24-1-amiga_2.6.24-5_m68k.deb linux-headers-2.6.24-1-amiga_2.6.24-5_m68k.deb linux-image-2.6.24-1-atari_2.6.24-5_m68k.deb linux-headers-2.6.24-1-atari_2.6.24-5_m68k.deb linux-image-2.6.24-1-bvme6000_2.6.24-5_m68k.deb linux-headers-2.6.24-1-bvme6000_2.6.24-5_m68k.deb linux-image-2.6.24-1-mac_2.6.24-5_m68k.deb linux-headers-2.6.24-1-mac_2.6.24-5_m68k.deb linux-image-2.6.24-1-mvme147_2.6.24-5_m68k.deb linux-headers-2.6.24-1-mvme147_2.6.24-5_m68k.deb linux-image-2.6.24-1-mvme16x_2.6.24-5_m68k.deb linux-headers-2.6.24-1-mvme16x_2.6.24-5_m68k.deb linux-headers-2.6.24-1-common_2.6.24-5_m68k.deb linux-headers-2.6.24-1-all_2.6.24-5_m68k.deb linux-headers-2.6.24-1-all-m68k_2.6.24-5_m68k.deb linux-libc-dev_2.6.24-5_m68k.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-2.6_2.6.24-5_m68k.changes ACCEPTED
Accepted: linux-headers-2.6.24-1-all-m68k_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-all-m68k_2.6.24-5_m68k.deb linux-headers-2.6.24-1-all_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-all_2.6.24-5_m68k.deb linux-headers-2.6.24-1-amiga_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-amiga_2.6.24-5_m68k.deb linux-headers-2.6.24-1-atari_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-atari_2.6.24-5_m68k.deb linux-headers-2.6.24-1-bvme6000_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-bvme6000_2.6.24-5_m68k.deb linux-headers-2.6.24-1-common_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-common_2.6.24-5_m68k.deb linux-headers-2.6.24-1-mac_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-mac_2.6.24-5_m68k.deb linux-headers-2.6.24-1-mvme147_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-mvme147_2.6.24-5_m68k.deb linux-headers-2.6.24-1-mvme16x_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-headers-2.6.24-1-mvme16x_2.6.24-5_m68k.deb linux-image-2.6.24-1-amiga_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-amiga_2.6.24-5_m68k.deb linux-image-2.6.24-1-atari_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-atari_2.6.24-5_m68k.deb linux-image-2.6.24-1-bvme6000_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-bvme6000_2.6.24-5_m68k.deb linux-image-2.6.24-1-mac_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-mac_2.6.24-5_m68k.deb linux-image-2.6.24-1-mvme147_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-mvme147_2.6.24-5_m68k.deb linux-image-2.6.24-1-mvme16x_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-image-2.6.24-1-mvme16x_2.6.24-5_m68k.deb linux-libc-dev_2.6.24-5_m68k.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.24-5_m68k.deb Override entries for your package: linux-headers-2.6.24-1-all-m68k_2.6.24-5_m68k.deb - optional devel linux-headers-2.6.24-1-all_2.6.24-5_m68k.deb - optional devel linux-headers-2.6.24-1-amiga_2.6.24-5_m68k.deb - optional devel linux-headers-2.6.24-1-atari_2.6.24-5_m68k.deb - optional devel linux-headers-2.6.24-1-bvme6000_2.6.24-5_m68k.deb - optional devel linux-headers-2.6.24-1-common_2.6.24-5_m68k.deb - optional devel linux-headers-2.6.24-1-mac_2.6.24-5_m68k.deb - optional devel linux-headers-2.6.24-1-mvme147_2.6.24-5_m68k.deb - optional devel linux-headers-2.6.24-1-mvme16x_2.6.24-5_m68k.deb - optional devel linux-image-2.6.24-1-amiga_2.6.24-5_m68k.deb - optional admin linux-image-2.6.24-1-atari_2.6.24-5_m68k.deb - optional admin linux-image-2.6.24-1-bvme6000_2.6.24-5_m68k.deb - optional admin linux-image-2.6.24-1-mac_2.6.24-5_m68k.deb - optional admin linux-image-2.6.24-1-mvme147_2.6.24-5_m68k.deb - optional admin linux-image-2.6.24-1-mvme16x_2.6.24-5_m68k.deb - optional admin linux-libc-dev_2.6.24-5_m68k.deb - optional devel Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian kernel version for lenny?
Hi I'm the maintainer of kernel-patch-openvz (soon linux-patch-openvz) and I would like to know which version of the linux kernel that you think will be part of Lenny? The reason is that the porting process for a specific kernel version is rather high for upstream, because Debian and pristine kernel do have rather lot of differences. The openvz kernel patch is also very big (~ 700kB). Thanks in advance. Best regards, // Ola -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://inguza.com/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#464191: Sound broken with linux-image-2.6.24-1-686
Thank you Gabor. I got my sounds back on this prescription! I hope it will be fixed on next kernels release though. On Mon, 31 Mar 2008, Gabor Burjan wrote: On Tue, Feb 12, 2008 at 06:23:17PM -0500, Rob Bochan wrote: So now I've got to recompile my kernel just to have sound? How nice. I haven't had to do that since about 1998. I guess this is good enough reason as any to remove Debian from my laptop. Sad too, it's been Debian since before Woody was released. You do not need to recompile the kernel, you need the appropriate binary firmware blob. Get the firmware package ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.16.tar.bz2 and run ./configure make make install After this you should have the following files present: /lib/firmware/ess/maestro3_assp_kernel.fw /lib/firmware/ess/maestro3_assp_minisrc.fw Then, run rmmod snd_maestro3 and modprobe snd_maestro3 again. HTH, Gabor -Tipi Koivisto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian kernel version for lenny?
hello On Mon, Mar 31, 2008 at 11:14:51AM +0200, Ola Lundqvist wrote: I'm the maintainer of kernel-patch-openvz (soon linux-patch-openvz) and I would like to know which version of the linux kernel that you think will be part of Lenny? why is it not linked to linux-module-extra? The reason is that the porting process for a specific kernel version is rather high for upstream, because Debian and pristine kernel do have rather lot of differences. The openvz kernel patch is also very big (~ 700kB). i saw that openvz patch comes quite late too after upstream stable release. well porting is the oot trouble, but the openvz do very cool cleanups along the namespace additions. although i kinda doubt that it will be ready for lenny release. the next trouble is that vserver left tracking mainline since 2.6.22. we have not settled for the lenny version it is certainly 2.6.24. Most probable candidate is 2.6.26. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian kernel version for lenny?
Hi On Mon, Mar 31, 2008 at 12:40:51PM +0200, maximilian attems wrote: hello On Mon, Mar 31, 2008 at 11:14:51AM +0200, Ola Lundqvist wrote: I'm the maintainer of kernel-patch-openvz (soon linux-patch-openvz) and I would like to know which version of the linux kernel that you think will be part of Lenny? why is it not linked to linux-module-extra? What is linux-module-extra? I have not heard about it before. The reason is that the porting process for a specific kernel version is rather high for upstream, because Debian and pristine kernel do have rather lot of differences. The openvz kernel patch is also very big (~ 700kB). i saw that openvz patch comes quite late too after upstream stable release. Yes that is probably the case. This is the main reason behind my question. Upstream is the one that ask me. :) They want to know where to focus their resources. well porting is the oot trouble, but the openvz do very cool cleanups along the namespace additions. although i kinda doubt that it will be ready for lenny release. the next trouble is that vserver left We successfully managed it last release, but it was not that easy to convince the release managers. ;) tracking mainline since 2.6.22. Ahh I was not aware of that. Do you know if Micah is working on that? we have not settled for the lenny version it is certainly 2.6.24. Most probable candidate is 2.6.26. Ok, thanks that is really good to know. Best regards, // Ola best regards -- maks -- --- Inguza Technology AB --- MSc in Information Technology / [EMAIL PROTECTED]Annebergsslingan 37\ | [EMAIL PROTECTED] 654 65 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: enabling ide-scsi
On 28 Mar at 21:14 dann frazier [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED] Does anyone see a problem w/ enabling the ide-scsi module for etch, sid, trunk, etc? #467291 claims its needed for ide-tape devices and udev includes a rule for this case. I'd been hesitant to enable this in etch for fear that making this module available would lead to it getting loaded/used unintentionally for cd writing. But from what I can tell, this would only happen if explicitly configured by the user. Well, fixing ide-tape would be a better long-term solution, but as that's upstream, unfixed for years, enabling ide-scsi is prrobably the more pragmatic solution. I have ide-scsi built/loaded into my otherwise standard etch system to drive my tape, but it is not interfering with CD burning. -- Tony van der Hoff| mailto:[EMAIL PROTECTED] Buckinghamshire, England -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473603: kernel command line antidote parameters
Package: linux-image-686 Severity: wishlist Foolishly I put this at the top of lilo.conf, experimenting: append=acpi=off noapic noisapnp pci=off pnpacpi=off pnpbios=off This caused all the images in lilo.conf to become unbootable (E.g., kernel modules couldn't be installed, waiting 8, 16, 32 seconds for disk, the messages said, whatever, that's besides the issue.) What is bothering me is there is no way to put the antidote parameters on the end of the lilo prompt (you know, where one can type S or single to boot single user mode.) I.e., I wish I could do acpi=on apic isapnp pci=on pnpacpi=on as an antidote, so I suppose the sum would be: Kernel command line: BOOT_IMAGE=2.6... ro root=UUID=... acpi=off noapic noisapnp pci=off pnpacpi=off acpi=on apic isapnp pci=on pnpacpi=on Alas, there is just no way to counteract bad parameters from an unfortunate append line in lilo.conf, with good parameters added at the lilo boot prompt. Therefore, the user might very well lock himself out of his system, with indeed the list of bad parameters staring him in the face via Shift+PgUp, but unable to counteract them from the lilo boot prompt. (I ended up installing potato onto an empty partition from an old CDROM and finally was able to run an old lilo to fix my mess. Very rural here, big rainstorm, no vehicle anyway.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473605: do better than FATAL: Kernel too old
Package: linux-image-686 Severity: wishlist Regarding the message FATAL: Kernel too old The user at a rural mountaintop might only have such a one single rescue disk. Please instead allow minimal operability. Or at least allow him to hit CTRL ALT DEL to reboot then, instead of having to resort to POWER OFF, POWER ON, if there is no RESET button on his laptop. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630
Le lundi, 31 mars 2008 18.33:19 Rafael J. Wysocki, vous avez écrit : On Monday, 31 of March 2008, Didier Raboud wrote: Hi, Hi, I'm using the latest Debian 2.6.25-rc7 kernel [0] and I have big troubles with hibernation. With this version, the hibernation (suspend on disk) is sometimes not resuming correctly. The only thing I get is a blinking cursor at the top-left of the screen. The problem is that it is not easily reproducible : sometimes it works, sometimes not. AFAIK, 2.6.24 is not affected, but 2.6.25-rc6 and -rc7 (at least) are. I'm using a Dell Latitude D630. (lspci attached). Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two successful hibernate/resume cycles. Could you please check if the problem is still present if you boot with acpi_new_pts_ordering kernel command line argument? Thanks, Rafael Hi. It did not help. I had to test 4 hibernation/resume cycles to see the resume fail. By the way, I just added acp_new_pts_ordering at the end of the Grub line beginning by linux (hd0,1)/vmlinuz(...). Is that correct ? Regards, Didier signature.asc Description: This is a digitally signed message part.
Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630
On Monday, 31 of March 2008, Didier Raboud wrote: Hi, Hi, I'm using the latest Debian 2.6.25-rc7 kernel [0] and I have big troubles with hibernation. With this version, the hibernation (suspend on disk) is sometimes not resuming correctly. The only thing I get is a blinking cursor at the top-left of the screen. The problem is that it is not easily reproducible : sometimes it works, sometimes not. AFAIK, 2.6.24 is not affected, but 2.6.25-rc6 and -rc7 (at least) are. I'm using a Dell Latitude D630. (lspci attached). Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two successful hibernate/resume cycles. Could you please check if the problem is still present if you boot with acpi_new_pts_ordering kernel command line argument? Thanks, Rafael
Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630
Le lundi, 31 mars 2008 19.24:55 maximilian attems, vous avez écrit : On Mon, Mar 31, 2008 at 07:03:13PM +0200, Didier Raboud wrote: snipp Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two successful hibernate/resume cycles. Could you please check if the problem is still present if you boot with acpi_new_pts_ordering kernel command line argument? By the way, I just added acp_new_pts_ordering at the end of the Grub line beginning by linux (hd0,1)/vmlinuz(...). Is that correct ? seems strange you should add it to the kopt line and then kick as root update-grub # kopt=root=/dev/sda1 ro it should land kernel /boot/vmlinuz-2.6.25-rc7-amd64 root=/dev/sda1 ro Well... I'm using Grub2 (grub-pc). I altered the boot option at boot time but forgot to check /proc/cmdline. Will try again and report back. Regards, Didier signature.asc Description: This is a digitally signed message part.
Re: 2.6.25-rc7 : hi bernation sometimes not resuming on Dell Latitude D630
On Mon, Mar 31, 2008 at 07:03:13PM +0200, Didier Raboud wrote: snipp Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two successful hibernate/resume cycles. Could you please check if the problem is still present if you boot with acpi_new_pts_ordering kernel command line argument? By the way, I just added acp_new_pts_ordering at the end of the Grub line beginning by linux (hd0,1)/vmlinuz(...). Is that correct ? seems strange you should add it to the kopt line and then kick as root update-grub # kopt=root=/dev/sda1 ro it should land kernel /boot/vmlinuz-2.6.25-rc7-amd64 root=/dev/sda1 ro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630
Le lundi, 31 mars 2008 19.36:00 Didier Raboud, vous avez écrit : Le lundi, 31 mars 2008 19.24:55 maximilian attems, vous avez écrit : On Mon, Mar 31, 2008 at 07:03:13PM +0200, Didier Raboud wrote: snipp Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two successful hibernate/resume cycles. Could you please check if the problem is still present if you boot with acpi_new_pts_ordering kernel command line argument? By the way, I just added acp_new_pts_ordering at the end of the Grub line beginning by linux (hd0,1)/vmlinuz(...). Is that correct ? seems strange you should add it to the kopt line and then kick as root update-grub # kopt=root=/dev/sda1 ro it should land kernel /boot/vmlinuz-2.6.25-rc7-amd64 root=/dev/sda1 ro Well... I'm using Grub2 (grub-pc). I altered the boot option at boot time but forgot to check /proc/cmdline. Will try again and report back. Regards, Didier Hi, I tried again and ensured that /proc/cmdline 's end was acpi_new_pts_ordering . It did work for 2-3 hibernation, but then failed. Regards, Didier signature.asc Description: This is a digitally signed message part.
Bug#472584:
On Mon, Mar 31, 2008 at 09:11:38AM +1100, Russell Coker wrote: I think it's reasonable to expect a Lenny kernel to work in the same manner as an Etch kernel and to consider any failure to do so to be a bug. Well, this is not possible in this case because they added code to hijack other devices _and_ proposed the usage by default with the knowledge that Linus won't ever accept this. The above is what I was using. I added the console=hvc0 bit as you suggested (why is that needed?) and it displayed some console messages, Because there is not code which overrides the default console. Fedora have a patch, maybe I'll pull them in for now. mount: Mounting /dev/xvda on /root failed: No such device Contents of /dev? /sys/block? Bastian -- Get back to your stations! We're beaming down to the planet, sir. -- Kirk and Mr. Leslie, This Side of Paradise, stardate 3417.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472584:
On Mon, Mar 31, 2008 at 09:26:32PM +0200, Bastian Blank wrote: Contents of /dev? /sys/block? Oh, and xenstore-ls /local/domain/$domid. Bastian -- A little suffering is good for the soul. -- Kirk, The Corbomite Maneuver, stardate 1514.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473645: linux-2.6: Please enable Xen guest support in all i386 kernel packages
Package: linux-2.6 Severity: wishlist Tags: patch I posted some time ago[0] regarding my desire to enable Debian Installer to run in a Xen guest domain. Since then I have been working on getting the necessary support into the upstream kernel. Those bits are now queued upstream, hopefully for inclusion in 2.6.26. I've attached a patch (enable-xen) against trunk (svn version 11011) which turns on Xen support in all i386 kernels. Since CONFIG_PARAVIRT is already enabled the extra overhead of enabling Xen is very low. I'd also appriciate if you would consider two other patches for inclusion in trunk. These are the bits I've found necessary for D-I support backported to 2.6.25. Having these patches in the Debian kernels will make working on this support in the installer very much easier for me once d-i moves to 2.6.25 (I expect both patches to be in 2.6.26). v2.08 is version 2.08 of the x86 boot protocol which allows the Xen domain builder to extract the ELF file from a bzImage in order to boot it. This is needed because the standard (i.e. non-Xen) kernel packages do not include the raw ELF file. xen-modules-autoprobing-support-for-frontend-drivers.patch adds support for module alias in order to allow modules to be autoloaded. Thanks, Ian. [0] http://lists.debian.org/debian-boot/2008/01/msg00269.html -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Index: linux-2.6/debian/config/i386/config === --- linux-2.6.orig/debian/config/i386/config2008-03-30 12:01:36.0 +0100 +++ linux-2.6/debian/config/i386/config 2008-03-30 12:01:52.0 +0100 @@ -148,7 +148,7 @@ ## ## file: arch/x86/xen/Kconfig ## -# CONFIG_XEN is not set +CONFIG_XEN=y ## ## file: crypto/Kconfig @@ -247,6 +247,7 @@ CONFIG_CDROM_PKTCDVD=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set +CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_VIRTIO_BLK=m ## @@ -312,6 +313,7 @@ CONFIG_PRINTER=m # CONFIG_LP_CONSOLE is not set CONFIG_PPDEV=m +CONFIG_HVC_XEN=y CONFIG_NVRAM=m CONFIG_RTC=m CONFIG_GEN_RTC=m @@ -1114,6 +1116,7 @@ CONFIG_VIA_VELOCITY=m CONFIG_TIGON3=m CONFIG_BNX2=m +CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_FDDI=y CONFIG_DEFXX=m # CONFIG_DEFXX_MMIO is not set Index: linux-2.6/debian/changelog === --- linux-2.6.orig/debian/changelog 2008-03-30 12:01:36.0 +0100 +++ linux-2.6/debian/changelog 2008-03-30 12:01:52.0 +0100 @@ -89,6 +89,9 @@ * topconfig: Enable CONFIG_CIFS_WEAK_PW_HASH, required for compatibility with legacy (pre-NTLM) fileservers. + [ Ian Campbell ] + * [x86]: Enable Xen guest support in all i386 flavours. + -- Bastian Blank [EMAIL PROTECTED] Tue, 26 Feb 2008 23:59:55 -0700 linux-2.6 (2.6.24-5) unstable; urgency=low Index: linux-2.6/debian/patches/series/1~experimental.1 === --- linux-2.6.orig/debian/patches/series/1~experimental.1 2008-03-30 11:51:33.0 +0100 +++ linux-2.6/debian/patches/series/1~experimental.12008-03-30 11:57:49.0 +0100 @@ -37,3 +37,4 @@ + bugfix/all/rtc-x1205-new-style-conversion-checkpatch-fixes.patch + bugfix/all/mtd-prevent-physmap-from-causing-request_module-runaway-loop-modprobe-net-pf-1.patch + bugfix/arm/oabi-shim-for-fstatat64.patch ++ features/x86/boot-protocol-v2.08.patch Index: linux-2.6/debian/changelog === --- linux-2.6.orig/debian/changelog 2008-03-30 11:56:43.0 +0100 +++ linux-2.6/debian/changelog 2008-03-30 11:57:31.0 +0100 @@ -91,6 +91,7 @@ [ Ian Campbell ] * [x86]: Enable Xen guest support in all i386 flavours. + * [x86]: Backport boot protocol v2.08. -- Bastian Blank [EMAIL PROTECTED] Tue, 26 Feb 2008 23:59:55 -0700 Index: linux-2.6/debian/patches/features/x86/boot-protocol-v2.08.patch === --- /dev/null 1970-01-01 00:00:00.0 + +++ linux-2.6/debian/patches/features/x86/boot-protocol-v2.08.patch 2008-03-30 11:57:31.0 +0100 @@ -0,0 +1,329 @@ +diff --git a/Documentation/i386/boot.txt b/Documentation/i386/boot.txt +index fc49b79..05c24df 100644 +--- a/Documentation/i386/boot.txt b/Documentation/i386/boot.txt +@@ -170,6 +170,8 @@ Offset Proto NameMeaning + 0238/42.06+ cmdline_sizeMaximum size of the kernel command line + 023C/42.07+ hardware_subarch Hardware subarchitecture + 0240/82.07+ hardware_subarch_data Subarchitecture-specific data ++0248/42.08+ compressed_payload_offset ++024C/42.08+
Bug#473644: linux-image-2.6.24-1-686: S3 suspend oops once in a while
Package: linux-image-2.6.24-1-686 Version: 2.6.24-4 Severity: normal I've seen this oops a couple times now, though it doesn't happen often. I try to put the machine to sleep (S3) with Fn-F4, whose action I've set to /etc/acpi/sleepbtn.sh /etc/acpi/sleep.sh, and I see an oops in the dmesg (with no S3 sleep). The machine is a Thinkpad T60 with Intel video, wireless. I had installed the 2.6.24-5 version of the kernel package but had not rebooted into it, so I was still running the 2.6.24-4 Debian kernel. It's uname: Linux approx 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 GNU/Linux The oops: BUG: unable to handle kernel NULL pointer dereference at virtual address printing eip: *pde = Oops: [#1] SMP Modules linked in: sbs sbshc battery ac thinkpad_acpi nvram thermal fan button iwl3945 mac80211 cfg80211 e1000 usb_storage snd_pcm_oss snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device fuse i915 drm ipt_LOG xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_filter ip_tables x_tables ppdev parport_pc lp parport ipv6 dm_snapshot dm_mirror dm_mod loop pcmcia hci_usb bluetooth arc4 ecb blkcipher video output firmware_class psmouse serio_raw yenta_socket rsrc_nonstatic pcmcia_core irtty_sir sir_dev nsc_ircc snd_hda_intel irda snd_pcm snd_timer snd soundcore intel_agp agpgart i2c_i801 crc_ccitt snd_page_alloc i2c_core iTCO_wdt rtc pcspkr evdev ext3 jbd mbcache ide_cd cdrom sd_mod generic piix ide_core ata_generic ahci uhci_hcd libata ehci_hcd scsi_mod usbcore processor Pid: 48, comm: kacpi_notify Not tainted (2.6.24-1-686 #1) EIP: 0060:[] EFLAGS: 00010282 CPU: 0 EIP is at _stext+0x3feff000/0x14 EAX: f7c36e14 EBX: f74fdaec ECX: EDX: 0080 ESI: f777d878 EDI: c020263d EBP: ESP: f7d35f80 DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 Process kacpi_notify (pid: 48, ti=f7d34000 task=f7c940b0 task.ti=f7d34000) Stack: c0207cc2 cab76940 cab76948 c020265f f31867a8 f7c5bdc0 c0132225 0246 c0135554 f7c5bdc0 f7c5bdc0 c0132a9b f7d35fd0 c0132b55 f7c940b0 c0135441 f7d35fc8 f7d35fc8 f7c5bdc0 c013537a c0135342 Call Trace: [c0207cc2] acpi_ev_notify_dispatch+0x4c/0x55 [c020265f] acpi_os_execute_notify+0x22/0x2b [c0132225] run_workqueue+0x7d/0x109 [c0135554] prepare_to_wait+0x12/0x49 [c0132a9b] worker_thread+0x0/0xc5 [c0132b55] worker_thread+0xba/0xc5 [c0135441] autoremove_wake_function+0x0/0x35 [c013537a] kthread+0x38/0x5e [c0135342] kthread+0x0/0x5e [c0104b0f] kernel_thread_helper+0x7/0x10 === Code: Bad EIP value. EIP: [] _stext+0x3feff000/0x14 SS:ESP 0068:f7d35f80 ---[ end trace 45643a917ff2a1b6 ]--- -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.24-1-686 depends on: ii debconf [debconf-2.0]1.5.20 Debian configuration management sy ii initramfs-tools [linux-initr 0.91e tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo Versions of packages linux-image-2.6.24-1-686 recommends: ii libc6-i6862.7-10 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.24-1-686/preinst/overwriting-modules-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/bootloader-error-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/create-kimage-link-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/old-system-map-link-2.6.24-1-686: true linux-image-2.6.24-1-686/prerm/would-invalidate-boot-loader-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/initrd-2.6.24-1-686: linux-image-2.6.24-1-686/preinst/failed-to-move-modules-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/depmod-error-initrd-2.6.24-1-686: false linux-image-2.6.24-1-686/preinst/bootloader-initrd-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/old-initrd-link-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.24-1-686/postinst/old-dir-initrd-link-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/abort-install-2.6.24-1-686: linux-image-2.6.24-1-686/prerm/removing-running-kernel-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/depmod-error-2.6.24-1-686: false linux-image-2.6.24-1-686/preinst/abort-overwrite-2.6.24-1-686: linux-image-2.6.24-1-686/preinst/elilo-initrd-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/bootloader-test-error-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/kimage-is-a-directory: linux-image-2.6.24-1-686/preinst/lilo-initrd-2.6.24-1-686: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe.
Processed: Re: Bug#470869: initramfs-tools: default compression level should be 6 rather than 9
Processing commands for [EMAIL PROTECTED]: tags 470869 pending Bug#470869: initramfs-tools: default compression level should be 6 rather than 9 There were no tags set. Tags added: pending stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#470869: initramfs-tools: default compression level should be 6 rather than 9
tags 470869 pending stop On Fri, 14 Mar 2008, Tollef Fog Heen wrote: I think the default gzip compression level should be changed from 9 to 6. In my measurements (which are done on an Ubuntu system, but I doubt there's any significant differences in this case), the size difference between -6 and -9 is about 1%, while the time needed to compress the initramfs goes from around 15.5s to around 2.5s. thanks for bringing the numbers already changed in git, discovered your ubuntu change some time ago. will be fixed by next upload. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#468116: update-initramfs: ro_bootcheck fix.
On Wed, 27 Feb 2008, Luke Yelavich wrote:
Attached is a patch to fix a possible ro_bootcheck error. The Ubuntu
changelog contains the following:
* Fix broken test in ro_boot_check (LP: #187282). It was matching ro as a
subword.
The patch applies against git head. See Ubuntu bug #187282,
https://launchpad.net/bugs/187282 for more information.
yes the test got bogus by kernel upstream adding more info to
/proc/mounts. although current version in debian is fine too.
- boot_opts=$(awk '/boot/{if ((match($4, /^ro/) || match($4, /,ro/)) \
- $2 == /boot) print ro}' /proc/mounts)
+ boot_opts=$(awk '/boot/{if (match($4,
/([^a-zA-Z0-9]|^)ro([^a-zA-Z0-9]|$)/) $2 == /boot) print ro}'
/proc/mounts)
hmmm don't see that as improvement, debians version seems more readble.
if you have futher enhancements to it please base the patches on it.
the only trouble on the debian side would be another mount option
beginning with ro, but that didn't get reported yet nor do i know one.
thanks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630
On Monday, 31 of March 2008, Didier Raboud wrote: Le lundi, 31 mars 2008 19.36:00 Didier Raboud, vous avez écrit : Le lundi, 31 mars 2008 19.24:55 maximilian attems, vous avez écrit : On Mon, Mar 31, 2008 at 07:03:13PM +0200, Didier Raboud wrote: snipp Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two successful hibernate/resume cycles. Could you please check if the problem is still present if you boot with acpi_new_pts_ordering kernel command line argument? By the way, I just added acp_new_pts_ordering at the end of the Grub line beginning by linux (hd0,1)/vmlinuz(...). Is that correct ? seems strange you should add it to the kopt line and then kick as root update-grub # kopt=root=/dev/sda1 ro it should land kernel /boot/vmlinuz-2.6.25-rc7-amd64 root=/dev/sda1 ro Well... I'm using Grub2 (grub-pc). I altered the boot option at boot time but forgot to check /proc/cmdline. Will try again and report back. Regards, Didier Hi, I tried again and ensured that /proc/cmdline 's end was acpi_new_pts_ordering . It did work for 2-3 hibernation, but then failed. Well, there were quite a lot of suspend-related changes between 2.6.24 and now. Hmm, do you have CONFIG_USB_SUSPEND set in .config by chance? Rafael
Processed: tagging 467078
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.18.1 tags 467078 pending Bug#467078: initramfs-tools: Network configuration can't work with multiple interfaces Tags were: patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630
Le lundi, 31 mars 2008 22.29:20 Rafael J. Wysocki, vous avez écrit : On Monday, 31 of March 2008, Didier Raboud wrote: Le lundi, 31 mars 2008 19.36:00 Didier Raboud, vous avez écrit : Le lundi, 31 mars 2008 19.24:55 maximilian attems, vous avez écrit : On Mon, Mar 31, 2008 at 07:03:13PM +0200, Didier Raboud wrote: snipp Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two successful hibernate/resume cycles. Could you please check if the problem is still present if you boot with acpi_new_pts_ordering kernel command line argument? By the way, I just added acp_new_pts_ordering at the end of the Grub line beginning by linux (hd0,1)/vmlinuz(...). Is that correct ? seems strange you should add it to the kopt line and then kick as root update-grub # kopt=root=/dev/sda1 ro it should land kernel /boot/vmlinuz-2.6.25-rc7-amd64 root=/dev/sda1 ro Well... I'm using Grub2 (grub-pc). I altered the boot option at boot time but forgot to check /proc/cmdline. Will try again and report back. Regards, Didier Hi, I tried again and ensured that /proc/cmdline 's end was acpi_new_pts_ordering . It did work for 2-3 hibernation, but then failed. Well, there were quite a lot of suspend-related changes between 2.6.24 and now. Hmm, do you have CONFIG_USB_SUSPEND set in .config by chance? Rafael I do (Debian default option)... I will build a kernel without it and retry. Didier signature.asc Description: This is a digitally signed message part.
Bug#468113: PlayStation 3 script update.
On Wed, 27 Feb 2008, Luke Yelavich wrote:
Attached is a patch to update the ps3 script. This patch allows the
supporting of old and new ps3 hardware configurations. The patch applies
against git head.
okay.
diff -urN initramfs-tools/scripts/init-premount/ps3
initramfs-tools.new/scripts/init-premount/ps3
--- initramfs-tools/scripts/init-premount/ps3 2008-02-26 10:36:10.419676705
+1100
+++ initramfs-tools.new/scripts/init-premount/ps3 2008-02-26
13:43:53.571676705 +1100
@@ -17,15 +17,20 @@
case $DPKG_ARCH in
powerpc|ppc64)
- while read line; do
- if [ ${line} != ${line#machine*PS3PF} ]; then
- # For PS3's we know these devices will exist,
- # and that we'll need them
- modprobe ps3_storage
- modprobe gelic_net
- modprobe ohci-hcd
- modprobe ehci-hcd
- fi
- done /proc/cpuinfo
+ # For PS3's we know these devices will exist, and we'll need them
+ if grep -q PS3 /proc/cpuinfo; then
+ # New style
+ modprobe -Qb ps3disk
+ modprobe -Qb ps3rom
+ modprobe -Qb ps3-gelic
+
+ # Old style
+ modprobe -Qb ps3_storage
+ modprobe -Qb gelic_net
+
+ modprobe -Qb ohci-hcd
+ modprobe -Qb ehci-hcd
+ modprobe -Qb sys-manager
+ fi
no please grep is *not* assured to be on initramfs.
if you boot with BUSYBOX=n thus don't replace the readline
part with grep that is useless.
also -Qb modprobe argument is ubuntu specific,
it shouldn't be used at all in the scripts,
but that in the start with MODPROBE_OPTIONS.
thanks tagging as pending as added the new style modprobe
to debian's initramfs.
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473645: marked as done (linux-2.6: Please enable Xen guest support in all i386 kernel packages)
Your message dated Mon, 31 Mar 2008 23:03:19 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#473645: linux-2.6: Please enable Xen guest support in all i386 kernel packages has caused the Debian Bug report #473645, regarding linux-2.6: Please enable Xen guest support in all i386 kernel packages 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 473645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473645 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-2.6 Severity: wishlist Tags: patch I posted some time ago[0] regarding my desire to enable Debian Installer to run in a Xen guest domain. Since then I have been working on getting the necessary support into the upstream kernel. Those bits are now queued upstream, hopefully for inclusion in 2.6.26. I've attached a patch (enable-xen) against trunk (svn version 11011) which turns on Xen support in all i386 kernels. Since CONFIG_PARAVIRT is already enabled the extra overhead of enabling Xen is very low. I'd also appriciate if you would consider two other patches for inclusion in trunk. These are the bits I've found necessary for D-I support backported to 2.6.25. Having these patches in the Debian kernels will make working on this support in the installer very much easier for me once d-i moves to 2.6.25 (I expect both patches to be in 2.6.26). v2.08 is version 2.08 of the x86 boot protocol which allows the Xen domain builder to extract the ELF file from a bzImage in order to boot it. This is needed because the standard (i.e. non-Xen) kernel packages do not include the raw ELF file. xen-modules-autoprobing-support-for-frontend-drivers.patch adds support for module alias in order to allow modules to be autoloaded. Thanks, Ian. [0] http://lists.debian.org/debian-boot/2008/01/msg00269.html -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Index: linux-2.6/debian/config/i386/config === --- linux-2.6.orig/debian/config/i386/config2008-03-30 12:01:36.0 +0100 +++ linux-2.6/debian/config/i386/config 2008-03-30 12:01:52.0 +0100 @@ -148,7 +148,7 @@ ## ## file: arch/x86/xen/Kconfig ## -# CONFIG_XEN is not set +CONFIG_XEN=y ## ## file: crypto/Kconfig @@ -247,6 +247,7 @@ CONFIG_CDROM_PKTCDVD=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set +CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_VIRTIO_BLK=m ## @@ -312,6 +313,7 @@ CONFIG_PRINTER=m # CONFIG_LP_CONSOLE is not set CONFIG_PPDEV=m +CONFIG_HVC_XEN=y CONFIG_NVRAM=m CONFIG_RTC=m CONFIG_GEN_RTC=m @@ -1114,6 +1116,7 @@ CONFIG_VIA_VELOCITY=m CONFIG_TIGON3=m CONFIG_BNX2=m +CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_FDDI=y CONFIG_DEFXX=m # CONFIG_DEFXX_MMIO is not set Index: linux-2.6/debian/changelog === --- linux-2.6.orig/debian/changelog 2008-03-30 12:01:36.0 +0100 +++ linux-2.6/debian/changelog 2008-03-30 12:01:52.0 +0100 @@ -89,6 +89,9 @@ * topconfig: Enable CONFIG_CIFS_WEAK_PW_HASH, required for compatibility with legacy (pre-NTLM) fileservers. + [ Ian Campbell ] + * [x86]: Enable Xen guest support in all i386 flavours. + -- Bastian Blank [EMAIL PROTECTED] Tue, 26 Feb 2008 23:59:55 -0700 linux-2.6 (2.6.24-5) unstable; urgency=low Index: linux-2.6/debian/patches/series/1~experimental.1 === --- linux-2.6.orig/debian/patches/series/1~experimental.1 2008-03-30 11:51:33.0 +0100 +++ linux-2.6/debian/patches/series/1~experimental.12008-03-30 11:57:49.0 +0100 @@ -37,3 +37,4 @@ + bugfix/all/rtc-x1205-new-style-conversion-checkpatch-fixes.patch + bugfix/all/mtd-prevent-physmap-from-causing-request_module-runaway-loop-modprobe-net-pf-1.patch + bugfix/arm/oabi-shim-for-fstatat64.patch ++ features/x86/boot-protocol-v2.08.patch Index: linux-2.6/debian/changelog === --- linux-2.6.orig/debian/changelog 2008-03-30 11:56:43.0 +0100 +++ linux-2.6/debian/changelog 2008-03-30 11:57:31.0 +0100 @@ -91,6 +91,7 @@ [ Ian Campbell ] * [x86]: Enable Xen guest support in all i386 flavours. + * [x86]: Backport boot protocol v2.08. -- Bastian Blank [EMAIL PROTECTED] Tue,
Bug#468112: Initramfs generation reliability fixes.
On Wed, 27 Feb 2008, Luke Yelavich wrote:
Attached is a patch to improve the way update-initramfs handles the
generating of new or updated initramfs images for kernels. It puts in
place a few measures to ensure that if there is not enough disk space on
/boot, a previous initramfs is still in tact, to allow the booting of
that kernel. The patch applies against current git head. See the Ubuntu
specification found at the following URL for more information:
https://wiki.ubuntu.com/HardyInitramfsErrorHandling
okay,
i still don't understands belows patch.
diff -urN initramfs-tools/update-initramfs
initramfs-tools.new/update-initramfs
--- initramfs-tools/update-initramfs 2008-02-26 11:04:36.943676705 +1100
+++ initramfs-tools.new/update-initramfs 2008-02-26 11:01:00.555676705
+1100
@@ -87,7 +87,7 @@
[ ! -r ${initramfs} ] return 0
initramfs_bak=${initramfs}.dpkg-bak
[ -r ${initramfs_bak} ] rm -f ${initramfs_bak}
- ln -f ${initramfs} ${initramfs_bak}
+ mv -f ${initramfs} ${initramfs_bak}
why does a mv instead of an hardlinkg ensure better reliabiality!?
with aboves hardlink you are assured to have a backup initramfs.
do you need support /boot that have no hardlink support?
sorry need more explanations for above to be satisfied.
- rm -f ${initramfs_bak}
+ mv -f ${initramfs_bak} ${initramfs}
how is that better again?
only a result of aboves first choice of not using hardlinks.
fi
- if mkinitramfs ${OPTS} ${initramfs}.new ${version}; then
- mv -f ${initramfs}.new ${initramfs}
+ if mkinitramfs ${OPTS} ${initramfs} ${version}; then
this hook got inversed but that doesn't matter right now,
need more info anyway.
thanks
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#468113: PlayStation 3 script update.
On Wed, Feb 27, 2008 at 02:20:18PM +1100, Luke Yelavich wrote: Attached is a patch to update the ps3 script. This patch allows the supporting of old and new ps3 hardware configurations. The patch applies against git head. Why are the modules not loaded by udev? Bastian -- Conquest is easy. Control is not. -- Kirk, Mirror, Mirror, stardate unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 468113
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.18.1 tags 468113 pending Bug#468113: PlayStation 3 script update. There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472584:
On Tuesday 01 April 2008 06:26, Bastian Blank [EMAIL PROTECTED] wrote: On Mon, Mar 31, 2008 at 09:11:38AM +1100, Russell Coker wrote: I think it's reasonable to expect a Lenny kernel to work in the same manner as an Etch kernel and to consider any failure to do so to be a bug. Well, this is not possible in this case because they added code to hijack other devices _and_ proposed the usage by default with the knowledge that Linus won't ever accept this. Do we have people with enough spare time to fix this foolishness? The above is what I was using. I added the console=hvc0 bit as you suggested (why is that needed?) and it displayed some console messages, Because there is not code which overrides the default console. Fedora have a patch, maybe I'll pull them in for now. Fedora also messes things up. /dev/tty0 doesn't work for a getty with a Fedora/RHEL/CentOS kernel in a DomU. mount: Mounting /dev/xvda on /root failed: No such device Contents of /dev? /sys/block? (initramfs) ls -l /sys/block/xvda -r--r--r--1 004096 Mar 31 21:55 capability -r--r--r--1 004096 Mar 31 21:55 dev lrwxrwxrwx1 00 0 Mar 31 21:55 device - ../../devices/vbd-51712 drwxr-xr-x2 00 0 Mar 31 21:55 holders drwxr-xr-x3 00 0 Mar 31 21:55 queue -r--r--r--1 004096 Mar 31 21:55 range -r--r--r--1 004096 Mar 31 21:55 removable -r--r--r--1 004096 Mar 31 21:55 size drwxr-xr-x2 00 0 Mar 31 21:55 slaves -r--r--r--1 004096 Mar 31 21:55 stat lrwxrwxrwx1 00 0 Mar 31 21:55 subsystem - ../../block --w---1 004096 Mar 31 21:55 uevent (initramfs) ls -l /dev/xvda brw-rw1 00202, 0 Mar 31 21:55 /dev/xvda xenstore-ls /local/domain/$domid gives the following: vm = /vm/5787f4aa-a61e-c6b7-ce50-6a507cc9233c device = vbd = 51712 = virtual-device = 51712 device-type = disk protocol = x86_32-abi backend-id = 0 state = 4 backend = /local/domain/0/backend/vbd/23/51712 ring-ref = 8 event-channel = 6 vif = 0 = mac = 00:16:3e:66:66:69 handle = 0 protocol = x86_32-abi backend-id = 0 state = 4 backend = /local/domain/0/backend/vif/23/0 tx-ring-ref = 768 rx-ring-ref = 769 event-channel = 7 request-rx-copy = 1 feature-rx-notify = 1 feature-sg = 1 feature-gso-tcpv4 = 1 console = 0 = protocol = x86_32-abi state = 1 backend-id = 0 backend = /local/domain/0/backend/console/23/0 device-misc = vif = nextDeviceID = 1 console = nextDeviceID = 1 console = ring-ref = 77958 port = 2 limit = 1048576 type = xenconsoled tty = /dev/pts/2 image = entry = 3224522752 pae-mode = yes loader = generic virt-base = 3221225472 features = pae-pgdir-above-4gb = 1 writable-page-tables = 0 xen-version = xen-3.0 guest-os = linux hypercall-page = 3224731648 guest-version = 2.6 store = ring-ref = 77959 port = 1 cpu = 0 = availability = online control = platform-feature-multiprocessor-suspend = 1 name = play-test domid = 23 memory = target = 102400 serial = 0 = tty = /dev/pts/2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: [Pkg-alsa-devel] Bug#465161: Bug#465161: alsa-base: Alsa fails to find maestro3 soundcard with Maestro3: probe of 0000:00:08.0 failed with error -2
Processing commands for [EMAIL PROTECTED]: reassign 465161 linux-latest-2.6 Bug#465161: alsa-base: Alsa fails to find maestro3 soundcard with Maestro3: probe of :00:08.0 failed with error -2 Bug reassigned from package `alsa-base' to `linux-latest-2.6'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473136: linux-image-2.6.24-1-iop32x: Can't found /dev/rtc : not hardware clock
Martin Michlmayr a écrit : It's still more similar to IQ31244, which doesn't define a RTC device at all. It's wonderful, it work with EM7210 enabled on a 2.6.24 kernel. Thank you for your help. $ dmesg [..] Machine: Lanner EM7210 [..] i2c /dev entries driver rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.5 rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0 [...] rtc-rs5c372 0-0032: setting system clock to 2008-03-31 21:36:52 UTC (1206999412) -- Florent Fourcot.
Bug#472584:
On Tue, Apr 01, 2008 at 09:00:57AM +1100, Russell Coker wrote: Fedora also messes things up. /dev/tty0 doesn't work for a getty with a Fedora/RHEL/CentOS kernel in a DomU. /dev/tty0 is a virtual console. A DomU have no virtual consoles except with a framebuffer. mount: Mounting /dev/xvda on /root failed: No such device (initramfs) ls -l /dev/xvda brw-rw1 00202, 0 Mar 31 21:55 /dev/xvda Okay, so this is the old race condition. Use rootdelay=X for now. Bastian -- A little suffering is good for the soul. -- Kirk, The Corbomite Maneuver, stardate 1514.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473605: marked as done (do better than FATAL: Kernel too old)
Your message dated Mon, 31 Mar 2008 19:00:24 -0600 with message-id [EMAIL PROTECTED] and subject line Re: Bug#473605: do better than FATAL: Kernel too old has caused the Debian Bug report #473605, regarding do better than FATAL: Kernel too old 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 473605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473605 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-686 Severity: wishlist Regarding the message FATAL: Kernel too old The user at a rural mountaintop might only have such a one single rescue disk. Please instead allow minimal operability. Or at least allow him to hit CTRL ALT DEL to reboot then, instead of having to resort to POWER OFF, POWER ON, if there is no RESET button on his laptop. ---End Message--- ---BeginMessage--- On Mon, Mar 31, 2008 at 11:22:20PM +0800, [EMAIL PROTECTED] wrote: Package: linux-image-686 Severity: wishlist Regarding the message FATAL: Kernel too old The user at a rural mountaintop might only have such a one single rescue disk. Please instead allow minimal operability. If you view this as a kernel bug, then the only way we could fix it is to update the kernel. Luckily we updated to 2.6 long ago, so we're good. -- dann frazier ---End Message---
Bug#473605: do better than FATAL: Kernel too old
On Mon, Mar 31, 2008 at 11:22:20PM +0800, [EMAIL PROTECTED] wrote: Package: linux-image-686 Severity: wishlist Regarding the message FATAL: Kernel too old The user at a rural mountaintop might only have such a one single rescue disk. Please instead allow minimal operability. If you view this as a kernel bug, then the only way we could fix it is to update the kernel. Luckily we updated to 2.6 long ago, so we're good. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
