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
On Sat, 2006-02-04 at 09:57 +0100, Brian Durant wrote:
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:
- The install seemed to go without a hitch.
- 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.
This functionality isn't really supported in Fedora - so don't panic. What "extra" cd were you trying? Just use yum post install.
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.
Do these work in runlevel 3? Can you also yum update to current errata and see if that improves (just to give us a base to test from).
I had to do a hard shutdown as the keyboard was frozen.d) I still seem to have fan and thermal control problems.
- 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.
I'm pretty sure this is a yaboot ofpath bug - I've an open bug for that can you let me know your partition layout of both disks, and your yaboot.conf, and a tarball of /proc/device-tree.
I'm hoping to get my hands on a setup with two drives shortly to fix this. If you have time I can run a few script modifications past you.
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?
Stick with FC 4 for now, lets get any outstanding issues that probably still occur in FC 5 (the yaboot thing, etc) fixed. Then we can see if the later kernel, etc fix things. Then we can move to FC5 T3 when releaseed to make sure we've polished everything for that.
Paul
On 4. feb 2006, at 16.26, Paul Nasrat wrote:
On Sat, 2006-02-04 at 09:57 +0100, Brian Durant wrote:
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:
- The install seemed to go without a hitch.
- 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.
This functionality isn't really supported in Fedora - so don't panic. What "extra" cd were you trying? Just use yum post install.
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.
Do these work in runlevel 3? Can you also yum update to current errata and see if that improves (just to give us a base to test from).
Runlevel 3? You mean getting a terminal? Everything freezes as soon as the graphical login appears. Not terminal, no nothing.
I had to do a hard shutdown as the keyboard was frozen.d) I still seem to have fan and thermal control problems.
- 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.
I'm pretty sure this is a yaboot ofpath bug - I've an open bug for that can you let me know your partition layout of both disks, and your yaboot.conf, and a tarball of /proc/device-tree.
I'll try, but to do this, I need to get logged in first. At this time I can tell you that I used the default option for formatting SATA-1 (sda) where the Fedora Core 4 install resides.
I'm hoping to get my hands on a setup with two drives shortly to fix this. If you have time I can run a few script modifications past you.
Sounds like a good idea.
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?
Stick with FC 4 for now, lets get any outstanding issues that probably still occur in FC 5 (the yaboot thing, etc) fixed. Then we can see if the later kernel, etc fix things. Then we can move to FC5 T3 when releaseed to make sure we've polished everything for that.
OK, sounds good. Thanks Paul.
Brian
On 4. feb 2006, at 16.26, Paul Nasrat wrote:
On Sat, 2006-02-04 at 09:57 +0100, Brian Durant wrote:
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:
- The install seemed to go without a hitch.
- 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.
This functionality isn't really supported in Fedora - so don't panic. What "extra" cd were you trying? Just use yum post install.
The CDs were #4 & #5 of the Fedora Core 4 Pegasos CDs.
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.
Do these work in runlevel 3? Can you also yum update to current errata and see if that improves (just to give us a base to test from).
I ran the command "linux runlevel 3". I tried "yum update logged in as a user, but it didn't work. Tried "sudo" but I am not listed in the "sudo" file and I didn't have the instructions printed out. I had to log in as root to run "yum update". There were 119 packages. At the end, I got a message that was something like:
"Warning rpmtsHrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2 Public key for net-toosl... Importing GPG key Is this OK? y/N"
All of a sudden the keyboard no longer functioned and yum (??) kept repeating something about that there had been no input and kept repeating something and then again complained about no input. I ended up have to do a hard shutdown as there was no keyboard response.
Then I restarted with "linux runlevel 3". In the middle of the boot up it changed to graphic mode and at graphic log in, there again was no keyboard response. After another hard shutdown, I rebooted and issued "linux runlevel 3". again. This time I logged in as root again and started a "yum update". Yum reported that 119 packages need to be downloaded and did I want to do that. I said "no" and then I got the same repeating message as above after "y/N" where there was the same message, but no complaint about no input. The keyboard input again froze up and that is where I am at this point.
Cheers,
Brian
Brian Durant writes:
This time I logged in as root again and started a "yum update".
I would run "yum -u update" so that it does not prompt you for the "y"/N response, since your keyboard seems to have problems in between these two steps.
I forget, are you using a standard Apple keyboard or was it wireless or ?
-bri
On 4. feb 2006, at 22.39, Brian D. Carlstrom wrote:
Brian D. Carlstrom writes:
I would run "yum -u update"
Sorry I meant "yum -y update"
-bri
OK, everything seemed to update OK, the new kernel got installed along with the other packages. No errors. There was some temporary scrambled text, but pressing an arrow key and everything got back to looking the way it should. Still having to do everything in root at this point. Everything finished and I got the normal blinking cursor next to a root@localhost and then all of a sudden I lost keyboard control. No keys worked at all and the following message kept repeating itself and scrolling:
"ata1: comman 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout"
I believe, but am not totally sure that this is the same message that I saw the other times that I lost keyboard control. I had to do another hard shutdown and then booted into OS X. I hope FC4 can handle these hard shutdowns :-(
Cheers,
Brian
Brian Durant writes:
"ata1: comman 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout"
Do you mean: ata1: command 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout Because others reported that here: http://ubuntuforums.org/archive/index.php/t-75145.html and here: http://ubuntuforums.org/archive/index.php/t-89712.html so you are not alone.
general google query http://www.google.com/search?hl=en&lr=&safe=off&c2coff=1&q=a... shows some FC4 responses as well.
unforuntately none of these seems to have a clear resolution.
does "uname -r" report kernel version 2.6.15-1.1830_FC4? this is the latest "updates" kernel.
-bri
On 5. feb 2006, at 0.57, Brian D. Carlstrom wrote:
Brian Durant writes:
"ata1: comman 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout"
Do you mean: ata1: command 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout Because others reported that here: http://ubuntuforums.org/archive/index.php/t-75145.html and here: http://ubuntuforums.org/archive/index.php/t-89712.html so you are not alone.
general google query http://www.google.com/search?hl=en&lr=&safe=off&c2coff=1&q=a... +command+timeout+stat+mpic_enable_irq+timeout shows some FC4 responses as well.
unforuntately none of these seems to have a clear resolution.
does "uname -r" report kernel version 2.6.15-1.1830_FC4? this is the latest "updates" kernel.
OK, here is a blow by blow report of what happened since your last e- mail:
1) I have now added myself as user to the /etc/sudoers list. 2) "uname -r" reports that the kernel version is 2.6.14-1.1637_FC4 3) The above kernel was the one that I booted with a "2.6.14-1.1637_F runlevel 3" command. 4) Everything seemed fine, except that I ran a "yum update" command and the #&@! yum program still wants to update the same programs (119) as have been updated before. 5) I exited as root with a "/sbin/shutdown -r now" and everyhting worked fine. No freezes, no nothing. It rebooted and I again booted with a "2.6.14-1.1637_F runlevel 3" command. 6) I logged in as "user" and since everything worked OK last time, I issued the command "startx". No problems there. Everything started fine and an up2date wizard popped up that I configured. No problems there. 7) I thought I was on a roll, so I brought up a terminal window to check on yum again. 8) As soon as I brought the terminal up, everything froze.
During the above process, my Bluetooth keyboard has been turned off AND the fans have been still running like crazy.
Cheers,
Brian
On 5. feb 2006, at 0.57, Brian D. Carlstrom wrote:
Brian Durant writes:
"ata1: comman 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout"
Do you mean: ata1: command 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout Because others reported that here: http://ubuntuforums.org/archive/index.php/t-75145.html and here: http://ubuntuforums.org/archive/index.php/t-89712.html so you are not alone.
Yup, that is the one, but I haven't seen it lately.
general google query http://www.google.com/search?hl=en&lr=&safe=off&c2coff=1&q=a... +command+timeout+stat+mpic_enable_irq+timeout shows some FC4 responses as well.
unforuntately none of these seems to have a clear resolution.
does "uname -r" report kernel version 2.6.15-1.1830_FC4? this is the latest "updates" kernel.
-bri
The latest news is that I did a "2.6.14-1.1637_F runlevel 3", user login and "startx". I got tired of the problem with yum, so I ran up2date. u2date found a newer kernel: 2.6.15-1.1830_FC4. I updated/ upgraded both the kernel, ALSA, yum and a number of drivers and programs. Everything went fine. I played around a little bit with Firefox, surfed the net, checked some of GNOME preferences, browsed through the file system, etc. In other words, normal stuff. No problems... until I decided to shutdown. So I chose "log out" from the GNOME panel/menu and everything froze. So here I am again, writing this e-mail in OS X :-(
Cheers,
Brian
On 5. feb 2006, at 0.57, Brian D. Carlstrom wrote:
does "uname -r" report kernel version 2.6.15-1.1830_FC4? this is the latest "updates" kernel.
The new kernel seems to be working (2.6.15-1.1830_FC4). as long as I do a "2.6.15-1.1830_F runlevel 3" at boot, I can login and then run "startx". I again updated the system running up2date, which had found a couple of networking libs. The thermal and fan control seem to be working. No problems with working in X as long as the sound is off, but as soon as I try to log out, the system freezes. I have also noticed that if I am working in the command line before running "startx", I have to be very careful when using the backspace key. If I go too far, I get the "ata1: command 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout" problem. The /etc/yaboot.conf seems to have been updated for the new linux kernels that were installed. I added a line "default=2.6.15-1.1830_F" in yaboot.conf, but at the OpenFirmware prompt at startup I can't just type in "runlevel 3" to make sure that the default kernel doesn't boot into X automatically as the system freezes when I get a normal graphic login.
Cheers,
Brian
Brian Durant writes:
On 5. feb 2006, at 0.57, Brian D. Carlstrom wrote:
does "uname -r" report kernel version 2.6.15-1.1830_FC4? this is the latest "updates" kernel.
The thermal and fan control seem to be working.
as expected in 2.6.15, although this is a major hurdle to be across in my opinion.
No problems with working in X as long as the sound is off,
again, video is another major hurdle. YDL 4.1 says it doesn't work for them: http://www.terrasoftsolutions.com/support/hardware/breakdown/index.php?hw_ca... I still have some G5 PowerMac's that won't work with their Apple monitors.
As far as sound goes, you did say you had an updated ALSA package, no luck with that?
but as soon as I try to log out, the system freezes. I have also noticed that if I am working in the command line before running "startx", I have to be very careful when using the backspace key. If I go too far, I get the "ata1: command 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout" problem.
well, this seems to be the major remaining hurdle. some people were saying that the sound was the problem, saying to disable artsd and esd:
http://www.suseforums.net/index.php?showtopic=19034 http://ubuntuforums.org/archive/index.php/t-89712.html
that seems to be a little suspect to be but who am I to say.
The /etc/yaboot.conf seems to have been updated for the new linux kernels that were installed. I added a line "default=2.6.15-1.1830_F" in yaboot.conf,n
I don't think that is necessary. In my experience, confirmed in the yaboot.conf man page, the first one in the file is the default, and that is where updates place new kernels.
but at the OpenFirmware prompt at startup I can't just type in "runlevel 3" to make sure that the default kernel doesn't boot into X automatically as the system freezes when I get a normal graphic login.
you can change the default runlevel in /etc/inittab from id:5:initdefault: to id:3:initdefault:
also, you might want to try using something like the "yumex" GUI instead of the "yum" command line since the problem seems terminal related somehow. of course, you'd have to use yum to install it. I would do "yum -y install yumex", perhaps from some "run command" GUI to avoid the terminal that seems to be plaguing you. I think up2date is going in FC5 if its not gone already.
-bri
On 5. feb 2006, at 18.43, Brian D. Carlstrom wrote:
Brian Durant writes:
On 5. feb 2006, at 0.57, Brian D. Carlstrom wrote:
does "uname -r" report kernel version 2.6.15-1.1830_FC4? this is the latest "updates" kernel.
The thermal and fan control seem to be working.
as expected in 2.6.15, although this is a major hurdle to be across in my opinion.
No problems with working in X as long as the sound is off,
again, video is another major hurdle. YDL 4.1 says it doesn't work for them: http://www.terrasoftsolutions.com/support/hardware/breakdown/ index.php?hw_cat_id=5 I still have some G5 PowerMac's that won't work with their Apple monitors.
I am using a Samsung SyncMaster 930 BF.
Resolution: 1280 x 1024 @ 75 Hz Depth: 16-bit Color Core Image: Supported Main Display: Yes Mirror: Off Online: Yes Quartz Extreme: Supported
GeForce FX 5200:
Chipset Model: GeForce FX 5200 Type: Display Bus: AGP Slot: AGP VRAM (Total): 64 MB Vendor: nVIDIA (0x10de) Device ID: 0x0321 Revision ID: 0x00b1 ROM Revision: 2060
As far as sound goes, you did say you had an updated ALSA package, no luck with that?
I haven't tried yet since I am still experiencing freezes, I wasn't sure what the cause was.
but as soon as I try to log out, the system freezes. I have also noticed that if I am working in the command line before running "startx", I have to be very careful when using the backspace key. If I go too far, I get the "ata1: command 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout" problem.
well, this seems to be the major remaining hurdle. some people were saying that the sound was the problem, saying to disable artsd and esd:
http://www.suseforums.net/index.php?showtopic=19034 http://ubuntuforums.org/archive/index.php/t-89712.htmlthat seems to be a little suspect to be but who am I to say.
The /etc/yaboot.conf seems to have been updated for the new linux kernels that were installed. I added a line "default=2.6.15-1.1830_F" in yaboot.conf,n
I don't think that is necessary. In my experience, confirmed in the yaboot.conf man page, the first one in the file is the default, and that is where updates place new kernels.
OK, I'll try to change it back.
but at the OpenFirmware prompt at startup I can't just type in "runlevel 3" to make sure that the default kernel doesn't boot into X automatically as the system freezes when I get a normal graphic login.
you can change the default runlevel in /etc/inittab from id:5:initdefault: to id:3:initdefault:
Sounds good, at least for now.
also, you might want to try using something like the "yumex" GUI instead of the "yum" command line since the problem seems terminal related somehow. of course, you'd have to use yum to install it. I would do "yum -y install yumex", perhaps from some "run command" GUI to avoid the terminal that seems to be plaguing you. I think up2date is going in FC5 if its not gone already.
yum works as long as I use it at runlevel 3 before I run "startx". It was just that it didn't seem to be updating properly. Is there some way to clear the yum cache and get it to reanalyze what the system needs??
Cheers,
Brian
yum works as long as I use it at runlevel 3 before I run "startx". It was just that it didn't seem to be updating properly. Is there some way to clear the yum cache and get it to reanalyze what the system needs??
earlier you were saying you were running "yum check-update" which just lists what "update" would do, I want to make sure you are running "yum update".
"yum clean all" will clean yums downloaded state of packages headersa and rpm files, but then you will have to redownload any packages it already grabbed. the man page has other options, but you might want to "yum clean all" at least once if you are worried, especially if you have a relatively fast connection.
however, I will say that "yum clean" doesn't remove any state about what the system needs, because I think yum just gets that information from the rpm system underneath.
were you getting an error running yum that would explain why it might seem to be starting over on every run?
-bri
On 5. feb 2006, at 19.41, Brian D. Carlstrom wrote:
yum works as long as I use it at runlevel 3 before I run "startx". It was just that it didn't seem to be updating properly. Is there some way to clear the yum cache and get it to reanalyze what the system needs??
earlier you were saying you were running "yum check-update" which just lists what "update" would do, I want to make sure you are running "yum update".
I ran both "yum check-update" and "yum list update", the one after the other, is what I said.
"yum clean all" will clean yums downloaded state of packages headersa and rpm files, but then you will have to redownload any packages it already grabbed. the man page has other options, but you might want to "yum clean all" at least once if you are worried, especially if you have a relatively fast connection.
however, I will say that "yum clean" doesn't remove any state about what the system needs, because I think yum just gets that information from the rpm system underneath.
were you getting an error running yum that would explain why it might seem to be starting over on every run?
No, there wasn't any error at all. BTW, last time I booted into FC4 in runlevel3, I issued the command "/sbin/shutdown -r now" , the problem with : " ata1: command 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout" started. Nothing with using the backspace key or anything.
Cheers,
Brian
Brian Durant writes:
yum works as long as I use it at runlevel 3 before I run "startx". It was just that it didn't seem to be updating properly.
I ran both "yum check-update" and "yum list update", the one after the other, is what I said.
Neither "check-update" or "list update" will actually update anything. You need to just use "yum update". I hope this is the only problem!
-bri
On 5. feb 2006, at 20.17, Brian D. Carlstrom wrote:
Brian Durant writes:
yum works as long as I use it at runlevel 3 before I run "startx". It was just that it didn't seem to be updating properly.
I ran both "yum check-update" and "yum list update", the one after the other, is what I said.
Neither "check-update" or "list update" will actually update anything. You need to just use "yum update". I hope this is the only problem!
-bri
I ran "yum clean all" and "yum update" and everything looks OK now. I think the only problems are:
1) The freezes. 2) The problem with " ata1: command 0x35 timeout, stat 0x50 host_stal 0x4 hda lost interrupt mpic_enable_irq timeout" 3) The sound issue.
Slowly, but surely we seem to be getting all of these things sorted out. I wouldn't have been able to do it without you. Many thanks for all of the help.
Brian
On 4. feb 2006, at 22.20, Brian D. Carlstrom wrote:
Brian Durant writes:
This time I logged in as root again and started a "yum update".
I would run "yum -u update" so that it does not prompt you for the "y"/N response, since your keyboard seems to have problems in between these two steps.
I forget, are you using a standard Apple keyboard or was it wireless or ?
I have both connected. Belt and suspenders, never can be too safe ;-)
On 4. feb 2006, at 22.39, Brian D. Carlstrom wrote:
Brian D. Carlstrom writes:
I would run "yum -u update"
Sorry I meant "yum -y update"
-bri
Yups.
Cheers,
Brian
-
Brian D. Carlstrom -
Brian Durant -
Paul Nasrat