I am trying to upgrade my current firewall which is using LEAF Bering uClibc
3.x something. I'm taking things cautiously because I had read information
about changes with the 4.x version, especially around Shorewall, so I wanted to
take things slowly and not put myself into huge hole of
On 4/11/2012 7:32 AM, Brad Klinghagen wrote:
I am trying to upgrade my current firewall which is using LEAF Bering uClibc
3.x something. I'm taking things cautiously because I had read information
about changes with the 4.x version, especially around Shorewall, so I wanted
to take things
I downloaded the file Bering-uClibc_4.1_geode_syslinux_ser.tar.
The above tar file will redirect all output to /dev/ttyS0 (aka
COM1:DB-9) serial ports (See page 12 of your AR-B1554 User's Guide). You
need to use a null modem cable and attach the other end to a Linux
console using minicom or
On 11 Apr 2012, at 19:12, n22e113 wrote:
I downloaded the file Bering-uClibc_4.1_geode_syslinux_ser.tar.
The above tar file will redirect all output to /dev/ttyS0 (aka
COM1:DB-9) serial ports (See page 12 of your AR-B1554 User's Guide). You
need to use a null modem cable and attach the
Well at least I know I was trying the right things. Thank you for your
contributions. I really do appreciate the assistance. Each of the suggestions
by David, Kwon, and Victor were the things I tried; thinking similar to what
you indicated in your emails. I tried the serial connection first;
Okay, I just tried another attempt. I kept the Geode based initrd.lrp, but
removed the part of the APPEND line indicating the serial port, REMOVED the
configdb.lrp file, and then added the libata.dma=3 into the APPEND statement.
It boots up. Thanks again.
Now that it is booting, can I just
On 4/11/2012 19:16, Brad Klinghagen wrote:
Now that it is booting, can I just copy the moddb.lrp and configdb.lrp from
my existing production device (BuC 3.x) to this test device to establish
the configuration (wanted to keep the same setup). I assume, even if I copy
those *.lrp files, I'll
