Bug#403217: linux-image-2.6.18-3-686: savage drm does not work

2006-12-15 Thread Manfred Paul
Package: linux-image-2.6.18-3-686
Version: 2.6.18-7
Severity: normal

I have an IBM  T23 Thinkpad. With the currently shipped kernel 3D acceleration 
does
not work with Savage Chips. I updated the savage.ko and drm.ko module from the 
current git repository.
Since this change 3D (AIGLX...) is working. The original bug is filled as 
#393266.
(This is a bug against the Savage X driver). You can also find the steps for 
the update
in the other bug.

regards

Manfred



-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-3-686 depends on:
ii  coreutils 5.97-5 The GNU core utilities
ii  debconf [debconf-2.0] 1.5.8  Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85c  tools for generating an initramfs
ii  module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-3-686 recommends:
ii  libc6-i686   2.3.6.ds1-8 GNU C Library: Shared libraries [i

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


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



Bug#393266: Bug is NOT is savage dri driver but in savage drm

2006-12-14 Thread Manfred Paul
Hello,

I found the source of the problem: savage drm in the kernel.
A fast update to the current git HEAD solved the problem.

Attention: Kernel headers must be installed.

git clone git://anongit.freedesktop.org/git/mesa/drm

cd drm/linux-core/

make DRM_MODULES="savage"

mv  /lib/modules/2.6.18-3-686/kernel/drivers/char/drm/savage.ko 
/lib/modules/2.6.18-3-686/kernel/drivers/char/drm/savage.ko.old
mv /lib/modules/2.6.18-3-686/kernel/drivers/char/drm/drm.ko 
/lib/modules/2.6.18-3-686/kernel/drivers/char/drm/drm.ko.old

cp savage.ko /lib/modules/2.6.18-3-686/kernel/drivers/char/drm/savage.ko
cp drm.ko /lib/modules/2.6.18-3-686/kernel/drivers/char/drm/drm.ko

sudo depmod -a 

and reboot

After I have dri, AIGLX and drm working (no error message any more). So please 
reassign to bug to the kernel team.

regards

P.S. I can provide the kernel modules if somebody wants them.




pgpKG0WmFUyVK.pgp
Description: PGP signature


Bug#384106: Kopete crashes whole system

2006-09-27 Thread Manfred Paul
Hi,

i am providing the unofficial Debian package, but  I never had such 
problems. Except that the statistics plugin causes 100% CPU and HDD
usage (Bug report upstream). All other things are working for me. 

Regards, 

manne 

On Wednesday 27 September 2006 04:03, Christopher Martin wrote:
> Hello,
>
> It looks like KDE 3.5.5 will have Kopete 0.12.x, a big update over the
> version shipped in KDE 3.5.4.
>
> Could you please test whether that version of Kopete still suffers from
> the bug? It's currently available unofficially from
> http://manfred.cp69.de/debian. I'd really appreciate it if those
> affected could give it a try and let us know if the problem still
> happens.
>
> Thanks,
> Christopher Martin
>
> Bastian Venthur wrote:
> > Package: kopete
> > Version: 4:3.5.4-2
> > Severity: critical
> >
> > The latest version of kopete regulary hangs the whole system.
> >
> > I don't know how to reproduce this bug, but it appears randomly every
> > few days.
> >
> > If it happens, kde hangs completely, leaving the user unable to
> > switch to a different terminal or even to restart X. The mouse is not
> > reacting anymore and the system does not respond on any keystrokes.


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



Bug#382874: kopete: Please package new version of Kopete

2006-08-14 Thread Manfred Paul
Hi,

i think it should be possible to upload kopete 0.12 to experimental. Or is 
this not possible until kopete 0.12 is in the upstream kde? 

In the meantime, everybody can download kopete 0.12.2 from:

deb http://manfred.cp69.de/debian sid main
deb-src http://manfred.cp69.de/debian sid main

There are some other kde apps as well (mostly from kde-apps.org)

regards

Manfred 

On Sunday, 13. August 2006 23:31, Eckhart Wörner wrote:
> Package: kopete
> Version: 4:3.5.4-2
> Severity: wishlist
>
> Kopete 0.12 branch (0.12.2 atm) contains great improvements over 0.11
> branch, like better jabber support.
>
> It would be great to see these improvements also in Debian. ;-)
>
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers testing
>   APT policy: (700, 'testing'), (500, 'unstable'), (200, 'experimental')
> Architecture: i386 (i686)
> Shell:  /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.16-2-686
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
>
> -- no debconf information


pgpc3XBHX3IYE.pgp
Description: PGP signature


Bug#382701: xemacs21: Segfault on startup. Fatal error (11)

2006-08-12 Thread Manfred Paul
Package: xemacs21
Version: 21.4.19-1
Severity: grave
Justification: renders package unusable

Today I tried xeamcs, but it there are some strange bugs.
I started xemacs21 by typing:

?> $ xemacs21

I got:

Fatal error (11).

Your files have been auto-saved.
Use `M-x recover-session' to recover them.

Your version of XEmacs was distributed with a PROBLEMS file that  may describe
your crash, and with luck a workaround.  Please check it first, but do report
the crash anyway.  Please report this bug by invoking M-x report-emacs-bug,
or by selecting `Send Bug Report' from the Help menu.  If necessary, send
ordinary email to [EMAIL PROTECTED]'.  *MAKE SURE* to include the XEmacs
configuration from M-x describe-installation, or equivalently the file
Installation in the top of the build tree.

*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
to be able to analyze the problem.  Locate the core file produced as a result
of this crash (often called `core' or `core.', and located in
the directory in which you started XEmacs or your home directory), and type

  gdb /usr/bin/xemacs21 core

then type `where' at the debugger prompt.  No GDB on your system?  You may
have DBX, or XDB, or SDB.  (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited'
in case of future recurrance of the crash.

Lisp backtrace follows:

  # bind (frame-being-created)
  make-frame(nil #)
  frame-initialize()
  # bind (debugger debug-on-error command-line-args-left)
  command-line()
  # (condition-case ... . ((t (byte-code "  �" ... 1
  # bind (error-data)
  normal-top-level()
  # (condition-case ... . error)
  # (catch top-level ...)
Segmentation fault

Then I tried:

?> $ gdb /usr/bin/xemacs21 core

I got:

GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

/home/manfred/core: No such file or directory.
(gdb) run
Starting program: /usr/bin/xemacs21
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1483462976 (LWP 14668)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1483462976 (LWP 14668)]
0xa7548a7f in _XInitOM () from /usr/lib/X11/locale/common/xomGeneric.so.2
(gdb)  

I am using xinerama with a T23. Could this problem be related to an X error?

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-beyond3
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages xemacs21 depends on:
ii  xemacs21-mule 21.4.19-1  highly customizable text editor --

xemacs21 recommends no packages.

-- no debconf information


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



Bug#375760: astyle: The package in the repository is not up2date.

2006-06-27 Thread Manfred Paul
Package: astyle
Version: 1.15.3-5
Severity: normal


The package in the repository is not up2date. The upstream version fixes
several bugs (e.g. correct formatting problems with pad=oper and
pad=paren, correct formatting when a bracket mode is not declared).

The upstream version is 1.18.

If needed, I can provide the package as well, because I needed the new
version and built the new package myself.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-emission2
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages astyle depends on:
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libgcc1   1:4.1.1-5  GCC support library
ii  libstdc++64.1.1-5The GNU Standard C++ Library v3

astyle recommends no packages.

-- no debconf information


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