--- Begin Message ---
Package: installation-reports
Debian-installer-version: http://http.us.debian.org/debian/dists/testing/main/installer-sparc/current/images/sparc32/netboot/boot.img (beta4)
uname -a: Linux limey 2.2.19 #1 Mon Apr 2 13:29:46 EDT 2001 sparc unknown (clock is wrong)
Date: 7th June 2004
Method: netboot
Machine: SparcStation 2
Processor: Fujitsu or Weitek Power-UP
Memory: 48Mb
Root Device: SCSI
Root Size/partition table: N/A
Output of lspci: N/A
Base System Installation Checklist:
Initial boot worked: [E]
Configure network HW: [ ]
Config network: [ ]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Create file systems: [ ]
Mount partitions: [ ]
Install base system: [ ]
Install boot loader: [ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
Machine appears to lock up after downloading the image via tftp from one of my servers. I've repeated this many times, each with the exact same failure.
After downloading the image it says:
bootmem_init: Scan sp_banks, init_bootmem(spfn[27a],bpfn[3c7],mlpfn[3000])
free_bootmem: base[0] size[fef000]
free_bootmem: base[1000000] size[1fc0000]
free_bootmem: base[2fcb000] size[35000]
reserve_bootmem: base[27a000] size[14c4fd]
reserve_bootmem: base[0] size[27a000]
reserve_bootmem: base[3c7000] size[600]
Bootling Linux...
mem_init: Calling free_all_bootmem().
After that no more activity ever. I've verified the md5 sum of the image on the server it's being hosted on. The sparcstation 2 has a keyboard and monitor physicaly attached to it during these tests. I was unable to find a suitable null modem cable to further test with. After starting booting the status of numlock cannot be toggled by me on the keyboard until the machine is reset.
Thanks,
Alan
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---