Bug#985635: ghostscript 9.53 produces incorrect output with xelatex and PStricks
This problem is resolved in Debian 12 Bookworm, with the arrival of ghostscript 10.0. The bug should probably be closed. Thank you all for all of your work, Jim McCloskey * Jim McCloskey (mccl...@ucsc.edu) wrote: |> Package: ghostscript |> Version: 9.53~dfsg-2+deb10u4 |> X-Debbugs-Cc: mccl...@ucsc.edu, debian-tex-ma...@lists.debian.org |> Severity: normal |> Tags: upstream |> |> Dear Maintainer, |> |> A LaTeX document which includes a call to PStricks and the pst-jtree package produces correct |> PDF output when compiled with xelatex in Debian buster. Following an upgrade to bullseye, the |> same document compiled in exactly the same way produces incorrect output. ---------- Jim McCloskey mccl...@ucsc.edu Department of Linguistics UC Santa Cruz http://people.ucsc.edu/~mcclosk --
Bug#985635: ghostscript 9.53 produces incorrect output with xelatex and PStricks
Package: ghostscript
Version: 9.53~dfsg-2+deb10u4
X-Debbugs-Cc: mccl...@ucsc.edu, debian-tex-ma...@lists.debian.org
Severity: normal
Tags: upstream
Dear Maintainer,
A LaTeX document which includes a call to PStricks and the pst-jtree package
produces correct
PDF output when compiled with xelatex in Debian buster. Following an upgrade
to bullseye, the
same document compiled in exactly the same way produces incorrect output.
Investigation suggests that the source of the problem was an upgrade to
ghostscript -- as far
as version 9.53. When I downgraded ghostscript to the version in buster
(ghostscript 9.27) and
made no other changes, compiling with xelatex produced correct output. Version
9.52 of
ghostscript is not available in the Debian archive, it seems. But I downloaded
a binary from:
https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/tag/gs952 and
created a symlink
between the 9.52 version in /opt and /usr/bin/gs. This adjustment also led to a
successful
compilation. The problem, then, seems to have been introduced in the transition
from
ghostscript 9.52 to ghostscript 9.53.
The nature of the problem is revealed in the attached files -- one source-file
(tree.tex) was
compiled with xelatex in three different contexts:
- with ghostscript 9.53 in bullseye (tree-gs-9.53.pdf)
- with ghostscript 9.27 in buster (tree-gs-9.27.pdf)
- with ghostscript 9.52 (tree-gs-9.52.pdf)
Under gs-9.53 all of the various labels are incorrectly gathered at the root of
the tree and
are superimposed on one another. Under earlier versions of ghostscript (9.52
and 9.27), the
document is rendered as intended -- with the labels distinct and printed at the
intended nodes.
Thank you for all of your work,
Jim McCloskey
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ghostscript depends on:
ii libc6 2.31-9
ii libgs9 9.27~dfsg-2+deb10u4
Versions of packages ghostscript recommends:
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.5
Versions of packages ghostscript suggests:
pn ghostscript-x
-- no debconf information
\documentclass[12pt]{article}
%%
%% FONTS
%%
\usepackage{textcomp}
\usepackage{fontspec}
\setmainfont[Numbers={OldStyle}]{Linux Libertine}
%%
%%
%\usepackage{pst-all}% makes no difference
\usepackage{pstricks}
\usepackage{pst-jtree}
%%
%%
\begin{document}
{\centering
\vspace*{4\baselineskip}
\jtree[xunit=1.5,yunit=1.5]
\start
{CP}
{C}!a ^ {TM1P}
{TM1} !b ^ {POLP}
{POL} !c ^ {TLOP}
{subj} ^
{TLO} ^ {VceP}
{Vce} ^ {vP}
{\itshape pro ól an nimh}.
\adjoin at !a {\textit{gu-}}.
\adjoin at !b {\textit{-r}} .
\adjoin at !c {\itshape ól-adar} .
\endjtree
}
\end{document}
tree-gs-9.53.pdf
Description: Adobe PDF document
tree-gs-9.27.pdf
Description: Adobe PDF document
tree-gs-9.52.pdf
Description: Adobe PDF document
Bug#864758: libmtp9 regression on upgrade to stretch
Package: libmtp9 Version: 1.1.12-1~bpo8+1 Severity: important Hello, and thanks for all of your work. In jessie with: libmtp-common: 1.1.11-1 libmtp-runtime: 1.1.9-1 libmtp9:1.1.9-1 mtp-tools 1.1.9-1 jmtpfs: 0.5-2 4.8.0-1-amd64 #1 SMP Debian 4.8.7-1 (2016-11-13) x86_64 GNU/Linux I was able to mount both my sailfish phone and my android tablet without problems using: /usr/bin/jmtpfs ~/xoom /usr/bin/jmtpfs ~/jolla Following an upgrade to stretch yielding: libmtp-common: 1.1.13-1 libmtp-runtime: 1.1.13-1 libmtp9:1.1.13-1 mtp-tools 1.1.13-1 jmtpfs: 0.5-2+b2 mounting failed consistently for both the android and the sailfish devices: --- Device 0 (VID=22b8 and PID=70a9) is a Motorola Xoom (MTP+ADB). ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt terminate called after throwing an instance of 'MtpErrorCantOpenDevice' what(): Can't open device Aborted --- Purging libmtp-runtime, libmtp9 and mtp-tools, then re-installing from jessie-backports to give: libmtp-common: 1.1.13-1 libmtp-runtime: 1.1.12-1~bpo8+1 libmtp9:1.1.12-1~bpo8+1 mtp-tools 1.1.12-1~bpo8+1 jmtpfs: 0.5-2+b2 restores the old behavior and solves the problem -- both devices are mounted without error or problems. Jim -- System Information: Debian Release: 9.0 Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libmtp9 depends on: ii dpkg 1.18.24 ii libc6 2.24-11 ii libgcrypt201.7.6-2 ii libmtp-common 1.1.13-1 ii libusb-1.0-0 2:1.0.21-1 ii multiarch-support 2.24-11 Versions of packages libmtp9 recommends: ii libmtp-runtime 1.1.12-1~bpo8+1 ii udev232-25 libmtp9 suggests no packages. -- no debconf information
Bug#687136: update
* Ben Hutchings (b...@decadent.org.uk) wrote: | On Tue, 2014-12-30 at 21:13 -0800, Jim McCloskey wrote: | [...] | However, two days ago I upgraded from wheezy to jessie and installed kernel version | 3.17-1. I purged fglrx and now rely again on the radeon driver. The problem reported | above is gone and all works very well (including acceleration). It's hard for me to know | which aspect of the upgrade was most important in resolving this, but in any case I'm | very happy indeed with the outcome and I suggest that the bug be closed at this point. | | I'd like to confirm that this is fixed in the current packaged kernel | version. You wrote 3.17-1 above, but we never packaged that version. | Do you mean version 3.16.7-ckt2-1? Ah, sorry ... I installed the 3.17-1 package from the experimental repository, without realizing that that was where it was coming from. Bad But this morning I installed 3.16.7-ckt2-1 from jessie, booted into it, and all is fine with this version also -- no problems after the best part of a day working on the system. Thanks, Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687136: update
* Jim McCloskey (mccl...@ucsc.edu) wrote: | This is what I've done so far to try to sort this bug out: | | . tried different monitors | . tested the memory | . upgraded the BIOS | . tried the card in a different machine | . tried a self-compiled version of (Debianized) kernel 3.4 | . tried libdrm packages built myself from: | | git://git.debian.org/git/pkg-xorg/lib/libdrm --branch debian-experimental | (September 25th) | | No luck. I get X freezes in every condition except when the firmware package is | uninstalled and no acceleration is attempted. | | Presumably the most relevant sign of trouble is the fact that GPU lockups | are reported: | |Oct 5 14:00:17 ohlone kernel: [ 34.436052] GPU lockup (waiting for 0x0004 last fence id 0x0001) |Oct 5 14:00:17 ohlone kernel: [ 34.437223] radeon :01:00.0: GPU softreset |Oct 5 14:00:17 ohlone kernel: [ 34.436052] GPU lockup (waiting for 0x0004 last fence id 0x0001) |Oct 5 14:00:17 ohlone kernel: [ 34.437223] radeon :01:00.0: GPU softreset | | at intervals of 12 to 20 seconds. | | At this point I think I have to just give up, I resorted then to using the proprietary driver from AMD. However, two days ago I upgraded from wheezy to jessie and installed kernel version 3.17-1. I purged fglrx and now rely again on the radeon driver. The problem reported above is gone and all works very well (including acceleration). It's hard for me to know which aspect of the upgrade was most important in resolving this, but in any case I'm very happy indeed with the outcome and I suggest that the bug be closed at this point. Thanks everyone, Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767449: closed by Khalid Aziz kha...@debian.org (Bug#767449: fixed in kexec-tools 1:2.0.7-4)
* Debian Bug Tracking System (ow...@bugs.debian.org) wrote: | This is an automatic notification regarding your Bug report | which was filed against the kexec-tools package: | | #767449: systemctl forces reboot with every shutdown | | It has been closed by Khalid Aziz kha...@debian.org. Just to confirm that this patch did in fact fix the problem here. Thank you very much! Jim McCloskey -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767449: systemctl forces reboot with every shutdown
Mert Dirik mertdi...@gmail.com wrote: | Do you have kexec-tools installed? Sound very much like #766338. Thank you! I did have kexec-tools installed (though I'm not sure how that came to be so and I wasn't aware of it). Purging kexec-tools solved the problem, so this bug should probably be closed. However judging by the discussion of #766338, the problem seems to stem from an interaction between kexec-tools and systemctl. I'm very grateful for your help, Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766338: kexec-tools: no shutdown possible with 1:2.0.7-3
Bernhard Úbelacker bernha...@vr-web.de wrote: | Can someone else reproduce this issue? Justin B Rye justin.byam@gmail.com wrote: | I can reproduce this (and see bug #785719 against general). I encountered this bug following an upgrade to testing on October 30th 2014, an upgrade that affected both kexec-tools and systemd. I reported it as bug #767449 against systemd (I didn't know that kexec-tools was installed on the relevant system, a laptop). The upgrade was from kexec-tools 2.0.4-1 to 2.0.7-3 and from systemd 208-8 to 215-5+b1. The problem did not exist before the upgrade. Purging kexec-tools `solves' the problem. Is it significant that all of the reports of this problem that I've seen (not that there are very many) involve the amd64 architecture? Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767449: systemctl forces reboot with every shutdown
Package: systemd Version: 215-5+b1 Severity: important Dear Maintainer, Thanks very much for all of your work. The core of my report is this: following an upgrade to testing on October 30th 2014, I am unable to shut down my laptop. Almost every way of shutting down is followed by a forced reboot (which of course I do not want). * What led up to the situation? Upgrading to testing on Thursday October 30th 2014. This included an upgrade to libsystemd0, libpam-systemd, systemd, systemd-sysv, libsystemd-daemon0, libsystemd-id128-0, libsystemd-journal0, libsystemd-login0. * What exactly did you do (or not do) that was effective (or ineffective)? 1. In Gnome 3: Tried to shutdown using the power-down icon in the dropdown menu of the status bar. The system shut down and rebooted. 2. In Gnome 3: pressed and held the power button (configured in gnome-tweak-tool to power down). The system shut down and immediately rebooted. 3. From the command-line as root, typed `shutdown -h now'. The system shut down and immediately rebooted. 4. From the command-line as root, typed `systemctl poweroff'. The system shut down and immediately rebooted. 5. From the command-line as root, typed `poweroff -p'. The system shut down and immediately rebooted. (Similarly just `poweroff'.) 6. From the command-line as root, typed `halt -p', The system shutdown and immediately rebooted. 7. From the command-line as root, typed `poweroff -f'. The system shut down and there was no reboot. Presumably because using this option entails that the init system is not contacted. * What was the outcome of this action? An automatic (and unwanted) reboot following shutdown in every circumstance except when `poweroff -f' was issued as root from the command line. This is the only way I've found so far to actually shut the laptop down. Since shutdown and poweroff are symbolic links to systemctl, presumably the problem ultimately lies there. * What outcome did you expect instead? That the system would shut down without automatically and instantly rebooting. That was the behavior before the upgrade. Thanks for any advice or help. Please let me know how I might help, Jim -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.4 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.25.1-5 ii libc6 2.19-12 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-2 ii libgcrypt20 1.6.2-3 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-5+b1 ii sysv-rc 2.88dsf-53.4 ii udev215-5+b1 ii util-linux 2.25.1-5 Versions of packages systemd recommends: ii dbus1.8.8-2 ii libpam-systemd 215-5+b1 Versions of packages systemd suggests: pn systemd-ui 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#756583: nouveau: GPU lockups following upgrade to jessie
Package: xserver-xorg-video-nouveau Version: 1:1.0.10-1+b2 Severity: normal Dear Maintainer, * What led up to the situation? Upgrading to testing/jessie (as of July 20th 2014) resulted in GPU lockups which I had not experienced on this system under stable/wheezy. * What exactly did you do (or not do) that was effective (or ineffective)? apt-get -t testing dist-upgrade; the screen froze during the upgrade, which made things difficult (I couldn't monitor progress or respond to queries), but I was ultimately able to complete the upgrade without error by switching to console-mode. These were among the packages affected: UPGRADED: xserver-xorg-video-nouveau:i386 (1.0.1-5, 1.0.10-1+b2) libdrm-nouveau2:i386 (2.4.49-2, 2.4.54-1) libdrm-nouveau2-dbg:i386 (2.4.49-2, 2.4.54-1) libdrm2:i386 (2.4.40-1~deb7u2, 2.4.54-1 libdrm2-dbg:i386 (2.4.40-1~deb7u2, 2.4.54-1) mesa-utils:i386 (8.0.1-2+b3, 8.2.0-1) libglu1-mesa:i386 (8.0.5-4+deb7u2, 9.0.0-2) xserver-xorg-core:i386 (1.12.4-6+deb7u1, 1.15.99.904-1) xserver-xorg:i386 (7.7+3~deb7u1, 7.7+7) xserver-xorg-core:i386 (1.15.99.904-1, 1.16.0-1) xserver-common:i386 (1.15.99.904-1, 1.16.0-1) xserver-xorg-input-evdev:i386 (2.7.0-1+b1, 2.8.2-1+b2) xserver-xorg-video-all:i386 (7.7+3~deb7u1, 7.7+7) x11-xserver-utils:i386 (7.7~3, 7.7+3) xserver-xorg-core:i386 (1.15.99.904-1, 1.16.0-1) xserver-common:i386 (1.14.3-5, 1.15.99.904-1) xserver-xorg-input-all:i386 (7.7+3~deb7u1, 7.7+7) REMOVED: libdrm-nouveau1a:i386 (2.4.40-1~deb7u2) INSTALLED xserver-xorg-video-modesetting:i386 (0.9.0-1+b1, automatic) linux-image-3.14-1-686-pae * What was the outcome of this action? I get GPU lockups. This did not happen before the upgrade. Usually it happens before the display manager (gdm3) can display the login screen. The screen is blank; the cursor is motionless in the top left-hand corner; usually the keyboard is responsive, but not always. Even when the keyboard is not responsive I can get access via ssh. When I can switch to a console using Ctl-Alt-F1, the message below is sometimes (but not always) displayed: nouveau E[DRM] GPU lockup - switching to software fbcon If I can get past the starting of gdm3 without a lockup, the system usually functions fine for several hours. But lockups can then also come at unpredictable (by me) moments. I did a further upgrade to libgl1-mesa-dri in sid: libgl1-mesa-dri:i386 (10.2.3-1, 10.2.4-1) but that made matters neither worse nor better. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Sep 18 2012 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2528112 Jul 17 16:04 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84GL [Quadro FX 1700] [10de:040f] (rev a1) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.14-1-686-pae (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-4) ) #1 SMP Debian 3.14.12-1 (2014-07-11) Xorg X server log files on system: -- -rw-r--r-- 1 root root 27238 Jul 20 22:12 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [21.861] X.Org X Server 1.15.99.904 (1.16.0 RC 4) Release Date: 2014-07-07 [21.861] X Protocol Version 11, Revision 0 [21.861] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian [21.861] Current Operating System: Linux branci40 3.2.0-4-686-pae #1 SMP Debian 3.2.51-1 i686 [21.861] Kernel command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-686-pae root=/dev/mapper/branci40-root ro quiet [21.861] Build Date: 08 July 2014 03:58:16PM [21.861] xorg-server 2:1.15.99.904-1 (http://www.debian.org/support) [21.861] Current version of pixman: 0.32.6 [21.861]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [21.861] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [21.861] (==) Log file: /var/log/Xorg.0.log, Time: Sun Jul 20 20:02:01 2014 [21.976] (==) Using system config directory /usr/share/X11/xorg.conf.d [22.088] (==) No Layout section. Using the first Screen section. [22.088] (==) No screen section available. Using defaults. [22.088] (**) |--Screen Default Screen Section (0) [
Bug#755568: , Resolved
This problem seems to have been resolved by a further upgrade to current testing: Start-Date: 2014-07-23 07:26:21 Commandline: apt-get -f -t testing dist-upgrade Wireless connectivity now works very well again. I have no idea which was the crucial package, but I'm relieved and grateful, Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755568: follow-up 2
| The other experiment I've been running is this: network-manager on the | laptop is currently at the version in testing (0.9.10.0-1), but I | purged network-manager-gnome almost exactly three hours ago. The | problem has not manifested itself in those three hours, But when I booted this morning (with network-manager-gnome still uninstalled) the problem was back. I had wireless connectivity for roughly 2 minutes and then the connection died without warning and further attempts to connect yielded only `no route to host' messages. So the problem does seem to be in network-manager itself, and in some change that was made betweeen version 0.9.8.10-4 and version 0.9.10.0-1, Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755568: upgrade to network-manager(-gnome?) in jessie breaks wireless connectivity
Package: network-manager Version: 0.9.10.0-1 Severity: important It's actually not clear to me whether this bug-report should be filed against network-manager or against network-manager-gnome. I upgraded my laptop to testing on Monday July 21st: Start-Date: 2014-07-21 09:38:16 Commandline: apt-get -t testing dist-upgrade Among the packages affected were network-manager and network-manager-gnome: network-manager:amd64 (0.9.8.10-4, 0.9.10.0-1) network-manager-gnome:amd64 (0.9.8.10-1, 0.9.10.0-2) Before the upgrade, my network connections worked really unusually well (better than my housemates using OsX). Following the upgrade, though, I saw the following problematic behavior (on my home network): Upon reboot, the laptop established a wireless link with the access point and all seemed normal. After roughly one minute's use, however, I lost the connection, with no notification from the system and in the following sense: addresses on the local network remained accessible, but any attempt to connect beyond the local network (ssh, http ... ) resulted in `no route to host' messages. I repeated this pattern (by rebooting) five times. The problem is not with the network configuration here -- all other machines (OsX and debian systems that had not been upgraded) continue to work as expected and as before. Only the system which had undergone this upgrade was affected. I forced a downgrade to the version of network-manager in wheezy (0.9.4.0-10), which in turn forced the removal of network-manager-gnome, and the problem disappeared. I upgraded again to version 0.9.10.0-1 (current testing) and the problem returned. At present, the system reports (through the network icon) that the laptop is connected; ifconfig shows that wlan0 has an IP address, but all outbound connections are impossible. It's as if the default route cannot be configured (or that that information is somehow lost after the initial connection). Here is a relevant part of syslog after the most recent such failure: Jul 21 17:10:21 lapdog4 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 Jul 21 17:10:21 lapdog4 NetworkManager[4634]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 Jul 21 17:10:21 lapdog4 dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Jul 21 17:10:21 lapdog4 dhclient: DHCPOFFER from 192.168.1.1 Jul 21 17:10:21 lapdog4 NetworkManager[4634]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Jul 21 17:10:21 lapdog4 NetworkManager[4634]: DHCPOFFER from 192.168.1.1 Jul 21 17:10:21 lapdog4 dhclient: DHCPACK from 192.168.1.1 Jul 21 17:10:21 lapdog4 NetworkManager[4634]: DHCPACK from 192.168.1.1 Jul 21 17:10:21 lapdog4 dhclient: bound to 192.168.1.108 -- renewal in 35719 seconds. Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info (wlan0): DHCPv4 state changed preinit - bound Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info address 192.168.1.108 Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info plen 24 (255.255.255.0) Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info gateway 192.168.1.1 Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info server identifier 192.168.1.1 Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info lease time 86400 Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info nameserver '192.168.1.1' Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started... Jul 21 17:10:21 lapdog4 avahi-daemon[2603]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.108. Jul 21 17:10:21 lapdog4 avahi-daemon[2603]: New relevant interface wlan0.IPv4 for mDNS. Jul 21 17:10:21 lapdog4 avahi-daemon[2603]: Registering new address record for 192.168.1.108 on wlan0.IPv4. Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info (wlan0): device state change: ip-config - ip-check (reason 'none') [70 80 0] Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete. Jul 21 17:10:21 lapdog4 NetworkManager[4634]: bound to 192.168.1.108 -- renewal in 35719 seconds. Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info (wlan0): device state change: ip-check - secondaries (reason 'none') [80 90 0] Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info (wlan0): device state change: secondaries - activated (reason 'none') [90 100 0] Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info NetworkManager state is now CONNECTED_LOCAL Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info NetworkManager state is now CONNECTED_GLOBAL Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info Policy set 'branci40 2' (wlan0) as default for IPv4 routing and DNS. Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info Activation (wlan0) successful, device activated. Jul 21 17:10:21 lapdog4 NetworkManager[4634]: info startup complete Jul 21 17:10:23 lapdog4 ntpd[2686]:
Bug#755470: follow-up
The system now usually (three times out of five) freezes hard before it gets to the gdm3 login screen and can then be used only in console-mode. There's no 0-greeter.log in /var/log/gdm3/ because (I think) X crashes before things can get that far: Jul 21 20:52:52 branci40 org.a11y.Bus[803]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Jul 21 20:52:52 branci40 ca.desrt.dconf[803]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Jul 21 20:52:52 branci40 gnome-session[799]: Window manager warning: Log level 16: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. I experienced no such crashes before the upgrade; the machine is now only occasionally usable, Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654939: mtpfs: broken overnight
For me, this bug (if it's one bug we're talking about) was caused, or exposed, by a recent dist-upgrade to testing. I have a Motorola Xoom that I mount on my Debian wheezy box with: mtpfs -o allow_other /media/android (run as root). This has worked with no problems since I got the Xoom about a month ago. In particular it was working on Friday evening January 31st. But then: Start-Date: 2013-02-01 00:01:06 Commandline: apt-get -t testing dist-upgrade This upgrade included: Upgrade: mtpfs:i386 (0.9-3+b1, 1.1-4), libmono-system-xml4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), gnome-shell:i386 (3.4.2-5, 3.4.2-6), libmono-sharpzip4.84-cil:i386 (2.10.8.1-6, 2.10.8.1-7), gnome-control-center:i386 (3.4.2+git20121016.29d7c0-1, 3.4.3.1-2), libmono-cairo4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), libmono-system-configuration4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), libmono-i18n-west4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), libmono-posix4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), libmono-security4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), mono-gac:i386 (2.10.8.1-6, 2.10.8.1-7), unattended-upgrades:i386 (0.79.3, 0.79.4), libmono-system-drawing4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), libmono-system-security4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), libmono-corlib4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), mono-runtime:i386 (2.10.8.1-6, 2.10.8.1-7), gnome-control-center-data:i386 (3.4.2+git20121016.29d7c0-1,3.4.3.1-2), libmono-system4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), libmono-system-core4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7), mono-4.0-gac:i386 (2.10.8.1-6, 2.10.8.1-7), gnome-shell-common:i386 (3.4.2-5, 3.4.2-6), libmono-i18n4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7) End-Date: 2013-02-01 00:02:09 As soon as the upgrade completed, I was unable to mount the tablet or communicate with it at all. % mtpfs -o allow_other /media/android Listing raw device(s) Device 0 (VID=22b8 and PID=70a8) is a Motorola Xoom (ID 1). Found 1 device(s): Motorola: Xoom (ID 1) (22b8:70a8) @ bus 1, dev 3 Attempting to connect device Android device detected, assigning default bug flags Listing File Information on Device with name: (NULL) fuse: bad mount point `/media/android': Transport endpoint is not connected and: cd /media/android bash: cd: /media/android: Transport endpoint is not connected and the /media/android directory is listed as: d? ? ?? ?? android `adb devices' shows no devices attached and `adb shell' reports: error: device not found (fusermount -u /dev/android returns the directory listing to normal, as reported by another user above). mtab, however, does list the device as mounted: mtpfs /media/android fuse.mtpfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0 Among the packages upgraded, presumably mtpfs is the likely culprit. And presumably the problem was caused by whatever is different between version 0.9-3+b1 and version 1.1-4. Looking at the changelog, the only likely possibilities seemed to be a dependency on fuse rather than on fuse-utils, or else the move to a new upstream version. I tried purging fuse-utils but that made no difference. I tried to downgrade to mtpfs 0.9-3 0 in stable, but apt wanted to remove grub in doing that, so Installing libmtp9 from the experimental repository made no difference. I hope this is helpful. Jim McCloskey -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687136: update
This is what I've done so far to try to sort this bug out: . tried different monitors . tested the memory . upgraded the BIOS . tried the card in a different machine . tried a self-compiled version of (Debianized) kernel 3.4 . tried libdrm packages built myself from: git://git.debian.org/git/pkg-xorg/lib/libdrm --branch debian-experimental (September 25th) No luck. I get X freezes in every condition except when the firmware package is uninstalled and no acceleration is attempted. Presumably the most relevant sign of trouble is that the fact that GPU lockups are reported: Oct 5 14:00:17 ohlone kernel: [ 34.436052] GPU lockup (waiting for 0x0004 last fence id 0x0001) Oct 5 14:00:17 ohlone kernel: [ 34.437223] radeon :01:00.0: GPU softreset Oct 5 14:00:17 ohlone kernel: [ 34.436052] GPU lockup (waiting for 0x0004 last fence id 0x0001) Oct 5 14:00:17 ohlone kernel: [ 34.437223] radeon :01:00.0: GPU softreset at intervals of 12 to 20 seconds. At this point I think I have to just give up, Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687136: ; graphics corruption with Radeon 6570
* Jon Severinsson (j...@severinsson.net) wrote: | Hello. Following an install of wheezy using debian-wheezy-DI-b2-i386-netinst.iso, | I reported bug #687136 [...] concerning xserver freezes with corruption of | the screen at every boot. The GPU is identified thus: | | [...] | | I've been doing my best to investigate since then and found some sources | which suggest that 3D support for this card was added only as of | libdrm_radeon-2.4.34. As far as I can tell no version more recent than | libdrm_radeon-2.4.33 is available in any Debian repository. | | Would it be possible for someone here to confirm or disconfirm this conjecture | so that I can correct/update the bug report? | | libdrm 2.4.34 does indeed add support for several additional chipset | variations, including thre new TURKS ids. The relevant commit can be viewed | at http://cgit.freedesktop.org/mesa/drm/commit/?id=cf7cc62a98 | | Unfortunately you seem to have cut out the PCI ID from the included GPU | identification, so I can't say for sure that your card is one of | the new variations. Thank you for this very helpful response. This is what hwinfo says: Model: ATI VGA compatible controller Vendor: pci 0x1002 ATI Technologies Inc Device: pci 0x6759 SubVendor: pci 0x1682 XFX Pine Group Inc. SubDevice: pci 0x3190 Memory Range: 0xd000-0xdfff (ro,non-prefetchable) Memory Range: 0xfe7c-0xfe7d (rw,non-prefetchable) I/O Ports: 0xb000-0xbfff (rw) Memory Range: 0xfe7a-0xfe7b (ro,non-prefetchable,disabled) IRQ: 16 (412396 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: pci:v1002d6759sv1682sd3190bc03sc00i00 Driver Info #0: Driver Status: radeon is active Driver Activation Cmd: modprobe radeon Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #14 (PCI bridge) but since /libdrm-2.4.33/radeonr600_pci_ids.h from wheezy already includes: CHIPSET(0x6759, TURKS_6759, TURKS) it seems like the chipset should be supported in that version. The ones that were added in the commit you referred me to are: +CHIPSET(0x6751, TURKS_6751, TURKS) +CHIPSET(0x675B, TURKS_675B, TURKS) +CHIPSET(0x675D, TURKS_675D, TURKS) | PS If there is a way for me to hand-compile a more recent version of | libdrm_radeon that might allow the machine to boot without freezing up, I | would really appreciate a link or some pointers. | | Yes, the following commands should build a libdrm 2.4.39 packages eventually | intended for debian experimental: Thank you for this help also. Good luck with your work, Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687136: further information
I tried a self-compiled 3.5 kernel (compiled from patched source in the Debian experimental repository), but the problem persisted. Looking through /var/log/messages (this under kernel 3.2.0-3-686-pae again), I see GPU lockups reported every minute or so: GPU lockup (waiting for 0x002E last fence id 0x002D) Sep 13 17:47:00 branci40 kernel: [ 829.917159] radeon :01:00.0: GPU softreset Sep 13 17:47:00 branci40 kernel: [ 829.917162] radeon :01:00.0: GRBM_STATUS=0xF5702828 Sep 13 17:47:00 branci40 kernel: [ 829.917165] radeon :01:00.0: GRBM_STATUS_SE0=0xFC05 Sep 13 17:47:00 branci40 kernel: [ 829.917168] radeon :01:00.0: GRBM_STATUS_SE1=0x0007 Sep 13 17:47:00 branci40 kernel: [ 829.917171] radeon :01:00.0: SRBM_STATUS=0x20C0 Sep 13 17:47:00 branci40 kernel: [ 829.917196] radeon :01:00.0: GRBM_SOFT_RESET=0x7F6B Sep 13 17:47:00 branci40 kernel: [ 829.917300] radeon :01:00.0: GRBM_STATUS=0x3828 Sep 13 17:47:00 branci40 kernel: [ 829.917303] radeon :01:00.0: GRBM_STATUS_SE0=0x0007 Sep 13 17:47:00 branci40 kernel: [ 829.917306] radeon :01:00.0: GRBM_STATUS_SE1=0x0007 Sep 13 17:47:00 branci40 kernel: [ 829.917309] radeon :01:00.0: SRBM_STATUS=0x20C0 Sep 13 17:47:00 branci40 kernel: [ 829.918304] radeon :01:00.0: GPU reset succeed Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684685: installation-reports: Successful install on Lenovo Thinkpad T60p: Wheezy Beta 1
Package: installation-reports Severity: minor Tags: d-i -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta1/i386/iso-cd/debian-wheezy-DI-b1-i386-netinst.isoy-DI-b1-i386-netinst.iso, Date: Sun Aug 12 14:31:03 PDT 2012 Machine: Lenovo Thinkpad T60p Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on rootfs rootfs95182424 5237936 85177768 6% / udev devtmpfs 10240 0 10240 0% /dev tmpfstmpfs 103300 680102620 1% /run /dev/mapper/lapdog2-root ext4 95182424 5237936 85177768 6% / tmpfstmpfs 5120 0 5120 0% /run/lock tmpfstmpfs 206596 20206576 1% /tmp tmpfstmpfs 206596 224206372 1% /run/shm /dev/sda1ext2233191 17039203711 8% /boot Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [OK] Detect network card:[OK] Configure network: [OK] Detect CD: [OK] Load installer modules: [OK] Clock/timezone setup: [OK] User/password setup:[OK] Detect hard drives: [OK] Partition hard drives: [OK] Install base system:[OK] Install tasks: [OK] Install boot loader:[OK] Overall install:[OK] Comments/Problems: Ancient hardware, I know, but it was all I had available for a test install. Everything smooth and fast; only two things worth commenting on: The wireless device could not be made to work (because of the missing iwlwifi firmware, I believe) so I plugged in an ethernet cable and everything went smoothly from there. Gnome3 started in fallback/classic mode (there was no direct rendering or acceleration for the ATI graphics card). It works fine in this mode. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20081217-20:16 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux branci40 2.6.26-1-486 #1 Wed Nov 26 18:28:42 UTC 2008 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 03) lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI Express Root Port [8086:2e21] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 1 [8086:3a40] lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 5 [8086:3a48] lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 6 [8086:3a4a] lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 [8086:3a34] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 [8086:3a35] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 [8086:3a36] lspci -knn: Kernel driver in
Bug#556906: Net-install (i386, build of November 8) fails on Dell Optiplex 360
* Otavio Salvador (ota...@ossystems.com.br) wrote: | This looks to be a kernel issue and would be nice to try latest | version of d-i to see if it happens or not. | | Mind to retest it? Sorry to be slow (I've been fiendishly busy). But I tested the d-i build of November 22nd and I did *not* encounter the problem I reported here. I notice that there's a new build today (Nov 26). I assume that if the problem is fixed in the build of Nov 22nd, it's still fixed in the build of Nov 26th, but let me know if you'd like me to test that also. Thanks very much for your help and for your work, Jim I'll attach the output of lspci -knn for the system in case that would be useful. 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 0a) Kernel driver in use: agpgart-intel Kernel modules: intel-agp 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 0a) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 0a) 00:02.1 Display controller [0380]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c3] (rev 0a) 00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 01) Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel 00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 01) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 [8086:27c8] (rev 01) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 [8086:27c9] (rev 01) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 [8086:27ca] (rev 01) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.3 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 [8086:27cb] (rev 01) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller [8086:27cc] (rev 01) Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01) Kernel modules: intel-rng, iTCO_wdt 00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01) Kernel driver in use: PIIX_IDE Kernel modules: piix 00:1f.2 IDE interface [0101]: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller [8086:27c0] (rev 01) Kernel driver in use: ata_piix Kernel modules: ata_piix 00:1f.3 SMBus [0c05]: Intel Corporation 82801G (ICH7 Family) SMBus Controller [8086:27da] (rev 01) Kernel driver in use: i801_smbus Kernel modules: i2c-i801 02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5784M Gigabit Ethernet PCIe [14e4:1698] (rev 10) Kernel driver in use: tg3 Kernel modules: tg3
Bug#545933: Installation-Report: Dell Optiplex 745 USB keyboard not recognized
Package: installation-reports Boot method: CD Image version: debian-testing-i386-netinst.iso, build of September 6th 2009, from http://cdimage.debian.org/cdimage/daily-builds/ Date: Wednesday Sept 9th, 7:10pm (Pacific) Machine: Dell Optiplex 745 Processor: Intel Celeron D Memory: Partitions: didn't get that far Output of lspci -knn (or lspci -nn): see below Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [O] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[E] Comments/Problems: These machines have no serial ports, so one must use a USB keyboard and mouse. The keyboard was detected fine in the BIOS and the initial installation menu could also be navigated (arrow keys and enter produced the expected responses). Upon reaching the first menu, however (Choose a Language), the keyboard became unresponsive (none of arrow keys, enter, space, or TAB produced any response) and so it was impossible to go any farther. Same behaviour with both graphic and non-graphic install methods. Reverting to debian-testing-i386-netinst.iso build of January 31st 2009 resolved the issue. Jim -- lspci 00:00.0 Host bridge: Intel Corporation Q963/Q965 Memory Controller Hub (rev 02) Subsystem: Dell Unknown device 01da Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Capabilities: [e0] Vendor Specific Information 00:02.0 VGA compatible controller: Intel Corporation Q963/Q965 Integrated Graphics Controller (rev 02) (prog-if 00 [VGA]) Subsystem: Dell Unknown device 01da Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin A routed to IRQ 169 Region 0: Memory at dfe0 (32-bit, non-prefetchable) [size=1M] Region 2: Memory at c000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at ecb8 [size=8] Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Address: Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:02.1 Display controller: Intel Corporation Q963/Q965 Integrated Graphics Controller (rev 02) Subsystem: Dell Unknown device 01da Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Region 0: Memory at dff0 (32-bit, non-prefetchable) [size=1M] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 (rev 02) (prog-if 00 [UHCI]) Subsystem: Dell Unknown device 01da Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 169 Region 4: I/O ports at ff20 [size=32] 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 (rev 02) (prog-if 00 [UHCI]) Subsystem: Dell Unknown device 01da Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 201 Region 4: I/O ports at ff00 [size=32] 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 (rev 02) (prog-if 20 [EHCI]) Subsystem: Dell Unknown device 01da Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin C routed to IRQ 225 Region 0: Memory at dfdfbc00 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management
Bug#509400: installation-reports: optical drive not detected (Lite-On 20X LightScribe)
* Christian Perrier (bubu...@debian.org) wrote: | Quoting Jim McCloskey (mccl...@ucsc.edu): | Package: installation-reports | | Boot method: CD | Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso | | Date: Dec 20th--21st | This is probably the following problem, listed in the errata file: | | Due to a pata_marwell module not begin properly autoloaded | on i386 and amd64 media, | peripherals driven by Marvell disk controllers are not detected. If | IDE is used in legacy mode with these controllers, switch to | console 2 when the installer boots (Alt+F2) and | run 'modprobe -r ahci; modprobe pata_marvel; modprobe ahci' before | continuing. | | | Could you do two tests ? | | 1) try with the same image, then follow the above instructions (switch | to VT2 when the installer boots and run the magic commands) and | check if the CD is detected later on. This did indeed fix the problem. Thank you. | 2) download the *netboot* image of the daily builds. I really mean | *netboot*. Not netinst. This is a very small ISO image (8MB). With | that image, which has the latest kernel package from unstable, that | problem should not happen I will try this when the current install finishes (I want to re-do the partition scheme in any case). Thanks very much to all who helped (the installation has now completed without problem), Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509400: installation-reports: optical drive not detected (Lite-On 20X LightScribe)
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso Date: Dec 20th--21st Machine: customized P4500A from Polywell COmputers Inc. Processor: Intel Core 2 Duo E8500 3.16GHz Memory: 2x DDR2 800MHz 2GB PC6400 Unbuffered Memory Partitions: not yet partitioned Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 03) 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI Express Root Port [8086:2e21] (rev 03) Kernel driver in use: pcieport-driver 00:1a.0 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1a.1 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1a.2 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39] Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1a.7 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c] Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e] 00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 1 [8086:3a40] Kernel driver in use: pcieport-driver 00:1c.4 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 5 [8086:3a48] Kernel driver in use: pcieport-driver 00:1c.5 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 6 [8086:3a4a] Kernel driver in use: pcieport-driver 00:1d.0 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 [8086:3a34] Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.1 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 [8086:3a35] Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.2 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 [8086:3a36] Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.7 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 [8086:3a3a] Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 90) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller [8086:3a16] 00:1f.2 IDE interface [0101]: Intel Corporation 82801JI (ICH10 Family) 4 port SATA IDE Controller [8086:3a20] Kernel driver in use: ata_piix Kernel modules: ata_piix 00:1f.3 SMBus [0c05]: Intel Corporation 82801JI (ICH10 Family) SMBus Controller [8086:3a30] 00:1f.5 IDE interface [0101]: Intel Corporation 82801JI (ICH10 Family) 2 port SATA IDE Controller [8086:3a26] Kernel driver in use: ata_piix Kernel modules: ata_piix 01:00.0 VGA compatible controller [0300]: nVidia Corporation Quadro FX 1700 [10de:040f] (rev a1) 02:00.0 Ethernet controller [0200]: Attansic Technology Corp. L1 Gigabit Ethernet Adapter [1969:1026] (rev b0) 03:00.0 IDE interface [0101]: Marvell Technology Group Ltd. 88SE6121 SATA II Controller [11ab:6121] (rev b2) Kernel driver in use: ahci Kernel modules: ahci, pata_marvell 05:00.0 Multimedia audio controller [0401]: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller [1412:1712] (rev 02) 05:01.0 Multimedia audio controller [0401]: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] [1013:6003] (rev 01) 05:03.0 FireWire (IEEE 1394) [0c00]: Agere Systems FW323 [11c1:5811] (rev 70) Kernel driver in use: ohci1394 Kernel modules: ohci1394 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [E] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: The optical dtrive is: DVDRW/CD/DVD:Lite-On 20X LightScribe DVD+/-RW Dual-Layer IDE which is identified in the BIOS as: IDE:ATAPI DVD A DH20A4P I've tried the install with the i386 daily build of December 18th and also with the amd64 Lenny beta 2 image of August 29th 2008. The latter was used for a problem-free installation in September. In each case, the
Bug#320277: neutrino: crashes at startup
Package: neutrino Version: 0.8.2-1 0 (testing/unstable) Severity: important -- System Information: Debian Release: 3.1 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11.3 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Neutrino consistently crashes at startup when the Nomad Zen Xtra is attached to a USB port. It starts only if the Nomad is not attached. David Knight ([EMAIL PROTECTED]) reports that he has just released version 0.8.3 which be believes fixes this problem. Jim McCloskey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290975: installation report (problem-free)
: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: ABIT Computer Corp.: Unknown device 101e Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at unassigned I/O ports at unassigned I/O ports at unassigned I/O ports at unassigned I/O ports at f000 [size=16] Memory at 1f80 (32-bit, non-prefetchable) [size=1K] :00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) (prog-if 8f [Master SecP SecO PriP PriO]) Subsystem: ABIT Computer Corp.: Unknown device 101e Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 18 I/O ports at a400 [size=8] I/O ports at a800 [size=4] I/O ports at ac00 [size=8] I/O ports at b000 [size=4] I/O ports at b400 [size=16] :00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) Subsystem: ABIT Computer Corp.: Unknown device 101e Flags: medium devsel, IRQ 17 I/O ports at 0500 [size=32] :00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) Subsystem: ABIT Computer Corp.: Unknown device 101e Flags: bus master, medium devsel, latency 0, IRQ 17 I/O ports at bc00 [size=256] I/O ports at c000 [size=64] Memory at fa081000 (32-bit, non-prefetchable) [size=512] Memory at fa082000 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 :01:02.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01) Subsystem: ABIT Computer Corp.: Unknown device 101e Flags: bus master, fast devsel, latency 32, IRQ 18 Memory at f900 (32-bit, non-prefetchable) [size=8K] Expansion ROM at unassigned [disabled] [size=16K] Capabilities: [40] Power Management version 2 -- lspci -n: :00:00.0 0600: 8086:2570 (rev 02) :00:02.0 0300: 8086:2572 (rev 02) :00:1d.0 0c03: 8086:24d2 (rev 02) :00:1d.1 0c03: 8086:24d4 (rev 02) :00:1d.2 0c03: 8086:24d7 (rev 02) :00:1d.3 0c03: 8086:24de (rev 02) :00:1d.7 0c03: 8086:24dd (rev 02) :00:1e.0 0604: 8086:244e (rev c2) :00:1f.0 0601: 8086:24d0 (rev 02) :00:1f.1 0101: 8086:24db (rev 02) :00:1f.2 0101: 8086:24d1 (rev 02) :00:1f.3 0c05: 8086:24d3 (rev 02) :00:1f.5 0401: 8086:24d5 (rev 02) :01:02.0 0200: 14e4:4401 (rev 01) -- Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: All very smooth. The new version (December) correctly detected and configured the ethernet adapter (Broadcom BCM4401 100Base-T), where the August version could not. I thought I could choose to install a 2.6 series kernel, but if that was an option, I somehow missed it. THANKS!!! Jim McCloskey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
