[TESTING] OSMC images for Debian Stretch


#1

Following on from: [TESTING] Debian Stretch upgrade for OSMC

Many thanks to all of those who tested our Debian Stretch release. We are now happy to consider this release stable and ready for prime time. We plan to release this as an update on 7th January with an announcement on our blog.

For those that wish to perform a fresh install, here are some disk images. You can either dd these to a bootable medium, or select ‘Local Image’ when using the OSMC Installer.

Cheers

Sam


[TESTING] Debian Stretch upgrade for OSMC
OSMC Unable to find update since Oct
My RF remote has stopped working after a fresh install debian-stretch Kodi v17.6 clean installation on rpi2
SPDIF does not work - Vero 4K
HDTV 720p50 playback problems (stuttering) with DVBViewer setup
#2

Thanks Sam,

looks like the Samba-Server from the Store has Problems to get installed, at first after the install it mentoned to be an error on install and then Update went fine, but the PI isn’t in the network


#3

Hi

Can you please post the logs which show the error?

Sam


#4

Just trying to do it on cli


#5

Works for me, didn’t had an error during install and server runs fine

osmc@osmc-blue:~$ smbclient -L localhost
Enter osmc's password: 
Domain=[WORKGROUP] OS=[Windows 6.1] Server=[Samba 4.5.12-Debian]

	Sharename       Type      Comment
	---------       ----      -------
	osmc            Disk      OSMC Home Directory
	IPC$            IPC       IPC Service (Samba 4.5.12-Debian)
Domain=[WORKGROUP] OS=[Windows 6.1] Server=[Samba 4.5.12-Debian]

	Server               Comment
	---------            -------
	OSMC-BLUE            Samba 4.5.12-Debian
	OSMC-VERO4K          Samba 4.5.12-Debian

	Workgroup            Master
	---------            -------
	WORKGROUP            OSMC-VERO4K

#6

Works on cli.

Log is there

Hope that helps anyway, system is an PI3 btw smbclient is not on the pakage list


#7

The log doesn’t show an attempt to install Samba unfortunately.
If it happens again, let us know.


#8

What do you mean with that? Did you update?

osmc@osmc-blue:~$ dpkg -l | grep smbc
ii  libsmbclient:armhf                   2:4.5.12+dfsg-2+deb9u1            armhf        shared library for communication with SMB/CIFS servers
ii  smbclient                            2:4.5.12+dfsg-2+deb9u1            armhf        command-line SMB/CIFS clients for Unix

#9

I get this:

osmc@osmc:~$ dpkg -l | grep smbc
ii  libsmbclient:armhf                   2:4.5.12+dfsg-2+deb9u1         armhf        shared library for communication with SMB/CIFS servers

#10

And what do you get if you do
sudo apt-get update
sudo apt-get install smbclient


#11

Yup did it this way

And there is it.

osmc@osmc:~$ sudo smbclient -L localhost
Enter root's password:
Domain=[WORKGROUP] OS=[Windows 6.1] Server=[Samba 4.5.12-Debian]

        Sharename       Type      Comment
        ---------       ----      -------
        osmc            Disk      OSMC Home Directory
        IPC$            IPC       IPC Service (Samba 4.5.12-Debian)
        LANGE           Disk      Auto-mount Volume
Domain=[WORKGROUP] OS=[Windows 6.1] Server=[Samba 4.5.12-Debian]

        Server               Comment
        ---------            -------
        FRITZ-NAS            FRITZ!Box
        OSMC                 Samba 4.5.12-Debian

        Workgroup            Master
        ---------            -------
        WORKGROUP            FRITZ-NAS

#12

So all good now ?!?


#13

On this way yes. But is strange that it would not work in the App-Store and that it’s work on cli


#14

It worked for me on the App Store and as @sam_nazarko wrote unfortunately your Kodi log didn’t show any attempt for an installation from App Store.
If you want to recheck, please reinstall the image, enable debug logging and try again to install it from App Store.


#15

So again, new installation with error-log on

Log is there


#16

Tried the installer file for the Vero (Classic) … but get a black screen after OSMC installation and box is dead; router tells me that there wasn’t a DHCP request at all.

Only thing I can provide is the install.log on the SD-card afterwards:

Thu Jan 1 00:00:08 1970 Starting OSMC installer
Thu Jan 1 00:00:13 1970 Detecting device we are running on
Thu Jan 1 00:00:13 1970 Mounting boot filesystem
Thu Jan 1 00:00:13 1970 Trying to mount to MNT_BOOT (/mnt/boot)
Thu Jan 1 00:00:13 1970 Using device->boot: /dev/mmcblk0p1 and FS: fat32
Thu Jan 1 00:00:13 1970 Preseed file found, will attempt to parse
Thu Jan 1 00:00:13 1970 Found a definition for storage: sd
Thu Jan 1 00:00:13 1970 Creating root partition
Thu Jan 1 00:00:13 1970 From a root partition of /dev/mmcblk0p2, I have deduced a base device of /dev/mmcblk0
Thu Jan 1 00:00:13 1970 Determined 255 MB as end of first partition
Thu Jan 1 00:00:13 1970 Calling mkpart for device: /dev/mmcblk0 and fs: ext4 with start 257M and end 100%
Thu Jan 1 00:00:15 1970 Calling fmtpart for partition /dev/mmcblk0p2 and fstype ext4
Thu Jan 1 00:00:35 1970 Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=2 blocks, Stripe width=1024 blocks
483328 inodes, 1931008 blocks
96550 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1979711488
59 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables:  0/59     done                            
Writing inode tables:  0/59     done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information:  0/59 8/59     done


Thu Jan 1 00:00:35 1970 Mounting root
Thu Jan 1 00:00:35 1970 Trying to mount to MNT_ROOT (/mnt/root)
Thu Jan 1 00:00:35 1970 Using device->root: /dev/mmcblk0p2
Thu Jan 1 00:00:35 1970 Extracting files to root filesystem
Thu Jan 1 00:00:35 1970 Starting extract progress...
Thu Jan 1 00:03:05 1970 Extraction of root filesystem completed
Thu Jan 1 00:03:05 1970 Configuring bootloader
Thu Jan 1 00:03:05 1970 Configuring bootloader: moving /boot to appropriate boot partition
Thu Jan 1 00:03:10 1970 Configuring boot cmdline
Thu Jan 1 00:03:10 1970 Configuring /etc/fstab
Thu Jan 1 00:03:10 1970 Successful installation. Dumping log and rebooting system

Tried two different SD-cards but ends in same behavior.
Finally used Vero image 2017.1-1 (local file was still on my PC) … and this works fine.


#17

Does updating from 2017.1-1 using the instructions in the old thread work?

Sam


#18

No, the update this way took ages but finally ends in the same black screen. Box is dead and not visible in the network.


#19

Okay, I’ll take a look at this shortly. It’s probably a GCC6 issue.

Sam


#20

Thanks for doing that test.
Seems that there is some issue with the apt cache, as you just logged in via SSH a minute before was the apt cache generation of that session finished?

Jan 03 17:58:46 osmc mediacenter[338]: Error in function pulse
Jan 03 17:58:46 osmc mediacenter[338]: Traceback (most recent call last):
Jan 03 17:58:46 osmc mediacenter[338]:   File "/usr/share/kodi/addons/script.module.osmcsetting.updates/resources/lib/apt_cache_action.py", line 491, in pulse
Jan 03 17:58:46 osmc mediacenter[338]:     msg = self.fetching
Jan 03 17:58:46 osmc mediacenter[338]: AttributeError: 'Download_Progress' object has no attribute 'fetching'
Jan 03 17:58:46 osmc mediacenter[338]: 2018-01-03 17:58:46.379379 apt_cache_action.py exception occurred
Jan 03 17:58:46 osmc mediacenter[338]: 2018-01-03 17:58:46.379517 apt_cache_action.py exception value : Failed to fetch http://security.debian.org/pool/updates/main/p/perl/perl-modules-5.24_5.24.1-3+deb9u2_all.deb Could not open file /var/cache/apt/archives/partial/perl-modules-5.24_5.24.1-3+deb9u2_all.deb - open (2: No such file or directory)