-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.63
Severity: normal
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 effecti
with
> OpenChrome,
> you may want to download, compile, and install the latest OpenChrome code.
> This post I
> made while back is very detailed, so you should not have issues installing
> the latest
> OpenChrome code.
>
> https://lists.freedesktop.org/archives/opench
-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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It probably does not make much sense to keep old wishlist-items.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlhSfVYACgkQ5+rBHyUt5wvR4ACgsr4OM0J5nYZika9Ogq2O2qPY
IZQAoKWfcBw47bNdZDEZVQcfRI2yzwE/
=BDAE
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Not using this box anymore, since unexpectedly it worked without any major
problem to
port the EWP-appliance to FreeBSD 10.3.
Currently making a clean KVM-image of XEWP in KVM/virt-manager.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEAREC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.62
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 effec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://savannah.gnu.org/bugs/?43379
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlcrTssACgkQ5+rBHyUt5wsFmACeMxkpcBkfZaCkzpd7zgS+sAlT
O8IAn05Qp+dUe/mPwk/CrQZf6UA7tPuQ
=am2+
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I retried this with the current netinstall-image from 2016-05-02,
using the internal ATA-flash-memory of the PC as /boot/-partition, but it
doesn't work
either, since GRUB cannot mount the filesystem-root.
It might be related to these upstream-
-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-
-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 w
-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
iEYEARECAAYFAlcHtpIACgkQ5+rBHyUt5
-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 to
-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 think of.
>
> "No
int to the installation-report.
Greetings
Andreas
On Wed, 6 Apr 2016 10:06:34 +0200
Andreas Glaeser wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> Begin forwarded message:
>
> Date: Tue, 5 Apr 2016 12:08:08 -0700
> From: Andrew Kurn
> To: b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Begin forwarded message:
Date: Tue, 5 Apr 2016 12:08:08 -0700
From: Andrew Kurn
To: bugs.andreas.glae...@freenet.de
Subject: Re: Bug#755230 closed by Andreas Glaeser
Thanks for your attention to this matter.
I agree with you that there is no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 2 Apr 2016 15:40:48 +0100
Steve McIntyre 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
> >to boot my
&g
-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 effectiv
6 14:06:46 +0200
From: Andreas Glaeser
To: debian-boot@lists.debian.org
Cc: "Lennart Sorensen"
Subject: 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" wro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 31 Mar 2016 11:43:24 -0400
"Lennart Sorensen" wrote:
> On Thu, Mar 31, 2016 at 09:57:51AM +0200, Andreas Glaeser wrote:
> > /dev/sdc1 was my -boot-partition from a previous attempt with BTRFS, as I
> > installed
&g
-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 (since they are inherently so un
-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 BTRFS-par
-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 network-storage,
-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" missed!
-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 effectiv
-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 only.
-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:
http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing
-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 effectiv
-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 effectiv
-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: application/g
-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 w
-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:
-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
-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:
http://cdimage.debian.org/debi
-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)
-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:
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-
-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:
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-c
-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 c
-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.
Runn
-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
-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 othe
-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-
Ve
-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: application/xz
-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
-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 DVD-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> From: Paul Wise
> To: Andreas Glaeser , 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: Evolution 3.12.7
-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 ze
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 30 Sep 2014 12:17:52 +0200
Cyril Brulebois wrote:
> Andreas Glaeser (2014-09-30):
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Package: installation-reports
> > Version: 2.57
> > Se
-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
-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 e
-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 (GNU/Li
-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 effectiv
-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 orig
-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
-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
4iUAnRXo4O05+HRHfwI4IOoFIq81EBc
-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:
http://cdimage.debian.org/debian-cd/7.4.0/i386/iso-cd/d
-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 effec
-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 effec
-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
-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:
http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray
Instructions to install De
st:~$ reportbug 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 ' as your from address.
Getting status for installation-report...
Checking for newer ver
-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
-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
-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
-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
-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
-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)
iEYEARECAAYFAlGI
-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-
-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 curren
-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
-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
-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
-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
-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)
iEYEARECAAYFAlEOk4wACgkQ5+rBHy
-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
-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 pinnin
-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
-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 co
-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
-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 XFCE
-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
-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
-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 Zip
-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:
http://hammurabi.acc.umu.se/debian-cd/6.0.6/i386/iso-cd/debian-6.0.6-i386-xfc
On Tue, 23 Oct 2012 21:33:26 +0200
Julien Cristau 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 21 Aug 2012 11:11:22 +0100
Brian Potkin 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-se
-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
-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: 2012-08-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 07 Aug 2012 13:31:28 +0200
Gaudenz Steinlin wrote:
>
> Hi Andreas
>
>
> Andreas Glaeser writes:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > To check if btrfs is really slo
-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 blocks.
-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: 2012-0
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 bo
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 debian-boot-requ...@lists.debian
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
xorg.conf.new.bz2
Description: application/bzip
Xorg.0.log.bz2
Description: application/bzip
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
Par
inst-report see attachment
reportbug-installation-report-20120321.txt.bz2
Description: application/bzip
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 thi
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
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 10
1 - 100 of 108 matches
Mail list logo
