ppc March 2005

ppc@lists.fedoraproject.org

21 participants
24 discussions

Mac Mini installation problem
by dj faké 30 Mar '05

30 Mar '05

trying to install FC4-PPC on Mac Mini, running into a odd problem - can't eject the disc. On a "regular" keyboard, F12 is the eject key, except it's mapped to "next" in FC-PPC. Trying to get out of the gui, but no luck. Anyone have tips for CD installation? btw, was able to install FC3-PPC via network, but it took forever and a day to install. Never got the audio to work on the Mini. c

4 5

Mac Mini
by dj faké 30 Mar '05

30 Mar '05

Hi - Finished installing FC3 on my Mac Mini. For the most part it went well. Did have issues with CD installation; using a PC keyboard I could not eject the boot CD so had to use Network install. X also gave a few hiccups on first boot, but nothing that didn't work itself out. Still haven't worked on the dual boot, and the audio doesn't work. Does FC4 fix any of this? c

2 1

power on after power loss
by Bret Hughes 30 Mar '05

30 Mar '05

Is there a way to set the power on after power loss on a mac mini? I can set it under OSX and it works but it does not seem like it works on the fedora side and Since I can't get to the bios ... I thought I would ask and in the meantime I will try to test thoroughly. Bret

5 4

Re: [PATCH] sleep & cpufreq problems
by David Woodhouse 29 Mar '05

29 Mar '05

On Tue, 2005-03-29 at 14:48 +1000, Benjamin Herrenschmidt wrote: > > > http://gate.crashing.org/~benh/ppc32-pmac-sleep-fix.diff > > http://gate.crashing.org/~benh/ppc32-cpufreq-gpio-off.diff > > I just updated the second patch, so if you got it since my last email, > please d/l it again. I still have no cpufreq on my PowerBook5,3. -- dwmw2

1 0

X hangs on FC4 t1 if no network connected on mac mini
by Bret Hughes 29 Mar '05

29 Mar '05

I have been testing Fedora core 4 test1 on a mac mini for a week or so and have hit the wall with regard to booting up without a network cable connected. eth0 is setup via dhcp This happens both in runlevel 3 and 5 X starts and vt7 is made active but no applications including the window manager ever start. I never even see the X curser. if I connect the cable, and ifup eth0 ( I do this with a cron job ) then killall X. X will work fine. no keyboard or mouse input is accepted. I cannot seem to recreate the scenario if I boot with the network on and then disable eth0 and even modprobe -r the sungem module. the hostname is in /etc/hosts ( it is not resolvable via dns anyway) Anyone have a direction where to look? Can anyone else recreate this error? Thanks in advance. Bret

2 1

Fedora 4 test 1 PPC left G5 unbootable
by Chris Leech 29 Mar '05

29 Mar '05

I attempted to install 3.90 on a single CPU G5 from DVD, which once I got the install image to boot and anaconda running seemed to go just fine. Unfortunately something seems to have gone wrong with the yaboot setup, and what I'm really worried about now is I can't get back into Mac OSX. I added a second SATA drive, and installed Fedora there. After installation nothing happened on reboot. From the OF shell I can find yaboot and boot into Fedora (X isn't working, there were some other errors I haven't looked into yet) but I can't get OSX running. I can start BootX (the apple BootX, not the old world Linux bootloader) but it doesn't seem to find the OS. From Linux I can see the first drive, but if I boot an OSX install CD it doesn't give me an option to install to that drive and Disk Utility doesn't show any partitions. Any ideas on what went wrong and how I might attempt to fix it? - Chris

2 2

Re: Overiding the default xorg config on the installer?
by Abel Lopez 26 Mar '05

26 Mar '05

If you're doing net installs (kickstart?) you can run Xautoconfig in the %pre section, or you could just run a text mode install. --Abe --- Keifer Miller <keifer.miller(a)gmail.com> wrote: > Ok, is it possible to overide the default xorg > config that the net > installer generates? Or prehapes to create a script > that runs > Xautoconfig? If it is possible, it might be able to > fix the problem > that users with gforce2 mx cards are having. It's > looking like anyone > with that card is getting this error: > > "Running anaconda, [...] > Probing for video card: NVIDIA GeForce 2MX > (generic) > Probing for monitor type: Unknown monitor > Probing for mouse type: Generic - 3 Button Mouse > (PS/2) > Attempting to start frame buffer X server > Waiting for X server to start...log located in > /tmp/X.log > 1...2...3..[..] X server started successfully. > mini-wm: Fatal IO error 104 (Connection reset by > peer) on X server :1.0" > > Another option would be to caniblize the graphical > installer for > yellowdog linux, as that version works on those > cards. Anyone have any > thoughts? > > [sorry if this is not that easy to read, meh typin' > aint too guud when > I'ma rushin'. :) ] > > _______________________________________________ > Fedora-ppc mailing list > Fedora-ppc(a)lists.infradead.org > http://lists.infradead.org/mailman/listinfo/fedora-ppc > __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

1 0

Overiding the default xorg config on the installer?
by Keifer Miller 25 Mar '05

25 Mar '05

Ok, is it possible to overide the default xorg config that the net installer generates? Or prehapes to create a script that runs Xautoconfig? If it is possible, it might be able to fix the problem that users with gforce2 mx cards are having. It's looking like anyone with that card is getting this error: "Running anaconda, [...] Probing for video card: NVIDIA GeForce 2MX (generic) Probing for monitor type: Unknown monitor Probing for mouse type: Generic - 3 Button Mouse (PS/2) Attempting to start frame buffer X server Waiting for X server to start...log located in /tmp/X.log 1...2...3..[..] X server started successfully. mini-wm: Fatal IO error 104 (Connection reset by peer) on X server :1.0" Another option would be to caniblize the graphical installer for yellowdog linux, as that version works on those cards. Anyone have any thoughts? [sorry if this is not that easy to read, meh typin' aint too guud when I'ma rushin'. :) ]

1 0

64-bit compilation in FC3
by Gary Byers 25 Mar '05

25 Mar '05

I installed FC-3 on an IBM 7043-260 (a POWER3) a few weeks ago; the installation went fairly smoothly. If I remember correctly, I did a "workstation" install. I find that compiling (linking) C programs in 64-bit mode doesn't work (or at least doesn't work as I expect): shell> cc -m64 hello.c /usr/bin/ld: skipping incompatible /usr/lib/gcc/ppc64-redhat-linux/3.4.2/../../../libc.so when searching for -lc /usr/bin/ld: skipping incompatible /usr/lib/gcc/ppc64-redhat-linux/3.4.2/../../../libc.a when searching for -lc /usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc /usr/bin/ld: skipping incompatible /usr/lib/libc.a when searching for -lc /usr/bin/ld: cannot find -lc collect2: ld returned 1 exit status I tried installing the gcc4 RPMs; it seemed able to find libc, but picked up the wrong versions of some runtime object files: gcc4 -m64 hello.c /usr/bin/ld: warning: powerpc:common architecture of input file `/usr/lib/gcc/ppc64-redhat-linux/4.0.0/../../../crt1.o' is incompatible with powerpc:common64 output /usr/bin/ld: warning: powerpc:common architecture of input file `/usr/lib/gcc/ppc64-redhat-linux/4.0.0/../../../crti.o' is incompatible with powerpc:common64 output /usr/bin/ld: warning: powerpc:common architecture of input file `/usr/lib/gcc/ppc64-redhat-linux/4.0.0/../../../crtn.o' is incompatible with powerpc:common64 output /usr/bin/ld: can not size stub section: Bad value /usr/lib/gcc/ppc64-redhat-linux/4.0.0/../../../crt1.o(.text+0x20): In function `_start': : relocation truncated to fit: R_PPC_REL24 __libc_start_main /usr/lib/gcc/ppc64-redhat-linux/4.0.0/../../../crti.o(.text+0x10): In function `call_gmon_start': : undefined reference to `_GLOBAL_OFFSET_TABLE_' /usr/bin/ld: /tmp/ccKMVHW4.o(.text+0x18): unresolvable R_PPC64_REL24 relocation against symbol `puts@@GLIBC_2.3' /tmp/ccKMVHW4.o(.text+0x18): relocation truncated to fit: R_PPC64_REL24 puts@@GLIBC_2.3 /usr/bin/ld: final link failed: Nonrepresentable section on output collect2: ld returned 1 exit status Which of the following is closest to being accurate: a) I'm missing something obvious; I need to say something more than just "-m64" here. b) linking 64-bit applications doesn't work in FC3 c) linking 64-bit applications works in FC3, but I need to install a few things that a "workstation" install doesn't install d) none of the above, the real probem is _____. The C compilers (both 3.4.2 and 4.0) do seem able to generate ppc64 assembly code, and the assembler seems able to assemble it; the problem seems to be some combination of bad specs file/missing files/bad gcc driver. If the answer is (b) or something like that, are things better in FC4T1 ? Thanks. Gary Byers gb(a)clozure.com

2 2

FC4T1 ppc install notes?
by nodata 24 Mar '05

24 Mar '05

Hi. Where can I find the install notes for getting FC4T1/ppc working? I've downloaded the boot.iso, burnt it and booted, but I get a message "the fedora core tree does not seem to match your boot media". Thanks

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

ppc March 2005