Jump to content

nawcom

nawcom

Member Since 09 Oct 2006
Offline Last Active Today, 12:03 AM
*****

Posts I've Made

In Topic: AOS NUC?! What is this guy doing?

16 March 2017 - 10:42 PM

My guess is they just have Ozmosis installed which is what AOS used from what I remember. You can install it into a number of motherboards' UEFI firmware, Haswell motherboards included. It takes away the need to install disk-based UEFI bootloaders like Clover. They're just using the AOS label to sell their stuff.

That case isn't anything special either - it's a Habey EMC-600BL designed for standard mini ITX boards. You can buy it from a number of online stores.

In Topic: Disk you inserted is not readable by this computer.

11 March 2017 - 12:23 AM

using /etc/fstab to prevent automounting still works in Sierra. In fact I use that myself to prevent automounting certain NTFS partitions in Sierra. However just like on any unix system, the fstab file is used to set automounting parameters for filesystems that it supports.

The error you're getting is as far as I know something you can't get rid of via some DiskArbitration setting or anything like it and as long as OS X lacks an ext4 filesystem driver, or for any unsupported filesystem for that matter, you'll get the nag once you enter the desktop. I dealt with this when I had a disk with an unsupported filesystem on it and just lived with that annoying error.

Luckily you can install ext4 support. In Sierra your choice is either fuse-ext2 which supports ext4 through FUSE for macOS, or Paragon ExtFS which is commercial. With ExtFS, getting it to use the filesystem drivers while removing the Trial nag is of course something that can't be discussed here, but it's possible.

I use Paragon ExtFS and preventing automounting works fine. Find the Volume UUID either through Disk Utility or command line diskutil. Since mine is disk1s1 I used
nawcoms-MacBook-Pro:~ nawcom$ diskutil info /dev/disk1s1
   Device Identifier:        disk1s1
   Device Node:              /dev/disk1s1
   Whole:                    No
   Part of Whole:            disk1

   Volume Name:              Untitled
   Mounted:                  No

   Partition Type:           Linux
   File System Personality:  UFSD_EXTFS3
   Type (Bundle):            ufsd_ExtFS
   Name (User Visible):      Extended Filesystem 3

   OS Can Be Installed:      No
   Media Type:               Generic
   Protocol:                 USB
   SMART Status:             Not Supported
   Volume UUID:              9485E394-BB0A-B841-054A-175E2A94002E

   Disk Size:                31.3 GB (31259656192 Bytes) (exactly 61054016 512-Byte-Units)
   Device Block Size:        512 Bytes

   Volume Total Space:       0 B (0 Bytes) (exactly 0 512-Byte-Units)
   Volume Available Space:   0 B (0 Bytes) (exactly 0 512-Byte-Units)

   Read-Only Media:          No
   Read-Only Volume:         Not applicable (not mounted)

   Device Location:          External
   Removable Media:          Removable
   Media Removal:            Software-Activated
Note: even though it mentions ext3 this is very much ext4.

Here's the line that I'm using in /etc/fstab:
UUID=9485E394-BB0A-B841-054A-175E2A94002E	none	ufsd_ExtFS	ro,noauto
And as a result it does not automount. Without this fstab line, it automounts.
 
So there you have it. Your choices are either:
  • Don't install ext4 filesystem support and deal with the nag, or
  • Install ext4 filesystem support and prevent it from mounting at boot. But to be honest, if you can mount it (read-only by default) why not leave it be?

In Topic: HP XW8400 Lion install problem

10 March 2017 - 04:15 PM

The recovery DVDs did full installations of the OS X version that originally came preinstalled with the Mac. Its only limitation was a Mac Model check that was done in the OSInstall.mpkg Distribution file. This check was removed through my ModCD so while I don't endorse doing it this way, I'm suggesting to try using it instead of tonymac's install media regardless to see if you can get past this 10.6 kp you're running into. The ModCD does use patched IOATAFamily.kext to get around known 10.6 kernel panics but your kernel panic is unrelated to the well known ones that people dealt with back then so there's no promises that it will fix your issue.

 

If you do boot up, be sure and look at the Customize install list and verify that what was autoselected is correct before installing. Many people mistake the ModCD as a typical swap CD, while it actually injects additional install packages for you to choose from including a hidden one for the Chameleon bootloader to the DVD's OS installation. It's done via ramdisk mounting and running a number of scripts.

 

If this doesn't solve your problem then don't expect any additional help from me. I think it's been too long to deal with 10.6 install issues these days, at least that's my personal opinion. You can try using 10.7 media instead, as your FX1300 loses support in 10.8 from what I understand. Replace the graphics card and you can run OS X versions newer than that.

In Topic: The macOS 10.13 is coming...

07 March 2017 - 11:44 PM

Are we keeping the URL a secret or something? here it is: https://swscan.apple...-1.sucatalog.gz let me know if you want it removed. Nothing too exciting about what's on it other than it existing

In Topic: CUDA for GT 130M?

07 March 2017 - 11:33 PM

Your GPU is not on this list: https://developer.nvidia.com/cuda-gpus so the answer is no

© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy