[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#263206: mips-netboot

Package: installation-reports

Debian-installer-version: http://people.debian.org/~tbm/d-i/images/mips/2004-07-25/r4k-ip22/netboot-boot.img 
uname -a: Linux nn126 2.4.25-r4k-ip22 ... mips unknown
Date: 3.8.1004 10:50
Method: netboot

Machine: SGI Indy
Processor: R4600 V2.0
Memory: 60 MB
Root Device: /dev/sda1
Root Size/partition table: 
Disk /dev/sda (SGI disk label): 33 heads, 62 sectors, 1011 cylinders
Units = cylinders of 2046 * 512 bytes

----- partitions -----
Pt#     Device  Info     Start       End   Sectors  Id  System
 1:  /dev/sda1  boot         5      1010   2058276  83  Linux native
 9:  /dev/sda2               0         4     10230   0  SGI volhdr
11:  /dev/sda3               0      1010   2068506   6  SGI volume
----- Bootinfo -----
Bootfile: /unix
----- Directory Entries -----
 0: arcboot    sector    4 size   67392

Output of lspci:
	Very funny.

Base System Installation Checklist:

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [O]
Detect CD:              [ ]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [ ]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [E]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it


- partitioning:
I'm dropped in fdisk for partitioning, so that should all work.
(Assumed the person installing knows what type of partition
table to install. Some information screen about that would be

- rebooting
when preparing to reboot it says:
Saving installation logs to /var/log/debian-installer/...E: Inimplemented function
and stops. When killing the process from the second console, it continues normaly.

After rebooting is asked some questions (like hostname and mirror) again.

- minor points:

The shell triggering this frame-buffer bug is a bit incommoding.
(When one is in the last line and using tab or the arrow up, the screen
is blanked. (When chrooting into the installed system,
that does not have that problem).) Having a clear command available
would be a great workaround for this.

Reply to: