ppc February 2006

ppc@lists.fedoraproject.org

13 participants
19 discussions

(OT) Fedora Core 3 i386 newbie upgrade?
by Brian Durant 28 Feb '06

28 Feb '06

I have the chance of installing Fedora Core on a Dell laptop (PP10L) as a dual-boot system with XP. Since I have a freebie DVD with Core 3 i386 on it, I was wondering if i could use that to install from and then just do a 'yum update' over a wireless network to bring the system up to Core 4, rather than downloading a bunch of .iso files that I burn once, use the CD's once and then throw them away? The computer is one that my wife got through work about a year ago and never uses. For this reason, I am not afraid of losing data as long as XP boots, but installing GRUB or LILO does something to the MBR so XP can't boot, doesn't it? What can be done about that? This is one area where it seems to me that Fedora has fallen behind Debian based systems. There is a real lack of Fedora based live-CD's that you can install a system from. Cheers, Brian

2 1

udev-event tty error messages at FC 5 test 3 boot.
by Brian Durant 25 Feb '06

25 Feb '06

Hi again, I am getting a large number of udev-event error messages (some containing "tty...") at FC 5 test 3 boot. Unfortunately, I can't seem to find the log that should contain these errors. Anyone have any ideas? Should I just post this as a bug? I don't have much info on it. Cheers, Brian

1 0

Weird error in tla package
by Josh Boyer 24 Feb '06

24 Feb '06

I'm getting a weird error when trying to build the tla package from Extras on PPC. I haven't done too much digging yet, but I thought I would ask in case the symptoms ring a bell for some reason. Basically, it fails with this: ================ unit-ar tests ================ /home/jwboyer/rpm/BUILD/tla-1.3.3/src/hackerlab/tests/arrays-tests/unit-ar.c:53:botched invariant 0 == ((unsigned long)ar & (16 - 1)) PANIC: exiting on botched invariant What is weird is where that '16' comes from. It's coming from a #define called MACHINE_ALIGNMENT which seems to be a computed value of some kind. On my x86 box, it's #defined to 4. When building on PPC, it's #defined to 16. If the macro really does what it says it does, then I have to go figure out why the test is failing. And it doesn't help that this code makes my head hurt. But is the alignment on a PPC box really 16 bytes? josh

2 3

List rejects my e-mail.
by Brian Durant 24 Feb '06

24 Feb '06

I am starting to have the same problem as others have also experienced on the list earlier. One of my e-mails was rejected by the list because of "suspicious" headers. All I did was access my account with webmail. Anyone remember who the listmom is, so that I can make sure the e-mail arrives on list? I am in the middle of trying to suss out my FC5 PPC test 3 install problems and something like this isn't exactly conducive... Cheers, Brian

2 1

[Re: Re: Newbie FC 5 test 3 PPC help and first impressions.]
by Brian Durant 24 Feb '06

24 Feb '06

-------- Original Message -------- X-Auth-OK: RoadTripDK X-NIMS-Flags: 1 Return-Path: <RoadTripDK(a)myrealbox.com> Received: from RoadTripDK [80.163.36.206] by myrealbox.com with NetMail ModWeb Module; Fri, 24 Feb 2006 07:12:28 +0100 Subject: Re: Re: Newbie FC 5 test 3 PPC help and first impressions. X-Mozilla-Status: 0200 From: Brian Durant <RoadTripDK(a)myrealbox.com> To: bdc(a)carlstrom.com CC: fedora-ppc(a)lists.infradead.org Date: Fri, 24 Feb 2006 07:12:28 +0100 X-Mailer: NetMail ModWeb Module X-Sender: RoadTripDK MIME-Version: 1.0 Message-ID: <1140761548.c7f07fbcRoadTripDK(a)myrealbox.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable -----Original Message----- From: "Brian D. Carlstrom" <bdc(a)carlstrom.com> To: RoadTripDK(a)MyRealBox.com Date: Thu, 23 Feb 2006 18:59:18 -0800 Subject: Re: Newbie FC 5 test 3 PPC help and first impressions. Brian Durant writes: > When I am getting errors at boot, which logs contain the errors, where > are the logs located and how can I tell if the errors are serious and > what to do about them? /var/log/dmesg has kernel output /var/log/messages has the syslog output, including a dump of dmseg after boot I don't know where the [ OK ] and [ FAILED ] messages go, if anywhere. -bri OK, I got my USB stick thingy to mount. The problem was syntax. I had written "users.noauto" instead of "users,noauto" Here is some output from the terminal: "]$ dmesg | tail Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.7 hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. SELinux: initialized (dev sdb3, type hfsplus), not configured for labeling hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. SELinux: initialized (dev sdb3, type hfsplus), not configured for labeling SELinux: initialized (dev autofs, type autofs), uses genfs_contexts eth0: no IPv6 routers present SELinux: initialized (dev sdc1, type vfat), uses genfs_contexts" "sata_svw 0001:02:0c.0: version 1.07 ata1: SATA max UDMA/133 cmd 0xD00008008225C000 ctl 0xD00008008225C020 bmdma 0xD00008008225C030 irq 10 ata2: SATA max UDMA/133 cmd 0xD00008008225C100 ctl 0xD00008008225C120 bmdma 0xD00008008225C130 irq 10 ata3: SATA max UDMA/133 cmd 0xD00008008225C200 ctl 0xD00008008225C220 bmdma 0xD00008008225C230 irq 10 ata4: SATA max UDMA/133 cmd 0xD00008008225C300 ctl 0xD00008008225C320 bmdma 0xD00008008225C330 irq 10 ata1: SATA link up 1.5 Gbps (SStatus 113) ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:007f ata1: dev 0 ATA-6, max UDMA/133, 156301488 sectors: LBA48 ata1: dev 0 configured for UDMA/133 scsi0 : sata_svw ata2: SATA link up 1.5 Gbps (SStatus 113) ata2: dev 0 cfg 49:2f00 82:7c69 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:007f ata2: dev 0 ATA-7, max UDMA/133, 320173056 sectors: LBA48 ata2: dev 0 configured for UDMA/133 scsi1 : sata_svw windfarm: SMU failed new fan command falling back to old method ata3: SATA link down (SStatus 0)" "SELinux: initialized (dev sdb3, type hfsplus), not configured for labeling audit(1140759646.506:3): avc: denied { mount } for pid=1569 comm="mount" name="/" dev=sdb3 ino=2 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. SELinux: initialized (dev sdb3, type hfsplus), not configured for labeling audit(1140759646.514:4): avc: denied { mount } for pid=1569 comm="mount" name="/" dev=sdb3 ino=2 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem audit(1140759646.518:5): avc: denied { relabelfrom } for pid=1569 comm="mount" name="blkid.tab" dev=sda3 ino=581017 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:etc_runtime_t:s0 tclass=file audit(1140759647.074:6): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.074:7): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.074:8): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.074:9): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:10): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:11): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:12): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:13): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:14): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:15): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:16): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:17): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:18): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:19): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:20): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:21): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.078:22): avc: denied { search } for pid=1611 comm="pam_console_app" name="lib64" dev=sda3 ino=161281 scontext=system_u:system_r:pam_console_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir audit(1140759647.838:23): avc: denied { relabelfrom } for pid=1624 comm="swapon" name="blkid.tab" dev=sda3 ino=582278 scontext=system_u:system_r:fsadm_t:s0 tcontext=system_u:object_r:etc_runtime_t:s0 tclass=file Adding 2953116k swap on /dev/sda4. Priority:-1 extents:1 across:2953116k SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts hvc_console: tty open failed, no vty associated with tty." I didn't copy the whole dmesg, but picked out some of the interesting bits. I don't want to overload with info as I am not sure what to look for. I hope someone gets something out of this. BTW, it seems like Firewire isn't working properly. Hardware browser doesn't seem to pick up my external Firewire drive. I haven't created any mount points, but then I can't do that before I know where the drive is located on the system. Cheers, Brian

1 0

Newbie USB thumb drive problem in FC5-PPC test 3.
by Brian Durant 23 Feb '06

23 Feb '06

I am trying to mount my USB thumb drive. Here is my fstab: LABEL=/1 / ext3 defaults 1 1 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 LABEL=/home1 /home ext3 defaults 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 LABEL=SWAP-sda4 swap swap defaults 0 0 /dev/sdc1 /mnt/usbdrive auto defaults,users.noauto 0 0 I have created "/mnt/usbdrive" and "/dev/sdc" is listed in system -> administration -> hardware. The drive is listed as "fat16" I have also tried in the terminal: $ sudo mount fat /dev/sdc mount: you must specify the filesystem type $ sudo mount fat16 /dev/sdc mount: you must specify the filesystem type I have tried to mount my HFS+ partition on my second SATA drive with the same result, when I used "hfsplus" as fs type. Anyone have any ideas? Cheers, Brian

2 5

Re: Newbie FC 5 test 3 PPC help and first impressions.
by Brian Durant 23 Feb '06

23 Feb '06

On Thu, 2006-02-23 at 13:08 +0000, David Woodhouse wrote: > On Thu, 2006-02-23 at 14:03 +0100, Brian Durant wrote: > > That would be nice as I got some errors when I ran "yum update", but > > until I figure out how to share a Thunderbird profile between Rawhide > > and OS X, I have to transfer the text files with the error messages > > between the two systems by using my USB stick. > > Linux can read and write OSX hfs+ volumes. I don't see why the > Thunderbird profile shouldn't be fairly portable -- if you really need > to _share_ it rather than just using the same config in both places, > then you might be able to make it work if your userid is the same on > both OSX and Linux. OK, I just did a quick and dirty setup to get this sent off to you and the list, by setting up Evolution. Here are the error messages that I got when I did a "yum update": Stopping sshd: [ OK ] Starting sshd: [ OK ] Updating : glibc [ 8/216]warning: /etc/ld.so.conf created as /etc/ld.so.conf.rpmnew Updating : glibc [ 8/216]warning: /etc/nsswitch.conf created as /etc/nsswitch.conf.rpmnew /var/tmp/rpm-tmp.14062: line 8: cd: /usr/lib64/firefox-1.5.0.1/extensions: No such file or directory unzip: cannot find or open /usr/lib64/beagle/beagle.xpi, /usr/lib64/beagle/beagle.xpi.zip or /usr/lib64/beagle/beagle.xpi.ZIP. grep: beagle-extension/install.rdf: No such file or directory mv: target `' is not a directory: No such file or directory error: %trigger(beagle-0.2.1-11.ppc) scriptlet failed, exit status 1 warning: /etc/libuser.conf created as /etc/libuser.conf.rpmnew warning: /etc/vimrc created as /etc/vimrc.rpmnew I am also getting quite a number of errors at boot, after doing the "yum update" command, but the system seems to still be running OK. I could send those as well, but I don't know which log files I need to copy or whether I can send them as attachments. Cheers, Brian

1 0

Re: Newbie FC 5 test 3 PPC help and first impressions.
by Brian Durant 23 Feb '06

23 Feb '06

David Woodhouse wrote: > On Thu, 2006-02-23 at 14:03 +0100, Brian Durant wrote: > >>That would be nice as I got some errors when I ran "yum update", but >>until I figure out how to share a Thunderbird profile between Rawhide >>and OS X, I have to transfer the text files with the error messages >>between the two systems by using my USB stick. > > > Linux can read and write OSX hfs+ volumes. I don't see why the > Thunderbird profile shouldn't be fairly portable -- if you really need > to _share_ it rather than just using the same config in both places, > then you might be able to make it work if your userid is the same on > both OSX and Linux. There should be a way of directing Thunderbird to the profile on the hfs+ partition (HD), but I don't see those instructions on Mozilla.org any more. They used to work with the old Moz monolithic app, but I have only seen references when googling about Firefox/Thunderbird being quite finiky when this is attempted. In principle two seperate profiles should be possible, as long as the mbox files are shared. That would avoid an overwriting of the extension preferences between OS's, just in case the same pref files aren't an exact match between platforms... Cheers, Brian

2 3

Newbie FC 5 test 3 PPC help and first impressions.
by Brian Durant 23 Feb '06

23 Feb '06

Hi again, WOW! I just installed Rawhide PPC Test 3 and my eyeballs almost popped out. Thermal control works for my PowerMac 9.1 (G5 tower single), yaboot configures correctly and I love the new default theme in GNOME. But what is with those bubbles in the install splash screen, GDM and as the default desktop background??? Is Fedora in trouble? Are we on the Titanic, or what ? ;-) It would be nice if the first user was automatically included to "sudoers", but I am really having to reach, to find something to complain about :-) Anyway, I have a couple of issues that I need to deal with now: 1) I can't get my USB stick thingy to pop-up on the desktop or in the "Computer" window. 2) FC only spots my Griffin iMic and not the stock sound card. Here is what my system profiler says: Built In Sound Card: Devices: Burr Brown PCM3052: Inputs and Outputs: Line Level Input: Controls: Mute, Master Playthrough: No PluginID: Onyx Headphones: Controls: Mute, Left, Right PluginID: Onyx Internal Speakers: Controls: Mute, Master PluginID: Onyx Line Level Output: Controls: Mute, Left, Right PluginID: Onyx Crystal Semiconductor CS84xx: Inputs and Outputs: S/PDIF Digital Output: Controls: Mute PluginID: Topaz Formats: PCM 16: Bit Depth: 16 Bit Width: 16 Channels: 2 Mixable: Yes Sample Rates: 32 KHz, 44.1 KHz, 48 KHz, 64 KHz, 88.2 KHz, 96 KHz PCM 24: Bit Depth: 24 Bit Width: 32 Channels: 2 Mixable: Yes Sample Rates: 32 KHz, 44.1 KHz, 48 KHz, 64 KHz, 88.2 KHz, 96 KHz AC3 16: Bit Depth: 16 Bit Width: 16 Channels: 2 Mixable: No Sample Rates: 32 KHz, 44.1 KHz, 48 KHz, 64 KHz, 88.2 KHz, 96 KHz Built In Sound Card: Devices: Crystal Semiconductor CS84xx: Inputs and Outputs: S/PDIF Digital Input: Controls: Mute Playthrough: No PluginID: Topaz Formats: PCM 16: Bit Depth: 16 Bit Width: 16 Channels: 2 Mixable: Yes Sample Rates: 32 KHz, 44.1 KHz, 48 KHz, 64 KHz, 88.2 KHz, 96 KHz PCM 24: Bit Depth: 24 Bit Width: 32 Channels: 2 Mixable: Yes Sample Rates: 32 KHz, 44.1 KHz, 48 KHz, 64 KHz, 88.2 KHz, 96 KHz AC3 16: Bit Depth: 16 Bit Width: 16 Channels: 2 Mixable: No Sample Rates: 32 KHz, 44.1 KHz, 48 KHz, 64 KHz, 88.2 KHz, 96 KHz Cheers, Brian

2 2

fc4 + Broadcom BCM43xx wireless support?
by Robert Story 23 Feb '06

23 Feb '06

I saw a message on wireless support via a rawhide kernel on (what I assume to be) stock fc4. [http://www.redhat.com/archives/fedora-test-list/2005-December/msg00820.html] However, that is a 2.6.14 kernel. Is there a patch, instead of having to grab a binary? Does it apply against newer rawhide kernels? Any chance of a patch against a fc4 kernel? Anyone running a rawhide kernel on an otherwise stock fc4 machine?

2 1

Airport Card Problems
by Ron Patterson 21 Feb '06

21 Feb '06

I can't get my airport card working on my bronze powerbook. I am running a Netgear WGR-614 with open security. The airport card works fine under Panther. The card is being detected and the drivers are installed. Here is the output from dmesg. orinoco 0.15rc3 (David Gibson <hermes(a)gibson.dropbear.id.au>, Pavel Roskin <proski(a)gnu.org>, et al) airport 0.15rc3 (Benjamin Herrenschmidt <benh(a)kernel.crashing.org>) airport: Physical address 80030000 eth1: Hardware identity 0005:0001:0001:0000 eth1: Station identity 001f:0001:0008:0046 eth1: Firmware determined as Lucent/Agere 8.70 eth1: Ad-hoc demo mode supported eth1: IEEE standard IBSS ad-hoc mode supported eth1: WEP supported, 104-bit key eth1: MAC address 00:30:65:08:0C:EA eth1: Station name "HERMES I" eth1: ready airport: Card registered for interface eth1 And the output from lsmod. airport 8096 0 orinoco 49108 1 airport hermes 8992 2 airport,orinoco Here is the output from iwconfig. I have put the card in managed mode and set the essid. I have even forced the router to use channel 3 2422 mhz with no results. eth1 IEEE 802.11b ESSID:"TREES" Nickname:"localhost.localdomain" Mode:Managed Frequency:2.422 GHz Access Point: 44:44:44:44:44:44 Bit Rate:11 Mb/s Sensitivity:1/3 Retry limit:4 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=0/92 Signal level=134/153 Noise level=134/153 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Does anyone have an original airport card working under Fedora Core 4? Any help would be appreciated. Ron

2 1

[Fwd: FUDCon Boston 2006 Call for Papers]
by Jack Aboutboul 16 Feb '06

16 Feb '06

This was sent out last week, but for some reason didn't make it to some of the lists.

1 0

FUDCon Boston 2006 Call for Papers
by Jack Aboutboul 10 Feb '06

10 Feb '06

**Please pass this around to anyone who might find this relevant** FUDCon Boston 2006 Call For Papers I would like to start out by thanking both the community and developers who have helped make Fedora such a huge success on so many different fronts. Riding on the success of the series of FUDCon events worldwide I am proud to announce that we will be holding FUDCon Boston 2006, taking it back to where it all began. The event will be graciously hosted by Boston University once again with sponsorship from BU Department of Electrical and Computer Engineering, the BU Office of Information Technology, and this year, the BU School of Management. The date for the event is Friday April 7th, the day following the LinuxWorld Conference and Expo. We are looking for interesting topics and presentations covering a number areas. Talks should be focused on one of the 3 main tracks. Track 1 - User Track : Topics that deal with the user experience, desktop innovations, etc. Track 2 - Developer Track : Topics that deal with software development in the Fedora environment. Track 3 - Application Track : Either topics that deal with applications/uses of Fedora in other Open Source projects or topics that showcase a specific Open Source application. To be considered for presentation, abstracts should be submitted fudcon-cfp(a)fedoraproject.org by no later than Thursday February 23, at 11:59pm. We welcome submission from both developers and community members alike, new and old. After the review process, notifications will go out on Thursday March 2nd followed by a full schedule for FUDCon Boston 2006 and official announcement on Monday March 6th. Thanks.

1 0

Fedora and iMac G5
by Zoltan Kota 07 Feb '06

07 Feb '06

Hi, I have installed FC4 on an iMac G5 (17" screen) machine. I'm really happy that it is usable (with some restrictions). I'm trying to follow the updates and improvements. Still, there are some issues to be fixed/improved however. Is there any progress regarding the snd-powermac problem? The latest kernel update (2.6.15-1.1830_FC4) doesn't help on this problem. But the fans seemed to stop to buzz so loud with these updates. Is there/will be any chance to use the screen with a resolution higher than 1024x768? Under MacOSX the normal resolution is 1440x900. Zoltan

1 0

突乳！Ｈなおねぇさんｗｗ 29
by info＠uranuslove.info 06 Feb '06

06 Feb '06

$B!!(B_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B $B!!FM(-F}(-!*(-#H(-$J(-$*(-$M(-$'(-$5(-$s(-(B $B!!(,(0(,(0(,(0(,(0(,(0(,(0(,(0(,(0(,(0(,(0(B $B!!(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/* $B!|KE9-9pBeM}E9$K6P$a$k<+>N%+%j%9%^1D6H%^%s!X#0;a!Y$,(B $B7+$j9-$2$k>W7b$N<rCSFyNSNx0&3(4,%l%]!<%H(B!! $B$G$-$k$@$199?7$7$F%3%C%A4X78$N(B $B1D6HJs9p=qBe$o$j$K8x3+$7$F$$$/$D$b$j$J%V%m%0(B!! $B!X2G$K$_$D$+$i$J$$$h$&$K!#!#!#(B $B$_$D$+$C$?$i;&$5$l$A$c$&$s$@$m$&$J!!26#w#w!Y(B $B(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(B $B!y!z!y!!(Bhttp://uranuslove.info/wty/$B!!!y!z!y(B $B(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(B $B"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#(B --------------------------------------------- $B$*CN$i$;%a!<%k<u?.5qH]$N>l9g$O2<5-%"%I%l%9$K$4JV?.$/$@$5$$!#(B info999(a)ok.kz --------------------------------------------->

1 0

Re: Newbie with Power Mac G5.
by Brian Durant 05 Feb '06

05 Feb '06

On 3. feb 2006, at 15.26, David Woodhouse wrote: > On Fri, 2006-02-03 at 15:23 +0100, Brian Durant wrote: >> Sorry, I am a little confused. The .iso files are labeled "fc4- >> pegasos-disc..." Can they be installed on my configuration >> successfully? > > They're updated FC4 install images. They should work on anything other > than the new dual-core Power Macs, I believe. > > -- > dwmw2 OK, time to make a status report: 1) The install seemed to go without a hitch. 2) I have 2 internal SATA drives and Fedora Core 4 Pegasos (PPC) is installed on #1. 3) First boot went fine in the beginning: a) When it was time to include extra install CDs, the system could not find a CD-ROM. b) Created user account and password. c) At prompt screen for loging into the system, I got a blinking cursor, but the mouse and keyboard were frozen. I had to do a hard shutdown as the keyboard was frozen. d) I still seem to have fan and thermal control problems. 4) Tried to boot into OS X at restart, but Fedora didn't setup OpenFirmware properly and I couldn't boot into OS X. I had to restart with the option key pressed down to call up the OF graphical interface for choosing which drive to boot from. Where do I go from here? Do I give up on my FC4 install and try a Rawhide install or do I try to fix the issues with Fedora Core 4? Cheers, Brian

3 17

Ich liebe Dich !!!
by root 03 Feb '06

03 Feb '06

Hallo liebe Lissi, ich wolllt dir auf den Weg sagen wie sehr Ich dich Liebe!!! Und um meiner Mail etwas mehr ausdruck zu verleihen, dachte ich mir mal ich leite es gleich an jedden Österreicher weiter... ICH LIEBE DICH !!! LG Andreas Please Note: A Hacker loves U so hack me if you can http://hackerz.da.cx

1 0

Re: Newbie with Fedora Core 4 PPC on Power Mac G5.
by Brian Durant 03 Feb '06

03 Feb '06

On 28. jan 2006, at 19.24, Brian D. Carlstrom wrote: > Brian Durant writes: >> 3) The fans on the G5 are revving excessively. I assume this is a >> problem with the "windfarm" module? > > Have you done a "yum update" to get the latest software and rebooted > with the newly installed kernel? For me the original FC4 did not > support > my PowerMac7,3 but the updated one did. However, I don't think this > will > work in your case, but updating to an updates-testing kernel might, > if I > recall my earlier email, the 2.6.15 kernel available there had the > PowerMac9,1 code. once you update everything else, you can try a "yum > --enable-depot=updates-testing kernel*" or something like that to get > the newer kernel. Be careful not to install a ppc (versus ppc64) > kernel > or you won't be able to boot. Sorry, I keep changing things around, but I am really getting frustrated about not being able to get anything to work with any of the distros. They all are acting worse than beta ware on my machine. In my opinion, none of them should have been released before the issues were sorted out. It doesn't make a good impression for total newbies. Fortunately, I have had some experience with Linux, so I know sometimes you need patience, but I still try to follow the ath of least resistance and deal with the distro that is least bad :-) Since my posting,I have gone back to YDL 4.0.1 as it seems to work best on my machine of all of the distros I have tried. Even though I have a thing for .deb based distros, I am basically a pragmatist at heart and since YDL works best for me, that is where I will concentrate my effort on getting things sorted out. Maybe I can be convinced to love an .rpm based system as well. Who knows? Time will tell. Hopefully since it has Fedora Core as its base, this won't be considered off topic for the list. Except for installing Danish language support, my YDL install is a default desktop install. Here are some pretty fundamental issues that I can't seem to get around: 1) I can start a root session, but YDL doesn't recognize the root password when I try to do a command like: $ su tail -f /var/log/messages [ENTER] $ sudo tail -f /var/log/messages [ENTER] $ root tail -f /var/log/messages [ENTER] (This is when I am in a normal user session) 2) "yum check-update" returns something about some file missing in / var/.... >> 1) At the log in, the cursor blinks in the "username" field, but >> neither my Apple wireless keyboard nor my Apple USB keyboard seem to >> work. The mouse (Apple Mighty Mouse) seems to freeze also. I end up >> having to do a hard shutdown by pressing the poser button. > > I have only used the regular wired mouse and keyboards. In addition to > the ones that Apple shipped with the machine, on one machine we have a > Microsoft wired optical mouse and that works fine. We general use the > USB connector on the back of the monitor but we have also used the > front > and back USB connectors without problem. > >> 2) Yaboot can't boot into OS X. > > There has been a new yaboot since the initial release as well, > though I > have no idea if its related to this problem you are having. I've never > created a dual boot configuration so I'm not helpful there. Also, make > sure you run /sbin/ybwin whenever you change your /etc/yaboot.conf so > that it will take effect. Are there settings in yaboot.conf for dual > boot support? > > $ yum provides /sbin/ybin > Searching Packages: > Setting up repositories > Reading repository metadata in from local files > > > yaboot.ppc 1.3.12-9 > base > Matched from: > /sbin/ybin > > > yaboot.ppc 1.3.12-10 > updates-released > Matched from: > /sbin/ybin > > > yaboot.ppc 1.3.12-10 > installed > Matched from: > /sbin/ybin > $ > > Finally, YDL 4.1 is supposed to be out relatively soon...:) Yes, I have been thinking about that as well, but to tell you the truth, I would like to get a boxed version shipped. I would like to have a manual in my hand to refer to when I am puzzling over a solution. I like to relax in a sofa and study the matter before I go back to my desk :-) I'll have to see if Terrasoft can handle a shipment to Denmark. They have a partner in Germany, but as I don't read German... For now, I am going to concentrate on getting 4.0.1 to work and then see where I go from there :-) Cheers, Brian

5 20

Re: Newbie with Power Mac G5.
by Brian Durant 03 Feb '06

03 Feb '06

On 22. jan 2006, at 0.49, Brian D. Carlstrom wrote: > Brian Durant writes: >> If the above works more or less as described, would there be any >> problems with the OpenFirmware and yaboot if I installed Linux with >> the OS X drive unplugged, just in case - up in space? > > with linux on drive "b" with the "a" drive unplugged? the only > concern I > would have is that it might make the /etc/fstab mount tab assuming > that > since its the only drive that its the "a" drive. Then again, it should > know what drive it is from the controller. I don't think you'll break > anything, and at worst I can imagine that you could just boot and fix > the /etc/fstab after the fact. > > -bri Hmm. Interesting, but short lived experience. I booted into the Fedora Core 4 PPC install CD, verified the disk and went to the start of the install procedure. When I got to choosing the keyboard, I got the following error message: "The partition's data region doesn't occupy the entire partition." Then: "Attempt to read sectors 16-18 outside of partition on /dev/sdb" Then: "The partition's data region doesn't occupy the entire partition." Then: "Attempt to read sectors 16-18 outside of partition on /dev/sdc" I kept pressing "ignore" and then finally got to the partitioning issue. The only choice that looked safe was to try a manual partition as you are not allowed to choose which drive to automatically partition (!!!!???). I started to add partitions to "sdb" which is the drive I want to install Linux on, but then all of a sudden the kernel bonked out and the system did an emergency exit. I tried once again on a reboot. This time, all of the places where choices are made "back", "next" or "select" something were all flashing in rotation. I got as far as the partition dialog, again with the same errors, but I didn't dare to go any further, as it was unclear as to what drives were going to get partitioned :-( (I should mention that this is the same in YDL.) Very unfortunate interface on this issue. Cheers, Brian

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

ppc February 2006