Your message dated Sat, 1 Apr 2006 18:08:55 +0200 with message-id <20060401160855.GH29291@djedefre.onera> and subject line "makes sparc keyboard stop working" probably over sinces ages.... has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: email@example.com
- Subject: Installation report for Sun Blade 100 TFTP boot image (RC1, keyboard directly connected)
- From: Evilpig <firstname.lastname@example.org>
- Date: Wed, 11 Aug 2004 00:27:28 -0500
- Message-id: <email@example.com>Package: installation-reports Debian-installer-version: Sarge RC1 20040806 sparc64 TFTP boot image from http://http.us.debian.org/debian/dists/testing/main/installer-sparc/rc1/images/sparc64/netboot/boot.img uname -a: N/A, didn't get that far Date: 20040809, 9pm CST Method: Put boot.img file on TFTP/RARP server (Sun E250 running Debian Woody) with proper symlink, added line to /etc/ethers for RARP. Booted via OpenBoot "boot net". Machine: Sun Blade 100 workstation (sun4u/sparc64) Processor: 500MHz UltraSPARC-IIe Memory: 512MB (4x128MB) Root Device: I didn't get far enough to choose one, but there are 2 IDE drives in the system. c0t0d0 is a Seagate ST315310A 15.3GB IDE drive; c0t2d0 is a Quantum Fireball AS40.0 40GB IDE drive (this is the one I would have chosen). Root Size/partition table: N/A, didn't get that far Output of lspci: N/A, didn't get that far Base System Installation Checklist: Initial boot worked: [O] Configure network HW: [O] Config network: [E] <- Not a problem w/network though! 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: I had better luck with this TFTP boot image than I did with the netinstall CD (I filed a separate installation report for that). Unfortunately I cannot make it through the installer with the keyboard attached to the system. This is not an issue when I use the TFTP boot image installer over a serial console, so I will write another installation report about that scenario when I finish with it. My keyboard is a Sun type 6 USB US/UNIX layout directly connected to the USB port in the back of the machine. It works during the initial part of the installer where I am asked to choose a language (English) and country (United States). I can use the arrows to scroll up and down through the choices, use the tab key, and use the letter keys for arguments to the installer's SILO. I am asked to choose a keyboard layout, so I choose "American English". After this, it briefly detects hardware and goes on to configure the network via DHCP,which it does successfully and asks me to confirm/edit the hostname. At this point I am unable to progress further, because I cannot even press "Enter" to go to the next step, nor can I edit the hostname or use "TAB" to go back. Pressing random keys will occasionally cause it to move between choices (and the asdf... row appears to correspond to the number keys), so it seems to know that it's still connected to the keyboard, but it's not usable at all.
--- End Message ---
--- Begin Message ---
- To: firstname.lastname@example.org, email@example.com
- Subject: "makes sparc keyboard stop working" probably over sinces ages....
- From: Christian Perrier <firstname.lastname@example.org>
- Date: Sat, 1 Apr 2006 18:08:55 +0200
- Message-id: <20060401160855.GH29291@djedefre.onera>Hello, In #264962, you reported a non working Sparc keyboard when using the RC1 sarge installer with a Sun Blade 100 workstation. Given the number of successsfuly install reports we've had since then on such hardware, I suspect that this bug is away for a long time but noone cared closing it. So I hereby close it....please reopen it if you still experience the very same bug. --
Description: Digital signature
--- End Message ---