On Mon, 2008-01-07 at 11:07 -0800, Les wrote: > Hi, everyone, > I am attempting to move my whole network to F8... Yes, I know that > something stable might be better, so lets skip those comments, OK? > > My current issue is with an HP Pavillion a8010n AMD K8 system with > Silicon Integrated Systems video on board, 1G of memory. It all seems > to work fine until (while following Finley's configuration site), I > install mplayer and mplayer codecs. At that point, when I bring up > video on the suggested bbc website, the system hangs. No error > messages, no control whatever, function keys will not return control, > and I have to power down to reboot. At this time I am running the > memory test on the system just to eliminate that possibility. Following > the pulse audio on going debate, I haven't seen anyone quite mentioning > the issue I am seeing. After this memory test runs, I will see if I can > see the error logs using chroot with the rescue mode of the F8 DVD. Any > suggestions on how to proceed will be gratefully accepted and followed. > > Regards, > Les H I know it is bad form to reply to your own request, but... I had the following issue as well, that the HP system overwrote grub, and apparently trashed something else on the disk where I had grub, slicking the F8 install in a way that caused errant but not strictly repeatable behavior. Also I did have some memory hits. I replaced the memory, reloaded F8 and reconfigured it to run windows as a second boot alternative (wife is going to school and needs windows access to keep it simple). And again the HP boot thingy killed it, so one more reload, and this time I took off the HP drive. I also turned off the boot check in the bios. That got it booting, and then I still seemed to have memory clobbering going on. No messages that I could find (for one thing, the system would totally lock up.) I just tried turning off the firewall (we have an external firewall on the network). No joy. Next I turned off SELinux by disabling it. JOY!! the system works. Why would disable be different from permissive (other than the background window telling you the errors?) In any event the system is not operational, but I do not like having SELinux disabled. I did try turning it on again, with debug enabled and got some messages about PAM that are not good. Now I wonder if having SELinux set to permissive, but without the window up is potentially the problem? Could SELinux be sending messages to a NULL window, causing X to have problems? I am not an X windows expert, but I have written some code using RPC calls and did have an occasion years ago where I wrote the transmission end first and had some issues on Solaris with no receiver installed to handle the calls, so that prompts my question. Regards, Les H
