<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with kernel]]></title><description><![CDATA[A list of topics that have been tagged with kernel]]></description><link>http://community.onion.io/tags/kernel</link><generator>RSS for Node</generator><lastBuildDate>Mon, 16 Mar 2026 05:18:34 GMT</lastBuildDate><atom:link href="http://community.onion.io/tags/kernel.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 24 Jul 2024 17:46:56 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[New bootloader getting stuck when loading kernel image]]></title><description><![CDATA[@luz hahaha, trying to become a full onioneer little by little.
It is the Omega2+. Here is a log of the boot process to see if I'm missing anything.

U-Boot 2024.04-gc2bfb2b8c6 (Jul 19 2024 - 15:18:23 -0400)

CPU:   MediaTek MT7688A ver:1 eco:2
Boot:  DDR2, SPI-NOR 3-Byte Addr, CPU clock from XTAL
Clock: CPU: 580MHz, Bus: 193MHz, XTAL: 40MHz
Model: Onion Omega2+
DRAM:  128 MiB
Core:  59 devices, 18 uclasses, devicetree: separate
Loading Environment from SPIFlash... SF: Detected mx25l25635e with page size 256 Bytes, erase size 64 KiB, total 32 MiB
OK
In:    uartlite@c00
Out:   uartlite@c00
Err:   uartlite@c00
Initializing MT7688 GPIO system.
Net:   eth0: eth@10110000
Hit any key to stop autoboot:  0
=&gt;


I did see that address 80800000 is outside the zone range of the memory but the load address is defined as 0x80800000 and trying to load it via tftp and booting anywhere else fails to decompress the image. Maybe thats the issue and just assumed it should work. Thought the offset would take care of that but maybe I am misunderstanding what the offset does
CONFIG_SYS_LOAD_ADDR=0x80800000

]]></description><link>http://community.onion.io/topic/5068/new-bootloader-getting-stuck-when-loading-kernel-image</link><guid isPermaLink="true">http://community.onion.io/topic/5068/new-bootloader-getting-stuck-when-loading-kernel-image</guid><dc:creator><![CDATA[baby Onioneer]]></dc:creator><pubDate>Wed, 24 Jul 2024 17:46:56 GMT</pubDate></item><item><title><![CDATA[Problem starting kernel, did I brick my board]]></title><description><![CDATA[@leviathan33 I looks like your firmware partition size is a bit wacky. I wonder if you mucked up the firmware with your "solution"  to not being unable to use scp. Did you see my reply to that post?
The LTE is basically an Omega2S+ with the LTE stuff added in, so for future reference you can always use the Omega2+ firmware images and then add in the LTE packages separately.
Have you tried a factory reset?  If so, what were the results?
Next step I would try is to reflash the device form USB, the instructions are here:
https://docs.onion.io/omega2-docs/Firmware-Flashing-from-USB-storage.html
USB device can be fussy so you may have to try from more than one USB device.
]]></description><link>http://community.onion.io/topic/4906/problem-starting-kernel-did-i-brick-my-board</link><guid isPermaLink="true">http://community.onion.io/topic/4906/problem-starting-kernel-did-i-brick-my-board</guid><dc:creator><![CDATA[crispyoz]]></dc:creator><pubDate>Tue, 22 Nov 2022 08:49:03 GMT</pubDate></item><item><title><![CDATA[query kernel error]]></title><description><![CDATA[@jossvall I wonder if removing the mmc kernel module would solve this issue without the need to modify your hardware design this late in the game.
]]></description><link>http://community.onion.io/topic/4532/query-kernel-error</link><guid isPermaLink="true">http://community.onion.io/topic/4532/query-kernel-error</guid><dc:creator><![CDATA[crispyoz]]></dc:creator><pubDate>Tue, 20 Jul 2021 02:05:54 GMT</pubDate></item><item><title><![CDATA[Contiguous Memory Allocator in kernel]]></title><description><![CDATA[@Modest-Polykarpovich not my own, but I'm still trying to improve existin driver, here my post, I add some of my fixes, It works better with them, but not perfect with rates higher than 96kHz, I really wanna play bit-perfect 192/24 on i2s Omega2
]]></description><link>http://community.onion.io/topic/3840/contiguous-memory-allocator-in-kernel</link><guid isPermaLink="true">http://community.onion.io/topic/3840/contiguous-memory-allocator-in-kernel</guid><dc:creator><![CDATA[Mark Nagaev]]></dc:creator><pubDate>Wed, 13 Nov 2019 11:26:11 GMT</pubDate></item><item><title><![CDATA[Request for improvement on driver for ttyS_ (or help to do it myself)]]></title><description><![CDATA[@Lazar-Demin
No: for size, cost, and power reasons we need to use the built-in UART(s).
I'm interested that @luz is having no trouble doing basically the same thing.  It would be nice to know what he/she is doing that is different from what I am doing.
I will rebuild buildroot and see if this makes a difference.
]]></description><link>http://community.onion.io/topic/3654/request-for-improvement-on-driver-for-ttys_-or-help-to-do-it-myself</link><guid isPermaLink="true">http://community.onion.io/topic/3654/request-for-improvement-on-driver-for-ttys_-or-help-to-do-it-myself</guid><dc:creator><![CDATA[JP Norair]]></dc:creator><pubDate>Fri, 23 Aug 2019 23:35:31 GMT</pubDate></item><item><title><![CDATA[Omega2+ GPIO IRQ question]]></title><description><![CDATA[Try this: https://github.com/OnionIoT/gpioIrq
But I 've never tested it! This code uses sysfs edge detection, so I think doesn't need an irq kernel module.
]]></description><link>http://community.onion.io/topic/3615/omega2-gpio-irq-question</link><guid isPermaLink="true">http://community.onion.io/topic/3615/omega2-gpio-irq-question</guid><dc:creator><![CDATA[Zerog]]></dc:creator><pubDate>Thu, 06 Jun 2019 09:38:22 GMT</pubDate></item><item><title><![CDATA[custom kernel]]></title><description><![CDATA[Did you mean this one? http://community.onion.io/topic/2830/building-kernel-modules-for-the-omega2
How does the kernel differ from just a fresh kernel from kernel.org? Devicetree settings etc.
What  I'm looking for is , grab kernelsource from kernel.org select correct devicetree and arch,
compile with cross compiler (mipsel-linux-musl) and create some sort of image to be programmed to the union
]]></description><link>http://community.onion.io/topic/3389/custom-kernel</link><guid isPermaLink="true">http://community.onion.io/topic/3389/custom-kernel</guid><dc:creator><![CDATA[gearloose -]]></dc:creator><pubDate>Wed, 23 Jan 2019 18:49:39 GMT</pubDate></item><item><title><![CDATA[Custom kernel .config options - best practice?]]></title><description><![CDATA[<p dir="auto">What is the best way to maintain your own kernel .config options?</p>
<p dir="auto">I recently added an RTC (DS3231) which involves adding RTC support and driver to the O2+ kernel.</p>
<p dir="auto">Currently I hacked a couple of scripts which I can run after resetting the config files with <code>git</code>. These set the necessary options manually in both the kernel and package config files, but is there a better (proper?) way to do this?</p>
<p dir="auto">Probably the different options should be set manually after running <code>make menuconfig</code>? But I don't know if the resulting .config file (after <code>make menuconfig</code> and saving .config) will build the same kernel as the one built with the .config from the Onion source repo. I'm doubtful that it will.</p>
<p dir="auto">fwiw, here are the scripts I wrote in case anyone else finds them useful. I did some light testing, so <strong>use at own risk</strong>:</p>
<pre><code>set-kerneloptions-RTCds1307.sh
#! /bin/sh

setoption() {
 local loption=$1
 local lstate=$2
 local lconfigfile=$3

 grep "${loption}\(=\| \)" ${lconfigfile} &gt; /dev/null
 if [ $? -eq 0 ]; then
  # set it to the required value
  echo -n Set: ${loption}
  sed -i -r "s/^(${loption}=.*|# ${loption} is not set)/${loption}=${lstate}/" ${lconfigfile}
 else
  # Add the option
  echo -n Add: ${loption}
  echo "${loption}=${lstate}" &gt;&gt; ${lconfigfile}
 fi
 echo " Now: `grep "${loption}\(=\| \)" ${lconfigfile}`"
}

unsetoption() {
 local loption=$1
 local lconfigfile=$2

 grep "${loption}\(=\| \)" ${lconfigfile} &gt; /dev/null
 if [ $? -eq 0 ]; then
  # set it to the required value
  echo -n Unset: ${loption}
  sed -i -r "s/^(${loption}=.*)/# ${loption} is not set/" ${lconfigfile}
 else
  # Add the option
  echo -n Add: ${loption}
  echo "# ${loption} is not set" &gt;&gt; ${lconfigfile}
 fi
 echo " Now: `grep "${loption}\(=\| \)" ${lconfigfile}`"
}

CONFIGFILE="target/linux/ramips/mt7688/config-4.4"

for configoption in CONFIG_RTC_CLASS \
                        CONFIG_RTC_DRV_DS1307 \
                        CONFIG_RTC_SUPPORT
do
 setoption "${configoption}" "y" "${CONFIGFILE}"
done

unsetoption "CONFIG_RTC_HCTOSYS" "${CONFIGFILE}"
</code></pre>
<p dir="auto">Execution is as follows:</p>
<pre><code>root@122126d368fa:~/source# git checkout target/linux/ramips/mt7688/config-4.4
root@122126d368fa:~/source# ./set-kerneloptions-RTCds1307.sh
Add: CONFIG_RTC_CLASS Now: CONFIG_RTC_CLASS=y
Add: CONFIG_RTC_DRV_DS1307 Now: CONFIG_RTC_DRV_DS1307=y
Add: CONFIG_RTC_SUPPORT Now: CONFIG_RTC_SUPPORT=y
Add: CONFIG_RTC_HCTOSYS Now: # CONFIG_RTC_HCTOSYS is not set
root@122126d368fa:~/source#
</code></pre>
<pre><code>set-packages-RTCds1307.sh
#! /bin/sh

setoption() {
 local loption=$1
 local lstate=$2
 local lconfigfile=$3

 grep "${loption}\(=\| \)" ${lconfigfile} &gt; /dev/null
 if [ $? -eq 0 ]; then
  # set it to the required value
  echo -n Set: ${loption}
  sed -i -r "s/^(${loption}=.*|# ${loption} is not set)/${loption}=${lstate}/" ${lconfigfile}
 else
  # Add the option
  echo -n Add: ${loption}
  echo "${loption}=${lstate}" &gt;&gt; ${lconfigfile}
 fi
 echo " Now: `grep "${loption}\(=\| \)" ${lconfigfile}`"
}

unsetoption() {
 local loption=$1
 local lconfigfile=$2

 grep "${loption}\(=\| \)" ${lconfigfile} &gt; /dev/null
 if [ $? -eq 0 ]; then
  # set it to the required value
  echo -n Unset: ${loption}
  sed -i -r "s/^(${loption}=.*)/# ${loption} is not set/" ${lconfigfile}
 else
  # Add the option
  echo -n Add: ${loption}
  echo "# ${loption} is not set" &gt;&gt; ${lconfigfile}
 fi
 echo " Now: `grep "${loption}\(=\| \)" ${lconfigfile}`"
}

CONFIGFILE=".config"

for configoption in CONFIG_PACKAGE_kmod-i2c-core \
                        CONFIG_PACKAGE_kmod-i2c-algo-bit \
                        CONFIG_PACKAGE_kmod-i2c-gpio \
                        CONFIG_PACKAGE_kmod-i2c-gpio-custom \
                        CONFIG_PACKAGE_hwclock \
                        CONFIG_PACKAGE_i2c-tools \
                        CONFIG_PACKAGE_kmod-rtc-ds1307
do
 setoption "${configoption}" "y" "${CONFIGFILE}"
done
</code></pre>
<p dir="auto">Execution is as follows:</p>
<pre><code>root@122126d368fa:~/source# git checkout .config
root@122126d368fa:~/source# ./set-packages-RTCds1307.sh
Set: CONFIG_PACKAGE_kmod-i2c-core Now: CONFIG_PACKAGE_kmod-i2c-core=y
Set: CONFIG_PACKAGE_kmod-i2c-algo-bit Now: CONFIG_PACKAGE_kmod-i2c-algo-bit=y
Set: CONFIG_PACKAGE_kmod-i2c-gpio Now: CONFIG_PACKAGE_kmod-i2c-gpio=y
Set: CONFIG_PACKAGE_kmod-i2c-gpio-custom Now: CONFIG_PACKAGE_kmod-i2c-gpio-custom=y
Set: CONFIG_PACKAGE_hwclock Now: CONFIG_PACKAGE_hwclock=y
Set: CONFIG_PACKAGE_i2c-tools Now: CONFIG_PACKAGE_i2c-tools=y
Add: CONFIG_PACKAGE_kmod-rtc-ds1307 Now: CONFIG_PACKAGE_kmod-rtc-ds1307=y
root@122126d368fa:~/source#
</code></pre>
]]></description><link>http://community.onion.io/topic/3355/custom-kernel-config-options-best-practice</link><guid isPermaLink="true">http://community.onion.io/topic/3355/custom-kernel-config-options-best-practice</guid><dc:creator><![CDATA[cas]]></dc:creator><pubDate>Thu, 13 Dec 2018 10:25:17 GMT</pubDate></item><item><title><![CDATA[Weak WIFI signal causes device to hang]]></title><description><![CDATA[@Lazar-Demin Sorry, all I have is my own PCB or the power dock. My own PCB has an Ethernet port but that too stops working (the link LED on the switch I am connecting to is Off).
]]></description><link>http://community.onion.io/topic/3211/weak-wifi-signal-causes-device-to-hang</link><guid isPermaLink="true">http://community.onion.io/topic/3211/weak-wifi-signal-causes-device-to-hang</guid><dc:creator><![CDATA[Claude Robitaille]]></dc:creator><pubDate>Thu, 18 Oct 2018 00:37:14 GMT</pubDate></item><item><title><![CDATA[Error compiling the kernel]]></title><description><![CDATA[@Lazar-Demin Thank you! I'll try again.
]]></description><link>http://community.onion.io/topic/3149/error-compiling-the-kernel</link><guid isPermaLink="true">http://community.onion.io/topic/3149/error-compiling-the-kernel</guid><dc:creator><![CDATA[Lee James]]></dc:creator><pubDate>Mon, 01 Oct 2018 02:18:43 GMT</pubDate></item><item><title><![CDATA[Unable to find rootfs after kernel_menuconfig]]></title><description><![CDATA[<p dir="auto">In the pursuit to track down my SPI issues I've reconfigured my kernel to <em>not</em> include the mt7621 SPI HW driver.</p>
<p dir="auto">The patch to the <code>.config</code> is almost trivially simple:</p>
<pre><code>diff --git a/target/linux/ramips/mt7688/config-4.4 b/target/linux/ramips/mt7688/config-4.4
index c4a844da38..6fc9a91e6d 100644
--- a/target/linux/ramips/mt7688/config-4.4
+++ b/target/linux/ramips/mt7688/config-4.4
@@ -225,8 +225,11 @@ CONFIG_SOC_MT7620=y
 # CONFIG_SOC_RT3883 is not set
 CONFIG_SOUND=m
 CONFIG_SPI=y
+CONFIG_SPI_BITBANG=y
+CONFIG_SPI_DEBUG=y
+CONFIG_SPI_GPIO=y
 CONFIG_SPI_MASTER=y
-CONFIG_SPI_MT7621=y
+# CONFIG_SPI_MT7621 is not set
 # CONFIG_SPI_RT2880 is not set
 CONFIG_SRCU=y
 CONFIG_SWCONFIG=y
</code></pre>
<p dir="auto">Building a new image works fine, but the resulting image -somehow- is not booting. I did not touch anything other that the patch above. Here is the kernel boot output deemed important:</p>
<pre><code>[    0.000000] Kernel command line: console=ttyS0,115200 rootfstype=squashfs,jffs2
</code></pre>
<p dir="auto"><em><strong>**snip**</strong></em></p>
<pre><code>[    0.435122] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    0.442720] Please append a correct "root=" boot option; here are the available partitions:
[    0.451254] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.460532] Rebooting in 1 seconds..
</code></pre>
<p dir="auto">Seemingly the kernel is not correctly pointed towards the rootfs. Isn't it u-boot's job to inform the kernel of the whereabouts of the rootfs and the layout of the MTD main storage device?</p>
<p dir="auto">Me not (yet :)) being an OpwnWRT/Buildroot expert, it's probably something trivial I'm overlooking here. Any handles anyone?</p>
]]></description><link>http://community.onion.io/topic/3144/unable-to-find-rootfs-after-kernel_menuconfig</link><guid isPermaLink="true">http://community.onion.io/topic/3144/unable-to-find-rootfs-after-kernel_menuconfig</guid><dc:creator><![CDATA[Rogier Lodewijks]]></dc:creator><pubDate>Sun, 16 Sep 2018 11:56:33 GMT</pubDate></item><item><title><![CDATA[Yocto support]]></title><description><![CDATA[For anyone with this problem, the switch must be configured before bringing up eth0.
These commands are needed for everything to work:
swconfig dev switch0 set reset 1
swconfig dev switch0 set enable_vlan 0
swconfig dev switch0 set apply 1

Cheers!
]]></description><link>http://community.onion.io/topic/2944/yocto-support</link><guid isPermaLink="true">http://community.onion.io/topic/2944/yocto-support</guid><dc:creator><![CDATA[João Oliveira]]></dc:creator><pubDate>Wed, 06 Jun 2018 16:17:47 GMT</pubDate></item><item><title><![CDATA[Building Kernel Modules for the Omega2]]></title><description><![CDATA[@Maximilian-Gerhardt I believe we both Geophoenixed in the early 2000's. Thanks for the article, it helped me migrate a water heater control unit to a newer linux kernel (with MMU)
]]></description><link>http://community.onion.io/topic/2830/building-kernel-modules-for-the-omega2</link><guid isPermaLink="true">http://community.onion.io/topic/2830/building-kernel-modules-for-the-omega2</guid><dc:creator><![CDATA[Tony Gutierrez]]></dc:creator><pubDate>Tue, 02 Jul 2019 19:29:35 GMT</pubDate></item><item><title><![CDATA[Wifi not working after building customized image]]></title><description><![CDATA[@Nick-Garner
We run some commands to setup the environment, that you can see in our Dockerfile. It in turn, runs the onion-feed-setup.sh script to setup our feeds. We then rely on the build system configuration that's stored in .config.
If it seems that your build system configuration isn't matching the firmware that we build, it might be because when ./scripts/feeds  is run, it overwrites the .config file. To remedy this, you can just run git checkout .config (assuming you're using our github repo or docker image).
As for packages failing to build, we've seen this happen as well but only when running our Docker image on a windows machine. If the Docker image is running on Linux or Mac, there's no issues. (Haven't had the cycles to figure out why it doesn't play nice with Windows)
]]></description><link>http://community.onion.io/topic/2755/wifi-not-working-after-building-customized-image</link><guid isPermaLink="true">http://community.onion.io/topic/2755/wifi-not-working-after-building-customized-image</guid><dc:creator><![CDATA[Lazar Demin]]></dc:creator><pubDate>Tue, 03 Jul 2018 15:09:15 GMT</pubDate></item><item><title><![CDATA[Best practice for firmware and kernel updates?]]></title><description><![CDATA[@Douglas-Kryder all great information, thank you. Your guess of a new wifi driver release seems realistic. If it doesn't arrive by July (which would be nearly 1 year late) then it probably won't ever come. I'll start testing the official lede builds with Onion packages and report back my findings.
]]></description><link>http://community.onion.io/topic/2750/best-practice-for-firmware-and-kernel-updates</link><guid isPermaLink="true">http://community.onion.io/topic/2750/best-practice-for-firmware-and-kernel-updates</guid><dc:creator><![CDATA[Steve Veerman]]></dc:creator><pubDate>Wed, 28 Feb 2018 16:29:22 GMT</pubDate></item><item><title><![CDATA[Messed up the kernel, how to recover?]]></title><description><![CDATA[@Anupam-Bakshi
Good news, glad to hear that.
Happy hacking. 
]]></description><link>http://community.onion.io/topic/2687/messed-up-the-kernel-how-to-recover</link><guid isPermaLink="true">http://community.onion.io/topic/2687/messed-up-the-kernel-how-to-recover</guid><dc:creator><![CDATA[cas]]></dc:creator><pubDate>Sun, 28 Jan 2018 09:13:46 GMT</pubDate></item><item><title><![CDATA[Problem building staging drivers (fbtft)]]></title><description><![CDATA[<p dir="auto">I downloaded the source code from here <a href="https://github.com/OnionIoT/source" rel="nofollow">https://github.com/OnionIoT/source</a></p>
<p dir="auto">make menuconfig<br />
and selected the required options</p>
<p dir="auto">I also configured the kernel to load the staging drivers</p>
<p dir="auto">make kernel_menuconfig</p>
<p dir="auto">Device drivers -&gt; Graphics support -&gt; Frame buffer Devices -&gt; Support for frame buffer devices<br />
Device drivers -&gt; Staging drivers -&gt; Support for small TFT LCD display modules</p>
<p dir="auto">&lt;M&gt; FB driver for the ST7735R LCD Controller<br />
&lt;M&gt; Generic FB driver for TFT LCD displays<br />
&lt;M&gt; Module to for adding FBTFT devices</p>
<p dir="auto">make -j5 V=s</p>
<p dir="auto">I flashed the Omega with the bin generated.</p>
<p dir="auto">sysupgrade -n lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin</p>
<p dir="auto">But when is time to use the module, it doesn't work, I've tried all of this:</p>
<p dir="auto">insmod fb_defio<br />
insmod fb<br />
insmod fbtft</p>
<p dir="auto">modeprobe fbtft</p>
<p dir="auto">fbtft_device</p>
<p dir="auto">and nothing works, I don't think the module is correctly configured<br />
Am I missing something?</p>
]]></description><link>http://community.onion.io/topic/2568/problem-building-staging-drivers-fbtft</link><guid isPermaLink="true">http://community.onion.io/topic/2568/problem-building-staging-drivers-fbtft</guid><dc:creator><![CDATA[Cesar Gutierrez]]></dc:creator><pubDate>Thu, 14 Dec 2017 03:48:52 GMT</pubDate></item><item><title><![CDATA[Omega2 Virtual Machine]]></title><description><![CDATA[@Chris-Georgiev
An Emulator for MT7688 Development
This is an open source emulator of an Omega2+ like board.
They are Chinese - in a Chinese community - so they are mostly write Chinese language - I think. 
]]></description><link>http://community.onion.io/topic/2028/omega2-virtual-machine</link><guid isPermaLink="true">http://community.onion.io/topic/2028/omega2-virtual-machine</guid><dc:creator><![CDATA[György Farkas]]></dc:creator><pubDate>Sun, 07 May 2017 14:48:43 GMT</pubDate></item><item><title><![CDATA[fail to install shadowsocks-libev]]></title><description><![CDATA[<p dir="auto">Installing shadowsocks-libev (2.6.1-1) to root...<br />
Downloading <a href="http://downloads.lede-project.org/snapshots/packages/mipsel_24kc/packages/shadowsocks-libev_2.6.1-1_mipsel_24kc.ipk" rel="nofollow">http://downloads.lede-project.org/snapshots/packages/mipsel_24kc/packages/shadowsocks-libev_2.6.1-1_mipsel_24kc.ipk</a><br />
Collected errors:</p>
<ul>
<li>satisfy_dependencies_for: Cannot satisfy the following dependencies for shadowsocks-libev:</li>
<li>kernel (= 4.4.59-1-20e24470450440309f80ab6bf0a84eb9) * 	kernel (= 4.4.59-1-20e24470450440309f80ab6bf0a84eb9) * 	kernel (= 4.4.59-1-20e24470450440309f80ab6bf0a84eb9) *</li>
<li>opkg_install_cmd: Cannot install package shadowsocks-libev.</li>
</ul>
]]></description><link>http://community.onion.io/topic/1947/fail-to-install-shadowsocks-libev</link><guid isPermaLink="true">http://community.onion.io/topic/1947/fail-to-install-shadowsocks-libev</guid><dc:creator><![CDATA[james lee]]></dc:creator><pubDate>Tue, 11 Apr 2017 15:45:57 GMT</pubDate></item><item><title><![CDATA[Omega2+: Kernel failure]]></title><description><![CDATA[@György-Farkas That's the thing, I tried various images, every one of which gave the same error log.
The omega-v0.1.5-b128.bin was the last one I tried prior to posting here.
I already tried the omega2p-v0.1.10-b160.bin image (and checked the hash to make sure), with the same result.
I will try again when I'm free though.
Edit: still the same result after trying again but with different "magic number":
## Booting image at bc050000 ...
Bad Magic Number,032DA956

]]></description><link>http://community.onion.io/topic/1833/omega2-kernel-failure</link><guid isPermaLink="true">http://community.onion.io/topic/1833/omega2-kernel-failure</guid><dc:creator><![CDATA[William Thenaers]]></dc:creator><pubDate>Thu, 23 Mar 2017 20:03:20 GMT</pubDate></item></channel></rss>