At Thu, 1 Apr 2004 22:29:42 -0500,
Nathanael Hasbrouck <[EMAIL PROTECTED]> wrote:
>
> On Thursday 01 April 2004 2031, somebody named Ron Murray inscribed this
> message:
>
> > ... and that's exactly what happened. I removed the PCI SCSI board,
> > disconnected power from the SCSI drives, the
At Thu, 1 Apr 2004 22:19:22 -0800,
Brad Boyer <[EMAIL PROTECTED]> wrote:
>
> On Thu, Apr 01, 2004 at 08:09:03PM -0500, Ron Murray wrote:
> >Hmmm. I've set the output device to the PCI display with BootVars,
> > but I still don't see anything. (I think the machine comes up a bit
> > faster no
On Thu, Apr 01, 2004 at 08:09:03PM -0500, Ron Murray wrote:
>Hmmm. I've set the output device to the PCI display with BootVars,
> but I still don't see anything. (I think the machine comes up a bit
> faster now, but I could be imagining things). I still can't get into OF:
> there's a pause,
On Thursday 01 April 2004 2031, somebody named Ron Murray inscribed this
message:
> ... and that's exactly what happened. I removed the PCI SCSI board,
> disconnected power from the SCSI drives, then connected an old SCSI
> drive to the other SCSI bus and powered it all up. The installer lock
Ron Murray wrote:
At Wed, 31 Mar 2004 22:09:45 -0500,
Nathanael Hasbrouck <[EMAIL PROTECTED]> wrote:
No chance of it being a termination problem, is there? Linux is a lot more
picky about that than MacOS, at least on my 7600's builtin controllers.
Had to do some black magic when I put an ID
Brad Boyer wrote:
On Wed, Mar 31, 2004 at 08:15:20PM -0500, Ron Murray wrote:
When I press cmd-opt-o-f (should I do this with power off and turn
the box on while holding them down, or can I do it a bit later? If so,
how long do you get to do it?), I get the same sequence as that above.
It m
At Wed, 31 Mar 2004 22:09:45 -0500,
Nathanael Hasbrouck <[EMAIL PROTECTED]> wrote:
> No chance of it being a termination problem, is there? Linux is a lot more
> picky about that than MacOS, at least on my 7600's builtin controllers.
> Had to do some black magic when I put an IDE disk in and t
On Wed, Mar 31, 2004 at 08:15:20PM -0500, Ron Murray wrote:
>When I press cmd-opt-o-f (should I do this with power off and turn
> the box on while holding them down, or can I do it a bit later? If so,
> how long do you get to do it?), I get the same sequence as that above.
> It may, of cours
On Wednesday 31 March 2004 2141, somebody named Ron Murray inscribed this
message:
> Benjamin Herrenschmidt wrote:
> >>Anyway, I'm back to having it crash during install. This time I
> >> got as far as the dhcp initialisation (which went ok, according to my
> >> dhcp server log). I then got th
Benjamin Herrenschmidt wrote:
Anyway, I'm back to having it crash during install. This time I got
as far as the dhcp initialisation (which went ok, according to my dhcp
server log). I then got the "dhcp went ok" dialog with the continue
button, but it had locked up at that point and hitting
> Anyway, I'm back to having it crash during install. This time I got
> as far as the dhcp initialisation (which went ok, according to my dhcp
> server log). I then got the "dhcp went ok" dialog with the continue
> button, but it had locked up at that point and hitting keys on the
> keyboa
Brad Boyer wrote:
What does it do when you try cmd-opt-o-f? Have you explicitly set the
output-device and input-device? OF is pretty dumb about auto-detecting
which devices you want to use for your console. Early models defaulted
to using the serial ports, but most G3 based models default to usi
Sven Luther wrote:
On Wed, Mar 31, 2004 at 03:16:31PM +1000, Benjamin Herrenschmidt wrote:
Do you have the System.map that corresponds to this kernel ? It's
needed to decode the numbers above.
It's the standard woody powerpc kernel, from the current CD I think
(downloaded it a couple of d
On Tue, Mar 30, 2004 at 04:41:55PM -0500, Ron Murray wrote:
>It does look like I have a lot to learn with these things,
> though. And I thought alphas were hard! For one thing, I don't seem to
> be able to get into Open Firmware on bootup, even when I press
> cmd-option-o-f like the book says.
Clearly it's a bug.
And I'll be submitting an installation report / bug report on this and
the other bug I noticed.
Probably this evening.
Rick
Sven Luther wrote:
>
> On Wed, Mar 31, 2004 at 12:57:13PM -0500, Rick Thomas wrote:
> >
> >
> > Rick Thomas wrote:
> > >
> > > This procedure worked,
On Wed, Mar 31, 2004 at 12:57:13PM -0500, Rick Thomas wrote:
>
>
> Rick Thomas wrote:
> >
> > This procedure worked, except for two "minor" glitches:
> >
> > 2) When it came time to reboot and run the configuration part, the
> > /etc/fstab file was empty so the reboot failed. I had to boot
> >
Rick Thomas wrote:
>
> This procedure worked, except for two "minor" glitches:
>
> 2) When it came time to reboot and run the configuration part, the
> /etc/fstab file was empty so the reboot failed. I had to boot
> single user and do
> mount -o remount /dev/hdc8 /
> to make root write
At Wed, 31 Mar 2004 12:13:13 +0200,
Sven Luther <[EMAIL PROTECTED]> wrote:
>
> On Wed, Mar 31, 2004 at 03:16:31PM +1000, Benjamin Herrenschmidt wrote:
> >
> > > >
> > > > Do you have the System.map that corresponds to this kernel ? It's
> > > > needed to decode the numbers above.
> > >
> > >
On Wed, Mar 31, 2004 at 03:16:31PM +1000, Benjamin Herrenschmidt wrote:
>
> > >
> > > Do you have the System.map that corresponds to this kernel ? It's
> > > needed to decode the numbers above.
> >
> > It's the standard woody powerpc kernel, from the current CD I think
> > (downloaded it a
This procedure worked, except for two "minor" glitches:
1) I had to use the "DEBCONF_PRIORITY=medium" kernel parameter to
get the menu that allowed me to execute "continue without
bootloader" immediately after partitioning and formatting the disk
(i.e. *before* it attempted to install a bootloade
Sven,
archdetect reports
powerpc/powermac_oldworld
In real life, it's a beige G3 mini-tower.
Hope this helps,
Rick
Sven Luther wrote:
>
>> libd-i or yaboot or something bug. Maybe archdetect is involved
too. Can
> you try going to the second console with alt+F2, and send the output of
> >
> > Do you have the System.map that corresponds to this kernel ? It's
> > needed to decode the numbers above.
>
> It's the standard woody powerpc kernel, from the current CD I think
> (downloaded it a couple of days ago). There's a copy of the sysmap on
> the CD; I'll email it direct t
On Wed, Mar 31, 2004 at 01:48:40PM +1000, Benjamin Herrenschmidt wrote:
>
> >
> > Now when I try and boot into the Linux installer, I always get a crash:
> >
> > Machine check in kernel mode. (regs at c01f5ea0)
> > Caused by (from srr1): Unknown values in srr1
> > NIP: C015E3CC XER: LR
Benjamin Herrenschmidt wrote:
Now when I try and boot into the Linux installer, I always get a crash:
Machine check in kernel mode. (regs at c01f5ea0)
Caused by (from srr1): Unknown values in srr1
NIP: C015E3CC XER: LR: C0163014 REGS: c01f5ea0 TRAP: 0200
MSR: 1030 [IR, DR, ME]
TASK
On Tue, Mar 30, 2004 at 06:57:30PM -0500, Rick Thomas wrote:
> 7) At some point inform d-i that I don't want it to
> install a boot loader.
> (*how???*)
d-i shouldn't even be trying to install yaboot-installer at all. Can you
get the contents of d-i's /var/log/syslog into a mail? It should con
Sorry to butt in, but Woody installs just fine on Old World Macs using boot
floppies and BootX and you can apt-get dist-upgrade to Sarge. I have a Mac
7300/180 running Sarge and kernel 2.4.25-ben1.
friendly,
--
jean-michel
>
> Now when I try and boot into the Linux installer, I always get a crash:
>
> Machine check in kernel mode. (regs at c01f5ea0)
> Caused by (from srr1): Unknown values in srr1
> NIP: C015E3CC XER: LR: C0163014 REGS: c01f5ea0 TRAP: 0200
> MSR: 1030 [IR, DR, ME]
> TASK = c01f41e0[0]
Benjamin Herrenschmidt wrote:
BootX version is 1.2.2. As for PCI cards, yes, I have three:
1. Atto "Express PCI" SCSI card. Has a SYM53c875 chip. No other markings.
2. Apple iX 3D video board. iXMICRO chip set. TI TVP3030 chip and
iXMICRO Twin Turbo 9135-388.
3. Apple Fast Ethernet 10/10
>
> BootX version is 1.2.2. As for PCI cards, yes, I have three:
>
> 1. Atto "Express PCI" SCSI card. Has a SYM53c875 chip. No other markings.
>
> 2. Apple iX 3D video board. iXMICRO chip set. TI TVP3030 chip and
> iXMICRO Twin Turbo 9135-388.
>
> 3. Apple Fast Ethernet 10/100Base-T Ca
Benjamin Herrenschmidt wrote:
On Tue, 2004-03-30 at 09:39, Ron Murray wrote:
I've been having lots of problems getting woody installed on a Power
Mac G3 minitower (300MHz processor, 128M RAM). Being an oldworld box, I
can't boot it from CD. I tried installing from floppies, but that tended
On Tue, Mar 30, 2004 at 07:46:35PM -0500, Rick Thomas wrote:
> I've gotten this far already several times. If I chose "continue
> without..." it complains that there are already files in the filesystem
> it's trying to install into. If I say go-ahead anyway, it downloads a
> bunch of duplicate pa
I've gotten this far already several times. If I chose "continue
without..." it complains that there are already files in the filesystem
it's trying to install into. If I say go-ahead anyway, it downloads a
bunch of duplicate packages and crashes when trying to re-install them.
I'm hoping that i
On Tue, Mar 30, 2004 at 06:57:30PM -0500, Rick Thomas wrote:
>
> Is there some way to tell d-i to not try to install a boot
> loader? I think that if I could get past that point, I
> might be able to finish a sarge new d-i installation using
> BootX as the boot loader.
Yes, it fails and then you
Is there some way to tell d-i to not try to install a boot
loader? I think that if I could get past that point, I
might be able to finish a sarge new d-i installation using
BootX as the boot loader.
Here's what I think I'd need to do:
1) Install MacOS (8.x or 9.x) in an HFS (*not* HFS+)
partiti
On Tue, 2004-03-30 at 09:39, Ron Murray wrote:
> I've been having lots of problems getting woody installed on a Power
> Mac G3 minitower (300MHz processor, 128M RAM). Being an oldworld box, I
> can't boot it from CD. I tried installing from floppies, but that tended
> to mostly crash just af
On Tue, Mar 30, 2004 at 04:41:55PM -0500, Ron Murray wrote:
> At Tue, 30 Mar 2004 23:30:25 +0200,
> Sven Luther <[EMAIL PROTECTED]> wrote:
> >
> > On Tue, Mar 30, 2004 at 04:01:59PM -0500, Rick Thomas wrote:
> > > Ron,
> > >
> > > I've done it (install woody on an OldWorld PowerMac) successfully.
At Tue, 30 Mar 2004 23:30:25 +0200,
Sven Luther <[EMAIL PROTECTED]> wrote:
>
> On Tue, Mar 30, 2004 at 04:01:59PM -0500, Rick Thomas wrote:
> > Ron,
> >
> > I've done it (install woody on an OldWorld PowerMac) successfully.
> > Email me at <[EMAIL PROTECTED]> if you need help.
> >
> > You need
On Tue, Mar 30, 2004 at 04:01:59PM -0500, Rick Thomas wrote:
> Ron,
>
> I've done it (install woody on an OldWorld PowerMac) successfully.
> Email me at <[EMAIL PROTECTED]> if you need help.
>
> You need BootX, as you have found out. You also need to make sure that
> your MacOS partition is HFS
Ron,
You don't need to mess with floppies. BootX, which you are already
using, works just fine -- and it handles kernels and ramdisk images that
are too big for a floppy. Once you get into the debian installer, you
will discover that it insists on trying to install the "yaboot"
bootloader, which
Ron,
I've done it (install woody on an OldWorld PowerMac) successfully.
Email me at <[EMAIL PROTECTED]> if you need help.
You need BootX, as you have found out. You also need to make sure that
your MacOS partition is HFS, not HFS+, so that you can copy updated
kernels to it while running Linux.
On Mon, Mar 29, 2004 at 06:39:29PM -0500, Ron Murray wrote:
>I've been having lots of problems getting woody installed on a Power
> Mac G3 minitower (300MHz processor, 128M RAM). Being an oldworld box, I
> can't boot it from CD. I tried installing from floppies, but that tended
> to mostly c
On (29/03/04 18:39), Ron Murray wrote:
>I've been having lots of problems getting woody installed on a Power
> Mac G3 minitower (300MHz processor, 128M RAM). Being an oldworld box, I
> can't boot it from CD. I tried installing from floppies, but that tended
> to mostly crash just after check
42 matches
Mail list logo
