Bug#928506: installation-report: fails to find mirror under OpenBSD vmm(4) hypervisor

Control: tag -1 - d-i Hi Matthew, Matthew T Hoare (2019-05-06): > Dear Maintainer, > >* What led up to the situation? >I ran the installer under OpenBSD's vmm(4) hypervisor. >* What exactly did you do (or not do) that was effective (or > ineffective)? >Tried to connect to

Processed: Re: Bug#928506: installation-report: fails to find mirror under OpenBSD vmm(4) hypervisor

Processing control commands: > tag -1 - d-i Bug #928506 [installation-reports] installation-report: fails to find mirror under OpenBSD vmm(4) hypervisor Removed tag(s) d-i. -- 928506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928506 Debian Bug Tracking System Contact

Processed: Re: Bug#926903: Installation-report addition

Processing control commands: > clone -1 -2 Bug #926903 [installation-reports] Package: installation-reports Bug 926903 cloned as bug 928510 > retitle -1 installation-reports: Installer with firmware does not install > firmware-amd-graphics Bug #926903 [installation-reports] Package:

Bug#926903: Installation-report addition

Control: clone -1 -2 Control: retitle -1 installation-reports: Installer with firmware does not install firmware-amd-graphics Control: reassign -2 firmware-amd-graphics Control: retitle -2 firmware-amd-graphics: Should trigger initramfs rebuild On Thu, 2019-05-02 at 11:10 +0100, Ben Hutchings

Bug#928506: installation-report: fails to find mirror under OpenBSD vmm(4) hypervisor

TF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) installation-report depends on no packages. Versions of packages installation-report recommends: ii pciutils 1:3.5.2-1 ii reportbug 7.5.2 installation-report suggests no packages. -- no debconf information

Bug#926903: Installation-report addition

Hi Ben, Success! Booting up on the Dell U2414H now has the screen centered. GUI windows and fonts are a little erratic. a) tty1-6 now has smaller (regular) font b) MATE Terminal, emacs and pluma have regular fonts c) Xemacs, XTerm & UXTerm have small windows with small font Tried to run the

Bug#926903: Installation-report addition

On Thu, 2019-05-02 at 12:00 +1000, Tom Thekathyil wrote: > Hi Ben, > > I ran 'update-initramfs -u' and got several lines saying > > 'W: Possible missing firmware /lib/firmware/amdgpu/vega20_ xxx for > module a[off screen here]pu' where xxx refers to different items. > > Regards, Tom Thekathyil

Bug#926903: Installation-report addition

Hi Ben, I ran 'update-initramfs -u' and got several lines saying 'W: Possible missing firmware /lib/firmware/amdgpu/vega20_ xxx for module a[off screen here]pu' where xxx refers to different items. Regards, Tom Thekathyil On Thu, 2019-05-02 at 00:45 +0100, Ben Hutchings wrote: > Does running

Bug#926903: Installation-report addition

On Thu, 2019-05-02 at 07:32 +1000, Tom Thekathyil wrote: > Hi Ben, > > Thanks for trying to help. You will note from my original report as > well as the follow-up on 28 April that I had installed the > 'firmware-amd-graphics' package and still get the error message. Ah, sorry. > # apt search

Bug#926903: Installation-report addition

Hi Ben, Thanks for trying to help. You will note from my original report as well as the follow-up on 28 April that I had installed the 'firmware-amd-graphics' package and still get the error message. # apt search firmware-amd-graphics > firmware-amd-graphics/testing, now 201901 14-1 all

Bug#926903: Installation-report addition

On Tue, 2019-04-30 at 10:51 +1000, Tom Thekathyil wrote: > Hi Geert, > > Thank you so much for your prompt reply. > > Your suggestion it could be a monitor problem provided the clue it > could be the 11-year old model used (Acer X223w) that was causing the > problem. Swapped for a more current

Bug#926903: Installation-report addition

Hi Geert, Thank you so much for your prompt reply. Your suggestion it could be a monitor problem provided the clue it could be the 11-year old model used (Acer X223w) that was causing the problem. Swapped for a more current unit (Dell U2414H) and screen is nicely centered now. That still

Bug#928192: installation-report: Successful install of Buster (daily 2019-04-29) on ThinkPad X23

F-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) installation-report depends on no packages. Versions of packages installation-report recommends: ii pciutils 1:3.5.2-1 ii reportbug 7.5.2 installation-report suggests no packages. -- no debconf information

Bug#926903: Installation-report addition

On Sun, Apr 28, 2019 at 11:26:24AM +1000, Tom Thekathyil wrote: > > 2019/04/20 > # remove --purge firmware-amd-graphics > (screen no longer shifted 10% to left but shifted 5% to right) > > 2019/04/22 > # apt update && apt upgrade > # apt install firmware-amd-graphics amd64-microcode > (screen

Bug#926903: Installation-report addition

Hi Debian, I am still grappling with the problem of screen being off-center although it is no longer 10% to left but 5% to right. My comments within brackets (). 2019/04/20 # remove --purge firmware-amd-graphics (screen no longer shifted 10% to left but shifted 5% to right) 2019/04/22 # apt

Bug#927518: Updating the installation-report Uploaders list

Source: installation-report Version: 2.64 2.69 2.71 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Christian Perrier has retired, so can't work on the installation-report package anymore (at least with this address). We are tracking their status in the MIA team and would like

Bug#927075: installation-report amd64 Buster 20190410, segv in gen-crypt

Package: installation-reports Boot method: network Image version: http://http.us.debian.org/debian/dists/buster/main/installer-amd64/20190410/images/netboot/netboot.tar.gz Date: 20190413T130500 Machine: Sun Microsystems SunFire x4170 Partitions: $ lsblk -i NAMEMAJ:MIN RM

Bug#820911: marked as done (installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut)

Your message dated Wed, 10 Apr 2019 20:33:55 + with message-id and subject line Bug#820911: fixed in debian-installer 20190410 has caused the Debian Bug report #820911, regarding installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated

Bug#926448: installation-report: success: DELL R330+UEFI+SecureBoot + buster d-i 20190404

Package: installation-reports Version: 2.62 Severity: normal Dear Maintainer, I succeeded to install Buster to DELL R330 UEFI + secure boot. Thank you for your great work. -- Package-specific info: Boot method: USB Image version: Debian GNU/Linux testing "Buster" - Official Snapshot amd64

Bug#924563: installation report, not good

Package: installation-reports Boot method: USB with dvd image Image version: debian-testing-amd64-DVD-1.iso weekly 2019-03-12 Date: 2019-03-14 Machine: generic desktop pc Processor:  AMD Athlon(tm) 5150 APU with Radeon(tm) R3 Memory: 8G Partitions: only one partition + swap (all by default) +

Bug#919606: installation-reports: installation report

Package: installation-reports Severity: wishlist Dear Maintainer, I am just sending you installation report as suggested in the Installation Howto Appendix A section 4 *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What

Bug#916843: marked as done (installation-report: Buster testing on Dell DX0D thin-client without non-free section)

Your message dated Thu, 17 Jan 2019 15:09:08 +0100 with message-id <20190117150908.60fc3ea4@a68n.lokal> and subject line done has caused the Debian Bug report #916843, regarding installation-report: Buster testing on Dell DX0D thin-client without non-free section to be marked as done. This

Bug#916843: installation-report: Buster testing on Dell DX0D thin-client without non-free section

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.69 Severity: minor Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was

Bug#904868: marked as done (Installation Report (Fail) : Debian 9.5 Install Fail)

Your message dated Mon, 30 Jul 2018 05:21:07 +0100 with message-id <20180730042107.vfhr5ozcabi5w...@tack.einval.com> and subject line Re: Bug#904868: Acknowledgement (Installation Report (Fail) : Debian 9.5 Install Fail) has caused the Debian Bug report #904868, regarding Installation

Bug#904868: Acknowledgement (Installation Report (Fail) : Debian 9.5 Install Fail)

I did some more testing with the system and discovered it is an issue with it attempting to display the greeter on a display that is turned off. Not an issue with the installation system this time around. Thanks for your time. On 29/07/18 15:39, Debian Bug Tracking System wrote: Thank you

Bug#904868: Installation Report (Fail) : Debian 9.5 Install Fail

Package: installation-reports Boot method: - netinst image on a pen drive non-UEFI Image version: https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.5.0-amd64-netinst.iso Date: 2018-07-29 15:00 NZST Machine: Homebuilt desktop with Intel DB75EN mainboard Processor: Intel

Bug#904421: installation-report

Package: installation-reports Boot method: DVD-1 Image version: https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.5.0-amd64-netinst.iso Date: 23 July 2018, 03:30 UTC Machine: Fujitsu Lifebook T4410 Processor: Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz Memory: 4GB

Bug#902870: installation-report: DI grub-install should use UUIDs instead of plain disk-device-names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.68 Severity: minor Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was

Bug#764361: marked as done (installation-report: XFS filesystem fails to upgrade from kernel 3.2 to 3.16)

Your message dated Mon, 28 May 2018 08:54:18 +0200 with message-id <20180528085418.5946639d@a68n.lokal> and subject line done has caused the Debian Bug report #764361, regarding installation-report: XFS filesystem fails to upgrade from kernel 3.2 to 3.16 to be marked as done. This means th

Bug#897145: marked as done (installation report)

Your message dated Sun, 29 Apr 2018 05:58:44 +0100 with message-id <76c0352d53a2c9ce562ddd5455b825bbb18ed3fa.ca...@decadent.org.uk> and subject line Re: Bug#897145: installation report has caused the Debian Bug report #897145, regarding installation report to be marked as done. This

Bug#897145: installation report

Package: installation-reports Boot method: USB drive created from Buster Alpha 2 ISO using unetbootin Image version: https://cdimage.debian.org/cdimage/buster_di_alpha2/amd64/iso-cd/debian-buster-DI-alpha2-amd64-netinst.iso Date: April 27, 2018 @ 21:33 Eastern (US) Daylight Saving time

Accepted installation-report 2.68 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 15 Feb 2018 06:57:58 +0100 Source: installation-report Binary: save-logs installation-report Architecture: source Version: 2.68 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team <debian-b

Bug#879987: Netboot installation report for Banana Pi M3

I cannot see anything in the log that would explain why the serial console driver didn't provide any output on the Debian kernel 4.13 (with the devicetree from 4.14). Would you perhaps be willing to do another test run once the debian-installer has moved to kernel 4.14? Yes of course, only how

Bug#879987: Netboot installation report for Banana Pi M3

Hello there, many thanks for your reply, I guess it can't be helped then. Out of curiosity, could you tell me on which list the discussion takes place? [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 4.14.0-rc6-00053-g15f859ae5c43-dirty (stefan@debian) (gcc

Bug#879987: Netboot installation report for Banana Pi M3

Package: installation-reports Boot method: Put the files on an SD card an manually loaded them in u-boot Image version: http://ftp.nl.debian.org/debian/dists/sid/main/installer-armhf/current/images/netboot/ At the time of dowloading the image, the time column says "20:48 19-09-17". Date:

Bug#800127: marked as done (installation-report: Jessie stable set up on Biostar a68n-5000 m-ITX mainboard)

Your message dated Wed, 11 Oct 2017 09:04:16 +0200 with message-id <20171011090416.0dc3f05b@a68n.lokal> and subject line done has caused the Debian Bug report #800127, regarding installation-report: Jessie stable set up on Biostar a68n-5000 m-ITX mainboard to be marked as done. This

Bug#876866: installation-report: no boot from USB upon removing installation memory-key

Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) installation-report depends on no packages. Ver

Bug#876352: Package: installation-report for Debian9

Package: installation-report Worth knowing if you use VirtualBox with Debian9 guests? : The rubyv3 guest is a fresh install of Debian9 from a CD including graphics and intended as a workstation. The rubyv4 guest is a fresh install of Debian9 from a network install CD with no optional software

Bug#868085: installation-report: Stretch - Important Info for Dell Mini and Others

Hi, bw (2017-07-18): > Interesting reading if you have the time. I'm not sure how I could help, > but if you think of a way, just let me know. Thanks. > > https://github.com/systemd/systemd/issues/1792 > https://bugzilla.kernel.org/show_bug.cgi?id=107651 > > Earlier

Bug#868085: installation-report: Stretch - Important Info for Dell Mini and Others

On Tue, 7/18/17, Cyril Brulebois <k...@debian.org> wrote: Subject: Re: Bug#868085: installation-report: Stretch - Important Info for Dell Mini and Others To: "b17" <bwtn...@yahoo.com>, 868...@bugs.debian.org Date: Tuesday,

Bug#868085: installation-report: Stretch - Important Info for Dell Mini and Others

Hi, b17 (2017-07-11): > Installation is fine, first boot is okay, but all further boots fail because > systemd.backlight.service tries to restore a kbd backlight that does not > exist on the machine. This is a two year old issue since around kernel 4.1 > the solution is : > #

Bug#854822: marked as done (installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk")

Rick Thomas (2017-07-17): > Great! Is there an installer image somewhere I can test this with on > my Cubox-i4x4 ? An installer rebuilt to include this change will be uploaded this week, and published along with the point release (this weekend). KiBi. signature.asc

Bug#854822: marked as done (installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk")

solo.debian.org> > and subject line Bug#854822: fixed in partman-base 191+deb9u1 > has caused the Debian Bug report #854822, > regarding installation-report: U-boot not correctly installed when > partitioning with "Guided - use entire disk" > to be marked as done. >

Bug#854822: marked as done (installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk")

Your message dated Sat, 15 Jul 2017 22:17:18 + with message-id <e1dwvng-000fnf...@fasolo.debian.org> and subject line Bug#854822: fixed in partman-base 191+deb9u1 has caused the Debian Bug report #854822, regarding installation-report: U-boot not correctly installed when partit

Bug#786872: marked as done (installation-report: Jessie (8) on Neoware m100 mobile thin-client without graphics)

Your message dated Wed, 12 Jul 2017 13:31:16 +0200 with message-id <20170712133116.6727b2f5@a68n.lokal> and subject line quite not worth it has caused the Debian Bug report #786872, regarding installation-report: Jessie (8) on Neoware m100 mobile thin-client without graphics to be marked a

Bug#800367: marked as done (installation-report: stretch-testing on NEOWARE m100: no graphics)

Your message dated Wed, 12 Jul 2017 13:17:00 +0200 with message-id <20170712131700.5503e0fb@a68n.lokal> and subject line quite not worth it has caused the Debian Bug report #800367, regarding installation-report: stretch-testing on NEOWARE m100: no graphics to be marked as done. This

Bug#868085: installation-report: Stretch - Important Info for Dell Mini and Others

to /bin/dash Init: systemd (via /run/systemd/system) installation-report depends on no packages. Versions of packages installation-report recommends: ii pciutils 1:3.5.2-1 ii reportbug 7.1.2 installation-report suggests no packages. -- no debconf information

Bug#819867: marked as done (installation-report: USB-boot fails with Stretch, no GRUB-installation with BTRFS-partition)

Your message dated Mon, 10 Jul 2017 08:28:32 +0200 with message-id <20170710082832.7574146d@a68n.lokal> and subject line done - usb-boot is now workable in the stretch-release has caused the Debian Bug report #819867, regarding installation-report: USB-boot fails with Stretch, no

Bug#866681: supplement to 866681-installation-report

Hello again, I want to make a small supplement to my bug report. lspci -nn //shows a litte bit more information XYZ@debian:~$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) 00:01.0 PCI bridge [0604]: Intel Corporation Xeon

Bug#866681: installation-report

Package: installation-reports Boot method: DVD Image version: debian-9.0.0-amd64-DVD-1.iso 2017-06-17 16:21 3.5G Date: 2017-06-30 Machine: ASUS Z87-WS motherboard Processor: Intel Core i7-47-4790T,

Bug#854822: marked as done (installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk")

Your message dated Sun, 25 Jun 2017 22:34:23 + with message-id <e1dpg6p-000fyz...@fasolo.debian.org> and subject line Bug#854822: fixed in partman-base 192 has caused the Debian Bug report #854822, regarding installation-report: U-boot not correctly installed when partitioning with &

Bug#854822: installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk"

Hi Rick, Rick Thomas (2017-06-25): > On Feb 10, 2017, at 12:43 PM, Cyril Brulebois wrote: > > Karsten Merker (2017-02-10): > >> when using the "Guided - use entire disk" option, partman by > >> default clobbers the boot sector and the

Bug#854822: installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk"

On Feb 10, 2017, at 12:43 PM, Cyril Brulebois wrote: > Hi, > > Karsten Merker (2017-02-10): >> when using the "Guided - use entire disk" option, partman by >> default clobbers the boot sector and the area after it (where >> u-boot is located) to make sure

Bug#863952: marked as done (installation-report: current font-size for mr_IN locale is smaller which makes difficult to read while installation)

Your message dated Tue, 20 Jun 2017 06:42:52 + with message-id <e1dncsg-000ivc...@fasolo.debian.org> and subject line Bug#863952: fixed in rootskel-gtk 1.37 has caused the Debian Bug report #863952, regarding installation-report: current font-size for mr_IN locale is smaller which

Bug#864991: installation-report: Installer blank screen

Hi, Aurora (2017-06-18): > Package: installation-reports > Version: 2.62 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? Debian graphical install

Bug#864991: installation-report: Installer blank screen

.9.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) installation-report depends on no packages. Versions of packages installation-report

Bug#863952: installation-report: current font-size for mr_IN locale is smaller which makes difficult to read while installation

Control: tags -1 + pending Hello, Sagar सागर, on mer. 14 juin 2017 18:45:19 +0530, wrote: > I attached patch which increases font size of mr_IN locale. Thanks, I have applied it to the source. Samuel

Processed: Re: Bug#863952: installation-report: current font-size for mr_IN locale is smaller which makes difficult to read while installation

Processing control commands: > tags -1 + pending Bug #863952 [rootskel-gtk] installation-report: current font-size for mr_IN locale is smaller which makes difficult to read while installation Added tag(s) pending. -- 863952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863952 Debian

Processed: Re: installation-report: current font-size for mr_IN locale is smaller which makes difficult to read while installation

Processing control commands: > reassign -1 rootskel-gtk Bug #863952 [installation-report] installation-report: current font-size for mr_IN locale is smaller which makes difficult to read while installation Bug reassigned from package 'installation-report' to 'rootskel-gtk'. Ignoring requ

Bug#863952: installation-report: current font-size for mr_IN locale is smaller which makes difficult to read while installation

Control: reassign -1 rootskel-gtk Tags: patch Hi , I attached patch which increases font size of mr_IN locale. Thanks, I Sagar diff --git a/src/usr/bin/gtk-set-font b/src/usr/bin/gtk-set-font index f3c0c3a..1cd0974 100644 --- a/src/usr/bin/gtk-set-font +++ b/src/usr/bin/gtk-set-font @@ -69,7

Bug#864015: marked as done (installation-reports: Installation report)

Your message dated Sat, 3 Jun 2017 14:03:23 +0200 with message-id <20170603120323.gb6...@mraw.org> and subject line Re: Bug#864015: installation-reports: Installation report has caused the Debian Bug report #864015, regarding installation-reports: Installation report to be marked a

Bug#864015: installation-reports: Installation report

drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Installation report about installation processed without errors. -- Please make sure that the hardware-summary log file

Bug#863952: installation-report: current font-size for mr_IN locale is smaller which makes difficult to read while installation

Package: installation-report Severity: normal Tags: d-i Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? When selecting marathi (mr_IN) locale for installation. * What exactly did you do (or not do

Re: Bug#863241: Debian Stretch 9 RC03 Installation Report

m <sub...@bugs.debian.org>Subject: installation-report:  > Debian Stretch 9 RC03 Installation ReportMessage-ID: > <149560279860.20727.11722936000839078769.reportbug@a>X-Mailer: reportbug > 7.1.6Date: Wed, 24 May 2017 05:13:18 + > Package: installation-reportsVersion: 2.6

Processed: Triaging successful installation report with suggestion

Processing commands for cont...@bugs.debian.org: > retitle 780208 Please ask for custom swap size in guided partition setup Bug #780208 [installation-reports] installation-report: Successful jessie install with 2015-03-09 daily uefi netboot image Changed Bug title to 'Please ask for custom s

Bug#765090: marked as done (installation-report: UEFI boot fails after install)

Your message dated Sat, 13 May 2017 10:21:00 + with message-id <f2a26d61-82f5-cd87-a3b8-10e92c485...@a4nancy.net.eu.org> and subject line Closing obsolete bug report has caused the Debian Bug report #765090, regarding installation-report: UEFI boot fails after install to be marked a

Bug#714470: marked as done (installation-report: UEFI boot fails after install)

Your message dated Sat, 13 May 2017 10:12:00 + with message-id <5ae3a9ef-a84e-36f2-405c-f13d65852...@a4nancy.net.eu.org> and subject line Closing obsolete bug report has caused the Debian Bug report #714470, regarding installation-report: UEFI boot fails after install to be marked a

Bug#707763: marked as done (Installation Report, Macbook Pro, Bad Install.)

Your message dated Sat, 13 May 2017 10:03:00 + with message-id <0d530179-8310-4674-dab1-8b16420aa...@a4nancy.net.eu.org> and subject line Closing obsolete bug report has caused the Debian Bug report #707763, regarding Installation Report, Macbook Pro, Bad Install. to be marked a

Re: how to get/put up installation report on installation failure when immediate network is not available.

In-line :- On 26/04/2017, shirish शिरीष <shirisha...@gmail.com> wrote: > in-line :- > > On 25/04/2017, Baptiste Jammet <bapti...@mailoo.org> wrote: >> Hello, >> > > Hello, > >> Dixit shirish शिरीष, le 25/04/2017 : >> >>>My query is

Re: how to get/put up installation report on installation failure when immediate network is not available.

in-line :- On 25/04/2017, Baptiste Jammet <bapti...@mailoo.org> wrote: > Hello, > Hello, > Dixit shirish शिरीष, le 25/04/2017 : > >>My query is how to save installation report and send it in the >>instance when the installation is a failure. I know that deta

Re: how to get/put up installation report on installation failure when immediate network is not available.

Hello, Dixit shirish शिरीष, le 25/04/2017 : >My query is how to save installation report and send it in the >instance when the installation is a failure. I know that details of >what worked or didn't is in the memory (RAM) but how to save it to usb >disk/usb thumbdrive ? At tim

how to get/put up installation report on installation failure when immediate network is not available.

Dear all, There are two three queries I have but instead of bunching them together, would try to get solutions or pointers by spelling them individually. Below is the first one - 1. Installation report on installation failure - At times when you are installing Debian either on too new hardware

Bug#860478: Installation Report

Package: installation-reports Boot method: VirtualBox Image version: http://cdimage.debian.org/cdimage/stretch_di_rc3/amd64/iso-cd/debian-stretch-DI-rc3-amd64-netinst.iso Date: 15:12 17.04.2017 Machine: VirtualBox 5.0.6 under Windows 10; default settings Processor: ? Memory: 5219 Mb

Bug#857743: installation-report: Jessie stable ++ all Backports cause kernel-panic on HP EliteBook 8440p

Control: reassign -1 systemd On Tue, 2017-03-14 at 17:05 +0100, Andreas Glaeser wrote: [...] > Kernel-Panic appears both with Kernel 3.16 and 4.9, when all backports are > installed, > see attachment [k-panic-sshot.JPG], [...] That shows that the kernel panicked because init (systemd) exited.

Processed: Re: Bug#857743: installation-report: Jessie stable ++ all Backports cause kernel-panic on HP EliteBook 8440p

Processing control commands: > reassign -1 systemd Bug #857743 [installation-reports] installation-report: Jessie stable ++ all Backports cause kernel-panic on HP EliteBook 8440p Bug reassigned from package 'installation-reports' to 'systemd'. No longer marked as found in versions 2.58. Ignor

Bug#839894: [patch] fix installation to system that has many disks (>= 27) (Re: Bug#839894: installation-report: Jessie installer fails to install GRUB on a large JBOD system

Hi, ping to debian-boot for patch review. On Sat, 04 Feb 2017 13:15:36 +0900 Hideki Yamane wrote: > control: reassign -1 grub-installer > control: tags -1 +patch (snip) > More tiny fix is enough for this issue. I've confirmed it by  >

Bug#857445: installation-report: Default https mirror list empty

Control: tag -1 - d-i Control: severity -1 normal Hi, kwadronaut (2017-03-11): > I used the alternative 'expert' installation, happens both remote or > with gui or text only. When the time came to choose my mirror for apt > sources, I could pick between http, ftp and

Processed: Re: Bug#857445: installation-report: Default https mirror list empty

Processing control commands: > tag -1 - d-i Bug #857445 [installation-reports] installation-report: Default https mirror list empty Removed tag(s) d-i. > severity -1 normal Bug #857445 [installation-reports] installation-report: Default https mirror list empty Severity set to 'normal

Bug#857445: installation-report: Default https mirror list empty

ease: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) installation-report depends on no packages. Versions of packages inst

Bug#597799: marked as done (installation-report: GPT related issues)

Your message dated Mon, 27 Feb 2017 21:34:36 +0200 with message-id <20170227193436.lt6jbbovu6fpucbm@localhost> and subject line Closing squeeze-only bugs has caused the Debian Bug report #507399, regarding installation-report: GPT related issues to be marked as done. This means that you

Processed: Re: Bug#854822: installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk"

Processing control commands: > tags 854822 + patch Bug #854822 [installation-reports] installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk" Added tag(s) patch. -- 854822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854822 Debian

Bug#854822: installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk"

Thanks for the quick insight into this, Karsten! Karsten Merker dijo [Fri, Feb 10, 2017 at 09:36:33PM +0100]: > (...) but this doesn't work in your case as we currently > only disable the clobbering for /dev/mmcblk0 while your SD card > shows up as /dev/mmcblk1. I am not 100% sure about that, but

Bug#854822: installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk"

Hi, Karsten Merker (2017-02-10): > when using the "Guided - use entire disk" option, partman by > default clobbers the boot sector and the area after it (where > u-boot is located) to make sure that there are no remains of old > partition tables. We have code in partman-base

Bug#854822: installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk"

Please note that the provided "hardware-summary" was taken from the second (successful) install. I mention this due to: > (...) > == > Installer hardware-summary: > == > (...) > df: Filesystem

Bug#854822: installation-report: U-boot not correctly installed when partitioning with "Guided - use entire disk"

en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) installation-report depends on no packages. Versions of packages installation-report recommends: ii pciutils 1:3.5.2-1 ii reportbug 7.1.4 installation-report suggests no packages. -- no

Bug#839894: [patch] fix installation to system that has many disks (>= 27) (Re: Bug#839894: installation-report: Jessie installer fails to install GRUB on a large JBOD system

control: reassign -1 grub-installer control: tags -1 +patch Hi, On Tue, 11 Oct 2016 12:13:33 +0200 "Jonathan Quick" wrote: > > Probably this part of grub-installer is the problem: > > > > > >

Processed: [patch] fix installation to system that has many disks (>= 27) (Re: Bug#839894: installation-report: Jessie installer fails to install GRUB on a large JBOD system

Processing control commands: > reassign -1 grub-installer Bug #839894 [installation-reports] installation-report: Jessie installer fails to install GRUB on a large JBOD system Bug reassigned from package 'installation-reports' to 'grub-installer'. No longer marked as found in versions 2

Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut

Alex ARNAUD, on Sat 21 Jan 2017 19:00:15 +0100, wrote: > Could we imagine to have an alternative way? Sure, it's a "matter" of implementing it in grub. For now I don't know any easy way in grub to append parameters, the support has thus to be added. To be discussed with grub people. Samuel

Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut

Alex ARNAUD, on Sat 21 Jan 2017 18:07:13 +0100, wrote: > >If you wish or need to add any boot parameters for either the installer > >or the kernel, press Tab (BIOS boot), or 'e' then down arrow three times > >then 'end' (UEFI boot). This will bring the boot command for the selected > >menu entry

Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut

Alex ARNAUD, on Sat 21 Jan 2017 19:00:15 +0100, wrote: > >Slightly off-topic here, but *please* don't use Virtualbox for testing > >with EFI. The virtualbox EFI support is half-assed and broken and will > >cause problems later. > > What alternative do you advise me? In d-i we have documented

Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut

Slightly off-topic here, but *please* don't use Virtualbox for testing with EFI. The virtualbox EFI support is half-assed and broken and will cause problems later. What alternative do you advise me? You've missed out the "down arrow three times" here - with that it works, I've just tested

Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut

Hey guys, On Sat, Jan 21, 2017 at 06:07:13PM +0100, Alex ARNAUD wrote: >>« >>If you wish or need to add any boot parameters for either the installer >>or the kernel, press Tab (BIOS boot), or 'e' then down arrow three times >>then 'end' (UEFI boot). This will bring the boot command for the

Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut

Le 15/01/2017 à 16:46, Samuel Thibault a écrit : Hello Alex, Hello Samuel « If you wish or need to add any boot parameters for either the installer or the kernel, press Tab (BIOS boot), or 'e' then down arrow three times then 'end' (UEFI boot). This will bring the boot command for the

Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut

Hello Alex, Alex ARNAUD, on Thu 01 Dec 2016 14:56:08 +0100, wrote: > - Change the Debian installation guide to help visual-impaired to > activate the ncurse or graphical high-contrast theme. > I'm not able to write it myself because the contrast of the first screen > makes it completely

Bug#800367: installation-report: stretch-testing on NEOWARE m100: no graphics

an 2017 10:33:04 +0100 > From: Andreas Glaeser <bugs.andreas.glae...@freenet.de> > To: 800...@bugs.debian.org, openchrome-us...@lists.freedesktop.org > Subject: [Openchrome-users] installation-report: stretch-testing on > NEOWARE m100: no graphics > Message-ID: <20170108

Bug#800367: installation-report: stretch-testing on NEOWARE m100: no graphics

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There is some improvement visible regarding openchrome video-diver, particularly, there is no xorg.conf necessary any more in order to make use of the VESA-driver, but obviously X falls back to VESA automatically, which is positive in my opinion,

Bug#848304: marked as done (Installation report for Stretch on cubietruck (armhf))

Your message dated Tue, 20 Dec 2016 07:49:05 +0100 with message-id <20161220064905.ga1...@excalibur.cnev.de> and subject line Re: Bug#848304: Issue resolved has caused the Debian Bug report #848304, regarding Installation report for Stretch on cubietruck (armhf) to be marked as done. This

Bug#848304: Installation report for Stretch on cubietruck (armhf)

ly due to the lack of an appropriate > > kernel module. I have the three files made available for > > debugging by the installer: hardware-summary.txt, syslog.txt, > > and partman.txt and can share them upon request. > > > > Under the theory that waiting a while might allow the > > repository and the kernel to sync, I attempted the installation > > multiple times over the course of several weeks and never got a > > different result, hence this installation report. I also tried > > prior versions of the installer as well as the stable version > > (Jessie) and none that I tried completed successfully. >

Bug#848304: Installation report for Stretch on cubietruck (armhf)

se of several weeks and never got a different result, hence this installation report. I also tried prior versions of the installer as well as the stable version (Jessie) and none that I tried completed successfully. In the past I have successfully installed Debian on the Cubietruck using the sd

Bug#820911: installation-report: Accessibility for visual impaired is broken,, High-Contrast Theme is no longer activated by shortcut

Dear all :), The issue still appears in the Debian Installer Stretch Alpha 8 (on EFI). I don't know how to fix this issue myself so I think at this time we have two options : - Change the Debian installation guide to help visual-impaired to activate the ncurse or graphical high-contrast

<    1   2   3   4   5   6   7   8   9   10   >