the output i'm getting with my device, is the output from the Bios (coreboot), isn't it ? yours in your screenshot is the one from the OS ?
if i understand well, i'm stuck in the bios. i can't get any device to boot correctly...
the output i'm getting with my device, is the output from the Bios (coreboot), isn't it ? yours in your screenshot is the one from the OS ?
if i understand well, i'm stuck in the bios. i can't get any device to boot correctly...
I didn't let it boot, GRUB's the boot loader, but It'd eventually boot the OS and give me a login prompt.
If I logon to the existing OS, or boot a flash drive, I could put any other Linux dist or Openwrt as a paralell OS on it.
Also, I didn't overwrite the whole drive, like you did, by accident
before erasing the drive, i had the same grub page, leting me choose the same things...
as everything is erased, or flashed with something that doesn't seem to boot, i can't go to this step...
i thought that flashing the whole drive with dd, means flashing root1 only
looks like the 500 are more friendly than the 520
I think having serial usb in has craused it to halt the boot order due to default bios settings
humm
There seems to be a hardware watchdog. Info for taming it https://modlog.net/velocloud-520-to-opensource/ ...
I got mine to boot, but an amd64 image didn't work, had to use the i686 image.
Grabbed one from https://www.system-rescue.org/Download/.
You need to manually enable serial console for isolinux and Linux, the default is obviously video output.
Added serial 0 115200
on top of /syslinux.cfg and all the cfg files it touches along the way.
/sysresccd/boot/syslinux/sysresccd.cfg
/sysresccd/boot/syslinux/sysresccd_head.cfg
/sysresccd/boot/syslinux/sysresccd_sys.cfg
then enabled serial console for the kernels in /sysresccd/boot/syslinux/sysresccd_sys.cfg by appending
console=ttyS0,115200n8
to all APPEND entries in the file.
in the comments, someone said :
Tien Mai on March 7, 2022 at 11:58 am said:
You can disable watchdog by flash new previous bios at link below
https://bitbucket.org/velocloud/openwrt/src/master/trunk/target/linux/x64/edge5x0/files/root/firmware/5×0/vc5x0-cb-01-bootorder.romAfter that you can install/modify and install any OS.
but this link is not working for me, it says " We can't let you see this page"
anyway, i don't see how i can flash this bios.
ok i'll try this...
from your link :
Finally after another few weeks, I had OpenWRT working, that (as far as I could tell) provided basic network switching capabilities. The USB installer image can be found here.
As a nasty “install” I did a “dd if=/dev/sda of=/dev/sdb”There is an install file in /root/installer -p (after removing all partitions and setting a blank GPT) to copy the data from the USB to the internal 8GB storage.
That usb image finaly booted !! let's see what i can do now...
Looks like it installed openwrt ?? no it didn't
BusyBox v1.23.2 (2021-11-14 02:37:18 AWST) built-in shell (ash)
_ __ __ ________ __
| | / /__ / /___ / ____/ /___ __ ______/ /
| | / / _ \/ / __ \/ / / / __ \/ / / / __ /
| |/ / __/ / /_/ / /___/ / /_/ / /_/ / /_/ /
|___/\___/_/\____/\____/_/\____/\__,_/\__,_/
VeloCloud Inc.
------------------------------------------------
root@vc:/# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 28.7G 0 disk
|-sda1 8:1 1 1M 0 part
|-sda2 8:2 1 18M 0 part
|-sda3 8:3 1 350M 0 part /
`-sda4 8:4 1 500M 0 part
sdb 8:16 1 7.3G 0 disk
|-sdb1 8:17 1 16M 0 part
|-sdb2 8:18 1 104M 0 part
`-sdb128 259:0 1 239K 0 part
root@vc:/#
not an official one, by the looks of it.
it didn't install it, it just booted the device. i removed the usb key and nothing changed.
so at least i have a shell and i can do something...
at this point what can i do by the way ??
try dd:ing that openwrt image to the 520s storage.
ok let's go.
ho the guy who made this image said :
There is an install file in /root/installer -p (after removing all partitions and setting a blank GPT) to copy the data from the USB to the internal 8GB storage.
yeah, you even C&Ped that piece of text in your last quote from the site
root@vc:~# ./installer -p
[ 296.309818] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
images in /tmp/mnt-inst/images
disk /dev/sda is 29340MB
creating new partition layout on /dev/sda, root size 1024MB ...
Error: Partition(s) on /dev/sda are being used.
/dev/sda: gpt partitions 1 2 3 4
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Warning: Not all of the space available to /dev/sdb appears to be used, you can fix the GPT to use all of the space (an extra 15023583 blocks) or continue wit h the current setting?
/dev/sdb: gpt partitions 128 1 2
making boot filesystem on /dev/sda2 ...
/dev/sda2 contains a ext4 file system
Proceed anyway? (y,n) y
making user filesystem on /dev/sda6 ...
The file /dev/sda6 does not exist and no size was specified.
installing grub to /dev/sda ...
making empty grub environment block ...
making grub core image ...
setting up grub MBR on /dev/sda ...
install to /dev/sda, runtime on /dev/sda
installing grub modules/configs in boot partition /dev/sda2 ...
[ 305.776443] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
root@vc:~#
what am i supposed to do here ?
type reboot
, and hope for the best ?
sda is my usbkey, according to the error message, i installed on my usbkey
i don't understand what to do and if i do it correctly :
root@vc:/# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 28.7G 0 disk
|-sda1 8:1 1 1M 0 part
|-sda2 8:2 1 18M 0 part
|-sda3 8:3 1 350M 0 part /
`-sda4 8:4 1 500M 0 part
sdb 8:16 1 7.3G 0 disk
|-sdb1 8:17 1 16M 0 part
|-sdb2 8:18 1 104M 0 part
`-sdb128 259:0 1 239K 0 part
sda is my 32GB usb key
root@vc:/# /root/installer -p
[ 161.481559] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
images in /tmp/mnt-inst/images
disk /dev/sda is 29340MB
creating new partition layout on /dev/sda, root size 1024MB ...
Error: Partition(s) on /dev/sda are being used.
/dev/sda: gpt partitions 1 2 3 4
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Warning: Not all of the space available to /dev/sdb appears to be used, you can fix the GPT to use all of the space (an extra 15023583 blocks) or continue with the current setting?
/dev/sdb: gpt partitions 128 1 2
making boot filesystem on /dev/sda2 ...
/dev/sda2 contains a ext4 file system
last mounted on /tmp/mnt-root on Mon Nov 15 09:54:53 2021
Proceed anyway? (y,n)
and that script try to install things on sda