Show all posts by user

Re: Forum PM send error - 4 weeks ago

bodhi Wrote: ------------------------------------------------------- > Welcome back! So happy to see this back online! I was scared it was gone forever.

by bluzfanmr1 - Off-Topic

Re: Kernel releases download - 5 weeks ago

bodhi Wrote: ------------------------------------------------------- > All, > > I've fixed the download links in the 2 kernel > release threads. Please try again. It's working, thanks!

by bluzfanmr1 - Debian

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 3 months ago

dhargens Wrote: ------------------------------------------------------- >It may be related to heat since > these things get REALLY hot when setting them up, > and maybe also the orion errors I see when I put a > USB 3.1 in the top port. I was happy to see this observation as I have experienced the same thing and was worried it was my device. As you said, the thing was really

by bluzfanmr1 - uBoot

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 3 months ago

After having the same issues as @dhargens with 6.3.5, I can confirm that 6.3.8 is working on the Pogoplug V4. Thanks for the continuing help!

by bluzfanmr1 - uBoot

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 3 months ago

bodhi Wrote: ------------------------------------------------------- > 1st post updated: > > Quote8. (Optional) Activate netconsole > > Please do not activate netconsole! > I'm troubleshooting a problem, stay tune... > . > > Something is lacking in netconsole implementation. > It is not robust enough. > > When u-boot crashes and reset (due

by bluzfanmr1 - uBoot

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 3 months ago

dhargens Wrote: ------------------------------------------------------- > I'm having a problem with upgrading the Debian > kernel from 5.13 to 6.3.5 and using it in one of > the rear USB 3 ports. > I had the same issue and had to go back to the earlier kernel to get the rear ports to work.

by bluzfanmr1 - uBoot

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 3 months ago

Excellent, I will delete that and thank you for the ls tip!

by bluzfanmr1 - uBoot

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 3 months ago

@bodhi one last quick question. I noticed a file named uInitr in the boot folder that I've never noticed before. Should that file be there or can it be deleted? I thought I may have left the d off the end when copying and pasting earlier in the upgrade process. Thank you. root@PogoplugV4:~$ ls -lha /boot/ total 83M drwxr-xr-x 3 root root 4.0K Jun 5 17:38 . drwxr-xr-x 21 root ro

by bluzfanmr1 - uBoot

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 3 months ago

bodhi Wrote: ------------------------------------------------------- > bluzfanmr1, > > > > I know better, but didn't keep the logs. > Lesson > > learned. I did not try the previous u-boot > (2017) > > and installed 2023.04 straight from stock. Yes, > I > > had set up netconsole, but it wasn't working. > I > > didn

by bluzfanmr1 - uBoot

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 3 months ago

bodhi Wrote: ------------------------------------------------------- > bluzfanmr1, > > > Do I have a > > hardware issue with this new box or have I done > > something wrong? > > The appearance does look much like a HW problem, > but I'd bet it is not. Just your envs are messed > up. > > > > U-Boot 2023.04-tld-1 (May 10 2023 - 2

by bluzfanmr1 - uBoot

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 3 months ago

I went ahead and updated to the latest kernel (linux-6.3.5-kirkwood-tld-1-bodhi.tar.bz2 (02 Jun 2023)) on my new Pogoplug V4 and it stopped booting. I hooked up serial console and when booting it stops at the same spot below, whether regular booting or using kwboot. Do I have a hardware issue with this new box or have I done something wrong? root@Pogoplug2:~# ./kwboot -t -B 115200 /dev/tty

by bluzfanmr1 - uBoot

Re: Forum PM send error - 3 months ago

bodhi Wrote: ------------------------------------------------------- > Looks like sending PM is broken. > > Thanks bluzfanmr1 for pointing out the typos in > the release threads! > > bluzfanmr1 or Chris, please try sending PM to me > (test if it's really broken). Done

by bluzfanmr1 - Off-Topic

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 4 months ago

Since a serial connection for the Pogoplug V4/Mobile is much harder than a serial connection for the Pogoplug E02, I thought I'd share a picture of my serial cable that uses the shirt pin method. This option eliminates the need for soldering. You can firmly but carefully push each pin into the solder for each connection until they stick without falling. I cut off the top of the pins to

by bluzfanmr1 - uBoot

Re: PogoPlug E02 unusable - 4 months ago

This is really strange because I had that same log yesterday, particularly the kernel panic, after creating this for a new Pogoplug 4 I had purchased. I ended up redoing it from scratch again and I no longer got the panic and things worked fine. You might try the same.

by bluzfanmr1 - Debian

Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 4 months ago

Thank you for this thread. Last week, via eBay, it inspired me to add a V4 to my Pogoplug collection. It was the last version I didn't own. I was able to use the shirt pin method to gain serial access and then install this latest U-Boot and Debian. I was a little rusty on the timing when trying to kwboot but after a few tries got it down pat!

by bluzfanmr1 - uBoot

Re: Pogoplug No Longer Allows You to Enable SSH ?? - 4 months ago

bodhi Wrote: ------------------------------------------------------- > asterix Wrote: > ------------------------------------------------------- > > throw out serveral poloplugs last month, pi > much > > better for DIY hobbies. > > Hey, good for you. > > But perhaps you should not treat pogoplugs like > garbage? Once upon the time, they were a good

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 - 4 months ago

Another update on this. I was gone for about 10 days and when I came home I decided to move things from the 2GB ssd in a usb enclosure to a random usb flash drive. To my surprise it fired right up and has been working for a couple of weeks now without any issues. I'm wondering if my issues were caused by the large ssd and/or the enclosure being the main drive. The ssd and enclosure see

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 - 5 months ago

Looks like I spoke too soon. After working fine for the past week, this morning I'm unable to ssh in again, even after multiple reboots. I'll have to dig back into it when I have more time.

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 - 6 months ago

bodhi Wrote: ------------------------------------------------------- > bluzfanmr1, > > > This last part seems to have fixed things. > After > > modifying the /etc/rc.local file the network no > > longer disappears, nor ssh access, and > everything > > is working as expected. I'm just really > confused > > as to why this happened. I

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 - 6 months ago

bodhi Wrote: ------------------------------------------------------- > bluzfanmr1, > > > The question now is how do I make this > permanent? > > You might not need to do ifdown/up if you can > avoid the problem with systemd started running > somehow. > > Instead of using the above commands to start > Netatalk, you can do the sysv initscripts way.

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 - 6 months ago

BobM Wrote: ------------------------------------------------------- > Not sure if this will help but the only way I get > SystemD to load correctly on my POGO was to > install the systemd helper - systemd-sysv as well > as systemd. That fixed the problem where systemd > was started first with PID 1. > > I use the pogo as NAS and gerbera media servers > and they

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 - 6 months 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 - 6 months 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 seri

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 - 6 months 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 - 6 months 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 - 6 months 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 thi

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 - 6 months 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 - 6 months 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 alo

by 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 - 6 months 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. I

by bluzfanmr1 - Debian

Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 1 year 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