Bug#248855: Package: installation-reports (overall success on SunBlade 150, with some problems)
Package: installation-reports
INSTALL REPORT
Debian-installer-version: sarge-sparc-businesscard.iso taken from
http://gluck.debian.org/cdimage/testing/daily/sparc/20040511/sarge-sparc-businesscard.iso
uname -a: Linux blade 2.4.26-sparc64 #1 Sat Apr 24 01:43:10 EDT 2004 sparc64 GNU/Linux
Date: Thu May 13 14:07:40 UTC 2004
Method: How did you install? What did you boot off? If network
install, from where? Proxied?
I downloaded ISO image and burned it on a CD-RW. Then I started the machine,
went to OpenPROM, and booted it using "boot cdrom". On the SILO screen
I simply pressed [Enter], using the default "linux" option.
Machine: Sun Blade 150 (with USB mouse and USB keyboard)
Processor: UltraSPARC-IIe 650MHz
Memory: 256MB
Root Device: /dev/hda
Root Size/partition table:
# fdisk /dev/hda
Disk /dev/hda (Sun disk label): 16 heads, 255 sectors, 19156 cylinders
Units = cylinders of 4080 * 512 bytes
Device Flag Start End Blocks Id System
/dev/hda1 258 3600 6817680 83 Linux native <-- sarge /root
/dev/hda2 u 3600 4115 1050600 82 Linux swap <-- sarge swap
/dev/hda3 0 19156 39078240 5 Whole disk
/dev/hda4 0 258 526320 83 Linux native <-- helper
/dev/hda5 4115 16458 25179720 83 Linux native <-- woody /root
/dev/hda6 16458 19028 5242800 83 Linux native <-- woody /var
/dev/hda7 u 19028 19156 261120 82 Linux swap <-- woody swap
Output of df -h :
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 6.4G 285M 5.8G 5% /
tmpfs 124M 0 124M 0% /dev/shm
Output of lspci and lspci -n:
lspci :
pcilib: Cannot open /sys/bus/pci/devices
0000:00:00.0 Host bridge: Sun Microsystems Computer Corp. Ultra IIe
0000:00:03.0 Non-VGA unclassified device: ALi Corporation M7101 PMU
0000:00:05.0 PCI bridge: Intel Corp. 21152 PCI-to-PCI Bridge
0000:00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV]
0000:00:08.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 01)
0000:00:0c.0 Bridge: Sun Microsystems Computer Corp. RIO EBUS (rev 01)
0000:00:0c.1 Ethernet controller: Sun Microsystems Computer Corp. RIO GEM (rev 01)
0000:00:0c.2 FireWire (IEEE 1394): Sun Microsystems Computer Corp. RIO 1394 (rev 01)
0000:00:0c.3 USB Controller: Sun Microsystems Computer Corp. RIO USB (rev 01)
0000:00:0d.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
0000:00:13.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
lspci -n :
pcilib: Cannot open /sys/bus/pci/devices
0000:00:00.0 Class 0600: 108e:a001
0000:00:03.0 Class 0000: 10b9:7101
0000:00:05.0 Class 0604: 8086:b152
0000:00:07.0 Class 0601: 10b9:1533
0000:00:08.0 Class 0401: 10b9:5451 (rev 01)
0000:00:0c.0 Class 0680: 108e:1100 (rev 01)
0000:00:0c.1 Class 0200: 108e:1101 (rev 01)
0000:00:0c.2 Class 0c00: 108e:1102 (rev 01)
0000:00:0c.3 Class 0c03: 108e:1103 (rev 01)
0000:00:0d.0 Class 0101: 10b9:5229 (rev c3)
0000:00:13.0 Class 0300: 1002:4752 (rev 27)
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [O]
Config network: [*]
Detect CD: [O]
Load installer modules: [E]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [*]
Comments/Problems:
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
0) General
Initial boot worked !!!
After about more than a month of non-working state it went smoothly.
I was sooo pleased :-)
Note: later, when presented the option, I selected the 'testing'
installation type.
1) Load installer modules
At first glance I saw the debian-installer displaying the option of choosing
a language for the installation (as it always does). Alas, there were some
lines shorter than the whole menu, and strange squares - instead of some
international characters. It looked like bad console font. Or bad unicode
mapping maybe?
After selecting language, auto-detection process started, but in the end
I was unable to use the keyboard. I rebooted and tried another language
(that is, I tried selecting "Polski" first and then "English (US)") but
without success. It looked like "Sun keyboard" was auto-selected by d-i.
I rebooted once again, and pressed the [Esc] key twice. This way I was taken
to the main menu and then I selected "USB keyboard" manually. It helped and
I was able to continue and finish the installation successfully.
2) Config network
We have a special network setup, so I had to repeat DHCP auto-configuration
several times (watching DHCPDISCOVER messages on tty4), because of the
timeouts. It worked finally (I knew it would), and the installation process
continued smoothly.
What I want to complain about is that this network setup was not transferred
to the target installation. I had to manually edit /etc/network/interfaces,
but for less experienced user this is an "it-just-does-not-work" condition.
I still wonder if this file is placed under config-protection, because
I didn't make a copy of it (as I was happy to see sarge working! :-)
After that and simple "/etc/init.d/networking start" I was able to use
aptitude to install other packages.
3) Reboot
Don't worry, it worked again :-) But there was some glitch with USB keyboard
driver. Everytime I pressed [CapsLock] or [ScrollLock] key, the corresponding
LED was not turned on, but instead a message "usbkbd.c: led urb status -32"
was displayed. I suppose I will have to recompile kernel to get rid of
this silly behavior :-(
Summary:
The network setup is a small problem, but the problems with the keyboard
should be corrected.
Happy again,
Wiktor Wandachowicz
Install logs and other status info is available in /var/log/debian-installer/.
Once you have filled out this report, mail it to submit@bugs.debian.org.
Reply to: