Bug#770231: Amd64-efi installer becomes unresponsive on x86 bios
On Fri, 2014-11-21 at 15:40 -0500, Samuel Comeau wrote: > On November 21, 2014 03:30:13 PM Steve McIntyre wrote: > > [ Re-adding the CC to the bug report ] > > > > On Thu, Nov 20, 2014 at 10:49:42PM -0500, Samuel Comeau wrote: > > >Hello Steve, > > > > > >The intent of the report was that the installer fails "silently", instead > > >of crashing with human readable output. I seem to recall seeing an > > >installer fail with references to incompatible architecture, but that may > > >be faulty memory. > > Right, OK. I'm not sure about that myself... :-) That answers my > > question, too. How about we re-assign this to the kernel package and > > ask about such a message? > > I thought that since there's the installer running, we could put an > architecture check right there, so when you reach the menu, the installer > would already be aware what it's running on. So when the amd64 kernel tries > to > start, it would correctly assume it's trying to run on compatible hardware, > unless the installer prevents it. I'm not sure how that would tie in with the > other installation methods, however, so it may be best to do as you say and > let kernel deal with that. > > > >I understand from your comment that this behaviour is known, but my > > >pre-bug- report-search didn't turn up any relevant results about "amd64 + > > >installer + (hangs OR stalls OR unresponsive) + x86". The results I get > > >are all about boot time, not installation time, unless I misunderstood > > >something very fundamental. In my understanding, when I reach the > > >installer menu, the boot procedure is complete. > > > > Correct - at that point you're in Linux with d-i running. > > That implies that there is some form of kernel running? Obviously not an > amd64 > kernel, if it shows up fine even on x86. Therefore, I assume the arch > specific > kernel gets booted once the user selects an operation to perform. What is the text of the last menu which you get to before the hang? Is there anything written on the screen at the point of the hang? If it is too much text to transcribe then a digital photo of the screen would be ok too. Which model of Xeon are you running on? If you don't know then by pressing cancel/back at the d-i menu you can get to a menu with an option to drop to a shell and from there run "cat /proc/cpuinfo". I'm most interested in the "model name" field. If you aren't getting to a d-i menu at all then there is probably an indication of the processor model in the BIOS screens somewhere. If you are booting to a proper Debian installer menu (i.e. past the initial bootloader menu) then with an amd64 netinst you must be running something which is at least somewhat amd64 capable and not an i?86 only thing, there is nothing other than an amd64 kernel on such an image AFAIK. Which suggests to me that the hang is happening elsewhere later on, perhaps when loading the driver modules, but is not related directly to the processor architecture. Ian. -- 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/1416652312.6331.4.ca...@hellion.org.uk
Bug#770546: installation-report: Mouse not working in graphical install
Package: installation-reports Version: 2.57 Severity: normal Dear Maintainer, I choose graphical install. On subsequent screens mouse is not working: it is just shown in the middle of the screen, but cannot be moved. I attach Xorg.0.log, hardware-summary and syslog files. (Also, be aware that the first line Package: as completed by reportbug contains reports with s, whereas the package name is without s.) Cheers, Eugen -- Package-specific info: Boot method: USB Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd, 21/11/2014 Date: Machine: Lenovo Y50 Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Xorg.0.log.gz Description: GNU Zip compressed data hardware-summary.gz Description: GNU Zip compressed data syslog.gz Description: GNU Zip compressed data
Re: Bug#770078: ifupdown: interfaces(5) falsely claims that interfaces.d is included by default on new installs
Hello, On Tue, 18 Nov 2014 11:15:00 -0700 Peter Karbaliotis wrote: > The interfaces(5) man page claims: > By default, on a freshly installed Debian system, the interfaces > file includes a line to source /etc/network/interfaces.d directory. > but on two new jessie installs there is no 'source-directory > interfaces.d' stanza. I guess this is something that should be done by the Debian installer, as there's a code in package's postinst which installs the correct /etc/network/interfaces file if it doesn't exist, so I guess it's never being run as the file has already been generated. To Debian Installer maintainers: is it something we can fix for Jessie? -- Cheers, Andrew signature.asc Description: PGP signature
Bug#770612: unblock: btrfs-tools/3.17-1.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package btrfs-tools
The upload backports two patches from the upstream 3.17.1 branch, fixing
RC bug #768746 (merged with #769684).
That upload allows packages depending on libbtrfs0 (such as snapper) to build
again.
X-D-CC'ing -boot@ as btrfs-tools produces a udeb, and is currently block-udeb'd.
Guessing the right hint would be:
unblock-udeb btrfs-tools/3.17-1.1
Thanks!
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru btrfs-tools-3.17/debian/changelog btrfs-tools-3.17/debian/changelog
--- btrfs-tools-3.17/debian/changelog 2014-10-23 23:04:25.0 +0200
+++ btrfs-tools-3.17/debian/changelog 2014-11-22 14:52:06.0 +0100
@@ -1,3 +1,13 @@
+btrfs-tools (3.17-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add 0002-Fix-linking-with-libbtrfs.patch from upstream, to properly
+export all the previously exported API (Closes: #768746)
+ * Add 0003-Make-headers-C++-compatible.patch from upstream, making the
+new headers C++-compatible.
+
+ -- Nicolas Dandrimont Sat, 22 Nov 2014 14:52:06 +0100
+
btrfs-tools (3.17-1) unstable; urgency=medium
* New upstream release.
diff -Nru btrfs-tools-3.17/debian/patches/0002-Fix-linking-with-libbtrfs.patch btrfs-tools-3.17/debian/patches/0002-Fix-linking-with-libbtrfs.patch
--- btrfs-tools-3.17/debian/patches/0002-Fix-linking-with-libbtrfs.patch 1970-01-01 01:00:00.0 +0100
+++ btrfs-tools-3.17/debian/patches/0002-Fix-linking-with-libbtrfs.patch 2014-11-15 16:23:00.0 +0100
@@ -0,0 +1,36 @@
+From dcf11c371cbcdca78f297fe042095912634a8323 Mon Sep 17 00:00:00 2001
+From: David Sterba
+Date: Thu, 30 Oct 2014 18:33:41 +0100
+Subject: [PATCH] btrfs-progs: fix linking with libbtrfs
+
+Reported at https://github.com/openSUSE/snapper/issues/128
+
+Commit cdb9e22e292275237c added another rbtree file that defines
+functions that libbtrfs uses.
+
+Signed-off-by: David Sterba
+---
+ Makefile | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/Makefile b/Makefile
+index 9c69ada..203597c 100644
+--- a/Makefile
b/Makefile
+@@ -10,14 +10,14 @@ objects = ctree.o disk-io.o radix-tree.o extent-tree.o print-tree.o \
+ root-tree.o dir-item.o file-item.o inode-item.o inode-map.o \
+ extent-cache.o extent_io.o volumes.o utils.o repair.o \
+ qgroup.o raid6.o free-space-cache.o list_sort.o props.o \
+- ulist.o qgroup-verify.o backref.o rbtree-utils.o
++ ulist.o qgroup-verify.o backref.o
+ cmds_objects = cmds-subvolume.o cmds-filesystem.o cmds-device.o cmds-scrub.o \
+ cmds-inspect.o cmds-balance.o cmds-send.o cmds-receive.o \
+ cmds-quota.o cmds-qgroup.o cmds-replace.o cmds-check.o \
+ cmds-restore.o cmds-rescue.o chunk-recover.o super-recover.o \
+ cmds-property.o
+ libbtrfs_objects = send-stream.o send-utils.o rbtree.o btrfs-list.o crc32c.o \
+- uuid-tree.o utils-lib.o
++ uuid-tree.o utils-lib.o rbtree-utils.o
+ libbtrfs_headers = send-stream.h send-utils.h send.h rbtree.h btrfs-list.h \
+ crc32c.h list.h kerncompat.h radix-tree.h extent-cache.h \
+ extent_io.h ioctl.h ctree.h btrfsck.h version.h
diff -Nru btrfs-tools-3.17/debian/patches/0003-Make-headers-C++-compatible.patch btrfs-tools-3.17/debian/patches/0003-Make-headers-C++-compatible.patch
--- btrfs-tools-3.17/debian/patches/0003-Make-headers-C++-compatible.patch 1970-01-01 01:00:00.0 +0100
+++ btrfs-tools-3.17/debian/patches/0003-Make-headers-C++-compatible.patch 2014-11-15 16:57:02.0 +0100
@@ -0,0 +1,96 @@
+From cafacda441120976105d01c07286e843cb7cbb94 Mon Sep 17 00:00:00 2001
+From: David Sterba
+Date: Mon, 3 Nov 2014 23:50:50 +0100
+Subject: [PATCH] btrfs-progs: libbtrfs, make exported headers compatible with
+ C++
+
+Add externs and don't use a reserved keyword.
+
+Signed-off-by: David Sterba
+---
+ rbtree-utils.h | 8
+ rbtree.h | 10 +-
+ rbtree_augmented.h | 8
+ 3 files changed, 25 insertions(+), 1 deletion(-)
+
+diff --git a/rbtree-utils.h b/rbtree-utils.h
+index 7298c72..718581f 100644
+--- a/rbtree-utils.h
b/rbtree-utils.h
+@@ -21,6 +21,10 @@
+
+ #include "rbtree.h"
+
++#ifdef __cplusplus
++extern "C" {
++#endif
++
+ /* The common insert/search/free functions */
+ typedef int (*rb_compare_nodes)(struct rb_node *node1, struct rb_node *node2);
+ typedef int (*rb_compare_keys)(struct rb_node *node, void *key);
+@@ -42,4 +46,8 @@ static void free_##name##_tree(struct rb_root *root) \
+ rb_free_nodes(root, free_func); \
+ }
+
++#ifdef __cplusplus
++}
++#endif
++
+ #endif
+d
Bug#770635: linux: [armhf/armmp] Add udeb modules to support video and keyboard for imx6
Package: linux Version: 3.16.7-2 Severity: normal Tags: d-i patch Debian-installer hd-media image on armhf doesn't work with the hdmi output and usb keyboard, though these work fine from an installed system. I believe adding the following modules to the fb-modules and usb-modules udebs should allow this to work for hd-media (and possibly netboot as well). I've tested it to work by manually appending these modules to the hd-media initrd, and it seemed to work on both a wandboard quad and cubox-i4pro. I've tried creating an installer image with my custom kernel and udebs to test with greater assurance, using the instructions found at: https://wiki.debian.org/DebianInstaller/Modify/CustomKernel Unfortunately debian-installer seemed to build with the udebs currently shipped in Jessie rather than the locally build udebs, though am unsure if there's an easier way to force it to use the udebs From localudebs. I think it will "just work" once these modules are actually in sid/jessie... diff --git a/installer/armhf/modules/armhf-armmp/fb-modules b/installer/armhf/modules/armhf-armmp/fb-modules new file mode 100644 index 000..29bdd07 --- /dev/null +++ b/installer/armhf/modules/armhf-armmp/fb-modules @@ -0,0 +1,2 @@ +imx-ipuv3-crtc +imx-hdmi diff --git a/installer/armhf/modules/armhf-armmp/usb-modules b/installer/armhf/modules/armhf-armmp/usb-modules index c0f4e1b..38f91fe 100644 --- a/installer/armhf/modules/armhf-armmp/usb-modules +++ b/installer/armhf/modules/armhf-armmp/usb-modules @@ -5,3 +5,4 @@ ohci-exynos ehci-exynos phy-exynos-usb2 ci_hdrc_imx +phy-mxs-usb Thanks for your work! live well, vagrant signature.asc Description: PGP signature
Re: Bug#770525: tasksel: Task selection menu does not have "Go Back" button
Control: reassign -1 tasksel Control: retitle -1 tasksel: Task selection menu does not have "Go Back" button Samuel Thibault, le Sat 22 Nov 2014 02:43:54 +0100, a écrit : > Samuel Thibault, le Sat 22 Nov 2014 02:34:40 +0100, a écrit : > > Package: tasksel > > Oops, sorry, I'm just realizing that in d-i it's called pkgsel. Mmm, but it's really tasksel which is running, reassigning back to tasksel. Samuel -- 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/2014110045.gl12...@type.youpi.perso.aquilenet.fr
Processed: Re: Bug#770525: tasksel: Task selection menu does not have "Go Back" button
Processing control commands: > reassign -1 tasksel Bug #770525 [pkgsel] pkgsel: Task selection menu does not have "Go Back" button Bug reassigned from package 'pkgsel' to 'tasksel'. Ignoring request to alter found versions of bug #770525 to the same values previously set Ignoring request to alter fixed versions of bug #770525 to the same values previously set > retitle -1 tasksel: Task selection menu does not have "Go Back" button Bug #770525 [tasksel] pkgsel: Task selection menu does not have "Go Back" button Changed Bug title to 'tasksel: Task selection menu does not have "Go Back" button' from 'pkgsel: Task selection menu does not have "Go Back" button' -- 770525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770525 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.b770525.14166936528889.transcr...@bugs.debian.org
Bug#769616: tasksel: fails to preseed desktop on kfreebsd, hurd
Samuel Thibault, le Sat 22 Nov 2014 01:57:41 +0100, a écrit : > Steven Chamberlain, le Sat 15 Nov 2014 02:20:53 +, a écrit : > > It was seen on kfreebsd and hurd that preseeding with: > > tasksel tasksel/first multiselect standard, desktop > > tasksel tasksel/desktop multiselect xfce > > no longer works, a regressions since wheezy; no desktop gets installed: > > https://lists.debian.org/debian-hurd/2014/11/msg00074.html > > Indeed, it should now be simply: > > tasksel tasksel/first multiselect standard, xfce-desktop I however fail to preseed this and still let the user choose. We'd need this for accessibility, to enable MATE by default when braille or speech was used. I have tried the following: debconf-set-selections mate-preseed.cfg where mate-pressed.cfg contains: tasksel tasksel/first multiselect standard, mate-desktop, print-server tasksel tasksel/first seen false tasksel tasksel/tasks multiselect standard, mate-desktop, print-server tasksel tasksel/tasks seen false tasksel tasksel/desktop mate tasksel tasksel/desktop seen false After that, debconf-get tasksel/first etc. return the expected values. But when arriving on the task choices, gnome is still the default... and debconf-get tasksel/first etc. have become empty. I guess I am missing something? Samuel -- 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/2014111924.gm12...@type.youpi.perso.aquilenet.fr
Re: Bug#770635: linux: [armhf/armmp] Add udeb modules to support video and keyboard for imx6
On 2014-11-22, Vagrant Cascadian wrote: > Debian-installer hd-media image on armhf doesn't work with the hdmi > output and usb keyboard, though these work fine from an installed > system. > > I believe adding the following modules to the fb-modules and > usb-modules udebs should allow this to work for hd-media (and possibly > netboot as well). ... > Unfortunately debian-installer seemed to build with the udebs > currently shipped in Jessie I figured out a fix for that (was a corner case of localudebs + custom sources.list)... and it works! Please consider applying the patch, which enables console installs on wandboard, cubox-i and probably several other imx6 based devices. live well, vagrant signature.asc Description: PGP signature
Processed: Re: debootstrap: host's /run/shm gets unmounted after debootstrap run
Processing control commands: > notfound -1 1.0.51 Bug #753442 [debootstrap] debootstrap: host's /run/shm gets unmounted after debootstrap run Ignoring request to alter found versions of bug #753442 to the same values previously set -- 753442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753442 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.b753442.141670145620761.transcr...@bugs.debian.org
Bug#753442: debootstrap: host's /run/shm gets unmounted after debootstrap run
Control: notfound -1 1.0.51 Probably a good idea to make BTS aware of when this issue was fixed. Not sure if it should be closed or if an stable update is needed, so I leave it open. -- Happy hacking Petter Reinholdtsen -- 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/2flh9xqhj3m@diskless.uio.no
Bug#770658: fails to debootstrap debian on fedora: Failure trying to run: chroot /debian mount -t proc proc /proc
Package: debootstrap Version: 1.0.64 Severity: normal W: Failure trying to run: chroot /debian mount -t proc proc /proc This is because mount is in a different location in fedora than in debian. On Debian, it's in /bin/mount, while on fedora, /usr/bin/mount. And, on fedora, root's default path does not contain /bin: [root@alien /]# echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin So, chroot tries each of those directories, does not find mount in them in the debian chroot, and fails. Suggested fix: Before chrooting into the debootstrapped chroot to run commands, debootstrap should ensure that the PATH includes all directories it does on a standard debian system. Eg: PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin This way, the host system's chroot etc will still be found whereever it's PATH has them, and the debian system's commands will likewise be found. -- see shy jo signature.asc Description: Digital signature
Bug#770666: partman-base: partman overwrites parts of u-boot (imx6/am335x)
Package: partman-base
Version: 179
Severity: important
Tags: patch
Several armhf platforms have u-boot installed directly to the device
in an area which gets wiped out by partman. This results in
debian-installer producing a "successful" install, but zeros out the
location of the bootloader in the process... so fails to boot.
This was fixed for sunxi/allwinner platforms (see:
https://bugs.debian.org/751704), but other platforms such as imx6
(Wandboard, CuBox-i) and am335x (BeagleBone Black) are still affected
by the issue.
The following proof-of-concept patch may be a little too broad,
affecting all Freescale or AM33XX systems, although it is limited to
installs to /dev/mmcblk0. BeagleBone Black may also need this code
when installing to /dev/mmcblk1...
Essentially it renames the is_sunxi_system to
is_system_with_firmware_on_disk, and adds cases for the additional
platforms.
diff --git a/parted_server.c b/parted_server.c
index 808a85f..e9e72a0 100644
--- a/parted_server.c
+++ b/parted_server.c
@@ -1330,9 +1330,10 @@ command_dump()
oprintf("OK\n");
}
-/* Check whether we are running on a sunxi-based system. */
+/* Check whether we are running on a sunxi-based, freescale-based, or
+ AM33XX (beaglebone black) system. */
int
-is_sunxi_system()
+is_system_with_firmware_on_disk()
{
int cpuinfo_handle;
int result = 0;
@@ -1345,6 +1346,10 @@ is_sunxi_system()
buf[length]='\0';
if (strstr(buf, "Allwinner") != NULL)
result = 1;
+else if (strstr(buf, "Freescale") != NULL)
+result = 1;
+else if (strstr(buf, "AM33XX") != NULL)
+result = 1;
}
close(cpuinfo_handle);
}
@@ -1365,9 +1370,9 @@ command_commit()
* the firmware area, resulting in an unbootable system (see
* bug #751704).
*/
-if (is_sunxi_system() && !strcmp(disk->dev->path, "/dev/mmcblk0")) {
+if (is_system_with_firmware_on_disk() && !strcmp(disk->dev->path,
"/dev/mmcblk0")) {
disk->needs_clobber = 0;
-log("Sunxi platform detected. Disabling ped_disk_clobber " \
+log("Sunxi/Freescale/AM33XX detected. Disabling
ped_disk_clobber" \
"for the boot device %s to protect the firmware " \
"area.", disk->dev->path);
}
Thanks for considering!
live well,
vagrant
signature.asc
Description: PGP signature
Bug#753442: debootstrap: host's /run/shm gets unmounted after debootstrap run
Petter Reinholdtsen (2014-11-23): > Control: notfound -1 1.0.51 > > Probably a good idea to make BTS aware of when this issue was fixed. notfound != fixed. > Not sure if it should be closed or if an stable update is needed, so I > leave it open. Figuring it out is the plan: https://lists.debian.org/20141106161851.ge25...@mraw.org Mraw, KiBi. signature.asc Description: Digital signature
