Thanks for your response, Sunil.
My method was to install debian (jessie) using the instructions here:
https://github.com/ssinyagin/pcengines-apu-debian-cd, upgrade it to
"testing" and then install freedombox-setup.
Your questions led me back to my notes, and I see that I did have errors
On 01/07/2017 05:43 AM, Jonas Smedegaard wrote:
[...]
>> So it is still booting the 4.3 kernel, which is unknown to aptitude.
>
> Seems your hardware is ARM-based. Commonly ARM-based hardware need the
> package flashkernel to copy installed kernel + initramfs to the
> different
On 01/07/2017 10:43 AM, Aaron Ferrucci wrote:
[...]
> This shows that apache is running, and would serve up the admin page
> to anything that could connect.
>
> So it seems I'm having a firewall or other connectivity issue, and I
> had
[...]
You are right about the firewall issue. It appears
I'm setting up an APU1D4 with freedombox, and I've hit a snag. I'm unable
to access the plinth config page from another computer on the same LAN. I
browsed the mailing list archives, and found this thread:
"[Freedombox-discuss] Need help with getting start", back in Nov 2015. The
problem described
Quoting permondes - sagen (2017-01-06 22:54:29)
> Am Freitag, den 06.01.2017, 20:25 +0100 schrieb permondes - sagen:
>
> > Am Freitag, den 06.01.2017, 18:41 +0100 schrieb permondes - sagen:
> >
> > > Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter
> > > Reinholdtsen:
> > >
> > > >
On 01/06/2017 12:41 PM, permondes - sagen wrote:
> Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter Reinholdtsen:
>> [permondes - sagen]
>> > I think that with the kernel and initrd-updates the old version
>> were not
>> > removed. Can I simply remove them with "rm"? Just keeping the latest
Hello mailinglist!
I'm running the "testing"-version of the fbx.
Since an update of a package, i have not yet found out which one it was,
i notice the Access-point of the WiFi to shut down every 30 minutes.
The journal says:
wpa_supplicant[822]: wlan0: AP-STA-DISCONNECTED
wpa_supplicant[822]:
Am Freitag, den 06.01.2017, 20:25 +0100 schrieb permondes - sagen:
> Am Freitag, den 06.01.2017, 18:41 +0100 schrieb permondes - sagen:
>
> > Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter
> > Reinholdtsen:
> >
> > > [permondes - sagen]
> > > > I think that with the kernel and
Am Freitag, den 06.01.2017, 18:41 +0100 schrieb permondes - sagen:
> Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter Reinholdtsen:
>
> > [permondes - sagen]
> > > I think that with the kernel and initrd-updates the old version were not
> > > removed. Can I simply remove them with "rm"?
Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter Reinholdtsen:
> [permondes - sagen]
> > I think that with the kernel and initrd-updates the old version were not
> > removed. Can I simply remove them with "rm"? Just keeping the latest
> > version?
>
> I would instead use 'dpkg -S /boot/v*'
[permondes - sagen]
> I think that with the kernel and initrd-updates the old version were not
> removed. Can I simply remove them with "rm"? Just keeping the latest
> version?
I would instead use 'dpkg -S /boot/v*' to identify packages to remove,
and 'apt purge ' to remove them.
--
Happy
My boot partition is full, so the latest kernel and uboot updates could
not be installed. The partition contains:
boot.cmd config-4.8.0-1-armmp-lpae
initrd.img-4.7.0-1-armmp-lpae System.map-4.7.0-1-armmp-lpae
vmlinuz-4.7.0-1-armmp-lpae
boot.scr
12 matches
Mail list logo
