You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After doing an update to the actual version 1.1.6 of fabUI from sdcard_latest my fabulous
red FABTOTUM doesn't come up from the attempt to run the first boot:
The I/F announces bootin' in 1 second, LEDs are blue, the colibri is flapping
eagerly, but that's it. No question, the printer is working with the previous
version, booting after a short beep and 32 flashes of white. But after the
update the one second message needs a philosophic interpretation.
I've checked the SDC, the hash of the file(s), tried the whole procedure
several times, no and no and not working. Did a firmware-update using the old
booting version an tried again. Used a new SDC and again:
A starving colibri (there is no blossom where it can feed) and a Fabtotum in
blue light.
Turning off the machine and checking the SDC on a laptop if there are logs giving a
clue what's keeping the hardware from booting properly did not show any:
no logs written.
So the SDC back into the Raspi and a monitor attached to see what is going on.
And there it is:
[80.971491] kernel panic - not syncing: Attempt to kill init!
exitcode = 0x00007e00 ...
[80.980105] CPU: 0 PID: 1 Comm: init Not tainted 4.4.38V6#1
[80.983170] Hardware name : BCM2708
The hardware this should be running on is this:
S-# EDBDB-FAB-2B3D2
Os Linux mahofab 4.4.38-v6 #1 armv6l GNU/Linux
Then I checked the same procedure on a Rasberry Pi 3B V1.2
Here it crashes too with Kernel Panic, but for BCM2709.
There seems to be a problem...
After doing an update to the actual version 1.1.6 of fabUI from sdcard_latest my fabulous
red FABTOTUM doesn't come up from the attempt to run the first boot:
The I/F announces bootin' in 1 second, LEDs are blue, the colibri is flapping
eagerly, but that's it. No question, the printer is working with the previous
version, booting after a short beep and 32 flashes of white. But after the
update the one second message needs a philosophic interpretation.
I've checked the SDC, the hash of the file(s), tried the whole procedure
several times, no and no and not working. Did a firmware-update using the old
booting version an tried again. Used a new SDC and again:
A starving colibri (there is no blossom where it can feed) and a Fabtotum in
blue light.
Turning off the machine and checking the SDC on a laptop if there are logs giving a
clue what's keeping the hardware from booting properly did not show any:
no logs written.
So the SDC back into the Raspi and a monitor attached to see what is going on.
And there it is:
[80.971491] kernel panic - not syncing: Attempt to kill init!
exitcode = 0x00007e00 ...
[80.980105] CPU: 0 PID: 1 Comm: init Not tainted 4.4.38V6#1
[80.983170] Hardware name : BCM2708
The hardware this should be running on is this:
S-# EDBDB-FAB-2B3D2
Os Linux mahofab 4.4.38-v6 #1
armv6l GNU/Linux
Then I checked the same procedure on a Rasberry Pi 3B V1.2
Here it crashes too with Kernel Panic, but for BCM2709.
Working OLD version:
NAME=Colibri
VERSION=2015.02-g510372e-dirty
ID=colibri
VERSION_ID=2015.02
PRETTY_NAME="Colibri 2015.02"
So I had to revert to this version. Better accept minor bugs than having a Fabtotum not booting at all ;-)
BTW.:
In webui.tar, indx.html line 165 should read
please instead of plaese
HTH
The text was updated successfully, but these errors were encountered: