β² 1121 βΌ Dual Booters be like (lemmy.ca) submitted 1 year ago by mintiefresh@lemmy.ca to c/linuxmemes@lemmy.world 84 comments fedilink hide all child comments
[β] possiblylinux127@lemmy.zip 2 points 1 year ago (1 child) That shouldn't be possible as the hardware gets reinitialized on boot permalink fedilink source parent hideshow 2 child comments replies: [β] MudMan@fedia.io 0 points 1 year ago (1 child) You would friggin' think. And yet. Turns out a DAC is a fairly complicated and self-sufficient bundle of software and hardcore electrical circuitry, so apparently you can mess it up so badly it will remain broken across soft reboots. Who knew! permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip 1 point 1 year ago (1 child) My guess is that somehow data left in ram is causing the driver to get screwy. However, that still wouldn't make sense as it shouldn't be using uninitialized memory. I guess do a full power off before switching OS. The other option is to just run a Windows VM. permalink fedilink source parent hideshow 2 child comments replies: [β] MudMan@fedia.io 1 point 1 year ago The other option is to just use Windows, which is the issue with these types of hardware incompatibility. I also have an ASUS laptop that won't use their slightly weird speakers correctly and, again, that whole thing makes it much less practical to boot into Linux instead. permalink fedilink source parent
[β] MudMan@fedia.io 0 points 1 year ago (1 child) You would friggin' think. And yet. Turns out a DAC is a fairly complicated and self-sufficient bundle of software and hardcore electrical circuitry, so apparently you can mess it up so badly it will remain broken across soft reboots. Who knew! permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip 1 point 1 year ago (1 child) My guess is that somehow data left in ram is causing the driver to get screwy. However, that still wouldn't make sense as it shouldn't be using uninitialized memory. I guess do a full power off before switching OS. The other option is to just run a Windows VM. permalink fedilink source parent hideshow 2 child comments replies: [β] MudMan@fedia.io 1 point 1 year ago The other option is to just use Windows, which is the issue with these types of hardware incompatibility. I also have an ASUS laptop that won't use their slightly weird speakers correctly and, again, that whole thing makes it much less practical to boot into Linux instead. permalink fedilink source parent
[β] possiblylinux127@lemmy.zip 1 point 1 year ago (1 child) My guess is that somehow data left in ram is causing the driver to get screwy. However, that still wouldn't make sense as it shouldn't be using uninitialized memory. I guess do a full power off before switching OS. The other option is to just run a Windows VM. permalink fedilink source parent hideshow 2 child comments replies: [β] MudMan@fedia.io 1 point 1 year ago The other option is to just use Windows, which is the issue with these types of hardware incompatibility. I also have an ASUS laptop that won't use their slightly weird speakers correctly and, again, that whole thing makes it much less practical to boot into Linux instead. permalink fedilink source parent
[β] MudMan@fedia.io 1 point 1 year ago The other option is to just use Windows, which is the issue with these types of hardware incompatibility. I also have an ASUS laptop that won't use their slightly weird speakers correctly and, again, that whole thing makes it much less practical to boot into Linux instead. permalink fedilink source parent
