DietPi | Debian Stretch Status

Created on 15 Aug 2016  ·  86Comments  ·  Source: MichaIng/DietPi

Images now Stretch by default:

Stretch Status Odroid C2: https://github.com/Fourdee/DietPi/issues/1032

Stretch Status Raspberry Pi:

🈯️ Now live and default image for DietPi on RPi.

Hardware

DietPi-Software status:

Desktops:

  • 🈯️ LXDE

    • 🈯️ FB

    • 🈯️ GL

  • 🈯️ MATE
  • GNUstep
  • 🈯️ XFCE
  • 🈯️ VNC4 server (now TigerVNC)
  • RealVNC server
  • 🈴 Chromium: /etc/chromium-browser.d/custom_flags no effect. Sandbox.

DietPi-Config:

DietPi-JustBoom

  • 🈯️ Global
  • 🈯️ MPD
  • 🈯️ CAVA

DietPi-Drive_Manager

- 🈯️ v145 : https://github.com/Fourdee/DietPi/issues/751#issuecomment-280850954

Why Stretch?

This will allow for more "recent" software version installations through apt, that our users are requesting.

http://dietpi.com/phpbb/viewtopic.php?f=12&t=590&p=2569#p2569

Debian Stretch Enhancement Feature Request
Source
picture Fourdee
🎉4 👍4 😄1

Most helpful comment

RPi Stretch image is now live and default on http://dietpi.com

picture Fourdee on 10 Dec 2017
❤2 🎉2 👍2

All 86 comments

Puhh,

reading, Debian Stretch will start over after Kernel 4.10 is released.

https://wiki.debian.org/DebianStretch

If I see the timeline, it will be end of 2017 until official Stretch release.
But good to know, you have a milestone.

Till then, let's go for hunting and fixing some bugs in Dietpi. 😃

k-plan picture k-plan on 15 Aug 2016
👍1

dietpi-drive_manager hangs at start with Stretch for roughly 30 seconds.

  • This occurs when auto entries for non-existent drives are enabled in /etc/fstab, in combination with x-systemd.automount
  • Setting ext4 for each drive resolves the issue. Which is unexpected?

SystemD, hangs commands such as df (which our script uses), until systemD times out waiting for drives.

  • Find/Reduce timeout for systemD waiting for drives?
Fourdee picture Fourdee on 9 Oct 2016

Notes:

  • dropbear now supports SCP/SFTP by default (YAY!)
  • PHP upgraded to php7

Webserver stack tests:

Jessie testing:

  • Lighttpd + nextcloud = yes
  • nginx + nextcloud = yes
  • apache2 + nextcloud = yes
  • nginx + owncloud = yes

Stretch testing:

  • Lighttpd + Nextcloud = yes | old apc.php not functional, phpinfo shows enabled and active.
  • nginx + nextcloud = yes
  • apache2 + nextcloud = yes | old apc.php not functional, phpinfo shows enabled and active.
  • nginx + owncloud = yes
Fourdee picture Fourdee on 11 Oct 2016

I think I'll hold off on my projects until this is implemented. Otherwise it requires a reformat.

ghost picture ghost on 3 Nov 2016

@Zone22

This wont be ready for a while, need to test and fix every installation. I may release the image under alpha, but wont be for a few weeks.

Fourdee picture Fourdee on 3 Nov 2016

@Fourdee

Alpha testing

http://dietpi.com/phpbb/viewtopic.php?f=9&t=986&p=4279#p4279

k-plan picture k-plan on 10 Dec 2016
👍3 ❤1

@k-plan
Many thanks for testing results 👍 , i've updated the list in first post and i'll get those fixed.

Fourdee picture Fourdee on 18 Dec 2016

Note to self: test RoonBridge installer and dietpi-justboom

Fourdee picture Fourdee on 20 Dec 2016

Typical, trying to do some RPi testing and http://archive.raspberrypi.org is unstable/offline lol:

The following packages will be upgraded:
  libraspberrypi-bin libraspberrypi0 raspberrypi-bootloader raspberrypi-kernel
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 34.5 MB of archives.
After this operation, 33.8 kB of additional disk space will be used.
Err:1 http://archive.raspberrypi.org/debian jessie/main armhf raspberrypi-kernel armhf 1.20161215-1
  500  Internal Server Error [IP: 46.235.227.11 80]
Err:2 http://archive.raspberrypi.org/debian jessie/main armhf libraspberrypi-bin armhf 1.20161215-1
  500  Internal Server Error [IP: 46.235.227.11 80]
Fourdee picture Fourdee on 21 Dec 2016

HiFi:

E: Package 'libavcodec56' has no installation candidate
E: Package 'libavformat56' has no installation candidate
E: Unable to locate package libavresample2
E: Package 'libavutil54' has no installation candidate
E: Package 'libbinio1ldbl' has no installation candidate
E: Unable to locate package libjson-c2
E: Package 'libnfs4' has no installation candidate
E: Unable to locate package libvpx1
E: Package 'libwildmidi1' has no installation candidate
E: Unable to locate package libx264-142

libavformat57
libavresample3
libavutil55

May make more sense to change our installation to:
apt-get install mpd
nb: arm64 mpd does not exist in repo yet.

Which pulls in all the required packages, then dpkg -i our latest mpd.deb (as of today, stretch installs 0.19.19 which is the same as our compiled version)

Fourdee picture Fourdee on 21 Dec 2016

@Fourdee

New Alpha testing DietPi v140:

http://dietpi.com/phpbb/viewtopic.php?f=9&t=986&p=4455#p4455

You DietPi fixes are well done! 😃

Put this stuff to the forum, to get some more user and concern for Stretch alpha testing.
But if you prefer it, I can put it as well on github. 😕

k-plan picture k-plan on 21 Dec 2016
❤1 👍1

@k-plan

But if you prefer it, I can put it as well on github.

Forums are fine, please keep giving me a nudge on here (notification) so I don't miss it 😃

Great testing, thanks @k-plan. Stretch is a long road, lots of testing as you know, but with your help (and hopefully others), we'll get there much quicker 👍

@k-plan Merry Xmas! 🎄 😃

Fourdee picture Fourdee on 22 Dec 2016

Looks like the bluetooth issue exists on jessie aswell. lacking pi-bluetooth packages. Will get that patched.
https://github.com/Fourdee/DietPi/issues/693

Ok thats done, still having issues with bluetooth on stretch:

root@DietPi:~# bluetoothctl
Waiting to connect to bluetoothd...

root@DietPi:~# systemctl status hciuart.service -l
● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2017-01-04 17:36:19 UTC; 2min 15s ago

Jan 04 17:36:19 DietPi systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Jan 04 17:36:19 DietPi hciattach[344]: Can't open serial port: No such file or directory
Jan 04 17:36:19 DietPi hciattach[344]: Can't initialize device: No such file or directory
Jan 04 17:36:19 DietPi systemd[1]: hciuart.service: Control process exited, code=exited status=1
Jan 04 17:36:19 DietPi systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
Jan 04 17:36:19 DietPi systemd[1]: hciuart.service: Unit entered failed state.
Jan 04 17:36:19 DietPi systemd[1]: hciuart.service: Failed with result 'exit-code'.
Fourdee picture Fourdee on 4 Jan 2017

WiFi:

root@DietPi:~# dmesg | grep brcm
[ 7414.760610] usbcore: registered new interface driver brcmfmac
[ 7414.761782] brcmfmac_sdio mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.bin failed with error -2
[ 7415.765022] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 7416.777708] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50


/lib/firmware/brcm/brcmfmac43430-sdio.bin # does not exist

apt-get update
apt-get dist-upgrade -y

root@DietPi:~# dmesg | grep brcm
[    3.291745] usbcore: registered new interface driver brcmfmac
[    3.317270] brcmfmac_sdio mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.txt failed with error -2
[    4.323907] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[    5.333980] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

wget https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/master/brcm80211/brcm/brcmfmac43430-sdio.txt -O /lib/firmware/brcm/brcmfmac43430-sdio.txt

works.

Fourdee picture Fourdee on 5 Jan 2017

Base package:

apt-get install neovim

Optional desktop GUI:

apt-get install neovim-qt

vi
image

Fourdee picture Fourdee on 19 Jan 2017
🎉1 👍1

RPi 3 onboard WiFi, not functional after reboot:
http://dietpi.com/phpbb/viewtopic.php?f=9&t=986&p=5434#p5407

Fourdee picture Fourdee on 3 Feb 2017

VNC4, and tightvnc server changed to tigervnc:

ii  tigervnc-standalone-server     1.7.0+dfsg-2                armhf        Standalone virtual network computing server
ii  vnc4server                     4.1.1+X4.3.0+t-1            armhf        transitional package

root@DietPi:~# vncpasswd
-bash: vncpasswd: command not found

systemctl status vncserver.service -l

Feb 05 15:05:35 DietPi bash[1445]: vncserver: Couldn't find "tigervncpasswd" on your PATH.
Feb 05 15:05:35 DietPi bash[1445]:         Please install the tigenvnc-common package, i.e., sudo apt-get install tigenvnc-common.

apt-get install tigervnc-common
tigervncpasswd

Seems to run, unable to connect...

Fourdee picture Fourdee on 5 Feb 2017

I'd like to note that(although I'm using a manually updated PineA64) v145 produced an error with Fail2Ban for me.
Apt-get has failed:
│ - Apt string = fail2ban --no-install-recommends
│ - Error code = 100
the console produced this:
Job for fail2ban.service failed because the control process exited with error code.
See "systemctl status fail2ban.service" and "journalctl -xe" for details.
invoke-rc.d: initscript fail2ban, action "start" failed.
Process: 7398 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)

kronflux picture kronflux on 2 Mar 2017
👍1

ToDo:

  • 🈯️ Update image (RPi Zero W support), new image live.
Fourdee picture Fourdee on 8 Mar 2017

@kronflux

Looks like an issue with apt, or a bug with the fail2ban package. Fails to install on RPi 3, at a basic apt-get install level:

Setting up fail2ban (0.9.6-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/fail2ban.service → /lib/systemd/system/fail2ban.service.
Job for fail2ban.service failed because the control process exited with error code.
See "systemctl status fail2ban.service" and "journalctl -xe" for details.
invoke-rc.d: initscript fail2ban, action "start" failed.
● fail2ban.service - Fail2Ban Service
   Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2017-03-10 13:50:55 UTC; 29ms ago
     Docs: man:fail2ban(1)
  Process: 4390 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)

Mar 10 13:50:55 DietPi systemd[1]: fail2ban.service: Unit entered failed state.
Mar 10 13:50:55 DietPi systemd[1]: fail2ban.service: Failed with result 'ex…de'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package fail2ban (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.24-9) ...
Processing triggers for systemd (232-18) ...
Errors were encountered while processing:
 fail2ban
E: Sub-process /usr/bin/dpkg returned an error code (1)
Fourdee picture Fourdee on 10 Mar 2017

@Fourdee As a suggestion, as I don't know if you're using a custom build for ffmpeg, but if yes; it may be worthy to include the openmax functionality to include hardware assisted encoding (as in https://github.com/legotheboss/YouTube-files/wiki/(RPi)-Compile-FFmpeg-with-the-OpenMAX-H.264-GPU-acceleration)

WolfganP picture WolfganP on 8 Apr 2017
👍2 ❤1

@WolfganP

it may be worthy to include the openmax functionality to include hardware assisted encoding (as in

Legend 👍 this should help Emby server performance which uses FFmpeg.
https://github.com/Fourdee/DietPi/issues/869

Fourdee picture Fourdee on 9 Apr 2017

I faced two problems with this image:

  1. During dietpi-software installation process some warning is shown about "--force-yes is deprecated" and options with "allow" should be used instead.

  2. I use dietpi to run nextcloud on my pi2. Chose LAAP webserver stack to assure that mariadb will be used. It is not yet possible to chose preferred database like webserver itself -> Separate issue already opened about that. Nevertheless depending or that or not, dietpi-services no tries to handle two database services "mysql" AND "mariadb". Actually mysql is not installed, at least not via apt and it does not show up in dietpi-software either. So I can't remove it. dietpi-services starts "mysql" first successfully and tries to start "mariadb" afterwards which fails after long trial time. Nextcloud works fine, using the available service. It IS actually mariadb, which can be seen via modules, version check and nextcloud web ui. I am wondering about this "mariadb" service. DietPi-Process_Tool also shows one entry about that beside : Webserver MariaDB (1086) Never saw mariadb running as another service name than mysql. Did something change there or is it just some typing bug introduced with this dietpi image?

mysql/error.log shows, that indeed the two services seem to disturb each other:

2017-06-02 18:22:57 1995976704 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
2017-06-02 18:23:28 1995976704 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2017-06-02 18:23:28 1995976704 [ERROR] Plugin 'Aria' init function returned error.
2017-06-02 18:23:28 1995976704 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-06-02 18:23:28 1995976704 [Note] InnoDB: The InnoDB memory heap is disabled
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-06-02 18:23:28 1995976704 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Using Linux native AIO
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Using generic crc32 instructions
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Completed initialization of buffer pool
2017-06-02 18:23:28 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Retrying to lock the first data file
2017-06-02 18:23:29 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:23:30 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:23:31 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:23:32 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
...
2017-06-02 18:25:07 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:25:08 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:25:08 1995976704 [Note] InnoDB: Unable to open the first data file
2017-06-02 18:25:08 76f83000  InnoDB: Operating system error number 1 in a file operation.
InnoDB: Error number 1 means 'Operation not permitted'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2017-06-02 18:25:08 1995976704 [ERROR] InnoDB: Can't open './ibdata1'
2017-06-02 18:25:08 1995976704 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to $
2017-06-02 18:25:08 1995976704 [ERROR] Plugin 'InnoDB' init function returned error.
2017-06-02 18:25:08 1995976704 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-06-02 18:25:08 1995976704 [Note] Plugin 'FEEDBACK' is disabled.
2017-06-02 18:25:08 1995976704 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-06-02 18:25:08 1995976704 [ERROR] Aborting

dietpi-bugreport Reference CODE: bce03d8e-9e30-406c-95ff-07df36fd1f9e-1

€: Moved 2. problem into an own issue: https://github.com/Fourdee/DietPi/issues/1000
€€: Moved 1. to here: https://github.com/Fourdee/DietPi/issues/1018

MichaIng picture MichaIng on 2 Jun 2017

About missing apc.php with PHP7+, which results in some dummy file will be used instead:

7317# - PHP7+ - File does not exist
7318else
7319
7320wget http://dietpi.com/downloads/conf/apc.php -O /var/www/apc.php

There is some apc.php on github which is working well with my dietpi rpi stretch PHP7 setup: https://github.com/krakjoe/apcu/blob/master/apc.php

MichaIng picture MichaIng on 2 Jun 2017

@MichaIng

There is some apc.php on github which is working well with my dietpi rpi stretch PHP7 setup:

Thanks for this 👍
I've tested with Jessie and seems compatible. I'll update the code with new link.

Fourdee picture Fourdee on 3 Jun 2017
👍1

Is there a beta image for the Asus Tinker Board by any chance? :P

tetherit picture tetherit on 10 Jun 2017

@xanview

Is there a beta image for the Asus Tinker Board by any chance? :

Yep: http://dietpi.com/downloads/images/DietPi_AsusTinkerBoard-armv7-(Stretch).7z

Image is named Jessie, however its Stretch.

Fourdee picture Fourdee on 11 Jun 2017
Fourdee picture Fourdee on 12 Jun 2017
👍1

That's awesome, thank you! - I'm using it as a headless server and so far latest image is working beautifully.

tetherit picture tetherit on 12 Jun 2017
👍1

Regarding the fail2ban issue, what solved it for me was simple:
$ sudo touch /var/log/auth.log
before the install, then it went through successfully 👍

(you might need to $ sudo apt-get purge fail2ban if you're in a half-complete state)

noplanman picture noplanman on 25 Jun 2017
👍1

@noplanman

$ sudo touch /var/log/auth.log
before the install, then it went through successfully 👍

Legend 👍 Many thanks for the fix. I'll get this added to dietpi-software. Works with Jessie aswell, so we'll add for all distros.

Fourdee picture Fourdee on 25 Jun 2017
👍1

Hi Fourdee, many thanks for your work.

I install webmin and the Module webminstats v2.16, if i open this Module ''Historic System Statistics" i get the Error Message "Error - Missing Content-Type Header"

I could solve this problem while I install apt-get install libcgi-pm-perl

many thanks again

mr-bolle picture mr-bolle on 8 Jul 2017
👍1

I install DietPi_RPi-armv6-(Stretch) image, and install over dietpi-software Fail2Ban, after that the service don't start

$ /etc/init.d/fail2ban status
Failed to start server : Starting fail2ban (via systemctl): fail2ban.serviceJob for fail2ban.service failed because the control process exited with error code. See "systemctl status fail2ban.service" and "journalctl -xe" for details. failed!

> $ journalctl -xe

-- Unit fail2ban.service has finished shutting down.
Jul 08 16:08:04 nc-raspi2 systemd[1]: Starting Fail2Ban Service...
-- Subject: Unit fail2ban.service has begun start-up
-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- Unit fail2ban.service has begun starting up.
Jul 08 16:08:05 nc-raspi2 fail2ban-client[1739]: ERROR Failed during configuration: While reading from '/etc/fail2ban/jail.conf' [line 52]: option 'port' in section 'pam-generic'
Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Control process exited, code=exited status=255
Jul 08 16:08:05 nc-raspi2 systemd[1]: Failed to start Fail2Ban Service.
-- Subject: Unit fail2ban.service has failed
-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- Unit fail2ban.service has failed.

-- The result is failed.
Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Unit entered failed state.
Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Jul 08 16:08:05 nc-raspi2 systemd[1]: Stopped Fail2Ban Service.
-- Subject: Unit fail2ban.service has finished shutting down
-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- Unit fail2ban.service has finished shutting down.
Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Start request repeated too quickly.
Jul 08 16:08:05 nc-raspi2 systemd[1]: Failed to start Fail2Ban Service.
-- Subject: Unit fail2ban.service has failed
-- Defined-By: systemd

-- Support: https://www.debian.org/support

-- Unit fail2ban.service has failed.

-- The result is failed.
Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Unit entered failed state.
Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Failed with result 'exit-code'.

Solution:
apt-get purge fail2ban && apt-get install fail2ban

$ /etc/init.d/fail2ban status
fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2017-07-08

V153 | RPi 2 Model B (armv7l)

https://github.com/Fourdee/DietPi/issues/475#issuecomment-285673712

mr-bolle picture mr-bolle on 8 Jul 2017

Please, update berryboot testing image. Last one in http://dietpi.com/downloads/testing/ is from December.

sal666 picture sal666 on 21 Jul 2017

Finally Stretch became stable for Raspbian: https://www.raspberrypi.org/downloads/raspbian/

MichaIng picture MichaIng on 17 Aug 2017
👍2

Will it change anything in Dietpi? I'm under the impression that @Fourdee updated kernel components a while ago (or maybe I messed with my system a lot :-)

WolfganP picture WolfganP on 17 Aug 2017

Yeah the kernel is updated together with dietpi regularly, but this has not much to do with the Distro version.

Raspbian still based on Debian Jessie until yesterday, thus DietPi for RPi did the same, if you didn't flash the beta above.
Stretch brings a lot of new package major versions, that were frozen in Jessie, most importantly for my use cases PHP7.0 (instead of PHP5.6), which also changes locations of configuration files etc. This will be the same for some other packages I guess.
So after full upgrade all DietPi images to Stretch, much code about distro version checks etc. can be cleaned up 😄 .

MichaIng picture MichaIng on 17 Aug 2017

@MichaIng

Finally Stretch became stable for Raspbian: https://www.raspberrypi.org/downloads/raspbian/

Nice one 👍

For now, we'll keep the Stretch as a beta image, Kodi and a few other items need testing and confirmed functional, before we replace our default Jessie image.

Fourdee picture Fourdee on 17 Aug 2017
👍1

Can you provide DietPi testing build for Pine64? I'll give it a shot and test.

rdslw picture rdslw on 22 Aug 2017

stretch will have to be installed from scratch, or an update from jessie will be possible?

molnarti picture molnarti on 3 Sep 2017

@molnarti

stretch will have to be installed from scratch, or an update from jessie will be possible?

Stretch installs, will require a clean installation with the Stretch image.

Its not feasible for us to distro upgrade existing systems, as we have no way of knowing if the user has applied manual changes to Linux settings. User input is also required for distro upgrade, which again, could change depending on what the user has installed/configured (we cant predict outcome enough, to ensure 100% success).

Fourdee picture Fourdee on 3 Sep 2017

@Fourdee

🈺 RPi Monitor: Memory missing: http://dietpi.com/phpbb/viewtopic.php?f=9&t=986 (external bug)

Where is a new upcoming version: RPi-Monitor v2.12-r0

https://github.com/XavierBerger/RPi-Monitor-deb/tree/master/packages

Tested with 2017-08-16-raspbian-stretch.img and it work.

170903-0005

Because of new strech ethernet interface naming enx(+mac-address), user have to edit /etc/rpimonitor/template/network.conf but it works as desired.

k-plan picture k-plan on 3 Sep 2017

I upgraded my Pine64 install to Stretch and then, since it is my experimental build, went up to sid.
Works fine overall but I don't have a bunch of packages installed, so it might be a premature 'works fine'.

I find the Stretch ethernet naming a bit gross but I'm sure there is a good reason for it.

atiensivu picture atiensivu on 3 Sep 2017

@atiensivu

I find the Stretch ethernet naming a bit gross but I'm sure there is a good reason for it.

We revert to wlanx/ethx naming in DietPi v155:
https://github.com/Fourdee/DietPi/blob/master/dietpi/patch_file#L2733-L2734

Fourdee picture Fourdee on 4 Sep 2017
👍2

Is it possible to boot with DietPi Stretch for the first time with an enabled wifi configuration ?

With DietPi Jessie the dietpi.txt file managed to do that but I don't manage to activate wifi on first boot with Stretch ? Am I missing something ?

Bridouz picture Bridouz on 27 Sep 2017
👍1

@Bridouz

With DietPi Jessie the dietpi.txt file managed to do that but I don't manage to activate wifi on first boot with Stretch ?

Thanks for the report, i'll try to replicate 👍

Fourdee picture Fourdee on 27 Sep 2017

DietPi Stretch (v151) installed with ethernet connexion. Wifi is not working out of the box.

By enabling wifi in DietPi-Config Raspbian wants to install netplug
A reboot after the installation of netplug and WIFI SSID are available.

However I tried (after the wifi setting) to disable Ethernet. By doing it it removes netplug and the Pi is now not accessible from either Ethernet or Wifi.

_Edit: OK Wifi working with netplug. Scanning for SSID juste after the package installation fails. A reboot is mandatory to ne able to scan through available SSID_

Bridouz picture Bridouz on 27 Sep 2017

@Fourdee

Certbot is now packaged on Stretch and I can confirm it works with the webroot plugin out of the box.

Would you authorize me to propose a PR with changes reflecting that ?

Bridouz picture Bridouz on 28 Sep 2017
👍2

Certbot is now packaged on Stretch and I can confirm it works with the webroot plugin out of the box.
Would you authorize me to propose a PR with changes reflecting that ?

Yep by all means 👍

Fourdee picture Fourdee on 28 Sep 2017

Yes certbot from repo also working well for me on raspbian stretch.

I use python-certbot-apache and did the automated apache configuration with it. This creates a quite nice ssl/cipher config in a separate config file. Same exist for nginx: python-certbot-nginx

MichaIng picture MichaIng on 28 Sep 2017

@MichaIng Thanks for mentioning python-certbot-nginx. I've just tested it and it's really nice, it works really great without any user input (except the fact I had to add my ddns domain to nginx.conf).

The ssl/cipher config is rated B from Qualys SSL Labs. Not bad but could be enhanced (with Mozilla recommendations https://mozilla.github.io/server-side-tls/ssl-config-generator/)

What do you think about Certbot :

  • Using certbot certonly --webroot which works but requires a well-known location in server config
  • Using certbot --nginx/apache which does the work without any user input + add a bit of ssl/cipher to server config file (which could not be bad afterall)
Bridouz picture Bridouz on 28 Sep 2017

@Fourdee Does the problem with kodi still exist? I am wondering, because stretch is already official released also for raspbian with kodi in default repo.

apt install kodi --dry-run ran without error, I hesitate to try the real installation with 100+ dependency packages 😛.

Can't wait to see DietPi Stretch release 🙂.

MichaIng picture MichaIng on 29 Sep 2017

Hi Fourdee and thank you for your work!
Please explain

  1. What Linux kernel version is being used for DietPi_SparkySBC-armv7-(Stretch).7z image?
  2. Is it possible to replace old kernel version 3.10.38?
kotamotov picture kotamotov on 6 Oct 2017

@kotamotov

Hi, its 3.10 currently:
https://github.com/Fourdee/DietPi/issues/1176#issue-263619322

Fourdee picture Fourdee on 7 Oct 2017

@Fourdee

No wifi out of the box on Dietpi Stretch V156 image.

In dietpi-config onboard wifi is active but wifi module is not. Need to activate it (which install netplug) reboot and then I'm able to scan SSID.

Strange because on latest Raspbian image wifi works OOTB withou netplug package.

Bridouz picture Bridouz on 9 Oct 2017

Maybe due to recent debian 9.2 release? https://www.debian.org/News/2017/20171007

MichaIng picture MichaIng on 10 Oct 2017

@Bridouz

In dietpi-config onboard wifi is active but wifi module is not. Need to activate it (which install netplug) reboot and then I'm able to scan SSID.

Confirmed, in testing i found 8/10 reboots results in scan failure:
dmesg

[    4.309924] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3)
[    4.309934] brcmfmac: brcmf_cfg80211_scan: scan error (-11)

Its really early on in boot, and we do nothing differently for Jessie/Stretch in DietPi, not sure on cause yet.
Our RPi kernel is the same on both Jessie and Stretch.

Same errors with netplug removed.

Fourdee picture Fourdee on 10 Oct 2017

i tried to install nextclout on the most recent RPi stretch image and got the following error

2017-10-12 23:48:32 (1.03 MB/s) - ‘/var/www/apc.php’ saved [38125/38125]

[Info] Apt-get is processing, please wait...

E: Command line option 'i' [from -intl] is not understood in combination with the other options.
[Failed] The apt cache may be corrupt, apt mirror offline, or you have held broken packages. DietPi-Software will now exit.

[Info] Apt Log:
E: Command line option 'i' [from -intl] is not understood in combination with the other options.

[Info] Please try:
[Info] - Fixing apt package errors with 'apt-get install -f'
[Info] - Change apt mirror: 'dietpi-config' > 'Networking: NAS/MISC' > 'Apt Mirror'
[Info] - Clear and refresh apt 'apt-get update'
[Info] - If problems persist, please create a Git ticket so DietPi can investigate the issue:

  • https://github.com/Fourdee/DietPi/issues
molnarti picture molnarti on 12 Oct 2017

@molnarti Are you using testing branch? Try it with the newest version of dietpi-software, just replace your version of it. This error occurred during our Nextcloud installation optimization and was fixed with the recent PRs.

€: Ah just checked: RPi Stretch test image was created just after the first test upgrade of Nextcloud installation merged into testing branch, which produced this error. @Fourdee is it expected that the Stretch images also contain testing branch, as there is sometimes stuff still in development that has not necessarily something to do with Stretch? Also the image is named v156 but contains as mentioned testing code from v157?

MichaIng picture MichaIng on 12 Oct 2017

@MichaIng

@Fourdee is it expected that the Stretch images also contain testing branch, as there is sometimes stuff still in development that has not necessarily something to do with Stretch? Also the image is named v156 but contains as mentioned testing code from v157?

Correct, when generating images I use the testing branch. Allows us to apply fixes to the image that are in devolpment.

But yes, seems this one caught the Nextcloud dev at a bad stage, regardless, will be fixed with v157 release, ETA next week.

@molnarti

You can fix this issue (before the v157 is released) by doing the following:

wget https://github.com/Fourdee/DietPi/raw/testing/dietpi/dietpi-software -O /DietPi/dietpi/dietpi-software

Nextcloud should now install.

Fourdee picture Fourdee on 13 Oct 2017

I can’t connect to my monitor 1600x900 to HDMI output of Sparky SBC properly.
Please explain how to set (change) desktop screen resolution for my monitor.
Bay default DietPi has 1024x600 for LXDE desktop. How to change it?
My monitor (display) has screen resolution 1600x900. Maybe it is possible to set 1280x720?
File uEnv.txt not help.

kotamotov picture kotamotov on 14 Oct 2017

@kotamotov

Hi,

Default output of Sparky SBC is 1080p

We'll need to compile you a kernel.dtb overlay with the requested resolution, as it cant be changed outside of the file. I've sent the request over to Allo, will update you.

Fourdee picture Fourdee on 14 Oct 2017

Thank you in advance for your attention to this software problem for Sparky SBC!
I am waiting for your compilation!

kotamotov picture kotamotov on 14 Oct 2017

@Fourdee Is posible to include some Recursive DNS Server like Unbound, Bind9 etc, preconfigured to working with Root Hints? Thanks!!!

athlonxp78 picture athlonxp78 on 26 Oct 2017

@kotamotov

Apologies for the delay. Please see instructions below provided by Allo.

If unsure, let me know and i'll try to assist.

https://raw.githubusercontent.com/sparky-sbc/sparky-test/master/sparky_720p_dtb/sparky_720p_dtb.tar

By default HDMI resolution takes auto mode.
To achieve 720p , kernel.dtb and u-boot-dtb.img need to change.

On SD card insert on linux system, using DD copy flash u-boot-dtb.img
Fdisk –l shows device sdx1 sdx2. X is the letter a,b,c,d,e ….

#dd if=u-boot-dtb.img of=/dev/sdb bs=512 seek=6144

Kernel.dtb you can copy by #mount /dev/sdx1 /mnt
Copy the file.

On Image you have to mount virtually and copy the u-boot-dtb.img

Fourdee picture Fourdee on 26 Oct 2017

I apologize if this is the wrong place to report this.

Latest stretch beta, I found that choosing to install OpenSSH over dropbear in dietpi-software doesn't actually remove dropbear. I was trying to connect to my Pi via SSHFS and it kept failing. Only until I checked my auth.log did I realize that I was still connecting via dropbear and it was still installed.

Thanks!

ghost picture ghost on 4 Nov 2017

WiFi

RL

root@raspberrypi:~# dmesg | grep brcm
[   24.114957] usbcore: registered new interface driver brcmfmac
[   24.227602] brcmfmac: Firmware version = wl0: Aug  7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[   25.530264] brcmfmac: power management disabled

DP

root@DietPi:~# dmesg | grep brcm
[   15.117510] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   15.129218] usbcore: registered new interface driver brcmfmac
[   15.311809] brcmfmac: Firmware version = wl0: Aug  7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[   15.312674] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.41 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-08-07 00:37:47

...
[  236.621353] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3)
[  236.621360] brcmfmac: brcmf_cfg80211_scan: scan error (-11)
...

Something in the system_prep script is the cause (eg: packages), works fine until prep is completed, need to debug.

  • 🈴 apt-get install -y libraspberrypi-bin libraspberrypi0 raspberrypi-bootloader --allow-change-held-packages
  • 🈴 104 = package removals only
  • 🈴 105 = configuration only
  • 🈯️ /etc/network/interfaces now incompatible? This is the cause, bringing up the adapter causes endless brcmf_cfg80211_scan, rendersdhcpcd null.
    -- Adapter needs to be up for iwlist wlan0 scan, doing so through ifup and using /etc/network/interfaces causes the errors.
    -- dhcpcd / wpa_supplicant must be doing something different with the adapter, as apposed to /etc/network/interfaces and ifup

Entries that render WiFi scan errors:

wpa-psk
  • 🈯️ Working using /etc/wpa_supplicant/wpa_supplicant.conf to configure WiFi creds. Seems we'll need to modify DietPi to use this feature, instead of wpa-ssid and wpa-psk entries in /etc/network/interfaces.
Fourdee picture Fourdee on 23 Nov 2017
🎉1

@Fourdee

🈺 RPi Monitor: Memory missing: http://dietpi.com/phpbb/viewtopic.php?f=9&t=986 (external bug)

possible fix with rpimonitor_2.11-r5_all.deb in DietPi v158 is new fixed memory.conf :

cp /etc/rpimonitor/template/memory.conf /etc/rpimonitor/template/memory.conf.bak
wget https://github.com/XavierBerger/RPiMonitor/raw/devel/src/etc/rpimonitor/template/memoryconf  /etc/rpimonitor/template/memory.conf
service rpimonitor restart

Old network.conf from rpimonitor_2.11-r5_all.deb works well with DietPi_v156_RPi-armv6-(Stretch).img

k-plan picture k-plan on 25 Nov 2017
👍1

ToDo:

  • 🈯️ Resolve for Chromium-Browser under root
    -- 🈯️ Running chromium-browser --temp-profile --no-sandbox from cmdline is fine
    -- Running chromium.desktop with the above Exec conditions, gets ignored
    -- 🈯️ echo "WARNING: \$CHROMIUM_USER_FLAGS is deprecated. Instead, update CHROMIUM_FLAGS in ~/.chromium-browser.init
  • Update image
  • 🈯️ Re-Test main software titles
    -- 🈴 Amiberry, fails due to renamed libguichan libs with XXXX-v5 ending. Also fails to launch.
  • 🈯️ Re-test WiFi
  • Switch to Stretch as default image.
Fourdee picture Fourdee on 7 Dec 2017

@Fourdee

  • Switch to Stretch as default image.

Good idea.

But what will you do with old and outdated Jessie images?

Freeze kernel, firmware, and dietpi version (to which?) and cancel support?

k-plan picture k-plan on 7 Dec 2017
👍1

@k-plan

But what will you do with old and outdated Jessie images?
Freeze kernel, firmware, and dietpi version (to which?) and cancel support?

I'll leave the existing Jessie code in DietPi.

Support wise, we will support both, at least until Stretch has been stable for a month without any reported issue. At that point, we'll lower support priority for Jessie, in favor of Stretch.

In regards to our other Jessie images, (eg: Odroid, NanoPi's etc), we'll do the same (once we offer and switch to Stretch images for those devices).

Fourdee picture Fourdee on 7 Dec 2017
😕1

Yeah and by times, if we are too annoyed to always consider both distros and Stretch has proven stable on all devices, we can do something similar than done with wheezy: https://github.com/Fourdee/DietPi/tree/wheezy-final-v120
A final image where we could disable dietpi-update.

MichaIng picture MichaIng on 7 Dec 2017
❤1 👍1

we can do something similar than done with wheezy

A final image where we could disable dietpi-update.

I would prefer to do this NOW!

wheezy-final-v120

... but this time as well freeze kernel, firmware, headers, ...

And let the orphaned devices freeze, no one has time to work on or will work on in the future.

Too many building lot for too little facilitator ... as always the same problem.
Be frightened of @Fourdee get break down and without him, there will be no DietPi any more.

DietPi has highly grown up and orientation has change over time.
And this will happen in future as well.

Sorry, mean no harm, but just my 2 Cent ...

k-plan picture k-plan on 7 Dec 2017
❤1 👍1

@k-plan
Generally I agree to look forward now. But first we need to get rid of the final issues with Stretch, in my opinion.
For the moment, considering the distro is still affordable for me.
About devices, no idea. I guess it just depends on someone, who has the device available for building/testing and is willing to do regular image updates.

Focus on Stretch:
@Fourdee

fail2ban

MichaIng picture MichaIng on 8 Dec 2017
👍1

@MichaIng && @k-plan

Yeah and by times, if we are too annoyed to always consider both distros and Stretch has proven stable on all devices, we can do something similar than done with wheezy: https://github.com/Fourdee/DietPi/tree/wheezy-final-v120
A final image where we could disable dietpi-update.

I completely forgot about our Wheezy Final image 👍

We'll do the same for each of our Jessie images, once their Stretch replacement has been proven stable for at least a month.

Fourdee picture Fourdee on 8 Dec 2017

@Fourdee

I completely forgot about our Wheezy Final image 👍

... and I have done testing to update Wheezy Final image, but if you explicate a 'Update firmware' via dietpi-config it's will become completely useless .... 😃 👎

k-plan picture k-plan on 8 Dec 2017
😄1 👍1

but if you explicate a 'Update firmware' via dietpi-config it's will become completely useless .... 😃 👎

Yes, if we drop support, dietpi-update and firmware updates need to be disabled. Hint about that could be given via dietpi-banner.
Users can than decide to stay on distro version and update by themself packages via apt etc. on own risk or switch to new image. After backup, apt upgrade by editing sources.list could be also tried. Work well for me on VirtualBox Jessie, but can easily fail/produce issues with more software installed.

MichaIng picture MichaIng on 8 Dec 2017
👍1

@MichaIng

can you please do this in https://github.com/Fourdee/DietPi/tree/wheezy-final-v120 ?

If so, I willing to build a last final updated image: DietPi_v120_RPi-armv6-(Wheezy).img with the last security fixes, which start without auto-update.

Thanks.

k-plan picture k-plan on 8 Dec 2017

Do you think this still matters? I am a bid afraid we open a barrel with this. As we do not support wheezy for so long, there might be several issues after doing a simple apt-get upgrade.
I don't believe there are many users still on wheezy.

We should concentrate on bringing up Stretch for all devices now and keep the mentioned things in mind for the final Jessie update.

MichaIng picture MichaIng on 8 Dec 2017
👍2

@k-plan

Add a line here:
https://github.com/Fourdee/DietPi/blob/wheezy-final-v120/dietpi/dietpi-banner#L75

eg: echo -e "This image is no longer supported, etc etc"

Fourdee picture Fourdee on 8 Dec 2017
😄1

Do you think this still matters?

Hmmm ... only as a 'proof-of-concept' for the last jessie final fix.

We should concentrate on bringing up Stretch for all devices now and keep the mentioned things in mind for the final Jessie update.

YES! 👍 😃

But I see so many bug as well with jessie and I 'm not able to fix a single one by myself 😢

Add a line here:

😄 I will have a look, if I find some spare time, but I will then do this outside of your github repository.
But let me first screw up RPi jessi image .... 😉

... and now back to topic: Debian Stretch

k-plan picture k-plan on 8 Dec 2017
❤1 👍1

AmiBerry:

https://github.com/Fourdee/DietPi/issues/475#issuecomment-350050345

  • Jessie binary fails to run, process hangs, black screen.
  • Compile on Stretch:
./amiberry-sdl2: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory

root@DietPi:~# find / -name  libbcm_host.so
/opt/vc/lib/libbcm_host.so

...

root@DietPi:~# cat /etc/ld.so.conf.d/00-vmcs.conf
/opt/vc/lib

...
export LD_LIBRARY_PATH=/usr/local/lib:/opt/vc/lib:/lib:/usr/lib
root@DietPi:/etc/amiberry# echo $LD_LIBRARY_PATH
/usr/local/lib:/opt/vc/lib:/lib:/usr/lib

#continues to fail



apt-get install -y libraspberrypi-bin libraspberrypi0 raspberrypi-bootloader
  • 🈴 Compile of dev branch, SDL1, run binary = returns to cmdline, no errors/info.

Ok this needs much longer than I have time available at the moment, and, its probably best we wait for the next official release.
I'll mark this is a known issue with Stretch image (Amiberry website still lists working Jessie for the download), and, create a separate ticket.
https://github.com/Fourdee/DietPi/issues/1278

Fourdee picture Fourdee on 8 Dec 2017

RPi Stretch image is now live and default on http://dietpi.com

Fourdee picture Fourdee on 10 Dec 2017
❤2 🎉2 👍2

I have a Odroid C2 that I could test Beta or alpha images for stretch

LexiconCode picture LexiconCode on 20 Dec 2017
👍1

@Fourdee
We did not yet fix fail2ban installation, did we?
http://dietpi.com/phpbb/viewtopic.php?f=11&t=2582&p=10090#p10090

Also we need to switching to journald observation, if rsyslog is not installed, thus no log to auth.log?
https://github.com/Fourdee/DietPi/blob/testing/dietpi/conf/fail2ban_jail.conf#L35-L43

MichaIng picture MichaIng on 22 Dec 2017

Marking as completed for v6.0 release (next week), minus Odroid devices, see below:
https://github.com/Fourdee/DietPi/issues/1385#issue-287129015

Fourdee picture Fourdee on 20 Jan 2018
Was this page helpful?
0 / 5 - 0 ratings

Related issues

1021683053 picture 1021683053  ·  3Comments
Fourdee picture Fourdee  ·  3Comments
Kapot picture Kapot  ·  3Comments
Fourdee picture Fourdee  ·  3Comments
bhaveshgohel picture bhaveshgohel  ·  3Comments