On Wed, May 11, 2016 at 05:32:17AM +0200, Cyril Brulebois wrote:
> [ Poke Steve. ]
>
> Andreas Bombe (2016-05-11):
> > On Tue, May 10, 2016 at 02:15:42PM +0200, Andreas Bombe wrote:
> > > Since 416 blocks is a rather odd value, the default is used and that has
> >
On Tue, May 10, 2016 at 02:15:42PM +0200, Andreas Bombe wrote:
> Since 416 blocks is a rather odd value, the default is used and that has
> changed. I think mtools is overzealous in checking those values and
> refusing to work. Still, it probably makes sense to use 64/32 as the
>
On Tue, May 10, 2016 at 01:53:24AM +0200, Cyril Brulebois wrote:
> The version bump from 3.0.28-2 to 4.0-1 led to a new FTBFS on all EFI
> archs for debian-installer (amd64, arm64, i386), where the following
> operations are happening:
> | + mkfs.msdos -C ./tmp/netboot-gtk/grub_efi/efi.img 416
> |
Package: installation-reports
Severity: normal
-- Package-specific info:
Boot method: USB stick
Image version: 20141116-5/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 2014-11-16
Machine: Lenovo ThinkPad X1 Carbon (current 20A7 model)
Partitions:
Dateisystem Typ 1K-Blöcke
0-4-sparc64
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Andreas Bombe
--
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/20130122230421.ga6...@amos.fritz.box
Package: os-prober
Version: 1.56
Followup-For: Bug #685159
The bug is caused by using GRUB's internal filesystems through FUSE
which doesn't support symlinks (at least not on ext4). This filesystem
is only used when the volume is not already mounted, therefore this bug
does not appear when the vol
a Sun Ultra 10, but that displays the
offset while it is loading. I got "a0 Fast Data Access MMU Miss"
which means the limit is exactly 10 MB. Presumably this limit has stayed
the same for a long time.
--
Andreas Bombe
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.deb
at you can still see the broken Slackware install
afterwards.
> Also: How do I subscribe?
You could go to http://lists.debian.org/debian-boot/ and subscribe
there, although this list is mostly about developing the Debian
installer and probably not that interesting to the average user.
--
Andr
before.
How did you choose the disk to install to in order to be sure that you
selected the correct one? By looking at the previous partitioning, the
disk size, something else?
--
Andreas Bombe
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "un
On Sun, Sep 04, 2011 at 02:33:44PM -0300, Otavio Salvador wrote:
> On Wed, Aug 31, 2011 at 21:26, Andreas Bombe wrote:
> > Initial boot was somewhat problematic, as the system appeared to freeze
> > after a
> > few lines of kernel output. Since keys such as Caps and Num Lo
Package: installation-reports
Severity: normal
-- Package-specific info:
Boot method: network
Image version:
http://ftp.halifax.rwth-aachen.de/debian/dists/squeeze/main/installer-sparc/current/images/netboot/boot.img
Date: 2011-08-30
Machine: Sun Ultra 10
Partitions:
FilesystemType 1K-
Package: installation-reports
Severity: normal
-- Package-specific info:
Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
2009-01-01
Date: 2009-01-01
Machine: Asus P5Q board / Core 2 Duo E8500 / 4GB
12 matches
Mail list logo
