0x4E4F @ 0x4E4F @infosec.pub

Posts

21

Comments

913

Joined

2 yr. ago

Have no idea what that is to be honest 😂.

What about cups, they have no driver for that printer there?

I have a LaserJet 1000, 20+ years old, only works Linux and Windows x86 😂... so I just set up a peint server and shared it 🤷.

Trust me when I say this, that wasn't always the case 😔.

Yeah, they came in later on and that's why I think they were "better"... learned from experience with the wifi drivers. And they weren't really better, most of them still use binary blobs.

Or switch wifi cards, have done that as well when there was no other option.

I just think you've had the luck of not having a lot of unsupported hardware on Linux 😂.

Yes, in general, things are OK driver wise, but remember when we had to resort to ndiswrapper to get wifi working... yeah, that was a pain 😔.

Use that till the drivers get released... temporary solution, but there isn't a better one at the moment 🤷.

Try Void, maybe it has the adequate firmware binary blobs... worth a try 🤷.

There are some oddball cards out there that need the linux firmware xxx (insert manufacturer instead of xxx) binary blobs in order to work, but yes, those cards are rare nowadays and mostly older hardware uses that (as you mentioned, hardware from 10+ years ago).

Have no idea to be honest, I stole the meme 😂. But yes, I have had problems with wifi drivers on Linux. Not a lot, but still.

And yes, I'm still trying to get an old Microtek scanner to work in Linux 😔.

Yeah, the Chinese stuff seems to work better under Linux... for some reason 😂. I one based on a Realtek chip (I think 🤔) and I couldn't get passed a few hundred KB in Windows. Linux fried that baby, it did 1.5MB 😂.

Yeah, but Timeshift uses the Ubuntu style subvolume naming, @ for root, @home for /home, so you have to create them that way, otherwise, it won't work. It can work if you tell it to ignore home, but checks for @ as root on start up.

Awww man, thanks ☺️.

Good thing I love fiish, it's my default shell 😉.

Yes, you can just set it to mount a, let's say @home, subvolume to /home and that's that, done.

I know how to do that, you set the subvolume as the default one, thus, when mounting, if no options are passed, it always mounts that subvolume as root.

But, you have to disable that. Sure, I set it during install, cuz installers are stupid (if you tell it to install in /@, it will most probably moan), but disable it after first run (set the real root as the default subvol, i.e. mount point) and just add subvol mount options in fstab.

It's just extra steps I have to do now 😒, that's why the rant.

I need it because of Timeshift, it works with subvolumes only.

Yes, you can, but now I have to move the entire install to a subvolume, risking borking the install 😒.

Yeah, that should work, thanks 👍.

I just do lspci and install the adequate firmware 😂.

Timeshift works only with BTRFS subvolumes, thus, if you wanna have backups (snapshots), you have to have subvolumes and not install in the root of a BTRFS filesystem 😔.