austin

Members
  • Posts

    66
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

austin's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. I tried searching through this thread, but not finding much. Is it possible to also use this driver with a QEMU VM? I'd like to try passing it through to my OSX VM but can't figure out how to edit my QEMU XML to include it.
  2. Well I was working and excited until I rebooted my entire unraid box and the entire VM disappeared. Is there an XML file somewhere that I can re-add it?
  3. anyone else with a conbee 2 been down since december? I have and cannot seem to get it back working. I upgraded the firmware using a separate laptop, have USB manager set to connect as serial and right now its showing up as QEMU in HA. I've also had it showing as dresden, but it fails to connect during the integration install no matter what I try. I've rebooted, I've tried different integrations, i've done it all. I think its something with unraid but can't figure it out. I'm on unraid 6.12.6 and home assistant 2024.1.4
  4. So I successfully booted up and even got updated to the latest OpenCore! I was hodge poding a lot of docs but at the end of the day, it's working perfect. I have iMessage working (I cloned an actual serial number for an old broken laptop I have laying around) and everything is smooth! I learned pretty quickly that people seem to hate on OpenCore Configurator, so I switched and used a number of different tools to get to the endpoint. 1. I used MountEFI.py at first https://github.com/corpnewt/MountEFI to mount my EFI 2. Then OCAT (OpenCoreAuxillaryTools) https://github.com/ic005k/OCAuxiliaryTools to upgrade my EFI to the latest opencore, there is a button to do this and it handles it all for you. You just need to mount the EFI, which I ended up having to do with OpenCoreConfigurator's mount option (I already had installed, but didnt end up using it besides for mounting) to mount the EFI that the unraid box was actually using. By default MountEFI.py was mounting the EFI of the boot drive and not the secondary disk from the unraid VM. 3. After updating you'll have an exclamation point at the top center of OCAT, this runs OCValidate which checks your config.plst. I had to update only one configuration to fix, which I just googled. It required me to go to NVRAM in OCAT and delete one of the reocrds and replace with a new value. 4.I think I might've had to do something in ACPI by running https://github.com/acidanthera/MaciASL and changing some CPU pinning thing or something, I did so many random things that I probably have all of this wrong. BUT, it works! So I dont care.
  5. Thank you Ghost! Trying this now. One question, can I still use the OpenCore configurator to set my serial number? Does anyone know which version of OpenCore Configurator is compatible with this macinabox method?
  6. Ok so everything went smooth as butter following the older spaceinvader video the only weird part was when I downloaded OpenCore configurator it said this is an older efi, i just ignore this and continued following along. The next "weird" thing was that the EFI partition didn't include the NvVars file, just the EFI folder. Again, ignore and copied it to the correct partition. After this, I shutdown and followed some of his edits to the VM helper script (adding name, etc). I tried adding some CPU's and updating RAM and I've never been able to boot again. I get this error in the log at the moment: 2024-01-13T22:46:40.073081Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2024-01-13T22:46:40.073111Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2024-01-13T22:46:40.074095Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2024-01-13T22:46:40.074103Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2024-01-13T22:46:40.074948Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2024-01-13T22:46:40.074955Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2024-01-13T22:46:40.075725Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2024-01-13T22:46:40.075732Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] qxl_send_events: spice-server bug: guest stopped, ignoring I tried changing the topology setting in the helper script and changing the custom to "unraid" neither of those changes made any difference. So I also tried putting my CPU's and memory back to where they started thinking it was related to that and it seemed to still have an issue. Any ideas what I can try or do I have to start over all together?
  7. Overview: The Falcon Player (FPP) is a lightweight, optimized, feature-rich sequence player designed to run on low-cost Single Board Computers (SBC). It was originally created to run on the $35 Raspberry Pi, hence the middle 'P' in the short name but now the FPP supports many more systems. It is still mostly commonly used on a Raspberry Pi (Zero, 2, 3, 4) or a Beagle Bone (Black, Green, Pocket). The FPP shorthand is still used but it is now just called Falcon Player. FPP aims to be controller agnostic, it can talk E1.31, DDP, DMX, Pixelnet, and Renard to hardware from multiple hardware vendors. Using various capes, FPP can also be a controller on P5 and P10 Matrixes, or strings of ws2811 pixels. Application: FPP - Falcon Player GitHub: https://github.com/FalconChristmas/fpph
  8. I haven't heard anyone talk about this, but makes sense to do. Let us know what you find out, as i would do the same.
  9. You'll probably want to contact the developer in Discord channel. I'm not able to provide support for the app itself, just the unraid community app configuration in this thread.
  10. Fixed in the XML. Thought I fixed this last night but realized I didn't. Should work now.
  11. Overview: StreamMaster is a versatile streaming application that allows users to import an unlimited number of M3U and EPG files for a wide range of streaming content. The platform offers robust analytics tools for tracking performance and gaining insights, as well as customizable logos for a unique user experience. It also features seamless integration with popular streaming platforms like Plex and Emby. Built on the latest React and C# core technologies, StreamMaster ensures fast and reliable streaming across various operating systems. Additional features like robust proxying and the ability to have multiple clients on a single backend stream make it a comprehensive solution for today's streaming needs. Application: StreamMaster GitHub: https://github.com/SenexCrenshaw/StreamMaster Discord: https://discord.gg/zACbUp6XvW
  12. Following because I'd like to give this a try as well
  13. Seems like most of the official documentation around hardware is deprecated and not really very usable. I last built an unraid server in 2012. It's still going strong but it is using a bunch of random drives from all PC's and the cache drive is throwing errors, another over heats all the time, but it still hums along quite nice with a AMD FX processor. However, I'm trying to just start to understand what is required these days for an effective unraid machine. I've tried reviewing some forums here and watching some guides on youtube, but really, what are the key features you need to get the best bang for your buck? I recall when I bought the AMD processor there was something about core virtualization and making sure it was compatible. Does stuff like that still exist? Do I need to make sure it can do something like GPU passthrough, special PCI lanes for speedy cache drives, ECC memory? What would you tell someone looking to build a "bang for your buck" build to look for? I'm sure the main question is, well it depends on what you are doing. Let's assume running a VM, maybe a few docker images, storage, and maybe attempting something fancy like running Starcraft 2 remotely (is that even a thing?). Anything that'll get me down the right path would be super useful. Right now i'm at the throwing darts at the wall stage and don't know where to start.
  14. I've never had to assign tuners to my Xboxes and I preordered the ceton when it first came out. Stills works as good today as day 1, really well built hardware. I have two Xboxes and medicenter PC. No issues using all at once and recording a show. Sent from Galaxy S6 Edge
  15. This thread is awesome because it's exactly what I want to do. Are you still using this config? I would recommend using mcebuddy to move your files each night instead of batch files. It strips commercials and converts to mp4. I have the 4 tuner PCI card so that'll be a challenge. Have you tried using Emby? Since wmc is losing support, I'm wanting to create win 7 VM to record with ceton and use emby for live TV and playback. Sent from Galaxy S6 Edge