Jump to content

Confusition with hdd's and mess after DSDT-Free installation


  • Please log in to reply
2 replies to this topic

#1
Morfi717

Morfi717

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts

Hello. :)


I'd like to bring up two cases here.


1) Disks
It's complete confusion to me how Chameleon deals with disks.
Firsly, my diskutil list

/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *120.0 GB   disk0
   1:               Windows_NTFS                         104.9 MB   disk0s1
   2:               Windows_NTFS                         119.9 GB   disk0s2
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *180.0 GB   disk1
   1:               Windows_NTFS SSD                     180.0 GB   disk1s5
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *120.0 GB   disk2
   1:                        EFI                         209.7 MB   disk2s1
   2:                  Apple_HFS Macintosh               119.7 GB   disk2s2
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *1.0 TB     disk3
   1:               Windows_NTFS New Volume              1.0 TB     disk3s1


I have only 2 Operating system. Mac on disk2 (Macintosh) and Windows on disk0 (no label as it's TC'ed partition).
Now it's complete mystery to me why does chameleon auto detects them as
hd(1,5) - SSD
hd(0,2) - Macintosh
hd(2,1) - New Volume


For me it should be
2,2 - Mac
3,1 - New Volume
1,1 - SSD
Well, perhaps it doesn't detect 0,1 or 0,2 as they have no labels but using <key>Rename Partition</key> won't display it either.


Could anyone exmplain me how can I find out how to operate with those hd(x,y) stuff? I can't find any pattern here.
Using Label or UUID does NOT satisfy me since labels can change, and UUID will not show for disk0. Despite that I tried to hide volume by using Device UUID both with and without quotes and trust me, it didn't hide it.

Proof:
sh-3.2# diskutil info disk0s1   Device Identifier:        disk0s1
   Device Node:              /dev/disk0s1
   Part of Whole:            disk0
   Device / Media Name:      Untitled 1


   Volume Name:              
   Escaped with Unicode:     


   Mounted:                  No


   File System Personality:  ExFAT
   Type (Bundle):            exfat
   Name (User Visible):      ExFAT


   Partition Type:           Windows_NTFS
   OS Can Be Installed:      No
   Media Type:               Generic
   Protocol:                 SATA
   SMART Status:             Verified


   Total Size:               104.9 MB (104857600 Bytes) (exactly 204800 512-Byte-Blocks)
   Volume Free Space:        0 B (0 Bytes) (exactly 0 512-Byte-Blocks)
   Device Block Size:        512 Bytes


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


   Whole:                    No
   Internal:                 Yes
   Solid State:              Yes


2) DSDT.aml
Before I installed UserDSDT or DSDT-Free Installation, HW monitor was able to detect my OC'ed CPU, show the temperatures etc.


Now after this installation it shows almost nothing, just SSD remaining life and HDD temperature.
I have DSDT.aml in /Extra/ crafted by myself which used to work properly on Chameleon on USB stick.
Now it doesn't matter wether I use DSDT.aml that installed together with this UserDSDT-Free Installation or if I use my own DSDT.aml or if I remove it completly, neither HW monitor or SMC monitor won't show me any values at all.
I tried to define <key>DSDT</key> with different values <string>/Extra/DSDT.aml</string>, <string>hd(0,2)/Extra/DSDT.aml</string>, <string>hd(0,2)/Extra/GTFO.aml</string> none of those did the trick.



I beg for help and appreciate your time with those 2 things.
Thanks
Mike

#2
Gringo Vermelho

Gringo Vermelho

    The Jan Bird fix

  • Supervisors
  • 6,214 posts
  • Gender:Male
  • Location:Brazil

How it works for other drives is a total mystery but as far as Chameleon is concerned, it seems that the first drive is always the one that chameleon is installed on. It doesn't matter what diskutil list shows after booting, what the boot order in your BIOS is or to which port or controller the drive is connected.

 

Go by the drive order as it appears in the Chameleon GUI, that seems to work.



#3
3.14r2

3.14r2

    The Round One

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,333 posts
  • Location:Molvania
Could anyone exmplain me how can I find out how to operate with those hd(x,y) stuff? I can't find any pattern here.
Using Label or UUID does NOT satisfy me since labels can change, and UUID will not show for disk0.

Labels are the safest bet. Though both UUID, labels and hd(x,y) can change. Labels are the most universal, since are independent of how HDDs are connected to MB or even on which disk the labelled partition resides on (as you can clone a partition to a different drive leaving label the same and it will work perfectly). UUIDs are the almost the same, as are permanent until anything is done to a disk/partition. hd(x,y) is the least option I'd go with. Just reconnect HDD to different SATA ports or rearrange partitions, and it all stops working.

 

2) DSDT.aml

Before I installed UserDSDT or DSDT-Free Installation, HW monitor was able to detect my OC'ed CPU, show the temperatures etc.

AFAIK HW monitoring is dependent on FakeSMC plugins used. I doubt DSDT has anything to do here...







0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

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