gmane.linux.gentoo.ppc

Re: Re: Building QEMU on PS3 (Gentoo/PowerPC)

陳韋任 — 2011-04-11T06:39:43

Hi, Nell

  I tried the CRUX PPC approach, but no luck. Here is my
enviroment.

-------------------------------------------------------
$ gcc --version
gcc-4.5.2 (Gentoo 4.5.2 p1.1, pie-0.4.5) 4.5.2
$ uname -a
Linux ps3 2.6.37-rc6 #6 SMP Thu Jan 6 21:50:40 CST 2011 ppc64 Cell Broadband Engine, altivec supported GNU/Linux
-------------------------------------------------------

And what I did is,

-------------------------------------------------------
$ export CFLAGS="$CFLAGS -fno-var-tracking"
$ ../qemu-0.13.0/configure --prefix=/tmp/chenwj/install
--target-list=i386-linux-user
-------------------------------------------------------

  But it's still failed to compiling translate.o which is the
OOM (out of memory) probelm metioned on the QEMU mailing list.
"--enable-debug" option solve this OOM problem, though.

Regards,
chenwj

Re: Building QEMU on PS3 (Gentoo/PowerPC)

nello martuscielli — 2011-03-29T00:13:25

maybe this is useful:
http://forums.gentoo.org/viewtopic-p-6594579.html#6594579


cheers,
Nell

--
PowerMac G4 450MHz - CRUX PPC 2.7

Re: Are there any Pegasos users?

nello martuscielli — 2011-03-29T00:07:49

you could get a working linux config (for peg2) from CRUX-PPC install iso.


cheers,
Nell

Re: Are there any Pegasos users?

Konstantin Tokarev — 2011-03-23T09:05:43


22.03.2011, 23:50, "Johannes Geiss" <johannes.geiss< at >web.de>:


Hi Johannes,

I'm not a Pegasos user, but if you can get other Linux distribution running
on your system (e.g., some old version of Debian), you will be able to 
build Gentoo from its environment.

Are there any Pegasos users?

Johannes Geiss — 2011-03-22T20:50:56

Hi here,

are there any Pegasos users using Gentoo?

Especially the hardware platform Pegasos II?

I am looking for experiences about building an own kernel for this
architecture. I compile them by myself for some years, but I think I could
be better if I find someone else who is building kernels for Pegasos
II. I am interested to exchange/talk about config files and so on.

Unfortunately Gentoo seems to have dropped kernel support for Pegasos
for some years. No installation disk contains a kernel for this
hardware.

Bye
Johannes

Building QEMU on PS3 (Gentoo/PowerPC)

陳韋任 — 2011-02-23T06:31:51

Hi, folks

  I am trying to build QEMU 0.13/0.14 on a PS3 machine (Gentoo/PowerPC).
But I got a gcc internal error.

  Here is the system information:
------------------------------------------------------------------------
gcc (Gentoo 4.4.4-r2 p1.3, pie-0.4.5) 
Linux ps3 2.6.37-rc6
------------------------------------------------------------------------

  And here is the compliation error:
------------------------------------------------------------------------
  CC    i386-linux-user/translate.o
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <http://bugs.gentoo.org/> for instructions.
make[1]: *** [translate.o] Error 1
make: *** [subdir-i386-linux-user] Error 2
------------------------------------------------------------------------

  I saw that gentoo has qemu 0.14 in its protage. Do I miss something
while building qemu?

  Thanks!

Regards,
chenwj

Re: -mabi=altivec in CFLAGS

2010-12-02T15:50:03

I've had that ever since I startd using PowerPC,
without any problems I that I would consider attributing to that.



I did not do any comparisons.


Wolfram

-mabi=altivec in CFLAGS

Konstantin Tokarev — 2010-12-02T14:50:38

Hi all,

AFAIK, some packages (e.g., dev-cpp/eigen) can use AltiVec vectorization
only when -mabi=altivec is specified in GCC flags.

Is it safe to use -mabi=altivec in global CFLAGS in make.conf?
Does anybody know if the system will perform better or worse in average?

Re: yaboot has kicked my butt - 5 times?!

Joseph Jezak — 2010-10-07T19:16:57

No problem! I'm glad it's working. The documentation has not been
updated recently, and it's on my list of things to do. Unfortunately, so
are a lot of other things. :) I've added it to my documentation fix it
list, I'll make sure to get this added to the documentation as soon as I
find some free time.

Most people aren't hit by the bug because when udev is installed, it
warns that these options will cause problems. You got lucky I guess! :)

Glad you stuck with it!
-Joe

Re: yaboot has kicked my butt - 5 times?!

Mark Knecht — 2010-10-07T18:29:48

Thank you Joe. For the first time in a couple of months the machine just booted.

Note that I didn't easily find  CONFIG_SYSFS_DEPRECATED in make
menuconfig so I only disabled  CONFIG_SYSFS_DEPRECATED_V2 which was
enough to allow it to boot.

I took a quick look at the PPC install guide and frankly I don't see
instructions there to disable this option, although I have done this
on other machines. Is it just me or are the instructions actually not
in the kernel config section. If they are truly missing then it would
be great if someone could update that.

Anyway, it seems completely unreasonable for me, after all this, to
just say thanks for the help. It doesn't begin to represent how
appreciative I am of the time you spent looking into this with me. I
really am indebted.

Cheers,
Mark

Re: yaboot has kicked my butt - 5 times?!

Joseph Jezak — 2010-10-07T17:34:29


Another busy week, but I think we might have your answer.

Disable these options in your kernel config, recompile and give it a try:
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y

I think these options interfere with udev.
-Joe

Re: yaboot has kicked my butt - 5 times?!

Mark Knecht — 2010-10-01T21:03:34

Not a problem. I've been busy myself.

<SNIP>

Good.

<SNIP>

Attached unless GMail does something to it.

Thanks,
Mark

Re: yaboot has kicked my butt - 5 times?!

Joseph Jezak — 2010-10-01T13:54:37

 Sorry, I've had a busy week and didn't have time to respond!


Sorry, that was my mistake, I was running from memory. :) You have the
right invocation below.


Cool, so now we know that fsck is fine.

Okay, so we fixed the first thing. That's good. :) Can you attach your
whole kernel config? I'm wondering if maybe udev isn't running properly
due to a misconfiguration.

-Joe

Re: yaboot has kicked my butt - 5 times?!

Mark Knecht — 2010-09-26T23:09:28

<SNIP>

OK, I switched to the newer PMAC_MACIO driver built into the kernel.
Names changed but the result is the same - now it fails /dev/sda4

* Checking root filesystem...
fsck.ext3: No such file or directory while trying to open /dev/sda4
/dev/sda4:
The superblock could not be read or does not describe...

Note one interesting difference with the newer driver is that I
couldn't run fsck.ext3 until I rebuilt the kernel without all the
power management stuff. Seems that by default fsck thought we were
using the battery and deferred the check.

Possibly I could have used fsck -f but I didn't want to take any chances.

Anyway, the current state is that /dev/sda4 fails to mount. With the
newer driver and modified kernel I had no problems with your bash
instructions other than the procfs issue.

Can I go further booting the machine by hand? If booting using the
init=/sbin/bash allows me to check the disk but booting automatically
does then it seems I should be able to walk through by hand doing all
the steps until I get to the same failure point, correct? I think I'll
Google around for web pages that describe that sort of thing. Sounds
like an interesting thing to get educated on after using Linux for
more than a decade... :-)

Here's my current yaboot.conf and fstab files. Note that for now the
use of /dev/hda2 is due to using the install CD. I suppose those will
have to change to 'sd' if I ever get this machine to boot Gentoo
again. (Still hoping Klaus' comment this morning about bad drives
isn't the root cause here. The MacMini doesn't look easy to open for
disk replacements...)

Again, thanks for the ideas.

Cheers,
Mark

(chroot) livecd / # cat /etc/yaboot.conf
## yaboot.conf generated by yabootconfig 1.0.8
##
## run: "man yaboot.conf" for details. Do not make changes until you have!!
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

boot=/dev/hda2
#device=/pci< at >f4000000/ata-6< at >d/disk< at >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/sda4
        read-only
(chroot) livecd / #


(chroot) livecd / # cat /etc/fstab
/dev/sda4   /            ext3    noatime              0 1
/dev/sda3   none         swap    sw                   0 0

/dev/cdrom  /mnt/cdrom   auto    noauto,user          0 0

proc        /proc        proc    defaults             0 0
shm         /dev/shm     tmpfs   nodev,nosuid,noexec  0 0
(chroot) livecd / #

Re: yaboot has kicked my butt - 5 times?!

Mark Knecht — 2010-09-26T20:52:28

<SNIP>

OK - to me this doesn't look good:

 # mount -t procfs none /proc
mount:none has wrong device number or fs type procfs not supported

on the off chance you menat proc instead of procfs I tried it that way
and got a slightly more reasonable message:

# mount -t proc none /proc
can't create lock file /etc/mtab~1038: Read-only file system (use -n
flag to override)


Worked fine. fsck.ext3 said it was clean

Seemed to work. Got this message:

EXT3-fs: (hda4):using internal journal


Didn't boot but got a little farther. Doesn't complain about mtab
anymore but still complains:

* Checking root filesystem...
fsck.ext3: No such file or directory while trying to open /dev/hda4
/dev/hda4:
The superblock could not be read......


<SNIP>


OK - I'll go back in and look at my kernel config again. Thought I'd
post these results for now.

Please remember, I'm extremely thankful for all your help and the help
of others on this frustrating little problem.

Cheers,
Mark

Re: yaboot has kicked my butt - 5 times?!

Mark Knecht — 2010-09-26T19:08:53

Well, that's sort of scary but exactly describes my predicament!

Thanks,
Mark

Re: yaboot has kicked my butt - 5 times?!

Joseph Jezak — 2010-09-26T17:36:06

(snip)


Okay, let's try a few things now that we can boot the machine (even if
it's not all the way!).

First, lets mount proc:
# mount -t procfs none /proc

Now, try fsck.ext3 again. Does it work?

Next, let's remount the root file system read/write so we can modify files:
# mount -o remount,rw /
 
We'll copy the current mount information from proc to /etc/mtab and see
if that helps:
# cp /proc/self/mounts /etc/mtab
# mount -o remount,ro /

Now, try fsck.ext3 again. Does it work?

If so, try rebooting the system again. Does it boot now?

(snip)


hda4 will be  the right device as long as you have the old ide driver in
your kernel.

The old PMAC_IDE driver is getting picked before the PATA_MACIO driver.
If you'd like to try the newer driver, you'll need to disable the old
one first.

-Joe

Re: yaboot has kicked my butt - 5 times?!

Klaus Müller — 2010-09-26T16:48:51

Most likely nothing at all.

Your hd may be faulty.
I had a problem with such a hd some time ago
(not on PPC, and a really old hd btw).

No error was found by any hd-check.

[X]Ubuntu and Puppy installed, booted and worked fine,
Gentoo installed fine but refused to boot.

After replacing the hd, Gentoo installed, booted and works.

Re: yaboot has kicked my butt - 5 times?!

Mark Knecht — 2010-09-25T22:40:17

<SNIP>

No change at all using the kernel created by 'make pmac32_defconfig'.
Fails at the same place.

udev is version 151-r4. I haven't created any rules for it. It's all
default Gentoo.

While I'm sure I won't actually do it I feel very close to burying a
ball-peen hammer right in the middle of this little box and being done
with this mess... ;-)

 - Mark

Re: yaboot has kicked my butt - 5 times?!

Mark Knecht — 2010-09-25T21:01:13

<SNIP>
<SNIP>

Nix this comment. I got the command to work and am going back to
ground zero on the kernel config. We'll see what happens.

Sorry for the noise. Just frustrated after weeks of this. Mac is just
harder than PC I suppose...

Thanks,
Mark

Re: yaboot has kicked my butt - 5 times?!

Mark Knecht — 2010-09-25T20:40:40

<SNIP>

Really? OK - cool then.


I need to find a good _SIMPLE_ book on how Linux boots. I'm just a
long time use with no real sys admin background so for a decade or
longer I just want the things go by at boot and then use my system.


I cannot due to the same sort of message I get when trying to boot:

e2fsck_check_if_mount: Can't check if filesystem is mounted due to
missing mtab file
fsck.ext3: Device or resource busy while trying to open /dev/hda4
Filesystem mounted or opened exclusively by another program?

For kicks I tried umount /dev/hda4 but that complains about the
missing mtab file also. It seems from the man page I could force it
but I didn't want to do that, and again if I did and it even worked
then where would the system read fsck.ext3 from to do the check since
it's on /dev/hda4 itself?


udev would be whatever comes with a stable ppc system these days.

Other than running ~ppc portage and sandbox the machine is currently
all stable with no USE flags. The make.conf file is pretty much empty
other than the stuff the install has me put in. (Which mirrors to sync
from, etc.)

I've gone back and done a couple more experiments:

1) So far anything I try that refers to the drive as /dev/sda4 results
in a VFS not syncing type error so at least as far as the boot process
goes hda4 seems to be the right device.

2) I tried building in the PATA_MACIO driver but that by itself didn't
change anything:

(chroot) livecd / # cat /usr/src/linux/.config | grep MACIO
CONFIG_PATA_MACIO=y
CONFIG_ADB_MACIO=y
(chroot) livecd / #

The boot still fails at the same point with the same message. Possibly
some other ATA driver is being selected ahead of this one and maybe it
needs to be removed from the kernel? I don't know what to remove
though so I'm sort of stuck on that account.

3) If this is a kernel config issue - and it seem plausible that it is
- then I'll point out that the kernel config page of the Gentoo PPC
Istall Guide had a possible command that didn't work for me:

http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml?part=1&chap=7

Specifically:

make pmac32_defconfig

which supposedly will make a config file that would boot most 32-bit
machines. Unfortunately the command doesn't work for me on current
kernels. The install guide should be updated to either remove this or
make it more clear if I need to do anything more than that command in
the /usr/src/linux directory.

I've looked around at lots more stuff in my kernel config and compared
it to what the Install guide says. I don't see any differences but I
suspect there probably are.

Thanks!

- Mark