Thanks kp for the explanation UPDATE_MODDB. In my case I leave Leaf running
24/7 on very low power machines and have plenty of space, so I will
set UPDATE_MODDB=false, and also change my standard update procedure. In
the past I always ran the "Find & load modules for hardware" from lrcfg and
then "
Hi Timothy, hi all;
Am Montag, 23. November 2015, 19:11:54 schrieb Timothy Wegner:
> I have tested both the x86x64 and 486 versions of 5.2.2 that came out
> yesterday on, respectively, Soekris net6501 (router with dmz) and net4801
> (tiny web server) boxen and this time both worked fine. (For 5.2.
I have tested both the x86x64 and 486 versions of 5.2.2 that came out
yesterday on, respectively, Soekris net6501 (router with dmz) and net4801
(tiny web server) boxen and this time both worked fine. (For 5.2.1 as we
now know, the 486 version had been compiled incorrectly and did not work on
the So
Am 23.11.2015 um 19:40 schrieb Robert K Coffman Jr. -Info From Data Corp.:
> > On 11/21/2015 1:14 PM, Erich Titl wrote:
>> We hope that
>> from this release the box will be able to upgrade itself
>
> This is the best news I've had all year!
Christmas is coming :-)
We are looking for testers all
> On 11/21/2015 1:14 PM, Erich Titl wrote:
> We hope that
> from this release the box will be able to upgrade itself
This is the best news I've had all year!
- Bob Coffman
--
Go from Idea to Many App Stores Faster with
Am Samstag, 21. November 2015, 12:43:52 schrieb Timothy Wegner:
> David,
>
> You are right about baud rate and screen garbage of course. Even though I
> know about the baud rate issue and the idea that the garbage might mean the
> wrong baud rate entered my head, I'm embarressed to say that I didn
David,
You are right about baud rate and screen garbage of course. Even though I
know about the baud rate issue and the idea that the garbage might mean the
wrong baud rate entered my head, I'm embarressed to say that I didn't
investigate quite enough.
However, no love. With the baud rate fixed,
Hi Tim,
Just a hunch, but “garbage” after the BIOS prompt is a classic symptom of
a baud rate mis-match on the serial console.
Might be worth checking what your terminal it set to use versus what is set
for the kernel boot line in syslinux.cfg (115200 IIRC these days whereas
it used to be 19200 i
Hi Timothy
Am 21.11.2015 um 18:37 schrieb Timothy Wegner:
> Erich,
>
> You are correct that the Soekris net4801 has a Geode CPU (boot screen
> says CPU Geode SC1100 267 Mhz). However, in the past I never got the Leaf
> Geode version to work, and when I tried it just now, I just got garbage on
> t
Erich,
You are correct that the Soekris net4801 has a Geode CPU (boot screen
says CPU Geode SC1100 267 Mhz). However, in the past I never got the Leaf
Geode version to work, and when I tried it just now, I just got garbage on
the screen after the bios message.
I searched the mailing lists and fou
Hi Timothy
Am 19.11.2015 um 16:17 schrieb Timothy Wegner:
> Hi Erich,
>
> I solved the problem you quoted - it was due to an old modules tgz file
> I had not cleaned off the compact flash. Andrew's note helped solve it.
>
> However I have another very different problem on a Soekris net4801 that
Kp wrote:
>>
It has been changed by accident and I've messed it up, sorry.
The i486 flavour is in fact a i686 kernel.
We've tried to fix this today and will require some time to verify, but if
all
goes well, you can expect a new version over the weekend.
>>
Certainly no need to apologise, and fo
Hi Timothy;
Am Mittwoch, 18. November 2015, 22:59:41 schrieb Timothy Wegner:
> Andrew or anyone,
>
> I am also having a problem upgrading from LEAF Bering-uClibc 5.2 to 5.2.1
> on a Soekris net4801. Boot fails immediately with the message:
>
> "This kernel requires the following features not pre
Andrew or anyone,
I am also having a problem upgrading from LEAF Bering-uClibc 5.2 to 5.2.1
on a Soekris net4801. Boot fails immediately with the message:
"This kernel requires the following features not present on the CPU: pae"
I am using Bering-uClibc_5.2.1_i486_syslinux_serial19200.tar.gz, th
Thanks Andrew!
I did discover a big old modules tgz file left from before that might have
been part of the problem. The timestamp was ok on modules.sqfs file. So I
deleted moddb.lrp and tried again. Everything was fine, so I executed
"Find and load modules for hardware" and "Backup modules" and r
Hi.
Please check modules.sqfs and moddb.lrp date on storage. It seems like
moddb.lrp isn't updated. If modules.sqfs is present on storage - just
delete moddb.lrp
18.11.2015 21:37, Timothy Wegner пишет:
> Here are some clues.
>
> Boot messages:
> [ 31.899909] softdog: disagrees about version of
16 matches
Mail list logo
