Re: 64 bit java?

2017-03-29 Thread Adam Stouffer 
On Wed, Mar 29, 2017 at 3:04 AM, Christian Zigotzky
 wrote:
> Have you already added [arch=powerpc] to the other deb lines? (not deb-src 
> lines)
>
> -- Christian

Yes, here is my sources.list

#

# deb cdrom:[Debian GNU/Linux 8.7.1 _Jessie_ - Official powerpc NETINST Binary-1
 20170116-11:54]/ jessie main

#deb cdrom:[Debian GNU/Linux 8.7.1 _Jessie_ - Official powerpc NETINST Binary-1
20170116-11:54]/ jessie main

deb [arch=ppc64] http://ftp-nyc.osuosl.org/debian/ jessie main
deb-src http://ftp-nyc.osuosl.org/debian/ jessie main

deb [arch=ppc64] http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main

# jessie-updates, previously known as 'volatile'
deb [arch=ppc64] http://mirror.techfak.uni-bielefeld.de/debian/ jessie-updates m
ain
deb-src http://mirror.techfak.uni-bielefeld.de/debian/ jessie-updates main



deb [arch=ppc64] http://ftp.ports.debian.org/debian-ports/ unstable main
deb [arch=ppc64] http://incoming.ports.debian.org/buildd/ unstable main
deb [arch=ppc64] http://ftp.ports.debian.org/debian-ports/ unreleased main

I also ran "dpkg --add-architecture ppc64" again and get the same results.

W: Failed to fetch
http://security.debian.org/dists/jessie/updates/InRelease  Unable to
find expected entry 'main/binary-ppc64/Packages' in Release file
(Wrong sources.list entry or malformed file)

W: Failed to fetch
http://mirror.techfak.uni-bielefeld.de/debian/dists/jessie-updates/InRelease
 Unable to find expected entry 'main/binary-ppc64/Packages' in Release
file (Wrong sources.list entry or malformed file)

W: Failed to fetch
http://ftp-nyc.osuosl.org/debian/dists/jessie/Release  Unable to find
expected entry 'main/binary-ppc64/Packages' in Release file (Wrong
sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old
ones used instead.

The entries its looking for do not exist in the Release files.

Re: 64 bit java?

2017-03-28 Thread Adam Stouffer 
On Tue, Mar 28, 2017 at 5:37 PM, John Paul Adrian Glaubitz
 wrote:
> Hi Adam!
>
>
> That's the architecture of your kernel. If your machine is capable of running
> 64-bit code, debian-installer will install a 64-bit kernel. Your userland, 
> i.e.
> all applications, are still 32-bit.
>
> See the output of:
>
> $ dpkg --print-architecture
>
>> Is there a 64 bit build?
>
> You need to add ppc64 as a Multi-Arch architecture by adding the following
> line to your sources.list:
>
> deb [arch=ppc64] http://ftp.ports.debian.org/debian-ports/ unstable main
> deb [arch=ppc64] http://incoming.ports.debian.org/buildd/ unstable main
> deb [arch=ppc64] http://ftp.ports.debian.org/debian-ports/ unreleased main
>
> All other deb lines (not deb-src lines) need to have [arch=powerpc] added.
>
> Then install the debian-ports-archive-keyring package and run:
>
> # dpkg --add-architecture ppc64
>
> Then:
>
> # apt update

Ok so far so good. Here is where I run into a problem.

W: Failed to fetch
http://security.debian.org/dists/jessie/updates/InRelease  Unable to
find expected entry 'main/binary-ppc64/Packages' in Release file
(Wrong sources.list entry or malformed file)

W: Failed to fetch
http://ftp-nyc.osuosl.org/debian/dists/jessie-updates/InRelease
Unable to find expected entry 'main/binary-ppc64/Packages' in Release
file (Wrong sources.list entry or malformed file)

W: Failed to fetch   Unable to find expected entry
'main/binary-ppc64/Packages' in Release file (Wrong sources.list entry
or malformed file)

The (In)Release files don't have listings for ppc64 packages, only
ppc64el. I found two mirrors with those listings and edited the
sources.list file. However it's still looking in the wrong place.

W: Failed to fetch
http://mirror.techfak.uni-bielefeld.de/debian/dists/jessie-updates/InRelease
 Unable to find expected entry 'main/binary-ppc64/Packages' in Release
file (Wrong sources.list entry or malformed file)

That InRelease file has no ppc64/Packages listing but this Release
file does 
http://mirror.techfak.uni-bielefeld.de/debian-ports/debian/dists/sid/Release

A bit confused at the moment...

Re: 64 bit java?

2017-03-28 Thread Adam Stouffer 
On Tue, Mar 28, 2017 at 3:05 AM, Simon Richter  wrote:
> The "powerpc" architecture should have 32 bit java, the "ppc64" and
> "ppc64le" architectures should have 64 bit Java. You can use
> Multiarch[1] if you want to have a version that doesn't match the rest
> of the system.
>
>Simon
>
> [1] https://wiki.debian.org/Multiarch
>

Simon, I'm running ppc64 and the java binary is 32 bit.

tesla@enid:~$ uname -a
Linux enid 3.16.0-4-powerpc64 #1 SMP Debian 3.16.39-1+deb8u2
(2017-03-07) ppc64 GNU/Linux

tesla@enid:~$ file /usr/lib/jvm/java-7-openjdk-powerpc/jre/bin/java
/usr/lib/jvm/java-7-openjdk-powerpc/jre/bin/java: ELF 32-bit MSB
executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically
linked, interpreter /lib/ld.so.1, for GNU/Linux 2.6.32,
BuildID[sha1]=84b7f9672614e3388199c054daf4a27ee599850f, stripped

Is there a 64 bit build?

Adam

64 bit java?

2017-03-27 Thread Adam Stouffer 
Is there a 64 bit version of java available? Everything apt-cache
returns doesn't say anything about 64 or 32 bits. I tried getting
IBM's jre but the installer bombs out.


Adam

Re: POWER6 not seeing memory above 2Gb

2017-03-23 Thread Adam Stouffer 
On Thu, Mar 23, 2017 at 3:29 PM, Lennart Sorensen
 wrote:
> What was on this machine before?  Is it possible that you are in fact
> running inside an existing LPAR config, which might have limited memory
> assigned?
>
> --
> Len Sorensen

Len, you were right about it being an LPAR. Previously I was running
PowerVM but removed the drive. I had no idea it configured the
hardware itself. Good thing you can run the special HMC Linux distro
within VMWare :) Here is the screenshot and cause of my woes
http://i.imgur.com/4Jlc1zq.png

Thanks again for your patience.

Adam

Re: POWER6 not seeing memory above 2Gb

2017-03-23 Thread Adam Stouffer 
> Good question.  I installed the machine with grub2 originally years ago,
> so I didn't have to try (I wanted MD raid1 which yaboot couldn't handle
> at that time, so I wanted grub2 to work, no matter what it took).  Took
> some work at the time, debugging disk issues and other issues in grub2,
> but eventually grub2 got to the point of working on the p520 properly.
> These days it ought to just work.
>
> I remember needing a Prep boot partition, which grub-install was then
> pointed at.  I can't remember if yaboot does it the same way.
>
> It might be as simple as installing the grub-ieee1275 package and running
> grub-install /dev/sda1 (assuming sda1 is the PReP boot partition).
>
> --
> Len Sorensen

So I have grub2 booting the same kernel but again the same result.
Only 2Gb available.

Re: POWER6 not seeing memory above 2Gb

2017-03-23 Thread Adam Stouffer 
On Thu, Mar 23, 2017 at 10:21 AM, Lennart Sorensen
 wrote
>
>
>
> That ought to be working.  I know the p520 I worked with before it
> worked fine.
>
> Which bootloader are you using?  I use grub2, just in case the bootloader
> has anything to do with memory detection in linux.
>
> --
> Len Sorensen


Ah, that might be the case. Yaboot seemed to have some install issues
anyhow. What would be the best way to switch from yaboot to grub2?

Re: POWER6 not seeing memory above 2Gb

2017-03-23 Thread Adam Stouffer 
On Thu, Mar 23, 2017 at 9:32 AM, Lennart Sorensen <
lsore...@csclub.uwaterloo.ca> wrote:

>
> Well I know running a 64 bit kernel on that model, does see 16GB ram.
> But I was doing that with no LPAR or anything else, just Debian installed
> straight onto the machine (IBM support people have a hard time
> understanding that people might do that).
>
> So either you somehow installed a 32 bit kernel, or you have an LPAR or
> something else restricting your memory size.
>
> --
> Len Sorensen
>

No LPAR or VM, running just "bare metal". I had AIX installed previously
and it recognized 16Gb.

uname -a
Linux new-host-4 3.16.0-4-powerpc64 #1 SMP Debian 3.16.39-1+deb8u2
(2017-03-07) ppc64 GNU/Linux

lscpu
Architecture:  ppc64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Big Endian
CPU(s):4
On-line CPU(s) list:   0-3
Thread(s) per core:2
Core(s) per socket:1
Socket(s): 2
NUMA node(s):  1
Model: IBM,8203-E4A
Hypervisor vendor: pHyp
Virtualization type:   para
L1d cache: 64K
L1i cache: 64K
NUMA node0 CPU(s): 0-3

Seems like a config issue? Wouldn't a 32 bit kernel see the 32 bit limit,
under 4Gb?

POWER6 not seeing memory above 2Gb

2017-03-22 Thread Adam Stouffer 
Hello all, I'm new to the list and just installed jessie on my IBM
8203-E4A box. It's a dual core 4.2Ghz with 16Gb of memory.

But anyhow like the subject says the kernel is only reporting 2Gb of
available memory. I tried appending "mem=16G" as a boot argument but
no change.

Here is the output from dmesg with kernel 3.16.0

[0.00] physicalMemorySize= 0x8000
[0.00] Node 0 Memory: 0x0-0x8000
[0.00] Early memory node ranges
[0.00] Memory: 1899264K/2097152K available (7360K kernel code,
1792K rwdata, 1840K rodata, 960K init, 2071K bss, 197888K reserved)
[0.023173] Initializing cgroup subsys memory
[1.036652] Freeing initrd memory: 16384K (c348 -
c448)
[1.242857] Freeing unused kernel memory: 960K (c091 -
c0a0)

Any ideas? Thanks.