Jump to content

Dimension e520 tower AKA: DM061


AWD_Guy

Recommended Posts

So, aparently the chameleon stuff doesn't make it to the log.

Can I force it to log it somewhere?

 

It looks like the IOATAFamily files are being read, just not catching the dev ID even though it is there???
 

From a ""Log from achidisk=1 debug=8 -v" Boot. I am not typing it all. Paths abreviated, etc...

 

It reads the kernel from HFS+ files

ACPI table not found: DSDT.aml

No DSDY found, using 0 as uid value

Using PCI-Root-UID value: 0

read /E/smbios.plist

DRAM

...

Customizing systemID...

efi_inject... NULL trying stringdata

ACPI table not found: DSDT.aml

ACPI table not found: SSDT.aml

FADT: applied! X2

Read a bunch of HFS+ files....   *.plist

INCLUDING...

/E/E/IOATAFamily.kext/C/PI/AppleIntelPIIXATA.kext/C/I.p
/E/E/IOATAFamily.kext/C/PI/IOATABlockStorage.kext/C/I.p

/E/E/IOATAFamily.kext/C/PI/IOATAPIProtocolTransport.kext/C/I.p
....

/E/E/IOATAFamily.kext/C/MacOS/IOATAFamily

/E/E/IOATAFamily.kext/C/MacOS/IOATAFamily

/E/E/IOATAFamily.kext/C/PI/AppleIntelPIIXATA.kext/C/MacOS/AppleIntelPIIXATA

/E/E/IOATAFamily.kext/C/PI/AppleIntelPIIXATA.kext/C/MacOS/AppleIntelPIIXATA

/E/E/IOATAFamily.kext/C/PI/IOATABlockStorage.kext/C/MacOS/IOATABlockStorage

 

/E/E/IOATAFamily.kext/C/PI/IOATABlockStorage.kext/C/MacOS/IOATABlockStorage

/E/E/IOATAFamily.kext/C/PI/IOATAPIProtocolTransport.kext/C/MacOS/IOATAPIProtocolTransport

/E/E/IOATAFamily.kext/C/PI/IOATAPIProtocolTransport.kext/C/MacOS/IOATAPIProtocolTransport

...
Errors encountered...

Pausing 5 seconds

Link to comment
Share on other sites

×
×
  • Create New...