Bug#694722: eMachines eM355, encrypted & boots off pendrive, preseeding fails

2012-11-29 Thread Stefan Klinger
Package: installation-reports

Boot method: USB pendrive with debian-wheezy-DI-b4-amd64-netinst.iso
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64
Date: Thu 2012-Nov-29 14:53:32 CET

Machine: eMachines eM355
Processor: Intel Atom N570 CPU @ 1.66GHz
Memory: 1G

Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
rootfs rootfs15622144 1450684  12193636  11% /
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs   101600 340101260   1% /run
/dev/mapper/sda1_crypt btrfs 15622144 1450684  12193636  11% /
tmpfs  tmpfs 5120   0  5120   0% /run/lock
tmpfs  tmpfs   203180   0203180   0% /run/shm
/dev/mapper/sda2_crypt btrfs228571136 152 226445248   1% /usr/local

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: i915
00:02.1 Display controller [0380]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition 
Audio Controller [8086:27d8] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 
1 [8086:27d0] (rev 02)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 
2 [8086:27d2] (rev 02)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI 
Controller #1 [8086:27c8] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI 
Controller #2 [8086:27c9] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI 
Controller #3 [8086:27ca] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI 
Controller #4 [8086:27cb] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI 
Controller [8086:27cc] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
[8086:2448] (rev e2)
00:1f.0 ISA bridge [0601]: Intel Corporation NM10 Family LPC Controller 
[8086:27bc] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
00:1f.2 SATA controller [0106]: Intel Corporation N10/ICH7 Family SATA 
Controller [AHCI mode] [8086:27c1] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller 
[8086:27da] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: i801_smbus
01:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR8152 v2.0 
Fast Ethernet [1969:2062] (rev c1)
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Kernel driver in use: atl1c
02:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless 
Network Adapter (PCI-Express) [168c:002b] (rev 01)
Subsystem: Lite-On Communications Inc Device [11ad:6631]
Kernel driver in use: ath9k


Comments:

I intend to have a completely encrypted harddisk and boot off a separate
pendrive.  apt-cacher on the local network is used to limit network
load, and I wanted (but failed) to use preseeding.

$ curl -OL 
'http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz'
$ curl -OL 
'http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso'

Again, I'm having trouble verifying authenticity of these files.  There
is no such thing as a signature file for `boot.img.gz`.  But even for
the second file, verification does not complete:

$ curl -OL 
'http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64

Bug#694771: installation-reports: s390x installer creates invalid /etc/network/interfaces

2012-11-29 Thread Mikulas Patocka
Package: installation-reports
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?

I installed Debian Wheezy 64-bit s390x in Hercules emulator according to 
these instructions:

http://www.josefsipek.net/docs/s390-linux/hercules-s390.html

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I followed the instructions (with tunnel IP addresses 192.168.144.1 and 
192.168.144.2)

When asked for a domain name, I entered nothing - just . (to forward a 
line to Linux) and enter

   * What was the outcome of this action?

The installation went fine (network was properly working and it was 
possible to download and install all packages from the network). 

However, the installer wrote invalid /etc/network/interfaces on the 
target system.

The file has "dns-search " line. Because the keywork "dns-search" 
doesn't have any parameter, the networking script considers the file 
syntax invalid, refuses to process the file and networking doesn't work 
at all in newly booted system.

The file lacks a "gateway" option, although gateway was entered during 
installation.


The installer created this /etc/networking/interfaces file:
---
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ctc0
iface ctc0 inet static
address 192.168.144.2
netmask 255.255.255.255
network 0.0.0.0
broadcast 255.255.255.255
pointopoint 192.168.144.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.128.1
dns-search 
---

When I removed "dns-serach " from /etc/network/interfaces and added 
"gateway 192.168.144.1", networking works fine in the installed system.

   * What outcome did you expect instead?

/etc/network/interfaces should be correct. There shouldn't be 
"dns-serach " line and there should be "gateway 192.168.144.1" line.

*** End of the template - remove these lines ***


-- Package-specific info:

Boot method: s390x generic kernel and initrd
Image version: 
ftp://ftp.debian.org/debian/dists/wheezy/main/installer-s390x/current/images/generic/
 14th Nov 2012
Date: 30th Nov 2012

Machine: Hercules s390 emulator
Partitions: 


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:  [ ]
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:[E]

Comments/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="7.0 (wheezy) - installer build 20121114"
X_INSTALLATION_MEDIUM=generic

==
Installer hardware-summary:
==
uname -a: Linux z-series 3.2.0-4-s390x #1 SMP Debian 3.2.32-1 s390x GNU/Linux
lspci -knn: pcilib: Cannot open /proc/bus/pci
lspci -knn: lspci: Cannot find any working access method.
lsmod: Module  Size  Used by
lsmod: dm_mod100240  0 
lsmod: md_mod127754  0 
lsmod: xfs   839741  0 
lsmod: ext4  522458  1 
lsmod: crc16  12343  1 ext4
lsmod: jbd2  101583  1 ext4
lsmod: ext3  234115  0 
lsmod: jbd88295  1 ext3
lsmod: vfat   21369  0 
lsmod: fat65583  1 vfat
lsmod: ext2   91301  0 
lsmod: mbcache17129  3 ext2,ext3,ext4
lsmod: lcs43857  0 
lsmod: dasd_eckd_mod  82370  4 
lsmod: ctcm   94140  0 
lsmod: dasd_mod   79914  3 dasd_eckd_mod
lsmod: ccwgroup   17534  2 ctcm,lcs
lsmod: fsm12610  1 ctcm
df: Filesystem   1K-blocks  Used Available Use% Mounted on
df: none 2493220 24912   0% /run
df: tmpfs   124656 0124656   0% /dev
df: /dev/dasda12366068565852   1776180  24% /target
df: /dev/dasda12366068565852   1776180  24% /dev/.static/dev
df: tmpfs   124656 0

Re: Bug#686927: installation does not detect existing Lubuntu

2012-11-29 Thread Rick Thomas


On Nov 29, 2012, at 4:00 AM, Herbert Kaminski wrote:


On Fri, 7 Sep 2012 16:38:31 -0700
Rick Thomas  wrote:

Rick,


I think this is the same as bug#684265, which I submitted a while
back for a PowerPC install using Beta1.


[...]


PS:  Is anybody working on this bug?  It would be a shame if it got
into beta2...


presumably, you already noticed this bug being fixed at last in  
beta-4.


Regards,
 Herbert




Thanks for the check-back...

Yeah, I noticed that Bug#684265 and Bug#686927 got fixed.

But then I noticed that this only fixed half the problem.  If the  
other OS partitions are on LVM, they still are not being discovered by  
the installer.


I submitted Bug#690515 for this, but nobody seems to have had the time  
to look at it yet.


I haven't tried this with Beta-4 yet, but I can personally verify that  
Bug#690515 was definitely present in Beta-3.


Given that Bug#684265 and Bug#6869267 were fixed by including the  
kernel fuse modules in the d-i, I'm hoping that there is another  
missing set of kernel modules that we need to have available in order  
to get access into LVM partitions -- once they are properly included,  
the problem will go away.  But it's all seriously dark-grey magic to  
me and I'm really just guessing.


Enjoy!

Rick


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/97d36d96-719e-4616-91c1-e21407dee...@pobox.com