Hello, suddenly today, I have lost my connection to omnia after a restart. The wifi is gone and I even cannot connect with cable. When I plug it in the LED does not light up and computer sees no connection. I have constantly power Led, WAN led and PCI2 led shining. I tried factory reset, but it did not help at all. The computer connects without problem to a different router. Is there anything else I can try?
Hello,
I just got the same. And my Omnia even did not accept to be re flashed (mode 4). The only thing I was able to do was flash from the internet (mode 6). Hope this can help.
I will fill a bug report about.
I am happy for you, but it did not work for me. I will have to use the ttl usb cable. I do not have idea how, but I hope I find out by the time it comes.
It would potentially only work with hardware revision CZ11NIC23, from the documentation:
This mode is for now avaialble only on Omnia 2019 and newer.
Could a be a DHCP issue. If you have not changed the default Lan subnet setting on the O you could try and set the client to a static IP (instead of being a DHCP client), e.g. 192.168.1.10, and see if that helps.
If not tried yet see if connecting to a(ny) other of the O’s Lan port yields a different result.
there is a bit of documentation that should help.
thanks for your help. But I am still far from the solution. I have the TTL cable. I ran screen and the output is here:
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver TIP-1.29.0
Memory config in EEPROM: 0x01
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
DDR3 Training Sequence - Ended SuccessfullyU-Boot 2015.10-rc2 (Aug 18 2016 - 20:43:35 +0200), Build: jenkins-omnia-master-23
SoC: MV88F6820-A0
Watchdog enabled
I2C: ready
SPI: ready
DRAM: 1 GiB (ECC not enabled)
Enabling Armada 385 watchdog.
Disabling MCU startup watchdog.
Regdomain set to **
MMC: mv_sdh: 0
SF: Detected S25FL164K with page size 256 Bytes, erase size 64 KiB, total 8 MiB
*** Warning - bad CRC, using default environmentPCI:
00:01.0 - 168c:002e - Network controller
PCI:
01:00.0 - 11ab:6820 - Memory controller
01:01.0 - 168c:003c - Network controller
PCI:
02:00.0 - 11ab:6820 - Memory controller
02:01.0 - 1b4b:9215 - Mass storage controller
Model: Marvell Armada 385 GP
Board: Turris Omnia SN: 0000000B00004150
Regdomain set to **
SCSI: MVEBU SATA INIT
SATA link 0 timeout.
SATA link 1 timeout.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs
Net: neta2
Hit any key to stop autoboot: 0
Setting bus to 1
BOOT eMMC FS
btrfs probe failed
** Unrecognized filesystem type **
btrfs probe failed
** Unrecognized filesystem type **
Bad Linux ARM zImage magic!
I tried this Bricked Omnia. How is it even possible, and how should one proceed in such a situation?, but I even cannot boot from serial with following commands on my Ubuntu linux when I downloaded everything needed:
(base) viktor@Desktop:~/Downloads/omnia$ sudo ./sendbeacon /dev/ttyUSB0
Sending beacon in loop. You have 5-10 seconds to power up Omnia.
(base) viktor@Desktop:~/Downloads/omnia$ sudo ./kwboot -t -b uboot-turris-omnia-uart-spl.kwb -B 115200 /dev/ttyUSB0
Sending boot message. Please reboot the target…/
I never get from there, if i reboot my omnia or not, I get stuck here. Any help really appreciated.
Looks there is some issue with the filesystem on the eMMC. What is the output from the serial with the 4-LED medkit reset (which will format the eMMC partition)?
Mode: Reflash…
[ 6.050587] usb 4-1: new high-speed USB device number 2 using xhci-hcd
[ 6.252177] usb 4-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 6.261116] usb 4-1: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 6.270075] usb-storage 4-1:1.0: USB Mass Storage device detected
[ 6.276305] scsi host2: usb-storage 4-1:1.0
[ 7.281228] scsi 2:0:0:0: Direct-Access USB Stick 2.0 ME 1100 PQ: 0 ANSI: 0 CCS
[ 7.290213] sd 2:0:0:0: [sda] 7831552 512-byte logical blocks: (4.01 GB/3.73 GiB)
[ 7.298170] sd 2:0:0:0: [sda] Write Protect is off
[ 7.303407] sd 2:0:0:0: [sda] No Caching mode page found
[ 7.308732] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 7.316979] sda: sda1
[ 7.320328] sd 2:0:0:0: [sda] Attached SCSI removable disk
Testing FS on device sda1
mount_fs /dev/sda1 /srcmnt
[ 7.914670] BTRFS: device fsid 6a13fe54-6894-4122-873e-57c5f28ac719 devid 1 transid 13 /dev/sda1
[ 7.924558] BTRFS info (device sda1): disk space caching is enabled
[ 7.930853] BTRFS: has skinny extents
Searching for /srcmnt/omnia-medkit*.tar.gz on sda1
Found medkit file /srcmnt/omnia-medkit-latest.tar.gz on device sda1
[ 17.990576] mmc0: Timeout waiting for hardware interrupt.
[ 28.010576] mmc0: Timeout waiting for hardware interrupt.
[ 28.016027] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0xe00
[ 28.079068] random: nonblocking pool is initialized
[ 49.490841] mmc0: Got data interrupt 0x00100000 even though no data operation was in progress.
[ 70.965678] mmc0: Got data interrupt 0x00100000 even though no data operation was in progress.
and so it continues
and after couple of minutes I get:
628.030588] mmc0: Card stuck in programming state! mmcblk0 card_busy_detect
[ 628.037577] blk_update_request: I/O error, dev mmcblk0, sector 0
[ 628.043617] Buffer I/O error on dev mmcblk0, logical block 0, lost async page write
1+0 records in
1+0 records out
512 bytes (51[ 628.064279] mmc0: Controller never released inhibit bit(s).
2B) copied, 620.[ 628.069941] mmcblk0: unknown error -5 sending read/write command, card status 0xe00
066241 seconds, [ 628.078978] blk_update_request: I/O error, dev mmcblk0, sector 0
0B/sWel[ 628.086383] blk_update_request: I/O error, dev mmcblk0, sector 8
come to fdisk (u[ 628.093794] blk_update_request: I/O error, dev mmcblk0, sector 16
til-linux 2.25.2[ 628.101293] blk_update_request: I/O error, dev mmcblk0, sector 24
).
Changes [ 628.118802] mmc0: Controller never released inhibit bit(s).
will remain in m[ 628.124436] mmcblk0: unknown error -5 sending read/write command, card status 0xe00
emory only, unti[ 628.133491] blk_update_request: I/O error, dev mmcblk0, sector 0
l you decide to [ 628.140896] Buffer I/O error on dev mmcblk0, logical block 0, async page read
write them.
Be careful before u[ 628.160851] mmc0: Controller never released inhibit bit(s).
sing the write c[ 628.166497] mmcblk0: unknown error -5 sending read/write command, card status 0xe00
ommand.fdisk[ 628.175540] blk_update_request: I/O error, dev mmcblk0, sector 0
: cannot open /d[ 628.182950] Buffer I/O error on dev mmcblk0, logical block 0, async page read
ev/mmcblk0: I/O [ 628.201511] mmc0: Controller never released inhibit bit(s).
error
[ 628.207142] mmcblk0: unknown error -5 sending read/write command, card status 0xe00
[ 628.215405] blk_update_request: I/O error, dev mmcblk0, sector 0
[ 628.221442] Buffer I/O error on dev mmcblk0, logical block 0, async page read
[ 628.228597] mmcblk0: unable to read partition table
blockdev: /dev/mmcblk0: I/O error
Error: Partition /dev/mmcblk0p1 missing. Exit.
umount_fs /srcmntBusyBox v1.23.2 (2016-08-18 20:38:45 CEST) built-in shell (ash)
It is possible, but sounds fishy, I have never used any LXCs and my router is like 4 years old. Though, it would explain that the router stopped working out of the blue. I still hope that it is SW problem of possibly faulty partitions.
BTRFS may not be the most suitable choice for deployment on NAND flash memory (durability), least OpenWrt utilises F2FS (Flash-Friendly File System) for that purpose as are quite a few of Android flavours.
So you think I am doomed, the only way is to replace the eMMC which should be costly according to the post you linked? I am still disappointed I am not able to boot from serial. It would enable me to explore much more.
There is nothing in the documentation about a tool in the u-boot recovery space that provides conclusive evidence whether the eMMC is gone. Just the reported I/O errors would indicate such, as mentioned by others.
It would seem so
Alternatively the OS can be deployed from:
- interior SSD
- interior USB drive (requires additional adapter)
Running from an exterior USB drive is currently only supported on the Mox platform but not for the Turris or the Omnia.
I use my Turris as NAS, so the PCI slot is full. I can at least try if it would work. Still, I am wondering about the uboot. That should work. Anyway, thanks very much for your help.
u-boot is just a boot-(environment)-manager placed on a MTD partition on NOR flash memory. Similar is u-boot rescue (invoked by the 5-LED reboot mode) on a secondary MTD partition, which is extended with a few basic rescue tools. Neither is providing/representing a fully fledged OS.
I understand that. Yet, it would give me the chance to try what worked for other, as reset of the environment.