[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.

Similar Messages

  • Crashing on start up on MacBook Pro had no trouble...

    Crashing on start up on MacBook Pro had no trouble until 03-10-15
    OS Version:            Mac OS X 10.10.2 (14C1510)
    Report Version:        11
    Anonymous UUID:        FDA4D1C5-18C3-DF9C-CC74-768C8C114969
    Time Awake Since Boot: 3400 seconds
    Crashed Thread:        6  Dispatch queue: SKFullTextIndexer text indexing queue
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:      KERN_INVALID_ADDRESS at 0x0000000000000008

    I'm having the same issue -- it started early this week. Using Skype 7.6.409. Immediate crash on startup. I can't even log in.
    Incident Identifier: 404C9849-CF51-4A77-97C7-EEE9217B3CB1
    CrashReporter Key: 22255918-4759-B086-00C9-78A539C25B51
    Hardware Model: MacBookPro11,1

  • My macbook pro takes a long time to start up, my macbook pro takes a long time to start up

    my macbook pro takes a long time to start up, my macbook pro takes a long time to start up

    up to 10 mins

  • (Trouble printing) Trouble with connection between Macbook Pro and Hp Deskjet 1510.

    Trouble with connection between Macbook Pro and Hp Deskjet 1510. (Nothing Prints).
    I have a Macbook Pro and am having difficulty printing documents from ‘Pages' from my Hp Deskjet 1510. I have installed the necessary software for the printer and it is connected via USB. Every time I try to print the printer icon comes up as it should, 'printing' and then 'job completed' and then the icon disappears. (Nothing is printed.) I thought it might be something to do with Pages compatibility with the printer but exporting the document to Word or making it a PDF doesn’t change anything. I don’t have Microsoft Word on my computer. The scanner does work and when I printed a ‘Test Page’ that worked too.
    Let me know if you know why this is happening.

    With these settings the network now works flawlessly, however, when i have my ethernet cable plugged in, my internet access via my airport card(on the macbook pro) is no longer available. Hoping you can tell me why this would be with this info i've provided.
    Educated guess. The networking devices have priorities as to which are used. The standard order is that Ethernet has a higher priority than Airport.
    While your Ethernet is unplugged it is inactive and the Mac ignores it. Once you plug it in, the Mac sees that it is active and switches traffic to that interface.
    I actually take advantage of this feature at home, but configuring my Airport and Ethernet with identical fixed IP addresses. Normally I'll use Airport, but if I'm copying a huge file and I want faster performance, I'll just walk my MacBook (previously iBook, previously Powerbook) over to my Ethernet switch and plug in my MacBook. Magically, the Mac detects that the Ethernet is active and continues the file transfer uninterrupted over the faster 100baseT Ethernet connection. When the transfer is finished, or if I really need to move back to the Comfy Chair, I unplug the Ethernet cable, and all activity reverts back to the Airport, all without disrupting any existing networking connections.
    You on the other hand have totally different settings for your Ethernet and your Airport, so when you switch to Ethernet, you basically loose your Airport connections.
    Something you can try:
    System Preferences -> Network
    Gear icon on the bottom left, next to the [+] [-] icons.
    Select *Set Service Order...*
    Now Drag the network interfaces into the perfer priority order you want. In this case put Airport above Ethernet.
    NOTE: You may want to create a new Network Location for this, instead of messing with your normal home Location (which is most likely the default Automatic. That way you have your original you can always fall back to.

  • Hi, I have problem with starting up my macbook pro, the gray screen coming and the circle still turning

    hi
    Could u please help me with the problem that I have with starting up my macbook pro?

    Reinstall OS X without erasing the drive
    Do the following:
    1. Repair the Hard Drive and Permissions
    Boot from your Snow Leopard 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. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Reinstall Snow Leopard
    If the drive is OK then quit DU and return to the installer.  Proceed with reinstalling OS X.  Note that the Snow Leopard installer will not erase your drive or disturb your files.  After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
    Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.

  • Boot from time machine to start up my macbook Pro?

    Can I boot up from my time machine to start up my macbook pro with 10.7.5? I have not been able to start up from my diskWarrior 4.4 disk in order to rebuild my hard drive, and I did not get a 10.7 system disk when I bought my computer. Also, if I can, how do I do it?

    If the time machine backup was made from your Mac with 10.7.x install on it yes toy can boot from it. Connect the backup drive to the Mac and power it on. Hold down the Option key and a boot menu screen willl come up. Select the backup drive, it might be label Recovery HD or Whatever you called the drive when you formatted it.
    Once that loads, which is a copy of the built ion Recovery HD files you can use disk utility to do maintance and do all the other things you can do with disk utility and then you can restore your system from that backup.

  • Everytime I start up my MacBook Pro, I get this message.  'Insecure Startup Disabled.'  "/Library/Startup items/HP Trap Monitor" has not been started because it does not have the proper security settings.

    Everytime I start up my MacBook Pro, I get this message.  'Insecure Startup Disabled.'  "/Library/Startup items/HP Trap Monitor" has not been started because it does not have the proper security settings.

    Update your HP Printer drivers/software at their website or uninstall using the developers method.

  • When I started up my macbook Pro after a boat trip (just lying in my bag the whole time) it started making weird sounds. Why does it do that and how do I stop it?

    When I started up my macbook Pro after a boat trip (just lying in my bag the whole time) it started making weird sounds. Why does it do that and how do I stop it?

    The 13" retina MBP has two fans, left and right near the hinge and about 2.5" each from the edges of the case.
    My conjecture is that one of the fans may be failing.  An appointment at an Apple store genius bar is the best option.  The evaluation will be FREE and a fan replacement (if that is the problem) should not break the bank account.
    You might run an Apple Hardware Test:
    http://support.apple.com/kb/PH11342
    This may confirm my suspicion or perhaps find a different problem. Note that an error free result should not be viewed as being definitive.
    Ciao.

  • On starting up, my macbook pro shuts down after 25 seconds of booting up.

    Hi there. On starting up, my macbook pro shuts down after 25 seconds of booting up. The time bar comes on for a while before it simply goes blank and switches off without any notification. Battery iappears charged. Could it be a virus? Help please!! O

    Reinstall Lion, Mountain Lion, or Mavericks without erasing drive
    Boot to the Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Repair
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu.
    Reinstall Mountain Lion or Mavericks
    OS X Mavericks- Reinstall OS X
    OS X Mountain Lion- Reinstall OS X
    OS X Lion- Reinstall Mac OS X
         Note: You will need an active Internet connection. I suggest using Ethernet
                     if possible because it is three times faster than wireless.

  • Why would a picture of a globe pop up when I start up my macbook pro?

    I started up my macbook pro, and instead of the Apple logo popping up while the computer loaded, a picture of a flashing globe had popped up. I ended up shutting the computer off and then turned it back on and it loaded up as normal. I was just curious if this was something i should be worried about..? i've only had my macbook for about 2 weeks, and it's my first time with a mac computer. Please help!

    That is a sigfn that either the Online Apple hardware test is starting or that you are booting from the Online Recovery HD system. Both are from the Apple web servers.

  • I have trouble shutting down my MacBook Pro using the normal way.

    I have trouble shutting down my MacBook Pro, operating Mac OS X Snow Leopard. I click on the "Shut Down" button from the Apple Menu, the screen fades to blue and I get a scrolling wheel; this lasts up to more than two hours and I still don't get any result, so I end up holding down the Power Button until it turns off. Can somebody help me, please?

    Make sure you quit all your applications before shutting down.
    And try resetting the SMC.
    Intel-based Macs: Resetting the System Management Controller (SMC)

  • Trouble with a new MacBook Pro - times 3 now..

    Hi all,
    Trouble Trouble Trouble - my frustrations with Apple:
    1) MacBook Pro -bought 19th nov 2009- Death On Arrival, 4HDD/11/40000004:SATA(0,0)
    Been sent back to Apple and I got a new one.
    New MacBook Pro -got it on the 25th nov 2009- Started to have random Kernel Panic's 2nd of November:
    2) Kernel Panic's everywhere.. even on the Mac Bootdisc with Disk Utility.. as random as they appeared, so random they went away. Just to be sure on the Apple helpdesk they advised me to cleaned disk and reinstalled everything. Lucky I made a back-up when it was still working.... otherwise I'd have lost everything.
    3) Worked well for 2 or 3 days and now -6th dec 09- all the sudden it doesn't want to start anymore. Giving me 9 beeps at start-up on a black screen in the morse code s.o.s. 3x short, 3x long, 3x short)
    Apple?
    I'm sure when I call Apple tomorrow I'll have to bring away my notebook to an Apple Service Provider cause they can't help me on the phone. If so, I will have to wait for another 20 days(experience in the past with my bro's MacBook for a new harddisk(!)).
    I used to be a PC-guy and took the brave step to be a full-time Apple-guy, but this is just frustrating me. Sold my old laptop and now I'm without one for ages.
    What would my options be? Could I get a complete new notebook?
    Niek

    Giving me 9 beeps at start-up on a black screen in the morse code s.o.s. 3x short, 3x long, 3x short)
    Sounds like bad RAM:
    http://support.apple.com/kb/HT2341?viewlocale=en_US
    Or bad power.
    Have you attempted to change the power supply or power source? If it isn't plugged into a surge protector, you may have issues with your house power that create problems for multiple computers.
    Also, be sure you aren't damaging the power cable unintentially*:
    http://www.macmaps.com/frayguide.html
    This is a user to user board.
    Call Apple directly at:
    (31) 0900 7777 703
    And let them know your repeated issues. They could give you a replacement machine, but also ask for a replacement power brick to at least test the theory the power brick may be damaged.
    - * Links to my pages may give me compensation.

  • Itunes has started crashing on macbook pro.

    itunes has started crashing everytime I launch it on macbook pro. have followed advice in earlier posts and removed ibooks by putting it in trash, emptied trash and restarted. but problem remains.
    i updated to 11.2.1  itunes a couple of days ago, and updated to OSX11.9.3 at the same time.
    Itunes hasnt worked since

    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Step 1
    For this step, the title of the Console window should be All Messages. If it isn't, select
    SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
    View ▹ Show Log List
    from the menu bar at the top of the screen.
    In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if iTunes crashed, you would enter "iTunes" (without the quotes.)
    Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    ☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    ☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
    Step 2
    In the Console window, select
    DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
    (not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
    I know the report is long, maybe several hundred lines. Please post all of it anyway.
    ☞ If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
    ☞ Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

  • [SOLVED] Extremely Slow Wireless on Macbook Pro

    SOLVED (Hopefully forever.)
    Problem: The b43 and bcma kernel modules do not get along. You'd never know this with kernels up to 3.2.14, as bcma is not automatically loaded and it is not needed with b43. For recent kernels however, it is. It in turn destroys wireless internet speeds.
    Solution: The broadcom-wl driver. It used to be portrayed in the Wiki as being something to avoid, but that has changed recently. It offers a better connection and much faster speeds, but can take a little bit more effort to set up. Just a bit.
    Broadcom-wl Installation and Setup
    1. Install broadcom-wl from the AUR.
    2. Uninstall b43-firmware if it's installed.
    3. Note what broadcom-wl has put into /etc/modprobe.d. These blacklistings will ensure no interference from other kernel modules. Also make sure you're not blacklisting `wl` or its friends, if you have been.
    4. Don't reboot yet. Go to /sys/class/net and use the command:
    udevadm info -a -p /sys/class/net/<yourdevice> | grep address | tr [A-Z] [a-z]
    (of course replacing <yourdevice> with the names of your interfaces - probably eth0 and wlan0) This will tell you their MAC addresses. Write these down!
    5. Go to /etc/udev/rules.d/ and create a file called 10-network.rules. We are going to make custom udev rules so that our interfaces are matched to their proper names at boot time. Here is a template:
    SUBSYSTEM=="net", ATTR{address}=="aa:bb:cc:dd:ee:ff", NAME="net0"
    SUBSYSTEM=="net", ATTR{address}=="ff:ee:dd:cc:bb:aa", NAME="wifi0"
    Enter the MAC addresses (in lower case!) and give them names in the NAME field. Apparently it's a good idea to choose new interface names, different from the default eth0 and wlan0. My file looks like this:
    SUBSYSTEM=="net", ATTR{address}=="58:b0:35:f6:45:0c", NAME="wired0"
    SUBSYSTEM=="net", ATTR{address}=="f8:1e:df:ea:99:17", NAME="wifi0"
    6. Go change ANYTHING that had references to the old interface names. I had to change my rc.conf, as well as settings in my wicd preferences so that it knows what names to look for.
    7. Rebuild your kernel image with
    sudo mkinitcpio -p linux
    (you might not have to do this, but it couldn't hurt.)
    8. Save this page. Yes, the html. This is so that you still know what to do in case of problems and no internet.
    9. Reboot and enjoy your restored wireless internet.
    ---- ORIGINAL POST ----
    Seems everybody and their grandmothers are having internet problems since 3.3.
    On a Macbook Pro, kernel 3.3.2-1.
    Here is my problem: http://i.imgur.com/AcqLM.jpg
    I made that image before checking the forums, but now that I've looked around I suspect the kernel.
    Put up with it until 3.3.3? Or regress?
    Last edited by fosskers (2012-08-31 13:00:28)

    @fosskers:
    Sry, I just told KDE to disable it
    @all:
    /proc/net/wireless looks pretty bad:
    Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE                                                                                 
    face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22                                                                                 
    wlan0: 0000   70.  -38.  -256        0      0      0    514      2        0
    After measuring this, I just got kicked out (again):
    [ 1072.839997] ieee80211 phy0: wlan0: No probe response from AP 4c:e6:76:22:4f:33 after 500ms, disconnecting.
    Now it even refuses to reconnect. This is a full "enable wireless - try connect - fail"-cycle:
    [ 1698.359901] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
    [ 1698.560136] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1721.394168] wlan0: authenticate with 4c:e6:76:22:4f:33
    [ 1721.420074] wlan0: send auth to 4c:e6:76:22:4f:33 (try 1/3)
    [ 1721.422002] wlan0: authenticated
    [ 1721.423411] wlan0: associate with 4c:e6:76:22:4f:33 (try 1/3)
    [ 1721.426883] wlan0: RX AssocResp from 4c:e6:76:22:4f:33 (capab=0x411 status=0 aid=1)
    [ 1721.426886] wlan0: associated
    [ 1721.428216] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 1729.470178] wlan0: deauthenticated from 4c:e6:76:22:4f:33 (Reason: 2)
    [ 1729.473907] cfg80211: Calling CRDA to update world regulatory domain [...]
    [ 1730.674444] wlan0: authenticate with 4c:e6:76:22:4f:33
    [ 1730.700199] wlan0: send auth to 4c:e6:76:22:4f:33 (try 1/3)
    [ 1730.702446] wlan0: authenticated
    [ 1730.703423] wlan0: associate with 4c:e6:76:22:4f:33 (try 1/3)
    [ 1730.706988] wlan0: RX AssocResp from 4c:e6:76:22:4f:33 (capab=0x411 status=0 aid=1)
    [ 1730.706997] wlan0: associated
    [ 1738.740963] wlan0: deauthenticated from 4c:e6:76:22:4f:33 (Reason: 2)
    [ 1738.748937] cfg80211: Calling CRDA to update world regulatory domain [...]
    [ 1739.954181] wlan0: authenticate with 4c:e6:76:22:4f:33
    [ 1739.980222] wlan0: send auth to 4c:e6:76:22:4f:33 (try 1/3)
    [ 1739.982773] wlan0: authenticated
    [ 1739.983401] wlan0: associate with 4c:e6:76:22:4f:33 (try 1/3)
    [ 1739.987077] wlan0: RX AssocResp from 4c:e6:76:22:4f:33 (capab=0x411 status=0 aid=1)
    [ 1739.987086] wlan0: associated
    [ 1746.001760] wlan0: deauthenticating from 4c:e6:76:22:4f:33 by local choice (reason=3)
    [ 1746.015596] cfg80211: Calling CRDA to update world regulatory domain [...]
    Sometimes it does not find any networks at all (iwlist wlan0 scan shows nothing)
    Again, everything was fine with kernel < 3.4. (downgrading helps).
    Maybe I should start compiling some kernels myself and search the regression with a bisection...

  • On start up, my MacBook Pro will just go dark and shut down. It clicks but does not chime. What's happening?

    My MacBook Pro on start-up with just go dark and shut down. It makes a clicking or popping sound but there is no chime or other typical Mac sound. I can push the power button again and it will generally power up. It is becoming more frequent with time.
    i recently had it in the Apple Store for repair... some cola was spilled on the keyboard.  They replaced the keyboard and through a series of circumstances replaced the logic board, case, and superdrive. 
    About a week or two afterward it started the odd start-up failure. At first only once every few days. Now almost daily. It concerns me.  I relay on this old Mac for work and even thought I use TimeMachine, it would be quite a hassle to have to replace it.
    Anyone have any idea what's going on?

    Try these first:
    http://support.apple.com/kb/HT3964
    http://support.apple.com/kb/HT1379
    reset the SMC and NVRAM

Maybe you are looking for