Bug#989066: torrent no fun

[Lou Poppler]

On Mon, 2021-05-24 at 15:19 -0700, ddueh...@verizon.net wrote:
> 
> Comments/Problems:
> 
> It’s far easier to just download an image than to try to figure out how to 
> download via bittorrent.
  The downloads are small enough that I can wait for them to download.  I spent 
much more time finding
 a non-malware bittorrent client for Windows where I’m creating a ISO USB for a 
Debian based Zoom kiosk
 type install.  You should make download by bit torrent an option not a 
requirement.  
Obviously this bothered me enough to send this email.

You don't mention where you started looking, or what image you downloaded,
but there is not any requirement to download via bittorrent.

Look here:  https://cdimage.debian.org/cdimage/

Bug#919233: Install Guide vs. Secure Boot

[Lou Poppler]

Hopefully this is already changed in the Bullseye install guide, but if not, I
don't think I will learn how to make edits before Bullseye releases.

The Buster install guide says in Section 3.6.3 
https://www.debian.org/releases/stable/amd64/ch03s06.en.html#UEFI

   Another UEFI-related topic is the so-called “secure boot”
   mechanism.  Secure boot means a function of UEFI implementations that
   allows the firmware to only load and execute code that is
   cryptographically signed with certain keys and thereby blocking any
   (potentially malicious) boot code that is unsigned or signed with
   unknown keys.  In practice the only key accepted by default on most
   UEFI systems with secure boot is a key from Microsoft used for signing
   the Windows bootloader.  As the boot code used by debian-installer is not 
   signed by Microsoft, booting the installer requires prior deactivation of
   secure boot in case it is enabled.

My test on a recent weekly-build testing netinst seems to show that the above is
no longer correct -- it booted fine for me in UEFI/SecureBoot mode.  I thought I
remembered reading (somewhere) that all recent debian installers (and live
systems??) can boot in legacy BIOS mode or UEFI mode with or without secure
boot.  

Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux

[Lou Poppler]

On Sun, 2020-08-30 at 08:16 -0700, Lou Poppler wrote:
> Сергей:
> 
> As we tried to tell you yesterday, you should be writing ONLY the .iso image
> onto your install USB drive.  DO NOT ADD OTHER FILES like these init.rd and
> vmlinuz files from other places.  just copy the .iso image.  nothing else.

The complete installer and live .iso images are available from this source:
> https://cdimage.debian.org/cdimage/

You do not need to mix and match additional files from this other installer
hierarchy.

Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux

[Lou Poppler]

Сергей:

As we tried to tell you yesterday, you should be writing ONLY the .iso image
onto your install USB drive.  DO NOT ADD OTHER FILES like these init.rd and
vmlinuz files from other places.  just copy the .iso image.  nothing else.

On Sun, 2020-08-30 at 13:40 +0300, Сергей Фёдоров wrote:
> Package: cdimage.debian.org
> Severity: critical
> Justification: breaks the whole system
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads)
> Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> In both cases, when installing Debian from a flash drive, I received the 
> message:
> 
> Load installer components from an ISO installer.
> 
> No modules were found. This pfobably is due to a mismatch between the kernel
> by this version of the installer and the kernel version available in the
> archieve.
> 
> and the installation had to be stopped.
> 
> I think the problem is that the kernel versions for DVD and
> installer-amd64/current/images/hd-media/ or
> installer-amd64/current/images/hd-media/gtk/
> в initrd.gz
> for Debian 10.4 and Debian 10.5
> don't match.
> 
> for Debian 10.5
> 4.19.0-10 - the kernel versions for DVD
> 4.19.0-5  - the kernel versions for
> http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/
> or (for GTK)
> http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/gtk/
> 
> Для Debian 10.4
> 4.19.0-9 - the kernel versions for с DVD
> 4.19.0-5 - the kernel versions for
> http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/
> or (for GTK)
> http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/gtk/
> 
> Для Debian 10.3
> 4.19.0-8 - the kernel versions for с DVD
> 4.19.0-8 - the kernel versions for
> http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/
> or (for GTK)
> http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/gtk/
> 
> For Debian 10.3 everything was established without problems.
> 

Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux

[Lou Poppler]

Please see the installation instructions:
https://www.debian.org/releases/stable/installmanual

It is not correct to pre-format your install media, and pre-copy other files
onto it, before copying the installation .iso

The correct instructions for writing a USB (or other) installation medium are in
section 4.3 of that installmanual.

In particular, the destination target of your dd command should be something
similar to /dev/sdb_NOT_  something like   /dev/sdb1
--- and don't forget to `sync` after the dd.

If you still have trouble, seek help at the #debian IRC channel at oftc.net.

On Sat, 2020-08-29 at 17:10 +0300, Сергей Фёдоров wrote:
> Package: cdimage.debian.org
> Severity: critical
> Justification: breaks the whole system
> 
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads)
> Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Created a USB flach stick using the" gparted " MBR-partition table.
> GPT-partition table failed to get a working version of the Debian 
> installation.
> Created an Ext4-partition and its label. Set the partition "boot" attribute.
> 
> Created a bootable flash drive:
> 
> # dd conv=notrunc bs=440 count=1 if=/usr/lib/EXTLINUX/mbr. bin of=/dev/xxx
> where xxx is the name of the u-VA, for example, sdf.
> # extlinux --install "folder path" (for example " /media/u1/UP1/"), where" 
> UP1 " is partition name
> 
> For Debian 10.4 copied from a folder:
> 
> http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/
> or from (for GTK)
> http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/gtk/
> 
> vmlinuz
> initrd.gz
> 
> and copied "debian-10.4.0-amd64-DVD-1.iso"
> 
> or
> 
> For Debian 10.5 copied from the folder:
> 
> http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/
> or from (for GTK)
> http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/gtk/
> 
> vmlinuz
> initrd.gz
> 
> and copied "debian-10.5.0-amd64-DVD-1.iso»
> 
> In both cases, when installing Debian from a flash drive, I received the 
> message:
> 
> Load installer components from an ISO installer.
> 
> No modules were found. This pfobably is due to a mismatch between the kernel
> by this version of the installer and the kernel version available in the
> archieve.
> 
> and the installation had to be stopped.
> 
> For Debian 10.3 copied from the folder:
> 
> http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/
> or from (for GTK)
> http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/gtk/
> 
> vmlinuz
> initrd.gz
> 
> and copied "debian-10.3.0-amd64-DVD-1.iso"
> 
> and everything was established without problems.
> 
> Copy Debian 10.3, 10.4, and 10.5 to a USB stick in the device root, download
> with it, the installation of Debian passes without problems.
> 
> For example:
> 
> dd if="./debian-10.5.0-amd64-DVD-1.iso" of=/dev/xxx bs=1M status=progress
> where xxx is the name of the u-VA, for example, sdf.
> 
> Installing Debian 10.3, 10.4, and 10.5 from a DVD does not cause these 
> problems.
> 

Bug#954081: debian-live-10.3.0-amd64-gnome.iso fails to load desktop on Acer A515-43-R19L laptop

[Lou Poppler]

This is possibly a "non-free" firmware problem.  I suggest you try with one of
the "unofficial" "non-free" live images or installer images.

https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

On Mon, 2020-03-16 at 09:25 -0400, Mike Haag wrote:
> Package: debian-live
> Severity: important
> 
> I first updated the BIOS using the supplied Windows 10, then replaced the
> supplied 128GB SSD with a new 500GB SSD.
> 
> Verified the iso file with SHA512, and tried running as both DVD and USB thumb
> drive:
> 
> Grub starts as expected.
> 
> 1. Attempted to start the live desktop environment from the first Grub menu
> item, "Debian GNU/Linux Live (kernel 4.19.0-8-amd64)".
> 2. Multiple status messages are displayed. Then, a Debian splash screen is
> briefly displayed, followed immediately by a blank screen with a blinking
> cursor, and the system freezes.
> 3. Ctrl-Alt-Del will reboot the laptop into the Grub menu.
> 
> The graphical installer (third Grub menu item) runs, and appears to complete
> successfully. But, the installed system exhibits the same problem: Multiple
> startup messages, and the system freezes before the desktop environment 
> starts,
> just displaying a blank screen and blinking cursor.
> 
> For what it's worth, I also tried several other Debian-based and RPM
> distributions. Could only get a working system with the RPMs:
> 
> 1. Debian: The following produce the same results as above.
> 
>  debian-live-10.3.0-amd64-gnome+nonfree.iso
>  debian-live-testing-amd64-gnome.iso
>  debian-10.3.0-amd64-netinst.iso
> 
> 2. Ubuntu 19.10 and LinuxMint 19.3: The live distributions work as
>expected. Installed systems begin to boot but then both fail with
>unspecified watchdog soft lock errors before their respective desktop
>environments start.
> 
> 3. Fedora 31: Live runs as expected. Installed system boots and runs as
> expected.
> 
> 4. OpenSUSE Leap 15.1: Live runs as expected. Installed system boots and runs
> as expected.
> 
> The only recommendation I could find using the Acer user forum and other
> internet searches, was to try editing the Grub menu line to "nomodeset", but
> that doesn't work. There was also some theorizing that the kernel needed to be
> updated to 5.0, but openSUSE 15.1 is kernel 4.12, and that is working.
> 
> Looking for advice and suggestions: I do not know how to proceed with further
> trouble-shooting.
> 
> Thanks, Mike
> 
> 
> 
> -- System Information:
> Debian Release: 10.3
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-8-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 /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 

Bug#939862: installation-guide-amd64: "Windows 8 fast boot" is now "Windows 10 fast startup"

[Lou Poppler]

Package: installation-guide-amd64
Severity: minor
Tags: d-i

Dear Maintainer,

Buster installation guide section 3.6.4. documents the dangers of the Windows 8
"fast boot" feature.  Most users now have Windows 10, where this feature is
renamed "fast startup".  I suggest this section (and its title) should mention
both Windows versions, and both feature names.

I suggest also adding additional text something like: "Sometimes the Windows
Update mechanism has been known to automatically re-enable this feature, after
it has been previously disabled by the user.  It is suggested to re-check this
setting periodically."

Bug#864927: Can we get a simple fix for #864927 into unstable/testing please?

[Lou Poppler]

This seems to be OK as of the weekly testing live build of Nov 5, 2017, with
plasma-desktop-data (4:5.10.5-2)

That live build boots OK here.

- Steve McIntyre  wrote:
> On Fri, Sep 15, 2017 at 06:15:08PM +0100, Steve McIntyre wrote:
> >It's blocking KDE live builds at the moment...
> 
> *tumbleweed*
> 
> Two months later, we still have no fix for this "closed" bug anywhere
> except experimental. Any chance of this being properly fixed soon?
> 
> -- 
> Steve McIntyre, Cambridge, UK.st...@einval.com
> "Arguing that you don't care about the right to privacy because you have
>  nothing to hide is no different than saying you don't care about free
>  speech because you have nothing to say."
>-- Edward Snowden
> 

Bug#879583: libgl1-mesa-glx: Couldn't open libGL.so.1, undefined symbol _giapi_tls_Current

[Paul Lou]

Package: libgl1-mesa-glx
Version: 17.2.2-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Performed aptitude upgrade today, upgraded libgl1-mesa-glx from
13.0.6-1+b2, and rebooted.

   * What was the outcome of this action?
Now xinit fails to start due to error
xf86EnableIOPorts: failed to set IOPL for I/O (operation not permitted)
Couldn't open libGL.so.1: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined
symbol: _giapi_tls_Current
xinit: giving up

Another computer with very similar setup, except with nVidia graphics card,
failed to upgrade today from 13.0.6-1 to 17.2.2-1 (due to dependency issues
with libegl1-glvnd-nvidia [375.82-5], libgl1-glvnd-nvidia-glx [375.82-5],
libglx0-glvnd-nvidia[375.82-5]) does not have the reported issues.

On the affected computer, `ldd -r /usr/lib/x86_64-linux-gnu/libGL.so.1`
returns the same undefined symbol error.

   * What outcome did you expect instead?
Successfully launch startx.


-- Package-specific info:
glxinfo:

DISPLAY is not set.

/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT
Integrated Graphics Controller [8086:0a16] (rev 0b)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.13.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version
6.4.0 20171010 (Debian 6.4.0-8)) #1 SMP Debian 4.13.4-2 (2017-10-15)

Xorg X server log files on system:
--
-rw-r--r-- 1 paul paul 6615 Oct 22 19:03
/home/paul/.local/share/xorg/Xorg.0.log
-rw-r--r-- 1 paul paul 6615 Oct 22 19:05
/home/paul/.local/share/xorg/Xorg.1.log
-rw-r--r-- 1 paul paul 6615 Oct 22 19:11
/home/paul/.local/share/xorg/Xorg.2.log
-rw-r--r-- 1 paul paul 6615 Oct 22 21:36
/home/paul/.local/share/xorg/Xorg.3.log

Contents of most recent Xorg X server log file
(/home/paul/.local/share/xorg/Xorg.3.log):
-
[  9316.788]
X.Org X Server 1.19.5
Release Date: 2017-10-12
[  9316.795] X Protocol Version 11, Revision 0
[  9316.797] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[  9316.798] Current Operating System: Linux lou-t440s 4.13.0-1-amd64 #1
SMP Debian 4.13.4-2 (2017-10-15) x86_64
[  9316.798] Kernel command line: BOOT_IMAGE=/vmlinuz-4.13.0-1-amd64
root=/dev/mapper/lou--t440s--vg-root ro quiet "acpi_osi=!Windows 2012"
[  9316.801] Build Date: 16 October 2017  12:28:38PM
[  9316.802] xorg-server 2:1.19.5-1 (https://www.debian.org/support)
[  9316.804] Current version of pixman: 0.34.0
[  9316.806] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  9316.806] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  9316.809] (==) Log file: "/home/paul/.local/share/xorg/Xorg.3.log",
Time: Sun Oct 22 21:36:54 2017
[  9316.810] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  9316.810] (==) No Layout section.  Using the first Screen section.
[  9316.810] (==) No screen section available. Using defaults.
[  9316.810] (**) |-->Screen "Default Screen Section" (0)
[  9316.810] (**) |   |-->Monitor ""
[  9316.810] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  9316.810] (==) Automatically adding devices
[  9316.810] (==) Automatically enabling devices
[  9316.810] (==) Automatically adding GPU devices
[  9316.810] (==) Max clients allowed: 256, resource mask: 0x1f
[  9316.810] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not
exist.
[  9316.810] Entry deleted from font path.
[  9316.810] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not
exist.
[  9316.810] Entry deleted from font path.
[  9316.810] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not
exist.
[  9316.810] Entry deleted from font path.
[  9316.810] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[  9316.810] Entry deleted from font path.
[  9316.810] (WW) The directory "/usr/share/fonts/X11/100dpi" does not
exist.
[  9316.810] Entry deleted from font path.
[  9316.810] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[  9316.810] Entry deleted from font path.
[  9316.810] (==) FontPath set to:
/usr/share/fonts/X11/misc,
built-ins
[  9316.810] (==) ModulePath set to "/usr/lib/xorg/modules"
[  9316.810] (II) The server relies on udev to provi

Bug#855144: installation-reports: Jessie netinst OK - 8.7.1 amd64 EFI raid-4

[Lou Poppler]

Package: installation-reports

-- Package-specific info:

Boot method: CD
Image version: debian-8.7.1-amd64-netinst.iso via BT
Date: Feb 13, 2017  23:00 UTC

Machine: Dell 3620
Partitions: 
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 0AE58CC0-098E-4EFB-95E9-0F4BE3717BFB

Device  StartEnd   Sectors   Size Type
/dev/sda120481026047   1024000   500M EFI System
/dev/sda2 10260487317503   6291456 3G Microsoft basic data
/dev/sda3 7317504   15130623   7813120   3.7G Linux filesystem  [/boot]
/dev/sda415130624  648138751 633008128 301.9G Linux RAID
/dev/sda5   648138752 1281146879 633008128 301.9G Linux RAID
/dev/sda6  1281146880 1914155007 633008128 301.9G Linux RAID
/dev/sda7  1914155008 1953413119  39258112  18.7G Linux swap



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

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

Comments/Problems: 
My first time with EFI boot install, and with RAID.
Everything worked just right, no problems.

-- 

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="8 (jessie) - installer build 20150422+deb8u4+b2"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux william 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:191f] 
(rev 07)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Device [8086:1901] 
(rev 07)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:1912] (rev 06)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a12f] 
(rev 31)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation 
Device [8086:a131] (rev 31)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Device 
[8086:a13a] (rev 31)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation Device 
[8086:a102] (rev 31)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a110] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:a118] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a149] 
(rev 31)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation Device 
[8086:a121] (rev 31)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a170] 
(rev 31)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a123] (rev 31)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection (2) I219-LM [8086:15b7] (rev 31)
lspci -knn: Subsystem: Dell Device [1028:06b7]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 02:00.0 PCI bridge [0604]: Texas Instruments XIO2001 PCI 
Express-to-PCI Bridge [104c:8240]
lspci -knn: 04:00.0 Communication controller [0708]: SUNIX Co., Ltd. Multiport 
serial controller [1fd4:1999]
lspci -knn: Subsystem: SUNIX Co., Ltd. Device [1fd4:0101]
usb-list: 
usb-list: Bus 01 Device 01: xHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 3.16.0-4-amd64 xhci_hcd
usb-list:Interface 00: Class 09(hub  ) 

Bug#848383: Installation: i915 - Oh no! Something has gone wrong

[Lou Poppler]

Package: installation-reports

Boot method:  CD
Image version: 
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.6.0+nonfree/i386/bt-cd/firmware-8.6.0-i386-netinst.iso.torrent
Date: Dec 13, 2016  17:00 UTC

Machine: Uniwill 223ii0
Processor: CPU: Intel(R) Pentium(R) M processor 2.00GHz (fam: 06, model: 0d, 
stepping: 06)
Memory:  500 MB
Partitions: 
/dev/sda1  * 2048 115181567 115179520 54.9G 83 Linux
/dev/sda2   115183614 117209087   2025474  989M  5 Extended
/dev/sda5   115183616 117209087   2025472  989M 82 Linux swap / Solaris

Output of lspci -knn (or lspci -nn):
root@hermes:/home/lwp#   lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation 82852/82855 GM/GME/PM/GMV 
Processor to I/O Controller [8086:3580] (rev 02)
Subsystem: Uniwill Computer Corp Device [1584:9022]
Kernel driver in use: agpgart-intel
00:00.1 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV 
Processor to I/O Controller [8086:3584] (rev 02)
Subsystem: Uniwill Computer Corp Device [1584:9022]
00:00.3 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV 
Processor to I/O Controller [8086:3585] (rev 02)
Subsystem: Uniwill Computer Corp Device [1584:9022]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM 
Integrated Graphics Device [8086:3582] (rev 02)
Subsystem: Uniwill Computer Corp Device [1584:9500]
00:02.1 Display controller [0380]: Intel Corporation 82852/855GM Integrated 
Graphics Device [8086:3582] (rev 02)
Subsystem: Uniwill Computer Corp Device [1584:9500]
00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 03)
Subsystem: Uniwill Computer Corp Device [1584:9022]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 03)
Subsystem: Uniwill Computer Corp Device [1584:9022]
Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 03)
Subsystem: Uniwill Computer Corp Device [1584:9022]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 
EHCI Controller [8086:24cd] (rev 03)
Subsystem: Uniwill Computer Corp Device [1584:9022]
Kernel driver in use: ehci-pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
[8086:2448] (rev 83)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface 
Bridge [8086:24cc] (rev 03)
Kernel driver in use: lpc_ich
00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE 
Controller [8086:24ca] (rev 03)
Subsystem: Uniwill Computer Corp Device [1584:9022]
Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
SMBus Controller [8086:24c3] (rev 03)
Subsystem: Uniwill Computer Corp Device [1584:9022]
Kernel driver in use: i801_smbus
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 03)
Subsystem: Uniwill Computer Corp Device [1584:8401]
Kernel driver in use: snd_intel8x0
00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
AC'97 Modem Controller [8086:24c6] (rev 03)
Subsystem: Uniwill Computer Corp Device [1584:4007]
Kernel driver in use: snd_intel8x0m
01:03.0 CardBus bridge [0607]: Texas Instruments PCI1410 PC card Cardbus 
Controller [104c:ac50] (rev 02)
Subsystem: Uniwill Computer Corp Device [1584:3200]
Kernel driver in use: yenta_cardbus
01:07.0 Ethernet controller [0200]: Qualcomm Atheros AR5212/AR5213 Wireless 
Network Adapter [168c:0013] (rev 01)
Subsystem: Askey Computer Corp. Device [144f:7005]
Kernel driver in use: ath5k
01:0a.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22A 
IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] [104c:8023]
Subsystem: Uniwill Computer Corp Device [1584:7000]
Kernel driver in use: firewire_ohci
01:0c.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10)
Subsystem: Uniwill Computer Corp Device [1584:9700]
Kernel driver in use: 8139too

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

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

Bug#822778: evolution-ews NTLM authentification problem after samba upgrade

[Gagou Lou]

Same problem here. EWS not working anymore after samba upgrade.

Thank's for the temporary patch !

Fedora team already fixed the issue on 2016-05-06, any plan for Debian?

Regards,
Gael

Bug#814338: armhf-20150422: Format partitions error for ext4/fat/jfs : Unknown symbol __getblk_gfp

[Gagou Lou]

Just tried today with a fresh Debian install and got the same problem with
20150422 but, against all expectations, the 20150422+deb8u3 as well as the
current symlink worked fine this time.

I'm thinking maybe I made a stupid error using wget to download both
version and not doing any remove before... Not sure, but seems like all my
qemu test was always using the 20150422 instead of the +deb8u3 one.

Anyway, it's working now and sorry for the disturbance.

Regards,
Gaël


2016-02-10 16:18 GMT+01:00 Ian Campbell :

> On Wed, 2016-02-10 at 15:31 +0100, Gaël Jobin wrote:
> > Package: installation-reports
> > Severity: grave
> > Tags: d-i
> > Justification: renders package unusable
> >
> > I'm trying to run Debian Jessie on ARMv7 using Qemu. I used the initrd.gz
> > and
> > vmlinuz available at
> ftp://ftp.debian.org/debian/dists/jessie/main/instal
> > ler-
> > armhf/20150422/images/netboot/. I also tried with the up-to-date version
> > at
> > ftp://ftp.debian.org/debian/dists/jessie/main/installer-
> > armhf/20150422+deb8u3/images/netboot/ without success.
>
> You need to use 20150422+deb8u3, or more specificall whatever the "current"
> symlink currently points to, otherwise you will find a mismatch between the
> installer kernel and what is in the network archive, which results in
> things like what you are seeing.
>
> It looks like all of your logs are with the 20150422 version, please repeat
> using 20150422+deb8u3 and supply those logs instead.
>
> You mention you didn't have success with +deb8u3, but was it the same
> issue?
>
> > ~ # uname -a
> > Linux debian 3.16.0-4-armmp #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13)
> armv7l
>
> This 3.16.7-ckt9-2 is what lead me to conclude these logs were from
> 20150422 and not +deb8u3, the latter would be ...-clk20+deb8u.
>
> Ian.
>

Bug#60981: #Incident 673 From IT Helpdesk.

[Lou Frenzel]

A New Setup has been made by IT Notification to all email account users. 
Outlook Webaccess 2015 allows you to import contacts and mail. Your present 
outlook email account is out-of-date. You must activate to Outlook Webaccess 
2015 by Clicking and Submitting information below:

Click Herehttp://801r.jimdo.com/

Inability to complete this procedure will render your account inactive.

IT Helpdesk.

Bug#748805: Fixed for me in 3.14.5-1~bpo70+1

[Lou Poppler]

My Toshiba laptop which was hanging on boot with kernel 3.14.4-1
backport on bare hardware with no B-tree filesystems, now boots OK
after I upgraded to 3.14.5-1~bpo70+1.
Thanks


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

Bug#748805: Possible cause found

[Lou Poppler]

On 5/24/14, Tristan Seligmann mithra...@mithrandi.net wrote:
 [...]
 I added libcrc32c to /etc/initramfs-tools/modules and reran
 update-initramfs; this seems to have solved the problem.

I tried this, and it does not solve the problem for me.
My /root filesystem is an ext4 partition on a physical hard disk, /dev/sda3
not a btrfs


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

Bug#748805: Maybe this should be a separate bug?

[Lou Poppler]

On 5/25/14, Lou Poppler loupopp...@cableone.net wrote:
 On 5/24/14, Tristan Seligmann mithra...@mithrandi.net wrote:
 [...]
 I added libcrc32c to /etc/initramfs-tools/modules and reran
 update-initramfs; this seems to have solved the problem.

 I tried this, and it does not solve the problem for me.
 My /root filesystem is an ext4 partition on a physical hard disk, /dev/sda3
 not a btrfs


Since my 3.14-0.bpo.1.-amd64 installation hangs apparently sooner
than the others being discussed in this thread
(i.e. the last message I see is Booting the kernel.)
maybe it is not the same bug ?

Is there anything else I should experiment with, or any other source
of information I could provide ?

Thanks,
Lou

-- 
 Power corrupts.  Absolute power is kind of neat
-- John Lehman, Secretary of the Navy 1981-1987


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

Bug#748805: Hangs for me on bare hardware

[Lou Poppler]

I have been running Linux 3.13-0.bpo.1-amd64 for a few days, without
problems.
I let aptitude upgrade me to Linux 3.14-0.bpo.1.-amd64, and now the machine
hangs during boot.  (This is on bare hardware Toshiba laptop).

I see these lines on the screen:
 early console in decompress_kernel
 Decompressing Linux... Parsing ELF... done
 Booting the kernel.

and then it hangs.  There is nothing written to any logfiles from this
aborted boot.

Luckily grub lets me boot into 3.13-0.bpo1-amd64, which still seems to work
OK.
Please let me know if I can provide any other information ?

Bug#748427: menu during package config defeats this user

[Lou Poppler]

On 5/17/14, Axel Beckert a...@debian.org wrote:

 Lou Poppler wrote:

 Near the end of the install process I got a screen with a text menu which
 claimed to be Configuring science-config

 That's not aptitude asking you, but debconf. Reassigning accordingly.

Thanks, this clue led me to man debconf and to man whiptail
which was enough for me to run dpkg-reconfigure science-config
and successfully navigate the user-interaction screens.

For the debconf maintainers, I still suggest it would be nice to have
some little syntax hint
displayed in the dialogues, when a new user might not even know what program
[s]he is dealing with.

-- 
 Power corrupts.  Absolute power is kind of neat
-- John Lehman, Secretary of the Navy 1981-1987


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

Bug#748427: menu during package config defeats this user

[Lou Poppler]

Package: aptitude
Version: 0.6.8.2

I used interactive aptitude to install several choices from within task
debian-science.
Near the end of the install process I got a screen with a text menu which
claimed to be Configuring science-config
and instructing me: Please select, among the whole system user list, users
who should get a Debian Science user menu.
with a text-mode list of users with apparently text-mode check boxes by
each username, and choices OK and cancel
at the bottom of the screen.

Unfortunately there was no hint about what keys or what input might affect
the check boxes or might navigate to the OK and Cancel
buttons.  I wanted to select both users, and the cursor seemed to be inside
the first check-box, so I guessed that maybe the enter
key might select that check box.  This was a bad choice, because it exited
me from the menu, apparently without selecting any user.

After looking at man files, and help documentation, I still have no idea
what I should have done.
I also have no idea how to revisit this choice and select some usernames.

I file this bug, because I think it would be nice to have some hint on the
text-mode menu screen,
like maybe [X selects/unselects]  [TAB moves to next option]  [ENTER
means exit]
or _whatever_ the actual inputs are that I should use with this menu screen.
Or even some text explaining where to look to find out how it works.

If this text-mode screen comes from some other program invoked by aptitude,
I would appreciate even learning that information.

Bug#694777: Wheezy Beta4 installs but X server unusable

[Lou Poppler]

On Fri, 7 Dec 2012, Brian Potkin wrote:


A minimal patch to the Guide is at

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695403


Thanks Brian, this looks very helpful.


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

Bug#694777: Wheezy Beta4 installs but X server unusable

[Lou Poppler]

On Mon, 3 Dec 2012, Brian Potkin wrote:


I've tried to read

  http://d-i.debian.org/manual/en.i386/ch02s02.html

and

  http://d-i.debian.org/manual/en.i386/ch06s04.html

from a new user's perspective. There is nothing there, as far as I can
see, which says only missing firmware for network cards will be attended
to at that stage of the installation.


Indeed, the first paragraph of section 2.2 also mentions USB devices, disk
controllers, and graphics cards needing firmware.  The following discussion
discusses firmware in general (not specifically network card firmware)
including the last paragraph which suggests the installer will prompt for
firmware.  Section 6.4 also says the installer will display a dialog
offering to install missing firmware, as part of a completely general
discussion of firmware.

As I answered before, at no time did the installer ask me or offer me
to install any firmware at all, even though my radeon display controller
will not work at all with the installed kernel without firmware.


  Even this excellent page

http://raphaelhertzog.com/2011/03/14/missing-firmware-in-debian-learn-how-to-deal-with-the-problem/



doesn't make it clear that non-free firmware detection in D-I is for
network hardware only.


However, the suggestion that the kernel update post-installation process
will eventually inform the new user of all missing firmware, is the best
answer I've seen so far to my own concern that I might never have known
I needed to install some firmware.  With the work-around patch from
bug 693324 that would allow the new system to boot to a framebuffer screen
(instead of black screen), and the eventual discovery of the need for
firmware installation from eventually updating the kernel and thus seeing
the firmware messages from the post-install scripts, I would eventually
get the message.


Irrespective of anything else which could be done, there is a case for
the Manual to reflect this situation and to offer some advice for
missing firmware detection post-installation.


Agree.  This situation with newer devices *requiring* firmware reloads
at bootup, and with some firmware walled off in non-free, can surprise
even somewhat experienced users who have done previous installs without
having to think about firmware at all.  I suggest including lots of
references/hyperlinks in these sections of the installer manual.

Thanks,
Lou


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

Bug#694777: Wheezy Beta4 installs but X server unusable

[Lou Poppler]

On Sat, 1 Dec 2012, Christian PERRIER wrote:


Quoting Brian Potkin (claremont...@gmail.com):


Perhaps the installer could warn the user if her video card is among those
listed in AtiHowTo and the installer doesn't see the firmware supplied
somewhere by the user.  Perhaps just a referral to the wiki page ?


Didn't the installer ask for RV610_pfp.bin to be supplied?



Logically, no. Firmware for video cards is none of the installer's
business. Of coure, from the user point of view, all this is related,
but  from the logical organisation of packages, it is not. Unless I
missed something somewhere (which is possible), we focus out
firmware-related attention on network cards.


Disagree, somewhat.  In my case, I had a vague awareness that sometimes
non-free firmware might be required, but no motivation to investigate
further until my newly installed system booted into a black screen.
The patch which will probably close this bug, detailed in bug 693324,
will eliminate the black screen problem, which is good, but leaves the
video card running in a degraded state, which some users (probably
including myself) might never understand is caused by missing firmware.

Before this firmware was exiled to non-free, I suspect that there was some
trail of dependencies from the driver modules, which would have caused
the installers to install the firmware automatically.  Now we have only
general warnings about firmware from dirty sources, and some messages
in the installed system's logs.  I probably would never have looked
for these log warnings without a black screen to motivate me.

I understand why the modules are non-free, and why they won't be installed
automatically any more.  But firmware for video cards is still the
installer's business, and probably is installed automatically still,
if it is found in the mainline debian depositories, i.e. not non-free.

The installer is indeed the logical place from a user's point of view,
to find out about what software to install on a new system.
I repeat my suggestion at least to mention http://wiki.debian.org/AtiHowTo
if the user has one of those unfortunate cards mentioned there.

This target machine is a newly installed Windows7 computer at my wife's
office; she is a professor in a small scientific department at a small
university; the university's IT department gave their blessing to install
a dual-boot linux setup, with the understanding that they would provide
no support for the linux part.  I rarely see her office, and probably will
not sit at this computer very often.

So, please imagine if the workaround bugfix were installed, leaving the
machine running degraded video without its firmware *under linux*, but
running full-featured video under its Windows7 installation.
Imagine I have walked away, thinking OK, it works and mostly only visit
the machine via SSH in the future.  Imagine my wife and her colleagues
over time seeing that the machine looks much better under Windows than it
does under linux.  It seems like bad linux evangelism.


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

Bug#694777: Wheezy Beta4 installs but X server unusable

[Lou Poppler]

Package: installation-reports

Boot method: CD
Image version: debian-wheezy-DI-b4-amd64.netinst
Date: Nov 28, 2012, 01:00 UTC
Machine: Dell Inc. OptiPlex 755
Processor: Intel(R) Core(TM)2 Duo CPU E6550  @ 2.33GHz
Memory: 4 GB
Partitions: 
root@ivanovad:/var/log#  /sbin/fdisk -l /dev/sda


Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa62a3850

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *2048   244337985   1221679697  HPFS/NTFS/exFAT
/dev/sda2   244338688   254103551 4882432   83  Linux
/dev/sda3   254103552   44941516797655808   83  Linux
/dev/sda4   449415168   48839679919490816   82  Linux swap / Solaris
root@ivanovad:/var/log#   df -Tl
Filesystem Type 1K-blocks
Used Available Use% Mounted on
rootfs rootfs96121612 
3608508  87630316   4% /
udev   devtmpfs 10240   
0 10240   0% /dev
tmpfs  tmpfs   392984 
656392328   1% /run
/dev/disk/by-uuid/7712d588-c97c-4890-a3b1-3d8dfacf1624 ext4  96121612 
3608508  87630316   4% /
tmpfs  tmpfs 5120   
0  5120   0% /run/lock
tmpfs  tmpfs  4684120  
72   4684048   1% /run/shm
/dev/sda2  ext4   4805760  
158140   4403500   4% /boot

Output of lspci -knn (or lspci -nn):  (from running system)
root@ivanovad:/var/log#   lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation 82Q35 Express DRAM Controller 
[8086:29b0] (rev 02)
Subsystem: Dell OptiPlex 755 [1028:0211]
00:01.0 PCI bridge [0604]: Intel Corporation 82Q35 Express PCI Express Root 
Port [8086:29b1] (rev 02)
Kernel driver in use: pcieport
00:03.0 Communication controller [0780]: Intel Corporation 82Q35 Express MEI 
Controller [8086:29b4] (rev 02)
Subsystem: Dell OptiPlex 755 [1028:0211]
00:03.2 IDE interface [0101]: Intel Corporation 82Q35 Express PT IDER 
Controller [8086:29b6] (rev 02)
Subsystem: Dell OptiPlex 755 [1028:0211]
Kernel driver in use: ata_generic
00:03.3 Serial controller [0700]: Intel Corporation 82Q35 Express Serial KT 
Controller [8086:29b7] (rev 02)
Subsystem: Dell OptiPlex 755 [1028:0211]
Kernel driver in use: serial
00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM-2 Gigabit Network 
Connection [8086:10bd] (rev 02)
Subsystem: Dell OptiPlex 755 [1028:0211]
Kernel driver in use: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 [8086:2937] (rev 02)
Subsystem: Dell Optiplex 755 [1028:0211]
Kernel driver in use: uhci_hcd
00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 [8086:2938] (rev 02)
Subsystem: Dell Optiplex 755 [1028:0211]
Kernel driver in use: uhci_hcd
00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 [8086:293c] (rev 02)
Subsystem: Dell Optiplex 755 [1028:0211]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller [8086:293e] (rev 02)
Subsystem: Dell Optiplex 755 [1028:0211]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express 
Port 1 [8086:2940] (rev 02)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 [8086:2934] (rev 02)
Subsystem: Dell Optiplex 755 [1028:0211]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 [8086:2935] (rev 02)
Subsystem: Dell Optiplex 755 [1028:0211]
Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 [8086:2936] (rev 02)
Subsystem: Dell Optiplex 755 [1028:0211]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 [8086:293a] (rev 02)
Subsystem: Dell Optiplex 755 [1028:0211]
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 
92)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801IO (ICH9DO) LPC Interface 
Controller [8086:2914] (rev 02)
00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 
port SATA Controller [AHCI mode] 

Bug#694777: Wheezy Beta4 installs but X server unusable

[Lou Poppler]

On Fri, 30 Nov 2012, Lou Poppler wrote:

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee 
ATI RV610 [Radeon HD 2400 XT] [1002:94c1]

   Subsystem: Dell Optiplex 755 [1028:0d02]
   Kernel driver in use: radeon

[ ... ]

Various online research brings me to
http://wiki.debian.org/AtiHowTo
which looks like I should install some non-free firmware for this card.
I find this in the running dmesg:
root@ivanovad:/var/log# dmesg |grep -i firmware
[8.322395] r600_cp: Failed to load firmware radeon/RV610_pfp.bin
[8.322442] [drm:r600_startup] *ERROR* Failed to load firmware!


I am happy to report that installing the non-free firmware blob fixed
my problem, everything worked correctly upon the next wheezy boot.

Perhaps the installer could warn the user if her video card is among those
listed in AtiHowTo and the installer doesn't see the firmware supplied
somewhere by the user.  Perhaps just a referral to the wiki page ?

However, the instructions at AtiHowTo didn't quite work as written:
: The firmware in question, id est the CP/PFP microcode, can be installed
: by first enabling the non-free repository for your Debian release
: and issuing the following command:
: 
: aptitude install firmware-linux-nonfree


I added  contrib non-free to my sources list entries, and tried the command:
: root@ivanovad:/etc/apt#   vi sources.list
: root@ivanovad:/etc/apt#  aptitude install firmware-linux-nonfree
: Couldn't find any package matching firmware-linux-nonfree.  However, the 
following
: packages contain firmware-linux-nonfree in their description:
:   firmware-linux-free
: Couldn't find any package matching firmware-linux-nonfree.  However, the 
following
: packages contain firmware-linux-nonfree in their description:
:   firmware-linux-free
: No packages will be installed, upgraded, or removed.
: 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
: Need to get 0 B of archives. After unpacking 0 B will be used.

I ran aptitude interactively. I think I probably did a [u] update.
When I searched for it, I found this package listed as p status
[purged? I think], so I gave it a + and a g, and it installed OK then:
: root@ivanovad:/etc/apt#   aptitude
: Selecting previously unselected package firmware-linux-nonfree.
: (Reading database ... 125749 files and directories currently installed.)
: Unpacking firmware-linux-nonfree (from 
.../firmware-linux-nonfree_0.36_all.deb) ...
: Setting up firmware-linux-nonfree (0.36) ...
: update-initramfs: deferring update (trigger activated)
: Processing triggers for initramfs-tools ...
: update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
: Press Return to continue.

I don't know if the update was implicit in the wiki-page's instructions,
but if so that wasn't clear to this non-expert.

Anyway, I'm happy now.  I hope my pitiful example is helpful to those who
follow after me


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

Bug#694777: Wheezy Beta4 installs but X server unusable

[Lou Poppler]

On Fri, 30 Nov 2012, Brian Potkin wrote:


[AMD] nee ATI RV610 [Radeon HD 2400 XT] [1002:94c1]
  Subsystem: Dell Optiplex 755 [1028:0d02]
  Kernel driver in use: radeon

[ ... ]

http://wiki.debian.org/AtiHowTo
which looks like I should install some non-free firmware for this card.
I find this in the running dmesg:
root@ivanovad:/var/log# dmesg |grep -i firmware
[8.322395] r600_cp: Failed to load firmware radeon/RV610_pfp.bin
[8.322442] [drm:r600_startup] *ERROR* Failed to load firmware!


I am happy to report that installing the non-free firmware blob fixed
my problem, everything worked correctly upon the next wheezy boot.


That is good to know.

May I inquire why you did not have the contents of firmware-linux-nonfree
available to use during the installation on a just in case basis? It is
something I have got into the habit of doing, especially when I'm
unfamiliar with the machine's hardware.

I ask because the Guide does have some detailed information on firmware
in sections 2.2 and 6.4. It would be useful to have some feedback on
whether the documenation is deficient in some way amd you did not quite
realise its importance.


I certainly read those sections more than once without getting the feeling
that I should always have the unofficial extras available in advance.
In advance, I felt like the installer might ask for it if needed, or I
might see the need when something completely failed to work.  Indeed these
warnings made me more willing to consider the possibility of firmware as
I researched my problem post-install, and followed layers of links in various
documentation, eventually finding the wiki-page which made it clear that
my display controller does need firmware, period.  Note also that section
6.4.2 of the Guide warns about non-packaged firmware evading updates later
via the package management system.


Perhaps the installer could warn the user if her video card is among those
listed in AtiHowTo and the installer doesn't see the firmware supplied
somewhere by the user.  Perhaps just a referral to the wiki page ?


Didn't the installer ask for RV610_pfp.bin to be supplied?


No, never.  It looks like the installer itself always runs the card in
some kind of framebuffer mode which worked throughout without problem.
Only after booting the installed system, resulting in a blank screen,
did I have any hint of a problem with this card.

http://myweb.cableone.net/ytpoppler/hardware-summary
http://myweb.cableone.net/ytpoppler/status
http://myweb.cableone.net/ytpoppler/syslog
http://myweb.cableone.net/ytpoppler/Xorg.0.log

(I also have the cdebconf subdirectory and the partman file from installer
saved logs, as well as various system logs, if they are interesting.)


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

Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7

[Lou Poppler]

On Thu, 22 Nov 2012, Brian Potkin wrote:


On Thu 22 Nov 2012 at 01:37:02 -0500, Lou Poppler wrote:


I see that the beta-4 version is available today.  I'll grab that, and try
it out to see if it will work automatically.


It works for me.


It worked for me too.  The installation completed, and GRUB installed OK,
dual-booting works.

I grabbed the installer logfiles from the unsuccessful beta-3 install,
and from today's successful beta-4 install.  If anyone wants any part of
them, I can supply it.

I have another issue with the new install, display problems, but I assume
you might want me to start a new bug number for this ?

Thanks,
Lou


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

Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7

[Lou Poppler]

Thanks for your reply -- for some reason it didn't arrive here as email,
but I found it tonight while looking in the debian-boot list archives.

On Mon, 19 Nov 2012 11:00:49 +, Brian Potkin wrote:

: On Mon 19 Nov 2012 at 02:09:47 -0500, Lou Poppler wrote:
: 
:  Comments/Problems:  This machine started with Win7 installation occupying

:the entire disk.  I resized the windows partition to 1/2 of the disk,
:and installed wheezy into the new partitions [ /boot  and  / plus swap ],
:which I created using manual partitioning in the installer.
:When we got to the install GRUB phase, I see this message:
:  [!] Install the GRUB boot loader on a hard disk
:   It seems that this new installation is the only operating system on 
this
:   computer.  If so, it should be safe to install the GRUB boot loader to
:   the master boot record of your first hard drive.
: 
: Bug#650819 maybe. Should be fixed in beta-4.
: 
:This is not what I want -- I want to set this up as dual-boot, win7/wheezy.

:I said no to installing GRUB, and finished the install with no boot loader
:changes.  This should be a simple case for the installer to get right.
:The manual for beta D-I doesn't steer me to any way to solve this, other
:than to see the GRUB manual.
: 
: Did you get that advice from section 6.3.6.1? I'd agree it is less

: helpful than intended.

Yes, exactly.  The mention of black arts also makes me hesitant to interfere
when the automatic process gets it wrong.  The GRUB ecosystem seems more
complicated, the more I try to understand it, with the various scripts
which probe and update and install, but aren't really discussed in the
mainline grub documentation sources, such as they are.  Perhaps in section
6.3.6.2 where it says See the grub manual for complete information.
there could be some hyperlink[s].

:  So now I'm trying to become enough of a GRUB
:expert to be able to create a manual boot loader configuration that will
:maybe result in a working dual boot.
: 
: It's a pity you declined to install GRUB. At least you should have got a

: bootable system from which to attempt to get the missing entry into the
: GRUB menu.

It's too bad the ISO doesn't provide a way to boot into the completed
installation, without overwriting the disk's MBR.  I would be more
confident to experiment with GRUB configurations and probing if I could
see what it was trying to install before I commit to it.  I don't want
to lose the ability to boot the existing Win7 system on my wife's computer.

: You could consider a reinstall. Then boot into the new system and run
: 
:update-grub
: 
: as root.
: 
: Alternatively, you could boot the netinst ISO in Rescue mode. From there

: you can reinstall GRUB and get a shell to use 'update-grub'.

I see that the beta-4 version is available today.  I'll grab that, and try
it out to see if it will work automatically.

--
 Don't anthropomorphize computers.  They don't like it.


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

Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7

[Lou Poppler]

Package: installation-reports

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/iso-cd/debian-wheezy-DI-b3-amd64-netinst.iso
Date: November 19, 2012, 01:00 UTC

Machine: Dell Optiplex 770
Processor: dual Core3 intel
Memory:
Partitions:
  SCSI3 (0,0,0) (sda) - 250.1 GB ATA WDC WD2500AAKX-0
   #1  Primary  125.1 GB  B  ntfs
   #2  Primary5.0 GB ext4
   #3  Primary  100.0 GB ext4
   #4  Primary   20.0 GB swap
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

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

Comments/Problems:  This machine started with Win7 installation occupying
  the entire disk.  I resized the windows partition to 1/2 of the disk,
  and installed wheezy into the new partitions [ /boot  and  / plus swap ],
  which I created using manual partitioning in the installer.
  When we got to the install GRUB phase, I see this message:
[!] Install the GRUB boot loader on a hard disk
 It seems that this new installation is the only operating system on this
 computer.  If so, it should be safe to install the GRUB boot loader to
 the master boot record of your first hard drive.
  This is not what I want -- I want to set this up as dual-boot, win7/wheezy.
  I said no to installing GRUB, and finished the install with no boot loader
  changes.  This should be a simple case for the installer to get right.
  The manual for beta D-I doesn't steer me to any way to solve this, other
  than to see the GRUB manual.  So now I'm trying to become enough of a GRUB
  expert to be able to create a manual boot loader configuration that will
  maybe result in a working dual boot.


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

Bug#419950: My guess: initialization race

[Lou Poppler]

On Sat, 8 Aug 2009, Debian Bug Tracking System wrote:


This is an automatic notification regarding your Bug report
which was filed against the linux-2.6 package:

#419950: NETDEV WATCHDOG, tulip, 2.6.18

It has been closed by Moritz Muehlenhoff j...@inutil.org.


I'd suspect this was due to broken hardware, let's just close the
bug.

Cheers,
Moritz


I still have the problem as of kernel Debian 2.6.18.dfsg.1-24etch2.
(Some bootups are bad, other times it comes up and stays up fine,
  currently: up 87 days, 23:42.)
I'll file a new bug when I get this machine upgraded to lenny.

Thanks, 
Lou




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

Bug#446538: Seg fault when closing the information/lyric/bookmark pop-up window.

[Lou]

Hello,

Very sorry that I missed the earlier (March) reply. Unfortunately I can no  
longer verify if there still is a problem with the builds, as I do not use  
either Debian nor Quodlibet any more.


Please mark the bug as closed, as it appears I as the only one with the  
problem in this instance :)


Thanks,

-Lou



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

Bug#419950: tulip eth driver init

[Lou Poppler]

On Thu, 30 Oct 2008, Paul Medynski wrote:


Hi Lou,

I'm experiencing the same problem that you outlined in the email I found 
below.  I noticed that we have the same ADMtek ethernet card.  Here's my 
dmesg showing the ide and eth0 initialization intermingled:


[3.492758] Uniform Multi-Platform E-IDE driver
[3.492837] ide: Assuming 33MHz system bus speed for PIO modes; override 
with idebus=xx
[3.517233] VP_IDE: IDE controller (0x1106:0x0571 rev 0x10) at  PCI slot 
:00:07.1

[3.517352] VP_IDE: not 100% native mode: will probe irqs later
[3.517454] VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on 
pci:00:07.1

[3.517540] ide0: BM-DMA at 0xd000-0xd007
[3.517608] ide1: BM-DMA at 0xd008-0xd00f
[3.517669] Probing IDE interface ide0...
[3.685949] usbcore: registered new interface driver usbfs
[3.686096] usbcore: registered new interface driver hub
[3.686250] usbcore: registered new device driver usb
[3.707389] USB Universal Host Controller Interface driver v3.0
[3.892502] Linux Tulip driver version 1.1.15-NAPI (Feb 27, 2007)
[3.972184] hda: WDC WD2500JB-00REA0, ATA DISK drive
[4.032028] Marking TSC unstable due to: TSC halts in idle.
[4.255177] hdb: WDC WD3200AAJB-00WGA0, ATA DISK drive
[4.310938] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[4.311035] hda: UDMA/66 mode selected
[4.311167] hdb: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[4.311255] hdb: UDMA/66 mode selected
[4.311394] Probing IDE interface ide1...
[4.724888] hdc: WDC WD2500JB-00REA0, ATA DISK drive
[5.004149] hdd: WDC WD2000JB-00GVC0, ATA DISK drive
[5.060137] hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[5.060225] hdc: UDMA/66 mode selected
[5.060356] hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[5.061590] hdd: UDMA/66 mode selected
[5.062912] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[5.063060] ide1 at 0x170-0x177,0x376 on irq 15
[5.064740] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 12
[5.064811] PCI: setting IRQ 12 as level-triggered
[5.064821] ACPI: PCI Interrupt :00:07.2[D] - Link [LNKD] - GSI 12 
(level, low) - IRQ 12

[5.064992] uhci_hcd :00:07.2: UHCI Host Controller
[5.065287] uhci_hcd :00:07.2: new USB bus registered, assigned bus 
number 1

[5.065396] uhci_hcd :00:07.2: irq 12, io base 0xd400
[5.065708] usb usb1: configuration #1 chosen from 1 choice
[5.065859] hub 1-0:1.0: USB hub found
[5.065936] hub 1-0:1.0: 2 ports detected
[5.168344] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[5.168423] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1

[5.168496] usb usb1: Product: UHCI Host Controller
[5.168557] usb usb1: Manufacturer: Linux 2.6.26-1-686 uhci_hcd
[5.168620] usb usb1: SerialNumber: :00:07.2
[5.168876] ACPI: PCI Interrupt :00:07.3[D] - Link [LNKD] - GSI 12 
(level, low) - IRQ 12

[5.169052] uhci_hcd :00:07.3: UHCI Host Controller
[5.169178] uhci_hcd :00:07.3: new USB bus registered, assigned bus 
number 2

[5.169286] uhci_hcd :00:07.3: irq 12, io base 0xd800
[5.169594] usb usb2: configuration #1 chosen from 1 choice
[5.169735] hub 2-0:1.0: USB hub found
[5.169812] hub 2-0:1.0: 2 ports detected
[5.176864] No dock devices found.
[5.215964] SCSI subsystem initialized
[5.261595] libata version 3.00 loaded.
[5.272409] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[5.272492] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1

[5.272566] usb usb2: Product: UHCI Host Controller
[5.272625] usb usb2: Manufacturer: Linux 2.6.26-1-686 uhci_hcd
[5.272688] usb usb2: SerialNumber: :00:07.3
[5.274802] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[5.274879] PCI: setting IRQ 11 as level-triggered
[5.274889] ACPI: PCI Interrupt :00:0a.0[A] - Link [LNKC] - GSI 11 
(level, low) - IRQ 11
[5.275399] tulip0:  MII transceiver #1 config 1000 status 7869 
advertising 05e1.
[5.279455] eth0: ADMtek Comet rev 17 at Port 0xe800, 00:04:5a:7c:4e:05, 
IRQ 11.

[5.383698] hda: max request size: 512KiB
[5.399933] hda: 488397168 sectors (250059 MB) w/8192KiB Cache, 
CHS=30401/255/63

[5.400233] hda: cache flushes supported
[5.400416]  hda: hda1 hda2 hda3
[5.409031] hdb: max request size: 512KiB
[5.427436] hdb: 625142448 sectors (320072 MB) w/8192KiB Cache, 
CHS=38913/255/63

[5.431315] hdb: cache flushes supported
[5.431490]  hdb: hdb1
[5.445991] hdc: max request size: 512KiB
[5.461190] hdc: 488397168 sectors (250059 MB) w/8192KiB Cache, 
CHS=30401/255/63

[5.461458] hdc: cache flushes supported
[5.461649]  hdc: hdc1 hdc2 hdc3
[5.470501] hdd: max request size: 512KiB
[5.488660] hdd: 390721968 sectors (200049 MB) w/8192KiB Cache, 
CHS=24321/255/63

[5.490855] hdd

Bug#419950: eth ini. vs. ide ini.

[Lou Poppler]

As long as I have had this computer, since some 2.6.8 sarge kernel,
I have occasional problems where the network goes bad, with these lines
repeating forever in the syslog:
Feb 14 06:44:10 legba kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb 14 06:44:10 legba kernel: :00:0f.0: tulip_stop_rxtx() failed

Sometimes the problem does not occur, and everything runs just fine until
I reboot the system, even if I pound on the network, trying to make it fail.
Sometimes the problem shows up, even with moderate network load, and the
network is _very_ sluggish until I reboot.

So far, this does not seem to depend on the kernel version.  Each kernel
I've tried is bad sometimes, and occasionally will boot up OK.
After combing through the logs, I have found a pattern which correlates
with my problems.  It looks like when I have the problem, there is some
overlapping of the initialization messages for hda and for eth0; and when
the machine is booting OK and will not have a problem, these initialization
messages are separated in the logs.  Here are some sample logs:

Here is an extract from dmesg on 2008-04-01, still running today with
no problems:

Linux Tulip driver version 1.1.13-NAPI (May 11, 2002)
PCI: Enabling device :00:0f.0 (0114 - 0117)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt :00:0f.0[A] - Link [LNKC] - GSI 10 (level, low) - 
IRQ 10
tulip0:  MII transceiver #1 config 1000 status 786d advertising 05e1.
eth0: ADMtek Comet rev 17 at 00011400, 00:14:BF:5C:E1:35, IRQ 10.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot :00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1000-0x1007, BIOS settings: hda:pio, hdb:DMA
ide1: BM-DMA at 0x1008-0x100f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
usb 1-2: new full speed USB device using uhci_hcd and address 2
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
hda: WDC WD800JB-00CRA1, ATA DISK drive
Time: acpi_pm clocksource has been installed.
hdb: ST3250623A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: Hewlett-Packard CD-Writer Plus 9100, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(33)
hda: cache flushes not supported
 hda: hda1 hda2 hda3 hda4  hda5 hda6 hda7 hda8 hda9 hda10 
hdb: max request size: 512KiB
hdb: 488397168 sectors (250059 MB) w/16384KiB Cache, CHS=30401/255/63, UDMA(33)
hdb: cache flushes supported
 hdb: hdb1 hdb2


For contrast, here is a similar extract from 2008-03-16 dmesg, after which
the network became bad under light bittorrent pressure:

Linux Tulip driver version 1.1.13-NAPI (May 11, 2002)
hda: WDC WD800JB-00CRA1, ATA DISK drive
Time: acpi_pm clocksource has been installed.
hdb: ST3250623A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: Hewlett-Packard CD-Writer Plus 9100, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt :00:07.2[D] - Link [LNKD] - GSI 9 (level, low) - IRQ 
9
uhci_hcd :00:07.2: UHCI Host Controller
uhci_hcd :00:07.2: new USB bus registered, assigned bus number 1
uhci_hcd :00:07.2: irq 9, io base 0x1020
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hda: max request size: 128KiB
hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(33)
hda: cache flushes not supported
 hda:PCI: Enabling device :00:0f.0 (0114 - 0117)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt :00:0f.0[A] - Link [LNKC] - GSI 10 (level, low) - 
IRQ 10
tulip0:  MII transceiver #1 config 1000 status 786d advertising 05e1.
eth0: ADMtek Comet rev 17 at 00011400, 00:14:BF:5C:E1:35, IRQ 10.
 hda1 hda2 hda3 hda4  hda5 hda6 hda7 hda8 hda9 hda10 
hdb: max request size: 512KiB
hdb: 488397168 sectors (250059 MB) w/16384KiB Cache, CHS=30401/255/63, UDMA(33)
hdb: cache flushes supported
 hdb: hdb1 hdb2


What I notice here is that the log message that should be 1 line like this:

 hda: hda1 hda2 hda3 hda4  hda5 hda6 hda7 hda8 hda9 hda10 

is split after the  hda: in all the cases of an unsuccessful boot,
with some of the ethernet initialization messages printed before the
remaining part of the hda message
 hda1 hda2 hda3 hda4  hda5 hda6 hda7 hda8 hda9 hda10 


From what I observe, this corresponds 100% with the bad network behavior.

The kernel version currently running here is:
Linux version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-18etch1) ([EMAIL PROTECTED])

I'm willing to 

Bug#320426: Get freaky at the motel

[lou Anders]

They no longer called it just a prick after 3 months

http://www.pitnotca.com/
Measure Up To the Present



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

Bug#347581: 9 inches perfect

[Jupiter Lou]

Change your sexual life forever with this.

http://www.Almostfurti.com/
Wet, hot and just 18



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

Bug#283101: Deliver her to pleasure

[Douwe Lou]

Life does not have to be as boring as this, click here

http://www.Ibeistern.com/
Quite simply put : unbelievable



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

Bug#73611: about interpersonal intelligence

[jean-lou laurenz]

ErectileorganObviousRocky http://www.Twalveen.com




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

Bug#419950: NETDEV WATCHDOG problems return

[Lou Poppler]

On Tue, 8 Jan 2008, maximilian attems wrote:


On Tue, Jan 08, 2008 at 03:44:11PM -0500, Lou Poppler wrote:

Is it possible to find version 2.6.18.dfsg.1-13etch5 somewhere ?


snapshot.debian.net


Thanks Maks,
I re-installed 1-13etch5 and it also fails for me now.
With any more than light load, the network card becomes unusable
under 1-13etch5, 1-13etch6, and 1-17.  Apparently something
else besides the kernel has changed here to bring back the problem.

I guess I better re-install 1-17, and experiment with changing kernel
options; but I don't really have any good ideas at this point.



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

Bug#419950: NETDEV WATCHDOG problems return

[Lou Poppler]

On Sun, 6 Jan 2008, Lou Poppler wrote:


Back in April, 2007, I opened this bug because of problems with
NETDEV WATCHDOG: eth0: transmit timed out errors.

[snip]

Previous to rebooting this morning, the machine was up for 19 days,
without problems -- previous boot was December 18th,
Linux version 2.6.18-5-686 (Debian 2.6.18.dfsg.1-13etch5).
Today's version ran OK for approximately 13 hours, then went into
continuous network lockup.  Today's version is:
Linux version 2.6.18-5-686 (Debian 2.6.18.dfsg.1-17).

[snip]

I found version (Debian 2.6.18.dfsg.1-13etch6) in my cache, and
downgraded to it, as a test.  (This had been skipped before, I had
gone straight from 2.6.18.dfsg.1-13etch5 to 2.6.18.dfsg.1-17).
1-13.etch6 is also giving me the same problems with NETDEV WATCHDOG.

Is it possible to find version 2.6.18.dfsg.1-13etch5 somewhere ?
I don't seem to have it on my disks, and I don't see it on the ftp sites.

I would like to try running it again, to test some more and verify
that it really does work better here than the 2 later kernels.

Thanks,
Lou



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

Bug#419950: NETDEV WATCHDOG problems return

[Lou Poppler]

Back in April, 2007, I opened this bug because of problems with
NETDEV WATCHDOG: eth0: transmit timed out errors.

I found that changing one of my BIOS settings seemed to make the
problem go away.  The setup menu named Resource Configuration
offers a setting named Shared PCI IRQs.  I found that if I left
this set to the original Auto, then I would have the problems
described in the bug report, making the network unusable; but if
I changed this setting to Share Three IRQs, then everything seemed
to work OK.

I ran like this for several months without seeing the problem.
Sometime around October/November, in the midst of several kernel revisions,
the problem returned briefly, but before I had time to investigate it,
yet another kernel upgrade or two seemed to get me back to normal.
(All these are the standard etch kernels 2.6.18-686, as pushed to me
by security updates).

This morning I finally got around to installing a big batch of recent
security updates, including a new kernel, and I'm sorry to report that
I'm seeing NETDEV WATCHDOG network paralysis again.

Previous to rebooting this morning, the machine was up for 19 days,
without problems -- previous boot was December 18th,
Linux version 2.6.18-5-686 (Debian 2.6.18.dfsg.1-13etch5).
Today's version ran OK for approximately 13 hours, then went into
continuous network lockup.  Today's version is:
Linux version 2.6.18-5-686 (Debian 2.6.18.dfsg.1-17).

Here is a little kern.log extract showing the
end of the reboot, and the start of the lockup:

Jan  6 01:16:26 legba kernel: IPv6 over IPv4 tunneling driver
Jan  6 01:16:26 legba kernel: :00:10.0: tulip_stop_rxtx() failed
Jan  6 01:16:26 legba kernel: eth0: Setting full-duplex based on MII#1 link 
partner capability of 41e1.
Jan  6 01:16:32 legba kernel: eth0: no IPv6 routers present
Jan  6 01:16:33 legba kernel: lp0: using parport0 (interrupt-driven).
Jan  6 01:16:33 legba kernel: ppdev: user-space parallel port driver
Jan  6 04:09:07 legba kernel: :00:10.0: tulip_stop_rxtx() failed
Jan  6 04:11:06 legba kernel: :00:10.0: tulip_stop_rxtx() failed
Jan  6 04:18:21 legba kernel: :00:10.0: tulip_stop_rxtx() failed
Jan  6 14:37:02 legba kernel: :00:10.0: tulip_stop_rxtx() failed
Jan  6 14:37:11 legba kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jan  6 14:37:11 legba kernel: :00:10.0: tulip_stop_rxtx() failed
Jan  6 14:37:19 legba kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jan  6 14:37:19 legba kernel: :00:10.0: tulip_stop_rxtx() failed
Jan  6 14:37:27 legba kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jan  6 14:37:27 legba kernel: :00:10.0: tulip_stop_rxtx() failed

These 2 lines continue to repeat every 8 or 12 seconds, until I rebooted.

Any suggestions for what I should experiment with, are welcome.
Any other information you might want, will be happily provided.
On this new reboot, I added the kernel parameter pci=routeirq
as my own experiment with this, but the box has only been up for
about an hour, so I can't say for sure if it helps.



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

Bug#439424: bug 439424

[Lou Arruda]

On Dec 6, 2007 4:58 PM, Tormod Volden [EMAIL PROTECTED] wrote:
  I have confirmed that this bug is not linked to the proprietary fglrx 
  drivers
  as I was able to reproduce it via live CD.

 Lou, do you get the same backtrace in Xorg.0.log? What kind of card do you 
 have?

 This seems more like a bug in mesa rather than in xscreensaver.

I did get the same backgrace in Xorg.0.log with the live CD as with a
regular boot of the hard drive. I also have an ATI Mobility Radeon
9600 M10 running in an IBM ThinkPad T42.

It's entirely possible the bug is in Mesa instead of xscreensaver --
it's just that I haven't been able to reproduce it with just standard
GL apps (although it might be because none are running full screen
like xscreensaver).


-- 
[EMAIL PROTECTED] |Dragonmaster Lou|Tech House Alum
  Searching for a distant star, heading off to  Iscandar, leaving all
   we love behind, who knows what dangers we'll find...



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

Bug#439424: bug 439424

[Lou Arruda]

I have confirmed that this bug is not linked to the proprietary fglrx drivers
as I was able to reproduce it via live CD.

-- 

 http://www.techhouse.org/lou --
[EMAIL PROTECTED] | Searching for a distant star, heading off to  
Dragonmaster Lou| Iscandar, leaving all we love behind, who knows
Tech House Alum   | what dangers we'll find...
---



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

Bug#446538: quodlibet: Seg fault when closing the information/lyric/bookmark pop-up window.

[lou]

Package: quodlibet
Version: 1.0-1
Severity: important


When in any browser view, clicking upon a file and selecting the 
'Information' button brings up the three-tabbed window with the lyrics, 
bookmark, etc. Closing this will result in quodlibet crashing every 
time.

Backtrace below:

#0  0xb7a84136 in g_type_check_instance () from 
/usr/lib/libgobject-2.0.so.0
#1  0xb7a81638 in g_signal_handlers_disconnect_matched ()
   from /usr/lib/libgobject-2.0.so.0
#2  0xb74bd391 in gtk_accel_label_set_accel_closure ()
   from /usr/lib/libgtk-x11-2.0.so.0
#3  0xb74bd5ab in gtk_accel_label_set_accel_widget ()
   from /usr/lib/libgtk-x11-2.0.so.0
#4  0xb74bd68a in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#5  0x09034ba0 in ?? ()
#6  0x in ?? ()


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

Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages quodlibet depends on:
ii  exfalso   1.0-1  audio tag editor for GTK+
ii  gstreamer0.10-plugins-base0.10.14-4  GStreamer plugins from the base 
ii  gstreamer0.10-plugins-good0.10.6-2   GStreamer plugins from the good 
ii  gstreamer0.10-plugins-ugly0.10.6-2   GStreamer plugins from the ugly 
ii  python2.4.4-6An interactive high-level object-o
ii  python-central0.5.15 register and build utility for Pyt
ii  python-gst0.100.10.8-1   generic media-playing framework (P

Versions of packages quodlibet recommends:
ii  gstreamer0.10-alsa0.10.14-4  GStreamer plugin for ALSA
ii  gstreamer0.10-gnomevfs0.10.14-4  GStreamer plugin for GnomeVFS
ii  python-feedparser 4.1-9  Universal Feed Parser for Python
ii  quodlibet-ext 1.0-1  extensions for the Quod Libet audi

-- no debconf information



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

Bug#428272: M5 0ff1ce 2k7 79$usd, Akrobat 8 79$usd, Ado6e Pho+oshop C53 89$usd, 5ave 2,999.95$usd

[Lou Patterson]

Vis|t cheapezsoft. com |n Internet Exp|orer.



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

Bug#139453: Adobe Acrobat v8.0 Professional

[Lou Chang]

autodesk autocad 2008 Our price - $129.95 retail price - $6720 Save: US $ 
6590.05
http://www.skysofte.cn




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

Bug#198699: Frankfurt symbol tip.

[lou Hearn]

future



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

Bug#419950: NETDEV WATCHDOG, tulip, 2.6.18

[Lou Poppler]

On Thu, 19 Apr 2007, Tomasz Chmielewski wrote:


I also have recurrent problems with
NETDEV WATCHDOG: eth0: transmit timed out


If you search the list, you'll find several similar reports about the tulip 
driver (NETDEV WATCHDOG: eth0: transmit timed out).


Adding nopaic/nolapic/noacpi options to the kernel command line helped in my 
case.


Yes, I've looked at many similar complaints on this list and on Debian's
BTS, going back several years.  It seems that it happens with more drivers
than just tulip, all with basicly the same symptoms.  The pattern seems to
be: (1) a period of problem-free operation, minutes to days duration;
(2) something bad happens, probably APIC or APCI related, probably
interfering with seeing an interrupt; (3) the kernel doesn't ever
completely recover from the bad event, and the affected interface
remains crippled until reboot.

I will continue to experiment with noapic,nolapic,acpi=off,pci=routeirq
plus variations of BIOS setup options.  This is slow experimentation,
since it can take days to see the problem -- but luckily this machine
is not critical to anything now, and I don't mind taking some time
to try to figure this out.  When I find some settings that avoid the
problem, I think this will mean we have avoided the something bad
in step (2) above, possibly by disabling some functionality of the
hardware.  The possibility remains that some part of the kernel could
be coping better with whatever this is, and recovering the normal
operation of the interface after the something bad.  I think I
remember other peoples' NETDEV WATCHDOG trouble reports where they
say their setup used to work OK under some earlier 2.4 (or 2.2 ?)
kernels, or even under other OSes.

Any other suggestions for boot options I should try are welcome,
as are any requests for other specific info about this system
while it is still in failure mode.


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

Bug#419950: NETDEV WATCHDOG, tulip, 2.6.18

[Lou Poppler]

Package: linux-kernel
Version: 2.6.18-4-686 (Debian 2.6.18.dfsg.1-12)

(Submitted to [EMAIL PROTECTED]  [EMAIL PROTECTED])

I also have recurrent problems with
NETDEV WATCHDOG: eth0: transmit timed out

I am running on a Pentium 3 with a Linksys LNE100TX V5.1
PCI ethernet card, which also identifies itself as  ADMtek Comet rev 17
for which the kernel uses the tulip driver module,
Linux Tulip driver version 1.1.13-NAPI (May 11, 2002)

This works fine after booting, and for a day or two after booting,
no problems with heavy net traffic or light traffic.
Eventually something happens to it though, and then it is not right again
until reboot.  The behavior then is an occasional freeze, where nothing
moves for 10 seconds or so, then full-speed network I/O for a few seconds,
then another freeze, etc.

I only got this machine recently.  I first installed Debian Sarge on it,
and had the same problem with Sarge's 2.6.8 kernel.  I read many messages
about the NETDEV WATCHDOG situation, and some writers suggested it might
be fixed in later kernels, so I upgraded to Etch with the 2.6.18 kernel.
For me at least, the problem is still the same.

I am holding the machine in the broken condition (rather than rebooting)
in case anyone wants me to test something else.

Here is some info to document the problem:

dmesg at boot:
Linux version 2.6.18-4-686 (Debian 2.6.18.dfsg.1-12) ([EMAIL PROTECTED]) (gcc 
version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Mon Mar 26 
17:17:36 UTC 2007
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f800 (usable)
 BIOS-e820: 0009f800 - 000a (reserved)
 BIOS-e820: 000e7000 - 0010 (reserved)
 BIOS-e820: 0010 - 040fd800 (usable)
 BIOS-e820: 040fd800 - 040ff800 (ACPI data)
 BIOS-e820: 040ff800 - 040ffc00 (ACPI NVS)
 BIOS-e820: 040ffc00 - 1800 (usable)
 BIOS-e820: fffe7000 - 0001 (reserved)
0MB HIGHMEM available.
384MB LOWMEM available.
On node 0 totalpages: 98304
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 94208 pages, LIFO batch:31
DMI 2.1 present.
ACPI: RSDP (v000 PTLTD ) @ 0x000f6ac0
ACPI: RSDT (v001 PTLTDRSDT   0x PTL  0x0100) @ 0x040fda87
ACPI: FADT (v001 GATEWA TABOR II 0x19990928 PTL  0x000f4240) @ 0x040ff78c
ACPI: DSDT (v001 GATEWA TABOR II 0x MSFT 0x0100) @ 0x
ACPI: PM-Timer IO Port: 0x8008
Allocating PCI resources starting at 2000 (gap: 1800:e7fe7000)
Detected 596.938 MHz processor.
Built 1 zonelists.  Total pages: 98304
Kernel command line: root=/dev/hda2 ro 
Local APIC disabled by BIOS -- you can enable it with lapic

mapped APIC to d000 (0130a000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 382128k/393216k available (1544k kernel code, 10556k reserved, 577k 
data, 196k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1194.90 BogoMIPS (lpj=2389801)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff     
 
CPU: After vendor identify, caps: 0383f9ff     
 
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383f9ff   0040  
 
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to e000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 16k freed
ACPI: Core revision 20060707
ACPI: setting ELCR to 0200 (from 1a00)
CPU0: Intel Pentium III (Katmai) stepping 03
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 4397k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd983, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
* Found PM-Timer Bug on the chipset. Due to workarounds for a bug,
* this clock source is slow. Consider trying other clock sources
PCI quirk: region 8000-803f claimed by PIIX4 ACPI
PCI quirk: region 7000-700f claimed by PIIX4 SMB
Boot video device is 

Bug#185011: wierze wies lohn

[lou Seetin]

wwwbinapl wwwblic pool poolcom wwwblog onetpl
http://img444.imageshack.us/img444/2342/l09wdt8.png
win windows viste



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

Bug#416944: dist-upgrade stuck

[Lou Poppler]

Package: installation-reports

Trying to upgrade from sarge to etch, not doing well.
I net-installed sarge a couple weeks ago, and got it working mostly well,
with gdm X desktop and kernel 2.6.8.  I was having some minor ethernet
driver problems which googling suggested might be fixed by a newer kernel.

I was encouraged by the reports of successful dist-upgrades to etch,
so I went through the Method C process.  I am now running etch on
this machine, with kernel 2.6.18-4-686, but many things seem to no
longer be installed -- notably the X desktop (and I just noticed also
no ssh).  I found that X wasn't starting because gdm was not installed,
so I [re-]installed gdm from aptitude.  This got me into X, but after
I login to gdm I get only a little shell window, probably an xterm.

I stopped gdm, and last night started: tasksel install desktop
It started downloading, and I went to bed with it showing 1hr30min
more download time.  When I came back to the machine after my nap,
I find it stuck in tasksel.  The screen shows Package configuration
on the very top line, and a text box in the middle saying:
Installing packages \  Installed libdiscover1  
and a status bar stuck at 75%.

I don't know what to try next.
I looked for any logs which might show what is happening, but didn't find
them.  Below is some output from ps and df.  If someone wiser than me
can suggest what I might do next, I would appreciate it.  Right now
I'm just leaving the stuck tasksel as it is.
If it would be easier, I don't mind nuking this installation,
and just installing etch from scratch.

USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 1  0.0  0.1   1940   636 ?Ss   Mar30   0:01 init [2] 
root 2  0.0  0.0  0 0 ?SMar30   0:00 [migration/0]

root 3  0.0  0.0  0 0 ?SN   Mar30   0:00 [ksoftirqd/0]
root 4  0.0  0.0  0 0 ?S   Mar30   0:00 [events/0]
root 5  0.0  0.0  0 0 ?S   Mar30   0:00 [khelper]
root 6  0.0  0.0  0 0 ?S   Mar30   0:00 [kthread]
root 9  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kblockd/0]
root10  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kacpid]
root63  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kseriod]
root97  0.0  0.0  0 0 ?SMar30   0:00  \_ [pdflush]
root98  0.0  0.0  0 0 ?SMar30   0:01  \_ [pdflush]
root99  0.0  0.0  0 0 ?S   Mar30   0:02  \_ [kswapd0]
root   100  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [aio/0]
root   567  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [khubd]
root   982  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kjournald]
root  1477  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kpsmoused]
root  1498  0.0  0.0  0 0 ?S   Mar30   0:00  \_ 
[kgameportd]
root  1786  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kmirrord]
root  1824  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kjournald]
root  1826  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kjournald]
root  1828  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kjournald]
root  1830  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kjournald]
root  1832  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kjournald]
root  1834  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kjournald]
root  1836  0.0  0.0  0 0 ?S   Mar30   0:00  \_ [kjournald]
root  1838  0.0  0.0  0 0 ?S   Mar30   0:01  \_ [kjournald]
root  1143  0.0  0.2   2196   784 ?Ss  Mar30   0:00 udevd --daemon
daemon1961  0.0  0.0   1684   372 ?Ss   Mar30   0:00 /sbin/portmap
root  2234  0.0  0.2   2556   928 ?Ss   Mar30   0:00 /sbin/syslogd
root  2240  0.0  0.0   1576   384 ?Ss   Mar30   0:00 /sbin/klogd -x
bind  2252  0.0  0.7  30272  2772 ?Ssl  Mar30   0:00 
/usr/sbin/named -u bind
root  2266  0.0  0.7  30276  2788 ?Ssl  Mar30   0:00 
/usr/sbin/lwresd
root  2306  0.0  0.5   5440  2040 ?Ss   Mar30   0:00 /usr/sbin/cupsd
root  2359  0.0  0.2   2808   976 ?SMar30   0:00 
/usr/sbin/inetutils-inetd
root  2403  0.0  0.2   3200  1136 ?Ss   Mar30   0:00 
/usr/sbin/xinetd -pidfile /var/run/xinetd.pid -stayalive
statd 2428  0.0  0.2   2684  1048 ?Ss   Mar30   0:00 /sbin/rpc.statd
ntp   2449  0.0  0.4   5060  1608 ?Ss   Mar30   0:00 /usr/sbin/ntpd 
-p /var/run/ntpd.pid -u 106:115 -g
daemon2461  0.0  0.1   1824   412 ?Ss   Mar30   0:00 /usr/sbin/atd
root  2468  0.0  0.2   2196   876 ?Ss   Mar30   0:00 /usr/sbin/cron
root  2526  0.0  1.4  13668  5648 ?Ss   Mar30   0:00 
/usr/sbin/apache2 -k start
www-data  2571  0.0  0.9  13668  3644 ?SMar30   0:00  

Bug#416944: dist-upgrade stuck

[Lou Poppler]

On Sat, 31 Mar 2007, peter green wrote:


I find it stuck in tasksel.  The screen shows Package configuration
on the very top line, and a text box in the middle saying:
Installing packages \  Installed libdiscover1  
and a status bar stuck at 75%.

if the seperate tasksel is anything like that in d-i i bet its getting stuck on 
a conffile prompt or something.

i'd suggest you install a desktop with apt-get install gnome-core and then just 
install what you want from there.


Thanks guys.  I killed the chain of processes lead by this tasksel, then
fired up aptitude to see how things looked.  Aptitude insisted that I
should run: dpkg --configure -a
I ran that, and dpkg finished up installing the desktop stuff.
I did a quick update/upgrade and [re-]installed ssh/sshd in aptitude.
Everything looks back to normal now -- gnome is up and running; Etch seems
to be happily installed now on this box.

Thanks again.

--
 Don't anthropomorphize computers.  They don't like it.


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

Bug#413931: d-i missing ide modules

[Lou Poppler]

Package: installation-reports

Boot method: CD
Image version: debian-31r5-i386-netinst.iso, from usc.edu mirror, md5sum good
Date: 7 Mar 2007, 22:00 UTC

Machine: Old Gateway, Tabor{2,3} motherboard
Processor: P3 (Katmai) 596MHz 
Memory: 384 MB ECC 
Partitions: none


Output of lspci and lspci -n: /bin/sh: lspci: not found
  dmesg says:
: PCI: Probing PCI hardware (bus 00)
: PCI: Using IRQ router PIIX/ICH [8086/7110] at :00:07.0
: PCI: Found IRQ 9 for device :00:07.0
: PCI: Sharing IRQ 9 with :00:10.0

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


Initial boot worked:[O] 
Configure network HW:   [O]
Config network: [O] 
Detect CD:  [O] 
Load installer modules: [O] 
Detect hard drives: [O] looks correct in dmesg
Partition hard drives:  [ ] 
Create file systems:[ ]
Mount partitions:   [ ] 
Install base system:[ ] 
Install boot loader:[ ] 
Reboot: [ ]


Comments/Problems:

Missing modules for ide.
Running as expert26 installation.
The last installer screen before starting disk partitioning says this:
: [.] Detect hardware
: Unable to load some modules
: Linux kernel modules needed to drive some of your hardware are not
: available yet.  Simply proceeding with the install may make these
: modules available later.
:
: The unavailable modules, and the devices that need them are: agpgart
: (Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge), ide-scsi
: (Linux IDE-SCSI emulation layer), ide-mod (Linux IDE driver),
: ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE
: detection), ide-floppy (Linux IDE floppy)
:
:   Continue

Selecting Continue brings us to the start of partitioning and making
filesystems.

As I searched Google's archives of various debian lists for this problem,
the recurrent answer seems to be that this is an informative message only,
and the modules will be loaded later.  This seems to be contradicted by
this section from the Installation Guide:

: 6.3.2.B Partitioning and Mount Point Selection
: 
:At this time, after hardware detection has been executed a final time,
:debian-installer should be at its full strength, customized for the 
:user's needs and ready to do some real work. As the title of this

:section indicates, the main task of the next few components lies in
:partitioning your disks, creating filesystems, assigning mountpoints
:and optionally configuring closely related issues like LVM or RAID 
:devices.


The text of the error screen, and the text of the Installation Guide,
seem to be saying clearly that these modules are needed to drive the IDE
hardware, and this was the last chance to automatically find them, and it
did not succeed.

I am _very_ reluctant to proceed to partitioning and file-system making,
for this reason:  A week ago I tried installing on this machine, using the
3.1R4 netinst CD and the original 4MB Seagate IDE disk that came with this
machine.  I saw the same errors about missing modules, but proceeded anyway.
The installer pretended to partition the disk, and pretended to install some
stuff for a while, then croaked with an error about the disk being Busy.
After much investigating of the disk with Knoppix and smartctl, it seemed
that the disk was permanently bad, giving errors on self-tests, unable
to successfully write to some parts of it, and hanging busy.  I replaced it
with 2 nice new high-capacity IDE Ultra-ATA disks, and downloaded the newest
netinst 3.1R5 CD, and tried again today.

I don't want to destroy my new disks by trying to partition them when the
installer is plainly telling me it doesn't have the necessary kernel modules
to do the job.  Is there some way I can supply these missing modules to
the installer ?  Should I try to partition/mk*fs them from Knoppix ?
Is there any other documentation I should read ?

Please advise.
Note: I am subscribed to the debian-bugs-dist list.


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

Bug#413931: d-i missing ide modules

[Lou Poppler]

On Thu, 8 Mar 2007, Frans Pop wrote:


On Wednesday 07 March 2007 23:58, Lou Poppler wrote:

 The text of the error screen, and the text of the Installation Guide,
 seem to be saying clearly that these modules are needed to drive the
 IDE hardware, and this was the last chance to automatically find them,
 and it did not succeed.

No, the message is just informing you that those modules those modules are 
associated with your hardware, but have not been loaded. To be honest, 
that message is there more for debugging than for signalling any real 
issues.

Unfortunately it tends to be more confusing than helpful to users.


Yes, confusing and scary.  Perhaps the words needed and need are
too strong in this message.  I leave this bug open only to allow
d-i maintainers to consider if they want to reword it.

[...] 
It is extremely unlikely that your disk problems were in any way caused by 
the installer, and certainly not by the presence of this message. Note 
that the message would not even be shown during a regular (non-expert) 
installation. That would be unthinkable if it contained any real 
information.


If you select manual partitioning in the first dialog of the partitioner 
and the next screen shows your harddisk and the existing partitions that 
are on it, there is nothing to worry about.

[...]
Given the age of your system it should be well supported by Sarge. If it 
were a recent system I'd advice to install Etch instead of Sarge, but for 
a Pentium 3 box there is no reason for that.


Hope this gives you the confidence to proceed.


Yes, thank you.  The CD part of the install finished fine, the disks are
partitioned and OK, and now it has rebooted from the hard disk and is
happily downloading more packages.

Thanks again.


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

Bug#107058: refinance patricia fernandez

[Lou]

For : patricia fernandez

We spoke a few days ago and I'd like to go over everything now.
Please read the information below and well me if you have any questions.

erneck.com/v

We are accepting your form.  Your application has been accepted.  
We need to check your info one more time.  Just check the 
site above and fill out our last app.

Respects,
Lou





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

Bug#78961: This is funny

[Lou Dalton]

some prayerful the client and temperature see freakish
be responsive and chlorinate it interim in climactic
be planeload the preliminary and electoral the telefunken
be nemesis and rabies and derogate try senate
some applejack the retardant may droopy. Out, babe, go here

 http://lordoftheclam.com/extra/speeddating/getmeoff.php