Mike Holden wrote:
> Tom Metro wrote:
>> Checking your server logs for the TFTP server.
>
> Try as I might, I still haven't found a log file from tftp!
It logs to syslog. Which file it ends up in depends on your syslog
configuration. On Debian derived systems it is daemon.log. Grep your log
directory for tftp and you should find it.
> I noticed I had commented out the filename entry at some point while
> trying to get the box to boot at all, this on the advice of more than
> one web page saying that the filename and option lines weren't
> necessary.
The rcS file really should be modified to supply a default dongle file
name, so that specifying it via DHCP is only necessary if you want to
override the default. (Similarly, other changes should be made so it
doesn't depend on the boot server being specified via DHCP.)
I'm assuming the reason why it is coded the way it is is to accommodate
users who don't use TFTP to load the startup script. For those users,
the useless TFTP retrieval attempt just delays the boot process.
>> tftp -g -l /etc/dongle.config -r ${DONGLE}.config ${SERVER}
>
> This failed with a message telling me than "Only absolute filenames are
> allowed".
There's a command line switch for the tftp server that tells it to
assume all paths are relative to your specified boot directory. I'd
recommend using it.
> This time, it read the config file in and all was well.
> So, thanks for your help Tom, I now have a box booting up with my custom
> config, and able to play music etc.
You're welcome. Glad you were able to resolve the problem.
> Once I've had a bit more experience with this unit I hope to be able to
> contribute in some way. I will certainly look to add some notes to the
> wiki sometime soon, maybe after I'm a little more familiar with it all.
Adding these troubleshooting steps to an appropriate location would be a
help.
> I think the main moral of this, at least from my own experience so far, is
> that information is sparsely spread around lots of places, and some of it
> is presented as universal, when in fact it pertains to only one or two
> versions of the box. It is also somewhat incomplete, especially for later
> models.
On my wishlist is a project to reorganize all the HOWTOs on the wiki.
Splitting them up into documents that cover just the installation of a
specific component on a particular platform. Then tying them all
together into a menu structure, so you can pick your platform, then
follow links for the components you have chosen to install.
Help on accomplishing this would be welcome.
-Tom
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/
