Bug#776037: installation-reports: cant install daily snapshot dont detect intel sata raid no devices listen
Package: installation-reports Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** cant install with daily snapshoot debian-testing-amd64-netinst.iso dont detect intel raid no problems with debian-jessie-DI-b2-amd64-netinst.iso *** End of the template - remove these template lines *** -- Package-specific info: Boot method: usb Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/ 23.01.2015 Date: <23.01.2015 9.30 clock> Machine: self constructed msi bigbang xpower2 with intel 4930k nvidia gtx titan Partitions: DateisystemTyp 1K-BlöckeBenutzt Verfügbar Verw% Eingehängt auf /dev/md125p2 btrfs 3906250009194864 3796539043% / udev devtmpfs 10240 0 102400% /dev tmpfs tmpfs 13205216 9708 131955081% /run tmpfs tmpfs 33013032 20616 329924161% /dev/shm tmpfs tmpfs 5120 4 51161% /run/lock tmpfs tmpfs 33013032 0 330130320% /sys/fs/cgroup /dev/md125p1 vfat 998032184 9978481% /boot/efi /dev/md121p1 btrfs5860526080 685984 58514269441% /Daten /dev/md122 btrfs5860268032 2251104472 3606857224 39% /home tmpfs tmpfs 6602608 2066025881% /run/user/1000 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0] Detect network card:[0 ] Configure network: [0 ] Detect CD: [0 ] Load installer modules: [0 ] Clock/timezone setup: [0 ] User/password setup:[0 ] Detect hard drives: [E ] Partition hard drives: [E ] Install base system:[0 ] Install tasks: [0 ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20141002" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux Eddy 3.16-2-amd64 #1 SMP Debian 3.16.3-2 (2014-09-20) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 DMI2 [8086:0e00] (rev 04) lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7737] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 1a [8086:0e02] (rev 04) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:02.0 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2a [8086:0e04] (rev 04) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3a [8086:0e08] (rev 04) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:05.0 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc [8086:0e28] (rev 04) lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7737] lspci -knn: 00:05.2 System peripheral [0880]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS [8086:0e2a] (rev 04) lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7737] lspci -knn: 00:05.4 PIC [0800]: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC [8086:0e2c] (rev 04) lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7737] lspci -knn: 00:11.0 PCI bridge [0604]: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port [8086:1d3e] (rev 06) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation C600/X79 series chipset MEI Controller #1 [8086:1d3a] (rev 05) lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7737] lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 06) lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7737] lspci -knn: Kernel driver in use: e1000e lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 [8086:1d2d] (rev 06) lspci -knn: Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7737] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: 0
Bug#764677: marked as done (installation-guide: Please use "---" not "--" on installer's kernel command line)
Your message dated Fri, 23 Jan 2015 11:40:47 +0100
with message-id <20150123104047.ga10...@type.bordeaux.inria.fr>
and subject line Re: Bug#762007: Kernel command line handling change breaks d-i
user-params functionality
has caused the Debian Bug report #764677,
regarding installation-guide: Please use "---" not "--" on installer's kernel
command line
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.)
--
764677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer-utils
X-Debbugs-CC: debian-ker...@lists.debian.org
(CCing debian-kernel just FYI, since I don't think this can/should be
fixed with a kernel change, likewise filing against
debian-installer-utils and not the kernel even though a kernel change
introduced the breakage)
A recent change to the kernel[0] (from v3.15 onwards) has changed the
way the kernel handles its command line, such that it now ignores
anything passed after a "--" marker. This has broken d-i's own use of
that marker which was to separate options intended for the installer
only (before the marker) from those which are intended to be both
consumed by the d-i kernel and propagated to the final installation
(after the marker, returned by the user-params utility).
It used to be that you could do:
vmlinuz some/preseed=value -- console=ttyFOO
which would have the dual affect of having the kernel console (and hence
installer UI) run on ttyFOO and also, via grub-installer's use of
user-params, propagate the console=ttyFOO into the final grub config
(similarly for other bootloaders).
With the kernel change this no longer works -- the kernel doesn't put
its console on ttyFOO since it stops parsing at the --. So you get
silence on boot.
To get the old behaviour you need
vmlinuz some/preseed=value console=ttyFOO -- console=ttyFOO
which is pretty tedious.
Just using
vmlinuz some/preseed=value console=ttyFOO
doesn't propagate the console=ttyFOO to the installed system.
Since the kernel change was related to the "systemd abusing kernel
cmdline" debacle I'm not overly keen on raising this upstream and I
don't think that changing the kernel in a way which diverges from
upstream would not be the right approach here.
I don't know how widely used/documented/Supported this ability was, but
I thought e.g. the pxe and isolinux cfgs made use of it.
Not sure what we can do about this. Perhaps choose another separator
("=="?) and make user-params support both?
Ian.
[0]
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=51e158c12aca3c9ac63988611a97c05109b14dc9
--- End Message ---
--- Begin Message ---
Version: 20141230
Ian Campbell, le Fri 10 Oct 2014 08:20:41 +0100, a écrit :
> > As well as this fix I think we need to investigate which of these need
> > fixing too (i.e. with s/--/---/ in appropriate places):
> > * Installation guide
>
> I've assigned clones of this bug to these.
I had actually fixed it in the latest upload, closing the bug.
Samuel--- End Message ---
Re: Bug#776101: aptitude: hangs forever on 'setting up console-setup (1.116)'
Control: reassign -1 console-setup 0.116 Hi, Gordon Morehouse wrote: > running 'aptitude upgrade' followed by 'aptitude update' You mean "running 'aptitude update' followed by 'aptitude upgrade'", don't you? > on a Debian testing system hangs How long did you approximately wait? > after similar output from aptitude: > > Installing new version of config file > /etc/console-setup/compose.ISO-8859-3.inc ... > Installing new version of config file > /etc/console-setup/compose.ISO-8859-4.inc ... > Installing new version of config file > /etc/console-setup/compose.ISO-8859-7.inc ... > Installing new version of config file > /etc/console-setup/compose.ISO-8859-9.inc ... This output is not from aptitude but either from dpkg or ucf. > Setting up console-setup (1.116) ... This is output from dpkg, announcing that it will now run console-setup's postinst script. > 'top' shows aptitude taking about 3-4% CPU but it is stuck. Because aptitude is probably not the one which is working at that time. The one which should do something is either a postinst script from some to-be-installed package or some trigger. But dpkg would have announce triggers. As well as aptitude is mentioning that it's re-reading it's database. Did top show any other child process of aptitude? > Ctrl-C is not effective. Ok. > Kill with SIGTERM does stop the process while breaking terminal > echo. Sure, because it doesn't leave aptitude a chance to do so. IMHO expected behaviour. > It leaves the aptitude /var lockfile dirty. Dito. > Running 'sudo dpkg --configure -a' has a couple errors about > /var/cache/debconf/config.dat being locked as well. This sounds as if the aptitude including its children processes were killed while debconf tried to ask you a question or -- more likely -- generate a config file. I'm quite sure this is no issue with aptitude at all but likely with the postinst script of a to-be-installed package. I currently assume it's console-setup, also because it's a heavy debconf user. Hence reassigning. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- 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/20150123233827.gd26...@sym.noone.org
Processed: Re: Bug#776101: aptitude: hangs forever on 'setting up console-setup (1.116)'
Processing control commands: > reassign -1 console-setup 0.116 Bug #776101 [aptitude] aptitude: hangs forever on 'setting up console-setup (1.116)' Bug reassigned from package 'aptitude' to 'console-setup'. No longer marked as found in versions aptitude/0.6.11-1. Ignoring request to alter fixed versions of bug #776101 to the same values previously set Bug #776101 [console-setup] aptitude: hangs forever on 'setting up console-setup (1.116)' There is no source info for the package 'console-setup' at version '0.116' with architecture '' Unable to make a source version for version '0.116' Marked as found in versions 0.116. -- 776101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776101 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: https://lists.debian.org/handler.s.b776101.1422056314885.transcr...@bugs.debian.org
Bug#773452: killing udhcp helps
> hang in netcfg on IPv6-only At that time, if you switch to a console (Ctrl-Alt-F2) and kill udhcp, the installer happily continues. Not even an error message is given (about udhcp's demise), and the installed system is configured for IPv6-only, as expected. -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- 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/20150124041015.ga16...@angband.pl
