> It looks like a problem with the watchdog and not shorewall. Probably the
> watchdogtimer which ends at the time shorewall starts.
> Did you change /etc/modules on the running system or in the etc.lrp
> package? Please rename your configdb.lrp to configdb.bak and try again.
> (You can also change the etc/modules file in the configdb package)
> 
> Are you sure you used the wd1100 module from the latest kernel tarball?
> Only that one will understand parameters.

The wd1100.o I used is from Bering-uClibc_modules_2.4.33.tar.gz, which
is in the 3.0 beta 2 package on the leaf sourceforge site.  I get this
when I run 'tar tvfz' against the tarball.

-rw-r--r-- root/root      5316 2006-08-13 13:49 
2.4.33/kernel/drivers/char/wd1100.o

Is it possible it's the wrong file?  How big is one known to work?

I looked again at my modules.lrp package.  I was wrong about having
commented out the line installing wd1100.  So your explanation makes
sense: it's not shorewall's fault. I'm impressed, though, that the
timeout always catches shorewall at exactly the same point in its
startup sequence.

I'll rename configdb.lrp and try again -- though I'll have to wait until
my daughter can live without her 'net connection for a bit, just in case
I have to open up the box again. :-)

Thanks,

--Eric

> > I just tried installing Bering-uClibc_3.0-beta2 on a WRAP box and got
> > the device into an infinite reboot loop.  The last line printed to console
> >  before each reboot is:
> >
> > Compiling /etc/shorewall/rules...
> >
> >
> > I'll describe what I did as best I can remember.  And should note:
> > I've been running Bering uClibc on this WRAP box for two years, and on
> > a Soekris box for about three.  I put 3.0-beta1 on the Soekris without
> > problems, but hadn't tried on this box.  Bering-uClibc 2.4.2 is what it's
> > been running for a while.  It's fine now that I've restored it to 2.4.2:
> > not a hardware problem.
> >
> > * On my desktop, downloaded the .bin file, modules and initrd_ide.lrp
> > as well as some other packages from the sourceforge site.  Did this last
> > night, so I assume they were current.
> >
> > * Mounted the .bin file -o loop and extracted its contents.  Replaced
> > initrd.lrp with initrd_ide.lrp.  Edited /etc/inittab in etc.lrp for serial
> > console.  Extracted wd1100.o from the modules file.  scp'd all this to the
> > CF card on my WRAP box.
> >
> >
> > * On the WRAP box, moved the working files out of position and set up
> > the new ones.  Ran syslinux -s /dev/hda1.  Rebooted.
> >
> > * 3.0 beta 2 came up fine over serial console.  Via serial, I changed
> > hostname, set a password, and edited /etc/network/interfaces and turned on
> > dhcp in dnsmasq.  Edited modules.lrp to add natsemi and crc32 and to
> > remove softdog.  I saved this config and rebooted. Without wd1100 in place
> > I had to unplug to restart, but it came back
> > up with my changes having stuck.
> >
> > * Still on serial, I generated dropbear keys and restarted dropbear.
> > I was then able to get a DHCP address and connect via ssh from my
> > desktop so I stopped using the serial connection.
> >
> > * I tried loading wd1100 at the command line using the new parameters
> > in /etc/modules. 'wd1100 timeout=25 graceful=0'.  I got complaints about
> > the timeout param.  I then installed without parameters and IIRC it was
> > ok.  I added the wd1100 to moddb.lrp, enabled the 'wd1100 timeout=25
> > graceful=0' line in /etc/modules and backed up everything then rebooted.
> >
> > * That put me into an infinite loop, with shorewall crashing (I
> > assume) and rebooting the device.  I pulled the CF card out of the device
> > and fixed /etc/modules, first removing the parameters to wd1100 and, when
> > that didn't help, removing wd1100 altogether. Neither of these helped.
> > Though I *think* I've gone back to a state
> > that was working, clearly I haven't.
> >
> > Is there anything I can do to help debug this?  I'm ok with running
> > 2.4.2 for a while, but would love to help track this down.  The -C
> > option to minicom lets me log serial output, so perhaps I can turn on more
> > verbose logging in shorewall?
> >
> > Note, though: I made no changes to shorewall.lrp!
> >
> >
> > Thanks,
> >
> >
> > --Eric
> > --
> > **************************************************************************
> > ****
> > * From the desktop of: Eric House, [EMAIL PROTECTED]
> > *
> > *        Crosswords 4.1.4 for PalmOS now ARM-native:
> > xwords.sourceforge.net  *
> > *************************************************************************
> > *****

-- 
******************************************************************************
* From the desktop of: Eric House, [EMAIL PROTECTED]                        *
*        Crosswords 4.1.4 for PalmOS now ARM-native: xwords.sourceforge.net  *
******************************************************************************

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Reply via email to