Is 10.1 beta? tested in an IBM pSeries virtual partition
Hello, I have tested some weeks ago a 10.1 beta build within a pSeries virtual partition. It was booting from CD but during the install I got some error messages about missing files. Has somebody tested 10.1.x in an pSeries partition environment? Has the test done using a 32 bit or 64 bit kernel? I like to resume tests with the upcoming 10.1 beta5. Thanks Helmut
On Tue, Feb 21, Helmut Tschemernjak wrote:
Hello,
I have tested some weeks ago a 10.1 beta build within a pSeries virtual partition. It was booting from CD but during the install I got some error messages about missing files.
What files are missing? Maybe your CD was badly burned.
Hello, I have tried to install 10.1 beta4 within a virtual pSeries partition. The CD boot works and later I get the following error message: *** An error occurred during the installation. I have assigned: 256 MB memory One network interface 12 GB disk 2 CPUs The problem only occurs using Suse 10.1 beta4, I tested as well Suse 9 "Enterprise Server 9 (ppc) - Kernel 2.6.5-7.97-pseries64" which works fine on this system. Any ideas? Helmut ----------------------------------------------------------- Please see the complete boot/install logof 10.1 beta 1 IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM Elapsed time since release of system processors: 14481 mins 11 secs yaboot starting: loaded at 0x00200000-0x00235ed8 (0x0/0x0/0x00c39a48;sp: 0x0187ffe0) Config file 'yaboot.cnf' read, 670 bytes Welcome to SuSE Linux 10.0.42 (PPC)! Type "install" to start the YaST installer on this CD/DVD Type "slp" to start the YaST install via network Type "rescue" to start the rescue system on this CD/DVD Welcome to yaboot version 1.3.13.SuSE booted from '/vdevice/v-scsi@30000002/disk@8200000000000000:1,\suseboot\yaboot.ibm' Enter "help" to get some basic usage information boot: install Please wait, loading kernel... Allocated 0x00a00000 bytes for executable @ 0x01c00000 Elf32 kernel loaded... SuSE Linux zImage starting: loaded at 0x01c00000-0x02410cbc (0x10000/0x0/0x00c39a48; sp: 0x0187fe70) uncompressing ELF header done. (0x00000100 bytes) Allocated 0x009f8fa0 bytes for kernel @ 0x02600000 Allocated 0x005cd575 bytes for initrd @ 0x02ff9000 uncompressing kernel done. (0x0063e428 bytes) entering kernel at 0x02610000(2ff9000/5cd575/00c39a48) OF stdout device is: /vdevice/vty@30000000 Hypertas detected, assuming LPAR ! command line: minmemory=0 MemYaSTText=0 quiet sysrq=1 memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 00000000035c7000 alloc_top : 0000000008000000 alloc_top_hi : 0000000010000000 rmo_top : 0000000008000000 ram_top : 0000000010000000 Looking for displays instantiating rtas at 0x0000000007734000 ... done 0000000000000000 : boot cpu 0000000000000000 0000000000000002 : starting cpu hw idx 0000000000000002... done copying OF device tree ... Building dt strings... Building dt structure... Device tree strings 0x00000000035c8000 -> 0x00000000035c9063 Device tree struct 0x00000000035ca000 -> 0x00000000035d0000 Calling quiesce ... returning from prom_init Page orders: linear mapping = 24, others = 12 Found initrd at 0xc000000002ff9000:0xc0000000035c6575 Partition configured for 4 cpus. Starting Linux PPC64 #1 SMP Wed Feb 15 15:03:23 UTC 2006 ----------------------------------------------------- ppc64_pft_size = 0x16 ppc64_interrupt_controller = 0x2 platform = 0x101 physicalMemorySize = 0x10000000 ppc64_caches.dcache_line_size = 0x80 ppc64_caches.icache_line_size = 0x80 htab_address = 0x0000000000000000 htab_hash_mask = 0x7fff ----------------------------------------------------- [boot]0100 MM Init [boot]0100 MM Init Done Linux version 2.6.16-rc3-git3-2-ppc64 (geeko@buildhost) (gcc version 4.1.0 20060210 (prerelease) (SUSE Linux)) #1 SMP Wed Feb 15 15:03:23 UTC 2006 [boot]0012 Setup Arch Node 0 Memory: 0x0-0x10000000 EEH: No capable adapters found PPC64 nvram contains 7168 bytes Using shared processor idle loop [boot]0015 Setup Done Built 1 zonelists Kernel command line: minmemory=0 MemYaSTText=0 quiet sysrq=1 Moving into tmpfs... done.
SUSE Linux installation program v2.0.18 (c) 1996-2006 SUSE Linux Products GmbH <<<
Starting udev ... ... udev running Starting hardware detection... Searching for info file... Loading Installation System (83520 kB) - 100% *** An error occurred during the installation. Main Menu 1) Settings 2) System Information 3) Kernel Modules (Hardware Drivers) 4) Start Installation or System 5) Verify Installation CD-ROM/DVD 6) Eject CD 7) Exit or Reboot 8) Power off
On Wed, Feb 22, Helmut Tschemernjak wrote:
Hello,
I have tried to install 10.1 beta4 within a virtual pSeries partition. The CD boot works and later I get the following error message:
*** An error occurred during the installation.
I have assigned: 256 MB memory One network interface 12 GB disk 2 CPUs
The problem only occurs using Suse 10.1 beta4, I tested as well Suse 9 "Enterprise Server 9 (ppc) - Kernel 2.6.5-7.97-pseries64" which works fine on this system.
Any ideas?
please boot with 'install linuxrcstderr=/dev/console' to see whats going wrong. I think the inst-sys file cant be mounted.
it looks like the loop device is not available, see messages at end. I checked as well a working Suse 9 after the boot the /dev/loop0 block device is available. Helmut Olaf Hering wrote:
On Wed, Feb 22, Helmut Tschemernjak wrote:
Hello,
I have tried to install 10.1 beta4 within a virtual pSeries partition. The CD boot works and later I get the following error message:
*** An error occurred during the installation.
I have assigned: 256 MB memory One network interface 12 GB disk 2 CPUs
The problem only occurs using Suse 10.1 beta4, I tested as well Suse 9 "Enterprise Server 9 (ppc) - Kernel 2.6.5-7.97-pseries64" which works fine on this system.
Any ideas?
please boot with 'install linuxrcstderr=/dev/console' to see whats going wrong. I think the inst-sys file cant be mounted.
--- the boot log ---- IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM check /vdevice/v-scsi@30000002/disk@8200000000000000 Elapsed time since release of system processors: 14742 mins 0 secs yaboot starting: loaded at 0x00200000-0x00235ed8 (0x0/0x0/0x00c39a48;sp: 0x0191ffe0) Config file 'yaboot.cnf' read, 670 bytes Welcome to SuSE Linux 10.0.42 (PPC)! Type "install" to start the YaST installer on this CD/DVD Type "slp" to start the YaST install via network Type "rescue" to start the rescue system on this CD/DVD Welcome to yaboot version 1.3.13.SuSE booted from '/vdevice/v-scsi@30000002/disk@8200000000000000:1,\suseboot\yaboot.ibm' Enter "help" to get some basic usage information boot: install linuxrcstderr=/dev/console Please wait, loading kernel... Allocated 0x00a00000 bytes for executable @ 0x01c00000 Elf32 kernel loaded... SuSE Linux zImage starting: loaded at 0x01c00000-0x02410cbc (0x10000/0x0/0x00c39a48; sp: 0x0191fe70) uncompressing ELF header done. (0x00000100 bytes) Allocated 0x009f8fa0 bytes for kernel @ 0x02600000 Allocated 0x005cd575 bytes for initrd @ 0x02ff9000 uncompressing kernel done. (0x0063e428 bytes) entering kernel at 0x02610000(2ff9000/5cd575/00c39a48) OF stdout device is: /vdevice/vty@30000000 Hypertas detected, assuming LPAR ! command line: minmemory=0 MemYaSTText=0 quiet sysrq=1 linuxrcstderr=/dev/console memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 00000000035c7000 alloc_top : 0000000008000000 alloc_top_hi : 0000000013000000 rmo_top : 0000000008000000 ram_top : 0000000013000000 Looking for displays instantiating rtas at 0x0000000007734000 ... done 0000000000000000 : boot cpu 0000000000000000 0000000000000002 : starting cpu hw idx 0000000000000002... done copying OF device tree ... Building dt strings... Building dt structure... Device tree strings 0x00000000035c8000 -> 0x00000000035c9063 Device tree struct 0x00000000035ca000 -> 0x00000000035d0000 Calling quiesce ... returning from prom_init Page orders: linear mapping = 24, others = 12 Found initrd at 0xc000000002ff9000:0xc0000000035c6575 Partition configured for 4 cpus. Starting Linux PPC64 #1 SMP Wed Feb 15 15:03:23 UTC 2006 ----------------------------------------------------- ppc64_pft_size = 0x17 ppc64_interrupt_controller = 0x2 platform = 0x101 physicalMemorySize = 0x13000000 ppc64_caches.dcache_line_size = 0x80 ppc64_caches.icache_line_size = 0x80 htab_address = 0x0000000000000000 htab_hash_mask = 0xffff ----------------------------------------------------- [boot]0100 MM Init [boot]0100 MM Init Done Linux version 2.6.16-rc3-git3-2-ppc64 (geeko@buildhost) (gcc version 4.1.0 20060210 (prerelease) (SUSE Linux)) #1 SMP Wed Feb 15 15:03:23 UTC 2006 [boot]0012 Setup Arch Node 0 Memory: 0x0-0x13000000 EEH: No capable adapters found PPC64 nvram contains 7168 bytes Using shared processor idle loop [boot]0015 Setup Done Built 1 zonelists Kernel command line: minmemory=0 MemYaSTText=0 quiet sysrq=1 linuxrcstderr=/dev/console Moving into tmpfs... done.
SUSE Linux installation program v2.0.18 (c) 1996-2006 SUSE Linux Products GmbH <<<
Starting udev ... ... udev running Remount of / ok Console: /dev/hvc0, serial line params "hvc0" error setting kbd mode: Invalid argument CPU: 0, Memory: 256056 insmod /modules/zlib_inflate.ko insmod /modules/isofs.ko insmod /modules/cramfs.ko insmod /modules/sunrpc.ko insmod /modules/lockd.ko insmod /modules/nfs_acl.ko insmod /modules/nfs.ko insmod /modules/floppy.ko insmod: error inserting '/modules/floppy.ko': -1 No such device insmod /modules/loop.ko Beginning hardware probing... Starting hardware detection... Hardware probing finished. There seems to be no floppy disk. Searching for info file... got info from cmdline insmod /modules/ibmvscsic.ko Ok, that seems to have worked. :-) Looking for a SUSE Linux CD... Checking CD: /dev/sr0 Found CD in /dev/sr0 Setting up localhost...done going for automatic install Loading image "/var/adm/mount/boot/ppc/root"... Loading Installation System (83520 kB) - 100% mount: /download/image0: we need a loop device mount: using /dev/loop0 No such file or directory udevd[369]: add_to_rules: invalid rule '' No such file or directory No such file or directory No such file or directory udevd[369]: add_to_rules: invalid rule '' No such file or directory No such file or directory udevd[369]: add_to_rules: invalid rule '' No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory No such file or directory /mounts/instsys/var/_?}? ?J$I???9?q/7qƖ?E??8???m?tK???k?߿}?e??o|?$?1ө?Mj?: No such file or directory /mounts/instsys/var/?ql??k;??K?/??Yr?BZ??.??????F-?\?*q? 1???^ ????s,??A: No such file or directory /mounts/instsys/var/?[???? ?????v??=?83?p????f?m?S???/?拼zU?R??J?nn????? 5kؤ?̞`?'??:8?G???? N >?U??~l?Zu??h?鰣??4y֙?怤;???p;?,S<??Cn?'?v>׀O/??-??: No such file or directory starting setctsid `showconsole` inst_setup yast error setting kbd mode: Invalid argument install program exit code is 127 sync... ok *** An error occurred during the installation. killing udevd (369) Main Menu 1) Settings 2) System Information 3) Kernel Modules (Hardware Drivers) 4) Start Installation or System 5) Verify Installation CD-ROM/DVD 6) Eject CD 7) Exit or Reboot 8) Power off
On Wed, Feb 22, Helmut Tschemernjak wrote:
it looks like the loop device is not available, see messages at end. I checked as well a working Suse 9 after the boot the /dev/loop0 block device is available.
I think the loop is ok, but something else is going on. I have not seen this bug.
On Wed, Feb 22, Olaf Hering wrote:
On Wed, Feb 22, Helmut Tschemernjak wrote:
it looks like the loop device is not available, see messages at end. I checked as well a working Suse 9 after the boot the /dev/loop0 block device is available.
I think the loop is ok, but something else is going on. I have not seen this bug.
Can you try beta6? Its not clear why there are files missing in the initrd. There is a bug open about random initrd corruption, but this seems to happen only after the AIX diagnostic CD was booted once. Doesnt seem to be the case according to your bootlog.
participants (2)
-
Helmut Tschemernjak -
Olaf Hering