Bug#960185: Acknowledgement (libgsl-dev: fails to converge on beta inv for some values)
My initial test case was this double lowerbound = gsl_cdf_beta_Qinv(0.95, 12093.0, 3602.0); which appears to be fixed with the patch, but I since found a new case that fails: double lowerbound = gsl_cdf_beta_Qinv(0.95, 9656, 5038); -- Hans Ekbrand
Bug#960185: libgsl-dev: fails to converge on beta inv for some values
Package: libgsl-dev
Version: 2.6+dfsg-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
#include
#include // for the cummulative beta distribution
gsl_cdf_beta_Q()
int
main (void)
{
double lowerbound = gsl_cdf_beta_Q(0.003, 12093.0, 3602.0);
printf ("%.18e\n", lowerbound);
return 0;
}
failed to converge
* What exactly did you do (or not do) that was effective (or
ineffective)?
I applied a patch supplied upstream http://savannah.gnu.org/bugs/?45924,
recompiled gsl and recompiled the above program
* What was the outcome of this action?
7.649597002136596657e-01
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.6.0-1-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to
sv_SE.utf8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to
sv_SE.utf8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libgsl-dev depends on:
ii libgsl25 2.6+dfsg-2
ii libgslcblas0 2.6+dfsg-2
libgsl-dev recommends no packages.
libgsl-dev suggests no packages.
-- debconf-show failed
Bug#920659: caffe-cuda: Fails to find the right cuda driver: "CUDA driver version is insufficient for CUDA runtime version"
Package: caffe-cuda Version: 1.0.0+git20180821.99bd997-2 Severity: normal Dear Maintainer, * What led up to the situation? $ caffe time -model examples/mnist/lenet.prototxt -gpu 0 I0128 01:30:26.382874 7238 caffe.cpp:339] Use GPU with device ID 0 F0128 01:30:26.384541 7238 common.cpp:152] Check failed: error == cudaSuccess (35 vs. 0) CUDA driver version is insufficient for CUDA runtime version *** Check failure stack trace: *** @ 0x7ff771464cad google::LogMessage::Fail() @ 0x7ff771466b13 google::LogMessage::SendToLog() @ 0x7ff771464808 google::LogMessage::Flush() @ 0x7ff771467579 google::LogMessageFatal::~LogMessageFatal() @ 0x7ff7717d17f2 caffe::Caffe::SetDevice() @ 0x55c3a4d7bf03 time() @ 0x55c3a4d76a71 main @ 0x7ff770b8409b __libc_start_main @ 0x55c3a4d775ea _start Aborted Not quite sure which package contains the CUDA driver, but here is a list of suspects: and yes I have cuda9.0 (nvidia-packages) installed side by side with cuda9.1 from Debian, libcudart9.2 was installed as a dependency by libcaffe-cuda1. Perhaps libcudart9.2 requires a newer kernel driver than 390.87? $ LC_ALL=C dpkg -l "*cuda*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--=== ii caffe-cuda 1.0.0+git20180821.99bd997-2 amd64Fast, open framework for Deep Learning (Meta) ii caffe-tools-cuda 1.0.0+git20180821.99bd997-2 amd64Tools for fast, open framework for Deep Learning (CUDA) rc cuda-command-line-tools-9-09.0.176-1 amd64CUDA command-line tools ii cuda-core-9-0 9.0.176-1 amd64CUDA core tools ii cuda-cublas-9-09.0.176.4-1 amd64CUBLAS native runtime libraries ii cuda-cublas-dev-9-09.0.176.4-1 amd64CUBLAS native dev links, headers ii cuda-cudart-9-09.0.176-1 amd64CUDA Runtime native Libraries ii cuda-cudart-dev-9-09.0.176-1 amd64CUDA Runtime native dev links, headers ii cuda-cufft-9-0 9.0.176-1 amd64CUFFT native runtime libraries ii cuda-cufft-dev-9-0 9.0.176-1 amd64CUFFT native dev links, headers ii cuda-curand-9-09.0.176-1 amd64CURAND native runtime libraries ii cuda-curand-dev-9-09.0.176-1 amd64CURAND native dev links, headers ii cuda-cusolver-9-0 9.0.176-1 amd64CUDA solver native runtime libraries ii cuda-cusolver-dev-9-0 9.0.176-1 amd64CUDA solver native dev links, headers ii cuda-cusparse-9-0 9.0.176-1 amd64CUSPARSE native runtime libraries ii cuda-cusparse-dev-9-0 9.0.176-1 amd64CUSPARSE native dev links, headers ii cuda-driver-dev-9-09.0.176-1 amd64CUDA Driver native dev stub library ii cuda-libraries-9-0 9.0.176-1 amd64CUDA Libraries 9.0 meta-package ii cuda-libraries-dev-9-0 9.0.176-1 amd64CUDA Libraries 9.0 development meta-package un cuda-license-7-5 (no description available) ii cuda-license-9-0 9.0.176-1 amd64CUDA licenses ii cuda-misc-headers-9-0 9.0.176-1 amd64CUDA miscellaneous headers ii cuda-npp-9-0 9.0.176-1 amd64NPP native runtime libraries ii cuda-npp-dev-9-0 9.0.176-1 amd64NPP native dev links, headers ii cuda-nvgraph-9-0 9.0.176-1 amd64NVGRAPH native runtime libraries ii cuda-nvgraph-dev-9-0 9.0.176-1 amd64NVGRAPH native dev links, headers ii cuda-nvrtc-9-0 9.0.176-1 amd64NVRTC native runtime libraries ii cuda-nvrtc-dev-9-0 9.0.176-1 amd64
Bug#740185: zathura: Two problems with the current mailcap entry
Dear Maintainer,
The current mailcap entry for zathura has two disturbing issues:
1. It does not fork zathura, so any calling program (like mutt, or
midnight commander) is locked until zathura has finished. Forking
should be the default behaviour here.
Is the default behavior specified somewhere?
Not that I know of. But other mail clients, eg icedove, is not locked
when an attached pdf is viewed. Exactly how they achieve this, I don't
know.
2. It causes confusing messages on stderr, which in turn can mess up
the screen state of the calling program.
Which one?
midnight commander http://packages.debian.org/sid/mc
I suggest the following entries as a solution to the aboved mentioned
problems:
application/pdf; { TMP=`mktemp` \; cp '%s' $TMP \; (zathura --fork $TMP
/dev/null 21 sleep 5 rm $TMP ) } ; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf;
application/x-pdf; { TMP=`mktemp` \; cp '%s' $TMP \; (zathura --fork $TMP
/dev/null 21 sleep 5 rm $TMP ) } ; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf;
I think that this is wrong. This makes zathura's support for saving some
state for documents useless as the information is stored per filename.
I see the problem, that's because mktemp is non-deterministic. I just
picked mktemp because it provided a file name, but any deterministic
file naming process would work, for example this one:
application/pdf; { cp -av '%s' /tmp/'%s'.tmp \; (zathura --fork /tmp/'%s'.tmp
/dev/null 21 sleep 5 rm /tmp/'%s'.tmp ) } ; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf;
application/x-pdf; { cp -av '%s' /tmp/'%s'.tmp \; (zathura --fork /tmp/'%s'.tmp
/dev/null 21 sleep 5 rm /tmp/'%s'.tmp ) } ; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf;
--
Note that I use Debian version 7.4
Linux hans 3.2.0-4-686-pae #1 SMP Debian 3.2.54-2 i686 GNU/Linux
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740185: zathura: Two problems with the current mailcap entry
On Thu, Mar 20, 2014 at 05:12:41PM +0100, Hans Ekbrand wrote:
I see the problem, that's because mktemp is non-deterministic. I just
picked mktemp because it provided a file name, but any deterministic
file naming process would work, for example this one:
application/pdf; { cp -av '%s' /tmp/'%s'.tmp \; (zathura --fork /tmp/'%s'.tmp
/dev/null 21 sleep 5 rm /tmp/'%s'.tmp ) } ; test=test -n
$DISPLAY; description=Portable Document Format; nametemplate=%s.pdf;
application/x-pdf; { cp -av '%s' /tmp/'%s'.tmp \; (zathura --fork
/tmp/'%s'.tmp /dev/null 21 sleep 5 rm /tmp/'%s'.tmp ) } ;
test=test -n $DISPLAY; description=Portable Document Format;
nametemplate=%s.pdf;
The substitution of '%s' does not work like that, it needs a temporary
variable. And I have updated it to quote the new file name. In my
testing the following entries will work with odd filenames and will
let zathura start at the last seen page (since the filename of the
temporary file is now deterministic).
application/pdf; { TMP=`basename '%s'` \; cp -a '%s' /tmp/$TMP.tmp \;
(zathura --fork /tmp/$TMP.tmp /dev/null 21 sleep 5 rm
/tmp/$TMP.tmp ) } ; test=test -n $DISPLAY; description=Portable Document
Format; nametemplate=%s.pdf;
application/x-pdf; { TMP=`basename '%s'` \; cp -a '%s' /tmp/$TMP.tmp \;
(zathura --fork /tmp/$TMP.tmp /dev/null 21 sleep 5 rm
/tmp/$TMP.tmp ) } ; test=test -n $DISPLAY; description=Portable Document
Format; nametemplate=%s.pdf;
--
Note that I use Debian version 7.4
Linux hans 3.2.0-4-686-pae #1 SMP Debian 3.2.54-2 i686 GNU/Linux
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740185: zathura: Two problems with the current mailcap entry
On Thu, Mar 20, 2014 at 06:08:58PM +0100, Sebastian Ramacher wrote:
On 2014-03-20 17:12:41, Hans Ekbrand wrote:
2. It causes confusing messages on stderr, which in turn can mess up
the screen state of the calling program.
Which one?
I meant the confusing messages on stderr. What's the error message?
info: successfully loaded plugin /usr/lib/zathura/pdf.so
info: Using plain database backend.
So, to be clear what I meant: consider a document named /a/b.pdf. If one
opens the file from within zathura or by passing it as argument to
zathura, bookmarks and all the other stored information will be
available. However, with that menu entry, opening from mc will not
preserve that. And this is not solved by using a deterministic name in
/tmp.
But the addition of a using deterministic name in /tmp also breaks other
use cases. Assume user A opens /a/c.pdf and user B opens /b/c.pdf (both
do this via mc), which file do they see?
You're right, copying the file is not the solution here. run-mailcap
already provides a nice mechanism, put a randomly named symlink in
/tmp which points back to the real file, give the viewer program
(zathura, in our case) the symlink. This mechanism is used whenever
the filename contains character(s) that the shell needs to be
protected from. While the mechanism is nice, it is not used in all
cases which introduces a complexity that has to be dealt with.
So, then, in what I think would solve the problem without reducing the
features of zathura, I propose this entry:
application/pdf; { TEMPSYMLINK=`mktemp` \; rm $TEMPSYMLINK \; if test -L '%s'
\; then cp -a '%s' $TEMPSYMLINK \; else CURRDIR=`pwd` \; FILE=`dir '%s'` \; ln
-s ${CURRDIR}/${FILE} $TEMPSYMLINK \; fi \; ( zathura $TEMPSYMLINK /dev/null
21 \; rm $TEMPSYMLINK ) } ; test=test -n $DISPLAY; description=Portable
Document Format; nametemplate=%s.pdf;
application/pdf; { TEMPSYMLINK=`mktemp` \; rm $TEMPSYMLINK \; if test -L '%s'
\; then cp -a '%s' $TEMPSYMLINK \; else CURRDIR=`pwd` \; FILE=`dir '%s'` \; ln
-s ${CURRDIR}/${FILE} $TEMPSYMLINK \; fi \; ( zathura $TEMPSYMLINK /dev/null
21 \; rm $TEMPSYMLINK ) } ; test=test -n $DISPLAY; description=Portable
Document Format; nametemplate=%s.pdf;
application/x-pdf; { TMP=`basename '%s'` \; cp -a '%s' /tmp/$TMP.tmp \;
(zathura --fork /tmp/$TMP.tmp /dev/null 21 sleep 5 rm
/tmp/$TMP.tmp ) } ; test=test -n $DISPLAY; description=Portable Document
Format; nametemplate=%s.pdf;
In order to see what it does, here is the code commented line by line
## Get a random name
TEMPSYMLINK=`mktemp` \;
## Remove that file, we only wanted the name
rm $TEMPSYMLINK \;
## Test if '%s' is a symlink or not
if test -L '%s' \; then
## '%s' is a symlink, we copy this one with cp -a to our own TEMPSYMLINK
cp -a '%s' $TEMPSYMLINK \;
else
## '%s' is not a symlink, locate it
CURRDIR=`pwd` \;
FILE=`dir '%s'` \;
## make a symlink from our TEMPSYMLINK to wherever '%s' is
ln -s ${CURRDIR}/${FILE} $TEMPSYMLINK \;
fi \;
## fork by starting zathura in sub shell,
## remove our TEMPSYMLINK when zathura exits
( zathura $TEMPSYMLINK /dev/null 21 \; rm $TEMPSYMLINK )
Now, some testing
1. file without protected characters in the name, in $HOME
$ see --debug foo.pdf
- parsing parameter foo.pdf
- Reading mime.types file /etc/mime.types...
- extension pdf maps to mime-type application/pdf
- Reading mailcap file /home/hans/.mailcap...
- Reading mailcap file /etc/mailcap...
Processing file foo.pdf of type application/pdf (encoding=none)...
- checking mailcap entry application/pdf; { TEMPSYMLINK=`mktemp` rm
$TEMPSYMLINK if test -L '%s' then cp -a '%s' $TEMPSYMLINK else
CURRDIR=`pwd` FILE=`dir '%s'` ln -s ${CURRDIR}/${FILE} $TEMPSYMLINK fi (
zathura $TEMPSYMLINK /dev/null 21 rm $TEMPSYMLINK ) } ; test=test -n
$DISPLAY; description=Portable Document Format; nametemplate=%s.pdf;
- program to execute: { TEMPSYMLINK=`mktemp` rm $TEMPSYMLINK if test -L
'%s' then cp -a '%s' $TEMPSYMLINK else CURRDIR=`pwd` FILE=`dir '%s'` ln -s
${CURRDIR}/${FILE} $TEMPSYMLINK fi ( zathura $TEMPSYMLINK /dev/null 21
rm $TEMPSYMLINK ) }
- running test: test -n $DISPLAY (result=0=true)
- executing: { TEMPSYMLINK=`mktemp` ; rm $TEMPSYMLINK ; if test -L 'foo.pdf'
; then cp -a 'foo.pdf' $TEMPSYMLINK ; else CURRDIR=`pwd` ; FILE=`dir 'foo.pdf'`
; ln -s ${CURRDIR}/${FILE} $TEMPSYMLINK ; fi ; ( zathura $TEMPSYMLINK
/dev/null 21 ; rm $TEMPSYMLINK ) }
zathura is started and the file is opened. In /tmp the following has happened:
ls -lStr /tmp/ | tail -n 1
lrwxrwxrwx 1 hans hans 18 mar 20 20:39 tmp.zxMFFkjgeb - /home/hans/foo.pdf
After closing zathura, this symlink is removed:
ls -lStr /tmp/tmp.zxMFFkjgeb
ls: cannot access /tmp/tmp.zxMFFkjgeb: No such file or directory
2. file with protected characters in the name, in a subdir with a space in its
name
$ see --debug test\ mailcap/5\!\.pdf
- parsing parameter test mailcap/5!.pdf
- Reading
Bug#740185: zathura: Two problems with the current mailcap entry
On Thu, Mar 20, 2014 at 08:51:22PM +0100, Hans Ekbrand wrote:
You're right, copying the file is not the solution here. run-mailcap
already provides a nice mechanism, put a randomly named symlink in
/tmp which points back to the real file, give the viewer program
(zathura, in our case) the symlink. This mechanism is used whenever
the filename contains character(s) that the shell needs to be
protected from. While the mechanism is nice, it is not used in all
cases which introduces a complexity that has to be dealt with.
So, then, in what I think would solve the problem without reducing the
features of zathura, I propose this entry:
application/pdf; { TEMPSYMLINK=`mktemp` \; rm $TEMPSYMLINK \; if test -L
'%s' \; then cp -a '%s' $TEMPSYMLINK \; else CURRDIR=`pwd` \; FILE=`dir '%s'`
\; ln -s ${CURRDIR}/${FILE} $TEMPSYMLINK \; fi \; ( zathura $TEMPSYMLINK
/dev/null 21 \; rm $TEMPSYMLINK ) } ; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf;
application/pdf; { TEMPSYMLINK=`mktemp` \; rm $TEMPSYMLINK \; if test -L
'%s' \; then cp -a '%s' $TEMPSYMLINK \; else CURRDIR=`pwd` \; FILE=`dir '%s'`
\; ln -s ${CURRDIR}/${FILE} $TEMPSYMLINK \; fi \; ( zathura $TEMPSYMLINK
/dev/null 21 \; rm $TEMPSYMLINK ) } ; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf;
application/x-pdf; { TMP=`basename '%s'` \; cp -a '%s' /tmp/$TMP.tmp \;
(zathura --fork /tmp/$TMP.tmp /dev/null 21 sleep 5 rm
/tmp/$TMP.tmp ) } ; test=test -n $DISPLAY; description=Portable
Document Format; nametemplate=%s.pdf;
That solution has two problems
a) it assumes that '%s' is not an absolute path
b) when used by mutt, mutt removes the PDF before zathura has opened it.
Problem a)
solved by checking for / as the first character in basename of '%s'
Problem b)
But, after even more hacking on this, I have a solution to both of
these problems too. That mutt relies on that the viewer program does
NOT fork is a problem with mutt rather than with zathura, but I think
I have a solution to this problem does not cause any other problems:
test if %s is in /tmp. If it is, then make a copy before forking.
Mutt will then delete the original, but zathura has its own copy. When
zatura is done, that copy is deleted too. The drawback is that zathura
does not remember state when viewing attached PDF:s, however that
feature is only useful on files you view a second time, and files in
/tmp are not very likely to be opened more than once.
application/pdf; { TEMPSYMLINK=`mktemp` \; rm $TEMPSYMLINK \; if test -L '%s'
\; then cp -a '%s' $TEMPSYMLINK \; else DIR=`dirname '%s'` \; if test `echo -n
$DIR | cut -b 1-4` = /tmp \; then cp '%s' $TEMPSYMLINK \; else
FILE=`basename '%s'` \; if test `echo -n $DIR | cut -b 1` = / \; then
ln -s ${DIR}/${FILE} $TEMPSYMLINK \; else FULLDIR=`pwd`/${DIR} \; ln -s
${FULLDIR}/${FILE} $TEMPSYMLINK \; fi \; fi \; fi \; ( zathura $TEMPSYMLINK
/dev/null 21 \; rm $TEMPSYMLINK ) } ; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf;
application/x-pdf; { TEMPSYMLINK=`mktemp` \; rm $TEMPSYMLINK \; if test -L '%s'
\; then cp -a '%s' $TEMPSYMLINK \; else DIR=`dirname '%s'` \; if test `echo -n
$DIR | cut -b 1-4` = /tmp \; then cp '%s' $TEMPSYMLINK \; else
FILE=`basename '%s'` \; if test `echo -n $DIR | cut -b 1` = / \; then
ln -s ${DIR}/${FILE} $TEMPSYMLINK \; else FULLDIR=`pwd`/${DIR} \; ln -s
${FULLDIR}/${FILE} $TEMPSYMLINK \; fi \; fi \; fi \; ( zathura $TEMPSYMLINK
/dev/null 21 \; rm $TEMPSYMLINK ) } ; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf;
And the full version with comments
## Get a random name
TEMPSYMLINK=`mktemp` ;
## Remove that file, we only wanted the name
rm $TEMPSYMLINK ;
## Test if $1 is a symlink or not
if test -L $1 ; then
## $1 is a symlink, we copy this one with cp -a to our own TEMPSYMLINK
cp -a $1 $TEMPSYMLINK ;
else ;
## $1 is not a symlink, locate it
DIR=`dirname $1` ;
## make a special assumption about /tmp: if the file is in /tmp, then do
not assume that the file will be left after we haved forked, so copy before we
fork.
if test `echo -n $DIR | cut -b 1-4` = /tmp ; then
cp $1 $TEMPSYMLINK ;
else ;
## make a symlink from our TEMPSYMLINK to wherever $1 is
FILE=`basename $1` ;
if test `echo -n $DIR | cut -b 1` = / ; then
## file has absolute path
ln -s ${DIR}/${FILE} $TEMPSYMLINK ;
else ;
## file has relative path
FULLDIR=`pwd`/${DIR} ;
ln -s ${FULLDIR}/${FILE} $TEMPSYMLINK ;
fi ;
fi ;
fi ;
## fork by starting zathura in sub shell,
## remove our TEMPSYMLINK when zathura exits
( zathura $TEMPSYMLINK /dev/null 21 ; rm $TEMPSYMLINK )
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740185: zathura: Two problems with the current mailcap entry
Package: zathura
Version: 0.1.2-4
Severity: wishlist
Dear Maintainer,
The current mailcap entry for zathura has two disturbing issues:
1. It does not fork zathura, so any calling program (like mutt, or
midnight commander) is locked until zathura has finished. Forking
should be the default behaviour here.
2. It causes confusing messages on stderr, which in turn can mess up
the screen state of the calling program.
Here is the current system default mail cap entry:
application/pdf; /usr/bin/zathura '%s'; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf
application/x-pdf; /usr/bin/zathura '%s'; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf
I suggest the following entries as a solution to the aboved mentioned problems:
application/pdf; { TMP=`mktemp` \; cp '%s' $TMP \; (zathura --fork $TMP
/dev/null 21 sleep 5 rm $TMP ) } ; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf;
application/x-pdf; { TMP=`mktemp` \; cp '%s' $TMP \; (zathura --fork $TMP
/dev/null 21 sleep 5 rm $TMP ) } ; test=test -n $DISPLAY;
description=Portable Document Format; nametemplate=%s.pdf;
Explanation: 1. make a temporary file an safe way with mktemp. 2 make zathura
fork and load this temporary file, without pushing back stuff on the console.
3. Wait until zathura has started to open the file, give it 5 seconds. 4.
remove the temporary file.
It would introduce a dependency on mktemp in coreutils, but coreutils
has priority: required, so that is a non-issue. No one will complain
about having to install coreutils in order to have zathura on the
system.
Kind regards,
Hans Ekbrand
-- System Information:
Debian Release: 7.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to sv_SE.utf8)
Shell: /bin/sh linked to /bin/dash
Versions of packages zathura depends on:
ii libc6 2.13-38+deb7u1
ii libcairo2 1.12.2-3
ii libgirara-gtk2-0 0.1.2-3
ii libglib2.0-0 2.33.12+really2.32.4-5
ii libgtk2.0-0 2.24.10-2
ii libpoppler-glib8 0.18.4-6
ii libsqlite3-0 3.7.13-1+deb7u1
zathura recommends no packages.
Versions of packages zathura suggests:
ii chromium [www-browser] 31.0.1650.63-1~deb7u1
ii iceweasel [www-browser] 17.0.10esr-1~deb7u1
ii poppler-data 0.4.5-10
ii w3m [www-browser]0.5.3-8
pn zathura-djvu none
pn zathura-ps none
-- 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#631866: linux-source-2.6.39: no APM support even when compiled in AND booted with apm=on
On Tue, Jun 28, 2011 at 02:51:31PM +0100, Ben Hutchings wrote: On Tue, 2011-06-28 at 08:09 +0200, Hans Ekbrand wrote: On Mon, Jun 27, 2011 at 11:21:26PM +0100, Ben Hutchings wrote: On Mon, Jun 27, 2011 at 11:28:34PM +0200, Hans Ekbrand wrote: Package: linux-source-2.6.39 Version: 2.6.39-2 Severity: normal Summary: I recompiled with make menuconfig, loaded the default config for linux-image-2.6.39-486-2 into menuconfig, disabled ACPI, enabled APM (but not the sub-items of APM in menuconfig). Then booted this image with apm=on and now: # apm -S No APM support in kernel So apm lies... selected output from dmesg: $ dmesg | grep -i apm [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.39 root=/dev/mapper/amin-root ro apm=on quiet [ 12.378224] apm: BIOS not found. [...] Well, are you sure that this machine does have APM BIOS support? Because the kernel cannot use APM that is not there... Yes I am sure, because apm -S has worked perfectly on this particular machine with older kernels. Could it be a battery thing? Otherwise I know APM is supported by that BIOS. This is an old compaq laptop, Armada 1540D, so I don't expect the BIOS to be perfectly compliant with the standards. But it did work with older official debian kernels, however, this is the first time I have tried a custom kernel on it. Which was the last version it worked on? I'm working on testing this, but it is hard, since the old kernels does not work with current udev, and this old beast cannot boot CDs or USB-sticks. I had to hack the postinst and create new binary packages to even get them installed, but booting failed. I'll try to manually put some old kernels and initrds in /boot and configure grub to offer them at boot-time. That I did not enable the sub-itmes of APM in menuconfig, might that be a problem? Yes, but that doesn't explain the 'apm: BIOS not found' warning. I recompiled with the following setting: CONFIG_X86_APM_BOOT=y CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set CONFIG_APM_DO_ENABLE=y CONFIG_APM_CPU_IDLE=y CONFIG_APM_DISPLAY_BLANK=y CONFIG_APM_ALLOW_INTS=y but, in vain. [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.39 root=/dev/mapper/amin-root ro apm=on quiet [ 12.428066] apm: BIOS not found. there is no /proc/apm when booting this kernel, shouldn't it be there? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631866: linux-source-2.6.39: no APM support even when compiled in AND booted with apm=on
On Mon, Jun 27, 2011 at 11:21:26PM +0100, Ben Hutchings wrote: On Mon, Jun 27, 2011 at 11:28:34PM +0200, Hans Ekbrand wrote: Package: linux-source-2.6.39 Version: 2.6.39-2 Severity: normal Summary: I recompiled with make menuconfig, loaded the default config for linux-image-2.6.39-486-2 into menuconfig, disabled ACPI, enabled APM (but not the sub-items of APM in menuconfig). Then booted this image with apm=on and now: # apm -S No APM support in kernel So apm lies... selected output from dmesg: $ dmesg | grep -i apm [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.39 root=/dev/mapper/amin-root ro apm=on quiet [ 12.378224] apm: BIOS not found. [...] Well, are you sure that this machine does have APM BIOS support? Because the kernel cannot use APM that is not there... Yes I am sure, because apm -S has worked perfectly on this particular machine with older kernels. Could it be a battery thing? Otherwise I know APM is supported by that BIOS. This is an old compaq laptop, Armada 1540D, so I don't expect the BIOS to be perfectly compliant with the standards. But it did work with older official debian kernels, however, this is the first time I have tried a custom kernel on it. That I did not enable the sub-itmes of APM in menuconfig, might that be a problem? They were described as (NEW), so I thought that they cannot be necessary, but later on I saw that they have been (NEW) for the last ten years or so :-) signature.asc Description: Digital signature
Bug#629009: Bug confirmed on other Pentium MMX
After upgrading gcc and cpp from 4.4 to 4.6, cpp stopped working on Pentium MMX. Currently, I have xrdb dying unless invoked with -cpp /usr/bin/i486-linux-gnu-cpp-4.4 and when compiling R packages, this is what I got: gcc -I/usr/share/R/include -I/usr/lib/R/library/Matrix/include -I/usr/lib/R/library/stats/include -fpic -std=gnu99 -O3 -pipe -g -c init.c -o init.o gcc: internal compiler error: Illegal instruction (program cc1) Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.6/README.Bugs for instructions. make: *** [init.o] Error 4 ERROR: compilation failed for package ‘lme4’ For the time being, I would like to use gcc-4.4 instead. How do you set 4.4 as the default version? signature.asc Description: Digital signature
Bug#589524: bug still there?
I tried to get around the bug by uninstalling pg-8.3, pg-8.4 and pg-common, followed by installing pg-8.4. But I still had the same problem. Have you tried a clean install of pg-8.4? signature.asc Description: OpenPGP digital signature
Bug#588293: grub-pc: fails to allocate memory so nothing can be booted (on an old compaq laptop)
Package: grub-pc
Version: 1.98+20100706-1
Severity: normal
Tags: d-i
When trying to boot linux, I get this error message:
error: cannot allocate real mode pages
And, when trying to boot memtest86+, I is informed that
error: too small lower memory (0x9910 0x0)
The same problem is reported in ubuntu, see
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/513528
The problem is not specific for grub-pc 20100706, I have had it for a
couple of versions of grub-pc but did not report until today. I have
followed unstable only for a few weeks, so earlier versions are not
tested. However, grub-legacy works perfectly.
The machine is a compaq Armada 1540D. Until this bug is fixed, perhaps
the d-i team keep a list of devices that only work with grub-legacy.
And the compaq Armade 1540D is such a device.
Kind regards,
Hans Ekbrand
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/amin-root / ext3
rw,noatime,nodiratime,errors=remount-ro,commit=3600,data=ordered 0 0
/dev/hda1 /boot ext3 rw,relatime,errors=continue,commit=3600,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-ST92130AG_FW185822
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
if terminal_input console ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_input
terminal console
fi
if terminal_output console ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal console
fi
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-486' --class debian --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 94c58265-b185-496f-bb9d-f70c9fc88dd7
echo'Loading Linux 2.6.32-5-486 ...'
linux /vmlinuz-2.6.32-5-486 root=/dev/mapper/amin-root ro quiet
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-486
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-486 (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 94c58265-b185-496f-bb9d-f70c9fc88dd7
echo'Loading Linux 2.6.32-5-486 ...'
linux /vmlinuz-2.6.32-5-486 root=/dev/mapper/amin-root ro single
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-486
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry Memory test (memtest86+) {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 94c58265-b185-496f-bb9d-f70c9fc88dd7
linux16 /memtest86+.bin
}
menuentry Memory test (memtest86+, serial console 115200) {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 94c58265-b185-496f-bb9d-f70c9fc88dd7
linux16 /memtest86+.bin console=ttyS0,115200n8
}
menuentry Memory test (memtest86+, experimental multiboot) {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 94c58265-b185-496f-bb9d-f70c9fc88dd7
multiboot /memtest86+_multiboot.bin
}
menuentry Memory test (memtest86+, serial console 115200, experimental
multiboot) {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 94c58265-b185-496f-bb9d-f70c9fc88dd7
multiboot /memtest86+_multiboot.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu
Bug#585791: Upgrading from pcscd_1.4.102-1_i386.deb to pcscd_1.4.102-1+lenny1_i386.deb broke my bankid application (digital signing internetbanking)
Package: pcscd Version: 1.4.102-1 Severity: normal Upgrading from pcscd_1.4.102-1_i386.deb to pcscd_1.4.102-1+lenny1_i386.deb broke my bankid application (digital signing internetbanking). With the working version installed, my signing app (personal from nexussafe.com) is able to use the card-reader and ask for pin-code from the card-reader. But with the latest version (pcscd_1.4.102-1+lenny1_i386.deb), the card-reader is not used, instead I am asked for a pin-code by a dialog. Since I don't have the source code of the app, it's a third party app distributed by the internet bank, I cannot be 100% certain that the app is using a correct API. However, a security update should not break working third party apps. Lastly, it may well be that libpcsclite1 is the guilty one, I solved the issue by down-grading both of them. Kind regards, Hans Ekbrand -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to sv_SE.utf8) Shell: /bin/sh linked to /bin/bash Versions of packages pcscd depends on: ii hal 0.5.11-8 Hardware Abstraction Layer ii libc6 2.7-18lenny4 GNU C Library: Shared libraries ii libccid [pcsc-ifd-handler 1.3.8-1PC/SC driver for USB CCID smart ca ii libdbus-1-3 1.2.1-5+lenny1 simple interprocess messaging syst ii libhal1 0.5.11-8 Hardware Abstraction Layer - share ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip pcscd recommends no packages. pcscd 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#318058: about Bug#318058: lidbdb-mysql-perl and UTF8
On Thu, Apr 02, 2009 at 04:12:24PM +0300, WK wrote: Terr! Hans Ekbrand kirjutas 30. märtsil sel aastal: Have you tried to run perl with -C? On Lenny, I had the same problems as described in this bug report, but they went away when started perl with -C, or defined the environmental variable PERL_UNICODE=. As you can see some messages back there, i am. -C63, to be precise. It did not help. Did you try it with my testcase i posted here? Which number you tried with -C? I used a single -C no number. Btw, i don't get messages which are posted to 318...@bugs.debian.org. I think you should get those if you are the bug reporter, otherwise I am confident that it is possible to subscribe to particular bugs. -- Note that I use Debian version 5.0 Linux sqlserver 2.6.26-1-powerpc #1 Mon Dec 15 13:20:34 CET 2008 ppc GNU/Linux Hans Ekbrand (http://sociologi.cjb.net) h...@sociologi.cjb.net Signature generated by Signify v1.14. For this and more, visit http://www.debian.org/ signature.asc Description: Digital signature
Bug#318058: about Bug#318058: lidbdb-mysql-perl and UTF8
On Fri, Mar 20, 2009 at 03:30:55PM +0100, gregor herrmann wrote: On Fri, 20 Mar 2009 14:00:35 +0200, WK wrote: [Please keep 318...@bugs.debian.org in the loop.] Some time ago i posted a testcase for reproducing this bug. Did you have time to test it? Not yet, sorry. I can add some symptoms more. Thanks for the additional information. I have this bug still on my TODO list, but I won't mind help from some other pkg-perl member :) Have you tried to run perl with -C? On Lenny, I had the same problems as described in this bug report, but they went away when started perl with -C, or defined the environmental variable PERL_UNICODE=. -- Note that I use Debian version 5.0 Linux samir 2.6.28-1-686 #1 SMP Mon Feb 23 03:13:24 UTC 2009 i686 GNU/Linux Hans Ekbrand (http://sociologi.cjb.net) h...@sociologi.cjb.net A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? signature.asc Description: Digital signature
Bug#493480: excessive dependencies in rxvt-unicode-lite
In Etch rxvt-unicode-lite only required: Depends: libc6 Depends: libgcc1 Depends: libx11-6 Depends: libxpm4 Depends: base-passwd Depends: ncurses-base in Lenny it requires: Depends: libafterimage0 Depends: libc6 Depends: libcairo2 Depends: libfreetype6 Depends: libgcc1 Depends: libglib2.0-0 Depends: libgtk2.0-0 Depends: libice6 Depends: libjpeg62 Depends: libpng12-0 Depends: librsvg2-2 Depends: libsm6 Depends: libtiff4 Depends: libx11-6 Depends: libxext6 Depends: zlib1g Depends: base-passwd Depends: ncurses-base This seems like a mistake, since the description of the package has not changed, and explictly says that the lite version is built without freetype support. -- Linux samir 2.6.26-1-686 #1 SMP Thu Aug 28 12:00:54 UTC 2008 i686 GNU/Linux Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] GPG Fingerprint: 1408 C8D5 1E7D 4C9C C27E 014F 7C2C 872A 7050 614E signature.asc Description: Digital signature
Bug#493480: excessive dependencies in rxvt-unicode-lite
On Thu, Sep 25, 2008 at 08:49:51AM -0400, Decklin Foster wrote: Hans Ekbrand writes: This seems like a mistake, since the description of the package has not changed, and explictly says that the lite version is built without freetype support. Someone requested Xft, I believe, but I have no idea why GTK is in there; that is definitely a mistake. (I don't use -lite myself.) I've been considering just building two packages, one with all useful options and one ideally pared down to close to where we were in etch. There's not much meaningful difference between rxvt-unicode and rxvt-unicode-ml anymore. Do you think this would be good? 1. I have never used anything but rxvt-unicode-lite, so I have no opinion on the differences between rxvt-unicode vs rxvt-unicode-ml. 2. Personally, I have Xft installed on all my systems anyway, so I wouldn't mind too much. But on the other hand, I only use bitmapped fonts in the console, and I think that those who want Xft can install rxvt-unicode. To sum up my opinion, keep three packages, and keep Xft out of -lite. -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? signature.asc Description: Digital signature
Bug#488715: (no subject)
I also have this error: Jun 30 16:03:18 fpunix wdm: X Error of failed request: BadMatch (invalid parameter attributes) Jun 30 16:03:18 fpunix wdm: Major opcode of failed request: 2 (X_ChangeWindowAttributes) Jun 30 16:03:18 fpunix wdm: Serial number of failed request: 2507 Jun 30 16:03:18 fpunix wdm: Current serial number in output stream: 2509 Jun 30 16:03:18 fpunix: Greet: guarenteed_read error, UNMANAGE DISPLAY Jun 30 16:03:18 fpunix: Greet: pipe read error with /usr/bin/wdmLogin Jun 30 16:03:18 fpunix wdm: Server crash rate too high: removing display :0 But only with: DefaultDepth 16 in xorg.conf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446111: xserver-xorg-core: X crashes immediately after wakeup from suspend-to-RAM (APM), but not always :-)
On Sun, Nov 18, 2007 at 06:48:38PM +0100, Brice Goglin wrote: On Wed, Oct 10, 2007 at 11:56:23PM +0200, Brice Goglin wrote: Hans Ekbrand wrote: X crashes seemingly randomly after wakeup from suspend-to-RAM. When it crashes, it seems to happen during wake-up. If if survives wake-up it runs stable until next suspend-cycle. I don't normally use suspend-to-disk, but I tried that once only to test if X would crash, which it did not. Since this computer is old and slow, suspend-to-disk too slow to be usable. Xserver 1.1.1 is very old, we have 1.3 in Lenny/testing and 1.4 in unstable. So your problem might well be gone with a uptodate Xserver. Is there any chance you try upgrading to testing or unstable? Ping? First, now upgrading to testing or unstable is not going to happen, sorry. Secondly, I have learnt that some crashes is related to the presence/absence of an external mouse. When an external mouse is plugged in during sleep, the internal touchpad entry in /proc/bus/input/devices is removed. I have stopped using external mouse completely, which seem to have reduced the number of crashes. One thing I have been thinking about is to define a serial mouse as core pointer, with the idea that the serial mouse would always be present as a device (even when not physically plugged in). Since the crashes are so unpredictable, I have little hope of getting this bug resolved. Close it if you want to. -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you. signature.asc Description: Digital signature
Bug#446111: xserver-xorg-core: X crashes immediately after wakeup from suspend-to-RAM (APM), but not always :-)
Package: xserver-xorg-core Version: 2:1.1.1-21 Severity: normal X crashes seemingly randomly after wakeup from suspend-to-RAM. When it crashes, it seems to happen during wake-up. If if survives wake-up it runs stable until next suspend-cycle. I don't normally use suspend-to-disk, but I tried that once only to test if X would crash, which it did not. Since this computer is old and slow, suspend-to-disk too slow to be usable. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2007-05-26 00:12 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1597964 2007-04-04 03:37 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:12.0 VGA compatible controller: Chips and Technologies F68554 HiQVision (rev a2) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 5614 2007-10-04 10:06 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section Files FontPath/usr/share/fonts/X11/misc FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadvbe # customization 070927 Loadsynaptics EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout se EndSection Section InputDevice Identifier Touchpad Driver synaptics Option Device/dev/psaux Option Protocol auto-dev Option Emulate3Buttons true Option SHMConfig on EndSection Section InputDevice Driversynaptics Identifieralps touchpad OptionCorePointer OptionDevice/dev/input/mice OptionProtocol auto-dev OptionLeftEdge 120 OptionRightEdge 830 OptionTopEdge 120 OptionBottomEdge650 OptionFingerLow 14 OptionFingerHigh15 OptionMaxTapTime180 OptionMaxTapMove110 OptionEmulateMidButtonTime 75 OptionVertScrollDelta 20 OptionHorizScrollDelta 20 OptionMinSpeed 0.3 OptionMaxSpeed 0.75 OptionAccelFactor 0.015 OptionEdgeMotionMinSpeed200 OptionEdgeMotionMaxSpeed200 OptionUpDownScrolling 1 OptionCircularScrolling 1 OptionCircScrollDelta 0.1 OptionCircScrollTrigger 2 EndSection Section InputDevice Identifier Configured Mouse Driver mouse # Option AlwaysCore Option Device/dev/input/mice Option Protocol ImPS/2 # Option Emulate3Buttons true EndSection Section Device Identifier Chips and Technologies F68554 HiQVision Driver chips BusID PCI:0:18:0 Option HWcursor Option SuspendHack EndSection Section Monitor Identifier Generic Monitor Option DPMS HorizSync 28-51 VertRefresh 43-60 EndSection Section Screen Identifier Default Screen Device Chips and Technologies F68554 HiQVision Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 1 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display
Bug#425955: libxslt1.1: changed behaviour with undefined variables (from 1.1.15-2 to 1.1.19-1)
Package: libxslt1.1 Version: 1.1.15-2 Severity: important While this system now uses 1.1.15-2, the bug was found in 1.1.19-1. If foo is undefined, the following xsl h3xsl:value-of select=foo //h3 will be transformed into h3 / in 1.1.19-1, while 1.1.15-2 transformed the xsl to h3/h3 See the attached files for a test case. good.xml was output by 1.1.15-2 and bad.xml comes from 1.1.19-1 (in both cases xsltproc was used). -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libxslt1.1 depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libgcrypt111.2.3-2 LGPL Crypto library - runtime libr ii libgpg-error0 1.4-1 library for common error values an ii libxml22.6.27.dfsg-1 GNOME XML library ii zlib1g 1:1.2.3-13compression library - runtime libxslt1.1 recommends no packages. -- no debconf information test.xsl Description: application/xml test.xml Description: application/xml good.xml Description: application/xml bad.xml Description: application/xml
Bug#425955: closed by Mike Hommey [EMAIL PROTECTED] (Re: [xml/sgml-pkgs] Bug#425955: libxslt1.1: changed behaviour with undefined variables (from 1.1.15-2 to 1.1.19-1))
On Fri, May 25, 2007 at 09:03:14AM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report #425955: libxslt1.1: changed behaviour with undefined variables (from 1.1.15-2 to 1.1.19-1), which was filed against the libxslt1.1 package. [...] Please don't file duplicate bugs. Sorry, the email address used to report 425828 was invalid, so I didn't notice that it was accepted by the BTS. Thanks for your explanation of 425828! Kind regards, -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] GPG Fingerprint: 1408 C8D5 1E7D 4C9C C27E 014F 7C2C 872A 7050 614E signature.asc Description: Digital signature
Bug#390432: bug#390432 - still no boot 2.6.18 here
On Mon, Oct 23, 2006 at 10:00:15PM -0700, Brian Morris wrote: On 10/23/06, Benjamin Herrenschmidt [EMAIL PROTECTED] wrote: On Mon, 2006-10-23 at 03:01 -0700, Brian Morris wrote: well i tried again, still same result as ever trying to boot 2.6.18 on my old powerbook. synopsis: bootx hangs after first line welcome to linux, quik goes all the way to VFS: ... unknown block(0,0) (as if there is no initramfs). no floppy drive, so can't try miboot. Quik can load an initrd at all ? I don't remember... works fine with 2.6.15-1, if modules=dep is set in etc/initramfs-tools/initramfs.conf. Me too. Works with yaird too, if I recall correctly. [...] quik is quik, it boots faster and runs faster, it would be much better if i could use it. but it acts like it can't see the ram disk initrd. Quik handles initrd well. There seems to be a problem with kernels 2.6.15 and initrd on oldworld. I managed to boot a customized 2.6.18 with the ide-drivers builtin with quick, but the official debian kernels fails to find root fs (as if the kernel does not find the ramdisk). I reported bug#366620 which is now closed, but patch that closed the bug didn't work on my performa 5400. #390432 seems to be a continuation of the same problem. On a possibly unrelated matter, the current (2006-10-24) set of miboot-floppies (http://people.debian.org/~wouter/d-i/powerpc-miboot/daily/powerpc/floppy/) also fails to load the initrd: RAMDISK: Compressed image found at block 0 No filesystem could mount root, tried: cramfs Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(1,0) The miboot-floppies of beta3 (2006-08-04) boots to debian-installer sucessfully with a 2.6.16 kernel and initrd (on cramfs). So 2.6.16 can load the initrd on oldworld macs, even though the official debian kernels 2.6.15 always has failed on my box (performa 5400, with 24 Mb ram). -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] GnuPG key: 1024D/7050614E Fingerprint: 1408 C8D5 1E7D 4C9C C27E 014F 7C2C 872A 7050 614E Learn about secure email at http://www.gnupg.org signature.asc Description: Digital signature
Bug#366620: kernel-image-2.6.16-2 on oldworld (success with a small change in config)
On Fri, Sep 08, 2006 at 03:32:25PM +0200, Sven Luther wrote:
On Fri, Sep 08, 2006 at 03:20:58PM +0200, Hans Ekbrand wrote:
Hi!
Hi, please make sure you CC debian-kernel too on issues like this.
Bug #366620 is against linux-image-2.6.16-2-powerpc, my post was a
follow up to [EMAIL PROTECTED] CC:ed to debian-powerpc.
The official debian kernels for powerpc stopped working for me with
2.6.16 (2.6.15 works fine). The 2.6.16 ones fail to mount root fs at
boot, which I have reported in bug #366620
I compiled my own 2.6.16 with a minimal change in .config, and that
was it, 2.6.16 now boots on my oldworld mac.
The needed change in config was the following: (diff against
./boot/config-2.6.16-2-powerpc in the package
linux-image-2.6.16-2-powerpc_2.6.16-18_powerpc.deb)
4c4
# Sat Aug 19 00:42:57 2006
---
# Fri Sep 8 09:14:38 2006
772c772
CONFIG_BLK_DEV_IDEDISK=m
---
CONFIG_BLK_DEV_IDEDISK=y
2317c2317
CONFIG_EXT2_FS=m
---
CONFIG_EXT2_FS=y
2328c2328
CONFIG_FS_MBCACHE=m
---
CONFIG_FS_MBCACHE=y
I think this shows that there is some problem with loading the proper
modules for ide and ext2 from the initrd. As stated in the bugreport
of #366620 I have tried both yaird and the other initrd creator.
[...]
Will you consider appling this patch to the config? While it is not
the right solution in the long term, it would make oldworld macs run
with official debian kernels again (at least the ones with
IDE-drives).
No, please get the ramdisk creator packages to get fixed for this one, if it
is that the issue.
I don't know what to belive anymore, I have tested both mkinitramfs
and yaird (their previous and current versions). I have inspected the
initrds that they produce and the module for ide, ide-disk is
included.
Also, can you please try the 2.6.18-rc6 packages from :
http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/
and see if your problem persists there.
Yes the problem persists. But 2.6.18-rc6 gives a clearer error message at boot.
Here is the output at boot on 2.6.18-rc6 (failing)
ide0: no intrs for device /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL
PROTECTED], using 13
ide0: Found Apple OHare ATA controller, bus ID 0, irq 13
[...]
hda: QUANTUM FIREBALL_TM1700A, ATA DISK drive
hda: Enabling Multiword DMA 2
ide0: Disabled unable to get IRQ 13.
ide0: failed to initialize IDE interface
[...]
VFS: Cannot open root device hda5 or unknown-block(0,0)
* Here is the output of a successful boot (with 2.6.16) *
ide0: no intrs for device /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL
PROTECTED], using 13
ide0: Found Apple OHare ATA controller, bus ID 0, irq 13
Probing IDE interface ide0...
[...]
hda: QUANTUM FIREBALL_TM1700A, ATA DISK drive
hda: Enabling MultiWord DMA 2
ide0 at 0xc2016000-0xc2016007,0xc2016160 on irq 13
hda: max request size: 128KiB
hda: 3335472 sectors (1707 MB) w/76KiB Cache, CHS=3309/16/63, DMA
hda: [mac] hda1 hda2 hda3 hda4 hda5 hda6 hda7
* Here is the output of yaird, looks OK *
# yaird --verbose --output=/boot/myyaird.img 2.6.18-rc6-powerpc
yaird: goal: template, prologue (/etc/yaird/Default.cfg:52)
yaird: action: prologue, {}
yaird: goal: module, fbcon (/etc/yaird/Default.cfg:56)
yaird: goal: input, -- (/etc/yaird/Default.cfg:73)
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action: insmod,
/lib/modules/2.6.18-rc6-powerpc/kernel/drivers/input/evdev.ko {optionList=-- }
yaird: goal: resume, -- (/etc/yaird/Default.cfg:143)
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:157)
yaird: action: insmod,
/lib/modules/2.6.18-rc6-powerpc/kernel/drivers/ide/ide-disk.ko {optionList=-- }
yaird: hardware: completed
pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda5 {sysname=hda/hda5 }
yaird: action: insmod, /lib/modules/2.6.18-rc6-powerpc/kernel/fs/mbcache.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.18-rc6-powerpc/kernel/fs/ext2/ext2.ko
{optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda5 fsType=ext2 isRoot=1 options=-o
'errors=remount-ro' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:170)
yaird: action: postlude, {}
#
--
Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED]
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
signature.asc
Description: Digital signature
Bug#366620: kernel-image-2.6.16-2 on oldworld (success with a small change in config)
Hi! The official debian kernels for powerpc stopped working for me with 2.6.16 (2.6.15 works fine). The 2.6.16 ones fail to mount root fs at boot, which I have reported in bug #366620 I compiled my own 2.6.16 with a minimal change in .config, and that was it, 2.6.16 now boots on my oldworld mac. The needed change in config was the following: (diff against ./boot/config-2.6.16-2-powerpc in the package linux-image-2.6.16-2-powerpc_2.6.16-18_powerpc.deb) 4c4 # Sat Aug 19 00:42:57 2006 --- # Fri Sep 8 09:14:38 2006 772c772 CONFIG_BLK_DEV_IDEDISK=m --- CONFIG_BLK_DEV_IDEDISK=y 2317c2317 CONFIG_EXT2_FS=m --- CONFIG_EXT2_FS=y 2328c2328 CONFIG_FS_MBCACHE=m --- CONFIG_FS_MBCACHE=y I think this shows that there is some problem with loading the proper modules for ide and ext2 from the initrd. As stated in the bugreport of #366620 I have tried both yaird and the other initrd creator. I don't know about the FS_MBCACHE=y thing, that must have been set automatically. Will you consider appling this patch to the config? While it is not the right solution in the long term, it would make oldworld macs run with official debian kernels again (at least the ones with IDE-drives). -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] GnuPG key: 1024D/7050614E Fingerprint: 1408 C8D5 1E7D 4C9C C27E 014F 7C2C 872A 7050 614E Learn about secure email at http://www.gnupg.org signature.asc Description: Digital signature
Bug#366620: initramfs-tools: 2.6.16-1-powerpc fails to mount rootfs, 2.6.15-1-powerpc works
On Wed, May 10, 2006 at 09:42:28AM +0200, Hans Ekbrand wrote: On Wed, May 10, 2006 at 07:48:42AM +0200, Sven Luther wrote: On Wed, May 10, 2006 at 12:55:39AM +0200, maximilian attems wrote: tags 366620 moreinfo stop hda: Quantum Fireball_tm1700A, ATA Disk drive hda: Enabling MultiWord DMA 2 ide0 at 0xc2016000-0x2016007,0xc2016160 on ir1q 13 [...] VFS: Cannot open root device hda5 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0) (0) Rebooting in 180 seconds... I miss the partition enumeration, it seems like the kernel does not see the partitions on the harddisk. I tried yaird today. No luck same error message. Also tried the installer floppies with 2.6.16 from here: http://people.debian.org/~cjwatson/d-i/powerpc-miboot/2006-05-13/powerpc/floppy/boot.img and it booted. The installer never detected the disk correctly though. So it might be some kernel problem with ide disks on powerpc. -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you. signature.asc Description: Digital signature
Bug#366620: initramfs-tools: 2.6.16-1-powerpc fails to mount rootfs, 2.6.15-1-powerpc works
On Mon, May 15, 2006 at 03:41:04PM +0200, Sven Luther wrote: On Mon, May 15, 2006 at 12:33:18PM +0200, Hans Ekbrand wrote: On Wed, May 10, 2006 at 09:42:28AM +0200, Hans Ekbrand wrote: On Wed, May 10, 2006 at 07:48:42AM +0200, Sven Luther wrote: On Wed, May 10, 2006 at 12:55:39AM +0200, maximilian attems wrote: tags 366620 moreinfo stop hda: Quantum Fireball_tm1700A, ATA Disk drive hda: Enabling MultiWord DMA 2 ide0 at 0xc2016000-0x2016007,0xc2016160 on ir1q 13 [...] VFS: Cannot open root device hda5 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0) (0) Rebooting in 180 seconds... I miss the partition enumeration, it seems like the kernel does not see the partitions on the harddisk. I tried yaird today. No luck same error message. Also tried the installer floppies with 2.6.16 from here: http://people.debian.org/~cjwatson/d-i/powerpc-miboot/2006-05-13/powerpc/floppy/boot.img and it booted. The installer never detected the disk correctly though. So it might be some kernel problem with ide disks on powerpc. Mmm, we need to investigate this. The boot floppy is another kind of kernel config though. Given that neither yaird nor initramfs-tools produced a working initrd, should this bug be moved to the linux-image package? Can you provide your /proc/cpuinfo and /proc/device-tree content ? as well as lspci and lspci -n output ? [Sven, considering the unsympathetic attitude to you of some debian-developers, and even the project leader, I want to take this opportunity and express my gratitude and respect for the work you put into the powerpc port of Debian. Thanks Sven!] [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 cpu : 603ev clock : 160MHz revision: 2.1 (pvr 0007 0201) bogomips: 105.98 machine : Power Macintosh motherboard : AAPL,e407 MacRISC detected as : 35 (Alchemy) pmac flags : memory : 24MB pmac-generation : OldWorld [EMAIL PROTECTED]:~$ [EMAIL PROTECTED]:~$ lspci :00:0b.0 Host bridge: Apple Computer Inc. Bandit PowerPC host bridge (rev 03) :00:10.0 ff00: Apple Computer Inc. O'Hare I/O (rev 01) :00:11.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] (rev 21) [EMAIL PROTECTED]:~$ [EMAIL PROTECTED]:~$ lspci -n :00:0b.0 0600: 106b:0001 (rev 03) :00:10.0 ff00: 106b:0007 (rev 01) :00:11.0 0200: 1011:0014 (rev 21) [EMAIL PROTECTED]:~$ /proc/device-tree: #address-cells #size-cells AAPL,[EMAIL PROTECTED] AAPL,cpu-id PowerPC,[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] clock-frequency compatible linux,phandle [EMAIL PROTECTED] model name [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] pci-OF-bus-map [EMAIL PROTECTED] /proc/device-tree/AAPL,[EMAIL PROTECTED]: device_type linux,phandle name reg /proc/device-tree/PowerPC,[EMAIL PROTECTED]: available clock-frequency cpu-version d-cache-block-size d-cache-sets d-cache-size device_type existing i-cache-block-size i-cache-sets i-cache-size linux,phandle name reg reservation-granularity timebase-frequency tlb-sets tlb-size translations /proc/device-tree/[EMAIL PROTECTED]: ata ata-int fd kbd linux,phandle mouse name pci1 screen scsi scsi-int ttya ttyb /proc/device-tree/[EMAIL PROTECTED]: #address-cells #size-cells AAPL,interrupts bus-range clock-frequency device_type linux,phandle model name [EMAIL PROTECTED] pci1011,[EMAIL PROTECTED] pci106b,[EMAIL PROTECTED] ranges reg slot-names /proc/device-tree/[EMAIL PROTECTED]/[EMAIL PROTECTED]: #address-cells #size-cells [EMAIL PROTECTED] assigned-addresses [EMAIL PROTECTED] class-code device-id device_type devsel-speed [EMAIL PROTECTED] linux,phandle max-latency [EMAIL PROTECTED] min-grant model name [EMAIL PROTECTED] ranges reg revision-id [EMAIL PROTECTED] vendor-id [EMAIL PROTECTED] /proc/device-tree/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: AAPL,connector [EMAIL PROTECTED],0 device_type linux,phandle name reg /proc/device-tree/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0: device_type linux,phandle name /proc/device-tree/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: AAPL,interrupts device_type linux,phandle name reg /proc/device-tree/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: #address-cells [EMAIL PROTECTED] [EMAIL PROTECTED] device_type linux,phandle name ranges reg /proc/device-tree/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: AAPL,connector AAPL,interrupts device_type linux,phandle name reg /proc/device-tree/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: AAPL,connector AAPL,interrupts device_type linux,phandle name reg /proc/device-tree/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: AAPL,connector AAPL,interrupts
Bug#366620: initramfs-tools: 2.6.16-1-powerpc fails to mount rootfs, 2.6.15-1-powerpc works
On Wed, May 10, 2006 at 07:48:42AM +0200, Sven Luther wrote: On Wed, May 10, 2006 at 12:55:39AM +0200, maximilian attems wrote: tags 366620 moreinfo stop On Tue, May 09, 2006 at 11:54:24PM +0200, Hans Ekbrand wrote: Package: initramfs-tools Version: 0.60 Severity: important This might be a bug in the kernel or udev or something else, but failure to mount root fs smells like an initrd problem to me. Bootloader: quik, with ramdisk_size 8192 (even tested 16384, with no luck) Rootfs: ext2 on ide Module for the harddisk: lsmod says ide_disk on 2.6.15, but the module is called ide-disk.ko and that module is present in booth the working initrd.img (2.6.15-1-powerpc) and the non-working (2.6.16-1-powerpc). ext2.ko also present in the initrd in booth initrds. Debuging is problematic on this box since I don't have a working serial console, nor can I interact with the bootloader via the keyboard, so If a kernel+initrd doesn't work, I have to boot from the woody installation floppy-disks and rescue from a shell in the installation program. you didn't tell the error message? hda: Quantum Fireball_tm1700A, ATA Disk drive hda: Enabling MultiWord DMA 2 ide0 at 0xc2016000-0x2016007,0xc2016160 on ir1q 13 mice: NET: IP route TCP TCP TCP: TCP TCP NET: NET: VFS: Cannot open root device hda5 or unknown-block(0,0) Please append a correct root= boot option Kernel panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0) (0) Rebooting in 180 seconds... I miss the partition enumeration, it seems like the kernel does not see the partitions on the harddisk. what mkvmlinuz version are you using? This is probably (not 100% sure though) an old-world powermac, probably booted by quik or bootx. In both cases, mkvmlinuz is not used, or at least its scripts are silently skipped. Sorry for leaving out cpuinfo! You are correct Sven, it's an old-world powermac (performa 5400) $ cat /proc/cpuinfo processor : 0 cpu : 603ev clock : 160MHz revision: 2.1 (pvr 0007 0201) bogomips: 105.98 machine : Power Macintosh motherboard : AAPL,e407 MacRISC detected as : 35 (Alchemy) pmac flags : memory : 24MB pmac-generation : OldWorld $ -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] GnuPG key: 1024D/7050614E Fingerprint: 1408 C8D5 1E7D 4C9C C27E 014F 7C2C 872A 7050 614E Learn about secure email at http://www.gnupg.org signature.asc Description: Digital signature
Bug#362556: xserver-xorg-core: XkbModel macintosh - XkbModel macintosh_vndr
Package: xserver-xorg-core Version: 1:1.0.2-7 Followup-For: Bug #362556 xdm stopped accepting normal english characters as input unless I modified /etc/X11/xorg.conf like this: -XkbModel macintosh +XkbModel macintosh_vndr However, numbers and the special swedish characters (I can't type them in this terminal though :-) did work Kind regards, Hans Ekbrand -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages xserver-xorg-core depends on: ii libc6 2.3.6-7GNU C Library: Shared libraries ii libfontenc1 1:1.0.1-5 X11 font encoding library ii libgcc1 1:4.1.0-2 GCC support library ii libxau6 1:1.0.0-3 X11 authorisation library ii libxdmcp6 1:1.0.0-4 X11 Display Manager Control Protoc ii libxfont1 1:1.0.0-4 X11 font rasterisation library ii x11-common1:7.0.15 X Window System (X.Org) infrastruc ii xserver-xorg-input-al 1:7.0.15 the X.Org X server -- input driver ii xserver-xorg-input-ev 1:1.0.0.5-2X.Org X server -- evdev input driv ii xserver-xorg-input-kb 1:1.0.1.3-2X.Org X server -- keyboard input d ii xserver-xorg-input-mo 1:1.0.4-2 X.Org X server -- mouse input driv ii xserver-xorg-video-al 1:7.0.15 the X.Org X server -- output drive ii xserver-xorg-video-at 1:6.5.8.0-1X.Org X server -- ATI display driv ii xserver-xorg-video-ch 1:1.0.1.3-3X.Org X server -- Chips display dr ii xserver-xorg-video-fb 1:0.1.0.5-2X.Org X server -- fbdev display dr ii xserver-xorg-video-gl 1:1.0.1.3-3X.Org X server -- Glint display dr ii xserver-xorg-video-im 1:1.0.0.5-2X.Org X server -- IMSTT display dr ii xserver-xorg-video-mg 1:1.2.1.3.dfsg.1-2 X.Org X server -- MGA display driv ii xserver-xorg-video-nv 1:1.0.1.5-2X.Org X server -- NV display drive ii xserver-xorg-video-s3 1:1.8.6.5-2X.Org X server -- S3 ViRGE display ii xserver-xorg-video-sa 1:2.0.2.3-4X.Org X server -- Savage display d ii xserver-xorg-video-si 1:0.8.1.3-2X.Org X server -- SiS display driv ii xserver-xorg-video-si 1:0.7.1.3-2X.Org X server -- SiS USB display ii xserver-xorg-video-td 1:1.1.1.3-3X.Org X server -- tdfx display dri ii xserver-xorg-video-tr 1:1.0.1.2-2X.Org X server -- Trident display ii xserver-xorg-video-vg 1:4.0.0.5-2X.Org X server -- VGA display driv ii zlib1g1:1.2.3-11 compression library - runtime Versions of packages xserver-xorg-core recommends: pn xkeyboard-config none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366615: xkb-data: Requires XkbModel to be macintosh_vndr rather than macintosh or won't accept plain english characters
Package: xkb-data Version: 0.8-5 Severity: important Tags: l10n Here is an excerpt from my xorg.conf Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard # Option XkbRules xfree86 Option XkbRules xorg Option XkbModel macintosh_vndr Option XkbLayout se Option XkbOptionsaltwin:meta_alt EndSection With XkbModel set to macintosh instead of macintosh_vndr xdm would not accept plain english characters (it would only accept numbers and non-english characters, i.e. the special swedish characters that I cannot type in this terminal). -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366620: initramfs-tools: 2.6.16-1-powerpc fails to mount rootfs, 2.6.15-1-powerpc works
Package: initramfs-tools Version: 0.60 Severity: important This might be a bug in the kernel or udev or something else, but failure to mount root fs smells like an initrd problem to me. Bootloader: quik, with ramdisk_size 8192 (even tested 16384, with no luck) Rootfs: ext2 on ide Module for the harddisk: lsmod says ide_disk on 2.6.15, but the module is called ide-disk.ko and that module is present in booth the working initrd.img (2.6.15-1-powerpc) and the non-working (2.6.16-1-powerpc). ext2.ko also present in the initrd in booth initrds. Debuging is problematic on this box since I don't have a working serial console, nor can I interact with the bootloader via the keyboard, so If a kernel+initrd doesn't work, I have to boot from the woody installation floppy-disks and rescue from a shell in the installation program. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages initramfs-tools depends on: ii busybox 1:1.01-4 Tiny utilities for small and embed ii cpio 2.6-11 GNU cpio -- a program to manage ar ii klibc-utils 1.3.11-1 small statically-linked utilities ii module-init-tools 3.2.2-2tools for managing Linux kernel mo ii udev 0.091-1/dev/ and hotplug management daemo initramfs-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351909: Serial port gives this output:
This is what I get on the serial console: RESETing to change Configuration! vector: 300 at pc=c010e0b4, lr=c010e308 msr = 9032, sp = c034ba60 [c034b9b0] dar = b4, dsisr = 2200 current = c0304070, pid = 154, comm = kadbprobe mon Is this a working prompt? Can I actually debug something here? What arguments are available? -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] GnuPG key: 1024D/7050614E Fingerprint: 1408 C8D5 1E7D 4C9C C27E 014F 7C2C 872A 7050 614E Learn about secure email at http://www.gnupg.org signature.asc Description: Digital signature
Bug#351909: 2.6.14 boots, but not 2.6.15
Package: linux-image-2.6-powerpc-miboot Severity: grave I tried the following images on a performa 5400. This box normally runs sid and has no problem with any 2.6.15-kernel when booted by quik. So the problem is specific to miboot and 2.6.15. http://people.debian.org/~luther/d-i/sid/images/2005-12-28/powerpc/floppy/boot.img 2.6.14 Works! http://people.debian.org/~luther/d-i/sid/images/2005-01-10/powerpc/floppy/boot.img 2.6.14 Works! http://people.debian.org/~luther/d-i/sid/images/2006-01-16/powerpc/floppy/boot.img 2.6.15 Hangs also, now with ide0: Found Apple Ohare ATA controller, bus ID 0, irq13 ADB keyboard at 2, handler set to 3 Serial port locked ON by debugger! ABD HID on ID 3 not yet registered http://people.debian.org/~luther/d-i/sid/images/2006-01-25/powerpc/floppy/boot.img 2.6.15 This kernel hangs with ide0: Found Apple Ohare ATA controller, bus ID 0, irq13 ADB keyboard at 2, handler set to 3 Serial port locked ON by debugger! http://people.debian.org/~luther/d-i/sid/images/2006-02-07/powerpc/floppy/boot.img 2.6.15 This kernel hangs with same as the 2006-01-25 So to sum up: 2.6.14 works, but 2.6.15 does not. Kind regards, Hans Ekbrand -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351909: 2.6.14 boots, but not 2.6.15
On Wed, Feb 08, 2006 at 01:53:16PM +0100, Sven Luther wrote: severity 351909 important retitle 351909 [powerpc,oldworld] 2.6.14 boots, but not 2.6.15 reassign 351909 linux-2.6 thanks Thanks Hans for your report, i lowered the severity since we are about to move 2.6.15 to testing, and oldworld has been a not fully working subarch previously, but this does not mean we don't want to fix this for etch. Of course, I hesitated long before setting it to grave, but it did match the description of grave :-) -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you. signature.asc Description: Digital signature
Bug#345911: Behaviour confirmed
$ gpg --import /usr/share/keyrings/debian-keyring.gpg [...] gpg: key 128287E8: public key Dafydd Harries [EMAIL PROTECTED] imported gpg: key 54AD21B5: public key Eric Warmenhoven [EMAIL PROTECTED] imported gpg: key 90267086: public key Marc Dequnes (Duck) [EMAIL PROTECTED] imported gpg: 900 keys processed so far gpg: key 39A8CCE2: public key Eugeniy Meshcheryakov [EMAIL PROTECTED] imported gpg: key F2833C93: public key Eric Evans [EMAIL PROTECTED] imported gpg: key 1E880A84: public key Frans Pop (Debian) [EMAIL PROTECTED] imported gpg: Total number processed: 903 gpg: imported: 903 (RSA: 11) Killed $ This happens both with the version in unstable 1.4.2-2 and and the sarge version of gnupg 1.4.1-1. If this behaviour is expected due to the number of keys in the debian keyring, a note in README.gz should be added. -- Linux samir 2.6.8-2-386 #1 Tue Aug 16 12:46:35 UTC 2005 i586 GNU/Linux Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#349953: foomatic-filters-ppds: Lack of support for Samsung-ML-2010
Package: foomatic-filters-ppds Version: 20050430-1 Severity: wishlist Tags: patch Attached is a ppd, based on Samsung-ML-4500-gdi.ppd, that works perfectly with Samsung-ML-2010. Changelog included. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (999, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.8-2-386 Locale: LANG=C, LC_CTYPE=sv_SE (charmap=ISO-8859-1) Versions of packages foomatic-filters-ppds depends on: ii foomatic-db-engine 3.0.2-20050403-1 linuxprinting.org printer support -- no debconf information *PPD-Adobe: 4.3 *% *% For information on using this, and to obtain the required backend *% script, consult http://www.linuxprinting.org/ *% *% This file is published under the GNU General Public License *% *% PPD-O-MATIC (3.0.0 or newer) generated this PPD file. It is for use with *% all programs and environments which use PPD files for dealing with *% printer capability information. The printer must be configured with the *% foomatic-rip backend filter script of Foomatic 3.0.0 or newer. This *% file and foomatic-rip work together to support PPD-controlled printer *% driver option access with arbitrary free software printer drivers and *% printing spoolers. *% *% This file is based on Samsung-ML-4500-gdi.ppd. *% Adjustments done for the ML-2010 by Hans Ekbrand [EMAIL PROTECTED] *% 2006-01-26 *% - added the Margins section (see that last 5 lines) with values appropriate *% for the Samsung-ML-2010. Values from trial-and-error and some help from *% the aliginmargins program from www.linuxprinting.org. I'm not quite happy *% with calling the proper definition of the margins Custom though. *% - changed *Name: and *FoomaticIDs: from Samsung ML-4500 to Samsung ML-2010 *% - removed the 300x300dpi resolution since it did not work. *% *FormatVersion: 4.3 *FileVersion: 1.1 *LanguageVersion: English *LanguageEncoding: ISOLatin1 *PCFileName:ML2010.PPD *Manufacturer: Samsung *Product: (ML-2010) *cupsVersion: 1.1 *cupsManualCopies: True *cupsModelNumber: 2 *cupsFilter:application/vnd.cups-postscript 0 foomatic-rip *%pprRIP:foomatic-rip other *ModelName: Samsung ML-2010 *ShortNickName: Samsung ML-2010 gdi *NickName: Samsung ML-2010 Foomatic/gdi (recommended) *PSVersion: (3010.000) 550 *PSVersion: (3010.000) 651 *PSVersion: (3010.000) 652 *PSVersion: (3010.000) 653 *PSVersion: (3010.000) 704 *PSVersion: (3010.000) 705 *PSVersion: (3010.000) 800 *LanguageLevel: 3 *ColorDevice: False *DefaultColorSpace: Gray *FileSystem:False *Throughput:1 *LandscapeOrientation: Plus90 *TTRasterizer: Type42 *VariablePaperSize: False *FoomaticIDs: Samsung-ML-2010 gdi *FoomaticRIPCommandLine: gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPA USE -sDEVICE=gdi%A%Z -sOutputFile=- - | perl -p -e apos;%Eapos; *End *OpenGroup: General/General *OpenUI *PageSize/Page Size: PickOne *FoomaticRIPOption PageSize: enum Composite A *OrderDependency: 99 AnySetup *PageSize *DefaultPageSize: A4 *PageSize Letter/Letter: %% FoomaticRIPOptionSetting: PageSize=Letter *FoomaticRIPOptionSetting PageSize=Letter: PageSizePS=Letter PageSize JCL=Letter *End *PageSize A4/A4: %% FoomaticRIPOptionSetting: PageSize=A4 *FoomaticRIPOptionSetting PageSize=A4: PageSizePS=A4 PageSizeJCL=A4 *PageSize A5/A5: %% FoomaticRIPOptionSetting: PageSize=A5 *FoomaticRIPOptionSetting PageSize=A5: PageSizePS=A5 PageSizeJCL=A5 *PageSize A6/A6: %% FoomaticRIPOptionSetting: PageSize=A6 *FoomaticRIPOptionSetting PageSize=A6: PageSizePS=A6 PageSizeJCL=A6 *PageSize B5JIS/B5 (JIS): %% FoomaticRIPOptionSetting: PageSize=B5JIS *FoomaticRIPOptionSetting PageSize=B5JIS: PageSizePS=B5JIS PageSizeJC L=B5JIS *End *PageSize Env10/Envelope #10: %% FoomaticRIPOptionSetting: PageSize=Env10 *FoomaticRIPOptionSetting PageSize=Env10: PageSizePS=Env10 PageSizeJC L=Env10 *End *PageSize EnvB5/Envelope B5: %% FoomaticRIPOptionSetting: PageSize=EnvB5 *FoomaticRIPOptionSetting PageSize=EnvB5: PageSizePS=EnvB5 PageSizeJC L=EnvB5 *End *PageSize EnvC5/Envelope C5: %% FoomaticRIPOptionSetting: PageSize=EnvC5 *FoomaticRIPOptionSetting PageSize=EnvC5: PageSizePS=EnvC5 PageSizeJC L=EnvC5 *End *PageSize EnvC6/Envelope C6: %% FoomaticRIPOptionSetting: PageSize=EnvC6 *FoomaticRIPOptionSetting PageSize=EnvC6: PageSizePS=EnvC6 PageSizeJC L=EnvC6 *End *PageSize EnvDL/Envelope DL: %% FoomaticRIPOptionSetting: PageSize=EnvDL *FoomaticRIPOptionSetting PageSize=EnvDL: PageSizePS=EnvDL PageSizeJC L=EnvDL *End *PageSize EnvMonarch/Envelope Monarch: %% FoomaticRIPOptionSetting: PageSize=EnvMonarch *FoomaticRIPOptionSetting PageSize=EnvMonarch: PageSizePS=EnvMonarch PageSizeJCL=EnvMonarch *End *PageSize Executive/Executive: %% FoomaticRIPOptionSetting: PageSize=Executive *FoomaticRIPOptionSetting PageSize=Executive: PageSizePS=Executive Pa geSizeJCL=Executive *End *PageSize Folio/Folio: %% FoomaticRIPOptionSetting: PageSize=Folio *FoomaticRIPOptionSetting PageSize=Folio: PageSizePS=Folio
Bug#349471: installing autoconf and gs-* solves the problem
As pointed out in private mail by Frank Küster, the problem is that auctext have undocumented dependencies on autconf and gs. Workaround: # apt-get install autoconf gs-gpl Thanks Frank! -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] GnuPG key: 1024D/7050614E Fingerprint: 1408 C8D5 1E7D 4C9C C27E 014F 7C2C 872A 7050 614E Learn about secure email at http://www.gnupg.org signature.asc Description: Digital signature
Bug#349471: auctex: post-installation script returned error exit status 1
Package: auctex Version: 11.81-2 Severity: normal Post-install fails with the following: # dpkg --configure -a Setting up auctex (11.81-2) ... install/auctex: Setting up for emacs21... emacs-package-install: /usr/lib/emacsen-common/packages/install/auctex emacs21 emacs21 failed at /usr/lib/emacsen-common/emacs-package-install line 30, TSORT line 1. dpkg: error processing auctex (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: auctex # -- Package-specific info: Content of '/usr/share/emacs/site-lisp/auctex/' 7cee6454910f8adc4571640e8dc3ee34 /usr/share/emacs/site-lisp/auctex/ChangeLog f7a3ed04d3d4ff57cf4569a6f47beaed /usr/share/emacs/site-lisp/auctex/Makefile 1adbb0b93e84e1f971d9292bbe1023a0 /usr/share/emacs/site-lisp/auctex/Makefile.in 6befd3a886581f9365133a82b43108b5 /usr/share/emacs/site-lisp/auctex/aclocal.m4 c515b501a8d5009537edfb0348d3f14e /usr/share/emacs/site-lisp/auctex/auctex.el e23e60e9de6051db5156aecaaaea11e7 /usr/share/emacs/site-lisp/auctex/auctex.el.in f811bf58aa85b11fae015df74262bd31 /usr/share/emacs/site-lisp/auctex/bib-cite.el 63d7a2ef4addca2bb78e986c5b7ec053 /usr/share/emacs/site-lisp/auctex/confdefs.h a05252af5c783d14593779080f75c919 /usr/share/emacs/site-lisp/auctex/config.log 04cef037ff6454ef7adb0c8b3f240575 /usr/share/emacs/site-lisp/auctex/config.status 46e1b083f042b1953fe6ab790b5ef880 /usr/share/emacs/site-lisp/auctex/configure dc4fd67520ec1c26cf55d8f8e1886b2a /usr/share/emacs/site-lisp/auctex/configure.ac 5f35c1b2e5570ff4ee4a54f3939500cf /usr/share/emacs/site-lisp/auctex/context-en.el 3a32e69b661cffb7267c505d4cf634fb /usr/share/emacs/site-lisp/auctex/context-nl.el c52650a818aa2f21adfdc434b6af1764 /usr/share/emacs/site-lisp/auctex/context.el 2b11f4f8c3a4189bf7cc8fec5a51e8c0 /usr/share/emacs/site-lisp/auctex/doc/Makefile 2b11f4f8c3a4189bf7cc8fec5a51e8c0 /usr/share/emacs/site-lisp/auctex/doc/Makefile.in 35fe14d906f0bf1acf3af9fb41833630 /usr/share/emacs/site-lisp/auctex/font-latex.el f176261b5a5511cbe1401ee72ffb8947 /usr/share/emacs/site-lisp/auctex/images/amstex.xpm d33121019448617a3ad3bcafdeb8db40 /usr/share/emacs/site-lisp/auctex/images/bibtex.xpm 1a43d6438010bceb374ab0a5f2bd05a8 /usr/share/emacs/site-lisp/auctex/images/dropdown.xpm 41f1ae0341ae2e307d92a7b8b815f868 /usr/share/emacs/site-lisp/auctex/images/dvipdf.xpm 2e4b8669b0168f32247411be3f999437 /usr/share/emacs/site-lisp/auctex/images/dvips.xpm 55f7600cadc3a209e94bacf6bbc42a7c /usr/share/emacs/site-lisp/auctex/images/error.xpm c29ad797273fd27201a40bd939a95fe0 /usr/share/emacs/site-lisp/auctex/images/exec.xpm 79b958849511c67d6b13ef9f5b3673e8 /usr/share/emacs/site-lisp/auctex/images/execbibtex.xpm a8570e26e9f96b6f527cdbe218d6c55f /usr/share/emacs/site-lisp/auctex/images/execdvips.xpm e647bc601aef2dc71b134a989df1adff /usr/share/emacs/site-lisp/auctex/images/execerror.xpm 4610ec6133f89ceb441c43dfee077361 /usr/share/emacs/site-lisp/auctex/images/execpdftex.xpm c9cd1fc9fe4fd122cbf900fae654a67b /usr/share/emacs/site-lisp/auctex/images/exectex.xpm 6a6b9af945d4735f048ea8e475f8d9b8 /usr/share/emacs/site-lisp/auctex/images/execviewdvi.xpm 466466f6d1867510b058a9c184ffce5d /usr/share/emacs/site-lisp/auctex/images/execviewpdf.xpm 39d8ccaffb40b0c118e000f45272db05 /usr/share/emacs/site-lisp/auctex/images/execviewps.xpm 6767e2583c668dcb47495197b9e8cb65 /usr/share/emacs/site-lisp/auctex/images/gv.xpm ff9c61ef5148a0cacd5422d7c0d99396 /usr/share/emacs/site-lisp/auctex/images/jumpdvi.xpm ece6608586b591f50f20d17cdb316a1c /usr/share/emacs/site-lisp/auctex/images/ltx-symb-turn-off.xpm b1f10de33dcf1b5ca9ac6155c13683a3 /usr/share/emacs/site-lisp/auctex/images/ltx-symb-turn-on.xpm 44e35faa18ab34f3c13ac3b0082bcc47 /usr/share/emacs/site-lisp/auctex/images/pdftex.xpm 84673eb20ac3be7bf0eb4e84e23e828f /usr/share/emacs/site-lisp/auctex/images/prverr16.xpm 59e6a0dddb00ab16c4209a2e4c6e283d /usr/share/emacs/site-lisp/auctex/images/prverr20.xpm 30dc2ada41625cb24ea459bd62f7386c /usr/share/emacs/site-lisp/auctex/images/prverr24.xbm 225929f8131bdd7b9b8207494a59619a /usr/share/emacs/site-lisp/auctex/images/prverr24.xpm 0dac3d8eb00c902037cc5fa6a03e53e3 /usr/share/emacs/site-lisp/auctex/images/prvtex-cap-up.xpm 40feb30f80d3606f32ba54b57ba18af5 /usr/share/emacs/site-lisp/auctex/images/prvtex12.xbm e1b3c9d6a6eb6fb6f096736cdfc059cf /usr/share/emacs/site-lisp/auctex/images/prvtex12.xpm 32406fc4b893b48d2996c424f61ea238 /usr/share/emacs/site-lisp/auctex/images/prvtex16.xbm cc4101ee6a3ab6a1f4e9991b91b3ff0b /usr/share/emacs/site-lisp/auctex/images/prvtex16.xpm d4dbe057a8d3b2facd61cf7583c1e97c /usr/share/emacs/site-lisp/auctex/images/prvtex20.xpm f25ba1b984b095c9c561e5443f3d77a3 /usr/share/emacs/site-lisp/auctex/images/prvtex24.xbm 28ac0855d853f606dd91e3cfacaa8a14
Bug#344477: debian-installer-manual: outdated information on how to install on oldworld powerpc
Package: debian-installer-manual Version: sarge? Severity: normal Tags: patch Suggestions for new text is attached. Note that I have not tested to build the manual with new text so before you accept it, please do a test build. I am interested in rewriting other parts of the manual too, but I don't know how to checkout just the manual. What is the proper command to do that? kind regards, Hans Ekbrand -- System Information: Debian Release: 3.1 Architecture: i386 (i586) Kernel: Linux 2.6.8-2-386 Locale: LANG=C, LC_CTYPE=sv_SE (charmap=ISO-8859-1) Title: Preparing Files for Hard Disk Booting The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS. A full, pure network installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks. The installer cannot boot from files on an NTFS file system. The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select Get Info for the volume in question. HFS file systems appear as Mac OS Standard, while HFS+ file systems say Mac OS Extended. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download. Different programs are used for hard disk installation system booting, depending on whether the system is a NewWorld or an OldWorld model. Hard disk installer booting using LILO or GRUB This section explains how to add to or even replace an existing linux installation using either LILO or GRUB. At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel. Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to /boot/newinstall/. vmlinuz (kernel binary) initrd.gz (ramdisk image) Finally, to configure the bootloader proceed to . Hard Disk Installer Booting for OldWorld Macs The boot-floppy-hfs floppy uses miBoot to launch Linux installation, but miBoot cannot easily be used for hard disk booting. BootX, launched from MacOS, supports booting from files placed on the hard disk. BootX can also be used to dual-boot MacOS and Linux after your Debian installation is complete. For the Performa 6360 and the Beige G3, it appears that quik cannot make the hard disk bootable. So BootX is required on those models. Download and unstuff the BootX distribution, available from . Use Stuffit Expander to extract it from its archive. Within the package, there is an empty folder called Linux Kernels. Download (or copy from a CD-ROM) vmlinux and initrd.gz from the one the folders in debian/dists//main/installer-/current/images/. The different folders represent different ways of loading the files needed later on in the installation process. If the debian installer should load files from a CD, choose the cdrom folder, if the files should be loaded from harddisk, choose the hd-media folder, if the files should be loaded from the internet, choose the netboot folder. Place vmlinux and initrd.gz in the Linux Kernels folder. Then place the Linux Kernels folder in the active System Folder. Hard Disk Installer Booting for NewWorld Macs NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via yaboot, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. BootX is not supported and must not be used on NewWorld PowerMacs. Copy (not move) the following four files which you downloaded earlier from the Debian archives, onto the root level of your hard drive (this can be accomplished by option-dragging each file to the hard drive icon). vmlinux initrd.gz yaboot yaboot.conf Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS pdisk program, you can use the L command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer. To boot the installer, proceed to .
Bug#344477: more patched files
Since reportbug only allowed me to attach one file, the rest of the patched files comes here. -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you. boot-new.xml Description: application/xml nobootloader.xml Description: application/xml signature.asc Description: Digital signature
Bug#341559: yaird: fails to create initrd
Package: yaird Version: 0.0.11-12 Severity: important This is a Old-world IDE-based Macintosh Performa 5400, running unstable on a 2.6.8-12 kernel. Unpacking linux-image-2.6-powerpc (from .../linux-image-2.6-powerpc_2.6.14-4_powerpc.deb) ... Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Failed to create initrd image. dpkg: error processing linux-image-2.6.14-2-powerpc (--configure): subprocess post-installation script returned error exit status 2 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages yaird depends on: ii cpio 2.6-3 GNU cpio -- a program to manage ar ii dash 0.5.2-7 The Debian Almquist Shell ii libc62.3.5-4 GNU C Library: Shared libraries an ii libhtml-template-perl2.7-1 HTML::Template : A module for usin ii libparse-recdescent-perl 1.94.free-1 Generates recursive-descent parser ii perl 5.8.7-4 Larry Wall's Practical Extraction yaird recommends no packages. -- no debconf information signature.asc Description: Digital signature
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote: On Thu, Dec 01, 2005 at 12:37:23PM +0100, Hans Ekbrand wrote: Package: yaird Version: 0.0.11-12 Severity: important This is a Old-world IDE-based Macintosh Performa 5400, running unstable on a 2.6.8-12 kernel. Hi Hans, ... Do you happen to know exactly which driver is needed for this device ? Do you mean which module to drive this IDE harddisk? Unpacking linux-image-2.6-powerpc (from .../linux-image-2.6-powerpc_2.6.14-4_powerpc.deb) ... Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Could you send us a : find /sys/devices/pci:00/:00:10.0/0.f300:ohare /sys/devices/pci:00/:00:10.0/0.f300:ohare /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0 /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0 /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3 /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Other suitable ramdisk generating tools : /usr/sbin/mkinitramfs. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Failed to create initrd image. dpkg: error processing linux-image-2.6.14-2-powerpc (--configure): -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you. signature.asc Description: Digital signature
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:41:01PM +0100, Maximilian Attems wrote: clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. OK. I thought installing initramfs-tools would suffice, I didn't know that it was an alternativ to yaird, nor that it would not be used by default. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd OK. Now it worked! the initrd was created and the boot successful. -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? signature.asc Description: Digital signature
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote:
On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote:
Could you send us a :
find /sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block
This is probably similar to the problem we had :
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io/0.0002:ata-3/ide1
so instead of ignoring 0.8000:mac-io and 0.0002:ata-3, you need to
ignore 0.f300:ohare and 0.0002:ATA.
So, in /usr/lib/yaird/perl/Hardware.pm, at line 81, you need to copy one of
the two
above lines :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:mac-io$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ata-\d+$!) {
# Apple IDE bus; harmless
}
for your case, maybe something like :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA\d+$!) {
# Apple IDE bus; harmless
}
but i am no perl expert, and may have gotten the exact magic wrong.
OK, I will try that but does not have enough time for the moment.
--
Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED]
Q. What is that strange attachment in this mail?
A. My digital signature, see www.gnupg.org for info on how you could
use it to ensure that this mail is from me and has not been
altered on the way to you.
signature.asc
Description: Digital signature
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote:
On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote:
[...]
find /sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block
This is probably similar to the problem we had :
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io/0.0002:ata-3/ide1
so instead of ignoring 0.8000:mac-io and 0.0002:ata-3, you need to
ignore 0.f300:ohare and 0.0002:ATA.
So, in /usr/lib/yaird/perl/Hardware.pm, at line 81, you need to copy one of
the two
above lines :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:mac-io$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ata-\d+$!) {
# Apple IDE bus; harmless
}
for your case, maybe something like :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA\d+$!) {
# Apple IDE bus; harmless
}
but i am no perl expert, and may have gotten the exact magic wrong.
Attached is a patch that made it match the two problematic lines:
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
With the patch applied, the initrd was successfully created, and the
kernel booted without any problems.
--
Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED]
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
78a79,81
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Another Apple bus; harmless
}
81a85,87
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA$!) {
# Apple IDE bus; harmless
}
signature.asc
Description: Digital signature
Bug#299679: cupsys-client: confusing dependecies
On Wed, Mar 16, 2005 at 02:12:15AM +0100, Achim Bohnet wrote: On Tuesday 15 March 2005 21:07, Hans Ekbrand wrote: Package: cupsys-client Version: 1.1.23-4 Severity: normal A user with limited or none experience of cups, the weak dependency on cupsys is confusing. If I have understood cups correctly, cupsys-client needs a server installed locally, either cupsys or No. Just set in /etc/cups/client.conf ServerName to whereever you cups server is (or set env var CUPS_SERVER). OK, then the rest of my reasonings does not apply. Thanks for making me understand that. I will close the bug. -- Note that I use Debian version 3.1 Linux samir 2.6.9-1-386 #1 Thu Nov 25 02:52:40 EST 2004 i586 GNU/Linux Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] Never trust a message that appears to come from me but is not signed with GPG! It is most likely SPAM or a VIRUS sent by someone who has my adress and got infected. My public key, ID 7050614E, is available from the HKP key servers and here: http://sociologi.cjb.net/~hans/key.txt signature.asc Description: Digital signature
Bug#299679: cupsys-client: confusing dependecies
Package: cupsys-client Version: 1.1.23-4 Severity: normal A user with limited or none experience of cups, the weak dependency on cupsys is confusing. If I have understood cups correctly, cupsys-client needs a server installed locally, either cupsys or lpr(ng), but the neither the package description nor the formal dependecies of cupsys-client reflect this. Cupsys-client has a stronger dependency on cupsys-bsd (recommends) than on cupsys (suggests), I think this is wrong. Citing the Debian policy manual: Recommends This declares a strong, but not absolute, dependency. The Recommends field should list packages that would be found together with this one in all but unusual installations. cupsys-client thus should recommend cupsys. Another approach that I personally would find even better would be to merge the packages cupsys cupsys-client into one, since the potential advantage of combining cupsys-client with lpr seems very small. Kind regards, Hans Ekbrand -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (300, 'testing'), (100, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.9-1-386 Locale: LANG=C, LC_CTYPE=sv_SE (charmap=ISO-8859-1) Versions of packages cupsys-client depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libcupsys2-gnutls10 1.1.23-4 Common UNIX Printing System(tm) - ii zlib1g 1:1.2.2-3compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
