Jump to content

Heideana

Donators
  • Content count

    9
  • Joined

  • Last visited

About Heideana

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  • Location
    NoeValSF
  • Interests
    DAW, Guitar, Heidegger

Recent Profile Visitors

1,286 profile views
  1. Hi and thanks for replies and thanks for kind answers and no offense taken as I am at the ends of my formal knowledge and any directions at this point... If I’m understanding Pavo’s direction correctly, I should be using the Clover installer to fix my weirded-out LOM NIC and get things back on track? Best...hopkins
  2. Hi and thanks to all for the suggestions/help…its’ greatly appreciated! As an update, I have to say its' been trip again exploring the phenomenology of the intel 82574L; this time however, I came across something new; namely the acronym LOM (LAN on motherboard). From what seems to be coming into relief it would seem that none of the tricks I’ve been finding about resetting my NIC apply as their only for off-board NIC’s which probably why I’m not getting anywhere… Given that I’ve been trying to fix my problem off/on for a years or so, I’m thinking its’ time to move on and try an Apple USB or Thunderbolt NIC and see if that gets me anywhere…doubt that it will but seems like something to try. If that doesn’t work, then its’ probably time to figure out how to set a non-LOM NIC so that I can access the App Store, etc., Last ditch effort would be using TonyMacx86 tools? Best…hopkins
  3. Much thanks for the response King! At the risk of sounding both green and inept, I did some quick Google rooting around EFX eeprom programs and I think it’s a preboot utility that I need? If so, does anyone know of or can point me towards the “best” guide for using it? The other oddity that I’m not understanding is why my NIC shows up and works in Windows but not in OS X and what’s the underlying relationship between the two? I’m kinda getting to the edges of my formal knowledge/understandings and any direction most appreciated! Best - hopkins Does anybody remember the last/best bios version for Mavericks “off the top of their head”? I think I remember starting to have NIC issues after moving on to Yosemite and I’m curious to see if it’ll show up under a “Mavericks” installation...best and thanks-hopkins
  4. Hi and thanks ammoune78 and apologies to all for the length of this post! I did download fresh copies of Yosemite and created fresh USB installers with no results. I think my old Window keys were used up in old machine that had been updated and, as my Microsoft instructor friend reminded me, it’s probably best to have an up-to-date copy in my library… After no success and some more phenomenological digging; I finally came across a trace in this thread where King identifies an identical LAN oddity for skwakk, back on page 70… 1) In #1388 (#1388) King traces thru skwakk’s DDump files and: Quote Found the error: Jun 11 23:39:03 localhost kernel[0] <Debug>: 0x1fad9eef, 0x00000000 Intel82574L::start - NVM Checksum incorrect Jun 11 23:39:03 localhost kernel[0] <Debug>: 0x1fad9eef, 0x00000000 Intel82574L::validateEEPROM - EEPROM checksum is incorrect Jun 11 23:39:03 localhost kernel[0] <Debug>: 0x1fad9eef, 0x00000000 Intel82574L::start - failed to validate EEPROM Did you tried to play with LAN eeprom(flash/update)? You need to fix LAN eeprom checksum, if you don't know how, I will try to put an easy way for you to do it, let me know… _______________________________ So I did a DarwinDump and found the exact same error lines and 2) followed the directions he gave skywalk in #1390 (#1390) Quote OK, I see you have windows so here is what you need to do: 1. Create bootable FAT32 DOS USB stick with http://rufus.akeo.ie/ 2. Copy all files from attached zip on the stick 3. Make sure in BIOS Legacy boot is enabled! 4. Boot from USB stick(legacy not UEFI). Once on DOS prompt type: eeupdate /nic=1 /d lan.eep This will write new LAN eeprom without changing existing MAC address, if you want to be pir8: eeupdate /nic=1 /d lan.eep /MAC=XXXXXXXXXXXX Where XXXXXXXXXXXX will be your new MAC address at your choice After this type celo then enter If it pass all tests then you are good to go on OS X for test. Have fun! (Attached file QLAN.zip) _______________________________ 3) But I think my results were different than skwakk’s as initiating the initial eprom reprograming command line resulted in a “Cannot open image file” reply from FDos… After rechecking my typing and getting the same reply, I gave the celo command and learned that my Nic failed the eeprom test. 4) I thought maybee the tools in King’s QLAN.zip were old, downloaded their current iterations from Intel, copied on to both my old FDos usb and a brand new one made with current FDos version and still get the same results. At this point I think I need to sort out how to implement using an ethernet card without the issue of not being able to log on to the App Store? Any thoughts/directions appreciated…best (and apologies for any autocorrect “oddities”) - Hopkins
  5. Hi again and FYI, I’m still working on getting my Quo MB back up and running and seem to making slow progress. So far: 1). I had problems on Thursday creating a new Yosemite installer usb on both of my Mac Mini’s; namely both of them were refusing to unmount the usb drives after completing the installer creation routine...I’m pretty sure this was a result of whatever updates Apple was pushing that day as yesterday the routine created/unmounted the installer media flawlessly. 2). I also kept running into lots of weird errors like being unable to mount installer, no numlock on keyboard and still no LAN port showing up under OS X. So I’ve replaced my keyboard, stripped the MB back to no cards, rechecked all connections, reset CMOS a couple of more times and I now have numlock back and can mount my the new installer drive I’d created. Part of me is wondering if I had a “funky” keyboard or maybee the MB was being “deformed” in such a way to cause a “shortish” type of error like the memory issues that can result from having tightened a couple of mounting screws too tightly? 3). My copy of Windows was pretty old and out of date so I bought a new copy of Windows 10 and installed it to make sure I had an uncorrupted/licensed version up and running to ensure my system was working and stable, etc. So I think I’m ready to proceed with installing Yosemite now that I fixed after fixing a few bugs - although I have another question in terms of workflow: In terms of Ozmosis creating the EFI partition on the 1st HD when you flash it into BIOS, does it get erased OS X installation process if/when you reformat your root disk before initiating the operating systems’ installation? IF SO, would you need to reflash your Oz BIOS between formatting your Root drive and OS installation? I might be “overthinking” or misunderstanding something and thought I’d better clarify... Best and much thanks for all the help/directions getting this far - hopkins
  6. Another couple of question if you don’t mind? 1). I have multiple “legal” copies and installation usb’s of Yosemite I’ve purchased and downloaded from the App Store for various Hackentoshes and Mac Minis’ I’ve built and purchased. Is there any reason to download another copy or am I ok using the installation usb that I already have? 2). Which of the current Ozmosis bios download and machine emulation should I use if my goal is using this machine as a basic DAW to run Pro Tools on? Not sure if that’s even a salient question to ask but thought I’d ask since I get a bit confused trying to sort out the various iterations. I know the MacPro 3, 1 is the default but wondering if I’d bee better served using a different machine definition for the smbios stuff in my default plist? Again much thanks for the guidance!
  7. Thank-you Ammoune78 and IronmanJFF for your replies! I finally found an Win8 installation disk, removed all of my PCI(e) cards/hdrives, and installed Windows 8 and now my MB LAN port works! Much thanks for that advice as I’ve been futzing with this issue for at least a year!!! I’m thinking at this point my best bet is to take my bios all the way back to the QUO original, make sure my LAN port is working, install Ozmosis from scratch then Yosemite so I can rebuild my DAW machine and make sure there’s no problems lurking in the background. Does this sound like a sound plan? Best and thanks- Hopkins
  8. Stopped working isn't clear enough to know what happened, try to describe Ethernet on Network Interface in Preferences still there or not, enabled or disabled: The LEDs of the Ethernet Port on your QUO board are enabled or disabled, is there any light: You can do an ONYX.app to clean your OS, there are some Terminal command that you can do to know if it's just an fair problem, and you can also reboot your Reuter, you can try unplugging and plugging the Ethernet cable from both QUO and Reuter. For better diagnostic, you need two different types of OS's, just to make sure that it isn't hardware problem IMHO! If you have two OS's installed (i mean macOS-X and another OS), and it only happened with macOS-X, then try re-installing the same macOS-X version from clean install. Now if you have that problem on the two OS's, try flashing the bios with the same version or the latest one. it is really rare for an Ethernet Port or Card to become defective on an motherboard, especially if it is from an good manufacturer! ______________________________________ Thanks for reply and kindness regarding my lack off knowledge. My on board LAN disappeared and doesn't show up in either my system information list or under network in my preferences. When I plug the ethernet cable into the Motherboard's LAN Port, its' indicator light is orange; when I plug the ethernet cable into the Card's LAN Port, its' light is green. I have tried reflashing my BIOS and re-installing Yosemite multiple times but not using a different OS which sounds like great idea. However what really lights up for me is your comment that it's rare for LAN Port or Cards to become defective...I've always run this board as a vanilla set with an i7-3770K and 32GB of RAM to run Pro Tools on. I had been using both the board port and a LAN card at one point and wondering if I managed to totally trash my ozmosis defaults in the EFI directory? Below I've pasted a copy of the entries are in my current Ozmosis default plist file in hopes that someone can look at it and tell me if it’s ok or missing any key entries? Also, if it is messed up is there anyway to obtain a current vanilla copy of the Ozmosis defaults entries for the Z77MX-QUO-AOS motherboard that I can try before I try before installing windows? Thanks for any helps or thoughts - Hopkins <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Credits</key> <string>Created with Champlist</string> <key>SMbiosvendor</key> <string>Apple Inc.</string> <key>SMbiosversion</key> <string>MP31.88Z.006C.B05.0802291410</string> <key>SMboardproduct</key> <string>Mac-F42C88C8</string> <key>SMfamily</key> <string>Mac Pro</string> <key>SMproductname</key> <string>MacPro3,1</string> <key>SMserial</key> <string>G8819C80XYL123456</string> </dict> </plist>
  9. Hi - I have an odd problem with my Quo AOS motherboard, namely my LAN port suddenly stopped working awhile back and I’ve been having to use a separate LAN card to establish internet connection. It also seems I can't to the App Store anymore secondary to not being recognized... I’ve done multiple searches/readings of this forum and the web and can’t seem to find anything about it. Has anyone else had this issue or information about fixing it? I suspect it’s something simple that I’m just not finding or seeing. Best and thanks for any help-Hopkins
×