EEPROM:Read from [factory] offset 0x0,length 0x400.
@WereCatf Did you manage to work on it?
@Federico-Corazza I forgot about it completely, but I'm just compiling an image and I should have something in ~15 minutes or so.
@Federico-Corazza Okay, here is a link to the image: https://dl.dropboxusercontent.com/u/11811685/omega2-eeprom/lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin
There is no WiFi, no ethernet enabled. Take a backup of your current factory-partition with
dd if=/dev/mtd2 of=/whereeveryouwant.mtd2and copy it to a USB-stick or microSD-card before flashing anything. You can then try to flash the contents of my Omega2's factory-partition with
mtd -r write /factory.mtd2 factory-- the file is already included inside the image. Then you can try flashing official firmware and it'll hopefully work, though your MAC-address might have changed.
@WereCatf I'm still having issues.
I flashed that image from dropbox but it freezes after:
[ 7.334675] hub 1-0:1.0: USB hub found
[ 7.338969] hub 1-0:1.0: 1 port detected
[ 7.347975] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 7.355920] ohci-platform: OHCI generic platform driver
[ 7.361567] ohci-platform 101c1000.ohci: Generic Platform OHCI controller
[ 7.368537] ohci-platform 101c1000.ohci: new USB bus registered, assigned bus number 2
[ 7.376660] ohci-platform 101c1000.ohci: irq 26, io mem 0x101c1000
[ 7.442319] hub 2-0:1.0: USB hub found
[ 7.446613] hub 2-0:1.0: 1 port detected
[ 7.464603] MTK MSDC device init.
[ 7.507286] mtk-sd: MediaTek MT6575 MSDC Driver
[ 7.517811] sdhci: Secure Digital Host Controller Interface driver
[ 7.524102] sdhci: Copyright(c) Pierre Ossman
[ 7.530271] sdhci-pltfm: SDHCI platform and OF driver helper
[ 7.544508] usbcore: registered new interface driver usb-storage
[ 7.561326] init: - preinit -
I rebooted it an then it went past the 7 seconds up to 48 but I can't reproduce it.
@WereCatf I flashed the imaged a second time and got it working, but when I loaded the latest firmware it froze again at
[ 17.490148] EEPROM:Read from [factory] offset 0x0,length 0x400.
@Federico-Corazza Are you absolutely certain your power supply is good?
@WereCatf how much can the omega withstand with the mini board? Can I use the power supply of the raspberry pi ? (5V 2.5A)
@Federico-Corazza Yes, you can.
@WereCatf It works!
Thank you very much!
I apologize if I made a bigger problem than it really was.
Working with some similar MT7688 hardware, I've also seen that an under-rated power supply can cause unexpected reboots, particularly when the wifi subsystem starts up.
Overall power consumption of these systems is low, maybe a watt and a half, but there seem to be some peak loads where a supply with poorly responding regulation can trigger a crash and reboot.
I seem to have same issues you have, I cannot get wifi working. However I dont think it is power related in my case. I have tried powering from my laptop and seperately from a phone charger rated 5V/1A on the micro usb on the docking board. But the issues presists...
I've got the same thing this person posted at startup: https://community.onion.io/topic/1082/help-omega2-not-working/2 with the stack trace.
I tried setting up wifi connection over the web but it just would not work and fails every time I try. Then I tried it over serial/ssh and I get this message when i tried to restart wifi with
/etc/init.d/network restartafter I verified all settings where ok in /etc/config/wireless. Then the same "EEPROM Read from" happens and the restart seems to fail?
[ 491.395130] br-wlan: port 2(ra0) entered disabled state [ 491.400506] br-wlan: port 1(eth0.1) entered disabled state [ 491.513483] device eth0.1 left promiscuous mode [ 491.518099] device eth0 left promiscuous mode [ 491.522709] br-wlan: port 1(eth0.1) entered disabled state [ 491.541241] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready [ 491.560027] device ra0 left promiscuous mode [ 491.564542] br-wlan: port 2(ra0) entered disabled state root@Omega-AEAF:/# [ 495.435051] EEPROM:Read from [factory] offset 0x0,length 0x400. [ 497.901039] ch4 bssid=90:f6:52:3f:5b:da [ 497.905039] ch6 bssid=62:35:3b:31:49:cb [ 497.909018] ch6 bssid=62:35:3b:31:49:cd [ 497.913024] ch6 bssid=5c:35:3b:31:49:ca [ 497.917003] ch9 bssid=60:e3:27:8d:86:4c [ 497.920977] ===================================================== [ 497.927176] Channel 1 : Dirty = 24, False CCA = 0, Busy Time = 3497, Skip Channel = FALSE [ 497.935481] Channel 2 : Dirty = 88, False CCA = 0, Busy Time = 469, Skip Channel = FALSE [ 497.943693] Channel 3 : Dirty = 104, False CCA = 0, Busy Time = 1087, Skip Channel = FALSE [ 497.952087] Channel 4 : Dirty = 154, False CCA = 0, Busy Time = 1396, Skip Channel = FALSE [ 497.960464] Channel 5 : Dirty = 148, False CCA = 0, Busy Time = 1642, Skip Channel = FALSE [ 497.968859] Channel 6 : Dirty = 262, False CCA = 0, Busy Time = 3503, Skip Channel = FALSE [ 497.977253] Channel 7 : Dirty = 148, False CCA = 0, Busy Time = 74, Skip Channel = FALSE [ 497.985472] Channel 8 : Dirty = 136, False CCA = 0, Busy Time = 701, Skip Channel = FALSE [ 497.993783] Channel 9 : Dirty = 142, False CCA = 0, Busy Time = 1008, Skip Channel = FALSE [ 498.002178] Channel 10 : Dirty = 92, False CCA = 0, Busy Time = 807, Skip Channel = FALSE [ 498.010467] Channel 11 : Dirty = 28, False CCA = 0, Busy Time = 35, Skip Channel = FALSE [ 498.018679] ===================================================== [ 498.024874] Rule 1 CCA value : Min Dirtiness (Include extension channel) ==> Select Channel 1 [ 498.033608] Min Dirty = 24 [ 498.036350] ExChannel = 0 , 0 [ 498.039356] BW = 20 [ 498.374026] device eth0.1 entered promiscuous mode [ 498.378907] device eth0 entered promiscuous mode [ 498.394614] br-wlan: port 1(eth0.1) entered forwarding state [ 498.400419] br-wlan: port 1(eth0.1) entered forwarding state [ 500.391085] br-wlan: port 1(eth0.1) entered forwarding state [ 500.793187] device ra0 entered promiscuous mode [ 500.797878] br-wlan: port 2(ra0) entered forwarding state [ 500.803451] br-wlan: port 2(ra0) entered forwarding state [ 502.801027] br-wlan: port 2(ra0) entered forwarding state
Does anyone know what the cause of this problem is or how I could get my Omega2+ connected to wifi?
@Maarten-G Don't try to hijack threads. Your device isn't crashing, so it's not the same issue.
Yes that does seem like a different issue, though the thread title is a bit unfortunate, it seems the EEPROM message is routine verbose output, not indicative of any issue.
But if the message is the last thing seen before a problem, or comes up in a search result, it's easy to associate it in the mind.
@WereCatf Apologies, not here to hijack a thread. I figured the EEPROM: Read from [factory ] error is/was an issues and since I got the same thing I thought it would be more helpful to post here, instead of making a new thread. Which was stated in the guidelines to not make a new thread and rather post in another user thread if I'm courteous and in the same situation.
I'd try looking around for other issues, testing the things that I can and make a new thread.