I am successfully using 6.0.2-rc1 on both Soekris net 4801 and 6501 boxen.
The 486 version on the 4801 seems very sensitive to non-Unix EOF in
leaf.cfg. Needs to be LF not Windows style CR LF. I have had boot problems
until I converted to LF. This may not be your problem but it's worth a try
to
Edfleco asked:
> However, I am still wondering which version of Bering-uClibc I want to use?
For Soekris net4501 I would presume a 486 serial version. See
https://sourceforge.net/projects/leaf/files/Bering-uClibc/5.2.8/Bering-uClibc_5.2.8_i486_syslinux_serial19200.tar.gz/download
or
I upgraded two Soekris boxen, a net4801 and net6501, to 6.0
On the net4801, I was using both a compact flash (boot) and an external usb
thumb drive (mass storage) , /dev/sda1 and /dev/sdb1 respectively. After
the upgrade, these were swapped. Other than a little confusion on my part
while I
un 4, 2016 at 10:29 AM, kp kirchdoerfer <
kap...@users.sourceforge.net> wrote:
> HI Timothy;
>
> Am Freitag, 3. Juni 2016, 18:58:09 schrieb Timothy Wegner:
> > I have a LEAF router on a Soekris box.
> >
> > LEAF Bering-uClibc 5.2.6-rc1 works perfectly. Bu
wrote:
> On 6/3/2016 4:58 PM, Timothy Wegner wrote:
> > I have a LEAF router on a Soekris box.
> >
> > LEAF Bering-uClibc 5.2.6-rc1 works perfectly. But 5.2.6 does not.
> Shorewall
> > complains that it can't get an ip and won't start, and the boot messages
> > just b
I have a LEAF router on a Soekris box.
LEAF Bering-uClibc 5.2.6-rc1 works perfectly. But 5.2.6 does not. Shorewall
complains that it can't get an ip and won't start, and the boot messages
just before shorewall runs indicate that an ipv6 ip was obtained but not
ipv4. After boot, the ip addr show
I tested Bering-uClibc_5.2.4-rc1_i486_syslinux_serial19200.tar.gz on a
Soekris net4801 used as a small web server
and Bering-uClibc_5.2.4-rc1_x86_64_syslinux_serial115200.tar.gz on a
Soekris 6501 used as a router and had no problems at all.
Tim
I upgraded a Soekris net6501 box used as a router with
Bering-uClibc_5.2.3_x86_64_syslinux_vga.tar.gz (configured as serial) and
it worked great. I had also tried rc1 (I know the team wants testing of
release candidates) but alas in the midst of holiday travel I neglected to
report that it worked
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
what is set
> for the kernel boot line in syslinux.cfg (115200 IIRC these days whereas
> it used to be 19200 in older versions).
> If you change it for the kernel bear in mind it’s also set (separately)
> for the
> login prompt in /etc/inittab
>
> dMb
>
>
> >
ppily test it at the first
opportunity. Meanwhile, the 486 variant of LEAF Bering-uClibc 5.2 works
perfectly on the Soekris net4801.
Thanks,
Tim
On Fri, Nov 20, 2015 at 4:34 PM, Erich Titl <erich.t...@think.ch> wrote:
> Hi Timothy
>
> Am 19.11.2015 um 16:17 schrieb Timothy Wegner
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
Here are some clues.
Boot messages:
[ 31.899909] softdog: disagrees about version of symbol module_layout
[ 31.948511] llc: disagrees about version of symbol module_layout
[ 31.994855] ifb: disagrees about version of symbol module_layout
[ 32.041640] act_police: disagrees about version of
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 symbol module_layout
> > [ 31.948511] llc: disagrees about versi
200.tar.gz, the same
as I always have for earlier versions. Have the kernel compile options
changed?
Thanks,
Tim
On Wed, Nov 18, 2015 at 6:06 PM, Timothy Wegner <t...@tswegner.net> wrote:
> Thanks Andrew!
>
> I did discover a big old modules tgz file left from before th
Victor wrote:
> Upgrading to LEAF 5.2 on a pc engines geode was simple and painless. I
> just copied the files, the old leaf.cfg and old configdb file and
> booted.
I had exactly the same painless upgrade experience as Victor on a
Soekris 6501. Just kept the old leaf.cfg and configdb file and
Timothy Wegner:
I have encountered a small Shorewall issue after upgrading from
Bering-uClibc_5.1.3-beta1 to 5.1.3-rc1. I'm using my Bering Soekris
box as a firewall/router that gets it's IP from Comcast via DHCP. I am
running the Bering-uClibc_5.1.3-rc1_x86_64_syslinux_vga.tar.gz version
modified
cope with dhcpcd's background, the
pragmatic answer is that Leaf's dhcpcd and shorewall package defaults
should be compatible.
On Tue, Jan 20, 2015 at 5:19 PM, Erich Titl erich.t...@think.ch wrote:
Hi
Am 20.01.2015 um 17:30 schrieb Timothy Wegner:
Hi kp,
You were exactly right! As you
I have encountered a small Shorewall issue after upgrading from
Bering-uClibc_5.1.3-beta1 to 5.1.3-rc1. I'm using my Bering Soekris
box as a firewall/router that gets it's IP from Comcast via DHCP. I am
running the Bering-uClibc_5.1.3-rc1_x86_64_syslinux_vga.tar.gz version
modified to use the
kp wrote:
Most probably it's the ehci-pci module (ehci-pci.ko.gz) which is missing.
It
This worked with Bering-uClibc_5.1.1-rc1! Thanks! My Soekris net6501 now
runs Bering-uClibc_5.1.1-rc1 like a champ!
While I am perfectly happy to manually add ehci-pci.ko.gz initmod.lrp as
needed in the
David wrote:
If you do press Enter to activate this console are you able to mount the
USB drive manually? If not then it is probably a Driver (i.e. missing
Module) issue; if you can always mount it manually then it's normally a
timing issue, and usb_wait should help. You might need usb_wait=4
David wrote:
I guess take a look at the output from 'lsmod' on your working system and
compare with what you get after the press Enter prompt.
lsmod of course reports a boatload of modules that are loaded later after
a successful boot process. So I renamed leaf.cfg to leaf.not so the good
Jürgen wrote:
syslinux.cfg is not enough. To put a getty on a serial line, you need inittab
too.
Of course you are right. I have the appropriate lines in inittab. Probably I
picked them up by re-using a configdb.lrp from a serial version of Leaf. I
appreciate the tip about re-using a
Thanks kp and Juergen for responding.
kp wrote:
Have you tried to add
usb_wait=3
the APPEND line in syslinux.cfg?
Yes, but no luck. I should add that I *did* successfully upgrade an older and
much slower Soekris net4801 box to 5.1 with no problems. So I am not surprised
that usb wait=3
Jurgen wrote:
have you upgraded your older 4801 box to version 5.1 with the geode image or
also with the Bering-uClibc_5.1_x86_64_syslinux_vga.tar.gz
No, I have always used the 486 image
(Bering-uClibc_5.1_i486_syslinux_serial.tar.gz) with the older 4801. I should
add I tried the 486
I can upgrade my Soekris 6501 box from 5.04 to 5.05. I can also
upgrade a Soekris 4801 to 5.1. But I have been unable to upgrade the
Soekris 6501 to Leaf 5.1. I get an error similar to the one mentioned
in the Wiki:
QUOTE
LINUXRC: Switch_root into newfs...
can't run '/etc/init.d/rcS': No such
I have run versions of lrp/leaf dating back more than a decade on a variety of
hardware. Recently I ported my router setup with the latest uclibc version from
a Soekris net4801 to a Soekris net6501 in order to accommodate more bandwidth.
The new box has an extra port. My question is how to use
Victor,
(Victor, Sorry you got duplicates, I meant to send this to the list the first
time because it might help others.)
I had already gotten the inittab change, but what I learned after posting the
message by searching the list archives for serial is that there are several
files named
28 matches
Mail list logo
