Processed (with 1 errors): Re: Bug#703146: apt: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze)?
Processing control commands:
found -1 1.0.44
Bug #703146 {Done: Christian Perrier bubu...@debian.org} [debootstrap] apt:
BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze)?
Marked as found in versions debootstrap/1.0.44.
severity serious
Unknown command or malformed arguments to command.
--
703146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703146
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.b703146.1364288476307.transcr...@bugs.debian.org
Bug#703146: apt: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze)?
Control: found -1 1.0.44 Control: severity serious I hit this bug yesterday ... and think that this should be RC if debootstrap/wheezy cannot produce a working chroot environment. Andreas -- 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/515163d9.2080...@debian.org
Processed: tagging 668728, tagging 679590, severity of 703146 is serious
Processing commands for cont...@bugs.debian.org:
tags 668728 - moreinfo
Bug #668728 [aolserver4-daemon] aolserver4-daemon: unowned files after purge
(policy 6.8, 10.8): /etc/default/aolserver4
Removed tag(s) moreinfo.
tags 679590 + pending
Bug #679590 [binkd] binkd: fails to purge: rmdir: failed to remove
`/var/log/binkd/': No such file or directory
Added tag(s) pending.
severity 703146 serious
Bug #703146 {Done: Christian Perrier bubu...@debian.org} [debootstrap] apt:
BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze)?
Severity set to 'serious' from 'important'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
668728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668728
679590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679590
703146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703146
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.13642891154823.transcr...@bugs.debian.org
Bug#703747: netcfg: preseed netcfg: confusion or regression about disable_dhcp, disable_autoconfig and use_autoconfig
Le 2013-03-26 02:11, Samuel Thibault a écrit : I have uploaded a fixed version on: http://dept-info.labri.fr/~thibault/tmp/mini.iso Could you check that just netcfg/disable_autoconfig=true works for you too? The uploaded iso image is for amd64 computers; but I only own a i386 PC. So, I can't check it, sorry. Not a problem, now it's an i386 image, please try :) OK. I have tried with: 1. Nothing - DHCP autoconfig 2. netcfg/disable_autoconfig=true (on boot cmdline) - prompt for static IP configuration 3. netcfg/disable_dhcp=true (on bootcmdline): - prompt for static IP configuration 4. In /preseed.cfg (into the initrd): d-i netcfg/disable_autoconfig boolean true - prompt for static IP configuration 5. In /preseed.cfg (into the initrd): d-i netcfg/disable_dhcp boolean true - prompt for static IP configuration Nice. For me, this bug can be closed now. Thanks, quidame -- 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/be4313104cc433cffc467b30ba91d...@poivron.org
Bug#703747: netcfg: preseed netcfg: confusion or regression about disable_dhcp, disable_autoconfig and use_autoconfig
Thanks for testing, the bug will be closed on upload :) Samuel -- 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/20130326094648.gc6...@type.bordeaux.inria.fr
Bug#703979: Cleanup after install wipes /target if umount failed (e.g. shell open in /target)
Package: debian-installer-launcher Version: 15 Severity: grave If umount is prevented for any reason, such as the user opening a shell in /lib/live/installer/target and then leaving it open, while exiting the installer, then the cleanup of /lib/live/installer after the install will remove the /target! It will also do damage to any bind-mounted filesystems under /lib/live/installer, (e.g. /lib/live/installer/dev), causing harm to the running live system. If any of the 'umount -f' commands performed in plugins/live fails in the cleanup after the installer exits, it should be considered fatal and no further cleanup should be attempted, or at the very least the cleanup needs to not cross filesystems so that nothing but the installer itself is removed. Thanks go to Kragen Javier Sitaker, who worked with me on irc to help identify this problem. He initially found it using one of our 6.0.7 images, so the bug is probably present in all existing versions of debian-installer-launcher. Ben -- 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/20130326132307.1893.34207.report...@lear.nslug.ns.ca
Bug#703995: apt-setup: preseeding apt-setup/multiarch breaks dpkg
Package: apt-setup Version: 0.77 Severity: normal Tags: patch I wanted to try out preseeding apt-setup/multiarch to i386 but before doing it, I reviewed apt-setup's handling of this option and I discovered that it actually creates the configuration file used by the early Ubuntu implementation of multiarch (which relied on the --foreign-architecture command line option instead of the single dpkg --add-architecture call). This means that it actually breaks dpkg since the current version of dpkg doesn't underestand the --foreign-architecture command-line option. Here's an untested patch: --- a/generators/01setup +++ b/generators/01setup @@ -17,8 +17,7 @@ fi db_get apt-setup/multiarch if [ $RET ]; then - mkdir -p $ROOT/etc/dpkg/dpkg.cfg.d for arch in $RET; do - echo foreign-architecture $arch - done $ROOT/etc/dpkg/dpkg.cfg.d/multiarch + chroot $ROOT dpkg --add-architecture $arch + done fi IMO it would be nice to have this fixed in wheezy but it's not required either. Cheers, -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-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 -- 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/20130326154609.1179.83517.report...@x230-buxy.home.ouaza.com
Bug#703146: Better debootstrap InRelease handling fix
Hi,
Pulling gnupg just to extract the cleartext of a PGP signed message
seems a bit too much for me. I stumbled upon this while in
debian-installer, which didn't depend on gnupg, only pgpv, until now.
This looks really overkill. Please find attached a better fix, to me,
only using sed (and compatible with the minimal busybox sed found in
d-i). It should extract anything according to RFC 4880 cleartext signed
message format, according to my reading of it.
I don't reopen this bug as I don't know what is the policy about it
currently, but really consider my solution, please.
Regards,
--
Benjamin Cama benjamin.c...@telecom-bretagne.eu
From 169cffe3c20f36947a1604a6e1151d0f31e18de2 Mon Sep 17 00:00:00 2001
From: Benjamin Cama benjamin.c...@telecom-bretagne.eu
Date: Tue, 26 Mar 2013 18:08:32 +0100
Subject: [PATCH] Remove dependency on gnupg, extract Release with sed
Get back gnupg to Recommends, as it is only used to extract the clear
text. We can rather do that with sed, furthermore in constrained
environments like in d-i. Should be compatible with RFC 4880 format.
Signed-off-by: Benjamin Cama benjamin.c...@telecom-bretagne.eu
---
debian/control |4 ++--
functions |9 +++--
2 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/debian/control b/debian/control
index 41af2df..0894e08 100644
--- a/debian/control
+++ b/debian/control
@@ -10,8 +10,8 @@ Vcs-Git: git://git.debian.org/d-i/debootstrap.git
Package: debootstrap
Architecture: all
-Depends: ${misc:Depends}, wget, gnupg
-Recommends: ${keyring}
+Depends: ${misc:Depends}, wget
+Recommends: gnupg, ${keyring}
Description: Bootstrap a basic Debian system
debootstrap is used to create a Debian base system from scratch,
without requiring the availability of dpkg or apt. It does this by
diff --git a/functions b/functions
index 1dc0f87..f44 100644
--- a/functions
+++ b/functions
@@ -530,8 +530,13 @@ download_release_sig () {
warning KEYRING Cannot check Release signature; keyring file not available %s $KEYRING_WANTED
fi
if [ $release_file_variant = IN ]; then
- rm -f $reldest
-gpg --output $reldest --decrypt --keyring $KEYRING --ignore-time-conflict $relsigdest
+ sed -n '/^-BEGIN PGP SIGNED MESSAGE-$/ { \
+n \
+: check_hash /^Hash:/ { n b check_hash } \
+n # blank line \
+ } \
+ /^-BEGIN PGP SIGNATURE-$/ q \
+ p' $relsigdest $reldest
fi
}
--
1.7.2.5
Bug#703146: Better debootstrap InRelease handling fix
Quoting Benjamin Cama (benjamin.c...@telecom-bretagne.eu): Hi, Pulling gnupg just to extract the cleartext of a PGP signed message seems a bit too much for me. I stumbled upon this while in debian-installer, which didn't depend on gnupg, only pgpv, until now. This looks really overkill. Please find attached a better fix, to me, only using sed (and compatible with the minimal busybox sed found in d-i). It should extract anything according to RFC 4880 cleartext signed message format, according to my reading of it. I don't reopen this bug as I don't know what is the policy about it currently, but really consider my solution, please. Thanks for your input. Julien Cristau recently committed another fix, that drops the supprot of InRelease files, in d-i, with the same reslt of turning gpg back into a Recommends. We now need to get this into wheezy, indeed. signature.asc Description: Digital signature
Anfrage
zu preseed.txt und partitonieren, gibt es jemand, der mit helfen kann? -- 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/5151f8e4.3080...@vienna.at
Re: Anfrage
Hi, Soos Arpad q...@vienna.at wrote: zu preseed.txt und partitonieren, gibt es jemand, der mit helfen kann? on this list, the used language is English. If you are uncomfortable with English, use debian-user-ger...@lists.debian.org (auf dieser Liste wird Englisch gesprochen. Falls du mit Englisch Probleme hast, schreibe auf debian-user-ger...@lists.debian.org ). Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 3.0.2 under D e b i a n G N U / L I N U X 6.0 ( S q u e e z e ) Registered LinuxUser #311290 - http://linuxcounter.net/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- 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/20130326211413.8add50ad.li...@wansing-online.de
Bug#703469: HP EliteBook 8570p UEFI install works, with some effort
I managed to get the USB storage working, so that I could grab the lspci output. 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) Subsystem: Hewlett-Packard Company Device [103c:17a7] 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:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) Subsystem: Hewlett-Packard Company Device [103c:17a7] 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: Hewlett-Packard Company Device [103c:17a7] 00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller [8086:1e3d] (rev 04) Subsystem: Hewlett-Packard Company Device [103c:17a7] Kernel driver in use: serial 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) Subsystem: Hewlett-Packard Company Device [103c:17a7] Kernel driver in use: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) Subsystem: Hewlett-Packard Company Device [103c:17a7] 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: Hewlett-Packard Company Device [103c:17a7] 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.2 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 [8086:1e14] (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: Hewlett-Packard Company Device [103c:17a7] Kernel driver in use: ehci_hcd 00:1f.0 ISA bridge [0601]: Intel Corporation QM77 Express Chipset LPC Controller [8086:1e55] (rev 04) Subsystem: Hewlett-Packard Company Device [103c:17a7] 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04) Subsystem: Hewlett-Packard Company Device [103c:17a7] Kernel driver in use: ahci 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Thames [Radeon 7500M/7600M Series] [1002:6841] Subsystem: Hewlett-Packard Company Device [103c:17a9] Kernel driver in use: radeon 01:00.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Turks/Whistler HDMI Audio [Radeon HD 6000 Series] [1002:aa90] Subsystem: Hewlett-Packard Company Device [103c:17a9] Kernel driver in use: snd_hda_intel 24:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:17a7] Kernel driver in use: firewire_ohci 24:00.1 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host Controller [197b:2392] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:17a7] Kernel driver in use: sdhci-pci 24:00.2 SD Host controller [0805]: JMicron Technology Corp. Standard SD Host Controller [197b:2391] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:17a7] 25:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0082] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6205 AGN [8086:1301] Kernel driver in use: iwlwifi
Bug#703470: UEFI USB stick installation fails on HP EliteBook 8570p
Control: retitle -1 UEFI USB stick installation fails to detect its media on a USB 3.0 port As mentioned in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703469 , I was able to install by booting without EFI. While having problems getting that system to recognize a USB stick that I plugged in, it occurred to me that I was using one of the USB 3.0 ports. A USB 2.0 port recognizes the device. Applying the same idea to this bug, I got the d-i to work just as well in EFI mode on a USB 2.0 port. I booted the existing system by choosing F9 Boot Device Options from the Startup Menu, then External USB Hard Drive (as opposed to USB Hard Drive 1 - ...). I stopped after configuring the network, since I don't want to destroy the system I've already installed. So the remaining issue is that the d-i doesn't find the installation media in a USB 3.0 port. -- 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/20130326214131.ga24...@64-142-29-25.dsl.static.sonic.net
Processed: Re: UEFI USB stick installation fails on HP EliteBook 8570p
Processing control commands: retitle -1 UEFI USB stick installation fails to detect its media on a USB 3.0 port Bug #703470 [installation-reports] UEFI USB stick installation fails on HP EliteBook 8570p Changed Bug title to 'UEFI USB stick installation fails to detect its media on a USB 3.0 port' from 'UEFI USB stick installation fails on HP EliteBook 8570p' -- 703470: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703470 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.b703470.136433582211699.transcr...@bugs.debian.org
Bug#703979: Available person to review/pull my fix for #703979?
I'm in Uploaders now, so technically I could just upload my (fully tested) fix. I'd appreciate, however, a review pull before I do. See: git clone http://syn.theti.ca/git/debian-installer-launcher.git gitweb: http://syn.theti.ca/gitweb/?p=debian-installer-launcher.git Thanks, Ben -- 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/51521724.1080...@sanctuary.nslug.ns.ca
Bug#703979: Available person to review/pull my fix for #703979?
On Tue, Mar 26, 2013 at 06:46:12PM -0300, Ben Armstrong wrote: git clone http://syn.theti.ca/git/debian-installer-launcher.git gitweb: http://syn.theti.ca/gitweb/?p=debian-installer-launcher.git This does one change to restrict rm to one filesyste. The second, replace umount -f with umount -l, is a no-op after that. Please fix this completely, with something like: - mount -t tmpfs none /lib/live/installer - umount /lib/live/installer Bastian -- I object to intellect without discipline; I object to power without constructive purpose. -- Spock, The Squire of Gothos, stardate 2124.5 -- 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/20130326233018.gb9...@waldi.eu.org
Bug#703146: Better debootstrap InRelease handling fix
* Benjamin Cama benjamin.c...@telecom-bretagne.eu [130326 18:33]:
index 1dc0f87..f44 100644
--- a/functions
+++ b/functions
@@ -530,8 +530,13 @@ download_release_sig () {
warning KEYRING Cannot check Release signature; keyring file
not available %s $KEYRING_WANTED
fi
if [ $release_file_variant = IN ]; then
- rm -f $reldest
-gpg --output $reldest --decrypt --keyring $KEYRING
--ignore-time-conflict $relsigdest
+ sed -n '/^-BEGIN PGP SIGNED MESSAGE-$/ { \
+ n \
+ : check_hash /^Hash:/ { n b check_hash } \
+ n # blank line \
+ } \
+ /^-BEGIN PGP SIGNATURE-$/ q \
+ p' $relsigdest $reldest
fi
}
Sorry, but this is not enough to properly extract the contents of a
inline signed message. You still need to do possible unescaping between
those lines.
Bernhard R. Link
--
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/20130326235344.ga5...@client.brlink.eu
Re: Is it a bad URL in the installation manual?
Yes, http://luks.endorphin.org/ is a bad URL. On 3/26/13, Regid Ichira regi...@nt1.in wrote: http://www.debian.org/releases/stable/i386/ch06s03.html.en#ftn.id593125 maps LUKS to http://luks.endorphin.org/ . $ host luks.endorphin.org Host luks.endorphin.org not found: 3(NXDOMAIN) Is http://en.wikipedia.org/wiki/LUKS a better mapping? -- 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/20130326032006.ga7...@nt1.in -- 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/cak-ixgxb7bxb4zosrycfdrvzjkkk1rqvvtzu_mdg9yxb+to...@mail.gmail.com
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:kfreebsd-amd64 Mar 25 00:50 buildd@fano build_cdrom_grub http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_grub.log * OLD BUILD:kfreebsd-amd64 Mar 25 00:51 buildd@fano build_cdrom_gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_gtk.log * OLD BUILD:kfreebsd-amd64 Mar 25 00:54 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * OLD BUILD:kfreebsd-amd64 Mar 25 00:57 buildd@fano build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-9.log Totals: 100 builds (0 failed, 4 old) -- 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/e1ukeii-0003ey...@ravel.debian.org
Bug#703470: UEFI USB stick installation fails on HP EliteBook 8570p
On Tue, 2013-03-26 at 21:41 +, Mike wrote: Control: retitle -1 UEFI USB stick installation fails to detect its media on a USB 3.0 port As mentioned in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703469 , I was able to install by booting without EFI. While having problems getting that system to recognize a USB stick that I plugged in, it occurred to me that I was using one of the USB 3.0 ports. A USB 2.0 port recognizes the device. Applying the same idea to this bug, I got the d-i to work just as well in EFI mode on a USB 2.0 port. I booted the existing system by choosing F9 Boot Device Options from the Startup Menu, then External USB Hard Drive (as opposed to USB Hard Drive 1 - ...). I stopped after configuring the network, since I don't want to destroy the system I've already installed. So the remaining issue is that the d-i doesn't find the installation media in a USB 3.0 port. The installer certainly includes the xHCI (USB 3.0 controller) driver. However, the lspci output you attached to #703469 shows that the xHCI does not have a driver bound to it. Perhaps the kernel log (from dmesg) would explain why. Ben. -- Ben Hutchings I'm not a reverse psychological virus. Please don't copy me into your sig. signature.asc Description: This is a digitally signed message part
Bug#700918: Just tried it again..
Tried it again still no dice. Ubuntu 12.10 boots fine. installed ok but I'd rather be running debian.. UEFI boot on lenovo x230 secureboot is off. -- 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/caccktow2kr48pyx9gzvx0hevnuom4ptz70grb7nw9iwevgh...@mail.gmail.com
Bug#703469: HP EliteBook 8570p UEFI install works, with some effort
dmesg output truncated after the USB stuff. There are two USB 2.0, one USB 2.0/eSATA, and two USB 3.0 ports on the hardware. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.39-2 [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/laptop-root ro quiet [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 000a (usable) [0.00] BIOS-e820: 0010 - bdcf3000 (usable) [0.00] BIOS-e820: bdcf3000 - beebc000 (reserved) [0.00] BIOS-e820: beebc000 - befbc000 (ACPI NVS) [0.00] BIOS-e820: befbc000 - befff000 (ACPI data) [0.00] BIOS-e820: befff000 - bf00 (usable) [0.00] BIOS-e820: e00f8000 - e00f9000 (reserved) [0.00] BIOS-e820: fed1c000 - fed2 (reserved) [0.00] BIOS-e820: ffee - ffeff000 (reserved) [0.00] BIOS-e820: 0001 - 00013e00 (usable) [0.00] NX (Execute Disable) protection: active [0.00] EFI v2.10 by HPQ [0.00] ACPI=0xbeffe000 ACPI 2.0=0xbeffe014 SMBIOS=0xbe56b698 [0.00] Kernel-defined memdesc doesn't match the one from EFI! [0.00] EFI: mem00: type=3, attr=0xf, range=[0x-0x1000) (0MB) [0.00] EFI: mem01: type=7, attr=0xf, range=[0x1000-0x00058000) (0MB) [0.00] EFI: mem02: type=4, attr=0xf, range=[0x00058000-0x00059000) (0MB) [0.00] EFI: mem03: type=7, attr=0xf, range=[0x00059000-0x0007d000) (0MB) [0.00] EFI: mem04: type=4, attr=0xf, range=[0x0007d000-0x0007e000) (0MB) [0.00] EFI: mem05: type=3, attr=0xf, range=[0x0007e000-0x000a) (0MB) [0.00] EFI: mem06: type=2, attr=0xf, range=[0x0010-0x003b) (2MB) [0.00] EFI: mem07: type=7, attr=0xf, range=[0x003b-0x00c0) (8MB) [0.00] EFI: mem08: type=3, attr=0xf, range=[0x00c0-0x0100) (4MB) [0.00] EFI: mem09: type=7, attr=0xf, range=[0x0100-0x36958000) (857MB) [0.00] EFI: mem10: type=2, attr=0xf, range=[0x36958000-0x374a4000) (11MB) [0.00] EFI: mem11: type=7, attr=0xf, range=[0x374a4000-0x88ddc000) (1305MB) [0.00] EFI: mem12: type=2, attr=0xf, range=[0x88ddc000-0xb6cf4000) (735MB) [0.00] EFI: mem13: type=4, attr=0xf, range=[0xb6cf4000-0xb6d14000) (0MB) [0.00] EFI: mem14: type=7, attr=0xf, range=[0xb6d14000-0xb80be000) (19MB) [0.00] EFI: mem15: type=1, attr=0xf, range=[0xb80be000-0xb80db000) (0MB) [0.00] EFI: mem16: type=3, attr=0xf, range=[0xb80db000-0xb8604000) (5MB) [0.00] EFI: mem17: type=4, attr=0xf, range=[0xb8604000-0xb9ce4000) (22MB) [0.00] EFI: mem18: type=3, attr=0xf, range=[0xb9ce4000-0xb9cf3000) (0MB) [0.00] EFI: mem19: type=7, attr=0xf, range=[0xb9cf3000-0xb9da) (0MB) [0.00] EFI: mem20: type=4, attr=0xf, range=[0xb9da-0xba6e4000) (9MB) [0.00] EFI: mem21: type=7, attr=0xf, range=[0xba6e4000-0xba6e5000) (0MB) [0.00] EFI: mem22: type=4, attr=0xf, range=[0xba6e5000-0xba736000) (0MB) [0.00] EFI: mem23: type=7, attr=0xf, range=[0xba736000-0xba737000) (0MB) [0.00] EFI: mem24: type=4, attr=0xf, range=[0xba737000-0xbbdce000) (22MB) [0.00] EFI: mem25: type=7, attr=0xf, range=[0xbbdce000-0xbbdd8000) (0MB) [0.00] EFI: mem26: type=2, attr=0xf, range=[0xbbdd8000-0xbbdde000) (0MB) [0.00] EFI: mem27: type=4, attr=0xf, range=[0xbbdde000-0xbbddf000) (0MB) [0.00] EFI: mem28: type=7, attr=0xf, range=[0xbbddf000-0xbbde1000) (0MB) [0.00] EFI: mem29: type=4, attr=0xf, range=[0xbbde1000-0xbbde4000) (0MB) [0.00] EFI: mem30: type=7, attr=0xf, range=[0xbbde4000-0xbbde7000) (0MB) [0.00] EFI: mem31: type=4, attr=0xf, range=[0xbbde7000-0xbbe04000) (0MB) [0.00] EFI: mem32: type=7, attr=0xf, range=[0xbbe04000-0xbbe06000) (0MB) [0.00] EFI: mem33: type=4, attr=0xf, range=[0xbbe06000-0xbbecb000) (0MB) [0.00] EFI: mem34: type=7, attr=0xf, range=[0xbbecb000-0xbbecc000) (0MB) [0.00] EFI: mem35: type=4, attr=0xf,
Bug#703470: UEFI USB stick installation fails on HP EliteBook 8570p
Ben Hutchings wrote: However, the lspci output you attached to #703469 shows that the xHCI does not have a driver bound to it. Perhaps the kernel log (from dmesg) would explain why. Thanks Ben. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703469#25 request interrupt 255 failed? That's the dmesg output from the running (non-Xen, that's another bug) system, not from the UEFI d-i. -- 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/20130327042309.gb25...@64-142-29-25.dsl.static.sonic.net
Bug#703470: UEFI USB stick installation fails on HP EliteBook 8570p
On Wed, 2013-03-27 at 04:23 +, Mike wrote:
Ben Hutchings wrote:
However, the lspci output you attached to #703469 shows that the xHCI
does not have a driver bound to it. Perhaps the kernel log (from
dmesg) would explain why.
Thanks Ben. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703469#25
request interrupt 255 failed?
That's the dmesg output from the running (non-Xen, that's another bug)
system, not from the UEFI d-i.
I think that *might* be fixed by:
commit ec51ee786df8a44d9058a478348534cf46945faf
Author: Hannes Reinecke h...@suse.de
Date: Mon Mar 4 17:14:43 2013 +0100
USB: xhci: correctly enable interrupts
commit 00eed9c814cb8f281be6f0f5d8f45025dc0a97eb upstream.
which went into Linux 3.2.42 earlier today. But that change won't go
into Debian for at least a week or so.
You could try it yourself using the attached patch and the instructions
at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.
Ben.
--
Ben Hutchings
I'm not a reverse psychological virus. Please don't copy me into your sig.
From: Hannes Reinecke h...@suse.de
Date: Mon, 4 Mar 2013 17:14:43 +0100
Subject: USB: xhci: correctly enable interrupts
commit 00eed9c814cb8f281be6f0f5d8f45025dc0a97eb upstream.
xhci has its own interrupt enabling routine, which will try to
use MSI-X/MSI if present. So the usb core shouldn't try to enable
legacy interrupts; on some machines the xhci legacy IRQ setting
is invalid.
v3: Be careful to not break XHCI_BROKEN_MSI workaround (by trenn)
Cc: Bjorn Helgaas bhelg...@google.com
Cc: Oliver Neukum oneu...@suse.de
Cc: Thomas Renninger tr...@suse.de
Cc: Yinghai Lu ying...@kernel.org
Cc: Frederik Himpe fhi...@vub.ac.be
Cc: David Haerdeman da...@hardeman.nu
Cc: Alan Stern st...@rowland.harvard.edu
Acked-by: Sarah Sharp sarah.a.sh...@linux.intel.com
Reviewed-by: Thomas Renninger tr...@suse.de
Signed-off-by: Hannes Reinecke h...@suse.de
Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
drivers/usb/core/hcd-pci.c | 23 ++-
drivers/usb/host/xhci.c|3 ++-
2 files changed, 16 insertions(+), 10 deletions(-)
--- a/drivers/usb/core/hcd-pci.c
+++ b/drivers/usb/core/hcd-pci.c
@@ -173,6 +173,7 @@ int usb_hcd_pci_probe(struct pci_dev *de
struct hc_driver *driver;
struct usb_hcd *hcd;
int retval;
+ int hcd_irq = 0;
if (usb_disabled())
return -ENODEV;
@@ -187,15 +188,19 @@ int usb_hcd_pci_probe(struct pci_dev *de
return -ENODEV;
dev-current_state = PCI_D0;
- /* The xHCI driver supports MSI and MSI-X,
- * so don't fail if the BIOS doesn't provide a legacy IRQ.
+ /*
+ * The xHCI driver has its own irq management
+ * make sure irq setup is not touched for xhci in generic hcd code
*/
- if (!dev-irq (driver-flags HCD_MASK) != HCD_USB3) {
- dev_err(dev-dev,
- Found HC with no IRQ. Check BIOS/PCI %s setup!\n,
- pci_name(dev));
- retval = -ENODEV;
- goto disable_pci;
+ if ((driver-flags HCD_MASK) != HCD_USB3) {
+ if (!dev-irq) {
+ dev_err(dev-dev,
+ Found HC with no IRQ. Check BIOS/PCI %s setup!\n,
+pci_name(dev));
+ retval = -ENODEV;
+ goto disable_pci;
+ }
+ hcd_irq = dev-irq;
}
hcd = usb_create_hcd(driver, dev-dev, pci_name(dev));
@@ -245,7 +250,7 @@ int usb_hcd_pci_probe(struct pci_dev *de
pci_set_master(dev);
- retval = usb_add_hcd(hcd, dev-irq, IRQF_SHARED);
+ retval = usb_add_hcd(hcd, hcd_irq, IRQF_SHARED);
if (retval != 0)
goto unmap_registers;
set_hs_companion(dev, hcd);
--- a/drivers/usb/host/xhci.c
+++ b/drivers/usb/host/xhci.c
@@ -342,7 +342,7 @@ static int xhci_try_enable_msi(struct us
* generate interrupts. Don't even try to enable MSI.
*/
if (xhci-quirks XHCI_BROKEN_MSI)
- return 0;
+ goto legacy_irq;
/* unregister the legacy interrupt */
if (hcd-irq)
@@ -363,6 +363,7 @@ static int xhci_try_enable_msi(struct us
return -EINVAL;
}
+ legacy_irq:
/* fall back to legacy interrupt*/
ret = request_irq(pdev-irq, usb_hcd_irq, IRQF_SHARED,
hcd-irq_descr, hcd);
signature.asc
Description: This is a digitally signed message part
Bug#703470: UEFI USB stick installation fails on HP EliteBook 8570p
On Wed, 2013-03-27 at 05:13 +, Mike wrote: This looks like http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700845 Yes. Does this workaround look sensible?: https://lkml.org/lkml/2013/3/9/134 It might be, but we need to find a real fix as well. You could also try this patch: https://lkml.org/lkml/2013/2/18/115 Ben. -- Ben Hutchings I'm not a reverse psychological virus. Please don't copy me into your sig. signature.asc Description: This is a digitally signed message part
