Op dinsdag 30 juni 2015 11:49:09 schreef u:
> On 06/30/15 11:24, Freek de Kruijf wrote:
> > Op dinsdag 30 juni 2015 10:57:31 schreef Alexander Graf:
> >> On 06/30/15 10:55, Freek de Kruijf wrote:
> >>> Earlier a second boot of a system generated with this build for
> >>> Raspberry
> >>> Pi 1B did n
Op dinsdag 30 juni 2015 11:49:09 schreef Alexander Graf:
> On 06/30/15 11:24, Freek de Kruijf wrote:
> > Op dinsdag 30 juni 2015 10:57:31 schreef Alexander Graf:
> >> On 06/30/15 10:55, Freek de Kruijf wrote:
> >>> Earlier a second boot of a system generated with this build for
> >>> Raspberry
> >>
On 06/30/15 11:24, Freek de Kruijf wrote:
Op dinsdag 30 juni 2015 10:57:31 schreef Alexander Graf:
On 06/30/15 10:55, Freek de Kruijf wrote:
Earlier a second boot of a system generated with this build for Raspberry
Pi 1B did not work. Now I have a system that works and can be booted
again.
How
Op dinsdag 30 juni 2015 10:57:31 schreef Alexander Graf:
> On 06/30/15 10:55, Freek de Kruijf wrote:
> > Earlier a second boot of a system generated with this build for Raspberry
> > Pi 1B did not work. Now I have a system that works and can be booted
> > again.
> >
> > However trying to start a m
On 06/30/15 10:55, Freek de Kruijf wrote:
Earlier a second boot of a system generated with this build for Raspberry Pi
1B did not work. Now I have a system that works and can be booted again.
However trying to start a module with yast (ncurses), I tried network,
software repositories and softwar
Earlier a second boot of a system generated with this build for Raspberry Pi
1B did not work. Now I have a system that works and can be booted again.
However trying to start a module with yast (ncurses), I tried network,
software repositories and software all end in the following error message:
