Bug#788330: marked as done (WG: Debian 8.1 installation on conga-QA3 machine)
Your message dated Tue, 16 Jun 2015 18:12:38 +0200 with message-id 20150616161238.gc23...@gpm.stappers.nl and subject line Re: Bug#788330: problem solved has caused the Debian Bug report #788330, regarding WG: Debian 8.1 installation on conga-QA3 machine 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.) -- 788330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-installer Version: 8.1.0 Dear Maintainer, I try to install debian 8.1 on a conga-QA3 machine. But the Installation hangs. The installation on a before used machine (conga-QA6) could be completed. Here all available information of the failed installation: Package: installation-reports Boot method: net installation from USB-Stick Image version: http://cdimage.debian.org/debian-cd/8.1.0/i386/iso-cd/debian-8.1.0-i386-neti nst.iso Date: 06/10/2015 06:00 Machine: conga-QA3 Processor: Intel ATOM E3815 Memory: 2 GB RAM / 4 GB eMMC Partitions: listing not possible because installation was not complete Partitions definitions during installation /dev/mmcblk0p1 1,5 GB Linux /dev/mmcblk0p2 2,1 GB Extended /dev/mmcblk0p5 673 MB Linux /var /dev/mmcblk0p6 277 MB Linux swap /dev/mmcblk0p7 109 MB Linux /tmp /dev/mmcblk0p8 1,2 GB Linux /home Output of lspci -knn (or lspci -nn): not possible because installation was not complete 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: [E] Install boot loader:[ ] Overall install:[ ] Comments/Problems: The installation hangs on 12 % when installing tasks. Here are the last steps before installation hangs libexpat1 (i386) installiert discover-data (i386) wird konfiguriert libdiscover2 (i386) wird konfiguriert discover (i386) wird konfiguriert discover (i386) installiert Aufruf des Nach-Installation-Triggers libc-bin Ausführen von dpkg After this the system hangs (keyboard without reaction) *** After the installation failed, I have installed the same image on a before used machine. Machine: conga-QA6 Processor: Intel ATOM E640 Memory: 2 GB RAM / 4 GB mSATA This installation could be completed. Mit freundlichen Grüßen / best regards Heino Schäfer ProSign GmbH http://de.wikipedia.org/wiki/Werner_Heisenberg Werner - Heisenberg - Straße 1 D-39106 http://maps.google.de/maps/ms?f=qhl=degeocode=ie=UTF8msa=0msid=1126591 68637196436702.00044839b01c7364882c2ll=52.143939,11.660246spn=0.010653,0.0 19312t=hz=16 Magdeburg Phone: +49 (0)391-56306890 Fax: +49 (0)391-56306899 E-mail: mailto:schae...@pro-sign.de mailto:schae...@pro-sign.de Internet: http://www.pro-sign.de/ http://www.pro-sign.de/ Geschäftsführer: Steffen Mertens Amtsgericht Stendal: HRB 109932 ---End Message--- ---BeginMessage--- On Tue, Jun 16, 2015 at 10:48:30AM +0200, Heino Schäfer wrote: the problem was solved by using the latest BIOS update from congatec. Now the installer can be completed. So closing the bug report. Thanks reporting back. Thanks for your efforts. Enjoy Free Software and other good things in life. Groeten Geert Stappers -- Leven en laten leven---End Message---
Processing of flash-kernel_3.43_armel.changes
flash-kernel_3.43_armel.changes uploaded successfully to ftp-master.debian.org along with the files: flash-kernel_3.43.dsc flash-kernel_3.43.tar.xz flash-kernel-installer_3.43_armel.udeb flash-kernel_3.43_armel.deb Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1z4u9p-0002w7...@coccia.debian.org
Processing of flash-kernel_3.43_armel.changes
flash-kernel_3.43_armel.changes uploaded successfully to localhost along with the files: flash-kernel_3.43.dsc flash-kernel_3.43.tar.xz flash-kernel-installer_3.43_armel.udeb flash-kernel_3.43_armel.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1z4ue6-jh...@franck.debian.org
flash-kernel_3.43_armel.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 16 Jun 2015 06:56:47 +0200 Source: flash-kernel Binary: flash-kernel flash-kernel-installer Architecture: source armel Version: 3.43 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: flash-kernel - utility to make certain embedded devices bootable flash-kernel-installer - Make the system bootable (udeb) Closes: 788782 Changes: flash-kernel (3.43) unstable; urgency=medium . [ Ian Campbell ] * Combine i.MX53 QSB and LOCO board entries, they are the same thing and the LOCO variant was missing DTB information. (Closes: #788782) Checksums-Sha1: a1daec95a04a184e1783054ca059befad0652bbc 1858 flash-kernel_3.43.dsc b77ff3a9b7e95244fddf49440417236c1458a3d9 61256 flash-kernel_3.43.tar.xz 9e4ee56f02d93c7c8c05e8429fb3c2ccce645032 22502 flash-kernel-installer_3.43_armel.udeb 81e1270137ddf6e2efec06c0b46d91090b5fcdb4 36876 flash-kernel_3.43_armel.deb Checksums-Sha256: e43de26a0e4c43823faf455fe9f1f5f99fe4fad7144ae38b958d90dbd37c4da0 1858 flash-kernel_3.43.dsc 1743c75163315302aaba1e7233bfb7ad91e7699fd9d8c4eda80d3a2cdee236b8 61256 flash-kernel_3.43.tar.xz 29ded19170ba8059d5ac3ac77ed82f9607452e01d88aee639f82ce94c6242b64 22502 flash-kernel-installer_3.43_armel.udeb 238d06ac5bc78d25baf3a8295c0556c282948b2afb84bc457292defd99e7354f 36876 flash-kernel_3.43_armel.deb Files: 6d4880aea9a6c69738082e64d93f49eb 1858 utils optional flash-kernel_3.43.dsc d07ffa582832711b82f0e3ffd515dc6a 61256 utils optional flash-kernel_3.43.tar.xz 66a59de74de5daf29456405aa1a75596 22502 debian-installer standard flash-kernel-installer_3.43_armel.udeb b400acbdaea0142e96617fa41c9ef813 36876 utils optional flash-kernel_3.43_armel.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVgFRtAAoJEIcvcCxNbiWo3RwP/3wgkfJDup6t3zGXFcRnKCQr 9qGYuD24IKT3UZKOYWZHvwanYeZLODfaPcTQ/ihAuQl1hpchwy/4a3YEGgsNO3Dg WleTF6oIpCdbEoD5kyUsERL3YJBXiDbjPtngjXiSioO+sFg/YXEb51p7sSr8v5Hr wbwwSmmm3cFNgF6XX82G5WiPFlo50uBsTYpyU47KqmhT/CluObT9yDk77ht+K5ze SCD8Vc191OJb6G/8RYtZkzL6hZmPUW6pPezJCbJOGuJzMZkLDlQxuEHFn0HapFta Rn6vbrJu4q0tk49TcwyrWgOJiuG+mnk0mwuEvxe686dYHYxpN5tBqSo2Xmxh7qVj eIvScvUDPhn72uoLFZecUnc0j3/rUcVG68CJaOyysNj2DMQeLzxhfGFnZb9lWFUR vI/ShJjuHdcBzGUlFOa8d9C15tAHEOG0v2dMPX+ErbxNb/v8wKv0sfHJHcfQKdy2 cY3MYcbUeKVgYNtjmqxjbUS9x2oouXsXZq5C2YFiId7zXgZvsGvkYeHj+qT4r9EZ 2MzGVPlYPp5Y6JDE0+jNep5dA3Tqsb42P5lm+52fU2qhOQhIaI5vK2K5elQB0fqP /O6xaSuyc//y3sbH11hKLNEXg+daRuNATVh+MGqCdomZanQHyApy60IFRqqbC1p/ U+RaJw74i+Aqk5OB14Dz =XUsP -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1z4uzo-0006rt...@franck.debian.org
Bug#787794: lifimage fails to successfully boot on hppa
In this case you could try to add to the kernel command line (at the IPL prompt) one (or both) of: hp_sdc.blacklist=yes hp_sdc.no_hpsdc=1 Awesome! hp_sdc.no_hpsdc=1 does the trick. Thanks much for the great help! Great, but I still think blacklisting the machine in the driver is the better way :-) Helge -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55809922.6030...@gmx.de
Bug#788782: marked as done (Need to add DTB settings for non-DTB Freescale MX53 LOCO Board too)
Your message dated Tue, 16 Jun 2015 17:23:08 + with message-id e1z4uzo-0006rf...@franck.debian.org and subject line Bug#788782: fixed in flash-kernel 3.43 has caused the Debian Bug report #788782, regarding Need to add DTB settings for non-DTB Freescale MX53 LOCO Board too 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.) -- 788782: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flash-kernel Version: 3.35 Severity: important Looking at the settings for the two different stanzas for imx53, they're quite different for no good reason that I can see: Machine: Freescale i.MX53 Quick Start Board Kernel-Flavors: armmp DTB-Id: imx53-qsb.dtb DTB-Append-From: 3.12 Boot-DTB-Path: /boot/dtb U-Boot-Kernel-Address: 0x70008000 U-Boot-Initrd-Address: 0x0 Boot-Kernel-Path: /boot/uImage Boot-Initrd-Path: /boot/uInitrd Required-Packages: u-boot-tools Bootloader-Sets-Incorrect-Root: no Machine: Freescale MX53 LOCO Board Kernel-Flavors: armmp mx5 U-Boot-Kernel-Address: 0x70008000 U-Boot-Initrd-Address: 0x0 Boot-Kernel-Path: /boot/uImage Boot-Initrd-Path: /boot/uInitrd Required-Packages: u-boot-tools The second one is the settings that will be used when *running* on a non-DTB kernel, even when installing a newer DTB-using kernel. This is exactly the setup that will happen when upgrading a machine from Wheezy to Jessie, for example, and will lead to machines not being bootable after the upgrade! The obvious fix is to clone the settings from the first stanza here to the second. It's also worth checking any *other* supported machine types for the same bug. This also *really* needs to be back-ported to stable! -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: flash-kernel Source-Version: 3.43 We believe that the bug you reported is fixed in the latest version of flash-kernel, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 788...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Perrier bubu...@debian.org (supplier of updated flash-kernel package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 16 Jun 2015 06:56:47 +0200 Source: flash-kernel Binary: flash-kernel flash-kernel-installer Architecture: source armel Version: 3.43 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: flash-kernel - utility to make certain embedded devices bootable flash-kernel-installer - Make the system bootable (udeb) Closes: 788782 Changes: flash-kernel (3.43) unstable; urgency=medium . [ Ian Campbell ] * Combine i.MX53 QSB and LOCO board entries, they are the same thing and the LOCO variant was missing DTB information. (Closes: #788782) Checksums-Sha1: a1daec95a04a184e1783054ca059befad0652bbc 1858 flash-kernel_3.43.dsc b77ff3a9b7e95244fddf49440417236c1458a3d9 61256 flash-kernel_3.43.tar.xz 9e4ee56f02d93c7c8c05e8429fb3c2ccce645032 22502 flash-kernel-installer_3.43_armel.udeb 81e1270137ddf6e2efec06c0b46d91090b5fcdb4 36876 flash-kernel_3.43_armel.deb Checksums-Sha256: e43de26a0e4c43823faf455fe9f1f5f99fe4fad7144ae38b958d90dbd37c4da0 1858 flash-kernel_3.43.dsc 1743c75163315302aaba1e7233bfb7ad91e7699fd9d8c4eda80d3a2cdee236b8 61256 flash-kernel_3.43.tar.xz 29ded19170ba8059d5ac3ac77ed82f9607452e01d88aee639f82ce94c6242b64 22502 flash-kernel-installer_3.43_armel.udeb 238d06ac5bc78d25baf3a8295c0556c282948b2afb84bc457292defd99e7354f 36876 flash-kernel_3.43_armel.deb Files: 6d4880aea9a6c69738082e64d93f49eb 1858 utils optional flash-kernel_3.43.dsc d07ffa582832711b82f0e3ffd515dc6a 61256 utils optional flash-kernel_3.43.tar.xz 66a59de74de5daf29456405aa1a75596 22502 debian-installer standard
Bug#787794: lifimage fails to successfully boot on hppa
Helge Deller del...@gmx.de: Hi Alex, Hi Helge Anyway, please let me know if you're going to make no_hpsdc=1 parameter work some way. The debian installer allows you to set such values on the kernel command line: modulename.blacklist=yesor modulename.parametername=value In this case you could try to add to the kernel command line (at the IPL prompt) one (or both) of: hp_sdc.blacklist=yes hp_sdc.no_hpsdc=1 Awesome! hp_sdc.no_hpsdc=1 does the trick. Thanks much for the great help! -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/canoehn9pcc2gxqw31+pcsz-aqqatghox03xcf9c_8pikrqz...@mail.gmail.com
Bug#787794: lifimage fails to successfully boot on hppa
Hi Alex, Anyway, please let me know if you're going to make no_hpsdc=1 parameter work some way. The debian installer allows you to set such values on the kernel command line: modulename.blacklist=yesor modulename.parametername=value In this case you could try to add to the kernel command line (at the IPL prompt) one (or both) of: hp_sdc.blacklist=yes hp_sdc.no_hpsdc=1 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/558077f3.9000...@gmx.de
Bug#788330: problem solved
Package: debian-installer Version: 8.1.0 Dear Maintainer, the problem was solved by using the latest BIOS update from congatec. Now the installer can be completed. Thanks for your efforts. Mit freundlichen Grüßen / best regards Heino Schäfer ProSign GmbH Werner - Heisenberg http://de.wikipedia.org/wiki/Werner_Heisenberg - Straße 1 D-39106 Magdeburg http://maps.google.de/maps/ms?f=qhl=degeocode=ie=UTF8msa=0msid=1126591 68637196436702.00044839b01c7364882c2ll=52.143939,11.660246spn=0.010653,0.0 19312t=hz=16 Phone: +49 (0)391-56306890 Fax: +49 (0)391-56306899 E-mail: mailto:schae...@pro-sign.de Internet: http://www.pro-sign.de/ Geschäftsführer: Steffen Mertens Amtsgericht Stendal: HRB 109932
Re: Bug#788634: debian-installer: Accepting a preseed URL from DHCP allows attacker to hijack installation
On Sun, Jun 14, 2015 at 04:48:20PM +0200, Geert Stappers wrote: control: tag -1 mordac I don't think handwaving and tagging wontfix is the right play here. Now tagging with 'mordac'. For those new to Mordac, get a first impression at http://dilbert.com/strip/2007-11-16 And http://dilbert.com/search_results?terms=Mordac for a complete overview of Mordac, the preventer of information services. In other words: How to cope with nonsense like security is more important than usability? It's not nonsense. Yes, if you boot off PXE, then it's fine if the network contains preseeding data. After all, you booted off PXE, so either your network is fine (and nothing to worry about) or it isn't (and then using a preseeding file off the network isn't going to make matters much worse, since you've already *booted* untrusted code). But if you boot off CD-ROM or USB or some such? Then the situation is much different. While I agree that having preseeding in that case can be useful, I can also understand the POV that the system *defaulting* to using such a preseed file is a bad idea. Let's say you buy a new laptop, take it out of the packaging while on the train home, pop in a USB stick with d-i on it, and boot. Somewhere on the way home, your train waits in a train station for a few minutes, during which time it picks up the wireless connection and does DHCP there. Should it trust any preseeding data that it got from that connection? I don't think so, but currently this *does* happen. -- It is easy to love a country that is famous for chocolate and beer -- Barack Obama, speaking in Brussels, Belgium, 2014-03-26 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150616093756.gb30...@grep.be
