Description of problem: When trying to install Fedora 14 x86_64 DVD on a macbook pro 7,1 the anaconda installer will start, but there will be absolutely no text. There are slightly visible buttons, which even still work when you click them, but it is impossible to navigate through the installer without text. Version-Release number of selected component (if applicable): Fedora 14 How reproducible: I'm guessing it is only reproducible on the macbook pro 7,1 (I have the 7,1 13.3'' version, but I don't think screen size matters so much) Steps to Reproduce: 1. Download and burn the fedora 14 x86_64 ISO to DVD 2. Put in Macbook Pro 7,1, boot to it (holding the "c" key at boot) 3. Select install Actual results: Anaconda starts up (slowly), but there is no text allowing for navigation through the screens. Expected results: Anaconda should have all the text displayed properly Additional info:
Can you attach a picture?
(In reply to comment #1) > Can you attach a picture? ummm...if you can tell me how I would get a screenshot saved while inside the fedora installation I could maybe? Or maybe the best I can do is taking a picture with a camera, is that what you mean? (bear in mind, if you do mean taking a screenshot I have no print screen button on my macbook, it's not a full keyboard.)
With a camera is fine. It's just hard to follow what graphical problems are without a picture as reference.
Created attachment 457280 [details] Image of the first screen as seen on my macbook pro 7,1 As you can see there is absolutely no text seen. What is not shown by the image is that the two buttons in the bottom right are (extremely faintly) shown.
Created attachment 457283 [details] Close-up of the first screen "next" button while being clicked I am clicking the button in the bottom right to make it visible to the camera.
Created attachment 457285 [details] Image of the second screen as seen on my macbook pro 7,1 As you can see, the next/previous buttons work, so I can move from screen to screen. Scroll bars can also be seen.
Can you get to the console (ctrl-alt-f2) and copy the /tmp/*log files and attach them to this bug? Especially the Xorg log.
I just gave copying the logs a try, but I couldn't mount a device to copy them to. How can I mount my flash drive? it's a fat32 type, and I figured out which device it was by checking what was/wasn't in the /dev/ folder when it was/wasn't plugged in (sdc and sdc1 are what appeared in the list when it was plugged in). So I tried this command: mount /dev/sdc/ /mnt/ It told me I needed to specify the file system type, so I did this command: mount -t fat32 /dev/sdc/ /mnt/ It then told me it didn't recognize the file type "fat32" I didn't try out sdc1, maybe I should have. how do I mount my flash drive so that I can copy the log files to it?
nevermind, I got it. I did have to use sdc1 and not sdc, and I had to create a new folder to mount it into, didn't need "-t [file system type]" at all.
Created attachment 457314 [details] Log file for anaconda
Created attachment 457315 [details] program.log
Created attachment 457316 [details] storage.log
Created attachment 457317 [details] syslog
Created attachment 457318 [details] X.log
There are a variety of nouveau warnings in your syslog, so let's start with that component. This is unlikely to be an anaconda bug given the nature of the problem and the fact that only you are seeing it (so far).
@Chris Lumens: Umm...so you said "let's start with that component,"...and I'm not sure if that means you're asking me to do something? If so, what exactly?
This looks like a dup of 635026, but that issue should be fixed as of xorg-x11-drv-nouveau-0.0.16-12.20100920gitf1ac413. I'd be surprised if that version wasn't in the install image.. What do you see from "rpm -q xorg-x11-drv-nouveau" ?
it says "package xorg-x11-drv-nouveau is not installed"
Also, I just tested out the "Install system with basic video driver" option, and that one displays correctly. Don't know if that means anything for this bug or not :/
Oh wait lol, I wasn't paying too much attention when I sent back that response...There's supposed to be a xorg-x11-drv-nouveau package shipped with this DVD and there isn't and that's the only problem, right?
Odd, the driver's definitely there, your X log proves that :) Perhaps the installation image doesn't have an RPM database on it so it doesn't know. In any case, my suggestion is to proceed with the install in basic video mode, run yum update to ensure you have all the latest packages, then remove any "nomodeset" or "xdriver=vesa" options from your /boot/grub/grub.conf, and remove any /etc/X11/xorg.conf completely.
Alright, thanks :)
Okay, so I tried installing with the basic video driver, but upon reboot the first thing I noticed was that rEFIt was now giving me TWO linux options instead of the single option I got from using Ubuntu. I tried both of them and it gave me a message: "no bootable device --insert boot disk and press any key" Then I remembered that updating the partitioning tool in rEFIt would be a good idea, so I did that, but both rEFIt linux options gave me a new message: "error: unknown filesystem grub rescue> " (btw the "grub rescue>" IS a prompt at which you can type.) Post note: I took your "yum update, remove 'nomodeset', etc." stuff to be things you wanted me to do AFTER I installed? because "yum update" command wasn't found in the installer, nor is there any /boot directory. I'm sure you meant post-install, but I just want to be sure. Any ideas about that?
Well, I just downloaded the 64-bit Live CD version of Fedora 14, and it's giving me a very similar bug, so I'm going to guess that it would be solved with the same fix once this one is fixed. What it did was boot up, auto-login, and then the desktop icons were not visible and the GNOME menus did not have text or images either. Just a blank white bar across the top and bottom of the screen with the background image. I'm going to try the 32-bit version to see if the problem is isolated to 64-bit.
nope, same problem with 32-bit...
I also have a MBP 13 inch 7,1 and am experiencing the same problem with the Fedora 14 x64 installer (haven't tried 32 bit) It is possible to bypass this by disabling nouveau during the installation: - In the boot menu press <tab> to edit the first line (Install a new system or...) - Add "rdblacklist=nouveau nomodeset" to the end of the line (without ") and press enter This will enable you to go through anaconda and actually see the text on screen. Upon the next boot text is still visible. I booted to init 3 and installed the proprietary NVidea drivers.
Thank you Kristof. I did as you said and installed with the "rdblacklist..." line appended to the first option, and it did as you said, but I'm still having a problem. I'm still seeing the prompt as I said before which says: "error: unknown filesystem grub rescue> " did you see this as well? If so, how do you get it to boot to init 3 then? Thanks Kristof
Hi, I haven't experienced this issue. (I did both a dual boot as well as single partition for Fedora) It might have to do with GRUB trying to start from the wrong partition. GRUB doesn't know HSF+ so that would explain the unknown filesystem error. Regards, Kristof
I use rEFIt to be able to boot to the particular partition with the GRUB bootloader on it, so that SHOULDN'T be the problem, but this weekend I will try a single partition installation to make sure. If it IS the problem, then how did you get it to dual boot properly? If you don't use rEFIt, how did you get GRUB to recognize the HFS+ partition and be able to boot it? Thanks Kristof
I also used rEFIt, have you done the parition sync in rEFIt? I guess this might also have to do with it. I can't reproduce it now as I've reinstalled Mac OS X for now, haven't got time to figure this out. I was hoping on a quick & clean install :-)
Yeah, I synced the partition tool. I also found time to try out installing Fedora over the whole drive, and it worked. But I put Mac back on it because I want them both to be installed, I don't know why it wouldn't work one way but will the other way. I'll keep trying I guess.
Kristof, how did you do your partitioning? maybe I'm doing something wrong with that?
Hi, This is my disk layout from parted: Model: ATA INTEL SSDSA2M080 (scsi) Disk /dev/sda: 80.0GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 20.5kB 210MB 210MB fat32 EFI System Partition boot, hidden 2 210MB 20.2GB 20.0GB hfsx Mac OS X hidden 3 20.3GB 80.0GB 59.7GB ext4 Untitled boot Basically I created a 20GB partition during Mac OS install and afterwards used the remainder for Fedora. I should have been able to use several partitions but that wasn't necessary for me. Kristof
Well, I got fedora to install (yay!), but it wasn't because I did anything differently. I installed everything exactly how I had before. The only different was that this time Ubuntu hadn't been installed first. Like I said before I had to put Mac OS X back on my hard drive, and I used all of the hard drive to do it. Last time I tried to put fedora on my macbook, Ubuntu was on it first, and I think maybe that's why it didn't work. Perhaps some bit of Ubuntu's installation was still lingering somewhere and rEFIt couldn't handle it. (it would explain the TWO options for linux I had in rEFIt before). Anyway, now it's working (with some problems: no sound and the like) So thanks to everybody :)
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping