You are not logged in.
- Topics: Active | Unanswered
#101 Re: Installation » Installing ISC-DHCP-SERVER on Daedalus » 2023-08-25 11:44:01
Although Network-Manager is great for desktops and laptop PCs.
And only for these and not for servers.
#102 Installation » Installing ISC-DHCP-SERVER on Daedalus » 2023-08-24 18:44:00
- Andre4freedom
- Replies: 2
It's important enough to report:
Should you install Devuan Daedalus and want to configure it as an DHCP server,
don't forget to remove the Network-Manager (apt remove network-manager) from your system and configure the network in the classical way in
/etc/network/interfaces.
This will save you from head-aches caused by quizzical entries in /var/log/syslog and the DHCP server not starting at system start.
In such a case you can still start the server manually after system-boot. But system-boot will fail the starting DHCP server. (I use OpenRC)
You may have to edit /etc/default/ISC_DHCP-SERVER too depending on your IPv4 and IPv6 configuration.
Network-Manager is not recommended on servers anyway - think of BIND9, NFS, DHCP etc.
Network-Manager comes along with DEs - but I still want to have an XFCE4 Desktop on a server.
I'm not sure if that has to do with Daedalus, but I hadn't that problem with Beowulf.
Otherwise I can tell only the best from Daedalus! Be happy, as I am.
#103 Re: Installation » Daedalus upgrade with OpenRC » 2023-08-23 11:49:23
Hello,
That's really good and helpful information, thank you.
Could you possibly post your future experiences with open-rc init?
I'm interested. I always use open-rc and I like it, but I always stuck to the default init program (InitSysV).
Have a great day.
#104 Re: Installation » Looking for server cd desktop environment installation guide » 2023-08-23 08:16:53
Welcome to the forum and the very friendly Devuan-community!
You complicate matters by using the server-CD and CD2,3,4, increasingly so if done in a VM, due to the CD swapping.
It can be done in a single go using the desktop-image iso, which you can directly import to your VM host and deploy your Cinnamon-Devuan installation.
The server CD, though installs only basic things to make up a server. However, you can install tasksel which gives you the comfort of an automated process to install desktop-environments.
BTW: you can install a pure server using the same dvd-iso.
The install instructions are here:
https://www.devuan.org/os/documentation … all-devuan
Good luck and have fun. Daedalus is really fun, believe me.
#105 Re: Devuan » Is Devuan Daedalus Changing to "Stable"? » 2023-08-15 11:07:14
Congratulations to all of the Devuan team and the community helping refine that release. Daedalus is simply fantastic.
BRAVO - Thank you all!!
#106 Re: Other Issues » Virus scanning on Devuan » 2023-08-09 11:40:22
It's quite easy:
install clamav-daemon (with all dependencies)
The services will be installed and started.
To make sure your on-access-scan is started by default:
$ sudo rc-update add clamav-daemonI've just verified it on my standard Devuan 4 (Chimaera) system. It run's with open-rc.
If you have a system installed with init-sysV, the same script should work:
$ ls -l /etc/init.d/clam*
-rwxr-xr-x 1 root root 9563 Feb 17 21:43 /etc/init.d/clamav-daemon
-rwxr-xr-x 1 root root 7692 Feb 17 21:43 /etc/init.d/clamav-freshclam#107 Re: Desktop and Multimedia » [SOLVED] Fixing broken Brother DCP-L3510CDW Printer Installation (howto) » 2023-08-04 18:32:31
Update - Devuan Daedalus
I have tested 3 different Brother MFC / DCP multifunction printers.
With the latest Daedalus RC7 install, all printers work well, immediately, without any config to do. This holds true for printing and scanning (flatbed and sheet-feeder).
With the Chimaera release the experience was and still is identical with the exception of the scanner not working correctly with the ADF (document feeder). For this version of Devuan I had to download the Brother br-sane-config-tool to setup the scanner (with ADF) correctly. If not, I could scan only with the flatbed scanner.
It looks as that detail was corrected with the sane release in Devuan Daedalus.
1. Install printer in to the IP network - 2. go to your Devuan box - 3. and start printing!
I'm so happy.
BTW: Daedalus RC7 looks very polished, slick and nice - and ready. I'd like to call it "the best".
@alexkemp: give it a try
#108 Re: Other Issues » Virus scanning on Devuan » 2023-08-04 07:31:50
Agree: none
Should you share files with Windows machines, you can check and protect these files with clamav. Just keep it updated. Read The Fascinating Man-pages.
#109 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-21 17:43:30
And one other note to add:
I've just tested the rc5 netinstall. The USB stick boots correctly, installation is flawless, the system works very well, on both, BIOS-architectures and EFI-architectures.
Good work, thanks to you.
#110 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-11 14:31:12
Just to conclude that matter,
the desktop-iso (rc4) works like a charm too.
I found no issues with all 3 isos tested. (rc4!)
I suggest to mark the topic resolved...
Thanks to you all
#111 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-08 09:35:02
Hello all,
I'm happy to report the new rc4 isos boot correctly from the USB sticks. I have tested the netinstall and server iso.
The desktop iso comes next.
I will report if issues come up again.
So for now life is beautiful and the world is a wonderful place. THANK YOU, Ralph and all concerned.
Have a good day, André
#112 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-08 09:07:00
I see, the rc4 isos are already there, I will test immediately and report back.
#113 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-08 06:00:41
Result:
The netinstall iso (rc3) successfully boots into the installer when burned to a CDROM and booted from.
The same iso booted from a USB stick fails.
The test was performed on the very same machine..
And yes, on the CD it's syslinux booting.
I hope the information helps...
#114 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-08 05:36:24
@ralph.ronnquist,
Sorry for the delay, had a night's rest....
Here the required lspci -v on my Alma Linux installation:
[linuxadmin@coyote ~]$ lspci -v
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
Subsystem: Intel Corporation Device 2035
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: ivb_uncore
Kernel modules: ie31200_edac
00:02.0 VGA compatible controller: Intel Corporation IvyBridge GT2 [HD Graphics 4000] (rev 09) (prog-if 00 [VGA controller])
DeviceName: CPU
Subsystem: Intel Corporation Device 2035
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI])
Subsystem: Intel Corporation Device 2035
Flags: bus master, medium devsel, latency 0, IRQ 24
Memory at f7e20000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
Subsystem: Intel Corporation Device 2035
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at f7e3c000 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>
Kernel driver in use: mei_me
Kernel modules: mei_me
00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04) (prog-if 02 [16550])
Subsystem: Intel Corporation Device 2035
Flags: 66MHz, fast devsel, IRQ 19
I/O ports at f0e0 [size=8]
Memory at f7e3a000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
Kernel driver in use: serial
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
DeviceName: L1U1
Subsystem: Intel Corporation Device 2035
Flags: bus master, fast devsel, latency 0, IRQ 25
Memory at f7e00000 (32-bit, non-prefetchable) [size=128K]
Memory at f7e39000 (32-bit, non-prefetchable) [size=4K]
I/O ports at f080 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI])
Subsystem: Intel Corporation Device 2035
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at f7e38000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
DeviceName: AU1
Subsystem: Intel Corporation Device 2035
Flags: bus master, fast devsel, latency 0, IRQ 32
Memory at f7e30000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 16
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: [disabled]
Memory behind bridge: [disabled]
Prefetchable memory behind bridge: [disabled]
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1c.6 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 (rev c4) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 18
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000e000-0000efff [size=4K]
Memory behind bridge: f7d00000-f7dfffff [size=1M]
Prefetchable memory behind bridge: [disabled]
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI])
Subsystem: Intel Corporation Device 2035
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at f7e37000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
I/O behind bridge: [disabled]
Memory behind bridge: f7c00000-f7cfffff [size=1M]
Prefetchable memory behind bridge: [disabled]
Capabilities: <access denied>
00:1f.0 ISA bridge: Intel Corporation Q77 Express Chipset LPC Controller (rev 04)
Subsystem: Intel Corporation Device 2035
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0])
Subsystem: Intel Corporation Device 2035
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 26
I/O ports at f0d0 [size=8]
I/O ports at f0c0 [size=4]
I/O ports at f0b0 [size=8]
I/O ports at f0a0 [size=4]
I/O ports at f060 [size=32]
Memory at f7e36000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
Subsystem: Intel Corporation Device 2035
Flags: medium devsel, IRQ 18
Memory at f7e35000 (64-bit, non-prefetchable) [size=256]
I/O ports at f040 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
DeviceName: L2U1
Subsystem: Intel Corporation Device 2035
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at f7d00000 (32-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=32]
Memory at f7d20000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e
03:03.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 70) (prog-if 10 [OHCI])
Subsystem: Intel Corporation Device 2035
Flags: medium devsel, IRQ 10
Memory at f7c00000 (32-bit, non-prefetchable) [disabled] [size=4K]
Capabilities: <access denied>
[linuxadmin@coyote ~]$ I will burn the rc3 iso to a CD and test booting it on that same machine.
I will report back. Thank you all!
#115 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-07 18:38:13
Unfortunately, the problem is still present in the rc3 files.
I have tested the netinstall-iso and the server-iso.
Does it help if I try to burn CDs with these rc3 files and test again?
#116 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-07 11:20:58
You are a hero Ralph, thank you!
I will test it when it appears and report back.
Have a good day.
#117 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-07 07:41:11
WOW, you are pointing to a good direction....
here the required information:
The system has
- UEFI Boot enabled
- Legacy Boot enabled
- Secure Boot disabled
Booting the Devuan5 rc2 USB stick in UEFI mode: fails
Booting the Devuan5 rc2 USB stick in Legacy mode: fails
In both ways: the output shows:
= = 0 Devuan boot preamble = = =
And then fails miserably (locked completely up, dead, after messages complaining about unable to mount cdrom...)
The same test with Debian 12 goes well and boots successfully into the installer.
here is the extract from /var/log/messages in Alma Linux when inserting that Devuan 5 rc2 USB stick>:
Jul 7 09:11:34 coyote systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jul 7 09:11:34 coyote systemd[1]: systemd-localed.service: Deactivated successfully.
Jul 7 09:11:42 coyote chronyd[1016]: Selected source 83.150.25.25 (2.almalinux.pool.ntp.org)
Jul 7 09:11:43 coyote journal[1628]: Service not used for 60 seconds. Shutting down..
Jul 7 09:11:43 coyote systemd[1]: geoclue.service: Deactivated successfully.
Jul 7 09:11:45 coyote systemd[1]: realmd.service: Deactivated successfully.
Jul 7 09:12:07 coyote PackageKit[1632]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Jul 7 09:12:07 coyote PackageKit[1632]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Jul 7 09:12:08 coyote systemd[1]: Starting Fingerprint Authentication Daemon...
Jul 7 09:12:08 coyote systemd[1]: Started Fingerprint Authentication Daemon.
Jul 7 09:12:28 coyote kernel: usb 1-1.6: new high-speed USB device number 5 using ehci-pci
Jul 7 09:12:28 coyote kernel: usb 1-1.6: New USB device found, idVendor=0781, idProduct=5581, bcdDevice= 1.00
Jul 7 09:12:28 coyote kernel: usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 7 09:12:28 coyote kernel: usb 1-1.6: Product: Ultra
Jul 7 09:12:28 coyote kernel: usb 1-1.6: Manufacturer: SanDisk
Jul 7 09:12:28 coyote kernel: usb 1-1.6: SerialNumber: 4C530001270914118551
Jul 7 09:12:28 coyote kernel: usb-storage 1-1.6:1.0: USB Mass Storage device detected
Jul 7 09:12:28 coyote kernel: scsi host7: usb-storage 1-1.6:1.0
Jul 7 09:12:28 coyote mtp-probe[2898]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6"
Jul 7 09:12:28 coyote mtp-probe[2898]: bus: 1, device: 5 was not an MTP device
Jul 7 09:12:28 coyote mtp-probe[2899]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6"
Jul 7 09:12:28 coyote mtp-probe[2899]: bus: 1, device: 5 was not an MTP device
Jul 7 09:12:29 coyote kernel: scsi 7:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6
Jul 7 09:12:29 coyote kernel: sd 7:0:0:0: Attached scsi generic sg6 type 0
Jul 7 09:12:29 coyote kernel: sd 7:0:0:0: [sdf] 30464000 512-byte logical blocks: (15.6 GB/14.5 GiB)
Jul 7 09:12:29 coyote kernel: sd 7:0:0:0: [sdf] Write Protect is off
Jul 7 09:12:29 coyote kernel: sd 7:0:0:0: [sdf] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul 7 09:12:29 coyote kernel: sdf: sdf1 sdf2
Jul 7 09:12:29 coyote kernel: sd 7:0:0:0: [sdf] Attached SCSI removable disk
Jul 7 09:12:30 coyote journal[952]: Mounted /dev/sdf1 at /run/media/linuxadmin/DEVUAN5 on behalf of uid 1000
Jul 7 09:12:36 coyote systemd[1]: virtqemud.service: Deactivated successfully.
Jul 7 09:12:39 coyote systemd[1]: fprintd.service: Deactivated successfully.
Jul 7 09:13:05 coyote systemd[1985]: Starting Mark boot as successful...
Jul 7 09:13:05 coyote systemd[1985]: Finished Mark boot as successful.
Jul 7 09:13:51 coyote chronyd[1016]: Selected source 195.186.1.100 (2.almalinux.pool.ntp.org)
Jul 7 09:14:30 coyote systemd-logind[950]: New session 4 of user linuxadmin.
Jul 7 09:14:30 coyote systemd[1]: Started Session 4 of User linuxadmin.
Jul 7 09:14:30 coyote systemd[1]: Starting Hostname Service...
Jul 7 09:14:30 coyote systemd[1]: Started Hostname Service.
Jul 7 09:15:00 coyote systemd[1]: systemd-hostnamed.service: Deactivated successfully.
(END)And here the output of lsmod after plugging the stick in:
[linuxadmin@coyote ~]$ lsmod > modules.text
[linuxadmin@coyote ~]$ cat modules.text
Module Size Used by
nls_utf8 16384 1
isofs 49152 1
uinput 20480 0
snd_seq_dummy 16384 0
snd_hrtimer 16384 1
nft_fib_inet 16384 1
nft_fib_ipv4 16384 1 nft_fib_inet
nft_fib_ipv6 16384 1 nft_fib_inet
nft_fib 16384 3 nft_fib_ipv6,nft_fib_ipv4,nft_fib_inet
nft_reject_inet 16384 6
nf_reject_ipv4 16384 1 nft_reject_inet
nf_reject_ipv6 20480 1 nft_reject_inet
nft_reject 16384 1 nft_reject_inet
nft_ct 24576 21
nft_chain_nat 16384 3
nf_nat 57344 1 nft_chain_nat
nf_conntrack 176128 2 nf_nat,nft_ct
nf_defrag_ipv6 24576 1 nf_conntrack
nf_defrag_ipv4 16384 1 nf_conntrack
bridge 315392 0
stp 16384 1 bridge
llc 16384 2 bridge,stp
ip_set 61440 0
rfkill 36864 3
nf_tables 270336 276 nft_ct,nft_reject_inet,nft_fib_ipv6,nft_fib_ipv4,nft_chain_nat,nft_reject,nft_fib,nft_fib_inet
nfnetlink 20480 3 nf_tables,ip_set
qrtr 49152 4
sunrpc 667648 1
vfat 20480 1
fat 86016 1 vfat
intel_rapl_msr 20480 0
intel_rapl_common 28672 1 intel_rapl_msr
x86_pkg_temp_thermal 20480 0
intel_powerclamp 20480 0
snd_hda_codec_hdmi 81920 1
coretemp 20480 0
snd_hda_codec_realtek 167936 1
snd_hda_codec_generic 98304 1 snd_hda_codec_realtek
ledtrig_audio 16384 1 snd_hda_codec_generic
snd_hda_intel 57344 2
kvm_intel 385024 0
snd_intel_dspcfg 32768 1 snd_hda_intel
snd_intel_sdw_acpi 20480 1 snd_intel_dspcfg
kvm 1105920 1 kvm_intel
snd_hda_codec 176128 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core 110592 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_hwdep 16384 1 snd_hda_codec
snd_seq 94208 7 snd_seq_dummy
snd_seq_device 16384 1 snd_seq
irqbypass 16384 1 kvm
iTCO_wdt 16384 0
rapl 24576 0
iTCO_vendor_support 16384 1 iTCO_wdt
snd_pcm 151552 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
mei_wdt 16384 0
snd_timer 49152 3 snd_seq,snd_hrtimer,snd_pcm
snd 118784 16 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
mei_me 49152 1
intel_cstate 24576 0
mei 155648 3 mei_wdt,mei_me
i2c_i801 32768 0
soundcore 16384 1 snd
intel_uncore 225280 0
lpc_ich 28672 0
pcspkr 16384 0
i2c_smbus 20480 1 i2c_i801
xfs 2002944 3
libcrc32c 16384 4 nf_conntrack,nf_nat,nf_tables,xfs
sr_mod 28672 0
cdrom 81920 2 isofs,sr_mod
sd_mod 65536 6
t10_pi 16384 1 sd_mod
sg 40960 0
i915 3321856 4
i2c_algo_bit 16384 1 i915
intel_gtt 24576 1 i915
drm_buddy 20480 1 i915
drm_dp_helper 159744 1 i915
drm_kms_helper 200704 2 drm_dp_helper,i915
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
cec 53248 2 drm_dp_helper,i915
ttm 86016 1 i915
ahci 49152 3
libahci 49152 1 ahci
crct10dif_pclmul 16384 1
crc32_pclmul 16384 0
drm 622592 7 drm_dp_helper,drm_kms_helper,drm_buddy,i915,ttm
libata 389120 2 libahci,ahci
crc32c_intel 24576 1
e1000e 323584 0
ghash_clmulni_intel 16384 0
video 57344 1 i915
uas 32768 0
usb_storage 81920 2 uas
dm_mirror 28672 0
dm_region_hash 24576 1 dm_mirror
dm_log 20480 2 dm_region_hash,dm_mirror
dm_mod 184320 12 dm_log,dm_mirror
fuse 176128 3
[linuxadmin@coyote ~]$It shows that the module "usb_storage 81920 2 uas" is present.
I hope that helps.... I'm ready to give more information if required. Thank you so much!
André
#118 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-06 14:10:47
@Ralph: No problem,
I did a normal boot into the installed system to get the information:
Alma Linux 9.1
[linuxadmin@coyote ~]$ cat /etc/redhat-release
AlmaLinux release 9.1 (Lime Lynx)
[linuxadmin@coyote ~]$
[linuxadmin@coyote ~]$ sudo fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD1000DHTZ-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 241CA6FA-A72E-437A-81A7-FDDE97E615BF
Device Start End Sectors Size Type
/dev/sda1 2048 1230847 1228800 600M EFI System
/dev/sda2 1230848 3327999 2097152 1G Linux filesystem
/dev/sda3 3328000 1953523711 1950195712 929.9G Linux LVM
Disk /dev/mapper/almalinux-root: 70 GiB, 75161927680 bytes, 146800640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/almalinux-swap: 7.78 GiB, 8355053568 bytes, 16318464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/almalinux-home: 852.14 GiB, 914979028992 bytes, 1787068416 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
[linuxadmin@coyote ~]$ Question: do you need the complete dmidecode output?
Here the essential information first:
[linuxadmin@coyote ~]$ sudo dmidecode -t bios
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Intel Corp.
Version: MKQ7710H.86A.8064.2013.1120.1214
Release Date: 11/20/2013
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 12 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 4.6
Handle 0x005E, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
[linuxadmin@coyote ~]$ sudo dmidecode -t system
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Netree AG
Product Name: netPC
Version:
Serial Number:
UUID: d5d9e0e1-8e94-e211-8fc5-2c27d725b21d
Wake-up Type: Power Switch
SKU Number: To be filled by O.E.M.
Family: To be filled by O.E.M.
Handle 0x0021, DMI type 12, 5 bytes
System Configuration Options
Option 1: To Be Filled By O.E.M.
Handle 0x0022, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected
[linuxadmin@coyote ~]$ sudo dmidecode -t baseboard
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Intel Corporation
Product Name: DQ77MK
Version: AAG39642-500
Serial Number: BTMK312008X0
Asset Tag: To be filled by O.E.M.
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To be filled by O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Handle 0x001F, DMI type 10, 12 bytes
On Board Device 1 Information
Type: Video
Status: Enabled
Description: Intel(R) HD Graphics Device
On Board Device 2 Information
Type: Ethernet
Status: Enabled
Description: Intel(R) 82579LM Gigabit Ethernet Device
On Board Device 3 Information
Type: Sound
Status: Enabled
Description: Intel(R) High Definition Audio Device
On Board Device 4 Information
Type: Ethernet
Status: Enabled
Description: Intel(R) 82574L Gigabit Ethernet Device
Handle 0x0038, DMI type 41, 11 bytes
Onboard Device
Reference Designation: CPU
Type: Video
Status: Enabled
Type Instance: 1
Bus Address: 0000:00:02.0
Handle 0x0039, DMI type 41, 11 bytes
Onboard Device
Reference Designation: L1U1
Type: Ethernet
Status: Enabled
Type Instance: 2
Bus Address: 0000:00:19.0
Handle 0x003A, DMI type 41, 11 bytes
Onboard Device
Reference Designation: AU1
Type: Sound
Status: Enabled
Type Instance: 1
Bus Address: 0000:00:1b.0
Handle 0x003B, DMI type 41, 11 bytes
Onboard Device
Reference Designation: L2U1
Type: Ethernet
Status: Enabled
Type Instance: 1
Bus Address: 0000:02:00.0
[linuxadmin@coyote ~]$ sudo dmidecode -t chassis
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
Manufacturer:
Type: Desktop
Lock: Not Present
Version:
Serial Number:
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number: To be filled by O.E.M.
[linuxadmin@coyote ~]$ sudo dmidecode -t processor
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
Handle 0x0040, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 1
Type: Central Processor
Family: Core i7
Manufacturer: Intel(R) Corporation
ID: A9 06 03 00 FF FB EB BF
Signature: Type 0, Family 6, Model 58, Stepping 9
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
Voltage: 11.1 V
External Clock: 100 MHz
Max Speed: 3800 MHz
Current Speed: 3400 MHz
Status: Populated, Enabled
Upgrade: Socket BGA1155
L1 Cache Handle: 0x003D
L2 Cache Handle: 0x003C
L3 Cache Handle: 0x003E
Serial Number: Not Specified
Asset Tag: Fill By OEM
Part Number: Fill By OEM
Core Count: 4
Core Enabled: 4
Thread Count: 8
Characteristics:
64-bit capable
[linuxadmin@coyote ~]$ sudo dmidecode -t memory
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
Handle 0x003F, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 32 GB
Error Information Handle: Not Provided
Number Of Devices: 4
Handle 0x0041, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x003F
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM3
Bank Locator: CHANNEL A SLOT0
Type: Unknown
Type Detail: None
Handle 0x0042, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x003F
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8 GB
Form Factor: DIMM
Set: None
Locator: DIMM1
Bank Locator: CHANNEL A SLOT1
Type: DDR3
Type Detail: Synchronous
Speed: 1333 MT/s
Manufacturer: Kingston
Serial Number: 1518CBE5
Asset Tag: 9876543210
Part Number: 99U5458-036.A00LF
Rank: 2
Configured Memory Speed: 1333 MT/s
Handle 0x0044, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x003F
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: DIMM4
Bank Locator: CHANNEL B SLOT0
Type: Unknown
Type Detail: None
Handle 0x0045, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x003F
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8 GB
Form Factor: DIMM
Set: None
Locator: DIMM2
Bank Locator: CHANNEL B SLOT1
Type: DDR3
Type Detail: Synchronous
Speed: 1333 MT/s
Manufacturer: Kingston
Serial Number: 1B18C3E5
Asset Tag: 9876543210
Part Number: 99U5458-036.A00LF
Rank: 2
Configured Memory Speed: 1333 MT/s
[linuxadmin@coyote ~]$ sudo dmidecode -t cache
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
Handle 0x003C, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L2
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Through
Location: Internal
Installed Size: 1 MB
Maximum Size: 1 MB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Multi-bit ECC
System Type: Unified
Associativity: 8-way Set-associative
Handle 0x003D, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L1
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Through
Location: Internal
Installed Size: 256 kB
Maximum Size: 256 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Parity
System Type: Data
Associativity: 8-way Set-associative
Handle 0x003E, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L3
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Write Back
Location: Internal
Installed Size: 8 MB
Maximum Size: 8 MB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Multi-bit ECC
System Type: Unified
Associativity: 16-way Set-associativePlease note that the install boot process fails before any disk-access. It boots from the USB stick. Boot from hard disk is no problem.
Just tell me if you need more... Glad to know you at my side. Thanks.
#119 Re: Other Issues » [SOLVED] is cron daemon crond is running when there is no cronjob set ? » 2023-07-06 10:51:13
my 2 cents to it:
andre@kyoto:~$ ps -aef | grep cron
root 2403 1 0 09:45 ? 00:00:00 /usr/sbin/cron
andre 11016 10606 0 12:45 pts/0 00:00:00 grep --color=auto cron
andre@kyoto:~$ The daemon is called cron:
andre@kyoto:~$ ls -l /etc/init.d/cron*
-rwxr-xr-x 1 root root 3059 Oct 11 2019 /etc/init.d/cron
andre@kyoto:~$Devuan 4, Chimaera, up-to-date.
#120 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-06 10:42:28
Yes, right, these were the isos tested:
https://files.devuan.org/devuan_daedalu … nstall.iso
https://files.devuan.org/devuan_daedalu … server.iso
https://files.devuan.org/devuan_daedalu … esktop.iso
Procedure:
1. Downloaded the files
2. Verified the checksums (sha256sum)
3. copied the files onto different USB sticks
(sudo dd if=devuan_daedalus_5.0.0-rc2_amd64_server.iso of=/dev/sdb bs=4M status=progress && sync)
4. Reset BIOS or EFI settings to default, disabled "secure-boot"
5. Inserted USB stick and tried to boot from it.
Important: After the attempt (as seen on screenshot) the computer, keyboard, everything was dead as in "dead". Had to power-cycle the computer to start again.
I tried on different machines. One of them (EFI-type machine) finally booted from the stick, the others did not (EFI and BIOS-types), they just locked up.
I have to say that an earlier daedalus-iso (early 2023)booted successfully on all machines.
If you need more info, please tell me and I will try to assist.
I'm really glad if you could bug-report it - I have rarely done so before... Thanks in advance!
#121 Re: Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-06 08:17:08
Ah, and of course, the machine is completely dead after this error message... Have to power it down.
#122 Installation » [SOLVED] Problems booting USB made from devuan_daedalus_5.0.0-rc2_amd64_* » 2023-07-06 08:15:31
- Andre4freedom
- Replies: 29
I'm sorry to report problems with the latest iso image files of daedalus rc2. (devuan_daedalus_5.0.0-rc2_amd64_netinstall.iso)
I have tested all rc2 isos, they all behave the same.
The problem occurs on some pure UEFI machines (GPT disk geometry) as well as on older machines (BIOS & MBR-geometry)
On some machines, the system would eventually boot into the installation, not at all on others.
I did try to boot the Debian 12 netinstall ISO and this one works perfectly well, as most other distro-isos do.
I'm not good enough to debug that, therefor I just report back to the community.
I hope this link to the screenshot works...
https://i.postimg.cc/4xjmyJRN/Screensho … -53-27.png
Have a great day - Andre
#123 Re: Desktop and Multimedia » [SOLVED] Can't figure out how to play DVDs » 2023-05-22 16:59:38
Excellent comment, alexkemp.
To play DVDs, vlc and libdvdcss2 did the trick for quite some time already, in most Linux distros.
Bluray is a completely different story! Thank you for your hints!
#124 Re: Intergalactic Communities » Interest probing: Devuan Conference » 2023-05-16 08:37:03
Could be nice, a good idea. Certainly if it's somewhere in Central Europe I'd be interested. Depending on the type of conference as well (speeches, workshops, exchange of experiences, future developments and directions where Devuan goes...). Lovely.
I'm committed to Devuan.
#125 Re: Desktop and Multimedia » XFCE4 config on devuan - differences to debian » 2023-04-04 16:39:55
webman, I'm not aware of what version of Devuan you use.....
but, by default the selection of xfce4 desktop environment installs slim as display-manager.
Just install lightdm instead --- and you will be able to switch users.
(Use sysnaptic or apt install lightdm to install and answer the questions sensibly)
Good luck
Board footer
