Bug#704191: HP EliteBook 8570p BIOS-GPT install fails

2013-03-29 Thread Mike
Package: installation-reports Boot method: ISO on USB stick on USB 2.0 port Image version: http://cdimage.debian.org/cdimage/wheezy_di_rc1/amd64/iso-cd/debian-wheezy-DI-rc1-amd64-netinst.iso Date: 2013-03-29 Machine: HP EliteBook 8570p (C6Z56UT) Processor: Intel Core i5-3320M Memory: 4 GiB Parti

Bug#704191: HP EliteBook 8570p BIOS-GPT install succeeds, with bootable flag

2013-03-29 Thread Mike
Control: retitle -1 HP EliteBook 8570p BIOS-GPT install succeeds, with bootable flag > But rebooting fails to find boot code, gives HP screen: > > > BootDevice Not Found > > Please install an operating system on your hard disk. > [...] >

Processed: HP EliteBook 8570p BIOS-GPT install succeeds, with bootable flag

2013-03-29 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 HP EliteBook 8570p BIOS-GPT install succeeds, with bootable flag Bug #704191 [installation-reports] HP EliteBook 8570p BIOS-GPT install fails Changed Bug title to 'HP EliteBook 8570p BIOS-GPT install succeeds, with bootable flag' from 'HP EliteBook 8570p

Bug#703469: marked as done (HP EliteBook 8570p UEFI install works, with some effort)

2013-03-29 Thread Debian Bug Tracking System
Your message dated Fri, 29 Mar 2013 07:41:28 + with message-id <20130329074128.gb30...@64-142-29-25.dsl.static.sonic.net> and subject line HP EliteBook 8570p UEFI install works, with some effort has caused the Debian Bug report #703469, regarding HP EliteBook 8570p UEFI install works, with some

Re: Bug#704138: "No disk drive was detected" during install

2013-03-29 Thread anshprat
I tried install with a cd rom image on USB and it worked! So I tried the pxe boot image again, went through the logs and looks like the scsi modules are missing in the netboot tar gz. 630: anna[1750]: DEBUG: resolver (scsi-modules-2.6.32-5-amd64-di): package doesn't exist (ignored) [anshup@isis i

Bug#704191: HP EliteBook 8570p BIOS-GPT install succeeds, with bootable flag

2013-03-29 Thread Mike
Xen/Linux also runs properly with this configuration. -- 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/20130329083838.ga30...@64-142-29-25.dsl.static.sonic.net

Bug#701694: Recent 3.4-stock-kernel update fixed the VT-graphics-trouble partially

2013-03-29 Thread Andreas Glaeser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The situation is now on my 'GNOME-box' as I like to call it, that there is no dmesg-error message issued anymore with the most recent 3.2. kernel-version, but intermittent blanking still occurs without showing in dmesg-output. Full-screen blanking as

Bug#704200: Installation was successfully on Lenovo Thinkpad

2013-03-29 Thread Bernhard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Boot method: USB Drive with self-made ISO image Image version: Self-made ISO image with wheezy installer RC1 Date: 2013-03-29 Machine: Lenovo Thinkpad L520 Processor: Intel(R) Pentium(R) CPU B950 @ 2.10GHz Memory: 4GB Pa

Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel

2013-03-29 Thread Tycho Lürsen
debootstrap version 1.0.47 has been in sid for a while now. When can we expect it in wheezy? If that is going to take long, I suggest reverting apt (in wheezy) to the version that masks the problems with debootstrap. @Pierre Blondeau Nice, what parameters did you use to get from a simple pxe bo

Bug#704138: marked as done ("No disk drive was detected" during install)

2013-03-29 Thread Debian Bug Tracking System
Your message dated Fri, 29 Mar 2013 18:40:44 + with message-id <1364582444.3520.95.ca...@deadeye.wl.decadent.org.uk> and subject line Re: Bug#704138: "No disk drive was detected" during install has caused the Debian Bug report #704138, regarding "No disk drive was detected" during install to be

Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel

2013-03-29 Thread Tycho Lürsen
I have tried the expert mode (google got me there in about 10 secs) but no luck whatsoever. First of all: Pierre Blondeau says: >During the system base installation, the installer ask you to choice your kernel version. That implies that you get that far. When I submitted this bug, I did inde

Processed: your mail

2013-03-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found #703979 Bug #703979 [debian-installer-launcher] Cleanup after install wipes /target if umount failed (e.g. shell open in /target) Ignoring request to alter fixed versions of bug #703979 to the same values previously set > End of message, s

Processed: your mail

2013-03-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 703979 5 Bug #703979 [debian-installer-launcher] Cleanup after install wipes /target if umount failed (e.g. shell open in /target) Marked as found in versions debian-installer-launcher/5. > found 703979 14 Bug #703979 [debian-installer-laun

preseed/file=/hd-media/a/deeper/directory/preseed.cfg. What about which fs it is?

2013-03-29 Thread Regid Ichira
1. When using a preseed/file kernel parameter, must I have the preconfiguration file in the toplevel directory of the hd-media? 2. Will the installer automatically try to figure out the fs in the media? Does ntfs an option? 3. Does it log problems? In short, if I boot the installer kernel

Processed: your mail

2013-03-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 704190 debootstrap Bug #704190 [ltsp-server] ltsp-build-client fails because of apt GPG error Bug reassigned from package 'ltsp-server' to 'debootstrap'. Ignoring request to alter found versions of bug #704190 to the same values previous