The officially official Devuan Forum!

You are not logged in.

#1 Re: Other Issues » [SOLVED] How to Install the latest version of Python ? » 2023-04-15 02:51:57

SpongeBOB wrote:

I've found this --> … on--source

is this ok for Devuan too ?

That page looks okay, but it is for python 3.11.1, not 3.11.3.  The 3.11.3 source can be downloaded here … 3.11.3.tgz.  The build/install process should work the same in devuan as in debian.
If you want a slightly smaller download, the xz-compressed source can be downloaded here … 1.3.tar.xz.

Here, just change the first section of that blog page to this:

cd /tmp/
tar -xvf Python-3.11.3.tar.xz
cd Python-3.11.3/

I believe all the rest should be the same.

#2 Re: Other Issues » Where do I report bugs in devuan-backports packages? » 2023-03-28 23:10:03

steve_v wrote:

Apparently, Devuan derives from Debian and Veteran Unix Administrators... I took this to mean that the distro would cater to administrators (who, ya know, administer things, like production servers), and inherit the stability and reliabilty of Debian... Rather than turn into another hobby distro for anti-conformist tinkerers with old laptops.
I appear to be mistaken, if the apparent focus on desktop customisation and the attitude I see from many people here have any bearing on things.

As for my bug-tracking skills... That's kinda my point. If my relatively meagre expertise and attention are all that stands between Devuan and undetected broken packages in the repos, we have problems. How am I the only one to have noticed this, in rsyslog of all things?

I use devuan (mainly chimaera) on a few servers, and never noticed this bug.  If it had affected me, I hope that I would have noticed pretty quickly... My completely uninformed guess is that not many people use backports of rsyslog, as it seems none of the other versions were affected.  What does the backports version of rsyslog do that I'm missing?

#3 Re: Hardware & System Configuration » Web server - a setting off somewhere ... » 2023-01-26 03:50:01

A few questions, to help figure out where the problem lies...
The local-network address of the webserver is ?
If so, can another computer on the network successfully open the site  It does appear that your web-server is listening for connections, but if this step isn't working then you may have a firewall that is blocking the connection.  So... do you have a software firewall (such as ufw) installed?  You may need to configure it to allow incoming traffic on ports 80 and 443.
Also, are you behind a NAT/router?  If so, you'll probably need to set up port forwarding for TCP ports 80 and 443, if you haven't done so already.  This would make your webserver accessible to the outside internet (  The process to do this varies, but it should be found somewhere on your router's admin page.

#4 Re: Hardware & System Configuration » [SOLVED] postfix dynamic ipv6 interfaces » 2023-01-13 17:58:37

I'm still not understanding something here.
Do you have two NICs (eth0 and eth1)?
If eth1 = LAN as posted earlier, then set up a static IPv6 network there. use one of the "Private internets" ranges (64:ff9b:1::/48 for example).  eth0 will receive whatever address is assigned when connecting to ISP.  In your postfix conf, use the static address that you've chosen for eth1.
(Note, I don't actually use IPv6, maybe someone with experience with this can chime in.)

You can do the same thing even if you only have one physical device, with a virtual interface (for example, ifconfig eth0:1 64:ff9b:1::1).  I do this with IPv4 addresses and postfix.

AFAIK, there's currently no other way to configure postfix for dynamic IP addresses, except for inet_interfaces = all.  I could be wrong there, but from skimming through I'm not seeing it.

#5 Re: Hardware & System Configuration » [SOLVED] postfix dynamic ipv6 interfaces » 2023-01-13 01:46:20

bai4Iej2need wrote:

Postfix shall listen on eth1,(LAN) but not on eth0 (World).

bai4Iej2need wrote:

with ipv6 I do not have fixed ip numbers, because these will change dynamically
The ipv6 numbers will change dynamically , what ever I receive from my ISP .

These statements appear to be contrary to each other.  Do you want postfix for local network only, or for world (internet)?  If you only need it for LAN, then it does not matter what your ISP assigns; just set up a static local address to use on eth1.
If you actually do want it to be reachable from outside your network (internet), then is there any reason not to use inet_interfaces = all?

#6 Re: Hardware & System Configuration » [SOLVED] SSL Report - What to Fix & Ignore » 2023-01-05 14:36:13

dcolburn wrote:

I'm guessing I need to figure out why DNS CAA isn't being reported ... DNS CAA     No (more info)

This is set by your domain registrar.  Log into the site that you registered the domain name, and add a CAA record using the issuer of your certificate. may have more information.  One of my CAA records looks like this: 1799 IN CAA 0 issue ""

Unfortunately, I don't know what to make of those handshake failures.  That seems unrelated to caa.

#7 Re: Hardware & System Configuration » [SOLVED] memory problem » 2022-12-19 01:38:47

fanderal wrote:

Procps was updated on Dec 6:
[UPGRADE] procps:amd64 2:3.3.17-7.1devuan1 -> 2:4.0.2-1devuan1

Maybe this is the cause of the discrepancy?  apt-listchanges news:

procps (2:4.0.2-1) unstable; urgency=medium

  * free: Used memory is Total - Available
    This means versions of free after 4.0.0 will show different Used
    values for older frees and some other system utilities.

 -- Craig Small Mon, 05 Dec 2022 21:34:57 +1100

#8 Re: ARM Builds » kernel-related question » 2022-11-26 02:10:27

OK, here's where I'm at now.

First, I edited /boot/config.txt and attempted to change the kernel line to the version that I had installed via apt as follows: kernel=vmlinuz-5.10.0-19-arm64
The "file" command reported both files (the previous kernel8.img and the vmlinuz-5.10.0-19-arm64) as "Linux kernel ARM64 boot executable Image, little-endian, 4K pages" -- so I thought it just might work.
When I rebooted, the system was stuck at the initial color "rainbow" screen.

I resized my boot partition (it was 128MB on the ascii image, but 256MB on the chimaera image).  I downloaded the file from the page  ... then using dd I overwrote my boot partition with the one from that image.  At first it would not complete the boot due to missing partition (I forgot to edit cmdline.txt).  After I got that straightened out, it did boot into Linux devuan 5.10.110 #1 SMP PREEMPT Fri Nov 25 00:43:14 CET 2022 aarch64 GNU/Linux

So I guess that part is solved, sort of.  I was hoping there would be a simpler way to just upgrade the kernel (like it works in amd64).

Also, upgrading the kernel didn't even fix the iptables problem.

# iptables -A INPUT -s -j DROP
iptables/1.8.7 Failed to initialize nft: Protocol not supported
# iptables -V
iptables/1.8.7 Failed to initialize nft: Protocol not supported

I think I've got the solution for this, though.
I found on

update-alternatives --set iptables /usr/sbin/iptables-legacy
update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy

I had to copy the /lib/modules/5.10.110 from the latest image file to my live system, too (which of course I forgot to do previously).

Now, iptables seems to be functioning correctly.

The only question remaining is, whether or not there's a simpler kernel upgrade process.  At least things are working again, and it is possible to upgrade kernel, just a bit more time-consuming than I'm used to :-)

#9 ARM Builds » kernel-related question » 2022-11-25 19:16:14

Replies: 4

I've been reading a few topics on this forum, but haven't yet come across a satisfactory answer.

Here's my situation:
I've got a raspberry pi 3b+.  I originally used the devuan ascii image on sd card, later moved to external usb drive.  After running this setup for a few years, I finally (today) decided to dist-upgrade to beowulf, and then to chimaera.  It all went pretty smoothly.  The one issue that I've noticed during startup now is that iptables refuses to load the rules I have stored in a script.  An example rule is: iptables -A INPUT -s -j DROP and the message that was returned on beowulf is: iptables: Invalid argument. Run `dmesg' for more information.dmesg contains nothing useful or related to the iptables command.  On chimaera the error is: iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument.

From some internet searching, I believe that the problem is due to an outdated kernel.  uname -a result is: Linux devuan 4.16.14-v8+ #1 SMP PREEMPT Tue Jun 5 18:50:10 CEST 2018 aarch64 GNU/Linux.

I then tried: apt install linux-image-arm64 which proceeded to download and install linux-image-5.10.0-19-arm64_5.10.149-2_arm64.deb
This did create the files in /boot, but they were not loaded upon a system reboot, it's still on 4.16.14-v8+.

I *believe* (but may be mistaken) that the newer rpi images contain a newer kernel.  Could I download the chimaera image, and copy the contents of its /boot to my /boot in order to load a newer kernel?  Or is there another way to perform a kernel upgrade on a running system?  Any help is greatly appreciated.

#10 Re: DIY » Linux ports of OpenBSD's ksh » 2022-09-16 22:46:08

FYI, after adding repository, apt install loksh says...

Preparing to unpack .../archives/loksh_7.1-1_amd64.deb ...
Unpacking loksh (7.1-1) ...
Setting up loksh (7.1-1) ...
update-alternatives: error: alternative path /bin/loksh doesn't exist
dpkg: error processing package loksh (--configure):
 installed loksh package post-installation script subprocess returned error exit status 2

loksh is located in /usr/bin, not in /bin
This occurred in devuan chimaera

#11 Re: Other Issues » [SOLVED] Couple questions regarding Chimaera » 2022-09-06 01:31:02

Installing inetutils-ping (which removed iputils-ping) did remove that warning, so that part is solved.  Thanks :-)

The change with tpm2-abrmd (adding the '-u tss' to line 17 of /etc/init.d/tpm2-abrmd) didn't help.

# service tpm2-abrmd start
Starting TPM2 Access Broker and Resource Management Daemon: tpm2-abrmdIllegal option -u
/sbin/start-stop-daemon: unable to stat //tss (No such file or directory)

I *do* have a user "tss" listed in /etc/passwd.  I guess I'm wondering, do I need this service?
After a little bit of internet searching, I think I may not even have tpm enabled on my motherboard.  Maybe that's part of the problem.  I'll reboot and check the ol' bios.

OK, under the "Trusted Computing" section of bios setup, my motherboard informed me that no device was found.  Guess it's not built-in and I never added it.  So I'll remove the tpm2-abrmd package, not sure why it got pulled in.  Sorry for the noise

#12 Other Issues » [SOLVED] Couple questions regarding Chimaera » 2022-09-05 17:53:03

Replies: 3

This weekend I dist-upgraded from Beowulf to Chimaera.
The upgrade itself went well, with one package problem I am stuck at (I've uninstalled for now)
The package that fails is: "tpm2-abrmd" :

Setting up tpm2-abrmd (2.3.3-1+b2) ...
Starting TPM2 Access Broker and Resource Management Daemon: tpm2-abrmd
** (process:6742): WARNING **: 13:44:06.774: tcti_conf before: "device:/dev/tpm0"

** (tpm2-abrmd:6742): WARNING **: 13:44:06.774: tcti_conf after: "device:/dev/tpm0"
Refusing to run as root. Pass --allow-root if you know what you are doing.
invoke-rc.d: initscript tpm2-abrmd, action "start" failed.
dpkg: error processing package tpm2-abrmd (--configure):
 installed tpm2-abrmd package post-installation script subprocess returned error exit status 1

I'm not going to "--allow-root", since I obviously don't know what I'm doing here.  I've uninstalled the package (not sure what it is, or why I had it to begin with).  Is this anything important?  I could note, this is on my desktop computer, not an internet server, if that makes any difference.

The second question has to do with ping. 

$ ping -c 1
ping: socket: Address family not supported by protocol
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=64 time=0.025 ms

Any fix for this warning?  I keep getting the warning (Address family not supported by protocol), but the ping itself does succeed.  Passing the "-4" switch will take the warning away; I might just make an alias to do that if there's not another workaround.  Possibly related:

#13 Re: Installation » mariadb on ceres » 2022-08-25 00:01:36

These log entries look very similar to an issue I had at the beginning of the year.

mknoop wrote:

Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24  2:19:07 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1651026,1651026
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24  2:19:07 0 [ERROR] InnoDB: Missing FILE_CHECKPOINT at 1651026 between the checkpoint 1651026 and the end 1651038.
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24  2:19:07 0 [ERROR] Plugin 'InnoDB' init function returned error.
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24  2:19:07 0 [ERROR] Unknown/unsupported storage engine: InnoDB

What fixed it for me was removing (actually, renaming, in case it was needed later; it wasn't) the file /var/lib/mysql/ib_logfile0

cd /var/lib/mysql
mv ib_logfile0 ib_logfile0.bad-renamed
service mariadb start

#14 Re: Installation » [SOLVED] Pi-Hole and Devuan Chimaera » 2022-08-20 23:33:57

Altoid wrote:
[root@devuan ~]# ss -tnlp | grep 4711
[root@devuan ~]# 


Phooey.  I was hoping another process (the old pihole?) was holding on to that port.  You can't connect, because the service is not running.  The service won't start (or rather, won't stay running) because of... something yet unknown.
Earlier you had posted this from your log:

[2022-08-19 18:05:28.696 1140M] Error opening IPv6 telnet socket: Address family not supported by protocol (97)

Would you mind trying this, add this line into the file /etc/pihole/setupVars.conf


Then run

# service pihole-FTL start

If it doesn't start properly, check /var/log/pihole/FTL.log for other clues.

Also, in the web interface, there is a section "Pi-hole diagnosis" under the "Tools" menu.  I'm not sure whether or not that is useful.

If all else fails, nuke it (including configs) and re-install.  Sometimes that is quicker (but less satisfying) than finding the actual problem.

#15 Re: Installation » [SOLVED] Pi-Hole and Devuan Chimaera » 2022-08-20 02:33:14

Altoid wrote:
root@chimaera:~# service lighttpd status
lighttpd is running.

can you open the pihole web admin page? ( try ... or whatever the machine's ip address is)

Altoid wrote:
root@chimaera:~# cat /etc/pihole/setupVars.conf

Basically the same as mine, except for PIHOLE_DNS_1=
This might be valid, I'm not sure, but it's not how mine is set up at all.  My pihole goes out to other DNS servers for its non-piholed queries.  I also don't see IPV4_ADDRESS or IPV6_ADDRESS in your configuration.  Mine is:

Altoid wrote:
[2022-08-19 18:05:28.675 1140M] Listening on port 4711 for incoming IPv4 telnet connections
[2022-08-19 18:05:28.696 1140M] Error opening IPv6 telnet socket: Address family not supported by protocol (97)

As you can see, port 4711  is mentioned.

If fsockopen gets refused trying to connect to, then there is a permissions problem with port 4711.

How do I troubleshoot that, specifically?

what happens when you run these:

root@devuan:/etc/pihole# ss -tnlp | grep 4711
LISTEN     0      5                     *:*                   users:(("pihole-FTL",pid=2819,fd=10))
LISTEN     0      5          ::1:4711                    :::*                   users:(("pihole-FTL",pid=2819,fd=13))
root@devuan:/etc/pihole# telnet 4711
Connected to
Escape character is '^]'.
telnet> quit
Connection closed.

#16 Re: Installation » [SOLVED] Pi-Hole and Devuan Chimaera » 2022-08-19 22:24:11

Altoid wrote:
root@chimaera:~#  service pihole-FTL status
[    ] pihole-FTL is not running

What is the output of:

service lighttpd status

FYI, my (very-old) FTL.php contains this:

function connectFTL($address, $port=4711)
	if($address == "")
		// Read port
		$portfile = file_get_contents("/var/run/pihole-FTL.port");
			$port = intval($portfile);

	// Open Internet socket connection
	$socket = @fsockopen($address, $port, $errno, $errstr, 1.0);

	return $socket;

The next place to look would be /etc/pihole/setupVars.conf... check if anything looks off in there.

Oh, and don't forget the log files: /var/log/pihole/FTL.log and /var/log/pihole/pihole.log

#17 Re: Installation » 32 bit browser for Devuan 5.10 » 2022-08-18 13:34:57

andyprough wrote:

The Pale Moon project does not currently create 32-bit binaries themselves, but they recommend the 32-bit builds by Steve Pusser. Links to his repos and deb packages for GTK2 and GTK3 versions are at the top of Pale Moon's 3rd party builds page here:

Thanks for this, I knew about Steve's repository, but wasn't aware that 32-bit was included there (I rarely use my 32-bit machine).

#18 Re: Installation » 32 bit browser for Devuan 5.10 » 2022-08-18 13:28:34

This is strange:

$ aptitude versions firefox-esr
Package firefox-esr:                              
p   78.14.0esr-1~deb10u1             oldstable     500 
i   91.12.0esr-1~deb10u1             oldstable-sec 500 

Package firefox-esr:i386:
p   78.14.0esr-1~deb10u1             oldstable     500 
p   78.15.0esr-1~deb10u1             oldstable-sec 500 

It appears firefox-esr:i386 is indeed at 78.15.0 with beowulf (above).  However, using ascii sources gives this:

$ aptitude versions firefox-esr
Package firefox-esr:                              
p   68.10.0esr-1~deb9u1              oldoldstable  500 
p   91.11.0esr-1~deb9u1              oldoldstable- 500 
i   91.12.0esr-1~deb10u1                           100 

Package firefox-esr:i386:
p   68.10.0esr-1~deb9u1              oldoldstable  500 
p   91.11.0esr-1~deb9u1              oldoldstable- 500 

I suppose you could (temporarily) change sources to ascii, apt-update, install firefox-esr (91.11.0), then restore sources to beowulf ...

#19 Re: Installation » 32 bit browser for Devuan 5.10 » 2022-08-18 04:29:55

I don't have the *exact* same setup as you (32-bit on beowulf)... I do have amd64 running beowulf, and i686 running chimaera.  Both of them show firefox at 91.12.0esr.  my arm64 running ascii shows firefox at 91.11.0esr.  Have you run apt update recently?  Do you have anything in /etc/apt/preferences.d/ that would prevent firefox upgrade (apt pinning)?

#20 Re: Hardware & System Configuration » Upgraded to chimaera; now cannot boot » 2022-03-18 20:40:54

Apologies for the late response.  It was, apparently, a hardware problem after all, although I'm not sure exactly what.  Something with the CPU or motherboard (I didn't have a spare of either that I could interchange and narrow down the problem).

#21 Re: Installation » apparmor foisted on, by default? » 2022-03-18 20:34:27

An alternate option for this particular case (apparmor) would be to create a file, e.g. /etc/apt/preferences.d/noapparmor

Package: apparmor*
Pin: release n=beowulf
Pin-Priority: -1

Change the release name if you're not using beowulf.

#22 Hardware & System Configuration » Upgraded to chimaera; now cannot boot » 2021-12-23 20:02:45

Replies: 5

I have 1 desktop that won't properly boot chimaera.  This is a machine I used once a week.
It ran beowulf fine (I may just go back to that).
I updated the apt sources to chimaera, did the upgrade and dist-upgrade successfully.  Rebooted into chimaera okay.
Some time later (the next week?) it wouldn't complete the boot -- it would go so far and then reboot itself (stuck in a reboot-loop).
I was able to boot into an older kernel, and it started up okay.
The following week, same problem.  Only the older kernel wouldn't complete its boot either.  I went to recovery mode, and was able to log in, exited and GUI started up fine.
The following week, nothing I did was successful.  Even "recovery mode" does not complete far enough to get me to login -- it reboots and reboots and reboots!  I let it continue this for over a half hour before shutting it down.

I've replaced this desktop with another one, so a fix is not something that is urgent or even necessary.  I have noticed, in attempts to get it working, that it will successfully boot jessie desktop-live USB; but will not even boot up from chimaera desktop-live USB (it does the reboot thing).
Perhaps there is some incompatible hardware ... but if that's the case I am confused why it initially worked after the dist-upgrade.  Should I just go back to beowulf?
I don't even know where to start looking for the cause ... syslog ?  kern.log ?  record a video of the boot to get the last message before it reboots ?
The chimaera desktop-live USB does work on other hardware so I don't think that it is a problem, either.

An old inxi output (showing the correct hardware at least; other info may be outdated)

  Host: fcc-audio Kernel: 5.8.0-0.bpo.2-amd64 x86_64 bits: 64 compiler: N/A 
  Desktop: Xfce 4.12.4 tk: Gtk 2.24.32 info: xfce4-panel wm: xfwm4 
  dm: SLiM 1.3.6 Distro: Devuan GNU/Linux 3 (beowulf) 
  Type: Desktop Mobo: MSI model: FM2-A55M-E33 (MS-7721) v: 2.0 serial: N/A 
  BIOS: American Megatrends v: 11.6 date: 02/12/2015 
  Topology: Quad Core model: AMD A10-6800K APU with Radeon HD Graphics 
  bits: 64 type: MCP arch: Piledriver rev: 1 L1 cache: 192 KiB 
  L2 cache: 2048 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 32736 
  Speed: 1993 MHz min/max: 2000/4100 MHz boost: enabled Core speeds (MHz): 
  1: 1996 2: 1996 3: 2092 4: 2044 
  Device-1: AMD Richland [Radeon HD 8670D] vendor: Micro-Star MSI 
  driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:990c 
  Display: server: X.Org 1.20.4 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1024x768~60Hz 
  OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.8.0-0.bpo.2-amd64 LLVM 7.0.1) 
  v: 4.3 Mesa 18.3.6 compat-v: 3.1 direct render: Yes 
  Device-1: AMD Trinity HDMI Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 00:01.1 chip ID: 1002:9902 
  Device-2: AMD FCH Azalia vendor: Micro-Star MSI driver: snd_hda_intel 
  v: kernel bus ID: 00:14.2 chip ID: 1022:780d 
  Sound Server: ALSA v: k5.8.0-0.bpo.2-amd64 
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Micro-Star MSI driver: r8169 v: kernel port: e000 bus ID: 01:00.0 
  chip ID: 10ec:8168 
  IF: eth0 state: down mac: xx:xx:xx:xx:xx:xx 
  Local Storage: total: 88.98 GiB used: 22.56 GiB (25.4%) 
  ID-1: /dev/sda vendor: Western Digital model: WD800JD-60LSA5 
  size: 74.53 GiB speed: 3.0 Gb/s serial: WD-XXXXXXXXXXXX rev: 1E03 
  temp: 35 C scheme: MBR 
  ID-2: /dev/sdf type: USB vendor: Toshiba model: TransMemory 
  size: 14.45 GiB serial: XXXXXXXXXXXXXXXXXXXXXXXX rev: 1.00 scheme: MBR 
  ID-1: / size: 21.88 GiB used: 8.81 GiB (40.3%) fs: ext4 dev: /dev/sda2 
  ID-2: /boot size: 938.0 MiB used: 177.7 MiB (18.9%) fs: ext2 
  dev: /dev/sda1 
  ID-3: /home size: 41.92 GiB used: 6.25 GiB (14.9%) fs: ext4 dev: /dev/sda3 
  ID-4: swap-1 size: 8.41 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda4 
  System Temperatures: cpu: 10.8 C mobo: N/A gpu: radeon temp: 0 C 
  Fan Speeds (RPM): N/A 
  Processes: 162 Uptime: 1h 48m Memory: 7.06 GiB used: 725.2 MiB (10.0%) 
  Init: SysVinit v: 2.93 runlevel: 2 default: 2 Compilers: gcc: 8.3.0 
  alt: 6/8 Shell: bash (sudo) v: 5.0.3 running in: xfce4-terminal 
  inxi: 3.0.32 

#23 Re: Installation » [SOLVED] Installing amd64 devuan beowulf 3.1 on an old imac ... » 2021-05-04 17:41:10

Adding to this thread, in case someone finds this useful, or needs the info at some later point.  To get the wifi (b43) working on this imac, I followed the steps at … ivers/b43/ under "Other distributions" to build the driver manually.
In case that page goes down, basically it came down to this:

tar xjf b43-fwcutter-018.tar.bz2
cd b43-fwcutter-018
sudo make install
cd ..
tar xjf broadcom-wl-5.100.138.tar.bz2
sudo b43-fwcutter -w /lib/firmware broadcom-wl-5.100.138/linux/wl_apsta.o

a reboot or modprobe b43 should get the device driver loaded, and wifi available.  I also had to set the wireless interface to "wlan0" in wicd preferences., but this might be done automatically if you reboot rather than use the modprobe command.

#24 Re: Installation » [SOLVED] Installing amd64 devuan beowulf 3.1 on an old imac ... » 2021-05-03 01:38:49

It actually *did* boot the amd64 live desktop dvd.  :-)   Installation went pretty smoothly from there.

This machine doesn't look like the one pictured on your link, snork.  The EFI situation could be similar though, I don't really know.  It does seem to be from the same era, though.  This is an all-in-one thing (basically the hardware is all mounted behind/under the screen.  no tower, more difficult to replace individual parts).

inxi reports this as:

System:    Host: imac Kernel: 4.19.0-14-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Xfce 4.12.4 tk: Gtk 2.24.32 
           info: xfce4-panel wm: xfwm4 dm: SLiM 1.3.6 Distro: Devuan GNU/Linux 3 (beowulf)
Machine:   Type: Desktop System: Apple product: iMac6,1 v: 1.0 serial: <> Chassis: type: 13 v: Mac-F4218FC8 
           serial: <> 
           Mobo: Apple model: Mac-F4218FC8 v: DVT serial: <> UEFI: Apple v: IM61.88Z.0093.B07.0706281250 
           date: 06/28/07 
CPU:       Topology: Dual Core model: Intel Core2 T7400 bits: 64 type: MCP arch: Core Merom rev: 6 L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 8645 
           Speed: 1589 MHz min/max: 1000/2167 MHz Core speeds (MHz): 1: 1101 2: 1049

#25 Re: Installation » [SOLVED] Installing amd64 devuan beowulf 3.1 on an old imac ... » 2021-05-02 23:39:01

Thank you both for the replies.

Unfortunately, I am not able to boot the amd64 debian buster netinstall cd, either.  The prompt that comes up trying to boot any amd64 disc (so far) is:
Select CD-ROM Boot Type :
(and all keyboard input is ignored at this point)

Also, thanks for the hint on using the desktop *live* installer disc.  I'll try that next, I think I should be able to get that to work.  Even if I can't boot it directly, I should be able to mount it and run the installer from it.

Board footer

Forum Software