public inbox for gentoo-ppc-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-ppc-user@lists.gentoo.org
Subject: Re: [gentoo-ppc-user] yaboot has kicked my butt - 5 times?!
Date: Thu, 23 Sep 2010 09:17:55 -0700	[thread overview]
Message-ID: <AANLkTinZWyqZidZJdu6Difr3q-aVKZVQHEeWhemD6f9S@mail.gmail.com> (raw)
In-Reply-To: <4C9B5FBE.9040604@gentoo.org>

On Thu, Sep 23, 2010 at 7:10 AM, Joseph Jezak <josejx@gentoo.org> wrote:
<SNIP>
>
> mtab is generated on boot as you mount devices. It's not the problem here.
>
> Can you try adding this line to your yaboot config? It will make the
> system boot directly into a shell instead of starting init:
> ### Put this in the kernel section
> append="init=/bin/bash"
>
> Once this boots, does hda* exist in /dev? How about /dev/null and /dev/zero?
>
> -Joe

OK, so I did it like this:

boot=/dev/hda2
#device=/pci@f4000000/ata-6@d/disk@0:
device=hd:
timeout=30
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot

image=/boot/kernel-2.6.34-gentoo-r1
        label=Gentoo-2.6.34-r1
        append="init=/bin/bash"
        partition=4
        root=/dev/hda4
        read-only

and ran ybin -v

When I reboot I have no keyboard and cannot probe around. The screen is showing

(none) / #

The kernel boots with printk timing info on each line, and then
finishes with two messages:

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

and at that point the machine is hung.

So this seems like it's just not finding the hardware at this point?
No disk? No keyboard?

If you want to see the whole screen I can post another screen shot on Flickr.

Thanks for the interest and help. I'm sure we'll figure it out.

- Mark



  reply	other threads:[~2010-09-23 16:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 22:59 [gentoo-ppc-user] yaboot has kicked my butt - 5 times?! Mark Knecht
2010-09-23  1:33 ` Joseph Jezak
2010-09-23  3:33   ` Mark Knecht
2010-09-23 12:05     ` kahl
2010-09-23 17:55       ` Mark Knecht
2010-09-23 19:59         ` Joseph Jezak
2010-09-23 14:10     ` Joseph Jezak
2010-09-23 16:17       ` Mark Knecht [this message]
2010-09-23 20:02         ` Joseph Jezak
2010-09-23 20:41           ` Mark Knecht
2010-09-24  5:04             ` Joseph Jezak
2010-09-24 20:30               ` Mark Knecht
2010-09-24 22:43                 ` Enlightened User
2010-09-25  0:23                   ` Mark Knecht
2010-09-25 11:45               ` Mark Knecht
2010-09-25 15:12                 ` Joseph Jezak
2010-09-25 20:40                   ` Mark Knecht
2010-09-25 21:01                     ` Mark Knecht
2010-09-25 22:40                     ` Mark Knecht
2010-09-26 17:36                     ` Joseph Jezak
2010-09-26 20:52                       ` Mark Knecht
2010-09-26 23:09                         ` Mark Knecht
2010-10-01 13:54                         ` Joseph Jezak
2010-10-01 21:03                           ` Mark Knecht
2010-10-07 17:34                             ` Joseph Jezak
2010-10-07 18:29                               ` Mark Knecht
2010-10-07 19:16                                 ` Joseph Jezak
2010-09-26 16:48 ` Klaus Müller
2010-09-26 19:08   ` Mark Knecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTinZWyqZidZJdu6Difr3q-aVKZVQHEeWhemD6f9S@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-ppc-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox