Re: [DNG] Devuan on RaspberryPi W Zero segfaults
Am Freitag, 26. Oktober 2018 schrieb Gregory Nowak: > On Fri, Oct 26, 2018 at 07:27:14PM +0200, Dr. Nikolaus Klepp wrote: > > Some additional information: > > - booting with devuan rpi1 image gives no serial console, but rpi boots (to > > an unknown state) > > - adding "enable_uart=1" in config.txt and booting does not work, rpi > > activity led goes dark after ~ 1 sec. > > - copying kernel+firmware+bootcode+kernelmoduels from raspbian to devuan > > and adding "enable_uart=1" works, kernel log is spit to uart. Userspace > > does not work, I cannot get a login console. > > > > Oh, I have no matching hdmi cable, so I don't know what happens on tty1. > > > > Any ideas? > > I only have a rpi2 and rpi3 here. Having said that, when the rpi3 came > out, raspbian made changes so that they could provide the same sd > image for all rpi models. That means that the serial console in > raspbian will always be on /dev/serial0, no matter which model of the > rpi is being used. What complicates things more is that if the serial > port is missing, systemd will happily ignore it, but agetty will keep > exiting, causing sysvinit to keep respawning it over, and over again. > > Devuan bug reports: > https://bugs.devuan.org/db/87/87.html > https://bugs.devuan.org/db/88/88.html > https://bugs.devuan.org/db/89/89.html > > I see that bug 89 was closed, even though 87 and 88 which are > prerequisites for bug 89 weren't closed. I've been meaning to look into > the status of this and other bugs, but lack of another sd card, and > time has so far prevented me from doing so. I've since gotten a second > sd card, but time is still very much lacking here for now. > > The bottom line for you is that since the rpi0 doesn't have a built in > bluetooth adapter, the serial port in devuan will be on > /dev/ttyAMA0. That means you need to specify that as the serial port > in cmdline.txt, and spin up agetty on that port in /etc/inittab. This is where things get complicated: - rpi0 has no BT nor WFi (this nice device is practically unavailable) - rpiw0 has BT and WiFi (this is what I can buy here) I cannot figure out which device is the correct serial to talk to, 'cause the devuan image - while it boots out of the box and generates ssh host keys - does not execute /etc/rc.local nor does it create any logfile, especially no /var/log/dmesg. My plan for today is this: modify package database so that all packages installed are "armel" instead of "armhf". Let's see how that will go ... Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan on RaspberryPi W Zero segfaults
On Fri, Oct 26, 2018 at 07:27:14PM +0200, Dr. Nikolaus Klepp wrote: > Some additional information: > - booting with devuan rpi1 image gives no serial console, but rpi boots (to > an unknown state) > - adding "enable_uart=1" in config.txt and booting does not work, rpi > activity led goes dark after ~ 1 sec. > - copying kernel+firmware+bootcode+kernelmoduels from raspbian to devuan and > adding "enable_uart=1" works, kernel log is spit to uart. Userspace does not > work, I cannot get a login console. > > Oh, I have no matching hdmi cable, so I don't know what happens on tty1. > > Any ideas? I only have a rpi2 and rpi3 here. Having said that, when the rpi3 came out, raspbian made changes so that they could provide the same sd image for all rpi models. That means that the serial console in raspbian will always be on /dev/serial0, no matter which model of the rpi is being used. What complicates things more is that if the serial port is missing, systemd will happily ignore it, but agetty will keep exiting, causing sysvinit to keep respawning it over, and over again. Devuan bug reports: https://bugs.devuan.org/db/87/87.html https://bugs.devuan.org/db/88/88.html https://bugs.devuan.org/db/89/89.html I see that bug 89 was closed, even though 87 and 88 which are prerequisites for bug 89 weren't closed. I've been meaning to look into the status of this and other bugs, but lack of another sd card, and time has so far prevented me from doing so. I've since gotten a second sd card, but time is still very much lacking here for now. The bottom line for you is that since the rpi0 doesn't have a built in bluetooth adapter, the serial port in devuan will be on /dev/ttyAMA0. That means you need to specify that as the serial port in cmdline.txt, and spin up agetty on that port in /etc/inittab. 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] Devuan on RaspberryPi W Zero segfaults
Am Freitag, 26. Oktober 2018 schrieb Dr. Nikolaus Klepp: > Am Freitag, 26. Oktober 2018 schrieb Arnt Karlsen: > > On Thu, 25 Oct 2018 23:55:36 +0200, Dr. wrote in message > > <201810252355.36418.dr.kl...@gmx.at>: > > > > > Hi all! > > > > > > I have a problem with Devuan on s new RPi W Zero: Raspbian (latest > > > image) boots fine, > > > > ..does our own > > https://mirror.leaseweb.com/devuan/devuan_ascii/embedded/devuan_ascii_2.0.0_armel_raspi1.img.xz > > work for you? > > It kind of works. The serial console is silent. Serial over USB with > "modules-load=dwc2,g_serial" does not work at all. WiFi misses firmware - so > does not work. I think there are suttle differences between "0/1" and "W0" > that are taken care of in raspbian but not in devuan. Most likely it's the > firmware and the kernel. I had simillar problems with RPi3+, it also needs > the latest firmware + kernel and des not work with the devuan rpi3 image. > > > > system updates work. Then I try to get rid of > > > systemd (replace raspbian sources with devuan sources). Installing > > > devuan-keyring works. Installing "sysv-rc" "sysvinit-core" and > > > "sysvinit-utils" throws several segfaults. "reboot" segfaults, too. > > > > ..the Raspian people calls their BCM2835 hardware arch armhf, while > > we and Debian calls it armel. Our armhf might work on RPi 2 and 3, > > but will fail on RPi 1 and Zero. > > Now this explains a lot - especially why the same procedure applied on RPi3+ > worked. > > > ..you will need to add the armel arch and replace all Raspian's armhf > > binaries with our armel binaries, and probably throw in some nefarious > > magic, to get in working your way. > > All magic didn't work. Burned my stock of black candles, did other > unspeakable thing, no use (The cat suvived! Would not touch the cat!). > Migration from armhf to armel would work like a charm, if there was not the > package manager that complains about not matching version numbers in > armhf/armel and consequently not configuring the package. I have found no way > to persuade that beast to ignore that pesky package suffix when the version > number matches :-( > > Now I try to transplant kernel+firmware from raspbian to devuan imag, let's > see how that turnes out. I would be happy if I git a serial console working > ... > > Nik > > > > > > > > ..devuan_ascii_2.0.0_armel_raspi1.img.* works fine on my RPi1, FWIW. > Don't doubt that. But RPiW0 has USB-OTG direct from the cpu, RPi1 has a usb > hub. That little difference turns out to be quite big. And the connectors > don't match ... *sigh* ... but I need that USB-OTG, that's the reason for > RPiW0 .. > Some additional information: - booting with devuan rpi1 image gives no serial console, but rpi boots (to an unknown state) - adding "enable_uart=1" in config.txt and booting does not work, rpi activity led goes dark after ~ 1 sec. - copying kernel+firmware+bootcode+kernelmoduels from raspbian to devuan and adding "enable_uart=1" works, kernel log is spit to uart. Userspace does not work, I cannot get a login console. Oh, I have no matching hdmi cable, so I don't know what happens on tty1. Any ideas? -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan on RaspberryPi W Zero segfaults
Am Freitag, 26. Oktober 2018 schrieb Arnt Karlsen: > On Thu, 25 Oct 2018 23:55:36 +0200, Dr. wrote in message > <201810252355.36418.dr.kl...@gmx.at>: > > > Hi all! > > > > I have a problem with Devuan on s new RPi W Zero: Raspbian (latest > > image) boots fine, > > ..does our own > https://mirror.leaseweb.com/devuan/devuan_ascii/embedded/devuan_ascii_2.0.0_armel_raspi1.img.xz > work for you? It kind of works. The serial console is silent. Serial over USB with "modules-load=dwc2,g_serial" does not work at all. WiFi misses firmware - so does not work. I think there are suttle differences between "0/1" and "W0" that are taken care of in raspbian but not in devuan. Most likely it's the firmware and the kernel. I had simillar problems with RPi3+, it also needs the latest firmware + kernel and des not work with the devuan rpi3 image. > > system updates work. Then I try to get rid of > > systemd (replace raspbian sources with devuan sources). Installing > > devuan-keyring works. Installing "sysv-rc" "sysvinit-core" and > > "sysvinit-utils" throws several segfaults. "reboot" segfaults, too. > > ..the Raspian people calls their BCM2835 hardware arch armhf, while > we and Debian calls it armel. Our armhf might work on RPi 2 and 3, > but will fail on RPi 1 and Zero. Now this explains a lot - especially why the same procedure applied on RPi3+ worked. > ..you will need to add the armel arch and replace all Raspian's armhf > binaries with our armel binaries, and probably throw in some nefarious > magic, to get in working your way. All magic didn't work. Burned my stock of black candles, did other unspeakable thing, no use (The cat suvived! Would not touch the cat!). Migration from armhf to armel would work like a charm, if there was not the package manager that complains about not matching version numbers in armhf/armel and consequently not configuring the package. I have found no way to persuade that beast to ignore that pesky package suffix when the version number matches :-( Now I try to transplant kernel+firmware from raspbian to devuan imag, let's see how that turnes out. I would be happy if I git a serial console working ... Nik > > > ..devuan_ascii_2.0.0_armel_raspi1.img.* works fine on my RPi1, FWIW. Don't doubt that. But RPiW0 has USB-OTG direct from the cpu, RPi1 has a usb hub. That little difference turns out to be quite big. And the connectors don't match ... *sigh* ... but I need that USB-OTG, that's the reason for RPiW0 .. Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan on RaspberryPi W Zero segfaults
On Thu, 25 Oct 2018 23:55:36 +0200, Dr. wrote in message <201810252355.36418.dr.kl...@gmx.at>: > Hi all! > > I have a problem with Devuan on s new RPi W Zero: Raspbian (latest > image) boots fine, ..does our own https://mirror.leaseweb.com/devuan/devuan_ascii/embedded/devuan_ascii_2.0.0_armel_raspi1.img.xz work for you? > system updates work. Then I try to get rid of > systemd (replace raspbian sources with devuan sources). Installing > devuan-keyring works. Installing "sysv-rc" "sysvinit-core" and > "sysvinit-utils" throws several segfaults. "reboot" segfaults, too. ..the Raspian people calls their BCM2835 hardware arch armhf, while we and Debian calls it armel. Our armhf might work on RPi 2 and 3, but will fail on RPi 1 and Zero. ..you will need to add the armel arch and replace all Raspian's armhf binaries with our armel binaries, and probably throw in some nefarious magic, to get in working your way. ..devuan_ascii_2.0.0_armel_raspi1.img.* works fine on my RPi1, FWIW. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Devuan on RaspberryPi W Zero segfaults
Hi all! I have a problem with Devuan on s new RPi W Zero: Raspbian (latest image) boots fine, system updates work. Then I try to get rid of systemd (replace raspbian sources with devuan sources). Installing devuan-keyring works. Installing "sysv-rc" "sysvinit-core" and "sysvinit-utils" throws several segfaults. "reboot" segfaults, too. After a forced reset "/sbin/init" segfaults when the kernel tries to execute it: [3.225592] devtmpfs: mounted [3.232735] Freeing unused kernel memory: 440K [3.239072] This architecture does not have kernel memory protection. [3.497781] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [3.497781] [3.512460] CPU: 0 PID: 1 Comm: init Not tainted 4.14.78+ #1156 [3.520308] Hardware name: BCM2835 [3.525637] [] (unwind_backtrace) from [] (show_stack+0x20/0x24) [3.537152] [] (show_stack) from [] (dump_stack+0x20/0x28) [3.546416] [] (dump_stack) from [] (panic+0xcc/0x250) [3.555304] [] (panic) from [] (do_exit+0xa30/0xa68) [3.564042] [] (do_exit) from [] (do_group_exit+0x4c/0xbc) [3.573300] [] (do_group_exit) from [] (get_signal+0x230/0x5dc) [3.584791] [] (get_signal) from [] (do_signal+0xc8/0x3f8) [3.594106] [] (do_signal) from [] (do_work_pending+0xcc/0xe4) [3.605584] [] (do_work_pending) from [] (slow_work_pending+0xc/0x20) [3.617712] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b I made the system bootable again (add init=/bin/systemd ... brrr) and tried a dist-upgrade. That failed when uncompressing "bash" segfaults. Anything I can do about that? -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
