model 150 almost there

2002-08-14 Thread John F Davis
ello

Thanks to the help of Hollis Blanchard, I almost have debian linux install
on my rs6000 model 150.  However I still need help.

Here's my situation I boot linux from netboot and then I mount my root
filesystem from floppy.  I have built a custom kernel
from the 2.4 devel tree using a cross compiler and I have dd'd a root
floppy using a debian chrp root.bin image.
When I boot the linux kernel, it asks me to insert the root floppy and hit
enter.  I do so and it soon after displays
a nice blue screen with centered grey field and black text. which says
Debian GNU Linux 2.2 boot floppy 2.2.23.  I hit enter,
the screen flashes up a dialog quickly which says something like, "The
installation program is determining the state of your system and the next
step of the installation procedure to be performed."  Then the screen
returns to the opening screen.  If I hit enter, it will repeat this
sequence ad nausem.

That sucks.

I can get to virtual terminal 2 and cd/ls about the filesystem.  I tried to
mount /dev/scd0 (My cdrom?) but it says the filesystem is read only and it
wont let me mount anything.  Which is weird
because, I can make a directory to mount the cdrom onto and mount says the
root filesystem is mounted rw.

Any idea what to do next?

JD







Re: model 150 almost there

2002-08-14 Thread John F Davis

Hello

Thanks for the help, but I have since solved the problem.  I rebuilt the
kernel without /dev fs support and
I have reached the next screen where I config the keyboard.

I need to know how to parition the disk now.  Do I create the partitions
like I normaly do in intel or
do I need to create a disk label like partition as in Sparc?

Thanks again for the help.  Hollis gave me the devfs tip in #debianppc

JD

Ole-Egil Hvitmyren <[EMAIL PROTECTED]> on 08/14/2002 10:42:34 AM

To:    John F Davis/Raleigh/[EMAIL PROTECTED]
cc:debian-powerpc@lists.debian.org
Subject:Re: model 150 almost there



On Wed, 14 Aug 2002, John F Davis wrote:

>I can get to virtual terminal 2 and cd/ls about the filesystem.  I tried
to
>mount /dev/scd0 (My cdrom?) but it says the filesystem is read only and it
>wont let me mount anything.  Which is weird
>because, I can make a directory to mount the cdrom onto and mount says the
>root filesystem is mounted rw.

It would seem you're trying to mount the cdrom using the "mount previously
initialized filesystem" menu entry. Right? Don't do that. You should
partition the harddisk and then mount/initialize the resulting partitions,
then later on, when the installation procedure gets to the point of
installing thing, select cdrom :-)

Ole-Egil







Re: Debian network installation on IBM RS/6000 44P-170 (POWER3) - HOWTO

2002-08-14 Thread John F Davis

Rolf,

Please update your docs to include some of my info.  I have a model 43p 150
which has a tenous
install of debian linux on it.  I am in a similar shape as you. e.g  I can
netboot, and auto mount my root fs from
hard disk, but I can not boot from hard disk.

Here is my saga:


Building the Kernel requires that I build the binutils, gcc cross compiler
from
scratch.  Here is how to do it:
1.  Download the binutils 2.11.90.0.8 from linuxppc website and build it.
2.  Download the gcc-2.95.3 from linuxppc website and build it.
3. Using rsync, I've downloaded both the 2.4 and 2.4dev kernel trees from
the mvista server per the directions on the linuxppc website.
4.  In either case, I copied the arch/ppc/boot/images/ibmchrp_defconfig to
my .config and then run make menuconfig.

Things I had to config in the kernel:
o  Turn off /def fs support.  From hollis, this kills the debian installer.
   In my case, this was what prevented me from getting past the first
screen.
   See previous post to this mailing list.
o  Enable ramddisk and initrd support.
o  Add the following options to the boot args:
   root=/dev/fd0 load_ramdisk=1
   hollis said I could do without those args and use this openfirmware
command
   instead: setenv boot-file root=/dev/fd0 load_ramdisk=1
o  Later, after you get up your system and you want to boot the kernel via
   tftpboot but not use the ramdisk and floppy but instead want to use the
harddisk as a root filesystem use these args:
   root=/dev/sda1


5.  make dep clean zImage
6.  Copy the arch/ppc/boot/zImage.chrp-r6k to my /tftpboot directory.
7.  edit /etc/inetd.conf to use /tftpboot instead of /boot for tftp server.
restart dhcpd and inetd /etc/init.d/dhcp restart and /etc/init.d/inetd
restart.

Here is my /etc/dhcpd.conf file:

always-reply-rfc1048 true;
deny unknown-clients;
not authoritative;
default-lease-time 600;
max-lease-time 7200;

subnet 192.168.0.0 netmask 255.255.255.0 {
  allow bootp;
  group {
host r6k {
  hardware ethernet 00:04:ac:97:92:05;
  fixed-address 192.168.0.2;
  filename "zImage.rs6000";
}
  }
}

Here is some other info:

I had to use tcpdump to determine the mac address of the rs6k.  SMS gave a
mac address, but
it wasn't the one used.  I don't know why.

Also, need to do:
arp -s ipaddy macadd eg. arp -s 192.168.0.2 00:04:ac:97:92:05

Also, use SMS to configure the ip address for the ether port.  Even if
you are on the same subnet as the box, set the gateway address the same as
the host address.  There is a firmware patch which corrects this, but I
didn't have it installed and I needed it.   For what its worth,
I have firmware revision: TCP00265

I also had to tweak my kernel on the host server. eg i386 laptop.
o  Enable Packet Socket and Socket Filtering so you can tftpboot in your
host kernel.


8. dd if=root.bin of=/dev/fd0 bs=1024 conv=sync; sync

I got my root.bin from debian potato dist site and powerpc chrp version.

11.  In openfirmware on the rs6000, I issued boot net and it started
booting linux.  It used
the vga as a display. ie. no serial console needed.

12,  When prompted by kernel to insert floppy, I did so and started install
process. It complained
about my disk partioning, but it wasn't a problem.  I ignored the prompts
and ran sfdisk.
I created one large partiton of type 82, one 5 MB 0x41 partition and a
swap.  I then did
every step in the install.
13.  When I rebooted, it failed to boot.  Not a problem.  I rebuilt my
kernel so it used
a root fs via harddisk and booted that.

So, I have a debian install which shows a nice console setup with virtual
terminals and it can
use the cdrom to apt-get install packages.  I don't have X support at this
point and I don't have
boot from the hard disk either.

John F. Davis



Rolf Brudeseth/Austin/[EMAIL PROTECTED] on 08/14/2002 11:51:29 AM

To:debian-powerpc@lists.debian.org
cc:[EMAIL PROTECTED]
Subject:Debian network installation on IBM RS/6000 44P-170 (POWER3) -
   HOWTO



The HOWTO can be found at the following URL:
http://www.personalized-story-book.com/debian/Woody_ibm_chrp_net_inst_HOWTO.html


Rolf

--
Rolf Brudeseth
[EMAIL PROTECTED]
pSeries System Engineering & Integration, IBM Enterprise Systems Group
Austin, TX





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]







Re: Woody on IBM RS/6000 7025 F50

2002-08-21 Thread John F Davis

Hello

Use minicom.

You have a matrox video card in a rs6000?  Was it the one which shipped
with the box?  I didn't know
rs6k's shipped with Matrox cards.  I'm far from an expert though.

JD

George Karaolides <[EMAIL PROTECTED]>@linustech.com.cy> on
08/21/2002 03:22:25 PM

Sent by:George Karaolides <[EMAIL PROTECTED]>


To:German Poo Caaman~o <[EMAIL PROTECTED]>
cc:"debian-powerpc@lists.debian.org" 
Subject:Re: Woody on IBM RS/6000 7025 F50




On 21 Aug 2002, German Poo Caaman~o wrote:

> What are you using: console or vga monitor?  I think the output
> is going to other device (your kernel seem works).

I'm trying to use a monitor and keyboard, the video card is a Matrox G200
and it works just fine with the existing old Yellow Dog installation.

> You can try booting with a console, append "console=ttyS0,9600"
> as argument when you boot from net, and connecting, with a null
> modem between serial ports, two machines.

OK, I've got a null modem cable right here.  Can I connect to the console
on the serial port from an Intel Linux machine (Debian woody)?  Is there
any software I must install?

Best regards,

|   George Karaolides  Planitis Communications Ltd.,  |
|   tel:   +357 22 45 65 00  Office 102, 11 Florinis Street,  |
|   web:   www.planitis.net Nicosia CY 1065,  |
|   email: [EMAIL PROTECTED]   Republic  of Cyprus.  |


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]







Re: Woody on IBM RS/6000 7025 F50

2002-08-21 Thread John F Davis

Hello

That's a good test.  I'll use that in the future.

Once you have setup the serial port (see other posters answers), you are
connected.  You are not
using a modem, so you don't need to do atdt type stuff.

JD

George Karaolides <[EMAIL PROTECTED]>@linustech.com.cy> on
08/21/2002 04:16:57 PM

Sent by:George Karaolides <[EMAIL PROTECTED]>


To:Thomas Gall/Rochester/[EMAIL PROTECTED]
cc:"debian-powerpc@lists.debian.org" 
Subject:Re: Woody on IBM RS/6000 7025 F50




On Wed, 21 Aug 2002, Tom Gall wrote:

> George Karaolides wrote:
>
> > 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...
>

I've configured minicom to use the serial port, and have configured
minicom to use the port with 9600 8N1, but (stupid user level
question...) how do I actually connect?  Should minicom connect
automatically on startup, or do I have to issue a command or something?

Just for the record, I've verified that my null-modem cable works between
two Linux machines:

cat < /dev/ttyS0 # on machine 1
echo hello > /dev/ttyS0  # on machine 2
hello# on machine 1

Best regards,

|   George Karaolides  Planitis Communications Ltd.,  |
|   tel:   +357 22 45 65 00  Office 102, 11 Florinis Street,  |
|   web:   www.planitis.net Nicosia CY 1065,  |
|   email: [EMAIL PROTECTED]   Republic  of Cyprus.  |


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]







Re: PowerPC kernel repository (was: Woody on IBM RS/6000 7025 F50)

2002-08-23 Thread John F Davis

Hello

It sounds good to me.  I would like to contribute the rs6k effort on
debian.

We need to get boot floppies which work as soon as possible.  Also, we need
to get working install cdroms.

JD

Rolf Brudeseth/Austin/[EMAIL PROTECTED] on 08/23/2002 10:23:51 AM

To:"Chris Tillman" <[EMAIL PROTECTED]>,
   "debian-powerpc@lists.debian.org" 
cc:
Subject:PowerPC kernel repository (was: Woody on IBM RS/6000 7025 F50)




> On Thu, Aug 22, 2002 at 10:06:56PM +0300, George Karaolides wrote:
> >
> > Further to my previous post about the serial port slowing down during
> > booting, here are the interrupts.  It took an hour and a half to get to
a
> > shell...
> >
> > It doesn't look like there's anything amiss.  Anyone have any other
ideas?
>
> Is it possible your terminal is set to a different rate than the kernel
> is communicating on? On Macs, the OF rate is 38400, but when I would
> pass 9600 to the kernel in the boot argument without changing the rate
> on the terminal, I would get something like that.
>
> --
> *--v- Installing Debian GNU/Linux 3.0 v--*
> |   |
> |debian-imac:    |
> |Chris Tillman[EMAIL PROTECTED]  |
> |  To Have, Give All to All (ACIM)   |
> **

Following the various install attempts on IBM hardware documented in this
mailing list, for a given architecture, it is clear that we have been using
kernels of different origin. It appears to me that we would benefit from
having a kernel repository with pre-compiled kernels. I know how to compile
a kernel; however, I prefer to use pre-compiled kernels that have been
built by people that fully understand the requirements for which source
tree to choose, patches to apply, compiler versions to use, etc. This way
we are all working with a common set of kernels.

Does this sound like a reasonable request?

If so, could someone create the following URL:
http://ftp.debian.org/debian/dists/sarge/main/disks-powerpc/current/
with the following sub-directories:
prep
chrp
power3
ppc64

Then add the following to each sub-directory:
vmlinux-2.4.xx
zImage-2.4.xx
config file


Rolf

--
Rolf Brudeseth
[EMAIL PROTECTED]
pSeries System Engineering & Integration, IBM Enterprise Systems Group
Austin, TX




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]







Re: PowerPC kernel repository (was: Woody on IBM RS/6000 7025 F50)

2002-08-23 Thread John F Davis

Hello

I could not get a boot floppy to work whatsoever.  It would be nice to have
one as a rescue disk.  It would also be nice if the boot floppy images on
the debian website
worked as well.  Note, they might work on different rs6k's from mine.  I
only tested on a 150 and neither the ones on my old potato cdrom or from
the debian website worked.
That's why I went through so much trouble to build my own kernel.

I was not aware the newer boxes were sans floppies.  Do they have zip disks
now or are do they only support CD-ROMs as removable media?

JD



From:  Rolf Brudeseth on 08/23/2002 01:32 PM

To:    John F Davis/Raleigh/[EMAIL PROTECTED], "debian-powerpc@lists.debian.org"
   
cc:
From:  Rolf Brudeseth/Austin/[EMAIL PROTECTED]
Subject:Re: PowerPC kernel repository (was: Woody on IBM RS/6000 7025
   F50)  (Document link: John F Davis)

> Hello
>
> It sounds good to me.  I would like to contribute the rs6k effort on
debian.
>
> 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.

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.

Rolf

--
Rolf Brudeseth
[EMAIL PROTECTED]
pSeries System Engineering & Integration, IBM Enterprise Systems Group
Austin, TX








Debian on RS6K

2002-12-04 Thread John F Davis




Debian Stable via Net
RS6K Model 43P 150
---

Hello

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.

Also, does debian support booting from hard disk now?


I have not played with this box and debian/linux for a long time now.
However, I have time
to play with it again.


JD



fdisk for RS/6000

2003-02-14 Thread John F Davis




Hello

I am using unstable and I can longer view my partition table.
fdisk and pdisk both dont work.  What is the problem?

JD



booting from hard disk of rs6000 43p 150

2003-02-19 Thread John F Davis




Hello

I'm trying to get my rs6k to boot from the hard disk again

Here is my setup:

Debian Unstable with custom built tools and kernel from MVista rsync.

I have a tftpboot kernel which works with boot net.
I want to use this kernel to boot from the disk.  I have copied
it to my root directory of my rs6k. ie. /zImage.chrp-rs6k

I have four scsi devices in this box. 1 cdrom and three disks.  I believe
/dev/sda corresponds to scsi id 4   Cat /proc/scsi/scsi shows them as id
3,4,5,6 (cdrom,disk1, disk2, disk3).
I hope the ids are likewise and not something weird like in sparc where id3
is "0" at boot time or something
like that.

I have three partitions, sda1 is / and linux native, sda2 is type 41 marked
bootable, sda3 is swap

At the boot prompt (accessed via F8), I have tried the following things and
none of them work:

Try 1:
setenv boot-file /zImage.chrp-rs6k
setenv boot-device /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]
boot hd

Try 2:
setenv boot-file /zImage.chrp-rs6k
setenv boot-device /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
PROTECTED]:1,/zImage.chrp-rs6k
boot hd

Try 3:
setenv boot-file /zImage.chrp-rs6k
setenv boot-device hd:4
boot hd

Other things of note:
I can get the cdrom to spin up (but it will not boot a debian ppc cd) if I
say "boot cdrom", or if I change the 4 to a 3 in
the above setenv lines.  I think this proves the scsi line and id is
correct.

Also, where is a document which describes the commands of the boot
interpeter?  The command help does nothing.

JD



Re: some basic problems with ppc assembler

2003-06-25 Thread John F Davis




Hello

There is powerpc compiler writers guide book.

Would that be appropiate?  I don't have a copy but I have seen it floating
around.

JD


|-+>
| |   [EMAIL PROTECTED]|
| |   (Brad Boyer) |
| ||
| |   06/25/2003 04:56 |
| |   PM   |
| ||
|-+>
  
>--|
  | 
 |
  |   To:   paubert <[EMAIL PROTECTED]> 
   |
  |   cc:   Benjamin Herrenschmidt <[EMAIL PROTECTED]>, Oliver Ripka 
<[EMAIL PROTECTED]>,  |
  |debian-powerpc@lists.debian.org  
 |
  |   Subject:  Re: some basic problems with ppc assembler  
 |
  | 
 |
  
>--|




On Wed, Jun 25, 2003 at 05:02:40PM +, paubert wrote:
> It is specified in the ABI for functions with variable number of
argumentsi:
> the crxor indicates that no parameters have been passed in the floating
point
> registers so an integer only task will not save fpr1-fpr8 to walk the
> argument list in va_arg. OTOH if you call a variadic functions with
> floating point parameters, the call will be preceded by creqv 6,6,6.

Do you actually have a document for the official ABI? I found a link
to a document in some old messages, but it was a dead link. A generic
search of the web didn't turn up anything, although I might have
been searching for the wrong words...

I've been trying to piece it together based on gcc, but that's
kind of a clumsy way to figure it out.

 Brad Boyer
 [EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]