Bug#489387: Please do not replace vserver with openvz.
On Fri, Aug 08, 2008 at 04:42:03PM -0500, William Pitcock wrote: It appears the plan is to drop vserver in favour of openvz, offering openvz as an alternative and perhaps default is a good option, but please do not remove vservers, as there are real people who depend on this feature. No. OpenVZ is an alternative. VServer is currently not supported because upstream is lets say in hibernation. There is simply no working patch available. Bastian -- Knowledge, sir, should be free to all! -- Harry Mudd, I, Mudd, stardate 4513.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494308: patch for e100
Hi, I'll be working on a patch for this one today. -- Robert Millan The DRM opt-in fallacy: Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: found 494308 in 2.6.18.dfsg.1-22
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 found 494308 2.6.18.dfsg.1-22 Bug#494308: binary firmware in drivers/net/e100.c Bug marked as found in version 2.6.18.dfsg.1-22. 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]
Processed: found 494308 in 2.6.18-1
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 found 494308 2.6.18-1 Bug#494308: binary firmware in drivers/net/e100.c Bug marked as found in version 2.6.18-1. 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]
Processed: severity
Processing commands for [EMAIL PROTECTED]: severity 494422 important Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot Severity set to `important' from `critical' -- 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#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot
* Monkey D. Luffy [EMAIL PROTECTED] [2008-08-09 12:05]: I reboot the system and surprise: grub was *overwritten* by lilo!!! I try to boot anyway... and another surprise: ramdisk: couldn't find valid ram disk image starting at 0 list of all partitions: no filesystem could mount root, tried: kernel panic - not syncing: VFS: unable to mount root fs in unknown-block (8,1) This is a known bug in lilo, see #479607 Although I see it was fixed in version 1:22.8-6. Which version of lilo do you have installed? I reboot the system and surprise: grub was *overwritten* by lilo!!! Maybe this is what happens when you have both grub and lilo installed. But I don't know. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494433: /sbin/vol_id: No such file or directory in preinst
Package: initramfs-tools Version: 0.92e Tags: patch preinst contains the following lines: 25 elif [ -x /lib/udev/vol_id ]; then 26 UUID=$(/sbin/vol_id -u $RESUME || true) 27 fi Line 26 clearly is a copypaste error in that it should read /lib/udev/vol_id instead of /sbin/vol_id. Changing this should fix the bug immediately (thus tagging patch). Best, Michael pgpW2DXnoYt3t.pgp Description: PGP signature
Bug#494308: patch for e100
On Sat, Aug 09, 2008 at 01:18:10PM +0200, Robert Millan wrote: I'll be working on a patch for this one today. Some advices: - Please make a minimal fix. As the firmwares are fix-only it may just remove them and the code referencing it. Please note that the patch must not include parts of the problematic code, use unifdef (see debian/patches/debian/dfsg/files-0 and the tg3 patches) to remove them and after that change anything else. This patch goes into the orig and it should not be broken because of that. - If you want (and can test it with the hardware) make the firmware loadable from userspace in a second patch. This patch goes into the normal flow and can be changed later. Bastian -- What terrible way to die. There are no good ways. -- Sulu and Kirk, That Which Survives, stardate unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494435: linux-headers-2.6.26-1-amd64: scripts/gcc-x86_64-has-stack-protector.sh missing
Package: linux-headers-2.6.26-1-amd64 Version: 2.6.26-2 Severity: normal Hello, When building external modules on linux-headers-2.6.26-1-amd64, I get the following error messages: $ make -C /usr/src/linux-headers-2.6.26-1-amd64/ M=$PWD /bin/sh: /usr/src/linux-headers-2.6.26-1-amd64/scripts/gcc-x86_64-has-stack-protector.sh: No such file or directory /bin/sh: /usr/src/linux-headers-2.6.26-1-amd64/scripts/gcc-x86_64-has-stack-protector.sh: No such file or directory make: Entering directory `/usr/src/linux-headers-2.6.26-1-amd64' [...] The build seems to complete fine anyway, so I don't know exactly what this missing file is needed for. thanks, Brice -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages linux-headers-2.6.26-1-amd64 depends on: ii gcc-4.1 4.1.2-23 The GNU C compiler ii linux-headers-2.6.26-1-common 2.6.26-2 Common header files for Linux 2.6. ii linux-kbuild-2.6.26 2.6.26-1 Kbuild infrastructure for Linux 2. linux-headers-2.6.26-1-amd64 recommends no packages. linux-headers-2.6.26-1-amd64 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494308: patch for e100
On Sat, Aug 09, 2008 at 01:18:10PM +0200, Robert Millan wrote: Hi, I'll be working on a patch for this one today. Such a patch already exists: http://lkml.org/lkml/2008/6/14/102 Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494444: linux-image-2.6.26-1-686: kacpid is in uninteruptible sleep and produces loads 1
Package: linux-image-2.6.26-1-686 Version: 2.6.26-1 Severity: normal Dear Maintainers, after upgrading to Kernel 2.6.26 I have loads 1 but no CPU usage. I discoverd that kacpid kernelthread is in uninteruptible sleep: $ ps axu | grep kacpid | grep -v grep root41 0.0 0.0 0 0 ?D 14:58 0:01 [kacpid] 'acpi -V' hang in uninteruptible sleep too and isn't killable any more: $ acpi -V Battery 1: Full, 97% AC Adapter 0: on-line Kernel linux-image-2.6.25-2-686 works well. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Jul 30 20:02:15 UTC 2008 ** Command line: root=UUID=cfa47139-db7a-41b0-a5dd-2d8d5b19b771 ro ** Not tainted ** Kernel log: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26-1-686 (Debian 2.6.26-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Jul 30 20:02:15 UTC 2008 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009f800 (usable) [0.00] BIOS-e820: 0009f800 - 000a (reserved) [0.00] BIOS-e820: 000dc000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3fee (usable) [0.00] BIOS-e820: 3fee - 3feec000 (ACPI data) [0.00] BIOS-e820: 3feec000 - 3ff0 (ACPI NVS) [0.00] BIOS-e820: 3ff0 - 4000 (reserved) [0.00] BIOS-e820: fec1 - fec2 (reserved) [0.00] BIOS-e820: ff80 - ffc0 (reserved) [0.00] BIOS-e820: fc00 - 0001 (reserved) [0.00] 126MB HIGHMEM available. [0.00] 896MB LOWMEM available. [0.00] Entering add_active_range(0, 0, 261856) 0 entries of 256 used [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] Normal 4096 - 229376 [0.00] HighMem229376 - 261856 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 - 261856 [0.00] On node 0 totalpages: 261856 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 4064 pages, LIFO batch:0 [0.00] Normal zone: 1760 pages used for memmap [0.00] Normal zone: 223520 pages, LIFO batch:31 [0.00] HighMem zone: 254 pages used for memmap [0.00] HighMem zone: 32226 pages, LIFO batch:7 [0.00] Movable zone: 0 pages used for memmap [0.00] DMI present. [0.00] ACPI: RSDP 000F62C0, 0014 (r0 ACER ) [0.00] ACPI: RSDT 3FEE6205, 0030 (r1 ACER Kestrel 20021012 LTP 0) [0.00] ACPI: FACP 3FEEBF2C, 0074 (r1 ACER Kestrel 20021012 PTL 50) [0.00] ACPI: DSDT 3FEE6235, 5CF7 (r1 ACER Kestrel 20021012 MSFT 10E) [0.00] ACPI: FACS 3FEFCFC0, 0040 [0.00] ACPI: HPET 3FEEBFA0, 0038 (r1 ACER Kestrel 20021012 PTL 0) [0.00] ACPI: BOOT 3FEEBFD8, 0028 (r1 ACER Kestrel 20021012 LTP 1) [0.00] ACPI: DMI detected: Acer [0.00] ACPI: PM-Timer IO Port: 0x1008 [0.00] ACPI: HPET id: 0x8086a201 base: 0x0 is invalid [0.00] Allocating PCI resources starting at 5000 (gap: 4000:bec1) [0.00] PM: Registered nosave memory: 0009f000 - 000a [0.00] PM: Registered nosave memory: 000a - 000dc000 [0.00] PM: Registered nosave memory: 000dc000 - 0010 [0.00] SMP: Allowing 0 CPUs, 0 hotplug CPUs [0.00] PERCPU: Allocating 37960 bytes of per cpu data [0.00] NR_CPUS: 8, nr_cpu_ids: 1 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 259810 [0.00] Kernel command line: root=UUID=cfa47139-db7a-41b0-a5dd-2d8d5b19b771 ro [0.00] Local APIC disabled by BIOS -- you can enable it with lapic [0.00] mapped APIC to b000 (0180f000) [0.00] Enabling fast FPU save and restore... done. [0.00] Enabling unmasked SIMD FPU exception support... done. [0.00] Initializing CPU#0 [0.00] PID hash table entries: 4096 (order: 12, 16384 bytes) [0.00] Detected 1598.697 MHz processor. [0.004000] Console: colour VGA+ 80x25 [0.004000] console [tty0] enabled [0.004000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [0.004000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [0.004000] Memory: 1027920k/1047424k available (1758k kernel code, 18744k reserved, 743k data, 244k init, 129920k highmem) [0.004000] virtual kernel memory layout:
Bug#494308: patch for e100
On Sat, Aug 09, 2008 at 02:29:31PM +0200, Bastian Blank wrote: On Sat, Aug 09, 2008 at 01:18:10PM +0200, Robert Millan wrote: I'll be working on a patch for this one today. Some advices: - Please make a minimal fix. As the firmwares are fix-only it may just remove them and the code referencing it. Please note that the patch must not include parts of the problematic code, use unifdef (see debian/patches/debian/dfsg/files-0 and the tg3 patches) to remove them and after that change anything else. This patch goes into the orig and it should not be broken because of that. - If you want (and can test it with the hardware) make the firmware loadable from userspace in a second patch. This patch goes into the normal flow and can be changed later. Okay. Which one of these do you prefer: - Make the orig patch as minimal as possible, even if it leaves the source in a state that won't build, then provide one (or two) patches to fix build and/or implement userspace load. - Make the orig patch remove the firmware, but with care not to break build or support for ICH, then provide another patch to implement userspace load. I also looked at Jaswinder's patch in http://lkml.org/lkml/2008/6/14/102. I notice some details that I missed in my work; but it also looks more intrusive in general (something that I assume is fine for upstream but not so for Debian). What's the upstream status of Jaswinder's patch? From the discussion it seems upstream is arguing about in which directory this patch can be put. Does anyone know if this will be merged? -- Robert Millan The DRM opt-in fallacy: Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494446: linux-image-2.6.25-2-686 wrong tuner used for Leadtek Winfast 2000XP Expert
Package: linux-image-2.6.25-2-686 Version: 2.6.25-6~bpo40 When the kernel boots the it detect the tuner as typ 44 instead of 38. This gives me only noise instead of sound in kradio. I hope i have the relevant parts of /var/lopg/messages attached for a working tuner detection from the package linux-image-2.6.18-6-k7 and the failing one. This is on debian etch. from linux-image-2.6.25-2-686 Aug 9 15:06:07 sle3 kernel: [ 24.179509] cx88/0: cx2388x v4l2 driver version 0.0.6 loaded Aug 9 15:06:07 sle3 kernel: [ 25.360853] cx88[0]: subsystem: 107d:6611, board: Leadtek Winfast 2000XP Expert [card=5,autodetected] Aug 9 15:06:07 sle3 kernel: [ 25.360929] cx88[0]: TV tuner type 44, Radio tuner type -1 Aug 9 15:06:07 sle3 kernel: [ 25.588843] tuner' 2-0043: chip found @ 0x86 (cx88[0]) Aug 9 15:06:07 sle3 kernel: [ 25.588909] tda9887 2-0043: tda988[5/6/7] found Aug 9 15:06:07 sle3 kernel: [ 25.593278] All bytes are equal. It is not a TEA5767 Aug 9 15:06:07 sle3 kernel: [ 25.593336] tuner' 2-0060: chip found @ 0xc0 (cx88[0]) Aug 9 15:06:07 sle3 kernel: [ 25.593406] tuner-simple 2-0060: type set to 44 (Philips 4 in 1 (ATI TV Wonder Pro/Conexant)) Aug 9 15:06:07 sle3 kernel: [ 25.640832] cx88[0]: Leadtek Winfast 2000XP Expert config: tuner=38, eeprom[0]=0x01 Aug 9 15:06:07 sle3 kernel: [ 25.641001] input: cx88 IR (Leadtek Winfast 2000XP as /class/input/input5 Aug 9 15:06:07 sle3 kernel: [ 25.642580] cx88[0]/0: found at :01:0a.0, rev: 5, irq: 16, latency: 32, mmio: 0xeb00 Aug 9 15:06:07 sle3 kernel: [ 25.642706] cx88[0]/0: registered device video0 [v4l2] Aug 9 15:06:07 sle3 kernel: [ 25.642779] cx88[0]/0: registered device vbi0 Aug 9 15:06:07 sle3 kernel: [ 25.642851] cx88[0]/0: registered device radio0 from linux-image-2.6.18-6-k7 Aug 9 15:16:27 sle3 kernel: CORE cx88[0]: subsystem: 107d:6611, board: Leadtek Winfast 2000XP Expert [card=5,autodetected] Aug 9 15:16:27 sle3 kernel: TV tuner 44 at 0x1fe, Radio tuner -1 at 0x1fe Aug 9 15:16:27 sle3 kernel: cx88[0]: Leadtek Winfast 2000XP Expert config: tuner=38, eeprom[0]=0x01 Aug 9 15:16:27 sle3 kernel: input: cx88 IR (Leadtek Winfast 2000XP as /class/input/input3 Aug 9 15:16:27 sle3 kernel: cx88[0]/0: found at :01:0a.0, rev: 5, irq: 225, latency: 32, mmio: 0xeb00 Aug 9 15:16:27 sle3 kernel: tuner 2-0043: chip found @ 0x86 (cx88[0]) Aug 9 15:16:27 sle3 kernel: tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner) Aug 9 15:16:27 sle3 kernel: tuner 2-0060: All bytes are equal. It is not a TEA5767 Aug 9 15:16:27 sle3 kernel: tuner 2-0060: chip found @ 0xc0 (cx88[0]) Aug 9 15:16:27 sle3 kernel: tuner 2-0060: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3)) Aug 9 15:16:27 sle3 kernel: cx88[0]/0: registered device video0 [v4l2] Aug 9 15:16:27 sle3 kernel: cx88[0]/0: registered device vbi0 Aug 9 15:16:27 sle3 kernel: cx88[0]/0: registered device radio0
Processed: tagging 494435
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 494435 + pending Bug#494435: linux-headers-2.6.26-1-amd64: scripts/gcc-x86_64-has-stack-protector.sh missing 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]
Processed: Re: Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot
Processing commands for controlbugs.debian.org: reassign 494422 lilo Bug#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot Bug reassigned from package `initramfs-tools' to `lilo'. -- 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#494422: [initramfs-tools] upgrading from 0.89 to 0.92e gets a kernel panic on next reboot
Hello, thank you very much for your insights Martin. I was able to solve the problem. I updated lilo to 1:22.8-6 and rebooted... another kernel panic. Then added the line large-memory in /etc/lilo.conf and this time I was able to reboot the system using the new kernel :D Then I installed grub on the first partition of my drive (some people will want it on the MBR isntead) grub-install /dev/sda1 And after another reboot I removed lilo. The bug is with lilo, which should add the large-memory line in lilo.conf. At the very least issue a warning. I would suggest initramfs-tools to ask the user which bootloader he is using when both lilo and grub are detected. Or at least issue a warning like lilo was executed, but you may want grub instead, in that case run it yourself by ... This bug should be changed to minor or wishlist. Thanks and regards. PS: after all of this I'm unsure if I should update my grub package :-/ heh On Sat, Aug 9, 2008 at 12:57 PM, Martin Michlmayr [EMAIL PROTECTED] wrote: * Monkey D. Luffy [EMAIL PROTECTED] [2008-08-09 12:05]: I reboot the system and surprise: grub was *overwritten* by lilo!!! I try to boot anyway... and another surprise: ramdisk: couldn't find valid ram disk image starting at 0 list of all partitions: no filesystem could mount root, tried: kernel panic - not syncing: VFS: unable to mount root fs in unknown-block (8,1) This is a known bug in lilo, see #479607 Although I see it was fixed in version 1:22.8-6. Which version of lilo do you have installed? I had 1:22.8-3, in which #479607 was open (by looking at debian changelog), since it was only fixed in 1:22.8-5. I have now upgraded to 1:22.8-6 but it didn't fix me the problem. I get the same kernel panic error. I reboot the system and surprise: grub was *overwritten* by lilo!!! Maybe this is what happens when you have both grub and lilo installed. But I don't know. It could be it. It was stupid of me to have both boot loaders... maybe some dependency or suggestions made me install it... I don't know. But ideally it should detect which bootloader is being used and use it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492268: linux-image-2.6.25-2-iop32x: Please enable kexec
* Mikhail Gusarov [EMAIL PROTECTED] [2008-07-25 01:23]: kexec works fine in armel architecture (tested in OpenEmbedded and Slind) - please enable it. Corresponding bugreport for kexec-tools is filed as #489175 Maybe you can check if it works with 2.6.26 in unstable. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494457: linux-image-2.6.26-1-amd64: Disable PRINTK_TIME
Subject: linux-image-2.6.26-1-amd64: Disable PRINTK_TIME Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-2 Severity: wishlist Please, disable printk_time on all kernel images; it causes too much bloat on boot process and is useless to the user. If some debuging help is needed why not create image-dbg packages as in most important binaries? -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Jul 30 18:46:19 UTC 2008
Bug#494455: linux-image-2.6.26-1-686: incorrect tuner type for saa7134 module
Package: linux-image-2.6.26-1-686 Version: 2.6.26-1 Severity: normal After upgrading from 2.6.25 to 2.6.26 the tv tuner don't work and output No signal to the screen. The driver of tv card is loaded with command: modprobe saa7134 tuner=1 This module options means that tuner type chosen is 1. And this was working for a years with all linux versions starting from 2.4.x Comparing dmesg for two kernel versions, I see the difference: [ 19.776346] tuner-simple 0-0061: type set to 37 (LG PAL (newer TAPC series)) [ 19.885036] tuner-simple 0-0061: type set to 1 (Philips PAL_I (FI1246 and compatibles)) That is for 2.6.26 kernel the tuner type is always set to 37, ignoring command line option tuner=1, tuner=2 or any other. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Jul 30 20:02:15 UTC 2008 ** Command line: root=/dev/hda1 ro acpi=noirq ** Not tainted ** Kernel log: [ 1457.660885] tuner-simple 0-0061: type set to 37 (LG PAL (newer TAPC series)) [ 1457.63] saa7130[0]: registered device video0 [v4l2] [ 1457.689593] saa7130[0]: registered device vbi0 [ 1457.690199] saa7130[0]: registered device radio0 [ 1581.644726] tuner-simple 0-0061: destroying instance [ 1807.185191] Linux video capture interface: v2.00 [ 1807.242658] saa7130/34: v4l2 driver version 0.2.14 loaded [ 1807.264017] saa7130[0]: found at :01:00.0, rev: 1, irq: 10, latency: 32, mmio: 0xd5001000 [ 1807.280058] saa7130[0]: subsystem: 5168:0138, board: LifeView/Typhoon FlyVIDEO2000 [card=3,insmod option] [ 1807.297909] saa7130[0]: board init: gpio is 39000 [ 1807.315788] saa7130[0]: there are different flyvideo cards with different tuners [ 1807.315798] saa7130[0]: out there, you might have to use the tuner=nr insmod [ 1807.315801] saa7130[0]: option to override the default value. [ 1807.372378] input: saa7134 IR (LifeView/Typhoon Fl as /class/input/input9 [ 1807.603170] saa7130[0]: i2c eeprom 00: 68 51 38 01 10 28 ff ff ff ff ff ff ff ff ff ff [ 1807.626315] saa7130[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.651545] saa7130[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.674495] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.696259] saa7130[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.720052] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.743214] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.766179] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.788110] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.812136] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.835113] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.856193] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.880101] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.900147] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.924138] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1807.944134] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1808.016531] tuner' 0-0061: chip found @ 0xc2 (saa7130[0]) [ 1808.160163] tuner-simple 0-0061: creating new instance [ 1808.178934] tuner-simple 0-0061: type set to 37 (LG PAL (newer TAPC series)) [ 1808.221907] saa7130[0]: registered device video0 [v4l2] [ 1808.239373] saa7130[0]: registered device vbi0 [ 1808.259400] saa7130[0]: registered device radio0 [ 1837.859416] tuner-simple 0-0061: destroying instance [ 1847.664779] Linux video capture interface: v2.00 [ 1847.701065] saa7130/34: v4l2 driver version 0.2.14 loaded [ 1847.701912] saa7130[0]: found at :01:00.0, rev: 1, irq: 10, latency: 32, mmio: 0xd5001000 [ 1847.702873] saa7130[0]: subsystem: 5168:0138, board: LifeView/Typhoon FlyVIDEO2000 [card=3,autodetected] [ 1847.703919] saa7130[0]: board init: gpio is 39000 [ 1847.704572] saa7130[0]: there are different flyvideo cards with different tuners [ 1847.704577] saa7130[0]: out there, you might have to use the tuner=nr insmod [ 1847.704581] saa7130[0]: option to override the default value. [ 1847.707138] input: saa7134 IR (LifeView/Typhoon Fl as /class/input/input10 [ 1847.91] saa7130[0]: i2c eeprom 00: 68 51 38 01 10 28 ff ff ff ff ff ff ff ff ff ff [ 1847.922451] saa7130[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1847.925892] saa7130[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1847.929338] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 1847.932737] saa7130[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff
Processed: forcibly merging 460667 486798
Processing commands for controlbugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35 forcemerge 460667 486798 Bug#460667: linux-source-2.6.23: mol.ko (Mac-on-Linux emulator module) needs handle_mm_fault symbol Bug#486798: restore export of handle_mm_fault for Mac on Linux kernel modules Forcibly Merged 460667 486798. 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]
Processing of linux-kbuild-2.6_2.6.26-2_powerpc.changes
linux-kbuild-2.6_2.6.26-2_powerpc.changes uploaded successfully to localhost along with the files: linux-kbuild-2.6_2.6.26-2.dsc linux-kbuild-2.6_2.6.26-2.diff.gz linux-kbuild-2.6.26_2.6.26-2_powerpc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-kbuild-2.6_2.6.26-2_powerpc.changes ACCEPTED
Accepted: linux-kbuild-2.6.26_2.6.26-2_powerpc.deb to pool/main/l/linux-kbuild-2.6/linux-kbuild-2.6.26_2.6.26-2_powerpc.deb linux-kbuild-2.6_2.6.26-2.diff.gz to pool/main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.26-2.diff.gz linux-kbuild-2.6_2.6.26-2.dsc to pool/main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.26-2.dsc Override entries for your package: linux-kbuild-2.6.26_2.6.26-2_powerpc.deb - optional devel linux-kbuild-2.6_2.6.26-2.dsc - source devel Announcing to [EMAIL PROTECTED] Closing bugs: 494435 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#494471: kernel-2.6.25 unable to resync (new) md array's
Processing commands for controlbugs.debian.org: reassign 494471 linux-2.6 Bug#494471: kernel-2.6.25 unable to resync (new) md array's Bug reassigned from package `linux-image' to `linux-2.6'. -- 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#494435: marked as done (linux-headers-2.6.26-1-amd64: scripts/gcc-x86_64-has-stack-protector.sh missing)
Your message dated Sat, 09 Aug 2008 19:02:05 + with message-id [EMAIL PROTECTED] and subject line Bug#494435: fixed in linux-kbuild-2.6 2.6.26-2 has caused the Debian Bug report #494435, regarding linux-headers-2.6.26-1-amd64: scripts/gcc-x86_64-has-stack-protector.sh missing 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.) -- 494435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494435 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-headers-2.6.26-1-amd64 Version: 2.6.26-2 Severity: normal Hello, When building external modules on linux-headers-2.6.26-1-amd64, I get the following error messages: $ make -C /usr/src/linux-headers-2.6.26-1-amd64/ M=$PWD /bin/sh: /usr/src/linux-headers-2.6.26-1-amd64/scripts/gcc-x86_64-has-stack-protector.sh: No such file or directory /bin/sh: /usr/src/linux-headers-2.6.26-1-amd64/scripts/gcc-x86_64-has-stack-protector.sh: No such file or directory make: Entering directory `/usr/src/linux-headers-2.6.26-1-amd64' [...] The build seems to complete fine anyway, so I don't know exactly what this missing file is needed for. thanks, Brice -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages linux-headers-2.6.26-1-amd64 depends on: ii gcc-4.1 4.1.2-23 The GNU C compiler ii linux-headers-2.6.26-1-common 2.6.26-2 Common header files for Linux 2.6. ii linux-kbuild-2.6.26 2.6.26-1 Kbuild infrastructure for Linux 2. linux-headers-2.6.26-1-amd64 recommends no packages. linux-headers-2.6.26-1-amd64 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: linux-kbuild-2.6 Source-Version: 2.6.26-2 We believe that the bug you reported is fixed in the latest version of linux-kbuild-2.6, which is due to be installed in the Debian FTP archive: linux-kbuild-2.6.26_2.6.26-2_powerpc.deb to pool/main/l/linux-kbuild-2.6/linux-kbuild-2.6.26_2.6.26-2_powerpc.deb linux-kbuild-2.6_2.6.26-2.diff.gz to pool/main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.26-2.diff.gz linux-kbuild-2.6_2.6.26-2.dsc to pool/main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.26-2.dsc 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 [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank [EMAIL PROTECTED] (supplier of updated linux-kbuild-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 [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 09 Aug 2008 20:45:12 +0200 Source: linux-kbuild-2.6 Binary: linux-kbuild-2.6.26 Architecture: source powerpc Version: 2.6.26-2 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Bastian Blank [EMAIL PROTECTED] Description: linux-kbuild-2.6.26 - Kbuild infrastructure for Linux 2.6.26 Closes: 494435 Changes: linux-kbuild-2.6 (2.6.26-2) unstable; urgency=low . * Include new scripts. (closes: #494435) Checksums-Sha1: 97e3895171cbdff9fafc01c0e8f472a09696eb62 1092 linux-kbuild-2.6_2.6.26-2.dsc 92f1556a4794a0be0eb2fd80227a12b12a9f5808 13121 linux-kbuild-2.6_2.6.26-2.diff.gz 5f11dffbfce8b268ae2c6557667b798b155dfd64 59260 linux-kbuild-2.6.26_2.6.26-2_powerpc.deb Checksums-Sha256: 5e2b3156a0581ff8fabff21035582ab04aff645f00fe5790aa784a2471e433bf 1092 linux-kbuild-2.6_2.6.26-2.dsc 7921f279e28b16fc2630f4b0d37515f91119f651cd35dbf8248d10d9e48ce393 13121 linux-kbuild-2.6_2.6.26-2.diff.gz f51eccaa75c8a01511561f3349b57be04a1806e3a44cd93bf57e2483ecddff42 59260 linux-kbuild-2.6.26_2.6.26-2_powerpc.deb Files: 128c79cc53787675ff29c089747c6b74 1092 devel optional linux-kbuild-2.6_2.6.26-2.dsc db4963f3756d26175440e02dc4995c80 13121 devel optional linux-kbuild-2.6_2.6.26-2.diff.gz cd99486d9e4eee6090538766485befaf 59260 devel optional linux-kbuild-2.6.26_2.6.26-2_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkid5mwACgkQxWtQqFixGB6N+ACfSvKQzmGBMgyPw5LKRyySlDt8 bjEAoJaKbuswGTXaHCNOB72jw13DyX2z =Wtxm -END PGP
Bug#494471: kernel-2.6.25 unable to resync (new) md array's
Package: linux-image Version: 2.6.25-2-686 I tried to create several software raid(md) array's on my Lenny system, but unfortunately the resync/recovery of the array's hangs like this: md3 : active raid1 sdb6[2](F) sda6[0] 126953536 blocks [2/1] [U_] [] recovery = 0.0% (103296/126953536) finish=634251.2min speed=0K/sec md4 : active raid6 sdf1[3] sde1[2] sdd1[1] sdc1[0] 976767872 blocks level 6, 64k chunk, algorithm 2 [4/4] [] [] resync = 0.2% (1037056/488383936) finish=289250.7min speed=0K/sec I also tried a 2.6.25.14 vanilla kernel, which I built myself but this one suffers from the same problem. Downgrading to Lenny's 2.6.24 kernel, however, fixes the problem! I guess it should (could?) be fixed upstream. But at least we want this fixed before the final release of Lenny, right? I don't know if it is related to the type of hardware I'm using, here are the relevant details of my setup: - Pentium III 500E - 2x Promise TX4 SATA controller - 4x Seagate 500Gb SATA disk - 2x Samsung 640Gb SATA disk -- Ing. A.C.J. van Amersfoort (Arno) Department Of Electronics (ELD, k1007) Huygens Laboratory Leiden University P.O. Box 9504 Niels Bohrweg 2 2333 CA Leiden The Netherlands Phone : +31-(0)71-527.1894 Fax: +31-(0)71-527.5819 E-mail: [EMAIL PROTECTED] Arno's (Linux firewall) homepage: http://rocky.eld.leidenuniv.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494007: old patch for drivers/char/drm/r128_cce.c
Hi, It appears that Nathanael sent a patch to implement user handling of r128_cce.c, I found it by digging in the #242866 meta-bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242866#33 It'd most likely need some work to get it updated, but the major barrier is that it was applied in 2004 and had to be reverted because it caused problems with X: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242866#73 unfortunately there's no reference to where are those problems documented, and I don't have the hardware to test myself. So first of all I'd like to know if someone has more information about them, and whether they have been fixed or not (Nathanael mentions in the bug log that he was going to try). Or, if someone has access to the affected hardware and can test things, I'd like to know about that too. Thanks -- Robert Millan The DRM opt-in fallacy: Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494477: Linux 2.6.26-1-686: insert key behaves abnormally
Package: linux-image-2.6.26-1-686 Version: 2.6.26-1 Severity: normal Under Linux 2.6.26-1-686 the insert key behaves in a very weird way: after pressing it the following keys does not work anymore: home, page up, page down and arrow keys. For example, under Linux 2.6.25-2-686, pressing left, insert, left, insert, left, insert produces the following `kbdmode -a` output: ^[[D 27 0033 0x1b 91 0133 0x5b 68 0104 0x44 ^[[2~27 0033 0x1b 91 0133 0x5b 50 0062 0x32 126 0176 0x7e ^[[D 27 0033 0x1b 91 0133 0x5b 68 0104 0x44 ^[[2~27 0033 0x1b 91 0133 0x5b 50 0062 0x32 126 0176 0x7e ^[[D 27 0033 0x1b 91 0133 0x5b 68 0104 0x44 ^[[2~27 0033 0x1b 91 0133 0x5b 50 0062 0x32 126 0176 0x7e But under Linux 2.6.26-1-686, the output is: ^[[D 27 0033 0x1b 91 0133 0x5b 68 0104 0x44 ^[[D 27 0033 0x1b 91 0133 0x5b 68 0104 0x44 -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (500, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.7-13 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii lilo 1:22.8-6 LInux LOader - The Classic OS load pn linux-doc-2.6.26 none (no description available) -- debconf information excluded -- Jakub Wilk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: [atl2] Fails to create a wifi interface
Processing commands for controlbugs.debian.org: retitle 463860 [atl2] Fails to create a wifi interface Bug#463860: No wifis detected Changed Bug title to `[atl2] Fails to create a wifi interface' from `No wifis detected'. found 463860 2.6.25-1 Bug#463860: [atl2] Fails to create a wifi interface Bug marked as found in version 2.6.25-1. severity 463860 important Bug#463860: [atl2] Fails to create a wifi interface Severity set to `important' from `normal' 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#463860: [atl2] Fails to create a wifi interface
retitle 463860 [atl2] Fails to create a wifi interface found 463860 2.6.25-1 severity 463860 important thanks From version 2.6.25 of the kernel, the package atl2-modules-2.6-686 (or rather, its dependency) does not create any wifi inteface. But I guess that this is not 686-specific. At boot time, I get a message printed in red like ath0 not found. The output of wlassistant is: # wlassistant Loaded application options. All interfaces: eth0 No wireless interfaces found. Exiting. Application options saved. Kernel socket closed. ifconfig only returns the interfaces eth0 and lo. Madwifi compiles and works nicely for the kernel 2.6.26 (and 2.6.25, and I presume for some previous versions as well). Upgrading the bug just in case you release this package in lenny :-) What a pity that I cannot mark the severity as grave :-) , but I think that severity important is justified. Thank you.
