Bug#685426: closed by Holger Levsen hol...@layer-acht.org (dealing with old installation-reports)

2013-08-31 Thread Holger Levsen
Hi,

On Samstag, 31. August 2013, . wrote:
 Sorry to bug you.

no problem, I said its fine to bother me :) Just do it via the BTS please.
 
 Is there any further explanation needed for this request?
 It really should not be hard to implement.

It _is_ implemented, see 
http://www.debian.org/releases/stable/amd64/ch05s03.html.en#boot-console

Alternativly, use https://wiki.debian.org/DebianInstaller/NetworkConsole
 

cheers,
Holger


signature.asc
Description: This is a digitally signed message part.


Bug#686953: marked as done (installation-reports: mouse wheel does't work during graphical installation)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #686953,
regarding installation-reports: mouse wheel does't work during graphical 
installation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
686953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: minor
Tags: d-i


 During the graphical installation I was trying to use to mouse wheel but it
didn't work. I am installing Debian on a KVM virtual machine under Fedora 15.
The mouse wheel works fine for other virtual machines I have installed (Ubuntu
 Fedora).



-- Package-specific info:

Boot method: network
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_beta1/amd64/iso-cd/debian-wheezy-DI-b1-amd64-netinst.iso
Date: Date and time of the install

Machine: KVM Virtual machine
Partitions: df -Tl will do; the raw partition table is preferred


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

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

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.


-- 

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 20120712
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux de014699 3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: 00:01.2 USB controller [0c03]: Intel Corporation 82371SB PIIX3 USB 
[Natoma/Triton II] [8086:7020] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 
[1013:00b8]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:03.0 Ethernet controller [0200]: Red Hat, Inc Virtio network 
device [1af4:1000]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:0001]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: 00:04.0 Audio device [0403]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller 
[8086:2668] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:05.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block 
device [1af4:1001]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:0002]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: 00:06.0 RAM memory [0500]: Red Hat, Inc Virtio memory balloon 
[1af4:1002]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:0005]
lspci -knn: Kernel driver in use: virtio-pci
usb-list: 
usb-list: Bus 01 Device 01: UHCI Host Controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 3.2.0-3-amd64 uhci_hcd

Bug#697442: marked as done (Bad experiences with wheezy installer)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #697442,
regarding Bad experiences with wheezy installer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
697442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: CD

Image version:
http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso

Date: 2013-01-04 22:00 UTC

Machine: HP Proliant Microserver
Processor: amd64 Turion
Memory: 2G
Partitions: there's the problem :-)

Output of lspci -knn (or lspci -nn):

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:  [E ]
Install base system:[E ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:  *** rant warning ***

  I'm trying to setup partitions like
1: sda1 /boot ext4 250MB
2: sda2 250G encrypted
 lvm vg00
 lv 10MB root
xfs to be mounted as root file system

It doesn't work.  It seems to do the right thing but cannot create xfs fs.
  It will create an ext4 fs but can't use that either!
  In install phase it thinks all debs are corrupted. Very
  difficult to stop the install phase when it errors.

If you revert to shell you can create luks partitition, create lvm pv, create
vg and lv.  In that lv mkfs.xfs fails - wrong tag size or something.  It seems
to know nothing about the partition. You can create an ext4 fs in the lv,
mount it and read it.  If you mount it on /target/root and select 'install
base system' it insists on returning to partitioner but that fails to use
mounted root fs and kindly umounts it.

It behaves the same with graphical and dialog installer.

It's not a nice tool to use especially the partitioner.  Half the menu goes
off the bottom of the screen, you don't know whether to choose 'done' or
'continue' or 'go back', there's no abort to main process menu and 'go back
shouldn't mean restart.  Really, you need just one menu and it needs to be
consistent and it needs to do as it's told. But most of all, it needs to
handle errors properly.

I gave up - I couldn't figure what was wrong.  I then tried netinst using PXE.
 That hangs (needs power cycle) when you do 'configure keyboard'. Skipped that
phase and it went better. I managed to complete installation but it won't
boot.  Initramfs issues the cryptsetup password prompt and then hangs (needs
power cycle).  I wonder if the problem with kbd config and cannot read
keyboard at boot are related. But I can't puzzle it out.

I've spent hours on it now and I'm giving up.  I've got another system,
identical h/w and config, which I just dist-upgraded to wheezy with just a few
minor problems so I think I'll copy that.

Finally a WIBNI.  It would save a lot of hassle if it was possible to save
initial, network and the partition configs to, say, a usb stick, so one
doesn't have to go round and round that loop when things don't work. I must
have done it all 20 times.

All the best

Dick

BTW if you enter a partition size of 20G it will will give you 8.4G.  You have
to specify 20GB.  It's just a little thing but it is so annoying.
---End Message---
---BeginMessage---
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See 

Bug#696770: marked as done (installation-report for 7.0 Beta4 CD1)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #696770,
regarding installation-report for 7.0 Beta4 CD1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
696770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: installation-reports

Hi devs,

I got a new machine so I can now use the old one to play around on. I did an 
installation of 7.0 Beta4 Cd1 on my old machine.  I decided to approach this 
as a newbie and my impressions.  It's all my notes I made to myself.  Kind of 
on the verbose side.  I hope you find it useful and feel free to ask me any 
questions.  Thanks for all the work you do.


Nick Marshall




Package: installation-reports

Boot method: CD.
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_beta4/i386/iso-cd/debian-wheezy-DI-b4-i386-CD-1.iso

Date: 2012.12.24-25

Machine:  Compaq Deskpro EN
Processor: PIII Coppermine 730.93MHz
Memory: 377MB
Partitions:

Filesystem Type 1K-blocks Used 
Available Use% Mounted on
rootfs rootfs 4804736 
3517640   1043028  78% /
udev   devtmpfs 10240 0 
10240   0% /dev
tmpfs  tmpfs38328 580 
37748   2% /run
/dev/disk/by-uuid/983e9f6a-471a-4f81-b28b-391651641240 ext4   4804736 
3517640   1043028  78% /
tmpfs  tmpfs 5120 0 
5120   0% /run/lock
tmpfs  tmpfs   154460 76 
154384   1% /run/shm
/dev/sda6  ext4   4425760 
144372   4056572   4% /home




Output of lspci -knn (or lspci -nn):

 lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge 
and Memory Controller Hub [8086:1130] (rev 02)

Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset 
Graphics Controller (CGC) [8086:1132] (rev 02)

Subsystem: Compaq Computer Corporation Device [0e11:0019]
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 
01)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801BA ISA Bridge (LPC) 
[8086:2440] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801BA IDE U100 Controller 
[8086:244b] (rev 01)

Subsystem: Intel Corporation Device [8086:2411]
Kernel driver in use: ata_piix
00:1f.4 USB controller [0c03]: Intel Corporation 82801BA/BAM USB Controller #1 
[8086:2444] (rev 01)

Subsystem: Intel Corporation Device [8086:2411]
Kernel driver in use: uhci_hcd
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801BA/BAM 
AC'97 Audio Controller [8086:2445] (rev 01)
	Subsystem: Compaq Computer Corporation Compaq Deskpro EN Audio 
[0e11:000b]

Kernel driver in use: snd_intel8x0
02:08.0 Ethernet controller [0200]: Intel Corporation 82801BA/BAM/CA/CAM 
Ethernet Controller [8086:2449] (rev 01)
	Subsystem: Compaq Computer Corporation EtherExpress PRO/100 VM 
[0e11:0012]

Kernel driver in use: e100



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

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

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.

The Begining of my notes
Opening screen.

Install highlighted.  Graphical Listed next.  I'm not sure most people would 
know the the difference on first boot. I think Install should be Graphical by 
default and the Curses based one in the Advanced options sub menu.  Should be:


Install [Graphical by default]
Help
Advanced options

Or like this:

Install [Graphical by  default]
Install [No Graphics, CLI, something like that]
Help
Advanced options

Pressing Tab to edit the menu entry should be under Advanced options.

The bottom should say:

Press Enter to make selection  and arrow keys to move up and down.


Bug#698739: marked as done (installation-reports: Sun Blade 1500: wheezy almost successful, root not found)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #698739,
regarding installation-reports: Sun Blade 1500: wheezy almost successful, root 
not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
698739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: normal


-- Package-specific info:

Boot method: network
Image version: daily build January 20 2013
Date: 2013-01-21

Machine: Sun Blade 1500 (red)
Partitions:
Disk /dev/sda (Sun disk label): 255 heads, 63 sectors, 9729 cylinders
Units = sectors of 1 * 512 bytes

   Device FlagStart   EndBlocks   Id  System
   /dev/sda1 0  58589055  29294527+  83  Linux native
   /dev/sda2  58589055  62492850   1951897+  82  Linux swap
   /dev/sda3 0 156296385  78148192+   5  Whole disk
   /dev/sda4  62492850  63472815489982+  83  Linux native



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

Comments/Problems:

I netbooted the installer image off another Debian box, that worked
fine. I had to provide firmware for the tigon3 network device through an
USB stick. The rest of the installation (including desktop task) went
just as fine, I manually partitioned the disk to leave space for a
possible FreeBSD install I might want to try.

Rebooting showed a problem: the root partition /dev/sdb1 wasn't found.
As it happens, I left the USB stick I used to copy the firmware
connected and it got assigned to /dev/sda while the disk that was the
target of the installation got /dev/sdb. /etc/fstab has no problem as it
is UUID based, but the SILO configuration had root=/dev/sdb1 in it and
so the initrd failed to mount root.

Manually giving root=/dev/sda1 on the SILO command line let it boot and
I manually corrected silo.conf.

There's now some other problems that are presumably not installer related
(no 3D acceleration even after radeon firmware installed, GNOME in
fallback mode uses the same color for text and window background).


-- 

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 20130120-00:11
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux blade 3.2.0-4-sparc64 #1 Debian 3.2.35-2 sparc64 GNU/Linux
lspci -knn: :00:02.0 PCI bridge [0604]: Texas Instruments PCI2250 
PCI-to-PCI Bridge [104c:ac23] (rev 02)
lspci -knn: :00:06.0 Non-VGA unclassified device []: ULi Electronics 
Inc. M7101 Power Management Controller [PMU] [10b9:7101]
lspci -knn: :00:07.0 ISA bridge [0601]: ULi Electronics Inc. 
M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] [10b9:1533]
lspci -knn: :00:08.0 Multimedia audio controller [0401]: ULi Electronics 
Inc. M5451 PCI AC-Link Controller Audio Device [10b9:5451] (rev 02)
lspci -knn: Subsystem: ULi Electronics Inc. M5451 PCI AC-Link Controller 
Audio Device [10b9:5451]
lspci -knn: :00:0a.0 USB controller [0c03]: ULi Electronics Inc. USB 1.1 
Controller [10b9:5237] (rev 03)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: :00:0b.0 USB controller [0c03]: ULi Electronics Inc. USB 1.1 
Controller [10b9:5237] (rev 03)
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: :00:0d.0 IDE interface [0101]: ULi Electronics Inc. M5229 IDE 
[10b9:5229] (rev c4)
lspci -knn: Kernel driver in use: pata_ali
lspci -knn: :01:08.0 USB controller [0c03]: NEC Corporation USB [1033:0035] 
(rev 43)
lspci -knn: Subsystem: Risq Modular Systems, Inc. Device 

Bug#698877: marked as done (installation-reports: Install as VM guest - boot from virtual USB stick)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #698877,
regarding installation-reports: Install as VM guest - boot from virtual USB 
stick
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
698877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: normal
Tags: d-i

Dear Maintainer,

Apart from the grub bit, the installation was fine.  Well done.
See Comments/Problems below.



-- Package-specific info:

Boot method: USB image
Image version: 16-Nov-2012
   http://ftp.nl.debian.org/debian/dists/testing/main
   installer-amd64/current/images/netboot/mini.iso
Date: 13-Jan-2013

Machine: kvm-qemu VM
Partitions: df -Tl will do; the raw partition table is preferred

Filesystem  Type 1K-blocksUsed Available Use% Mounted on
rootfs  rootfs  575500  188820357448  35% /
udevdevtmpfs 10240   0 10240   0% /dev
tmpfs   tmpfs50896 696 50200   2% /run
/dev/disk/by-uuid/...   ext4575500  188820357448  35% /
tmpfs   tmpfs 5120   0  5120   0% /run/lock
tmpfs   tmpfs   101780  76101704   1% /run/shm
/dev/sda6   ext4   1056264   61460994804   6% /home
/dev/sda7   ext4   4035648 2762836   1272812  69% /usr
/dev/sda8   ext4   1537024  366164   1092780  26% /var
/dev/sda9   ext4   1046168   34072   1012096   4% /opt


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

Comments/Problems:

To get qemu-kvm to boot the virtual USB stick, it had to be disk 0.
The grub installer proposed to install its bootloader on disk 0,
which is not what was wanted.

However, post-installation device.map reads:

(hd0)   /dev/disk/by-id/ata-QEMU_HARDDISK_QM1
(hd1)   /dev/disk/by-id/ata-QEMU_HARDDISK_QM2

This would make it hard for any heuristic that didn't consider disk contents
to tell which 'disk' was installed from and which was installed to.

-- 

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=netboot

==
Installer hardware-summary:
==
uname -a: Linux wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 
[1013:00b8]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ [10ec:8139] (rev 20)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: 8139cp
lsmod: Module  Size  Used by
lsmod: hfsplus

Bug#697327: marked as done (installation-reports: Can not write on usb flash memory)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #697327,
regarding installation-reports: Can not write on usb flash memory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
697327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: normal
Tags: d-i

Dear Maintainer,

   * What led up to the situation?
I installed wheezy-xfce (testing - build cd binay-1 20121217-05:10) on a new
partition.
Can not write to USB flash memory (~ operation not allowed).


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Commented out following lines in /etc/fstab :
#/dev/sdb1   /media/usb0 autorw,user,noauto  0   0
#/dev/sdb2   /media/usb1 autorw,user,noauto  0   0
#/dev/sdb3   /media/usb2 autorw,user,noauto  0   0

NB : I may have left some USB devices while installing wheezy from CD.

   * What was the outcome of this action?
Problem fixed.




-- Package-specific info:

Boot method: 
Image version: 
Date: Date and time of the install

Machine: 
Partitions: df -Tl will do; the raw partition table is preferred


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

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

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.


-- 

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 20121217-00:04
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux pc4 3.2.0-4-amd64 #1 SMP Debian 3.2.35-1 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0104] (rev 09)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd 
Generation Core Processor Family Integrated Graphics Controller [8086:0116] 
(rev 09)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 
Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:13c7]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express 

Bug#697915: marked as done (Problem with LVM when installing latest Debian Wheezy)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #697915,
regarding Problem with LVM when installing latest Debian Wheezy
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
697915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: Cd 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-netinst.iso
Date: Friday 11 January 2013.

Machine: Tested on VirtualBox and a Dell Optiplex 960 and a Dell PowerEdge R210.
Processor:
Memory:
Partitions: df -Tl ; mais nous préférons la table des partitions

Sys. fich.Type 1K-blocks   Util. Disponible Uti% Monté sur
rootfsrootfs19223252 1100720   17146048   7% /


udev  devtmpfs 10240   0  10240   0% /dev
tmpfs tmpfs37988 244  37744   1% /run
/dev/mapper/vglocal-slash ext4  19223252 1100720   17146048   7% /


tmpfs tmpfs 5120   0   5120   0% /run/lock
tmpfs tmpfs75960   0  75960   0% /run/shm
/dev/sda1 ext4 93207   23165  65230  27% /boot


fdisk -l

Disque /dev/sda : 107.4 Go, 107374182400 octets
255 têtes, 63 secteurs/piste, 13054 cylindres, total 209715200 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets


taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Identifiant de disque : 0x0004cbc3

Périphérique Amorce  DébutFin  Blocs Id  Système
/dev/sda1   *2048  194559   96256   83  Linux
/dev/sda2  194560   209713151   104759296   8e  LVM Linux

Disque /dev/mapper/vglocal-slash : 20.0 Go, 19998441472 octets
255 têtes, 63 secteurs/piste, 2431 cylindres, total 39059456 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Identifiant de disque : 0x

Disque /dev/mapper/vglocal-swap : 998 Mo, 998244352 octets

255 têtes, 63 secteurs/piste, 121 cylindres, total 1949696 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Identifiant de disque : 0x


Résultat de lspci -knn (ou lspci -nn) :

00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC
[Natoma] [8086:1237] (rev 02)

00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA
[Natoma/Triton II] [8086:7000]

00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4
IDE [8086:7111] (rev 01)
00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH
VirtualBox Graphics Adapter [80ee:beef]
00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit
Ethernet Controller [8086:100e] (rev 02)


00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH
VirtualBox Guest Service [80ee:cafe]
00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA
AC'97 Audio Controller [8086:2415] (rev 01)


00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f]
00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI
[8086:7113] (rev 08)
00:0b.0 USB controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW
(ICH6 Family) USB2 EHCI Controller [8086:265c]


00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM
(ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02)


Installation du système de base :
[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:  [E]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:


Hi,

It seems there is a problem with partman and LVM.

I created a VirtualBox machine with a 107.4 GB hard drive (sparce file).

In the first place, I created 3 masters partitions with partman.

- /dev/sda1/ as /boot in ext4 - 98.6 MB

- /dev/sda2 as LVM partition - 50 

Bug#698878: marked as done (installation-reports: Boot from USB stick 1 - install to USB stick 2)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #698878,
regarding installation-reports: Boot from USB stick 1 - install to USB stick 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
698878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: normal
Tags: d-i

Dear Maintainer,

I think the Debian Installer does an excellent job but I have quibbles with:
  the partitioner's handling of swap
  the grub installer's handing of USB sticks.
See Comments/Problems below.

Also my first attempt failed at the Install tasks step.  The /var partition
was 'only' 1 Gb and that is not enough to netinstall KDE.  Put that in your
minimum system requirements.


-- Package-specific info:

Boot method: USB stick
Image version: 16-Nov-2012
   http://ftp.nl.debian.org/debian/dists/testing/main
   installer-amd64/current/images/netboot/mini.iso
Date: 14-Jan-2013

Machine: i5 Laptop
Partitions: df -Tl will do; the raw partition table is preferred
Filesystem  Type 1K-blocksUsed Available Use% Mounted on
rootfs  rootfs  472036  173823273842  39% /
udevdevtmpfs 10240   0 10240   0% /dev
tmpfs   tmpfs   3848361012383824   1% /run
/dev/disk/by-uuid/...   ext4472036  173823273842  39% /
tmpfs   tmpfs 5120   0  5120   0% /run/lock
tmpfs   tmpfs  116  80   1159920   1% /run/shm
/dev/sdb6   ext4960504  208324752180  22% /home
/dev/sdb7   ext4   3844152 3412248431904  89% /usr
/dev/sdb8   ext4   1441280  921828446236  68% /var
/dev/sdb9   ext4984696   17628967068   2% /opt

$ sudo swapon -s
FilenameTypeSizeUsedPriority
/dev/sda1   partition   1951740 0   -1

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:  [F]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[F]
Overall install:[O]

Comments/Problems:

The quibble with the partitioner's handling of swap:
  - by default, the partitioner will use all existing swap partitions
- usually this is what is wanted
  - by default, it will reformat swap partition, changing their UUID
- usually no one cares about the UUID
  - you can't set a label for the swap partition
- seems you can for most other partitions

Suppose I have a dual boot (or even multi boot) machine.

Do I need a distinct swap partition for each bootable installation ?
I think not.

If I accept the installer's default action and if the other installations
have fstabs using *%@^%@^ UUIDs, those fstabs are broken.  This may
not be noticed for some time.

Workaround is to define no swap during installation and do it by hand
afterwards.
   
In my case, I want the USB to use the swap partition on the hard-drive.
The hard-drive of whatever machine I plug the USB stick into.  I don't
want an fstab full of UUIDs.

I label my swap partitions - swapa (swapb usw).  I can't do this
during the installation.  I do it by hand after for each machine.

What would be nice is an option in the installer to use existing swap,
either without reformatting or, where compatible, with the old UUID
and label.

The quibbles with the grub install.  There are two.

Here's the post-install grub device.map.

(hd0)   /dev/disk/by-id/usb-Verbatim_STORE_N_GO_TT018706-0:0


(hd1)   /dev/disk/by-id/usb-BUFFALO_ClipDrive_A320051021751-0:0 


(hd2)   /dev/disk/by-id/ata-Hitachi_HTS545025B9A300_100411PBN2061SFS47GT

In this case, the proposal to install the grub bootloader to disk 0 was
the right guess:  the installation was to the Verbatim USB and the
Buffalo USB was the installation medium.

However, the grub boot menu 

Bug#689849: marked as done (grub2 installed to mmcblk0 rather than sda)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #689849,
regarding grub2 installed to mmcblk0 rather than sda
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
689849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: dd'ed debian-wheezy-DI-b2-amd64-CD-1.iso to USB stick
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_beta2/amd64/iso-cd/debian-wheezy-DI-b2-amd64-CD-1.iso
Date: 2012-10-06 13:00 US/Pacific

Machine: Thinkpad X1 Carbon
Processor: Core i5-3427U
Memory: 8GB
Partitions:

Disk /dev/sda: 256.1 GB, 256060514304 bytes
255 heads, 63 sectors/track, 31130 cylinders, total 500118192 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: 0x00076d21

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *2048  499711  248832   83  Linux
/dev/sda2  501758   500117503   2498078735  Extended
/dev/sda5  501760   500117503   249807872   83  Linux

Output of lspci -knn (or lspci -nn):

00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: Lenovo Device [17aa:21f9]
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09)
Subsystem: Lenovo Device [17aa:21f9]
Kernel driver in use: i915
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04)
Subsystem: Lenovo Device [17aa:21f9]
Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Lenovo Device [17aa:21f9]
00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 Series 
Chipset Family KT Controller [8086:1e3d] (rev 04)
Subsystem: Lenovo Device [17aa:21f9]
Kernel driver in use: serial
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
Subsystem: Lenovo Device [17aa:21f9]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Lenovo Device [17aa:21f9]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 2 [8086:1e12] (rev c4)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
Subsystem: Lenovo Device [17aa:21f9]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation QS77 Express Chipset LPC 
Controller [8086:1e56] (rev 04)
Subsystem: Lenovo Device [17aa:21f9]
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 
6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
Subsystem: Lenovo Device [17aa:21f9]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family 
SMBus Controller [8086:1e22] (rev 04)
Subsystem: Lenovo Device [17aa:21f9]
Kernel driver in use: i801_smbus
02:00.0 System peripheral [0880]: Ricoh Co Ltd MMC/SD Host Controller 
[1180:e822] (rev 07)
Subsystem: Lenovo Device [17aa:21f3]
Kernel driver in use: sdhci-pci
03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6205 
[8086:0085] (rev 96)
Subsystem: Intel Corporation Device [8086:c220]
Kernel driver in use: iwlwifi

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]
Detect hard drives: [O]
Partition hard drives:  [O]
Install 

Bug#692437: marked as done (installation report)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #692437,
regarding installation report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
692437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: installation-reports

Boot method: How did you boot the installer? CD? floppy? network?   USB
Image version: Full URL to image you downloaded is best 
http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/iso-cd/debian-wheezy-DI-b3-amd64-netinst.iso
Date: Date and time of the install  Nov 
04, 2012

Machine: Description of machine (eg, IBM Thinkpad R32)  Assembled 
Machine with ASUS mother board
Processor:  AMP 
Sempron 1GHz
Memory: 1GB
Partitions: df -Tl will do; the raw partition table is preferred500GB 
HDD with 160GB partitioned for root /

Filesystem Type 1K-blocks 
Used Available Use% Mounted on
rootfs rootfs   163199520  
5997792 148911388   4% /
udev   devtmpfs 10240   
 0 10240   0% /dev
tmpfs  tmpfs89536  
628 88908   1% /run
/dev/disk/by-uuid/f496b538-7099-45bc-8cf7-956acdf19ee9 ext4 163199520  
5997792 148911388   4% /
tmpfs  tmpfs 5120   
 0  5120   0% /run/lock
tmpfs  tmpfs   222420   
88222332   1% /run/shm
/dev/sda5  fuseblk   46829440 
10345948  36483492  23% /media/KRISHNA
/dev/sda7  fuseblk   50050472 
14111480  35938992  29% /media/KRISHNA_
/dev/sda9  fuseblk   75152036 
41163364  33988672  55% /media/KRISHNA__
/dev/sda8  fuseblk  150328204 
32220356 118107848  22% /media/KRISHNA___

Output of lspci -knn (or lspci -nn):

root@gml:~# lspci -knn
00:00.0 RAM memory [0500]: NVIDIA Corporation MCP61 Memory Controller 
[10de:03ea] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP61 LPC Bridge [10de:03e0] (rev 
a2)
Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
00:01.1 SMBus [0c05]: NVIDIA Corporation MCP61 SMBus [10de:03eb] (rev a2)
Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
Kernel driver in use: nForce2_smbus
00:01.2 RAM memory [0500]: NVIDIA Corporation MCP61 Memory Controller 
[10de:03f5] (rev a2)
Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
00:02.0 USB controller [0c03]: NVIDIA Corporation MCP61 USB 1.1 Controller 
[10de:03f1] (rev a3)
Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
Kernel driver in use: ohci_hcd
00:02.1 USB controller [0c03]: NVIDIA Corporation MCP61 USB 2.0 Controller 
[10de:03f2] (rev a3)
Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
Kernel driver in use: ehci_hcd
00:04.0 PCI bridge [0604]: NVIDIA Corporation MCP61 PCI bridge [10de:03f3] (rev 
a1)
00:05.0 Audio device [0403]: NVIDIA Corporation MCP61 High Definition Audio 
[10de:03f0] (rev a2)
Subsystem: ASUSTeK Computer Inc. Device [1043:8290]
Kernel driver in use: snd_hda_intel
00:06.0 IDE interface [0101]: NVIDIA Corporation MCP61 IDE [10de:03ec] (rev a2)
Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
Kernel driver in use: pata_amd
00:07.0 Bridge [0680]: NVIDIA Corporation MCP61 Ethernet [10de:03ef] (rev a2)
Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
Kernel driver in use: forcedeth
00:08.0 IDE interface [0101]: NVIDIA Corporation MCP61 SATA Controller 
[10de:03f6] (rev a2)
Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
Kernel driver in use: sata_nv
00:09.0 PCI bridge [0604]: NVIDIA Corporation MCP61 PCI Express bridge 
[10de:03e8] (rev a2)
Kernel driver in use: pcieport
00:0b.0 PCI bridge [0604]: NVIDIA Corporation MCP61 PCI Express bridge 
[10de:03e9] (rev a2)
Kernel driver in use: pcieport
00:0c.0 PCI bridge [0604]: NVIDIA Corporation 

Bug#692475: marked as done ()

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #692475,
regarding 
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
692475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: The installator was boot from a USB stick
Image version: Weekly amd64 build CD
Date: 5 november 2012 - 15h30 GMT+2

Machine: Dell Precision T1650
Processor: Intel Xeon
Memory: 16 GB RAM, 2*1TB SATA Disk
Partitions: Installation didn't finish

Résultat de lspci -knn (ou lspci -nn) :

Installation du système de base :
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [0]
Detect network card:[E]
The card was not detected at all. It didn't work out on this computer
newly bought but as well as another one with debian already installed
on it and without any network card related problem. It seems to me as
a regression not found in the beta3 installer
Configure network:  [ ]
Detect CD:  [O]
Load installer modules: [ ]
Detect hard drives: [O]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[O]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[E]

Comments/Problems:


It seems that a regression occurs between the beta 3 installation
(going on as now without any problem apparently. At least a lot less)
for at least the network.
As I tested with this CD, RAID installs seems to be not possible (it
does not recognize new hardware, that work with beta3 install) but I
did not tested the installation very far. It should tested again to be
sure.


Best regards and thank you for the good work !
Florent
---End Message---
---BeginMessage---
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#698933: marked as done (hangs on 'Configuring APT')

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #698933,
regarding hangs on 'Configuring APT'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
698933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: Debian-6.0.6-amd64-netinst.iso

Hi.

I recently attempted to install Debian (for the first time) lastest 
stable small CD. Debian-6.0.6-amd64-netinst.iso.


Machine is as below, W7 installed, Debian resize partition used.

However, the install hangs on 'Configuring APT' about 50%, when trying 
to download 'file 5 of 5'.

Tried other mirrors, same problem.

I found this bug Bug#389285 from 2006 which was closed.
However, this appears to be the same bug 7 years on?

Please advise. Would a large complete DVD install avoid the configuring 
APT step?


Regards
Mike

Processor Intel Core i3-3220 3.3Ghz
Memory 8GB DDR3 RAM
Hard Drive 1TB SATA HDD
Motherboard ASUS P8H61-MX
Wired internet connection
---End Message---
---BeginMessage---
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Processed: reassign

2013-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 673468 debian-installer
Bug #673468 [installation-reports] kfreebsd9: umlauts missing on german keymap
Bug reassigned from package 'installation-reports' to 'debian-installer'.
Ignoring request to alter found versions of bug #673468 to the same values 
previously set
Ignoring request to alter fixed versions of bug #673468 to the same values 
previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
673468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.13779481296770.transcr...@bugs.debian.org



Bug#699136: marked as done (installation-reports: partman hangs on Dell Optiplex 960)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #699136,
regarding installation-reports: partman hangs on Dell Optiplex 960
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
699136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: normal


-- Package-specific info:

Boot method: network
Image version: wheezy non-graphical netboot from 2013-01-13 (i think)
Date: Date and time of the install

Machine: Dell Optiplex 960
Partitions: df -Tl will do; the raw partition table is preferred


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:  [E]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

partman hung at either 50% or 54% during the Partition hard drives
phase of the installer.

switching to a vt, i was able to see that it appeared to be hung
during 35dump.

killing parted from a vt was successful, but each time i tried to
re-run partman, it hung on 35dump again.

I ultimately installed manually, thanks to parted-deb and debootstrap
:(

--dkg

-- 

I'm attaching the output of lshw -- i'm not sure what  else would be useful.

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

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#692731: marked as done (Debian wheezy CD1 beta3 installation on Mac Pro Retina)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #692731,
regarding Debian wheezy CD1 beta3 installation on Mac Pro Retina
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
692731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: CD in an external CD drive
Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/jigdo-cd/
- CD1 used jigdo to build it
Date: 8th Nov 2012

Machine: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS
MBP101.88Z.00EE.B00.1205101839 05/10/2012
Processor: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz stepping 09
Memory: 16Gb
Partitions:
df  -T
Filesystem Type  Size
Used Avail Use% Mounted on
rootfs rootfs118G
 98G   15G  88% /
udev   devtmpfs   10M
   0   10M   0% /dev
tmpfs  tmpfs 1.6G
452K  1.6G   1% /run
/dev/disk/by-uuid/9ad44c06-106c-40c8-b1fa-ff72043d760b ext4  118G
 98G   15G  88% /
tmpfs  tmpfs 5.0M
   0  5.0M   0% /run/lock
tmpfs  tmpfs 7.9G
   0  7.9G   0% /run/shm
tmpfs  tmpfs 7.9G
2.9M  7.9G   1% /tmp

sudo parted /dev/sda print
Model: ATA APPLE SSD SM256E (scsi)
Disk /dev/sda: 251GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End SizeFile system  Name  Flags
 1  20.5kB  210MB   210MB   fat32EFI system partition  boot
 2  210MB   99.2GB  99.0GB  hfs+ Customer
 3  100GB   101GB   650MB   hfs+ Recovery HD
 4  101GB   112GB   10.7GB  ext4
 5  112GB   123GB   11.6GB  ext4
 6  123GB   251GB   128GB   ext4

Output of lspci -knn (or lspci -nn):
lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor
DRAM Controller [8086:0154] (rev 09)
Subsystem: Apple Inc. Device [106b:00f7]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor PCI Express Root Port [8086:0151] (rev 09)
Kernel driver in use: pcieport
00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor PCI Express Root Port [8086:0155] (rev 09)
Kernel driver in use: pcieport
00:01.2 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor PCI Express Root Port [8086:0159] (rev 09)
Kernel driver in use: pcieport
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 7
Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev
04)
Subsystem: Intel Corporation Device [8086:7270]
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series
Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series
Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series
Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation HM77 Express Chipset LPC
Controller [8086:1e57] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset
Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)

Bug#699136: dealing with old installation-reports

2013-08-31 Thread Holger Levsen
reopen 699136
# sorry, Daniel!
thanks

I didn't mean to close this one...

On Samstag, 31. August 2013, Holger Levsen wrote:
 reassign 699136 partman
 retitle 699136 partman hangs with specific mbr/usbsticks
 tags 696755 +confirmed
[...]
 If I've closed a bug incorrectly please do reply (it's easy to reopen [...]


cheers,
 Holger





signature.asc
Description: This is a digitally signed message part.


Processed: Re: dealing with old installation-reports

2013-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reopen 699136
Bug #699136 {Done: Holger Levsen hol...@layer-acht.org} 
[installation-reports] installation-reports: partman hangs on Dell Optiplex 960
Bug reopened
Ignoring request to alter fixed versions of bug #699136 to the same values 
previously set
 # sorry, Daniel!
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
699136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.137794962917819.transcr...@bugs.debian.org



Processed: reassign 699136 partman

2013-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 699136 partman
Bug #699136 [installation-reports] installation-reports: partman hangs on Dell 
Optiplex 960
Bug reassigned from package 'installation-reports' to 'partman'.
Warning: Unknown package 'partman'
Warning: Unknown package 'partman'
Ignoring request to alter found versions of bug #699136 to the same values 
previously set
Warning: Unknown package 'partman'
Warning: Unknown package 'partman'
Ignoring request to alter fixed versions of bug #699136 to the same values 
previously set
Warning: Unknown package 'partman'
 retitle 699136 partman hangs with specific mbr/usbsticks
Bug #699136 [partman] installation-reports: partman hangs on Dell Optiplex 960
Warning: Unknown package 'partman'
Changed Bug title to 'partman hangs with specific mbr/usbsticks' from 
'installation-reports: partman hangs on Dell Optiplex 960'
Warning: Unknown package 'partman'
 tags 696755 +confirmed
Bug #696755 [installation-reports] installation-reports: no network connection 
after reboot if only tasksel's standard and ssh-server
Added tag(s) confirmed.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
696755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696755
699136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.137795088127112.transcr...@bugs.debian.org



Bug#699478: marked as done (installation failed (disk full) in virtualbox with lvm / /home chioce)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #699478,
regarding installation failed (disk full) in virtualbox with lvm / /home chioce
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
699478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: debian-testing-i386-DVD-1.iso
Image version: debian-testing-i386-DVD-1.iso 28/01/2013 at 05:17
url 
http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-dvd/debian-testing-i386-DVD-1.iso
but same problem on net installer
Date: 31/01/2013

Machine: virtualbox linux 3.2.10 ose and lastest version on windows
Processor:  AMD Athlon(tm) II X4 620 Processor
Memory: 4Gb

Installation du système de base :
[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:  [N ]
Install boot loader:[N ]
Overall install:[N ]

Comments/Problems:
The virtualbox give a 8Gb disk by default
With the Lvm partition the choice of a / and /home partition give a
2.4 on /  and 5.4 Gb on /home
if you said yes
the / filesystem is full with an install with web and desktop

So an installation by default break on virtualbox. (testing and
stable)  whith lvm and / and /home partition choice.
When problem occur :
 df -h give 100% full file system on /target

I think you should give more place for / in installation process
---End Message---
---BeginMessage---
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#693756: marked as done (installation-reports: thinkpad edge e135: graphics broken, needs nonfree firmware and experimental libdrm)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #693756,
regarding installation-reports: thinkpad edge e135: graphics broken, needs 
nonfree firmware and experimental libdrm
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
693756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: normal

-- Package-specific info:

Boot method: USB
Image version: 
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-CD-1.iso
 (2012-11-13)
Date: 2012-11-18

Machine: Lenovo ThinkPad Edge E135 (bios disabled, using only uefi)


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

Initial boot:   [O]
Detect network card:[O]
Configure network:  [E]
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:[E]

Comments/Problems:

the wifi was detected and loaded nonfree firmware from usb, but couldn't
connect. seems to be an rf-kill problem that has yet to be investigated
and is likely to spawn its own bug report.

the main issue was getting the graphics to run -- the symptom being that
after the system was installed and starts up, the display shows a random
image that looks like memory. (random colours over large areas, large
black areas, some white areas, occasionally black areas with a few
coloured pixels). changing terminals didn't affect the screen's state.

debugging based on init=/bin/sh revealed that the state occurs when udev
loads the `radeon` module, and that the relevant dmeesg log line is:

 kernel: [...] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing 
 generic drivers

setting the module option radeon.modeset=0 in the kernel command line
makes the garbage go away, but x still fails to start.


with help from #radeon and a very helpful jcristau, i got things to run;
those were the minimal steps required:

* download the .bin files from [1] to `/lib/firmware/radeon`. i didn't
  have the patience to determine which exactly are needed, but
  PALM_pfp.bin is among them. those files are non-free, but hey, better
  than needing fglrx which runs non-free software on my cpu.

* install libdrm-radeon1 and libdrm2 = 2.4.40 (from experimental; works
  with a system that is otherwise wheezy)

gdm and lightdm still fail to start, and strange graphics bugs show up
in the gnome shell, but the system appears to be usable with xdm and
xfce4 with and without compositing. armagetronad runs fluently to make
me assume hardware 3d acceleration is active.

[1] http://people.freedesktop.org/~agd5f/radeon_ucode/


-- 

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=7.0 (wheezy) - installer build 20121113-00:04
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux artemis 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 14h 
Processor Root Complex [1022:1510]
lspci -knn: Subsystem: Lenovo Device [17aa:5105]
lspci -knn: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices 
[AMD] nee ATI Device [1002:9808]
lspci -knn: Subsystem: Lenovo Device [17aa:5105]
lspci -knn: 00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI 
Wrestler HDMI Audio [Radeon HD 6250/6310] [1002:1314]
lspci -knn: Subsystem: Lenovo Device [17aa:5105]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h 
Processor Root Port [1022:1513]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:06.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h 
Processor Root Port [1022:1514]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:07.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 14h 
Processor Root Port [1022:1515]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:10.0 USB controller [0c03]: Advanced 

Bug#699760: marked as done (netboot.tar.gz for debian wheezy is not working)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #699760,
regarding netboot.tar.gz for debian wheezy is not working
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
699760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: |installation-reports 
http://bugs.debian.org/installation-reports|

Version: snapshot from 2013-02-04

Hello,

On 2013-02-04 I downloaded: 
http://d-i.debian.org/daily-images/amd64/daily/netboot/netboot.tar.gz 
and after ungzipping and untaring in tftp-hpa dir I was unable to 
install Debian via PXE, instalation stops on information that some file 
is missing, pleaase check it. When I use netboot.tar.gz for squeeze I do 
not get the error, and when I used older version of netboot.tar.gz for 
wheezy I also did not have such problems.


 Pozdrawiam,
 Lukasz.
---End Message---
---BeginMessage---
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Processed: Re: Processed: reassign 699136 partman

2013-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 699136 partman-base
Bug #699136 [partman] partman hangs with specific mbr/usbsticks
Warning: Unknown package 'partman'
Bug reassigned from package 'partman' to 'partman-base'.
Ignoring request to alter found versions of bug #699136 to the same values 
previously set
Ignoring request to alter fixed versions of bug #699136 to the same values 
previously set
 # sigh
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
699136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.13779519661806.transcr...@bugs.debian.org



Bug#700918: marked as done (Installation report)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #700918,
regarding Installation report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
700918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: USB drive (dd if=iso from below of=/dev/sdb)
Image version: 
http://napoleon.acc.umu.se/cdimage/.wheezy_di_rc1/amd64/iso-cd/debian-wheezy-DI-rc1-amd64-CD-1.iso
Date: 18-02-2013 9pm


Machine: Lenovo Thinkpad x230
Processor: i5-3320M
Memory: 8GB
Partitions: N/A

Output of lspci -knn (or lspci -nn):

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

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

Comments/Problems:

Boots fine if legacy bios only is selected in the system setup (bios)

if the system is in UEFI mode (required for dual boot) I see grub
stage 1 flash by and then a blinking cursor in top right (no response
to input at all)

I also tried beta4 which got a little further in that a text mode grub
menu appeared with the
option to boot the installer in text mode or graphics mode.
---End Message---
---BeginMessage---
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#693891: marked as done (Fails to boot in UEFI mode on Dell PowerEdge R520)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #693891,
regarding Fails to boot in UEFI mode on Dell PowerEdge R520
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
693891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: netinst amd64 cd-rom
Image version:  Debian GNU/Linux testing Wheezy - Official
Snapshot amd64 NETINST Binary-1 20121121-09:10
Date: 2012-11-21 15:00 GMT+1

Machine: Dell PowerEdge R520
Processor: 2x Intel Xeon E5-2430L
Memory: 32 GB
Partitions: empty disk

Output of lspci -knn (or lspci -nn):

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

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

Comments/Problems:

With both beta 4 amd64 netinst image from
http://cdimage.debian.org/cdimage/.wheezy_di_b4/as as the daily amd64
netinst build 20121121-09:10, this system refuses to boot in UEFI mode.

I did the following actions when powering on the machine:
- insert cd-rom
- Press F11: UEFI boot menu.
- In the graphical Boot Manager Main Menu, I select UEFI boot menu
- Then I select Embedded SATA Port Optical Drive
- This text appears on the screen:
Boot Failed:

Please ensure compatible bootable media is available.
Use the system setup program to change the boot mode as needed.

Strike F1 to retry boot, F2 for system setup, F11 for boot manager.

If I replace the Debian disc by SystemrescueCD 3.00 disc and strike F1,
the system successfully loads up the GRUB boot loader on the
SystemRescueCD 3.00 disc in UEFI mode.

When I start the same Debian disc in BIOS mode, it loads successfully.

-- 
Frederik Himpe fhi...@telenet.be
---End Message---
---BeginMessage---
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#694062: marked as done (debian Wheezy installer)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #694062,
regarding debian Wheezy installer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
694062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: netinstall
package: debian-testing-amd64-netinst.iso (
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/)
Date: today failled
Machine: ICP desktop
Processor: intell atom 2
Memory: 2 GB RAM, 500gb rom
Partitions:

Output of lspci -knn (or lspci -nn):

Base System Installation Checklist:
[O] = OK, [E] = Error (it loads the first screen, then type point when I
enyer install), [ ] = didn't try it

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

Comments/Problems:
I have purchased a new computer, with Atom 2, 2Gb RAM,500 GB ROM, an ICP
desktop.
I was unabel to run the Wheezy installer, even as the Ubuntu and the
mini.iso of Ubuntu, yet the Debian 6.0 installer (my old disk) works fine,
even as an old Windows XP installer.
I would like to try the former version of the wheezy installer,if it would
perhaps be more stable then the later.
It goes until the first screen and writtes many points when I type enter to
install.
Em 23/11/2012 11:03, Adriano Trentini adrianotrenti...@gmail.com
escreveu:
---End Message---
---BeginMessage---
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#700175: marked as done (wheezy installation issues)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #700175,
regarding wheezy installation issues
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
700175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: netinst CD
Image version: 
http://caesar.acc.umu.se/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso
Date: 2013-02-08 ~10pm to 2013-02-09 ~ 8am

Machine: Dell Inspiron 7520
Processor: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz, 2201 Mhz, 4 Core(s), 8 
Logical Processor(s)
Memory: 8.00 GB

(df and lspci output after installation)

$ df -Tl
Filesystem Type 1K-blocks
Used Available Use% Mounted on
rootfs rootfs42284288 
3697076  36439272  10% /
udev   devtmpfs 10240   
0 10240   0% /dev
tmpfs  tmpfs   805056 
776804280   1% /run
/dev/disk/by-uuid/7a434279-a151-4c86-bb97-7b4ca48b0084 ext4  42284288 
3697076  36439272  10% /
tmpfs  tmpfs 5120   
0  5120   0% /run/lock
tmpfs  tmpfs  3258320  
84   3258236   1% /run/shm
/dev/sda1  vfat507904   
50120457784  10% /boot/efi


$ lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: Dell Device [1028:0572]
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port [8086:0151] (rev 09)
Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09)
Subsystem: Dell Device [1028:0572]
Kernel driver in use: i915
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04)
Subsystem: Dell Device [1028:0572]
Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Dell Device [1028:0572]
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
Subsystem: Dell Device [1028:0572]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Dell Device [1028:0572]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 2 [8086:1e12] (rev c4)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
Subsystem: Dell Device [1028:0572]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation HM77 Express Chipset LPC 
Controller [8086:1e57] (rev 04)
Subsystem: Dell Device [1028:0572]
00:1f.2 RAID bus controller [0104]: Intel Corporation 82801 Mobile SATA 
Controller [RAID mode] [8086:282a] (rev 04)
Subsystem: Dell Device [1028:0572]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family 
SMBus Controller [8086:1e22] (rev 04)
Subsystem: Dell Device [1028:0572]
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI 
Cape Verde [Radeon HD 7700M Series] [1002:682f]
Subsystem: Dell Device [1028:0572]
07:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 07)
Subsystem: Dell Device [1028:0572]
Kernel driver in use: r8169
08:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 2230 
[8086:0887] (rev c4)
Subsystem: Intel Corporation Centrino 

Bug#694247: marked as done (installation-report: problems with installation from iso-file present on hard drive (loop.ko and pata_amd.ko is absent))

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #694247,
regarding installation-report: problems with installation from iso-file present 
on hard drive (loop.ko and pata_amd.ko is absent)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
694247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

When I try install Debian (
http://cdimage.debian.org/debian-cd/6.0.6/amd64/iso-cd/debian-6.0.6-amd64-xfce+lxde-CD-1.iso)
I boot from my hdd with grub:
menuentry 'debian-6.06-amd64.iso' {
loopback loop /debian.iso
linux (loop)/install.amd/vmlinuz vga=788 iso-scan/filename=/debian.iso
-- quiet
initrd (loop)/install.amd/initrd.gz
}

But the option iso-scan/filename not work (Ok. It's normal. It's work
with a Ubuntu *.iso. I try it for Debian, but without success.) The Debian
image not include kernel module loop.ko, so not with the option, not
manually I can't mount iso-file
and install Debian. That's bad, but not fatal.
I find here (
http://d-i.alioth.debian.org/manual/en.i386/apas02.html#howto-getting-images-hard-disk)
a way install Debian from my hdd with iso-file. I boot with this (
http://ftp.nl.debian.org/debian/dists/squeeze/main/installer-amd64/current/images/hd-media/{initrd.gz,vmlinuz})
and try this (
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/{initrd.gz,vmlinuz})
too, but both of them don't have kernel module pata_amd.ko and my hdd don't
appears in /dev after boot and I can't install Debian. I don't know, is it
a bug or not? It's no fatal for me, too. I boot and install Debian from my
usb flash drive, but more convenient ways is desirable. Thanks.

P.s. I'm sorry for my English. I hope it don't hurt your heart and ruin
your brain.
---End Message---
---BeginMessage---
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#694722: marked as done (eMachines eM355, encrypted boots off pendrive, preseeding fails)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #694722,
regarding eMachines eM355, encrypted  boots off pendrive, preseeding fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
694722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
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 

Bug#694803: marked as done (Wheezy beta4 installation report)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #694803,
regarding Wheezy beta4 installation report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
694803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: CD
Image 
version:http://cdimage.debian.org/cdimage/wheezy_di_beta4/i386/iso-cd/debian-wheezy-DI-b4-i386-netinst.iso
Date: 09:00 Fri 30 Nov 2012

Machine: Dell Inspiron 530
Processor:Intel® Core™2 Quad CPU Q6600 @ 2.40GHz × 4
Memory:4GB
Partitions: df -Tl:
Filesystem Type
1K-blocksUsed Available Use% Mounted on
rootfs rootfs
472486168 3649328 444835868   1% /
udev   devtmpfs
10240   0 10240   0% /dev
tmpfs  tmpfs
413836 708413128   1% /run
/dev/disk/by-uuid/anonymised ext4
472486168 3649328 444835868   1% /
tmpfs  tmpfs
5120   0  5120   0% /run/lock
tmpfs  tmpfs
2500460 152   2500308   1% /run/shm

--- fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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: 0x00010153
   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *2048   960040959   480019456   83  Linux
/dev/sda2   960043006   976771071 83640335  Extended
/dev/sda5   960043008   976771071 8364032   82  Linux swap / Solaris

Output of lspci -knn:
00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31
Express DRAM Controller [8086:29c0] (rev 02)
Subsystem: Dell Inspiron 530 [1028:020d]
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express
PCI Express Root Port [8086:29c1] (rev 02)
Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31
Express Integrated Graphics Controller [8086:29c2] (rev 02)
Subsystem: Dell Inspiron 530 [1028:020d]
Kernel driver in use: i915
00:19.0 Ethernet controller [0200]: Intel Corporation 82562V-2 10/100
Network Connection [8086:10c0] (rev 02)
Subsystem: Dell Inspiron 530 [1028:020d]
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 Inspiron 530 [1028:020d]
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 Inspiron 530 [1028:020d]
Kernel driver in use: uhci_hcd
00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #6 [8086:2939] (rev 02)
Subsystem: Dell Inspiron 530 [1028:020d]
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 Inspiron 530 [1028:020d]
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 Inspiron 530 [1028:020d]
Kernel driver in use: snd_hda_intel
00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family)
USB UHCI Controller #1 [8086:2934] (rev 02)
Subsystem: Dell Inspiron 530 [1028:020d]
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 Inspiron 530 [1028:020d]
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 Inspiron 530 [1028:020d]
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 Inspiron 530 [1028:020d]
Kernel driver in use: ehci_hcd

Bug#694771: marked as done (installation-reports: s390x installer creates invalid /etc/network/interfaces)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #694771,
regarding installation-reports: s390x installer creates invalid 
/etc/network/interfaces
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
694771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
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: df -Tl will do; the raw partition table is preferred


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:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.


-- 

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

Bug#694777: marked as done (Wheezy Beta4 installs but X server unusable)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #694777,
regarding Wheezy Beta4 installs but X server unusable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
694777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

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 

Bug#705187: marked as done (Installation bug 6.0.7 incorrectly boot)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #705187,
regarding Installation bug 6.0.7 incorrectly boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
705187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: install
Version: 6.0.7

If the disk contains the OS Windows + Windows-recovery on installation
Debian is after trying GRUB record makes it impossible to load any of the
OS.

This is because it is an bootable partition on which Debian is installed,
but the GRUB is written to the not bootable partition.  (It was
automatic disk partitioning with separate /home).

This happened on two laptops:
Toshiba Satellite A660-157, Windows 7 + section recovery from Acronis
Asus U32U, Windows 7 + serial section recovery

So users are not familiar with Debian is not able to try it when installed
together with Windows and generally unable to function laptop.

For further corrections have to use a boot live-image and install GRUB
thrugh terminal. Installing Debian is not completed (not created Root
password, user, etc.)

Here is image
http://postimg.org/image/e2lzeit7v/
and here details of problem and solution
http://www.linux.org.ru/forum/linux-install/9034841#comments

Best regards, Oleg
---End Message---
---BeginMessage---
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#705790: marked as done (Installation hangs starting up the partitioner)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #705790,
regarding Installation hangs starting up the partitioner
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
705790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: USB stick
Image version: debian-testing-amd64-netinst.iso downloaded yesterday
Date: 2013-04-18 21:45 Pacific Time (-7:00?)

Machine: Puget Systems Echo II
Processor: Intel Core i3 3225
Memory: 8G (2 x Kingston DDR3-1600 4GB)
Partitions: /dev/sdb does not contain a valid partition table (says fdisk)
/dev/sdb - ST310005 1G via USB 2.0; sda is USB stick
No good way to get output from lspci out of the system.  Intel DH77DF
motherboard with no added internal devices.
Current connections are keyboard, external drive, USB stick, ethernet and
power.  The external drive enclosure has
additional USB ports, one of which is connected to a mouse.  The mouse
works in the graphical installer.


While netbooting squeeze I found the USB 3.0 ports did not work reliably;
nothing is attached to them.

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] via DHCP
Detect CD:  [?] I think it said it was detecting CD, which is
not on the system, and did use the USB stick for next step
Load installer modules: [O]
Detect hard drives: [E]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ] it did go through questions about this OK
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[E ]

Comments/Problems:


The system has no internal disk; I booted the installer off a USB stick
and have an external hard drive cocnnected via USB.  When the (graphical)
installer gets to the partition disk step it shows Starting up the
partitioner over a progress bar that is half complete.  Below there it
displays Scanning disks.  The drive mounted by USB is known to the
hardware, evidence by the BIOS boot menu, and to the installer OS,
evidence by /dev/disk/ entries.  The disk is unformatted as far as I know
(an exchange for a defective disk).

The system has been functioning OK (except for the USB 3.0) via netboot
and NFS; the server it was using died.

It's not entirely clear to me that this scenario (external drive only)
should work, though I had hopes.

Full story: this box was functioning as a HTPC via netboot with a server. 
The server died and I am attempting to use the box in its place using a
spare hard drive.

I'd love to get this working so I'm less hosed.
---End Message---
---BeginMessage---
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#694788: marked as done (bug report against the installation-reports)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #694788,
regarding bug report against the installation-reports
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
694788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: DVD
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/jigdo-dvd/debian-wheezy-DI-b4-amd64-DVD-1.jigdo
Date: Thu Nov 29, 17:00 UTC-1

Machine: Asus K55VJ i7
Processor: Intel Core i7 - 3630QM, 2.4 GHz
Memory: 8GB
Partitions:
Filesystem Type
1K-blocksUsed Available Use% Mounted on
rootfs rootfs
143222512 3581144 132366004   3% /
udev   devtmpfs
10240   0 10240   0% /dev
tmpfs  tmpfs
808096 720807376   1% /run
/dev/disk/by-uuid/40841bcc-f302-4cea-a8c5-ccd9cdc0084a ext4
143222512 3581144 132366004   3% /
tmpfs  tmpfs
5120   0  5120   0% /run/lock
tmpfs  tmpfs
5522320 328   5521992   1% /run/shm
/dev/sda1  vfat
303104   37756265348  13% /boot/efi
/dev/sda7  ext4
653666848  249728 620212744   1% /home

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor
DRAM Controller [8086:0154] (rev 09)
Subsystem: ASUSTeK Computer Inc. Device [1043:1447]
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor PCI Express Root Port [8086:0151] (rev 09)
Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen
Core processor Graphics Controller [8086:0166] (rev 09)
Subsystem: ASUSTeK Computer Inc. Device [1043:1447]
Kernel driver in use: i915
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
Subsystem: ASUSTeK Computer Inc. Device [1043:1447]
Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 7
Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev
04)
Subsystem: ASUSTeK Computer Inc. Device [1043:1447]
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
Subsystem: ASUSTeK Computer Inc. Device [1043:1447]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series
Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: ASUSTeK Computer Inc. Device [1043:1447]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series
Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series
Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series
Chipset Family PCI Express Root Port 4 [8086:1e16] (rev c4)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
Subsystem: ASUSTeK Computer Inc. Device [1043:1447]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation HM76 Express Chipset LPC
Controller [8086:1e59] (rev 04)
Subsystem: ASUSTeK Computer Inc. Device [1043:1447]
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset
Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
Subsystem: ASUSTeK Computer Inc. Device [1043:1447]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset
Family SMBus Controller [8086:1e22] (rev 04)
Subsystem: ASUSTeK Computer Inc. Device [1043:1447]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device
[10de:0de3] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 

Bug#702294: marked as done (installation-reports: netinst all ok)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #702294,
regarding installation-reports: netinst all ok
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
702294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: normal

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- Package-specific info:

Boot method: network
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_rc1/amd64/iso-cd/debian-wheezy-DI-rc1-amd64-netinst.iso
Date: Date and time of the install

Machine: noname Intel Core2Duo E4700/RAM: 2GB DDR2/HDD 160GB WD SATA/MB ASUS 
P5K-V/videonetwork:onboard
Partitions: df -Tl will do; the raw partition table is preferred


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:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.


-- 

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 20130211
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux a343 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 
Express DRAM Controller [8086:29c0] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation 82G33/G31 
Express Integrated Graphics Controller [8086:29c3] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #4 [8086:2937] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #5 [8086:2938] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #6 [8086:2939] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB2 EHCI Controller #2 [8086:293c] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) 
PCI Express Port 1 [8086:2940] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) 
PCI Express Port 6 [8086:294a] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller 

Bug#701196: marked as done (Installation-report)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #701196,
regarding Installation-report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
701196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: installation-reports

Boot method: Flash drive
Image version: Release 1, wheezy installer
Date: 2012 Feb 21

Machine: Dell T5600 
Processor:
Memory:32G
Partitions: df -Tl will do; the raw partition table is preferred

Output of lspci -knn (or lspci -nn):

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:  [E]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

I wanted to install a Raid 1 system with 2 active disks and one missing spare. 
After selecting
no partition for the spare, no MD drive was created but I was back at the 
create raid prompt.

I got around this by using a recovery disk to create the md drive before 
starting the install.



--As an additional problem, the entire install failed in that the new system 
would hang during
the boot (Someting after usb discovery)
---End Message---
---BeginMessage---
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#697645: Bug not solved

2013-08-31 Thread Franck
But do not reopen, because I went forward.

Just to inform you that I get success by:
Installing debian on my SSD through USB3 to SATA adapter,
*then plugin my SSD to the SATA controler when install was finished...

So:
- it is not a successfull install and
- I know from last hand experience that the functionality is not fully working
in 
Wheezy and
- they only contained a lot of information (and a user who was redy to make
test) and
- they didn't contained user errors (as I double check as usual when I'm
reporting a bug) and
- they weren't caused by broken hardware (because Wheezy is running well once
installed) and
- they have been from a STABLE release phase and
- they are quite old and not yet fixed today and
- moreinfo wasn't asked and 
- they aren't wishlist.

Now, I'm just waiting to get the next weekly-ISO of testing to check  ;-)


-- 
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/4163AAB7CB4741A7B2ACFEDEC189F171@BlackTower



Processed (with 5 errors): dealing with old installation-reports

2013-08-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 699136 partman
Bug #699136 [partman-base] partman hangs with specific mbr/usbsticks
Bug reassigned from package 'partman-base' to 'partman'.
Warning: Unknown package 'partman'
Warning: Unknown package 'partman'
Ignoring request to alter found versions of bug #699136 to the same values 
previously set
Warning: Unknown package 'partman'
Warning: Unknown package 'partman'
Ignoring request to alter fixed versions of bug #699136 to the same values 
previously set
Warning: Unknown package 'partman'
 retitle 699136 partman hangs with specific mbr/usbsticks
Bug #699136 [partman] partman hangs with specific mbr/usbsticks
Warning: Unknown package 'partman'
Ignoring request to change the title of bug#699136 to the same title
Warning: Unknown package 'partman'
 tags 696755 +confirmed
Bug #696755 [installation-reports] installation-reports: no network connection 
after reboot if only tasksel's standard and ssh-server
Ignoring request to alter tags of bug #696755 to the same tags previously set
 Hi,
Unknown command or malformed arguments to command.
 thank you for submitting installation reports, much appreciated.
Unknown command or malformed arguments to command.
 I read through all the bugs mentioned here (and I'm sure they were read by
Unknown command or malformed arguments to command.
 several people at the time they were submitted) and am closing them now as/if
Unknown command or malformed arguments to command.
 - they (finally) indicated success and/or
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

Please contact me if you need assistance.
-- 
696755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696755
699136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.137796793217357.transcr...@bugs.debian.org



Bug#694934: marked as done (Installer hangs at detect network hardware)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #694934,
regarding Installer hangs at detect network hardware
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
694934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: installation-reports

Boot method: From DVD image
Image version: debian-wheezy-DI-b4-amd64-DVD-1.iso
Date: 2012-12-01

Machine: Self-build around Asrock X58 motherboard
Processor: Intel i7-920
Memory: 6GB DDR3
Partitions: see attachment df_Tl.out
Output of lspci: see attachment lspci_knn.out

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

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

Comments/Problems:

I chose:
Advanced options 
  Alternative desktop environments 
Xfce 
  Advanced options 
Expert install

and answered questions about language, keyboard, locale (default), modules
to load (default), extra installer components (none).  At the next stage
Detect network hardware the installation stalled indefinitely (more than
ten minutes) with a blue screen having a single white line at the bottom
and a black cursor.  Keyboard input was echoed to this bottom line, but I
was unable to get any other response from the system and was obliged to
use the machine's power on/off switch.

On a second attempt, the installation progressed to completion when I
skipped the steps

  Detect network hardware
  Configure the network
  Configure the clock

although I was then left with an unusable system owing to the absence of
the necessary Radeon firmware (see bug #692001 for example).  Using a live
rescue CD and accessing the internal hard disk via chroot it was possible
to achieve network connectivity by manually setting up files
/etc/network/interfaces and /etc/resolv.conf, whereupon I could install the
package firmware-linux-nonfree and finally obtain a working graphical display.

Mike Thomas

Filesystem Type 1K-blocks
Used Available Use% Mounted on
rootfs rootfs   949052564 
2748460 898094952   1% /
udev   devtmpfs 10240   
0 10240   0% /dev
tmpfs  tmpfs   554628 
724553904   1% /run
/dev/disk/by-uuid/2ffea0c7-27f0-42f4-b5ab-a46796122a63 ext4 949052564 
2748460 898094952   1% /
tmpfs  tmpfs 5120   
0  5120   0% /run/lock
tmpfs  tmpfs  3624600   
0   3624600   0% /run/shm
00:00.0 Host bridge [0600]: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port 
[8086:3405] (rev 12)
Subsystem: ASRock Incorporation Device [1849:3405]
00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
Root Port 3 [8086:340a] (rev 12)
Kernel driver in use: pcieport
00:05.0 PCI bridge [0604]: Intel Corporation 5520/X58 I/O Hub PCI Express Root 
Port 5 [8086:340c] (rev 12)
Kernel driver in use: pcieport
00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
Root Port 7 [8086:340e] (rev 12)
Kernel driver in use: pcieport
00:09.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
Root Port 9 [8086:3410] (rev 12)
Kernel driver in use: pcieport
00:10.0 PIC [0800]: Intel Corporation 5520/5500/X58 Physical and Link Layer 
Registers Port 0 [8086:3425] (rev 12)
00:10.1 PIC [0800]: Intel Corporation 5520/5500/X58 Routing and Protocol Layer 
Registers Port 0 [8086:3426] (rev 12)
00:14.0 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub System Management 
Registers [8086:342e] (rev 12)
Kernel driver in use: i7core_edac
00:14.1 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch 
Pad Registers [8086:3422] (rev 12)
00:14.2 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub Control Status and 
RAS Registers [8086:3423] (rev 12)
00:14.3 PIC [0800]: Intel Corporation 

Bug#695058: marked as done (Linux installation bug)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #695058,
regarding Linux installation bug
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
695058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: Purchased a DVD or Debian 6.0.6 from linuxCollections.com
Image version: LC catalog #53628, don't know what else to put
Date: 12/03/2012

Machine: G5 Mac, 4 Gig Memory 250 Gig Hard Drive
Processor: PPC 9xx series
Memory:
Partitions: selected 'default suggested for new users'

Output of I don't know, doesn't ring a bell, will reinstall if
requested, also installed 'intall64'

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

Comments/Problems:
Installation seems to be ok, but when it re-boots, the display shows
output from the scripts. However towards the end, I'm assuming, the
display goes black and says NO SIGNAL.  I did notice that it
output that it was 'setting the display to default' I believe.  Also,
the Cinema display screen that I had is not connected but is replace
with a View Sonic VA720 (other is in storage in another state)
and is going through a 'dongle' that changes the output pins to that
that resemble a VGA display.

My questions:  Can I invoke it to just give me a non gui interface via
some boot option?
 This option would at least allow me to view what's happening and if
the boot actually completed properly.
I tried to download the 'netinst' image and it resulted in the same
problem. Although I could ^C out of the scripts and get to a partial
system, but many things seemed missing.
should I install another option, install expert64, etc?  I was hoping
that the complete system would avoid this problem.  Any suggestions
would be appreciated.  Note that I can't get into the system to
run any commands or see any output.  Is there any way to get 'error
out' or the displayed output to some device? like a printer or better
still a file that I can find?
---End Message---
---BeginMessage---
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
---End Message---


Bug#695008: marked as done (installation-reports: Acer TM8371 nicely installed, partitioning could be improved, suspend to RAM broken)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #695008,
regarding installation-reports: Acer TM8371 nicely installed, partitioning 
could be improved, suspend to RAM broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
695008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: normal
Tags: d-i

Dear Maintainer,

As I was not concentrated during the disk partitioning process, the
partition manager wanted to use my USB flash drive used for booting the
installer for the system installation, and I only noticed when the
partitioning table was already written.

Then, I got a warning that the installer could not inform the kernel
of the change in the partitioning table, presumably because the device
was mounted.

I wonder why this could happen, but I believe it should not be possible
to select the medium from which the installer was booted as a system
disk in the partitioning manager.

I had to put the installer on the USB drive again and restart the
process.

Partitioning: Also, it turned out that the 10 GB proposed as default for
the root partition, when choosing a separate /home partition, was not
enough for my KDE4 installation (well, not only KDE4...), so I had
trouble when I installed my package list via dpkg --set-selections.

Package selection: It was also problematic that dselect was not
installed per default, as I wanted to recover my package list from the
predecessor system via dpkg --set-selections. Please consider putting it
back into the list of packages installed per default.

Sound: I had to start alsamixer to unmute channel speaker. This is not
obvious for GUI users.

Suspend to RAM: This does not work any more. I am currently looking for
the appropriate plasma component to file a bug report on this.

Thanks for your kind attention,

Johannes


-- Package-specific info:

Boot method: USB flash drive
Image version: debian-wheezy-DI-b4-amd64-netinst.iso
Date: Date and time of the install

Machine: Acer Travelmate 8371
Partitions: df -Tl will do; the raw partition table is preferred
DateisystemTyp
1K-Blöcke   Benutzt Verfügbar Verw% Eingehängt auf
rootfs rootfs
9611492   8841268281984   97% /
udev   devtmpfs
10240 0 102400% /dev
tmpfs  tmpfs
198860   7041981561% /run
/dev/disk/by-uuid/004a0d93-feb6-416b-9534-7d3fa4db5cfa ext4
9611492   8841268281984   97% /
tmpfs  tmpfs
5120 0  51200% /run/lock
tmpfs  tmpfs
1206860 0   12068600% /run/shm
/dev/sda6  ext4
478661528 372713672  81633184   83% /home


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:  [E]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

As detailed above, the partition manager at first wanted to use my USB
flash drive from which the installer was loaded, as a system disk.

-- 

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=cdrom

==
Installer hardware-summary:
==
uname -a: Linux time 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series 
Chipset Memory Controller Hub [8086:2a40] (rev 07)
lspci 

Bug#706320: marked as done (Installation-report)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id 201308311252.51555.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #706320,
regarding Installation-report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
706320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: USB generate with unetbootin application
Image version: http://d-i.debian.org/daily-images/i386/daily/netboot/mini.iso
Date: 28-04-2013 at 11:30 am

Machine: Inves Noobi 10 (Educational PC)
Processor: Intel Atom CPU N450 @1.66GHz
Memory: 1GB
Partitions:

S.ficheros  Tipo 1K-bloques  Usados Disponibles Uso% Montado en
rootfs  rootfs  9611492 3639372 5483880  40% /
udevdevtmpfs  10240   0   10240   0% /dev
tmpfs   tmpfs102384 724  101660   1% /run
/dev/mapper/debian-root ext49611492 3639372 5483880  40% /
tmpfs   tmpfs  5120   05120   0% /run/lock
tmpfs   tmpfs204760 268  204492   1% /run/shm
/dev/sda1   ext2 233191   17127  203623   8% /boot
/dev/mapper/debian-home ext4  141935424  196168   134529272   1% /home


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]
Subsystem: QUANTA Computer Inc Device [152d:0834]
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]
Subsystem: QUANTA Computer Inc Device [152d:0834]
Kernel driver in use: i915
00:02.1 Display controller [0380]: Intel Corporation Atom Processor
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012]
Subsystem: QUANTA Computer Inc Device [152d:0834]
00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High
Definition Audio Controller [8086:27d8] (rev 02)
Subsystem: QUANTA Computer Inc Device [152d:0834]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI
Express Port 1 [8086:27d0] (rev 02)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI
Express Port 2 [8086:27d2] (rev 02)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB
UHCI Controller #1 [8086:27c8] (rev 02)
Subsystem: QUANTA Computer Inc Device [152d:0834]
Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB
UHCI Controller #2 [8086:27c9] (rev 02)
Subsystem: QUANTA Computer Inc Device [152d:0834]
Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB
UHCI Controller #3 [8086:27ca] (rev 02)
Subsystem: QUANTA Computer Inc Device [152d:0834]
Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB
UHCI Controller #4 [8086:27cb] (rev 02)
Subsystem: QUANTA Computer Inc Device [152d:0834]
Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2
EHCI Controller [8086:27cc] (rev 02)
Subsystem: QUANTA Computer Inc Device [152d:0834]
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: QUANTA Computer Inc Device [152d:0834]
00:1f.2 SATA controller [0106]: Intel Corporation NM10/ICH7 Family
SATA Controller [AHCI mode] [8086:27c1] (rev 02)
Subsystem: QUANTA Computer Inc Device [152d:0834]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus
Controller [8086:27da] (rev 02)
Subsystem: QUANTA Computer Inc Device [152d:0834]
Kernel driver in use: i801_smbus
05:00.0 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host
Controller [197b:2382] (rev 80)
Subsystem: QUANTA Computer Inc Device [152d:0834]
Kernel driver in use: sdhci-pci
05:00.2 SD Host controller [0805]: JMicron Technology Corp. Standard
SD Host Controller [197b:2381] (rev 80)
Subsystem: QUANTA Computer Inc Device 

Bug#695180: marked as done (Installation report)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #695180,
regarding Installation report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
695180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reportsBoot method: Debian-testing-64-kde-iso "burned" to an USBImage version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-kde-CD-1.isoDate: 3-December-2012Machine: Toshiba Portégé Z830Processor: i5Memory: 4GbPartitions: /dev/sda1 ext4 mounted on /Output of lspci -knn (or lspci -nn):00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09)00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 04)00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b4)00:1c.4 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b4)00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04)00:1f.0 ISA bridge [0601]: Intel Corporation HM65 Express Chipset Family LPC Controller [8086:1c49] (rev 04)00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 04)01:00.0 System peripheral [0880]: Ricoh Co Ltd Device [1180:e823] (rev 07)02:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)03:00.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 04)Base System Installation Checklist:[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try itInitial 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:[O]Comments/Problems:Everything went almost all right. Only one issue: on my first attempt, despite having set the right partition on the main disk, at the end of the partitioning and disk setting step, the installer tried to format my SD card instead; so, I had to remove it in order for the installer not to get confused.And one suggestion: just before installing the system and after the warning "if you chose to use a mirror the next step might take very long" (or something like that), there is a step called "select and install packages"; however, you're not offered any kind of "selection" prior to installation, which is somewhat misleading, as there's nothing to select then: the installer starts installing packages right away. I suggest this step should read only "install packages".---End Message---
---BeginMessage---
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + 

Bug#695476: marked as done (installation-report: workarounds for i845 rev 1 on wheezy)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #695476,
regarding installation-report: workarounds for i845 rev 1 on wheezy
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
695476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Version: 2.47
Severity: normal
Tags: d-i

Dear Maintainer,

Pretty good, but lightdm crashes x on this board.  Also reportbug does not 
--configure itself on first run.

Hope this info will help someone, not sure where to send it.  Maybe you can help
forward, this will probably be a fairly common problem when wheezy goes stable.

I found two ways to run x on this board with direct rendering, details below.
# /usr/share/X11/xorg.conf.d/05-i845g.conf
# 8086:2562 Intel Corporation
# 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
Section Device
#Option DRI False# [bool]
Option DRI True# [bool]
#option dri false results from glxinfo:
#direct rendering: Yes
#OpenGL vendor string: VMware, Inc.
#OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x209)
#OpenGL version string: 2.1 Mesa 8.0.4
#OpenGL shading language version string: 1.20
#---
#option dri true
#direct rendering: Yes
#OpenGL vendor string: Tungsten Graphics, Inc
#OpenGL renderer string: Mesa DRI Intel(R) 845G x86/MMX/SSE2
#OpenGL version string: 1.3 Mesa 8.0.4
#---
Option Shadow  True# [bool]
#Option Shadow  False# [bool]
# Shadow False = kernel panic before x starts, no Xorg log
Option XvMC   False # [bool]
Option XvPreferOverlay  False   # [bool]
# The Two Above seem related to the kernel panic
Identifier  Card0
Driver  intel
VendorName  Intel Corporation
BoardName   82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics $
BusID   PCI:0:2:0
EndSection

-- Package-specific info:

Boot method: usb flash
Image version: wheezy beta4 lxde cd, base only
Date: dec, 07, 2012

Machine: netvista 8305
--


==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=7.0 (wheezy) - installer build 20121114
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux junior 3.2.0-4-486 #1 Debian 3.2.32-1 i686 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 
82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] 
(rev 01)
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 
01)
lspci -knn: Subsystem: IBM Device [1014:0267]
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01)
lspci -knn: Subsystem: IBM Device [1014:0267]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01)
lspci -knn: Subsystem: IBM Device [1014:0267]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.7 USB controller [0c03]: Intel Corporation 82801DB/DBM 
(ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01)
lspci -knn: Subsystem: IBM Device [1014:0267]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev 81)
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801DB/DBL 
(ICH4/ICH4-L) LPC Interface Bridge [8086:24c0] (rev 01)
lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 82801DB (ICH4) IDE 
Controller [8086:24cb] (rev 01)
lspci -knn: Subsystem: IBM Device [1014:0267]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) SMBus Controller [8086:24c3] (rev 01)
lspci -knn: Subsystem: IBM Device [1014:0267]
lspci -knn: 02:08.0 Ethernet controller [0200]: Intel Corporation 82801DB 
PRO/100 VE (LOM) 

Bug#695669: marked as done (Installation Failure)

2013-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2013 12:52:55 +0200
with message-id 201308311253.30231.hol...@layer-acht.org
and subject line dealing with old installation-reports
has caused the Debian Bug report #695669,
regarding Installation Failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
695669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: installation-reports
Wheezy DI-b4 lxde Binary-1 20121117-19:19
  debian-wheezy-DI-b4-i386-lxde-CD-1.iso
Booted from CD; Dec. 10, 2012 c.10AM
Machine: HPcompaq 6910p
Processor: Intel Core(TM)2 Duo
Memory: 2G

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xfc5e16ea

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   1 638 5124703+   7  HPFS/NTFS
/dev/sda2 6391726 87393607  HPFS/NTFS
/dev/sda31727   14594   1033553935  Extended
/dev/sda5   *1728   1085073280497+  83  Linux
/dev/sda6   14089   14594 4051968   82  Linux swap / 
Solaris

/dev/sda7   10851   1238112288000   83  Linux
/dev/sda8   12382   1403913312000   83  Linux00:00.0


00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 
Memory Controller Hub [8086:2a00] (rev 0c)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
00:01.0 PCI bridge [0604]: Intel Corporation Mobile PM965/GM965/GL960 
PCI Express Root Port [8086:2a01] (rev 0c)

Kernel driver in use: pcieport
00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM Gigabit 
Network Connection [8086:1049] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: e1000e
00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) 
USB UHCI Controller #4 [8086:2834] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: uhci_hcd
00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) 
USB UHCI Controller #5 [8086:2835] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: uhci_hcd
00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) 
USB2 EHCI Controller #2 [8086:283a] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD 
Audio Controller [8086:284b] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: HDA Intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI 
Express Port 1 [8086:283f] (rev 03)

Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI 
Express Port 2 [8086:2841] (rev 03)

Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI 
Express Port 5 [8086:2847] (rev 03)

Kernel driver in use: pcieport
00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) 
USB UHCI Controller #1 [8086:2830] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: uhci_hcd
00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) 
USB UHCI Controller #2 [8086:2831] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: uhci_hcd
00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) 
USB UHCI Controller #3 [8086:2832] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: uhci_hcd
00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) 
USB2 EHCI Controller #1 [8086:2836] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
[8086:2448] (rev f3)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801HBM (ICH8M-E) LPC 
Interface Controller [8086:2811] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
00:1f.1 IDE interface [0101]: Intel Corporation 82801HBM/HEM 
(ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 03)

Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver 

Bug#721460: debian-installer: Unable to preseed keyboard layout de_CH for Wheezy

2013-08-31 Thread Stephan
Package: debian-installer
Severity: normal
Tags: l10n


I'm trying to deploy Debian using preseeding.
Unfortunately I'm not able to set the swiss german keyboard layout.

The append line contains the following settings:
language=en country=CH locale=en_US.UTF-8 debian-installer/keymap=de_CH 
keymap=de_CH

But the keymap is not set correctly.
If I switch to the second console the file /etc/default/keyboard contains:
XKBMODEL=pc105
XKBLAYOUT=us
XKBVARIANT=
XKBOPTIONS=

I also tried the setting sg-latin1:
language=en country=CH locale=en_US.UTF-8 debian-installer/keymap=sg-latin1 
keymap=sg-latin1

The file /etc/default/keyboard then contains:
XKBMODEL=pc105
XKBLAYOUT=
XKBVARIANT=de
XKBOPTIONS=

The same setup for swiss french seems to work.
language=en country=CH locale=en_US.UTF-8 debian-installer/keymap=fr_CH 
keymap=fr_CH

Contents of /etc/default/keyboard:
XKBMODEL=pc105
XKBLAYOUT=ch
XKBVARIANT=fr
XKBOPTIONS=


If the keymap options are not set on the append line and swiss german is 
selected manually it seems to work.

I used the debian-installer from the i386 netboot:
ftp://ftp.ch.debian.org/debian/dists/wheezy/main/installer-i386/current/images/netboot/debian-installer/i386/

I haven't tested any other installer yet.


Thanks,
Stephan


-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
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/20130831195437.13747.76631.report...@juno.srv.aiwana.ch



Bug#721360: debian-installer: warn that blockdev-wipe can be very slow

2013-08-31 Thread Julian Gilbey
On Fri, Aug 30, 2013 at 08:22:29PM +0200, Holger Levsen wrote:
 control: severity -1 wishlist
 control: tags -1 +confirmed

Oh, gosh, I didn't realise *how* slow: it's taken about 36 *hours*
(!!!) to wipe the 750GB disc.

That is not really going to endear Debian to people trying it for the
first time or even not for the first time; there really has to be a
better way of handling this!

I don't want to play bug-severity games, but I'd rate this higher than
wishlist, as 36 hours to even begin the installation is unreasonable.

   Julian


-- 
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/20130831231907.ga6...@d-and-j.net



Bug#721360: debian-installer: warn that blockdev-wipe can be very slow

2013-08-31 Thread Cyril Brulebois
Julian Gilbey j...@debian.org (2013-09-01):
 On Fri, Aug 30, 2013 at 08:22:29PM +0200, Holger Levsen wrote:
  control: severity -1 wishlist
  control: tags -1 +confirmed
 
 Oh, gosh, I didn't realise *how* slow: it's taken about 36 *hours*
 (!!!) to wipe the 750GB disc.
 
 That is not really going to endear Debian to people trying it for the
 first time or even not for the first time; there really has to be a
 better way of handling this!
 
 I don't want to play bug-severity games, but I'd rate this higher than
 wishlist, as 36 hours to even begin the installation is unreasonable.

Like the 'Cancel' button?
| partman-crypto (23) unstable; urgency=low
| ...
|   * Make erase cancellable. Closes: #381898, #400034
| ...
|  -- Max Vozeler x...@debian.org  Sun, 25 Nov 2007 17:01:43 +0100

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#721360: debian-installer: warn that blockdev-wipe can be very slow

2013-08-31 Thread Julian Gilbey
On Sun, Sep 01, 2013 at 01:31:38AM +0200, Cyril Brulebois wrote:
  Oh, gosh, I didn't realise *how* slow: it's taken about 36 *hours*
  (!!!) to wipe the 750GB disc.
  
  That is not really going to endear Debian to people trying it for the
  first time or even not for the first time; there really has to be a
  better way of handling this!
  
  I don't want to play bug-severity games, but I'd rate this higher than
  wishlist, as 36 hours to even begin the installation is unreasonable.
 
 Like the 'Cancel' button?
 
 Mraw,
 KiBi.

Yes, there's a cancel button, but that might take me back to the
partitioning process and then I'd have to start again perhaps - or
does it just cancel the wiping stage?  It's not clear, and I'm a
little reticent to try, having been sitting here for so long already.
(It's currently at 87% ;-)

It seems to me (as a naïve user who's not looked into the installer
process in detail) that before embarking on a disc wipe, it would be
good to offer a choice: Do you wish to wipe the disc before
installing Debian?  This has the advantage that ..., but it could take
about NNN hours.  Yes/No.  Then either call blockdev-wipe or skip
that step, depending upon the user's choice.

   Julian


-- 
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/20130831235056.ga7...@d-and-j.net



Bug#721360: debian-installer: warn that blockdev-wipe can be very slow

2013-08-31 Thread Cyril Brulebois
Julian Gilbey j...@debian.org (2013-09-01):
 On Sun, Sep 01, 2013 at 01:31:38AM +0200, Cyril Brulebois wrote:
  Like the 'Cancel' button?

I did write more than that, I quoted a changelog entry, which contains
bug references. If you had read the whole *four* lines of #381898…

  Mraw,
  KiBi.
 
 Yes, there's a cancel button, but that might take me back to the
 partitioning process and then I'd have to start again perhaps - or
 does it just cancel the wiping stage?  It's not clear, and I'm a
 little reticent to try, having been sitting here for so long already.
 (It's currently at 87% ;-)

Happy waiting then.

 It seems to me (as a naïve user who's not looked into the installer
 process in detail) that before embarking on a disc wipe, it would be
 good to offer a choice: Do you wish to wipe the disc before
 installing Debian?  This has the advantage that ..., but it could take
 about NNN hours.  Yes/No.  Then either call blockdev-wipe or skip
 that step, depending upon the user's choice.

I didn't object.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#721360: debian-installer: warn that blockdev-wipe can be very slow

2013-08-31 Thread Ben Hutchings
On Sun, 2013-09-01 at 01:31 +0200, Cyril Brulebois wrote:
 Julian Gilbey j...@debian.org (2013-09-01):
  On Fri, Aug 30, 2013 at 08:22:29PM +0200, Holger Levsen wrote:
   control: severity -1 wishlist
   control: tags -1 +confirmed
  
  Oh, gosh, I didn't realise *how* slow: it's taken about 36 *hours*
  (!!!) to wipe the 750GB disc.
  
  That is not really going to endear Debian to people trying it for the
  first time or even not for the first time; there really has to be a
  better way of handling this!
  
  I don't want to play bug-severity games, but I'd rate this higher than
  wishlist, as 36 hours to even begin the installation is unreasonable.
 
 Like the 'Cancel' button?
 | partman-crypto (23) unstable; urgency=low
 | ...
 |   * Make erase cancellable. Closes: #381898, #400034
 | ...
 |  -- Max Vozeler x...@debian.org  Sun, 25 Nov 2007 17:01:43 +0100

I have to wonder why this is so slow.  We should be able to write about
100 MB/s sequentially to a recent HD, so 750 GB would take about 2 hours
and not 36 hours.

Is encryption really that expensive, and if so can we fix this by adding
accelerated crypto drivers to d-i (such as aesni_intel)?

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg


signature.asc
Description: This is a digitally signed message part


Bug#721360: debian-installer: warn that blockdev-wipe can be very slow

2013-08-31 Thread Cyril Brulebois
Ben Hutchings b...@decadent.org.uk (2013-09-01):
 I have to wonder why this is so slow.  We should be able to write about
 100 MB/s sequentially to a recent HD, so 750 GB would take about 2 hours
 and not 36 hours.
 
 Is encryption really that expensive, and if so can we fix this by adding
 accelerated crypto drivers to d-i (such as aesni_intel)?

I have no particular clue about that (except the few times I used it it
really felt slow, but then that was with low end laptops, so I wasn't
expecting anything speedish); but the idea of adding accelerated crypto
stuff to d-i would seem like a nice idea if that indeed helps.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Debian installer build: failed or old builds

2013-08-31 Thread Daily build aggregator
Debian installer build overview
---

Failed or old builds:

* FAILED BUILD: amd64 Sep 01 00:02 buildd@barber build_cdrom_isolinux 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log

* FAILED BUILD: amd64 Sep 01 00:03 buildd@barber build_cdrom_gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_gtk.log

* FAILED BUILD: amd64 Sep 01 00:03 buildd@barber build_cdrom-xen 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom-xen.log

* FAILED BUILD: amd64 Sep 01 00:05 buildd@barber build_netboot-gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log

* FAILED BUILD: amd64 Sep 01 00:05 buildd@barber build_netboot-xen 

http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log

* FAILED BUILD: amd64 Sep 01 00:05 buildd@barber build_hd-media 

http://d-i.debian.org/daily-images/amd64/daily/build_hd-media.log

* FAILED BUILD: amd64 Sep 01 00:06 buildd@barber build_hd-media_gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_hd-media_gtk.log

* FAILED BUILD: armel Aug 31 08:35 buildd@ancina build_kirkwood_netboot-gtk 

http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log

* OLD BUILD:armhf Aug 21 23:08 buildd@hasse build_mx5_netboot 

http://d-i.debian.org/daily-images/armhf/daily/build_mx5_netboot.log

* OLD BUILD:armhf Aug 22 03:20 buildd@hasse build_mx5_network-console 

http://d-i.debian.org/daily-images/armhf/daily/build_mx5_network-console.log

* OLD BUILD:armhf Aug 22 09:27 buildd@hasse build_mx5_netboot-gtk 

http://d-i.debian.org/daily-images/armhf/daily/build_mx5_netboot-gtk.log

* OLD BUILD:armhf Aug 22 14:33 buildd@hasse build_vexpress_netboot 

http://d-i.debian.org/daily-images/armhf/daily/build_vexpress_netboot.log

* FAILED BUILD: i386 Sep 01 00:03 buildd@biber build_cdrom_isolinux 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom_isolinux.log

* FAILED BUILD: i386 Sep 01 00:04 buildd@biber build_cdrom_gtk 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom_gtk.log

* FAILED BUILD: i386 Sep 01 00:04 buildd@biber build_cdrom-xen 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom-xen.log

* FAILED BUILD: i386 Sep 01 00:06 buildd@biber build_netboot-gtk 

http://d-i.debian.org/daily-images/i386/daily/build_netboot-gtk.log

* FAILED BUILD: i386 Sep 01 00:06 buildd@biber build_netboot-xen 

http://d-i.debian.org/daily-images/i386/daily/build_netboot-xen.log

* FAILED BUILD: i386 Sep 01 00:06 buildd@biber build_hd-media 
http://d-i.debian.org/daily-images/i386/daily/build_hd-media.log

* FAILED BUILD: i386 Sep 01 00:07 buildd@biber build_hd-media_gtk 

http://d-i.debian.org/daily-images/i386/daily/build_hd-media_gtk.log

* OLD BUILD:ia64 May 26 00:12 buildd@alkman build_cdrom 
http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log

* OLD BUILD:ia64 May 26 00:16 buildd@alkman build_netboot 
http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log

* OLD BUILD:amd64 Aug 12 09:17 debian-cd@pettersson 4sidmipsel 
http://cdbuilder.debian.org/cdimage-log/4sidmipsel

* OLD BUILD:amd64 Aug 19 09:33 debian-cd@pettersson 4sidmipsel 
http://cdbuilder.debian.org/cdimage-log/4sidmipsel

* OLD BUILD:amd64 Aug 19 11:40 debian-cd@pettersson 4sidkfreebsd-amd64 
http://cdbuilder.debian.org/cdimage-log/4sidkfreebsd-amd64

* OLD BUILD:amd64 Aug 19 12:12 debian-cd@pettersson Asidkfreebsd-i386 
http://cdbuilder.debian.org/cdimage-log/Asidkfreebsd-i386

* OLD BUILD:amd64 Aug 19 12:12 debian-cd@pettersson 4sidkfreebsd-i386 
http://cdbuilder.debian.org/cdimage-log/4sidkfreebsd-i386

* FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson 5sidi386 
http://cdbuilder.debian.org/cdimage-log/5sidi386

* FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson Asidi386 
http://cdbuilder.debian.org/cdimage-log/Asidi386

* FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson 4sidi386 
http://cdbuilder.debian.org/cdimage-log/4sidi386

* FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson Dsidi386 
http://cdbuilder.debian.org/cdimage-log/Dsidi386

* FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson sidi386 
http://cdbuilder.debian.org/cdimage-log/sidi386

* FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson 9sidi386 
http://cdbuilder.debian.org/cdimage-log/9sidi386

* FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson 3sidi386 
http://cdbuilder.debian.org/cdimage-log/3sidi386

* FAILED BUILD: amd64