Can't boot with zfs root - Solaris 10 u6

Having installed Solaris 10 u6 on one disk with native ufs and made this work by adding the the following entries
/etc/driver_aliases
glm pci1000,f
/etc/path_to_inst
<lang pci string for my scsi controller> glm
which are needed since the driver selected by default are the ncsr scsi controller driver that do not work in 64 bit.
Now I would like to create a new boot env. on a second disk on the same scsi controller, but use zfs instead.
Using Live Upgrade to create a new boot env on the second disk with zfs as file system worked fine.
But when trying to boot of it I get the following error
spa_import_rootpool: error 22
panic[cpu0]/thread=fffffffffbc26ba0: cannot mount root path /pci@0,0-pci1002,4384@14,4/pci1000@1000@5/sd@1,0:a
Well that's the same error I got with ufs before making the above mentioned changes /etc/driver_aliases and path_to_install
But that seems not to be enough when using zfs.
What am I missing ??

Hmm I dropped the live upgrade from ufs to zfs because I was not 100% sure it worked.
Then I did a reinstall selecting to use zfs during the install and made the changes to driver_aliases and path_to_inst before the 1'st reboot.
The system came up fine on the 1'st reboot and did use the glm scsi driver and running in 64bit.
But that was it. When the system then was rebooted (where it made a new boot-archive) it stopped working. Same error as before.
I have managed to get it to boot in 32bit mode but still the same error (thats independent of what scsi driver used.)
In all cases it does pop the SunOS Relase banner and it do load the driver (ncrs or glm) and detects the disks in the correct path and numbering.
But it fails to load the file system.
So basically the current status are no-go if you need to use the ncrs/glm scsi driver to access the disks with your zfs root pool.
File-Safe works and can mount the zfs root pool, but that's no fun as server OS :(

Similar Messages

Can't boot with install disk

I ran out of disk space on the Mac HD and I only have 452 MB left. Before, I had 12 GB. I think trying to connect a router swallowed up the GB.
Anyway, because I ran out of disk space, I had trouble starting the Mac HD.
I can open Bootcamp (XP Professional) and have no problem there.
I attached the dvd drive to the MacBook Air and put the Snow Leopard Install disc inside and tried
1) Option start
2) Pressing C key start
3) Option command shift delete start but none of them work.
I cannot get it to boot with the Snow Leopard install disc.
What can I do?
I was planning to do a clean install but can't boot with the Snow Leopard install disc.
Can I do it from Bootcamp?

I booted with the Snow Leopard Install disk and checked Disk Utility and found that the HD disk was corrupted. This time it showed only 77MB free space even though I freed up 2 GB using 'rm' commands in single-user mode.
The problem was some kind of virus or something that not only ate up free space but corrupted the system.
I had to do a clean install (erasing the Mac HD volume and formatting it) to get the Mac HD operational again.

After installing Win7, I created an 3a. partition and now I can't boot with Win7

After installing Win7 with success, I created an other data partition and now I can't boot with Win7 anymore. What can I do?
Thanks!
Vernon

Thanks, hatter! But I´m new in the Mac World and that´s greek for me. I have no idea about what is BCDedit, GPT, EFI, etc... I went to your bookmarks and found many discursions there. I selected 5 that the subject looks useful for me (https://discussions.apple.com/thread/3543804, https://discussions.apple.com/thread/3477901,
https://discussions.apple.com/thread/3360787, https://discussions.apple.com/thread/3354587 and https://discussions.apple.com/thread/3199099) but, as a tipical windows user, a really new mac user and a non-american (I don´t speak English well), it´s impossible to me to understand all this.
Do you know any "how to" in this forum or i any other part of the Internet where explain step-by-step what a dummy needs to do to recover the acess to the Windows partition (my primary objective) and create an third partition (FAT32) for data acessible for both OS?
Thank you very much!

Solaris 10 with zfs root install and VMWare-How to grow disk?

I have a Solaris 10 instance installed on an ESX host. During the install, I selected a 20gig disk. Now, I would like to grow the disk from 20GB to 25GB, I made the change on VMWare but now the issue seems to be Solaris. I haven't seen anything on how to grow the FS in Solaris. Someone mentioned using fdisk to manually change the number of cylinders but that seems awkward. I am using a zfs root install too.
bash-3.00# fdisk /dev/rdsk/c1t0d0s0
Total disk size is 3263 cylinders
Cylinder size is 16065 (512 byte) blocks
Cylinders
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 Active Solaris2 1 2609 2609 80
This shows the expanded number of cylinders. but a format command does not.
bash-3.00# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 2607 alt 2 hd 255 sec 63>
/pci@0,0/pci1000,30@10/sd@0,0
Specify disk (enter its number):
Any ideas?
Thanks.

That's the MBR label on the disk. That's easy to modify with fdisk.
Inside the Solaris partition is another (VTOC) label. That one is harder to modify. It's what you see when you run 'format' -> 'print' -> 'partition' or 'prtvtoc'.
To resize it, the only method I'm aware of is to record the slices somewhere, then destroy the label or run 'format -e' and create a new label for the autodetect device. Once you have the new label in place, you can recreate the old slices. All the data on the disk should be stable.
Then you can make use of the space on the disk for new slices, for enlarging the last slice, or if you have a VM of some sort managing the disk.
Darren

Live Upgrade fails on cluster node with zfs root zones

We are having issues using Live Upgrade in the following environment:
-UFS root
-ZFS zone root
-Zones are not under cluster control
-System is fully up to date for patching
We also use Live Upgrade with the exact same same system configuration on other nodes except the zones are UFS root and Live Upgrade works fine.
Here is the output of a Live Upgrade:
bash-3.2# lucreate -n sol10-20110505 -m /:/dev/md/dsk/d302:ufs,mirror -m /:/dev/md/dsk/d320:detach,attach,preserve -m /var:/dev/md/dsk/d303:ufs,mirror -m /var:/dev/md/dsk/d323:detach,attach,preserve
Determining types of file systems supported
Validating file system requests
The device name </dev/md/dsk/d302> expands to device path </dev/md/dsk/d302>
The device name </dev/md/dsk/d303> expands to device path </dev/md/dsk/d303>
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
Comparing source boot environment <sol10> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
The device </dev/dsk/c0t1d0s0> is not a root device for any boot environment; cannot get BE ID.
Creating configuration for boot environment <sol10-20110505>.
Source boot environment is <sol10>.
Creating boot environment <sol10-20110505>.
Creating file systems on boot environment <sol10-20110505>.
Preserving <ufs> file system for </> on </dev/md/dsk/d302>.
Preserving <ufs> file system for </var> on </dev/md/dsk/d303>.
Mounting file systems for boot environment <sol10-20110505>.
Calculating required sizes of file systems for boot environment <sol10-20110505>.
Populating file systems on boot environment <sol10-20110505>.
Checking selection integrity.
Integrity check OK.
Preserving contents of mount point </>.
Preserving contents of mount point </var>.
Copying file systems that have not been preserved.
Creating shared file system mount points.
Creating snapshot for <data/zones/img1> on <data/zones/img1@sol10-20110505>.
Creating clone for <data/zones/img1@sol10-20110505> on <data/zones/img1-sol10-20110505>.
Creating snapshot for <data/zones/jdb3> on <data/zones/jdb3@sol10-20110505>.
Creating clone for <data/zones/jdb3@sol10-20110505> on <data/zones/jdb3-sol10-20110505>.
Creating snapshot for <data/zones/posdb5> on <data/zones/posdb5@sol10-20110505>.
Creating clone for <data/zones/posdb5@sol10-20110505> on <data/zones/posdb5-sol10-20110505>.
Creating snapshot for <data/zones/geodb3> on <data/zones/geodb3@sol10-20110505>.
Creating clone for <data/zones/geodb3@sol10-20110505> on <data/zones/geodb3-sol10-20110505>.
Creating snapshot for <data/zones/dbs9> on <data/zones/dbs9@sol10-20110505>.
Creating clone for <data/zones/dbs9@sol10-20110505> on <data/zones/dbs9-sol10-20110505>.
Creating snapshot for <data/zones/dbs17> on <data/zones/dbs17@sol10-20110505>.
Creating clone for <data/zones/dbs17@sol10-20110505> on <data/zones/dbs17-sol10-20110505>.
WARNING: The file </tmp/.liveupgrade.4474.7726/.lucopy.errors> contains a
list of <2> potential problems (issues) that were encountered while
populating boot environment <sol10-20110505>.
INFORMATION: You must review the issues listed in
</tmp/.liveupgrade.4474.7726/.lucopy.errors> and determine if any must be
resolved. In general, you can ignore warnings about files that were
skipped because they did not exist or could not be opened. You cannot
ignore errors such as directories or files that could not be created, or
file systems running out of disk space. You must manually resolve any such
problems before you activate boot environment <sol10-20110505>.
Creating compare databases for boot environment <sol10-20110505>.
Creating compare database for file system </var>.
Creating compare database for file system </>.
Updating compare databases on boot environment <sol10-20110505>.
Making boot environment <sol10-20110505> bootable.
ERROR: unable to mount zones:
WARNING: zone jdb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/jdb3-sol10-20110505 does not exist.
WARNING: zone posdb5 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/posdb5-sol10-20110505 does not exist.
WARNING: zone geodb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/geodb3-sol10-20110505 does not exist.
WARNING: zone dbs9 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs9-sol10-20110505 does not exist.
WARNING: zone dbs17 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs17-sol10-20110505 does not exist.
zoneadm: zone 'img1': "/usr/lib/fs/lofs/mount /.alt.tmp.b-tWc.mnt/global/backups/backups/img1 /.alt.tmp.b-tWc.mnt/zoneroot/img1-sol10-20110505/lu/a/backups" failed with exit code 111
zoneadm: zone 'img1': call to zoneadmd failed
ERROR: unable to mount zone <img1> in </.alt.tmp.b-tWc.mnt>
ERROR: unmounting partially mounted boot environment file systems
ERROR: cannot mount boot environment by icf file </etc/lu/ICF.2>
ERROR: Unable to remount ABE <sol10-20110505>: cannot make ABE bootable
ERROR: no boot environment is mounted on root device </dev/md/dsk/d302>
Making the ABE <sol10-20110505> bootable FAILED.
ERROR: Unable to make boot environment <sol10-20110505> bootable.
ERROR: Unable to populate file systems on boot environment <sol10-20110505>.
ERROR: Cannot make file systems for boot environment <sol10-20110505>.
Any ideas why it can't mount that "backups" lofs filesystem into /.alt? I am going to try and remove the lofs from the zone configuration and try again. But if that works I still need to find a way to use LOFS filesystems in the zones while using Live Upgrade
Thanks

I was able to successfully do a Live Upgrade with Zones with a ZFS root in Solaris 10 update 9.
When attempting to do a "lumount s10u9c33zfs", it gave the following error:
ERROR: unable to mount zones:
zoneadm: zone 'edd313': "/usr/lib/fs/lofs/mount -o rw,nodevices /.alt.s10u9c33zfs/global/ora_export/stage /zonepool/edd313 -s10u9c33zfs/lu/a/u04" failed with exit code 111
zoneadm: zone 'edd313': call to zoneadmd failed
ERROR: unable to mount zone <edd313> in </.alt.s10u9c33zfs>
ERROR: unmounting partially mounted boot environment file systems
ERROR: No such file or directory: error unmounting <rpool1/ROOT/s10u9c33zfs>
ERROR: cannot mount boot environment by name <s10u9c33zfs>
The solution in this case was:
zonecfg -z edd313
info ;# display current setting
remove fs dir=/u05 ;#remove filesystem linked to a "/global/" filesystem in the GLOBAL zone
verify ;# check change
commit ;# commit change
exit

U410 - Can't boot with Win 8.1 OR Ubuntu

Hi-
I have been trying to fix a dual-boot issue with Win 8.1 and Ubuntu, and I've totally screwed up my boot record. I was advised to look at the instructions below, and it might help me straighten out my boot situation. After following these directions, I can no longer boot into anything now.
Here's what I did:
This also may be part of the issue as Windows and UEFI copy between themselves.
Remove Duplicate Firmware Objects in BCD and NVRAM
http://technet.microsoft.com/en-us/l...=ws.10%29.aspx
I followed the directions outlined above, and now I can't do anything. When I start it up, it boots into Windows Boot Manager with a single entry for Ubuntu. When I selected that, it gives me the usual warning that it can't find the .efi file or .mbr file. The (really) bad part is that I can't get to the UEFI Firmware Setup (i.e., the old BIOS menu), so I can't boot from a USB - I'm stuck. When I boot it up, it does flash for a split second, almost like it goes to another screen (the UEFI menu?), but then goes into the Win Boot Mgr.
Does anyone have any ideas as to how to get into the UEFI firmware settings? I've tried to hit F12 (and every other F* combination) during boot, but it still just flashes for a second, and then goes into Windows Boot Manager. If I could get to the UEFI settings, I could boot from USB into a Windows rescue/rapair USB device, but I can't get to it at a moment, so I'm in limbo.
If anyone has any suggestions, it would be muchg appreciated, as I'm stuck and can't do anything.
Thanks,
Nipper
Moderator Note; subject edited.

Hi,
I don't even see a loss rates in the pathping result you provided before. and it shows "Computing statistics for
0 seconds", this is really strange, have you pasted the full pathping result here? Or as I mentioned before, you can try to pathping your own ip as a test. What is the result if we use other tool, simple like ping to Google website? Make sure
to install latest driver for network adapter, reset router, get latest firmware for router.
Yolanda Zhu
TechNet Community Support

Can't boot with the Leopard disk

Hi,
I upgraded to 10.5.7 from 10.5.6 and after 2 or 3 reboots and I can't get to leopard (I only see a blue-screen that does not dissappear). I reset everything, but I still can't boot into Leopard. To make things worse, I am trying to boot from the Leopard disk to do a clean install and fix that problem, but I can't because it also gets through the blue-screen and never dissappears. How can I make the Mac to boot into Leopard disk 'cause I've been like 2 or 3 days trying to figure it out.
Also...Can I fix this using target mode and formatting the HD with another mac?
Thanks in advance.

HEy!!
Finally, after a nightmare I could succesfully restored my Mac!!!.
I was really desperate, so, after talking to a friend who knows this stuff very well, he told me that all that was left before taking it to the Apple Store was to do some maintainance with it. He told me to buy Drive Genius 2.0 and run every single maintainance tool the software had. So I did it, and magically I could boot into Leopard and reinstall the OS again1!!!!. Even I could fix some video-graphics problems that I had.
All of these because I upgraded to 10.5.7. Right now I'm running perfectly fine with 10.5.4.
Thank you guys for helping me out!!. If you have this problem you could try Drive Genius and maybe you can get out of trouble easily!!
Message was edited by: Neonrx07

Boot from second hard drive with ZFS in Solaris 10 x86

Hi,
The usual menu.lst to boot Solaris10 x86 with a boot environment that contains a ZFS boot loader is this one
title Solaris 10 5/08 s10x_nbu6wos_nightly X86
findroot (pool_rpool,0,a)
kernel$ /platform/i86pc/multiboot -B $ZFS-BOOTFS
module /platform/i86pc/boot_archive
title Solaris failsafe
findroot (pool_rpool,0,a)
kernel /boot/multiboot kernel/unix -s    -B console=ttyb
module /boot/x86.miniroot-safeI understand that to add an alternate boot disk, I have to play with installgrub and then attach it in the pool.
But my question is : Is there a way to boot from my alternate hard disk by adding a new entry in menu.lst or is the only
way is to modify the BIOS parameter?
Thanks for your help,
Groucho_fr

Groucho_fr wrote:
Thanks for your answer Alan,
But ok, I imagineI can add a grub entry. But what I want to know is what is the exact way to boot from an alternate hard disk on Solaris 10u6
x86.AFAIK there are only two ways to do this. Select the disks via BIOS which becomes a royal PITA in a short amount of time or play with a boot manager such as GRUB until you get the syntax right.
Personally I put all OS's on the primary disks if possible to avoid these situations and if I have others to play with then you can easily mount them in or set them up as D: drive etc...
The only exception would be in an enterprise setting where you need to do things such as mirroring but then again in those situations it's only one OS per machine anyways so it's much easier.
So at the end, I am not sure what I have to configure and what is the procedure to boot from my alternate boot diskTry the grub homepage for the grub manual and hopefully for a mailing list or try a search engine.
http://docs.sun.com/app/docs/doc/819-5461/zfsboot-1?a=view
has an example to follow of using -B.
And moreover, the installgrub does not working for me :
root@mac1 # zpool status
pool: rpool
state: ONLINE
scrub: resilver completed after 0h2m with 0 errors on Thu Mar 26 10:56:24 2009
config:
NAME          STATE     READ WRITE CKSUM
rpool         ONLINE       0     0     0
mirror      ONLINE       0     0     0
c5t0d0s0 ONLINE       0     0     0
c5t4d0s0 ONLINE       0     0     0
errors: No known data errors
root@mac1 # installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c5t4d0s0
cannot open/stat device /dev/rdsk/c5t4d0s2
You shouldn't need to do an installgrub if you installed Solaris. Try c5t4d0s0 not s2.
alan

[solved] Can't boot with LVM and usb external disk

I successfully installed Archlinux on my first computer, using LVM on two internal Hard Drives.
I'm trying to do exactly the same on my second computer, but I got a problem: the LVM volume is not found at boot, so that the root partition can't be mounted and the boot fails.
The only difference is that, on my second computer, the second hard drive is connected through USB.
Some hints: my second computer boots perfectly with LVM and Ubuntu. Archlinux needs to be configured adequately.
I tried to add rootdelay=30 in menu.lst, but it changes nothing. Of course, in /etc/rc.conf I have USELVM="yes" and in /etc/mkinitcpio.conf I have HOOKS="base udev autodetect pata scsi sata keymap lvm2 filesystems"
Thank you for helping me to keep Archlinux on my second computer!
Last edited by Achille (2008-06-29 21:59:09)

I finally solved my problem!
In the file /etc/mkinitcpio.conf, I modified the MODULES loaded:
MODULES="pata_acpi ata_generic ata_piix usbcore usb_storage uhci_hcd ehci_hcd sg scsi_mod sd_mod dm_mod"
I also add in the file /lib/initcpio/hooks/lvm2 the line /bin/sleep 10
/bin/sleep 10
msg "Scanning logical volumes..."
And finally, I ran the command:
mkinitcpio -p kernel26

10 update 6 - Jumpstart with ZFS root

Please help me to solve the problem with jumpstart and root on zfs in update 6:
On server:
#grep pool profile
pool zfs all auto auto auto
...ok, but on a client:
#/sbin/install-solaris
...<skip>...
ERROR: Field 1 - Keyword "auto" is invalid
Solaris installation program exited.
The manuals says that this keyword is appeared in the Update 6 (10/08).
What's wrong?
Thanks.

Is it possible that someone could elaborate on the solution a little more? I copied the check file from the 10_08 DVD to no avail. The Solaris install root is 10/08 and I've correctly updated the solaris_media_locations file, but I still get this error. I cannot find a mention of the word "pool" in my profiles, but of course, I am using "rpool".
ERROR: Field 1 - Keyword "pool" is invalid
Solaris installation program exited.
Thanks,
E.R.

MSI A88XM GAMING | Can't boot with new PCI-e x1 card plugged in

Hi,
I'm a owner to an MSI A88XM GAMING motherboard and I purchased a AverMedia Live Gamer HD card last week. After unboxing and installing the card to one of my PCI-e x1 slots the computer won't boot. All what happends is what the fans starts and the power LED turns on, but that's all. No beeps or anything.
I know for sure what the AverMedia Live Gamer HD card is working just fine, as I've already tested it on my old computer. I've also tested if it might have been a power issue, by disconnected everything and running it on a towel outside the case, still the same result. Connecting it to any of the other 3 PCI-e ports gives the same result. All the PSU cables are properly connected and the motherboard has the latest BIOS version on it.
Is there any way to get it to work on my computer? I would really like to avoid switching motherboard is possible. Using a 2:nd computer is also not an option, as I want to be able to just take it with me without any issues.
My Computer
Motherboard: MSI A88XM GAMING
CPU: AMD A10-7850K
RAM: Kingston HyperX Beast 2400MHz 2x8GB
GFX: XFX R9 280X 3GB DD Black
SSD: Samsung 840 EVO 500GB
Case: BitFenix Prodigy M Black
PSU: Corsair 760W (don't remember the model)
OS: Win 8.1 Pro x64

Quote from: jfreiman on 15-October-14, 16:54:29
Well, someone is doing something with the BIOS because they sent me 1.2B6 a couple weeks ago for the same 88XM GAMING motherboard -- and it didn't fix my Display Port issues. Maybe the changes were to the PCIe timings?
I didn't want to test any more 1.2 beta builds, due to earlier problem with them. But I'll give the final build of v1.2 a try later today, I didn't notice what it had been released.
Quote from: Alcifer on 18-October-14, 01:47:13
Out of curiosity, have you tried the video output from the motherboard, instead of the 280x, when you have card installed? (Make sure the IGP is enabled in bios)
That was one of the very first things I tried, did so after my 2:nd post on the forum. You can find the results here: https://forum-en.msi.com/index.php?topic=183220.msg1315289#msg1315289
I've contacted the AverMedia Support, hopefully they should be able to find the issue. It's possible what it might be a firmware related issue.
I've also searched around on the XSplit forum if there's anyone else what have run into the same problem. But couldn't find anything, so I made a thread and asked directly instead. I got a reply from someone on the Support Staff, but he couldn't find anything either.

Can you boot with Windows XP from an external drive?

Just curious really. If you have Windows XP on a bootable external drive, I know other PCs can boot from it, but can a Mac?

On a G5 or other PPC Mac, the answer is no (unless you count running XP with VirtualPC). On the Intel Macs, it's a different story, although I have no idea if they support booting from an external drive with Boot Camp.

Removed bootcamp now can only boot with option

I recently removed my windows xp on a bootcamp partition....now when I reboot the imac, I get a message that says there is no bootable drive....use installation discs....
If I power up with my remote's menu button held, it starts like bootcamp used too but only shows the mac HD....and it boots fine in that case.....I think some remnant of the original bootcamp wasn't removed....How can I fully remove it?

Open the Startup Disk pane of System Preferences and select the Mac OS X system.
(41522)

Can't boot with wireless adaptor installed

Hi all,
I've had a problem for several years with this; I'm finally getting around to dealing with it now.
I have a Pismo G3, OS X 10.4.8, and I've never been able to get the machine to recognize a wireless adaptor (both a RaLink USB one I just bought, and a D-Link DWL-650X before) if the adaptor was plugged into the laptop when it powered up. The only way to make it work is to boot the machine without the adaptor installed, then plug in the device (either the PC card or the USB device) after I'm in the finder. In fact, with the former PC card, if I didn't remove the card at startup, the OS would NEVER see the card; at least with the USB adaptor, I could pull it out and put it back in after startup and it would still work.
There's got to be a way to make this work; because I had the problem with two different cards, and two different drivers, using two different interfaces, I'm thinking it has something to do with the hardware/firmware of the Powerbook itself.
I would even be happy if someone could just give me a script that I could set to run at startup that would just cause the USB port to THINK that it got a device plugged into it (some kind of "re-scan the ports). The device itself is getting power - I can see the light on it, and the other USB devices that are plugged in at startup (like the printer) work fine.
Any suggestions?

BigBoote66,
Welcome to the Discussions.
This is not an uncommon problem with the black G3 powerbooks although I cannot say it is universal; there is just not a large enough base of complaints on these boards to say none of the WiFi cards avoids this problem. My Wallstreet refuses to boot to either 9.x or 10.x with the Buffalo 54Mbps card. Some Pismo owners have to insert the WiFi PC card during a certain phase of the boot to get the card to work. This all appears to be related to the firmware contained on the PC card.
I might suggest this: Call OWC and speak to a technician about the Sonnet Aria Extreme...ask if this particular card avoids your issues. This is a well-regarded, natively-compatible WiFi card which uses the Broadcom chipset. OWC also used to sell the Buffalo AirStation, the card I use, but recent, subtle changes in its firmware introduced the startup problem.
http://eshop.macsales.com/item/Sonnet%20Technology/G54CB/
Possibly someone will also post here with the name of a fully compatible card.
Message was edited by: jpl

P7N Diamond - Can't boot with 4GB Ram (no picture)

I wonder if there's any settings I need to modify in order to make my system to work with 4 gigs of ram (4x1GB) ?
Is there any known issues I should be aware of?
I really appreciate any help I can get!

Sorry about the lack of info, I tend to rush things when I get frustrated.
I bought two kits at the same time, as far as I know they are identical. I haven't played around with the BIOS apart from adjusting the voltage to 2.1 (which didn't improve the situation)
It does boot fine with two sticks, as well as three.
Any BIOS settings that comes to mind?
Let me know if you need more info!

Can't boot with zfs root - Solaris 10 u6

Similar Messages

Maybe you are looking for