You are not logged in.
I used to have a /boot partition, but with UEFI it was difficult to manage the size (it only filled up once but that was enough),
so I stopped worrying about /boot file space. (The bios partition only requires 100Mb)
your / is 28Gb... I reserve 28Gb just for /var. here's the rest...
df -h
glenn@GamesBox ~ $ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 1.4M 1.6G 1% /run
/dev/sda2 22G 1.3G 19G 7% /
/dev/sda6 17G 9.6G 5.8G 63% /usr
tmpfs 5.0M 16K 5.0M 1% /run/lock
tmpfs 3.7G 0 3.7G 0% /dev/shm
/dev/sda7 865G 121G 700G 15% /home
/dev/sdc6 58G 18G 38G 32% /home/glenn/local/archive
/dev/sdc2 295G 208G 73G 75% /home/glenn/local/data
/dev/sdc5 472G 119G 329G 27% /home/glenn/local/free
/dev/sdc7 711G 50G 625G 8% /home/glenn/local/media/circus
/dev/sdc9 480G 255G 201G 56% /home/glenn/local/media/movies
/dev/sdc8 961G 103G 809G 12% /home/glenn/local/media/music
/dev/sdc1 207G 12G 185G 6% /home/glenn/local/other
/dev/sdc3 480G 58G 398G 13% /home/glenn/local/spare
/dev/sda5 2.9G 17M 2.7G 1% /tmp
/dev/sda3 8.1G 1.6G 6.1G 21% /var
/dev/loop0 3.7G 3.7G 0 100% /home/glenn/local/archive/debs/iso/devuan_daedalus_5.0.1_i386_desktop
/dev/loop1 3.8G 3.8G 0 100% /home/glenn/local/archive/debs/iso/devuan_daedalus_5.0.1_amd64_desktop
cgroup_root 10M 0 10M 0% /sys/fs/cgroup
tmpfs 1.6G 12K 1.6G 1% /run/user/1000
glenn@GamesBox ~ $
Some places you can check for swelling...
/tmp/
/var/log/
/var/cache/apt/archives/
just my two cents worth. :-)
Hi! Welcome!
The system is quite old (not that old it NOT should work) and may not supply enough power for a longer cable.
Have you checked your power supply specs?
just a thought...
is the eth chip auto x-over (cable) detect?
I wonder, how you will reinstall any of those packages without wifi.
I can only see a few packages in that list that may be required, but you must have removed a package that you rely on.
A re-install of the OS may be easier, then just remove the accessible apps you don't want. One at a time... keep a list...
the system keeps a log here...
/var/log/dpkg.log
/var/log/apt/history.log
use cat or tail to see in a terminal/console
checkout this link...
Hi, I add a ipv6.disable=1 line to grub... the vpn I have only uses ipv4
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# GlennsPref 20230920 ipv6
GRUB_DEFAULT=0
GRUB_TIMEOUT=4
GRUB_DISTRIBUTOR=`lsb_release -i -s`
GRUB_CMDLINE_LINUX_DEFAULT="console=tty12 vga=794 modeset.nouveau=0 nokmsboot ipv6.disable=1"
# discover other os's
GRUB_DISABLE_OS_PROBER=false
GRUB_GFXMODE=1920x1080
GRUB_INIT_TUNE="400 440 1"
# resume=uuid errors... noresume "we don't susspend"
GRUB_CMDLINE_LINUX="noresume idle=nomwait"
GRUB_THEME=/usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txt
run update-grub as root, and reboot.
all the best
It's not building for some reason.
apt install libglvnd-dev libglvnd0 pkg-config build-essential gcc12 linux-headers linux-headers-common linux-compiler-gcc-12
check for error messages...
Hi, if you get a white screen for login, sddm...
you may find a selection box near the bottom left corner, really hard to see...
you may select plasma-x11, instead of wayland (never worked for me)
see how you go.
Hi, to properly install the proprietary nVidia .run package...?
If you need to block nouveau module...
make a file, /etc/modprobe.d/nvidia-installer-disable-nouveau.conf
# generated by nvidia-installer
blacklist nouveau
options nouveau modeset=0
Make sure you have a build environment, build essentials, linux-headers and libglvnd-dev
Then reboot to safe mode., down arrow at the grub boot loader to
"Advanced options for Dev..."
arrow to (don't use enter) select your kernel and (recovery mode) and press E to edit
move the cursor to the end of the last "linux" line and type
modeset.nouveau=0 vga=794 nokmsboot
and press F10 to boot to "single" mode.
type in the root password when prompted.
install package.
reboot with
shutdown -r now
I hope this helps.
I don't think it's criminal, it simply won't work the same in every country.
The worst that could happen is "no connection", imho.
On my system the wifi regulatory database file name may be found...
dmesg | grep firm (root needed)
root@GamesBox:/root dmesg | grep firm
[ 0.472983] Spectre V2 : Enabling Speculation Barrier for firmware calls
[ 9.270684] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[ 9.293653] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[ 9.368664] iwlwifi 0000:05:00.0: firmware: direct-loading firmware iwlwifi-9260-th-b0-jf-b0-46.ucode
[ 9.489964] iwlwifi 0000:05:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 9.499585] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[ 9.509055] iwlwifi 0000:05:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 9.518225] iwlwifi 0000:05:00.0: loaded firmware version 46.ea3728ee.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
[ 9.736185] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 9.742789] bluetooth hci0: firmware: direct-loading firmware intel/ibt-18-16-1.sfi
[ 9.749235] Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
[ 15.095529] Bluetooth: hci0: Waiting for firmware download to complete
[ 15.127996] bluetooth hci0: firmware: direct-loading firmware intel/ibt-18-16-1.ddc
>> 9.518225] iwlwifi 0000:05:00.0: loaded firmware version 46.ea3728ee.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
This file comes from the firmware package for my intel-wire-less wifi (iwlwifi).
This file may be stored on a memory stick and inserted for install, the installation program will usually find it and load it while telling you so.
If you use the wrong one, it just won't work properly.
see how you go.
ps. the installation will continue with out wifi (for updates). My system asks for it but it's built-in now.
I had a similar problem/symptoms... desktop & nVidia graphics, after updating Daedalus (X11 packages) last week.
one screen went blank during boot and then did not revive.
I tried lots of things but was at a loss.
I'm using Plasma (KDE5) and I found one screen was disabled in the system settings, display&monitor.
First time this has happened. After a while, and quite a few reboots I realised the 2 screens were like stacked, but one was disabled.
So check that.
On box No.2, The blank screen could be that the system is trying to use non-X like "Wayland". (never got it to run on my setup)
And in my experience a blank white screen is normal for a fresh install sddm login page.
But If I move the mouse around the bottom left corner there is a choice (drop-down menu), though nearly invisible to change it to Plasma-X11 (a blank white screen).
Just last night (after reinstalling Chimaera like you did, just to check the hardware) did the full install & upgrade for Daedalus &
this morning it booted fine.
I hope this helps you.
I have al my data on separate partitions, even on another ssd.
All are mounted through fstab in /home/$USER/local/ ...
I find it easier for me to put them there rather than in the system, /media or /mnt.
Also the permissions are different to yours because they are all (except other OS's) mounted at boot.
I use a few symlinks for my home folder from those data partitions like, documents, bin, build, music, pictures...videos...
A collection of backups there too that I need to be careful not to change the perms on those.
Anyway, I'm a bit chatty today... :-) I hope this helps someone.
I agree with Fred, you need to go into your bios setup and switch off secure boot, enabling/allowing legacy boot.
You may change it back later.
Note that the updated Devuan daedalus installer ISO set 5.0.1 now also handles the use case of booting from CDROM on UEFI.
The issue indeed was that the boot loader got confused about the iso9660 block size (2k) differing from the expected block size (512) for the EFI filesystem. To fix that we forked syslinux, added a corrective patch and published to Devuan experimental. The patched software was next used for building the updated ISO set.
Very cool! Thank you for the heads-up, Ralph.
Welcome! :-)
This is a cross post, the removal of elogind made this system unusable.
But, I have tested the new Devuan 5.0 desktop-install iso and it worked perfectly.
:-)
I tried to install my way back to a reasonable media system...
I re-installed elogind and rebooted & everything is back...
I can use synaptic package manager (required a password dialog, at least)
I have sounds
I have all the restart and shutdown buttons (so I don't have to logout and ctrl+alt+del to restart)
I will try again next time I have a clean install.
Hi, I ran with it and had to turn off elogind from starting, ...
How do I check?
No sound atm, but I was relieved to see the remove list shortened (kde stuff).
I can login, and access the desktop tools.
I have lost the shut-down and reboot buttons from the plasma start menu.
See how I go.
...imho, it's just M$ hobbling the competition.
I just tried
apt install -s elogind- libpam-ck-connector sway seatd
Basically, over 80 lines of mostly kde packages to auto-remove,
0 upgraded, 29 newly installed, 236 to remove and 0 not upgraded.
I don't think "I'm" ready for this yet.
For what it's worth, Pre-empt is not RealTime, but close.
I hope it keeps working for you.
See how you go when playing back 14 tracks while recording overdubs in real time.
Minimal xruns.
Hi, I think jack wants realtime access from the kernel.
uname -a will show your current kernel version, yours should have rt in it's name.
(edit) terrible typos
To setup /etc/fstab from /dev/sd(x)(n) to UUID
Use lsblk blkid and fstab, for clues
you might need root access for one of those.
This will give you the uuids and show you which /dev/... to follow.
Too many errors since I was introduced to Discover. I usually remove it as soon as it starts making noise.
ymmv.