openSUSE PPC April 2014

ppc@lists.opensuse.org

1 participants
3 discussions

[opensuse-ppc] Thank you very much indeed for openSUSE 12.2

by Christian Zigotzky

Hi list, Thank you very much indeed for openSUSE 12.2 PowerPC. It runs very well on my Power Mac G5 2003, 2.0GHz, 4 GB RAM, ATi Radeon 9600 128 MB with sound and X11 support. Unfortunately Firefox doesn't work. I use the Firefox by ppcnux.de. Are there any updates available for openSUSE 12.2 PowerPC e.g. Firefox 16? Cheers, Christian -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ppc+owner(a)opensuse.org

5 years, 12 months

[opensuse-ppc] Factory CD boot problem

by Andreas Färber

Hello, Since a number of weeks I am unsuccessful in using the ppc64 install media on my POWER5+ box. Below is output from latest openSUSE-NET64-ppc64-Build0023-Media.iso. In qemu-system-ppc64 it proceeds okay, and Factory boots okay (below). The only difference is me entering SMS menu to select booting from IDE CD. I notice that the booting system loads an Elf64 kernel while the ppc64 iso loads an Elf32 kernel. Any ideas? Thanks, Andreas CD: yaboot starting: loaded at 00040000 00065a88 (0/0/02039a68; sp: 02cbffd0) Config file 'yaboot.cnf' read, 285 bytes Welcome to openSuSE Factory! 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 r22.8-r1190.SuSE booted from '/pci@800000020000003/pci@2,3/ide@1/disk@0:1,\suseboot\yaboot.ibm' running with firmware 'IBM,SF240_284' on model 'IBM,9111-285', serial 'IBM,*********', partition '06-C903E' Enter "help" to get some basic usage information boot: install slp rescue boot: install Please wait, loading kernel... Allocated 02f00000 bytes for executable @ 03000000 Elf32 kernel loaded... SuSE Linux zImage starting: loaded at 03000000-05dc0d30 (4000000/0/02039a68; sp: 02cbfd90) uncompressing ELF header done. (00000100 bytes) Allocated 018461cc bytes for kernel @ 05f00000 Leave 027c7fc4 bytes for initrd @ 035ecece uncompressing kernel done. (01240ef8 bytes) entering kernel at 05f10000(35ecece/27c7fc4/02039a68) OF stdout device is: /vdevice/vty@30000000 Preparing to boot Linux version 3.10.1-3.g0cd5432-default (geeko@buildhost) (gcc version 4.8.1 20130711 [gcc-4_8-branch revision 200903] (SUSE Linux) ) #1 SMP Fri Jul 19 14:39:31 UTC 2013 (0cd5432) Detected machine type: 0000000000000101 Max number of cores passed to firmware: 512 (NR_CPUS = 1024) Calling ibm,client-architecture-support... not implemented command line: quiet sysrq=1 insmod=sym53c8xx insmod=ipr memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 0000000007470000 alloc_top : 0000000008000000 alloc_top_hi : 0000000077000000 rmo_top : 0000000008000000 ram_top : 0000000077000000 found display : /pci@800000020000002/display@1, opening... done Could not allocate memory for RTAS EXIT called ok 0 > Disk: yaboot starting: loaded at 00040000 00065a88 (0/0/02039a68; sp: 02cbffd0) Config file 'yaboot.cnf' read, 611 bytes Welcome to yaboot version r22.8-r1190.SuSE booted from '/pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8,0:1,yaboot' running with firmware 'IBM,SF240_284' on model 'IBM,9111-285', serial 'IBM,*********', partition '06-C903E' Enter "help" to get some basic usage information boot: Linux_4 Using 01401f9c bytes for initrd buffer Please wait, loading kernel... Allocated 01700000 bytes for kernel @ 03000000 Elf64 kernel loaded... Loading ramdisk... ramdisk loaded 01401f9c @ 04700000 OF stdout device is: /vdevice/vty@30000000 Preparing to boot Linux version 3.10.1-3.g0cd5432-default (geeko@buildhost) (gcc version 4.8.1 20130711 [gcc-4_8-branch revision 200903] (SUSE Linux) ) #1 SMP Fri Jul 19 14:39:31 UTC 2013 (0cd5432) Detected machine type: 0000000000000101 Max number of cores passed to firmware: 512 (NR_CPUS = 1024) Calling ibm,client-architecture-support... not implemented command line: root=/dev/disk/by-uuid/671e0a08-2bb3-4fae-b606-287d887e2060 quiet sysrq=1 insmod=sym53c8xx insmod=ipr memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 0000000005b10000 alloc_top : 0000000008000000 alloc_top_hi : 0000000077000000 rmo_top : 0000000008000000 ram_top : 0000000077000000 found display : /pci@800000020000002/display@1, opening... done instantiating rtas at 0x00000000076a0000... done Querying for OPAL presence... not there. boot cpu hw idx 0 copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0000000005b20000 -> 0x0000000005b21372 Device tree struct 0x0000000005b30000 -> 0x0000000005b40000 no ibm,pcie-link-speed-stats property no ibm,pcie-link-speed-stats property no ibm,pcie-link-speed-stats property /home/abuild/rpmbuild/BUILD/kernel-default-3.10.1/linux-3.10/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) doing fast boot [...] -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ppc+owner(a)opensuse.org

6 years, 2 months

[opensuse-ppc] Few problems on P7 ppc

by Hans Scheffers

Hi all, as told earlier, we are running opensuse 13.1 ppc on a IBM P7 lpar ( thx to Dinar Valeev for the help), but we are running into a few problems. Is there someone who experiences the same problems, or maybe even better, solved them ;) We use our system for icinga monitoring of about 200 servers with a total of 5000 services. We migrated from x-series to p-series (P710) because the load that is generated by WMI checks for the windows systems in our environment. We have assigned max 2 processors and 4 gig of memory to our lpar (no swapping at the moment) Our problems are: - We tried to run MariaDB 5.5.33 on the system, which generated under some load (of ido2db for all our hosts), which generated a lot of "InnoDB: Assertion failure in thread 70366933971360 in file buf0buf.ic line 1277" errors. Moving to MySQL 5.5.6 reduced the number of errors, but certain queries are interpreted differently as the older versions of MYSQL (or this is a bug somewhere), and was not usable. We ended up moving our mysql-db back to x-series. - On all of our lnx systems we have AD users, implemented according to on http://en.gentoo-wiki.com/wiki/Active_Directory_Authentication_using_LDAP. When we enable the pam modules used in the AD authentication, su-ing to root gives a memory fault. - we have our monitoring over two systems at the moment, x-series with a few networkdevices (which will be transferred to p-series also, but we have a freeze in december). To have all the results in one interface, we installed check_mk on x-series and mk_livestatus on p-series. The mk_livestatus doesn't read a configuration setting (or doesn't interpreted it correctly), and gives a 0 for config_broker_options instead of the -1 in the config. Recompiling the file with the -1 hardcoded gives a working mk_livestatus. - mk_livestatus is used to read values from nagios using a commandpipe, but some of the values (always the same fields) are 0 instead of the unix timestamp they should have. Somehow this all seems a bit memory rmanagement related, but i am not a programmer / debugger... Has someone any ideas about these problems? Kernel version on the p-series: uname -a Linux <systemname> 3.11.6-4-default #1 SMP Wed Oct 30 18:04:56 UTC 2013 (e6d4a27) ppc64 ppc64 ppc64 GNU/Linux Hans Scheffers AIX / Linux Systeembeheer -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ppc+owner(a)opensuse.org

6 years, 11 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

openSUSE PPC April 2014