(ARCHIVED) Debian Jessie Images (3.10.102 BSP Kernel) New Release

[rahlquist]

how long before you rebooted after doing the update/install?

I think it's a matter of restarting the device before all data is written to disk that maybe affecting things .

On a separate note I have a work around on getting 720 desktop resolution mentioned in my first post for anyone to try with any of the Debian images I posted. It should work until we get a proper driver in place for display (mali).

Ok still having odd corruption like issues here. I have use the SD consortiums SD card formatter v4.0 to format my card. Then I ran h2testw.exe and got no errors or issues from it, then I coped over a fresh image using win32diskimage. On login I ran a ls /boot -al and get this

Code:

pine64user@debianpine64:~$ ls /boot -al
ls: cannot access /boot/pine64: Input/output error
total 1076
drwxr-xr-x  4 root root   16384 Jan  1  1970 .
drwxr-xr-x 21 root root    4096 Apr  6 00:13 ..
-rwxr-xr-x  1 root root 1076058 Apr  3 11:16 initrd.img
d?????????  ? ?    ?          ?            ? pine64
drwxr-xr-x  2 root root    2048 Apr  8 07:56 System Volume Information
-rwxr-xr-x  1 root root     137 Jan  1  2010 uEnv.txt
pine64user@debianpine64:~$ ls /boot/pine64 -al
ls: cannot access /boot/pine64: Input/output error
pine64user@debianpine64:~$

On my serial console I see this;

Code:

[  198.044915] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)
[  198.053813] FAT-fs (mmcblk0p1): Filesystem has been set read-only

I am going to try to download another of your images and see if I have the same issue. If I do I suspect I have a faulty/flaky card or perhaps something wrong with my pine. Before anyone asks voltage in is showing as 5.05 and out on the usb ports is 5.03.

BTW. Any idea why with every new image install to my flash card the pine uses a new MAC address for DHCP?


EDIT 
Definitely think my copy of the XFCE image is corrupt. (hard to tell without md5's hint hint). After a wipe of my card, windows disk check, win32 image install and then boot during boot I get;

Code:

[   14.208113] systemd[1]: Started Journal Service.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Configuration File System.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Apply Kernel Variables.
        Starting Copy rules generated while the root was ro...
        Starting LSB: Set preliminary keymap...
[  OK  ] Started Copy rules generated while the root was ro.
[  OK  ] Started LSB: Set preliminary keymap.
[  OK  ] Created slice system-systemd\x2drfkill.slice.
        Starting Remount Root and Kernel File Systems...
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Reached target Sound Card.
[  OK  ] Found device /dev/mmcblk0p1.
        Starting File System Check on /dev/mmcblk0p1...
[   15.014258] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[  OK  ] Started Remount Root and Kernel File Systems.
        Starting Load/Save RF Kill Switch Status of rfkill0...
        Starting Various fixups to make systemd work better on Debian...
        Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Started Load/Save RF Kill Switch Status of rfkill0.
[  OK  ] Started Various fixups to make systemd work better on Debian.
[  OK  ] Started Load/Save Random Seed.
[    8.482132] systemd-fsck[1465]: fsck.fat 3.0.27 (2014-11-12)
[    8.483625] systemd-fsck[1465]: /PINE64
[  OK  ] Started File System Check on /dev/mmcblk0p1.
[    8.521418] systemd-fsck[1465]: Has a large number of bad entries. (2/5)
[    8.560686] systemd-fsck[1465]: Not dropping it in auto-mode.
[    8.561319] systemd-fsck[1465]: /PINE64/.
[    8.561849] systemd-fsck[1465]: Bad short file name (.).
[    8.562415] systemd-fsck[1465]: Auto-renaming it.
[    8.562944] systemd-fsck[1465]: Renamed to FSCK0000.000
[    8.563474] systemd-fsck[1465]: /PINE64/..
[    8.564004] systemd-fsck[1465]: Bad short file name (..).
[    8.564531] systemd-fsck[1465]: Auto-renaming it.
[    8.565073] systemd-fsck[1465]: Renamed to FSCK0000.001
        Mounting /boot...
[    8.565672] systemd-fsck[1465]: /PINE64/FSCK0000.000
[    8.660727] systemd-fsck[1465]: File size is 0 bytes, cluster chain length is > 0 bytes.
[    8.661383] systemd-fsck[1465]: Truncating file to 0 bytes.
[    8.661915] systemd-fsck[1465]: Performing changes.
[    8.662457] systemd-fsck[1465]: /dev/mmcblk0p1: 9 files, 6117/25541 clusters
[  OK  ] Mounted /boot.
[  OK  ] Reached target Local File Systems.

EDIT2
Ok pulled the lxde image and that too is giving me errors.

Code:

[  OK  ] Started Load/Save RF Kill Switch Status of rfkill0.
[  OK  ] Started Various fixups to make systemd work better on Debian.
[  OK  ] Started Load/Save Random Seed.
[    8.274966] systemd-fsck[1474]: fsck.fat 3.0.27 (2014-11-12)
[    8.276396] systemd-fsck[1474]: /PINE64
[    8.321241] systemd-fsck[1474]: Has a large number of bad entries. (2/5)
[    8.322399] systemd-fsck[1474]: [Not dropping it in auto-mode.  OK
] Started File System Check on /dev/mmcblk0p1.
[    8.341476] systemd-fsck[1474]: /PINE64/.
        Mounting /boot...
[    8.380717] systemd-fsck[1474]: Bad short file name (.).
[    8.420791] systemd-fsck[1474]: Auto-renaming it.
[    8.440722] systemd-fsck[1474]: Renamed to FSCK0000.000
[    8.441506] systemd-fsck[1474]: /PINE64/..
[    8.442036] systemd-fsck[1474]: Bad short file name (..).
[    8.442593] systemd-fsck[1474]: Auto-renaming it.
[    8.443142] systemd-fsck[1474]: Renamed to FSCK0000.001
[    8.443675] systemd-fsck[1474]: /PINE64/FSCK0000.000
[    8.444205] systemd-fsck[1474]: File size is 0 bytes, cluster chain length is > 0 bytes.
[    8.444740] systemd-fsck[1474]: Truncating file to 0 bytes.
[    8.445280] systemd-fsck[1474]: Performing changes.
[    8.445813] systemd-fsck[1474]: /dev/mmcblk0p1: 9 files, 6117/25541 clusters
[  OK  ] Mounted /boot.

So if no one else sees the fsck issues on their first boot then I will have to assume I have a card issue.