Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[Mut@nt HD2400] Can't Start Samba

  • Thread starter Thread starter JeanReno
  • Start date Start date
I've tried @SpaceRat's "test" and at the end get the following.....

Code:
root@et10000:~# [COLOR="#0000FF"]opkg install packagegroup-base-samba[/COLOR]
Couldn't find anything to satisfy 'packagegroup-base-samba'.
Unknown package 'packagegroup-base-samba'.
Configuring ntpdate.
Collected errors:
 * opkg_install: Cannot install package packagegroup-base-samba.
root@et10000:~#
 
Well that's done it!!!

I can't say I understand, but has something changed since yesterday? (just seen your previous post - I understand now, many thanks)

Code:
Last login: Thu Jan 26 11:04:46 GMT 2017 on pts/0
root@et10000:~# opkg update
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/3rdparty/Packages.gz.
Updated source 'openvix-3rdparty'.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/all/Packages.gz.
Updated source 'openvix-all'.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/et10000/Packages.gz.
Updated source 'openvix-et10000'.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/et10000_3rdparty/Packages.gz.
Updated source 'openvix-et10000_3rdparty'.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/mips32el/Packages.gz.
Updated source 'openvix-mips32el'.
root@et10000:~#
root@et10000:~# opkg install packagegroup-base-samba
Installing packagegroup-base-samba (1.0-r83.1) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/et10000/packagegroup-base-samba_1.0-r83.1_et10000.ipk.
cifs: unsatisfied recommendation for kernel-module-cifs
packagegroup-base-smbfs: unsatisfied recommendation for kernel-module-cifs
packagegroup-base-smbfs: unsatisfied recommendation for kernel-module-smbfs
Installing packagegroup-base-smbfs-client (1.0-r83.1) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/et10000/packagegroup-base-smbfs-client_1.0-r83.1_et10000.ipk.
Installing packagegroup-base-smbfs (1.0-r83.1) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/et10000/packagegroup-base-smbfs_1.0-r83.1_et10000.ipk.
Installing cifs (5.9-r3) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/mips32el/cifs_5.9-r3_mips32el.ipk.
Installing smbclient (3.6.25-r6) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/mips32el/smbclient_3.6.25-r6_mips32el.ipk.
Installing packagegroup-base-smbfs-utils (1.0-r83.1) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/et10000/packagegroup-base-smbfs-utils_1.0-r83.1_et10000.ipk.
Installing samba (3.6.25-r6) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/mips32el/samba_3.6.25-r6_mips32el.ipk.
Installing packagegroup-base-smbfs-server (1.0-r83.1) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/et10000/packagegroup-base-smbfs-server_1.0-r83.1_et10000.ipk.
Installing samba-base (3.6.25-r6) on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.2/et10000/mips32el/samba-base_3.6.25-r6_mips32el.ipk.
 Removing any system startup links for samba ...
Configuring smbclient.
Configuring samba.
Configuring packagegroup-base-smbfs-utils.
Configuring samba-base.
 Adding system startup for /etc/init.d/samba.
Starting Samba: smbd nmbd.
Configuring cifs.
Configuring packagegroup-base-smbfs.
Configuring packagegroup-base-smbfs-client.
Configuring packagegroup-base-smbfs-server.
Configuring packagegroup-base-samba.
root@et10000:~#

This is what I had before the "test"...
Code:
root@et10000:~# opkg list-installed *smb*
smbclient - 3.6.25-r6
root@et10000:~# opkg list-installed *samb*
root@et10000:~# opkg list-installed *cifs*

and now.....
Code:
root@et10000:~# opkg list-installed *smb*
packagegroup-base-smbfs - 1.0-r83.1
packagegroup-base-smbfs-client - 1.0-r83.1
packagegroup-base-smbfs-server - 1.0-r83.1
packagegroup-base-smbfs-utils - 1.0-r83.1
smbclient - 3.6.25-r6
root@et10000:~# opkg list-installed *samb*
packagegroup-base-samba - 1.0-r83.1
samba - 3.6.25-r6
samba-base - 3.6.25-r6
root@et10000:~# opkg list-installed *cifs*
cifs - 5.9-r3
root@et10000:~#
 
Last edited:
Ok, I think I found the reason:
As OpenViX has crippled their base image by wiping out Samba entirely, there is nothing that pulls packagegroup-base-samba and its dependencies onto the feed.

https://github.com/oe-alliance/oe-alliance-core/commit/7d6e383d83bce6fcd6da00f7ec509916f6f350bc
should fix that.
That would be because there is great confusion about what "samba" is.
As far as mounting remote CIFS shares (and looking for them) on a system the only thing needed was smbclient (to find them) as the cifs kernel module was already in place. The number of package splits for samba and cifs seems to be way too complicated.
 
Well that's done it!!!
I can't say I understand, but has something changed since yesterday? (just seen your previous post - I understand now, many thanks)

Well, if "opkg update" fixed things for you, my commit on Github has nothing to do with it, that won't be instant.
It shouldn't harm either, it just ensures that each and every distro has complete Samba support on the feed, even if they haven't built it into the image (Most have it in the base image anyways).

Your problem appears to be that you were unaware of opkg update:
It refreshs the box' list of what is available on the feeds.

"opkg update" is required before you can do any opkg install or opkg upgrade action.
Without current lists for the feeds, opkg only knows about packages that are already installed.
 
We shouldn't really have to be manually refreshing feeds to obtain modules that are (albeit, now an 'optional') part of Vix.
 
That would be because there is great confusion about what "samba" is.
As far as mounting remote CIFS shares (and looking for them) on a system the only thing needed was smbclient (to find them) as the cifs kernel module was already in place. The number of package splits for samba and cifs seems to be way too complicated.
Well, OpenViX introduced all those Samba meta-packages ...

And you are still wrong.

Requirements are
  • Kernel support for CIFS/SMB (Actually nobody will really be using CIFS, at least not intentionally, but SMB), referred to as "kernel-module-cifs", either built-in (Almost all boxes) or as a loadable module (Very old boxes with tight space on kernel partition)
  • Mount helper mount.cifs, shipped in package "cifs".

These two form the actual client. Nothing more is required for client use, as long as you edit /etc/auto.network (Preferred) or /etc/fstab (Not so good for Windows servers) yourself.

The package "smbclient" offers highly limited support for attempts to find legacy (IBM OS/2, Windows 9x, Windows NT 4.0, Windows 2000, Windows XP, Windows Vista) types of shares on the net.
It assists the NetworkBrowser in making bad entries to auto.network or fstab.

The actual server is split across the packages samba and samba-base:
While the core server is in samba-base, the package samba contains some utilities to control the server, of which one (testparm) is required for the start script of Samba.
 
We shouldn't really have to be manually refreshing feeds to obtain modules that are (albeit, now an 'optional') part of Vix.
That's how all package managers work.
For "apt-get install blah" to work you also need to perform "apt-get update" first.

The only thing the distro could make to fake remove the need to perform "opkg update" first would be to silently do it for you, e.g. when installing Samba via the E2 network menu.
But not everybody has unlimited traffic - there actually are E2 users with only cellular (UMTS/LTE) internet access - and initiating useless downloads for any package install wouldn't do your traffic any good.
 
That's how all package managers work.
For "apt-get install blah" to work you also need to perform "apt-get update" first.

The only thing the distro could make to fake remove the need to perform "opkg update" first would be to silently do it for you, e.g. when installing Samba via the E2 network menu.
But not everybody has unlimited traffic - there actually are E2 users with only cellular (UMTS/LTE) internet access - and initiating useless downloads for any package install wouldn't do your traffic any good.

I wouldn't call it a useless download. 'Useless' would be Vix trying to download packages that don't exist because it hasn't bothered to check it's reading from an up-to-date list, surely?
 
We applied fixes some time back. If you follow the normal process, it should work. I tried it yesterday.

Please repeat exactly how you do/would do things from square one on a newly installed image.
 
I wouldn't call it a useless download. 'Useless' would be Vix trying to download packages that don't exist because it hasn't bothered to check it's reading from an up-to-date list, surely?
That depends on how you define "up-to-date".

For OpenATV where builds happen nightly the list is usually up-to-date for about 24hrs.
Once you have for example done "opkg update && opkg upgrade", there is no need to do another "opkg update" before package installations until the next build.

For OpenViX with its "releases", the principle remains the same, except that the lists would stay up-to-date for even longer, provided OpenViX doesn't update the feeds in between "releases".
In that case, "opkg update" once would stay up-to-date until the next "release", making automated "opkg update" in between even more useless.

The only thing OpenViX could do, provided their feed stays frozen in between "releases", would be to add the lists into the image at build time.

But I suggest you rather get used to how things work, because it's that way with any other package manager on any other Linux system too.
 
The point is that the GUI user shouldn't need to perform manual workarounds and shouldn't care about what happens in the background. Its a menu option, it should work for them without technical intervention.
 
You shouldn't. Please answer as to what steps you did/would do from a new install. We can compare what's gone on and improve things even more.
 
You shouldn't. Please answer as to what steps you did/would do from a new install. We can compare what's gone on and improve things even more.
I ran @SpaceRat's "test" from a clean install of 4.2.027, posted here..

http://www.world-of-satellite.com/s...-t-Start-Samba&p=436388&viewfull=1#post436388

I posted all steps in detail (apart from needing "opkg --force-depends remove smbclient" to get rid of smbclient).

Whether all were actually needed, pass.

I haven't tried this, but "opkg update", followed by a GUI samba install might work - do you want me to have a go?
 
Last edited:
I haven't tried this, but "opkg update", followed by a GUI samba install might work - do you want me to have a go?

The answer is (from a clean install of 027) - it does work.
 
Last edited:
You shouldn't. Please answer as to what steps you did/would do from a new install. We can compare what's gone on and improve things even more.

I need to do an update this evening since I'm on .026. It's a (yet another, grrr) Linux kernel update, so will use Image Manager.

It will be something along the lines of . . .

Setup - Vix - Backup Manager - New Backup
Setup - Vix - Image Manager - Downloads (choose latest image)
Setup - Vix - Image Manager - Restore (choose latest image)
Restore plugins and settings upon boot
Re-download LCD skins and skin etc since they never seem to be retained
Check Samba . . .

I'll see how it goes this evening and report back (toddler willing).
 
Setup - Vix - Backup Manager - New Backup
This is done automatically, has been for a while. No harm doing it manually though.

Setup - Vix - Image Manager - Downloads (choose latest image)
Setup - Vix - Image Manager - Restore (choose latest image)
Restore plugins and settings upon boot
Re-download LCD skins and skin etc since they never seem to be retained
They should be now, provided they are on server. The list of installed plugins now only lists packages, not dependencies. Dependencies will be installed automatically. We have removed the kernel restriction, so everything that is on server should install.

As an extra measure, you can use this: http://www.world-of-satellite.com/s...talled-plugins&p=435697&viewfull=1#post435697


Check Samba . . .
 
The answer is (from a clean install of 027) - it does work.

I'm going to have to qualify that. Everything looks ok, I can see the ET10K from my pc and the ET10K can see my NAS.

However, playing a recording in another room using a fire tv is constantly buffering and unwatchable, it's never happened before.

The box is actually on 4.2.028 now. I've moved back to 4.2.026 and playback thru' the fire tv is working fine.

I did notice some odd delays using telnet when messing about earlier today on 027, but thought nothing about it at the time.
 
Just a thought - my Sundtek usb tuner doesn't work on 027, and my rtl8192cu usb wireless dongle isn't too happy either.
 

OpenViX Feeds Status

Back
Top