2.6.33 Kernel Macbook not booting

Hi All,
I installed Arch linux on macbook based on the instructions in the wiki. It went ok with 2.6.30 Kernel. But when I did a system upgrade and restarted, system seems to go blank after the "Waiting for udev events" step.
I can confirm this is a problem with 2.6.33 kernel, since I am facing the same issue if I attempt to install using an ftp mirror (Thus getting latest kernel during install).
Any pointers on this? Or is there a way to get some debug logs somehow for posting here?
Thanks for your time.
Regards,
Prabhu

timmahcheese wrote:
Yup, it was an issue with the intel driver and KMS. You can fix this by initializing KMS before the kernel is bootstrapped by udev. Follow this link:
http://wiki.archlinux.org/index.php/Int … Setting.29
Thanks for that. This did the trick. Mine is a 2007 model. I have some issues with trackpad but will raise it separately.
Cheers.

Similar Messages

[SOLVED] Kernel will not boot. No early hooks, nothing...

I am having some serious trouble getting my machine to boot. It never even gets to ":: running early hooks (udev)."
I normally shut it down every night, but I recently kept in on for a few days straight. I was having some trouble with a USB flash drive being read-only in Windows 8 in VirtualBox. I shut down Windows 8 and then arch wouldn't even read the flash drive. I'm pretty sure that pacman updated the kernel since I last shut down the machine, so I decided to restart just for good measure. I never got back in...
I am UEFI booting, running LVM on top of LUKS on top of two Samsung 830 256GB SSDs in mdadm raid 0. I have encrypted root and no swap. I have /boot mounted on a 512MB FAT32 partition and use a straight efibootmgr entry to start the system. It has worked fine until today.
My mkinitcpio.conf has
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are run. Advanced users may wish to specify all system modules in this array.
MODULES="ahci dm_mod dm_crypt aes_x86_64 raid0"
# BINARIES
# This setting includes any additional binaries a given user may wish into the CPIO image. This is run last, so it may be used to override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
## ORIGINAL ##HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck"
HOOKS="base udev autodetect sata mdadm usbinput keymap encrypt lvm2 filesystems fsck shutdown"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
My kernel parameters are
cryptdevice=/dev/md1:RootVault root=/dev/RootArray/VolRoot ro rootfstype=ext4 init=/bin/systemd add_efi_memmap initrd=initramfs-linux.img
I can boot fine from the Arch install media via UEFI at which point I can luksOpen, activate the lvm volumes, mount everything, and chroot in like normal. I have:
rebuilt the initramfs
reinstalled linux, mkinitcpio, and udev
erased and recreated the efibootmgr entry
tried to boot straight from the UEFI shell
slimmed down to minimal hooks in mkinitcpio
tried nomodeset and mem=4G kernel parameters
tried booting the kernel with debugging enabled at various levels
I get nothing at all every time. I boot up to a black screen with a static white cursor in the top left.
I am happy to offer any more necessary information and I would be extremely grateful for any suggestions. Thanks.
Last edited by matthew02 (2012-11-02 15:14:46)

lesto wrote:
same problem here with a stock kernel. solver rolling back to 3.6.3-1 by livecd.
seems a problem with AMD cpu. solution here https://bbs.archlinux.org/viewtopic.php?id=151686
I had just rolled back my kernel and was about to comment here that it worked when I saw your post. I had actually skimmed that other post, but since mem=4G didn't work for me, I didn't figure it applied. I suppose I should have read it more thoroughly. Thanks for the help everyone!

MAC Mini A1176 (MA607B/A) Kernel Panic / Not Booting

Hello,
I have a mac mini MA607B/A 1.66/2x1GB/60GB HDD, that is not booting. It Chimes and hands on the apple logo.
I searched this forum and I performed every solution I found. The mac is still doing the same thing.
I also changed the battery but no joy.
I inserted the CD that came with the MAC mini and it does exactly the same while booting from the cd.
I did a H/W check by holding the CMD+D keys and all tests were passed successfuly !!!
I booted in Verbiose mode and I have attached the log as a photo in this thread.
I really have no clue why it gives a kernel panic on CPU...
Temperature seems to be normal and the fan is working.
Any suggestions how to resolve this?

Hi,
Thank you for your reply.
I tried to boot in Open Firmware mode but it crashes almost imediately.
I have also Installed OSX 10.6 on an external usb hard drive of mine and tried to boot from that and it does exactly the same. I noticed that the external hard drive's light is on and binking while the computer is loading which means that it reads OS files. and after a while when the MAC freezes, the light goes completely off like there is no power supplied to it.
It does exactly the same thing even if i put the original disc that came with it and try to boot from that.
I entered Verbose mode again and now it always freezes after the "AppleIntelCPUPowerManagementClient: Ready" line
Also the keyboard is not responding and the lighs of the keyboard are off as well.

Macbook not booting up so I resorted to Disk Utility...it has been stuck on "updating boot support partitions for the volume as required"

So my Macbook was not booting up so I resorted to using Disk Utility...it has been stuck on "updating boot support partitions for the volume as required" for over two days.
Has anyone else had to wait this long?
I have read that I should leave it until I get another message but I saw this reply on another site....
"Hi everybody, the message: “Updating boot support partitions for the volume as required.“ means: the Disk Utilities is telling you what it is doing: 'Disk Utilities': "(I'm) Updating boot support partitions for the volume as required (& I'm done with it)." So when you see this message, the DS (Disk Utilities) is done & you can close the application"...
Any advice/tips would be greatly appreciated!

Doesn't have to be another MacBook - any Mac with FireWire (400 or 800) will do. FW 400 to 800 adapters or adapter cables should be available from any computer store.
Instructions for FWTDM -
Disconnect all other FireWire devices from both computers before you use FireWire target disk mode. Do not connect any FireWire devices until after you have disconnected the two computers from each other or have stopped using target disk mode.
To use FireWire target disk mode
    1.    Make sure that the target computer is turned off.
    2.    If you are using an Apple portable computer such as a PowerBook or MacBook as the target computer, plug in its AC power adapter.
    3.    Use a FireWire cable to connect the target computer to a host computer. The host computer can be powered on.
    4.    Start up the target computer and immediately press and hold down the T key until the FireWire icon appears. The hard disk of the target computer should become available to the host computer and will likely appear on desktop. (If the target computer is running Mac OS X v10.4 Tiger, you can also open System Preferences, choose Startup Disk, and click Target Disk Mode. Restart the computer and it will start up in Target Disk Mode.)
    5.    When you are finished copying files, locate the target computer's hard disk icon on the desktop of the host computer and drag it to the Trash or choose Eject (or Put Away) from the File menu.
    6.    Press the target computer's power button to turn it off.
    7.    Unplug the FireWire cable.
(extract from http://support.apple.com/kb/HT1661)

Macbook not booting, faint ticking noise?

Hi there, I'm hoping you guys can give me a few pointers here. I have a mid 2007 black 13" Macbook that I have been having problems with. There have been two previous issues which may or may not be related.
Over the last three years, this Macbook has eaten through five HDD's. After finally getting fed up of this, I wondered if perhaps somehow I was to blame, maybe without realising I was putting it down on the desk a bit too hard or something, so when the most recent failure came, (approx six months ago) I bit the bullet and bought myself an SSD and all now seems to be well on the storage front.
Around the same time as the first HDD failure, came random shutdowns, without warning, what appeared to be complete power failures. I also noticed the X symbok in the battery indicator. These initially were fairly frequent but eventually subsided, along with the X symbol, but always seemed to rear up again, in times a heavy use, and were more often than not followed by HDD failure.
Now, the current issue is that yesterday, I started experiencing these power failures again, hoping to myself, I turned the machine back on. Upon logging in, the fan spun up to max, so, checking activity monitor, I found that spotlight indexing, was taking up 148%CPU and this seemed to be the cause of the shutdowns.
I left the machine to cool down for a few hours, booted it up, let spotlight finish indexing, and all was well for about 3 hours. Then came another shutdown.
This time, there was a reluctance to boot. The DVD drive made its usual noise, the sleep light glowed on, and then everything died. I tried again, same result, I tried a third time, and was greeted with the all to familiar, 'no boot media' icon (Folder with ?? flashing). Frustrated at the possible death of my SSD I turned the machine off and let it be.
Later on, I gave it one last try, hoping beyonnd hope, and lo and behold, it booted with no problem. When I logged in, I noticed the 'X' in the battery indicator once more, and spotlight started indexing again, fearing this would cause more shutdowns, I temporarily disabled indexing via terminal. All was well for a couple of hours, I turned my machine off, and went to bed.
I came down this morning, tried to turn on my Macbook, nothing. Tried again, still nothing. magsafe is plugged in w/ green light, battery shows full charge with or without magsafe plugged in, then I heard a faint ticking noise from the machine, on the logic board somewhere while the power button was pressed. it's somewhere around the 'W' on the keyboard. I have read that it could possibly be a shorted inductor on the logic board. Is there any chance it could be something a little more replaceable?
I'm hoping against hope here, as if it is the logic board, it may be time to retire the old beasty.
Cheers in anticipation,
A

I was indeed looking into getting a mainboard for my old MacBook. I found a place where I was told, they will order it and replace it for me... the 'piece' never came to its destination ... after being almost 4months without computer, I decided to make the plunge and got a new one. After thinking, even if you found a 'reclaimed one' it may solve your problem just temporarly. If I were you, I would rather make a downpayment and get a financing on a new machine - you will be good to go for at least 6 or 7years again (with the new technology). Now, if you do not want to 'loose your money' you may wanna consider to resell your Device after a 1y1/2 or 2year, which permits you to get money back and stay 'in' the iDevices.

[SOLVED] Kernel will not boot after update to 3.1.5

Not sure what went wrong here. Pacman seemed to hang when updating, so I CTRL-C'd it and restarted the upgrade. It seemed to complete properly. That was a few hours ago and I did not immediately reboot the computer but went on with my work instead. After rebooting the laptop I get this
***normal boot up to this :
Running Hook [uresume]
resume libgcrypt version: 1.5.0
resume: Could not stat the resume device file '/dev/sda4'
Please type in the full path name to try again or press ENTER to boot the system: _
Pressing ENTER at this point results in mean looking error message :
ERROR : Unable to determine major/minor number of root device '/dev/sda4'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]# _
**typing exit**
Trying to continue (this will most likely fail)...
mount: you must specify the filesystem type
You are being dropped into an emergency shell
sh: can't access tty: job control turned off
[ramfs /]# _
Did I somehow ruin my install or is there something I can do?
EDIT : Oh and it can still boot the windows partition, so it's not likely due to defective hardware.
Last edited by bolshevik (2011-12-16 14:31:19)

bolshevik wrote:
Not sure what went wrong here. Pacman seemed to hang when updating, so I CTRL-C'd it and restarted the upgrade. It seemed to complete properly. That was a few hours ago and I did not immediately reboot the computer but went on with my work instead. After rebooting the laptop I get this
***normal boot up to this :
Running Hook [uresume]
resume libgcrypt version: 1.5.0
resume: Could not stat the resume device file '/dev/sda4'
Please type in the full path name to try again or press ENTER to boot the system: _
Pressing ENTER at this point results in mean looking error message :
ERROR : Unable to determine major/minor number of root device '/dev/sda4'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]# _
**typing exit**
Trying to continue (this will most likely fail)...
mount: you must specify the filesystem type
You are being dropped into an emergency shell
sh: can't access tty: job control turned off
[ramfs /]# _
Did I somehow ruin my install or is there something I can do?
EDIT : Oh and it can still boot the windows partition, so it's not likely due to defective hardware.
If you foolishly interrupted the initramfs creation after a kernel upgrade and didn't regenerate it manually, you earned this.
You'll need to find a live CD so you can chroot to your install and rerun mkinitcpio.

Macbook not booting (after i screwed it all up)

Hi guys!
I'm coming here for guidance because apparently I can't do things properly on my own. here's the story, I hope you'll get me out of there!
I recently tried to dualboot my macbook with an old version of Ubuntu: 10.04 Lucid Lynx. yes, I specifically wanted this version (and yes, it'll come down to bootcamp later on). So i installed rEFIt and my dual boot and everything semmed ok, at least on the boot side of things. I couldn't get Lucid Lynx to work properly with my macbook though, I had trouble with the keyboard and more importantly with the network devices. To solve that later problem, a google search showed that i needed a more recent verion of ubuntu, which I didn't want.
Considering this, and especially the fact that I didn't feel like fighting with the machine in command lines while having a badly configured keyboard, I finally decided to remove ubuntu and install a dualboot with win7 instead, from where I'd use a lucid lynx VM to do what i wanted to do.
Here's where it gets tricky...
In order to install win7, i neede first to have my HD back to a single partition. I used gparted from the live cd to do delete all existing non osx partitions, and then disk utility from OSX to expand the mac partition to the whole free space. Hurray to that, it worked just fine. but after that, i followed the bootcamp procedure, and then... it all went wrong. namely, i couldn't install windows because it said something like this: "Windows cannot be installed on this disk. The selected disk of the GPT partition style". I tried cleaning the partition with windows's tool but it didn't work better... And after that, i couldn't boot on anthinganymore. "No bootable device" it says. there's stuff on my mac partition i'd like to have back, so if there is another solution than re-installing osX from scratch that's be great!
And if anyone knows how i could install that win7 without running in the same error once I get osX set up again, that'be greatly appreciated!
Thank you in advance!
Rouli

Hi Dan,
You won't see any apps in iCloud.com.
Actually, what you're describing is a feature that's been available prior to iOS5 launch, even though the cloud icon is used. You can download from the cloud previously purchased (from iTunes) apps and music to your iDevice. For music this doesn't cover anything you've added, but that will change (I believe) if you've signed up for Match.
For apps, go to the App Store on your device and select Updates. At the top of the Updates screen, you should have "Purchased" as selectable. This will give you an option to see ALL apps, as well as ones that are not on your device. If you pull down on the screen, it will reveal a search box, making it easier to find an app. Click on the cloud icon and enter your password to begin downloading.
Similar steps for music in the iTunes store. Instead of going to Updates, go directly to Purchased and you can download Music AND TV shows.
Hope this helps

MacBook not booting after RAM upgrade

I'm sorry if the case has been already posted.
Yesterday I took my MacBook Alu unibody late 2008 to a RAM upgrade (from 2 to 4gigs) to an offical Mac Reseller. They installed it and showed me that the system loads properly and recognized the new RAM.
I took it home, started working on After Effects and Photoshop and when i wanted to check a video on Quicktime, this program refused to boot.
Then photoshop freeze and after effects did so. I quited all aplications and restarted. On restart after the 'bong' i've got the grey screen white an apple logo and a loading bar underneath, that was it, it never finished loading but shutting down.
After the 2nd try the computer gave me the BAD RAM alarm signal right before the start button was pressed and nothing more. I just managed to start it ONCE on safe mode, but this one also freezed and colapsed.
Today i didn't get the BAD ram alarm but the grey screen and loading bar after shutting down.
I took it back to the reseler, the shop boss who did the upgrade wasn't there , the guys on the morning shift placed the old RAM back resulting the same. So they told me it's a software problem, not hardware and might be caused by a failed firmware update or something i did wrong and since i was showed that the system booted after the upgrade i can't complain or argue that they did somethiing wrong.
So basically the want 80euros to check what's wrong with my computer plus the 120 i already payed them for a RAM that doesn't work and of course the repair cost of the computer.
On monday i'll go to talk to the boss, what do you guys recomend me to tell him? i'm frustrated that the guys there treat me like if i broke my computer for beeing stupid and wanted to get it fixed for free, when it clearly broke after they did something wrong on it!
please advice me!
thanks!
Message was edited by: finn bell

What brand is the RAM? From what you said, it is obvious that the RAM is at fault. I would simply tell them that it is not compatible and return the RAM.
Check the System Profiler to see what it says about the RAM (Apple Logo - About this Mac - More Info) and run this application to test the RAM:
http://www.memtestosx.org/joomla/index.php
If either shows any errors, print out the results and take them with you to the store.

Custom kernel does not boot.

Hi all, I recently changed to a laptop HP Pavilion G4, I installed Arch Linux and it works perfect, but I want to compile my own kernel to optimize the system a bit more.
I compiled a kernel in Gentoo sometimes, but I have no arch problems, I used the traditional method of compilation and all good, but I have a simple problem starting.
The kernel runs in "initramfs loading" and nothing happens, do not get errors or anything like that.
This is an image of what I have in /boot and /usr/lib/modules:
http://ompldr.org/vaDY0ZA/image.png
In case you wondered if you think the initramfs with mkinitcpio:
mkinitcpio -k 3.2.9-custom -g /boot/initramfs-compiled.img
And kernel config:
General setup --->
[*] Initial RAM filesystem and RAM disk (initramfs/initrd) support
The grub I think I have it configured correctly, these are the lines of the default kernel and the kernel compiled.
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-5de5f584-af2b-47ff-84d6-c7adf842892f' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 5de5f584-af2b-47ff-84d6-c7adf842892f
else
search --no-floppy --fs-uuid --set=root 5de5f584-af2b-47ff-84d6-c7adf842892f
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=5de5f584-af2b-47ff-84d6-c7adf842892f ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Arch GNU/Linux, with Linux compiled' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-compiled-true-5de5f584-af2b-47ff-84d6-c7adf842892f' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 5de5f584-af2b-47ff-84d6-c7adf842892f
else
search --no-floppy --fs-uuid --set=root 5de5f584-af2b-47ff-84d6-c7adf842892f
fi
echo 'Loading Linux compiled ...'
linux /boot/vmlinuz-compiled root=UUID=5de5f584-af2b-47ff-84d6-c7adf842892f ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-compiled.img
I appreciate any help

But you are not going to achieve a faster boot by eliminating modules that are not going to be used/loaded anyway. I can see a faster boot being achieved if you were compiling in order to eliminate the need for an initramfs, but it seems taht you are still using one anyway (besides, there are advantages to having and initramfs). The modules you don't use will simply take up disk space, udev probes your hardware and only applies what you need.
Also if you think about the time you will save with your boot relative to the time it takes to configure and compile the kernel, it is not really worth it. Say you only take compilation into account and it takes five minutes. Then say that results in an amazing 2 second decrease in boot time. It would take 150 boots to make that compilation worth the time. Then with Arch's rolling release model, you will likely have a kernel update long before you ever get there.
I think a better idea might be to simply optimize what goes in your initramfs. Falconindy made this blog post (reluctantly it seems) about just that. I tried it before I started using device-mapper functions (which then require a bunch more stuff), and it actually made a noticeable difference. The beauty of this is that the configuration will stay consistent between kernel versions, and will automatically be built after every kernel update.
Edit: Also, you really should check out the CK kernel, as graysky has made it so damn easy its ridiculous. And it is pretty functionally amazing.
Last edited by WonderWoofy (2013-01-25 01:42:01)

Macbook not booting - big problem - please help!

Ok, here's my story.
The macbook was re-formated, and was working fine. Software updates followed and firmware update as well. It completed well and the computer was running flawlessly for a day or two.
After beeing shut down, it doesn't want to boot anymore.
When i turn it on, it stays on the gray screen with the apple logo and it loads. Before OS X turns one, it shuts down.
I have already tried all the troubleshooting that the help section offers (reset ram, check battery, reset power management etc...)
I called Apple on the phone, the first guy suggested that i restore the firmware using the firmware restore disk that is available on their site. The computer refused to boot the CD. It also refused to boot from Mac OS X installation disk.
I'm really out of options here.
The second time i called, they told me they couldn't much unless i paid, since the warranty is expired.
Any suggestions will be greatly appreciated. Hopefully i won't have to send it for repairs, because i'm on a tight budget.
Thank you very much.
Joey
[email protected]

welcome to macbook forum.
insert your installer disk #1, restart and press alt/option and it will give you all option to boot from.
if it only shows you to boot from installer disk system folder, that might be the sign that your HD is failed.
or you can insert installer disk #1, restart and press C to boot right away from the isntaller dsik.
after select the language, open utilities from menu bar and select utility / and check if your hd is mounted (on the left portion), if it mounted, choose repair disk and reboot (you might need to re-install the OS X if the system folder corrupted). But if it didn't shows up, then it might be failed as suspected.
Since your warranty is already expired, you can consider to get a new HD yourself and install that HD and OS X yourself (cheaper than using apple genius guy at apple store).
Good Luck.

Upgrade kernel beyond not booting anymore

Hi
upgraded with pacman -Syu without paying much attention to the output I guess. I had the beyond kernel. After a reboot I get the following error:
Unpacking Linux .. Ok, booting kernel
Initial ramdisk loading Modules ...
BUG: unable to handle kernel paging request at virtual address 0002005c
eip:
*pde=000000
Oops:0000[#1]
PREEPTXMP
Modules in : ide_cd
it's possible that I copied some of the output incorrectly, since I did it by hand.
Any suggestions would be welcome.
Thank you

Use Arch install cd to go back in & fix problems
check lilo/grub, mkinitcpio.conf ...
HTH

MacBook not booting up, stuck on blue screen

I just got my MacBook and a friend of mine who is quite experienced with Macs had it for the weekend just to look at and play with... I got it back and it isn't booting up. The grey Apple screen comes up, the little spinning line-circle shows up, then it goes to the blue screen that usually comes before the "Starting up Mac OS X" screen, but it stays blue and the fan spins up and no progress is made and the process cant be broken without force shutting down the computer. If it is necessary to erase the hard drive and reinstall Tiger, I can do that, as my data is backed up... but what would I do?

Try a PRAM reset...
http://docs.info.apple.com/article.html?artnum=2238
and/or an SMC reset...
http://docs.info.apple.com/article.html?artnum=303319
Failing this, start up from your Install DVD and run Disc Utility to repair/verify the permissions and the drive itself.

Macbook not booting up with hard drive in optical bay

I have a SSD in the main bay and have my stock Toshiba 500GB 5400RPM installed in the optical bay with a hard drive caddy. When I boot up I get stuck at the White Apple scrren with the spinning dotted wheel or it boots up to the desktop and my mouse and keyboard freezes. Has anyone else experienced this problem or have a resolution? I tried two separate hard drive caddys and two separate hard drive thinking these might be the problem with no luck. Please help I'm getting really frustrated with this problem and would love to start using the hard drive in the optical bay. Thanks in advance!

This is considered a "hardware hack" outside of Apple guidlines and unfortuntly not really addressed in this forum or by many members really.
However I can point you into the correct direction of Dave Merten (aka "Bmer) of the Mac Owners Support Group as he has done such a hardware hack and best can tell you how to fix your particular issue
http://macosg.com/
Good luck.

Macbook not booting up! Hard Disk???

I have a "Week 1" MacBook and today, when I picked it up to surf the net, when I clicked Safari, it just hanged for about 3 minutes. After the 3 mins, I gave up and forced turned off the computer (holding down the pwr button until it's off.) When I tried rebooting...I hear a click, coming from what sounds like the hard drive and it doesn't boot up. All I get is a folder with a question mark on it.
I get the feeling the hard drive crashed but its a 7 month old computer!!! To add insult to injury, I take care of this computer like it's my baby!!! What the heck???
Any thoughts? Anyone else had this problem???
Eric

If there is a clicking coming from the bottom right side as you use the MB, then it is the HD.
Clicking HDs are bad, bad, bad.
It could be a disk corruption, but the clicking makes me think it is the drive itself. The good news is that it would be covered under the standard warranty, but if it id the drive and it needs replacing, Apple will keep that drive and you will lose all the data on it unless you have a backup.

MacBook not booting up. SSD card not working. What to do?

I have been informed by a technical consultant that the SSD card for my MacBook Air is faulty and needs to be replaced. Does my warranty cover this replacement. I bought the system in may 2013. Also what is the process of replacement if it is covered.
Thanks.

Youre within warranty yes.
I assume youve already contacted Apple since theyve diagnosed it already.
The process is another SSD is ordered, they take the bottom plate off your Air pop out bad, put in new,....takes just a few mins for the mechanical replacement.

2.6.33 Kernel Macbook not booting

Similar Messages

Maybe you are looking for