Bug#806164: installation-reports: jessie install on dell xps 13 9350 (grub-installer issues)

2015-11-24 Thread Julien Cristau 
Package: installation-reports

Boot method: USB
Image version: 
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/firmware-8.2.0-amd64-netinst.iso
Date: November 24, 2015

Machine: Dell XPS 13 9350
Partitions: fdisk -l

Disk /dev/nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 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
Disklabel type: gpt
Disk identifier: 121A6F68-CA63-4FB1-98BD-61F0971A674C

Device StartEnd   Sectors   Size Type
/dev/nvme0n1p1  20481026047   1024000   500M EFI System
/dev/nvme0n1p2   10260481288191262144   128M Microsoft reserved
/dev/nvme0n1p3   1288192  502419455 501131264   239G Microsoft basic data
/dev/nvme0n1p4 977592320  979337215   1744896   852M Windows recovery environmen
/dev/nvme0n1p5 979337216 1000214527  2087731210G Windows recovery environmen
/dev/nvme0n1p6 502419456  961990655 459571200 219.1G Linux filesystem
/dev/nvme0n1p7 961990656  977592319  15601664   7.5G Linux swap

Partition table entries are not in disk order.


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

Initial boot:   [O]
Detect network card:[O] (had to use an usb wlan thing, the shipped one 
isn't supported until linux 4.4)
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [E] 
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[E]
Overall install:[O]

Comments/Problems:

Initially, the disk was setup as "RAID" in the BIOS, and I couldn't get
linux to recognize it.  Googling suggested disabling that mode and using
"AHCI" instead.  That broke Windows, so I had to reinstall, but it
allowed d-i to see the disk.

Installation went fine (well, had to stay close to the screen because
the text was quite small on this high-dpi display) until the
grub-installer step.  Which failed horribly, I think because the
/dev/nvme0n1 device name for the drive isn't expected.  See attached
excerpt from syslog (contains a few invocations of grub-installer while
I was trying to understand what was going on; the last one has
DEBCONF_DEBUG and set -x enabled.

After reboot I'm on the fbdev X driver (on simplefb) and llvmpipe, and
gnome-shell works surprisingly well (if it wasn't for xrandr not listing
outputs I might not have noticed).

Cheers,
Julien
-- 

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150422+deb8u2"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux  3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 
(2015-08-04) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:1904] 
(rev 08)
lspci -knn: Subsystem: Dell Device [1028:0704]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:1916] (rev 07)
lspci -knn: Subsystem: Dell Device [1028:0704]
lspci -knn: 00:04.0 Signal processing controller [1180]: Intel Corporation 
Device [8086:1903] (rev 08)
lspci -knn: Subsystem: Dell Device [1028:0704]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:9d2f] 
(rev 21)
lspci -knn: Subsystem: Dell Device [1028:0704]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation 
Device [8086:9d31] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:0704]
lspci -knn: 00:15.0 Signal processing controller [1180]: Intel Corporation 
Device [8086:9d60] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:0704]
lspci -knn: 00:15.1 Signal processing controller [1180]: Intel Corporation 
Device [8086:9d61] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:0704]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Device 
[8086:9d3a] (rev 21)
lspci -knn: Subsystem: Dell Device [1028:0704]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:9d14] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation Device [8086:9d15] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9d18] 
(rev f1)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d48] 
(rev 21)
lspci -knn:

Bug#806171: flash-kernel causes postinsts to fail when it happens to be installed on an unsupported system

2015-11-24 Thread Newell Jensen 
Package: flash-kernel
Version: 3.50
Severity: normal
Tags: patch

diff --git a/functions b/functions
index d86cf7d..d07b967 100644
--- a/functions
+++ b/functions
@@ -629,6 +629,10 @@ if [ -L "$kfile" ]; then
 fi

 if ! check_supported "$machine"; then
+# do nothing if an unsupported platform is booted from EFI
+ if [ -d /sys/firmware/efi ]; then
+echo "Unsupported platform on EFI system."
+ exit 0
  error "Unsupported platform."
 fi



Dear Maintainer,

   * What led up to the situation?
Running:
$ apt-get --reinstall install linux-image-4.2.0-1-arm64; echo $?
Led to:
Processing triggers for flash-kernel (3.50) ...
Unsupported platform.
dpkg: error processing package flash-kernel (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
flash-kernel
E: Sub-process /usr/bin/dpkg returned an error code (1)
100

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

   * What was the outcome of this action?
See above.

   * What outcome did you expect instead?
Non-fatal warning.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 4.2.0-1-arm64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.58
ii  devio  1.2-1
ii  initramfs-tools0.120
ii  linux-base 4.0
ii  ucf3.0031

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2015.10+dfsg1-2

flash-kernel suggests no packages.

-- debconf information:
  flash-kernel/linux_cmdline: quiet

Processing of flash-kernel_3.51_armel.changes

2015-11-24 Thread Debian FTP Masters 
flash-kernel_3.51_armel.changes uploaded successfully to ftp-master.debian.org
along with the files:
  flash-kernel_3.51.dsc
  flash-kernel_3.51.tar.xz
  flash-kernel-installer_3.51_armel.udeb
  flash-kernel_3.51_armel.deb

Greetings,

Your Debian queue daemon (running on host coccia.debian.org)

Processing of flash-kernel_3.51_armel.changes

2015-11-24 Thread Debian FTP Masters 
flash-kernel_3.51_armel.changes uploaded successfully to localhost
along with the files:
  flash-kernel_3.51.dsc
  flash-kernel_3.51.tar.xz
  flash-kernel-installer_3.51_armel.udeb
  flash-kernel_3.51_armel.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

Re: Broken EFI grub.cfg on stretch images

2015-11-24 Thread Steve McIntyre 
On Mon, Nov 23, 2015 at 12:09:41PM -0430, Emilio Lazo Zaia wrote:
>On 23/11/15 11:16, Steve McIntyre wrote:
>>On Mon, Nov 23, 2015 at 10:50:02AM -0430, Emilio Lazo Zaia wrote:
>>>Hello
>>>
>>>Debian-installer testing gives GRUB prompt while booting on UEFI platforms;
>>>the issue is related to a broken /boot/grub/grub.cfg file. The screen shows
>>>only Debian's background and the loaded font but no menu options are shown.
>>>
>>>Up to the date (Nov 23), all three (official, weekly and daily) images are
>>>broken. Its grub.cfg file is only 449 bytes and the last line is "set
>>>theme="; there are no "menuentry" directives, so after loading theme it comes
>>>with the prompt.
>>Hmmm. Can you give me a URL to exactly which images you're looking at
>>please? I've just looked at a daily sid amd64 netinst iso and it looks
>>sane enough to me from the files in its build tree. This suggests
>>we're looking at different images, maybe...
>I'm sorry; I forgot to mention some details: multi-arch netinst ISO images
>are the failing ones. For example:

Ah, ok. Yes, I see that now. Thanks for clarifying!

>Official CD and DVD multi-arch [1], [2] aren't good... amd64 and i386 looks
>fine. Weekly multi-arch DVD and CD [3] and [4] are broken. Daily CD
>multi-arch is also broken [5].
>
>grub.cfg file seems to be truncated at 449 bytes.

I'm looking now to see what's broken there, thanks for reporting.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Mature Sporty Personal
  More Innovation More Adult
  A Man in Dandism
  Powered Midship Specialty

flash-kernel_3.51_armel.changes ACCEPTED into unstable

2015-11-24 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 24 Nov 2015 12:27:57 +0100
Source: flash-kernel
Binary: flash-kernel flash-kernel-installer
Architecture: source armel
Version: 3.51
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 flash-kernel - utility to make certain embedded devices bootable
 flash-kernel-installer - Make the system bootable (udeb)
Closes: 805856
Changes:
 flash-kernel (3.51) unstable; urgency=medium
 .
   [ Vagrant Cascadian ]
   * Fix typo with distro_bootpart handling in u-boot generic bootscript.
   * Fix syntax errors when testing for empty variables in uboot-generic,
 cubox-i, and wandboard bootscripts. Thanks to Rick Thomas for the
 report (Closes: #805856).
   * Add a machine db entry for Kosagi Novena Dual/Quad.
   * Add a machine db entry for Lamobo R1.
Checksums-Sha1:
 af5ecc4663266c25981a39abb9aab577842082da 1853 flash-kernel_3.51.dsc
 fb638369dbfb01b6fe49030d2bfbaae8094ab3c2 63324 flash-kernel_3.51.tar.xz
 2e911e88daab5d958a20cc77a6336e0bace4b2ad 23624 
flash-kernel-installer_3.51_armel.udeb
 671b249000e47f0776ea1b1aae4f7c6f297b3708 39206 flash-kernel_3.51_armel.deb
Checksums-Sha256:
 61284607656cdd9a64c8a8e3b5b4daf90a4c05a751b962d5346777f74f1ee956 1853 
flash-kernel_3.51.dsc
 7aea0374eee53b9ada03144bb1f0f6eed914f3a960068084a96a9f7380de010a 63324 
flash-kernel_3.51.tar.xz
 53cad24e05427c423561f94262954291a620f8e3e0ff0d8589a91d3b9305f607 23624 
flash-kernel-installer_3.51_armel.udeb
 ffac3eae29db0ff71f9bb522439ca29f9f96e3b73c714b01c7dd861f16e1d76b 39206 
flash-kernel_3.51_armel.deb
Files:
 abfd6842fe385c53b88f76d26705e1bc 1853 utils optional flash-kernel_3.51.dsc
 b91ce64fef622124a8f4268a4a72b4d6 63324 utils optional flash-kernel_3.51.tar.xz
 045e06dbdacd482155f06ce401ae2ef1 23624 debian-installer standard 
flash-kernel-installer_3.51_armel.udeb
 6f3fcee7e15e1454297be18d6985d047 39206 utils optional 
flash-kernel_3.51_armel.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWVImgAAoJEIcvcCxNbiWo4SAP/i1YkCLZe8jILDYAA3LZOkBX
2vQOM1LXI26p3I85p8BJRj1W5hK7SMT3/KSeDiYErm8IETCu77Is1HiBKoPV2T7Z
mqcGdsO3uVK9Qg7joPsj3T/M1IKS2DoJsBfq+idKE6tbo2fhvoS4g5yh4YeOk1rq
C4Mh9u8I4MdOt5zmQJKnRWKTIrHvIYGTdVh9GgiV7Sanp0vrcw11CXml++ng9Ojs
duRw95XOHVHMdVPDuhhl7aPXII9JE8Adzqs0SDFTljiCEpPVQh/U+e634nxmPlTV
JxFH7WZAnAzU92VKtWS4dkiftYgLrWiNDW1iZissYIpDfvngLRBG3Q53LBCv4Vhx
8vQGfqnhYDl8sngeCFDmyzPRqNzePM0FLloyjse+sHbxfNOruiqglFtNlMNSBb0F
ZmXrf1O5Vzif/7p1YNZBJfUlU0EHAZEOJkaq4uyR+EpMkqcWrSZY+7o6C54zFlpf
C9VBPNuGcQN2R7+b0cY3yWLQAZ7x5yGULmE9chWIrbsgsZuDFqnrsKQx6fDtkJ9T
L5a16XVCVqoz8pG35Ir//+feDlqTpp+EQuAW+BXHdZl04N8rWag0McY/DXvtc+uL
LIu/8f6p13gjFL9C+CbQHHneV9/xelsfhO5wiAEL1D8ZXUgaDKVczdKdE4dpzf8h
QvOnleFIVHw3J7jUFZKg
=aKS+
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processed: tagging 805994

2015-11-24 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 805994 + pending
Bug #805994 [src:apt-setup] apt-setup: FTBFS when built with dpkg-buildpackage 
-A (No such file or directory)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#805994: apt-setup: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

2015-11-24 Thread Santiago Vila 
Package: src:apt-setup
Version: 1:0.102
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   dh_auto_install -i
   dh_install -i
   dh_installdocs -i
   dh_installchangelogs -i
   debian/rules override_dh_installdebconf
make[1]: Entering directory '/<>'
dh_installdebconf
WARNING: se: spurious newline removed
WARNING: se: spurious newline removed
WARNING: se: spurious newline removed
WARNING: se: spurious newline removed
WARNING: se: spurious newline removed
WARNING: se: spurious newline removed
WARNING: se: spurious newline removed
WARNING: se: spurious newline removed
sed -i 's/@MULTIARCH@//' \
debian/apt-setup-udeb/DEBIAN/templates
sed: can't read debian/apt-setup-udeb/DEBIAN/templates: No such file or 
directory
debian/rules:14: recipe for target 'override_dh_installdebconf' failed
make[1]: *** [override_dh_installdebconf] Error 2
make[1]: Leaving directory '/<>'
debian/rules:3: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).

Thanks.