search

MichaIng / DietPi

Lightweight justice for your single-board computer!
https://dietpi.com/
GNU General Public License v2.0
4.88k stars 496 forks source link

v6.0 | Recreate all images #1385

Closed Fourdee closed 6 years ago

Fourdee commented 6 years ago

v6.0 image notes:

High priority devices:

Low priority devices:

all ARMbian based devices. https://github.com/Fourdee/DietPi/issues/1537#issue-298337026 NanoPi: [-] NanoPi Neo | ARMbian [-] NanoPi Neo Air | ARMbian (https://github.com/Fourdee/DietPi/issues/1385#issuecomment-361003168)

Banana Pi: https://github.com/Fourdee/DietPi/issues/1537#issue-298337026 [-] BPi Pro | ARMbian [-] BPi M2+| ARMbian

Orange Pi: https://github.com/Fourdee/DietPi/issues/1537#issue-298337026 [-] OPi PC | ARMbian [-] OPi PC 2 | ARMbian [-] OPi Prime | ARMbian [-] OPi Win 🈴 https://github.com/Fourdee/DietPi/issues/1385#issuecomment-358002327 | ARMbian [-] OPi One | ARMbian [-] OPi Lite | ARMbian [-] OPi Plus ~https://github.com/Fourdee/DietPi/issues/1385#issuecomment-358002327~ | ARMbian [-] OPi Zero | ARMbian [-] OPi Zero 2+ ARMv7 | ARMbian [-] OPi Zero 2+ ARMv8 | ARMbian

Other low priority:

Specials:

MichaIng commented 6 years ago

@Fourdee And if we, based on HW_MODEL/2nd partition size/content(dietpi.txt), just remove the tiny 2nd partition before first run resizing rootfs? A tiny free space would not hurt. I am afraid of generally changing all the partitions for other devices, if I understand your idea right, as this was/is always a bid fragile.

Fourdee commented 6 years ago

@MichaIng

just remove the tiny 2nd partition before first run resizing rootfs?

Could work 👍

But honestly, I can't comprehend why MS, with all their billions of $ and many thousands of staff, simply can't support EXT4 in their OS. Drives me up the wall lol.

Fourdee commented 6 years ago

@zador-blood-stained @ThomasKaiser @igorpecovnik

Question:

Are the following options, fully supported in ARMbian build tools?

https://github.com/armbian/build/blob/e546ac684d0fe0c0f47ab032aa867062e37da4e6/lib/configuration.sh#L224-L225

Reason for query:

zador-blood-stained commented 6 years ago

Are the following options, fully supported in ARMbian build tools? BOOTFS_TYPE BOOTSIZE

No, and by that answer I mean that it may work (or rather should work) in most cases, but

so it is a semi-supported build script option that may not work since currently we favor single-partition images (except for experimental OMV builds).

Its been mentioned in the past as a depreciated feature

FAT boot partition support in general and using BOOTSIZE to switch to a FAT partition is deprecated, but except for mentioned bugs and limitations building 2-partition images is supported.

MichaIng commented 6 years ago

@Fourdee @zador-blood-stained FAT partition support should be no problem, as DietPi by default adds dosfstools package. So we should be able to create the tiny FAT partition after full distro/package upgrade was done during preparation script, and then it should be able to mount during first run. All kernel/boot files can/should stay on 1st root partition to not mess something up there.

zador-blood-stained commented 6 years ago

FAT partition support should be no problem, as DietPi by default adds dosfstools package.

True unless you are talking about the first partition on the system device mounted to /boot.

This was discussed already, but there are several problems:

Fourdee commented 6 years ago

Notes: Native PC BIOS, 1st attempt failed. invalid filesystem after image ready (faulty SSD 😢 ).

k-plan commented 6 years ago

@Fourdee

If these options work (i've downloaded Paragon to test)? We could provide this information in 1st run guide for ARMbian images.

Quick check on Windows 7 running native on hardware.

:100: fail

Fourdee commented 6 years ago

@k-plan

@MichaIng method (extra 1MB fat partition) is the solution here, however, if i'am being honest, time limited at the moment. It may be after v6.0 is released that we can achieve it (all images need to be re-configured and script changes etc)

notes:

if [ partitionlabel = 'dietpi_extra' ]; then

del part

fi

expand
Fourdee commented 6 years ago

Sparky Allo install, hangs system. Hardware issue?:

[ 1076.024195] read phy reg-5
[ 1200.875145] INFO: task kworker/1:2:102 blocked for more than 120 seconds.
[ 1200.875155] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1200.875162] kworker/1:2     D c07bfe48     0   102      2 0x00000000
[ 1200.875187] Workqueue: events_power_efficient close_delayed_work
[ 1200.875213] [<c07bfe48>] (__schedule+0x390/0x7cc) from [<c07c065c>] (schedule_preempt_disabled+0x14/0x20)
[ 1200.884908] [<c07c065c>] (schedule_preempt_disabled+0x14/0x20) from [<c07bef44>] (__mutex_lock_slowpath+0x174/0x368)
[ 1200.895631] [<c07bef44>] (__mutex_lock_slowpath+0x174/0x368) from [<c07bf144>] (mutex_lock+0xc/0x24)
[ 1200.904913] [<c07bf144>] (mutex_lock+0xc/0x24) from [<c056ebdc>] (close_delayed_work+0x20/0xc8)
[ 1200.913756] [<c056ebdc>] (close_delayed_work+0x20/0xc8) from [<c00470dc>] (process_one_work+0x134/0x414)
[ 1200.923380] [<c00470dc>] (process_one_work+0x134/0x414) from [<c00477b8>] (worker_thread+0x138/0x37c)
[ 1200.932730] [<c00477b8>] (worker_thread+0x138/0x37c) from [<c004d394>] (kthread+0xa4/0xb0)
[ 1200.941113] [<c004d394>] (kthread+0xa4/0xb0) from [<c000f3d8>] (ret_from_fork+0x14/0x3c)
[ 1210.845796] read phy reg-4
[ 1210.846145] read phy reg-0
[ 1210.846487] read phy reg-5

Need to update DB user in GUI code.

(2/2) QueryException
SQLSTATE[HY000] [1698] Access denied for user 'root'@'localhost' (SQL: select * from `users` where `email` = admin@allo.com limit 1)
Fourdee commented 6 years ago

AmiBerry image test did not install, automation issue? Fixed with https://github.com/Fourdee/DietPi/commit/36b59349ae339f4d8082eaac915360facf77df22

Fails to install due to connection test name or service not known, fine after running it again. Most likely DHCP/DNS not ready in time, may need to increase default wait time for net boot, or, allow G_CHECK_URL to re-run 2/3 times with 1/2 second delay?

Fourdee commented 6 years ago

AlloGUI images notes: Need to test Allo GUI indepth before release of updated v6.0 image (soundcard selection etc). v159 image will still function in the mean time, so no rush.

Sparky only, RPi fine, same web interface code and .bashrc.

CPU Temperature :Bash: G_OBTAIN_CPU_TEMP: Command Not Found 'C
Fourdee commented 6 years ago

NanoPi Neo Air WiFi (and possibily all ARMbian devices with onboard WiFi)

[  118.030568] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430a0-sdio.bin for chip 0x00a9a6(43430) rev 0x000000
[  118.033560] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43430a0-sdio.bin failed with error -2
[  118.033580] brcmfmac mmc2:0001:1: Falling back to user helper

root@DietPi:~# ls -lha /lib/firmware/brcm/brcmfmac43430a0-sdio.bin
ls: cannot access '/lib/firmware/brcm/brcmfmac43430a0-sdio.bin': No such file or directory

Contained in armbian-firmware

        #   Check for existing firmware
        #   - ARMbian
        # AUTO_DETECT_FIRMWARE_PKG=$(dpkg --get-selections | grep '^armbian-firmware' | awk '{print $1}')
        # if [ -n "$AUTO_DETECT_FIRMWARE_PKG" ]; then

            # G_AGI $AUTO_DETECT_FIRMWARE_PKG

        # fi
            # Unpacking armbian-firmware (5.35) ...
            # dpkg: error processing archive /var/cache/apt/archives/armbian-firmware_5.35_all      .deb (--unpack):
            # trying to overwrite '/lib/firmware/rt2870.bin', which is also in package firmwa      re-misc-nonfree 20161130-3
            # dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

Options:

For now (to ensure v6.0 release), i've copied the required brcm firmware to image. But i'll need to revisit this for devices with onboard WiFi (before v6.0 release if possible).

Verify:

Fourdee commented 6 years ago

Ok Native PC BIOS: Tried several attempts at this. Unsuccessful in terms of available USB drives failing to boot (even with Debian simply installed and boot enabled in MBR etc). PC/USB issue/incompatibility, unsure, needs further investigation. PREP script is fine.

I'll need to revisit this, however, for now, i'll do a guide that references installing Debian, then forward user to running PREP.

k-plan commented 6 years ago

@Fourdee

only remark:

method (extra 1MB fat partition) is the solution here, however, if i'am being honest, time limited at the moment. It may be after v6.0 is released that we can achieve it (all images need to be re-configured and script changes etc)

YES! :+1:

On last image DietPi_OPiZeroH2-ARMv7-Stretch there no way to configure first config in dietpi.txt So I can't connect with Wi-Fi.

https://github.com/Fourdee/DietPi/issues/1427