From: Ethan Benson <erbenson@alaska.net>
To: yaboot-users@lists.penguinppc.org,
yaboot-devel@lists.penguinppc.org,
Debian-powerpc <debian-powerpc@lists.debian.org>,
Linux/PPC-devel <linuxppc-dev@lists.linuxppc.org>,
yellowdog-general@lists.terrasoftsolutions.com,
yellowdog-devel@lists.terrasoftsolutions.com,
g5-test@lists.terrasoftsolutions.com
Subject: [YABOOT] Preliminary ofpath with 2.6 kernel support NEEDS TESTING
Date: Sun, 21 Mar 2004 17:35:36 -0900 [thread overview]
Message-ID: <20040322023536.GB21226@plato.local.lan> (raw)
Hello,
As many are painfully aware ofpath in current yaboot does not function
correctly under 2.6 systems, worse case it gives out bogus paths
therefore causing the system to fail to boot.
I have preliminary changes in current development version of yaboot
which fixes ofpath to support 2.6.4 and above kernels.
I need everyone with 2.6.4 or newer systems to test this version of
ofpath and verify that it produces correct OpenFirmware paths to your
devices (compare with ofpath output from a recent 2.4 kernel (2.4.23
or newer))
Prerequisites:
* You must have 2.6.4 or newer, previous versions lack necessary
sysfs information.
* You must have sysfs mounted (normally on /sys, but ofpath should be
able to detect where its mounted).
* You must still have /proc/ide so if this becomes a configurable
option like /proc/scsi you must have it enabled (/proc/scsi is also
required for machines with SATA drives).
The easiest way to test the new ofpath is download the current version
from http://penguinppc.org/~eb/files/ofpath and install it manually:
as root enter:
which ofpath
this will return the path of the active ofpath program, probably
/usr/sbin/ofpath
move it to safe place:
mv `which ofpath` /root
install the new version (put it in the same place as the old one was,
see step 1):
install -m 755 /home/youruser/ofpath /usr/sbin/ofpath
run ofpath on all your disk devices and ensure its output is correct.
then comment out any ofboot= lines in /etc/yaboot.conf and change your
macos* entries back to /dev/ nodes, run ybin and ensure the bootloader
functions correctly.
MOST IMPORTANTLY:
* REPORT SUCCESS *AND* FAILURE *
I want to know what kind of machine you have, and that ofpath worked
correctly, I will release yaboot 1.3.12 once I have enough success
reports for enough differing machines, very new machines are most
important, as they are the ones which old ofpath failed on.
Thanks in advance, and thanks to Nick Lopez for granting me local
shell access to his machine so I could get this done.
--
Ethan Benson
http://www.alaska.net/~erbenson/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-03-22 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 2:35 Ethan Benson [this message]
2004-03-22 3:07 ` [YABOOT] Preliminary ofpath with 2.6 kernel support NEEDS TESTING Benjamin Herrenschmidt
2004-03-23 4:55 ` digger vermont
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=20040322023536.GB21226@plato.local.lan \
--to=erbenson@alaska.net \
--cc=debian-powerpc@lists.debian.org \
--cc=g5-test@lists.terrasoftsolutions.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=yaboot-devel@lists.penguinppc.org \
--cc=yaboot-users@lists.penguinppc.org \
--cc=yellowdog-devel@lists.terrasoftsolutions.com \
--cc=yellowdog-general@lists.terrasoftsolutions.com \
/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;
as well as URLs for NNTP newsgroup(s).