You are not logged in.
Yr welcome, let me tell you about my day(s) - spent all of yesterday upgrading from debian 6.0 CD1 lxde/openbox to Bookworm/LMDE 6 with sysvinit still installed from debian 6.0, didn't backup along the way as it was more about seeing what happens if kmod isn't allowed to upgrade and kick the 2.6 kernel, anyway, after the final upgrade, unbootable on all fronts, all kernels, all inits, and bash init was borked by a short libtinfo.
The day before, had upgraded LMDE1 to LMDE6 with sysv. Took a backup at Debbie and a final one after Faye.
This morning, couldn't boot system 2, so decided to restore system1. Faye backup was borked and unfixable, luckily Debbie backup worked and was fixable (needed swap repair).
I blame usrmerge, or kmod, or 18 yo eee pc ssd, or my 90% of backups untested, and another 9% untested.
Unbootable system here after usrmerge. It failed, so I booted into single mode to fix it, then booted and finished up the upgrade, then couldn't boot anything, kernel panic on sysv or systemd, can boot into ash shell but commands don't work
kernel panic complaining about libtinfo being too short?
rbit is correct, EFI partitions are typically mostly empty and are at the start of the disk where there can be lots of non-zeroed old junk that can make your compressed images much larger.
The joy of using dd in a fat partition where you never need sudo
Just booted LMDE 6 on a 3.2 kernel with command mem=72M single init=/usr/bin/ash and ran modprobe -r a lot then ran htop
3.97MiB used. Htop appears to be using around 1.5, so actual shell running neofetch may be just under 2.5MB???
Current lowest ever bookworm / LMDE 6 mate desktop memory usage is 32.5M
Hi, hope you find a solution! Some advice for anyone finding this thread:
Open your EFI partition in terminal then run
dd if=/dev/zero of=zero.img
then run
rm zero.img
then take a backup of the partition using dd or any disk utility then zip up your partition backup and save it for efi partition deletion emergencies. For accidental deletion of contents, just mount the backup image and copy the files over from it.
If you need to recreate a lost EFI partition, you can set the label to be the same as the lost one very easily.
OK thanks so far, if I install apulse and remove pulsaudio, then moc/mocp plays without pulse, and sounds fine
BUT when I reinstall pulse, moc/mocp just goes back to launching pulse? I only want pulse at desktop level init 5 or lower level init when I choose to launch it. Otherwise, I just want moc/mocp to default to apulse.
Sorry my bad, I mean mocp (music on console player) complains of no sound server >_<
* switches to ash weeb because it's lighter *
Can't figure out how to get sound without pulseaudio!
Is there a handy guide somewhere? Nothing complicated, just audio from headphone jack is needed, no input, no networking.
Alsa complains of no sound server, no Jack, OSS, or Pulse. Does one need OSS or Jack for audio without Pulse?
Asking for a friend with an eee pc.
Will this fix the problem with mint icons not coming through to the notification area in mate and xfce for LMDE 5 and 6
How many times now have I held mint artwork from cindy or debbie?
Also, when I'm using a mint theme, can I please have a mint icon for my menus that come with the panel and are not mintmenu/matemenu?
Been finding refracta isos work with ventoy and have used devuan with ventoy in the past???
You could temporarily send it to a tmpfs in ram, that way you can read your logs until you choose to power off, and if you run out of ram, you can visit them and delete as many GB of logram as you need.
This will keep unused ram locations warm and be more responsive than hdd logs.
Been having lots of fun with refracta devuan. Started with xfce, removed all and installed mint artwork from LMDE 4 debbie
Because later icons do not work properly with mate panel notification area.
So WHY does my notification area have wrong icons?
Turns out devuan have crossported mint-y-icons
Attempt 2: refracta NOX i386
Lovingly added xorg and desktop bits on eee pc taking a long time.
Resulting in the most effed of all effed desktops. Couldn't login, /home/eee was showing as /home/[tofu]4eee
Started x as root, renamed [tofu]4eee to eee
On ctrl+alt F2 user eee autologsin to cli but cannot startx and has no /home directory
But I had the right icons this time
Will not be seeking remedy, as the audio settings persistence bug in mate is still present.
Can you please also ask why 330+MB rather than around 188MB?
There's a 17 MB bios boot boost partition for eee pc xp too! I should put that online too.
One does wonder about the breadth of testing of new 32 bit kernels, so many million use cases, so fewer eee pc users ;_:
If some good folk would be happy to compile kernels for eee pc I'd be not only happy, my obsessively compelled to try them out on many eee, though I hesitate to say test.
Been enabling zram on a few eee, it seems to help, especially when torturing the fanless ones with cinnamon desktop and browser action. On the 4G / 630mhz single core the name of the game is no fan even in high summer, so ram ceiling isn't important, so the question is, does zram not increase overall cpu and/or ram usage?
If you have a 128gb ssd then I bet you don't have the bios boost partitions, but never fear, I have put them on drop box, you can copy one of them with gparted and easily recreate the other using gnome-disks, make the fat partition 513KB instead of 7.84MiB if you like!
https://www.dropbox.com/scl/fi/koa3hdwa … 6wtxc&dl=0
Link changed to point to actual file >.<
Yes they all (my asus eee pc fleet) still run fine on every kernel since 3.16, they just all have different esoteric messages on boot.
I mean, is there some way to just include all relevant new security updates to an old kernel without worrying about new features or hardware that the asus eee pc will never know or be able to run?
The poor little 2G surf, I just managed to get lmde 6 onto it with latest kernel and 300 MB free space of the 1.87MIB ssd. No room for newest kernel upgrade. They can run the new kernels, but can't install them!
Hey, tried out refracta, very nice system, eee pc nearly full with no desktop tho!
Just a question, why is the latest i386 kernel from there 330MB when the last 6.1... kernels were 188MB?
300+ is the size of the amd64 kernels, so are these i386 kernels being compiled with all amd64 bits included but unused or something or have they actually needed to double in size?
Where to find modern secure small i386 kernels???
Hey that's wonderful thanks, it's for my eee pcs so no need for the firmware or pae, they take max 2GB ram!
Downloading that kernel now and will try it on eee pc later
Where will we get out 32 bit kernels from?
Got it working, reverted to pre-migration state and tried a different approach: Installed orphan-sysv-scripts and the four sysvinit-core dependencies under the debian repos, then checked and inittab was present, so went ahead with the migration instructions as before.
This worked fine, albeit with extra apt-get upgrades and apt-get -f installs, but the inittab.d warning was still there, so mkdir /etc/inittab.d fixed the warning, which didn't affect the system.
I am learning
Also forgot to reinstall lightdm, so booted to no desktop, but startx worked.
I'd like the system to always behave that way? Booting to cli, with startx option, but removing lightdm breaks switching between consoles.
Thankyou, I did copy over an existing inittab from a saved eee pc daedalus iso, this cured the 'no inittab' error, but then there is a 'no inittab.d' error.
Can't see inittab.d on any sysv system, so am stumped.
Is nobody worried that simply following the latest devuan migration instructions leads to a rather poorly system?
Debian 12.9 netinstall base.
Is the fix to simply copy over a known good inittab and mkdir /etc/inittab.d/ ?
Hilarious AI overview for devuan question. Ever felt quite so trolled??
AI Overview
After a Devuan migration, the absence of /etc/inittab and /etc/inittab.d is normal, as Devuan, a fork of Debian, uses systemd for system initialization instead of the older sysvinit which uses those files.
Here's a more detailed explanation:
Devuan and Systemd:
Devuan, a fork of Debian, intentionally removes sysvinit and its associated files (like /etc/inittab) in favor of systemd. systemd is a system and service manager that provides a different approach to managing system processes and boot sequences.
What /etc/inittab and /etc/inittab.d were for:
In systems that used sysvinit, /etc/inittab contained configuration for runlevels and the initial processes to be started, while /etc/inittab.d was used for adding custom configurations.
Why you won't find them:
Since Devuan uses systemd, the files and concepts associated with sysvinit are not present.
What to use instead:
If you need to manage services or boot processes, you should consult the systemd documentation and use systemd's tools and configuration files, such as unit files in /etc/systemd/system/.
No need to worry:
The absence of /etc/inittab and /etc/inittab.d is expected in a Devuan system and should not cause any problems.
No inittab.d directory found during boot log - Devuan Forum
23 Mar 2022 — Re: [SOLVED] init: No inittab. d directory found during boot log. The *. d directories are a place for the administrato...
Devuan Forum
Directory /etc/inittab.d - LinuxQuestions.org
22 Jan 2023 — master could probably have gone to separate files in /etc/auto. master. d but I was lazy and reused an older package. S...
LinuxQuestions.org
"No inittab file found" after reset - debian - Server Fault
6 Jan 2015 — Is /etc/inittab the only file missing or does it look like other parts of / are affected? If only inittab is missing, tr...
Server Fault
Show all
Generative AI is experimental.
So the question is, who here has a Ryxen 7 5800x3D and can you run linux solely within the 98MB on chip cache?