T5240 boot net issues

I have a T5240 I am installing with a Jump Start server and I cannot get it to start the install via the Jump Server. On boot right before it reaches the OK Prompt I receive an error that says:
"The following devices have been disabled: /MB/CMP1/P48-P55"
I believe that is Memory, the problem is the server has a dual stacked motherboard from what our hardware guys told us and he doesnt know which board contains CMP1 and which selection is P48 through P55.
Back to the boot issue, it took me a really long time to get the server up as it had been shut off for over a year and I was asked to do a build on it for work. I finally got Solaris 10 to install on the server, but I was unable to mount our filer or boot it from net. The system has link lights the cables are good, IPs are set correctly I have the correct MAC address. Just wondering if anybody has some insight on this.

Hi.
Regarding the disabled components, It looks like your system has some CPU Threads disabled. In order to confirm it, I suggest creating a Service Request and upload snapshot from ILOM for analysis.
click here for more information on Handling Faults on T5240 systems.
Regarding the boot issue, I believe you can post the same question to Solaris discussion groups (installation) and provide additional information regarding the steps followed and messages displayed on console after you issue "boot -net" command.
The boot device is specified by the setting of an OpenBoot configuration variable called boot-device. The default setting of this variable is disk net. Because of this setting, the firmware first attempts to boot from the system hard drive, and if that fails, from the on-board NET0 Gigabit Ethernet interface.
HTH!

Similar Messages

Problem with logical domain and boot net

Trying to install a new domain on a T2000. Able to get to "Configuring devices" but then it just sits and twirls... What have I configured wrong in the domain creation?
I have:
{0} ok show-devs
/cpu@7
/cpu@6
/cpu@5
/cpu@4
/cpu@3
/cpu@2
/cpu@1
/cpu@0
/virtual-devices@100
/virtual-memory
/memory@m0,8000000
/aliases
/options
/openprom
/chosen
/packages
-virtual-devices@100/channel-devices@200
\virtual-devices@100/console@1
/virtual-devices@100/ncp@4
/virtual-devices@100/channel-devices@200/disk@0
/virtual-devices@100/channel-devices@200/network@0
/openprom/client-services
/packages/obp-tftp
/packages/kbd-translator
/packages/SUNW,asr
/packages/dropins
/packages/terminal-emulator
/packages/disk-label
/packages/deblocker
/packages/SUNW,builtin-drivers
|0} ok show-disks
/) /virtual-devices@100/channel-devices@200/disk@0

There are a number of issues with network booting in LDOM 1.0.2, I think they affect all versions of the LDOM software though. If you add a vnet to a guest domain and then try and jumpstart a guest domain from time to time immediately after the guest domain does the RARP request it hangs. Just sending a break to the guest domain, going back to the ok prompt and starting the boot net - install again generally fixes it.
Also there are some gotcha's with LDOM's that affect jumpstart.
1) If you chose option a) harden the OS using JASS when doing the installation of the LDOM software and you have the jumpstart server on the control domain then it isn't going to work. JASS turns off things like rpcbind which will prevent jumpstart from working. The same problem affects network booting. You would think that running a jass-execute -u to undo the hardening of the o/s in the control domain would work but it doesn't and you have to start over with a fresh solaris image for the control domain. This only applies if you have your jumpstart server on your control domain.
2) Since jumpstart relies on the MAC of the client to function and since with LDOM's the MAC is dynamically assigned from a pool of address's you can end up with the wrong entry in /etc/ethers on your jumpstart server. That is worth checking.
3) Since the MAC of the virtual network device isn't the same as the MAC shown when you run banner at the ok prompt in the guest domain you can end up with the wrong entry in /etc/ethers. Either do a boot net (vnet1 whatever) and then make a note of the MAC its broadcasting or do an ldm list-bindings domainname for the guest you want to network boot and copy and paste the MAC of the virtual network you are going to be booting from.
All the regular gotcha's with net boot and jumpstart still apply with LDOM's but so do all the usual fixes. Use of snoop will allow you do debug most problems. Also using show-nets at the ok prompt in the guest domain and make sure that you have the right number of virtual networks.
Paul.

After boot net-tpe - install sparc20 loses connection

I'm trying to install Solaris 8 on a Sparcserver 20. Due to a defect cdrom, I've to use a jumstart install. The jumpstart-client (the Sparcserver 20) finds it's own ip-adress and retrieves the bootblock(?) When I use snoop on the server, I can see that everthing looks normal (see Snoop output). But right after that, the client starts complaining about "ARP/RARP send failed" (see Sparc20 messages). The 20c00 is (obviously) a counter that counts recieved data. Why is it failing? It just had a connection before... Also I can see the networkswitch blinking every 2/3 seconds when the errors begin. Does anybody has a clue? The Sparc20 is running Solaris 5.6 at this moment and has no network problems. If anybody needs more informatioin, let me know. Thanks in advance.
Snoop output:
1 0.00000 BROADCAST -> (broadcast) RARP C Who is 8:0:20:22:42:1 ?
2 0.00126 polen -> po RARP R 8:0:20:22:42:1 is 10.0.0.2, po
3 0.00214 po -> polen TFTP Read "0A000002.SUN4M" (octet)
4 0.01909 polen -> po TFTP Data block 1 (512 bytes)
5 0.00683 po -> polen TFTP Ack block 1
6 0.00015 polen -> po TFTP Data block 2 (512 bytes)
7 0.00688 po -> polen TFTP Ack block 2
8 0.00010 polen -> po TFTP Data block 3 (512 bytes)
9 0.00676 po -> polen TFTP Ack block 3
10 0.00009 polen -> po TFTP Data block 4 (512 bytes)
11 0.00677 po -> polen TFTP Ack block 4
12 0.00009 polen -> po TFTP Data block 5 (512 bytes)
truncated
461 0.00793 po -> polen TFTP Ack block 229
462 0.00013 polen -> po TFTP Data block 230 (512 bytes)
463 0.00787 po -> polen TFTP Ack block 230
464 0.00009 polen -> po TFTP Data block 231 (132 bytes) (last block)
465 0.00168 po -> polen TFTP Ack block 231
Sparc20 messages:
ok boot net-tpe - install
Boot device: /iommu/sbus/ledma@f,400010:tpe/le@f,c00000 File and args: - instal
l
Lost Carrier (transceiver cable problem?)
Twisted pair cable problem or hub link-test disabled.
Use the PROM command "help ethernet" for more information.
ARP/RARP send failed. Check Ethernet cable and transceiver.
20c00
Lost Carrier (transceiver cable problem?)
Cable problem or twisted pair hub link-test disabled.
Use the PROM command "help ethernet" for more information.

Do you have tpe link disabled???
ok printenv
look for any setting with "tpe" in it.
Halting at the 20c00 indicates that the client is
trying to resolve it's name/ip from servers /etc/hosts
file. It has completed downloading tftpboot from
server using it's mac address so it sucessfully
navigated the /etc/ethers entry.Nope. tpe-link-test? is true. Weird, isn't it? When I turn the diag-switch to true, I can see that the client receives it's ip-adress. After the tftpboot, the client should issue a whoami request to find out it's hostname (afaik) but I can't see any packets on the line after recieving the boot information. Should it try to boot or something? Beats me.

WAN boot Server issues.

I 'm getting following error while booting client from WAN boot server.
{0} ok setenv network-boot-arguments host-ip= 10.63.25.208 ,router-ip= 10.63.24.1 ,subnet-mask= 255.255.252.0 hostname=xxxxxx-u012 ,filename=http://10.63.25.180/cgi-bin/wanbnetwork-boot-arguments = host-ip= 10.63.25.208 ,router-ip= 10.63.24.1 ,subnet-mask= 255.255.252.0 hostname=essapl020-u012 ,filename=http://10.63.25.180/cgi-bin/wanboot-cgi
{0} ok boot net - install
Boot device: /pci@0/pci@0/pci@1/pci@0/pci@2/network@0 File and args: - install
Improperly formatted value for 'host-ip'
ERROR: boot-read fail

dedwards wrote:
I am having cronic issues with the WAN port reporting that it is unplugged. The Time Capsule LED is flashing amber when this happens.
When that happens do you see a tiny green light next to the WAN port socket on the Time Capsule?
You might try reversing that Ethernet cable end-for-end or trying a different cable.

X220 and z230 ThinkPad boot up issues

We have ran into the same recurring issue with the x220 and x230's. We are running windows 7 pro 64bit, and on a consistent basis we have boot up issues, were windows gets stuck after the bios. The computer needs to be rebooted several times for it to fully boot up. Our users do have docking stations as well, anyone else having this issue?

Hi
If you're hearing noises coming from the hard drive area chances are it is failing hard drive. In which case it may be possible to target disk mode to another mac and try and recover what you can using either drag/drop methods or something like DataRescue:
http://www.prosofteng.com/products/data_rescue.php
This ultimately could be a painfully slow experience. It really does depend on how 'screwed' the hard drive is? Only you can decide how important your data is and how much time you want to spend on it. There is a good possibility (if your data is absolutely vital) that a Data Recovery Specialist can recover the data for you? It can be very expensive. It all depends on what value you place on your data?
If your mac is still in Warranty you have an added dilemma. To qualify for a warranty replacement drive you have to send the drive back to Apple. Neither can you send it to the Data Recovery Specialist first and then send it to Apple. The reason being in all probability the Data Recovery Specialist will have to tamper with the drive in some way to stand a chance of recovering your valuable data. Tampering voids the warranty. Of course if you value your data higher than the cost of a new 3rd-party (cheap) or an Apple branded drive (ridiculously more expensive) then don't bother and replace the drive at your own expense.
Tony

MSI z87 g45 Boot up issues

So I built a computer for my sister and her husband and it has been having some boot up issues,Here are the computer parts:
wiindows 7 64bit
MSI Z87 G45 Gaming motherboard
INTEL CORE I-7 4770K 3.5GHZ
RADEON HD 5700 GPU
G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1866
kINGSTON 64 GB SSD ( spare part, not sure the numbers)
Sunbeam PSU-H680-REV-US 680W ATX 12V 2.0 Power Supply - OEM
Seagate Barracuda ST2000DM001 2TB 7200 RPM
ASUS Black 12X BD-ROM 16X DVD-ROM 48X CD-ROM SATA Internal Blu-ray Drive Model BC-12B1ST/BLK/B/AS
I've cleared both the HDD and SSD and now I'm looking to check the msi z87 g45 mobo, The computer starts up and sits on a2 for a while and then sometimes it fails to detect the SSD and says a0 and then I have to go back into the bios after I reset the computer again and maybe it detected the SSD and I can set it to boot from that again because it constantly changes the boot order, and sometimes it gives a blue screen when nearly into windows and then restarts, I had transferred some data from their old computer to this one and the data had virus's in it and I didnt know so I eventually found out and a day later and got rid of them all and the computer started behaving better but not fixed, faster mainly, I don't know if the virus may have altered some files so, I have a few more things to try, any help would be appreciated.
(Something I forgot to mention is that when I unplugg the HDD all the issues go away, the computer seems to work fine, But there are no issues with the hdd, ive tested it with seatools and I plugged it into my computer and restarted mant times as well as used my computer for a while and nothing, the HDD is fine, the start up on their computer sits on a2 for a long time when it isnt going to work and it only happens with the 2tb seagate HDD plugged in)

which storage drive holds the boot files the SSD or the HDD? the ATA mode of the BIOS needs to remain in the same mode it was when Windows was deployed to the storage drive. next the only way a BIOS settings will change with out user input is if the Li cell battery is going dead/the BIOS is getting reset frequently. sounds like you're about at square one, I'd format the Seagate 2TB HDD, install windows onto that either in RAID or AHCI mode whichever your preference, you can use the 64GB SSD as caching later if you use RAID mode, if AHCI the 64GB could be spare. I don't understand the SSD as boot drive method, it doesn't make sense the solid state storage is volatile meaning it degrades over time, the HDD isn't and the performance gain isn't going to change the way you use your PC. AHCI has it's advantages it's up to you. Following those steps is the only way you're going to keep the computer booting on a regular basis. You shouldn't need to manually configure which storage drive to initialize/boot from first, the BIOS automatically goes through your devices to find boot files then boots from the first one with boot files, it won't even try to boot from a device without boot files, because it can't. Just to reiterate the BSOD you speak of sounds similar to the ATA mode changing to something other than what it was when Windows was deployed to the device.

[SOLVED] Wifi won't auto connect on boot - systemd issue?

I'm using netcfg and have a working profile for a WPA wireless network. Connecting using netcfg from the terminal works reliably.
However, I can't get automatic wifi connection at boot to work. I've followed the wiki instructions on the netcfg page, but some thing isn't quite right.
Last in the post is the output from:
$ systemctl status net-auto-wireless.service
Could this be some kind of timing / starting order issue with systemd and the network-related services?
Any ideas anyone?
net-auto-wireless.service - Provides automatic netcfg wireless connection
Loaded: loaded (/usr/lib/systemd/system/net-auto-wireless.service; enabled)
Active: active (running) since Sat, 2013-01-12 20:32:01 CET; 1min 39s ago
Process: 1142 ExecStart=/usr/bin/netcfg-wpa_actiond $WIRELESS_INTERFACE (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/net-auto-wireless.service
â””â”€1323 /usr/sbin/wpa_actiond -p /run/wpa_supplicant -i wlan...
Jan 12 20:32:00 carbon systemd[1]: Starting Provides automatic netcfg wireless connection...
Jan 12 20:32:00 carbon netcfg-wpa_actiond[1142]: catland
Jan 12 20:32:01 carbon wpa_actiond[1323]: Starting wpa_actiond session for interface 'wlan0'
Jan 12 20:32:01 carbon systemd[1]: Started Provides automatic netcfg wireless connection.
Jan 12 20:32:04 carbon wpa_actiond[1323]: Interface 'wlan0' connected to network 'CATLAND'
Jan 12 20:32:04 carbon dhcpcd[1402]: version 5.6.4 starting
Jan 12 20:32:04 carbon dhcpcd[1402]: wlan0: sending IPv6 Router Solicitation
Jan 12 20:32:04 carbon dhcpcd[1402]: wlan0: sendmsg: Cannot assign requested address
Jan 12 20:32:04 carbon dhcpcd[1402]: wlan0: broadcasting for a lease
Jan 12 20:32:08 carbon dhcpcd[1402]: wlan0: send_raw_packet: Network is down
Jan 12 20:32:08 carbon dhcpcd[1402]: wlan0: sending IPv6 Router Solicitation
Jan 12 20:32:08 carbon dhcpcd[1402]: wlan0: sendmsg: Network is unreachable
Jan 12 20:32:12 carbon dhcpcd[1402]: wlan0: sending IPv6 Router Solicitation
Jan 12 20:32:12 carbon dhcpcd[1402]: wlan0: sendmsg: Network is unreachable
Last edited by 4ZM (2013-01-14 08:16:17)

For posterity: the problem seems to be that I hadn't enabled netcfg@<networkprofile>.service with systemd. I had only enabled my wired profile. I.e. doing 'systemctl enable [email protected]' fixed it.
In short this was a failure to configure netcfg startup with systemd. But hey, that makes it (drum roll...) a sysytemd issue! Like most of the problems one encounters while setting up a computer; it is a configuration issue (i.e. PEBKAC). But hey, thats what the forums are for.
@Trilby, @WonderWoofy Thank you both for your insightful, constructive and, above all, helpful comments. I hope everyone else coming to this thread for information on why their wifi won't start will find them every bit as useful as I did.

IMPORTANT Technical Information RE: 890FXA-GD70 - BIOS/Memory/Boot-UP Issues

I have been having the same problem (see my post...user 'n9nu') as many others have and I have been researching this problem for a month now and come across a few important pages on other web-sites that address this very problem. While I have not read over 100 percent of them completely, they all pertain specifically to these situations with several users being able to resolve their issue(s) with the following sources. Several of the posts mention the instability with a few of the BIOS versions (1.8 and 1.9), so read up on these as well.
TROUBLESHOOTING THE MSI 890FXA-GD70 BIOS, STARTUP AND MEMORY ERRORS/ISSUES
My currently installed BIOS: Version 1.9
Motherboard hardware revision: Version 1.1
CPU: AMD Phenom II X6 1100T
Memory: Corsair Vengeance DDR3 1066 8GB Kit
GPU: nVidia 590 Reference GPU
Overclock.net
http://www.overclock.net/amd-motherboards/724846-official-msi-890fx-890gx-890g-club.html - 'Official' 890FXA-GD70 Users Club (No affiliation with MSI)
http://www.overclock.net/amd-motherboards/770915-i-toasted-my-msi-890fx-gd70.html - Gee....a specific club for those who own dead 890's
Tom's Hardware
http://www.tomshardware.com/forum/309538-31-solved-890fxa-gd70-debug-code-load-edit-bios - BIOS FF Errors
TechArena
http://forums.techarena.in/overclocking-computer-modification/1401757.htm - FF BIOS Issues
http://forums.techarena.in/motherboard-processor-ram/1402256.htm - BIOS & Start-up issues
http://forums.techarena.in/motherboard-processor-ram/1401777.htm - Pre-Purchase Information
http://forums.techarena.in/motherboard-processor-ram/1411672.htm - Memory/BIOS Issues
http://forums.techarena.in/motherboard-processor-ram/1401689.htm - FF Errors after upgrading BIOS
NCIX Forums
http://forum.ncixus.com/forums/?mode=showthread&forum=116&threadid=2282823&pagenumber=0&msgcount=0&subpage=1 - BIOS Code 'FF' & Cycling errors (re-starting)
Computerforum
http://www.computerforum.com/179382-msi-mobo-help.html - More BIOS 'FF' issues
The above references are just several posts that discuss and in some cases alleviate problems with this motherboard. Upon trying one of the more popular methods to attempt a boot-up, I successfully booted in BIOS bypassing that rude 'FF' BIOS code....however the happiness was short lived as I configured some settings in the BIOS and when I restart was presented with the FF again.
The method I used was to place one (1) stick of DDR3 memory in memory slot 4 (the furthest away from the processor) and was kinda surprised that it worked....and while happy, I didn't hold my breath.
I have BIOS version 1.9 currently installed and have been noticing many problems with that particular release, so I will be attempting to re-flash the BIOS to either 1.7 to bypass some of the other issues being reported or try version 1.8 again. I will keep on posting when I receive further information or come across a sure fix for this (a user oriented fix that is)...otherwise, it is going back for another RMA.
I am working with someone that I know that tricks out BIOS code in order to enhance/unlock/fix them and he is presently looking at it using the exact same hardware that I am to try and find out just what the exact issue(s) are and how to resolve them. This, of course, has nothing to do with MSI, but rather an attempt by someone who programs these for a living just to see whats what.
Tim
ARS N9NU

After spending 12-14 hours on the problem i can now safely give a detailed report of the problem
Disregard what i said before as they were just symptoms of another problem
It boots 100% stable if DIMM slots 1 2 and 3 are empty
it does not matter the make or model of the ram in slot 4 but the system boots and works flawlessly.
I ran extensive tests with prime 95 and memory tests. It works flawlessly in this configuration.
As soon as a stick of ram goes into any other slot either singular or dual channel the board does a rapid boot cycle
this constant power on and off if left too long corrupts the bios settings
bios setting problem is rectified by putting one stick of ram into dimm 4 and letting it reset itself in a stable enviorment
also while the system is stable i used the MSI software to check all the voltages and everything appeared normal
However
if i make the system boot with standard memory configuration such as one in DIMM 1 or 1+2 i get odd voltage readings
(extremely unstable if im lucky enough to get it to boot)
the NB voltage quickly fluctuates between 1.15 and 1.7+ every min or so like if there are micro spikes in voltage
While this happens the 2 lights next to the slots indicating i believe the dram power phase blink
But
When i only put a ram stick into DIMM 4 only one light for the powerphase is lit and it is stable
So this so far is not a corrupt BIOS chip to me but rather a symptom of another problem
I have another CPU coming in the mail tommorow I will test it out along with a few other boards
a 1090T
2 890fxa-gd70's and some others
If i have a hardware problem it will surely be singled out
I will find out what the problem is with this board and post my result.
If anyone has any suggestions to make this board work please comment

P35 Neo 2 Fr boot up issue

Hi Guys, hope I can use some help here...
I'm having an issue that whenever I turn on my PC, My PC will keep rebooting without going into bios. No display but it's running.
After thorough checks, I notice the on-board led stuck at the Memory Detection Test before it restarts. This has never happen before until recently... I have no clue what happen to it. After unplugging the ram and put it back, it will work for the day before failing me again the next time it start.
I did a memory test and the ram is good. Could it be the memory slot issue? I hope some kind souls can direct me to the right direction.
And everytime the PC is boot up from failing, it will show this error message.
This is my setup;
Processor
Intel Core 2 Duo E8400
Mainboard
MSI P35 NEO2-FR
Graphics Card
ASUS HD4850
Memory
Kingston ValueRam PC2-6400 DDR2-800 2GB x 2
Storage
Western Digital 640GB + Western Digital 160GB
PSU
Corsair HX520W
OS
Window Xp Pro With Service Pack 3

Quote from: Jack on 16-December-10, 02:10:36
Ah, sorry, I overlooked that.
Can you please test if putting the OC Jumpers into the 333 MHz position helps?
Erm... Setting already is at 333MHZ... But error still occur...
Quote from: NovJoe on 19-December-10, 00:28:39
Do let us know on the results.
Thanks for the help seriously. Anyway, went to main office and get the board tested. They said the board passed the test. NO error was found. I was skeptical as I am experiencing the problem... They said is ram issue, I brought my ram along and they tested it too. Again, no error was found.
I wonder what caused this overclock problem issue...

Poorly MBP - Booting/Crashing Issues.

Hi Folks,
Recently my MBP has been getting more and more ill, i've spent a lot of time trying tips and tricks i've found to see if i can resolve the issue. The most odd thing seems to be that the problem only really occurs at work, when attached to an SBS2000 AD domain, at home it works fine.
The list of issues are:
1) Frequent system crashes, lots of apps stop responding and Force Quit doesn't always do so..
2) Disk Images/USB Disks don't mount... the DMG's just sit there "attaching" whereas the USB drives don't mount at all.
3) Most irritating is that i frequently have to force shut down (press and hold power button) as the apps crashing mean Finder won't actually shut down correctly. When i have to reboot most times it won't reboot properly;
a) Some times the top bar will appear, but on the right only Spotlight, no other icons and nothing on desktop.
b) Other times it will appear to have booted up fine but will actually have crashed totally, i.e. you can't click on any icons/dock.
c) Some times the Dock will appear but no desktop icons.
Invariably i will have to disconnect the Network Cable, disable the Airport and also remove the external USB HDD and eventually after a couple more attempts the machine will boot up fine....
4) Frequently the machine won't wake from sleep, i get left with a spinning beach ball of doom... I have applied the latest Firmware as i know this was an issue with early units (mine's an early model)
I've repaired disk permissions with Disk utility, run the Apple Hardware Test (came back fine) and tried lots of other little tweaks (MacJanitor etc) I downloaded a program WhatSize to see where the large files were as i was preparing to reinstall Tiger and noticed that my Entourage/Microsoft User Data Database is 22Gb! I am the SysAdmin so have a couple of Mailboxes open at once... could this rather large amount of data being sent back and forth across the network cause the problems, or are there other things i should be doing???
Please help if you can as i'm going mad
Thanks
Scott
MBP 2.0Ghz, 2Gb RAM, 100Gb 7200rpm Mac OS X (10.4.8) Parallels

This one of the many reasons I say people should move off Entourage. Here on my personal website, I explain how:
http://www.macmaps.com/entouragemigration.html
But the fact images won't mount, says that your mounting preferences or cache may be corrupted. You can try a different user to see if the problem persists there. At least that will tell you if the problem is systemwide, or localized to your user.
The fact it only happens at work, says something is wrong with the firmware of the router you use at work, or that the power supply at work may not be clean.
I would repair permissions and see if that improves matters as well. Do that with Applications -> Utilities -> Disk Utility.
Also don't use any other utility other than a backup utility, Macjanitor or Anacron. Utilities such as Cocktail, AppleJack, Onyx, Macaroni, Tiger Cache Cleaner can cause the issues you are seeing if run at the wrong time because system caches are constantly written to, and if one of those programs should interrupt the writing of those files, those can become corrupt and cause systemwide degradation of the sort you've been seeing. I've seen it happen on few people's machines. Most important is that you backup your data now, just in case these are also symptoms of a dying hard drive.

Windows 7 and boot camp issue

On an iMac a1224 I installed windows 7 then boot camp from the os disc. Bootcamp version 2.1 was installed. The current installation and set up guide suggested updating bootcamp to 3.1 however that particular update requires version 3.0. That being said, is it necessary for me to update my version 2.1?
Thanks

Leeopard huh?
You need Snow Leopard w. 10.6.x to get 3.0.
If it works and no issues fine though probably the first time I have read someone did.
BC 2.2 was more about XP and some support for Vista.

Windows 7 with Boot Camp issues

Hi,
I have a Macbook early 2008 model, with 10.5, which apparently has boot camp 2.0 installed on it. Despite this, I managed to install Windows 7 64-bit on it, without issue, until I tried to install all the bootcamp drivers for stuff like the trackpad and the function buttons. It turns out that the only way to get the drivers for 64-bit windows 7 is by updating to bootcamp 3.1, which you can't do if you have 2.0 (not totally sure about that), because the OS X cd which should install the drivers, doesnt work for windows 7 64-bit. As far as I can see, you can't download the drivers from apple without the cd, and to use the downloads you do have, I would need bootcamp 3.1, which would require purchasing snow leaopard, and completely reinstalling my entire system (which would be an enormous pain). Is there any way around this? Can I download the drivers independently? The only thing I need to be honest is two-finger right clicking, because I don't use windows much, and that is pretty essential...
Thanks in advance,
Pete

Hi Pete,
you can buy Snow Leopard for about USD 29 but you don't have to install OSX Snow Leopard in order to install the updated BootCamp Drivers from it.
Since the BootCamp Drivers are on a seperate 'partition' on the OSX DVD (better said the OSX DVD is an OSX/Windows-hybrid disc) you can just install the BootCamp Drivers from it.
Regards
Stefan

New MBP boot/sleep issues

I have a new 15" MBP and it occasionally has issues booting where it will get to the gray Apple screen and the spinning circle will freeze. Also when it has been asleep for a while (1+ hour) it will almost always freeze when trying to wakeup. If I force it to sleep or close the lid and immediately revive it, it always works. Is there anything I can try to do to diagnose the issue? I took it to the Apple store and they ran a drive repair and we couldn't reproduce the issue. It did it again on the first boot once I got home.
Thanks in advance.

Welcome to AD!
Well,
there is this Apple doc.
DALE

Maverick boot camp issues

Hello,
I am relatively new to Apple Products and I have a Mac Book Pro and I recently upgraded it from OX X 10.8.6 and I am now running OS X 10.9.1.
I had been using Boot Camp and running Windows 7. No issues.
When the Mavericks update was completed, everything was running fine on the Apple side, but my boot camp partician and ability to use boot camp is gone.
I now have a 55 GB particioned as disk 04.
When I used the boot camp utility my computer was partioned in a 650/100 GB split.
I am not sure how to proceed at this point.
Is there a way to recover my Win 7paticianed portion, or am I out of luck and I need to start all over. What is this disk 04 I am seeing on disk utitility? Can I erase it or should I?
thanks for any help that can be offered.

I am deeply sorry if anyone was offended. I did not mean yell at anyone. I just wanted to state the most important paragraph as summary. When I have to yell at someone, I put all the text in capitals and bold and also with exclamation mark at the end. But anyway, thanks for the clarification.
Finally, I solved the problem by returning to the old system leopard.

A Few Boot Camp Issues

I just set up a new Boot Camp partition (XP SP2), didn't have these issues previously:
1. When I get to the desktop I get a window asking me to insert the CD labeled "iSight Installation Disk #1". Not sure why and don't really care if iSight works or not under Boot Camp as I barely use it anyway.
2. The keys illuminate when the laptop boots up, is there any way to keep that from happening or do I have to manually shut if off every time?
3. The num lock is switched on when I boot to Windows, how can I have it shut off by default?
Appreciate any help. THANKS!

Mitchell, you will find it productive to post this question in the Boot Camp section of the discussions. You will find it listed under discussions down the left side listed under Windows Compatible Technology. Good luck with finding your solution.

T5240 boot net issues

Similar Messages

Maybe you are looking for