x86 64-bit | Forum profile

Quote: Originally Posted by slopoke_iii on boot i can get to grub boot loader where i choose the last kernel and that is as far as i can get unless i choose to edit grub there. I don't know how to get to a terminal from grub without booting the kernel and it locks up before i get there. Ok just add a 3 to the end ( it's only a temp edit ) Code: Kernel /vmlinuz-2.6.31.6-166.fc12.x86 ro root=/1dev/mapper/vg_ricky...

Are your fans operational? It sounds like emergency shutdown from BIOS due to overheating CPU.

Apparently, the 127 kernel does not work for me because the update to 162 is what enabled the UUID references after the USB devices were enumerated. So maybe it's time to upgrade -- nybigjet -- does the 127 kernel still work for you? ---------- Post added at 12:01 PM CST ---------- Previous post was at 06:34 AM CST ---------- Well, upgrade to 166 kernel is completed and quite successfully, and the USB Linux partitions mount (the ntfs...

Leigh i finally got a to a terminal and did the install for nouveau . it wouldn't let me do the mv of the 2 files oir the remove of xorg.conf. but i was able to edit the grub.conf. so i am now back to where it boots again and it loads the nouveau driver and i have video. i don't understand why tho the nvidia driver didn't work . I had then install on FC11 and working fine. should i try the pae kernel version to try and get it...

NO NO Panoz: I had the same problem. the 127 will mount itself as sda1 (or sdb1 or sdc1 etc.) when it physically resides in higher partitions; this is a virtual mount, it makes no difference what's in the actual partition. Yes my 127 still runs, however, it's no longer needed. Now using the 166. We had the same error messages, the same boot problems, and they probably stemmed from the same kernel changes. Let me try to explain this...

Dear UPGrouseman, Hello there! In my nickel's worth of opinion, i always feel a clean install is the best way to go! I bought a DVD-RW, and downloaded the .ISO image to the HDD and burnt it using Nero onto this dvd-rw. Your point of backing up personal data is well taken. Kindly view this thread in this website where a folk with a similar prob. as yours posted and it was "resolved". Best wishes!...

Quote: Originally Posted by CSchwangler Did you already try this method: http://www.my-guides.net/en/content/..._firefox_flash or alternatively http://www.mjmwired.net/resources/mj...f12.html#flash Hi CSchwangler, I solved my problem running; # rpm -Uvh /home/satimis/flash-plugin-10.0.42.34-1.x86_64.rpm to install flash-plugin. It is working now. B.R. satimis

I'm quite sure that the update causes the problem as I put a fix in the new code, recompiled a new rpm and installed it. The SEGFAULT did not reappear. Concerning your links, they should have followed the new file as mine did. When you renamed the old file the two links should have showed up as broken. Then when you put in the new file they should link up to it automatically. I can't say why yours didn't. In any case if...

thank you CSchwangler, will check it out & report back later.

Sounds like a DNS problem to me, since yum, afaik, uses IP addresses to connect to mirrors. There is a setting in Firefox you might try to change: about :config -> network.dns.disableIPv6 You might also try to add nameserver to /etc/resolv.conf.