I imagine there are a lot of monitors out there with bogus EDID serial numbers, since it isn't important for getting the display modes right. using incorrect units for the physical dimensions or leaving placeholder/OEM data for vendor and model number that don't match the finished product's advertised vendor or model number. However, errors in EDID are quite common, e.g. There is a field for a serial number parent is proposing using this to identify individual monitors. It contains data like the vendor, model number, physical screen dimensions, and supported display modes. INF file to install in Windows or the supported sync ranges to type into your XFree86 configuration if you wanted anything above 640x480. It essentially enables "plug and play" for monitors, as opposed to the bad old days when you needed either an. I’m almost bothered enough by it to switch jobs to go there and work on fixing it.ĮDID is a little EEPROM inside virtually all modern monitors with a standardized format, which can be read over the display cable. Why is this suddenly harder than putting a Tesla on Mars? Why don’t we have good real wireless HD displays by now? The current state of affairs with Apple laptops and docking is just sad to me. It worked damn great, nearly every time, even with sleep States in Linux on a laptop 10 years ago. It was a single (albeit proprietary) connector, and the dock was fairly expensive (~$200 IIRC). The dock powered the laptop and a mouse, keyboard, external drive, and two monitors. About 10 years ago, I had a Dell D830 running Fedora and later, early versions of Gnome shell. So, plug in, wait 5-30 seconds, nothing, open laptop, nothing, unplug dock, nothing, hold down fingerprint reader (the idiotic power button on the rMBP) until.nothing happens, then wait a random amount of seconds, stab it again, wait another 5-10 seconds for the Apple logo to appear, macOS boots into recovery (reset credentials screen, because it assumed that since I couldn’t log in during a boot that I need to reset my password I guess), restart, wait for disk decryption screen which doesn’t work with my wireless keyboard plugged into the dock, type in that password on the laptop keyboard, wait another few seconds for it to log in, ensure that WiFi is enabled as my normal network connection is via LAN via the dock which isn’t plugged in at this point, log in, wait for everything to start, close lid and pray that I don’t have to repeat this, wait another 5 seconds for it to actually sleep, plug dock in, mash random keys until it wakes up, log in again, rearrange monitor layout as it’s usually swapped L/R, one monitor doesn’t work, or they both don’t work again, fix that by power cycling monitors / dock, then finally maybe do some work if it’s not yet lunch time.įor a ~$6k setup, it’s awful. This is when it works at all, without having to guess if the laptop is actually on, because it’s the rMBP which has no power indicators despite having a useless oled screen across the top of the keyboard. Half the time, when I go into work and plug in, I get 30hz sync on the monitor plugged into the dock. This is idiotic, but I wouldn’t mind so much if it actually worked consistently. Because of apparently some lame design decisions, in order to run dual external monitors over a single TB3 port, you need the dock, which has one DisplayPort output, then a TB3-> DisplayPort (via USB-C alt mode IIRC) dongle plugged into the dock. I use the OWC TB3 dock with dual Asus PA328qs with the latest firmware. Why it doesn’t do this and “tries” to guess their position somehow is beyond me. Store the screen layout using serials from the EDIDs. Throughout this Apple Support has been anything but (aborting when for some reason my Mini’s S/N failed to match their records for Server machines, and thus bailing on me on the premise that I shouldn’t have RAID anyway so basically screw me.) On Monday I’m gonna nuke it again and try another route from scratch. Currently permissions are so fucked up I can’t even stream music from iTunes. I re-defined my home folder to be on the second drive but cannot log in until I’ve logged into a utility account and mounted the encrypted partition separately. After failing to re-enable RAID I broke my system into individual root and /User partitions on separate drives (or tried to) and discovered that APFS (Encrypted) and /etc/fstab don’t get along. I finally managed to boot my system again on the 20th December. When I decided to reinstall my OS from scratch and reload from backups I discovered to my horror that mine was not a supported configuration and there was no way in hell I would be getting back to where I started from. High Sierra beta worked fine and upgraded fine to golden master and subsequent. My MacMini6,2 (2012 Server) has two SSDs RAIDed together.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |