Jump to content

[Guide] Yosemite 10.10.X - Dell Optiplex 780 (760)


pepto
 Share

468 posts in this topic

Recommended Posts

Sebus

 

Thanks for the reply.  I have taken note of what you say, it really helps.  

 

However, I am totally new to this and have to learn some how so please bear with me, i am doing my best.

 

Thanks again,

 

Makin

  • Like 1

Logical thinking is all that you need. That helps to understand the process. From then on it is easy.

 

Guide is confusing in parts & pepto never changed it, even it was suggested many times

 

sebus


Next (important) problem [AND SOLUTION]:

My network connection doesn't seem to be stable. I get a lot of "Server not found" errors every now and then. I tried different DNS Servers (Google: 8.8.8.8) but that only solved it for the first moment. I don't know how to tackle that problem.

 

[...]

[...]

So here we are again. I am still having huge trouble with my network. It works at first but network shares (smb) get disconnected frequently and as soon as I leave the computer, the network totally dies and I have to reboot to get it working again.

 

Symptoms are:

 

while in use the keyboard

  • often disconnects from network share via smb
Feb 23 14:04:08 localhost kernel[0]: smb2_smb_parse_change_notify: smb_rq_reply failed smb2_smb_read_write_async60
Feb 23 14:04:08 localhost kernel[0]: : smb_rq_reply failed 60
Feb 23 14:04:08 localhost kernel[0]: smb2_smb_parse_change_notify: smb_rq_reply failed 60
Feb 23 14:04:08 localhost kernel[0]: smb2_smb_parse_change_notify: smb_rq_reply failed sm60
  • I could reconnect just a couple of seconds later manually
  • overall bad performance

while away from keyboard

  • the connection dies almost immediately
  • no ping to internet or router
$ ping 192.168.2.1
ping: sendto: Host is down
Request timeout for icmp_seq 1170
  • no sign of problems in the network adapter (ethernet) settings

 

I checked the logs and this is what I found that could be related:

# these lines are from the boot sequence
Feb 23 11:08:23 localhost kernel[0]: "name" not a kext
Feb 23 11:08:23 localhost kernel[0]: "FailedCLUT" not a kext
Feb 23 11:08:23 localhost kernel[0]: "FailedImage" not a kext
Feb 23 11:08:23 localhost kernel[0]: Refusing new kext com.insanelymac.driver.AppleIntelE1000e, v1.3.10: already have prelinked v3.1.
Feb 23 11:08:23 localhost kernel[0]: Refusing new kext org.voodoo.driver.VoodooHDA, v0.2.62: already have prelinked v2.8.4.
Feb 23 11:08:23 localhost kernel[0]: AppleIntelE1000e(Info): Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Feb 23 11:08:23 localhost kernel[0]: AppleIntelE1000e(Info): changing MTU from 0 to 1500
Feb 23 11:08:23 localhost kernel[0]: AppleIntelE1000e(Info): AppleIntelE1000e:rx = 256, tx = 256
Feb 23 11:08:41 WIESELMAC kernel[0]: AppleIntelE1000e(Info): e1000e NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
...
# this error floods the logs every second (beginning right after the boot process)
Feb 23 17:32:13 localhost kernel[0]: AppleIntelE1000e(Err): Detected Hardware Unit Hang:
Feb 23 17:32:13 localhost kernel[0]: TDH <dd>
Feb 23 17:32:13 localhost kernel[0]: TDT <54>
Feb 23 17:32:13 localhost kernel[0]: next_to_use <54>
Feb 23 17:32:13 localhost kernel[0]: next_to_clean <d8>
Feb 23 17:32:13 localhost kernel[0]: buffer_info[next_to_clean]:
Feb 23 17:32:13 localhost kernel[0]: time_stamp <232896>
Feb 23 17:32:13 localhost kernel[0]: next_to_watch <dd>
Feb 23 17:32:13 localhost kernel[0]: next_to_watch.status <0>
Feb 23 17:32:13 localhost kernel[0]: MAC Status <80083>
Feb 23 17:32:13 localhost kernel[0]: PHY Status <796d>
Feb 23 17:32:13 localhost kernel[0]: PHY 1000BASE-T Status <3800>
Feb 23 17:32:13 localhost kernel[0]: PHY Extended Status <3000>
Feb 23 17:32:13 localhost kernel[0]: PCI Status <10>
...
# This is the first time this error appears and it must be close to when I left the computer
Feb 23 17:31:15 localhost kernel[0]: e1000_tx_map: failed to getphysicalsegment.
Feb 23 17:31:45 --- last message repeated 158 times ---
Feb 23 17:31:45 localhost kernel[0]: e1000_tx_map: failed to getphysicalsegment.
Feb 23 17:32:13 --- last message repeated 127 times ---
…
Feb 23 17:32:39 localhost discoveryd[50]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 192.168.2.1 Port 53 errno 64, fd 63, ErrLogCount 5 ResolverIntf:0
…
Feb 23 17:33:42 localhost KernelEventAgent[70]: tid 54485244 received event(s) VQ_DEAD (32)
Feb 23 17:33:42 localhost KernelEventAgent[70]: tid 54485244 type 'smbfs', mounted on '/Volumes/media', from '//USERLOGIN@192.168.2.231/media', dead
Feb 23 17:33:42 localhost KernelEventAgent[70]: tid 54485244 force unmount //USERLOGIN@192.168.2.231/media from /Volumes/media
Feb 23 17:33:42 localhost kernel[0]: smb2_smb_read_write_async: smb_iod_rq_enqueue failed 57
…
Feb 23 17:33:57 localhost sharingd[287]: 17:33:57.004 : netfs_GetServerInfo returned -1
…
Feb 23 17:34:00 localhost KernelEventAgent[70]: tid 54485244 received event(s) VQ_NOTRESP (1)
Feb 23 17:34:00 localhost KernelEventAgent[70]: tid 54485244 type 'smbfs', mounted on '/Volumes/D', from '//WIN_USERNAME@192.168.2.203/D', not responding
Feb 23 17:34:00 localhost loginwindow[68]: Error: could not load nib file for DisconnectedFS plugin
…
Feb 23 17:36:24 localhost discoveryd[50]: Basic DNSResolver  Re-Binding to random udp port 55742
…
Feb 23 17:40:16 localhost apsd[51]: Failed entitlement check 'com.apple.private.aps-connection-initiate' for ManagedClientAgent[1542]
Feb 23 17:40:16 localhost apsd[51]: Peer connection [pid=1542] lacks APSConnectionInitiateEntitlement
…
Feb 23 17:43:35 localhost WindowServer[175]: CGError post_notification(const CGSNotificationType, void *const, const size_t, const bool, const CGSRealTimeDelta, const int, const CGSConnectionID *const, const pid_t): Timed out 1.000 second wait for reply from "loginwindow" for synchronous notification type 102 (kCGSDisplayWillSleep) (CID 0x7107, PID 68)
Feb 23 17:43:35 localhost WindowServer[175]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7fa139654500(2001)
…
Feb 23 17:43:36 localhost identityservicesd[292]: <IMMacNotificationCenterManager: 0x7fb963625a50>:    NC Disabled: NO
Feb 23 17:43:36 localhost identityservicesd[292]: <IMMacNotificationCenterManager: 0x7fb963625a50>:   DND Enabled: YES
Feb 23 17:43:36 localhost identityservicesd[292]: <IMMacNotificationCenterManager: 0x7fb963625a50>: Updating enabled: NO   (Topics: (null))

Steps I tried:

  • toggle Ethernet off/on
  • use DHCP/Manual
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=3<RXCSUM,TXCSUM>
	inet6 ::1 prefixlen 128 
	inet 127.0.0.1 netmask 0xff000000 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=6b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4,TSO6>
	ether 14:HIDE:3c 
	inet6 fe80::HIDE:fc3c%en0 prefixlen 64 scopeid 0x4 
	inet 192.168.2.204 netmask 0xffffff00 broadcast 192.168.2.255
	nd6 options=1<PERFORMNUD>
	media: autoselect
	status: active
  • disconnect and reconnect network cable
  • reboot (helped)

My best bet is the driver is not the right one and sleep mode makes it worse... But I don't know which one to use. The logs say something aobut not using one version of a driver but another one...

 

Do you have those errors as well without the problems I mentioned?

If not: Which Network driver did you install to get it fully working?

Any other help?

 

Thank you.


Ok, Let's start over.

 

It seems that you've got a Huge problem with kexts. I think that you installed them the wrong way, probably because of the non-updated/corrected guide.

 

So let's make some cleaning :

 

First :

• All extras kexts (I mean those from Clover zip file) must be placed in EFI/Clover/Kexts/10.10 folder inside your EFI partition. Nowhere else.

• If you have placed any of those kexts in Sytem/Library/Extensions, remove all of them.

• If you ever tried Chameleon Bootloader instead of Clover, remove Extra folder from the root of your HDD.

 

Second :

• rebuild kernel cache with terminal :

 

sudo touch /System/Library/Extensions

sudo kextcache -prelinked-kernel

 

Then reboot.

 

About Ethernet/Internet concerns : Use Intel82566MM.kext instead of AppleIntelE1000e.kext which is known to have sleep/wake issues.

 

Finaly, if you own an AMD Radeon HD 5450 series, use Jake Lo's DSDT available in this topic (do some research) to get full video/3D acceleration. In this case, don't use any AMD related kexts from Clover zip and don't modify any AMD kexts in S/L/E.

 

Otherwise, use Clover zip DSDT file and place it in EFI/Clover/ACPI/Patched folder to get full sleep/wake functions enabled.

  • Like 1

It seems that you've got a Huge problem with kexts. I think that you installed them the wrong way, probably because of the non-updated/corrected guide.

A few questions first:

 

I installed the Network kext (AppleIntelIE1000e) with Kext Wizard. That tool installs kexts under /S/L/E!

 

• All extras kexts (I mean those from Clover zip file) must be placed in EFI/Clover/Kexts/10.10 folder inside your EFI partition. Nowhere else.

 

1.) Does that mean I have to place ALL kexts in the E/C/K/10.10 folder? Or just the ones that are already in thereß

There is the first problem by the way: in that folder is another AppleIntelIE1000e.kext (so I have two installed).

 

• If you have placed any of those kexts in Sytem/Library/Extensions, remove all of them.

 

2.) Does that mean I have to install ALL custom kexts in E/C/K10.10?

 

About Ethernet/Internet concerns : Use Intel82566MM.kext instead of AppleIntelE1000e.kext which is known to have sleep/wake issues.

 

3.) Where would I get a trustworthy Intel82566MM.kext?

 

Finaly, if you own an AMD Radeon HD 5450 series, use Jake Lo's DSDT available in this topic (do some research) to get full video/3D acceleration. In this case, don't use any AMD related kexts from Clover zip and don't modify any AMD kexts in S/L/E.

 

Otherwise, use Clover zip DSDT file and place it in EFI/Clover/ACPI/Patched folder to get full sleep/wake functions enabled.

4.) Another puzzle. I do own a HD 5450 and used Jake Lo's DSDT but I still have a VoodooHDA.kext in the S/L/E folder should I remove that?

5.) Is the sleep/wake solved by Jake Lo's as well, or do I have to use the Clover DSDT on top of Jake Lo's?

 

Thank you so much for your time.


Obviously, you don't understand how bootloaders works :)

It's OK since you're a noob.

 

To make it clear :

 

When using Clover, all custom/extra kexts such as FakeSMC, Ethernet and Audio kexts should always be placed in E/C/K/10.10.

 

S/L/E should remain untouched with only original kexts from OS X, except for "traditionnal" kexts such as the ones used by some 3rd party software (i.e. Paragon NTFS or AirParrot and so on).

 

VoodooHDA pkg is an exception as it installs VoodooHDA.kext and AppleHDADisabler.kext in S/L/E. You can leave it that way as AppleHDADisabler.kext is meant to avoid potential KP with AppleHDA.kext.

 

Kext Wizard will install any kext in S/L/E or Extra/Extensions (only used by Chameleon bootloader, so it's irrelevant in that case). One workaround is to manually place/move every new custom kexts in E/C/K/10.10, rebuild disk permissions and rebuild kernel cache using the terminal as stated above.

 

But keep in mind that you should not install the same kext in two different place. It must be in S/L/E or in E/C/L/10.10, not both !

 

Otherwise, you'll get this :

Feb 23 11:08:23 localhost kernel[0]: Refusing new kext com.insanelymac.driver.AppleIntelE1000e, v1.3.10: already have prelinked v3.1.
Feb 23 11:08:23 localhost kernel[0]: Refusing new kext org.voodoo.driver.VoodooHDA, v0.2.62: already have prelinked v2.8.4.

The Intel82566MM.kext shouldn't be hard to find ;) Google it or simply read previous posts of this thread :P

 

If you own a 5450, Jake Lo's DSDT is fine, no need to use another one. Remember to name it DSDT.aml and place it where it should be. That's it.

  • Like 1

OK, I did as you told me.

  • I deleted AppleIntelE1000e.kext from /S/L/E AND from /EFI/EFI/Clover/kexts/10.10.
  • Deleted VoodooHDA from /E/E/C/10.10 (present in /S/L/E).
  • copied the Intel82566MM.kext to /E/E/C/10.10
  • used your commands and rebooted.

So far, most of the errors are gone. No "Refusing kext" and no "ppleIntelE1000e(Err): Detected Hardware Unit Hang".

SMB (rsync) seems to be more stable but to soon to tell about performance impact I guess.

 

Thank you!

  • Like 1

I use AppleIntelE1000e.kext

AppleIntelE1000e.kext.zip
133,496 bytes

CRC32: E1915AC3
MD5: 8FC9A4FEB555D799A30231C5A9C0F567
SHA-1: 95B808548DBC8C9E2AF0DE361DE35050674065B4

from S/L/E (installed with Kext Wizard) with no issues regarding connectivity with/without sleep (computer could sleep for 24 hours & on wakeup connectivity would be just there)


I use AppleIntelE1000e.kext

AppleIntelE1000e.kext.zip
133,496 bytes

CRC32: E1915AC3
MD5: 8FC9A4FEB555D799A30231C5A9C0F567
SHA-1: 95B808548DBC8C9E2AF0DE361DE35050674065B4

from S/L/E (installed with Kext Wizard) with no issues regarding connectivity with/without sleep

 

Yes, AppleIntelE1000e.kext actually works fine. The issue wasn't the kext in itself in the case of MacWiesel, issues went from the use of the same kext in two different locations. OS X tried to load them both resulting in an unstable setup.

 

That said, I ran into troubles with AppleIntelE1000e.kext when I woke up my Optiplex 760. The connection was lost every single time I did.

 

Intel82566MM.kext solved all my issues and that's why I recommend to use it instead of AppleIntelE1000.kext as it also works fine and fix any potential problems.


A little fun anectode about the last couple of hours: I had another "disconnect after coming back to the computer" problem and of course blamed the driver and system again. But it happenend again while using it. So I rebooted.

I looked for logs I could present here until by chance I found out that my f***ing new network cable (different cable than with the old driver) didn't connect proberly. It must have slipped out during the night while I was AFK.

 

Log said: 25.02.15 15:09:05,000 kernel[0]: Intel82566MM info: Link is Down > and if I could understand logs, that would have been a strong hint, I guess.

 

lets see what the future brings.


Sometimes it might be best to do a fresh install.

 

If you have all of the folders in your EFI Partition correct, then you could reboot from your Yosemite USB installer, then select Disc Utility, erase the partition your last install was on, (leave the EFI alone), then do a fresh install of Yosemite. After the second reboot, when the install is through, it pretty much should boot right up with very little else left to do, especially if you have an HD5450 Video card, and you are using the edited DSDT.

 

Another suggestion when you are trouble-shooting problems with your install; Have an extra hard drive or two on standby. It takes only a minute or two to change hard drives, so just change drives, and then try another fresh install to see if that corrects your problem.

 

The main thing here is; get your EFI Partition Correct, and fresh install should be easy. :)


Honestly, if you do install Mac OS on hardware that is not mean for it, then you should have some idea what you are doing. Not that complicated. Forget following steps blindly & try to think for yourself.

 

USB is not only install medium, it can also hold any files that you need to transfer between here & there... (you you can have Clover installer pkg on USB)

 

Also forget copying all the files from Clover folder.

 

You only need:

 

CLOVER_780.zip\CLOVER\ACPI\patched\DSDT.aml
CLOVER_780.zip\CLOVER\kexts\10.10\ElliottForceLegacyRTC.kext
CLOVER_780.zip\CLOVER\kexts\10.10\FakeSMC.kext
CLOVER_780.zip\CLOVER\kexts\10.10\NullCPUPowerManagement.kext
CLOVER_780.zip\CLOVER\config.plist

 

Ethernet & VoodooHDA kext you can deal with AFTER the setup

 

sebus

 

 

@ sebus

 

Appreciate your input here, but maybe just chill out a little, please. :)  

 

We were all Hackintosh newbies at one time, and we are all here to help each other.

 

That is what makes this Site so special. :)


Blindly following step 1...10 does not make you learn. End result might be OK, but one still has no idea what & why...

 

True. But If you don't even know how kexts works and why you shouldn't installed them twice in two different places (which Clover nor Chameleon makes it easy to understand), you might be confused on why your setup is unstable.

 

The guide is no help to understand that. Plus, it still has some uncorrected mistakes and/or unclear parts. And last but not least, it uses Clover as the main bootloader which is well-known for not being as easy as Chameleon.

 

So let's be cool with noobs. This guide should be fixed as soon as possible because it is misleading a lot of people !

  • Like 3

I just had another instance of sudden network drop out which is a huge pain in the a... when it happens when you're in a rush. ;)

I checked both ends of the network cable. All other computers had net and my Network Settings didn't show anything.

 

ifconfig was normal as well, still had my manual IP but I wasn't able to ping the router anymore. Only a reboot fixed the problem.

 

Is there anything in the logs here, which I oversaw?

 

Thank you.

network.log.txt


then buy Apple hardware & it will be guaranteed to work...

 

C'mon, this is such an arrogant answer !

The right one should have been : "go and instruct yourself". That's an acceptable answer here on InsanelyMac !

I just had another instance of sudden network drop out which is a huge pain in the a... when it happens when you're in a rush. ;)

I checked both ends of the network cable. All other computers had net and my Network Settings didn't show anything.

 

ifconfig was normal as well, still had my manual IP but I wasn't able to ping the router anymore. Only a reboot fixed the problem.

 

Is there anything in the logs here, which I oversaw?

 

Thank you.

 

Try to install Ethernet kext directly in S/L/E. Sometimes, it's necessary to have it in there to correctly load it. Don't forget to remove it from E/C/K/10.10 and to rebuid kernelcache before restarting.

  • Like 1

Obviously, you don't understand how bootloaders works :)

It's OK since you're a noob.

 

To make it clear :

 

When using Clover, all custom/extra kexts such as FakeSMC, Ethernet and Audio kexts should always be placed in E/C/K/10.10.

 

S/L/E should remain untouched with only original kexts from OS X, except for "traditionnal" kexts such as the ones used by some 3rd party software (i.e. Paragon NTFS or AirParrot and so on).

 

VoodooHDA pkg is an exception as it installs VoodooHDA.kext and AppleHDADisabler.kext in S/L/E. You can leave it that way as AppleHDADisabler.kext is meant to avoid potential KP with AppleHDA.kext.

 

Kext Wizard will install any kext in S/L/E or Extra/Extensions (only used by Chameleon bootloader, so it's irrelevant in that case). One workaround is to manually place/move every new custom kexts in E/C/K/10.10, rebuild disk permissions and rebuild kernel cache using the terminal as stated above.

 

 

Obviously, a lot of people don't understand how bootloaders works :)

 

This is absolute nonsense...  This has been addressed 100's of times here, both Slice and aplanti have wade in on this and clearly specified that all kext should be in S/L/E...   Put fake in EFI/Clover/Kext/10.10 of the installer only to facilitate the install...

 


Obviously, a lot of people don't understand how bootloaders works :)

 

This is absolute nonsense...  This has been addressed 100's of times here, both Slice and aplanti have wade in on this and clearly specified that all kext should be in S/L/E...   Put fake in EFI/Clover/Kext/10.10 of the installer only to facilitate the install...

 

 

Awesome!  :thumbsup_anim:

 

Maybe you could stick around and help us "Clover Newbies".   :P

 

I would love to learn how to get HD5450 HDMI audio working. 

 

That, and would like to know why my unit boots up so slow. On startup after splash-screen, it takes about a minute before I see Clover Screen.

 

I have read, and read for months, but I cannot figures these out. I really could use any Clover help I can get.   :drool:


It works!

 

Thanks to all that helped and the kick up the arse to sort the problems myself.

 

As some have mentioned whilst the guide is a start bits do not work etc, I even found that the tools in the 780 folder did not work so sourced them myself!

 

But it works and I learned something new which is good.

 

Thanks again.

  • Like 1

Obviously, a lot of people don't understand how bootloaders works :)

 

This is absolute nonsense...  This has been addressed 100's of times here, both Slice and aplanti have wade in on this and clearly specified that all kext should be in S/L/E...   Put fake in EFI/Clover/Kext/10.10 of the installer only to facilitate the install...

 

Well that's not entirely true. This is the well-known and endless debate between the "100% Vanilla OS X" pros and the rest of us. I've seen a lot of people that can't even bear to see any "extra" kext in S/L/E and who claims that hiding them and all of the associated bootloaders files in the EFI partition (or in Extra/Extensions for Chameleon users) is the best practice.

 

Furthermore, you state that this been addressed a 100's times here... Where ? Where is the pinned topic at InsanelyMac that explain it clearly and definitively ? And please, don't point to a deeply and well-hidden link :). This should be at the root of the forum, like a "Hey guys, it's here and nowhere else !". Sadly, there no consensus on this.

 

Don't forget that Yosemite brings some huge changes about the way bootloaders works because of the kexts-signing and cache support which is slightly different than in the previous OS X versions.

 

Things moves fast so please, don't forget that there's a lot of people that just want to install and enjoy OS X and doesn't necessarily want to become a Hackintosh Guru :P.

 

What is a non-sense for me is to focus on this. As long as it works, put your files where you want to and go enjoy your Hack !

  • Like 2

Nice guide but why do you write "[Guide] Mavericks 10.10.X - Dell Optiplex 780 (760)"

 

Should be "[Guide] Yosemite 10.10.X - Dell Optiplex 780 (760)" instead

 

happy hacking

 

OSBeast


Obviously, a lot of people don't understand how bootloaders works :)

 

This is absolute nonsense...  This has been addressed 100's of times here, both Slice and aplanti have wade in on this and clearly specified that all kext should be in S/L/E...   Put fake in EFI/Clover/Kext/10.10 of the installer only to facilitate the install...

 

All of my kexts are on the EFI Partition, and my box runs fine.

 

Sleep works, Wake from Sleep using Bluetooth Device works.

iMessage works

FaceTime Works with the Logitech C615 HD Webcam I added, (Plug & Play)

 

So, if the way I have installed Yosemite is "Absolute Nonsense", than I am just fine with that.

I am absolutely thrilled with my Optiplex 780 Hackintosh. IMO you can't beat it for $150. Heck, I like it so much, I built a second one. :)

 

It is very easy for people to drop by and make a post or two to criticize, but it takes more effort to stick around and help out.

  • Like 2

Depending on definition of arrogant. (you think Apple hardware wold not work?)

 

Still think that it is the best answer in circumstances. Why to struggle to use something illegally in first place

 

No, I don't think Apple's Hardware wouldn't work and I don't understand your argument :huh: . What's an arrogant answer to me (I should have said "Lazy" ?) is to say that "if you're not skilled enough to make it works, then go buy a real Mac" ! And I'm pretty sure that what you wanted to say.

 

Sorry if I'm wrong but if I don't, then this is not an acceptable answer to noob's problems. If you don't want to help that's OK. But at least, share you personal experience and instruct them…

 

BTW, Hackintosh are not illegal in Europe. It may be very different in the U.S. (I don't know it for sure and I'm not a legal expert) but here in France and in the rest of the whole European Union, they are not ! :D


OFF TOPIC!

 

Read Apple license agreement (which you click Agreed when you install OS X), in Europe or US. Makes no difference....

 

"if you're not skilled enough to make it works, then..." LEARN LONGER and HARDER, do not expect delivery on a silver platter!

 

Apple's EULA and all other private laws does not prevail over European laws which allow using or modifying software for personal use as long as you don't sell it or attempt to Apple's honor and reputation (and good luck for them to prove that in a Court of Justice :P !). There's no need to argue on this.

 

Once again, I'm not a legal expert but that's the way it is.

 

And as you said, it's Off topic so let's end this right now.


Apple's EULA and all others private laws does not prevail over European laws which allow using or modifing softwares for personnal use as long as you don't sell it or attempt to Apple's honor and reputation (and good luck for them to proove that in a Court of Justice :P !). There's no need to argue on this.

 

Once again, I'm not a legal expert but that's the way it is.

 

And as you said, it's Off topic so let's end this right now.

 

Thats true and in europe you're not allowed to bundle software STRICTLY to some piece of hardware :)

 

happy hacking

 

OSBeast


"if you're not skilled enough to make it works, then..." LEARN LONGER and HARDER, do not expect delivery on a silver platter!

 

And what's the best thing to do when you don't know ? ASK, ASK and ASK !!!

This very different than to expect delivery on a silver platter.

 

But if you think that you must learn the Hard way, that's your problem, not mine… :whistle:


Hi, you great helpers,

I still suffer from network lock ups.

I did what you said @polyzargone : I removed network kext from /EFI partition and installed it in /S/L/E.
The first night was promising. The first time w/o having to reboot. But after some hours of work I had another total network breakdown.
It happend coincidentally when mounting a samba share and moving data around.

More precisely: I was using rsync to backup data to a mounted samba share successfully for a couple of hours. Than I connected to a samba share on my Android mobile and wanted to move some images and baaam a minute or so later the network was down. (On a side note: rsync doesnt recognize that and it looks in the terminal like it would still copy files).

Any more ideas on how to fix that problem?


 Share

×
×
  • Create New...