Bug#890192: installation-reports pseudo package

2018-02-11 Thread Chris Dunn
Package: installation-reports

Boot method: https://cdimage.debian.org/cdimage/buster_di_alpha2/amd64/iso-dvd/debian-buster-DI-alpha2-amd64-DVD-1.iso
Date:  4th February 04.00am

Machine:  Chuwi Hi12 tablet
Processor: Intel Atom x5-Z8350 (-MCP-)
Memory: 3854.8MB
Partitions: 

sysfs  sysfs  0 0 0- /sys
proc   proc   0 0 0- /proc
udev   devtmpfs1.9G 0  1.9G   0% /dev
devpts devpts 0 0 0- /dev/pts
tmpfs  tmpfs   386M   12M  375M   3% /run
/dev/mmcblk0p2 ext4 53G   11G   40G  22% /
securityfs securityfs 0 0 0- /sys/kernel/security
tmpfs  tmpfs   1.9G 0  1.9G   0% /dev/shm
tmpfs  tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs  tmpfs   1.9G 0  1.9G   0% /sys/fs/cgroup
cgroup cgroup20 0 0- /sys/fs/cgroup/unified
cgroup cgroup 0 0 0- /sys/fs/cgroup/systemd
pstore pstore 0 0 0- /sys/fs/pstore
efivarfs   efivarfs   0 0 0- /sys/firmware/efi/efivars
cgroup cgroup 0 0 0- /sys/fs/cgroup/cpuset
cgroup cgroup 0 0 0- /sys/fs/cgroup/net_cls,net_prio
cgroup cgroup 0 0 0- /sys/fs/cgroup/blkio
cgroup cgroup 0 0 0- /sys/fs/cgroup/memory
cgroup cgroup 0 0 0- /sys/fs/cgroup/pids
cgroup cgroup 0 0 0- /sys/fs/cgroup/devices
cgroup cgroup 0 0 0- /sys/fs/cgroup/freezer
cgroup cgroup 0 0 0- /sys/fs/cgroup/perf_event
cgroup cgroup 0 0 0- /sys/fs/cgroup/cpu,cpuacct
systemd-1  autofs 0 0 0- /proc/sys/fs/binfmt_misc
mqueue mqueue 0 0 0- /dev/mqueue
hugetlbfs  hugetlbfs  0 0 0- /dev/hugepages
debugfsdebugfs0 0 0- /sys/kernel/debug
/dev/mmcblk0p1 vfat511M  256K  511M   1% /boot/efi
tmpfs  tmpfs   386M   20K  386M   1% /run/user/1000
Output of lspci -nn:

00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium
Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register
[8086:2280] (rev 36)
00:02.0 VGA compatible controller [0300]: Intel Corporation
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI
Configuration Registers [8086:22b0] (rev 36)
00:03.0 Multimedia controller [0480]: Intel Corporation
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging
Unit [8086:22b8] (rev 36)
00:0b.0 Signal processing controller [1180]: Intel Corporation
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power
Management Controller [8086:22dc] (rev 36)
00:14.0 USB controller [0c03]: Intel Corporation Atom/Celeron/Pentium
Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller [8086:22b5]
(rev 36)
00:16.0 USB controller [0c03]: Intel Corporation Device [8086:22b7] (rev 36)
00:1a.0 Encryption controller [1080]: Intel Corporation
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted
Execution Engine [8086:2298] (rev 36)
00:1f.0 ISA bridge [0601]: Intel Corporation Atom/Celeron/Pentium
Processor x5-E8000/J3xxx/N3xxx Series PCU [8086:229c] (rev 36)

Base System Installation Checklist:
 [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [0]
Detect network card:[0]
Configure network:  [0]
Detect CD:  [0]
Load installer modules: [0]
Detect hard drives: [0]
Partition hard drives:  [0]
Install base system:[0]
Clock/timezone setup:   [0]
User/password setup:[0]
Install tasks:  [0]
Install boot loader:[0]
Overall install:[0]

Comments/Problems:

I believe (from memory) that the configure network took more than one try
and on a first installation (of 2) the install tasks page did not show up.

Second install was fine.

 

I used guided partitioning of the whole disk and was a little surprised

to be offered 1mb + 500+mb + balance to / + 4?gb swap + 1mb

Some explanation of the offering would have been useful.

The grub install options were somewhat alarming and I copped out and installed

grub to a separate partition but still wonder if this was necessary


Re: help - vanishing keyboard

2006-12-05 Thread Chris Dunn
On Mon, 04 Dec 2006 13:48:54 +0100

sferriol [EMAIL PROTECTED] wrote:

 hello
 i have no usb keyboard, so can you test the following images:
 http://www-timc.imag.fr/Sylvain.Ferriol/debian/d-i/i386/current
 
 there are no usb drivers in boot floppy, so you have 30 seconds to 
 change the boot floppy to the root floppy.
 
 and after your keyboard will be activated
 
 thanks
 sylvain
 
First class.

I had a bad root.img floppy first time around so left the boot
root after 30 seconds message running while I burnt another one, on
another box. Inserted the new root floppy and it booted without problem.

I was then able to use the usb keyboard and ultimately exit the install
using the keyboard without any problems.

Thanks for the consideration.
 
Chris Dunn
-
PO Box 1027, Providenciales, Turks and Caicos Islands
telephone : 1 (649) 941 5406
fax :   1 (649) 941 5406
mobile :1 (649) 231 0231
Tue Dec  5 18:31:00 EST 2006
-


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



Re: help - vanishing keyboard

2006-11-22 Thread Chris Dunn
On Tue, 21 Nov 2006 11:04:21 -0500
Douglas Tutty [EMAIL PROTECTED] wrote:

 On Tue, Nov 21, 2006 at 10:24:37AM +0100, sferriol wrote:
  Chris Dunn a ?crit :
  I'm trying (hard) to install Testing or Etch on a Stylistic 3500 tablet.
  
  Sarge installed successfully, but I'm having problems with the boot /
  root diskettes on Testing / Etch.
  
  The Stylistic has an external Fujitsu floppy drive connected, and I
  have a USB keyboard connected.
  
  etch installer uses 2.6 kernel instead of sarge (2.4)
  and the 2.6 kernel is really bigger than 2.4 so we can not put usb 
  keyboard drivers on the boot floppy.
  So etch installer with floppies does not longer support usb keyboard and 
  usb floppy driver, sorry :(
  may be we will try to find a solution but i think it will be after etch 
  release
  
  for you, the only solution is to install a minimal sarge and after 
  upgrade to etch
  
 
 Does the tablet have a serial port which you could use as a serial
 console (using either a terminal or other computer) for the install?
 

Thanks for the input, but no serial port. 

The box has an onboard network card, but unfortunately the card is only
accessible when connected to the separate dock which I lack.

 
Chris Dunn


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