Welcome! Log In Create A New Profile

Advanced

Pogoplug v4 Mobile uboot issue.

Posted by umd 
umd
Pogoplug v4 Mobile uboot issue.
April 26, 2017 02:13PM
Prior to flashing I entered ethaddr:

fw_printenv ethaddr 
Warning: Bad CRC, using default environment.
## Error: "ethaddr" not defined


I ignored it since I'd be flashing the envs anyway per the instructions.

I flashed the new u-boot successfully changed all the corresponding envs except ethaddr. This time it said,

Can't overwrite "ethaddr"


I figured I'd reboot the box into linux and then adjust it. The Pogo successfully booted into Debian with the default ethaddr from the flashed envs and changed the ethaddr to the one on the bottom of the case (I assume that is the right one). When I reboot, I am not able to access the device. It only works with the default ethaddr that I flashed from uboot.2016.05-tld-1.environment.bodhi.tar.

Is that fixable?
Re: Pogoplug v4 Mobile uboot issue.
April 26, 2017 05:31PM
umd,


Quote

and changed the ethaddr to the one on the bottom of the case (I assume that is the right one).

You meant you changed it to the correct MAC at Debian prompt, using fw_setenv ?

Quote

When I reboot, I am not able to access the device. It only works with the default ethaddr that I flashed from uboot.2016.05-tld-1.environment.bodhi.tar.

If you use dynamic IP (as default in the released Debian 4.4 rootfs), then the new MAC address will cause the router to assign a different one. Did you look for a different IP? or did you try to ping the box?

I assume the hostname is still debian:
ping debian.local

And do you have netconsole or serial console?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 04/26/2017 05:32PM by bodhi.
umd
Re: Pogoplug v4 Mobile uboot issue.
April 27, 2017 11:53AM
bodhi,

Ok I think I figured it out. I also have a Pogo E02 that wasn't turned on. For some reason my router was taking the same IP address that was assigned to the E02. So I first booted up the E02 and it took its IP address. Then booted up the Pogoplug Mobile with the MAC on the bottom of the case and now my router assigned it a new IP address and it shows the correct MAC. Wacky and doesn't make much sense, but at least I figured it out. :-)

Quote

> You meant you changed it to the correct MAC at Deb
> ian prompt, using fw_setenv ?
>

Correct.


Quote

> If you use dynamic IP (as default in the released
> Debian 4.4 rootfs), then the new MAC address will
> cause the router to assign a different one. Did yo
> u look for a different IP? or did you try to ping
> the box?


I would have my router console open watching for new devices and it wouldn't show up. The router would show the netconsole IP for a few seconds then I'd wait for a new IP, but nothing would appear.


Quote

> And do you have netconsole or serial console?

I have both now. I used UART through serial for initial flashing of the Uboot.
Re: Pogoplug v4 Mobile uboot issue.
April 27, 2017 06:23PM
umd Wrote:
-------------------------------------------------------
> bodhi,
>
> Ok I think I figured it out. I also have a Pogo E0
> 2 that wasn't turned on. For some reason my router
> was taking the same IP address that was assigned t
> o the E02. So I first booted up the E02 and it too
> k its IP address. Then booted up the Pogoplug Mobi
> le with the MAC on the bottom of the case and now
> my router assigned it a new IP address and it show
> s the correct MAC. Wacky and doesn't make much sen
> se, but at least I figured it out. :-)
>
>
Quote

> > You meant you changed it to the correct MAC at D
> eb
> > ian prompt, using fw_setenv ?
> >
>
>
> Correct.
>
>
>
Quote

> > If you use dynamic IP (as default in the release
> d
> > Debian 4.4 rootfs), then the new MAC address wil
> l
> > cause the router to assign a different one. Did
> yo
> > u look for a different IP? or did you try to pin
> g
> > the box?
>
>
>
> I would have my router console open watching for n
> ew devices and it wouldn't show up. The router wou
> ld show the netconsole IP for a few seconds then I
> 'd wait for a new IP, but nothing would appear.
>
>
>
Quote

> > And do you have netconsole or serial console?
>
>
> I have both now. I used UART through serial for in
> itial flashing of the Uboot.

Cool! Glad you have figured it out. When in doubt, use static IP.

You have reminded me to make it better in the next release, or add more instruction, thanks!

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
umd
Re: Pogoplug v4 Mobile uboot issue.
April 28, 2017 02:42PM
No problem!

One last question for you. I have a 4TB external drive. I was looking to create a 4GB boot partition and a second partition for data. I figured out that I need to use parted, but for some reason it is not booting and giving me this error in netconsole:

loading uImage ...
GPT: first_usable_lba incorrect: 22 > 0
part_get_info_efi: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
part_get_info_efi: *** ERROR: Invalid Backup GPT ***
** Invalid partition 1 **
loading uInitrd ...
GPT: first_usable_lba incorrect: 22 > 0
part_get_info_efi: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
part_get_info_efi: *** ERROR: Invalid Backup GPT ***
** Invalid partition 1 **
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
GPT: first_usable_lba incorrect: 22 > 0
part_get_info_efi: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
part_get_info_efi: *** ERROR: Invalid Backup GPT ***
** Invalid partition 1 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

here is what i typed in parted:

parted /dev/sdb
mklabel gpt
mkpart primary 0GB 4GB
mkpart primary 4GB 4001GB <---4001GB was what print outputed
quit

mkfs.ext4 -L ROOTFS -j /dev/sdb1
mkfs.ext4 -L USB /dev/sdb2

I then mounted and extracted the Debian tar into sdb1 and powered down. And booted with only the new drive. I seem to be missing something. My first time using Parted. Fdisk was a bit more straightforward. Thanks.



Edit:

Just had a thought. Can I create a 4GB partition with Fdisk and then created the 2nd partition with Parted? I don't know if that would work or cause a conflict?



Edited 3 time(s). Last edit at 04/28/2017 03:03PM by umd.
Re: Pogoplug v4 Mobile uboot issue.
April 28, 2017 07:48PM
umd Wrote:
-------------------------------------------------------
> No problem!
>
> One last question for you. I have a 4TB external d
> rive. I was looking to create a 4GB boot partition
> and a second partition for data. I figured out tha
> t I need to use parted, but for some reason it is
> not booting and giving me this error in netconsole
> :
>
>
> loading uImage ...
> GPT: first_usable_lba incorrect: 22 > 0
> part_get_info_efi: *** ERROR: Invalid GPT ***
> GUID Partition Table Header signature is wrong: 0x
> 0 != 0x5452415020494645
> part_get_info_efi: *** ERROR: Invalid Backup GPT *
> **
> ** Invalid partition 1 **
> loading uInitrd ...
> GPT: first_usable_lba incorrect: 22 > 0
> part_get_info_efi: *** ERROR: Invalid GPT ***
> GUID Partition Table Header signature is wrong: 0x
> 0 != 0x5452415020494645
> part_get_info_efi: *** ERROR: Invalid Backup GPT *
> **
> ** Invalid partition 1 **
> loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
> GPT: first_usable_lba incorrect: 22 > 0
> part_get_info_efi: *** ERROR: Invalid GPT ***
> GUID Partition Table Header signature is wrong: 0x
> 0 != 0x5452415020494645
> part_get_info_efi: *** ERROR: Invalid Backup GPT *
> **
> ** Invalid partition 1 **
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!
>
>
> here is what i typed in parted:
>
> parted /dev/sdb
> mklabel gpt
> mkpart primary 0GB 4GB
> mkpart primary 4GB 4001GB <---4001GB wa
> s what print outputed
> quit
>
> mkfs.ext4 -L ROOTFS -j /dev/sdb1
> mkfs.ext4 -L USB /dev/sdb2
>
> I then mounted and extracted the Debian tar into s
> db1 and powered down. And booted with only the new
> drive. I seem to be missing something. My first ti
> me using Parted. Fdisk was a bit more straightforw
> ard. Thanks.
>
>
>
> Edit:
>
> Just had a thought. Can I create a 4GB partition w
> ith Fdisk and then created the 2nd partition with
> Parted? I don't know if that would work or cause a
> conflict?i


umd,

1. The rootfs label is in lower case rootfs
2. But gpt part errors indicates the partitions are incorrect any way. I am not at home so afraid that I cant help, you will need google this instruction.
3. It needs to be formatted with gparted or parted. Fdisk will not wok.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Pogoplug v4 Mobile uboot issue.
April 28, 2017 11:31PM
Better don't put system on the 4tb drive. It won't be able to spin down with system on it.
Re: Pogoplug v4 Mobile uboot issue.
April 29, 2017 04:44AM
daviddyer Wrote:
-------------------------------------------------------
> Better don't put system on the 4tb drive. It won't
> be able to spin down with system on it.

That's a very good point. But sometimes, taking the easy approach (having one partition, one disk) makes things so much simpler.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
umd
Re: Pogoplug v4 Mobile uboot issue.
April 29, 2017 02:20PM
bodhi Wrote:
-------------------------------------------------------
> daviddyer Wrote:
> --------------------------------------------------
> -----
> > Better don't put system on the 4tb drive. It won
> 't
> > be able to spin down with system on it.
>
> That's a very good point. But sometimes, taking t
> he easy approach (having one partition, one disk)
> makes things so much simpler.


bodhi and daviddyer,

I might have to do that and leave the system on my other drive. I tried GParted this morning created a 4gb primary partition. Still getting the same error. Not sure if I'm doing something wrong when I create partition. Seems pretty straight forward. Oh well. Thanks.
Re: Pogoplug v4 Mobile uboot issue.
April 30, 2017 01:04AM
umd,

This error is quite common. You just need to use parted to wipe out everything and start fresh. And create onlty one 1 partition.

- Post the actual log of what you did to create the 4TB partition.
- Post the serial boot log.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
umd
Re: Pogoplug v4 Mobile uboot issue.
April 30, 2017 09:43AM
bodhi,

I just went ahead and made the entire drive a samba drive and used my existing rootfs. Easier that way and the drive will be able to spin down like Dave said. It's funny, when I was trying to get the new drive to boot, one time it actually did boot but I also had my thumb drive with the working rootfs in the 1st usb slot. So the Pogo must have got the necessary initial boot info from the thumb drive then jumped over to my new hard drive rootfs that I just created. It took me a few tries logging in with the wrong password to realize that is what happened. This new drive is a Western Digital and we know how quirky they can be. Thanks for your help.
Re: Pogoplug v4 Mobile uboot issue.
April 30, 2017 10:41AM
umd,

That's actually normal. Because the 4TB drive partition is labeled rootfs. Once the kernel booted, it will find the first partition that has the label rootfs and mount that (we set it up that way in bootargs). So to make sure the rootfs on USB is selected, you need to relabel the 4TB partition to something else.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: