One of the hashtags _guru
While I'm busy configuring the VM I thought it would be good to get a nice taste of Italia
With the compliments of Sesto Giovanni I got some Birra Moretti from a friend of mine in Europe
From the photographs and the hashtags it must be obvious what I'm doing. Creating a virtual machine with which I will go into simulation mode to ride beautiful machines of absolute maximum Torque and Power
Since the /e/ Operating System is a fork from Lineage OS I was not surprised that my particular phone is not supported at this time
What is hot warming is the fact that capable programmers put their time, money, food & drink & sweat into enabling users to rip themselves from the grip of the Duo Poly which exists of Apple and Google
This is the main page of the Murena /e/ OS driven phones
Jumping in right at the most important section which is the supported phones on Murena /e/ which is an operating system alternative for Android phones.
I bid thanks to the individual who taught me about the existence of this operating system
#MurenaOS #bash #csh #ksh #sh #kernel #parameters #POST #Linux #Android #programming #POSIX
On this page you can clearly see how difficult Xiaomi makes it to install an alternative operating system; the bootloader unlocker is unbelievably program which is proprietary and runs in a proprietary operating system. Now I would have run it if my model was supported specifically
Xiaomi only allows you to unlock four devices a year, just four devices a year
#LineageOS #bash #csh #ksh #sh #kernel #parameters #POST #Linux #Android #programming #POSIX
https://wiki.lineageos.org/devices/earth/install/variant1/#unlocking-the-bootloader
Those of us who have other phones can check if another Linux for Android runs on their device
Atm I'm looking at Lineage OS for my Android devices
I have scrolled through the most important parts of lineage us website.
One thing that you have to realize is that you're taking a grave risk when you are installing another operating system on the Android phone, at least that's what the manufacturer will tell you.
The manufacturer will **not** tell you that, you're freeing yourself from their **stranglehold** when you do this.
They will also not tell you that chances are, your device will work much more efficiently, because it will not have any bloatware, I repeat any bloatware what so ever
One thing they will never ever tell you, is that they make deliberately as difficult as possible for you to install another operating system, on your phone, your device, which you own, which you are the absolute Master of
The phone manufacturer will absolutely make sure, that they will never tell you, that they even put traps on your phone, when you install another operating system, just so that it bricks, so that you come running screaming and go back into their strangle hold
All these factors make installing another operating system on an Android phone risky, tedious, nerve wracking, and not worth it, if the phone is brand new, and the money you spent on it, isn't just chump change that you can easily afford if it breaks.
Just looking at the enormous list of do's and don'ts that you have to follow to the letter, clearly show per model, per manufacturer, how many traps have been put in, just so you are prevented to install another operating system, with which you free your phone from the stranglehold of the manufacturer, a phone that you have bought with your money, a phone that you own, a phone that you have the right to put whatever operating system you want upon.
On top of everything, your specific model of phone, needs to be supported even if there's just one letter difference, you should not even attempt to install that version of Linux on your phone, because the chances of breaking your phone literally bricking your phone, are astronomically High
The phone I need Lineage OS on is the one I'm working on right now, the phone overheats dramatically fast, has very poor physical Cooling, which became apparent when a broken patch was pushed to the phone, by Xiaomi, a couple of months ago.
Because of the overheating it needs to be shut down for most parts of the day making it a useless device
Xiaomi does the following to make it very difficult for you to unlock their fabricated devices:
* The boot unlocker is personal and you need to make an account for it
* An arbitrary limit is put upon the amount of Xiaomi devices that you can unlock per day per week per month.
* Every account can only unlock four devices
* Essentially Xiaomi is sending a f$ck you, towards you, as the owner of your devices, when you want to unlock the bootloader, so that you can put an arbitrary, much more stable operating system on the devices which YOU possess
My specific device is not supported yet by Lineage OS Xiaomi Redmi Note 12S
That means that I have to stop right there because the installation sequence specifically states that you need to double check that the image you put on the device is specifically designed for not only your model but your model to the letter so I need one for the Xiaomi Redmi Note 12S
By now I do not care which Linux distribution I put on this Android, just as long as it's specifically supported
The Journey through which I went to attempt to install Lineage OS on my Xiaomi Redmi note 12s has taught me the following
Android phone manufacturers do not like their clients. Android phone manufacturers detest their clients and treat them like slaves. Android phone manufacturers want their phones to be theirs forever, even when they sell them to you.
The rights to own a physical piece of hardware, are irrefutable yet manufacturers hate your rights in that respect.
Quite disturbing, this conclusion I came to, after the above research was done
In #CatNews the tuna in spring water has entered the #cat #system and all cat #parameters are now at acceptable norms.
Fvwm is the first Window Manager I used in Linux, way back when you had to compile everything yourself from scratch. It made me think of the Amiga Magic User Interface, which gave fvwm a very familiar look and feel
#UI #DE #XFCE #fvwm #Desktops #Max12
#bash #csh #ksh #sh #parameters #Linux #programming #POSIX
Since the people who know about kernel parameter parsing via GRUB, did not see my post and because I forgot to use the AksFediverse hash, I hunted for an answer and am reading this one...
https://linuxconfig.org/how-to-set-kernel-boot-parameters-on-linux
This looks good, right? I can make unlimited desktops in XFCE, yeehaaa!
The big but(t) that I may only define 12 shortcuts to go straight to them, out of the box, but I have 16 now!
Now I have to go hunt for the config files, edit one by hand so I can make 16 specific shortcuts. Why limit the ammount and not put an easy option to add more if you need them, I ask myself. Now I need to kludge beyond desktop 12 and use CTRL ALT RIGHT, pfff
#UI #DE #XFCE #Desktops #Max12
#bash #csh #ksh #sh #parameters #Linux #programming #POSIX
This is the massive list of GRUB sub commands that I have to wade through
I have taken a Higher Grade Android to make this photograph and luckily this camera system knows how to capture the Light of the IPS LED panel in Total Darkness.
Compliments of Open Camera Android version
I'm going to include another photograph to give you an indication of how complex GRUB is in comparison to Legacy Lilo
When I press tab twice in Rapid Succession, the whole screen is filled with commands that I can execute within the GRUB sh {command environment}
I literally have to read all the man pages of those GRUB sub commands which give me an indication that they can do what I want, just so I can pass the parameters to the kernel
GRUB has made the distance between the command prompt and the kernel much bigger!
The camera of the Android is utterly failing to focus on the dimly lit IPS Led flat panel screen, but I have still captured a photograph of the command shell of GRUB
I have found the way to add parameters to the kernel at both time from GRUB
I'll make a photograph in a number of minutes
I dived into the disappearance of Lilo on all distro's. It turns out that Lilo was only usuable on BIOS, it did not evolve to UEFI systems.
I wanted to easily pass commands to the kernel pre-boot. Before I dive into the workings of grub, can anyone tell me where i Need to go to parse pre boot parameters through grub to the kernel?
Jumping in deep immediately
OS Linux
Kernel 6.x
found workaround for hardware errors on critical timer tsc
snippet from dmesg
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 1796.607 MHz processor
snippet two
[ 0.068905] AMD-Vi: Using global IVHD EFR:0x206d73ef22254ade, EFR2:0x0
[ 0.069804] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.074120] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x19e5a467a58, max_idle_ns: 440795257552 ns
[ 0.074127] Calibrating delay loop (skipped), value calculated using timer frequency.. 3593.21 BogoMIPS (lpj=1796607)
[ 0.074141] Zenbleed: please update your microcode for the most optimal fix
line [ 0.074141] clearly states that my microcode is not updated (not related to tsc)
[ 0.210124] TSC synchronization [CPU#0 -> CPU#8]:
[ 0.210124] Measured 2808 cycles TSC warp between CPUs, turning off TSC clock.
[ 0.210126] tsc: Marking TSC unstable due to check_tsc_sync_source failed
[ 0.210176] #1 #3 #5 #7 #9 #11 #13 #15
I added tsc=unstable to the boot options in grub, so from what I read here the parameter was passed to the kernel? Can someone please verify for me if this output states that?
The warning I get is that the BIOS of this machine is broken! and that the option tsc=unstable will work around that massive bug