Posts by rolfie

rolfie · News & Announcements

Thanks for the confirmation concerning nano.

Just repeated the install into the same VM overwriting it.
* Strange behaviour when using arrow keys to bring back previous commands: line not deleted, text is added on the end up to 80 characters? The last command is executed again.
* Looks like the hostname is not evaluated correctly. The login tells me Devuan GNU/Linux 3 (none), when I login the prompt is root@(none), cat hostname shows the intended name.

rolfie

PS: Using the desktop.iso seems to work fine. At first sight no issues like with the netinstall image.
Observation: no graphical installer present. Is that intended?

rolfie · News & Announcements

Great that it is finally there.

CLI mode expert install from netinstall image into a VM, no other specials:
* Is nano no more on board?
* Strange behaviour when using arrow keys to bring back previous commands: line not deleted, text is added on the end.

Somebody else with the same error?

rolfie

PS: checksum checked, is ok.

rolfie · Other Issues

You have to run dpkg as root.

rolfie

rolfie · Other Issues

Extract Palemoon to /tmp.
As root do a cd /tmp and then mv palemoon /opt/palemoon
As user create starter on the desktop that calls up /opt/palemoon/palemoon

That should work fine.

rolfie

rolfie · Installation

Thanks, the keyboard works (reacts to NUMLOCK), but no reaction to any ctrl-alt-fn combination.

The single boot deletes the time setting, is back to 1.1.2019 00:00.

Can reboot with ctrl-alt-del.

rolfie

rolfie · Desktop and Multimedia

That package does not come automatically. As root enter:

apt update
apt -t ascii-backports install mate-applet-brisk-menu

It may be worth to read: https://wiki.debian.org/Backports

rolfie

rolfie · Installation

Head_on_a_Stick wrote:

From where did you obtain the firmware?
I would try https://git.kernel.org/pub/scm/linux/ke … ree/amdgpu
Have you tested this hardware with Arch Linux yet? They have kernel 5.8.8 and the firmware from 2020-02-24.

Thats exactly where I got the individual files and the tarball from.

Loaded the latest available arch onto a stick and bootet the PC from that. I did not see the same errors, may be due to the fact that arch uses systemd, but the boot ends on the command line with wrong locale and no network, both to be configured in a different way. I am not familiar with arch/systemd.

I checked the journal for indications if the navi14 firmware is loaded, could not find anything.

What can I learn from this experiment? Does it pay to invest time for learning something I do not want/need as a stable working environment?

Thanks, rolfie

rolfie · Desktop and Multimedia

You have to enable ascii-backports in your sources.list.

rolfie

rolfie · Installation

Good question. Reloaded 18 individual files again from a different PC, and the latest complete firmware package as tarball I found on github. I could not find any checksums.

Replacing the 18 individual files did not seem to make a difference. Then I extracted the files from the tarball and copied them into the library.

Then I realised a new phenomenon: with every reboot the clock is reset to 1.1.2019 00:00 (looks like this is the bios minimum). And not due to the bios battery being bad, replacing that did not help. Other parameters do not seem to be affected, i.e. Power fail: ON.

The PC now is stuck at "waiting for /dev to be fully populated", there is no more login window poppping up now.

What is this? Any suggestions?

rolfie

rolfie · Desktop and Multimedia

https://ftp.mozilla.org/pub/firefox/releases/52.9.0esr/

rolfie

rolfie · Installation

Having invested into some hot new hardware planned to be the replacment for my wifes PC, I need some advice to get it fully working.

The HW concerned is a AMD X570 chipset board with a Ryzen7 3700X CPU and a Radeon RX5500XT graphics card.

The initial cli installation was done with a Sapphire GPRO 2200 installed, based on ASCII2.1 with openrc, then upgraded to Beowulf, updated with kernel 5.4 from backports, then xorg/lightdm/Mate desktop on top. Finally I changed the graphics card to the 5500XT. The PC boots and seems to be usable, though there are a few issues left.

1.) Minor issue: lspci shows a 7340 as detected VGA which seems to be the vendor ID.

lspci
0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 7340 (rev c5)

2.) There are iommu errors shown during boot.

Mar  1 16:42:52 rh060 kernel: [    1.825144] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    1.945170] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
Mar  1 16:42:52 rh060 kernel: [    1.945170] pci 0000:00:00.2: AMD-Vi: Extended features (0x58f77ef22294ade):
Mar  1 16:42:52 rh060 kernel: [    1.945171]  PPR X2APIC NX GT IA GA PC GA_vAPIC
Mar  1 16:42:52 rh060 kernel: [    1.945172] AMD-Vi: Interrupt remapping enabled
Mar  1 16:42:52 rh060 kernel: [    1.945173] AMD-Vi: Virtual APIC enabled
Mar  1 16:42:52 rh060 kernel: [    1.945173] AMD-Vi: X2APIC enabled
Mar  1 16:42:52 rh060 kernel: [    1.945264] AMD-Vi: Lazy IO/TLB flushing enabled
Mar  1 16:42:52 rh060 kernel: [    1.945276] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=0a:00.0 address=0x7fb570a40]
Mar  1 16:42:52 rh060 kernel: [    1.945279] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=0a:00.0 address=0x7fb570a60]
Mar  1 16:42:52 rh060 kernel: [    1.945982] amd_uncore: AMD NB counters detected
Mar  1 16:42:52 rh060 kernel: [    1.945985] amd_uncore: AMD LLC counters detected
Mar  1 16:42:52 rh060 kernel: [    1.946171] LVT offset 0 assigned for vector 0x400
Mar  1 16:42:52 rh060 kernel: [    1.946238] perf: AMD IBS detected (0x000003ff)
Mar  1 16:42:52 rh060 kernel: [    1.946242] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
Mar  1 16:42:52 rh060 kernel: [    1.946610] Initialise system trusted keyrings
Mar  1 16:42:52 rh060 kernel: [    1.946618] Key type blacklist registered
Mar  1 16:42:52 rh060 kernel: [    1.946666] workingset: timestamp_bits=40 max_order=23 bucket_order=0
Mar  1 16:42:52 rh060 kernel: [    1.947333] zbud: loaded
Mar  1 16:42:52 rh060 kernel: [    1.947476] Platform Keyring initialized
Mar  1 16:42:52 rh060 kernel: [    1.947477] Key type asymmetric registered
Mar  1 16:42:52 rh060 kernel: [    1.947477] Asymmetric key parser 'x509' registered
Mar  1 16:42:52 rh060 kernel: [    1.947482] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
Mar  1 16:42:52 rh060 kernel: [    1.947517] io scheduler mq-deadline registered
Mar  1 16:42:52 rh060 kernel: [    1.951955] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    1.951955] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    1.951955] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    2.323671] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    2.447853] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    2.575032] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=0a:00.0 address=0x7fb570a90]
Mar  1 16:42:52 rh060 kernel: [    2.579018] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    2.703212] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    2.827398] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    2.951446] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    3.075596] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    3.199711] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    3.323794] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    3.443723] tsc: Refined TSC clocksource calibration: 3593.250 MHz
Mar  1 16:42:52 rh060 kernel: [    3.443732] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x33cb6addeae, max_idle_ns: 440795225061 ns
Mar  1 16:42:52 rh060 kernel: [    3.443753] clocksource: Switched to clocksource tsc
Mar  1 16:42:52 rh060 kernel: [    3.447731] AMD-Vi: Completion-Wait loop timed out
Mar  1 16:42:52 rh060 kernel: [    3.577101] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=0a:00.0 address=0x7fb570ad0]
Mar  1 16:42:52 rh060 kernel: [    3.577104] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=0a:00.0 address=0x7fb570af0]
Mar  1 16:42:52 rh060 kernel: [    3.577135] pcieport 0000:00:07.1: AER: enabled with IRQ 31
Mar  1 16:42:52 rh060 kernel: [    3.577246] pcieport 0000:00:08.1: AER: enabled with IRQ 32
Mar  1 16:42:52 rh060 kernel: [    3.577390] pcieport 0000:00:08.2: AER: enabled with IRQ 33
Mar  1 16:42:52 rh060 kernel: [    3.577532] pcieport 0000:00:08.3: AER: enabled with IRQ 34
Mar  1 16:42:52 rh060 kernel: [    3.578516] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Mar  1 16:42:52 rh060 kernel: [    3.578522] efifb: probing for efifb
Mar  1 16:42:52 rh060 kernel: [    3.578542] efifb: framebuffer at 0xe0000000, using 3072k, total 3072k
Mar  1 16:42:52 rh060 kernel: [    3.578542] efifb: mode is 1024x768x32, linelength=4096, pages=1
Mar  1 16:42:52 rh060 kernel: [    3.578543] efifb: scrolling: redraw
Mar  1 16:42:52 rh060 kernel: [    3.578543] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Mar  1 16:42:52 rh060 kernel: [    3.578593] Console: switching to colour frame buffer device 128x48
Mar  1 16:42:52 rh060 kernel: [    3.579610] fb0: EFI VGA frame buffer device
Mar  1 16:42:52 rh060 kernel: [    3.579636] Monitor-Mwait will be used to enter C-1 state
Mar  1 16:42:52 rh060 kernel: [    3.580669] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Mar  1 16:42:52 rh060 kernel: [    3.580894] Linux agpgart interface v0.103
Mar  1 16:42:52 rh060 kernel: [    3.581248] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>

3.) The latest amdgpu firmware package not yet supports the 5500 card. Found navi14 firmware on github that should support the 5500XT card, downloaded the files and placed them in /lib/firmware/amdgpu, but it looks like they are not loaded from kernel 5.4/5.5.

Mar  1 16:42:52 rh060 kernel: [   13.634934] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xe0000000 -> 0xefffffff
Mar  1 16:42:52 rh060 kernel: [   13.634936] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xf0000000 -> 0xf01fffff
Mar  1 16:42:52 rh060 kernel: [   13.634937] amdgpu 0000:0a:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xfcb00000 -> 0xfcb7ffff
Mar  1 16:42:52 rh060 kernel: [   13.634938] checking generic (e0000000 300000) vs hw (e0000000 10000000)
Mar  1 16:42:52 rh060 kernel: [   13.634939] fb0: switching to amdgpudrmfb from EFI VGA

Mar  1 16:42:52 rh060 kernel: [   13.635031] amdgpu 0000:0a:00.0: vgaarb: deactivate vga console

Mar  1 16:42:52 rh060 kernel: [   13.660960] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/navi14_gpu_info.bin
Mar  1 16:42:52 rh060 kernel: [   13.660961] amdgpu 0000:0a:00.0: Failed to validate gpu_info firmware "amdgpu/navi14_gpu_info.bin"
Mar  1 16:42:52 rh060 kernel: [   13.660966] amdgpu 0000:0a:00.0: Fatal error during GPU init
Mar  1 16:42:52 rh060 kernel: [   13.660968] [drm] amdgpu: finishing device.

Mar  1 16:42:52 rh060 kernel: [   13.660981] ------------[ cut here ]------------
Mar  1 16:42:52 rh060 kernel: [   13.660982] sysfs group 'fw_version' not found for kobject '0000:0a:00.0'
Mar  1 16:42:52 rh060 kernel: [   13.660991] WARNING: CPU: 5 PID: 954 at fs/sysfs/group.c:280 sysfs_remove_group+0x76/0x80
Mar  1 16:42:52 rh060 kernel: [   13.660992] Modules linked in: snd_hda_codec_realtek snd_hda_codec_generic pcc_cpufreq(-) amdgpu(+) ledtrig_audio snd_hda_codec_hdmi edac_mce_amd gpu_sched snd_hda_intel ttm efi_pstore snd_intel_nhlt drm_kms_helper kvm_amd eeepc_wmi asus_wmi snd_hda_codec drm kvm snd_hda_core battery snd_hwdep sparse_keymap snd_pcm rfkill sp5100_tco evdev irqbypass video serio_raw wmi_bmof mxm_wmi pcspkr efivars k10temp mfd_core watchdog snd_timer snd ccp soundcore rng_core button acpi_cpufreq ext4 crc16 mbcache jbd2 crc32c_generic algif_skcipher af_alg dm_crypt dm_mod sg sr_mod cdrom sd_mod hid_generic usbhid hid uas usb_storage crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ahci libahci xhci_pci xhci_hcd libata aesni_intel igb nvme usbcore scsi_mod crypto_simd cryptd glue_helper i2c_algo_bit dca i2c_piix4 nvme_core ptp pps_core usb_common wmi
Mar  1 16:42:52 rh060 kernel: [   13.661016] CPU: 5 PID: 954 Comm: udevd Not tainted 5.4.0-0.bpo.3-amd64 #1 Debian 5.4.13-1~bpo10+1
Mar  1 16:42:52 rh060 kernel: [   13.661017] Hardware name: System manufacturer System Product Name/PRIME X570-PRO, BIOS 1405 11/19/2019
Mar  1 16:42:52 rh060 kernel: [   13.661018] RIP: 0010:sysfs_remove_group+0x76/0x80
Mar  1 16:42:52 rh060 kernel: [   13.661019] Code: 48 89 df 5b 5d 41 5c e9 e8 bd ff ff 48 89 df e8 e0 ba ff ff eb cb 49 8b 14 24 48 8b 75 00 48 c7 c7 40 d2 ac 8a e8 e3 85 d5 ff <0f> 0b 5b 5d 41 5c c3 0f 1f 00 0f 1f 44 00 00 48 85 f6 74 31 41 54
Mar  1 16:42:52 rh060 kernel: [   13.661020] RSP: 0018:ffffae6e0075ba20 EFLAGS: 00010282
Mar  1 16:42:52 rh060 kernel: [   13.661021] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8ac4d7e8
Mar  1 16:42:52 rh060 kernel: [   13.661022] RDX: 0000000000000001 RSI: 0000000000000092 RDI: 0000000000000247
Mar  1 16:42:52 rh060 kernel: [   13.661022] RBP: ffffffffc0da3de0 R08: 000000000000043b R09: 0000000000000004
Mar  1 16:42:52 rh060 kernel: [   13.661023] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9aceba1170b0
Mar  1 16:42:52 rh060 kernel: [   13.661023] R13: ffff9aceb7b94da0 R14: 0000000000000000 R15: ffff9acead9d8b10
Mar  1 16:42:52 rh060 kernel: [   13.661024] FS:  00007f722b6df880(0000) GS:ffff9acebe940000(0000) knlGS:0000000000000000
Mar  1 16:42:52 rh060 kernel: [   13.661025] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar  1 16:42:52 rh060 kernel: [   13.661025] CR2: 00007ffc55325fc8 CR3: 00000007ee7b4000 CR4: 0000000000340ee0
Mar  1 16:42:52 rh060 kernel: [   13.661026] Call Trace:
Mar  1 16:42:52 rh060 kernel: [   13.661109]  amdgpu_device_fini+0x445/0x479 [amdgpu]
Mar  1 16:42:52 rh060 kernel: [   13.661169]  amdgpu_driver_unload_kms+0x4a/0x90 [amdgpu]
Mar  1 16:42:52 rh060 kernel: [   13.661245]  amdgpu_driver_load_kms.cold.12+0x38/0x6e [amdgpu]
Mar  1 16:42:52 rh060 kernel: [   13.661257]  drm_dev_register+0x10d/0x150 [drm]
Mar  1 16:42:52 rh060 kernel: [   13.661315]  amdgpu_pci_probe+0x15a/0x1d0 [amdgpu]
Mar  1 16:42:52 rh060 kernel: [   13.661318]  local_pci_probe+0x42/0x80
Mar  1 16:42:52 rh060 kernel: [   13.661320]  pci_device_probe+0xfc/0x1b0
Mar  1 16:42:52 rh060 kernel: [   13.661322]  really_probe+0x1c2/0x3e0
Mar  1 16:42:52 rh060 kernel: [   13.661324]  driver_probe_device+0xb4/0x100
Mar  1 16:42:52 rh060 kernel: [   13.661325]  device_driver_attach+0x4f/0x60
Mar  1 16:42:52 rh060 kernel: [   13.661326]  __driver_attach+0x86/0x140
Mar  1 16:42:52 rh060 kernel: [   13.661327]  ? device_driver_attach+0x60/0x60
Mar  1 16:42:52 rh060 kernel: [   13.661328]  bus_for_each_dev+0x77/0xc0
Mar  1 16:42:52 rh060 kernel: [   13.661331]  ? klist_add_tail+0x3b/0x70
Mar  1 16:42:52 rh060 kernel: [   13.661332]  bus_add_driver+0x14d/0x1f0
Mar  1 16:42:52 rh060 kernel: [   13.661333]  ? 0xffffffffc0ff1000
Mar  1 16:42:52 rh060 kernel: [   13.661334]  driver_register+0x6b/0xb0
Mar  1 16:42:52 rh060 kernel: [   13.661335]  ? 0xffffffffc0ff1000
Mar  1 16:42:52 rh060 kernel: [   13.661337]  do_one_initcall+0x46/0x1f4
Mar  1 16:42:52 rh060 kernel: [   13.661340]  ? _cond_resched+0x15/0x30
Mar  1 16:42:52 rh060 kernel: [   13.661342]  ? kmem_cache_alloc_trace+0x1d9/0x220
Mar  1 16:42:52 rh060 kernel: [   13.661344]  do_init_module+0x5a/0x220
Mar  1 16:42:52 rh060 kernel: [   13.661346]  load_module+0x222d/0x24a0
Mar  1 16:42:52 rh060 kernel: [   13.661349]  ? __do_sys_finit_module+0xa8/0x110
Mar  1 16:42:52 rh060 kernel: [   13.661350]  __do_sys_finit_module+0xa8/0x110
Mar  1 16:42:52 rh060 kernel: [   13.661352]  do_syscall_64+0x52/0x160
Mar  1 16:42:52 rh060 kernel: [   13.661354]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar  1 16:42:52 rh060 kernel: [   13.661355] RIP: 0033:0x7f722bc20f59
Mar  1 16:42:52 rh060 kernel: [   13.661356] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 07 6f 0c 00 f7 d8 64 89 01 48
Mar  1 16:42:52 rh060 kernel: [   13.661357] RSP: 002b:00007ffc5532e958 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Mar  1 16:42:52 rh060 kernel: [   13.661358] RAX: ffffffffffffffda RBX: 00005585f19bd080 RCX: 00007f722bc20f59
Mar  1 16:42:52 rh060 kernel: [   13.661358] RDX: 0000000000000000 RSI: 00007f722bd01cad RDI: 000000000000000f
Mar  1 16:42:52 rh060 kernel: [   13.661359] RBP: 00007f722bd01cad R08: 0000000000000000 R09: 0000000000000000
Mar  1 16:42:52 rh060 kernel: [   13.661359] R10: 000000000000000f R11: 0000000000000246 R12: 0000000000000000
Mar  1 16:42:52 rh060 kernel: [   13.661360] R13: 00005585f199f460 R14: 0000000000020000 R15: 00005585f19bd080
Mar  1 16:42:52 rh060 kernel: [   13.661361] ---[ end trace c007050759878ea8 ]---
Mar  1 16:42:52 rh060 kernel: [   13.661474] amdgpu: probe of 0000:0a:00.0 failed with error -22

4.) Like in this thread https://dev1galaxy.org/viewtopic.php?id=3336 the boot messages stop at "waiting for /dev to be fully populated". When switching to the login screen first of all a scrambled display is present for a second, then Lightdm login is presented as expected.

5.) Digged a bit in the internet and found a release candidate for kernel 5.5 in Debian experimental. I downloaded the .deb package from Debian and installed it with dpkg -i. The PC boots, but the issues remain as is.

6.) navi14 firmware: downloaded them and copied them into what I think is the right directory, access rights seem to be set correctly. The message is "Failed to validate gpu_info firmware "amdgpu/navi14_gpu_info.bin"". What did I miss?

Thanks, rolfie

rolfie · Hardware & System Configuration

When lilo supports UUID, an additional device smuggling itself into the device list should not matter at all. Something else is wrong.

I am running a ASUS Prime X470 Pro, Ryzen7 2700X CPU, Pulse Radeon RX 570 running ASCII with backports kernel. UEFI mode, gpt partition table, grub, encrypted except boot. A different HW and system setup, but with some relation to yours.

I needed to install firmware-linux-free from stable and firmware-linux-nonfree from backports to support the HW. firmware-linux-nonfree automatically pulls firmware-amd-graphics and the amd microcode required to support the Ryzen. Give that a try.

BTW: when there are package versions in stable and backports, without specifying explicitely backports the stable version is installed. i.e. you need to write apt -t ascii backports install .... to get the backports package.

rolfie

rolfie · Hardware & System Configuration

@hmj: sorry, I overread the Lilo topic. This is outside my expertise, I am using grub only.

To get a clue what might be going wrong we will need more details.

How is the original PC set up? It had a conventional Bios without UEFI, so the assumption is that the HDD had a msdos partition table. Showing this might also give a clue. Are the three installations using standard or custom kernels/initrds? Was the HDD the only device on that old PC? Are the installations using encryption/LVM or other specialities? What kind of mouse and keyboard interface has this mainboard? Is the HDD still booting in the old PC?

Booting from the new PC should work in principle, but .....
Different graphics, different network chipset etc. might need different firmware. But all of these things should only count when the kernel is booting up.

Can you tell us which parameters you modified in the UEFI bios to make CSM work? Secure boot out of the way? Boot from Legacy set for storgaer devices?

To the keyboard trouble: if you are using an USB keyboard, make sure you got the legacy USB mode enabled in the bios. It might be worth trying an old PS2 keyboard if available.

Is the HDD the only device connected to the new mainboard? Have a close look to other devices on the new mainboard like USB sticks, card readers .....

Is lilo able to start against an UUID? Or does it still use the oldfashioned hd0,0 notation? When I looked into lilo last it couldn't cope with UUID.

I hope this gives you some ideas what to check and something to think about.

Good lukc, rolfie

rolfie · Hardware & System Configuration

Maybe putting your HD into a different PC deleted some entries in /boot/efi that are required. Give the following procedure a try:

* Boot from your Live DVD
* chroot into one of the 3 installations you want to revive.
* As root:

update-grub
apt-get --reinstall install grub-common grub-efi-amd64 os-prober

Good luck, rolfie

rolfie · Installation

This is from a native Beowulf installed from a netinstall image last spring/summer:

apt policy
Paketdateien:
 100 /var/lib/dpkg/status
     release a=now
 500 http://deb.devuan.org/merged beowulf-updates/main amd64 Packages
     release v=3.0.0,o=Devuan,a=testing-updates,n=beowulf-updates,l=Devuan,c=main,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged beowulf-security/non-free amd64 Packages
     release v=3.0.0,o=Devuan,a=testing-security,n=beowulf-security,l=Devuan-Security,c=non-free,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged beowulf-security/main amd64 Packages
     release v=3.0.0,o=Devuan,a=testing-security,n=beowulf-security,l=Devuan-Security,c=main,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged beowulf/contrib amd64 Packages
     release v=3.0,o=Devuan,a=testing,n=beowulf,l=Devuan,c=contrib,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged beowulf/non-free amd64 Packages
     release v=3.0,o=Devuan,a=testing,n=beowulf,l=Devuan,c=non-free,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged beowulf/main amd64 Packages
     release v=3.0,o=Devuan,a=testing,n=beowulf,l=Devuan,c=main,b=amd64
     origin deb.devuan.org

I am receiving security updates every now and then.

rolfie

rolfie · Installation

Alsa is available on Beowulf, you may check what is available in the reps and installed with apt list alsa*. I my case I think it comes with Mate desktop, I did not need to install it separately. I just have got alsa-utils installed. Maybe adding the alsamixergui also makes sense.

Then as root execute an alsactl init.

rolfie

rolfie · Other Issues

Thanks for confirming, I feel better now since I understand I am not alone. The BIOS is set to Greenwich time, the desktop shows the time what is to expect and complies to my three radio controlled clocks, sync is done via ntp/ntpdate, despite the confusing output everything seems to be working right.

Have a nice Sunday, rolfie

rolfie · Hardware & System Configuration

The failure message from the original post and after installing libmtp-runtime look the same. I wonder if its not mtp-probe thats missing but that the /sys/devices/-link is wrong? Make a thorough check.

BTW: I think your upgrade to Beowulf is incomplete. You are still running the 4.9 kernel from ASCII. Do a apt full-upgrade to get rid of all dist mixtures. If that means that you need some firmware, install it.

rolfie

rolfie · Other Issues

Just for fun I checked with my ASCII PC and on my fileserver running Beowulf. On both identical behaviour. I am confused.

Mate displays 11:21.

hwclock --utc
2020-03-01 11:21:00.327413+01:00
hwclock --localtime
2020-03-01 10:21:11.155645+01:00
ls -l /etc/localtime
lrwxrwxrwx 1 root root 33 Sep 25 22:48 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin

I would expect it the other way round. ???

rolfie

rolfie · Desktop and Multimedia

The issues with consolekit are not only limited to reboot/shutdown, initially you also can't open memory sticks/external drives as a user.

Simply installing

apt install libpolkit-backend-elogind-1-0 libpolkit-gobject-elogind-1-0

did the trick for me. It removes consolekit or whatever and issues are gone.

I guess this is inherited from Debian. The ASCII2.0 installer brings consolekit, and if I am not mistaken this is fixed with ASCII2.1, and for sure with Beowulf, no matter if installed from netinstall (currently no more available) or upgraded from ASCII.

rolfie

rolfie · Desktop and Multimedia

Ignore that comment that the fix is for Ceres only. I can confirm that lightdm/mate with elogind works as well with ASCII 2.0 as Beowulf (comes that way out of the box) while consolekit causes problems. Gave me a hard time when setting up ASCII directly after release. There are some threads in this forum that deal with this problem.

rolfie

rolfie · Installation

You seem to have a pretty unusual setup. Well, sda5 being present must not mean that you must have sda1-4. If your disk has a msdos partition table, it is possible that you only have sda5 on that disk. msdos partitions do only support up to four primary partitions. Except there is a way out: you define one partition to be an extended partition. In the extended partition you can have up to I think 24 or so logical drives. Modern Linux distributions label the first logical drive in the extended partition sda5. In your case sda5 is a physical volume for an LVM, as system-config-lvm shows.

Use gparted to show the type of partition table (drive information) and if there isn't an sda1. I am not 100% sure, I never tried such a setup, but I think you must at least have a sda1 drive with /boot assigned to that partition.

Drives with gpt partition table work different, there you can have I think 128 primary partitions on a device, starting from sdx1 to sdx128. There is enough literature in the internet for these two scenarios.

Your approach trying out which distro suits your needs and your preferences in terms of tools, desktop etc. makes sense based on live systems. When your laptop supports booting from USB stick, use that, its faster.

My experience with installing live systems onto a PC is very mixed, maybe because very often I used special HW configurations like a socket 7 AMD K2 PC with an UltraTX133 card that was not supported by the kernels at the time when trying this, or later when insisting on encrypting my installations. I stick to official install media.

I started of with Debian Sarge on a file server, a small Linux based router, and began to experiment with Edge and Lenny in parallel to Windows. I moved to a Linux workstation more than 8 years ago using Squeeze with Gnome desktop.

Nowadays I am on ASCII with Mate desktop, and I am happy to use non-free firmware and e.g. Virtual Box from Oracle from contrib. My network (Realtek chipset) and Radeon graphics won't work without the non-free firmware, but I am not that picky. I use Evolution and Thunderbird for mail and news, Firefox ESR for internet, I have tried the TOR browser and Palemoon, cups for an old Kyocera colour printer with Postscript controlled by a PPD file from Kyocera, got a Canon scanner that works with xsane/gscan2pdf. Attention: Not all scanners are supported by Linux! I owned an older Canon scanner that only was supported under Windows. Had to operate it from a XP VM in VirtualBox, and stuck with this operation mode for several years until I was tired and spent the money for a new scanner selected to be supported under Linux.

There are a lot of other combinations of desktops and programs. A pure Debian/Devuan is free SW and in my eyes a good choice. Its wide spread, already lives quite a long time and is mature, and will go on living for quite a while making progress. There is a big community availabe to help you.

If you do not like to use non-free firmware, you might need to live with limitations. Your choice.

Have fun, rolfie

rolfie · Installation

If fdisk only shows one or maybe two partitions (I can only guess, you are not disclosing details, there are many ways to set up a Linux system), I am pretty sure the last installation has overwritten everything older. I do not think any rescue system will find other Linux systems.

A LVM can be used for various things. One is that you can span a logical volume over a set of hard disk drives.

I am using if for a different purpose. My systems are all encrypted, with separate /boot partitions and also external /home drives. The Linux system hosts in an encrypted luks container that again hosts a physical volume for LVM typically consisting of two logical volumes, one for / and one for /swap. /swap typically resides in a separate partition.

If you use ASCII, you may analyse your LVM with system-config-lvm. This graphical program shows up under system tools and also requires root privilegues.

Using a LVM to support several Linux systems is an unsual approach, I never heard of it, this is outside my knowledge and experience. I know how to set up a Linux next to a Windows, but never have tried several Linux versions on a disk drive. There are for sure how-tos on the internet.

Good luck, rolfie

rolfie · Hardware & System Configuration

Tried the current built 2020-02-01 on CD, that comes with kernel 5.4.15. Same messages displayed during boot.

I am not familiar with putting such an iso on a stick and then to update this. Will wait a few days for the next release.

rolfie

rolfie · Installation

hmm, you are new to Linux, aren't you? I guess you haven't installed two or three distros in parallel, but have overwritten them. Such an approach is not straight forward and something for the advanced user.

First of all, let have a look at the partitions on your disk. Open a console with root privilegues and enter fdisk -l. That should show how the disk is used currently. My preferred gui program is gparted, could be an alternative for you.

Also wondering about the lvm. This is also something more advanced. Don't know if you have any special reason to use it on your laptop?
Some literature:
https://en.wikipedia.org/wiki/Logical_volume_management
https://wiki.ubuntuusers.de/Logical_Volume_Manager/ (in German)
http://tldp.org/HOWTO/LVM-HOWTO/

Is there anything else on the laptop like a Windows version?

rolfie

The officially official Devuan Forum!

#1026 Re: News & Announcements » Beowulf Beta is here! » 2020-03-16 19:13:10

#1027 Re: News & Announcements » Beowulf Beta is here! » 2020-03-16 18:14:53

#1028 Re: Other Issues » Can't execute program. System doesn't recognize it's location. » 2020-03-10 21:57:24

#1029 Re: Other Issues » Can't execute program. System doesn't recognize it's location. » 2020-03-09 14:22:55

#1030 Re: Installation » [Solved at last] Issues with very new hardware » 2020-03-09 10:48:43

#1031 Re: Desktop and Multimedia » SOLVED: Brisk menu (mate-applet-brisk-menu) is not available » 2020-03-08 09:45:01

#1032 Re: Installation » [Solved at last] Issues with very new hardware » 2020-03-07 20:10:43

#1033 Re: Desktop and Multimedia » SOLVED: Brisk menu (mate-applet-brisk-menu) is not available » 2020-03-07 19:16:12

#1034 Re: Installation » [Solved at last] Issues with very new hardware » 2020-03-06 18:01:51

#1035 Re: Desktop and Multimedia » compile firefox-esr (52) --enable-alsa ? » 2020-03-05 20:28:30

#1036 Installation » [Solved at last] Issues with very new hardware » 2020-03-05 20:23:22

#1037 Re: Hardware & System Configuration » [Solved ]Mainboard ASUS with AMD Ryzen 3: root device not found » 2020-03-05 19:31:14

#1038 Re: Hardware & System Configuration » [Solved ]Mainboard ASUS with AMD Ryzen 3: root device not found » 2020-03-05 10:01:22

#1039 Re: Hardware & System Configuration » [Solved ]Mainboard ASUS with AMD Ryzen 3: root device not found » 2020-03-04 18:39:28

#1040 Re: Installation » Security Updates for Beowulf not installed automatically » 2020-03-04 12:47:57

#1041 Re: Installation » (beowulf) no ALSA available? » 2020-03-04 09:57:20

#1042 Re: Other Issues » Hwclock issue » 2020-03-01 13:28:18

#1043 Re: Hardware & System Configuration » UDEV problem - Brother MFC7420 » 2020-03-01 11:14:42

#1044 Re: Other Issues » Hwclock issue » 2020-03-01 11:03:52

#1045 Re: Desktop and Multimedia » KDE doesn't shutdown or reboot! » 2020-03-01 09:46:14

#1046 Re: Desktop and Multimedia » login / Display managers » 2020-03-01 09:38:50

#1047 Re: Installation » bood manager ?? » 2020-02-27 20:03:40

#1048 Re: Installation » bood manager ?? » 2020-02-25 18:45:40

#1049 Re: Hardware & System Configuration » [Solved] Boot messages surpressed with new graphics card » 2020-02-24 19:30:26

#1050 Re: Installation » bood manager ?? » 2020-02-24 18:02:25

Board footer