Your message dated Tue, 4 Mar 2014 14:56:25 +0100
with message-id <20140304135625.gc5...@mraw.org>
and subject line Bug#709534: installation-reports: amd geode hardware netinst
failure
has caused the Debian Bug report #709534,
regarding amd geode hardware netinst failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
709534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Boot method: <How did you boot the installer? = network via USB
Image version: <Full URL to image you downloaded is best>
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
Date: 5-23-2012 3pm
Machine: DT Research WebDT366 "AMD Geode SOC"
Processor: Geode LX800
Memory: 512MB RAM
Partitions: one root partition on a 4gb ide dom
Output of lspci -knn (or lspci -nn):
Base System Installation Checklist: installer would not install base system
Initial boot: [x ]
Detect network card: [x ]
Configure network: [x ]
Detect CD: [ ] no cd drive
Load installer modules: [x ]
Detect hard drives: [x ]
Partition hard drives: [x ]
Install base system: [o ]
Clock/timezone setup: [x ]
User/password setup: [x ]
Install tasks: [o ]
Install boot loader: [o ]
Overall install: [o ]
Comments/Problems: Looking at tty4 I see that the key pulled did not
match signature. Errors are every ten lines or so indicating libgcc1
was not found and it was needed to check the public key. debbootstrap
failed on generic description and the rest should be pretty easy as we
cant pass go until the public key resolved. Also see mentions that
apt-setup-udeb failed.
When downloading installer components I elected every single one. Not
sure if that is bad practice or not.
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.> If libgcc1 and
apt-setup-udeb were accessible during the installer routines I feel
that this may have gone smoother.
--- End Message ---
--- Begin Message ---
Control: retitle -1 installation-reports: amd geode hardware netinst failure
Hi,
daryl kuchay <daryl.kuc...@gmail.com> (2013-05-23):
> Boot method: <How did you boot the installer? = network via USB
> Image version: <Full URL to image you downloaded is best>
> http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
> Date: 5-23-2012 3pm
>
> Machine: DT Research WebDT366 "AMD Geode SOC"
> Processor: Geode LX800
> Memory: 512MB RAM
> Partitions: one root partition on a 4gb ide dom
>
> Output of lspci -knn (or lspci -nn):
>
> Base System Installation Checklist: installer would not install base system
>
>
> Initial boot: [x ]
> Detect network card: [x ]
> Configure network: [x ]
> Detect CD: [ ] no cd drive
> Load installer modules: [x ]
> Detect hard drives: [x ]
> Partition hard drives: [x ]
> Install base system: [o ]
> Clock/timezone setup: [x ]
> User/password setup: [x ]
> Install tasks: [o ]
> Install boot loader: [o ]
> Overall install: [o ]
>
> Comments/Problems: Looking at tty4 I see that the key pulled did not
> match signature. Errors are every ten lines or so indicating libgcc1
> was not found and it was needed to check the public key. debbootstrap
> failed on generic description and the rest should be pretty easy as we
> cant pass go until the public key resolved. Also see mentions that
> apt-setup-udeb failed.
>
>
> When downloading installer components I elected every single one. Not
> sure if that is bad practice or not.
>
> <Description of the install, in prose, and any thoughts, comments
> and ideas you had during the initial install.> If libgcc1 and
> apt-setup-udeb were accessible during the installer routines I feel
> that this may have gone smoother.
I suspect you might have hit a transient issue after the wheezy release.
I'd suggest using released wheezy installation images, or waiting for an
official jessie alpha image (current weekly testing images have some
nasty, known bugs). On that basis I'm closing this installation report,
feel free to reopen if you can reproduce with a wheezy image (if so,
please tell us which, and attach /var/log/syslog).
Thanks for the report anyway.
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
