You are not logged in.
I did suggest that a bug report was called for in respect of that statement over at the forums. It's nonsense.
EDIT: and yes, Manjaro fuckwits regularly try to get Archers to fix their problems. It's very sad.
Does this work this way on hardware from 2008+?
Or before 2014?
I think so. Have you checked sysfs? Which governors are available.
And please stop full-quoting unnecessarily. It's really annoying and it makes the thread very hard to follow.
Manjaro users aren't bastards
The ones who try to get help on the Arch forums are.
Archlinux's current principles go against their keep it simple stupid lightweight principles
Arch is not, and has never been, lightweight. It uses glibc FFS...
Just allow an exception. I promise it's worth it.
Did the .deb remove the Realtek error messages?
Wonderfully cohesive desktop experience. Just a shame it's so ugly.
A blast from the past:
I was a regular reader back in the day. Loved it.
And now they have a website :-)
I used to get those Realtek messages from my RTL8852AE but they've gone now I'm using the firmware from 2022-12-14, the .deb for which is available from ceres. Just download and install the .deb though, don't add the repositories.
https://deb.debian.org/debian/pool/non- … -3_all.deb
My backlight has always behaved itself so I don't think the wireless card has anything to do with that.
Jeff Beck. RIP.
Slightly simpler version:
pkill -u "$USER" pipewire-pulse >/dev/null 2>&1
pkill -u "$USER" wireplumber >/dev/null 2>&1
pkill -u "$USER" pipewire >/dev/null 2>&1
pipewire &
until pgrep -f pipewire >/dev/null 2>&1 ; do
sleep 1
done
wireplumber &
pipewire-pulse &
No need for full paths or exec (the ampersands already fork the commands) and the until clause is simpler and quicker than a formal test.
I use "hack" and derivatives in their original meanings, always have.
Oh c'mon Steve, that's just begging the question
Language is fluid and meanings change over time. I'm really annoyed that Richard Dawkins' original meaning of the word "meme" has been subverted by ignorant youths sharing silly gifs but I've learned to live with it. Bloody kids.
I can't tell from those screens.
Correct alignment requires that the partitions start at sector 2048 (for a disk with 512 byte sectors, as yours seems to be) with subsequent partitions aligned to 1MiB boundaries.
Reference: https://wiki.archlinux.org/title/Advanc … _alignment
Those screens say the partitions start at "1.0 MB" but 1MB is not the same as 1MiB (2048 512 byte sectors or 1,048,576 bytes). I don't know if that screen is actually showing MB or if it is showing MiB but displaying the wrong units. You will have to check that yourself.
If you use fdisk or gdisk they will automatically align the partitions. They're the only partitioning tools I use so I don't know if there are others that work properly in that respect.
Sorry dcolburn, I was in a foul mood this morning. My tone was uncalled far and I apologise.
Any idea?
Report the bug.
The buster version needs libunique, which is abandoned upstream and unmaintained. Having it on your system might expose it to vulnerabilities, which is why it was removed for the bullseye release:
https://bugs.debian.org/cgi-bin/bugrepo … =%23885813
You should probably check what else has been pulled from buster:
aptitude search '?narrow(?installed, ?archive(oldstable))'
The Devuan developers do not recommend adding Debian repositories.
A new version of xfce4-notes which does not rely on an unmaintained package has been uploaded to Debian's experimental repositories:
https://tracker.debian.org/news/1226238 … erimental/
I do not recommend attempting to install it from experimental though. You could try backporting it instead. That might work.
is this essentially a configuration of snd-hda-intel to be applied at boot in initramfs?
Yes, that's right. It's probably not necessary to apply the configuration as early as the initramfs but it won't do any harm.
Or just purge that GVFS shite.
The transition freeze for bookworm starts the day after tomorrow so the chances of v1.4 making it into Debian 12 are zero.
The strange parted output is because you're trying to run it from the installer's shell, which uses busybox's gimped version. Why didn't you just load a live ISO image with a graphical desktop? Then you could have started a browser and just pasted the terminal output here directly. Work smarter, not harder.
Anyway the (busybox) fdisk output shows that all of the partitions on /dev/sdb are misaligned. This will result is poor disk I/O performance. I did ask how that partition table was created but you ignored me. Nice.
Whatever you used to create that partition table is a buggy pile of shite. Do not use it again. I would recommend either gdisk for GUID partition tables (as is present on /dev/sdb at the moment) or fdisk for MS-DOS ("MBR" type) partition tables, but don't use the busybox versions. Load up a live ISO image and use the full versions instead.
And what exactly are you using /dev/sdb for? It has an EFI system partition and you should only have one of those per machine. That being the case I would expect the ESP to be present on the "main" system disk, which would usually be /dev/sda.
It is almost impossible to offer any reasonable advice without knowing the exact requirements so help me to help you by supplying more information. This thread is a useless shit-show for anybody else now so we might as well use it as your general help desk to stop you making more useless threads elsewhere.
I think the installer has aligned the disk correctly. Please run my suggested commands to confirm this. I don't post shit like that just for fun...
The limitation is caused by the partition table rather than the filesystem.
If you're re-partitioning why not move into the 21st century and use a GUID partition table (GPT) instead? That has an 18TiB limit for individual partitions.
What is that output from? How did you create this new partition table?
Correct alignment in a disk with a 512 byte sector size does require the partitions to start at sector 2048, which is exactly 1MiB (1,048,576 bytes). It most certainly is not "1.0 MB" though.
Check
# fdisk -l /dev/sdb
That should show the first partition starting at sector 2048.
And also
# parted /dev/sdb align-check opt 1
That should say 1 aligned.
No idea about RAID though, I've never used that.
that's why I said Firefox and not Firefox-ESR from the repos.
Ah. Sorry Miyo.