[Freedombox-discuss] New images available for testing
Am Dienstag, den 07.02.2017, 19:15 -0500 schrieb James Valleroy:
> On 02/07/2017 11:35 AM, sagen at permondes.de wrote:
> > Mmh, I will try again end of the week.
> >
> > I understood the initial set up is a 2 step process. Can I check if it
> > did the first step before the reboot?
> > How long did it take for you before you saw the device in the network?
> >
> > Dietmar
>
> Yes, during first boot it should write to /var/log/freedombox-first-run.log.
>
> I didn't check how long it took. I just plugged it in and then check it
> about 20 minutes later. (But I expect it shouldn't take more than 5
> minutes.)
>
> --
> James
I wrote the image again to the ?SD card, inserted it in the LIME and
booted it up. Then I waited for about 50 minutes. I still could not
access it, nor did it appear in nmap or in the router.
In var/log/ I have these files:
> -rw-r--r-- 1 root root 11433 Feb 3 05:06 alternatives.log
> drwxr-x--- 1 root adm 84 Feb 3 05:06 apache2
> drwxr-xr-x 1 root root 60 Feb 3 05:08 apt
> -rw-r--r-- 1 root root 51860 Feb 3 05:00 bootstrap.log
> -rw------- 1 root utmp 0 Feb 3 04:49 btmp
> -rw-r--r-- 1 root root 294279 Feb 3 05:08 dpkg.log
> -rw-r--r-- 1 root root 24024 Feb 3 05:08 faillog
> -rw-r--r-- 1 root root 8651 Feb 3 05:09 freedombox-setup.log
> -rw-r--r-- 1 root root 16056 Feb 3 05:08 hardware-setup.log
> -rw-rw-r-- 1 root utmp 292292 Feb 3 05:08 lastlog
> drwxr-xr-x 1 Debian-exim ssl-cert 0 Jan 28 12:58 ntpstats
> drwxr-xr-x 1 saned avahi 40 Feb 3 05:09 plinth
> drwxr-x--- 1 root adm 0 Dez 11 11:31 unattended-upgrades
> -rw-rw-r-- 1 root utmp 384 Nov 3 18:18 wtmp
As LIME2 and LIME are the same architecture, I am not sure what goes
wrong on my setup.
In freedombox-setup.log (no reedombox-first-run.log) ends with
> FreedomBox setup completed
>
If there are no ideas, I would try the LIME2 image.
Dietmar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/freedombox-discuss/attachments/20170209/00ee2f6d/attachment.html>
Reply to: