Kernel packages in Debian ()

Mike Martin | 1 Jan 2005 01:54

Re: 43p-140 install issues

(re-sending for the benefit of those on the lists .. sorry Sven)

Would there be any image I can use to install this machine currently?
Here's my situation, If I can get the machine to boot and install by
next week (back to work) my boss will let me keep working on it -
otherwise he'll declare it useless and it'll go back in the closet. If
I can get anything on it I'm ok - It doesn't need to be 2.6.

Attached is /var/log/syslog and /var/log/messages.

Mike Martin

On Fri, 31 Dec 2004 10:53:10 +0100, Sven Luther <sven.luther <at> wanadoo.fr> wrote:
> On Wed, Dec 29, 2004 at 01:51:51PM -0500, Mike Martin wrote:
> > I have a 43p-140, It will netboot, start the installer and let be run
> > through the motions. It doesn't seem to be able to recognize the cdrom
> > or be able to set up the network. This puts a stop on the installation
> > pretty quickly. I can't seem to figure it out on my own. Can anyone
> > help?
> >
> > Attached is a console capture from my latest boot using the Dec. 28th
> > image from:
> > http://people.debian.org/~luther/debian-installer/daily-powerpc-built/daily/powerpc/netboot/
> >
> > Other images are similar.
> 
> Could you try to get the /var/log/syslog and /var/log/messages out of that box
> ?
> 
> > When the installer gets to configuring the network with DHCP, it

(Continue reading)

headers

Ulrich Teichert | 1 Jan 2005 14:15

Re: 43p-140 install issues

Hi,

>Would there be any image I can use to install this machine currently?

Sure, check http://www.solinno.co.uk/7043-140/, that's Leigh Browns site.
There's a detailed step-by-step guide which will take you through the whole
process. You can even choose what distro you want to install, but you may
have to update your firmware first (I had to do it as well, but it was
OK). BTW: great job Leigh!

>Here's my situation, If I can get the machine to boot and install by
>next week (back to work) my boss will let me keep working on it -
>otherwise he'll declare it useless and it'll go back in the closet. If
>I can get anything on it I'm ok - It doesn't need to be 2.6.
[del]

There are 2.4.x kernels on that site which are working very well, I
installed Debian Woody on top of it 

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert <at> gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

--

-- 
To UNSUBSCRIBE, email to debian-powerpc-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

(Continue reading)

headers

Sven Luther | 1 Jan 2005 16:00

Re: 43p-140 install issues

On Sat, Jan 01, 2005 at 02:15:33PM +0100, Ulrich Teichert wrote:
> Hi,
> 
> >Would there be any image I can use to install this machine currently?
> 
> Sure, check http://www.solinno.co.uk/7043-140/, that's Leigh Browns site.
> There's a detailed step-by-step guide which will take you through the whole
> process. You can even choose what distro you want to install, but you may
> have to update your firmware first (I had to do it as well, but it was
> OK). BTW: great job Leigh!

I would prefer that we fix the debian kernels for them to work correctly
though. More on this on monday.

> >Here's my situation, If I can get the machine to boot and install by
> >next week (back to work) my boss will let me keep working on it -
> >otherwise he'll declare it useless and it'll go back in the closet. If
> >I can get anything on it I'm ok - It doesn't need to be 2.6.
> [del]
> 
> There are 2.4.x kernels on that site which are working very well, I
> installed Debian Woody on top of it 

Yeah, well.

Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
kernel on my powerstack, but this is a different machine, so the issues may be
a bit different. 

Friendly,

(Continue reading)

headers

Ulrich Teichert | 1 Jan 2005 17:30

Re: 43p-140 install issues

Hi,

[del]
>I would prefer that we fix the debian kernels for them to work correctly
>though. More on this on monday.

I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
I think some of Leigh patches for this must be applied, but I haven't
gone any further.

[del]
>Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
>kernel on my powerstack, but this is a different machine, so the issues may be
>a bit different. 

I've only tried the Woody PREP kernel, which failed in a way which I can't
remember, but I'll give it a try.

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert <at> gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

--

-- 
To UNSUBSCRIBE, email to debian-powerpc-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

(Continue reading)

headers

Sven Luther | 1 Jan 2005 17:57

Re: 43p-140 install issues

On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> Hi,
> 
> [del]
> >I would prefer that we fix the debian kernels for them to work correctly
> >though. More on this on monday.
> 
> I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
> I think some of Leigh patches for this must be applied, but I haven't
> gone any further.

I had some report on a power3 box, that only the SMP sym53c8xx driver worked.
When configuring in UP mode, 

> [del]
> >Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
> >kernel on my powerstack, but this is a different machine, so the issues may be
> >a bit different. 
> 
> I've only tried the Woody PREP kernel, which failed in a way which I can't
> remember, but I'll give it a try.

Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
Let' try to get this fixed before the sarge release, which is not so far off
now.

Friendly,

Sven Luther

(Continue reading)

headers

Ulrich Teichert | 2 Jan 2005 16:38

Re: 43p-140 install issues

Hi,

[del]
>Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
>Let' try to get this fixed before the sarge release, which is not so far off
>now.

OK, 9 hours later I had a current sarge buisnesscard CD image, with
interesting results. I booted the standard kernel from the cdrom
with `boot cdrom:`, it came up and failed to load the initrd, so it died
on the spot as nothing could be mounted. It was detecting that I was using
a serial console.
Of course, I forgot to capture that session, so I did it again with logging
on in kermit. Then I could not boot anything from the CD, but I can still
boot fine from disk, so it's not a hardware problem. The LED displays F05
after reading something from the CDROM in this case and the machine hangs.
Strange.

I will try to boot via tftp, the firmware seems to be unable to boot
a specific file from CDROM,

CU,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert <at> gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

--

-- 
To UNSUBSCRIBE, email to debian-powerpc-REQUEST <at> lists.debian.org

(Continue reading)

headers

Sven Luther | 2 Jan 2005 17:41

Re: 43p-140 install issues

On Sun, Jan 02, 2005 at 04:38:00PM +0100, Ulrich Teichert wrote:
> Hi,
> 
> [del]
> >Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
> >Let' try to get this fixed before the sarge release, which is not so far off
> >now.
> 
> OK, 9 hours later I had a current sarge buisnesscard CD image, with
> interesting results. I booted the standard kernel from the cdrom
> with `boot cdrom:`, it came up and failed to load the initrd, so it died
> on the spot as nothing could be mounted. It was detecting that I was using
> a serial console.

You need to boot install/powerpc/vmlinuz-prep.initrd, not the vmlinux one.

> Of course, I forgot to capture that session, so I did it again with logging
> on in kermit. Then I could not boot anything from the CD, but I can still
> boot fine from disk, so it's not a hardware problem. The LED displays F05
> after reading something from the CDROM in this case and the machine hangs.
> Strange.
> 
> I will try to boot via tftp, the firmware seems to be unable to boot
> a specific file from CDROM,

Ah, strange. That said, tftp is the prefered boot method for prep hardware.

Friendly,

Sven Luther

(Continue reading)

headers

Mike Martin | 2 Jan 2005 02:15

Re: 43p-140 install issues

I can boot with this image:
http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd

And things seems to go very well. Network configures, hard drives
partition, it dies at "Install the base system"  with "The debootstrap
program exited with an error (return value 255)." It instructs me to
check /var/log/messages which now contains: "execv: No such file or
directory"

The previous step, partitioning, added:
  "No matching physical volumes found
  No volume groups found
  Reading all physical volumes.  This may take a while..."

Anyone?

MikeMartin

On Sat, 1 Jan 2005 17:57:58 +0100, Sven Luther <sven.luther <at> wanadoo.fr> wrote:
> On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> > Hi,
> >
> > [del]
> > >I would prefer that we fix the debian kernels for them to work correctly
> > >though. More on this on monday.
> >
> > I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
> > I think some of Leigh patches for this must be applied, but I haven't
> > gone any further.
>

(Continue reading)

headers

Sven Luther | 2 Jan 2005 10:43

Re: 43p-140 install issues

On Sat, Jan 01, 2005 at 08:15:13PM -0500, Mike Martin wrote:
> I can boot with this image:
> http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd

Cool.

> And things seems to go very well. Network configures, hard drives
> partition, it dies at "Install the base system"  with "The debootstrap
> program exited with an error (return value 255)." It instructs me to
> check /var/log/messages which now contains: "execv: No such file or
> directory"

Strange, can you check at what percentage of "install base system" this error
happned ? can you attach the full /var/log/messages and /var/log/syslog ?

Mmm, CCing debian-boot as this seems more relevant there. <at> 

> The previous step, partitioning, added:
>   "No matching physical volumes found
>   No volume groups found
>   Reading all physical volumes.  This may take a while..."
> 
> Anyone?
> 
> MikeMartin
> 
> On Sat, 1 Jan 2005 17:57:58 +0100, Sven Luther <sven.luther <at> wanadoo.fr> wrote:
> > On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> > > Hi,
> > >

(Continue reading)

headers

Mike Martin | 3 Jan 2005 05:15

Re: 43p-140 install issues

Now I'm very confused .... on my next reboot ... the network wouldn't
work. After much trial and error, I got the current unstable d-i image
to work. It did it all right up to the reboot (where is warns you that
it doesn't have a boot loader installed).

Now what!

I have an installed system, but I can't figure out how to boot it! I
have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
write a boot sector or tell OpenFirmware to boot from this file? I
tried to netboot and set root=/dev/sdb1 - but without the scsi modules
loaded it fails to read the drives and panics.

I think I neet to create a type 41 PReP boot partition and get the
kernel onto it. I've found this thread:
http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html

and this:
http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml

I tried booting up with the installer, going to a shell after the scsi
was active and the installed system was mounted. I used sfdisk from
/target/sbin to create a 10 Meg type 41 partition on the first HD
(/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
partition. But it still won't boot.

I'm very close. If I can get the system to boot (really it needs to
boot itself - not netboot) I'd call this a success.

Thanks!

(Continue reading)

headers

Philippe Guyot | 3 Jan 2005 10:56

Re: 43p-140 install issues

On Monday 03 January 2005 05:15, Mike Martin wrote:
> Now I'm very confused .... on my next reboot ... the network wouldn't
> work. After much trial and error, I got the current unstable d-i image
> to work. It did it all right up to the reboot (where is warns you that
> it doesn't have a boot loader installed).
>
> Now what!
>
> I have an installed system, but I can't figure out how to boot it! I
> have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> write a boot sector or tell OpenFirmware to boot from this file? I
> tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> loaded it fails to read the drives and panics.
>
> I think I neet to create a type 41 PReP boot partition and get the
> kernel onto it. I've found this thread:
> http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
>
> and this:
> http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml
>
> I tried booting up with the installer, going to a shell after the scsi
> was active and the installed system was mounted. I used sfdisk from
> /target/sbin to create a 10 Meg type 41 partition on the first HD
> (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> partition. But it still won't boot.

I succeeded last year to install a woody on a 143P-140 whith the help of Leigh 
Brown (thanks to him again). And two 150 whit sarge also.

(Continue reading)

headers

Sven Luther | 3 Jan 2005 11:48

Re: 43p-140 install issues

On Mon, Jan 03, 2005 at 10:56:30AM +0100, Philippe Guyot wrote:
> On Monday 03 January 2005 05:15, Mike Martin wrote:
> > Now I'm very confused .... on my next reboot ... the network wouldn't
> > work. After much trial and error, I got the current unstable d-i image
> > to work. It did it all right up to the reboot (where is warns you that
> > it doesn't have a boot loader installed).
> >
> > Now what!
> >
> > I have an installed system, but I can't figure out how to boot it! I
> > have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> > write a boot sector or tell OpenFirmware to boot from this file? I
> > tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> > loaded it fails to read the drives and panics.
> >
> > I think I neet to create a type 41 PReP boot partition and get the
> > kernel onto it. I've found this thread:
> > http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
> >
> > and this:
> > http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml
> >
> > I tried booting up with the installer, going to a shell after the scsi
> > was active and the installed system was mounted. I used sfdisk from
> > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > partition. But it still won't boot.
> 
> 
> I succeeded last year to install a woody on a 143P-140 whith the help of Leigh

(Continue reading)

headers

Philippe Guyot | 3 Jan 2005 11:56

Re: 43p-140 install issues

On Monday 03 January 2005 11:48, Sven Luther wrote:
> On Mon, Jan 03, 2005 at 10:56:30AM +0100, Philippe Guyot wrote:
> > On Monday 03 January 2005 05:15, Mike Martin wrote:
> > > Now I'm very confused .... on my next reboot ... the network wouldn't
> > > work. After much trial and error, I got the current unstable d-i image
> > > to work. It did it all right up to the reboot (where is warns you that
> > > it doesn't have a boot loader installed).
> > >
> > > Now what!
> > >
> > > I have an installed system, but I can't figure out how to boot it! I
> > > have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> > > write a boot sector or tell OpenFirmware to boot from this file? I
> > > tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> > > loaded it fails to read the drives and panics.
> > >
> > > I think I neet to create a type 41 PReP boot partition and get the
> > > kernel onto it. I've found this thread:
> > > http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
> > >
> > > and this:
> > > http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.sh
> > >tml
> > >
> > > I tried booting up with the installer, going to a shell after the scsi
> > > was active and the installed system was mounted. I used sfdisk from
> > > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > > partition. But it still won't boot.
> >

(Continue reading)

headers

Sven Luther | 3 Jan 2005 12:17

Re: 43p-140 install issues

On Mon, Jan 03, 2005 at 11:56:07AM +0100, Philippe Guyot wrote:
> On Monday 03 January 2005 11:48, Sven Luther wrote:
> > On Mon, Jan 03, 2005 at 10:56:30AM +0100, Philippe Guyot wrote:
> > > On Monday 03 January 2005 05:15, Mike Martin wrote:
> > > > Now I'm very confused .... on my next reboot ... the network wouldn't
> > > > work. After much trial and error, I got the current unstable d-i image
> > > > to work. It did it all right up to the reboot (where is warns you that
> > > > it doesn't have a boot loader installed).
> > > >
> > > > Now what!
> > > >
> > > > I have an installed system, but I can't figure out how to boot it! I
> > > > have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> > > > write a boot sector or tell OpenFirmware to boot from this file? I
> > > > tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> > > > loaded it fails to read the drives and panics.
> > > >
> > > > I think I neet to create a type 41 PReP boot partition and get the
> > > > kernel onto it. I've found this thread:
> > > > http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
> > > >
> > > > and this:
> > > > http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.sh
> > > >tml
> > > >
> > > > I tried booting up with the installer, going to a shell after the scsi
> > > > was active and the installed system was mounted. I used sfdisk from
> > > > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > > > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > > > partition. But it still won't boot.

(Continue reading)

headers

Michael Schmitz | 3 Jan 2005 12:57

Re: 43p-140 install issues

> > > > is, so Leigh did a piece of code named "preptools" in order to patch the
> > > > image with the location of root.
> > >
> > > Hey, cool, where is this tool ? We need to package it for debian if it is
> > > not already, and use it in d-i, and maybe even mkvmlinuz directly.
> > >
> >
> > Just over there....
> >
> > http://www.solinno.co.uk/7043-140/downloads.php
> > But ask Leigh for details.
>
> Ok, thanks. ...

Do we need that added to powerpc-utils perhaps?

	Michael

headers

Sven Luther | 3 Jan 2005 13:47

Re: 43p-140 install issues

On Mon, Jan 03, 2005 at 12:57:35PM +0100, Michael Schmitz wrote:
> > > > > is, so Leigh did a piece of code named "preptools" in order to patch the
> > > > > image with the location of root.
> > > >
> > > > Hey, cool, where is this tool ? We need to package it for debian if it is
> > > > not already, and use it in d-i, and maybe even mkvmlinuz directly.
> > > >
> > >
> > > Just over there....
> > >
> > > http://www.solinno.co.uk/7043-140/downloads.php
> > > But ask Leigh for details.
> >
> > Ok, thanks. ...
> 
> Do we need that added to powerpc-utils perhaps?

Whatever is powerpc-utils ? Mmm, maybe, but then maybe mkvmlinuz would benefit
from being added there too, not sure. In any way i believe it has more its
place inside mkvmlinuz, than inside the more userland powerpc-utils.

Friendly,

Sven Luther

headers

Michael Schmitz | 3 Jan 2005 16:24

Re: 43p-140 install issues

> > > > http://www.solinno.co.uk/7043-140/downloads.php
> > > > But ask Leigh for details.
> > >
> > > Ok, thanks. ...
> >
> > Do we need that added to powerpc-utils perhaps?
>
> Whatever is powerpc-utils ? Mmm, maybe, but then maybe mkvmlinuz would benefit

WTF is mkvmlinuz?

> from being added there too, not sure. In any way i believe it has more its
> place inside mkvmlinuz, than inside the more userland powerpc-utils.

Whatever. Just thought people might want to use it to change kernel
options on the fly, without invoking mkvmlinuz.

	Michael

headers

Sven Luther | 3 Jan 2005 17:04

Re: 43p-140 install issues

On Mon, Jan 03, 2005 at 04:24:40PM +0100, Michael Schmitz wrote:
> > > > > http://www.solinno.co.uk/7043-140/downloads.php
> > > > > But ask Leigh for details.
> > > >
> > > > Ok, thanks. ...
> > >
> > > Do we need that added to powerpc-utils perhaps?
> >
> > Whatever is powerpc-utils ? Mmm, maybe, but then maybe mkvmlinuz would benefit
> 
> WTF is mkvmlinuz?

mkvmlinuz is a nice little kernel-derived tool by Jens and me, which allows
one to create a zImage.chrp, or zImage.coff or whatever, from the
arch/ppc/boot/* stuff and the plain vmlinux kernel. It avoids having to chip
the same kernel X times as we did on 2.4 kernels, and can be used as a
kernel-package postinst hook to automate this process.

> > from being added there too, not sure. In any way i believe it has more its
> > place inside mkvmlinuz, than inside the more userland powerpc-utils.
> 
> Whatever. Just thought people might want to use it to change kernel
> options on the fly, without invoking mkvmlinuz.

Well, we would need at least a .udeb containing it. IF you can add it to
powerpc-tools, then nice. I think that maybe mkvmlinuz would be also a
candidate to be part of the powerpc-tools, not sure though.

Friendly,

(Continue reading)

headers

Michael Schmitz | 6 Jan 2005 13:19

Re: 43p-140 install issues

> > > from being added there too, not sure. In any way i believe it has more its
> > > place inside mkvmlinuz, than inside the more userland powerpc-utils.
> >
> > Whatever. Just thought people might want to use it to change kernel
> > options on the fly, without invoking mkvmlinuz.
>
> Well, we would need at least a .udeb containing it. IF you can add it to
> powerpc-tools, then nice. I think that maybe mkvmlinuz would be also a

Does it work independently of mkvmlinuz (that is, operate on the bootable
files generated by mkvmlinuz)? Does it make sense for non-PREP/CHRP
machines? Otherwise, I'd suggest adding it to mkvmlinuz.

> candidate to be part of the powerpc-tools, not sure though.

Does the mkvmlinuz trick help with bootable CDs on Macs (OldWorld), BTW?

	Michael

headers

Sven Luther | 6 Jan 2005 15:02

Re: 43p-140 install issues

On Thu, Jan 06, 2005 at 01:19:32PM +0100, Michael Schmitz wrote:
> > > > from being added there too, not sure. In any way i believe it has more its
> > > > place inside mkvmlinuz, than inside the more userland powerpc-utils.
> > >
> > > Whatever. Just thought people might want to use it to change kernel
> > > options on the fly, without invoking mkvmlinuz.
> >
> > Well, we would need at least a .udeb containing it. IF you can add it to
> > powerpc-tools, then nice. I think that maybe mkvmlinuz would be also a
> 
> Does it work independently of mkvmlinuz (that is, operate on the bootable

Sure.

> files generated by mkvmlinuz)? Does it make sense for non-PREP/CHRP
> machines? Otherwise, I'd suggest adding it to mkvmlinuz.

Not, it is usefull only for prep machines, but the kernel needs patching
anyway, so i will just drop that for now.

> > candidate to be part of the powerpc-tools, not sure though.
> 
> Does the mkvmlinuz trick help with bootable CDs on Macs (OldWorld), BTW?

No, it is just a small tool which do the last part linking phase of the kernel
build so you can generate chrp, prep, coff, whatever zImage and zImage.initrd.
So you can ship only yhe vmlinux, and not chip the vmlinux, the zImage.chrp,
the zImage.prep, the zImage.coff, the zImage.ppcbug and so on.

Friendly,

(Continue reading)

headers

Sven Luther | 3 Jan 2005 08:05

Re: 43p-140 install issues

On Sun, Jan 02, 2005 at 11:15:35PM -0500, Mike Martin wrote:
> Now I'm very confused .... on my next reboot ... the network wouldn't
> work. After much trial and error, I got the current unstable d-i image
> to work. It did it all right up to the reboot (where is warns you that
> it doesn't have a boot loader installed).

There may be some problems with 2.6 kernels and pci irqs on prep. I will
investigate this shortly.

There is indeed no prep boot-loader installer available. I hear there is a
partman-prep prepared, but not yet part of d-i. more to this below.

> Now what!
> 
> I have an installed system, but I can't figure out how to boot it! I
> have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> write a boot sector or tell OpenFirmware to boot from this file? I
> tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> loaded it fails to read the drives and panics.

You need to install mkvmlinuz, i think it is already, but not use
/boot/vmlinux-2.6.8-powerpc, but /boot/vmlinuz-2.6.8-powerpc, which is the
result of mkvmlinuz adding the initrd containing the modules onto the kernel,
and then adding the prep simple bootloader. Check if you have the
vmlinuz-2.6.8-powerpc, which should have been generated at install time, and
copy it to your netboot tftp server, and try again. It should even recognize
the root= partition automatically.

> I think I neet to create a type 41 PReP boot partition and get the
> kernel onto it. I've found this thread:

(Continue reading)

headers

Mike Martin | 3 Jan 2005 14:39

Re: 43p-140 install issues

On Mon, 3 Jan 2005 08:05:35 +0100, Sven Luther <sven.luther <at> wanadoo.fr> wrote:

[snip]
> There may be some problems with 2.6 kernels and pci irqs on prep. I will
> investigate this shortly.

There is definitely something strange happening. The image I used to
do the (nearly) complete install will no longer configure the network.
Very inconsistent. I will try it (same image) again later today and
see if it "just works" next time - like it did last time.

[snip]
> 
> Yep. Until partman-prep is ready, you should simply try to add the prep flag
> to the a small partition. I think the normal scheme is to create /dev/sdb1 as
> a small (8MB ?) prep partition, /dev/sdb2 as swap, and /dev/sdb3 as /. If
> partman is not able to do it, jump to console 2, and launch parted directly,
> and do a set 1 prep on.

Can't jump to console 2 - I can only comunicate through the serial
console. However I'll give this a shot through the "execute shell"
menu item. "set 1 prep on"? Haven't seen that documented anywhere,
what does it do?

> 
> Then i suppose that copying the kernel is just a matter of :
> 
>   dd if=/boot/vmlinuz-2.6.8-powerpc of=/dev/sdb1
> 
> but you have to have a small prep partition as /dev/sdb1, or the above will

(Continue reading)

headers

Ulrich Teichert | 3 Jan 2005 16:51

Re: 43p-140 install issues

Hi,

>[snip]
>> There may be some problems with 2.6 kernels and pci irqs on prep. I will
>> investigate this shortly.
>
>There is definitely something strange happening. The image I used to
>do the (nearly) complete install will no longer configure the network.
>Very inconsistent. I will try it (same image) again later today and
>see if it "just works" next time - like it did last time.

Yes, I've seen inconsistencies as well, like booting the default kernel
from a sarge CD worked *once* and rebooting not. I found out why:
during the first cold boot, the firmware asks if it should make my
serial console the active console (which I acknowledged), but with a
warm boot, this question is not asked again.

This seems to result in a different setting and the kernel is not able
to figure out that it is running on a serial console. According to Leigh
Browns, it is not possible to give the kernel parameters on boot-up, unless
you are using his patches, so this may be another issue.

But this is how far the default kernel (which is all I can load from CD)
boots:

0 > setenv load-base 1000000  ok
0 > setenv real-base c00000  ok
0 > boot cdrom: 

loaded at:     01000400 01492FF4

(Continue reading)

headers

Leigh Brown | 3 Jan 2005 17:50

Re: 43p-140 install issues

Ulrich Teichert said:
>>[snip]
>>> There may be some problems with 2.6 kernels and pci irqs on prep. I
>>> will
>>> investigate this shortly.
>>
>>There is definitely something strange happening. The image I used to
>>do the (nearly) complete install will no longer configure the network.
>>Very inconsistent. I will try it (same image) again later today and
>>see if it "just works" next time - like it did last time.
>
> Yes, I've seen inconsistencies as well, like booting the default kernel
> from a sarge CD worked *once* and rebooting not. I found out why:
> during the first cold boot, the firmware asks if it should make my
> serial console the active console (which I acknowledged), but with a
> warm boot, this question is not asked again.

That's because the firmware will only ask that question if detects that
a mouse or keyboard is present/not present where it previously was/n't.

> This seems to result in a different setting and the kernel is not able
> to figure out that it is running on a serial console. According to Leigh
> Browns, it is not possible to give the kernel parameters on boot-up,
> unless you are using his patches, so this may be another issue.

I have a patch you can use to specify parameters on the *command line*
(e.g. boot floppy: root=/dev/sda3 ...).  However, you can always type
parameters on the serial console as it boots (see below).

> But this is how far the default kernel (which is all I can load from CD)

(Continue reading)

headers

Ulrich Teichert | 3 Jan 2005 20:32

Re: 43p-140 install issues

Hi,

[del]
>> Linux/PPC load: console=ttyS0,9600 console=tty0
>
>*** This is the point you get 5 seconds to start editing the parameters.
>I guess if you specify root=/dev/ram0 or something then it will boot
>from the ramdisk, rather than trying to boot from /dev/sda3.

Right, now I can even boot over network:

0 > setenv load-base 1000000  ok
0 > setenv real-base c00000  ok
0 > boot net: 
LOAD: Waiting 60 seconds for Spanning Tree
BOOTP R = 1 BOOTP S = 1  
FILE: /tftpboot/wehrle/vmlinuz-prep.initrd
Load Addr=0x1000000 Max Size=0xf000000 
Packet Count = 100 [snipped the packet count lines]

loaded at:     01000400 01554FF4
relocated to:  00800000 00D54BF4
zimage at:     0080A94C 0093DC0A
initrd at:     0093E000 00D4AB7A
avail ram:     00400000 00800000

Linux/PPC load: console=ttyS0,9600 console=tty0 root=/dev/ram
Uncompressing Linux...done.
Now booting the kernel
Total memory = 256MB; using 512kB for hash table (at c0300000)

(Continue reading)

headers

Leigh Brown | 3 Jan 2005 20:42

Re: 43p-140 install issues

Ulrich Teichert said:
[...]
> Linux/PPC load: console=ttyS0,9600 console=tty0 root=/dev/ram

Delete the "console=tty0", so you end up with:

 Linux/PPC load: console=ttyS0,9600 root=/dev/ram

and try again!

[...]
>>It should never ask the console question again unless you change the
>>config (plug in a mouse for example), unless your nvram battery is a
>>bit flat of course!
>
> This seems to be the case. But it really simplifies things, as I've never
> been able to warm-boot anything  Only a cold boot helps. Maybe Daniel
> should remove the battery to reset things completely?
>
> Anyway, without your site, Leigh, I would still have a big doorstop only,
> thanks again,

No problem.  The amazing thing is, once you actually get them running,
RS/6000's run Linux really reliably.  It's getting them booting that's
the problem :-/

--

-- 
To UNSUBSCRIBE, email to debian-powerpc-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

(Continue reading)

headers

Ulrich Teichert | 3 Jan 2005 23:11

Re: 43p-140 install issues

Hi,

>Delete the "console=tty0", so you end up with:
>
> Linux/PPC load: console=ttyS0,9600 root=/dev/ram
>
>and try again!
[del]

Right, then the installer knows what to do. I think this should go into
the Debian installation docs, there are a lot of boxes with graphic cards
out which are not supported by Linux.

But the low level SCSI-driver is missing in this image, or any low level
SCSI drivers for that matter. There are only the high level modules there,
like sd_mod.ko and sr_mod.ko:

Nov 30 00:06:32 hw-detect: Using discover version 1.
Nov 30 00:06:35 hw-detect: Detecting hardware...
Nov 30 00:06:36 hw-detect: Missing module 'sym53c8xx'.
Nov 30 00:06:36 hw-detect: Missing module 'usb-storage'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-mod'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-probe-mod'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-detect'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-generic'.
Nov 30 00:06:37 hw-detect: Missing module 'ide-floppy'.
--More-- (57% of 44385 bytes)                             Nov 30 00:06:37 hw-detect: Missing module 'ide-disk'.
Nov 30 00:06:37 hw-detect: Missing module 'isofs'.
Nov 30 00:06:37 hw-detect: Loading modules...
Nov 30 00:06:37 hw-detect: Detected module 'pcnet32' for 'Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]'

(Continue reading)

headers

Sven Luther | 4 Jan 2005 23:28

Re: 43p-140 install issues

On Mon, Jan 03, 2005 at 11:11:06PM +0100, Ulrich Teichert wrote:
> Hi,
> 
> >Delete the "console=tty0", so you end up with:
> >
> > Linux/PPC load: console=ttyS0,9600 root=/dev/ram
> >
> >and try again!
> [del]
> 
> Right, then the installer knows what to do. I think this should go into
> the Debian installation docs, there are a lot of boxes with graphic cards
> out which are not supported by Linux.

Err, it should default to vga tedxt mode if the graphic card fbdev is not
builtin, at least it does it here.

> But the low level SCSI-driver is missing in this image, or any low level
> SCSI drivers for that matter. There are only the high level modules there,
> like sd_mod.ko and sr_mod.ko:

Sure, these should be loaded through the network. Try the
powerpc/cdrom/vmlinuz-prep.initrd for images with scsi modules included.

> Nov 30 00:06:32 hw-detect: Using discover version 1.
> Nov 30 00:06:35 hw-detect: Detecting hardware...
> Nov 30 00:06:36 hw-detect: Missing module 'sym53c8xx'.
> Nov 30 00:06:36 hw-detect: Missing module 'usb-storage'.
> Nov 30 00:06:36 hw-detect: Missing module 'ide-mod'.
> Nov 30 00:06:36 hw-detect: Missing module 'ide-probe-mod'.

(Continue reading)

headers

Leigh Brown | 4 Jan 2005 23:39

Re: 43p-140 install issues

Sven Luther said:
> On Mon, Jan 03, 2005 at 11:11:06PM +0100, Ulrich Teichert wrote:
>> Hi,
>>
>> >Delete the "console=tty0", so you end up with:
>> >
>> > Linux/PPC load: console=ttyS0,9600 root=/dev/ram
>> >
>> >and try again!
>> [del]
>>
>> Right, then the installer knows what to do. I think this should go into
>> the Debian installation docs, there are a lot of boxes with graphic
>> cards
>> out which are not supported by Linux.
>
> Err, it should default to vga tedxt mode if the graphic card fbdev is not
> builtin, at least it does it here.

The PReP specs says that the cards should be initialised to a
minimum resolution of 640x480 iirc.  The boot loader has code to
manually reprogram the card *back* into VGA text mode, but only
for a very limited number of cards.  So, if your card is not
supported by fbdev, and isn't one of the very few supported
cards in the boot loader, it simply won't work under PReP.

[...]

Cheers,

(Continue reading)

headers

Sven Luther | 5 Jan 2005 10:03

Re: 43p-140 install issues

On Tue, Jan 04, 2005 at 10:39:15PM -0000, Leigh Brown wrote:
> Sven Luther said:
> > On Mon, Jan 03, 2005 at 11:11:06PM +0100, Ulrich Teichert wrote:
> >> Hi,
> >>
> >> >Delete the "console=tty0", so you end up with:
> >> >
> >> > Linux/PPC load: console=ttyS0,9600 root=/dev/ram
> >> >
> >> >and try again!
> >> [del]
> >>
> >> Right, then the installer knows what to do. I think this should go into
> >> the Debian installation docs, there are a lot of boxes with graphic
> >> cards
> >> out which are not supported by Linux.
> >
> > Err, it should default to vga tedxt mode if the graphic card fbdev is not
> > builtin, at least it does it here.
> 
> The PReP specs says that the cards should be initialised to a
> minimum resolution of 640x480 iirc.  The boot loader has code to
> manually reprogram the card *back* into VGA text mode, but only
> for a very limited number of cards.  So, if your card is not
> supported by fbdev, and isn't one of the very few supported
> cards in the boot loader, it simply won't work under PReP.

Ah, ok ... Well i have a cirrus logic card also, and it seems to work. I have
anot yet tried the matrox cards though. Do they need to be special cards with
forth rom, or will any do ?

(Continue reading)

headers

Philippe Guyot | 5 Jan 2005 10:49

Re: 43p-140 install issues

On Wednesday 05 January 2005 10:03, Sven Luther wrote:
> On Tue, Jan 04, 2005 at 10:39:15PM -0000, Leigh Brown wrote:
> > Sven Luther said:
> > > On Mon, Jan 03, 2005 at 11:11:06PM +0100, Ulrich Teichert wrote:
> > >> Hi,
> > >>
> > >> >Delete the "console=tty0", so you end up with:
> > >> >
> > >> > Linux/PPC load: console=ttyS0,9600 root=/dev/ram
> > >> >
> > >> >and try again!
> > >>
> > >> [del]
> > >>
> > >> Right, then the installer knows what to do. I think this should go
> > >> into the Debian installation docs, there are a lot of boxes with
> > >> graphic cards
> > >> out which are not supported by Linux.
> > >
> > > Err, it should default to vga tedxt mode if the graphic card fbdev is
> > > not builtin, at least it does it here.
> >
> > The PReP specs says that the cards should be initialised to a
> > minimum resolution of 640x480 iirc.  The boot loader has code to
> > manually reprogram the card *back* into VGA text mode, but only
> > for a very limited number of cards.  So, if your card is not
> > supported by fbdev, and isn't one of the very few supported
> > cards in the boot loader, it simply won't work under PReP.
>
> Ah, ok ... Well i have a cirrus logic card also, and it seems to work. I

(Continue reading)

headers

Sven Luther | 5 Jan 2005 12:47

Re: 43p-140 install issues

On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> > BTW, i have another question. I am trying to fix debian-installer to create
> > the prep partition, but i would like to have some info on the expected
> > constraints of said partition. Some tell it has to be entirely in the first
> > 8MB, others the first 5MB, and my powerstack has a 17MB boot partition
> > right now.
> 
> 
> All I can say, it's that my boot PReP partition is the 1st and about 4 MB in 
> size (cannot size it less than 1% of the disk.....)
> second partition is /
> third is swap.

BTW, for debian, it makes more sense to have the second partition as swap, and
the third as /, i think, since it was decided some time back to default to
root=/dev/sda3, and not sda2.

> That works for me.

Until the kernel grows beyond 4MB.

Friendly,

Sven Luther

headers

Hollis Blanchard | 5 Jan 2005 16:45

Re: 43p-140 install issues

On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:

> On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
>>> BTW, i have another question. I am trying to fix debian-installer to 
>>> create
>>> the prep partition, but i would like to have some info on the 
>>> expected
>>> constraints of said partition. Some tell it has to be entirely in 
>>> the first
>>> 8MB, others the first 5MB, and my powerstack has a 17MB boot 
>>> partition
>>> right now.
>>
>> All I can say, it's that my boot PReP partition is the 1st and about 
>> 4 MB in
>> size (cannot size it less than 1% of the disk.....)
>> second partition is /
>> third is swap.
>
> BTW, for debian, it makes more sense to have the second partition as 
> swap, and
> the third as /, i think, since it was decided some time back to 
> default to
> root=/dev/sda3, and not sda2.
>
>> That works for me.
>
> Until the kernel grows beyond 4MB.

The size of that partition depends on firmware limitations. I have

(Continue reading)

headers

Sven Luther | 5 Jan 2005 17:08

Re: 43p-140 install issues

On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
> On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:
> 
> >On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> >>>BTW, i have another question. I am trying to fix debian-installer to 
> >>>create
> >>>the prep partition, but i would like to have some info on the 
> >>>expected
> >>>constraints of said partition. Some tell it has to be entirely in 
> >>>the first
> >>>8MB, others the first 5MB, and my powerstack has a 17MB boot 
> >>>partition
> >>>right now.
> >>
> >>All I can say, it's that my boot PReP partition is the 1st and about 
> >>4 MB in
> >>size (cannot size it less than 1% of the disk.....)
> >>second partition is /
> >>third is swap.
> >
> >BTW, for debian, it makes more sense to have the second partition as 
> >swap, and
> >the third as /, i think, since it was decided some time back to 
> >default to
> >root=/dev/sda3, and not sda2.
> >
> >>That works for me.
> >
> >Until the kernel grows beyond 4MB.
>

(Continue reading)

headers

Leigh Brown | 5 Jan 2005 17:30

Re: 43p-140 install issues

Sven Luther said:
> On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
>> On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:
>> >On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
>> >>>BTW, i have another question. I am trying to fix debian-installer
>> >>>to create the prep partition, but i would like to have some info
>> >>>on the expected constraints of said partition. Some tell it has
>> >>>to be entirely in the first 8MB, others the first 5MB, and my
>> >>>powerstack has a 17MB boot partition right now.
>> >>
>> >>All I can say, it's that my boot PReP partition is the 1st and about
>> >>4 MB in size (cannot size it less than 1% of the disk.....)
>> >>second partition is /
>> >>third is swap.
>> >
>> >BTW, for debian, it makes more sense to have the second partition
>> >as swap, and the third as /, i think, since it was decided some
>> >time back to default to root=/dev/sda3, and not sda2.
>> >
>> >>That works for me.
>> >
>> >Until the kernel grows beyond 4MB.
>>
>> The size of that partition depends on firmware limitations. I have
>> definitely seen reports of systems not booting when the PReP boot
>> partition was too large. I think on some systems that has even happened
>> at 8MB.
>
> Is the problem really the size of the partition, or the space used by
> the kernel. I mean we could make a 100MB partition at start, and since

(Continue reading)

headers

Sven Luther | 5 Jan 2005 18:00

Re: 43p-140 install issues

On Wed, Jan 05, 2005 at 04:30:05PM -0000, Leigh Brown wrote:
> Sven Luther said:
> > On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
> >> On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:
> >> >On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> >> >>>BTW, i have another question. I am trying to fix debian-installer
> >> >>>to create the prep partition, but i would like to have some info
> >> >>>on the expected constraints of said partition. Some tell it has
> >> >>>to be entirely in the first 8MB, others the first 5MB, and my
> >> >>>powerstack has a 17MB boot partition right now.
> >> >>
> >> >>All I can say, it's that my boot PReP partition is the 1st and about
> >> >>4 MB in size (cannot size it less than 1% of the disk.....)
> >> >>second partition is /
> >> >>third is swap.
> >> >
> >> >BTW, for debian, it makes more sense to have the second partition
> >> >as swap, and the third as /, i think, since it was decided some
> >> >time back to default to root=/dev/sda3, and not sda2.
> >> >
> >> >>That works for me.
> >> >
> >> >Until the kernel grows beyond 4MB.
> >>
> >> The size of that partition depends on firmware limitations. I have
> >> definitely seen reports of systems not booting when the PReP boot
> >> partition was too large. I think on some systems that has even happened
> >> at 8MB.
> >
> > Is the problem really the size of the partition, or the space used by

(Continue reading)

headers

Philippe Guyot | 5 Jan 2005 17:18

Re: 43p-140 install issues

On Wednesday 05 January 2005 17:08, Sven Luther wrote:
> On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
> > On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:
> > >On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> > >>>BTW, i have another question. I am trying to fix debian-installer to
> > >>>create
> > >>>the prep partition, but i would like to have some info on the
> > >>>expected
> > >>>constraints of said partition. Some tell it has to be entirely in
> > >>>the first
> > >>>8MB, others the first 5MB, and my powerstack has a 17MB boot
> > >>>partition
> > >>>right now.
> > >>
> > >>All I can say, it's that my boot PReP partition is the 1st and about
> > >>4 MB in
> > >>size (cannot size it less than 1% of the disk.....)
> > >>second partition is /
> > >>third is swap.
> > >
> > >BTW, for debian, it makes more sense to have the second partition as
> > >swap, and
> > >the third as /, i think, since it was decided some time back to
> > >default to
> > >root=/dev/sda3, and not sda2.
> > >
> > >>That works for me.
> > >
> > >Until the kernel grows beyond 4MB.
> >

(Continue reading)

headers

Hollis Blanchard | 5 Jan 2005 17:52

Re: 43p-140 install issues

On Jan 5, 2005, at 10:18 AM, Philippe Guyot wrote:
> On Wednesday 05 January 2005 17:08, Sven Luther wrote:
>> On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
>>>
>>> The size of that partition depends on firmware limitations. I have
>>> definitely seen reports of systems not booting when the PReP boot
>>> partition was too large. I think on some systems that has even 
>>> happened
>>> at 8MB.
>>
>> Is the problem really the size of the partition, or the space used by 
>> the
>> kernel. I mean we could make a 100MB partition at start, and since we 
>> just
>> dd the kernel to it, the kernel would be found at the start of the
>> partition, and the firmware probably doesn't care about the real size 
>> of
>> the partition, as long as it can access all the kernel data we dded 
>> to it,
>> no ?
>
> I agree, see the IEEE P1275 on solinno's site. OF determines the load 
> image
> length and transfers only that. I was able to verify that by dumping 
> storage
> after a "load" when debugging boot process.

Are you specifically talking about booting from a PReP partition and 
not a floppy disk or netboot? Did you dump the bytes from the disk just 
after the kernel and see if they were also present in memory?

(Continue reading)

headers

Philippe Guyot | 6 Jan 2005 10:12

Re: 43p-140 install issues


message resent on the list because an accident.

On Wednesday 05 January 2005 17:52, you wrote:
> On Jan 5, 2005, at 10:18 AM, Philippe Guyot wrote:
> > On Wednesday 05 January 2005 17:08, Sven Luther wrote:
> >> On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
> >>> The size of that partition depends on firmware limitations. I have
> >>> definitely seen reports of systems not booting when the PReP boot
> >>> partition was too large. I think on some systems that has even
> >>> happened
> >>> at 8MB.
> >>
> >> Is the problem really the size of the partition, or the space used by
> >> the
> >> kernel. I mean we could make a 100MB partition at start, and since we
> >> just
> >> dd the kernel to it, the kernel would be found at the start of the
> >> partition, and the firmware probably doesn't care about the real size
> >> of
> >> the partition, as long as it can access all the kernel data we dded
> >> to it,
> >> no ?
> >
> > I agree, see the IEEE P1275 on solinno's site. OF determines the load
> > image
> > length and transfers only that. I was able to verify that by dumping
> > storage
> > after a "load" when debugging boot process.
>

(Continue reading)

headers

Philippe Guyot | 5 Jan 2005 15:02

Re: 43p-140 install issues

On Wednesday 05 January 2005 12:47, Sven Luther wrote:
> On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> > > BTW, i have another question. I am trying to fix debian-installer to
> > > create the prep partition, but i would like to have some info on the
> > > expected constraints of said partition. Some tell it has to be entirely
> > > in the first 8MB, others the first 5MB, and my powerstack has a 17MB
> > > boot partition right now.
> >
> > All I can say, it's that my boot PReP partition is the 1st and about 4 MB
> > in size (cannot size it less than 1% of the disk.....)
> > second partition is /
> > third is swap.
>
> BTW, for debian, it makes more sense to have the second partition as swap,
> and the third as /, i think, since it was decided some time back to default
> to root=/dev/sda3, and not sda2.

Yes, I did that on my two 150.

>
> > That works for me.
>
> Until the kernel grows beyond 4MB.
>

Friendly.
Felipe

headers

Leigh Brown | 5 Jan 2005 11:00

Re: 43p-140 install issues

Philippe Guyot said:
> On Wednesday 05 January 2005 10:03, Sven Luther wrote:
>> On Tue, Jan 04, 2005 at 10:39:15PM -0000, Leigh Brown wrote:
[...]
>> > The PReP specs says that the cards should be initialised to a
>> > minimum resolution of 640x480 iirc.  The boot loader has code to
>> > manually reprogram the card *back* into VGA text mode, but only
>> > for a very limited number of cards.  So, if your card is not
>> > supported by fbdev, and isn't one of the very few supported
>> > cards in the boot loader, it simply won't work under PReP.
>>
>> Ah, ok ... Well i have a cirrus logic card also, and it seems to work. I
>> have anot yet tried the matrox cards though. Do they need to be special
>> cards with forth rom, or will any do ?
>
> Well, my box seems to have a matrox video card and I did the install with
> my graphical console, not the tty.
[...]

That's because your Matrox card is fully supported by fbdev.

Cheers,

Leigh.

--

-- 
To UNSUBSCRIBE, email to debian-powerpc-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

(Continue reading)

headers

Sven Luther | 3 Jan 2005 18:28

Re: 43p-140 install issues

On Mon, Jan 03, 2005 at 04:50:00PM -0000, Leigh Brown wrote:
> Ulrich Teichert said:
> > This seems to result in a different setting and the kernel is not able
> > to figure out that it is running on a serial console. According to Leigh
> > Browns, it is not possible to give the kernel parameters on boot-up,
> > unless you are using his patches, so this may be another issue.
> 
> I have a patch you can use to specify parameters on the *command line*
> (e.g. boot floppy: root=/dev/sda3 ...).  However, you can always type
> parameters on the serial console as it boots (see below).

Mmm, is this one already present in the debian 2.6.8 kernel packages ? If not
we would probably want to include it. I am currently preparing a bunch of prep
patches, so it is a good idea to include this one too. How is it related to
the below command line prompt thingy ...

> > But this is how far the default kernel (which is all I can load from CD)
> > boots:
> >
> > 0 > setenv load-base 1000000  ok
> > 0 > setenv real-base c00000  ok
> > 0 > boot cdrom:
> >
> > loaded at:     01000400 01492FF4
> > relocated to:  00800000 00C92BF4
> > zimage at:     0080A94C 0093E3DC
> > initrd at:     0093F000 00C884AE
> > avail ram:     00400000 00800000
> >
> > Linux/PPC load: console=ttyS0,9600 console=tty0

(Continue reading)

headers

Sven Luther | 3 Jan 2005 15:01

Re: 43p-140 install issues

On Mon, Jan 03, 2005 at 08:39:43AM -0500, Mike Martin wrote:
> On Mon, 3 Jan 2005 08:05:35 +0100, Sven Luther <sven.luther <at> wanadoo.fr> wrote:
> 
> [snip]
> > There may be some problems with 2.6 kernels and pci irqs on prep. I will
> > investigate this shortly.
> 
> There is definitely something strange happening. The image I used to
> do the (nearly) complete install will no longer configure the network.
> Very inconsistent. I will try it (same image) again later today and
> see if it "just works" next time - like it did last time.

What exact machine do you have again ? 

> [snip]
> > 
> > Yep. Until partman-prep is ready, you should simply try to add the prep flag
> > to the a small partition. I think the normal scheme is to create /dev/sdb1 as
> > a small (8MB ?) prep partition, /dev/sdb2 as swap, and /dev/sdb3 as /. If
> > partman is not able to do it, jump to console 2, and launch parted directly,
> > and do a set 1 prep on.
> 
> Can't jump to console 2 - I can only comunicate through the serial

Ok, then go to execute a shell then.

> console. However I'll give this a shot through the "execute shell"
> menu item. "set 1 prep on"? Haven't seen that documented anywhere,
> what does it do?

(Continue reading)

headers

Mike Martin | 3 Jan 2005 15:07

Re: 43p-140 install issues

On Mon, 3 Jan 2005 15:01:02 +0100, Sven Luther <sven.luther <at> wanadoo.fr> wrote:

[snip]
> What exact machine do you have again ?

An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.

[snip]

> 
> set <minor> <flag> <on|off>
> 
> minor is the partition, starting at 1, flag is the flag, (prep in this case)
> and on|off is obvious.
> 
> It simply sets the prep flag, which is then translated as a 0x41 partition
> type. I think this is a deficiency in the parted/libparted API, but well,
> there is not much we can do about that unless a major libparted change.

Cool. That's good to know.

[snip]

> Yep, d-i uses devfs, still partitions start at 1.

Ok. Oops

> > I see how much more time I can buy with this machine. It may need to
> > go back into storage this week if I can't make it run. Not fun.
>

(Continue reading)

headers

Sven Luther | 3 Jan 2005 15:30

Re: 43p-140 install issues

On Mon, Jan 03, 2005 at 09:07:31AM -0500, Mike Martin wrote:
> On Mon, 3 Jan 2005 15:01:02 +0100, Sven Luther <sven.luther <at> wanadoo.fr> wrote:
> 
> [snip]
> > What exact machine do you have again ?
> 
> An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.

Well, prep_pci.c does know about : 

  IBM RS/6000 7043-240 (ibm_doral)
  IBM RS/6000 7024-E30

As far as IBM boxes are concerned. Doe the -140 have stuff in common with
leigh's -240 (the -140 being mono-cpu while the -240 being dual ?).

> [snip]
> 
> > 
> > set <minor> <flag> <on|off>
> > 
> > minor is the partition, starting at 1, flag is the flag, (prep in this case)
> > and on|off is obvious.
> > 
> > It simply sets the prep flag, which is then translated as a 0x41 partition
> > type. I think this is a deficiency in the parted/libparted API, but well,
> > there is not much we can do about that unless a major libparted change.
> 
> Cool. That's good to know.

(Continue reading)

headers

Philippe Guyot | 3 Jan 2005 15:30

Re: 43p-140 install issues

On Monday 03 January 2005 15:30, Sven Luther wrote:
> On Mon, Jan 03, 2005 at 09:07:31AM -0500, Mike Martin wrote:
> > On Mon, 3 Jan 2005 15:01:02 +0100, Sven Luther <sven.luther <at> wanadoo.fr>
> > wrote:
> >
> > [snip]
> >
> > > What exact machine do you have again ?
> >
> > An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.

I suppose you meen 233 Mhz ?
>
> Well, prep_pci.c does know about :
>
>   IBM RS/6000 7043-240 (ibm_doral)
>   IBM RS/6000 7024-E30
>
> As far as IBM boxes are concerned. Doe the -140 have stuff in common with
> leigh's -240 (the -140 being mono-cpu while the -240 being dual ?).

More different than that, 140 is more recent.

But works fine with Debian woody.(sorry Sven...)

>
> > [snip]
> >
> > > set <minor> <flag> <on|off>
> > >

(Continue reading)

headers

Mike Martin | 4 Jan 2005 05:03

Re: 43p-140 install issues

(Re-posting with shorter attachment to please the list gods. Sorry)

> If there is such a deadline, why not consider to install first a woody (many
> successes exist) then upgrading to sarge after ?

Ok... trying again with Leigh Brown's boot image and a woody root
floppy and a woody CD.

The console capture is below. Leigh's kernel boots up great, asks for
a root floppy and then ...

VFS: Insert root floppy and press ENTER

FAT: bogus logical sector size 1981
FAT: bogus logical sector size 1981
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 64, size 1024)
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 8, size 1024)
Kernel panic: VFS: Unable to mount root fs on 02:00

Reiserfs? Huh? I tried it twice, two different floppies. Both written
as follows (as suggested in Debian manual):
sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
\1440+0 records in
1440+0 records out
1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)

I can however boot the installation I made earlier using Leigh's
image. I have completed the installation and it runs ... for a short

(Continue reading)

headers

Philippe Guyot | 4 Jan 2005 10:23

Re: 43p-140 install issues

On Tuesday 04 January 2005 05:03, Mike Martin wrote:
> (Re-posting with shorter attachment to please the list gods. Sorry)
>
> > If there is such a deadline, why not consider to install first a woody
> > (many successes exist) then upgrading to sarge after ?
>
> Ok... trying again with Leigh Brown's boot image and a woody root
> floppy and a woody CD.
>
> The console capture is below. Leigh's kernel boots up great, asks for
> a root floppy and then ...
>
> VFS: Insert root floppy and press ENTER
>
> FAT: bogus logical sector size 1981
> FAT: bogus logical sector size 1981
> read_super_block: can't find a reiserfs filesystem on (dev 02:00,
> block 64, size 1024)
> read_super_block: can't find a reiserfs filesystem on (dev 02:00,
> block 8, size 1024)
> Kernel panic: VFS: Unable to mount root fs on 02:00
>
> Reiserfs? Huh? I tried it twice, two different floppies. Both written
> as follows (as suggested in Debian manual):
> sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
> \1440+0 records in
> 1440+0 records out
> 1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)
>
> I can however boot the installation I made earlier using Leigh's

(Continue reading)

headers

Ulrich Teichert | 4 Jan 2005 12:19

Re: 43p-140 install issues

Hi,

[del]
> BTW, what about your firmware? Is it the most recent one ?

Yes, it is. I have asked this before 

CU,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert <at> gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

--

-- 
To UNSUBSCRIBE, email to debian-powerpc-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

headers

Mike Martin | 4 Jan 2005 12:23

Re: 43p-140 install issues

The firmware is the most recent.

The kernel (boot) is Leigh's 2.4.19 kernel.

The root is from Woody.

Both floppies were written with dd to blank, unforatted disks.

I'll give 2.4.22 a try tonight.

Thanks!
MikeMartin

On Tue, 4 Jan 2005 10:23:37 +0100, Philippe Guyot <pguyot <at> cvf.fr> wrote:
> On Tuesday 04 January 2005 05:03, Mike Martin wrote:
> > (Re-posting with shorter attachment to please the list gods. Sorry)
> >
> > > If there is such a deadline, why not consider to install first a woody
> > > (many successes exist) then upgrading to sarge after ?
> >
> > Ok... trying again with Leigh Brown's boot image and a woody root
> > floppy and a woody CD.
> >
> > The console capture is below. Leigh's kernel boots up great, asks for
> > a root floppy and then ...
> >
> > VFS: Insert root floppy and press ENTER
> >
> > FAT: bogus logical sector size 1981
> > FAT: bogus logical sector size 1981

(Continue reading)

headers

Mike Martin | 4 Jan 2005 14:41

Re: 43p-140 install issues

> I'll give 2.4.22 a try tonight.
> 
> Thanks!
> MikeMartin

I gave Leigh's 2.4.22 a try. It gave me the same result with the
debian root disk:

VFS: Insert root floppy and press ENTER

FAT: bogus logical sector size 1981
FAT: bogus logical sector size 1981
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 64, size 1024)
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 8, size 1024)
Kernel panic: VFS: Unable to mount root fs on 02:00

Tonight I'll grab a different root floppy and see what happens.

Leigh's 2.4.22 will also boot the system installed on /dev/sdb1,
however it also stopped responding after awhile. I think it lasted
longer than with 2.4.19.

MikeMartin

headers

Ulrich Teichert | 4 Jan 2005 16:23

Re: 43p-140 install issues

Hi,

>I gave Leigh's 2.4.22 a try. It gave me the same result with the
>debian root disk:
>
>VFS: Insert root floppy and press ENTER
>
>FAT: bogus logical sector size 1981
>FAT: bogus logical sector size 1981
>read_super_block: can't find a reiserfs filesystem on (dev 02:00,
>block 64, size 1024)
>read_super_block: can't find a reiserfs filesystem on (dev 02:00,
>block 8, size 1024)
>Kernel panic: VFS: Unable to mount root fs on 02:00

Could you try to format them before dd'ing on them, like fdformat /dev/fd0h1440?
I am not sure if that will change anything, though.

>Tonight I'll grab a different root floppy and see what happens.
>
>Leigh's 2.4.22 will also boot the system installed on /dev/sdb1,
>however it also stopped responding after awhile. I think it lasted
>longer than with 2.4.19.

I am begining to believe that there is some sort of hardware problem with your
box or it is an upgraded version which was a -140 in it's previous life, but my
-140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
I will leave it running tonight to see what happens,

HTH,

(Continue reading)

headers

Mike Martin | 4 Jan 2005 16:39

Re: 43p-140 install issues

On Tue, 4 Jan 2005 16:23:50 +0100 (MET), Ulrich Teichert 
> Could you try to format them before dd'ing on them, like fdformat /dev/fd0h1440?
> I am not sure if that will change anything, though.

Will do.

> 
> I am begining to believe that there is some sort of hardware problem with your
> box or it is an upgraded version which was a -140 in it's previous life, but my
> -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
> I will leave it running tonight to see what happens,
> 
> HTH,
> Uli

I am starting to believe this as well. I'm going to see if I can get
some history on the machine from before it was shelved. As well, I
know there is a second machine, I'm going to see if I can swap this
one for that one and see if the same issues exist.

MikeMartin

headers

Mike Martin | 5 Jan 2005 05:36

Re: 43p-140 install issues

On Tue, 4 Jan 2005 10:39:41 -0500, Mike Martin <sydneymartin <at> gmail.com> wrote:
> On Tue, 4 Jan 2005 16:23:50 +0100 (MET), Ulrich Teichert
> > Could you try to format them before dd'ing on them, like fdformat /dev/fd0h1440?
> > I am not sure if that will change anything, though.
> 
> Will do.

Done - no difference. Same message. Written multiple images, multiple
times on multiple machine. Each one with the same result. At least I'm
not completely alone, I found this:
http://wikihip.cern.ch/twiki/bin/view/RS6000/KernelTestsOn43P240 exact
same error.

> >
> > I am begining to believe that there is some sort of hardware problem with your
> > box or it is an upgraded version which was a -140 in it's previous life, but my
> > -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
> > I will leave it running tonight to see what happens,
> >
> > HTH,
> > Uli
> 
> I am starting to believe this as well. I'm going to see if I can get
> some history on the machine from before it was shelved. As well, I
> know there is a second machine, I'm going to see if I can swap this
> one for that one and see if the same issues exist.
> 
> MikeMartin
> 
The machine was working fine under AIX when it was decomissioned. It

(Continue reading)

headers

Mike Martin | 6 Jan 2005 04:35

Re: 43p-140 install issues

> > > I am begining to believe that there is some sort of hardware problem with your
> > > box or it is an upgraded version which was a -140 in it's previous life, but my
> > > -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
> > > I will leave it running tonight to see what happens,

[snip]

> The machine was working fine under AIX when it was decomissioned. It
> had some issues with a disk going bad due to heat (blocked vents). But
> once they were cleared there were no issues. I am going to try the
> other machine. I'll keep my finger's crossed.
> 
> MikeMartin

An update (Sucess!!!):
After jogging some people's memory I found out that this machine has a
PCI token ring card (which I wasn't using) because the on-board
ethernet went flaky. This certainly helps explain my intermitent
network, and quite possibly the short up-times before crashing. As we
guessed - a hardware problem.

Is there any way (jumper ?) to disable the onboard ethernet? I may try
not loading the modules for it and see if the machine becomes stable.
Would a standard PCI ethernet card work as a substitute (likely won't
netboot)?

Now the success:
I put Leigh's boot floppy and the Woody root floppy (from
debian.yorku.ca mirror) into the second machine at noon today. By 1pm
I had a fully installed, configured and self-booting installation of

(Continue reading)

headers

Mike Martin | 7 Jan 2005 06:10

Re: 43p-140 install issues

Another update, More success

> An update (Sucess!!!):
> After jogging some people's memory I found out that this machine has a
> PCI token ring card (which I wasn't using) because the on-board
> ethernet went flaky. This certainly helps explain my intermitent
> network, and quite possibly the short up-times before crashing. As we
> guessed - a hardware problem.
> 
> Is there any way (jumper ?) to disable the onboard ethernet? I may try
> not loading the modules for it and see if the machine becomes stable.
> Would a standard PCI ethernet card work as a substitute (likely won't
> netboot)?

I checked the machine's docs - there appears to be no jumper to
disable the onboard ethernet. However, If I simply unplug the ethernet
cable the instability seems to diappear. The machine just did a
flawless install booting from Leigh's disk, Woody root on a floppy and
base on cd-rom.

I have a PCI ethernet card left over from an old PentiumPro. It says
it is a 3Com "Fast EtherLink XL PCI" "3C905-TX". Would this card work
in this machine? Would it be able to netboot (doubtfull).

MikeMartin

headers

Sven Luther | 7 Jan 2005 08:57

Re: 43p-140 install issues

On Fri, Jan 07, 2005 at 12:10:49AM -0500, Mike Martin wrote:
> Another update, More success
> 
> > An update (Sucess!!!):
> > After jogging some people's memory I found out that this machine has a
> > PCI token ring card (which I wasn't using) because the on-board
> > ethernet went flaky. This certainly helps explain my intermitent
> > network, and quite possibly the short up-times before crashing. As we
> > guessed - a hardware problem.
> > 
> > Is there any way (jumper ?) to disable the onboard ethernet? I may try
> > not loading the modules for it and see if the machine becomes stable.
> > Would a standard PCI ethernet card work as a substitute (likely won't
> > netboot)?
> 
> I checked the machine's docs - there appears to be no jumper to
> disable the onboard ethernet. However, If I simply unplug the ethernet
> cable the instability seems to diappear. The machine just did a
> flawless install booting from Leigh's disk, Woody root on a floppy and
> base on cd-rom.

What about d-i or a debian kernel ? I will make a new upload of the powerpc
kernel this weekend, and if there is a fix needed for 43P-140, i would like to
fix it before that.

> I have a PCI ethernet card left over from an old PentiumPro. It says
> it is a 3Com "Fast EtherLink XL PCI" "3C905-TX". Would this card work
> in this machine? Would it be able to netboot (doubtfull).

Not sure if you need a forth-rom enabled card or not. I plugged a cheap

(Continue reading)

headers

Sven Luther | 6 Jan 2005 09:15

Re: 43p-140 install issues

On Wed, Jan 05, 2005 at 10:35:50PM -0500, Mike Martin wrote:
> > > > I am begining to believe that there is some sort of hardware problem with your
> > > > box or it is an upgraded version which was a -140 in it's previous life, but my
> > > > -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
> > > > I will leave it running tonight to see what happens,
> 
> [snip]
> 
> > The machine was working fine under AIX when it was decomissioned. It
> > had some issues with a disk going bad due to heat (blocked vents). But
> > once they were cleared there were no issues. I am going to try the
> > other machine. I'll keep my finger's crossed.
> > 
> > MikeMartin
> 
> An update (Sucess!!!):
> After jogging some people's memory I found out that this machine has a
> PCI token ring card (which I wasn't using) because the on-board
> ethernet went flaky. This certainly helps explain my intermitent
> network, and quite possibly the short up-times before crashing. As we
> guessed - a hardware problem.
> 
> Is there any way (jumper ?) to disable the onboard ethernet? I may try
> not loading the modules for it and see if the machine becomes stable.
> Would a standard PCI ethernet card work as a substitute (likely won't
> netboot)?

You have to blacklist the module in discover/hotplug, and it won't be loaded
at install time. In d-i, i believe you could rmmod it as soon as possible, not
sure if you can blacklist it, i will investigate.

(Continue reading)

headers

Leigh Brown | 5 Jan 2005 12:17

Re: 43p-140 install issues

Mike Martin said:
> On Tue, 4 Jan 2005 10:39:41 -0500, Mike Martin <sydneymartin <at> gmail.com>
> wrote:
>> On Tue, 4 Jan 2005 16:23:50 +0100 (MET), Ulrich Teichert
>> > Could you try to format them before dd'ing on them, like fdformat
>> /dev/fd0h1440?
>> > I am not sure if that will change anything, though.
>>
>> Will do.
>
> Done - no difference. Same message. Written multiple images, multiple
> times on multiple machine. Each one with the same result. At least I'm
> not completely alone, I found this:
> http://wikihip.cern.ch/twiki/bin/view/RS6000/KernelTestsOn43P240 exact
> same error.

I think I know what's going on here.  What boot arguments are you using?
You should have "load_ramdisk=1" in there somewhere at the very least.

Cheers,

Leigh.

--

-- 
To UNSUBSCRIBE, email to debian-powerpc-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

headers

Ulrich Teichert | 5 Jan 2005 09:07

Re: 43p-140 install issues

Hi,

[del]
>Done - no difference. Same message. Written multiple images, multiple
>times on multiple machine. Each one with the same result. At least I'm
>not completely alone, I found this:
>http://wikihip.cern.ch/twiki/bin/view/RS6000/KernelTestsOn43P240 exact
>same error.

Perhaps there are two different board revisions of -140's out? I'll check
what's written on the system board when I'm home again today.

>> > I am begining to believe that there is some sort of hardware problem with your
>> > box or it is an upgraded version which was a -140 in it's previous life, but my
>> > -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
>> > I will leave it running tonight to see what happens,
[del]

Still running fine:

wehrle:~> uname -a
Linux wehrle 2.4.19 #3 Sun Aug 4 08:28:30 BST 2002 ppc unknown
wehrle:~> uptime
 08:58:25 up 13:08,  1 user,  load average: 0.00, 0.00, 0.00

I did a kernel compile with a parallel scp transfer as well to put the box
under a bit of load before, no issues.

HTH,
Uli

(Continue reading)

headers

Ulrich Teichert | 5 Jan 2005 23:09

Re: 43p-140 install issues

Hi,

the only reference number on my board is the IBM FRU number:

FRU 93H7143

I would expect that you will have the same marking on your mainboard.
My box ran all day with various loads from high to low or no load
at all:

wehrle:~> uptime
 22:29:24 up 1 day,  2:39,  2 users,  load average: 0.15, 0.32, 0.61

with Leigh's 2.4.19 kernel. As I searched for the number, I noticed
that the CPU fan was *covered* with dirt. Perhaps you should have
a look at yours too, because the front fan will pick up all dust and
throw it right on the CPU fan. I still wonder why mine was still
spinning....

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert <at> gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

--

-- 
To UNSUBSCRIBE, email to debian-powerpc-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

(Continue reading)

headers

Ulrich Teichert | 4 Jan 2005 09:20

Re: 43p-140 install issues

Hi,

[del]
>Ok... trying again with Leigh Brown's boot image and a woody root
>floppy and a woody CD.
>
>The console capture is below. Leigh's kernel boots up great, asks for
>a root floppy and then ...
>
>VFS: Insert root floppy and press ENTER
>
>FAT: bogus logical sector size 1981
>FAT: bogus logical sector size 1981

Strange.

[del]
>Reiserfs? Huh? I tried it twice, two different floppies. Both written
>as follows (as suggested in Debian manual):
>sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
>\1440+0 records in
>1440+0 records out
>1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)

How did you format the floppys before?

>I can however boot the installation I made earlier using Leigh's
>image. I have completed the installation and it runs ... for a short
>period of time. After about 5 minutes or so it stops responding to the
>console and to pings.

(Continue reading)

headers

Mike Martin | 3 Jan 2005 15:43

Re: 43p-140 install issues

> > > An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.
> 
> I suppose you meen 233 Mhz ?

I know 332 MHz doesn't sound right ... but I'm sure that's what it
says on the IBM nameplate on the front. I'll verify this tonight

> More different than that, 140 is more recent.

Have you got specs and stuff on the -140 you could link to? Maybe this
would help.

> 
> But works fine with Debian woody.(sorry Sven...)
[snip]
> If there is such a deadline, why not consider to install first a woody (many
> successes exist) then upgrading to sarge after ?

This is my preference. I'd like to install woody on one drive so I can
boot it up and say "Look Linux runs, it's stable and useful" and then
have the other to install, boot, and otherwise help test the new
stuff.

Unfortunately, I can't get _anything_ to install (I even tried a BSD,
but quickly realized I was in too deep there!). The unstable stuff I'm
trying now has gotten me the furthest along.

MikeM

(Continue reading)

headers

vinai | 3 Jan 2005 16:47

Re: 43p-140 install issues

>>>> An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.
>>
>> I suppose you meen 233 Mhz ?
>
> I know 332 MHz doesn't sound right ... but I'm sure that's what it
> says on the IBM nameplate on the front. I'll verify this tonight

According to this page:

    http://www.sinca.biz/IBM/rs6000_43p_140.html

the 7043-140 does come in 2 flavours, a 233 and 332 MHz model.  I've
been looking into getting my own 150 to play with :)

cheers
vinai

--

-- 
To UNSUBSCRIBE, email to debian-powerpc-REQUEST <at> lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster <at> lists.debian.org

headers

Sven Luther | 3 Jan 2005 15:45

Re: 43p-140 install issues

On Mon, Jan 03, 2005 at 03:30:54PM +0100, Philippe Guyot wrote:
> On Monday 03 January 2005 15:30, Sven Luther wrote:
> > On Mon, Jan 03, 2005 at 09:07:31AM -0500, Mike Martin wrote:
> > > On Mon, 3 Jan 2005 15:01:02 +0100, Sven Luther <sven.luther <at> wanadoo.fr>
> > > wrote:
> > >
> > > [snip]
> > >
> > > > What exact machine do you have again ?
> > >
> > > An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.
> 
> 
> I suppose you meen 233 Mhz ?
> >
> > Well, prep_pci.c does know about :
> >
> >   IBM RS/6000 7043-240 (ibm_doral)
> >   IBM RS/6000 7024-E30
> >
> > As far as IBM boxes are concerned. Doe the -140 have stuff in common with
> > leigh's -240 (the -140 being mono-cpu while the -240 being dual ?).
> 
> More different than that, 140 is more recent.
> 
> But works fine with Debian woody.(sorry Sven...)

Yeah, that is not the problem, the problem is that it doesn't work with the
2.6.8 kernel used by debian/sarge. So, now, the first order of business to fix
this is to find out what exactly is broken in the 2.6.8 kernel on this

(Continue reading)