Hi,
> i've also experienced the "two passes behaviour" occasionally, but
> up to now haven't been able to figure out a pattern. It's definately
> Linux-specific, since we don't see that behaviour with our AIX LPARs.
> Not sure though if its yaboot or Kernel related.
It's not specific to Linux, ho
Hi,
> I thinkg SSA is the better of the two but before I worry about that I
> want to know if SSA is supported. Untill I know, I can always get the
> unit with neither six-pack and just use the base boot drive.
Unfortunately SSA isnt supported on Linux.
Anton
--
To UNSUBSCRIBE, email to [EM
lt in hangs at boot.
Signed-off-by: Anton Blanchard <[EMAIL PROTECTED]>
---
Index: build/drivers/char/Kconfig
===
--- build.orig/drivers/char/Kconfig 2006-02-09 11:35:15.0 +1100
+++ build/drivers/char/Kconf
> just wondering, is the timebase suppose to look like this? and where are
> the bogomips gone?
Yep, the timebase is externally clocked on those machines. And since
bogomips is useless there is no need to advertise it here :)
Anton
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
> Mucking with the environment variables as you suggest fixed my problem.
> Thanks! I have now compiled a PPC 64 kernel, but sadly do not have a G5
> to try it on. :(
Unfortunately I cant help you there :)
> I noticed gcc uses the -m64 option when compiling the 64 bit things. When
> no -mXY
> >Can anyone tell me where to get a toolchain that can build a PPC64 (NOT
> >PPC32) kernel? I've now got a few PPC64 machines running Debian that
> >I'd like to run an actual 64-bit kernel on...
>
> Maybe you'll have better luck. I built one with crosstool-031 which was
> very easy. Unfortu
Hi,
I was looking for a POWER3 debian install CD and came across the
installer ports status page:
http://www.debian.org/devel/debian-installer/ports-status
It mentions these as working:
powerpc IBM RS6000
power3 IBM RS6000
power4 IBM RS6000
It turns out these targets overlap with the next two
Hi,
> Does anyone know how many processors are supported on Power 5 SMP machines
> with Linux?
>
> I'm hoping to buy a 16 processor system and am cureous if theres any hope
> of Linux being able to use all 16 procs.
Yes. We regularly boot POWER5 machines with 128 threads (64 way).
Note that
Hi,
> I've just updated the installer image to have no POWER4+ optimization,
> but the language chooser seems to be broken. I've no idea why.
Nice, it gets a lot further on POWER3 now :) It stops right here:
time_init: decrementer frequency = 93.748235 MHz
time_init: processor frequency = 375
Hi,
> I've just updated the installer image to have no POWER4+ optimization,
> but the language chooser seems to be broken. I've no idea why.
Nice, it gets a lot further on POWER3 now :) It stops right here:
time_init: decrementer frequency = 93.748235 MHz
time_init: processor frequency = 375
> This option is enabled because the kernel was targeted to IBM pseries systems
> which have POWER(4/4+/5) processors.
>
> I've disabled this in the config now, but will rebuild the kernel on the next
> build cycle since this is somewhat time consuming. Will trop you a message.
Thanks! Im loo
Hi,
> There's a 64-bit tftp installer image based on kernel 2.6.10 here:
>
> http://debian.gonicus.de/debian/dists/sarge/main/binary-powerpc/pseries.img
>
> Since most installer packages are not "official" yet, you've to continue the
> net installation by choosing the mirror manually to soun
> I just tried it on my POWER3 box. You dont happen to have
> CONFIG_POWER4_ONLY enabled do you? That option enables some minor
> optimisations that actually prevent booting on older boxes.
It boots on a 1.6GHz JS20 blade. Unfortunately I couldnt bring up a
network, we need the tg3 driver as a m
> Oh, if it is the js20, i think we had had some report of people trying to make
> it work some time back. I don't think d-i is already upto it, but the work
> Cajus is doing should help. There may be kernel issues, but maybe the latest
> bunch of 970Fx fixes will help, or maybe you need a ppc64
Hi,
> Why won't the 32bit power4 kernels boot on these machines ? They should, only
> the iseries really need a 64bit kernel.
The 32bit kernel does not have the pseries LPAR interfaces and so will
not boot on a partitioned POWER4 box or any POWER5 box.
Anton
Hi,
> I haven't tried it, but the error does look familiar. I think this is
> the error you get when binaries get too many symbols. The TOC normally
> fits in a single 16bit offset window. If your binary gets too big, it
> can't use simple immediate offsets to access individual elements. I
> ha
Hi,
> I have downloaded xlc ibm compiler for suse (trial version) but ppc64
> isn't supported by alien. So I unpacked everythings but I didn't
> success in running it (xlc doesn't found 1501-231 message). Does
> somebody already have done it ?
>
> I really want to run it under debian since
Hi,
> Ok, mmm, you mean the pcnet32 driver is not in the debian-installer net
> drivers ?
>
> It is in the nic-extra-modules, which is not part of the initrd, we will
> fix this, either move it to nic-modules or add the nic-extra-modules to
> the initrd.
FYI to cover most RS6000/pseries boxes
> I've heard people mention on this list that they are running IBM's Java
> package rather than the (elderly) Blackdown one. Unfortunately, I
> cannot for the life of me find a download link for it on IBM's site.
> Could someone please point me in the right direction so that I can get
> this
> So, as I've noticed that I can't successfully compile a 64bit powerpc
> kernel using any sort of 'normal' kernels (or it may be a GCC issue).
> Precisely what toolchain/kernel sources (ie give me URL's or debian
> package names) do I need to build a ppc64 kernel?
Can you elaborate? 2.6 shou
Hi,
> Mmm, maybe it should be possible to create a proper kernel package for
> your boxes, could you send me a .config file for a 2.4.22 kernel ? Will
> the standard linuxppc_2_4 tree do, or do you need special patches ?
We need to get the 64bit ppc cross compiler into debian, it sounded
like t
Hi,
We tested debian-installer (daily build from a day ago) on a ppc64 box
and found a few issues. To keep life interesting, we also used a 2.6
kernel.
1. Installer requires devfs support. In 2.6 devfs is pretty much
deprecated, so it would be nice if d-i could handle a non devfs kernel.
I
> When i understand you right, i have to install and compile the
> Toolchain on my System and after that i can compile the
> patched Kernel from penguinppc64 ?
> Sorry, i'am not yet an Insider but where can
> i find the 2.4.21-pre6 Code under Marcelo's Directory on kernel.org ?
If it becomes all
Hi Rolf,
> How can I help out testing Sarge on IBM pSeries systems ( I have access to
> a lab full of these systems )?
Eventually Id like to see a debian CD that boots on pSeries boxes. I
built a woody one recently but I run into problems during the install.
Im not adventurous enough to rebuild
> I have six shiny new IBM p655 nodes
Great!
> and I can't do a thing with them...
Not great.
> I'll save AIX aches for else where, but my Debian problem is that I
> can't seem to get them to tftpboot (and they have no removable media).
>
> the get IP and the boot file name correctly from th
Hi John,
> Does debian support X on RS6K?
>
> I have IBM 256-bit graphics rasterizer [Fire GL1] card. I tried
> using the generic vga settings but
> it complains about the clocks line.
Interesting, is this a standard RS6000 card? If so what is the IBM
name for it?
> Also, does debian su
Hi,
> Is any one running Debian on an IBM pSeries server?
>
> I have a p655 on the way and I'm wondering what my chances are.
>
> I have fairly extensive experience with Debian, and no experience with
> IBM Powerpc based machines or AIX.
>
> Any and all pointers and suggestions welcomed.
Ive
> Does anybody have expirience with this Graphic-Adapter ? I can't even see
> the Boot Console (over a serial Line it's ok).
> When i use the Adapter, i see two small reflections of the console with
> unreadble text. I think it is a syncronisation Problem.
> I don't wanna use X in the moment, the
Hi,
I submitted some patches for strace on ppc a few months ago but nothing
has happened. The worst one is the fact that strace tries to insert
an intel assembly instruction in order to lock a child process in
a busy loop. This makes the -f option completely unreliable.
Can someone do an NMU for
> It sounds a lot like the cases in i386 where a given hardware module
> isn't compiled into the kernel.
It does. Is the SYM53C8XX driver compiled into the boot disk kernel?
Anton
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTE
> Dear Friends,
> This is the first time that i write to you
> and i don't know is this email destination
> is rigth for my questions.
> If No, please, tell me where email.
>
> I have:
> IBM RISC System/6000
> model 43P-140
> other informations:
> 640e 200 MHz
> 7043 44-L0258
> firmware TIG 97112
> I'm being freaked out by a really weird bug.
>
> iBook2, running testing, with 2.4.16-ben0 as the kernel.
>
> The machine is convinced it's a month ahead (as the headers on this mail
> probably say).
It sounds like a kernel bug that should be fixed in a more recent
kernel. It wasnt a laptop b
Hi,
> wmb is defined as
>
> #define wmb() __asm__ __volatile__ ("eieio" : : : "memory")
>
> however, ``eieio'' has no effect on memory, that is
> Write Through Not Required, thus I think it should be
>
> #define wmb() __asm__ __volatile__ ("sync" : : : "memory")
While the original ppc spec
Hi,
> even a small start would be helping me get better RS/6000 support in
> ybin, since the boot-floppies completely rely on ybin to make
> yaboot systems bootable.
I have debian running on a number of RS6000s. Ignoring the install,
all that is required (on POWER3 machines) is to fix libc to
> btw mmap("/proc/bus/pci/...") was added around 2.4.4 right ?
Yep 2.4.5. From memory the X patches I saw did not allow the
X server to fall back to mmap("/dev/mem") which is important.
Anton
Hi,
> - r128 doesn't work without UseFBDev at least on Pismos (I suspect all
> UniNorth Macs) because we're now trying to do ISA I/O with the help of a new
> system call, but the server crashes. It works fine on those machines without
> it, so what would we lose by disabling it in r128 #ifdef __
> The big endian patches change the code to use little endian ordering
> for all on-disk structures. IMO this is a mistake, and certainly
> costs a dear performance penalty, because on big endian processors,
> this method requires converting endianness both ways (reading and
> writing) for all m
37 matches
Mail list logo
