06 June 2017
After searching for a while, I find this (quite old and still an issue). So the problem is the hicolor icon theme... ffs. Let's fix this (atm, it's quite different to fix it, but it works):
1) Go to this folder: /usr/share/pixmaps/pidgin/tray/hicolor
2) Make a backup or just rename your 16x16 to something else (16x16.old will do it)
3) Link or copy your 22x22 to a new 16x16 folder
4) Restart your WM
It's quite an odd fix, but it works (until someone fix it properly and I have OCD with the problematic icon).
08 February 2017
[ 1063.859661] IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u3: link is not ready
[ 1063.907145] R8188EU: ERROR indicate disassoc
[ 1064.008095] IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u3: link is not ready
[ 1065.279303] R8188EU: ERROR indicate disassoc
[ 1065.380294] IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u3: link is not ready
[ 1065.430806] R8188EU: ERROR indicate disassoc
12 December 2016
At first, only people in MacOS and Windows have some sort of mental illness about "NO, YOU DON'T NEED TO DO ANYTHING, THE ENTIRE OS IS JUST OPTIMIZED FOR YOUR NEEDS, IT WORKS IN THIS WAY". Now this starting to land on linux, so let's get started.
If you really want to protect a fat32 from damage and mounting at boot (like the EFI partition), just use sync option in fstab and you're good to go.
This is hideous and sad. It's not about having something to hide you sick fuck, it's not about being a criminal or having some illegal in your harddrive. This doesn't mean that any jackass company have the right to spy on EVERYTHING YOU DO. Or even worse if you think in man-in-the-middle scenarios (anything can create a bug making man-in-the-middle possible, a lib, a software, ANYTHING).
If you need to use windows 10 for whatever reason and you're not mentally disable and want to stop microsoft to messing up your privacy, use my post.
22 November 2016
03 October 2016
31 August 2016
If you're here, then I don't need to say that this solution will erase everything inside your Vita.
- Card doesn't detect at all, even restoring the defaults
- If you try to format inside the settings, it'll give you an error C2-12828-1 (AFAIK, it's a pretty much an old windows GPF, thanks for nothing, Sony).
- Even reformating the entire device, doesn't fix it.
- Enter in SAFE MODE (turn off the device, press power+PS button+R Trigger for some seconds).
- Format Memory Card (it will restart the device).
- Enter in SAFE MODE again, Restore the PS Vita, it will restart again.
- Enter in SAFE MODE for the last time and rebuild the database.
27 July 2016
I have a repository with some experiments and useful stuff (for the braves).
It's a collection of proprietary blobs that I use on some of my tests/ports. Useful if you own one of those devices and want to port some rom or try some obscure stuff with the related hardware.
Not populated (yet) because I'm lazy.
That's a collection of UEFI firmwares (or bios files, if you're stuck in the past), DSDT (fixed and original ones) and many other things related to UEFI platform.
I've organized the directories to have the original UEFI firmware and my updated one, to be easy to identify. The updated one's have the last upgrades and fixes available for the related hardware on the pertinent motherboards (since the manufacturers doesn't give a crap to update their hardware firmware properly and fix dreadful bugs).
It's well assembled and tested by me. Works for me (doesn't mean that will work for you, so if you make a gamma ray generator using one of my custom firmwares, you're at your own).
Have fun and as well, depending on my free time, I accept patches and/or requests.
This isn't a real howto, is more like a safeboat.
Everybody knows the problems of proprietary drivers in linux, and everybody knows how sweet those companies are about that. They think someone will stole a chip idea just looking to the fucking source code of a fucking driver (well, I don't see any other reason to be less stupid than that). Well, isn't only the fact that those closed-source drivers have compatibility issues, they're broken, incomplete and incompatible MOST of time.
For example, why the binary drivers doesn't work with a lot of type of configurations? Because "fuck you" - ATI/NVIDIA says. Why the binary drivers doesn't work with EFI framebuffer, since is something that just cames from the firmware? Because "fuck you" - ATI/NVIDIA says. Really? Incompatible with EFIFB? So huge companies like ATI and NVIDIA aren't capable to make a fucking less-retarded driver that works with the goddamit EFIFB that is so common than textmode?
Eh.. there's no solution...Well.. sort of...
1) Making two different kernels
This is the most secure and easy way.
Make the first kernel without any framebuffer, with a different name (you know how to customize your kernel name, right?), so you can enter in single mode if something happens. Another one without any framebuffer, with your binary driver proper installed. I have this configuration in my funtoo install without any issue. However, you'll need a different approach if you use CloverEFI instead of rEFInd (nothing to hard to deal, if you're here already).
2) Don't use EFIFB at all
It's quite dangerous if something happens. But still, you can make a pendrive (or use a sdcard with at least 128Mb of space and configure some bootloader to deal nomodeset in case of some emergency).
3) Don't use proprietary drivers
Disregard the problems of proprietary drivers, the opensource drivers aren't well to use in regular basis (Yet? YET?). But the choice is yours.
1) You don't need a bootloader if you use rEFInd or CloverUEFI. Learn about EFISTUB. You can even pass a kernel cmdline using EFISTUB, but isn't necessary since rEFInd and CloverUEFI can pass kernel cmdline without any problem at all (I use rEFInd+EFISTUB with initram incorporated to vmlinuz+LVM).
2) The ATI/NVIDIA drivers make your life harder as hell when you want to use EFI.Apple devices with nvidia cards doesn't have this problem because their EFIFB ARE NvidiaFBs, no big deal. Same for some IBM devices I did some research (of course I didn't use a proprietary driver on a server). Don't know about motherboards with native ATI/NVIDIA, also don't know about notebooks with discrete cards (my notebook with a nvidia card doesn't have EFI, unfortunately).
3) I've already tried to trick using CloverUEFI and even modifying my firmware and SMBIOS. It doesn't work anyways.
4) There's some options for the kernel change on-the-fly the framebuffers drivers from EFI to any some others drivers to make a more "native" approach, mysteriously those two big companies are not able to achieve this (efifb can change on-the-fly to nouveau, nuff said).
Update 20170515: They work now, you can use efifb+proprietary drivers, don't know exactly who had the problem atm.
16 June 2016
All the extra uninstalable crap in windows 10 isn't enough, microsoft? WTF?
Well then, just stop with this nonsense, open regedit and go to this key:
Create a new 32-bit DWORD value named DisableWindowsConsumerFeatures and set its value data to 1
Or use this with an administrative prompt:
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent" /v DisableWindowsConsumerFeatures /d 1 /t REG_DWORD /f
22 May 2016
Actually, I have a Toshiba Qosmio with a windows machine and after the "free" upgrade to windows 10, I see that even my notebook with a US-English Windows, US-English Keyboard, and yes US configurations for everything, give me automatic keyboards because I'm in Brazil (WTF?). Not sufficient, that's a ridiculous arbitrary retarded feature, because he gives not one, but, FOUR LAYOUTS!! WTF? (US, US-English, ABNT, ABNT2). And guess what? He changes from one to another automagically, just to mess up your work, your brains, your life and everything else, because yeah, you're using windows so fuck you!
After mining google, someone had the solution here.
Simply change this thing on registry (because windows doesn't want to give you an option to change THIS SIMPLE THING):
Disable the obnoxious "Auto Detect Keyboard Layout":
Administrative command version:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard\Layout" /v IgnoreRemoteKeyboardLayout /d 1 /t REG_DWORD /f
If the language crapbar still shows, use this DWORD:
Administrative command version:
reg add "HKEY_CURRRENT_USER\Software\Microsoft\CTF\LangBar" /v ShowStatus /d 3 /t REG_DWORD /f
01 April 2016
Apr 1 09:17:50 ubuntuVM sshd: error: Hm, kex protocol error: type 30 seq 1 [preauth]