Bug#579306: memtest86+: does not invoke update-grub after installation
Hi, thanks for your mail. I've tested the memtest86+ installation procedure on Feb 11 2022 on an older devuan 2.1 installation (which installs memtest86+ 5.01-3). Everything worked fine, including update-grub invocation. So it seems that the issue has been fixed in the meantime (at least in devuan). Kind regards, Martin On Mon, Feb 07, 2022 at 07:52:05PM +0100, Fabio Fantoni wrote: > Hi, I don't remember about that very old memtest86+ version (of over 10 > years ago), in version >=5.01 update-grub run always on postins, in > 5.31b+dfsg-4 I only added to not run it in a container > > are there still problems with the latest memtest86 + versions about > update-grub? if yes can you tell me which ones please?
Bug#898587: grub-pc: Adding code for toggling 'serial console' and 'multiboot' memtest86+ menu entries on and off
Dear package maintainer or DBS admin, I've realised that I've filed this bugreport against the wrong package. I've filed a new one against memtest86+, so you may delete this one here. I'm sorry for the caused inconvenience.
Bug#898636: Adding code for toggling 'serial console' and 'multiboot' memtest86+ GRUB2 menu entries on and off
Package: memtest86+
Version: 4.10-1.1
Severity: wishlist
Tags: patch
When installing the memtest86+ package, four GRUB menu entries get added
nowadays:
memtest86+
memtest86+, serial console 115200
memtest86+, experimental multiboot
memtest86+, serial console 115200, experimental multiboot
In order to reduce that, I've added two variables and some if-statements
to /etc/grub.d/20_memtest86+.
In /etc/default/grub:
GRUB_MEMTEST_ENABLE_SERIAL=[true|false]
GRUB_MEMTEST_ENABLE_MULTIBOOT=[true|false]
In addition, I've added a variable holding the memtest86+ serial params:
GRUB_MEMTEST_SERIAL_PARAMS="ttyS0,115200n8"
In /etc/grub.d/20_memtest86+:
Have a look at the patch file.
-- System Information:
Debian Release: 6.0.10
APT prefers oldoldstable-updates
APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-0.bpo.4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages memtest86+ depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
memtest86+ recommends no packages.
Versions of packages memtest86+ suggests:
ii grub-pc1.98+20100804-14+squeeze1 GRand Unified Bootloader, version
pn hwtools(no description available)
pn kernel-patch-b (no description available)
pn memtest86 (no description available)
pn memtester (no description available)
ii mtools 4.0.12-1 Tools for manipulating MSDOS files
-- Configuration Files:
/etc/grub.d/20_memtest86+ changed:
set -e
if [ -f /usr/lib/grub/grub-mkconfig_lib ]; then
. /usr/lib/grub/grub-mkconfig_lib
LX=linux16
elif [ -f /usr/lib/grub/update-grub_lib ]; then
. /usr/lib/grub/update-grub_lib
LX=linux
else
# no grub file, so we notify and exit gracefully
echo "Cannot find grub config file, exiting." >&2
exit 0
fi
case ${GRUB_DEVICE_BOOT} in
/dev/loop/*|/dev/loop[0-9]) exit 0 ;;
esac
prepare_boot_cache="$(prepare_grub_to_access_device ${GRUB_DEVICE_BOOT} | sed
-e "s/^/\t/")"
if test -e /boot/memtest86+.bin ; then
MEMTESTPATH=$( make_system_path_relative_to_its_root "/boot/memtest86+.bin" )
echo "Found memtest86+ image: $MEMTESTPATH" >&2
cat << EOF
menuentry "Memory test (memtest86+)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
$LX $MEMTESTPATH
}
EOF
if [ "${GRUB_MEMTEST_ENABLE_SERIAL}" = "true" ]; then
cat << EOF
menuentry "Memory test (memtest86+, serial console)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
$LX $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
fi
fi
if [ "${GRUB_MEMTEST_ENABLE_MULTIBOOT}" = "true" ]; then
if test -e /boot/memtest86+_multiboot.bin ; then
MEMTESTPATH=$( make_system_path_relative_to_its_root
"/boot/memtest86+_multiboot.bin" )
echo "Found memtest86+ multiboot image: $MEMTESTPATH" >&2
cat << EOF
menuentry "Memory test (memtest86+, experimental multiboot)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
multiboot $MEMTESTPATH
}
EOF
if [ "${GRUB_MEMTEST_ENABLE_SERIAL}" = "true" ]; then
cat << EOF
menuentry "Memory test (memtest86+, experimental multiboot, serial console)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
multiboot $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
fi
fi
fi
-- debconf information:
shared/memtest86-run-lilo: false
--- 20_memtest86+.orig 2018-05-14 00:52:58.719587898 +0200
+++ 20_memtest86+ 2015-02-18 17:47:52.0 +0100
@@ -30,16 +30,21 @@
cat << EOF
$LX $MEMTESTPATH
}
-menuentry "Memory test (memtest86+, serial console 115200)" {
+EOF
+ if [ "${GRUB_MEMTEST_ENABLE_SERIAL}" = "true" ]; then
+ cat << EOF
+menuentry "Memory test (memtest86+, serial console)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
- $LX $MEMTESTPATH console=ttyS0,115200n8
+ $LX $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
+ fi
fi
-if test -e /boot/memtest86+_multiboot.bin ; then
+if [ "${GRUB_MEMTEST_ENABLE_MULTIBOOT}" = "true" ]; then
+ if test -e /boot/memtest86+_multiboot.bin ; then
MEMTESTPATH=$( make_system_path_relative_to_its_root
"/boot/memtest86+_multiboot.bin" )
echo "Found memtest86+ multiboot image: $MEMTESTPATH" >&2
cat << EOF
@@ -49,11 +54,16 @@
cat << EOF
multiboot $MEMTESTPATH
}
-menuentry "Memory test (memtest86+, serial console 115200, experimental
multiboot)" {
+EOF
+ if [ "${GRUB_MEMTEST_ENABLE_SERIAL}" = "true" ]; then
+ cat << EOF
+menuentry "Memory test (memtest86+, experimental multiboot, serial console)" {
EOF
printf '%s\n' "${prepare_boot_cache}"
cat << EOF
-multiboot $MEMTESTPATH console=ttyS0,115200n8
+ multiboot $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
+ fi
+ fi
fi
Bug#898587: grub-pc: Adding code for toggling 'serial console' and 'multiboot' memtest86+ menu entries on and off
Package: grub-pc
Version: 1.98+20100804-14+squeeze1
Severity: wishlist
Tags: upstream patch
When installing the memtest86+ package, four GRUB menu entries get added
nowadays:
memtest86+
memtest86+, serial console 115200
memtest86+, experimental multiboot
memtest86+, serial console 115200, experimental multiboot
In order to reduce that, I've added two variables and some if-statements to
/etc/grub.d/20_memtest86+.
In /etc/default/grub:
GRUB_MEMTEST_ENABLE_SERIAL=[true|false]
GRUB_MEMTEST_ENABLE_MULTIBOOT=[true|false]
In addition, I've added a variable holding the memtest86+ serial params:
GRUB_MEMTEST_SERIAL_PARAMS="ttyS0,115200n8"
In /etc/grub.d/20_memtest86+:
Have a look at the diff file.
I think it would be nice if this would make it into upstream.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/disk/by-uuid/0adcabcc-c32e-4760-9eac-12d8d7749208 / ext4
rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/sda5 /tmp ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/sda6 /home ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/sda7 /data ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-ST9160310AS_5SV1V363
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos2)'
search --no-floppy --fs-uuid --set 0adcabcc-c32e-4760-9eac-12d8d7749208
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=1024x600
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos2)'
search --no-floppy --fs-uuid --set 0adcabcc-c32e-4760-9eac-12d8d7749208
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
set timeout=5
# set superusers to enable authentication support
set superusers='martin'
### PASSWORD LINE REMOVED ###
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos2)'
search --no-floppy --fs-uuid --set 0adcabcc-c32e-4760-9eac-12d8d7749208
insmod png
if background_image /usr/share/images/desktop-base/spacefun-grub.png; then
set color_normal=light-gray/black
set color_highlight=white/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 3.2.0-0.bpo.4-686-pae' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos2)'
search --no-floppy --fs-uuid --set 0adcabcc-c32e-4760-9eac-12d8d7749208
echo'Loading Linux 3.2.0-0.bpo.4-686-pae ...'
linux /boot/vmlinuz-3.2.0-0.bpo.4-686-pae
root=UUID=0adcabcc-c32e-4760-9eac-12d8d7749208 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-0.bpo.4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.2.0-0.bpo.4-686-pae (recovery mode)'
--class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos2)'
search --no-floppy --fs-uuid --set 0adcabcc-c32e-4760-9eac-12d8d7749208
echo'Loading Linux 3.2.0-0.bpo.4-686-pae ...'
linux /boot/vmlinuz-3.2.0-0.bpo.4-686-pae
root=UUID=0adcabcc-c32e-4760-9eac-12d8d7749208 ro single
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-0.bpo.4-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 2.6.38-bpo.2-686' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos2)'
search --no-floppy --fs-uuid --set 0adcabcc-c32e-4760-9eac-12d8d7749208
echo'Loading Linux 2.6.38-bpo.2-686 ...'
linux /boot/vmlinuz-2.6.38-bpo.2-686
root=UUID=0adcabcc-c32e-4760-9eac-12d8d7749208 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-bpo.2-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.38-bpo.2-686 (recovery mode)'
--class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
Bug#612371: memtest86+: added two more variables for enabling/disabling serial and/or multiboot menuentries
Package: memtest86+
Version: 4.20-1.1
Followup-For: Bug #612371
Dear Maintainer,
I added two more variables in /etc/default/grub for being able to
enabling/disabling the serial and the multiboot menuentry.
Here is what I did:
1.) In /etc/default/grub I added these lines:
GRUB_MEMTEST_ENABLE_SERIAL=false
GRUB_MEMTEST_ENABLE_MULTIBOOT=false
2.) In /usr/sbin/grub-mkconfig I added these variables to the list of exportet
variables:
at line 280:
GRUB_MEMTEST_SERIAL_PARAMS \
GRUB_MEMTEST_ENABLE_SERIAL \
GRUB_MEMTEST_ENABLE_MULTIBOOT
3.) I modified /etc/grub.d/20_memtest86+:
Two times:
if [ ${GRUB_MEMTEST_ENABLE_SERIAL} = true ]; then
...
fi
One time:
if [ ${GRUB_MEMTEST_ENABLE_MULTIBOOT} = true ]; then
...
fi
I'm not sure if it's the best solution, but at least it works...
See my attached patch-files.
-- System Information:
Debian Release: 7.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages memtest86+ depends on:
ii debconf [debconf-2.0] 1.5.49
memtest86+ recommends no packages.
Versions of packages memtest86+ suggests:
ii grub-pc 1.99-27+deb7u2
pn hwtools none
pn kernel-patch-badram none
pn memtest86none
pn memtesternone
pn mtools none
-- Configuration Files:
/etc/grub.d/20_memtest86+ changed [not included]
-- debconf information excluded
--- /tmp/grub-mkconfig 2011-09-19 05:12:37.0 +0200
+++ /usr/sbin/grub-mkconfig 2015-02-18 16:56:41.151090002 +0100
@@ -276,7 +276,10 @@
GRUB_DISABLE_OS_PROBER \
GRUB_INIT_TUNE \
GRUB_SAVEDEFAULT \
- GRUB_BADRAM
+ GRUB_BADRAM \
+ GRUB_MEMTEST_SERIAL_PARAMS \
+ GRUB_MEMTEST_ENABLE_SERIAL \
+ GRUB_MEMTEST_ENABLE_MULTIBOOT
if test x${grub_cfg} != x; then
rm -f ${grub_cfg}.new
--- /tmp/20_memtest86+ 2010-10-19 18:32:29.0 +0200
+++ /etc/grub.d/20_memtest86+ 2015-02-18 17:47:52.385794462 +0100
@@ -30,16 +30,21 @@
cat EOF
$LX $MEMTESTPATH
}
-menuentry Memory test (memtest86+, serial console 115200) {
+EOF
+ if [ ${GRUB_MEMTEST_ENABLE_SERIAL} = true ]; then
+ cat EOF
+menuentry Memory test (memtest86+, serial console) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
- $LX $MEMTESTPATH console=ttyS0,115200n8
+ $LX $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
+ fi
fi
-if test -e /boot/memtest86+_multiboot.bin ; then
+if [ ${GRUB_MEMTEST_ENABLE_MULTIBOOT} = true ]; then
+ if test -e /boot/memtest86+_multiboot.bin ; then
MEMTESTPATH=$( make_system_path_relative_to_its_root /boot/memtest86+_multiboot.bin )
echo Found memtest86+ multiboot image: $MEMTESTPATH 2
cat EOF
@@ -49,11 +54,16 @@
cat EOF
multiboot $MEMTESTPATH
}
-menuentry Memory test (memtest86+, serial console 115200, experimental multiboot) {
+EOF
+ if [ ${GRUB_MEMTEST_ENABLE_SERIAL} = true ]; then
+ cat EOF
+menuentry Memory test (memtest86+, experimental multiboot, serial console) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
- multiboot $MEMTESTPATH console=ttyS0,115200n8
+ multiboot $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
+ fi
+ fi
fi
Bug#612371: memtest86+: in /etc/grub.d/20_memtest86+ menuentries are generated very hardcoded
Package: memtest86+ Version: 4.20-1.1 Followup-For: Bug #612371 Dear Maintainer, in /etc/grub.d/20_memtest86+ menuentries are generated very hardcoded. In my opinion, this is the outcome of a misunderstanding of what I wrote in bug report #580604. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580604 for more info. kopt console=ttyS0,115200n8 should be added to the memtest86+ kernel line when update-grub is invoked. was just meant as an example, not as a given hardcoded value. Of course, grub-pc should take the parameters from a variable (maybe just one, maybe several variables) set somewhere in a grub config file (maybe /etc/default/grub). GRUB2 also should be configurable to generate or not generate menuentries with the serial console option enabled and for the multiboot memtest86+-image. For example add these lines in /etc/default/grub: GRUB_ENABLE_MEMTEST_MULTIBOOT=[true/false] GRUB_ENABLE_MEMTEST_SERIAL=[true/false] GRUB_MEMTEST_CONSOLE_PARAMS=ttyS0,115200n8 or something similar which allows the user to configure which and how grub menuentries are created for memtest86+ (i.e. these should be created more dynamically). -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages memtest86+ depends on: ii debconf [debconf-2.0] 1.5.49 memtest86+ recommends no packages. Versions of packages memtest86+ suggests: ii grub-pc 1.99-27+deb7u2 pn hwtools none pn kernel-patch-badram none pn memtest86none pn memtesternone pn mtools none -- Configuration Files: /etc/grub.d/20_memtest86+ changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612371: memtest86+: Add the patch tag.
Package: memtest86+ Version: 4.20-1.1 Followup-For: Bug #612371 Patch tag added. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612371: memtest86+: Patch for hardcoded serial port parameters
Package: memtest86+
Version: 4.20-1.1
Followup-For: Bug #612371
Dear Maintainer,
here is my patch for this issue.
I hope it helps.
I've added a variable to /etc/default/grub named
GRUB_MEMTEST_SERIAL_PARAMS
and did some modifications to
/usr/sbin/grub-mkconfig and /etc/grub.d/20_memtest86+, as shown in the attached
patch-files.
I've set GRUB_MEMTEST_SERIAL_PARAMS=ttyS0,115200n8 in /etc/default/grub and
did 'update-grub' which worked fine.
Best regards,
Martin
-- System Information:
Debian Release: 7.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages memtest86+ depends on:
ii debconf [debconf-2.0] 1.5.49
memtest86+ recommends no packages.
Versions of packages memtest86+ suggests:
ii grub-pc 1.99-27+deb7u2
pn hwtools none
pn kernel-patch-badram none
pn memtest86none
pn memtesternone
pn mtools none
-- Configuration Files:
/etc/grub.d/20_memtest86+ changed:
set -e
if [ -f /usr/lib/grub/grub-mkconfig_lib ]; then
. /usr/lib/grub/grub-mkconfig_lib
LX=linux16
elif [ -f /usr/lib/grub/update-grub_lib ]; then
. /usr/lib/grub/update-grub_lib
LX=linux
else
# no grub file, so we notify and exit gracefully
echo Cannot find grub config file, exiting. 2
exit 0
fi
case ${GRUB_DEVICE_BOOT} in
/dev/loop/*|/dev/loop[0-9]) exit 0 ;;
esac
prepare_boot_cache=$(prepare_grub_to_access_device ${GRUB_DEVICE_BOOT} | sed
-e s/^/\t/)
if test -e /boot/memtest86+.bin ; then
MEMTESTPATH=$( make_system_path_relative_to_its_root /boot/memtest86+.bin )
echo Found memtest86+ image: $MEMTESTPATH 2
cat EOF
menuentry Memory test (memtest86+) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
$LX $MEMTESTPATH
}
EOF
fi
-- debconf information excluded
--- /usr/sbin/grub-mkconfig 2015-02-15 20:14:29.306247010 +0100
+++ /usr/sbin/grub-mkconfig.new 2015-02-15 19:39:09.064671362 +0100
@@ -276,7 +276,8 @@
GRUB_DISABLE_OS_PROBER \
GRUB_INIT_TUNE \
GRUB_SAVEDEFAULT \
- GRUB_BADRAM
+ GRUB_BADRAM \
+ GRUB_MEMTEST_SERIAL_PARAMS
if test x${grub_cfg} != x; then
rm -f ${grub_cfg}.new
--- /tmp/20_memtest86+ 2015-02-15 20:35:13.709384283 +0100
+++ /etc/grub.d/20_memtest86+ 2015-02-15 20:33:33.624169320 +0100
@@ -30,11 +30,11 @@
cat EOF
$LX $MEMTESTPATH
}
-menuentry Memory test (memtest86+, serial console 115200) {
+menuentry Memory test (memtest86+, serial console) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
- $LX $MEMTESTPATH console=ttyS0,115200n8
+ $LX $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
fi
@@ -49,11 +49,11 @@
cat EOF
multiboot $MEMTESTPATH
}
-menuentry Memory test (memtest86+, serial console 115200, experimental multiboot) {
+menuentry Memory test (memtest86+, experimental multiboot, serial console) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
- multiboot $MEMTESTPATH console=ttyS0,115200n8
+ multiboot $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
fi
Bug#612371: memtest86+: Add the patch tag.
Package: memtest86+
Version: 4.20-1.1
Tags: patch
Followup-For: Bug #612371
Patch tag added.
--- /usr/sbin/grub-mkconfig 2015-02-15 20:14:29.306247010 +0100
+++ /usr/sbin/grub-mkconfig.new 2015-02-15 19:39:09.064671362 +0100
@@ -276,7 +276,8 @@
GRUB_DISABLE_OS_PROBER \
GRUB_INIT_TUNE \
GRUB_SAVEDEFAULT \
- GRUB_BADRAM
+ GRUB_BADRAM \
+ GRUB_MEMTEST_SERIAL_PARAMS
if test x${grub_cfg} != x; then
rm -f ${grub_cfg}.new
--- /tmp/20_memtest86+ 2015-02-15 20:35:13.709384283 +0100
+++ /etc/grub.d/20_memtest86+ 2015-02-15 20:33:33.624169320 +0100
@@ -30,11 +30,11 @@
cat EOF
$LX $MEMTESTPATH
}
-menuentry Memory test (memtest86+, serial console 115200) {
+menuentry Memory test (memtest86+, serial console) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
- $LX $MEMTESTPATH console=ttyS0,115200n8
+ $LX $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
fi
@@ -49,11 +49,11 @@
cat EOF
multiboot $MEMTESTPATH
}
-menuentry Memory test (memtest86+, serial console 115200, experimental multiboot) {
+menuentry Memory test (memtest86+, experimental multiboot, serial console) {
EOF
printf '%s\n' ${prepare_boot_cache}
cat EOF
- multiboot $MEMTESTPATH console=ttyS0,115200n8
+ multiboot $MEMTESTPATH console=${GRUB_MEMTEST_SERIAL_PARAMS}
}
EOF
fi
Bug#737765: musescore: 100% CPU load after program start without identifiable reason
Package: musescore Version: 0.9.6+dfsg-1 Severity: important Musescore produces 100% CPU load after starting. There is no identifiable reason for that. It was reproducible on at least two machines. I assume a serious programming error/mistake in it. I do not know if it is an upstream or a debian specific error; didn't compile it from source, but I _guess_ it is upstream related and not Debian specific. -- System Information: Debian Release: 6.0.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-0.bpo.4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages musescore depends on: ii desktop-file-utils 0.15-2 Utilities for .desktop files ii gawk 1:3.1.7.dfsg-5 GNU awk, a pattern scanning and pr ii libasound2 1.0.23-2.1 shared library for ALSA applicatio ii libc62.11.3-4Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libportaudio219+svn20071022-3.2 Portable audio I/O - shared librar ii libqt4-designer 4:4.6.3-4+squeeze1 Qt 4 designer module ii libqt4-network 4:4.6.3-4+squeeze1 Qt 4 network module ii libqt4-script4:4.6.3-4+squeeze1 Qt 4 script module ii libqt4-scripttools 4:4.6.3-4+squeeze1 Qt 4 script tools module ii libqt4-svg 4:4.6.3-4+squeeze1 Qt 4 SVG module ii libqt4-xml 4:4.6.3-4+squeeze1 Qt 4 XML module ii libqtcore4 4:4.6.3-4+squeeze1 Qt 4 core module ii libqtgui44:4.6.3-4+squeeze1 Qt 4 GUI module ii libqtscript4-qtbindi 0.1.0-3 Qt Script bindings for Qt 4 - meta ii libsndfile1 1.0.21-3+squeeze1 Library for reading/writing audio ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii musescore-common 0.9.6+dfsg-1Full featured WYSIWYG score editor ii musescore-soundfont- 0.9.6+dfsg-1Small GM SoundFont for MuseScore ( ii xdg-utils1.0.2+cvs20100307-2 desktop integration utilities from ii zlib1g 1:1.2.3.4.dfsg-3compression library - runtime Versions of packages musescore recommends: pn pulseaudio-utils none (no description available) Versions of packages musescore suggests: pn fluid-soundfont-gmnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720213: rename of config-file results in error message when '/etc/init.d/fancontrol start' is called
Package: fancontrol
Version: 1:3.1.2-6
Severity: normal
Tags: patch upstream
A rename of the fancontrol config-file /etc/fancontrol results in an
error message when '/etc/init.d/fancontrol start' is called even if
CONF is set corretly.
The CONF-variable is not passed through in the 'start' case at least.
Have a look at the patch.
-- System Information:
Debian Release: 6.0.7
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.38-bpo.2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages fancontrol depends on:
ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
fancontrol recommends no packages.
fancontrol suggests no packages.
-- Configuration Files:
/etc/init.d/fancontrol changed:
.. /lib/lsb/init-functions
[ -f /etc/default/rcS ] . /etc/default/rcS
PATH=/bin:/usr/bin:/sbin:/usr/sbin
DAEMON=/usr/sbin/fancontrol
DESC=fan speed regulator
NAME=fancontrol
PIDFILE=/var/run/fancontrol.pid
CONF=/etc/fancontrol.conf
test -x $DAEMON || exit 0
case $1 in
start)
if [ -f $CONF ] ; then
if $DAEMON --check $CONF 1/dev/null 2/dev/null ; then
log_daemon_msg Starting $DESC $NAME
start-stop-daemon --start --quiet --background
--pidfile $PIDFILE --startas $DAEMON $CONF
log_end_msg $?
else
log_failure_msg Not starting fancontrol, broken
configuration file; please re-run pwmconfig.
fi
else
if [ $VERBOSE != no ]; then
log_warning_msg Not starting fancontrol; run pwmconfig
first.
fi
fi
;;
stop)
log_daemon_msg Stopping $DESC $NAME
start-stop-daemon --stop --quiet --pidfile $PIDFILE --oknodo --startas
$DAEMON
rm -f $PIDFILE
log_end_msg $?
;;
restart)
$0 stop
sleep 3
$0 start
;;
force-reload)
if start-stop-daemon --stop --test --quiet --pidfile $PIDFILE --startas
$DAEMON ; then
$0 restart
fi
;;
status)
status_of_proc $DAEMON $NAME exit 0 || exit $?
;;
*)
log_success_msg Usage: /etc/init.d/fancontrol
{start|stop|restart|force-reload|status}
exit 1
;;
esac
exit 0
-- no debconf information
--- /tmp/fancontrol 2013-08-19 17:55:40.634568822 +0200
+++ /etc/init.d/fancontrol 2013-08-19 17:54:20.845714678 +0200
@@ -25,9 +25,9 @@
case $1 in
start)
if [ -f $CONF ] ; then
- if $DAEMON --check 1/dev/null 2/dev/null ; then
+ if $DAEMON --check $CONF 1/dev/null 2/dev/null ; then
log_daemon_msg Starting $DESC $NAME
- start-stop-daemon --start --quiet --background
--pidfile $PIDFILE --startas $DAEMON
+ start-stop-daemon --start --quiet --background
--pidfile $PIDFILE --startas $DAEMON $CONF
log_end_msg $?
else
log_failure_msg Not starting fancontrol, broken
configuration file; please re-run pwmconfig.
--- /tmp/fancontrol 2013-08-19 17:55:40.634568822 +0200
+++ /etc/init.d/fancontrol 2013-08-19 17:54:20.845714678 +0200
@@ -25,9 +25,9 @@
case $1 in
start)
if [ -f $CONF ] ; then
- if $DAEMON --check 1/dev/null 2/dev/null ; then
+ if $DAEMON --check $CONF 1/dev/null 2/dev/null ; then
log_daemon_msg Starting $DESC $NAME
- start-stop-daemon --start --quiet --background
--pidfile $PIDFILE --startas $DAEMON
+ start-stop-daemon --start --quiet --background
--pidfile $PIDFILE --startas $DAEMON $CONF
log_end_msg $?
else
log_failure_msg Not starting fancontrol, broken
configuration file; please re-run pwmconfig.
Bug#701700: Acknowledgement (psi: I'd like to have a disable-option for each soundevent.)
Hello, I wrote it for 0.15 too. Have a look at http://www-stud.cs.uni-frankfurt.de/~teufel/patches/psi-0.15.sounds-disabled.patch Best regards, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701700: psi: I'd like to have a disable-option for each soundevent.
Package: psi Version: 0.14-2 Severity: wishlist Tags: patch upstream I'd like to have a disable-option for each soundevent. Have a look at https://github.com/psi-im/psi/issues/49 and/or http://teufel.homenet.org/patches/ to get my patch. Since upstream is at version 0.15 and my patch isn't really compatible with that, I think it is a good idea to patch the debian version of 0.14. -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.38-bpo.2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages psi depends on: ii libaspell15 0.60.6-4 GNU Aspell spell-checker runtime l ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libqca2 2.0.2-1libraries for the Qt Cryptographic ii libqca2-plugin-ossl 0.1~20070904-4 QCA OSSL plugin for libqca2 ii libqt4-dbus 4:4.6.3-4+squeeze1 Qt 4 D-Bus module ii libqt4-network4:4.6.3-4+squeeze1 Qt 4 network module ii libqt4-qt3support 4:4.6.3-4+squeeze1 Qt 3 compatibility library for Qt ii libqt4-xml4:4.6.3-4+squeeze1 Qt 4 XML module ii libqtcore44:4.6.3-4+squeeze1 Qt 4 core module ii libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module ii libstdc++64.4.5-8The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-4 X11 client-side library ii libxss1 1:1.2.0-2 X11 Screen Saver extension library ii zlib1g1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages psi recommends: ii sox 14.3.1-1 Swiss army knife of sound processi Versions of packages psi suggests: ii libqca2-plugin-gnupg 2.0.0~beta3-1 QCA gnupg plugin for libqca2 pn psi-translations none (no description available) ii xdg-utils1.0.2+cvs20100307-2 desktop integration utilities from -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701700: psi: I'd like to have a disable-option for each soundevent.
Hi Jan, On Tue, Feb 26, 2013 at 03:05:05PM +0100, Jan Niehusmann wrote: I'm sorry, but I think there's no way to get such a change into wheeze at this time. Wheezy is frozen, and only fixes for critical bugs are allowed. And for jessie, we'll have psi 0.15 (or higher). no Problem. Don't worry about that. I know that wheezy is frozen... I just wrote the patch for myself. If anybody likes it, he or she can download the source of 0.14 and apply my patch. I'll write a patch for 0.15 and send it to upstream. Would be cool if we could at least get a backport of this version to wheezy then... Best regards, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699619: psi: breaks audio after some sounds (maybe about 30 or 50) were played
Hello Jan, thank you for the hint. It is indeed a concurrency problem. I got the problem once again and had a look at my process list. There were two instances of aplay running, blocking the sounddevice. Sending them SIGTERM solved the problem / freed it again. Remains the question why sometimes an aplay process does not terminate well... So it may still be a bug. Regards, Martin On Mon, Feb 11, 2013 at 05:50:40PM +0100, Jan Niehusmann wrote: Maybe some kind of concurrency problem? Psi may call aplay again while an earlier instance is still running. Regards, Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701460: procps: in top, CPU is misspelled as Cpu
Package: procps Version: 1:3.2.8-9squeeze1 Severity: minor Tags: upstream In top, CPU is misspelled as Cpu. Since it is an acronym, it has to be written in capital letters. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.38-bpo.2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages procps depends on: ii initscripts2.88dsf-13.1+squeeze1 scripts for initializing and shutt ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libncurses55.7+20100313-5shared libraries for terminal hand ii libncursesw5 5.7+20100313-5shared libraries for terminal hand ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip Versions of packages procps recommends: ii psmisc22.11-1utilities that use the proc file s procps suggests no packages. -- Configuration Files: /etc/sysctl.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699619: psi: breaks audio after some sounds (maybe about 30 or 50) were played
Hi Jan, Psi just calls an external program to play sounds. You can configure the command to use in general/options/sound/player. that's interesting, but makes sense. Do you have a player manually configured? No, I don't have a player configured manually. The configuration is empty. If the configuration is empty, psi autodetects if it should use play or aplay. (aplay in case /proc/asound exists, play otherwise). Yes, /proc/asound/ exists. It should use aplay then, assuming you're right. Does the same problem occur if you play sounds by manually calling 'aplay' (or 'play')? I'm testing it at the moment, but not so far. My problem with the situation: What _if_ aplay plays correctly all the time, but in psi it breaks the sound after a while? (At the moment, for me, it seems to be the case.) Best regards, Martin On Mon, Feb 11, 2013 at 04:39:57PM +0100, Jan Niehusmann wrote: Psi just calls an external program to play sounds. You can configure the command to use in general/options/sound/player. If the configuration is empty, psi autodetects if it should use play or aplay. (aplay in case /proc/asound exists, play otherwise). In any case, I don't see how the behaviour you describe could be a psi bug. (Of course, I could be wrong.) Do you have a player manually configured? Does the same problem occur if you play sounds by manually calling 'aplay' (or 'play')? Regards, Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699619: psi: breaks audio after some sounds (maybe about 30 or 50) were played
Package: psi Version: 0.14-2 Severity: important Tags: upstream After some sound-notifications were played, the sounddevice somehow breaks. I.e. no more sounds are played (of course psi tries to) and I can't output any sound/music at all (e.g. with mplayer or something). Please feel free to mail me if I may help finding the cause. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.38-bpo.2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages psi depends on: ii libaspell15 0.60.6-4 GNU Aspell spell-checker runtime l ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libqca2 2.0.2-1libraries for the Qt Cryptographic ii libqca2-plugin-ossl 0.1~20070904-4 QCA OSSL plugin for libqca2 ii libqt4-dbus 4:4.6.3-4+squeeze1 Qt 4 D-Bus module ii libqt4-network4:4.6.3-4+squeeze1 Qt 4 network module ii libqt4-qt3support 4:4.6.3-4+squeeze1 Qt 3 compatibility library for Qt ii libqt4-xml4:4.6.3-4+squeeze1 Qt 4 XML module ii libqtcore44:4.6.3-4+squeeze1 Qt 4 core module ii libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module ii libstdc++64.4.5-8The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-4 X11 client-side library ii libxss1 1:1.2.0-2 X11 Screen Saver extension library ii zlib1g1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages psi recommends: ii sox 14.3.1-1 Swiss army knife of sound processi Versions of packages psi suggests: ii libqca2-plugin-gnupg 2.0.0~beta3-1 QCA gnupg plugin for libqca2 pn psi-translations none (no description available) ii xdg-utils1.0.2+cvs20100307-2 desktop integration utilities from -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699619: upstream flag
Please check and/or remove the upstream flag. I haven't tested it on an other Distribution than Debian, so it may be Debian-specific. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699003: mail-notification: please add an option to display the amount of _new_ mails instead of unread mails
Package: mail-notification Version: 5.4.dfsg.1-2.2 Severity: wishlist Tags: upstream Mail-notification just displays the amount of unread mails (if counter is activated). Please add an option to check for and/or show the amount of NEW mails instead of unread mails. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.38-bpo.2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages mail-notification depends on: ii gconf2 2.28.1-6 GNOME configuration database syste ii gnome-icon-theme 2.30.3-2 GNOME Desktop icon theme ii libart-2.0-2 2.3.21-1 Library of functions for 2D graphi ii libatk1.0-01.30.0-1 The ATK accessibility toolkit ii libbonobo2-0 2.24.3-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.24.3-1 The Bonobo UI library ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libdbus-1-31.2.24-4+squeeze1 simple interprocess messaging syst ii libdbus-glib-1-2 0.88-2.1 simple interprocess messaging syst ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.2-2.1+squeeze4FreeType 2 font engine, shared lib ii libgconf2-42.28.1-6 GNOME configuration database syste ii libglade2-01:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgmime-2.0-2a2.2.25-2 MIME library ii libgnome-keyring0 2.30.1-1 GNOME keyring services library ii libgnome2-02.30.0-1 The GNOME library - runtime files ii libgnomecanvas2-0 2.30.1-1 A powerful object-oriented display ii libgnomeui-0 2.24.3-1 The GNOME libraries (User Interfac ii libgnomevfs2-0 1:2.24.3-1GNOME Virtual File System (runtime ii libgnomevfs2-extra 1:2.24.3-1GNOME Virtual File System (extra m ii libgtk2.0-02.20.1-2 The GTK+ graphical user interface ii libice62:1.0.6-2 X11 Inter-Client Exchange library ii libnotify1 [libnot 0.5.0-2 sends desktop notifications to a n ii liborbit2 1:2.14.18-0.1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.28.3-1+squeeze2 Layout and rendering of internatio ii libpopt0 1.16-1lib for parsing cmdline parameters ii libsasl2-2 2.1.23.dfsg1-7Cyrus SASL - authentication abstra ii libsm6 2:1.1.1-1 X11 Session Management library ii libx11-6 2:1.3.3-4 X11 client-side library ii libxml22.7.8.dfsg-2+squeeze6 GNOME XML library ii notification-daemo 0.5.0-2 daemon to displays passive pop-up ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages mail-notification recommends: pn fetchyahoonone (no description available) pn getlive none (no description available) ii mail-notification-evoluti 5.4.dfsg.1-2.2 evolution support for mail notific mail-notification suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699004: mail-notification: please add an option to display multiple mailboxes separately in systray
Package: mail-notification Version: 5.4.dfsg.1-2.2 Severity: wishlist Tags: upstream Please add an option to display multiple mailboxes separately in the notification area (e.g. two mailboxes = two icons, two counters) instead of one summarized notification. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.38-bpo.2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages mail-notification depends on: ii gconf2 2.28.1-6 GNOME configuration database syste ii gnome-icon-theme 2.30.3-2 GNOME Desktop icon theme ii libart-2.0-2 2.3.21-1 Library of functions for 2D graphi ii libatk1.0-01.30.0-1 The ATK accessibility toolkit ii libbonobo2-0 2.24.3-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.24.3-1 The Bonobo UI library ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libdbus-1-31.2.24-4+squeeze1 simple interprocess messaging syst ii libdbus-glib-1-2 0.88-2.1 simple interprocess messaging syst ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.2-2.1+squeeze4FreeType 2 font engine, shared lib ii libgconf2-42.28.1-6 GNOME configuration database syste ii libglade2-01:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgmime-2.0-2a2.2.25-2 MIME library ii libgnome-keyring0 2.30.1-1 GNOME keyring services library ii libgnome2-02.30.0-1 The GNOME library - runtime files ii libgnomecanvas2-0 2.30.1-1 A powerful object-oriented display ii libgnomeui-0 2.24.3-1 The GNOME libraries (User Interfac ii libgnomevfs2-0 1:2.24.3-1GNOME Virtual File System (runtime ii libgnomevfs2-extra 1:2.24.3-1GNOME Virtual File System (extra m ii libgtk2.0-02.20.1-2 The GTK+ graphical user interface ii libice62:1.0.6-2 X11 Inter-Client Exchange library ii libnotify1 [libnot 0.5.0-2 sends desktop notifications to a n ii liborbit2 1:2.14.18-0.1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.28.3-1+squeeze2 Layout and rendering of internatio ii libpopt0 1.16-1lib for parsing cmdline parameters ii libsasl2-2 2.1.23.dfsg1-7Cyrus SASL - authentication abstra ii libsm6 2:1.1.1-1 X11 Session Management library ii libx11-6 2:1.3.3-4 X11 client-side library ii libxml22.7.8.dfsg-2+squeeze6 GNOME XML library ii notification-daemo 0.5.0-2 daemon to displays passive pop-up ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages mail-notification recommends: pn fetchyahoonone (no description available) pn getlive none (no description available) ii mail-notification-evoluti 5.4.dfsg.1-2.2 evolution support for mail notific mail-notification suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663911: watchdog: missing important informations in package description
Package: watchdog Version: 5.9-1 Severity: minor Tags: patch Important informations are missing in the long package description; the short description is (or can be) misleading too. This package/program can either be used as a software watchdog and/or can be used to pet a hardware watchdog. It isn't just a software watchdog (can be used otherwise - bad short description) and the functionality to pet hardware watchdogs should be mentioned (at least) in the long description. The new package description in 5.10-1 and later is still unsatisfactory in my opinion. It *really* should be mentioned that this package also provides an opportunity to pet hardware watchdogs. Here is my suggestion: short description: ## System health checker that also trigger kernel watchdogs and may pet a hardware watchdog if available ## long description: # The watchdog program writes to /dev/watchdog every ten seconds. If the device is opened but not written to within a minute, the machine will reboot. This feature is available when the kernel is built with 'software watchdog' support (standard in Debian kernels) or if the machine is equipped with a hardware watchdog. If a hardware watchdog is available, this package can also be used to pet it. The ability to reboot will depend on the state of the machine and interrupts if the kernel software watchdog is used. The watchdog tool itself runs several health checks and acts accordingly if the system is not in a good shape. # Best regards, Martin Teufel -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i586) Kernel: Linux 2.6.32-5-geode Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages watchdog depends on: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii udev164-3/dev/ and hotplug management daemo watchdog recommends no packages. watchdog suggests no packages. -- Configuration Files: /etc/watchdog.conf changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663911: watchdog: missing important informations in package description
Hello Justin, I *fully* agree with your corrections and diff file except for your choice of the short description. In my opinion it would be better to mention the fact that this package can handle software *and* hardware watchdogs. So I would prefer your second suggestion: system health checker and software/hardware watchdog handler The ability to reboot will depend on the state of the machine and interrupts if the kernel software watchdog is used. If this is saying The kernel software watchdog's ability to reboot will depend on the state of the machine and interrupts. ...then I think it would be clearer expressed that way. I assume that this is what it wants to say and fully agree with your suggestion. It's really expressed better this way. Best regards, Martin On Wed, Mar 14, 2012 at 11:52:44PM +, Justin B Rye wrote: (I am not the maintainer, but I help out with description reviews on the debian-l10n-english mailinglist, and I noticed this bug report.) Martin Teufel wrote: Important informations are missing in the long package description; the short description is (or can be) misleading too. This package/program can either be used as a software watchdog and/or can be used to pet a hardware watchdog. It isn't just a software watchdog (can be used otherwise - bad short description) and the functionality to pet hardware watchdogs should be mentioned (at least) in the long description. The new package description in 5.10-1 and later is still unsatisfactory in my opinion. For a start, it's ungrammatical - trigger should be triggers or can trigger! Plus, DevRef 6.2.2 recommends not capitalising the first word of a synopsis. It *really* should be mentioned that this package also provides an opportunity to pet hardware watchdogs. Here is my suggestion: short description: ## System health checker that also trigger kernel watchdogs and may pet a hardware watchdog if available ## That's much too long, too much like jargon, and still ungrammatical. Is there a general term that could be used to describe both triggering and petting a watchdog? I would suggest: system health checker and watchdog handler Or you might make it system health checker and software/hardware watchdog handler My patch goes for the simpler approach, on the principle that if you don't specify, the reader can assume it means either kind; but I may of course be displaying my ignorance of how watchdog functions. long description: # The watchdog program writes to /dev/watchdog every ten seconds. If the device is opened but not written to within a minute, the machine will reboot. This feature is available when the kernel is built with 'software watchdog' support (standard in Debian kernels) or if the machine is equipped with a hardware watchdog. If a hardware watchdog is available, this package can also be used to pet it. Yes, there's room for that term here, and even for an explanation, but there's no need to repeat the concept of if a hardware watchdog is available. I would suggest: The watchdog program writes to /dev/watchdog every ten seconds. If the device is opened but not written to within a minute, the machine will reboot. This feature is available when the kernel is built with software watchdog support (standard in Debian kernels) or if the machine is equipped with a hardware watchdog (in which case this package can also be used to pet it, resetting its timer). (Standardising some punctuation details in the direction of the debian-l10n-english house style.) The ability to reboot will depend on the state of the machine and interrupts if the kernel software watchdog is used. If this is saying The kernel software watchdog's ability to reboot will depend on the state of the machine and interrupts. ...then I think it would be clearer expressed that way. The watchdog tool itself runs several health checks and acts accordingly if the system is not in a good shape. That last paragraph has crept in since the last time this text passed through d-l-e, and it could do with a couple of tweaks: The watchdog tool itself runs several health checks and acts appropriately if the system is not in good shape. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610271: proposal for new package description
Since this bug is still unfixed, I want to suggest a new package description. The new short description may be: A software watchdog and a tool to pet hardware watchdogs The new long description may be: The watchdog program writes to /dev/watchdog every ten seconds. If the device is opened but not written to within a minute, the machine will reboot. This can be done either by a hardware watchdog which is pet by this tool, or by a software watchdog which is also provided through this program. This feature is available if the kernel is built with 'software watchdog' support (standard in Debian kernels). In the case of the software watchdog (and just in this case), the ability to reboot will depend on the state of the machine and interrupts. I suggest to upload the package with the new description into main even if there is no new upstream version so it can't mislead more users. Best regards, Martin pgpZoMOsgw5cC.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi! On Thu, May 05, 2011 at 05:07:05PM -0500, Jonathan Nieder wrote: Mm, I have read your report carefully enough yet, but: did you get any response upstream? I would suggest filing a bug at [1], product DRI, component DRM/Radeon, version unspecified (yes, this is the place for kernel DRI bugs), mentioning which versions worked and did not work, pointing to your lkml message and attaching logs. No, I did not. I followed your suggestion and filed a bug at bugs.freedesktop.org. That way one could be sure upstream knows about the problem. :) That's the point. I thought by mailing to the LKML upstream would get informed about this, but that seems to be not the case. Then I thought the debian kernel team would inform upstream, but that seems to be not the case either... If you do so, do please send us the bug number. Here it is: Bug 37040 Best regards, Martin pgpL0kOv9Lx3S.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi, sorry, this was just a bad copypaste mistake: (it was the same with Linux 2.6.32-5-amd64 (2.6.32-31)) should have been: (it was the same with Linux 2.6.38-2-amd64 (2.6.38-3)) See the bug. I already mentioned it there. On Mon, May 09, 2011 at 08:15:05PM -0500, Jonathan Nieder wrote: forwarded 624549 https://bugs.freedesktop.org/show_bug.cgi?id=37040 quit Martin Teufel wrote: Here it is: Bug 37040 Thanks! Marking it. kernel: Linux 2.6.38-bpo.2-amd64 (2.6.38-3~bpo60+1) (it was the same with Linux 2.6.32-5-amd64 (2.6.32-31)) That's interesting. Are there any previous versions that did not exhibit the problem? pgpOp3Q9IIQDZ.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi, I want and have to rectify my last mail: This patch is obviously not applied in 2.6.38-bpo.2 because I get: [5.924366] drm: Unknown parameter `edid_strict' Could you get this applied to the next version of a linux backport? Best regards, Martin On Tue, May 03, 2011 at 10:29:27PM +0200, Martin Teufel wrote: Hi together, does someone know if this patch has been applied already to linux-image-2.6.38-bpo.2-amd64 (2.6.38-3~bpo60+1)? I installed this image yesterday and had the idea to test the drm.edid_strict=0 parameter on it today. - It works like a charm. ;) Dunno why my patch didn't work... (But I don't have the time nor the mood to track this down atm.) Nevertheless: Thank you for trying to help me. - And sorry for bugreporting this twice and not cc-ing the last mail. Reason for the first was that I never used reportbug on this machine before and therefore had no .reportbugrc on it which caused in a nonexistent mail address due to some circumstances. Best regards, Martin pgpOTcbiGFgyl.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi, On Thu, May 05, 2011 at 03:56:31PM -0500, Jonathan Nieder wrote: So that leaves us with a puzzle: does that mean that 2.6.38-3~bpo60+1 fixed it (forgetting about the drm.edid_strict parameter for a moment)? no. Without drm.edid_strict=0 the error occurs (every 10 seconds ...). With drm.edid_strict=0 given, the error doesn't occur but KMS gets disabled (don't know why and figured this out only today, when I got to the machine (did this test via a serial line behind a ssh connection on tuesday). Ah, sorry I wasn't clearer before. The edid_strict patch is something Alex had been thinking about but it is not in appliable shape (it does not have strict enough buffer size checks to cope with e.g. maliciously made hardware). And of course it's even better if it is possible through a driver change to get an uncorrupted edid. Hm, I see (and agree). So we/I'll wait for a fix from upstream. I got back to drm_kms_helper.poll=0 for now. Regards, Martin pgp3Tec2TApJt.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi together, does someone know if this patch has been applied already to linux-image-2.6.38-bpo.2-amd64 (2.6.38-3~bpo60+1)? I installed this image yesterday and had the idea to test the drm.edid_strict=0 parameter on it today. - It works like a charm. ;) Dunno why my patch didn't work... (But I don't have the time nor the mood to track this down atm.) Nevertheless: Thank you for trying to help me. - And sorry for bugreporting this twice and not cc-ing the last mail. Reason for the first was that I never used reportbug on this machine before and therefore had no .reportbugrc on it which caused in a nonexistent mail address due to some circumstances. Best regards, Martin On Tue, May 03, 2011 at 02:01:08PM -0500, Jonathan Nieder wrote: Thanks; cc-ing the bug log. So, my only other suggestion is a few rounds of bisection. It works like this: apt-get install git build-essential git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git cd linux-2.6 git bisect start git bisect bad v2.6.37 git bisect good v2.6.32;# or whichever was known to be good # now it checks out a version half-way between make localmodconfig;# minimal configuration make deb-pkg ... install the package, reboot, test ... git bisect good;# if it doesn't spam dmesg git bisect bad; # if it does git bisect skip;# if some other bug makes it hard to test # okay, next iteration... make oldconfig make deb-pkg At the end of this process, we would know what the first bad commit is, which can be very helpful for tracking it down. Just narrowing down the regression range with a few rounds is already useful; in that case, if you send git bisect log output at the end we should be able to use it to figure something out. If you are the visual sort of person like I am, git bisect visualize with gitk installed can show what's going on between steps. Thanks again for working on this, and sorry I don't have more useful advice. Regards, Jonathan pgpH88omeVqgt.pgp Description: PGP signature
Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Hi, I applied this patch to the source tree of linux 2.6.38 with debian patches (package linux-source-2.6.38 of wheezy), compiled the kernel with the same config as of debians linux-image-2.6.38-2-amd64 (wheezy) and set 'drm_kms_helper.poll=0', but it had absolutely no affect. Same messages every 10 seconds. Any further suggestions? Best regards, Martin On Fri, Apr 29, 2011 at 04:46:08PM -0500, Jonathan Nieder wrote: Thanks for letting us know. Could you try the patch from https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7 and boot with the drm.edid_strict=0 option? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624549: linux-image-2.6.38-2-amd64: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Package: linux-2.6 Version: 2.6.38-3 Severity: important Tags: upstream Hi, I encountered a bug in the radeon driver module of 2.6.37 which still exists in 2.6.38. I have a mainboard called M2A-VM which has VGA, DVI and display port as graphic output ports. When I boot Debian GNU/Linux with Linux 2.6.37 or 2.6.38 I get every 10 seconds: radeon :01:05.0: HDMI-A-1: EDID block 0 invalid. [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID This error message is spamming to tty1 (and because of my configuration to ttyS0 too). With radeon.modeset=0 set, I get rid of this messages by disabling KMS for this driver. This behaviour is also described here: http://ubuntuforums.org/showthread.php?t=1607778 My board has no HDMI port btw. - I think the driver should either not search for the HDMI-A-1: EDID block 0 resp. a HDMI connected monitor while the board has no HDMI port at all or just probe for it once instead of every 10 seconds. I don't see any reason for probing every 10 seconds but I don't know if there is one. I already reportet this on the LKML btw. Regards, Martin -- 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: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=UUID=c491e50b-1626-4ab2-bb2f-9d9c795a0ea9 ro console=tty0 console=ttyS0,115200n8 drm_kms_helper.poll=0 ** Not tainted ** Kernel log: [7.020103] input: PS/2 Logitech Mouse as /devices/platform/i8042/serio1/input/input4 [7.029227] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.034620] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034623] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034626] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034628] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034631] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034633] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034636] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034639] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034641] [7.086413] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.091835] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091838] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091840] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091843] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091845] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091848] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091850] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091853] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091855] [7.142701] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.148085] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148088] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148090] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148093] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148095] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148098] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148101] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148103] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148105] [7.198952] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.204332] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204335] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204337] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204340] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204343] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204345] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204348] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204350] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204352] [7.205893] radeon :01:05.0: HDMI-A-1: EDID block 0 invalid. [7.211985] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID [7.224664] [drm] fb mappable at 0xFA04 [7.228916] [drm] vram apper at 0xFA00 [7.233062] [drm] size 2150400 [7.236169] [drm] fb depth is 8 [7.239361] [drm]pitch is 1792 [7.250869] Console: switching to colour frame buffer device 200x75 [
Bug#624486: linux-image-2.6.38-2-amd64: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Package: linux-2.6 Version: 2.6.38-3 Severity: important Hi, I encountered a bug in the radeon driver module of 2.6.37 which still exists in 2.6.38. I have a mainboard called M2A-VM which has VGA, DVI and display port as graphic output ports. When I boot Debian GNU/Linux with Linux 2.6.37 or 2.6.38 I get every 10 seconds: radeon :01:05.0: HDMI-A-1: EDID block 0 invalid. [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID This error message is spamming to tty1 (and because of my configuration to ttyS0 too). With radeon.modeset=0 set, I get rid of this messages by disabling KMS for this driver. This behaviour is also described here: http://ubuntuforums.org/showthread.php?t=1607778 My board has no HDMI port btw. - I think the driver should either not search for the HDMI-A-1: EDID block 0 resp. a HDMI connected monitor while the board has no HDMI port at all or just probe for it once instead of every 10 seconds. I don't see any reason for probing every 10 seconds but I don't know if there is one. I already reportet this on the LKML btw. Regards, Martin -- 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: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=UUID=c491e50b-1626-4ab2-bb2f-9d9c795a0ea9 ro console=tty0 console=ttyS0,115200n8 drm_kms_helper.poll=0 ** Not tainted ** Kernel log: [7.020103] input: PS/2 Logitech Mouse as /devices/platform/i8042/serio1/input/input4 [7.029227] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.034620] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034623] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034626] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034628] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034631] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034633] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034636] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034639] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034641] [7.086413] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.091835] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091838] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091840] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091843] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091845] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091848] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091850] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091853] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091855] [7.142701] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.148085] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148088] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148090] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148093] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148095] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148098] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148101] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148103] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148105] [7.198952] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.204332] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204335] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204337] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204340] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204343] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204345] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204348] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204350] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204352] [7.205893] radeon :01:05.0: HDMI-A-1: EDID block 0 invalid. [7.211985] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID [7.224664] [drm] fb mappable at 0xFA04 [7.228916] [drm] vram apper at 0xFA00 [7.233062] [drm] size 2150400 [7.236169] [drm] fb depth is 8 [7.239361] [drm]pitch is 1792 [7.250869] Console: switching to colour frame buffer device 200x75 [7.259926] fb0:
Bug#622797: update-notifier-common: would be nice if /usr/lib/update-notifier/apt_check.py would omit n packages are security updates if no packages can be updated at all
Package: update-notifier-common Version: 0.99.3debian8 Severity: wishlist In my (maybe a bit subjective) opinion, the second line of this message is superfluous: 0 packages can be updated. 0 updates are security updates. Maybe the second line can/should be omitted. I see no sense in saying 0 updates are security updates. when 0 packages can be updated.. In this case, the second line is superfluous and a line containing no information can/should be omitted. So I would code sth. like (pseudocode) if n0 in 'n packages can be updated.' do print 'm updates are security updates.'. It's just a thought... -- 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.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages update-notifier-common depends on: ii python 2.6.6-3+squeeze6 interactive high-level object-orie ii python-apt 0.7.100.1Python interface to libapt-pkg Versions of packages update-notifier-common recommends: ii libpam-modules1.1.1-6.1 Pluggable Authentication Modules f update-notifier-common suggests no packages. -- Configuration Files: /etc/apt/apt.conf.d/10periodic changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610271: watchdog: missing important informations in package description
Package: watchdog Version: 5.9-1 Severity: minor Important informations are missing in the long package description; the short description is (or can be) misleading too. This package/program can either be used as a software watchdog and/or can be used to pet a hardware watchdog. It isn't just a software watchdog (can be used otherwise - bad short description) and the functionality to pet hardware watchdogs should be mentioned (at least) in the long description. -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-bpo.5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607493: grub-pc: giving output to serial line *and* console isn't documented very well
Package: grub-pc
Version: 1.98+20100804-10
Severity: wishlist
Tags: upstream
In difference to grub(-legacy), there is no option in grub2 to set a timeout
for choosing whether to use the console or the serial line for the bootmenu.
In the grub2 manual, section 13.2.2 it is documented that you can do:
terminal_input [--append|--remove] [terminal1] [terminal2]
I needed some time to realize that that implies you can set
terminal_input serial console
terminal_output serial console
in grub.cfg, so that the menu goes to serial line and console concurrently.
After that, it was just a guess, that
GRUB_TERMINAL=serial console
in /etc/default/grub would do it.
So my request is to make a clear mention to this in the grub manual section
13.2.2 and maybe include an example in /etc/default/grub like:
#GRUB_TERMINAL=console serial # for concurrent output of the bootmenu to
console and serial line
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/sda2 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda1 /boot ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sda6 /tmp ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sda7 /home ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/sda8 /data ext3 rw,relatime,errors=continue,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-SAMSUNG_HM160HC_S12TJDRZ233094
(hd1) /dev/disk/by-id/ata-CF_CARD_2GB_0
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
terminal_input serial console
terminal_output serial console
set timeout=5
play 480 440 1
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-486' --class debian --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 2439f5e7-d2bd-4361-98ec-3b64b9e7a18f
echo'Loading Linux 2.6.32-5-486 ...'
linux /vmlinuz-2.6.32-5-486
root=UUID=8b80e9e9-f8fc-451c-8332-4d168d177977 ro console=tty0
console=ttyS0,115200n8
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-486
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-486 (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 2439f5e7-d2bd-4361-98ec-3b64b9e7a18f
echo'Loading Linux 2.6.32-5-486 ...'
linux /vmlinuz-2.6.32-5-486
root=UUID=8b80e9e9-f8fc-451c-8332-4d168d177977 ro single console=tty0
console=ttyS0,115200n8
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-486
}
menuentry 'Debian GNU/Linux, with Linux 2.6.26-2-geode' --class debian --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 2439f5e7-d2bd-4361-98ec-3b64b9e7a18f
echo'Loading Linux 2.6.26-2-geode ...'
linux /vmlinuz-2.6.26-2-geode
root=UUID=8b80e9e9-f8fc-451c-8332-4d168d177977 ro console=tty0
console=ttyS0,115200n8
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.26-2-geode
}
menuentry 'Debian GNU/Linux, with Linux 2.6.26-2-geode (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 2439f5e7-d2bd-4361-98ec-3b64b9e7a18f
echo'Loading Linux 2.6.26-2-geode ...'
linux /vmlinuz-2.6.26-2-geode
root=UUID=8b80e9e9-f8fc-451c-8332-4d168d177977 ro single console=tty0
console=ttyS0,115200n8
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.26-2-geode
}
menuentry 'Debian GNU/Linux, with Linux 2.6.26-2-486' --class debian --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
Bug#580604: /usr/sbin/update-grub: update-grub does not append default kernel options console=... (i.e. console=ttyS0, 115200n8) to memtest86+ kernel entry
Package: grub Version: 0.97-47lenny2 Severity: normal File: /usr/sbin/update-grub update-grub does not append default kernel options console=... (i.e. console=ttyS0,115200n8) to memtest86+ kernel entry (and removes it if existing, of course). I have installed memtest86+ 2.01 and set # memtest86=true in grubs menu.lst. Since memtest86+ has serial support as a linux boot parameter since 2.00, kopt console=ttyS0,115200n8 should be added to the memtest86+ kernel line when update-grub is invoked. -- Package-specific info: *** BEGIN /boot/grub/device.map (hd0) /dev/sda *** END /boot/grub/device.map *** BEGIN /proc/mounts /dev/sda2 / ext3 rw,errors=remount-ro,data=ordered 0 0 /dev/sda5 /home ext3 rw,errors=continue,data=ordered 0 0 /dev/sda6 /data ext3 rw,errors=continue,data=ordered 0 0 *** END /proc/mounts *** BEGIN /boot/grub/menu.lst -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages grub depends on: ii grub-common 1.96+20080724-16 GRand Unified Bootloader, version ii libc6 2.7-18lenny2 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand grub recommends no packages. Versions of packages grub suggests: pn grub-legacy-doc none (no description available) pn mdadm none (no description available) pn multiboot-doc none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579306: memtest86+: does not invoke update-grub after installation
Package: memtest86+ Version: 2.01-1.1 Severity: normal After the installation of memtest86+, update-grub is not invoked (but I think it should be, because it is a kernel and I have set # memtest86=true in /boot/grub/menu.lst). I'm using grub 0.97. BTW: I think update-grub should also be invoked during deinstallation (which is done neither). -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash memtest86+ depends on no packages. memtest86+ recommends no packages. Versions of packages memtest86+ suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn hwtoolsnone(no description available) pn kernel-patch-badramnone(no description available) pn memtester none(no description available) ii mtools 3.9.11-1 Tools for manipulating MSDOS files -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
