Bug#396412: installation-reports: Installation report on AS/400 / iSeries / System i / i5
On Wed, Nov 01, 2006 at 07:23:22AM +0100, Frans Pop wrote: Hmm. Nice to see a report for this. I didn't even know we supported AS/400 boxes :-) Neither I did, but it was worth a try. :-) The installer uses UTF-8 encoding. You may get a better display if you're able to configure the remote console to use that. Oups. I'll try that out. This probably could be made to work by using a separate /boot partition. Doesn't place yaboot its config in /etc? Anyways, a warning like yaboot may be unable to read its configuration file or something would have been nice. I'm not quite sure how the kernel selection for powerpc works, but we should be able to fix this. Could you send us the output of 'cat /proc/cpuinfo'? # cat /proc/cpuinfo processor : 0 cpu : POWER5+ (gs) clock : 2197.80MHz revision: 2.1 (pvr 003b 0201) processor : 1 cpu : POWER5+ (gs) clock : 2197.80MHz revision: 2.1 (pvr 003b 0201) timebase: 27506 machine : CHRP IBM,9406-570 # After rebooting, yaboot loaded the Elf64 kernel and all services started. However, a getty did not start on /dev/console (what made me a bit nervous first). I don't know if this is considered a bug or not... What did you change in /etc/inittab to fix this. just started a getty on /dev/console by putting this into the inittab: 0:2345:respawn:/sbin/getty 38400 console If you used a serial console, what is its name? Is it /dev/ttyS? or something fancy? I really have no idea. I have found out two ways to get a console: a) via Open a terminal window in the partitions's context menu in the HMC or b) connecting via telnet to the i5/OS partition and selecting a remote panel for the guest partition. I don't know what type of console are either of them. Maybe this is some kind of serial console (I have configured virtual serial adapters from the linux to the i5/OS partition). I will investigate on that console thing further next week. Greetings, Sebastian -- signature intentionally left blank pgpqBFq7aFFvA.pgp Description: PGP signature
Bug#396412: installation-reports: Installation report on AS/400 / iSeries / System i / i5
Package: installation-reports Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Boot method: Virtual CD-ROM (LODIMGCLG IMGCLG(MYCLG) DEV(OPTVRT01) OPTION(*LOAD)) Image version: etch with d-i beta3 (as of August 2006) - http://cdimage.debian.org/cdimage/etch_di_beta3/powerpc/iso-dvd Date: 27 Oct 2006 Machine: IBM iSeries / i5 / AS/400 / System i (whatever IBM calls it now) Model 570 Processor: POWER5+, 2.2GHz, dual-core Memory: 1275696 kB Partitions: sda1 PPC PReP Partition, sda2 /, sda5 swap Output of lspci -nn and lspci -vnn: Machine has no PCI Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[O] Configure network: [ ] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[O] Comments/Problems: I tried to install Debian as a guest within an i5/OS (or OS/400) partition via the CRTNWSD (Create Network Server Description) command. Unfortunately, i5/OS refused to recognize neither the yaird image nor the kernel itself as a valid IPL source. However, turning the partition on via the HMC and booting into SMS worked. Note that the the NWS has still to be varied on via WRKCFGSTS *NWS. Else, virtual I/O devices (and most notably NWSSTG) are missing. After booting into SMS, I was able to choose the virtual CD-ROM drive as IPL source. Booting and installing was straightforward (in case, one chose the expert64 or install64 yaboot entry - i5 refuses to boot from 32 bit kernels and crashes into ofdbg displaying a nice register dump). Graphics were a bit garbled[1] on the console (via telnet i5/OS partition 2301), but d-i was usable. D-i allowed me to make my root partition managed by LVM, what I chose on my first try. However, yaboot was unable to read its config from this partition, so I reinstalled (it was friday afternoon anyway) it without LVM on my /. yaboot was installed to a PReP partition (nothing notably until then) and the system rebooted. Unfortunately, I didn't start installation in expert mode, so I didn't notice that d-i only installed a 32 bit kernel. As expected, yaboot booted right into the open firmware debugger. After re-restarting the installation in expert mode, I hoped to find a 64 bit kernel in the installer's kernel selection list. However, only 32 bit kernels where listed, so I had to install a 64 bit version via a chroot environment in the command line. After rebooting, yaboot loaded the Elf64 kernel and all services started. However, a getty did not start on /dev/console (what made me a bit nervous first). I don't know if this is considered a bug or not... Anyway - nice job! I didn't expect the installation to go on that smoothly ;-) Footnotes = 1: http://kitt.yath.de/~yath/2006-10-31-d-i-1.png -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFFR3oavBVic1oTsEgRAq6UAJ9m8Tb8J7NSDJUqk2/fIuIGybYp9QCfe0a4 bwsmyTFGQ3ocvbbb8HvJu+M= =6CHk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396412: installation-reports: Installation report on AS/400 / iSeries / System i / i5
On Tuesday 31 October 2006 17:30, Sebastian Schmidt wrote: Comments/Problems: I tried to install Debian as a guest within an i5/OS (or OS/400) partition via the CRTNWSD (Create Network Server Description) command. Hmm. Nice to see a report for this. I didn't even know we supported AS/400 boxes :-) After booting into SMS, I was able to choose the virtual CD-ROM drive as IPL source. Booting and installing was straightforward (in case, one chose the expert64 or install64 yaboot entry - i5 refuses to boot from 32 bit kernels and crashes into ofdbg displaying a nice register dump). Graphics were a bit garbled[1] on the console (via telnet i5/OS partition 2301), but d-i was usable. The installer uses UTF-8 encoding. You may get a better display if you're able to configure the remote console to use that. D-i allowed me to make my root partition managed by LVM, what I chose on my first try. However, yaboot was unable to read its config from this partition, so I reinstalled (it was friday afternoon anyway) it without LVM on my /. This probably could be made to work by using a separate /boot partition. yaboot was installed to a PReP partition (nothing notably until then) and the system rebooted. Unfortunately, I didn't start installation in expert mode, so I didn't notice that d-i only installed a 32 bit kernel. As expected, yaboot booted right into the open firmware debugger. After re-restarting the installation in expert mode, I hoped to find a 64 bit kernel in the installer's kernel selection list. However, only 32 bit kernels where listed, so I had to install a 64 bit version via a chroot environment in the command line. I'm not quite sure how the kernel selection for powerpc works, but we should be able to fix this. Could you send us the output of 'cat /proc/cpuinfo'? After rebooting, yaboot loaded the Elf64 kernel and all services started. However, a getty did not start on /dev/console (what made me a bit nervous first). I don't know if this is considered a bug or not... What did you change in /etc/inittab to fix this. D-I basically supports two modes of installation: - regular monitor connected to video card - serial console installs; should set up a serial console for the installed system too If you used a serial console, what is its name? Is it /dev/ttyS? or something fancy? Cheers, FJP pgpnNjResFmcz.pgp Description: PGP signature
