Linux - Reddit – Telegram
Linux - Reddit
778 subscribers
4.19K photos
207 videos
39.9K links
Stay up-to-date with everything Linux!
Content directly fetched from the subreddit just for you.

Powered by : @r_channels
Download Telegram
Will i need another hardware to test the kernel?
https://redd.it/1jnzisj
@r_linux
SATA SSD disappears on reboot command but not shutdown

I'm not sure what all information is required to help troubleshoot this issue so please ask whatever questions are necessary.

I have a PC running KDE Neon (ubuntu 24.4). Linux was installed originally on a SATA SSD that was over 12 years old (OCZ vertex4) and the SSD was mounted at /. Everything worked fine but the OCZ drive was so old it did not have all the modern SMART features and did not have the ability to provide remaining life status. I was getting a bit paranoid as the drive was old. Shutdowns and restarts worked with zero issues.

I recently wanted to upgrade the OCZ SSD and got a Samsung 870 Evo. I used clonezilla to clone the OCZ to the Samsung SSD. Everything booted up fine and worked. I noticed the drive disappeared on reboots and thought it was defective so I replaced it. I swapped back to the OCZ and ordered a WD Blue SATA SSD. Upon receiving it, I did the same thing. I used clonezilla to do device-to-device cloning from OCZ to WD. Booted up the WD and everything worked fine except the drive would disappear on reboots. Same as the Samsung I just didn't notice the pattern with the Samsung.

So starting to look into it more, when using the "restart" command in KDE, when the computer reboots and gets to the bios startup, the bios does not see the SSD anymore. The SSD has essentially powered down or went into sleep and wont wake back up. I have to remove power at the power supply and then power back up and bios sees the SSD just fine and boots. The shutdown menu button in KDE has no such issue. If I use the shutdown menu button and then turn the PC back on, drive is seen right away in the bios and boots with no issues. So something is happening or not happening with the restart KDE menu button that causes the drive to go offline.

Thinking that this might be some issue due to the original install being on a very old SSD which acted more like an HDD than modern SSD, I tried a fresh new Live USB session to test and see if that had the same issue. It does. Using the KDE Neon latest Live USB version, restart command kills the drive but shutdown command does not.

I think this might have something to do with EFI or APM. This old PC has legacy bios and not UEFI. Would someone be able to help me figure this out?

THanks for any help.

https://redd.it/1jo3uyn
@r_linux
Linux GTK Theme for a completely black and white setup with red accents

Hi there! I'm currently trying to rice sway to make it completely black/white with a few red accents and I wanted to ask if anybody can provide a gtk-config that matches the setup. I once tried to tweak GTK myself but I'm no pro and some things looked very weird.

https://preview.redd.it/tdxbeobdw1se1.png?width=1920&format=png&auto=webp&s=065e950faa7cf5240ffc8f709e0b73eaa29f95d3



https://redd.it/1jo76o0
@r_linux
Linux saved me from buying a new Laptop
https://redd.it/1jo84ln
@r_linux
bootable usb

hey fellow linux users, i created a bootable usb using rufus and when i click on try/install ubuntu a a ubuntu logo appears with the loading circle and after a minute or so the loading circle disappears and im just left with the ubuntu logo on a black screen. any ideas on what is happening that it is not loading ubuntu?


https://redd.it/1jof4jd
@r_linux
Why installing Linux is "hard"

I am someone who does not finding installing Linux "hard". Like many Linux users, I was already a proficient computer user when I started using Linux, and that was because I really like using computers. Installing Linux is "hard" for most people because 90% of users are hopelessly incompetent. Linux users will say "Ubuntu/Mint is just as easy as installing Windows" which is true, but the vast majority of users have not installed any operating system in the past 15 years and most of those people have never installed an operating system once. Installing windows simply is not a normal part of the user experience anymore, and so those 90% of users never interact with the bios and don't even know it exists. Shit, some particularly oblivious people likely don't even know that their os is called "Windows" you might think that's impossible given it's all over the screen but a lot of people don't actually read what's on the screen. All they know is that they bought a "Dell" or an "Asus".

That and also, a unix-like system is fundamentally different to windows in a way that is going to be very unintuitive to most users due to starting on windows. I remember being confused as to why Linux had no equivalent to ".exe" for executables, and why something like a bash noscript was in many ways treated the same as a binary, but now I see the sense in it and I prefer it to the windows way. Finding solutions for Linux problems isn't always easy since every distro has it's own quirks, and noobs don't understand that what they are actually interacting with most of the time is the desktop environment, and so they probably want a solution for a problem on XFCE, or Gnome, rather than Ubuntu or Manjaro. A GNU/Linux system is kind of just a bunch of software thrown in a pile which I'm not a huge fan and so I've been interested in trying FreeBSD for some time but that's besides the point.

Before a novice user can even live boot their Linux usb, they have to look up how to get to the bios, how to choose a boot device, and then they can live boot. And this sums up why I think Linux is hard - using Linux trails off into having to research a lot of unfamiliar vocabulary before you can really understand what it actually is you're doing. And that really is hard for a novice user.

https://redd.it/1jojmx9
@r_linux
Breathe! (Again! Antix and a story)
https://redd.it/1jomybt
@r_linux
Help plz... Getting my label printer working.

Hello All,
I have no clue if what I want is even possible.
I have a Casio Lateco EC-P10 label printer (https://www.casio.com/jp/label-writer/product.EC-P10/)
This printer was intended to run on Windows/Mac but, I am running Linux Mint.

The printer can connect to wifi, and the builtin application sends data to it. I attempted to use Wireshark to figure out what port it is on, but haven't yet figured it out.

The printer doesn't show up in the netework printers dialog.

I COULD run virtual box to talk to it, but my hope is to add this printer to my work flow where when I code an MCU using STM32CubeIDE I then trigger a process to print a label. I am all ready to get the process triggered, but sadly I can't figure the printing part out.

Does anyone know where to start on this, and if it is even possible at all?

Thanks everyone!

https://redd.it/1jonvwf
@r_linux
This is why I use linux
https://redd.it/1jop49h
@r_linux
Belgium Introduces “Freedom Fee” on US Commercial Software, Open Source Spared
https://redd.it/1josx52
@r_linux
BREAKING: Linus merged /dev/llm0 into kernel 6.16

In a surprise move, Linus Torvalds has merged /dev/llm0 into Linux 6.16. This new character device responds to plain English prompts with context-aware code suggestions, shell pipelines, and sarcastic comments about your coding habits.

The merge commit message reads:

“As long as it doesn’t break userspace, I don’t care if it hallucinates.”

Early benchmarks show /dev/llm0 consumes 3GB RAM just to say “it depends.”

https://redd.it/1jowcms
@r_linux
A solution I found for fixing monitor speaker (HDMI sound problem) (Debian 12, Alsa)

In short, input aplay -l in your terminal, it should list all the sound card & device, usually the first one is the right one. (In my case it is card 0, device 3)

DON'T create .asoundrc file in your home folder. Create one with "defaults.pcm.card 0" and
"defaults.pcm.device 3" do give your monitor speaker sound, but it will have cracking sound all the time.

INSTEAD, edit the /user/share/alsa/alsa.conf file with sudo, find the "defaults.pcm.card #" and
"defaults.pcm.device #" and replace the # with your correspond number listed by aplay earlier.

I guess system generate the sound signal with default sound driver setting first, then check if .asoundrc setting exist, if so, edit the sound signal with personal setting. < By doing so, it cause the sound signal inconsistent, thus the monitor speaker sound cracking. So user have to to edit the system sound driver file.

Hope this post help some unfortunate souls who suffer the tyranny of HDMI.

https://redd.it/1jp2m68
@r_linux
linux is so GOOD!!!!!!

I just switched to linux mint xfce(from win11) even though my hardware is good (since i m using a laptop and dont want a heavy os)
and I am blown away!!!!!!!!
I used to have AUDIO driver issues all the time ;-;
and i didn't even had to click a button and wallah the audio works fine
the temps are so stable!!!!!!!!!
m ready to spend time learning this rather than getting frustrated over a non working os
ALSO I have so much space left !!!!!!!!
FUCK MICROSOFT

https://redd.it/1jp3uiw
@r_linux
Why have I never seen anyone recommending Ubuntu as a distro? By "never," I mean never.

I’ve been exploring Linux distros for a while, and I’ve noticed that when people recommend distros, Ubuntu almost never comes up, despite being one of the most popular and user-friendly distros out there. I’m curious why that is. Is it that Ubuntu is too mainstream for hardcore Linux users, or do people simply prefer other distros for specific reasons?

https://redd.it/1jp3s7g
@r_linux