Bug#626031: debian-kernel-handbook: please support U-Boot format images.
Package: debian-kernel-handbook
Version: 1.0.10
Severity: wishlist
Tags: patch
Hello,
While looking to DebianBug#550584, I wonder why do we need to carry
with the burden of maintaining hardcoded stuff for some architectures,
while part of it is maintained by Linux kernel upstream developers.
Adding support for U-Boot image format ('uImage' kernel target) in
official kernel packages seem to me the right thing to do, it would
not only simplify `flash-kernel` (see #108 comments for a `flash-kernel`
summary of issues) but also `debian-installer` which currently have to
add extra code to support U-Boot image format per device. Part of that
extra code could be reduced by allowing U-Boot format images in official
packages.
Regarding initramfs generation, it could be generated as usual by initramfs
tools but if platform uses U-Boot format after creating, updating or deleting
initrd.img it should call the uinitrd.img handler (nowadays flash-kernel) with
a couple parameters:
The following patch against SVN trunk (r89) ammends kernel handbook policy
for allowing U-Boot image format support (and also fixes some indentation
to be coherent with writting style).
Index: chapter-initramfs.sgml
===
--- chapter-initramfs.sgml (revision 89)
+++ chapter-initramfs.sgml (working copy)
@@ -63,7 +63,7 @@
sect id=initramfs-gen-process
headingChoosing the tool/heading
p
- At the end of the kernel package installation a script is
+At the end of the kernel package installation a script is
automatically invoked to determine the availability of the
initramfs-generating tools and run one of them. This script
contains the list of all such tools available in Debian.
@@ -96,20 +96,33 @@
be regenerated. This is achieved by the command
example
# dpkg-reconfigure linux-image-2.6.18-3-686
-/example
-where ttlinux-image-2.6.18-3-686/tt is the name of the
+ /example
+ where ttlinux-image-2.6.18-3-686/tt is the name of the
kernel package for which the initramfs regeneration is requested.
+ /p
/sect
sect id=initramfs-exam
headingExamining the initramfs contents/heading
- p
+ p
Occasionally it is useful to examine the contents of initramfs
to diagnose a problem or for educational purposes. They are
compressed ttcpio/tt archives, which may be extracted
using the command
example
$ zcat /boot/initrd.img-2.6.18-3-686 | cpio -i
-/example
+ /example
It will unpack the contents of the initramfs into the current directory.
+ /p
/sect
+ sect id=initramfs-uimage
+headingGenerating U-Boot format initramfs images
(uinitrd.img)/heading
+ p
+If U-Boot format (ttuImage/tt) Linux kernel image exists
+ initramfs generation tool must run to create, update or delete initramfs
+ after each one of those tasks it must pass control to the uinitrd.img
+ generation tool, nowadays the only known tool ttflash-kernel/tt
passing
+ two arguments: action performed (create, update, delete) and
+
emversion/em-emabiname/em[-emfeatureset/em]-emflavour/em.
+ /p
+ /sect
/chapt
Index: chapter-update-hooks.sgml
===
--- chapter-update-hooks.sgml (revision 89)
+++ chapter-update-hooks.sgml (working copy)
@@ -28,7 +28,8 @@
optionally, the absolute path to the kernel image. If the
second argument is missing then the path is
either tt/boot/vmlinuz-emversion/em/tt or
- tt/boot/vmlinux-emversion/em/tt, according to
+ tt/boot/vmlinux-emversion/em/tt or
+ tt/boot/uImage-emversion/em/tt, according to
architecture convention. The environment variable
ttDEB_MAINT_PARAMS/tt will contain the arguments given to
the kernel maintainer script, possibly single-quoted. In a
Index: chapter-packaging.sgml
===
--- chapter-packaging.sgml (revision 89)
+++ chapter-packaging.sgml (working copy)
@@ -281,19 +281,35 @@
pre-built binary modules for a particular
arch/featureset/flavour combination. Names of the files
installed by this package are
- architecture-dependent. Typical locations of essential
- files for the tti386/tt architecture are:
+ architecture-dependent. Traditionally Debian Linux kernel uses
+ ttvmlinuz/tt, a gzip compressed ELF, COFF or a.out image.
+ U-Boot format Linux kernel images, ttuImage/tt, are supported
as well
+ for architectures that use such format.
+ Typical locations of essential files are:
taglist
Bug#610085: using 2.6.32-5 kernel (debian/testing) couses my xeon x3430 to crash at bootup hanging on various unpredictable modules
Dear sir, i just wanted to ask if the bug is resolved already. Booting into kernel 2.6.38 also brings the system to halt when more then one CPU core is activated. The system boots fine when only one CPU core (of four) is activated. Sincerely, Adrian Kiess -- Adrian Immanuel Kieß (adrian at immanuelK.net)
Bug#626031: debian-kernel-handbook: please support U-Boot format images.
* Hector Oron zu...@debian.org [2011-05-08 08:10]:
Adding support for U-Boot image format ('uImage' kernel target) in
official kernel packages seem to me the right thing to do, it would
This was suggested before but there are some reasons why I don't
believe it will work:
- We need to hardcode the machine ID into the kernel and the machine
ID depends on a particular device, so shipping a uImage rather than
a normal kernel file will just make it harder.
- Some machines require different uImage settings (load address, etc).
For example, the mv2120 doesn't use a normal uImage but a
multi-boot uImage.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110508094908.gu16...@jirafa.cyrius.com
Bug#626031: debian-kernel-handbook: please support U-Boot format images.
Hi,
2011/5/8 Martin Michlmayr t...@cyrius.com:
* Hector Oron zu...@debian.org [2011-05-08 08:10]:
Adding support for U-Boot image format ('uImage' kernel target) in
official kernel packages seem to me the right thing to do, it would
This was suggested before but there are some reasons why I don't
believe it will work:
- We need to hardcode the machine ID into the kernel and the machine
ID depends on a particular device, so shipping a uImage rather than
a normal kernel file will just make it harder.
I think machine_ID and kernel_format (uImage|vmlinuz|vmlinux) could
easily be fields in the architecture config files (defines).
Having a kernel task that overrides machine ID (when needed) does not
seem to be a complicated task either. OTOH, we
simplify `debian-installer` and `flash-kernel` (where code is
duplicated), plus we avoid to play with create, upgrade, delete
kernel hooks.
- Some machines require different uImage settings (load address, etc).
For example, the mv2120 doesn't use a normal uImage but a
multi-boot uImage.
What's a multi-boot uImage?
Best regards,
--
Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
PS.- I have just built an uImage for tegra device and linux kernel
have all the needed information,
why Debian Linux kernel is unable to do the same?
zumbi@ts01:~/linux-2.6.39-rc6$ make uImage
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALLscripts/checksyscalls.sh
CHK include/generated/compile.h
Kernel: arch/arm/boot/Image is ready
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
UIMAGE arch/arm/boot/uImage
Image Name: Linux-2.6.39-rc6
Created: Sun May 8 09:47:21 2011
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:2147104 Bytes = 2096.78 kB = 2.05 MB
Load Address: 8000
Entry Point: 8000
Image arch/arm/boot/uImage is ready
Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us.
-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/BANLkTi�fxbxf+4nsyaglblj0pvfk9...@mail.gmail.com
Bug#626031: debian-kernel-handbook: please support U-Boot format images.
* Hector Oron hector.o...@gmail.com [2011-05-08 11:27]: I think machine_ID and kernel_format (uImage|vmlinuz|vmlinux) could easily be fields in the architecture config files (defines). How does this help? We ship one kernel image for a platform and this will run on several machines (which have their own machine IDs?) Having a kernel task that overrides machine ID (when needed) does not seem to be a complicated task either. OTOH, we simplify `debian-installer` and `flash-kernel` (where code is If I understand you correctly, you're basically proposing moving the flash-kernel code into the linux-2.6 postinst? What's a multi-boot uImage? Sorry, I mean an u-boot multi-boot image that contains both the kernel and the ramdisk. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110508104501.gc12...@jirafa.cyrius.com
Bug#626031: debian-kernel-handbook: please support U-Boot format images.
Hi, 2011/5/8 Martin Michlmayr t...@cyrius.com: * Hector Oron hector.o...@gmail.com [2011-05-08 11:27]: I think machine_ID and kernel_format (uImage|vmlinuz|vmlinux) could easily be fields in the architecture config files (defines). How does this help? We ship one kernel image for a platform and this will run on several machines (which have their own machine IDs?) Well, correct me if I am wrong, but in Linux kernel I find, i.e.: arch/arm/mach-tegra/Makefile.boot:1:zreladdr-$(CONFIG_ARCH_TEGRA_2x_SOC) := 0x8000 arch/arm/mach-mx5/Makefile.boot:1: zreladdr-$(CONFIG_ARCH_MX50) := 0x70008000 arch/arm/mach-mx5/Makefile.boot:4: zreladdr-$(CONFIG_ARCH_MX51) := 0x90008000 arch/arm/mach-mx5/Makefile.boot:7: zreladdr-$(CONFIG_ARCH_MX53) := 0x70008000 arch/arm/mach-kirkwood/Makefile.boot:1: zreladdr-y:= 0x8000 etc... Load address and entry point is coded in kernel source used by mkimage when uImage kernel target is called. So having a field in debian/config/$arch/defines kernel-format: uImage should build uImage with default addresses provided by Linux kernel. The rest of the magic still needs to happen in `flash-kernel`, basically device dependent code. Machine ID stuff cannot go in kernel package. Note that if we are more comfortable using vmlinuz, we could allow: kernel-format: uImage, vmlinuz so both files get shipped in the package, having the posibility of overriding default uImage if needed. Having a kernel task that overrides machine ID (when needed) does not seem to be a complicated task either. OTOH, we simplify `debian-installer` and `flash-kernel` (where code is If I understand you correctly, you're basically proposing moving the flash-kernel code into the linux-2.6 postinst? Just the uImage generation part. (And we gain hooks very cheap?) uInitrd, boot scripts (boot.scr) and machine ID hackery probably needs to live where it is now. What's a multi-boot uImage? Sorry, I mean an u-boot multi-boot image that contains both the kernel and the ramdisk. It can probably still be generated, as my proposal does not try to conflict with current design, but allow for simplification and both solutions are compatible at the same time. Best regards, -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us. -- Day DVB-T stop working nicely Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktikf_vwjsvstxg70k-o9vcnsk3h...@mail.gmail.com
Bug#626031: debian-kernel-handbook: please support U-Boot format images.
* Hector Oron hector.o...@gmail.com [2011-05-08 12:19]: Machine ID stuff cannot go in kernel package. Right. And that's the reason why I don't understand why you'd want to put an uImage into the kernel package. We just need to take the uImage apart again, add the machine ID and generate an uImage again. Can you describe what you intend to achieve by shipping the uImage in the kernel package? It can probably still be generated, as my proposal does not try to conflict with current design, but allow for simplification and both solutions are compatible at the same time. Ok, good. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110508112904.gg12...@jirafa.cyrius.com
Bug#626057: linux-image-2.6-amd64: oops copying file
Package: linux-image-2.6-amd64 Severity: important Hi! I try to copy / move file to a smb share using nautilus. I got an kernel oops Here the dmesg output after resuming the box [ 963.340370] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,commit=120,commit=0 [ 963.344790] EXT4-fs (sda5): re-mounted. Opts: commit=120,commit=0 [ 963.545697] EXT4-fs (sda10): re-mounted. Opts: commit=120,commit=0 [ 963.563811] EXT4-fs (sda8): re-mounted. Opts: commit=120,commit=0 [ 963.737258] EXT4-fs (sda7): re-mounted. Opts: commit=120,commit=0 [ 964.529867] PM: Marking nosave pages: 0009e000 - 0010 [ 964.529876] PM: Marking nosave pages: b9e6 - b9ebf000 [ 964.529883] PM: Marking nosave pages: b9f8 - b9fbf000 [ 964.529889] PM: Marking nosave pages: b9fe2000 - b9ff7000 [ 964.529893] PM: Marking nosave pages: ba00 - 0001 [ 964.532898] PM: Basic memory bitmaps created [ 964.532900] PM: Syncing filesystems ... done. [ 964.714599] Freezing user space processes ... (elapsed 0.01 seconds) done. [ 964.732154] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [ 964.748181] PM: Preallocating image memory... done (allocated 598169 pages) [ 965.79] PM: Allocated 2392676 kbytes in 1.01 seconds (2368.98 MB/s) [ 965.766673] Suspending console(s) (use no_console_suspend to debug) [ 965.772434] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 965.980093] HDA Intel :00:1b.0: PCI INT A disabled [ 965.980143] ACPI handle has no context! [ 965.996045] PM: freeze of devices complete after 228.827 msecs [ 965.996651] PM: late freeze of devices complete after 0.600 msecs [ 965.997374] ACPI: Preparing to enter system sleep state S4 [ 966.016067] PM: Saving platform NVS memory [ 966.018460] Disabling non-boot CPUs ... [ 966.124038] CPU 1 is now offline [ 966.124621] PM: Creating hibernation image: [ 966.128010] PM: Need to copy 374634 pages [ 966.128010] PM: Normal pages needed: 374634 + 1024, available pages: 648990 [ 966.128010] PM: Restoring platform NVS memory [ 966.128010] Enabling non-boot CPUs ... [ 966.128010] Booting Node 0 Processor 1 APIC 0x1 [ 966.212411] NMI watchdog enabled, takes one hw-pmu counter. [ 966.216017] Switched to NOHz mode on CPU #1 [ 966.216063] CPU1 is up [ 966.217863] ACPI: Waking up from system sleep state S4 [ 966.341539] HDA Intel :00:1b.0: restoring config space at offset 0x1 (was 0x16, writing 0x12) [ 966.341590] pcieport :00:1c.0: restoring config space at offset 0x7 (was 0x20002020, writing 0x2020) [ 966.341668] pcieport :00:1c.3: restoring config space at offset 0x7 (was 0x20001010, writing 0x1010) [ 966.342027] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b00403, writing 0x2b00407) [ 966.342499] PM: early restore of devices complete after 1.218 msecs [ 966.496233] i915 :00:02.0: setting latency timer to 64 [ 966.496466] uhci_hcd :00:1a.0: setting latency timer to 64 [ 966.496514] usb usb3: root hub lost power or was reset [ 966.496534] ehci_hcd :00:1a.7: setting latency timer to 64 [ 966.496561] usb usb1: root hub lost power or was reset [ 966.500463] ehci_hcd :00:1a.7: cache line size of 64 is not supported [ 966.500484] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 966.500493] HDA Intel :00:1b.0: setting latency timer to 64 [ 966.500555] HDA Intel :00:1b.0: irq 45 for MSI/MSI-X [ 966.500619] uhci_hcd :00:1d.0: setting latency timer to 64 [ 966.500664] usb usb4: root hub lost power or was reset [ 966.500678] uhci_hcd :00:1d.1: setting latency timer to 64 [ 966.500723] usb usb5: root hub lost power or was reset [ 966.500737] uhci_hcd :00:1d.2: setting latency timer to 64 [ 966.500780] usb usb6: root hub lost power or was reset [ 966.500798] ehci_hcd :00:1d.7: setting latency timer to 64 [ 966.500820] usb usb2: root hub lost power or was reset [ 966.504703] ehci_hcd :00:1d.7: cache line size of 64 is not supported [ 966.504718] pci :00:1e.0: setting latency timer to 64 [ 966.504737] ahci :00:1f.2: setting latency timer to 64 [ 966.505044] sd 0:0:0:0: [sda] Starting disk [ 966.832173] ata2: SATA link down (SStatus 0 SControl 300) [ 966.840174] ata6: SATA link down (SStatus 0 SControl 300) [ 966.848172] ata5: SATA link down (SStatus 0 SControl 300) [ 966.972162] usb 6-2: reset full speed USB device using uhci_hcd and address 2 [ 966.996166] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 966.998542] ata1.00: configured for UDMA/133 [ 967.123486] btusb 6-2:1.0: no reset_resume for driver btusb? [ 967.123491] btusb 6-2:1.1: no reset_resume for driver btusb? [ 967.216124] usb 2-5: reset high speed USB device using ehci_hcd and address 2 [ 967.460087] usb 3-1: reset full speed USB device using uhci_hcd and address 2 [ 967.612449] PM: restore of devices complete after 1116.357 msecs [
Bug#626031: debian-kernel-handbook: please support U-Boot format images.
Hi, 2011/5/8 Martin Michlmayr t...@cyrius.com: * Hector Oron hector.o...@gmail.com [2011-05-08 12:19]: Machine ID stuff cannot go in kernel package. Right. And that's the reason why I don't understand why you'd want to put an uImage into the kernel package. We just need to take the uImage apart again, add the machine ID and generate an uImage again. OK, I understand that, I did not had such a deep thought on machine ID stuff. Maybe because I was not thinking it is the general case, do we always change machine ID? IIUC, few devices need to change ID, if I am wrong then it is probably not worth to implement such behaviour. Can you describe what you intend to achieve by shipping the uImage in the kernel package? On device I can do: make uImage cp arch/arm/boot/uImage /boot/ (more or less) and it should work. Then I am trying to apt-get install kernel and have an uImage installed, which already triggers initramfs and initramfs triggers flash-kernel for converting initrd.img into U-Boot format and do all the tweaks we need to do on device. That should probably work for creating, updating and deleting kernel package without much hassle. This proposal is really triggered by aiming to find a solution for DebianBug#550584. -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us. -- Day DVB-T stop working nicely Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktinq06gblmrbnhkkt5jz_7rby4q...@mail.gmail.com
Bug#599121: marked as done (linux-2.6: [m68k] nfeth driver vanished? no network connectivity!)
Your message dated Sun, 08 May 2011 12:37:37 + with message-id e1qj3ev-0007v0...@franck.debian.org and subject line Bug#599121: fixed in linux-2.6 2.6.38-5 has caused the Debian Bug report #599121, regarding linux-2.6: [m68k] nfeth driver vanished? no network connectivity! 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 ow...@bugs.debian.org immediately.) -- 599121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux-2.6 Version: 2.6.32-24 Severity: important Tags: experimental sid After compiling an m68k kernel for ARAnyM using the atari platform, requiring the fix from Debian #598893 as well as a patch I've sub- mitted upstream¹ in order to allow inclusion into the Debian kernel, and getting it to boot into multiuser, I find myself with a system that doesn't support the nfeth (nat-feature) ethernet endpoint. Further grepping in sid and experimental reveals: tg@frozenfish:~/linux-2.6-2.6.32 $ fgrep -r NFETH . ../debian/config/m68k/config.atari:CONFIG_NFETH=y tg@frozenfish:~/linux-2.6-2.6.36~rc6 $ fgrep -r NFETH . ../debian/config/m68k/config.atari:CONFIG_NFETH=y So this must have been lost somewhere in the progress; I believe it was available in linux-image-2.6.29-2-atari_2.6.29-5_m68k and can say for sure 2.6.26-1-atari (Debian 2.6.26-13) had it. With having *either* TLS *or* (virtual) networking but not both, and having to rely on VMs to develop, this unfortunately brings my attempts at helping reviving m68k to just another stop. So, please bring back these patches. Thanks in advance! ① http://thread.gmane.org/gmane.linux.ports.m68k/1580/focus=1581 I'll reportbug this separately once the maintainer accepted it. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: m68k Kernel: Linux 2.6.32-5-atari Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/mksh-static ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.38-5 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.38-5.diff.gz to main/l/linux-2.6/linux-2.6_2.6.38-5.diff.gz linux-2.6_2.6.38-5.dsc to main/l/linux-2.6/linux-2.6_2.6.38-5.dsc linux-doc-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-doc-2.6.38_2.6.38-5_all.deb linux-manual-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-manual-2.6.38_2.6.38-5_all.deb linux-patch-debian-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.38_2.6.38-5_all.deb linux-source-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-source-2.6.38_2.6.38-5_all.deb linux-support-2.6.38-2_2.6.38-5_all.deb to main/l/linux-2.6/linux-support-2.6.38-2_2.6.38-5_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 599...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 May 2011 21:24:55 +0100 Source: linux-2.6 Binary: linux-tools-2.6.38 linux-source-2.6.38 linux-doc-2.6.38 linux-manual-2.6.38 linux-patch-debian-2.6.38 linux-support-2.6.38-2 linux-libc-dev linux-headers-2.6.38-2-all linux-headers-2.6.38-2-all-alpha linux-headers-2.6.38-2-common linux-image-2.6.38-2-alpha-generic linux-headers-2.6.38-2-alpha-generic linux-image-2.6.38-2-alpha-smp linux-headers-2.6.38-2-alpha-smp linux-image-2.6.38-2-alpha-legacy linux-headers-2.6.38-2-alpha-legacy linux-headers-2.6.38-2-all-amd64 linux-image-2.6.38-2-amd64 linux-headers-2.6.38-2-amd64 linux-image-2.6.38-2-amd64-dbg linux-headers-2.6.38-2-all-armel linux-image-2.6.38-2-iop32x linux-headers-2.6.38-2-iop32x linux-image-2.6.38-2-ixp4xx linux-headers-2.6.38-2-ixp4xx linux-image-2.6.38-2-kirkwood linux-headers-2.6.38-2-kirkwood linux-image-2.6.38-2-orion5x linux-headers-2.6.38-2-orion5x linux-image-2.6.38-2-versatile linux-headers-2.6.38-2-versatile linux-headers-2.6.38-2a-all linux-headers-2.6.38-2a-all-hppa linux-headers-2.6.38-2a-common linux-image-2.6.38-2a-parisc linux-headers-2.6.38-2a-parisc
Bug#623808: marked as done (Please activate RT33XX options)
Your message dated Sun, 08 May 2011 12:37:37 + with message-id e1qj3ev-0007v6...@franck.debian.org and subject line Bug#623808: fixed in linux-2.6 2.6.38-5 has caused the Debian Bug report #623808, regarding Please activate RT33XX options 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 ow...@bugs.debian.org immediately.) -- 623808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.38-3 Severity: wishlist Tags: sid Hi, As there was not follow-up on my email to the list, I'm sending this bug report, in the hope that it will bring attention to the kernel team. I have an old laptop with a bad internal WiFi board, so I bought a newer RaLink driver. To make it work, I had to add the option rt2800usb - Include support for rt33xx devices (EXPERIMENTAL) and rt2800usb - Include support for rt35xx devices (EXPERIMENTAL). These are not activated in your build (I've just checked). I believe that one of the most important point of running a backported kernel is to have such drivers for newer hardware. Could you please include the option above? The options to activate are as below: CONFIG_RT2800PCI_RT33XX CONFIG_RT2800PCI_RT35XX CONFIG_RT2800USB_RT33XX CONFIG_RT2800USB_RT35XX If you include the above options, I'll be able to test your backport instead of the quick and dirty one that I did myself. Thanks, and keep-up the good work, Thomas Goirand (zigo) -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.38-5 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.38-5.diff.gz to main/l/linux-2.6/linux-2.6_2.6.38-5.diff.gz linux-2.6_2.6.38-5.dsc to main/l/linux-2.6/linux-2.6_2.6.38-5.dsc linux-doc-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-doc-2.6.38_2.6.38-5_all.deb linux-manual-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-manual-2.6.38_2.6.38-5_all.deb linux-patch-debian-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.38_2.6.38-5_all.deb linux-source-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-source-2.6.38_2.6.38-5_all.deb linux-support-2.6.38-2_2.6.38-5_all.deb to main/l/linux-2.6/linux-support-2.6.38-2_2.6.38-5_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 623...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 May 2011 21:24:55 +0100 Source: linux-2.6 Binary: linux-tools-2.6.38 linux-source-2.6.38 linux-doc-2.6.38 linux-manual-2.6.38 linux-patch-debian-2.6.38 linux-support-2.6.38-2 linux-libc-dev linux-headers-2.6.38-2-all linux-headers-2.6.38-2-all-alpha linux-headers-2.6.38-2-common linux-image-2.6.38-2-alpha-generic linux-headers-2.6.38-2-alpha-generic linux-image-2.6.38-2-alpha-smp linux-headers-2.6.38-2-alpha-smp linux-image-2.6.38-2-alpha-legacy linux-headers-2.6.38-2-alpha-legacy linux-headers-2.6.38-2-all-amd64 linux-image-2.6.38-2-amd64 linux-headers-2.6.38-2-amd64 linux-image-2.6.38-2-amd64-dbg linux-headers-2.6.38-2-all-armel linux-image-2.6.38-2-iop32x linux-headers-2.6.38-2-iop32x linux-image-2.6.38-2-ixp4xx linux-headers-2.6.38-2-ixp4xx linux-image-2.6.38-2-kirkwood linux-headers-2.6.38-2-kirkwood linux-image-2.6.38-2-orion5x linux-headers-2.6.38-2-orion5x linux-image-2.6.38-2-versatile linux-headers-2.6.38-2-versatile linux-headers-2.6.38-2a-all linux-headers-2.6.38-2a-all-hppa linux-headers-2.6.38-2a-common linux-image-2.6.38-2a-parisc linux-headers-2.6.38-2a-parisc linux-image-2.6.38-2a-parisc-smp linux-headers-2.6.38-2a-parisc-smp linux-image-2.6.38-2a-parisc64 linux-headers-2.6.38-2a-parisc64 linux-image-2.6.38-2a-parisc64-smp linux-headers-2.6.38-2a-parisc64-smp
Bug#624505: marked as done (linux-image-2.6.38-2-amd64: easycap.ko module not enabled)
Your message dated Sun, 08 May 2011 12:37:37 + with message-id e1qj3ev-0007vb...@franck.debian.org and subject line Bug#624505: fixed in linux-2.6 2.6.38-5 has caused the Debian Bug report #624505, regarding linux-image-2.6.38-2-amd64: easycap.ko module not enabled 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 ow...@bugs.debian.org immediately.) -- 624505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.38-3 Severity: wishlist Tags: upstream please include easycap.ko (staging) driver as a module in kernel. -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 ** Command line: root=/dev/mapper/sda2_crypt ro ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 29.436244] ACPI: AC Adapter [ADP1] (on-line) [ 29.511338] wmi: Mapper loaded [ 29.619054] input: PC Speaker as /devices/platform/pcspkr/input/input6 [ 29.820219] ACPI: Battery Slot [BAT1] (battery present) [ 30.130248] cfg80211: Calling CRDA to update world regulatory domain [ 30.204421] [drm] Initialized drm 1.1.0 20060810 [ 30.575955] Synaptics Touchpad, model: 1, fw: 6.1, id: 0xa3a0b3, caps: 0xa04713/0x10008/0x0 [ 30.649195] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input7 [ 30.698296] i801_smbus :00:1f.3: PCI INT C - GSI 18 (level, low) - IRQ 18 [ 30.924998] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree: [ 30.925084] iwlagn: Copyright(c) 2003-2010 Intel Corporation [ 30.925246] iwlagn :05:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [ 30.925317] iwlagn :05:00.0: setting latency timer to 64 [ 30.925348] iwlagn :05:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54 [ 30.935224] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 30.935337] i915 :00:02.0: setting latency timer to 64 [ 30.948570] iwlagn :05:00.0: device EEPROM VER=0x11f, CALIB=0x4 [ 30.948637] iwlagn :05:00.0: Device SKU: 0Xb [ 30.948925] iwlagn :05:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [ 30.949087] iwlagn :05:00.0: irq 45 for MSI/MSI-X [ 30.974485] mtrr: type mismatch for d000,1000 old: write-back new: write-combining [ 30.974566] [drm] MTRR allocation failed. Graphics performance may suffer. [ 30.975042] i915 :00:02.0: irq 46 for MSI/MSI-X [ 30.975049] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 30.975112] [drm] Driver supports precise vblank timestamp query. [ 31.055124] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 31.055537] fixme: max PWM is zero. [ 31.256986] iwlagn :05:00.0: loaded firmware version 8.83.5.1 build 33692 [ 31.451081] Console: switching to colour frame buffer device 160x50 [ 31.454061] fb0: inteldrmfb frame buffer device [ 31.454085] drm: registered panic notifier [ 31.461984] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 31.477419] acpi device:28: registered as cooling_device2 [ 31.478011] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input8 [ 31.478172] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 31.478564] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 31.635249] Linux video capture interface: v2.00 [ 31.706700] uvcvideo: Found UVC 1.00 device BisonCam, NB Pro (5986:0203) [ 31.710243] input: BisonCam, NB Pro as /devices/pci:00/:00:1a.7/usb1/1-2/1-2:1.0/input/input9 [ 31.710437] usbcore: registered new interface driver uvcvideo [ 31.710470] USB Video Class driver (v1.0.0) [ 31.730680] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 31.730802] HDA Intel :00:1b.0: irq 47 for MSI/MSI-X [ 31.730835] HDA Intel :00:1b.0: setting latency timer to 64 [ 32.041818] hda_codec: ALC888: BIOS auto-probing. [ 32.041853] hda_codec: ALC888: SKU not ready 0x598301f0 [ 32.043097] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input10 [ 32.120633] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input11 [ 34.263060] EXT3-fs (dm-0): using internal journal [ 34.490912] loop: module loaded [ 35.194151] fuse init (API version 7.16) [ 35.391503] EXT3-fs: barriers not enabled [ 35.393515] kjournald starting. Commit interval 5 seconds [ 35.393827] EXT3-fs (sda1):
Bug#626031: marked as done (debian-kernel-handbook: please support U-Boot format images.)
Your message dated Sun, 8 May 2011 13:45:00 +0100
with message-id BANLkTi=nzyfnys7dpxs8u44vog80tsc...@mail.gmail.com
and subject line Re: Bug#626031: debian-kernel-handbook: please support U-Boot
format images.
has caused the Debian Bug report #626031,
regarding debian-kernel-handbook: please support U-Boot format images.
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 ow...@bugs.debian.org
immediately.)
--
626031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debian-kernel-handbook
Version: 1.0.10
Severity: wishlist
Tags: patch
Hello,
While looking to DebianBug#550584, I wonder why do we need to carry
with the burden of maintaining hardcoded stuff for some architectures,
while part of it is maintained by Linux kernel upstream developers.
Adding support for U-Boot image format ('uImage' kernel target) in
official kernel packages seem to me the right thing to do, it would
not only simplify `flash-kernel` (see #108 comments for a `flash-kernel`
summary of issues) but also `debian-installer` which currently have to
add extra code to support U-Boot image format per device. Part of that
extra code could be reduced by allowing U-Boot format images in official
packages.
Regarding initramfs generation, it could be generated as usual by initramfs
tools but if platform uses U-Boot format after creating, updating or deleting
initrd.img it should call the uinitrd.img handler (nowadays flash-kernel) with
a couple parameters:
The following patch against SVN trunk (r89) ammends kernel handbook policy
for allowing U-Boot image format support (and also fixes some indentation
to be coherent with writting style).
Index: chapter-initramfs.sgml
===
--- chapter-initramfs.sgml (revision 89)
+++ chapter-initramfs.sgml (working copy)
@@ -63,7 +63,7 @@
sect id=initramfs-gen-process
headingChoosing the tool/heading
p
- At the end of the kernel package installation a script is
+At the end of the kernel package installation a script is
automatically invoked to determine the availability of the
initramfs-generating tools and run one of them. This script
contains the list of all such tools available in Debian.
@@ -96,20 +96,33 @@
be regenerated. This is achieved by the command
example
# dpkg-reconfigure linux-image-2.6.18-3-686
-/example
-where ttlinux-image-2.6.18-3-686/tt is the name of the
+ /example
+ where ttlinux-image-2.6.18-3-686/tt is the name of the
kernel package for which the initramfs regeneration is requested.
+ /p
/sect
sect id=initramfs-exam
headingExamining the initramfs contents/heading
- p
+ p
Occasionally it is useful to examine the contents of initramfs
to diagnose a problem or for educational purposes. They are
compressed ttcpio/tt archives, which may be extracted
using the command
example
$ zcat /boot/initrd.img-2.6.18-3-686 | cpio -i
-/example
+ /example
It will unpack the contents of the initramfs into the current directory.
+ /p
/sect
+ sect id=initramfs-uimage
+headingGenerating U-Boot format initramfs images
(uinitrd.img)/heading
+ p
+If U-Boot format (ttuImage/tt) Linux kernel image exists
+ initramfs generation tool must run to create, update or delete initramfs
+ after each one of those tasks it must pass control to the uinitrd.img
+ generation tool, nowadays the only known tool ttflash-kernel/tt
passing
+ two arguments: action performed (create, update, delete) and
+
emversion/em-emabiname/em[-emfeatureset/em]-emflavour/em.
+ /p
+ /sect
/chapt
Index: chapter-update-hooks.sgml
===
--- chapter-update-hooks.sgml (revision 89)
+++ chapter-update-hooks.sgml (working copy)
@@ -28,7 +28,8 @@
optionally, the absolute path to the kernel image. If the
second argument is missing then the path is
either tt/boot/vmlinuz-emversion/em/tt or
- tt/boot/vmlinux-emversion/em/tt, according to
+ tt/boot/vmlinux-emversion/em/tt or
+ tt/boot/uImage-emversion/em/tt, according to
architecture convention. The environment variable
ttDEB_MAINT_PARAMS/tt will contain the arguments given to
the kernel maintainer script, possibly single-quoted. In a
linux-2.6_2.6.38-5_multi.changes ACCEPTED into unstable
Accepted: linux-2.6_2.6.38-5.diff.gz to main/l/linux-2.6/linux-2.6_2.6.38-5.diff.gz linux-2.6_2.6.38-5.dsc to main/l/linux-2.6/linux-2.6_2.6.38-5.dsc linux-doc-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-doc-2.6.38_2.6.38-5_all.deb linux-manual-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-manual-2.6.38_2.6.38-5_all.deb linux-patch-debian-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.38_2.6.38-5_all.deb linux-source-2.6.38_2.6.38-5_all.deb to main/l/linux-2.6/linux-source-2.6.38_2.6.38-5_all.deb linux-support-2.6.38-2_2.6.38-5_all.deb to main/l/linux-2.6/linux-support-2.6.38-2_2.6.38-5_all.deb Override entries for your package: linux-2.6_2.6.38-5.dsc - source devel linux-doc-2.6.38_2.6.38-5_all.deb - optional doc linux-manual-2.6.38_2.6.38-5_all.deb - optional doc linux-patch-debian-2.6.38_2.6.38-5_all.deb - optional kernel linux-source-2.6.38_2.6.38-5_all.deb - optional kernel linux-support-2.6.38-2_2.6.38-5_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 599121 623808 624505 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qj3ev-0007uu...@franck.debian.org
linux-latest-2.6_34_multi.changes ACCEPTED into unstable
Accepted: linux-doc-2.6_2.6.38+34_all.deb to main/l/linux-latest-2.6/linux-doc-2.6_2.6.38+34_all.deb linux-headers-2.6-486_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-486_2.6.38+34_i386.deb linux-headers-2.6-686-bigmem_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-686-bigmem_2.6.38+34_i386.deb linux-headers-2.6-686_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-686_2.6.38+34_i386.deb linux-headers-2.6-amd64_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-headers-2.6-amd64_2.6.38+34_i386.deb linux-image-2.6-486_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-486_2.6.38+34_i386.deb linux-image-2.6-686-bigmem_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-686-bigmem_2.6.38+34_i386.deb linux-image-2.6-686_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-686_2.6.38+34_i386.deb linux-image-2.6-amd64_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-image-2.6-amd64_2.6.38+34_i386.deb linux-image-486_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-image-486_2.6.38+34_i386.deb linux-image-686-bigmem_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-image-686-bigmem_2.6.38+34_i386.deb linux-image-686_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-image-686_2.6.38+34_i386.deb linux-image-amd64_2.6.38+34_i386.deb to main/l/linux-latest-2.6/linux-image-amd64_2.6.38+34_i386.deb linux-latest-2.6_34.dsc to main/l/linux-latest-2.6/linux-latest-2.6_34.dsc linux-latest-2.6_34.tar.gz to main/l/linux-latest-2.6/linux-latest-2.6_34.tar.gz linux-source-2.6_2.6.38+34_all.deb to main/l/linux-latest-2.6/linux-source-2.6_2.6.38+34_all.deb linux-tools-2.6_2.6.38+34_all.deb to main/l/linux-latest-2.6/linux-tools-2.6_2.6.38+34_all.deb Override entries for your package: linux-doc-2.6_2.6.38+34_all.deb - optional kernel linux-headers-2.6-486_2.6.38+34_i386.deb - optional kernel linux-headers-2.6-686-bigmem_2.6.38+34_i386.deb - optional kernel linux-headers-2.6-686_2.6.38+34_i386.deb - optional kernel linux-headers-2.6-amd64_2.6.38+34_i386.deb - optional kernel linux-image-2.6-486_2.6.38+34_i386.deb - optional kernel linux-image-2.6-686-bigmem_2.6.38+34_i386.deb - optional kernel linux-image-2.6-686_2.6.38+34_i386.deb - optional kernel linux-image-2.6-amd64_2.6.38+34_i386.deb - optional kernel linux-image-486_2.6.38+34_i386.deb - optional kernel linux-image-686-bigmem_2.6.38+34_i386.deb - optional kernel linux-image-686_2.6.38+34_i386.deb - optional kernel linux-image-amd64_2.6.38+34_i386.deb - optional kernel linux-latest-2.6_34.dsc - source admin linux-source-2.6_2.6.38+34_all.deb - optional kernel linux-tools-2.6_2.6.38+34_all.deb - optional kernel Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qj3fg-00089g...@franck.debian.org
upload 2.6.39-rc6 exp
there will be soon an rc7, so nothing interesting to be seen yet. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110508125343.ga23...@stro.at
Bug#625804: linux-2.6: fix rtc lockups on armhf
Hi, On Sun, May 08, 2011 at 01:14:11AM +0100, Hector Oron wrote: Here is a proposed patch against trunk for fixing this bug. Patch was written initial by Arnaud Patard, later changed by Uwe Kleine-König. I have built a kernel with the following patch and I have been able to reproduce the lockup. Currently building another kernel with Arnaud patch to test. -- Héctor Orón Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us. -- Day DVB-T stop working nicely Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html signature.asc Description: Digital signature
Processing of linux-2.6_2.6.39~rc6-1~experimental.1_amd64.changes
linux-2.6_2.6.39~rc6-1~experimental.1_amd64.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.39~rc6-1~experimental.1.dsc linux-2.6_2.6.39~rc6.orig.tar.gz linux-2.6_2.6.39~rc6-1~experimental.1.diff.gz linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-support-2.6.39-rc6_2.6.39~rc6-1~experimental.1_all.deb linux-image-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-image-2.6.39-rc6-amd64-dbg_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-common_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-all_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-all-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qj616-00035p...@franck.debian.org
linux-2.6_2.6.39~rc6-1~experimental.1_amd64.changes is NEW
linux-2.6_2.6.39~rc6-1~experimental.1.diff.gz
to main/l/linux-2.6/linux-2.6_2.6.39~rc6-1~experimental.1.diff.gz
linux-2.6_2.6.39~rc6-1~experimental.1.dsc
to main/l/linux-2.6/linux-2.6_2.6.39~rc6-1~experimental.1.dsc
linux-2.6_2.6.39~rc6.orig.tar.gz
to main/l/linux-2.6/linux-2.6_2.6.39~rc6.orig.tar.gz
linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb
to main/l/linux-2.6/linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb
(new) linux-headers-2.6.39-rc6-all-amd64_2.6.39~rc6-1~experimental.1_amd64.deb
optional kernel
All header files for Linux 2.6.39 (meta-package)
This package depends against all architecture-specific kernel header files
for Linux kernel version 2.6.39-rc6, generally used for building
out-of-tree kernel modules.
(new) linux-headers-2.6.39-rc6-all_2.6.39~rc6-1~experimental.1_amd64.deb
optional kernel
All header files for Linux 2.6.39 (meta-package)
This package depends against all architecture-specific kernel header files
for Linux kernel version 2.6.39-rc6, generally used for building
out-of-tree kernel modules.
(new) linux-headers-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb
optional kernel
Header files for Linux 2.6.39-rc6-amd64
This package provides the architecture-specific kernel header files for
Linux kernel 2.6.39-rc6-amd64, generally used for building out-of-tree
kernel modules. These files are going to be installed into
/usr/src/linux-headers-2.6.39-rc6-amd64, and can be used for building
modules that load into the kernel provided by the
linux-image-2.6.39-rc6-amd64 package.
(new) linux-headers-2.6.39-rc6-common_2.6.39~rc6-1~experimental.1_amd64.deb
optional kernel
Common header files for Linux 2.6.39-rc6
This package provides the architecture-specific common kernel header files
for Linux kernel version 2.6.39-rc6, generally used for building
out-of-tree kernel modules. To obtain a complete set of headers you also
need to install the linux-headers-2.6.39-rc6-(flavour) package, matching
the flavour of the kernel you intend the build for.
(new) linux-image-2.6.39-rc6-amd64-dbg_2.6.39~rc6-1~experimental.1_amd64.deb
extra debug
Debugging infos for Linux 2.6.39-rc6-amd64
This package provides the binary debug image and pre-built debug loadable
modules for Linux kernel 2.6.39-rc6 on PCs with AMD64 or Intel 64
processors machines.
(new) linux-image-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb
optional kernel
Linux 2.6.39-rc6 for 64-bit PCs
The Linux kernel 2.6.39-rc6 and modules for use on PCs with AMD64 or Intel
64 processors.
.
This kernel also runs on a Xen hypervisor. It supports only unprivileged
(domU) operation.
linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb
to main/l/linux-2.6/linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb
linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb
to main/l/linux-2.6/linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb
linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb
to
main/l/linux-2.6/linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb
linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb
to main/l/linux-2.6/linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb
(new) linux-support-2.6.39-rc6_2.6.39~rc6-1~experimental.1_all.deb optional
devel
Support files for Linux 2.6.39-rc6
This package provides support files for the Linux kernel build, e.g.
scripts to handle ABI information and for generation of build system meta
data.
linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb
to main/l/linux-2.6/linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb
Changes: linux-2.6 (2.6.39~rc6-1~experimental.1) experimental; urgency=low
.
* New upstream release candidate
.
[ maximilian attems ]
* Enable SQUASHFS_{LZO,XZ}. (closes: #613658)
* [x86] Enable EASYCAP. (closes: #624505)
.
[ Ben Hutchings
* xhci-hcd: Include linux/slab.h in xhci-pci.c (fixes FTBFS on armel)
* [x86] Enable BRCMSMAC; the brcmsmac module replaces brcm80211
(Closes: #625510)
.
[ Aurelien Jarno ]
* drm/nouveau, drm/radeon: remove fix for non-powerpc/sparc/x86.
* [mips,mipsel] Disabled CONFIG_DRM_NOUVEAU and CONFIG_DRM_RADEON_KMS.
* [mips/octeon] Disabled CONFIG_HOTPLUG_CPU and CONFIG_PM.
Override entries for your package:
linux-2.6_2.6.39~rc6-1~experimental.1.dsc - source devel
linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb - optional doc
linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb - optional devel
linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb - optional doc
linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb - optional kernel
linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb - optional kernel
linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb - optional kernel
Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 613658 624505 625510
Your package contains new components which requires manual editing of
the override file. It is ok otherwise, so please be patient. New
Bug#625804: linux-2.6: fix rtc lockups on armhf
Hi, 2011/5/8 Hector Oron zu...@debian.org: Hi, On Sun, May 08, 2011 at 01:14:11AM +0100, Hector Oron wrote: Here is a proposed patch against trunk for fixing this bug. Patch was written initial by Arnaud Patard, later changed by Uwe Kleine-König. I have built a kernel with the following patch and I have been able to reproduce the lockup. Currently building another kernel with Arnaud patch to test. With Arnaud patch I have not seen the lockup. :-? Cheers, -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us. -- Day DVB-T stop working nicely Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTi=ob8x7ugxscc44y14ppmozz1x...@mail.gmail.com
Bug#613658: marked as done (Please enable SQUASHFS_XZ et al for =2.6.38-rc1.)
Your message dated Sun, 08 May 2011 19:25:08 + with message-id e1qj9bi-00054d...@franck.debian.org and subject line Bug#613658: fixed in linux-2.6 2.6.39~rc6-1~experimental.1 has caused the Debian Bug report #613658, regarding Please enable SQUASHFS_XZ et al for =2.6.38-rc1. 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 ow...@bugs.debian.org immediately.) -- 613658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: wishlist Tags: experimental User: debian-l...@live.debian.org Usertags: kernel xz (a.k.a. LZMA2) is a shiny new compression algorithm that yields smaller files than gzip, and is faster than bzip2. For Debian Live images, especially, it would be nice to have better compression of the squashfs root filesystem. This can be done by setting SQUASHFS_XZ=y This was introduced between .37 and .38-rc1. Less important, but probably Nice To Have, are squashfs LZO support, ramdisk XZ support, and this BCJ (a.k.a. DEC, below) stuff, which appears to allow arch-specific tweaks to compact the squashfs further. CONFIG_SQUASHFS_LZO=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_RD_XZ=y CONFIG_XZ_DEC=y CONFIG_XZ_DEC_X86=y CONFIG_XZ_DEC_POWERPC=y CONFIG_XZ_DEC_IA64=y CONFIG_XZ_DEC_ARM=y CONFIG_XZ_DEC_ARMTHUMB=y CONFIG_XZ_DEC_SPARC=y CONFIG_XZ_DEC_BCJ=y CONFIG_XZ_DEC_TEST=m -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.39~rc6-1~experimental.1 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.39~rc6-1~experimental.1.diff.gz to main/l/linux-2.6/linux-2.6_2.6.39~rc6-1~experimental.1.diff.gz linux-2.6_2.6.39~rc6-1~experimental.1.dsc to main/l/linux-2.6/linux-2.6_2.6.39~rc6-1~experimental.1.dsc linux-2.6_2.6.39~rc6.orig.tar.gz to main/l/linux-2.6/linux-2.6_2.6.39~rc6.orig.tar.gz linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-headers-2.6.39-rc6-all-amd64_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-all-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-all_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-all_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-common_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-common_2.6.39~rc6-1~experimental.1_amd64.deb linux-image-2.6.39-rc6-amd64-dbg_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.39-rc6-amd64-dbg_2.6.39~rc6-1~experimental.1_amd64.deb linux-image-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-support-2.6.39-rc6_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-support-2.6.39-rc6_2.6.39~rc6-1~experimental.1_all.deb linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 613...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems m...@debian.org (supplier of updated linux-2.6 package) (This message was
Bug#624505: marked as done (linux-image-2.6.38-2-amd64: easycap.ko module not enabled)
Your message dated Sun, 08 May 2011 19:25:08 + with message-id e1qj9bi-00054j...@franck.debian.org and subject line Bug#624505: fixed in linux-2.6 2.6.39~rc6-1~experimental.1 has caused the Debian Bug report #624505, regarding linux-image-2.6.38-2-amd64: easycap.ko module not enabled 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 ow...@bugs.debian.org immediately.) -- 624505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.38-3 Severity: wishlist Tags: upstream please include easycap.ko (staging) driver as a module in kernel. -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 ** Command line: root=/dev/mapper/sda2_crypt ro ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 29.436244] ACPI: AC Adapter [ADP1] (on-line) [ 29.511338] wmi: Mapper loaded [ 29.619054] input: PC Speaker as /devices/platform/pcspkr/input/input6 [ 29.820219] ACPI: Battery Slot [BAT1] (battery present) [ 30.130248] cfg80211: Calling CRDA to update world regulatory domain [ 30.204421] [drm] Initialized drm 1.1.0 20060810 [ 30.575955] Synaptics Touchpad, model: 1, fw: 6.1, id: 0xa3a0b3, caps: 0xa04713/0x10008/0x0 [ 30.649195] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input7 [ 30.698296] i801_smbus :00:1f.3: PCI INT C - GSI 18 (level, low) - IRQ 18 [ 30.924998] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree: [ 30.925084] iwlagn: Copyright(c) 2003-2010 Intel Corporation [ 30.925246] iwlagn :05:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [ 30.925317] iwlagn :05:00.0: setting latency timer to 64 [ 30.925348] iwlagn :05:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54 [ 30.935224] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 30.935337] i915 :00:02.0: setting latency timer to 64 [ 30.948570] iwlagn :05:00.0: device EEPROM VER=0x11f, CALIB=0x4 [ 30.948637] iwlagn :05:00.0: Device SKU: 0Xb [ 30.948925] iwlagn :05:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [ 30.949087] iwlagn :05:00.0: irq 45 for MSI/MSI-X [ 30.974485] mtrr: type mismatch for d000,1000 old: write-back new: write-combining [ 30.974566] [drm] MTRR allocation failed. Graphics performance may suffer. [ 30.975042] i915 :00:02.0: irq 46 for MSI/MSI-X [ 30.975049] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 30.975112] [drm] Driver supports precise vblank timestamp query. [ 31.055124] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 31.055537] fixme: max PWM is zero. [ 31.256986] iwlagn :05:00.0: loaded firmware version 8.83.5.1 build 33692 [ 31.451081] Console: switching to colour frame buffer device 160x50 [ 31.454061] fb0: inteldrmfb frame buffer device [ 31.454085] drm: registered panic notifier [ 31.461984] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 31.477419] acpi device:28: registered as cooling_device2 [ 31.478011] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input8 [ 31.478172] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 31.478564] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 31.635249] Linux video capture interface: v2.00 [ 31.706700] uvcvideo: Found UVC 1.00 device BisonCam, NB Pro (5986:0203) [ 31.710243] input: BisonCam, NB Pro as /devices/pci:00/:00:1a.7/usb1/1-2/1-2:1.0/input/input9 [ 31.710437] usbcore: registered new interface driver uvcvideo [ 31.710470] USB Video Class driver (v1.0.0) [ 31.730680] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 31.730802] HDA Intel :00:1b.0: irq 47 for MSI/MSI-X [ 31.730835] HDA Intel :00:1b.0: setting latency timer to 64 [ 32.041818] hda_codec: ALC888: BIOS auto-probing. [ 32.041853] hda_codec: ALC888: SKU not ready 0x598301f0 [ 32.043097] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input10 [ 32.120633] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input11 [ 34.263060] EXT3-fs (dm-0): using internal journal [ 34.490912] loop: module loaded [ 35.194151] fuse init (API version 7.16) [ 35.391503] EXT3-fs: barriers not enabled [ 35.393515] kjournald starting. Commit interval 5 seconds [
Bug#625510: marked as done (Broadcom 802.11 driver missing from 2.6.39-rc[45])
Your message dated Sun, 08 May 2011 19:25:08 + with message-id e1qj9bi-00054o...@franck.debian.org and subject line Bug#625510: fixed in linux-2.6 2.6.39~rc6-1~experimental.1 has caused the Debian Bug report #625510, regarding Broadcom 802.11 driver missing from 2.6.39-rc[45] 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 ow...@bugs.debian.org immediately.) -- 625510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.39~rc5-1~experimental.1 Severity: normal Tags: experimental The driver for my other laptops broadcom BCM4313 seems to be missing. Comparing the config files: /boot/config-2.6.38-2-686:CONFIG_BRCM80211=m /boot/config-2.6.38-2-686:CONFIG_BRCM80211_PCI=y /boot/config-2.6.38-2-686:# CONFIG_BRCMFMAC is not set /boot/config-2.6.39-rc5-686-pae:CONFIG_BRCM80211=m /boot/config-2.6.39-rc5-686-pae:# CONFIG_BRCMSMAC is not set /boot/config-2.6.39-rc5-686-pae:# CONFIG_BRCMFMAC is not set /boot/config-2.6.39-rc5-686-pae:# CONFIG_BRCMDBG is not set I wonder if maybe BRCMSMAC is the appropriate option now. A short search revealed a patch to remove CONFIG_BRCM80211 since [...] renamed to brcmsmac. Could you enable that option for the next upload? Thanks. (Not sure what the full-mac cards are that the BRCMFMAC driver is for. There I saw something that you could not have SMAC und FMAC as module at the same time (well, actually a patch that removes such a comment), but nothing yet of the benefits of one over the other. Apparently fmac does more in the hardware of the wireless card, but offering less features. Anyway, you could try enabling both, unless there is some hint that this doesn't work? Thank you for all your work on Debian! ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.39~rc6-1~experimental.1 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.39~rc6-1~experimental.1.diff.gz to main/l/linux-2.6/linux-2.6_2.6.39~rc6-1~experimental.1.diff.gz linux-2.6_2.6.39~rc6-1~experimental.1.dsc to main/l/linux-2.6/linux-2.6_2.6.39~rc6-1~experimental.1.dsc linux-2.6_2.6.39~rc6.orig.tar.gz to main/l/linux-2.6/linux-2.6_2.6.39~rc6.orig.tar.gz linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-headers-2.6.39-rc6-all-amd64_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-all-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-all_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-all_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-common_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-common_2.6.39~rc6-1~experimental.1_amd64.deb linux-image-2.6.39-rc6-amd64-dbg_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.39-rc6-amd64-dbg_2.6.39~rc6-1~experimental.1_amd64.deb linux-image-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-support-2.6.39-rc6_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-support-2.6.39-rc6_2.6.39~rc6-1~experimental.1_all.deb linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 625...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems m...@debian.org (supplier of updated
linux-2.6_2.6.39~rc6-1~experimental.1_amd64.changes ACCEPTED into experimental
Accepted: linux-2.6_2.6.39~rc6-1~experimental.1.diff.gz to main/l/linux-2.6/linux-2.6_2.6.39~rc6-1~experimental.1.diff.gz linux-2.6_2.6.39~rc6-1~experimental.1.dsc to main/l/linux-2.6/linux-2.6_2.6.39~rc6-1~experimental.1.dsc linux-2.6_2.6.39~rc6.orig.tar.gz to main/l/linux-2.6/linux-2.6_2.6.39~rc6.orig.tar.gz linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-headers-2.6.39-rc6-all-amd64_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-all-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-all_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-all_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-headers-2.6.39-rc6-common_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc6-common_2.6.39~rc6-1~experimental.1_amd64.deb linux-image-2.6.39-rc6-amd64-dbg_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.39-rc6-amd64-dbg_2.6.39~rc6-1~experimental.1_amd64.deb linux-image-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb linux-support-2.6.39-rc6_2.6.39~rc6-1~experimental.1_all.deb to main/l/linux-2.6/linux-support-2.6.39-rc6_2.6.39~rc6-1~experimental.1_all.deb linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb Override entries for your package: linux-2.6_2.6.39~rc6-1~experimental.1.dsc - source devel linux-doc-2.6.39_2.6.39~rc6-1~experimental.1_all.deb - optional doc linux-headers-2.6.39-rc6-all-amd64_2.6.39~rc6-1~experimental.1_amd64.deb - optional kernel linux-headers-2.6.39-rc6-all_2.6.39~rc6-1~experimental.1_amd64.deb - optional kernel linux-headers-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb - optional kernel linux-headers-2.6.39-rc6-common_2.6.39~rc6-1~experimental.1_amd64.deb - optional kernel linux-image-2.6.39-rc6-amd64-dbg_2.6.39~rc6-1~experimental.1_amd64.deb - extra debug linux-image-2.6.39-rc6-amd64_2.6.39~rc6-1~experimental.1_amd64.deb - optional kernel linux-libc-dev_2.6.39~rc6-1~experimental.1_amd64.deb - optional devel linux-manual-2.6.39_2.6.39~rc6-1~experimental.1_all.deb - optional doc linux-patch-debian-2.6.39_2.6.39~rc6-1~experimental.1_all.deb - optional kernel linux-source-2.6.39_2.6.39~rc6-1~experimental.1_all.deb - optional kernel linux-support-2.6.39-rc6_2.6.39~rc6-1~experimental.1_all.deb - optional devel linux-tools-2.6.39_2.6.39~rc6-1~experimental.1_amd64.deb - optional kernel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 613658 624505 625510 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qj9bi-00054u...@franck.debian.org
Bug#613658: marked as done (Please enable SQUASHFS_XZ et al for =2.6.38-rc1.)
This is very cool. It has been enabled in the experimental kernel. Is that possible the kernel in sid (2.6.38) to be enabled, too? Thanks. Steven. On 2011/5/9 上午 03:27, Debian Bug Tracking System wrote: Your message dated Sun, 08 May 2011 19:25:08 + with message-ide1qj9bi-00054d...@franck.debian.org and subject line Bug#613658: fixed in linux-2.6 2.6.39~rc6-1~experimental.1 has caused the Debian Bug report #613658, regarding Please enable SQUASHFS_XZ et al for=2.6.38-rc1. 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 ow...@bugs.debian.org immediately.) -- Steven Shiau steven _at_ nchc org tw steven _at_ stevenshiau org National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc7816d.7050...@nchc.org.tw
