Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Thu, Jan 27, 2022 at 04:38:37PM -0700, Gregory Nowak wrote: > Hi Joel, > redirecting back to the list. > > > On Thu, Jan 27, 2022 at 12:44:55PM -1000, Joel Roth wrote: > > Thank you for the response, Gregory. > > > > On Thu, Jan 27, 2022 at 03:33:01PM -0700, Gregory Nowak via Dng wrote: > > > On Thu, Jan 27, 2022 at 11:37:52AM -1000, Joel Roth via Dng wrote: > > > > It seems that my new router uses IPv6. Perhaps that means > > > > the ISP does so as well. > > > > > > Just because a router uses IPv6, doesn't necessarily mean the ISP > > > supports it. > > > > > > My problem is connecting via dhcp over ethernet. On IRC > > > > I was advised to try > > > > > > > > ping ff02::1%eth1 > > > > > Just to make sure, the interface connected to your router is in fact > > > eth1, and not eth0, right? > > > > Yes, it's eth1. > > > > > > which fails to get a response, indicating IPv6 is not enabled in my > > > > client. > > > > > > Posting the actual output might help. > > > > Usually ping (with no options) periodically returns a line > > with the time taken for the round trip. In this instance, > > one line beginning with PING and nothing more. > > > > > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > > > > then "ifup eth1". This fails with > > > > > > > > no link-local IPv6 address for eth1 > > > > > > Even if your interface isn't able to configure a global IPv6 address, > > > it should still get a link local address starting with fe80. > > > > This is the problem. I don't have a link local address: > > > > $ ifconfig eth1 > > eth1: flags=4099 mtu 1500 > > ether 28:d2:44:1a:e0:ca txqueuelen 1000 (Ethernet) > > RX packets 0 bytes 0 (0.0 B) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 0 bytes 0 (0.0 B) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > device interrupt 20 memory 0xf250-f252 > > You don't seem to have an IPv4 address, even for obtaining a dhcp > lease. Is this what you expect? If not, then the problem would seem to > be wider in scope than just IPv6. > > > > > > Also, before modifying /etc/network/interfaces, I would advise doing > > > ifdown eth1, modifying the file, and then ifup eth1. Instead of inet6 > > > dhcp, I would suggest: > > > > > > iface eth1 inet6 auto > > > > > > My understanding is this should use either dhcp6, or RA/NDP to > > > configure it. > > > > > What does the following output: > > > > > > cat /proc/sys/net/ipv6/conf/all/disable_ipv6 > > > cat /proc/sys/net/ipv6/conf/default/disable_ipv6 > > > cat /proc/sys/net/ipv6/conf/eth1/disable_ipv6 > > > > All zeroes. > > > > Do you have network-manager or the like installed which could be > trying to configure the interface on its own? > > Is there anything > different in the dmesg(1) output for eth1 than for your other > interfaces? bingo: [467072.085551] e1000e :00:19.0 eth1: PHY Wakeup cause - Unicast Packet [467072.902423] e1000e :00:19.0 eth1: Hardware Error [467081.10] e1000e :00:19.0 eth1: Hardware Error [467089.669913] e1000e :00:19.0 eth1: Hardware Error [467090.624833] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [467097.725663] e1000e :00:19.0 eth1: PHY Wakeup cause - Unicast Packet [467098.549348] e1000e :00:19.0 eth1: Hardware Error [467243.278267] e1000e :00:19.0 eth1: Hardware Error [467243.588770] e1000e: eth1 NIC Link is Down [467248.986061] e1000e :00:19.0 eth1: Hardware Error [467249.940380] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [467255.211266] e1000e :00:19.0 eth1: Could not acquire PHY [467255.211285] e1000e :00:19.0 eth1: PHY Wakeup cause - Unicast Packet [467255.918047] e1000e :00:19.0 eth1: Hardware Error This is a used Thinkpad pad, recently purchased. Fortunately usb-ethernet adapters are easily available. > Since ifconfig is depricated, what does: > > ip address show eth1 > > give you? 2: eth1: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 28:d2:44:1a:e0:ca brd ff:ff:ff:ff:ff:ff > What does: > > cat /proc/sys/net/ipv6/conf/eth1/autoconf 1 > output? > Other than that, that's all I can think of at the moment. Thanks, Greg, you've been very helpful. -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] software question
On Wed, Jan 26, 2022 at 08:29:01AM -0500, Ken Dibble wrote: > On 1/25/22 12:53 PM, Hendrik Boom wrote: > > On Tue, Jan 25, 2022 at 05:43:44AM -0600, o1bigtenor via Dng wrote: > > > On Tue, Jan 25, 2022 at 3:02 AM Olaf Meeuwissen via Dng > > > wrote: > > > > > > > > Hendrik Boom writes: > > > > > > > > > On Sun, Jan 23, 2022 at 07:29:27PM +0100, Florian Zieboll via Dng > > > > > wrote: > > > > > > On January 21, 2022 7:15:06 PM GMT+01:00, o1bigtenor via Dng > > > > > > wrote: > > > > > > > Greetings > > > > > > > > > > > > > > For a non-profit - - - this is not bulk email for sales - - - - > > > > > > > bulk > > > > > > > email for connection. > > > > > > > > > > > > > > Is there a linux program (foss hopefully) that will allow me to > > > > > > > do this? > > > > > > > > > > > > > > (Sending regualr emails to a group of people (from 15 to 50 > > > > > > > recipients).) > > > > > > With LibreOffice you can send personalized bulk mail. IIRC it was > > > > > > quite annoying to set up, but once done, it worked. > > > > > I just use /etc/aliases > > > > That was my first reaction too ;-) > > > OK - - - I'm not a programmer in any shape way or form. > > > My guess would be when using /etc/aliases - - - - that's some > > > form of bash programming? using awk or ? > > > > > > Please advise? (purdy (sic) please. > > It's a list ot aliases. > > > > mom : al...@homeowners.ca > > > > tells that mail for mom is to be sent to al...@homowners.ca > > > > anglers: j...@fish.ca, al...@poisson.ca > > > > tells it that mail for anglers is to be sent to j...@fish.ca and also to > > al...@poisson.ca > > > > And that's about all there is to it. entries in a line of destinations can > > refer to other alias lines, but there's a onstraint as to which has to come > > first. > > > > Try it out. Just edit an /etc/aliases into existence, and you'll likely > > find it works if your system handles its own email. > > > > -- hendrik > > > > > I just use the tools in the computering universe so far - - - have > > > barely begun anything any deeper. (Starting with hardware - - - > > > putting together stuff for control and now starting for sensors.) > > > > > > TIA > > > ___ > > > Dng mailing list > > > Dng@lists.dyne.org > > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > And, if you are like me and occasionally neglect to rtfm, > > don't forget to run newaliases every time you change /etc/aliases. > > Per man 8 newaliases. I have a reminder in a comment in /etc/aliases -- hendrik > > > Regards, > > Ken > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
Joel Roth via Dng said on Thu, 27 Jan 2022 11:37:52 -1000 >Hi veteran admins, > >It seems that my new router uses IPv6. Perhaps that means >the ISP does so as well. > >My problem is connecting via dhcp over ethernet. On IRC >I was advised to try > >ping ff02::1%eth1 > >which fails to get a response, indicating IPv6 is not enabled in my >client. > >I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, >then "ifup eth1". This fails with > >no link-local IPv6 address for eth1 > >References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" >will trigger the kernel to assign an IPv6 address. Since >this is not happening, I'm asking the wisdom of the list VUAs >how to enable IPv6 for this port. > >Thanks in advance, Hi Joel, Good to see you again! On my next router, (probably OpenBSD/pf), I'm going to block all IPV6. I enjoy that the badguys have to jump through one more hoop (NAT) to hit me where it hurts. I'm not an authority on firewalls and routers, but I'm going to try hard to pass only a very few IP addresses on my LAN, and put the Wifi on a third network card. In my opinion, IOT (the Internet Of Things) is for the most part an abomination. I don't want my thermostat on the same subnet as my LAN. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
Hi Joel, redirecting back to the list. On Thu, Jan 27, 2022 at 12:44:55PM -1000, Joel Roth wrote: > Thank you for the response, Gregory. > > On Thu, Jan 27, 2022 at 03:33:01PM -0700, Gregory Nowak via Dng wrote: > > On Thu, Jan 27, 2022 at 11:37:52AM -1000, Joel Roth via Dng wrote: > > > It seems that my new router uses IPv6. Perhaps that means > > > the ISP does so as well. > > > > Just because a router uses IPv6, doesn't necessarily mean the ISP > > supports it. > > > > My problem is connecting via dhcp over ethernet. On IRC > > > I was advised to try > > > > > > ping ff02::1%eth1 > > > Just to make sure, the interface connected to your router is in fact > > eth1, and not eth0, right? > > Yes, it's eth1. > > > > which fails to get a response, indicating IPv6 is not enabled in my > > > client. > > > > Posting the actual output might help. > > Usually ping (with no options) periodically returns a line > with the time taken for the round trip. In this instance, > one line beginning with PING and nothing more. > > > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > > > then "ifup eth1". This fails with > > > > > > no link-local IPv6 address for eth1 > > > > Even if your interface isn't able to configure a global IPv6 address, > > it should still get a link local address starting with fe80. > > This is the problem. I don't have a link local address: > > $ ifconfig eth1 > eth1: flags=4099 mtu 1500 > ether 28:d2:44:1a:e0:ca txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 20 memory 0xf250-f252 You don't seem to have an IPv4 address, even for obtaining a dhcp lease. Is this what you expect? If not, then the problem would seem to be wider in scope than just IPv6. > > > Also, before modifying /etc/network/interfaces, I would advise doing > > ifdown eth1, modifying the file, and then ifup eth1. Instead of inet6 > > dhcp, I would suggest: > > > > iface eth1 inet6 auto > > > > My understanding is this should use either dhcp6, or RA/NDP to > > configure it. > > > What does the following output: > > > > cat /proc/sys/net/ipv6/conf/all/disable_ipv6 > > cat /proc/sys/net/ipv6/conf/default/disable_ipv6 > > cat /proc/sys/net/ipv6/conf/eth1/disable_ipv6 > > All zeroes. > > > -- > Joel Roth > Do you have network-manager or the like installed which could be trying to configure the interface on its own? Is there anything different in the dmesg(1) output for eth1 than for your other interfaces? Since ifconfig is depricated, what does: ip address show eth1 give you? What does: cat /proc/sys/net/ipv6/conf/eth1/autoconf output? Other than that, that's all I can think of at the moment. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
On Thu, Jan 27, 2022 at 11:37:52AM -1000, Joel Roth via Dng wrote: > It seems that my new router uses IPv6. Perhaps that means > the ISP does so as well. Just because a router uses IPv6, doesn't necessarily mean the ISP supports it. > > My problem is connecting via dhcp over ethernet. On IRC > I was advised to try > > ping ff02::1%eth1 Just to make sure, the interface connected to your router is in fact eth1, and not eth0, right? > > which fails to get a response, indicating IPv6 is not enabled in my client. Posting the actual output might help. > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > then "ifup eth1". This fails with > > no link-local IPv6 address for eth1 Even if your interface isn't able to configure a global IPv6 address, it should still get a link local address starting with fe80. Also, before modifying /etc/network/interfaces, I would advise doing ifdown eth1, modifying the file, and then ifup eth1. Instead of inet6 dhcp, I would suggest: iface eth1 inet6 auto My understanding is this should use either dhcp6, or RA/NDP to configure it. What does the following output: cat /proc/sys/net/ipv6/conf/all/disable_ipv6 cat /proc/sys/net/ipv6/conf/default/disable_ipv6 cat /proc/sys/net/ipv6/conf/eth1/disable_ipv6 Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What is your take on finit?
On Wed, 26 Jan 2022 08:59:24 +0100 Martin Steigerwald wrote: > Hi! > > I saw this coming into Debian Sid, so should be available in Devuan > Ceres as well: > > https://troglobit.com/projects/finit/ > > Sounds interesting, I'd say. > > Best, Hi, what scares me is; originally reverse engineered from the EeePC fastinit by Claudio Matsuoka from: https://blog.darknedgy.net/technology/2015/09/05/0/ Asus eeePC fastinit + derivatives (2007-2015) As part of Asus’s eeePC notebook line around 2007-2008, which had variants preinstalled with a GNU/Linux distribution called Xandros, they wrote a proprietary init(8) replacement entitled fastinit specifically designed for the purpose of… booting really fast, I suppose. So it was proprietary and then reverse engineeredcouldn't this lead to licensing problems further down the road? Ciao, Tito ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
Oops, I missed a negative. I can add that I have **no** problem connecting to the router via wifi. ifconfig wlan2 shows both IPv4 and IPv6 addresses. Thank you for you attention! -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
On Thu, Jan 27, 2022 at 11:37:52AM -1000, Joel Roth via Dng wrote: > Hi veteran admins, > > It seems that my new router uses IPv6. Perhaps that means > the ISP does so as well. > > My problem is connecting via dhcp over ethernet. On IRC > I was advised to try > > ping ff02::1%eth1 > > which fails to get a response, indicating IPv6 is not enabled in my client. > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > then "ifup eth1". This fails with > > no link-local IPv6 address for eth1 > > References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" > will trigger the kernel to assign an IPv6 address. Since > this is not happening, I'm asking the wisdom of the list VUAs > how to enable IPv6 for this port. > > Thanks in advance, I can add that I have problem connecting to the router via wifi. ifconfig wlan2 shows both IPv4 and IPv6 addresses. grep CONFIG_IPV6 /boot/config-$(uname -r) shows that all the IPv6 drivers are compiled into the kernel. -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Configuring ethernet port for IPv6
Hi veteran admins, It seems that my new router uses IPv6. Perhaps that means the ISP does so as well. My problem is connecting via dhcp over ethernet. On IRC I was advised to try ping ff02::1%eth1 which fails to get a response, indicating IPv6 is not enabled in my client. I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, then "ifup eth1". This fails with no link-local IPv6 address for eth1 References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" will trigger the kernel to assign an IPv6 address. Since this is not happening, I'm asking the wisdom of the list VUAs how to enable IPv6 for this port. Thanks in advance, -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What is your take on finit?
Syeed Ali said on Thu, 27 Jan 2022 03:52:34 -0800 >On Wed, 26 Jan 2022 08:59:24 +0100 >Martin Steigerwald wrote: > >> I saw this coming into Debian Sid, so should be available in Devuan >> Ceres as well: >> >> https://troglobit.com/projects/finit/ > >I'm going to hazard the guess that this will be lined up in the same >way that Microsoft propped up Apple so they can point to a "competitor" >and say "see, we're not a monopoly!". What Syeed sounds reasonable. I read the docs at https://troglobit.com/projects/finit/ , and have some opinions technically... * It's better than systemd and sysvinit, which is faint praise. * It's better at mixing long-runs and do-once than runit (but not s6) * Each line of the config is kinda complicated, so you'd better have a cheat sheet when configuring. * It requires each daemon to background itself. Eww, gross! About self-backgrounding daemons... Requiring daemons to self-background is very bad because it makes daemon supervision very hard because they depend on a PID file which could get erased or overwritten or whatever. You can have much better control over a daemon the way runit, s6 and daemontools do it: run the daemon in the foreground. Ideally your init should have a choice between self-backgrounding daemons and the superior foreground daemons. Systemd has that choice, and runit, s6 and daemontools all have a kludge that usually can run backgrounded daemons. Please keep in mind that intelligently created daemons that background themselves have a command line option to run in the foreground --- only a tiny minority (cough, cough, httpd) have no option to prevent self-backgrounding. Ability to run foreground daemons is a huge asset when you make your own daemons. Any C, Python, Perl, Ruby, Lua, Java, PHP, C++, Pascal, bash, /bin/sh, or pretty much any other program that loops forever doing its job can be made into a daemon by an init that accepts foreground daemons. This is revolutionary, because it means the daemon author no longer needs to write the (non-trivial) self-backgrounding code. I have several home-made no-backgrounding daemons running, and those wouldn't be possible with finit. So Syeed, the cynical part of me thinks not only that you're right, but they picked a real dog of an init system to compete with systemd, because if they picked runit or s6, systemd would be out-competed. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Chimaera on Dell Wyse 3040 installs but won't boot
On 27-01-2022 11:06, Mike Tubby wrote: Can anyone provide help with this one? I have a Dell Wyse 3040 tiny PC intended for use a thin client running "ThinOS" (Ubuntu 16.04 and custom desktop/thin client). Others have reported success sunning desktop Linux distros "out of the box": https://roytanck.com/2020/05/13/running-linux-on-a-dell-wyse-3040-thin-client/ but I want to run Devuan 4.0 Server to run DNS and a few other light weight infrastructure things on little box on a home network. The Wyse 3040 is an Intel Atom quad core unit with 2Gb of DDR3, 16Gb of eMMC flash, Gigabit Ethernet, 2 x DisplayPort, 4 x USB and audio. I have set the BIOS back to defaults, booted from the server installation on a USB stick made with Rufus 3.17 and performed the installation, re-partitioned the eMMC flash, installed minimum components and the installation has run to the end successfully and for the "Now time to boot to your new installation". When rebooting the machine it drops to a "No bootable devices" error. Now these systems are EFI based and do not appear to have any legacy drive support in BIOS. I have run the installation a second time and paid more attention, when it installs Grub it doesn't pop a menu asking where I want the boot loader installed (MBR, first partition,) or providing a list of 'drives' or block devices to choose where to put the boot loader - instead something flashes past about grub and EFI and it completes, but after cycling the power the system isn't bootable. Is there something incomplete/configurable/different that has to be done on systems with eMMC/EFI to get them to boot? Mike IIRC there are two common problems. 1) On the EFI partition there is a hard link to Debian directory which should be Devuan or reverse 2) The BIOS is expecting a bootx32.efi whereas only a bootx64.efi has been installed You can check this with the tools from the link to GrubEFIReinstall from Tim Wallace mail. Grtz Nick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Chimaera on Dell Wyse 3040 installs but won't boot
If you boot from the refind rescue media by following the instructions here: https://wiki.debian.org/GrubEFIReinstall you can probably rescue your system. This has worked for me and others. I don't know why Devuan gets into this state! --Tim On Thursday, January 27, 2022, 05:57:00 AM EST, Florian Zieboll via Dng wrote: Am 27. Januar 2022 11:06:15 MEZ schrieb Mike Tubby : > I have run the installation a second time and paid more attention, when > it installs Grub it doesn't pop a menu asking where I want the boot > loader installed (MBR, first partition,) or providing a list of 'drives' > or block devices to choose where to put the boot loader - instead > something flashes past about grub and EFI and it completes, but after > cycling the power the system isn't bootable. On tty4 (I think) of the running installer, a detailed log is printed - press [alt]+[f4] to get there. If you can access the filesystem after the installation: The log should be saved under '/var/log/installer/'. -- [message sent otg] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What is your take on finit?
On Wed, 26 Jan 2022 08:59:24 +0100 Martin Steigerwald wrote: > I saw this coming into Debian Sid, so should be available in Devuan > Ceres as well: > > https://troglobit.com/projects/finit/ I'm going to hazard the guess that this will be lined up in the same way that Microsoft propped up Apple so they can point to a "competitor" and say "see, we're not a monopoly!". ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Chimaera on Dell Wyse 3040 installs but won't boot
Am 27. Januar 2022 11:06:15 MEZ schrieb Mike Tubby : > I have run the installation a second time and paid more attention, when > it installs Grub it doesn't pop a menu asking where I want the boot > loader installed (MBR, first partition,) or providing a list of 'drives' > or block devices to choose where to put the boot loader - instead > something flashes past about grub and EFI and it completes, but after > cycling the power the system isn't bootable. On tty4 (I think) of the running installer, a detailed log is printed - press [alt]+[f4] to get there. If you can access the filesystem after the installation: The log should be saved under '/var/log/installer/'. -- [message sent otg] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Chimaera on Dell Wyse 3040 installs but won't boot
Can anyone provide help with this one? I have a Dell Wyse 3040 tiny PC intended for use a thin client running "ThinOS" (Ubuntu 16.04 and custom desktop/thin client). Others have reported success sunning desktop Linux distros "out of the box": https://roytanck.com/2020/05/13/running-linux-on-a-dell-wyse-3040-thin-client/ but I want to run Devuan 4.0 Server to run DNS and a few other light weight infrastructure things on little box on a home network. The Wyse 3040 is an Intel Atom quad core unit with 2Gb of DDR3, 16Gb of eMMC flash, Gigabit Ethernet, 2 x DisplayPort, 4 x USB and audio. I have set the BIOS back to defaults, booted from the server installation on a USB stick made with Rufus 3.17 and performed the installation, re-partitioned the eMMC flash, installed minimum components and the installation has run to the end successfully and for the "Now time to boot to your new installation". When rebooting the machine it drops to a "No bootable devices" error. Now these systems are EFI based and do not appear to have any legacy drive support in BIOS. I have run the installation a second time and paid more attention, when it installs Grub it doesn't pop a menu asking where I want the boot loader installed (MBR, first partition,) or providing a list of 'drives' or block devices to choose where to put the boot loader - instead something flashes past about grub and EFI and it completes, but after cycling the power the system isn't bootable. Is there something incomplete/configurable/different that has to be done on systems with eMMC/EFI to get them to boot? Mike ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
