The officially official Devuan Forum!

You are not logged in.

#1 Devuan » Inst manpages-de 4.9.1-5 causes Remv xorg, initramfs-tools, etc. » 2021-02-18 11:33:13

pAul
Replies: 0

I came across with a strange behavior installing the newest version of manpages-de:

An installation of manpages-de 4.9.1-5 causes to remove more then 50 packages among which are xorg, linux-image, eudev, cryptsetup-initramfs, udev, procps, initramfs-tools, firefox-esr, openssh-server, cups etc.

First I struggled over a strange behavior updating psmisc, cf. the situation in https://bugs.debian.org/cgi-bin/bugrepo … bug=982059

This affects Devuan Ceres system, but not Beowulf.

Debian Sid seems not to be affected.

bug number #552

#2 Re: Installation » Devuan on Raspberry Pi 4 - now also aarch64 » 2020-05-23 09:01:20

forgot to answer, everything works fine with your above instruction, therion23
(clean install is sometimes better ;-) )

the only thing I don't understand is what you mean with

- Double check your /boot/cmdline.txt - especially the root= setting.

cf. with my output post #16

Anyway, everything works great, thanks for the instruction

#3 Re: ARM Builds » Is any work planned for devuan on the raspberry pi 4? » 2020-05-19 10:10:53

thanks, tuxd3v,  thought I have to remove it after download big_smile

worked well

#4 Re: Installation » Devuan on Raspberry Pi 4 - now also aarch64 » 2020-05-19 10:07:11

WLAN I will set up later. Firstly, the Pi is connected via LAN. I thought, I can grab the working SD Card form the 1 GB version with devuan, plug in into the 2 GB Pi and get started.

Maybe that's the point. The 1 GB Pi has a wlan1 interface, and my Pi2 a wlan2. However, since I use both as WLAN AP, I bridged those interfaces with eth0 to the bridge interface br0 which is the only one to ask the DHCP server. The only explanation I have, is that the bridge does not succeed on the 2 GB having a wlan0 interface, and thus does not ask for an IP address.

I should better start with a blank SD card.

Btw: clean Raspbian or yan's image from https://dev1galaxy.org/viewtopic.php?id=3209&p=3 worked well

#5 Re: Installation » Devuan on Raspberry Pi 4 - now also aarch64 » 2020-05-19 08:42:56

therion23 wrote:

Do you have a wlan0 interface at all?

wlan0 is present

output from raspbian:

$ iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          
eth0      no wireless extensions.

#6 Re: Installation » Devuan on Raspberry Pi 4 - now also aarch64 » 2020-05-19 08:35:18

Thanks for your reply. I'm really confused about what's going on. I'm able to boot raspbian and also made an EEPROM update using stable/pieeprom-2020-04-16.bin as explained.

The ouput of $ vcgencmd bootloader_config changed from

BOOT_UART=0
WAKE_ON_GPIO=1
POWER_OFF_ON_HALT=0
FREEZE_VERSION=0

to

[all]
BOOT_UART=0
WAKE_ON_GPIO=1
POWER_OFF_ON_HALT=0
DHCP_TIMEOUT=45000
DHCP_REQ_TIMEOUT=4000
TFTP_FILE_TIMEOUT=30000
TFTP_IP=
TFTP_PREFIX=0
BOOT_ORDER=0x1
SD_BOOT_MAX_RETRIES=3
NET_BOOT_MAX_RETRIES=5
[none]
FREEZE_VERSION=0

However, I'm not able to see devuan receiving an ip address. Also tried the SD card with devuan from Raspi4 - 1GB without success in my Pi4 - 2 GB.

#7 Re: Installation » Devuan on Raspberry Pi 4 - now also aarch64 » 2020-05-18 14:45:51

therion23 wrote:

Mine is a 4GB model, but i doubt it makes any difference. Tell me where it breaks for you and i'll try to think of a solution.

It boots up wright on the Pi2, but on the Pi4 (2GB) it does not receive an IP-address

# uname -a
Linux devuan 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux

# cat /boot/cmdline.txt 
dwc_otg.fiq_fix_enable=2 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait rootflags=noload net.ifnames=0

On the Pi4 with 1GB everything works fine even with ascii (and newest hostapd). But the same card does not receive an IP on the version with 2GB of memory.

#8 Re: Installation » Devuan on Raspberry Pi 4 - now also aarch64 » 2020-05-18 08:36:08

therion23 wrote:

If you have a Pi 2 1.0 or 1.1, the easiest way of making a bootable SD card for the Pi 4 is like this:

- Grab a Devuan image for Pi 2 (sorry, 32 bit only when doing this on a Pi 2). For some reason i could never boot the Ascii image on my Pi 2, but Jessie worked fine.
- Boot it on your Pi 2 and set up networking.
- From http://archive.raspberrypi.org/debian/p … -firmware/ get raspberrypi-bootloader and raspberrypi-kernel - make sure they have matching version numbers and not older than 20190620.
- From http://archive.raspberrypi.org/debian/p … e-nonfree/ get the latest firmware-brcm80211.
- install all three with dpkg.

If it boots right, you should be running 4.19.50-v7l+. Shutdown, put the card into your Pi 4 and boot it up.

does this procedure only work with the version with 1GB of memory? I have no success with the 2GB version, or should I also upgrade to boewulf or even ceres? I'll try out and report.

#10 Re: Installation » Devuan on Raspberry Pi 4 - now also aarch64 » 2020-01-11 17:49:05

pAul wrote:

I followed therion23's description, raspi 4 boots up, looks nice, thanks!
However, I cannot set up WLAN AP. I even played with newer kernels and newest firmware.

an upgrade of hostapd to version 2.6 did the job:
https://github.com/raspberrypi/firmware/issues/1117

#11 Re: Installation » Devuan on Raspberry Pi 4 - now also aarch64 » 2020-01-05 22:22:22

I followed therion23's description, raspi 4 boots up, looks nice, thanks!
However, I cannot set up WLAN AP. I even played with newer kernels and newest firmware.

Current configs:

# uname -a
Linux devuan 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux

# dmesg | grep brcmfmac
[    2.614772] brcmfmac: F1 signature read @0x18000000=0x15264345
[    2.622859] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    2.623389] usbcore: registered new interface driver brcmfmac
[    2.859070] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    2.873290] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[    3.018180] brcmfmac mmc1:0001:1 wlan1: renamed from wlan0
[   11.974904] brcmfmac: power management disabled
[   12.039577] brcmfmac: power management disabled

# iw list | grep AP
         * AP
         * #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{P2P-device } <= 1,

starting hostapd:

# hostapd -dd /etc/hostapd/hostapd.conf
...
nl80211: Teardown AP(wlan1) - device_ap_sme=1 use_monitor=0
nl80211 driver initialization failed.
hostapd_interface_deinit_free(0xc70cd8)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0xc70cd8)
wlan1: interface state UNINITIALIZED->DISABLED
hostapd_bss_deinit: deinit bss wlan1
wlan1: AP-DISABLED
hostapd_cleanup(hapd=0xc719a0 (wlan1))
hostapd_free_hapd_data: Interface wlan1 wasn't started
....

# iwconfig 
eth0      no wireless extensions.
lo        no wireless extensions.
br0       no wireless extensions.

wlan1     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

as well as

# cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
allow-hotplug eth0
iface eth0 inet manual

auto wlan1
allow-hotplug wlan1
iface wlan1 inet manual
wireless-power off

auto br0
iface br0 inet dhcp
bridge_ports eth0 wlan1
bridge_fd 0
bridge_stp off

and

# cat /etc/hostapd/hostapd.conf 
bridge=br0

interface=wlan1
driver=nl80211

ssid=XSXDX
channel=7
hw_mode=g
preamble=1
ieee80211n=1
ieee80211d=1
country_code=DE
wmm_enabled=1

auth_algs=3
wpa=2
wpa_key_mgmt=WPA-PSK
rsn_pairwise=CCMP
wpa_passphrase=XPXPX

Did I miss something or is it due to the 32bit version?

Board footer

Forum Software