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
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
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
I upgraded to bullseye and that took care of the issue. Thanks for the guidance.by bluzfanmr1 - Debian
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
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
I think this is what you are looking for: Arch to Debianby bluzfanmr1 - Debian
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
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
Thank you, appreciate it!by bluzfanmr1 - Debian
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
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
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
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
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
Sorry to jump in on this but I thought I was hacked as I was experiencing the same thing on my 2 Pogoplug Pro boxes. I went back to the previous release and all is well now. No matter what I tried I couldn't get them to keep the correct MAC address. I ended up messing one up so bad I just reinstalled everything, but not doing the latest release.by bluzfanmr1 - Debian