UUID Error 35, a big problem
i have this dammed UUID Error 35. unable to dtermine UUID for host. Error: 35 Beside that this spams my Console Windows , cause this any serious Problems ? I know there is a fix for , but i want to do my Installation as Vanila as Possible.…
- Primary Author
- @Bettarg Published 2009-04-03
- Collection
- OSx86 Core & 10.X
- Archival Footprint
- 12,261 historical reads · 3 curated field notes (from 7 dispatches) · 2009-04-03 – 2009-05-26
- Credited Voices (4)
- @Bettarg (3)@milanca (2)@Chris83@zuz242
i have this dammed UUID Error 35.
unable to dtermine UUID for host. Error: 35
Beside that this spams my Console Windows , cause this any serious Problems ? I know there is a fix for , but i want to do my Installation as Vanila as Possible.
Thanks for u help.
Author Updates & Technical Revisions
Follow-up dispatches by @Bettarg
This is strange, i can remeber that i have installd a TM Fix. At least TM works fine.
I have try to find informations about DSDT, but dont find mutch informations.
This is the many Problem of the OSX86 Com. So many information ar deep buried in a lot of Forums. A Wiki page would be nice, but OSX86Wiki…a k, this is not a real Wiki
Synthesized Community Field Notes
3 technical responses curated from 7 original dispatches
_CFGetHostUUIDString: unable to determine UUID for host, is a common thing on OSX. It is a message in log caused by kernel when system doesn't find ethernet adapter as built-in. Can be fixed via IOnetworkingfix but the best way is to fix it by making ethernet, LAN as 'built-in' via DSDT. Try to search a bit how to do this. It has no side effects apart from logs, on your networking, internet speed for example and so on. (or at least i just think it doesn't have). But it is good to fix it and have as perfect system as possible.
You are more than welcome Bettarg. If you have any problems fixing it i'd be glad to assist. If you decide to fix it via dsdt for example, i can help you if needed. One thing i forgot to tell you is that this fix is also called time-machine fix; time machine requires built-in lan to work properly. If you don't use TM you can freely ignore message logs.
DSDT is not the same as EFI strings, isn´t it?
because you could also add the ethernet card via efi-studio so it is recognized as build in.
works for timemachine, so it could work for uuid as well.