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
Attachment:
pgpEGGW7_bZ2c.pgp
Description: PGP signature