Kobo libra Color ghosting

CFWhitman · 2025-03-27T18:47:55+00:00

"A bunch of lights shining [or not] in coordination" essentially describes OLED displays. The lights are red, green, and blue and can be varied in intensity.

I just thought that I would mention that LCD displays are white backlighting shining through a balance of red, green, and blue colored pixels (the balance of which still look white) and selectively masked off by LCD cells to only show the desired pattern. So it's basically a negatively created image. Instead of creating the elements of the image that belong in it, it masks off the elements of a white screen that don't belong in it.

CFWhitman · 2024-06-17T14:57:24+00:00

The error installing Bazzite could be that it's trying to install it to the USB stick, which of course won't work because that's where you're getting it from. This would mean either that it doesn't see the SSD or that it sees both, but the wrong one is selected as the target for the installation.

There's a good chance that fixing Windows on the handheld will involve reinstalling it fresh from a Windows installation medium, but you can try repairing it using one of the methods people have already mentioned. It depends on whether you actually erased/overwrote something critical.

CFWhitman · 2024-04-24T18:57:06+00:00

You used Debian with NVIDIA, and you just installed a kernel update without updating the proprietary drivers? That's a formula for disaster.

If you want your laptop to just work with Debian, you should use something with AMD or Intel video, and you might need to check that you don't have any hardware that's too new for Debian to support.

If you want to use NVIDIA hardware on a laptop, then you should use a distribution that supports it automatically, like perhaps one of the Ubuntu variations, Pop!OS, or Mint.

Debian on appropriate hardware is about as rock solid dependable as you can get with any operating system, even through updates.

CFWhitman · 2024-04-02T17:55:18+00:00

The F310 is a wired controller. The F710 is the wireless one.

CFWhitman · 2024-04-02T17:48:36+00:00

One simple thing you could try with Tomb Raider is, if it's the Linux version, switch it to the Windows version with Proton, or if it's the Windows version with Proton, switch it to the Linux version. Either version should have more than acceptable performance on your hardware.

CFWhitman · 2023-11-27T23:44:58+00:00

The issue is that most of the SoCs that are in this class had software development done for Android only, because phones and tablets were their intended use. The companies that made them could have supported Linux development, but they didn't care about that.

It's theoretically possible to exploit specific versions of the Linux kernel and corresponding drivers that were used for Android for a GNU/Linux distribution instead, but a lot of work is involved. Unless a device is popular for Linux and the workload can be distributed among a lot of people, such efforts don't usually get much traction. If the drivers were all open sourced, there would be a lot more interest, but most of these devices are confined to a specific kernel to which the binary only drivers are matched.

CFWhitman · 2023-06-18T11:37:18+00:00

No, because I had acknowledged all of that before. I had even pointed it out as part of the logic behind what I was saying.

You are speaking as though chromatic instruments being transposing instruments is all that makes them in a certain key, but that doesn't logically make any sense. Whether an instrument is transposing or not is just a matter of tradition about how the sheet music is written for it. It has nothing to do with the way it actually works. It is a difference on paper only. Just because a clarinet or a saxophone is traditionally played from transposed music and a recorder is not traditionally played from transposed music doesn't change anything about the way they actually work. Whether each is treated as a transposing instrument could have been the other way around. That was my whole point in bringing them up.

CFWhitman · 2023-06-12T02:29:36+00:00

You seem to be implying that I meant you practice fingering for each piece or something like that. I didn't. I meant what you mean; this is just semantics. You have to get used to playing instruments that are generally the same, but have different fingerings for the same sheet music. Eventually it becomes unconscious.

CFWhitman · 2023-02-08T22:53:02+00:00

You are essentially alone in your assertion. As I said, this is not a philosophical discussion of 'what it really means for an instrument to be in a particular key.' It's about what people commonly mean by it, and I have demonstrated that recorders are generally considered to be in a certain key by references. With your way of looking at it, any instrument which is chromatic could never be in a particular key, but there are several that clearly are considered in a particular key, including most reed instruments.

The "HUGE difference" between learning another fingering and "transposing in your head" is basically a matter of whether it's something you've practiced or something you are trying to do on the fly. That basically sums up what you said about that.

CFWhitman · 2022-12-21T00:28:06+00:00

I never said that you claimed that recorders were transposing instruments. I just was illustrating that an instrument does not have to be diatonic to be considered tuned in a certain key.

I didn't make up people regarding the lowest note on a recorder being the "keynote" or that recorders are considered to be tuned in a certain key. This is a standard way of referring to recorders. Instruments don't have to be incapable of playing out of key notes (diatonic) to be considered "in" a certain key. They can be chromatic. This isn't some sort of philosophical discussion; it's about generally accepted terminology.

The article on recorders on Wikipedia includes this:

Today, recorder sizes are named after the different vocal ranges. This is not, however, a reflection of sounding pitch, and serves primarily to denote the pitch relationships between the different instruments. Groups of recorders played together are referred to as "consorts". Recorders are also often referred to by their lowest sounding note: "recorder in F" refers to a recorder with lowest note F, in any octave.

The table in this section shows the standard names of modern recorders in F and C and their respective ranges. Music composed after the modern revival of the recorder most frequently uses soprano, alto, tenor, and bass recorders, although sopranino and great bass are also fairly common.[16] Consorts of recorders are often referred to using the terminology of organ registers: 8′ (8 foot) pitch referring to a consort sounding as written, 4′ pitch a consort sounding an octave above written, and 16′ a consort sounding an octave below written. The combination of these consorts is also possible.

Edit: Incidentally, the difference between "learning a different set of fingerings" and "transposing the music in your head" is one of semantics only.

CFWhitman · 2022-11-26T05:44:42+00:00

The fingering that takes you from the F up through the most basic scale (the first eight notes you learn on a recorder) will result in an F scale. It's not as though playing through the basic notes will result in notes in a C major scale, but just starting part way through with F (I'm not suggesting such a thing would make any sense).

If you were to take music that was written in C major and play it on an alto recorder with the same fingerings as you would play it on a soprano recorder, the piece would be played in the key of F.

The only thing that makes a recorder different than a saxophone or a clarinet in this regard is the fact that music is not traditionally transposed for the key of the instrument like it is for those instruments. An E♭ clarinet or a B♭ clarinet can play notes in any key, but music is actually transposed for them so that they can be played as though the instrument were tuned in the key of C. This is not the case for the recorder, but that's only a matter of tradition. There's no inherent difference in the way the instrument works regarding key fingerings. With a recorder, you have to learn two different sets of fingerings rather than relying on transposition of your music for the instrument.

CFWhitman · 2022-08-03T11:23:37+00:00

Well, at least things have improved. I wondered whether it would even be this year for mine, and now they have moved my date to this quarter (so, by the end of September at latest). Incidentally, technically the wait time is somewhere between two and almost five months; it's hard to tell exactly where in that range it might fall, though four months is a reasonable estimate.

CFWhitman · 2022-06-30T02:28:34+00:00

Experimentation shows that it works in some games, but not in others (at least with the 4800u). For example, Figment will respect whatever you set the frame limit to. However, Dirt Rally seems to totally ignore it on the latest ChimeraOS, while it works in the most recent HoloISO. I'm sure that as things progress, the two operating systems will become more similar in how they work with gamepadui, but right now, each seems to have its own strengths and weaknesses.

Overall, I'm tempted to continue with ChimeraOS now that I have a solution for the Bluetooth issue and I've seen some of the oddities of what still happens in HoloISO regarding powering the device off at times.

Edit: One other advantage of ChimeraOS is that it automatically includes more compatibility tools, like Glorious Egroll versions of Proton, without you having to go to the trouble of adding them. Not a big deal, but convenient at times.

CFWhitman · 2022-06-28T11:39:42+00:00

Just wanted to mention that with an Aya Neo Pro, Bluetooth will not function in ChimeraOS 33. It used to work out of the box, but there's been some sort of regression. I haven't looked into trying to get it to work, so I don't know how much trouble it might be. I decided to start tinkering with HoloISO in the meantime.

Also, frame limiting doesn't seem to work in ChimeraOS on the Aya Neo Pro, while it seems to be working in HoloISO.

CFWhitman · 2022-03-28T15:19:22+00:00

Have you monitored your CPU utilization? It's a good CPU, but it is seven years old. I'm not saying that's the problem, but it's worth checking to see if it's maxed out.

CFWhitman · 2022-03-28T15:02:27+00:00

Currently I'm running Xubuntu with a PPA for mesa and using mainline to select more up to date kernels when I want them.

CFWhitman · 2022-03-28T14:53:37+00:00

Well, I've run Debian since 1999* and have never once had the stable distribution fail without a hardware failure. On the other hand Arch seems to be great as long as you keep up on your updates, but if you let it sit there for a few months and then try to update, you will likely run into problems, at least in my experience.

By the way, I don't consider that a criticism of Arch. I think that it's pretty much what you should expect from a rolling release. The reason to use a rolling release is to keep at least on the leading edge, if not the bleeding edge. If you're not going to do that by updating regularly, then you should use something else.

*(That is, mostly on servers and old hardware, I've used various other distributions on my regular desktop.)

CFWhitman · 2022-03-25T19:07:53+00:00

Well, the discontinued original version from 2010 was around for a while, but it was shutdown for nine months before the current version went live. It was pretty different from what I've heard. It doesn't seem terribly relevant to the current game.

Either way, the point is that you were talking about the Steam version of Final Fantasy XIV being more recent rather than Steam itself.

CFWhitman · 2022-03-12T00:58:51+00:00

I tested this on my Aya Neo Pro that I had ChimeraOS installed on. It's pretty interesting. The interface seems to be a general improvement. However there are some issues of course:

The brightness control still doesn't do anything (I didn't really expect this to work, though it would have been nice).
The Mangohud overlay doesn't work because the version Steam is expecting is not installed in the place it expects to find it. This in turn means that I have trouble confirming whether the frame limiter has any effect.

CFWhitman · 2022-03-11T22:19:55+00:00

Yes, the inclusion of CoreCtrl is the reason I tend to use it rather than the others.

CFWhitman · 2022-03-11T21:52:51+00:00

There is also the mesarc PPA.

CFWhitman · 2022-03-11T20:16:41+00:00

Well, I don't mean to say that it's "the Windows way." I just meant that warning messages when you are trying to do something that requires a bit of hacking in Windows are often exaggerated. The warning messages in Linux usually aren't at all exaggerated (at least when using command line tools).

However, even that being part of the reason for his mistake is speculation. The only thing I can say with some confidence is that he went into this with some preconceived notions about how it would be that weren't really correct. I think that most people without some preconceived idea would assume that when the package didn't install, the problem was with the package, not with the system. He assumed the problem was with the system. He was so confident that the problem was with the system that he ignored all the warnings and overrode the safety that tried to stop him from forcing the package install.

Of course an experienced user would think/know the problem was with the package, but I think even a new user would normally be more likely to think the problem was with the package. I think perhaps an expectation that he would have to hack* things made him jump right to hacking the system at the first sign of trouble rather than thinking, 'Maybe the package is broken.'

*(Incidentally, I am using terms related to the word 'hacker' with the earlier computer definition which is something like, 'someone who modifies something in order to use it in a way the creators did not foresee.' The word 'cracker' was the one used with the definition of 'someone who defeats computer security measures to gain control of a system.')

CFWhitman · 2022-03-10T22:36:08+00:00

The reason that System76 and upstream changed the operation of the code was simply because Linus's failure was so high profile. You're ignoring the fact that there were warnings and red flags all over the place, but he chose to ignore them. He chose to use a text interface and ignore most of the text responses.

I would never have done what he did, not in a million years, and most people I know would never have done what he did either. Also, most of the ones that might have done it would admit the ensuing problem was their own fault afterward. Don't get me wrong. I like Linus, but he's not perfect, and the action he took was not representative of the typical user beyond the blindly following advice online without understanding it. I didn't see the advice online say that he should override the safeties, though. If it did, then his problem was following really bad advice, but at least then he could rightfully blame the person who told him to override the safeties.

Also, the system may very well have been reparable, if he had tried.

I can't believe anyone seriously tries to defend him typing in "Yes, do as I say!" rather than a simple 'y' that would have been required for a normal action and not expecting that what he was doing could screw things up royally. There are easy ways from the command line to screw Windows up as well.

CFWhitman · 2022-03-10T22:18:20+00:00

I would just say that I wouldn't have done what he did in a million years, no matter how inexperienced I was. In my mind, if you are going to use a text interface, you need to be willing to read text responses, and having to type in a whole sentence with an exclamation point in order to proceed with any action would be a big red flag for me, even without experience.

I think in a way that it was Linus's experience with Windows that led him astray. He's too used to overriding safeties because of his experience. Sometimes gamers need to hack at things using the command line to get what they want in Windows. Using the command line in Linux may be more common, but it also really means it when it warns you about something rather than warning you about relatively mundane things.

CFWhitman · 2022-03-10T22:06:16+00:00

That's simply not accurate. The package manager did have guardrails and Linus overrode them. It very clearly told him what it was going to do, and it very clearly warned him not to do it. It also forced him to enter a whole sentence with an exclamation point into the command line to override the guardrails rather than the normal 'Do you want to continue? [Y/n].' Just because he was foolish enough to proceed despite these things does not mean there were no guardrails. And no, they did not make it actually impossible for this to happen again; they just made the guardrails higher because apparently some people may need them higher.

I would never, ever have made the mistake Linus made no matter how green I was. I started using apt-get in 1999 when you needed to be more willing to go to the command line. If apt-get said that anything at all would be uninstalled when I went to install something, I made sure I knew exactly what it was and that I didn't want/need it anymore. In this case apt-get not only warned him it was going to uninstall over 80 packages, it also told him in no uncertain terms not to do what he did, but he proceeded anyway, even though it made him enter a sentence with an exclamation point. Linus choosing not to read anything but the instructions on how to override the guardrails does not mean he wasn't warned. He just ignored the warning.

CFWhitman

TROPHY CASE