Bug#785415: ulogd2 fails with kernel 4.0.0-1

[hugo vanwoerkom]

Hi Chris,
That FIREHOL_LOG_MODE="NFLOG" works like a charm.  Thanks!

Hugo

On Sun, Aug 30, 2015 at 6:27 AM, Chris Boot  wrote:

> Control: tag -1 pending
> Control: retitle -1 Document removal of ULOG target in kernels 3.17+
>
> On 16/05/15 00:31, hugo vanwoerkom wrote:
> > Running Sid dist-upgraded on May 12 2015 which went to kernel 4.0.0-1.
> > I run the firewall via Firehol and use  'FIREHOL_LOG_MODE="ULOG"'.
> > Iptables then gets errors because it cannot find ULOG.
> > That is because ulogd2 failed with:
> >
> > May 15 11:56:39 hdbb ulogd[5785]: Can't create ULOG handle
> > May 15 11:56:39 hdbb ulogd[5785]: error starting `ulog1'
> >
> > When this dist-upgraded system is booted with kernel 3.16.0-4 ulogd2
> > starts correctly:
> >
> > May 15 15:46:24 hdbb ulogd[27455]: building new pluginstance stack:
> > 'ulog1:ULOG,base1:BASE,ip2str1:IP2STR,print1:PRINTPK
>
> Hi Hugo,
>
> The underlying problem is that the ULOG target was removed from
> iptables/ebtables in the 3.17 kernel. You will need to migrate to using
> the NFLOG target instead.
>
> It appears that from version 1.296 onwards, Firehol supports using the
> NFLOG target, so you should be able to simply set
> FIREHOL_LOG_MODE="NFLOG" and leave the ULOG stuff disabled in ulogd.conf.
>
> I have added a NEWS.Debian entry documenting the change in the kernel in
> commite 20a0ed299793c40e345ecee46f234423574da0b [1].
>
> HTH,
> Chris
>
> 1.
>
> http://anonscm.debian.org/cgit/collab-maint/ulogd2.git/commit/?id=e20a0ed299793c40e345ecee46f234423574da0b
>
> --
> Chris Boot
> bo...@bootc.net
>



-- 
https://www.dhamma.org/

Bug#723973: [gsmartcontrol] gsmartcontrol-root fails to launch

[hugo vanwoerkom]

Package: gsmartcontrol
Version: 0.8.7-1.1
Severity: normal

gsmartcontrol-root doesn't work here either. If I launch it from konsole,
kdesu asks for root's password, but then fails to launch complaining:
>> Cannot execute command ' 'gsmartcontrol $@''.

This bug is almost 2 years old now.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages gsmartcontrol depends on:
ii  libatk1.0-0  2.16.0-2
ii  libatkmm-1.6-1   2.22.7-2.1
ii  libc62.19-18
ii  libcairo21.14.2-2
ii  libcairomm-1.0-1 1.10.0-1.1
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-4
ii  libgcc1  1:5.1.1-11
ii  libgdk-pixbuf2.0-0   2.31.4-2
ii  libglib2.0-0 2.44.1-1
ii  libglibmm-2.4-1c2a   2.44.0-1
ii  libgtk2.0-0  2.24.28-1
ii  libgtkmm-2.4-1c2a1:2.24.4-1.1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  libpangomm-1.4-1 2.36.0-1
ii  libpcre3 2:8.35-6
ii  libsigc++-2.0-0c2a   2.4.1-1
ii  libstdc++6   5.1.1-11
ii  menu 2.1.47
ii  smartmontools6.3+svn4002-2+b2

gsmartcontrol recommends no packages.

gsmartcontrol suggests no packages.

-- no debconf information

Bug#723973: [gsmartcontrol] gsmartcontrol-root fails to launch

[hugo vanwoerkom]

Package: gsmartcontrol Version: 0.8.7-1.1 Severity: normal
gsmartcontrol-root doesn't work here either. If I launch it from konsole,
kdesu asks for root's password, but then fails to launch complaining: >>
Cannot execute command ' 'gsmartcontrol $@''. This bug is almost 2 years
old now. -- System Information: Debian Release: stretch/sid APT prefers
unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign
Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked
to /bin/dash Init: unable to detect Versions of packages gsmartcontrol
depends on: ii libatk1.0-0 2.16.0-2 ii libatkmm-1.6-1 2.22.7-2.1 ii libc6
2.19-18 ii libcairo2 1.14.2-2 ii libcairomm-1.0-1 1.10.0-1.1 ii
libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgcc1 1:5.1.1-11 ii
libgdk-pixbuf2.0-0 2.31.4-2 ii libglib2.0-0 2.44.1-1 ii libglibmm-2.4-1c2a
2.44.0-1 ii libgtk2.0-0 2.24.28-1 ii libgtkmm-2.4-1c2a 1:2.24.4-1.1 ii
libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii
libpangoft2-1.0-0 1.36.8-3 ii libpangomm-1.4-1 2.36.0-1 ii libpcre3
2:8.35-6 ii libsigc++-2.0-0c2a 2.4.1-1 ii libstdc++6 5.1.1-11 ii menu
2.1.47 ii smartmontools 6.3+svn4002-2+b2 gsmartcontrol recommends no
packages. gsmartcontrol suggests no packages. -- no debconf information

Bug#785415: ulogd2 fails with kernel 4.0.0-1

[hugo vanwoerkom]

Package: ulogd2
Severity: important

Reportbug is down with:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785407
So I am doing this by hand.

Running Sid dist-upgraded on May 12 2015 which went to kernel 4.0.0-1.
I run the firewall via Firehol and use  'FIREHOL_LOG_MODE="ULOG"'.
Iptables then gets errors because it cannot find ULOG.
That is because ulogd2 failed with:

May 15 11:56:39 hdbb ulogd[5785]: Can't create ULOG handle
May 15 11:56:39 hdbb ulogd[5785]: error starting `ulog1'

When this dist-upgraded system is booted with kernel 3.16.0-4 ulogd2 starts
correctly:

May 15 15:46:24 hdbb ulogd[27455]: building new pluginstance stack:
'ulog1:ULOG,base1:BASE,ip2str1:IP2STR,print1:PRINTPK

Thank you for your attention.

Hugo Vanwoerkom

Bug#730130: k3b gets no optical device found if udisks2 is not installed

[hugo vanwoerkom]

Package: k3b
Version: 2.0.2-7
Severity: normal

Dear Maintainer,

After upgrading Sid on November 14, 2013 k3b would say that no optical
device was found.
Before this date k3b worked as expected. Since May 10, 2012 I install hal
and udisks for k3b to work.
Per http://forum.kde.org/viewtopic.php?f=260&t=117063 now udisks2 is needed
and indeed installing udisks2 solves the problem.
I don't use KDE, just konsole, kwrite and k3b.
Note that udisks2 is not listed as a dependency of k3b.

Regards,

Hugo Vanwoerkom


-- Package-specific info:
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/sr0
Using /dev/cdrom of unknown capabilities
Device type: Removable CD-ROM
Version: 5
Response Format: 2
Capabilities   :
Vendor_info: 'ASUS'
Identification : 'DRW-24B1ST  '
Revision   : '1.03'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages k3b depends on:
ii  cdparanoia 3.10.2+debian-11
ii  cdrdao 1:1.2.3-2
ii  genisoimage9:1.1.11-2
ii  k3b-data   2.0.2-7
ii  kde-runtime4:4.11.3-1
ii  libc6  2.17-96
ii  libk3b62.0.2-7
ii  libkcddb4  4:4.11.3-1
ii  libkcmutils4   4:4.11.3-2
ii  libkde3support44:4.11.3-2
ii  libkdecore54:4.11.3-2
ii  libkdeui5  4:4.11.3-2
ii  libkfile4  4:4.11.3-2
ii  libkio54:4.11.3-2
ii  libknotifyconfig4  4:4.11.3-2
ii  libqt4-qt3support  4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqt4-xml 4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqtcore4 4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqtgui4  4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqtwebkit4   2.2.1-7
ii  libsolid4  4:4.11.3-2
ii  libstdc++6 4.8.2-5
ii  wodim  9:1.1.11-2

Versions of packages k3b recommends:
ii  dvd+rw-tools 7.1-10
ii  growisofs7.1-10
pn  libk3b6-extracodecs  
pn  vcdimager

Versions of packages k3b suggests:
pn  k3b-extrathemes  
pn  k3b-i18n 
pn  kde-config-cddb  
pn  movixmaker-2 
pn  normalize-audio  
pn  sox  

-- no debconf information

Bug#720716: initramfs-tools: workaround in 707286 solves serious problem

[hugo vanwoerkom]

Followup-For: Bug #707286
Package: initramfs-tools
Version: 0.113

Dear Maintainer,

The workaround from 707286 (add ‘sleep 1’ before “modprobe -q dm-mod” in
scripts/local-top/lvm2) has made the latest Debian kernels bootable again!
They all got stuck in the initramfs shell because the root on LVM could not
be found.

Hugo Vanwoerkom


-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root  12M Jul 31 09:36 /boot/initrd.img-3.10-1-amd64
-rw-r--r-- 1 root root  12M Aug 24 10:06 /boot/initrd.img-3.10-2-amd64
-rw-r--r-- 1 root root 3.1M Aug 15 11:01 /boot/initrd.img-3.10.4-nodeb-amd64
-rw-r--r-- 1 root root 3.1M Aug 20 20:11 /boot/initrd.img-3.10.7-nodeb-amd64
-rw-r--r-- 1 root root  11M Jul  4 15:02 /boot/initrd.img-3.2.0-4-amd64
-rw-r--r-- 1 root root 3.1M Jul  4 17:30 /boot/initrd.img-3.8.1-nodeb-amd64
-rw-r--r-- 1 root root  12M Jul 18 10:37 /boot/initrd.img-3.9-1-amd64
-- /proc/cmdline
root=/dev/mapper/vgHDB-HDBB vga=791 nouveau.modeset=0
resume=LABEL=HD502HJ_02.08

-- resume
RESUME=UUID=f2b6dbbe-6ed3-4d57-8c11-823ce166b7c5
-- /proc/filesystems
ext2

-- lsmod
Module  Size  Used by
nvidia   9315617  50
drm   211856  2 nvidia
pci_stub   12429  1
vboxpci19094  0
vboxnetadp 25443  0
vboxnetflt 23697  0
vboxdrv   217395  4 vboxnetadp,vboxnetflt,vboxpci
nf_conntrack_irc   12427  0
nf_conntrack_ftp   12651  0
xt_helper  12507  12
xt_tcpudp  12570  32
nf_conntrack_ipv4  18549  61
nf_defrag_ipv4 12483  1 nf_conntrack_ipv4
xt_conntrack   12681  49
xt_limit   12638  14
nf_conntrack   59788  5
xt_helper,xt_conntrack,nf_conntrack_ftp,nf_conntrack_irc,nf_conntrack_ipv4
ipt_ULOG   12862  13
nfnetlink_log  17396  1
nfnetlink  12989  2 nfnetlink_log
iptable_filter 12536  1
ip_tables  22036  1 iptable_filter
x_tables   19041  7
xt_helper,ipt_ULOG,ip_tables,xt_tcpudp,xt_limit,xt_conntrack,iptable_filter
loop   22869  0
snd_hda_codec_via  22832  1
snd_hda_intel  35718  13
snd_hda_codec 122850  2 snd_hda_codec_via,snd_hda_intel
snd_hwdep  13189  1 snd_hda_codec
snd_pcm68525  6 snd_hda_codec,snd_hda_intel
acpi_cpufreq   13280  1
i2c_nforce212628  0
edac_mce_amd   17070  0
edac_core  43448  0
mperf  12453  1 acpi_cpufreq
psmouse74832  0
serio_raw  12940  0
snd_page_alloc 13018  2 snd_pcm,snd_hda_intel
video  17792  0
kvm_amd47719  0
processor  28526  1 acpi_cpufreq
i2c_core   24353  3 drm,nvidia,i2c_nforce2
snd_timer  22773  5 snd_pcm
kvm   301458  1 kvm_amd
snd53068  24
snd_hwdep,snd_timer,snd_hda_codec_via,snd_pcm,snd_hda_codec,snd_hda_intel
hid_a4tech 12531  0
pcspkr 12632  0
soundcore  13026  1 snd
wmi13243  0
thermal_sys23137  2 video,processor
microcode  30413  0
button 12944  0
asus_atk0110   17246  0
evdev  17611  15
ext2   59601  8
mbcache13082  1 ext2
hid_generic12393  0
usb_storage48158  0
usbhid 40964  0
hid81894  3 hid_a4tech,hid_generic,usbhid
sr_mod 21988  0
cdrom  35212  1 sr_mod
sg 26095  0
sd_mod 40541  10
crc_t10dif 12348  1 sd_mod
dm_mod 64008  27
ata_generic12490  0
firewire_ohci  31931  0
firewire_core  49211  1 firewire_ohci
crc_itu_t  12347  1 firewire_core
ehci_pci   12472  0
ohci_hcd   26678  0
ehci_hcd   40590  1 ehci_pci
ahci   25148  9
libahci23136  1 ahci
pata_amd   13378  0
forcedeth  54034  0
libata141969  4 ahci,libahci,pata_amd,ata_generic
scsi_mod  158249  5 sg,usb_storage,libata,sd_mod,sr_mod
usbcore   134993  5
usb_storage,ohci_hcd,ehci_hcd,ehci_pci,usbhid
usb_common 12440  1 usbcore

-- /etc/initramfs-tools/modules
dm_mod
-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:

/usr/share/initramfs-tools/hooks:
busybox
dmsetup
keymap
klibc
kmod
lvm2
thermal
udev


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT

Bug#610207: gphoto2: Error (-60: 'Could not lock the device')

[hugo vanwoerkom]

With gphoto2 2.4.14-1 and Wheezy with LXDE I am getting the exact same
error and the workaround is the one given above. Except in my case the file
manager is PCManFM, which comes with LXDE. In the X display shows up the
error and the option to start the FM. Once there the 2 camera files must be
unmounted in the left side  window of PCManFM. The camera is a Kodak Co.
CX4210.

Hugo Vanwoerkom

Bug#689519: libapt-pkg4.12: SIGSEGV when used by apt-get or aptitude

[hugo vanwoerkom]

Running wheezy: I did not get such an error:

<==>
root@HDBF:/# apt-get install google-chrome-beta
The following packages will be upgraded:
  google-chrome-beta
1 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
Need to get 36.0 MB of archives.
After this operation, 5,333 kB of additional disk space will be used.
Preparing to replace google-chrome-beta 22.0.1229.91-r158759 (using
.../google-chrome-beta_23.0.1271.22-r160452_amd64.deb) ...

Unpacking replacement google-chrome-beta ...
Processing triggers for desktop-file-utils ...
Processing triggers for man-db ...
Setting up google-chrome-beta (23.0.1271.22-r160452) ...
root@HDBF:/# apt-cache policy libapt-pkg4.12
libapt-pkg4.12:
  Installed: 0.9.7.5
  Candidate: 0.9.7.5

  Version table:

 *** 0.9.7.5 0

500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages

100 /var/lib/dpkg/status

root@HDBF:/# exit
<===>

Hugo Vanwoerkom

Bug#689012: chrony: Refuses to start: Fatal error : Cannot read information from uname, sorry

[hugo vanwoerkom]

I patched it, but probably not right:

...
diff -Naur chrony-1.24-3.1-build.orig/chrony-1.24/sys_linux.c
chrony-1.24-3.1-build.new/chrony-1.24/sys_linux.c
--- chrony-1.24-3.1-build.orig/chrony-1.24/sys_linux.c  2012-09-28
19:42:44.0 -0500
+++ chrony-1.24-3.1-build.new/chrony-1.24/sys_linux.c   2012-09-28
19:21:24.0 -0500
@@ -736,7 +736,12 @@
 LOG_FATAL(LOGF_SysLinux, "Cannot uname(2) to get kernel version,
sorry.");
   }
   if (sscanf(uts.release, "%d.%d.%d", &major, &minor, &patch) != 3) {
-LOG_FATAL(LOGF_SysLinux, "Cannot read information from uname, sorry");
+   patch = 0;
+  }
+  else {
+if (sscanf(uts.release, "%d.%d.%d", &major, &minor) != 2) {
+   LOG_FATAL(LOGF_SysLinux, "Cannot read information from uname,
sorry");
+}
   }

   LOG(LOGS_INFO, LOGF_SysLinux, "Linux kernel major=%d minor=%d patch=%d",
major, minor, patch);
...

The amd64 .deb with the patch is here:

https://docs.google.com/open?id=0BwcitGMmYn5-N253a1VZb24yMVk

Hugo Vanwoerkom

Bug#689012: chrony: Refuses to start: Fatal error : Cannot read information from uname, sorry

[hugo vanwoerkom]

The problem is in the kernel release:

hugo@HDBF:~$ uname -r
+ uname -r
3.5-trunk-amd64

he expects 3.5.-trunk-amd64 in sys_linux.c #738.

Hugo Vanwoerkom

Bug#661240: mime-support 3.52-1 breaks WordPress

[hugo vanwoerkom]

On Fri, Aug 3, 2012 at 10:35 PM, Charles Plessy  wrote:

> Le Sun, Feb 26, 2012 at 10:37:22AM -0600, hugo vanwoerkom a écrit :
> > The fix is to uncomment line 440 of /etc/mime.types:
> > 'application/x-httpd-php phtml pht php'.
>
> Dear Hugo,
>
> It looks like without this entry in /etc/mime.types, some php pages were
> served
> as text on your system.
>
> Strangely, it did not occur for the whole WordPress installation,
> otherwise you
> would not have even had the welcome message.  On my system, I made a quick
> test
> and Apache httpd is able to display correctly a trivial PHP page.
>
> Can you confirm that the bug still occurs with the latest version
> of Wheezy's packages for wordpress and libapache2-mod-php5 ?
>
>
Charles, I no longer uncomment that line. I use wordpress 3.2.1 from
upstream.

root@HDBF:/home/hugo# apt-cache policy libapache2-mod-php5
libapache2-mod-php5:
  Installed: 5.4.4-2
  Candidate: 5.4.4-2
  Version table:
 *** 5.4.4-2 0
500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
100 /var/lib/dpkg/status

Still running wheezy.
Thanks.

Hugo

Bug#683768: linux-image-3.2.0-3-amd64: hibernate 3x slower after upgrade to linux-image-3.2.0-3-amd64

[hugo vanwoerkom]

 It gets stranger still: when I compile a kernel after 'make
localmodconfig' to streamline it, then the hibernate time sometimes changes.
This is true for 3.2.23-1: it goes from 31s. to 10s.
It is not true for 3.2.21-3: it stays at 31s.
Neither is it true for 3.5.0 from experimental: it was 30s. and streamlined
only went to 20s.

Hugo

Bug#683768: linux-image-3.2.0-3-amd64: hibernate 3x slower after upgrade to linux-image-3.2.0-3-amd64

[hugo vanwoerkom]

On Sun, Aug 5, 2012 at 6:36 PM, Ben Hutchings  wrote:

> On Sun, 2012-08-05 at 17:50 -0500, hugo vanwoerkom wrote:
> [...]
>
> > Yes, 3.2.19-1 still takes 12s. But as to problems
> > disappearing/appearing I could have sworn that 3.2.21-3 took 12s. last
> > night but now it takes 35s. I think the problem comes from the kernel,
> > because that is the only thing that I am varying and I have been
> > hibernating this box for years with up to now predictable speeds.
> > Don't use wicd though.
>
> If the change was made between 3.2.19 and 3.2.21 then it might be due
> to:
>
> commit d006ab31cd818f5e4dda2453fd09767063f49933
> Author: Michal Hocko 
> Date:   Tue May 29 15:06:45 2012 -0700
>
> mm: consider all swapped back pages in used-once logic
>
> So you could test with the reverse of that patch (attached), following
> the instructions at
> <http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2>
>
>
I tested all the snapshot kernels again and the change occurred with
3.2.21-1. That is the first one to have a hibernate of 35s. The one
previous to that 3.2.20-1 is fine with 10s. These results are consistent.
It could not be the mm vmscan patch because both 3.2.20-1 and 3.2.21-1 have
that set the same way:

if (referenced_ptes) {
if (PageSwapBacked(page))
return PAGEREF_ACTIVATE;


Hugo

Bug#683768: linux-image-3.2.0-3-amd64: hibernate 3x slower after upgrade to linux-image-3.2.0-3-amd64

[hugo vanwoerkom]

On Sun, Aug 5, 2012 at 4:17 PM, Vincent Lefevre  wrote:

> On 2012-08-05 15:27:47 -0500, hugo vanwoerkom wrote:
> > Let me check some more Ben. I just checked 3.2.21-3 again and it took
> > 40secs. to hibernate. Should be 12secs.  I'll let you know for sure.
>
> Have you tried to downgrade to 3.2.19-1 to see if it still takes 12s?
> It seems that problems can strangely appear and disappear without any
> known reason. Are you sure that the problem comes from the kernel
> itself and not from one of the hooks (see /var/log/pm-suspend.log)?
> For me, the slow suspend (not always reproducible) comes from the
> wicd hook.
>
>

Yes, 3.2.19-1 still takes 12s. But as to problems disappearing/appearing I
could have sworn that 3.2.21-3 took 12s. last night but now it takes 35s. I
think the problem comes from the kernel, because that is the only thing
that I am varying and I have been hibernating this box for years with up to
now predictable speeds. Don't use wicd though.

Hugo

Bug#683768: linux-image-3.2.0-3-amd64: hibernate 3x slower after upgrade to linux-image-3.2.0-3-amd64

[hugo vanwoerkom]

On Sun, Aug 5, 2012 at 2:47 PM, Ben Hutchings  wrote:

> On Sun, 2012-08-05 at 12:11 -0500, hugo vanwoerkom wrote:
> > Slow hibernate occurs for the first time in 3.2.23-1.
>
> I really don't understand this, because I can't see any changes between
> 3.2.21-3 and 3.2.23-1 that could slow down disk I/O for hibernation.
>
> My suspicion is that this has something to do with the amount of memory
> that needs to be saved.  But I also don't see why that would increase by
> any significant amount.
>
> > None of the kernels previous to that one have the problem.
> > 3.5-1~experimental.1 still has the problem.
>
> Please report this upstream at https://bugzilla.kernel.org under product
> 'Power Management', component 'Hibernation/Suspend'.



Let me check some more Ben. I just checked 3.2.21-3 again and it took
40secs. to hibernate. Should be 12secs.  I'll let you know for sure.

Hugo

Bug#683768: linux-image-3.2.0-3-amd64: hibernate 3x slower after upgrade to linux-image-3.2.0-3-amd64

[hugo vanwoerkom]

Slow hibernate occurs for the first time in 3.2.23-1.
None of the kernels previous to that one have the problem.
3.5-1~experimental.1 still has the problem.
Thanks!

Hugo

Bug#683768: linux-image-3.2.0-3-amd64: hibernate 3x slower after upgrade to linux-image-3.2.0-3-amd64

[hugo vanwoerkom]

But it's a Debian problem.

I compiled the stable 3.4.7 kernel from kernel.org and that does not have
the problem: normal hibernate, takes 12secs.

Hugo

Bug#683768: linux-image-3.2.0-3-amd64: hibernate 3x slower after upgrade to linux-image-3.2.0-3-amd64

[hugo vanwoerkom]

Unfortunately the swap.c patch makes no difference at all. :-(

Hugo

Bug#683768: linux-image-3.2.0-3-amd64: hibernate 3x slower after upgrade to linux-image-3.2.0-3-amd64

[hugo vanwoerkom]

On Fri, Aug 3, 2012 at 6:59 PM, Ben Hutchings  wrote:

> On Fri, 2012-08-03 at 16:24 -0500, hugo vanwoerkom wrote:
> > On Fri, Aug 3, 2012 at 3:22 PM, Ben Hutchings 
> > wrote:
> > On Fri, Aug 03, 2012 at 02:09:38PM -0500, hugo vanwoerkom
> > wrote:
> > > On Fri, Aug 3, 2012 at 12:36 PM, Julien Cristau
> >  wrote:
> > >
> > > > On Fri, Aug  3, 2012 at 12:06:13 -0500, hugo vanwoerkom
> > wrote:
> > > >
> > > > > Package: src:linux
> > > > > Version: 3.2.23-1
> > > > > Severity: normal
> > > > >
> > > > > Hibernate of about 400.000 pages takes normally 12secs.
> > after the last
> > > > > upgrade of the kernel (wheezy or sid) it takes 40 secs.
> >
> >
> > You don't say what the previous version was.  You may be able
> > to find
> > this information in /var/log/dpkg.log if you don't remember.
> >
> >
> >
> >
> > Sorry, the previous version was 3.2.19-1.
>
> I can't see any change since 3.2.19-1 that would explain this.  But
> please do test the patch:
>

Running the compile right now. Will let you know. Thanks Ben!

Hugo



>
> > There are some fixes for bad hibernation performance in Linux
> > 3.2.24.
> > You can try these out by applying
> > <
> http://git.kernel.org/?p=linux/kernel/git/bwh/linux-3.2.y.git;a=patch;h=6ed6791a1697afcb1615b4252d0c304a743b5f4d
> >
> > following the instructions at
> > <
> http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2>.
>
>
>
> --
> Ben Hutchings
> Experience is directly proportional to the value of equipment destroyed.
>  - Carolyn
> Scheppner
>

Bug#683768: linux-image-3.2.0-3-amd64: hibernate 3x slower after upgrade to linux-image-3.2.0-3-amd64

[hugo vanwoerkom]

On Fri, Aug 3, 2012 at 3:22 PM, Ben Hutchings  wrote:

> On Fri, Aug 03, 2012 at 02:09:38PM -0500, hugo vanwoerkom wrote:
> > On Fri, Aug 3, 2012 at 12:36 PM, Julien Cristau 
> wrote:
> >
> > > On Fri, Aug  3, 2012 at 12:06:13 -0500, hugo vanwoerkom wrote:
> > >
> > > > Package: src:linux
> > > > Version: 3.2.23-1
> > > > Severity: normal
> > > >
> > > > Hibernate of about 400.000 pages takes normally 12secs. after the
> last
> > > > upgrade of the kernel (wheezy or sid) it takes 40 secs.
>
> You don't say what the previous version was.  You may be able to find
> this information in /var/log/dpkg.log if you don't remember.
>
>
Sorry, the previous version was 3.2.19-1.

Hugo


> > > It is not the disk
> > > > space because when I move that to a different device, the same thing
> > > > happens. This might be a feature, but it is so noticable :-(
> > > > Thanks!
> > > >
> > > Is that reproducible without the nvidia driver?
> > >
> > Yes, Julien, behavior is the same slow hibernate w/o the nvidia driver.
>
> There are some fixes for bad hibernation performance in Linux 3.2.24.
> You can try these out by applying
> <
> http://git.kernel.org/?p=linux/kernel/git/bwh/linux-3.2.y.git;a=patch;h=6ed6791a1697afcb1615b4252d0c304a743b5f4d
> >
> following the instructions at
> <http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2>.
>
> Ben.
>
> --
> Ben Hutchings
> We get into the habit of living before acquiring the habit of thinking.
>   - Albert
> Camus
>

Bug#683768: linux-image-3.2.0-3-amd64: hibernate 3x slower after upgrade to linux-image-3.2.0-3-amd64

[hugo vanwoerkom]

On Fri, Aug 3, 2012 at 12:36 PM, Julien Cristau  wrote:

> On Fri, Aug  3, 2012 at 12:06:13 -0500, hugo vanwoerkom wrote:
>
> > Package: src:linux
> > Version: 3.2.23-1
> > Severity: normal
> >
> > Hibernate of about 400.000 pages takes normally 12secs. after the last
> > upgrade of the kernel (wheezy or sid) it takes 40 secs. It is not the
> disk
> > space because when I move that to a different device, the same thing
> > happens. This might be a feature, but it is so noticable :-(
> > Thanks!
> >
> Is that reproducible without the nvidia driver?
>
> Yes, Julien, behavior is the same slow hibernate w/o the nvidia driver.

Hugo


-- 
Being unified, you have no liking;
being transmuted, you have no fixity.
http://gpc-qt.sourceforge.net/
https://linuxcounter.net/machine/419602.html
http://debian-oaxaca.blogspot.com/

Bug#409349: usbhid: control queue full; hung apcupsd task

[hugo vanwoerkom]

On Thu, Apr 5, 2012 at 6:49 AM, Steven Chamberlain  wrote:
> On 05/04/12 04:52, hugo vanwoerkom wrote:
>>> Thanks much.  Do you remember roughly when you last experienced this
>>> bug?
>>
>> Jan. 31 2011
>> But I have no records of what kernel I was running then :-(
>
> Hi Hugo,
>
> Are you still using the APC UPS, and the problem has gone away?  What
> kernel are you running now?  That would at least narrow it down to a
> version where this is fixed.
>

apcupsd  3.14.10-1 with MODEL: Back-UPS RS 700G and Sid kernel
3.2.0-2-amd64. Can't reproduce problem.

Hugo



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#409349: usbhid: control queue full; hung apcupsd task

[hugo vanwoerkom]

On Wed, Apr 4, 2012 at 7:18 PM, Jonathan Nieder  wrote:
> Tom Wright wrote:
>> On Thursday 05 April 2012 00:39:32 you wrote:
>>> Tom Wright wrote:
>
 I haven't seen this bug in quite a while, so maybe it's fixed in 3.X?
 Best see what others say too I guess.
>>>
>>> Thanks for the update.  How long have you been using the wheezy/sid
>>> kernel?  Do you mind if I forward this information to the bug log?
>>
>> Quite a while now - I run sid on the machine which has a UPS, so however long
>> it's been the standard kernel in that branch.  A few months, at least.  
>> You're
>> welcome to send it on to the bug log too.
>
> Thanks much.  Do you remember roughly when you last experienced this
> bug?
>

Jan. 31 2011
But I have no records of what kernel I was running then :-(

Hugo


> (The last time I see in the bug log is in 2007 with 2.6.17 or so :).
> Others have experienced it with kernels as new as 2.6.32-41 so I'd be
> especially interested if you remember the behavior with 2.6.33,
> 2.6.35, 2.6.38, etc.  /var/log/dpkg.log* should have the upgrade
> history of the kernel package if that helps jog your memory.)
>
> Jonathan



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#661240: mime-support 3.52-1 breaks WordPress

[hugo vanwoerkom]

The fix is to uncomment line 440 of /etc/mime.types:
'application/x-httpd-php phtml pht php'.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#661240: mime-support 3.52-1 breaks WordPress

[hugo vanwoerkom]

Package: mime-support
Version: 3.51-1
Severity: normal

I have WordPress 2.1.3 installed. When I dist-upgraded in Sid and
Wheezy and mime-support 3.52-1 was installed I could no longer use it.
The problem went away when I dist-upgraded and pinned mime-support to 3.51-1.

The problem shows up especially using the administrator function: the
screen is messed up and there is no prompt for password. This is what
the screen looked like:
https://docs.google.com/leaf?id=0BwcitGMmYn5-NWRiYWFmZTctYWIxNy00ZmYwLThkYWMtMzFhNTJjYThlMDZl

and this is what it is supposed to look like:
https://docs.google.com/leaf?id=0BwcitGMmYn5-ZWU4MGQ4ODctOTE2OS00MWUzLTk1OWUtMTU4ZmY0NGIwNjc4

Not being fluent in PHP5 I fail to see why this would happen but the
fact is that it does. WP was installed from tar from upstream, not
from the Debian package.

Thanks.
Hugo Vanwoerkom


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

mime-support depends on no packages.

Versions of packages mime-support recommends:
ii  file  5.10-1

mime-support 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#648077: [Pkg-xfce-devel] Bug#648077: xfce4-timer-plugin cannot be selected to be added to panel

[hugo vanwoerkom]

You're right. The timer was already present in panel1. I was a little
bar at the end.
My error. I'll close the bug. Thanks for your help.

Hugo Vanwoerkom



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#648077: [Pkg-xfce-devel] Bug#648077: xfce4-timer-plugin cannot be selected to be added to panel

[hugo vanwoerkom]

On Wed, Nov 9, 2011 at 12:32 AM, Yves-Alexis Perez  wrote:
> On mar., 2011-11-08 at 17:27 -0600, hugo vanwoerkom wrote:
>> On Tue, Nov 8, 2011 at 3:49 PM, Yves-Alexis Perez  wrote:
>> > On mar., 2011-11-08 at 13:52 -0600, hugo vanwoerkom wrote:
>> >> Package: xfce4-timer-plugin
>> >> Version: 0.6.2-1Severity: normal
>> >> Hi,
>> >>
>> >> After installing xfce4-timer-plugin it cannot be selected to be added
>> >> to a panel: the 'add' button is greyed out.
>> >>
>> > That usually mean is has already been added.
>> >
>>
>> To a new panel where nothing is visible?
>>
> To any panel
>
> --

But if it is already added to any panel then I should be able to
select it and set it, but nothing is selectable and there are no items
in the new panel.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#648077: [Pkg-xfce-devel] Bug#648077: xfce4-timer-plugin cannot be selected to be added to panel

[hugo vanwoerkom]

On Tue, Nov 8, 2011 at 3:49 PM, Yves-Alexis Perez  wrote:
> On mar., 2011-11-08 at 13:52 -0600, hugo vanwoerkom wrote:
>> Package: xfce4-timer-plugin
>> Version: 0.6.2-1Severity: normal
>> Hi,
>>
>> After installing xfce4-timer-plugin it cannot be selected to be added
>> to a panel: the 'add' button is greyed out.
>>
> That usually mean is has already been added.
>

To a new panel where nothing is visible?

Regards,

Hugo Vanwoerkom



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#648077: xfce4-timer-plugin cannot be selected to be added to panel

[hugo vanwoerkom]

Package: xfce4-timer-plugin
Version: 0.6.2-1Severity: normal
Hi,

After installing xfce4-timer-plugin it cannot be selected to be added
to a panel: the 'add' button is greyed out.

Regards,

Hugo Vanwoerkom

-- System Information:
Debian Release: sid  APT prefers unstable  APT policy: (500,
'unstable')Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores)Locale:
LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)Shell: /bin/sh linked to /bin/dash
Versions of packages xfce4-timer-plugin depends on:ii  libc6
    2.13-21ii  libcairo2           1.10.2-6.1ii  libgdk-pixbuf2.0-0
2.24.0-1ii  libglib2.0-0        2.28.8-1ii  libgtk2.0-0
2.24.7-1ii  libxfce4util4       4.8.2-1ii  libxfcegui4-4
4.8.1-5ii  xfce4-panel         4.8.6-1
xfce4-timer-plugin recommends no packages.
xfce4-timer-plugin 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#647831: xfce4-wmdock-plugin: wmdock does not swallow wmmount

[hugo vanwoerkom]

My error: if you start like: 'wmmount -- -w' then everything works
right. I'll close the bug. Thanks.

Hugo Vanwoerkom



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#647831: xfce4-wmdock-plugin: wmdock does not swallow wmmoun

[hugo vanwoerkom]

Package: xfce4-wmdock-pluginVersion: 0.3.4-1Severity: normal
Hi,

I use the wmdock plugin in XFCE4, my favorite app! I can now make my
desktop look like it did in Fvwm...
However, it refuses to swallow
wmmount(http://packages.debian.org/sid/wmmount). Swallows everything
else I throw at it, not wmmount :-(

Hugo Vanwoerkom

-- System Information:Debian Release: wheezy  APT prefers testing  APT
policy: (500, 'testing')Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)Locale:
LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)Shell: /bin/sh linked to /bin/dash
Versions of packages xfce4-wmdock-plugin depends on:ii  libc6
     2.13-21ii  libcairo2           1.10.2-6.1ii  libgdk-pixbuf2.0-0
2.24.0-1ii  libglib2.0-0        2.28.6-1ii  libgtk2.0-0
2.24.6-2ii  libwnck22           2.30.7-1ii  libx11-6
2:1.4.4-2ii  libxfce4util4       4.8.2-1ii  libxfcegui4-4
4.8.1-5ii  xfce4-panel         4.8.6-1
xfce4-wmdock-plugin recommends no packages.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#635537: acpitool does not handle the latest kernel release 3.0.0.

[hugo vanwoerkom]

This is better:
==

--- acpitool-orig//acpitool-0.5.1/src/acpitool.cpp  2009-08-13
14:37:48.0 -0500
+++ acpitool-new//acpitool-0.5.1/src/acpitool.cpp   2011-07-28
08:40:37.0 -0500
@@ -200,14 +200,15 @@
 file_in.getline(str, 9);
 file_in.close();

-if(strncmp(str,"2.4",3)==0)
-{
+if(strncmp(str,"2.4",3)==0) {
Kernel_24 = 1;
Kernel_26 = 0;
 }
-
-if(strncmp(str,"2.6",3)==0)
-{
+else if(strncmp(str,"2.6",3)==0) {
+   Kernel_24 = 0;
+   Kernel_26 = 1;
+}
+else {
Kernel_24 = 0;
Kernel_26 = 1;
 }
========

Hugo Vanwoerkom



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#635537: acpitool does not handle the latest kernel release 3.0.0.

[hugo vanwoerkom]

Package: acpitool
Version: 0.5.1-2
Severity: normal

This patch will fix the problem:

--- acpitool-orig-build//acpitool-0.5.1/src/acpitool.cpp
2009-08-13 14:37:48.0 -0500
+++ acpitool-chg-build//acpitool-0.5.1/src/acpitool.cpp 2011-07-26
10:04:58.0 -0500
@@ -211,6 +211,12 @@
Kernel_24 = 0;
Kernel_26 = 1;
 }
+
+if(strncmp(str,"3.0",3)==0)
+{
+   Kernel_24 = 0;
+   Kernel_26 = 1;
+}

 return 0;
 }


Thanks to Sven Joachim for pointing this out.

Regards,

Hugo Vanwoerkom

-- System Information:
Debian Release: wheezy/sid
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages acpitool depends on:
ii  libc6 2.13-11Embedded GNU C Library: Shared lib
ii  libgcc1   1:4.6.1-5  GCC support library
ii  libstdc++64.6.1-5GNU Standard C++ Library v3

Versions of packages acpitool recommends:
ii  acpid 1:2.0.10-1 Advanced Configuration and Power I

acpitool 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#635391: linux-image-3.0.0-1-amd64: Function Do_Suspend : could not open file : /proc/acpi/sleep.

[hugo vanwoerkom]

Package: linux-2.6
Version: 3.0.0-1
Severity: normal

Cannot suspend to disk with acpitool -S:
Function Do_Suspend : could not open file : /proc/acpi/sleep.
You must have write access to /proc/acpi/sleep to suspend your computer.

-- Package-specific info:
** Version:
Linux version 3.0.0-1-amd64 (Debian 3.0.0-1) (b...@decadent.org.uk)
(gcc version 4.5.3 (Debian 4.5.3-4) ) #1 SMP Sun Jul 24 0
2:24:44 UTC 2011

** Command line:
root=/dev/mapper/vgHDB-HDB6 vga=791 nouveau.modeset=0
resume=LABEL=6Y080P0.05 quiet

** Not tainted

** Kernel log:
[1.848877] usbcore: registered new interface driver usb-storage
[1.848879] USB Mass Storage support registered.
[1.850269] scsi8 : usb-storage 1-2:1.0
[1.850367] usbcore: registered new interface driver ums-cypress
[1.855223] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw
xa/form2 cdda tray
[1.855228] cdrom: Uniform CD-ROM driver Revision: 3.20
[1.855339] sr 2:0:0:0: Attached scsi CD-ROM sr0
[1.960088] usb 2-1: new high speed USB device number 2 using ehci_hcd
[2.095554] usb 2-1: New USB device found, idVendor=13fe, idProduct=1d00
[2.095557] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[2.095560] usb 2-1: Product: DataTraveler 2.0
[2.095561] usb 2-1: Manufacturer: Kingston
[2.095563] usb 2-1: SerialNumber: 5B791500042C
[2.095902] scsi9 : usb-storage 2-1:1.0
[2.512097] usb 4-2: new full speed USB device number 2 using ohci_hcd
[2.736128] usb 4-2: New USB device found, idVendor=051d, idProduct=0002
[2.736132] usb 4-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[2.736134] usb 4-2: Product: Back-UPS RS 700G FW:856.L1 .D USB
FW:L1
[2.736136] usb 4-2: Manufacturer: American Power Conversion
[2.736137] usb 4-2: SerialNumber: 3B1051X26126
[2.826963] generic-usb 0003:051D:0002.0001: hiddev0,hidraw0: USB
HID v1.00 Device [American Power Conversion Back-UPS RS
 700G FW:856.L1 .D USB FW:L1  ] on usb-:00:04.0-2/input0
[2.827096] usbcore: registered new interface driver usbhid
[2.827097] usbhid: USB HID core driver
[2.851189] scsi 8:0:0:0: Direct-Access WDC WD16 00AAJB-00J3A0
   PQ: 0 ANSI: 0
[2.952235] sd 8:0:0:0: Attached scsi generic sg4 type 0
[2.953639] sd 8:0:0:0: [sdd] 312581808 512-byte logical blocks:
(160 GB/149 GiB)
[2.954556] sd 8:0:0:0: [sdd] Write Protect is off
[2.954560] sd 8:0:0:0: [sdd] Mode Sense: 27 00 00 00
[2.99] sd 8:0:0:0: [sdd] No Caching mode page present
[2.955615] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[2.958287] sd 8:0:0:0: [sdd] No Caching mode page present
[2.958343] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[3.028802]  sdd: sdd1 sdd2 sdd3 sdd4 < sdd5 sdd6 sdd7 sdd8 >
[3.036161] sd 8:0:0:0: [sdd] No Caching mode page present
[3.036217] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[3.036273] sd 8:0:0:0: [sdd] Attached SCSI disk
[3.040064] usb 3-3: new low speed USB device number 2 using ohci_hcd
[3.097942] scsi 9:0:0:0: Direct-Access Kingston DataTraveler
2.0 PMAP PQ: 0 ANSI: 0 CCS
[3.192239] sd 9:0:0:0: Attached scsi generic sg5 type 0
[3.193407] sd 9:0:0:0: [sde] 4014080 512-byte logical blocks:
(2.05 GB/1.91 GiB)
[3.194805] sd 9:0:0:0: [sde] Write Protect is off
[3.194809] sd 9:0:0:0: [sde] Mode Sense: 23 00 00 00
[3.195825] sd 9:0:0:0: [sde] No Caching mode page present
[3.195883] sd 9:0:0:0: [sde] Assuming drive cache: write through
[3.199828] sd 9:0:0:0: [sde] No Caching mode page present
[3.199884] sd 9:0:0:0: [sde] Assuming drive cache: write through
[3.200585]  sde: sde1
[3.203816] sd 9:0:0:0: [sde] No Caching mode page present
[3.203872] sd 9:0:0:0: [sde] Assuming drive cache: write through
[3.203927] sd 9:0:0:0: [sde] Attached SCSI removable disk
[3.241121] usb 3-3: New USB device found, idVendor=09da, idProduct=0006
[3.241125] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[3.241127] usb 3-3: Product: USB Optical Mouse
[3.241128] usb 3-3: Manufacturer: A4Tech
[4.257404] device-mapper: uevent: version 1.0.3
[4.257466] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02)
initialised: dm-de...@redhat.com
[4.724853] PM: Starting manual resume from disk
[4.724857] PM: Hibernation image partition 8:21 present
[4.724858] PM: Looking for hibernation image.
[4.725196] PM: Image not found (code -22)
[4.725199] PM: Hibernation image not present or could not be loaded.
[5.803094] udevd[402]: starting version 172
[6.286936] input: Power Button as
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
[6.286941] ACPI: Power Button [PWRB]
[6.286999] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[6.287001] ACPI: Power Button [PWRF]
[6.299109] ACPI: acpi_idle registered with cpuidle
[6.299141] ACPI: processor limited to max C-state 1
[6.368447] wmi: Mapper loa

Bug#629534: Upgrade fails, resulting in unusable system (no dynamic linking)

[hugo vanwoerkom]

Package: libc6
Version: 2.13-5
Severity: normal

I upgraded libc6 from 2.13-4 -> 2.13-5 and experienced no difficulties.
But this is Sid amd64.

Regards,

Hugo Vanwoerkom

-- System Information:
Debian Release: wheezy/sid
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6 depends on:
ii  libc-bin  2.13-5 Embedded GNU C Library: Binaries
ii  libgcc1   1:4.6.0-11 GCC support library

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0] 1.5.39 Debian configuration management sy
pn  glibc-doc  (no description available)
ii  locales   2.13-5 Embedded GNU C Library: National L

-- debconf information:
  glibc/upgrade: true
  glibc/disable-screensaver:
  glibc/restart-failed:
* glibc/restart-services: mysql cron apache2



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#624008: udev: initramfs.hook include all programs for current /lib/udev/rules.d

[hugo vanwoerkom]

Hi,

But when I apply the patch and run update-initramfs I get:
E: /usr/share/initramfs-tools/hooks/udev failed with return 1.

Regards,

Hugo Vanwoerkom

-- 
zwei Seelen, eine Gedanke
http://gpc-qt.sourceforge.net/
http://counter.li.org/
http://debian-oaxaca.blogspot.com/

Bug#611646: apcupsd: Hang with Back-UPS LS 500

[hugo vanwoerkom]

Hi,

I get this with Squeeze and Sid, with kernel 2.6.32-5-amd64 and
2.6.37-2-amd64 and with apcupsd 3.14.4, 3.14.5, 3.14.7 and 3.14.8. I have
never gotten it in a system that is more than one year old and runs
2.6.32-trunk-686 and 3.14.5-2, but lately I haven't tried.

I switched motherboards on Oct. 19 2010 and never got it on the old
motherboard.

So you'd think it was the mobo: but this would be the only thing that goes
wrong with it: and there are:

Bus 001 Device 003: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A
EZ-USB AT2 USB 2.0 to ATA/ATAPI
Bus 002 Device 002: ID 13fe:1d00 Kingston Technology Company Inc.
DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive
Bus 004 Device 002: ID 051d:0002 American Power Conversion Uninterruptible
Power Supply
Bus 003 Device 002: ID 04b8:010f Seiko Epson Corp. Perfection 1250
Bus 003 Device 003: ID 09da:0006 A4 Tech Co., Ltd Optical Mouse WOP-35 /
Trust 450L Optical Mouse

3 other USB devices never have any problems (the Epson scanner is temporary
but has no problems.)

So it could be the Back-UPS LS 500: it is from Oct. 2005 and now 5 years
old. But why does a reboot clear up the error?

A very un-linux reboot is necessary to clear up the error: that 'control
queue full' message never goes away and shows up every 10 secs and the root
partition won't unmount because it is busy.

I am thinking of switching UPS's

Regards,

Hugo Vanwoerkom

Bug#567854: xserver-xorg: kbd actions on seat2 show up on console of seat1

[hugo vanwoerkom]

Hi KiBi,
Thanks for answering!
Although my heart is still with multiseat, my hardware changed and I can't
run it anymore: I lost one of the 2 displays.
Also I changed motherboard from an Epox 8VTAI to an Asus M4N98TD EVO, much
better! But it means more power too, so I have to change the PS and the UPS,
I have the former but not the latter: not enough $!
However, the biggest threat to multiseat is gdm: with gdm3 you can't start
multiple servers anymore:
http://preview.tinyurl.com/multiseat-dead
and to keep gdm I already have to 'apt-get -t squeeze install gdm' because
sid no longer has it...

However, this has nothing to do with 567854... Except to say that I cannot
test multiseat with the latest Sid :-(
As soon as I can get funds for a new kbd, new display and new UPS, I will
sure give it another try.

Thanks!

Hugo


--
zwei Seelen, eine Gedanke
http://gpc-qt.sourceforge.net/
http://counter.li.org/
http://debian-oaxaca.blogspot.com/

Bug#611082: apcupsd: USB problems with APC CS 500

[hugo vanwoerkom]

Hi,

Where did you get 3.14.7?

Regards,

Hugo Vanwoerkom

Bug#611646: apcupsd: Hang with Back-UPS LS 500

[hugo vanwoerkom]

Package: apcupsd
Version: 3.14.8-2
Severity: important

Since Jan. 19th 2011 apcupsd hangs, stops, after running from 1-6 hours. The
symptoms are always the same:

   1. The apps that monitor TIMELEFT and BCHARGE stop.
   2. Apcaccess does not respond
   3. 3 more apcupsd tasks appear in htop (from the 2 that are normally
   there)
   4. Half an hour later every 10 secs. this appears in syslog: Debian
   kernel: [ 4987.404050] generic-usb 0003:051D:0002.0001: control queue full.
   5. This refers to Bus 003 Device 002: ID 051d:0002 American Power
   Conversion Uninterruptible Power Supply
   6. Apcupsd cannot be cancelled or restarted
   7. Upon reboot / cannot be unmounted because it is busy.

Reboot finds that / was not unmounted correctly, e2fsck's it and reboots
again.

I have been running apcupsd on Sid for about 6 years with this unit, I am on
my 3rd battery. Sid is uptodate and udev is at version 164-4.

Regards,
Hugo Vanwoerkom

-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages apcupsd depends on:
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared
lib
ii  libgcc1   1:4.4.5-10 GCC support library
ii  libwrap0  7.6.q-19   Wietse Venema's TCP wrappers
libra

Versions of packages apcupsd recommends:
ii  apcupsd-doc   3.14.8-2   APC UPS Power Management
(document

Versions of packages apcupsd suggests:
pn  apcupsd-cgi(no description available)
pn  hal(no description available)
ii  udev  164-4  /dev/ and hotplug management
daemo

-- Configuration Files:
/etc/apcupsd/apcupsd.conf changed:
UPSCABLE smart
UPSTYPE usb
DEVICE
LOCKFILE /var/lock
SCRIPTDIR /etc/apcupsd
PWRFAILDIR /etc/apcupsd
NOLOGINDIR /etc
ONBATTERYDELAY 6
BATTERYLEVEL 5
MINUTES 3
TIMEOUT 0
ANNOY 300
ANNOYDELAY 60
NOLOGON disable
KILLDELAY 0
NETSERVER on
NISIP 127.0.0.1
NISPORT 3551
EVENTSFILE /var/log/apcupsd.events
EVENTSFILEMAX 10
UPSCLASS standalone
UPSMODE disable
STATTIME 0
STATFILE /var/log/apcupsd.status
LOGSTATS off
DATATIME 0

/etc/default/apcupsd changed:
APCACCESS=/sbin/apcaccess
ISCONFIGURED=yes

-- no debconf information

Bug#610816: wmtemp: Use libsensors4 to find sensor

[hugo vanwoerkom]

Package: wmtemp
Version: 0.0.6-3
Severity: wishlist


I have an M4N98TD EVO Asus motherboard. When I use wmtemp with that it finds
no sensors. But 'sensors' reports:

atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage:  +1.39 V  (min =  +0.80 V, max =  +1.80 V)
3.3V Voltage:   +3.26 V  (min =  +2.97 V, max =  +3.63 V)
5V Voltage: +5.00 V  (min =  +4.50 V, max =  +5.50 V)
12V Voltage:   +11.90 V  (min = +10.20 V, max = +13.80 V)
CPU FAN Speed: 1406 RPM  (min =  600 RPM)
CHASSIS1 FAN Speed:   0 RPM  (min =  600 RPM)
CHASSIS2 FAN Speed:   0 RPM  (min =  600 RPM)
CPU Temperature:+32.0°C  (high = +60.0°C, crit = +75.0°C)
MB Temperature: +27.0°C  (high = +45.0°C, crit = +75.0°C)

and so does 'xsensors'. The difference appears to be installing and using
libsensors4 and libsensors4-dev.
So I patched wmtemp to do so and now it reports CPU and MB temps. I attach
the patch.

Regards,

Hugo Vanwoerkom


-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages wmtemp depends on:
ii  libc6 2.11.2-9   Embedded GNU C Library: Shared
lib
ii  libsensors3   1:2.10.8-2 library to read
temperature/voltag
ii  libc6 2.11.2-9   Embedded GNU C Library: Shared
lib
ii  libsensors3   1:2.10.8-2 library to read
temperature/voltag
ii  libx11-6  2:1.3.3-4  X11 client-side library
ii  libxext6  2:1.1.2-1  X11 miscellaneous extension
librar
ii  libxpm4   1:3.5.9-1  X11 pixmap library
ii  lm-sensors1:3.1.2-6  utilities to read
temperature/volt

wmtemp recommends no packages.

wmtemp suggests no packages.

-- no debconf information


wmtemp.0.0.6.patch
Description: Binary data

Bug#610321: xsensors: source package does not compile

[hugo vanwoerkom]

I forgot to mention why I wanted to compile xsensors.

sensors and xsensors find the sensor but wmtemp does not:

hugo@Debian:~$ sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage:  +1.39 V  (min =  +0.80 V, max =  +1.80 V)
3.3V Voltage:   +3.26 V  (min =  +2.97 V, max =  +3.63 V)
5V Voltage: +5.03 V  (min =  +4.50 V, max =  +5.50 V)
12V Voltage:   +11.97 V  (min = +10.20 V, max = +13.80 V)
CPU FAN Speed: 1406 RPM  (min =  600 RPM)
CHASSIS1 FAN Speed:   0 RPM  (min =  600 RPM)
CHASSIS2 FAN Speed:   0 RPM  (min =  600 RPM)
CPU Temperature:+30.0°C  (high = +60.0°C, crit = +75.0°C)
MB Temperature: +25.0°C  (high = +45.0°C, crit = +75.0°C)

So I wanted to fid out why, for one they use different versions of
libsensors-dev.

Hugo Vanwoerkom

Bug#610321: xsensors: source package does not compile

[hugo vanwoerkom]

Package: xsensors
Version: 0.70-1.1
Severity: normal

Compiling the source package gets an error:

In file included from main.h:30,
 from main.c:22:
chips.h:64: error: type defaults to 'int' in declaration of
'sensors_feature'
chips.h:64: error: expected ';', ',' or ')' before '*' token
make[3]: *** [main.o] Error 1
make[3]: Leaving directory
`/sda7/hda10/backup.files/fromhd/home/hugo/xsensors_build/xsensors-0.70/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/sda7/hda10/backup.files/fromhd/home/hugo/xsensors_build/xsensors-0.70'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/sda7/hda10/backup.files/fromhd/home/hugo/xsensors_build/xsensors-0.70'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2

This refers to this line in chips.h:

updates *add_node( const sensors_chip_name *, const sensors_feature * );

Downloading the tarball of 0.70 from upstream and compiling that gets the
same error

I have lm-sensors 1:3.1.2-6 installed.

Regards,

Hugo Vanwoerkom

-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages xsensors depends on:
ii  libatk1.0-0   1.30.0-1   The ATK accessibility toolkit
ii  libc6 2.11.2-8   Embedded GNU C Library: Shared
lib
ii  libcairo2 1.8.10-6   The Cairo 2D vector graphics
libra
ii  libfontconfig12.8.0-2.1  generic font configuration
library
ii  libfreetype6  2.4.2-2.1  FreeType 2 font engine, shared
lib
ii  libglib2.0-0  2.24.2-1   The GLib library of C routines
ii  libgtk2.0-0   2.20.1-2   The GTK+ graphical user
interface
ii  libpango1.0-0 1.28.3-1   Layout and rendering of
internatio
ii  libsensors4   1:3.1.2-6  library to read
temperature/voltag

Versions of packages xsensors recommends:
ii  lm-sensors1:3.1.2-6  utilities to read
temperature/volt

xsensors suggests no packages.

-- no debconf information

Bug#603837: mondo/mindi fails with current kernel

[hugo vanwoerkom]

Package: mondo
Version: 2.2.7-2.1
Severity: important

The mondo/mindi packages will not work with the current stock kernel.
Upstream is at 
mondo_2.2.9.4-1<http://mondorescue.muskokamug.org/debian/5.0/mondo_2.2.9.4-1_i386.deb>and
mindi_2.0.7<http://mondorescue.muskokamug.org/debian/5.0/mindi_2.0.7_i386.deb>while
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560716 requested an update
a year ago almost.

Regards,

Hugo Vanwoerkom


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.36-trunk-686-bigmem (SMP w/1 CPU core)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages mondo depends on:
ii  afio  2.5-5  archive file manipulation
program
ii  buffer1.19-10Buffering/reblocking program
for t
ii  gawk  1:3.1.7.dfsg-5 GNU awk, a pattern scanning and
pr
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared
lib
ii  libnewt0.52   0.52.11-2  Not Erik's Windowing Toolkit -
tex
ii  mindi 2.0.7.5-1  creates boot/root disks based
on y

Versions of packages mondo recommends:
ii  dvd+rw-tools  7.1-9  DVD+-RW/R tools
ii  lzop  1.02~rc1-2 fast compression program

Versions of packages mondo suggests:
pn  mondo-doc  (no description available)
ii  ntfsprogs 2.0.0-1+b1 tools for doing neat things in
NTF

-- no debconf information

Bug#601368: acpi-fakekey: kernel oops on halt or reboot

[hugo vanwoerkom]

On Mon, Nov 15, 2010 at 7:30 AM, Michael Meskes  wrote:

> On Mon, Oct 25, 2010 at 09:08:48AM -0500, hugo vanwoerkom wrote:
> > Upon system halt or reboot I get a kernel oops that points to
> acpi_fakekeyd.
>
> Do you also see the oops if you just stop acpi_fakekeyd by calling
> "/etc/init.d/acpi-fakekey stop"? What happens if you manually remove the
> uinput
> module after killing acpi_fakekeyd?
>
> > Tainted: P   (2.6.32-5-686 #1) KT880-8237
>
> Do you see the same problem when using a non-tainted kernel?
>
>
Did a new install of Sid, avoiding acpi_fakekeyd: the error necessitated
running a live-cd before every boot to grub-install the mbr.
AFAIK the kernel is tainted because I use NVIDIA-Linux-x86-260.19.21.run to
be able to run a two-seater. It's the choice between that or not having one:
so tainted it stays.

Regards,

Hugo Vanwoerkom

Bug#602003: installation-reports: partition created hangs on boot

[hugo vanwoerkom]

The hang on boot is not due to the installer but due to 2.6.32-5-686 and the
nouveau driver: I have 2 Nvidia graphics cards:

Model: "nVidia GeForce 6200 (0x0221)"
Vendor: pci 0x10de "nVidia Corporation"
Device: pci 0x0221 "GeForce 6200 (0x0221)"

When I boot with 'nouveau.modeset=0' the hang goes away.

Nouveau is nice, avoid it like the plague.

Hugo Vanwoerkom

Bug#602003: installation-reports: partition created hangs on boot

[hugo vanwoerkom]

Package: installation-reports
Severity: normal

-- Package-specific info:

Boot method: CD
Image version: weekly build of 1/31/2010

Machine: PC homebuilt
Partitions: 
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/hdc5 ext2 7692876   6722104579996  93% /
tmpfstmpfs  452416 0452416   0% /lib/init/rw
udev tmpfs   10240   504  9736   5% /dev
tmpfstmpfs  452416   296452120   1% /dev/shm
/dev/hda7 ext226647936  14140972  11153324  56% /hda7
/dev/hda10ext229362324   9077412  18793352  33% /hda10
/dev/sdb7 ext238448276  16248400  20246776  45% /sda7
/dev/sdb8 ext257707836244944  54531436   1% /sda8
/dev/sda1 ext2 7692876   4256324   3045776  59% /sdb1

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:  [O ]
Detect network card:[O ]
Configure network:   [O ]
Detect CD:  [O ]
Load installer modules: [O ]
Detect hard drives:   [O ]
Partition hard drives:[O ]
Install base system:[O ]
Clock/timezone setup:   [O ]
User/password setup:[O ]
Install tasks:   [O ]
Install boot loader:   [O ]
Overall install: [O ]

Comments/Problems:

Booting the generated partition hangs on 'waiting for /dev to be populated'

Note that I generated this report on a different partition!

Thanks.

Hugo Vanwoerkom

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="5.0 (lenny) - installer build 20090209-10:04"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
umame -a: Linux debian 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686
unknown
lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. KT880 Host
Bridge [1106:0269]
lspci -knn: 00:00.1 Host bridge [0600]: VIA Technologies, Inc. KT880 Host
Bridge [1106:1269]
lspci -knn: 00:00.2 Host bridge [0600]: VIA Technologies, Inc. KT880 Host
Bridge [1106:2269]
lspci -knn: 00:00.3 Host bridge [0600]: VIA Technologies, Inc. KT880 Host
Bridge [1106:3269]
lspci -knn: 00:00.4 Host bridge [0600]: VIA Technologies, Inc. KT880 Host
Bridge [1106:4269]
lspci -knn: 00:00.7 Host bridge [0600]: VIA Technologies, Inc. KT880 Host
Bridge [1106:7269]
lspci -knn: 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237/VX700
PCI Bridge [1106:b198]
lspci -knn: 00:08.0 VGA compatible controller [0300]: nVidia Corporation
NV44A [GeForce 6200] [10de:0221] (rev a1)
lspci -knn: 00:0a.0 Multimedia audio controller [0401]: Creative Labs SB
Audigy LS [1102:0007]
lspci -knn: 00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VIA VT6420
SATA RAID Controller [1106:3149] (rev 80)
lspci -knn: Kernel driver in use: sata_via
lspci -knn: Kernel modules: sata_via
lspci -knn: 00:0f.1 IDE interface [0101]: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06)
lspci -knn: Kernel driver in use: VIA_IDE
lspci -knn: Kernel modules: via82cxxx
lspci -knn: 00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x
UHCI USB 1.1 Controller [1106:3038] (rev 81)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82x
UHCI USB 1.1 Controller [1106:3038] (rev 81)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x
UHCI USB 1.1 Controller [1106:3038] (rev 81)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82x
UHCI USB 1.1 Controller [1106:3038] (rev 81)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0
[1106:3104] (rev 86)
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: Kernel modules: ehci-hcd
lspci -knn: 00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237 ISA
bridge [KT600/K8T800/K8T890 South] [1106:3227]
lspci -knn: 00:11.5 Multimedia audio controller [0401]: VIA Technologies,
Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 60)
lspci -knn: 00:12.0 Ethernet controller [0200]: VIA Technologies, Inc.
VT6102 [Rhine-II] [1106:3065] (rev 78)
lspci -knn: Kernel driver in use: via-rhine
lspci -knn: Kernel modules: via-rhine

Bug#601368: acpi-fakekey: kernel oops on halt or reboot

[hugo vanwoerkom]

Package: acpi-fakekey
Version: 0.137-5
Severity: normal

Upon system halt or reboot I get a kernel oops that points to acpi_fakekeyd.
This is with the latest Sid kernel 2.6.32-5-686.
The system hangs afterwards and it messes up grub so I have to grub-install
from a live CD.
This is what syslog shows:

Oct 24 11:41:24 debian kernel: [ 4149.530020] BUG: unable to handle kernel
NULL pointer dereference at 0018
Oct 24 11:41:24 debian kernel: [ 4149.530406] IP: []
sysfs_find_dirent+0x4/0x23
Oct 24 11:41:24 debian kernel: [ 4149.530767] *pde = 
Oct 24 11:41:24 debian kernel: [ 4149.531120] Oops:  [#1] SMP
Oct 24 11:41:24 debian kernel: [ 4149.531473] last sysfs file:
/sys/devices/platform/w83627hf.656/temp3_max
Oct 24 11:41:24 debian kernel: [ 4149.531824] Modules linked in:
iptable_filter ipt_ULOG uinput ip_tables x_tables ide_cd_mod ide_core loop
w83627hf hwmon_vid eeprom nvidia(P) nouveau snd_via82xx gameport snd_ca0106
ttm snd_ac97_codec snd_pcm_oss ac97_bus snd_mpu401_uart drm_kms_helper
snd_mixer_oss drm i2c_algo_bit i2c_viapro snd_pcm snd_seq_midi snd_rawmidi
snd_seq_midi_event snd_seq snd_timer snd_seq_device snd i2c_core pcspkr
soundcore button processor hid_a4tech faketty parport_pc evdev parport
shpchp snd_page_alloc pci_hotplug ext2 mbcache raid10 raid456
async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx
raid1 raid0 multipath linear md_mod ums_cypress usb_storage usbhid hid sg
sr_mod cdrom sd_mod crc_t10dif ata_generic sata_via fan uhci_hcd pata_via
thermal via_rhine floppy thermal_sys ehci_hcd libata usbcore nls_base mii
scsi_mod [last unloaded: fuse]
Oct 24 11:41:24 debian kernel: [ 4149.532011]
Oct 24 11:41:24 debian kernel: [ 4149.532011] Pid: 1946, comm: acpi_fakekeyd
Tainted: P   (2.6.32-5-686 #1) KT880-8237
Oct 24 11:41:24 debian kernel: [ 4149.532011] EIP: 0060:[] EFLAGS:
00010286 CPU: 0
Oct 24 11:41:24 debian kernel: [ 4149.532011] EIP is at
sysfs_find_dirent+0x4/0x23
Oct 24 11:41:24 debian kernel: [ 4149.532011] EAX:  EBX: 
ECX: c11365be EDX: c1318380
Oct 24 11:41:24 debian kernel: [ 4149.532011] ESI: c1318380 EDI: c13a7638
EBP: f66957a4 ESP: f67c9d80
Oct 24 11:41:24 debian kernel: [ 4149.532011]  DS: 007b ES: 007b FS: 00d8
GS: 00e0 SS: 0068
Oct 24 11:41:24 debian kernel: [ 4149.532011] Process acpi_fakekeyd (pid:
1946, ti=f67c8000 task=f6f74440 task.ti=f67c8000)
Oct 24 11:41:24 debian kernel: [ 4149.532011] Stack:
Oct 24 11:41:24 debian kernel: [ 4149.532011]   c1318380 c10f2efa
c13a7624  c10f43cc c13a7624 f669579c
Oct 24 11:41:24 debian kernel: [ 4149.532011] <0> f66957a4 c13a7604 c11b08c7
c13a75a0 f669579c f6c47888  f62a1800
Oct 24 11:41:24 debian kernel: [ 4149.532011] <0> c11b09f5 f669579c 0010
f6695000 c11b0a5c f6f87600 f826c0b8 
Oct 24 11:41:24 debian kernel: [ 4149.532011] Call Trace:
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
sysfs_get_dirent+0x19/0x2f
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
sysfs_remove_group+0x18/0x9c
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
device_remove_attrs+0x4f/0x8a
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
device_del+0xf3/0x152
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
device_unregister+0x8/0x10
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
uinput_destroy_device+0x5f/0x83 [uinput]
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
uinput_release+0xb/0x16 [uinput]
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
__fput+0xd5/0x170
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
filp_close+0x4e/0x54
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
put_files_struct+0x60/0xa6
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
do_exit+0x1d4/0x5c6
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
do_group_exit+0x5f/0x82
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
get_signal_to_deliver+0x30d/0x32e
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
kunmap_atomic+0x51/0x6d
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
do_notify_resume+0x6f/0x713
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
fd_install+0x1e/0x3c
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
sys_select+0x81/0x8f
Oct 24 11:41:24 debian kernel: [ 4149.532011]  [] ?
work_notifysig+0x13/0x1b
Oct 24 11:41:24 debian kernel: [ 4149.532011] Code: 00 00 eb dc 85 c0 53 89
c3 74 18 8b 00 85 c0 75 0f ba 8b 00 00 00 b8 3c 07 30 c1 e8 05 d5 f3 ff 3e
ff 03 89 d8 5b c3 56 89 d6 53 <8b> 58 18 eb 11 8b 43 10 89 f2 e8 39 7c 04 00
85 c0 74 07 8b 5b
Oct 24 11:41:24 debian kernel: [ 4149.532011] EIP: []
sysfs_find_dirent+0x4/0x23 SS:ESP 0068:f67c9d80
Oct 24 11:41:24 debian kernel: [ 4149.532011] CR2: 0018
Oct 24 11:41:24 debian kernel: [ 4149.553797] ---[ end trace
41fdc93bc4003e82 ]---
Oct 24 11:41:24 debian kernel: [ 4149.554229] Fixing recursive fault but
reboot is needed!
Oct 24 11:41:24 debian acpid: exiting

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')

Bug#598116: wmtemp: Use acpi when lm-sensors finds no chip

[hugo vanwoerkom]

Package: wmtemp
Version: 0.0.6-3
Severity: wishlist

On my (most?) laptop(s) wmtemp won't work because lm-sensors finds no chip.
But the acpi thermal zone
has temps and trip points for alarms. It would be nice for wmtemp to use
these as alternative to
lm-sensors. I made the modifications and attach the patch file.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages wmtemp depends on:
ii  libc6 2.11.2-1   Embedded GNU C Library: Shared
lib
ii  libsensors3   1:2.10.8-2 library to read
temperature/voltag
ii  libx11-6  2:1.3.3-3  X11 client-side library
ii  libxext6  2:1.1.1-3  X11 miscellaneous extension
librar
ii  libxpm4   1:3.5.8-1  X11 pixmap library
ii  lm-sensors1:3.1.2-6  utilities to read
temperature/volt

wmtemp recommends no packages.

wmtemp suggests no packages.

-- no debconf information
diff -Naur wmtemp.orig//main.c wmtemp.new//main.c
--- wmtemp.orig//main.c	2008-04-28 04:18:38.0 -0500
+++ wmtemp.new//main.c	2010-09-26 08:51:24.0 -0500
@@ -23,6 +23,8 @@
  *along with this program; if not, write to the Free Software
  *Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
  *
+	09/25/2010 HVW Modified to use acpi if no lm-sensors chip found
+
  */
 
 #include 
@@ -66,11 +68,14 @@
 static void parse_arguments(int argc, char **argv);
 static void print_help(char *prog);
 
+int use_acpi;
+
 int main(int argc, char **argv)
 {
XEvent event;
XpmColorSymbol colors[2] = { {"Back0", NULL, 0}, {"Back1", NULL, 0} };
int ncolor = 0;
+use_acpi = 0;
 
/* Parse CommandLine */
parse_arguments(argc, argv);
@@ -92,8 +97,12 @@
 	   backlight_off_xpm = celcius_off_xpm;
}

-   /* Initialize Application */
-   temp_init(configfile);
+/* Initialize Application */
+temp_init(configfile);
+
+if ( use_acpi == 1 )
+	get_acpi_trip_points(&alarm_cpu, &alarm_sys);
+
dockapp_open_window(display_name, PACKAGE, SIZE, SIZE, argc, argv);
dockapp_set_eventmask(ButtonPressMask);
 
@@ -234,9 +243,10 @@
}
 
/* redraw digit */
-   temp_getusage(&cpu_temp, &sys_temp);
-   draw_cpudigit(cpu_temp);
-   draw_sysdigit(sys_temp);
+//   temp_getusage(&cpu_temp, &sys_temp);
+get_acpi_trip_points(&cpu_temp, &sys_temp);
+draw_cpudigit(cpu_temp);
+draw_sysdigit(sys_temp);
 
/* show */
dockapp_copy2window(pixmap);
diff -Naur wmtemp.orig//temp.c wmtemp.new//temp.c
--- wmtemp.orig//temp.c	2004-03-09 03:31:30.0 -0600
+++ wmtemp.new//temp.c	2010-09-25 16:24:55.0 -0500
@@ -2,11 +2,13 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 
 #include "temp.h"
 
 static FILE *f = NULL;
+static FILE *acpi = NULL;
 static char sensors = 0;
 
 static const sensors_chip_name *chip_name = NULL;
@@ -14,6 +16,10 @@
 
 char *cpu_feature_name = "temp1";
 char *sys_feature_name = "temp2";
+char *acpi_sys_temperature = "/proc/acpi/thermal_zone/TZS1/temperature";
+char *acpi_sys_trip_pts= "/proc/acpi/thermal_zone/TZS1/trip_points";
+char *acpi_cpu_temperature = "/proc/acpi/thermal_zone/TZS0/temperature";
+char *acpi_cpu_trip_pts= "/proc/acpi/thermal_zone/TZS0/trip_points";
 
 temperature_t t_type = CELCIUS;
 
@@ -38,14 +44,25 @@
 
 	f = fopen(filename, "r");
 	if (f == NULL) {
-		fprintf(stderr, "could not open configfile %s: %s\n", filename,
-strerror(errno));
+	if ( try_acpid() == 1 ) {
+//		fprintf(stderr, "could not open configfile %s: %s, but acpi is active\n", filename,strerror(errno));
+		use_acpi = 1;
+	}
+	else {
+		fprintf(stderr, "could not open configfile %s: %s, and acpi is not active\n", filename,strerror(errno));
 		exit(1);
+	}
 	}
 
 	if (sensors_init(f)) {
-		fprintf(stderr, "could not initialize sensors\n");
+	if ( try_acpid() == 1 ) {
+//		fprintf(stderr, "could not initialize sensors, but acpi is active\n");
+		use_acpi = 1;
+	}
+	else {
+		fprintf(stderr, "could not initialize sensors, and acpi is not active\n");
 		exit(1);
+	}
 	}
 
 	sensors = 1;
@@ -68,14 +85,21 @@
 	}
 
 	if (chip_name == NULL) {
-		fprintf(stderr, "could not find a suitable chip\n");
+	if ( try_acpid() == 1 ) {
+//		fprintf(stderr, "could not find a suitable chip, but acpi is active\n");
+		use_acpi = 1;
+	}
+	else {
+		fprintf(stderr, "could not find a suitable chip, and acpi is not active\n");
 		exit(1);
+	}
 	}
 }
 
 void temp_getusage(unsigned int *cpu_temp, unsigned int *sys_temp) {
 	double cpu, sys;
 
+if ( use_acpi == 0 ) {
 	sensors_get_feature(*chip_name, cpu_feature, &cpu);
 	sensors_get_feature(*chip_name, sys_feature, &sys);
 
@@ -86,7 +110,140 @@
 		cpu = TO_KELVIN(cpu);
 		sys = TO_KE

Bug#532818: zsync aborts when downloading from cdimage.debian.org

[hugo vanwoerkom]

I still get the abort with the latest zsync from upstream (0.6.1) as
of today (26 Aug. 2010)
Why does cdimage.debian.org provide the zsync files if it doesn't work?
http://saimei.acc.umu.se/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/
doesn't seem to be around any longer.

Hugo Vanwoerkom



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#572964: chrony: RTC support is missing

[hugo vanwoerkom]

Sure enough, download http://download.tuxfamily.org/chrony/chrony-1.24.tar.gz
untar, do ./configure + make +make install and adjust the place of
chrony.conf and that of the daemon and RTC support is back again.
But I'd like to know why it was taken out.

Hugo Vanwoerkom



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#505977:

[hugo vanwoerkom]

Sorry, I apologize, hit the send button too fast,  disregard the
previous message.

Hugo Vanwoerkom

-- 
zwei Seelen, eine Gedanke
http://counter.li.org/
http://www.google.com/chrome



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#572964: chrony: RTC support is missing

[hugo vanwoerkom]

I also ran into this when I updated from 1.23-6 to 1.23-7, but if it
is missing RTC support, how come there is nothing in the changelog?
I presumed that it had to do with my kernel configuration. (But what?)

Hugo Vanwoerkom
-- 
zwei Seelen, eine Gedanke
http://counter.li.org/
http://www.google.com/chrome



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#505977: chrony: RTC support is missing

[hugo vanwoerkom]

I also ran into this when I updated from 1.23-6 to 1.23-7, but if it
is missing RTC support, how come there is nothing in the changelog?
I presumed that it had to do with my kernel configuration. (But what?)

Hugo Vanwoerkom

-- 
zwei Seelen, eine Gedanke
http://counter.li.org/
http://www.google.com/chrome



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#580488: dpkg: duplicated Provides: field on packages (already installed) fail to be removed

[hugo vanwoerkom]

Spoke too soon again ;-)

dpkg-repack 1.30 indeed puts a second 'Architecture' field in control.
Or it always was there, I never checked.
So eliminate the second field:

*  HOWTO eliminate the duplicate Architecture field:
* Create a package directory (say /mc_4.6.2-2)
* /Wed May 26-11:46:27SDB6# dpkg-deb -x
mc_4.6.2~git20080311-4_i386.deb /mc_4.6.2-2
* /Wed May 26-11:47:35SDB6# dpkg-deb -e
mc_4.6.2~git20080311-4_i386.deb /mc_4.6.2-2
* Move the files from the latter into a dir named ‘DEBIAN’
* Edit the control file in DEBIAN and delete the second Architecture field.
* /Wed May 26-11:50:15SDB6# dpkg-deb -b /mc_4.6.2-2
* This will create mc_4.6.2-2.deb
* dpkg -i mc_4.6.2-2.deb

This maybe common knowledge to all, but this is the first time I've run into it.

I create a Debian mirror of all the packages I install with
dpkg-repack and reprepro. Then I start a new installation from a
script with the sources file pointing to that mirror.

But every single one of the packages in the mirror have duplicate
Architecture fields.

Regards,

Hugo Vanwoerkom


-- 
zwei Seelen, eine Gedanke
http://counter.li.org/
http://www.google.com/chrome



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#580488: dpkg: duplicated Provides: field on packages (already installed) fail to be removed

[hugo vanwoerkom]

Hi,

I just did an upgrade to dpkg 1.15.7.2 and I get this error on trying
to install a package that was created with dpkg-repack 1.30 on another
partition.

The error says:

/Wed May 26-09:22:20SDB6# dpkg -i mc_4.6.2~git20080311-4_i386.deb
dpkg: error processing mc_4.6.2~git20080311-4_i386.deb (--install):
 parse error, in file '/var/lib/dpkg/tmp.ci/control' near line 25 package 'mc':
 duplicate value for `Architecture' field
Errors were encountered while processing:
 mc_4.6.2~git20080311-4_i386.deb

This error does not occur with dpkg 1.15.5.4 on that other partition.

How do I get around this?

Regards,

Hugo Vanwoerkom



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567700: xserver-xorg: System freezes after X starts

[hugo vanwoerkom]

I cannot reproduce this error when I upgraded to the following:

# xorg 1:7.5+5
# xserver-xorg 1:7.5+5
# xserver-xorg-core 2:1.7.6-1
# xserver-common 2:1.7.6-1
# xserver-xorg-input-all 1:7.5+5
# xserver-xorg-input-evdev 1:2.3.2-4
# xserver-xorg-input-kbd 1:1.4.0-1
# NVIDIA-Linux-x86-195.36.15-pkg1.run

I thought I tried the latest nvidia driver instead of the legacy one.
But I don't find anything about it in my notes.

Hugo Vanwoerkom



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567700: xserver-xorg: System freezes after X starts

[hugo vanwoerkom]

Today I tried X on a brandnew installation, with only enough installed
to bring up X, gdm, window-manager and iceweasel.

The same thing happens, after 7 mins.: *the system freezes*.

2 users were logged on, one in iceweasel, the other just logged on and
switched to VT1

VT1 gets spots on the screen and the system is frozen because all
clocks and timer ticks have stopped.

I used the Debian netinstall CD  from March 1st of this year to
install the basic system.
Then I upgraded to current Sid.
Then I installed the following software:

x-window-system-core,xterm,menu,patch,gcc,g++,make,gv,gpm,file,bzip2,linux-image-2.6-686,
linux-headers-2.6-686,grub-legacy,libsensors-dev,lm-sensors,
fvwm,gdm,sudo,libaudio2,libaudio-dev,nas,qt3-dev-tools,libqt3-mt-dev,ddclient,
mkisofs,cdrecord,eject,gawk,chrony,gcal,wmcpuload,wmmoonclock,wmppp.app,expect,
xsane,buffer,mindi,lzop,dvd+rw-tools,mondo,smartmontools,xbindkeys,
xmacro,firehol,ulogd,attr,acl,mtools,lsof,htop,apcupsd,rsync,gdm-themes,libqt4-qt3support,
libqt4-dev,console-setup,xserver-xorg-input-kbd

Hugo Vanwoerkom



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#574762: partimage: segfault restoring image

[hugo vanwoerkom]

Package: partimage
Version: 0.6.8-1
Severity: normal

Selecting to restore a partition from an image file created March 3rd
2010 partimage segfaults.
It does so trying to tell me that the restore partition is too small
for the image file,
but the error message is cut off and doesn' t give details.

cfdisk shows the original partition and the restore partition both to
be 8003.20MB
Partimage itself shows both to be 7.45GB.

However 'df' shows the saved partition to be 7692908 1K-blocks while
the restore partition is 7692876 1K-blocks. Indeed too small by 32
1K-blocks.

Segfaulting also occurs using the batch option, without error messages.

Hugo Vanwoerkom


-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages partimage depends on:
ii  libbz2-1.0 1.0.5-1   high-quality block-sorting file co
ii  libc6  2.10.2-2  GNU C Library: Shared libraries
ii  libgcc11:4.3.3-3 GCC support library
ii  libnewt0.520.52.2-11.3   Not Erik's Windowing Toolkit - tex
ii  libpam0g   1.1.0-4   Pluggable Authentication Modules l
ii  libslang2  2.1.3-3   The S-Lang programming library - r
ii  libssl0.9.80.9.8g-15 SSL shared libraries
ii  libstdc++6 4.3.3-3   The GNU Standard C++ Library v3
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

partimage recommends no packages.

partimage 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#567700: xserver-xorg: System freezes after X starts

[hugo vanwoerkom]

Also happens with xserver-xorg 1:7.5+4

Hugo Vanwoerkom



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567700: xserver-xorg: System freezes after X starts

[hugo vanwoerkom]

Also happens with xserver-xorg 1:7.5+3.

Hugo Vanwoerkom

Bug#534324: linux-image-2.6.30-1-686: USB disk fails to show up at initramfs

[hugo vanwoerkom]

I include the dmesg from the initramfs shell of 2.6.32-trunk-686,named
initramfs.deb.dmesg, and the one from my own kernel named initramfs.dmesg
from kernel 2.6.32.2-hvw.

I also include the /proc/modules from the initramfs shell of the 2 different
kernels, named initramfs.deb.mods and initramfs.mods.

Hugo Vanwoerkom


initramfs.deb.dmesg
Description: Binary data


initramfs.dmesg
Description: Binary data


initramfs.deb.mods
Description: Binary data


initramfs.mods
Description: Binary data

Bug#542443: util-linux: hwclock w/o --directisa fails

[hugo vanwoerkom]

Package: util-linux
Version: 2.16-3
Severity: normal

The hwclock command fails on my system w/o the --directisa option. What it
produces is:

hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
Cannot access the Hardware Clock via any known method.
hwclock from util-linux-ng 2.16
No usable clock interface found.

As a result the clock cannot be set nor saved. And since I use localtime,
not UTC, the system thinks the localtime is UTC time and the true localtime
5 hours earlier. When you boot with that fsck fails on all fs because the
superblock time is five hours in the future.

Severity is the highest really because you don't have a system anymore,
But with 439 bugs in package util-linux, who wants to quibble.

To fix it I ran dpkg -i util-linux_2.13.1.1-1_i386.deb and that replaced
hwclock with a version that does not need the --directisa option. Except
that it changed more things than hwclock. But produced a running system
again.

Hugo Vanwoerkom

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30.4-hvw (PREEMPT)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages util-linux depends on:
ii  libc6  2.9-24GNU C Library: Shared libraries
ii  libncurses55.7+20090803-1+b1 shared libraries for terminal
hand
ii  libselinux12.0.82-1  SELinux shared libraries
ii  libslang2  2.1.4-3   The S-Lang programming library
- r
ii  libuuid1   2.16-3Universally Unique ID library
ii  lsb-base   3.2-23Linux Standard Base 3.2 init
scrip
ii  tzdata 2009k-3   time zone and daylight-saving
time
ii  zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  console-tools1:0.2.3dbs-65.1 Linux console and font
utilities
ii  dosfstools   3.0.5-1 utilities for making and
checking
pn  util-linux-locales (no description available)

-- no debconf information

Bug#525736: console-setup: kbd actions on seat2 show up on console of seat1

[hugo vanwoerkom]

Aivils Stoss has a work-around for this problem: install faketty and use its
VT's on seat 2:
http://en.wikibooks.org/wiki/Multiseat_Configuration/faketty

Except the version attached of faketty has to be used.


   1. compile and install faketty
   2. install xserver-xorg-input-kbd
   3. modify xorg.conf for seat2 to use driver=kbd
   4. modify gdm.conf for seat 2 to say: command=/usr/bin/X0 :1 -layout X0
   -dpi 110 -isolateDevice PCI:0:8:0 vt51

Note the 'vt51' in step 4.

Result: problem goes away. Thanks Aivils!


faketty-2.6.29.tar.bz2
Description: BZip2 compressed data

Bug#505977: v86d: segfault

[hugo vanwoerkom]

On Sat, Jun 6, 2009 at 5:45 AM, Evgeni Golov  wrote:

> Hi Hugo,
>
> this bug is quite old, and many things happened since you reported it
> (esp the kernel, Xorg etc). Thus I wanted to hear from you, if you
> still can reproduce it with latest kernel (2.6.29 or 2.6.30-rcX),
> uptodate Xorg from Sid and the appropriate drivers for your GeForce
> (nv, nouveau, nvidia).
>
> Regards
> Evgen


Evgeni,

Since my discovery of edd=off as kernel parm to get framebuffer support
again I am using the Debian Sid kernels again. They don't use v86d.
I will try 2.6.29 and see what I get with v86d.
Regards

Hugo

Bug#525736: console-setup: kbd actions on seat2 show up on console of seat1

[hugo vanwoerkom]

On Tue, Apr 28, 2009 at 4:50 AM, Julien Cristau  wrote:

> On Mon, Apr 27, 2009 at 17:27:59 -0500, hugo vanwoerkom wrote:
>
> > Since all the multiseat is in xorg.conf and gdm.conf where does it say
> what
> > *is* and *is not* supported by Debian regarding those configuration
> files;
> > and for the last 5 years it has worked flawlessly.
> >
> Disable AutoAddDevices in xorg.conf, and things should work as before.
> See xserver-xorg's NEWS.Debian file for some information on the recent
> changes.
>
> Cheers,
> Julien
>

Not true. If you examine the xorg.conf that I attached, it has this at the
beginning:

Section "ServerFlags"
Option  "AutoAddDevices""false"
Option  "AllowEmptyInput"   "false"
EndSection

Does *not* solve the problem.

Hugo

Bug#525736: console-setup: kbd actions on seat2 show up on console of seat1

[hugo vanwoerkom]

On Mon, Apr 27, 2009 at 2:11 PM, Samuel Thibault <
samuel.thiba...@ens-lyon.org> wrote:

> hugo vanwoerkom, le Mon 27 Apr 2009 10:27:29 -0500, a écrit :
> > Meaning the bug belongs to the hal package?
>
> Meaning the way multiseat works has changed.
>
> > Because at the very least it is a security exposure because passwords
> > are broadcast.
>
> I'm not sure multiseat is really "supported" by Debian.
>
> Samuel
>

Since all the multiseat is in xorg.conf and gdm.conf where does it say what
*is* and *is not* supported by Debian regarding those configuration files;
and for the last 5 years it has worked flawlessly.

Hugo

Bug#525736: console-setup: kbd actions on seat2 show up on console of seat1

[hugo vanwoerkom]

Hi,

Meaning the bug belongs to the hal package? Because at the very least it is
a security exposure because passwords are broadcast.

Hugo


On Mon, Apr 27, 2009 at 9:54 AM, Samuel Thibault <
samuel.thiba...@ens-lyon.org> wrote:

> Hello,
>
> This is not handled by console-setup, it should probably now be setup in
> hal.
>
> Samuel
>

Bug#525736: console-setup: kbd actions on seat2 show up on console of seat1

[hugo vanwoerkom]

Package: console-setup
Version: 1.32
Severity: normal

On a two-seat Debian Sid system (2 monitors/graphic
cards/xservers/keyboards/mice) after installing the latest xserver-xorg,
when keyboard data is typed on seat-2 it appears on the active VT on seat-1.
Including passwords, etc. It makes the console on seat-1 near unusable.


-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.29-1-686 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages console-setup depends on:
ii  console-terminus  4.26-2.1   Fixed-width fonts for fast
reading
ii  debconf [debconf-2.0] 1.5.24 Debian configuration management
sy
ii  xkb-data  1.5-2  X Keyboard Extension (XKB)
configu

Versions of packages console-setup recommends:
ii  console-tools1:0.2.3dbs-65.1 Linux console and font
utilities

Versions of packages console-setup suggests:
ii  locales   2.7-18 GNU C Library: National
Language (
ii  lsb-base  3.2-20 Linux Standard Base 3.2 init
scrip

-- debconf information:
* console-setup/variant: USA - International (with dead keys)
  console-setup/unsupported_options: true
* console-setup/fontsize-text: 20x10
* console-setup/compose: Right Alt
  console-setup/modelcode: pc101
  console-setup/switch: No temporary switch
  console-setup/unsupported_config_layout: true
  console-setup/fontsize: 16
  console-setup/unsupported_layout: true
* console-setup/charmap: ISO-8859-15
  console-setup/layoutcode: us
  console-setup/optionscode: lv3:ralt_switch
  debian-installer/console-setup/title:
  console-setup/unsupported_config_options: true
* console-setup/layout: USA
  console-setup/variantcode: intl
  console-setup/codesetcode: Lat15
* console-setup/altgr: Right Alt
* console-setup/ttys: /dev/tty[1-6]
* console-setup/model: Generic 101-key PC
* console-setup/fontsize-fb: 16
* console-setup/codeset: # Latin1 and Latin5 - western Europe and Turkic
languages
  console-setup/toggle: No toggling
* console-setup/fontface: TerminusBold


-- 
zwei Seelen, eine Gedanke

Bug#518161: booting DVD finds no disks

[hugo vanwoerkom]

This is solved by mondo 2.2.8 + mindi  2.0.5 that are available upstream as
.deb's.

One proviso: /usr/sbin/mindi must be changed at line #53 and 'ide-gd_mod'
added! (Watch the spelling). If you don't do this then no IDE disks will be
found.

The nice boxes of ncurses are messed up.

I'll close the bug.

Hugo Vanwoerkom

Bug#518161: booting DVD finds no disks

[hugo vanwoerkom]

Tried to use failsafe:

mondoarchive -O -r -d /dev/hdd -0 -S /hda10/ -T /hda10/ -E "/sdb1 /hda10
/home /usr/local /sys/devices/pci:0
0 /var/cache/apt/archives" -s 4380m -l GRUB -f /dev/hda -g -k FAILSAFE

But booting that DVD is a mess, he can't find anything, no cdrom, no disks.

I used Q4/ How do I create my mindi Failsafe kernel? in
http://www.mondorescue.org/docs.shtml to create a failsafe kernel (the last
one that booted successfully) but that is not the one he uses as the
attached log shows.

He used linux-image-2.6.26-1-486, and I am guessing that's the first kernel
in /boot:

-rw-r--r-- 1 root root 1468016 Jan 10 16:56 vmlinuz-2.6.26-1-486
-rw-r--r-- 1 root root 1505936 Jan 10 16:58 vmlinuz-2.6.26-1-686
-rw-r--r-- 1 root root 1684496 Mar  2 07:06 vmlinuz-2.6.28-1-686

How do you create your own failsafe kernel? I posted this question to the
list also.


mondoarchive.1.log.gz
Description: GNU Zip compressed data

Bug#517934: Hyperlatex ERROR: Unknown command: HlxModeLevelUp

[hugo vanwoerkom]

Package: hyperlatex
Version: 2.9a-3
Severity: normal

Hyperlatex fails with:
Hyperlatex ERROR: Unknown command: HlxModeLevelUp
when doing tables.

This error occurs with emacs, emacs22, emacs22-bin-common, emacs22-common at
level 22.2+2-5, *not* the versions seen below.
I backleveled those packages and the error disappeared.

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.28-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages hyperlatex depends on:
ii  emacs [emacsen]22.2+2-3  The GNU Emacs editor
(metapackage)
ii  emacs22 [emacsen]  22.2+2-2  The GNU Emacs editor
ii  ghostscript-x [gs] 8.63.dfsg.1-2 The GPL Ghostscript
PostScript/PDF
ii  netpbm 2:10.0-12 Graphics conversion tools

Versions of packages hyperlatex recommends:
ii  tetex-bin  2007.dfsg.1-5 TeX Live: teTeX transitional
packa

hyperlatex suggests no packages.

-- no debconf information

Bug#507676: initramfs-tools: does not wait for usb disks in fstab to show up

[hugo vanwoerkom]

Even fixing the error of
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507059
and installing the latest udev with udevadm: same result: no wait!

Bug#507676: initramfs-tools: does not wait for usb disks in fstab to show up

[hugo vanwoerkom]

On Wed, Dec 3, 2008 at 5:18 PM, Cesare Leonardi <[EMAIL PROTECTED]> wrote:

> hugo vanwoerkom wrote:
>
>> Booting linux-image-2.6.26-1-686 initramfs does not wait for the 2 USB
>> disks that are in /etc/fstab to show up, causing the
>> boot to fail.
>>
>
> From what i've heard from previous posts, you can try with the
> "rootdelay=n" kernel boot parameter, where n is the number of seconds to
> wait.
>
> Good luck.
>
> Cesare.
>

But it isn't the root that needs delayed, the 2 USB disks that don't have
root on them but other partitions need to be delayed.

Hugo

Bug#507676: initramfs-tools: does not wait for usb disks in

[hugo vanwoerkom]

On Wed, Dec 3, 2008 at 10:30 AM, Bernhard Kleine <[EMAIL PROTECTED]>wrote:

> Am Wed, 03 Dec 2008 16:30:30 +0100 schrieb hugo vanwoerkom:
>
> > Package: initramfs-tools
> > Version: 0.92l
> > Severity: normal
> >
> > Booting linux-image-2.6.26-1-686 initramfs does not wait for the 2 USB
> > disks that are in /etc/fstab to show up, causing the boot to fail.
>
> I had a similar problem 2 days ago, one usb partition as /dev/sda1, boot
> stopped with an error, I do not remember but related to a missing device.
> Rebooting solved the problem.
>
> Bernhard
>

My solution is to insert:

echo -e "\033[1;33;40mSelf-imposed wait of
10s...(12/02/08)\033[0;37;40m"
/bin/sleep 10.0

just ahead of

wait_for_udev 10

in /usr/share/initramfs-tools/scripts/local function mountroot (). But I
don't think I should have to do that.

Hugo

Bug#507676: initramfs-tools: does not wait for usb disks in fstab to show up

[hugo vanwoerkom]

Package: initramfs-tools
Version: 0.92l
Severity: normal

Booting linux-image-2.6.26-1-686 initramfs does not wait for the 2 USB disks
that are in /etc/fstab to show up, causing the
boot to fail.
This is the relevant section of /etc/fstab:
...
# 80GB PATA Seagate disk USB
LABEL=ST380211.01   /sda1   ext2
defaults,user,noauto,errors=remount-ro  0   1
LABEL=ST380211.02   /sda2   ext2
defaults,user,noauto,errors=remount-ro  0   1
LABEL=ST380211.03   /sda3   ext2
defaults,user,noauto,errors=remount-ro  0   1
LABEL=ST380211.05   /sda5   ext2
defaults,user,noauto,errors=remount-ro  0   1
LABEL=ST380211.06   /sda6   ext2
defaults,user,noauto,errors=remount-ro  0   1
LABEL=ST380211.07   /sda7   ext2
defaults,user,noauto,errors=remount-ro  0   1
##LABEL=ST380211.07 /sda7   ext2
auto,user,exec  0   0

# 80GB SATA Western Digital disk USB
LABEL=wd80_0jd-60.03/sdb3   ext2
defaults,user,noauto,errors=remount-ro  0   1
LABEL=wd80_0jd-60.05/sdb5   ext2
defaults,user,noauto,errors=remount-ro  0   1
LABEL=wd80_0jd-60.06/sdb6   ext2
defaults,user,noauto,errors=remount-ro  0   1
...

-- Package-specific info:
-- /proc/cmdline
root=LABEL=ST380011A.05 noapic apm=on vga=791 edd=off ddcon-1 network quiet

-- /proc/filesystems
ext2

-- lsmod
Module  Size  Used by
ppp_deflate 4224  1
zlib_deflate   17624  1 ppp_deflate
zlib_inflate   14144  1 ppp_deflate
bsd_comp4864  0
ppp_async   7488  1
crc_ccitt   2080  1 ppp_async
vmnet  29160  12
vmmon  98924  0
nvidia   4701104  52
ipt_ULOG6820  1
ppdev   6468  0
lp  8164  0
wmi 6440  0
video  16432  0
output  2912  1 video
sbs2  0
sbshc   5184  1 sbs
battery10180  0
container   3456  0
ac  4196  0
usbhid 35904  1
evdev   8000  4
xt_tcpudp   2816  40
ipt_LOG 5028  12
xt_limit2180  14
xt_state2016  41
iptable_filter  2624  1
iptable_nat 4680  0
nf_nat 15576  1 iptable_nat
nf_conntrack_ipv4  12268  44 iptable_nat,nf_nat
nf_conntrack   55508  4
xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4
iptable_mangle  2688  0
ipv6  235300  26
ppp_generic20028  7 ppp_deflate,bsd_comp,ppp_async
slhc5408  1 ppp_generic
dm_snapshot14340  0
dm_mirror  15104  0
dm_log  8452  1 dm_mirror
dm_mod 46184  3 dm_snapshot,dm_mirror,dm_log
ip_tables  10160  3 iptable_filter,iptable_nat,iptable_mangle
x_tables   13284  7
ipt_ULOG,xt_tcpudp,ipt_LOG,xt_limit,xt_state,iptable_nat,ip_tables
loop   12748  0
w83627hf   20984  0
hwmon_vid   2720  1 w83627hf
eeprom  5232  0
sg 26964  0
parport_pc 22500  1
parport30988  3 ppdev,lp,parport_pc
snd_ca0106 27584  0
snd_pcm_oss32800  0
snd_mixer_oss  12320  3 snd_pcm_oss
snd_pcsp8576  1
i2c_viapro  6836  0
i2c_core   19828  3 nvidia,eeprom,i2c_viapro
snd_via82xx20664  1
gameport   10700  1 snd_via82xx
snd_ac97_codec 88484  2 snd_ca0106,snd_via82xx
snd_pcm62596  5
snd_ca0106,snd_pcm_oss,snd_pcsp,snd_via82xx,snd_ac97_codec
snd_mpu401_uart 6368  1 snd_via82xx
snd_rawmidi18496  2 snd_ca0106,snd_mpu401_uart
snd_seq_dummy   2660  0
snd_seq_oss24992  0
button  6096  0
snd_seq_midi_event  6432  1 snd_seq_oss
snd_seq41456  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_timer  17800  2 snd_pcm,snd_seq
snd_seq_device  6380  4
snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd45604  13
snd_ca0106,snd_pcm_oss,snd_mixer_oss,snd_pcsp,snd_via82xx,snd_ac97_codec,snd_pc
m,snd_mpu401_uart,snd_rawmidi,snd_seq_oss,snd_seq,snd_timer,snd_seq_device
soundcore   6368  3 snd
ac97_bus1728  1 snd_ac97_codec
snd_page_alloc  7816  3 snd_ca0106,snd_via82xx,snd_pcm
shpchp 25528  0
pci_hotplug23460  1 shpchp
via_agp 7744  1
agpgart28776  2 nvidia,via_agp
ext2   54440  2
mbcache 7108  1 ext2
sd_mod 22200  0
usb_storage75936  0
hid33184  1 usbhid
ff_memless  4392  1 usbhid
ide_cd_mod 27652  0
cdrom 

Bug#481063: linux-image-2.6.25-1-686: vga=791 gets 'undefined video mode number'

[hugo vanwoerkom]

I figured it out:
linux-image-2.6.26-1-686 has "CONFIG_EDD=m" set and I don't set that in my
kernel.

Hugo

Bug#481063: linux-image-2.6.25-1-686: vga=791 gets 'undefined video mode number'

[hugo vanwoerkom]

Indeed 'edd=off' fixes the problem. I wished I had checked back earlier,
wasted another month with uvesafb.
I still wonder why I don't have to say 'edd=off' with my own rolled kernel
to get vga-791 to work.
I'll close bug 481063.
Thanks for that solution!

Hugo

Bug#505977: v86d: segfault

[hugo vanwoerkom]

Hi Evgeni,

I can now cause the problem at will by issuing:

startx -- :1 -layout X0 -dpi 110 -deferglyphs 16 -isolateDevice PCI:0:8:0
-sharevts

and I get:

Nov 21 05:24:09 debian kernel: [  391.380003] uvesafb: mode switch failed
(eax=0x14f, err=0). Trying again with
default timings.
Nov 21 05:24:09 debian kernel: [  391.380003] uvesafb: mode switch failed
(eax=0x14f, err=0)
Nov 21 05:24:10 debian kernel: [  392.124005] uvesafb: mode switch failed
(eax=0x14f, err=0). Trying again with
default timings.
Nov 21 05:24:10 debian kernel: [  392.124005] uvesafb: mode switch failed
(eax=0x14f, err=0)
Nov 21 05:24:37 debian kernel: [  418.725455] uvesafb: mode switch failed
(eax=0x14f, err=0). Trying again with
default timings.
Nov 21 05:24:37 debian kernel: [  418.726021] uvesafb: mode switch failed
(eax=0x14f, err=0)

I attach the applicable xorg.conf

Regards,

Hugo


xorg.conf.nv
Description: Binary data

Bug#505977: v86d: segfault

[hugo vanwoerkom]

Hi Evgeni,

I don't remember if I told you why I use uvesafb: it's because since
linux-image-2.6.25-1-686 I cannot use 'vga=791':
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481063

But I *can* when I roll my own kernel with  the same version from kernel.org
.
It's something that is happening in the Debian kernel.

Don't know if it is related.

Regards,

Hugo

Bug#505977: v86d: segfault

[hugo vanwoerkom]

On Tue, Nov 18, 2008 at 10:11 AM, Evgeni Golov <[EMAIL PROTECTED]>wrote:

> Hi Hugo,
>
> Never seen that on my systems.
> Can you try 0.1.9 from
> http://die-welt.net/~evgeni/v86d/v86d_0.1.9-0_i386.deb?
> It's unpatched and compiled with x86emu, so you shouldn't need any
> changes.
>
> Regards
> Evgeni


Hi Evgeni,

Thanks for the quick response. This occurred several times on Oct. 3 2008,
but I did not submit a bug report. I'll try 0.1.9 and let you know, for
certain if it happens again.

Hugo

Bug#505977: v86d: segfault

[hugo vanwoerkom]

The startup messages for uvesafb were:

Nov 16 22:19:05 debian kernel: [   23.476272] uvesafb: NVIDIA Corporation,
nv44 Board - p382h1  , Chip Rev   , O
EM: NVIDIA, VBE v3.0
Nov 16 22:19:05 debian kernel: [   23.508283] uvesafb: protected mode
interface info at c000:d3a0
Nov 16 22:19:05 debian kernel: [   23.508288] uvesafb: pmi: set display
start = c00cd3d6, set palette = c00cd440
Nov 16 22:19:05 debian kernel: [   23.508291] uvesafb: pmi: ports = 3b4 3b5
3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9
3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
Nov 16 22:19:05 debian kernel: [   23.511052] uvesafb: VBIOS/hardware
doesn't support DDC transfers
Nov 16 22:19:05 debian kernel: [   23.511056] uvesafb: no monitor limits
have been set, default refresh rate wil
l be used
Nov 16 22:19:05 debian kernel: [   23.516863] uvesafb: scrolling: ypan using
protected mode interface, yres_virt
ual=6144
Nov 16 22:19:05 debian kernel: [   23.743379] Console: switching to colour
frame buffer device 128x48
Nov 16 22:19:05 debian kernel: [   23.762168] uvesafb: framebuffer at
0xc000, mapped to 0xf8b8, using 24
576k, total 262144k
Nov 16 22:19:05 debian kernel: [   23.762171] fb0: VESA VGA frame buffer
device

The only difference I see is that "no monitor limits" because I had the
monitors turned off.
I run a 2-seat system and normally gdm brings up the 2 monitors, but not
this time: it brought up only one, so I had to restart gdm.
Unfortunately I did not save the Xorg logs of that startup.


Hugo

Bug#505050: xcompmgr: many error messages in .xsession-errors

[hugo vanwoerkom]

Package: xcompmgr
Version: 1.1.4-0.1
Severity: normal

After starting 'xcompmgr -c -f' I get many error messages in
.xsession-errors like this:

...
error 182 request 157 minor 8 serial 136701
error 182 request 157 minor 8 serial 136783
error 182 request 157 minor 8 serial 136865
error 182 request 157 minor 8 serial 136947
error 182 request 157 minor 8 serial 137029
error 182 request 157 minor 8 serial 137111
error 182 request 157 minor 8 serial 137193
error 182 request 157 minor 8 serial 137275
error 182 request 157 minor 8 serial 137357
error 182 request 157 minor 8 serial 137439
error 182 request 157 minor 8 seria
...Too much output, ignoring rest...


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26.7-hvw (PREEMPT)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages xcompmgr depends on:
ii  libc6 2.7-13 GNU C Library: Shared libraries
ii  libx11-6  2:1.0.3-7  X11 client-side library
ii  libxcomposite11:0.4.0-2  X11 Composite extension library
ii  libxdamage1   1:1.1.1-4  X11 damaged region extension
libra
ii  libxfixes31:4.0.3-2  X11 miscellaneous 'fixes'
extensio
ii  libxrender1   1:0.9.4-1  X Rendering Extension client
libra

xcompmgr recommends no packages.

xcompmgr suggests no packages.

-- no debconf information

Bug#500800: xorg: -isolatedevice fails: multiseat impossible

[hugo vanwoerkom]

Julien, you're a Godsent. That's it: no quotes.
I'll close the bug.
Hugo

On Wed, Oct 1, 2008 at 10:07 AM, Julien Cristau <[EMAIL PROTECTED]> wrote:

> On Wed, Oct  1, 2008 at 09:39:21 -0500, hugo vanwoerkom wrote:
>
> > and the pieces in /etc/gdm/gdm.conf:
> >
> > [server-Standard]
> > name=Standard server
> > command=/usr/bin/X1 :0 -layout X1 -dpi 110 -deferglyphs 16 -isolateDevice
> > \"PCI:1:0:0\" vt7
> > ...
> > [server-2nd]
> > name=2nd server
> > command=/usr/bin/X0 :1 -layout X0 -dpi 110 -deferglyphs 16 -isolateDevice
> > \"PCI:0:8:0\" -sharevts
> >
> > The latter 2 commands cause the error.
> >
> What if you remove the quotes around the PCI ids?
>
> The relevant code is:
>  if (!strcmp(argv[i], "-isolateDevice"))
>  {
>int bus, device, func;
>CHECK_FOR_REQUIRED_ARGUMENT();
>if (strncmp(argv[++i], "PCI:", 4)) {
>   FatalError("Bus types other than PCI not yet isolable\n");
>}
>if (sscanf(argv[i], "PCI:%d:%d:%d", &bus, &device, &func) == 3) {
>   xf86IsolateDevice.bus = bus;
>   xf86IsolateDevice.device = device;
>   xf86IsolateDevice.func = func;
>   return 2;
>} else {
>   FatalError("Invalid isolated device specification\n");
>}
>  }
>
> Cheers,
> Julien
>



-- 
zwei Seelen, eine Gedanke

Bug#500800: xorg: -isolatedevice fails: multiseat impossible

[hugo vanwoerkom]

Package: xorg
Version: 1:7.3+10
Severity: important

the -isolatedevice option now always fails with:

Fatal server error:
Bus types other than PCI not yet isolable

No matter what BusID you specify. This means that multiseat (>1
screen/mouse/keybrd/videocard/xserver) now is impossible.

This happened a while back for the first time. In February 2008 my 2nd PCI
videocard failed so that was the end of my 2-seater.
I got the error message for the first time after a Sid dist-upgrade with
just the APG card on August 4th 2008. But at that time it did not matter.
Just now, however, I finally got additionally a GeForce 6200 PCI card and it
turns out -isolatedevice *always* gives an error.

It does not fail with xorg 1:7.2-5 with which I am running now. But that
means that only Etch still gives a functional multiseat.

The hardware looks like this:
00:08.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200]
(rev a1)
01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 4000
AGP 8x] (rev c1)

and the pieces in xorg.conf:

Identifier  "nvidia0"
BusID   "PCI:1:0:0"
...
Identifier  "nvidia1"
BusID   "PCI:0:8:0"

and the pieces in /etc/gdm/gdm.conf:

[server-Standard]
name=Standard server
command=/usr/bin/X1 :0 -layout X1 -dpi 110 -deferglyphs 16 -isolateDevice
\"PCI:1:0:0\" vt7
...
[server-2nd]
name=2nd server
command=/usr/bin/X0 :1 -layout X0 -dpi 110 -deferglyphs 16 -isolateDevice
\"PCI:0:8:0\" -sharevts

The latter 2 commands cause the error.

Thanks
Hugo Vanwooerkom

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages xorg depends on:
ii  konsole [x-terminal 4:3.5.9.dfsg.1-2+b1  X terminal emulator for KDE
ii  libgl1-mesa-glx [li 7.0.3-1  A free implementation of the
OpenG
ii  libglu1-mesa7.0.3-5  The OpenGL utility library
(GLU)
ii  x11-apps7.3+1X applications
ii  x11-session-utils   7.3+1X session utilities
ii  x11-utils   7.3+1X11 utilities
ii  x11-xfs-utils   7.3+1X font server utilities
ii  x11-xkb-utils   7.4+1X11 XKB utilities
ii  x11-xserver-utils   7.3+2X server utilities
ii  xauth   1:1.0.3-1X authentication utility
ii  xfonts-100dpi   1:1.0.0-4100 dpi fonts for X
ii  xfonts-75dpi1:1.0.0-475 dpi fonts for X
ii  xfonts-base 1:1.0.0-5standard fonts for X
ii  xfonts-scalable 1:1.0.0-6scalable fonts for X
ii  xfonts-utils1:7.4+1  X Window System font utility
progr
ii  xinit   1.0.8-1  X server initialisation tool
ii  xkb-data1.2~cvs.20080501.1-1 X Keyboard Extension (XKB)
configu
ii  xserver-xorg1:7.3+10 the X.Org X server
ii  xterm [x-terminal-e 235-1X terminal emulator

Versions of packages xorg recommends:
ii  xorg-docs 1:1.4-2Miscellaneous documentation for
th

xorg suggests no packages.

-- no debconf information

Bug#495151: linux-image-2.6.26-1-686: 'video=uvesafb:1024x768-32, mtrr:3, ypan' does nothing

[hugo vanwoerkom]

Package: linux-image-2.6.26-1-686
Version: 2.6.26-2
Severity: normal

After installing v86d on sid and installing linux-image-2.6.26-1-686 and
including
video=uvesafb:1024x768-32,mtrr:3,ypan in the kernel cmdline, reboot drops
into an 80x25 VGA screen.


-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

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.92a  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  grub  0.97-35GRand Unified Bootloader
(Legacy v
pn  linux-doc-2.6.26   (no description available)

-- debconf information:
  linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686:
  linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false
  linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686:
  linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true
  linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686:
true
  linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true
  linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686:
true
  linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false
  linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686:
  linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686:
  linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686:

Bug#481063: booting vmlinuz-2.6.25-2-686 w. vga=791 gets "undefined video mode"

[hugo vanwoerkom]

This installer has ppp but not pppconfig.

So if you are on a dialup line you are stuck, unless you know exactly what
files to add/change to dial out with ppp.

I could do it because I was on a system with lots of partitions that had
running systems, but if you use this installer on a new system, I'd say
you've got problems.

Hugo

Bug#481063: linux-image-2.6.25-1-686: vga=791 gets 'undefined video mode number'

[hugo vanwoerkom]

I get the same error with 2.6.26-1-686.

Yet no errors with the kernels from kernel.org.

So I had a thought: recompile the Debian kernel with the .config I use.
Guess what: no error.

So Maximilian was right when he pointed to the .config differences.

It's in the .config somewhere.

Hugo

Bug#493244: booting vmlinuz-2.6.25-2-686 w. vga=791 gets "undefined video mode"

[hugo vanwoerkom]

Package: installation-reports

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
Date: Fri. Aug 1 2008 6:00:00 CDT

Machine: homebuilt PC
Processor:AMD Athlon 2700+
Memory:1 GB
Partitions: /hdb5/bootFri Aug 01-09:37:45HDC3# df -Tl
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/hdc3 ext2 7692908   4683604   2618524  65% /
tmpfstmpfs  452888 0452888   0% /lib/init/rw
udev tmpfs   10240   240 1   3% /dev
tmpfstmpfs  452888 0452888   0% /dev/shm
/dev/hda10ext229362324  12654692  15216072  46% /hda10
/dev/sdb1 ext2 7692876   1635420   580  23% /sdb1
/dev/hdc5 ext2 7692876261848   7040252   4% /hdb5

Output of lspci -knn (or lspci -nn):
/hdb5/bootFri Aug 01-09:38:32HDC3# lspci -knn
00:00.0 Host bridge [0600]: VIA Technologies, Inc. KT880 Host Bridge [1106:0269]
Kernel driver in use: agpgart-via
00:00.1 Host bridge [0600]: VIA Technologies, Inc. KT880 Host Bridge [1106:1269]
00:00.2 Host bridge [0600]: VIA Technologies, Inc. KT880 Host Bridge [1106:2269]
00:00.3 Host bridge [0600]: VIA Technologies, Inc. KT880 Host Bridge [1106:3269]
00:00.4 Host bridge [0600]: VIA Technologies, Inc. KT880 Host Bridge [1106:4269]
00:00.7 Host bridge [0600]: VIA Technologies, Inc. KT880 Host Bridge [1106:7269]
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237 PCI Bridge [1106:b198]
00:0a.0 Multimedia audio controller [0401]: Creative Labs SB Audigy LS
[1102:0007]
Kernel driver in use: CA0106
Kernel modules: snd-ca0106
00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VIA VT6420 SATA
RAID Controller [1106:3149] (rev 80)
00:0f.1 IDE interface [0101]: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571]
(rev 06)
Kernel driver in use: VIA_IDE
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI
USB 1.1 Controller [1106:3038] (rev 81)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI
USB 1.1 Controller [1106:3038] (rev 81)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI
USB 1.1 Controller [1106:3038] (rev 81)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI
USB 1.1 Controller [1106:3038] (rev 81)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0
[1106:3104] (rev 86)
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237 ISA bridge
[KT600/K8T800/K8T890 South] [1106:3227]
Kernel modules: i2c-viapro
00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 60)
Kernel driver in use: VIA 82xx Audio
Kernel modules: snd-via82xx
00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102
[Rhine-II] [1106:3065] (rev 78)
Kernel driver in use: via-rhine
Kernel modules: via-rhine
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV18
[GeForce4 MX 4000] [10de:0185] (rev c1)
Kernel driver in use: nvidia
Kernel modules: nvidia

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o ]
Detect network card:[o ]
Configure network:  [o ]
Detect CD:  [o ]
Load installer modules: [o ]
Detect hard drives: [o ]
Partition hard drives:  [o ]
Install base system:[o ]
Clock/timezone setup:   [e ]
User/password setup:[o ]
Install tasks:  [o ]
Install boot loader:[o ]
Overall install:[o ]

Comments/Problems:

1. Although I specified "localtime" the clock got set to "UTC"
2. Booting kernel vmlinuz-2.6.25-2-686 and specifying vga=791 gets
"undefined video mode"

There is something funny going on with the post 2.6.24 Debian kernels.
Specifying vga=791, which works 2.6.24 and before, no longer works.
I have submitted a bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481063

I can specify vga=791 with kernels 2.6.25 + 2.6.26 from kernel.org. I
cannot with the Debian kernel images post 2.6.24.
AFAIK it must be a Debian problem then.

Hugo Vanwoerkom

Bug#487556: fixed in xulrunner 1.9~rc2-5: works like a charm!

[hugo vanwoerkom]

My throbbers are throbbin'! As the matter of fact, they look better than
those of FF3!
Thanks Mike, great job!

Hugo

Bug#487411: iceweasel 3.0~rc2-1: Loading... favicon does not rotate

[hugo vanwoerkom]

On Sat, Jun 21, 2008 at 4:00 PM, Mike Hommey <[EMAIL PROTECTED]> wrote:

> On Sat, Jun 21, 2008 at 11:45:30AM -0500, hugo vanwoerkom <
> [EMAIL PROTECTED]> wrote:
> > Package: iceweasel
> > Version: 3.0~rc2-1
> > Severity: normal
> >
> > When opening a tab, or reusing one, the favicon of Loading... stays
> > motionless.
> > It rotated in iceweasel 2.
> > It also rotates using the latest Firefox nightly build and using Firefox
> 3
> > RC3.
>
> The most probable reason is that the new icon is an APNG, which iceweasel 3
> doesn't recognize, while firefox does. APNG is a torture of the PNG
> standard,
> that was rejected by the PNG group, and official libpng is probably not
> going
> to include APNG support for a while. Firefox uses a bundled and heavily
> patched libpng, which we can't for maintenability reasons.
>
>
Thanks Mike, that explains it.

Hugo

Bug#487411: iceweasel 3.0~rc2-1: Loading... favicon does not rotate

[hugo vanwoerkom]

Package: iceweasel
Version: 3.0~rc2-1
Severity: normal

When opening a tab, or reusing one, the favicon of Loading... stays
motionless.
It rotated in iceweasel 2.
It also rotates using the latest Firefox nightly build and using Firefox 3
RC3.

Regards,

Hugo Vanwoerkom


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages iceweasel depends on:
ii  debianutils   2.28.6 Miscellaneous utilities
specific t
ii  fontconfig2.5.0-2generic font configuration
library
ii  libc6 2.7-11 GNU C Library: Shared libraries
ii  libgcc1   1:4.3.0-4  GCC support library
ii  libglib2.0-0  2.16.3-2   The GLib library of C routines
ii  libgtk2.0-0   2.12.10-2  The GTK+ graphical user
interface
ii  libnspr4-0d   4.7.1-3NetScape Portable Runtime
Library
ii  libstdc++64.3.0-4The GNU Standard C++ Library v3
ii  procps1:3.2.7-8  /proc file system utilities
ii  psmisc22.6-1 Utilities that use the proc
filesy
ii  xulrunner-1.9 1.9~rc2-2  XUL + XPCOM application runner

iceweasel recommends no packages.

-- no debconf information

Bug#482074: linux-2.6: system freeze with 2.6.25-1-686 (3x)

[hugo vanwoerkom]

Package: linux-2.6
Severity: normal

While running linux-image-2.6.25-1-686 and 2-686 I had 3 system freezes in
the 9 days I ran 2.6.25.
I then went back to 2.6.24-1-686.

System halts: there is no kbd, no mouse, vcstime stops marking the time.
Sound loops on the last bytes received, apparently.
I was in X and had 3 or so VT's open. Once I was installing VMware and twice
I was running rsync from a USB-HDD to an ATA drive.
Nothing shows in the logs.
I haven't had this since I bought this motherboard 3 years ago.
I realize this is not enough information, but Debian kernels never freeze on
me.
I include the output of hwinfo --short, for whatever it's worth:

===
/home/hugoTue May 20-11:03:19SDA6# hwinfo --short
cpu:
   AMD Athlon(tm) , 2000 MHz
keyboard:
  /dev/input/event0AT Translated Set 2 keyboard
  /dev/input/event1AT Raw Set 2 keyboard
mouse:
  /dev/input/mice  A4 Tech USB Optical Mouse
  /dev/input/mice  A4 Tech USB Optical Mouse
monitor:
   Samsun SyncMaster 753DFX
graphics card:
   nVidia GeForce4 MX 4000
sound:
   EPoX VT8233/A/8235/8237 AC97 Audio Controller
   Creative SB0410 SBLive! 24-bit
storage:
   Floppy disk controller
   VIA VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC
Bus Master IDE
   EPoX VIA VT6420 SATA RAID Controller
network:
  eth0 EPoX VT6103
network interface:
  ppp0 Network Interface
  vmnet1   Ethernet network interface
  vmnet8   Ethernet network interface
  eth0 Ethernet network interface
  lo   Loopback network interface
disk:
  /dev/sdb WDC WD80 0JD-60LUA0
  /dev/sda ST380211 0A
  /dev/hdc ST380011A
  /dev/hda Maxtor 6Y080P0
partition:
  /dev/sdb1Partition
  /dev/sdb2Partition
  /dev/sdb3Partition
  /dev/sdb4Partition
  /dev/sdb5Partition
  /dev/sdb6Partition
  /dev/sdb7Partition
  /dev/sda1Partition
  /dev/sda2Partition
  /dev/sda3Partition
  /dev/sda4Partition
  /dev/sda5Partition
  /dev/sda6Partition
  /dev/sda7Partition
  /dev/hdc1Partition
  /dev/hdc2Partition
  /dev/hdc3Partition  <-This partition has 2.6.25-2-686
installed and got the freezes
  /dev/hdc4Partition
  /dev/hdc5Partition
  /dev/hdc6Partition
  /dev/hdc7Partition
  /dev/hda1Partition
  /dev/hda2Partition
  /dev/hda5Partition
  /dev/hda6Partition
  /dev/hda7Partition
  /dev/hda8Partition
  /dev/hda9Partition
  /dev/hda10   Partition
cdrom:
  /dev/hdd LITE-ON DVDRW SHW-160P6S
usb controller:
   VIA USB 2.0
   VIA VT82x UHCI USB 1.1 Controller
   VIA VT82x UHCI USB 1.1 Controller
   VIA VT82x UHCI USB 1.1 Controller
   VIA VT82x UHCI USB 1.1 Controller
bios:
   BIOS
bridge:
   EPoX VT8237 ISA bridge [KT600/K8T800/K8T890 South]
   VIA VT8237 PCI Bridge
   VIA KT880 Host Bridge
   VIA KT880 Host Bridge
   VIA KT880 Host Bridge
   VIA KT880 Host Bridge
   VIA KT880 Host Bridge
   VIA KT880 Host Bridge
hub:
   D-Link Hub
   Linux 2.6.24-1-686 ehci_hcd EHCI Host Controller
   Linux 2.6.24-1-686 uhci_hcd UHCI Host Controller
   Linux 2.6.24-1-686 uhci_hcd UHCI Host Controller
   Linux 2.6.24-1-686 uhci_hcd UHCI Host Controller
   Linux 2.6.24-1-686 uhci_hcd UHCI Host Controller
memory:
   Main Memory
unknown:
   FPU
   DMA controller
   PIC
   Timer
   RTC
   Keyboard controller
  /dev/lp0 Parallel controller
   PS/2 Controller
   PnP Unclassified device
   PnP Unclassified device
   PnP Unclassified device
   PnP Unclassified device
   PnP Unclassified device
   PnP Unclassified device
   PnP Unclassified device
   PnP Unclassified device
   PnP Unclassified device
   PnP Unclassified device

Bug#481063: linux-image-2.6.25-1-686: vga=791 gets 'undefined video mode number'

[hugo vanwoerkom]

A workaround to the problem is to use uvesafb instead, specified here:
http://wiki.debian.org/HowToUseUvesafbWithDebian

Hugo

Bug#481063: linux-image-2.6.25-1-686: vga=791 gets 'undefined video mode number'

[hugo vanwoerkom]

Sorry I did not submit this under linux-2.6

I compiled the vanilla 2.6.25.3 kernel from www.kernel.org and that boots OK
with vga=791, so the problem resides somewhere within the Debian changes.

Hugo

Bug#481063: linux-image-2.6.25-1-686: vga=791 gets 'undefined video mode number'

[hugo vanwoerkom]

Package: linux-image-2.6.25-1-686
Version: 2.6.25-1
Severity: normal

specifying vga=791 on the grub kernel command line gets 'undefined video
mode number'
in previous kernels that never caused a problem.


-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.25-1-686 depends on:
ii  debconf [debconf-2.0]1.5.14  Debian configuration management
sy
ii  initramfs-tools [linux-initr 0.91b   tools for generating an
initramfs
ii  module-init-tools3.3-pre11-4 tools for managing Linux kernel
mo

Versions of packages linux-image-2.6.25-1-686 recommends:
pn  libc6-i686 (no description available)

-- debconf information:
  linux-image-2.6.25-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.25-1-686/preinst/abort-install-2.6.25-1-686:
  linux-image-2.6.25-1-686/postinst/create-kimage-link-2.6.25-1-686: true
  linux-image-2.6.25-1-686/postinst/bootloader-test-error-2.6.25-1-686:
  linux-image-2.6.25-1-686/preinst/overwriting-modules-2.6.25-1-686: true
  linux-image-2.6.25-1-686/preinst/initrd-2.6.25-1-686:
  linux-image-2.6.25-1-686/postinst/old-initrd-link-2.6.25-1-686: true
  linux-image-2.6.25-1-686/postinst/bootloader-error-2.6.25-1-686:
  linux-image-2.6.25-1-686/preinst/lilo-initrd-2.6.25-1-686: true
  linux-image-2.6.25-1-686/preinst/bootloader-initrd-2.6.25-1-686: true
  linux-image-2.6.25-1-686/preinst/elilo-initrd-2.6.25-1-686: true
  linux-image-2.6.25-1-686/prerm/would-invalidate-boot-loader-2.6.25-1-686:
true
  linux-image-2.6.25-1-686/postinst/old-system-map-link-2.6.25-1-686: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.25-1-686/preinst/failed-to-move-modules-2.6.25-1-686:

Bug#473795: hyperlatex: htmlcaption generates wrong html code

[hugo vanwoerkom]

Package: hyperlatex
Version: 2.9a-3
Severity: normal

'\W\htmlcaption{{\bf{BUILD HISTORY}}}' in version 2.9a-3 wrongly generates:

BUILD HISTORYbody>


which places a spurious 'body>' above 'BUILD HISTORY'

In version 2.8b-3 it generated correctly:

BUILD HISTORY

I apologize if this is not a hyperlatex matter but something emacs did.

I attach the entire file that is used with the hyperlatex command:

'hyperlatex this_build.tex'

Regards,

Hugo Vanwoerkom


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages hyperlatex depends on:
ii  emacs [emacsen]  22.1+1-3The GNU Emacs editor (metapackage)
ii  emacs22 [emacsen]22.1+1-3The GNU Emacs editor
ii  gs-esp [gs]  8.15.3.dfsg.1-1 The Ghostscript PostScript interpr
ii  gs-gpl [gs]  8.56.dfsg.1-1.1 The GPL Ghostscript PostScript int
ii  netpbm   2:10.0-11   Graphics conversion tools

Versions of packages hyperlatex recommends:
ii  tetex-bin 2007-11TeX Live: teTeX transitional packa

-- no debconf information


this_build.tex
Description: TeX document

Bug#436943: grub2: after install boots into rescue mode

[hugo vanwoerkom]

Hi,

Thanks for the continued support.
An explanation: it is difficult trying grub2 because I have changed
legacy grub to do things I needed:

I changed the commands to be able to do this:

title   2.6.24-ck1 on HDB3-NOAPIC CORRECTED network
find/ST380011A.03
rootFILE=/ST380011A.03
kernel  /boot/vmlinuz-2.6.24-1-686 root=LABEL=ST380011A.03
noapic vga=791 apm=on ddcon=1 network quiet
initrd  /boot/initrd.img-2.6.24-1-686
boot

That eliminates having to specify a hardcoded partition location and
enables me to use all labels so I can swap disk positions without
having to change any configuration parameters.

This certainly is [OT] to this bug but explains why I am sticking with
legacy grub for the moment.

Hugo



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#447346: Same issue here - Upstream problem

[hugo vanwoerkom]

On Dec 17, 2007 4:18 AM, Patrick Matthäi <[EMAIL PROTECTED]> wrote:
> Severity: important
>
> Hello,
>
> I've got the same issue on one of two desktop since 2.6.23.x
> (selfcompiled), too.
> I reported it to the Linux bugtracker and they rejected it with the
> reason, that it was an error in the upstream version of udevinfo.
>
> See here: http://bugzilla.kernel.org/show_bug.cgi?id=9150
>
> You should please update the udev package.
>

FWIW, I compiled Debian Sid's 2.6.23-1-686 kernel and patched it with
2.6.23-ck1 and *that* does not get the errors.
I got the error on the vanilla 2.6.23-1 patched with 2.6.23-ck1.

Hugo

Bug#456302: ted never opens anything

[hugo vanwoerkom]

On Dec 17, 2007 2:06 AM, Chris Waters <[EMAIL PROTECTED]> wrote:
> On Sun, Dec 16, 2007 at 05:12:23AM -0600, hugo vanwoerkom wrote:
> > Those are installed:
> > ...
> > ii  xfonts-100dpi  1:1.0.0-4
> >100 dpi fonts for X
> [...]
>
> > It would be strange if the standard default install of Etch not
> > installed xfonts.
>
> Yes, but Ted seems to need the transcoded fonts, which are more
> compatible with the 1990s era Motif-based systems that Ted was
> designed to work with.  Please install the "xfonts-100dpi-transcoded
> and xfonts-75dpi-transcoded packages and see if that fixes your
> problem.
>

SOLVED. Ted needs the transcoded fonts.
Chris, I really appreciate your help. Thanks a lot!



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]