Re: p-server 640 debian install questions
Ethan Benson wrote: > > On Wed, Jun 06, 2001 at 07:26:58PM -0400, Rahul Jain wrote: > > > > I have a p-server 640 at work that I'm trying to install debian on. > > It _seems_ to be CHRP, but OF has info about prep too, so I don't know... The p640 is a CHRP box. Well mostly. These boxes do run linux, they run it rather well! Debian probably won't work tho, especially if they still have the cache line bug in their glibc. > > The hardware: > > 2 375 MHz POWER3 CPUs > > an eepro100 connected to the network > > a matrox g200 > > 2 18GB SCSI hard disks > > a SCSI CDROM drive > > _no_ floppy drive Yup, sounds good. > > The current software: > > SuSE 7.1 booting via yaboot (installed with lilo??) > > lilo in this case is suse's reinvention of ybin. ybin supports the > raw bootstrap partition chrp machines use, read the man page. > > > The desired software: > > debian unstable running kernel 2.4.5(-xfs) > > > > The problem: > > I can't figure out how to get it to boot off the debian cdrom. > > at the of prompt, I've tried: > > setenv boot-device cdrom (cdrom is in devalias as /[EMAIL > > PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 or > >some such) > > setenv boot-image /install/chrp/linux (also tried prep) > > boot Take a look at the file /ppc/bootinfo.txt on the 3rd cdrom. That's one key for booting off of CD. > > I get something like "no valid PReP image found". Am I supposed to use a > > boot-image of \\yaboot? You can boot a straight kernel zimage if you want... or yaboot works as well or the file above that I just mentioned... so you can do something like boot cdrom:,\zimage boot cdrom:,\ppc\bootinfo.txt etc etc > \\yaboot is a Mac specific hack, it won't work on non-apple OF. a > yaboot binary is at /install/powermac/yaboot We've been extended yaboot so it isn't mac specific anymore. > im not sure if it works on non-macs the way its compiled though. If you're getting it from benh, it should be fine. Regards, Tom -- Tom Gall - PPC64 Maintainer "Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://www.ibm.com/linux/ltc/projects/ppc
Re: Can't boot from hd on RS/6000
Jens Kutilek wrote: > > Hi, > I have installed Potato on a IBM RS/6000 B50. > I've upgraded to kernel 2.4.8, and am able to boot the system from > floppy. > It just won't boot from hd. > My partitions are like this: > /dev/sda1 PReP-boot 4M > /dev/sda2 /boot 8M > /dev/sda3 / 2G > /dev/sda5 swap > ... Hi Jens, > I compiled yaboot 0.8 with a patch from IBM > <http://oss.software.ibm.com/developer/opensource/linux/patches/ppc/yabo > ot-misc.patch.gz > and then did "dd if=yaboot of=/dev/sda1". You shouldn't need this patch, especially if you jump to a recent version of yaboot such as 1.1.1 or the like. > Now when I try to boot from hd it says: > Welcome to yaboot version 0.8 > Config file read, 4096 bytes > boot: > Loading kernel... > Elf32 kernel loaded... Looks like yaboot is working just fine. > ... and then nothing else happens. Do you have any numbers on the lcd display on the front of the B50? This looks almost like something isn't right with the kernel. I assume that you're using the same vmlinux for your default kernel in your yaboot.conf that you are dd'ing when you tried that. > I also tried copying the kernel directly to /dev/sda1, then it boots, > but doesn't find the root fs/init. > What can I do? I also tried quik, but it didn't work either. If you copy the kernel directly, you should set the OF variable boot-file to at least root=/dev/sda3 > Jens. Regards, Tom -- Tom Gall - PPC64 Code Monkey "Where's the ka-boom? There was Linux Technology Center supposed to be an earth (w) [EMAIL PROTECTED] shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian (h) [EMAIL PROTECTED] http://www.ibm.com/linux/ltc/projects/ppc
JFS for PowerPC Linux
Hi All, I had some time this past week to try this out. JFS is the Journalled File System technology from IBM that we've open sourced. This is the same as what AIX has. (Minus the logical volume manager) It's still in a "pre-alpha" state but you can create the file system, read and write files into it so from that perspective it's mighty cool. But don't go and put your valuable data into it just yet! And hey if you feel like jumping in and helping out, it'd be great. Take a gander at oss.software.ibm.com/developerworks/opensource/linux. You'll want the patch for PowerPC linux and the 0.0.7 version of the code. I was on a 2.3.99-pre9 kernel / yellow dog 1.2 setup when I was playing with it but hopefully for you debian folks it'll just work. Regards Tom Tom Gall IBM Linux Technology Center, PowerPC Linux Team w) [EMAIL PROTECTED] h) [EMAIL PROTECTED]
Re: RS/6000 frozen Display is 185
Hi Fabricio, What kind of RS/6000 is it? Fabricio Scariott wrote: > Hi. > I have make a floppy boot disk(boot.bin) and after load boot my machine > frozen. > With the file zImage.prep it frozen too. > The display led is 185 > > Thanks, Fabricio > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Tom Gall - [embedded] [PPC64 | PPC32] Code Monkey Peace, Love & "Where's the ka-boom? There was Linux Technology Center supposed to be an earth http://www.ibm.com/linux/ltc/ shattering ka-boom!" (w) [EMAIL PROTECTED] -- Marvin Martian (w) 507-253-4558 (h) [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Woody installation on IBM 44P-170 - Success & boot-floppies/debian-installer
Rolf Brudeseth wrote: > Well, I was finally able to get Woody installed on an IBM 44P-170 (Power3) > system. > > I can document the steps if there is an interest. I booted via BOOTP/tftp, > downloaded the kernel, basedebs.tar and driver.tgz with wget, and got the > rest with dselect/apt. > > I do not think that 'boot-floppies' would have to be modified much to work > properly; however, since 'debian-installer' is what will ship on the next > release I will see where I can help out there. > > Rolf I'm interested! (And happy to post it to linuxppc64.org too) Regards, Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Woody on IBM RS/6000 7025 F50
George Karaolides wrote: > Hi all, > > I'm trying to install Debian woody on an IBM RS/6000 7025 F50 using the > latest floppies. > > I'm having very little success so far. The best I've managed is to get a > "Booting:" message from OpenFirmware using the chrc rescue floppy and the > OpenFirmware command > > 0> boot floppy:.\linux.bin root=/dev/fd0 load_ramdisk=1 > > However, the booting procedure stops after the disk is read, nothing > appears on the screen and the only way to get control of the machine back > is to power it down. Hi George, None too surprising. You want a kernel compiled as CHRP. Tho one question, is your box an SMP box? If so, make sure SMP is turned on. Otherwise the standard CHRP config in arch/ppc/configs should work just fine. Regards, Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
F50 Debian Install
Hi All, Well I've started to get alot more adventurous and this morning started an install of an F50 Rs/600 which is a CHRP box. Doing an install over the net failed for two reasons. 1) There needs to be an SMP chrp kernel for the F50 and it's ilk for debian. Anyone take a contribution of a config file? 2) The drivers.tgz downloaded for chrp from ftp.us.debian.org// also appears to be foobar. The system couldn't unpack it. In the grand scheme of things it's ok since I have to roll my own kernel anyway and modules and such issues I can handle. Still nice to fix it for the average bear. Thanks! Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
Re: Woody on IBM pSeries 630 (POWER4)
JP Glutting wrote: > Hi, > > I am trying to figure out how much work it will be to get Debian working > on an IBM pSeries 630 (with a one-way POWER4). We are getting one here > at work, and we will be transfering our software from our current > server, a dual Athlon, onto that. IBM has worked some things out with > RedHat and SuSE for installations of Linux after shipment. I contacted > the SuSE folks, and they said that they have a working 64-bit compiled > kernel that should work. > > I have a few questions for the list: > > Does Debian have a kernel that will work on this chip? They just need to build ppc64 kernels. Sources are available from linuxppc64.org for everything from the toolchain to the kernel itself. > What are the trade-offs for 64 vs. 32 bit kernels? 32 won't work on that hardware. Sorry. 8-( > How much trouble will it be to compile source from unavailable packages > on this computer? Unavailable packages? huh? Not sure what you mean here? Regards, Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
Re: Woody on IBM pSeries 630 (POWER4)
JP Glutting wrote: > Thanks! > > Tom Gall wrote: > > JP Glutting wrote: > > >>What are the trade-offs for 64 vs. 32 bit kernels? > > > > > > 32 won't work on that hardware. Sorry. 8-( > > Ouch.. But it is possible to run the 32-bit compiled software in > "userspace", or am I completely off the track here? Software compiled as 32 bit should work just fine. The one gotcha is that your glibc is built without the memcpy.S routine that uses the dbcz instruction. Or inline assembler that uses it. > >>How much trouble will it be to compile source from unavailable packages > >>on this computer? > > > > Unavailable packages? huh? Not sure what you mean here? > > > Well, I am assuming that Debian has binaries that work on the POWER4 as > well as other PPC chips, although that may not be the case. Any > information would be helpful. > > I guess what I meant were things that are not available in Debian (we > have to compile lots of little bioinformatics tools we can get the > source to). Of course, we have other machines we can use these for, so > that should not be too much of an issue, but are there any big compiler > issues with the POWER4? Assuming you are building 32 bit apps, just use the current crop of ppc32 compilers. 64 bit applications are just now possible since the 64 bit ppc glibc patches have just hit the streets. > Actually, what might be good to hear is what steps I need to take to get > a working Debin installation on a p630, starting from scratch. I need to > compile (cross-compile?) a kernel (or get one that is already compiled), > make boot disks, and do the install. What am I missing? What problems am > I going to run into? I'm about to install my 270 (a 64 bit ppc box) for the first time as debian. Earlier Rolf Brundeseth has posted to the list (and folks their commends) about how to install. Your 630 route should be about the same. Regards, Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
Re: Woody on IBM RS/6000 7025 F50
George Karaolides wrote: > Hi, > > I have no idea whether the Matrox G200 shipped with the box. Hmmm might have... doesn't matter it should work and does work with linux. Now this is an RS/6000 Matrox card right? > Any pointers on how to use Minicom to access the console on the serial > port? I have a null modem cable right here but I haven't tried this > before. Just fire it up... connect 9600 8N1 ... just works! You can pass console=ttyS0,9600 then to use serial... > > If indeed the kernel is running, I should be able to connect via the > serial port at any time after boot, is that correct? Yup ... or see the wonderful xmon problem... which means you're in the kernel debugger. 8-/ Regards, Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
Re: Woody on IBM RS/6000 7025 F50
George Karaolides wrote: > On 21 Aug 2002, German Poo Caaman~o wrote: > > > I use kermit (on a debian machine). Just: > > # kermit > > C-kermit> set line /dev/ttyS0 > > C-Kermit> set carrier-watch off > > C-Kermit> connect > > > > (it's belong to non-free). > > > > Tried as you suggest. I don't see anything much... :( > > Should I be doing something else after I connect? Ummm you do realize you're not going to get any output from the system unless you have configured linux to use a serial console. (ie not just your kernel param but also set your inittab) I don't recall an f50 is like a say 270 which has a service processor that even when the machine is off, you can hit return and talk to the service processor. (Tho that might be the case ... it's been a couple of years!) So the big question is, when you are looking for output from the machine? If you want to say for example get to the OF prompt you have to get the machine to relook for consoles. One way to do this is with the machine turned off, unplug the keyboard and mouse and then plug in the mouse in the keyboard slot. (Yes I know it sound goofie but it works) then turn your machine on. Later in the boot sequence it should try and output to all devices where a console would be possible (including serial) and would allow you to choose (From the firmware's perspective) the serial port as the console. Regards, Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
Power3/44P 270 Debian Install
Hi All, Welp... I've had YDL 1.2 on this 44P 270 **FOREVER**. Trivia for the day, this machine was the second power3 box to run linux. Time to move forward so I thought I'd throw debian on and see how the 3.0 installer behaved. Really only one snafu thus far and only one snafu on the horizon. In my case since i started with a "working" system with yaboot on it, it was fairly easy, I just took a working 32 bit power3 linux kernel and used that but with the following yaboot.conf entry: image=/boot/vmlinux-32-2.4.18 label=debian-install initrd=/root.bin initrd-size=8192 append="root=/dev/sda2 console=tty0 video=matrox:memtype:4" The matrox part is since i have a g200 in the system, need to tap it on the shoulder so it uses all 8 meg on the card. So this successfully brought up kernel and into the installer. Tho the first screen I saw was a dull gray background with a cursor in the upper right. I hit the tab key a couple of times which seemed to "wake" it up and then put me in into the chooser for languages. Then from there... standard stuff. I did skip the kernel/module install step since afterall I need a custom kernel. And this is where the second snafu comes into play. I needed to make myself a boot kernel on floppy before hand. OOoops! O well, easy enough to do, so when we boot the first time to install the rest of the packages, that part will work. Something for tomorrow, but overall quite encouraging for running linux on at least power3 systems. Full blow ppc64 boxen tho would seem to be a problem tho as on some of those you can only run the 64 bit kernel and I'm not sure the installer will react well to a uname of ppc64. But knows! Certainly worth a try for the adventurous soul. Regards, Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
Re: PowerPC kernel repository (was: Woody on IBM RS/6000 7025 F50)
Rolf Brudeseth wrote: > > Hello > > > > It sounds good to me. I would like to contribute the rs6k effort on > debian. > > Amen bro! > > We need to get boot floppies which work as soon as possible. Also, we > need to > > get working install cdroms. > > What do you mean by boot floppies? Do you mean the boot-floppies installer > or bootable floppies? The former will be replaced by debian-installer on > sarge, while the latter is not supported on all RS6000/pSeries systems. > Some do not even have floppy drives anymore. Indeed and for those it would be nice to have a small boot iso > I am currently trying to figure out how to make a single CDs that is > bootable both on PREP and CHRP (IBM) systems. I have some anecdotal > evidence that there is more to it than just pointing to the boot image from > Open Firmware and/or setting up the /ppc/bootinfo.txt file correctly. > Another issue is the 'prep-boot' and 'generic-boot' switches for the > mkisofs command, which are used in creating PREP and CHRP bootable CDs, > respectively; are mutually exclusive according to the man page. I discovered this yesterday. I thought on my 270 I would just be able to dump a zimage on a cd and have it be able to boot from it from the OF command line. Heck no! There definately seem to have to be magic bits present on the cd for OF to be able to load a zimage from a CD. A normal old ISO won't do. Quite surprising! Anyway... t'will have an update on my 270 install story when the journey is complete... I'm somewhat stuck at the moment. Regards, Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
Re: AmigaOne
Ole-Egil Hvitmyren wrote: > Claas Langbehn wrote: > > >Hello Ole-Egil, > > > > > >You said, you are already working on an AmigaOne. > >I think it is a really interesting system which > >just has been started to be shipped. I think it depends on the goals that you have. You can't compare one of these things to a TiPB for instance or a Dual G4 system. It's a reasonable G3 based motherboard and could be a reasonable linux box in time. More PowerPC hardware to choose from is always a good thing. But don't forget the AmigaOne is about Amiga and the efforts surrounding that OS. That's not a bad thing, but obviously that's not an open source solution. > >So, why don't you tell us about your experience > >with AmigaOne and (Debian) Linux. I've got YDL on mine. But no reason why Debian shouldn't work. > >What about the hardware support with the current > >2.4.19 kernel? Is already everything working as > >expected? So can we already buy the mainboards or > >shall we wait some more time? Boards ask Eyetech. On the kernel front, it's not an openfirmware style based solution anymore and falls more into the custom front. Early on this is somewhat of a bummer from the kernel perspective but in time it hopefully will work itself out. > >And for the critics: If the AmigaOne is crap, > >which system is better? Of course, we are talking > >about PPC systems only. Again depends on your goals. If you wanna run OS X for instance as well as linux then I'm not so sure this would be the solution for you and perhaps Apple hardware might be the better choice. Wanna run the Amiga OS in time, then obviously this is a good choice. > Well, for now I can only say the linux kernel isn't ready. Tom Gall > disappeared from our mailing list a month ago with the words "I'll start > coding on the kernel now, look for patches on the POP page on > penguinppc.org". So Hyperion (who is already doing AmigaOS PPC and was > contracted from MAI to port PPCBoot to the boards) has been helping out. Indeed. I don't have PPCBoot in ROM like Ole does. Running PPCBoot out of RAM booted from the softex of was turning out to be rather difficult. Without a real ROM there wasn't much point. > Anyway, I can't tell you to go and buy, but if you order now the board > won't be sent to you for another month. So you might as well wait until > they are in stock. > > Everything is NOT already working as expected. But it is coming along. > I've come down with a severe case of real life work, and I'm trying to > do too many things at the same time here. Life happens. Regards, Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
Re: java 1.4 for ppc
"Kevin B. Hendricks" wrote: > Hi, > > AFAIK, none exists. I am basically the Blackdown JDK for ppc porting team > and I simply have not had the time to start working on JDK 1.4 yet. My > real need is for help from someone who understands PPC assmebler and > instruction set well and can help implement HotSpot for 1.4. > > IBM has a wonderful JDK with a fast JIT that I have used but it seems to be > a JDK 1.3.1 version only. As far as I know they have not even released an > alpha or beta of JDK 1.4 for ppc linux. > > Sorry I can't be more help. > Greets, Afraid I won't be of greater assistance here but on the IBM developerworks web site for Java + Linux it does state the availability of Java 1.4 for Linux on PowerPC in "mid 2003". Regards, Tom > > Kevin > > On April 21, 2003 07:18 am, florian wrote: > > hi! > > > > does anybody know of a java 1.4 implementation for > > ppc? i searched around quite a bit. but didnt find anything.. > > > > anybody knows more? > > > > ciao! > > florian > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
Re: java 1.4 for ppc
florian wrote: > hey tom and kevin! > > thats already good to know that at least some 1.4 is coming > soon.. tom, do you know if any betas will be available already > before mid 2003? > > cant hardly wait =) > > ciao! > florian Hi Florian, Honestly don't know. I just read the web page. www-106.ibm.com/developerworks/java/jdk/other/portingplans.html Regards, Tom -- Tom Gall - [Embedded] [ppc|ppc64] Code Monkey Peace, Love and Linux Technology Center "Where's the ka-boom? (h) [EMAIL PROTECTED] supposed to be an earth (w) [EMAIL PROTECTED]shattering ka-boom!" (w) 507-253-4558 -- Marvin Martian http://www.ibm.com/linux/ltc
Re: Running Debian Linux on a RS6K H50
On Friday, June 13, 2003, at 03:31 AM, [EMAIL PROTECTED] wrote: Dear All, I have an IBM RS/6000 7026-H50 with 3 332MHz PowerPC 604e Procs, can or has anyone tried to run Debain Linux on it? Chris B If I remember my lore correctly, that's pretty much the same as an F50. So build yourself an SMP chrp kernel, and away you go, debian does install and run. Regards, Tom Tom Gall - [Embedded] [PPC64 | PPC32] Linux Peace, Love & Linux "Where's the kaboom? There was Technology Center supposed to be an earth shattering (w) [EMAIL PROTECTED] kaboom! " -- Marvin Martian (h) [EMAIL PROTECTED]
Re: Apple PowerMac G5
On Thursday, June 26, 2003, at 03:54 AM, Gabriel Paubert wrote: On Thu, Jun 26, 2003 at 08:48:57AM +0200, Christoph Hellwig wrote: On Wed, Jun 25, 2003 at 04:46:50PM +, paubert wrote: Not exactly since there are several claims that this is an Apple design, but the 970 bus "was designed exclusively for Apple" according to IBM. I'm speculating, but I would not be surprised if in exchange IBM had the right to use the northbridge in its own designs (they also manufacture it in the same process as the 970). It's an apple design manufactured by IBM and IBM will use it in their new PPC970based blades, too. Thanks. Great to know. This may mean that the docs will become public. Hi Gabriel, The docs are starting to show up slowly: http://www-3.ibm.com/chips/techlib/techlib.nsf/products/ PowerPC_970_Microprocessor Do you know if IBM has the right to sell the chip to third parties. (the bridge, not the 970 which is their design) ? IBM Micro Electronics would be the best folks to pose this question to. I do have a couple of contacts there, I'll see if they might be willing to answer that question. Regards, Tom Tom Gall - [Embedded] [PPC64 | PPC32] Linux Peace, Love & Linux "Where's the kaboom? There was Technology Center supposed to be an earth shattering (w) [EMAIL PROTECTED] kaboom! " -- Marvin Martian (h) [EMAIL PROTECTED]
Re: Linux on RS/6000 E20
German Poo Caaman~o wrote: > > On Mon, 22 Oct 2001, Andrew Sharp wrote: > > Olaf Hering wrote: > > > On Fri, Oct 19, Benny Siegert wrote: > > > Dont try to run 2.2 on non-IBM PRePs. > > > Try http://master.penguinppc.org/~olaf/2.4.12/zImage.prep or > > > ftp://ftp.suse.com/pub/suse/ppc/kernel/2.4.2/zImage-2.4.2.prep > > > > I thought an RS/6000 WAS an IBM PReP? > > No. I have a RS/6000 CHRP64 (44P 170). Debian's glibc doesn't > work in that :-( Pick up SuSE 7.1 or later. Works great on the 170. While it's not debian at least it's linux. Regards, Tom -- Tom Gall - [embedded] [PPC64 | PPC32] Code Monkey Peace, Love & "Where's the ka-boom? There was Linux Technology Center supposed to be an earth http://www.ibm.com/linux/ltc/ shattering ka-boom!" (w) [EMAIL PROTECTED] -- Marvin Martian (w) 507-253-4558 (h) [EMAIL PROTECTED]
Re: Luxo jr.
Jens Schmalzing wrote: > > Hi, > > our department is thinking of buying a number of new desktop machines, > and we are considering the new iMac as an alternative to the standard > i386 boxes. Has anybody here run Debian on one of these things yet? > Any glitches, caveats, pitfalls? Hi Jens, Well the key is that the box isn't yet in the hands of those who if it needs fixes for any reason can create those fixes. It's also quite possible it'll just work. No need to worry tho, people will put in the effort to get it working > Thanks and best regards, Jens. Regards, Tom -- Tom Gall - [embedded] [PPC64 | PPC32] Code Monkey Peace, Love & "Where's the ka-boom? There was Linux Technology Center supposed to be an earth http://www.ibm.com/linux/ltc/ shattering ka-boom!" (w) [EMAIL PROTECTED] -- Marvin Martian (w) 507-253-4558 (h) [EMAIL PROTECTED]
Re: Luxo jr.
Adam C Powell IV wrote: > > Tom Gall wrote: > > >Jens Schmalzing wrote: > > > >>Hi, > >> > >>our department is thinking of buying a number of new desktop machines, > >>and we are considering the new iMac as an alternative to the standard > >>i386 boxes. Has anybody here run Debian on one of these things yet? > >>Any glitches, caveats, pitfalls? > >> > >Hi Jens, > > > >Well the key is that the box isn't yet in the hands of those who if it > >needs fixes for any reason can create those fixes. It's also quite > >possible it'll just work. > > > So there are drivers for the nVidia GeForce2 DRI on PPC? I'd think that > will be the biggest obstacle, and that's why I'm not rushing out to get > one, though I'm in the market for something like it. Then again, having > to maintain binary drivers for multiple kernel/platform combinations > might finally push nVidia to open up their code, but I wouldn't count on it. Well I have faith in Annex and his latest efforts with nVidia's GeForce2. Sure things aren't 100% done yet but hey it's a start. Regards, Tom -- Tom Gall - [embedded] [PPC64 | PPC32] Code Monkey Peace, Love & "Where's the ka-boom? There was Linux Technology Center supposed to be an earth http://www.ibm.com/linux/ltc/ shattering ka-boom!" (w) [EMAIL PROTECTED] -- Marvin Martian (w) 507-253-4558 (h) [EMAIL PROTECTED]
Re: AmigaONE && Debian (unstable?)
Jens Schmalzing wrote: Hi, Benjamin Herrenschmidt writes: Can't uboot load the ramdisk separately like yaboot can ? Duh, I must have misunderstood this then. So uboot is the bootloader for AmigaOne? Then it should be taught to load an uncompressed kernel and a separate ramdisk from a real root filesystem. Also, it should be packaged for Debian, probably in a separate package from the other PowerPC bootloaders. We One item of note. In the case of the AmigaONE it's burned into EEPROM. (Least it was when I was playing around with it which was some time ago). These boxes originally had an implementation of OF which was .. well it wasn't quite perfect, but it could load yaboot at least... You are quite right tho, it would be desireable for it to know how to load a kernel and ramdisk from a file system. Regards, Tom Regards, Jens.
Re: Is there GXT 4000 support
Greetings, On Sep 7, 2004, at 4:59 AM, Marcus Schwarz wrote: Hi again. Some people told me a lot of intersting things about sarge on the 7044-170 (44p). But before I start I would like to know if the GXT4000 Graphics Card is supported. No it is not. Sorry! Regards, Tom FB would be nice but an accelerated X would be even more nice ;) Regards Marcus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Tom Gall Gentoo/PPC64 Team Leader [EMAIL PROTECTED]
Re: ppc64 port
Greetings, Benjamin Herrenschmidt wrote: On Tue, 2004-04-27 at 23:36, Cajus Pollmeier wrote: Hi! Just a simple query... I _may_ have a chance to get a ppc64 machine. Is anyone interested in such a port? It's fun stuff and there seems to be a bunch of interest. I know that it basically works with the 32 bit binaries, but the installation is non trivial right now and having no 64 bit code isn't optimal, too. Well, the later is not true. 32 bits code tend to run faster than 64 bits code on ppc64. Unlike amd64 where you win by having access to more registers, on ppc64, you just end up having to use more instructions to load a full constant in a register ;) Well let's be careful here. As there old saying goes, there's lies, damn lies and benchmarks. Yes some operations on PPC64 are slower than they are on PPC32 but that is not universally true. Given that things are a bit early in the life of PPC64 current performance is not necessarily a prediction of future performance. It's not like everyone is working on ppc32 performance and forgetting ppc64 entirely. Overall, we can go the gentoo way, and do a full 64 bits debian distribution independant from the 32 bits one, or we can simply do like other distributions do, and I think it makes some sense, is to have a biarch distribution. The main lot of packages stays 32 bits. Let's review where some of the the other distros are at and what they are doing for x86_64 as well. Everyone (and I mean everyone) has the ability to run both 32 bit and 64 bit code. The design choice is what is the "default" mode. IE if a user just calls gcc, are they going to get a 64 bit app, or a 32 bit app. Install something like apache, will it be 64 bit or 32 bit... etc etc. 1) SuSE SLES 8 for PowerPC64 - Default is 32 bit 2) SuSE SLES 8 for x86_64 - Default is 64 bit 4) Gentoo/ppc64 - Default is 64 bit 5) Gentoo/x86_64 - Default is 64 bit 6) Redhat Enterprise for PowerPC64 - Default is 32 bit 7) Redhat for x86_64 (fedora) - Default 64 bit 8) Redhat exterprise for x86_64 -Default 64 bit and IIRC Debian x86_64 is 64 bit as well. But we need a biarch gcc and the 2 libcs. Then, for each lib package, we can build both the ppc and the ppc64 deb and they can be both installed at the same time. But the first thing to have is a 64 bits kernel. That we really want. For that, we need to be able to build it. So the first thing that need to be done is to have a biarch toolchain. gcc 3.4 can be compiled biarch, but doing the "initial" biarch build is very difficult. I wouldn't say that. Tedious yes, difficult no. Besides, the debian x86_64 folks build bi-arch already. Just grab their build scripts. Regards, Tom
Re: ppc64 port
Albert Cahalan wrote: On Wed, 2004-04-28 at 09:13, Tom Gall wrote: The design choice is what is the "default" mode. IE if a user just calls gcc, are they going to get a 64 bit app, or a 32 bit app. Install something like apache, will it be 64 bit or 32 bit... etc etc. 1) SuSE SLES 8 for PowerPC64 - Default is 32 bit That may be, but they did manage to compile a number of packages as 64-bit. This isn't another case of slapping a 64-bit kernel and libc on a 32-bit install and calling it good. Yes exactly... but on the other hand it's not a full 64 bit environment either. Clearly it's something to get one started and be somewhat useful. If you really want a 32-bit userspace, remember that you can simply run a 32-bit distribution. Exactly. 2) SuSE SLES 8 for x86_64 - Default is 64 bit 4) Gentoo/ppc64 - Default is 64 bit Well, that looks like the thing to run on a Mac G5. Gentoo is planning ahead and keeping things simple. Alternately, run a pure 32-bit system. Why not? Let's not complicate things for no good reason. Again, exactly. Given that one can very easily do something like install 64 bit default distro x to /dev/sda2 install 32 bit default distro x to /dev/sda3 boot kernel with root=/dev/sda2 mount /dev/sda3 /mnt/32bitenv cd /mnt/32bitenv mount -o bind /dev ./dev mount -o bind /proc ./proc mount -o bind /tmp ./tmp chroot . /bin/bash (or whatever) and there ya go, 32 bit env that can even run x apps displayed on a 64 bit x windows. Just works. It's not complicated, one doesn't have to battle AT ALL any of the package issues or worry about a 64 bit package installing over a 32 bit package etc etc etc. The whole jam a 32 bit env and a 64 bit env into the same file system seems wrought with problems. It can be done yes... but the cost in complexity seems far too high. Regards, Tom
Re: ppc64 port
Greets, Peter Bergner wrote: On Wed, 2004-04-28 at 08:13, Tom Gall wrote: Benjamin Herrenschmidt wrote: Well, the later is not true. 32 bits code tend to run faster than 64 bits code on ppc64. Unlike amd64 where you win by having access to more registers, on ppc64, you just end up having to use more instructions to load a full constant in a register ;) Well let's be careful here. As there old saying goes, there's lies, damn lies and benchmarks. Yes some operations on PPC64 are slower than they are on PPC32 but that is not universally true. Given that things are a bit early in the life of PPC64 current performance is not necessarily a prediction of future performance. It's not like everyone is working on ppc32 performance and forgetting ppc64 entirely. Ben is talking about 32-bit app performance versus 64-bit app performance on 64-bit hardware, not app performance differences between 32-bit hardware versus 64-bit hardware. Getting back to what Ben said, yes, PPC64 apps do tend to need more instructions for some things. I will say that the compiler is smart enough to use fewer than 5 instructions for loading constants when it can. It's cases like code with RELOCS as well as the use of the TOC where we tend to get more instructions relative to 32-bit apps and that doesn't help your icache. Right but I think the assumption being put forward with no real data behind it is that is that ppc64 apps are always slower than ppc32 apps. 1% slower, 10% slower, these kinds of contexts mean something. I certainly don't disagree that there are certain code paths for ppc64 that are slower. But on the other hand the sky doesn't seem to be falling when running a ppc64 box as 64 bit. I'm aweful curious to do some comparisons. Let's review where some of the the other distros are at and what they are doing for x86_64 as well. Everyone (and I mean everyone) has the ability to run both 32 bit and 64 bit code. The design choice is what is the "default" mode. IE if a user just calls gcc, are they going to get a 64 bit app, or a 32 bit app. Install something like apache, will it be 64 bit or 32 bit... etc etc. 1) SuSE SLES 8 for PowerPC64 - Default is 32 bit 2) SuSE SLES 8 for x86_64 - Default is 64 bit 4) Gentoo/ppc64 - Default is 64 bit 5) Gentoo/x86_64 - Default is 64 bit 6) Redhat Enterprise for PowerPC64 - Default is 32 bit 7) Redhat for x86_64 (fedora) - Default 64 bit 8) Redhat exterprise for x86_64 -Default 64 bit and IIRC Debian x86_64 is 64 bit as well. Let's resort your list by arch: x86_64: 2) SuSE SLES 8 for x86_64 - Default is 64 bit 5) Gentoo/x86_64 - Default is 64 bit 7) Redhat for x86_64 (fedora) - Default 64 bit 8) Redhat exterprise for x86_64 -Default 64 bit and IIRC Debian x86_64 is 64 bit as well. ppc64: 1) SuSE SLES 8 for PowerPC64 - Default is 32 bit 4) Gentoo/ppc64 - Default is 64 bit 6) Redhat Enterprise for PowerPC64 - Default is 32 bit Yes, all x86_64 distros are making 64-bit binaries the default. My point here is two fold. 1) ppc64 and x86_64 share the same characteristic that they both have good 32 bit performance and compatibility 2) it is better that ppc64 and for that matter all 64 bit architectures to be consistant, be it across debian, or the open source universe? The question is why are they doing that, not "hmmm, if they're doing that for x64_64, that must be the correct answer for ppc64 too". The reason 64-bit is the default for x86_64 is as Ben mentioned above, they have access to more registers which leads to vastly less spill code versus 32-bit apps. Sixty-four bit apps on x86_64 have the same problem with extra code for some RELOCS, but that is overwhelmed by the reduction in spill code. Therefore, the correct solution for x86_64 is 64-bit apps are the default. It should not be forgotten that x86_64 is also a better 32 bit processor. For ppc64, we have 2 out of the 3 distros choosing 32-bit as the default and only Gentoo/ppc64 choosing 64-bit as the default. Tom, would you happen to know who decided Gentoo would default to 64-bit apps? ;-) Sorry, I couldn't resist the little dig! Wasn't me. It was Brad House. So back at ya! ;-) Yes I have an interest in a real 64 bit env for ppc64 and thus gentoo/ppc64 was born but that's entirely besides the point. Try building a reasonable *USEFUL* complete 64 bit environment any other way. It is the odd package in the linux community that cross builds well. And on a ppc64 box, with a default of ppc32, one is sentanced to the cross build penalty box for 64 bit code. This is an old tired debate. It's happened time and time again, from 8 bit to 16 bit to 32 bit and now 64 bit. Progress marches on, and the number of bits expands. I shouldn't wonder if this discussion won't be revisted again and for other orders of 2. :-) Certainly there w
Re: ppc64 port
Ian McKellar wrote: On Wed, 2004-04-28 at 12:38 -0500, Peter Bergner wrote: Yes, all x86_64 distros are making 64-bit binaries the default. The question is why are they doing that, not "hmmm, if they're doing that for x64_64, that must be the correct answer for ppc64 too". The reason 64-bit is the default for x86_64 is as Ben mentioned above, they have access to more registers which leads to vastly less spill code versus 32-bit apps. Also, IIRC the x86-64 ABI specifies that int is still 32 bit - so much of the memory penalty for going 64bit doesn't apply. int is 32 bits on ppc64 as well. Regards, Tom Ian
