Package: installation-reports

Boot method: USB
Image version: 
http://d-i.debian.org/daily-images/amd64/daily/hd-media/boot.img.gz, 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-businesscard.iso

I have set up the USB pendrive as follows: 

>>>>>
# Change this to identify the device of your USB pendrive. Check twice!
dev='/dev/disk/by-id/usb-PNY_ATTACHE_PRO_07750E180008-0:0';

# USB pendrive image.
boot='http://d-i.debian.org/daily-images/amd64/daily/hd-media/boot.img.gz';

# Installer ISO image.
iso='http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-businesscard.iso';

curl -L "$boot" | gunzip > "$dev"; 
mount "$dev" /media/usb; 
pushd /media/usb; 
curl -OL "$iso";
popd;
umount "$dev";
<<<<<

Booting with the pendrive plugged in hangs after showing the message

  (process:1067): INFO: kbd-mode: setting console mode to Unicode (UTF-8)

, and if I add the "nopat" option, the machine hangs or after displaying the
language selection dialog. I have tried the following options on the boot
prompt:

  install
  install nopat
  install noapic nolapic
  install nopat noapic nolapic


Since installation hangs that early, I only can provide data gathered at a
previous attemt with a different (stupid) pendrive setup:

*** NOTE: data below gathered on the same machine, with *different*
*** installation media setup!

hardware-summary 
<http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=hardware-summary;att=1;bug=548705>
lsb-release 
<http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=lsb-release;att=3;bug=548705>
syslog 
<http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=syslog;att=5;bug=548705>



-- 
Stefan Klinger                                      o/klettern
                                                    /\/  bis zum
send plaintext only - max size 32kB - no spam         \   Abfallen
http://stefan-klinger.de



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to