RelativeArea0

joined 1 year ago
[–] RelativeArea0@lemmy.world 3 points 1 week ago (1 children)

Does commercial displays also has "smart" bs on it?

[–] RelativeArea0@lemmy.world 3 points 1 week ago* (last edited 1 week ago)

Personally, I really would not advise dual booting because the hassle is not really worth it, unless theyre on seperate drives.

It is because of mbr vs gpt partition and some weird bs from laptop manufacturers

Mbr are mostly on older systems and could only support up to 4 partitions, legacy boot works on this, so if someone decided to add another os, it adds another partition and most likely to jank that persons pc

Gpt is newer, could support more than 4 partitions, runs only on efi, so someone would be like, cool, why not set my drives to gpt instead

Unfortunately, most laptop manufacturers do some bs called instant lock to secure boot if you change to efi boot, the problem with secure boot is that it only works on 1 os, the manufacturer of that laptop already decided that you'll only run 1 os and its windows, so dual booting on efi is a no go

So if you really need windows in a linux machine is vm, try vm. Most vms support pcie passthrough, (unless acer has some weird implementation).

Or the other way around, nuke your linux then return to windows.

Or if your laptop has 2 drives, then you can go 1 drive linux, 1 drive windows.

[–] RelativeArea0@lemmy.world 3 points 1 week ago* (last edited 1 week ago) (2 children)

What i usually do nowadays when doing a fresh intall of windows is by using winNTsetup because it avoids too many steps if you have already decided to nuke the drive. You can download it from majorgeeks or have it preintalled on most portable windows like hirens, dlcboot or medicat.

Edit: oops my bad, sry, i got some bad reading comprehension, youre doing dual boot, ignore what i've said.

Dual boot is troublesome, even if you managed to make it work, it could mess your system, like for example, a windows update that could mess your grub partition thats why most people avoid it and use vm instead( qemu, vbox, etc.)

[–] RelativeArea0@lemmy.world 7 points 2 weeks ago

Aside from negative nature consequences caused by humans, they also eat themselves....so yea...sad.

[–] RelativeArea0@lemmy.world 2 points 2 weeks ago (1 children)

My only concern to these machines is that if theyre running an intel chip, its most likely to have intel ME which is a QOL stuff but a potential backdoor. Luckily, these cheap mini pcs has most of the time, an unlocked bios, so it is easier to pull the bios bin, patch it with intel ME removal and then reflash the patched bios.

I find the US branded ones (HP, DELL, etc.) more pain in the ass to patch the bios because most of them has locked bios. Doable but a pain in the ass for sure.

[–] RelativeArea0@lemmy.world 6 points 3 weeks ago

Both looks inbred, but not too inbred to have genomic erosion

[–] RelativeArea0@lemmy.world 8 points 3 weeks ago

HyperV4every1 version whateverthefuckitis

[–] RelativeArea0@lemmy.world 5 points 1 month ago (4 children)

For bloatware, this is what I use if you have access to adb https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/

As for privacy, I cant think of any approach for base roms aside from piping your connection through a vpn that screens every IP or domain from that device whatever it reaches to. Unfortunately, I dont know any vpn that could do that.

[–] RelativeArea0@lemmy.world 18 points 1 month ago

Until the bubble bursts

[–] RelativeArea0@lemmy.world 17 points 1 month ago* (last edited 1 month ago)

Why, instead of safely entering a BIOS setup

effiency and lawsuits, phones has embedded hardware, its a bit op to have that initial hardware calls for a embedded hardware system.

BIOS is initally an IBM tech

_does the cell phone brick when installing the Custom ROM wrongly? _

Android is based on linux, that includes the partitioned bootloader (mostly grub on linux and fastboot on android, they're not technically the same but the idea is somewhat related) if that partition is messed up then its most likely not to boot

Wouldn't this protection be better for users? I mean, this could be done through ADB.

Android is owned by a corporation, I dont think that will be their primary objective

Also, do you think it's possible that this way of doing things will come to the computer, with ARM hoping to gain a good share of the market and all?

ARM is mostly a cpu design corporation that offers license fee to other companies to manufacture thier cpu designs, they're everywhere. It depends on thier licensees what to add to make profit.

 

I mostly leaned on snapdragon because of its rich custom rom community thanks to CAF, now that it has been a year dead, i wonder whats next for custom roms? What chipsets (aside from risc v and google chips/tensor whatever tf theyre calling thier chips) that could fill what CAF has left?

view more: next ›