Show all posts by user
Discuss all things Debian on your device
Page 1 of 2 Pages: 12
Results 1 — 30 of 31
Re: System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down - 2 days ago
I've been unable to pin this down either. First I thought it was related to swap, then Netatalk. It does seem to be random. SSH works fine at first but stops within a few hours and seems to take out the ethernet availability. I don't understand why I would now have to do these special things just to get ethernet to work as that's never been the case before.by bluzfanmr1 - Debian
Re: System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down - 9 days ago
bodhi Wrote: ------------------------------------------------------- > bluzfanmr1. > > I think because you are running systemd, it is > harder to get evrything going. My basic rootfs is > running sysvinit. > > However, I can see that the network is not > running. You don't have Ethernet. > > > PogoplugPro2 login: > > Log in through seriby bluzfanmr1 - Debian
Re: System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down - 9 days ago
bodhi Wrote: ------------------------------------------------------- > bluzfanmr1. > > I think because you are running systemd, it is > harder to get evrything going. My basic rootfs is > running sysvinit. > I am using your rootfs and did not change this. Do you know how this would happen?by bluzfanmr1 - Debian
Re: New Computer Parts - 9 days ago
For me, it's Newegg (90% of the time), Monoprice, Microcenter and Best Buy, in that order. Only once have had an issue and that was with a Monoprice product. They immediately shipped a replacement and told me to keep the original product.by bluzfanmr1 - Off-Topic
Re: System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down - 9 days ago
Asure Wrote: ------------------------------------------------------- > > System has not been booted with systemd as init > system (PID 1). Can't operate. Failed to connect > to bus > > > I've just walked this route, it's the other way > around. He is using sysv. > > You get this message when you try to use systemctl > tool to start thiby bluzfanmr1 - Debian
Re: System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down - 9 days ago
I got pulled away from things but am about to work on this. I will post my findings shortly. Thank you!by bluzfanmr1 - Debian
Re: System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down - 10 days ago
Forgot I could do that! Here's what's showing. The really weird thing is everything is normal via serial and I can log in just fine, but I cannot log in via SSH from my Macbook any more. I mentioned the swap file earlier but I don't think that's it. I removed the swap file via serial but still cannot SSH. Just to note, I could login via SSH from my Macbook Air all aloby bluzfanmr1 - Debian
System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down - 10 days ago
QuoteSystem has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down I have a few Pogoplug Pro's and I keep having this same issue as stated above. It seemed to start when things went from 4.xx to 5.xx and hopefully someone smarter than I can help with a solution. After I get that message I can no longer ssh to the Pogoplug. Iby bluzfanmr1 - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 7 months ago
bodhi Wrote: ------------------------------------------------------- > bluzfanmr1, > > Let's wait for the next kernel release. And then > we go from there. Will do, thanks again.by bluzfanmr1 - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 7 months ago
I guess that wasn't the issue. It's still hanging on timeout waiting for carrier. Do you have any other ideas? If not, I'll wait to try the next version or I'll blow everything away and start from scratch, though I'm trying to avoid that due to everything I have set up on it. Thanks for all you help!by bluzfanmr1 - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 7 months ago
bodhi Wrote: ------------------------------------------------------- > So perhaps boot back to 4.14.x and remove > netconsole from /etc/initram-tools/modules, too. > And then reinstall 5.4.179. I'll bet that was it as it has to be something unique to my setup. I am working on going back to 4.14 and then forward again. Will report back shortly.by bluzfanmr1 - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 7 months ago
bodhi Wrote: ------------------------------------------------------- > > [ 11.254469][ T134] netpoll: netconsole: local > IPv4 address 10.1.1.196 > [ 11.261071][ T134] netpoll: netconsole: > interface 'eth0' > [ 11.266449][ T134] netpoll: netconsole: remote > port 6666 > [ 11.271869][ T134] netpoll: netconsole: remote > IPv4 address 10.1by bluzfanmr1 - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 7 months ago
bodhi Wrote: ------------------------------------------------------- > OK I've updated the post above: > > https://forum.doozan.com/read.php?2,132799,132846#msg-132846 > > Please try. No luck, it still stops at the same spot: U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12) Boot device: NAND Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020aby bluzfanmr1 - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 7 months ago
bodhi Wrote: ------------------------------------------------------- > bluzfanmr1, > > Since you have recreated the uImage, boot again > with serial console. Interrupt u-boot countdown, > and turn off netconsole. > > > setenv preboot > saveenv > > > and then > > reset > > > Let it boot automatically. > > Please theby bluzfanmr1 - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 7 months ago
bodhi Wrote: ------------------------------------------------------- > bluzfanmr1, > > > [ 15.359731][ T134] netpoll: netconsole: > > timeout waiting for carrier > > That sounds familiar. And your boot log also > show: > > - a random MAC address (36:5d:d7:18:18:93) > - The DTB is probably appended to the uImage > > 1. Boot again and iby bluzfanmr1 - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 7 months ago
I'm searching to try and find the fix but here is where it hangs: Uncompressing Linux... done, booting the kernel. [ 0.000000][ T0] Booting Linux on physical CPU 0x0 [ 0.000000][ T0] Linux version 5.4.179-oxnas-tld-1 (root@tldDebianVM) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #1.0 SMP PREEMPT Mon Feb 14 21:50:21 PST 2022 [ 0.000000][ T0] CPU: ARMv6-compatiby bluzfanmr1 - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 7 months ago
bodhi Wrote: ------------------------------------------------------- > bluzfanmr1, > > > Begining with Kernel linux-5.4.101-oxnas-tld-1 > the > > following is what I see. Everything seems the > > same but it just stops at "Starting kernel ..." > > and the light will stay solid green but Debian > > Bullseye never starts. I'm watchinby bluzfanmr1 - Debian
Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 7 months ago
I have been unable to get my Pogoplug Pro to boot on any version 5 and up, starting with Kernel linux-5.4.101-oxnas-tld-1. Version Kernel linux-4.14.198-oxnas-tld-1 works just fine and I can always go back when I try a failed version at 5 and above. I can't for the life of me figure it out so I'm hoping I can get some help. Begining with Kernel linux-5.4.101-oxnas-tld-1 the folloby bluzfanmr1 - Debian
Re: New Error Lately - 7 months ago
I upgraded to bullseye and that took care of the issue. Thanks for the guidance.by bluzfanmr1 - Debian
Re: New Error Lately - 7 months ago
bodhi Wrote: ------------------------------------------------------- > bluzfanmr1, > > > It's the exact same error on all 3 so it's > > something they have in common I assume. Is > there > > something I need to do to fix this or is it > > harmless? > > It is security related so should be fixed. Which > Debian version are you on? buby bluzfanmr1 - Debian
New Error Lately - 7 months ago
I have 3 different model Pogoplug's and I'm suddenly getting the following error message when running updates: N: Skipping acquire of configured file 'main/binary-armel/Packages' as repository 'http://deb.debian.org/debian-security buster/updates InRelease' doesn't support architecture 'armel' N: Skipping acquire of configured file 'contrib/by bluzfanmr1 - Debian
Re: OLD POGO E02 update to debian - 8 months ago
I think this is what you are looking for: Arch to Debianby bluzfanmr1 - Debian
Re: Copied USB stick does not boot correctly - 2 years ago
myhobby Wrote: ------------------------------------------------------- > Bodhi, > > If you check the log of the copied stick, you see > that it is finding the usb stick and the boot > directory. I even checked the label before I > started my copy action via e2label /dev/sdb? which > resulted in rootfs as a label. > > Nevertheless I tried another approach wheby bluzfanmr1 - Debian
Re: Linux Kernel 5.5.1 Kirkwood package and Debian rootfs - 2 years ago
I noticed after the upgrade to 5.7.1 that there are 2 identical files in the /boot directory, though it doesn't seem to affect anything: -rw-r--r-- 1 root root 172K Jun 7 21:54 config-5.7.1-kikrwood-tld-1 -rw-r--r-- 1 root root 172K Jun 7 21:56 config-5.7.1-kirkwood-tld-1by bluzfanmr1 - Debian
Re: Linux Kernel 5.5.1 Kirkwood package and Debian rootfs - 2 years ago
Thank you, appreciate it!by bluzfanmr1 - Debian
Re: Linux Kernel 5.5.1 Kirkwood package and Debian rootfs - 2 years ago
bodhi, My verification of the downloaded file is showing that the checksums failed because they do not match. Can you please verify this or have I done something wrong? Thanksby bluzfanmr1 - Debian
Re: Ethernet problem with Linux Kernel 4.14.176 Oxnas (OX820) Pogo V3 - 2 years ago
bodhi, I just updated one of my boxes and it works perfectly! Thanks for your help! Also, could you educate a Linux amateur as to examples where a random MAC address would be preferable? I read about it but haven't been able to wrap my head around it. Thanks again.by bluzfanmr1 - Debian
Re: Ethernet problem with Linux Kernel 4.14.176 Oxnas (OX820) Pogo V3 - 2 years ago
Schnee, Thanks for your reply. Here is what I have and it doesn't seem to work: auto lo eth0 iface lo inet loopback iface eth0 inet static address 10.1.1.197 netmask 255.255.255.0 broadcast 10.1.1.255 network 10.1.1.0 gateway 10.1.1.1 hwaddress ether 00:25:31:xx:xx:xx Is there anythere here that looks wrong? Could I possibly have something else messed up? This is hby bluzfanmr1 - Debian
Re: Ethernet problem with Linux Kernel 4.14.176 Oxnas (OX820) Pogo V3 - 2 years ago
bodhi, I did as you suggested and added the hwaddress ether to /etc/network/interfaces but it isn't working. Anything else I can try? Can you explain the reason for the new default behavior for this? Why would one wish to use a random mac address instead of the real one? Thanks again!by bluzfanmr1 - Debian
Re: Ethernet problem with Linux Kernel 4.14.176 Oxnas (OX820) Pogo V3 - 2 years ago
bodhi, Thank you for the fix, I appreciate it. I remember now seeing that but by that time I had decided to start over. I will upgrade to the latest and do as you advise. FYI, I have been following this forum for years but never signed up until recently. I have learned so much from here and especially from you. Around 2010 or so I had a couple of dead Pogoplug's from when they stilby bluzfanmr1 - Debian
Page 1 of 2 Pages: 12