Bug#661792: installation-report: wheezy installed on Quicksilver mac by upgrading from stable

Package: installation-reports Version: 2.45 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of

Bug#596454: installation-report: debian-testing on P4 system

Package: installation-reports Version: 2.42 Severity: wishlist *** Please type your report below this line *** -- Package-specific info: Boot method: CD Image version: 2010-08-30 from http://hammurabi.acc.umu.se/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-CD-1.iso Date: 2010-09-11,

Bug#596454: Additional hard- and software-information

To make the picture more complete, you receive attached to this e-mail, an unsent bug-report from about one year ago concerning an analog bttv tv card, which did not work with zapping. That problem was fixed in testing. In the meantime it turned out that the card prevents my usb connected canon

Bug#751000: Installation in Virtualbox works now with EFI

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Installation in Virtualbox works now with EFI and UEFI-GPT partitioning, but the system is not bootable then. It shows a black screen and a fully loaded CPU instead of booting up correctly. I have no idea, how to fix this, because I have hardly any

Bug#763426: installation-report: installed system not bootable by default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.57 Severity: normal Dear Maintainer, The installed system was not bootable upon installation, but grub could be installed manually: root@s5:/home/andrew# fdisk -l . .. .. . Disk /dev/sdc: 15.9 GB,

Bug#763426: installation-report: installed system not bootable by default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 30 Sep 2014 12:17:52 +0200 Cyril Brulebois k...@debian.org wrote: Andreas Glaeser bugs.andreas.glae...@freenet.de (2014-09-30): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.57 Severity

Bug#764361: installation-report: XFS filesystem fails to upgrade from kernel 3.2 to 3.16

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

Bug#763426: current netinstall-image is not workable for me either

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I retried this today with XFS and ext4, the former failed very early at bootstrapping the base system, the latter failed at setting up the kernel, towards the end of the process. It is also kind of strange, that 'lastlog' and 'faillog' consist of

Bug#763426: D-I in Jessie

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 From: Paul Wise p...@debian.org To: Andreas Glaeser bugs.andreas.glae...@freenet.de, 763...@bugs.debian.org Subject: Re: Bug#763426: installation-report: installed system not bootable by default Date: Mon, 20 Oct 2014 15:54:59 +0800 X-Mailer

Bug#763426: GRUB-installation for Jessie/Testing beta

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Today I tried this image: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso from 2014-10-27 It did not boot from CD, only from USB, apart from this the situation is unchanged, but it may be my

Bug#769778: installation-report: Testing set up by upgrading Stable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.49 Severity: normal Dear Maintainer, Debian-Testing is still not installable for me only expert-installation is possible (because of IPv6?) and then it failed at the step of installing tasks, so I set it up

Bug#769778: DSDT table dissasmbled of HP t5735

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [see attachment: DSDT.dsl.xz] -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlR5cWgACgkQ5+rBHyUt5wuLOACgnlJknSuh5qw298OlSQD+tnNZ KOUAoIm4bc5mqk5bFgMNG73FvURMlov+ =3od8 -END PGP SIGNATURE- DSDT.dsl.xz Description:

Bug#612184: installation-report: Stable release of squeeze on Dell Optiplex GX 150

Package: installation-reports Version: 2.44 Severity: wishlist -- Package-specific info: Boot method: CD Image version: debian-6.0.0-i386-CD-1.iso downloaded through http://cdimage.debian.org/debian-cd/6.0.0/i386/bt-cd/debian-6.0.0-i386-CD-1.iso.torrent, date: 2011-02-06 Date: 2011-02-06, from

Bug#623139: Harddisk names still exchange from install-time to post-install

Package: installation-reports Version: 2.44 Severity: minor -- Package-specific info: Boot method: Image version: debian-6.0.1a-i386-CD-1.iso Date: 2011-04-07 Machine: Asus_P4-GE-FSC Partitions: Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units

Bug#691147: installation-report: FSC_Futro_S300 set up with Wheezy beta

On Tue, 23 Oct 2012 21:33:26 +0200 Julien Cristau jcris...@debian.org wrote: On Mon, Oct 22, 2012 at 09:24:27 +0200, Andreas Glaeser wrote: This installation went quite fine, but I had the debian-desktop-environment installed on this box and wondered in the end, that it was Gnome3

Bug#693141: installation-report: XFCE-variant of Squeeze installed on FSC-Futro-S300 w/ backports

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.44 Severity: wishlist *** Please type your report below this line *** - -- Package-specific info: Boot method: USB Image version:

Bug#693141: cpufreqd.conf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 see attachment -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlCiYr4ACgkQ5+rBHyUt5wtA/QCfQwDJrvB9vlddCkV5O8YVZBM9 K7cAoI9tne2NVeVmefapirlqAxWk/nT0 =advI -END PGP SIGNATURE- cpufreqd.conf.gz Description: GNU

Bug#694344: installation-report: Wheezy beta set up on FSC Futro S400

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

Bug#695454: installation-report: Wheezy beta set up using a root-filesystem on an SD-flashdisk

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

Bug#694344: Device does not work with 'linux-image-686-pae', but it is the default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First there were intermittent bootproblems, then more often and finally the box would not boot anymore at all. I tried all kinds of BIOS-settings changes, but could not resolve the situation, began to feel desperate already. Then I installed the

Bug#697265: installation-report: Wheezy beta set up with GA-MA-78GM-S2H Mainboard

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

Bug#697265: Corresponding Xorg.0.log

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 see attachment -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlDlOMsACgkQ5+rBHyUt5wv8TwCgodwrSt4Q2vdvJmLBhpcClI5w qQQAoIknLqiRpfkOI56iYDdicKHqH5Jg =65CO -END PGP SIGNATURE- Xorg.0.log.gz Description: GNU Zip

Bug#698542: installation-report: Wheezy beta on FSC Futro A240

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

Bug#699156: debian-installer: d-i should offer users the installation of backported packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: debian-installer Version: 20110106+squeeze4+b2 Severity: wishlist *** Please type your report below this line *** When I set up a new i486-system (i.e.32-bit-PC) yesterday, I had to add backported packages manually and take care about

Bug#699691: installation-report: Wheezy beta set up on FSC Futro S450

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

Bug#694344: Boot-problems not limited to PAE-kernels, but as ageneral regression in 3.x-series kernels

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This issue was tested with the latest 3.8-rc-series Ubuntu-kernel and reported formally here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1107909 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux)

Bug#701694: installation-report: Wheezy set up newly using AMD-64 architecture now

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

Bug#703838: installation-report: Wheezy-beta-rc on fixed AMD64-mainboard

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

Bug#703904: installation-report: Wheezy-beta-rc on diskless Thinkpad-T4_

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

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

-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

Bug#701694: New 3.8 experimental kernel-version built

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yesterday I slightly reconfigured the 3.9 kernel source on this box as embedded low-latency-desktop and disabled a few unneeded drivers and was a bit surprised that this actually built just fine and the result is running more nicely, too. So my

Bug#661792: System reinstalled with basically the same method

inst-report see attachment reportbug-installation-report-20120321.txt.bz2 Description: application/bzip

Bug#673274: installation-report: Wheezy installed for testing purposes

Package: installation-reports Version: 2.46 Severity: wishlist -- Package-specific info: Boot method: CD Image version: http://caesar.acc.umu.se/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-CD-1.iso Date: 2012-05-17, 14:00 h Machine: custom-built with 'AMD690GM-M2 PLUS' Mainboard

Bug#673274: attachments

xorg.conf.new.bz2 Description: application/bzip Xorg.0.log.bz2 Description: application/bzip

Bug#674855: hardware-information

see here: http://kmuto.jp/debian/hcl/DELL/Optiplex+740 -- 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/20120529112039.474cfe36@osrdii.lokal

Bug#675004: Other distributions tried

When I tried Linux Mint 13 AMD64 (Cinnamon) today, that failed to boot, too, rebooted at some point during startup. Ubuntu 12.04 AMD64 started as live-CD and was installable from this mode, a report was filed as Ubuntu-bug #1009385 -- To UNSUBSCRIBE, email to

Bug#661792: NVidia graphics card removed - change in the situation

The computer practically was not usable anymore at all, uprganding from stable to testing, as described and done before, failed, too, recently. Upon retrying to boot Fedora-17-ppc and freebsd9-ppc, I decided to remove the NVidia-adaptor. This led to the unexpected situation that I was able to

Bug#683773: installation-report: Wheezy installed three times on G4-PowerMac

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.47 Severity: normal - -- Package-specific info: Boot method: CD Image version: http://hammurabi.acc.umu.se/cdimage/weekly-builds/powerpc/iso-dvd/debian-testing-powerpc-DVD-1.iso from 2012-07-30 Date:

Bug#683773: btrfs-write-performance rechecked, downgrading the severity to 'wishlist'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 To check if btrfs is really slow I tried the following: - -# aptitude install btrfs-tools - -created a btrfs-partition as /dev/sdb14 with gparted and aligned it to sector, not to mbr, because the harddisk is an advanced format model with 4096k

Bug#683773: btrfs-write-performance rechecked, downgrading the severity to 'wishlist'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 07 Aug 2012 13:31:28 +0200 Gaudenz Steinlin gaud...@debian.org wrote: Hi Andreas Andreas Glaeser bugs.andreas.glae...@freenet.de writes: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 To check if btrfs is really slow I tried

Bug#685127: installation-report: Wheezy beta installed on AMD64, network setup failed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.47 Severity: normal Dear Maintainer, - -- Package-specific info: Boot method: DVD Image version: http://hammurabi.acc.umu.se/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso Date:

Bug#685367: installation-report: Wheezy beta installed on powermac g4 900 MHz w/ ATI rage graphicscard

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

Bug#685367: installation-report: Wheezy beta installed on powermac g4 900 MHz w/ ATI rage graphicscard

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 21 Aug 2012 11:11:22 +0100 Brian Potkin claremont...@gmail.com wrote: On Mon 20 Aug 2012 at 11:46:37 +0200, Andreas Glaeser wrote: The Installation went OK, but the graphical XFCE-Desktop was not usable, because the x-server

Bug#595052: Successfull installation of Squeeze base system from single cd without network mirror on low memory PIII System

Package: installation-reports Version: 2.41 Severity: wishlist -- Package-specific info: Boot method: CD Image version: Debian GNU/Linux Squeeze testing i386 Date: about 2010-08-21 Machine: Siemens Scenic 600 Partitions: df -Tl will do; the raw partition table is preferred Filesystem

Bug#694344: One more installation done on this machine, boot-problems fixed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 please see attached draft installation-report.txt.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlFqakgACgkQ5+rBHyUt5wtBlACgkI1+QwmjLAFtGlDC3qlpQckY gt4AoI7h+91cMcsJldP0xNcTAQDZrAS2 =Cs5A -END PGP SIGNATURE-

Bug#703904: XFCE4-terminal issue was reported before

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I reported the XFCE-terminal-issue against package xfce4-terminal as 695...@bugs.debian.org, but it was closed very quickly, reopening does not seem to be possible now. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux)

Bug#712490: installation-report: Wheezy stable set up on eMachines E725 notebook for testing purposes

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

Bug#723635: installation-report: MDADM filesystem-root set up by reinstalling

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

Bug#723635: kern.log.xz attached (two internal USB-ports dead already)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlJ4+SYACgkQ5+rBHyUt5wsNtwCfWtj6JM4KhkJRdwH8StuFmtD1 KKgAn1VVOz2wrjFdQHmPidgZAtxSESEt =OtxG -END PGP SIGNATURE- kern.log.xz Description: application/xz

Bug#732060: installation-report: Jessie testing on FSC Futro S400

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

Bug#733337: installation-report: Jessie testing set up on FSC Futro S 500 thinclient

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

Bug#734056: installation-report: GNU/kFreeBSD on AMD64 'reportbug installation-report' is impossible

installation-report Warning: no reportbug configuration found. Proceeding in novice mode. Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Andreas Glaeser andreas@localhost' as your from address. Getting status for installation-report... Checking for newer versions

Bug#728948: Detailed installation-instructions for Wheezy on Pogoplug

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sources: Our Debian-installation started from Arch-Linux, which could be booted on the Pogoplug-device already. This was installed following these instructions: link http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray /link Instructions to

Bug#736922: installation-report: Wheezy/stable reinstalled on main AMD64-machine with Level1 MD-RAID

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

Bug#741601: installation-report: Jessie/testing on IGEL 4200 thin-client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.55 Severity: wishlist 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#745240: installation-report: Jessie alpha on FSC Futro S550 thin-client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.55 Severity: wishlist 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#745494: installation-report: Wheezy/stable on IGEL M300c thin-client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.49 Severity: wishlist Dear Maintainer, this installation went fine, not quite as expected. - -- Package-specific info: Boot method: USB Image version:

Bug#745416: The problem does not seem to have to do anything with the installer itself

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It was reported already there: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743360 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlNXaRAACgkQ5+rBHyUt5ws9VQCeOHyLHwFghCGva0JEoLnjufkA

Bug#745240: ACPI-tables from FSC Futro S500

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I submit the ACPI-tables from FSC Futro S500 with Athlon l310 CPU @ 2x1.2 GHz now, which has almost the same mainboard as Futro S550. I also disassembled the DSDT-table and attach this too. [tables.tar.bz] and [DSDT.dsl.bz2] These were read out from

Bug#745240: ACPI-tables from FSC Futro S450

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 See attachments: [tables.tar.bz2] and [DSDT.dls.xz] These were ripped from the FSC Futro S450, but this time with the original CPU, that runs at 800 MHz or 1600 MHz, depending on the load, but it turned out, that the board only does so with the

Bug#751000: Jessie-testing set up in KVM/virt-manager

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.55 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#751000: Hardware-Information for virtual environment in Virtualbox

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 see attachments [dmsg.txt.xz] and [hw-rep.txt.xz]. I chose the ICH9-chipset there and ICH6 for storage and enabled bridged networking in order to be able to export the information using NFS. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12

Bug#598924: Cross-installation of testing-release on PIII - Systems

Package: installation-reports Version: 2.42 Severity: wishlist Cross-installation of testing-release on 'MEDION 2001' -- HP e-Vectra -- Package-specific info: Boot method: cd Image version: testing i386 2010-09-20 Date: Friday, 2010-09-24, about 15.00 h Machine: HP e-Vectra Partitions:

Bug#600621: installation-report: Debian 6.0-beta reinstalled without TV-card

Package: installation-reports Version: 2.42 Severity: wishlist *** Please type your report below this line *** Originally I tried to file this against 596...@bugs.debian.org, but received an error-message from the free mail service I use. So I resend this now as a new bug although there is

Bug#600621: Additional information concerning the tv-card / scanning

Because you left the bug-report open I send you a link about my canon MP270 scanner/printer, i.e. where I found out that actually the TV- card interferes with it.: http://ubuntuforums.org/showthread.php?t=1458531 Before I found that, I tried to contact the german canon-support, but first they

Bug#606033: Squeeze in Oracle VirtualBox version 3.2.10 r66523 under Win_XP on FSC Scenic W600

Package: installation-reports Version: 2.43 Severity: wishlist *** Please type your report below this line *** -- Package-specific info: Boot method: cd Image version: dvd-i386 Date: 2010-11-24, about 10.00h Machine: virtualbox windows xp fsc scenic w600 Partitions: df -Tl will do; the raw

Bug#608126: installation-report: debian squeeze reinstalled once more, harddisk names exchanging

Package: installation-reports Version: 2.43 Severity: minor -- Package-specific info: Boot method: CD Image version: 2010-12-20 from http://hammurabi.acc.umu.se/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-CD-1.iso Date: 2010-12-26, about 17.00 h Machine: Asus_P4-GE-FSC Partitions:

Bug#763426: Retried with i386 version of Testing, situation unchanged

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Because there were news, that there is actually RC1 out of Debian 8-Jessie, I retried installation on i386 architecture today. It went well, but GRUB would not boot the system upon that, situation mostly unchanged. -BEGIN PGP SIGNATURE-

Bug#763426: Non-installable RC1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is the image, I tried today: http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-netinst.iso On the one hand the upgrade-path from stable needs some testing, too, and I tried that already and it worked. On the

Bug#779100: [solved] - done

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The following 40_custom in /etc/grub.d/ fixed the issue for me: #!/bin/sh exec tail -n +3 $0 # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to

Bug#779100: Making the SD-card boot in the internal cardreader is not trivial

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Today I tried this out, making a /boot/ partition on the harddisk and changing /etc/fstab accordingly. It is workable while the card remains in the expresscard-cardreader, but not workable, when it is inserted in the internal mmcblk-cardreader.

Bug#779100: Wheezy stable on Dell Latitude E 4300 including backports

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

Bug#782333: Server-Kernel built for VIA-Nano thin-client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am using this box currently as a bittorrent-seeder with qbittorrent-nox. The web-interface is nice. Today I built an embedded-server kernel for it. It seems to be doing quite well so far, but there were problems with the Sandisk-Ultra-USB3 (32GB)

Bug#783949: installation-report: Jessie-release-i386 set up on VIA-eden-homeserver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.58 Severity: wishlist Dear Maintainer, this is only a wishlist-item, you may also think of it as a success-story. - -- Package-specific info: Boot method: USB Image version:

Bug#783949: making good progress

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Today I built a kernel-image for this box, it is doing well, as far as I can tell. Some research was necessary to find out, how o cross-compile for i386 on AMD64. This is how I did it: $ make ARCH=i686-PAE -j6 deb-pkg LOCALVERSION=-es-via-c7 doing

Bug#782757: installation-report: Jessie-RC-AMD64 on my build-PC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.58 Severity: wishlist Dear Maintainer, This is wishlist only, just some info. - -- Package-specific info: Boot method: USB Image version:

Bug#782378: installation-report: Jessie-RC on DELL notebook

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.58 Severity: wishlist Dear Maintainer, this wa a flawless installation, wishlist only. - -- Package-specific info: Boot method: USB Image version:

Bug#788337: No Graphics on IGEL H 700C thin-client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.58 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#786872: It's possible to use the VESA graphics-driver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First I tried to set up fbdev, but it did not work out for me, then I removed the openchrome-driver using apt-get and generated a new X-configuration: # init 1 # cd /etc/X11 # X -configure # cp /root/xorg.conf.new ./xorg.conf That's all, graphics

Bug#786872: autogenerated xorg.conf for VESA

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 see attachment [xorg.conf.gz] -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlVofrIACgkQ5+rBHyUt5wvBhwCdHHNfiKjdL2jskolZ1kc3/KyT PDkAoLMzxig8rvYGsomEBVJSHYE/9N8o =G1BJ -END PGP SIGNATURE- xorg.conf.gz Description:

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.58 Severity: normal Dear Maintainer, It's another VIA-device without graphics-output, I wished, it would work by default, not the other way around, getting fixes upon request. - -- Package-specific info:

Bug#801511: VESA not workable, VIA-driver not workable either

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I tried to use the VESA-driver, putting [xorg.conf.xz] in place, it was not workable, see [Xorg.0.log.vesa], the VIA-driver does not work for me either: > root@t5550:~/5.76.52.92-l140402_32bit-005f78-20150730# ./vinstall > error: tool "make"

Bug#801511: installation-report: Jessie-stable set up for testing graphics-driver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.58 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#801511: installation-report: no graphics on HP t5550 thin-client w/ stretch-testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.60 Severity: minor Dear Maintainer, graphics are still not workable, see attached file [Xorg.0.log.xz]. I was using a DVI-to-VGA adapter here, because only my main screen is digital, the others are VGA

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.60 Severity: minor Dear Maintainer, I still have to use VESA-graphics. - -- Package-specific info: Boot method: USB Image version:

Bug#800127: installation-report: Jessie stable set up on Biostar a68n-5000 m-ITX mainboard

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.58 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#814088: Be cautious about data-loss !!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This obviously has been a low-priority project, but I have the box basically up and running now. If you have a similar scenario as myself, with an external harddisk with data on it, that you want to integrate into a RAID and use as

Re: Stretch/testing instllable, but not bootable upon installation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 30 Mar 2016 11:08:47 -0400 "Lennart Sorensen" wrote: > /dev/sdc2 sounds odd. I wonder if a USB key confused it about disk > ordering. I also thought everything used UUID to find disks now, not > device names

Bug#755230: closed by Andreas Glaeser

to the installation-report. Greetings Andreas On Wed, 6 Apr 2016 10:06:34 +0200 Andreas Glaeser <bugs.andreas.glae...@freenet.de> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > Begin forwarded message: > > Date: Tue, 5 Apr 2016 12:08:08 -0700 &g

Bug#753947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753947

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What about your report?? Did you still experience any problems, when Jessie was released stable ?? Or with the current testing-branch ?? If you think the problem is resolved in the meanwhile, you can close the ticket yourself by sending E-mail

Bug#762840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762840

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Can you retry with the current stable release or with current debian-testing?? Possibly you need to set the BIOS to legacy mode, some UEFI-implementations are buggy. -BEGIN PGP SIGNATURE- Version: GnuPG v2

Bug#765552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765552

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since your installation-report was from before the Jessie-release, the issue has probably been fixed in the meantime. If so, then please close the report-ticket yourself by sending e-mail to: 765552-d...@bugs.debian.org giving a few explanatory

Bug#819867: bug-report filed against the grub-pc package now

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 see there: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820806 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlcNDUIACgkQ5+rBHyUt5wtdcACgoln5wrsPp2QTy+iZu3jV2XWG fV4AoJEU7MMMDewbKGv4Pq9LkeZZ71Eu =QpyN -END PGP SIGNATURE-

Bug#755230: Fw: Bug#755230 closed by Andreas Glaeser

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Begin forwarded message: Date: Tue, 5 Apr 2016 12:08:08 -0700 From: Andrew Kurn <k...@sfu.ca> To: bugs.andreas.glae...@freenet.de Subject: Re: Bug#755230 closed by Andreas Glaeser Thanks for your attention to this matter. I agree wi

Bug#755230: closed by Andreas Glaeser

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 6 Apr 2016 12:15:57 -0700 Andrew Kurn wrote: > Dear Andreas, > > In my turn, I don't understand how to work around a non-bootable > installer image. Believe me, I booted the way I did because it > was the only way I could

Re: Stretch/testing instllable, but not bootable upon installation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 2 Apr 2016 15:40:48 +0100 Steve McIntyre <st...@einval.com> wrote: > On Sat, Apr 02, 2016 at 04:20:27PM +0200, Andreas Glaeser wrote: > > > >now I dd'ed the raw-image, made in vm-manager, onto my USB-stick and tried

Bug#819867: installation-report: USB-boot fails with Stretch, no GRUB-installation with BTRFS-partition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.62 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

Stretch/testing instllable, but not bootable upon installation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Today I tried already to complain about this at paste.debian.net: > > Debian Stretch testing is currently installable, but it is not bootable, I > tried this several times since last week. First of all GRUB is not > installable on

Re: Stretch/testing instllable, but not bootable upon installation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 31 Mar 2016 11:43:24 -0400 "Lennart Sorensen" <lsore...@csclub.uwaterloo.ca> wrote: > On Thu, Mar 31, 2016 at 09:57:51AM +0200, Andreas Glaeser wrote: > > /dev/sdc1 was my -boot-partition from a previous

Fw: Stretch/testing instllable, but not bootable upon installation

+0200 From: Andreas Glaeser <bugs.andreas.glae...@freenet.de> To: debian-boot@lists.debian.org Cc: "Lennart Sorensen" <lsore...@csclub.uwaterloo.ca> Subject: Re: Stretch/testing instllable, but not bootable upon installation - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On

  1   2   >