Macbook Pro Rev B.

My apologies if there has recently been a post made about this but I was curious if anyone had any relatively solid speculation as to how long it would be before there was a MBP Rev. B and Apple will have a whine free MBP? Or at least have the major quirks worked out of this machine. I owned a MBP but the whine was too much to handle, then on top of other hardware problems I ended up returning it. I now have a Macbook and I'm into more problems (power brick sizzling, whine, and turning on by itself). I'm just getting frustrated and it looks like this one will be returned. I know that putting out a product and working through the issues seems to be a Rev. A expectancy...but I'm considering just using an old laptop and waiting until these appear to be stable. I'd love to go back to the MBP as it was a beautiful machine (as is the MB).
Any ideas as so how long of a wait it would be before they have all these quirks worked out (mostly the whine), so "work arounds" are not needed?

I'm skeptical about the need for or actual results of the "thermal grease" modification and suspect that it will void one's warranty coverage for those things that would be most expensive to repair under warranty. Of course an owner is free to do anything he wishes with a computer, so long as it doesn't harm others.
I've got a week 12 with no whine, no problems of any kind and operating and case temperatures that are perfectly acceptable to me. It's fast and stable, with great WiFi connections. It runs my UB applications on a par with and sometimes even faster than my big PowerMac, which is better than I had expected. It's a joy to use and the best notebook I've ever owned (I've had lots).
Perhaps it should be noted that the various tricks some use to eliminate or reduce whine will result in more processor load, shorter battery runtime and more heat. An iPod would eliminate the whine (if present and objectionable) without those side effects.

Similar Messages

  • Apple address certain problems with macbook pro Rev D (week 12) ?! eh?

    i just came across this.
    http://www.dailytech.com/article.aspx?newsid=1584
    hmm.....

    This article just smacks different then what we are
    hearing on these forums. People with week 11 and
    later builds still have some of the issues this
    writer say have been fixed. My week 11 still drops
    Airport connection after sleep or restart. It also
    gets hot. Not enough to me to be a big deal, but it's
    there. Who is this author, and who did he speak to?
    Why would Apple discuss this with a no name writer in
    a little read online article?
    I think, and I say I think, thee've known about these issues and were scrambling to address them. So many, they had to figure out what to do. I think we will see some sort of official statement soon.
    If you check out all the Mac Web Sites it's obvious. They may have isolated the issues to QA or just a certain supplier of Logic Boards and or inverters.
    This is a big transition PPC to Intel CPU's, bugs will be present. In the end I know the issues will be addressed and we will end up with some pretty powerfull Mac's.
    Putting all issues aside, these MBP's are VERY powerfull. When the apps become native we will really see the speed bump.
    Apple does not want to say anthing until they have solved all the issues at hand.
    William
    My 2 cents.

  • Buy old rev Macbook Pro instead?

    My 4-yr-old G4 Powerbook has led a full & venerable life, but now--since I can't tell the "I' key from the "O" key anymore, they're so effaced--it's time to upgrade. And so I awaited the Oct. 14th date with bated breath, But now, having read scores of reviews slamming the glossy display (I do do digital photography) and the lack of a 400-firewire (less of a concern, IMHO), I'm wondering if purchasing the "old," previous-rev MacBook Pro might be the way to go?
    However--the reason I've waited so long, actually: I'm an audio-GarageBand-LogicPro person who has read many rants about the audio glitches/"hisses"/et al. in the old Penryn architecture. I'm was hoping/assuming that the new MBP would remedy that.(But that may be wishful thinking, too.)
    But then, I've also read testimonials from many "old" MBP music-recorder users who haven't had any problems. So I'm weighing all that, against this apparently god-awful glossy display.
    (But frankly, it seems I heading towards talking myself into the new one, though?)
    At last, I do have the real option of buying the old rev MBP: my local university Computer Store tells me that they won't be getting the new MBP's for "a couple weeks." (Huh?!) But they still have 10 "old" MPB's in stock.
    --dazed & confused in MacLand--
    --tcg

    tgannon wrote:
    My 4-yr-old G4 Powerbook has led a full & venerable life, but now--since I can't tell the "I' key from the "O" key anymore, they're so effaced--it's time to upgrade.
    Are you a hunt and peck or touch typer? If you're the latter, this shouldn't matter.
    And so I awaited the Oct. 14th date with bated breath, But now, having read scores of reviews slamming the glossy display (I do do digital photography) and the lack of a 400-firewire (less of a concern, IMHO), I'm wondering if purchasing the "old," previous-rev MacBook Pro might be the way to go?
    Only you can decide that. If you're adamantly against glossy displays, and/or you absolutely need Firewire 400, then maybe an older generation MBP is the way to go. Early benchmarks suggest that there isn't any significant CPU performance difference between old and new.
    At last, I do have the real option of buying the old rev MBP: my local university Computer Store tells me that they won't be getting the new MBP's for "a couple weeks." (Huh?!) But they still have 10 "old" MPB's in stock.
    Stocks of the new machines will be scarce at 3rd party resellers, since Apple is more concerned with filling internet orders from their website and stocking their retail stores with the new models until supply can keep up with demand. Also remember that the "old" 17" MBP is still for sale directly from Apple for the time being.

  • Why do the fans on my macbook pro suddenly rev up

    The fans on my macbook pro (about 3 - 4) yrs old suddenly rev up and the computer gets very hot. This is sometimes (but not necessarily) at times of optimum use.
    The case seems to be vented ok. I am running Mavericks osx and use computer for range of uses - graphics, e-mails, word and spreadsheets.
    Is this a problem?
    it sure make the computer noisy.

    Hello kiwiwoodz,
    Thanks for the question. After reviewing your post, it sounds like the fan is running at high speed while properly ventilated. I would recommend that you read this article, it may be able to help you isolate or resolve the issue.
    Intel-based Macs: Resetting the System Management Controller (SMC) - Apple Support
    Thanks for using Apple Support Communities.
    Have a nice day,
    Mario

  • Macbook Pro line out hissing (HW rev: 8,2)

    I just got a new 2011 Macbook Pro, the headphones line out has way too much hissing. All my windows laptop HP/Dell/Lenovo have non, this is pretty bad for an expensive Mac. Is there any fix?
    Thanks,
    Daniel.

    I asked some of my friends about this and it seems that it's not as noticable on their Macs as they have different headphones, I'm using high-end Shure SE530 Sound Isolating Earphones, which are very sensitve and I have the sound level turned right down to one or two bars on my Mac.

  • Is KVM VGA Passthrough Possible on Macbook Pro Mid 2014?

    I've been using Arch on and off for a couple years on different hardware, and this time I'm trying to get it to work semi-flawlessly on my mid 2014 Macbook Pro. My Linux skills are meager, so I need some help understanding if VGA passthrough is possible on this machine, and if it is, how to set it up. I have hope that it might work after reading this blog and the Arch forums. An outline of my current setup follows. I will also document progress and research for anyone who might want to try this in the future.
    Here are the specifications for this machine:
    Processor: 2.5 GHz Intel Core i7
    Memory: 16 GB 1600 MHz DDR3
    Graphics: Intel Iris Pro 1536 MB, Nvidia GT 750M 2 GB
    I have successfully dual-booted Mac OS X Yosemite and Arch with EFI on a btrfs partition using this blog and the wiki as starting points. Somlo's research also helped. All the basic functionality works (networking, WiFi, etc.), and I am able to boot the physical Arch partition as a Virtualbox VM with the help of the wiki. However, I'm having trouble with getting the integrated Intel graphics to work. The following command:
    lspci | grep VGA
    prints the Nvidia card specifications, and nothing about the Intel graphics.
    Reading this blog, it looks like someone had to apply a "grub gmux" patch to grub to disable the Nvidia card at boot. I feel uncomfortable installing anything other than the official Arch packages, so I have to know if installing a patched grub is still necessary, and if installing it would still allow me to use VGA passthrough in KVM.
    My ambitious to-do list looks like this:
    1. Dual-boot Mac OS X and Arch with btrfs. -done
    2. Setup the physical Arch partition to boot in Virtualbox. -done
    3. Get Intel graphics to work on Arch ideally with OpenGL support. -done
    4. Get Enlightenment working as the desktop environment on Arch. -done
    5. Get Qemu+KVM to boot off the physical Mac OS X partition. -tbd
    6. Enable VGA passthrough for Mac OS X from Qemu+KVM. -tbd
    7. Install Windows as a VM in Qemu+KVM. -tbd
    8. Enable VGA passthrough for Windows from Qemu+KVM. -tbd
    9. Work and do research on Mac OS X from Arch, play hardcore 3D games on WIndows from Arch, play around with Arch, and live happily ever after. -tbd
    Can anyone help me with this? Thanks in advance for any hints/input.
    Edit:
    The Ubuntu forums has something about getting the two graphics cards to be recognised by using `refind` instead of `grub`. I was able to set up `refind` to boot using the `efi-stub`, but:
    $ lspci
    00:00.0 Host bridge: Intel Corporation Crystal Well DRAM Controller (rev 08)
    00:01.0 PCI bridge: Intel Corporation Crystal Well PCI Express x16 Controller (rev 08)
    00:01.1 PCI bridge: Intel Corporation Crystal Well PCI Express x8 Controller (rev 08)
    00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
    00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
    00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
    00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
    00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
    00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
    00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
    00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
    00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
    01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] (rev a1)
    01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1)
    03:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter (rev 03)
    04:00.0 Multimedia controller: Broadcom Corporation 720p FaceTime HD Camera
    05:00.0 SATA controller: Samsung Electronics Co Ltd Apple PCIe SSD (rev 01)
    06:00.0 PCI bridge: Intel Corporation Device 156d
    07:00.0 PCI bridge: Intel Corporation Device 156d
    07:03.0 PCI bridge: Intel Corporation Device 156d
    07:04.0 PCI bridge: Intel Corporation Device 156d
    07:05.0 PCI bridge: Intel Corporation Device 156d
    07:06.0 PCI bridge: Intel Corporation Device 156d
    08:00.0 System peripheral: Intel Corporation Device 156c
    still only shows the Nvidia card. The boot options suggested by this blog did not change anything. However, this very helpful discussion led me to this on-going project. I patched the kernel according the instructions in the said project's `readme`, and Arch is now able to see the two graphics cards and an extra Intel audio controller.
    $ lspci
    00:02.0 VGA compatible controller: Intel Corporation Crystal Well Integrated Graphics Controller (rev 08)[/bold]
    00:03.0 Audio device: Intel Corporation Crystal Well HD Audio Controller (rev 08)
    01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] (rev a1)
    Also, I was able to fire up Enlightenment using the Intel graphics card and `0xbb`'s `gpu-switch` script. After using some post-installation tips from this, the computer started getting hot. I followed this thread to get it back to normal.
    Edit:
    So I finally got some time to experiment on this. I ended up installing Gnome 3 after trying out Enlightenment, KDE Plasma 5, and Cinnamon. I thought Gnome 3 and Cinnamon had the best Hi-DPI support of those four. Cinnamon's look was too much trouble for me to configure, so I ended up choosing Gnome 3.
    To achieve the graphics card passthrough, I tried setting up and starting a VM in `virt-manager`, but starting the VM would cause Arch to freeze. Finally, I tried following the instructions on the wiki, this thread, and the Arch forums. I haven't yet tried booting the Windows installer, but the following are the steps I took so far:
    1. Uninstall all `nvidia` drivers from my system.
    2. Blacklist the `nouveau` driver.
    3. Add `pci-stub` to the modules array in `mkinitcpio.conf`.
    4. Recreate the `initramfs`.
    5. Add `intel_iommu=on pci-stub.ids=10de:0fe9,10de:0e1b,8086:156c` to the `refind.conf` `options` line.
    - These three IDs are ones for the Nvidia graphics, Nvidia sound, and the "Intel Corporation Device" (probably the HDMI port, or something related to the
    ethernet card), which belong to the same "IOMMU group". What was curious was that a Gigabit ethernet controller would appear in the IOMMU group iff I had
    an ethernet cable connected to my thunderbolt port. I don't know if I have to add the ID for this, but so far there are no complaints about it in `dmesg`.
    6. Install `ovmf-svn` from the AUR.
    6. Follow the "Binding a device to vfio-pci" section documented at https://bbs.archlinux.org/viewtopic.php?id=162768.
    7. Follow the "Testing if its working out" section documented at https://bbs.archlinux.org/viewtopic.php?id=162768.
    So far, the test at step 7 is failing -- I get a `vfio-pci 0000:01:00.0: Invalid ROM contents` complaint in `dmesg`, and I see a prompt in the `qemu` window. I'm supposed to be getting a black `qemu` window, and a prompt on an external monitor which I haven't connected yet. I read the comments on this blog about graphics card ROM and EFI compatibility, and it looks like my graphics card ROM can't be read. I also read that the graphics card ROM would only be read once by qemu/KVM and saved as a file for later use, so all I need to do to get around that is pass a snapshot of the ROM of the Nvidia GT 750M card to qemu/KVM. Apparently, "You can download the 750m rom files directly from Lenovo's website on the support page" according to this thread, but all I see is this. I will continue hunting around for a ROM file for this graphics card.
    Last edited by rb3 (2015-06-05 02:01:20)

    It`s not beacuse of the case. I have the same problem with a macbook pro retina 15 late 2013 (I7 - 2.3 Ghz, 16 GB, 512 SSD, GT750M) with windows 8.1 on bootcamp. The temperature is higher than yosemite. It gets easily at 80 celsius in a demanding game, while on yosemite it barely reaches 55-60 under heavy load. It`s beacuse of windows, and these are the temperatures, I got the same average 55-60 in windows and 45 celsius in yosemite. I read on the forums and I tried evend with a cooler pad. But it doesn`t seem to be any improvement with lowering the temperature in windows.

  • Switching to archlinux on MacBook Pro 13'' (december 2010)

    Hi all!
    I've been missing a lot archlinux since i bought a 13 inches MacBook Pro in december.
    So i started looking around on the forum get some informations about using Arch on the MB, and i'm very happy that all runs smoothly without issues.
    Before moving, tho, i still have some questions.
    I bought this laptop for three reasons: the battery, the mobility and the multitouch.
    I do a lot of developing, always moving from university to office to home, and i needed a robust and quick laptop with a lot of battery time, other than low weight.
    I use it for django and python developing (so, also, mysql server) and c/c++/java for university projects, and with those i am sure i'll have no problem!
    I need to have windows installed too (just for steam, actually, and dawn of war 2), to be sure i can use the mini display port (with hdmi, for the external monitor and movies) and have no problems with the graphic chipset (just to play hd videos on the monitor)
    If i'm leaving osx (lot of bloatness) for arch, i'll be back to my minimal configuration with urxvt, xmonad (or awesome), irssi, vim and mpd, xrandr to handle the multi monitors and old proud conkeror as browser.
    So, in the end, what about the mini display port? And will i be able to mantain my battery time (or even improving it, by using a low-resource minimal system like arch)? Any issues i should know about?
    Thanks all in advance for your opinion!

    Can't seem to find mini display port.
    It seems others have been successful, alas I am not.  I am attempting to attach an external monitor on my aluminum body macbook running Arch, but the mini display port seems to be evading detection.
    Output of lspci:
    [09:44:10] tds3 ~ $ lspci
    00:00.0 Host bridge: nVidia Corporation MCP79 Host Bridge (rev b1)
    00:00.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
    00:03.0 ISA bridge: nVidia Corporation MCP79 LPC Bridge (rev b2)
    00:03.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
    00:03.2 SMBus: nVidia Corporation MCP79 SMBus (rev b1)
    00:03.3 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
    00:03.4 RAM memory: nVidia Corporation Device 0a98 (rev b1)
    00:03.5 Co-processor: nVidia Corporation MCP79 Co-processor (rev b1)
    00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
    00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
    00:06.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
    00:06.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
    00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1)
    00:09.0 PCI bridge: nVidia Corporation MCP79 PCI Bridge (rev b1)
    00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1)
    00:0b.0 IDE interface: nVidia Corporation MCP79 SATA Controller (rev b1)
    00:10.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
    00:15.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
    02:00.0 VGA compatible controller: nVidia Corporation C79 [GeForce 9400M] (rev b1)
    03:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
    Output of xrandr -q: (with external monitor attached and powered on)
    [09:49:18] tds3 ~ $ xrandr -q
    xrandr: Failed to get size of gamma for output default
    Screen 0: minimum 320 x 175, current 1280 x 800, maximum 1280 x 800
    default connected 1280x800+0+0 0mm x 0mm
       1280x800       50.0*
       1024x768       51.0     52.0 
       832x624        53.0 
       800x600        54.0     55.0     56.0     57.0     58.0 
       720x400        59.0 
       700x525        60.0 
       640x512        61.0     62.0 
       640x480        63.0     64.0     65.0     66.0     67.0 
       640x400        68.0 
       640x350        69.0 
       576x432        70.0 
       512x384        71.0     72.0     73.0     74.0     75.0 
       416x312        76.0 
       400x300        77.0     78.0     79.0     80.0     81.0 
       360x200        82.0 
       320x240        83.0     84.0     85.0     86.0 
       320x200        87.0 
       320x175        88.0 
    Does this make sense?

  • What cable do i need to connect my macbook pro to the hdmi input on my tv?.

    what cable do i need to connect my macbook pro to the hdmi input on my tv?.

    hi Sam
    It's actally an HDMI adapter that Apple sells.
    You hook the small adapter up to your MBP and then HDMI cable to your TV. Please note adapter is for HDMI compliant for HDMI rev 1.3 and above:
    My TV, which has DVI port also, besides HDMI gets its best resolution by DVI of which also sell at Apple store for the MBP.
    Bottom line is check w/ your TV manufacture to be sure your flat screen supports 1920 X 1200.
    Let 'er rip and...
    cheers

  • MacBook Pro won't start after upgrade, not even in recovery mode

    So here is what happened:
    Yesterday, the app store icon told me that one update was not installed yet,because I need to restart the computer first (hard for me to reconstruct now, because I didn't really read it carefully, which I should have done, but Apple"just works™", so hey, why should I ). So I restarted the computer. This is where things went very wrong. Eventually during reboot, text appeared on the grey Apple logo screen, it looked like verbose boot mode, but overlaid on the "regular" grey boot screen with the  logo. Before I could read, what was happening, I got a kernel panic with the "hold down the power button to restart".
    Holding down the power button took me to the login/file vault unlock screen (I have my disk encrypted). Unfortunately neither keyboard nor trackpad worked. So I held down the power button again, which brought me back to the login/file vault unlock screen.
    At this point I noticed that it said in the lower part of the screen that, in case I had problems to enter my login information, I should press the power button for a long time and then again for a short time to get into recovery mode (this is all from my memory, I might not recall it exactly as it happened).
    This made things kind of worse, it showed me the Apple logo with the progress bar, which advanced to about a third or a quarter, then the progress stopped and I ended up on a grey screen with a grey crossed circle in the center (looks kind of like an european no parking sign).
    I tried booting into recovery mode by holding down the R key. This brings me to the progress bar and the subsequent grey screen.
    I tried to boot into my time machine, by holding down the option key. This gets me to the boot volume selection, I can choose my time machine volume (external FW800 drive), but it does not use this volume to boot (I can hear that the external disk is not spinning). Instead I get the above mentioned behavior (progress bar, grey screen).
    I tried to boot into target disk mode by holding down the T key. This only works, when I connect an external USB keyboard. This way I could use another computer to recover my important files (which is good). I could also peek at the logs. It seems as if the failed boot attempts do not produce logs. But I have the system log from the "restart to install update" process. The last few seconds or so I get a lot of these messages:
    Feb  3 14:33:51 Larss-MacBook-Pro kernel[0]: Refusing new kext com.apple.kpi.libkern, v14.1: already have loaded v14.0.
    I use a Macbook Pro 13" early 2011. I don't know the processor speed, because I cannot boot it. I guess it has 8 GB Ram (pretty sure I maxed it out).
    I have an SSD installed (I replaced the original HD with a 1GB Samsung SSD). There is another post here, which sounds similar, but I definitely did not use "Trim enabler" or similar third party software.
    I use Yosemite, I think I was pretty much up to date, I suspect the reboot was for the 10.10.2 installation, but I am not sure (I simply didn't look when I hit that reboot to install button).
    Yosemite on SSD wont boot and wont go in safe or recovery mode
    Anyone any ideas? Any help is appreciated!

    So I just went through the install.log.
    First of all, there I found out that I have a MacBook Pro (13-inch, Mid 2010):
    Feb  3 14:31:12 larsmbpro.domain.com suhelperd[336]: GetModel: model = MacBookPro; major rev = 7; minor rev = 1
    I think it was indeed the upgrade to Yosemite 10.10.2:
    Feb  3 14:31:18 larsmbpro.domain.com softwareupdated[334]: SoftwareUpdate: Added foreground transaction [0x1] for OSXUpd10.10.2-10.10.2
    but there was also a firmware update included:
    Feb  3 14:31:21 larsmbpro.domain.com installd[363]: PackageKit: packages=(
         "PKLeopardPackage <file:///Library/Updates/031-17157/OSXUpd10.10.2Patch.pkg>",
         "PKLeopardPackage <file:///Library/Updates/031-17157/FirmwareUpdate.pkg>"
    The last messages in this log are:
    Feb  3 14:33:07 larsmbpro.domain.com Software Update.app[2747]: Running /sbin/reboot
    Feb  3 14:33:07 larsmbpro.domain.com softwareupdated[334]: Removing client SUUpdateServiceClient pid=2747, uid=0, installAuth=YES rights=(system.install.apple-software, system.install.apple-software.standard-user, system.install.software, com.apple.SoftwareUpdate.modify-settings), transactions=1 (/System/Library/CoreServices/Software Update.app/Contents/MacOS/Software Update)
    According to the system.log, the shutdown happened 14:33:08. The boot time is 14:33:24, no log entries between 14:33:08 and that time. 16 seconds seems awfully long for a reboot:
    Feb  3 14:33:08 larsmbpro kernel[0]: Kernel requests now disabled.
    Feb  3 14:33:24 localhost bootlog[0]: BOOT_TIME 1422970404 0
    Feb  3 14:33:46 localhost syslogd[19]: Configuration Notice:
      ASL Module "com.apple.AccountPolicyHelper" claims selected messages.
      Those messages may not appear in standard system log files or in the ASL database.

  • [SOLVED] Trouble starting Xorg on Macbook Pro 7,1

    I'm trying to set up Xorg on my 13" Macbook Pro 7,1.  Every time I run startx, I get a blank screen and have to do a hard reset.  This is on a brand new install.  I've installed the wireless drivers, connected to the network, upgraded any packages needing it (pacman -Syuu), installed vim and yaourt, and created a non-privileged user.  I did not upgrade kernel26 or kernel26-headers because they fail to boot (I think I need the physical mode patch).
    Here's what I've done so far:
    pacman -S xorg-server xorg-utils xorg-xinit xorg-twm xterm
    pacman -S nvidia nvidia-utils
    (reboot)
    nvidia-xconfig
    pacman -S acpid hal
    /etc/rc.d/hal start
    (log in as non-privileged user)
    startx
    The screen goes black, and then nothing happens.  I've tried it both with and without acpid and hal.
    Here is my xorg.conf:
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 280.11 ([email protected]) Thu Jul 21 14:16:58 PDT 2011
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    EndSection
    Section "Files"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    Option "DPMS"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    And my Xorg.0.log:
    [ 237.871]
    X.Org X Server 1.10.3
    Release Date: 2011-07-08
    [ 237.871] X Protocol Version 11, Revision 0
    [ 237.871] Build Operating System: Linux 2.6.39-ARCH x86_64
    [ 237.872] Current Operating System: Linux jhallLinux 2.6.39-ARCH #1 SMP PREEMPT Mon Jun 6 22:37:55 CEST 2011 x86_64
    [ 237.872] Kernel command line: BOOT_IMAGE=/boot/vmlinuz26 root=/dev/sda3 reboot=pci
    [ 237.872] Build Date: 09 July 2011 07:52:32AM
    [ 237.873]
    [ 237.873] Current version of pixman: 0.22.2
    [ 237.873] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 237.873] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 237.874] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 27 21:24:48 2011
    [ 237.889] (==) Using config file: "/etc/X11/xorg.conf"
    [ 237.889] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 237.916] (==) ServerLayout "Layout0"
    [ 237.916] (**) |-->Screen "Screen0" (0)
    [ 237.916] (**) | |-->Monitor "Monitor0"
    [ 237.916] (**) | |-->Device "Device0"
    [ 237.916] (**) |-->Input Device "Keyboard0"
    [ 237.916] (**) |-->Input Device "Mouse0"
    [ 237.917] (==) Automatically adding devices
    [ 237.917] (==) Automatically enabling devices
    [ 237.949] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
    [ 237.949] Entry deleted from font path.
    [ 237.949] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 237.949] Entry deleted from font path.
    [ 237.949] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 237.949] Entry deleted from font path.
    [ 237.949] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 237.950] Entry deleted from font path.
    [ 237.950] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 237.950] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 237.950] Entry deleted from font path.
    [ 237.950] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 237.950] (==) FontPath set to:
    /usr/share/fonts/misc/
    [ 237.950] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 237.950] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 237.950] (WW) Disabling Keyboard0
    [ 237.950] (WW) Disabling Mouse0
    [ 237.950] (II) Loader magic: 0x7d3440
    [ 237.950] (II) Module ABI versions:
    [ 237.950] X.Org ANSI C Emulation: 0.4
    [ 237.950] X.Org Video Driver: 10.0
    [ 237.950] X.Org XInput driver : 12.2
    [ 237.950] X.Org Server Extension : 5.0
    [ 237.951] (--) PCI:*(0:4:0:0) 10de:08a0:106b:00c2 rev 162, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00001000/128, BIOS @ 0x????????/131072
    [ 237.952] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 237.952] (II) LoadModule: "extmod"
    [ 237.959] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 237.967] (II) Module extmod: vendor="X.Org Foundation"
    [ 237.967] compiled for 1.10.3, module version = 1.0.0
    [ 237.967] Module class: X.Org Server Extension
    [ 237.967] ABI class: X.Org Server Extension, version 5.0
    [ 237.967] (II) Loading extension MIT-SCREEN-SAVER
    [ 237.967] (II) Loading extension XFree86-VidModeExtension
    [ 237.967] (II) Loading extension XFree86-DGA
    [ 237.967] (II) Loading extension DPMS
    [ 237.967] (II) Loading extension XVideo
    [ 237.967] (II) Loading extension XVideo-MotionCompensation
    [ 237.967] (II) Loading extension X-Resource
    [ 237.967] (II) LoadModule: "dbe"
    [ 237.967] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 237.968] (II) Module dbe: vendor="X.Org Foundation"
    [ 237.968] compiled for 1.10.3, module version = 1.0.0
    [ 237.968] Module class: X.Org Server Extension
    [ 237.968] ABI class: X.Org Server Extension, version 5.0
    [ 237.968] (II) Loading extension DOUBLE-BUFFER
    [ 237.968] (II) LoadModule: "glx"
    [ 237.968] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 238.562] (II) Module glx: vendor="NVIDIA Corporation"
    [ 238.569] compiled for 4.0.2, module version = 1.0.0
    [ 238.569] Module class: X.Org Server Extension
    [ 238.569] (II) NVIDIA GLX Module 280.11 Thu Jul 21 14:13:06 PDT 2011
    [ 238.570] (II) Loading extension GLX
    [ 238.570] (II) LoadModule: "record"
    [ 238.570] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 238.578] (II) Module record: vendor="X.Org Foundation"
    [ 238.578] compiled for 1.10.3, module version = 1.13.0
    [ 238.578] Module class: X.Org Server Extension
    [ 238.578] ABI class: X.Org Server Extension, version 5.0
    [ 238.578] (II) Loading extension RECORD
    [ 238.578] (II) LoadModule: "dri"
    [ 238.578] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 238.585] (II) Module dri: vendor="X.Org Foundation"
    [ 238.585] compiled for 1.10.3, module version = 1.0.0
    [ 238.585] ABI class: X.Org Server Extension, version 5.0
    [ 238.585] (II) Loading extension XFree86-DRI
    [ 238.585] (II) LoadModule: "dri2"
    [ 238.585] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 238.586] (II) Module dri2: vendor="X.Org Foundation"
    [ 238.586] compiled for 1.10.3, module version = 1.2.0
    [ 238.586] ABI class: X.Org Server Extension, version 5.0
    [ 238.586] (II) Loading extension DRI2
    [ 238.586] (II) LoadModule: "nvidia"
    [ 238.607] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 238.672] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 238.674] compiled for 4.0.2, module version = 1.0.0
    [ 238.674] Module class: X.Org Video Driver
    [ 238.701] (II) NVIDIA dlloader X Driver 280.11 Thu Jul 21 13:56:10 PDT 2011
    [ 238.701] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 238.701] (--) using VT number 7
    [ 238.751] (II) Loading sub module "fb"
    [ 238.751] (II) LoadModule: "fb"
    [ 238.751] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 238.762] (II) Module fb: vendor="X.Org Foundation"
    [ 238.762] compiled for 1.10.3, module version = 1.0.0
    [ 238.762] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 238.762] (II) Loading sub module "wfb"
    [ 238.762] (II) LoadModule: "wfb"
    [ 238.762] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 238.775] (II) Module wfb: vendor="X.Org Foundation"
    [ 238.775] compiled for 1.10.3, module version = 1.0.0
    [ 238.775] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 238.775] (II) Loading sub module "ramdac"
    [ 238.775] (II) LoadModule: "ramdac"
    [ 238.775] (II) Module "ramdac" already built-in
    [ 238.790] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 238.790] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 238.790] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 238.800] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    [ 238.800] (==) NVIDIA(0): RGB weight 888
    [ 238.800] (==) NVIDIA(0): Default visual is TrueColor
    [ 238.800] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 239.489] (EE) NVIDIA(0): Failed to initialize the display subsystem for the NVIDIA
    [ 239.489] (EE) NVIDIA(0): graphics device!
    [ 239.489] (EE) NVIDIA(0): Failed to get supported display device(s)
    [ 239.489] (EE) NVIDIA(0): Failed to initialize dac HAL
    [ 239.490] (II) UnloadModule: "nvidia"
    [ 239.490] (II) Unloading nvidia
    [ 239.490] (II) UnloadModule: "wfb"
    [ 239.490] (II) Unloading wfb
    [ 239.490] (II) UnloadModule: "fb"
    [ 239.490] (II) Unloading fb
    [ 239.490] (EE) Screen(s) found, but none have a usable configuration.
    [ 239.490]
    Fatal server error:
    [ 239.490] no screens found
    [ 239.490]
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 239.490] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 239.490]
    The NVIDIA page in the Arch Wiki says to comment out any occurrences of dri (and I assume dri2 as well) in xorg.conf.  As you can see, they are not in xorg.conf, but they are still being loaded.  I'm not sure where they are coming from.  I haven't messed with anything in xord.conf.d (though the 20-nvidia.conf file showed up).  I don't see any references to dri there, either.
    I've also tried nvidia-beta and nvidia-utils-beta, but the same thing happens.
    Does anyone know what the problem is?
    Last edited by ldb88 (2011-07-30 23:56:55)

    On a typical setup, Ctrl+Alt+F7--or really, Alt-F7--switches to Display 0, where X will attach if you're using startx.
    Probably, Display 0 is on screen after startx, and you're just not getting anything.  As long as your keyboard is binding correctly, you should be able to hit Ctrl+Alt+F1 to get back to the first terminal, assuming that is from where you started X.
    Otherwise, yes, make sure dbus is installed and started.
    rc.d dbus start
    Or, is it--
    rc.d start dbus
    I've been using systemd for a while now.  Can't remember.
    Also make sure dbus is in your daemons array in /etc/rc.conf.

  • Xorg doesn't start on Macbook Pro 4,1

    I've just installed Arch on my Macbook Pro 4,1 (Early 2008).
    The machine has this graphics card:
    VGA compatible controller: NVIDIA Corporation G84M [GeForce 8600 GT] (rev a1)
    I've installed "nvidia" package driver, launched "nvidia-xconfig" but when I try to launch:
    X -config /etc/X11/xorg.conf
    Xorg gives me some errors and doesn't starts X.
    http://i.imgur.com/AtzHf77l.jpg
    Ideas?
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

    Yeah it is quite a mess... but thats what you get when you try to use hardware that picks and chooses the bits of the UEFI standard it wants to include.
    So like most UEFI systems, Mac(book)s are able to boot their own system with it's EFI setup.  It *can* also be used to boot other systems, but setting it up is unique to Macs.  So for the purpose of "bootcamp", Apple introduced a bios compatibility mode.  When it was introduced, there was no real windows UEFI prevalence (existence?) at that point.  So that is how they made this possible.
    But the compatibility mode is not turned on by default.  OSX uses GPT (according to the standard and everything in this case), but when it makes a "bootcamp" partition it adds to the GPT a MBR partition table (ms-dos) with partitions.  According to the GPT spec, there is the actual GPT partition table, but there is also the inclusion of a MBR with a single partition spanning the whole disk.  This is to protect the disk from being overwritten by non-GPT aware tools (like fdisk was until recently).  So a hybrid MBR simply adds partitions to the ms-dos partition table that (hoepfully) line up with at lease the first few partitions of the GPT.  When this is present, the machine will enable the bios compatibility mode.
    Booting the Mac with EFI will have no bearing on the Arch Linux installation that is installed in bios compatibility mode.  It will use its own bootloader and everything.  So there should be no issue.  It is probably good to use something like rEFInd in order to give yourself a nice interface with which to select between the two though.  The other boot loaders and/or boot managers don't have the ability to recognize both EFI and bios bootloaders.

  • My MacBook Pro is running very slow is there anything I can do to improve the performance?

    Is there anything I can do to improve the speed of my MacBook Pro?

    Kappy's Personal Suggestions About OS X Maintenance
    For disk repairs use Disk Utility.  For situations DU cannot handle the best third-party utility is: Disk Warrior;  DW only fixes problems with the disk directory, but most disk problems are caused by directory corruption. Drive Genius provides additional tools not found in Disk Warrior for defragmentation of older drives, disk repair, disk scans, formatting, partitioning, disk copy, and benchmarking. 
    Four outstanding sources of information on Mac maintenance are:
    1. OS X Maintenance - MacAttorney.
    2. Mac maintenance Quick Assist
    3. Maintaining Mac OS X
    4. Mac Maintenance Guide
    Periodic Maintenance
    OS X performs certain maintenance functions that are scheduled to occur on a daily, weekly, or monthly period. The maintenance scripts run in the early AM only if the computer is turned on 24/7 (no sleep.) See Mac OS X- About background maintenance tasks. If you are running Leopard or later these tasks are run automatically, so there is no need to use any third-party software to force running these tasks.
    If you are using a pre-Leopard version of OS X, then an excellent solution is to download and install a shareware utility such as Macaroni, JAW PseudoAnacron, or Anacron that will automate the maintenance activity regardless of whether the computer is turned off or asleep.  Dependence upon third-party utilities to run the periodic maintenance scripts was significantly reduced after Tiger.  (These utilities have limited or no functionality with Snow Leopard, Lion, or Mountain Lion and should not be installed.)
    Defragmentation
    OS X automatically defragments files less than 20 MBs in size, so unless you have a disk full of very large files there's little need for defragmenting the hard drive except when trying to install Boot Camp on a fragmented drive. But you don't need to buy third-party software. All you need is a spare external hard drive and Carbon Copy Cloner.
    Cheap and Easy Defragmentation
    You will have to backup your OS X partition to an external drive, boot from the external drive, use Disk Utility to repartition and reformat your hard drive back to a single volume, then restore your backup to the internal hard drive. You will use Carbon Copy Cloner to create the backup and to restore it.
      1. Get an empty external hard drive and clone your internal drive to the
           external one.
      2. Boot from the external hard drive.
      3. Erase the internal hard drive.
      4. Restore the external clone to the internal hard drive.
    Clone the internal drive to the external drive
      1. Open Carbon Copy Cloner.
      2. Select the Source volume from the left side dropdown menu.
      3. Select the Destination volume from the left side dropdown menu.
      4. Be sure the Block Copy button is not depressed or is ghosted.
      5. Click on the Clone button.
    Destination means the external backup drive. Source means the internal startup drive.
    Restart the computer and after the chime press and hold down the OPTION key until the boot manager appears.  Select the icon for the external drive and click on the upward pointing arrow button.
    After startup do the following:
    Erase internal hard drive
      1. Open Disk Utility in your Utilities folder.
      2. After DU loads select your internal hard drive (this is the entry with the
           mfgr.'s ID and size) from the left side list. Note the SMART status of the
           drive in DU's status area.  If it does not say "Verified" then the drive is
           failing or has failed and will need replacing.  SMART info will not be
           reported  on external drives. Otherwise, click on the Partition tab in the
           DU main window.
      3. Under the Volume Scheme heading set the number of partitions from the
           drop down menu to one. Set the format type to Mac OS Extended
           (Journaled.) Click on the Options button, set the partition scheme to
           GUID then click on the OK button. Click on the Partition button and wait
           until the process has completed.
    Restore the clone to the internal hard drive
      1. Open Carbon Copy Cloner.
      2. Select the Source volume from the left side dropdown menu.
      3. Select the Destination volume from the left side dropdown menu.
      4. Be sure the Block Copy button is not selected or is ghosted.
      5. Click on the Clone button.
    Destination means the internal hard drive. Source means the external startup drive.
    Note that the Source and Destination drives are swapped for this last procedure.
    Malware Protection
    As for malware protection there are few if any such animals affecting OS X. Starting with Lion Apple has included built-in malware protection that is automatically updated as necessary.
    Helpful Links Regarding Malware Protection:
    1. Mac Malware Guide.
    2. Detecting and avoiding malware and spyware
    3. Macintosh Virus Guide
    For general anti-virus protection I recommend only using ClamXav, but it is not necessary if you are keeping your computer's operating system software up to date. You should avoid any other third-party software advertised as providing anti-malware/virus protection. They are not required and could cause the performance of your computer to drop.
    Cache Clearing
    I recommend downloading a utility such as TinkerTool System, OnyX 2.4.3, Mountain Lion Cache Cleaner 7.0.9, Maintenance 1.6.8, or Cocktail 5.1.1 that you can use for periodic maintenance such as removing old log files and archives, clearing caches, etc. Corrupted cache files can cause slowness, kernel panics, and other issues. Although this is not a frequent nor a recurring problem, when it does happen there are tools such as those above to fix the problem.
    If you are using Snow Leopard or earlier, then for emergency cleaning install the freeware utility Applejack.  If you cannot start up in OS X, you may be able to start in single-user mode from which you can run Applejack to do a whole set of repair and maintenance routines from the command line.  Note that AppleJack 1.5 is required for Leopard. AppleJack 1.6 is compatible with Snow Leopard. (AppleJack works with Snow Leopard or earlier.)
    Installing System Updates or Upgrades
    When you install any new system software or updates be sure to repair the hard drive and permissions beforehand.
    Backup and Restore
    Having a backup and restore strategy is one of the most important things you can do to maintain your computer. Get an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
      1. Carbon Copy Cloner.
      2. Deja Vu
      3. SuperDuper!
      4. Synk Pro
      5. Tri-Backup
    Visit The XLab FAQs and read the FAQs on maintenance and backup and restore.
    Always have a current backup before performing any system updates or upgrades.
    Be sure you have an adequate amount of RAM installed for the number of applications you run concurrently. Be sure you leave a minimum of 10% of the hard drive's capacity or 20 GBs, whichever is greater, as free space. Avoid installing utilities that rely on Haxies, SIMBL, or that alter the OS appearance, add features you will rarely if ever need, etc. The more extras you install the greater the probability of having problems. If you install software be sure you know how to uninstall it. Avoid installing multiple new software at the same time. Install one at a time and use it for a while to be sure it's compatible.
    Additional suggestions will be found in:    
    1. Mac OS X speed FAQ
    2. Speeding up Macs
    3. Macintosh OS X Routine Maintenance
    4. Essential Mac Maintenance: Get set up
    5. Essential Mac Maintenance: Rev up your routines
    6. Five Mac maintenance myths
    7. How to Speed up Macs
    8. Myths of required versus not required maintenance for Mac OS X
    Referenced software can be found at CNet Downloads or MacUpdate.
    Add more RAM or run fewer applications concurrently.

  • [Solved] Xorg Macbook Pro 4,1 Errors

    Hello everyone. It's my first time here and I've come with issues that I was hoping to get some help with. After finally getting Arch onto my Macbook Pro 4,1 (Early 2008), I'm stumped with Xorg. For reference, after logging in the first time and setting up my wifi and the base Xorg configuration, I ran:
    sudo pacman -S nvidia
    sudo pacman -U /mnt/usb/lib32-nvidia-utils-331.20-1-x86_64.pkg.tar.xz
    Long story short, I rebooted as per the instructions then ran:
    startx
    but received errors. Below is my xorg.conf followed by the Xorg.0.log file. Any help would be greatly appreciated. Thanks.
    xorg.conf
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 331.20 (buildmeister@swio-display-x86-rhel47-05) Wed Oct 30 18:20:53 PDT 2013
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    EndSection
    Section "Files"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    Option "DPMS"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600M GT"
    BusID "PCI:1:0:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "UseDPLib" "off"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Xorg.0.log
    [ 585.317]
    X.Org X Server 1.14.4
    Release Date: 2013-10-31
    [ 585.322] X Protocol Version 11, Revision 0
    [ 585.324] Build Operating System: Linux 3.11.6-1-ARCH x86_64
    [ 585.325] Current Operating System: Linux archer 3.12.0-1-ARCH #1 SMP PREEMPT Wed Nov 6 09:06:27 CET 2013 x86_64
    [ 585.325] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=/dev/sda6 rw nomodeset nouveau.modset=0 quiet
    [ 585.328] Build Date: 01 November 2013 05:10:48PM
    [ 585.330]
    [ 585.331] Current version of pixman: 0.32.4
    [ 585.335] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 585.335] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 585.341] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 20 19:34:04 2013
    [ 585.343] (==) Using config file: "/etc/X11/xorg.conf"
    [ 585.345] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 585.345] (==) ServerLayout "Layout0"
    [ 585.345] (**) |-->Screen "Screen0" (0)
    [ 585.345] (**) | |-->Monitor "Monitor0"
    [ 585.345] (**) | |-->Device "Device0"
    [ 585.345] (**) |-->Input Device "Keyboard0"
    [ 585.345] (**) |-->Input Device "Mouse0"
    [ 585.345] (==) Automatically adding devices
    [ 585.345] (==) Automatically enabling devices
    [ 585.345] (==) Automatically adding GPU devices
    [ 585.345] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
    [ 585.345] Entry deleted from font path.
    [ 585.345] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 585.345] Entry deleted from font path.
    [ 585.345] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 585.345] Entry deleted from font path.
    [ 585.345] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 585.345] Entry deleted from font path.
    [ 585.345] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 585.345] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 585.345] Entry deleted from font path.
    [ 585.345] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 585.345] (==) FontPath set to:
    /usr/share/fonts/misc/
    [ 585.345] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 585.345] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 585.345] (WW) Disabling Keyboard0
    [ 585.345] (WW) Disabling Mouse0
    [ 585.345] (II) Loader magic: 0x7fdc20
    [ 585.345] (II) Module ABI versions:
    [ 585.345] X.Org ANSI C Emulation: 0.4
    [ 585.345] X.Org Video Driver: 14.1
    [ 585.345] X.Org XInput driver : 19.1
    [ 585.345] X.Org Server Extension : 7.0
    [ 585.345] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 585.348] (--) PCI:*(0:1:0:0) 10de:0407:106b:00a3 rev 161, Mem @ 0x92000000/16777216, 0x80000000/268435456, 0x90000000/33554432, I/O @ 0x00007000/128, BIOS @ 0x????????/131072
    [ 585.350] Initializing built-in extension Generic Event Extension
    [ 585.352] Initializing built-in extension SHAPE
    [ 585.353] Initializing built-in extension MIT-SHM
    [ 585.355] Initializing built-in extension XInputExtension
    [ 585.356] Initializing built-in extension XTEST
    [ 585.358] Initializing built-in extension BIG-REQUESTS
    [ 585.359] Initializing built-in extension SYNC
    [ 585.361] Initializing built-in extension XKEYBOARD
    [ 585.362] Initializing built-in extension XC-MISC
    [ 585.363] Initializing built-in extension SECURITY
    [ 585.365] Initializing built-in extension XINERAMA
    [ 585.366] Initializing built-in extension XFIXES
    [ 585.367] Initializing built-in extension RENDER
    [ 585.369] Initializing built-in extension RANDR
    [ 585.370] Initializing built-in extension COMPOSITE
    [ 585.371] Initializing built-in extension DAMAGE
    [ 585.372] Initializing built-in extension MIT-SCREEN-SAVER
    [ 585.374] Initializing built-in extension DOUBLE-BUFFER
    [ 585.375] Initializing built-in extension RECORD
    [ 585.376] Initializing built-in extension DPMS
    [ 585.377] Initializing built-in extension X-Resource
    [ 585.378] Initializing built-in extension XVideo
    [ 585.380] Initializing built-in extension XVideo-MotionCompensation
    [ 585.381] Initializing built-in extension XFree86-VidModeExtension
    [ 585.382] Initializing built-in extension XFree86-DGA
    [ 585.383] Initializing built-in extension XFree86-DRI
    [ 585.384] Initializing built-in extension DRI2
    [ 585.384] (WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
    [ 585.384] (WW) "DRI2" will not be loaded unless you've specified it to be loaded elsewhere.
    [ 585.384] (WW) "nouveau" will not be loaded unless you've specified it to be loaded elsewhere.
    [ 585.384] (II) "glx" will be loaded by default.
    [ 585.384] (II) LoadModule: "glx"
    [ 585.384] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 585.404] (II) Module glx: vendor="NVIDIA Corporation"
    [ 585.404] compiled for 4.0.2, module version = 1.0.0
    [ 585.404] Module class: X.Org Server Extension
    [ 585.404] (II) NVIDIA GLX Module 331.20 Wed Oct 30 17:36:48 PDT 2013
    [ 585.405] Loading extension GLX
    [ 585.405] (II) LoadModule: "nvidia"
    [ 585.405] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 585.405] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 585.405] compiled for 4.0.2, module version = 1.0.0
    [ 585.406] Module class: X.Org Video Driver
    [ 585.406] (II) NVIDIA dlloader X Driver 331.20 Wed Oct 30 17:16:53 PDT 2013
    [ 585.406] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 585.406] (++) using VT number 1
    [ 585.406] (II) Loading sub module "fb"
    [ 585.406] (II) LoadModule: "fb"
    [ 585.406] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 585.406] (II) Module fb: vendor="X.Org Foundation"
    [ 585.406] compiled for 1.14.4, module version = 1.0.0
    [ 585.406] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 585.406] (WW) Unresolved symbol: fbGetGCPrivateKey
    [ 585.406] (II) Loading sub module "wfb"
    [ 585.406] (II) LoadModule: "wfb"
    [ 585.406] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 585.406] (II) Module wfb: vendor="X.Org Foundation"
    [ 585.406] compiled for 1.14.4, module version = 1.0.0
    [ 585.406] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 585.406] (II) Loading sub module "ramdac"
    [ 585.406] (II) LoadModule: "ramdac"
    [ 585.406] (II) Module "ramdac" already built-in
    [ 585.407] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    [ 585.407] (==) NVIDIA(0): RGB weight 888
    [ 585.407] (==) NVIDIA(0): Default visual is TrueColor
    [ 585.407] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 585.407] (**) NVIDIA(0): Enabling 2D acceleration
    [ 585.417] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    [ 585.417] (EE) NVIDIA(GPU-0): check your system's kernel log for additional error
    [ 585.417] (EE) NVIDIA(GPU-0): messages and refer to Chapter 8: Common Problems in the
    [ 585.417] (EE) NVIDIA(GPU-0): README for additional information.
    [ 585.417] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!
    [ 585.417] (EE) NVIDIA(0): Failing initialization of X screen 0
    [ 585.417] (II) UnloadModule: "nvidia"
    [ 585.417] (II) UnloadSubModule: "wfb"
    [ 585.417] (II) UnloadSubModule: "fb"
    [ 585.417] (EE) Screen(s) found, but none have a usable configuration.
    [ 585.417] (EE)
    Fatal server error:
    [ 585.417] (EE) no screens found(EE)
    [ 585.417] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 585.417] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 585.417] (EE)
    [ 585.421] (EE) Server terminated with error (1). Closing log file.
    If there's any other information needed, let me know.
    Last edited by Proxy (2013-11-24 16:19:29)

    I tried installing that, removed nvidia because of the conflicts, restarted then ran it again. Still errors. I've included the updated log file:
    [ 162.658]
    X.Org X Server 1.14.4
    Release Date: 2013-10-31
    [ 162.662] X Protocol Version 11, Revision 0
    [ 162.663] Build Operating System: Linux 3.11.6-1-ARCH x86_64
    [ 162.664] Current Operating System: Linux archer 3.12.1-1-ARCH #1 SMP PREEMPT Thu Nov 21 08:18:42 CET 2013 x86_64
    [ 162.665] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=/dev/sda6 rw nomodeset quiet
    [ 162.667] Build Date: 01 November 2013 05:10:48PM
    [ 162.668]
    [ 162.669] Current version of pixman: 0.32.4
    [ 162.672] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 162.672] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 162.677] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 22 20:19:10 2013
    [ 162.679] (==) Using config file: "/etc/X11/xorg.conf"
    [ 162.680] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 162.680] (==) ServerLayout "Layout0"
    [ 162.680] (**) |-->Screen "Screen0" (0)
    [ 162.680] (**) | |-->Monitor "Monitor0"
    [ 162.680] (**) | |-->Device "Device0"
    [ 162.680] (**) |-->Input Device "Keyboard0"
    [ 162.680] (**) |-->Input Device "Mouse0"
    [ 162.680] (==) Automatically adding devices
    [ 162.680] (==) Automatically enabling devices
    [ 162.681] (==) Automatically adding GPU devices
    [ 162.681] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
    [ 162.681] Entry deleted from font path.
    [ 162.681] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 162.681] Entry deleted from font path.
    [ 162.681] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 162.681] Entry deleted from font path.
    [ 162.681] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 162.681] Entry deleted from font path.
    [ 162.681] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 162.681] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 162.681] Entry deleted from font path.
    [ 162.681] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 162.681] (==) FontPath set to:
    /usr/share/fonts/misc/
    [ 162.681] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 162.681] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 162.681] (WW) Disabling Keyboard0
    [ 162.681] (WW) Disabling Mouse0
    [ 162.681] (II) Loader magic: 0x7fdc20
    [ 162.681] (II) Module ABI versions:
    [ 162.681] X.Org ANSI C Emulation: 0.4
    [ 162.681] X.Org Video Driver: 14.1
    [ 162.681] X.Org XInput driver : 19.1
    [ 162.681] X.Org Server Extension : 7.0
    [ 162.683] (--) PCI:*(0:1:0:0) 10de:0407:106b:00a3 rev 161, Mem @ 0x92000000/16777216, 0x80000000/268435456, 0x90000000/33554432, I/O @ 0x00007000/128, BIOS @ 0x????????/131072
    [ 162.685] Initializing built-in extension Generic Event Extension
    [ 162.686] Initializing built-in extension SHAPE
    [ 162.688] Initializing built-in extension MIT-SHM
    [ 162.689] Initializing built-in extension XInputExtension
    [ 162.690] Initializing built-in extension XTEST
    [ 162.692] Initializing built-in extension BIG-REQUESTS
    [ 162.693] Initializing built-in extension SYNC
    [ 162.695] Initializing built-in extension XKEYBOARD
    [ 162.696] Initializing built-in extension XC-MISC
    [ 162.698] Initializing built-in extension SECURITY
    [ 162.699] Initializing built-in extension XINERAMA
    [ 162.700] Initializing built-in extension XFIXES
    [ 162.702] Initializing built-in extension RENDER
    [ 162.703] Initializing built-in extension RANDR
    [ 162.705] Initializing built-in extension COMPOSITE
    [ 162.706] Initializing built-in extension DAMAGE
    [ 162.707] Initializing built-in extension MIT-SCREEN-SAVER
    [ 162.709] Initializing built-in extension DOUBLE-BUFFER
    [ 162.710] Initializing built-in extension RECORD
    [ 162.711] Initializing built-in extension DPMS
    [ 162.712] Initializing built-in extension X-Resource
    [ 162.714] Initializing built-in extension XVideo
    [ 162.715] Initializing built-in extension XVideo-MotionCompensation
    [ 162.716] Initializing built-in extension XFree86-VidModeExtension
    [ 162.717] Initializing built-in extension XFree86-DGA
    [ 162.718] Initializing built-in extension XFree86-DRI
    [ 162.719] Initializing built-in extension DRI2
    [ 162.719] (II) LoadModule: "glx"
    [ 162.719] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 162.719] (II) Module glx: vendor="X.Org Foundation"
    [ 162.719] compiled for 1.14.4, module version = 1.0.0
    [ 162.719] ABI class: X.Org Server Extension, version 7.0
    [ 162.719] (==) AIGLX enabled
    [ 162.720] Loading extension GLX
    [ 162.720] (II) LoadModule: "nvidia"
    [ 162.720] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 162.721] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 162.721] compiled for 4.0.2, module version = 1.0.0
    [ 162.721] Module class: X.Org Video Driver
    [ 162.721] (II) NVIDIA dlloader X Driver 331.20 Wed Oct 30 17:16:53 PDT 2013
    [ 162.721] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 162.721] (++) using VT number 1
    [ 162.721] (II) Loading sub module "fb"
    [ 162.721] (II) LoadModule: "fb"
    [ 162.721] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 162.721] (II) Module fb: vendor="X.Org Foundation"
    [ 162.721] compiled for 1.14.4, module version = 1.0.0
    [ 162.721] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 162.721] (WW) Unresolved symbol: fbGetGCPrivateKey
    [ 162.721] (II) Loading sub module "wfb"
    [ 162.721] (II) LoadModule: "wfb"
    [ 162.721] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 162.722] (II) Module wfb: vendor="X.Org Foundation"
    [ 162.722] compiled for 1.14.4, module version = 1.0.0
    [ 162.722] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 162.722] (II) Loading sub module "ramdac"
    [ 162.722] (II) LoadModule: "ramdac"
    [ 162.722] (II) Module "ramdac" already built-in
    [ 162.723] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
    [ 162.723] (EE) NVIDIA: system's kernel log for additional error messages.
    [ 162.723] (EE) No devices detected.
    [ 162.723] (EE)
    Fatal server error:
    [ 162.723] (EE) no screens found(EE)
    [ 162.723] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 162.723] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 162.723] (EE)

  • Hi, My Macbook Air Rev A 80gb HDD isn't showing up in Disk Utilitiy (new hdd btw)

    Hey guys.. im new and this is my first post
    Recently my Macbook Air rev a 80gb original hdd was failing *S.M.A.R.T* so i knew its time for a new hdd soon anyways... then i managed to format it with disk utility one day then after that it completely stopped detecting in disk utilitiy. now got my new hdd which is exactly the same *confirmed* and well its not detecting with my macbook...
    Helllppppp meee please
    (PS. dont just comment stating the obvious i.e. try a new hdd cable as they are not cheap for a trial and error case)
    Thanks...
    Ps. i have a secondary Mac Pro to use in the meantime if this can help repair/cd boot?

    Does the new drive appear in Disk Utility?  If so then you need to prep the drive before you can use it:
    Drive Preparation
    1.  Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button.  When the menu bar appears select Disk Utility from the Utilities menu.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area.  If it does not say "Verified" then the drive is failing or has failed and will need replacing.  SMART info will not be reported  on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    When formatting has completed quit DU and return to the installer.  Complete the OS X installation.
    If the drive does not appear in Disk Utility then either the new drive is dead, you've installed the ribbon cable incorrectly, the new drive is physically installed improperly, or there is some other hardware issue.

  • HELP: MacBook Pro does not boot at all

    MacBook Pro 15" 2.5GHz 4GB RAM Serial No. W8******YK0
    Snow Leopard (with all updates)
    Yesterday when leaving my office I just closed the cover on my MacBook. When I later opened it again the front white lite was steadyly on (dim) and the computer did not react to anything.
    I tried the following:
    Long-pressed the power button to turn it off, after 10 sec. turned it on  again. Disk makes a faint noise but no more life signs. Screen stays black.
    Tried to boot from original system disk (the grey disk I). Disk spins at high rev as expected when trying to boot but then goes to a slow speed and stays like that forever. Have to shut down by hiolding down power key until power off.
    Removed power cable and battery, held power switch down for 10 sec. to reset SMC. No effect.
    Removed both RAM banks. Tried to boot without RAM. No effect.
    Tried swapping RAM banks. No effect.
    Booted with single RAM bank. No effect.
    Are there any steps I could take to get it back to life? I need the computer urgently for work (have to give two presentations the coming week which I wanted to work on this weekend). I have had time machine connected and I have a full backup of the hard disk from about a month ago.
    Any help sincerely appreciated!
    <Serial Number Edited by Host>

    Hi, Now, I am not sure if i can help you, but at least i am "glad" too see that i am not the only one with this problem. The same problem i have/had in December, so i took my Mac Book Pro after trying the same as you did to the Service, only to hear from them that i must buy a new LogicBoard, ok, i did this & it was then replaced, but after picking it up from Service 1 Month later, it was working, but only for 2 Hours, so i went back to the service again complaning about this problem, & all that i heard again from them was..." Your LogicBoard is not working, you must buy a New LogicBoard"... This i cannot not understand or accept after spending so much money for repairs, (2 Times in such a short period) After speaking with Apple, i was only told that this is not normal, & that i must go again to the Service where i was before & speak with them about it.

Maybe you are looking for

  • Camera lock screen iPhone 5S not working properly after upgrade to iOS 8.1.3

    Actually, i upgrade my iPhone to 8.1.3. What i am trying achieve is, when my iPhone is locked i just need to access my camera without login. When i open camera when my iPhone is locked, camera displays for 2 seconds and then my screen will be black.

  • Trouble booting up after HD failure - 1405-S171

    I have a Satellite laptop, model 1405-S171.  I think my hard drive just failed, but I don't seem to be able to boot up from the recovery CDs that came with my computer.  Where can I find information on how to do that?  I'm running Windows XP Home. He

  • Reducing time required for ABAP-only copyback (system copy) process

    Our company is investigating how to reduce the amount of time it takes to perform a copyback (system copy) from a production ABAP system to a QA system.  We use a similar process for all ABAP-only systems in our landscape, ranging from 3.1h systems t

  • Can't instal java

    i get this notepad message # An unexpected error has been detected by Java Runtime Environment: # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0630c77a, pid=456, tid=1552 # Java VM: Java HotSpot(TM) Client VM (10.0-b19 mixed mode, sharing windows-

  • PHOTOSHOP CS5 file saving name question (.png .jpg)

    Hi, If I open a new file and go to save it the extension names show up (.jpg or .png). However, if I open an illustrator file in Photoshop and try to save it, the extension names are not there (it's saving them as the proper format, but I want the fi