Scripting news

https://github.com/MiSTer-devel/Main_MiSTer/wiki

Moderators: Mug UK, Zorro 2, Greenious, spiny, Sorgelig, Moderator Team

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Tue Aug 20, 2019 4:09 pm

Scripting news:
===========================
Scripts_MiSTer: 2019-08-20
- ini_settings.sh - Version 1.1.11 - 2019-08-20 - Added support for direct_video.
===========================

Regards.

Locutus73

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Wed Aug 21, 2019 11:01 am

Scripting news:
===========================
Updater_script_MiSTer: 2019-08-21
- mister_updater.sh - Version 3.2 - 2019-08-21 - Implemented GOOD_CORES_URL for having a list of curated "good" cores.

Specifies an optional URL with a text file containing a curated list of "good" cores.
If a core is specified there, it will be preferred over the latest "bleeding edge" core in its repository.
The text file can be something simple as "Genesis_20190712.rbf SNES_20190703.rbf"

You can see an example list here https://raw.githubusercontent.com/MiSTe ... _cores.txt
Obviously, as always, you can have two different updaters with two different ini files, i.e. one update_curated.sh with its update_curated.ini with the GOOD_CORES_URL parameter for downloading "stable" cores, and one update_bleeding_edge.sh with its update_bleeding_edge.ini without the parameter for testing the latest cores in their repositories.
===========================

Regards.

Locutus73

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Wed Aug 21, 2019 2:43 pm

Scripting news:
===========================
Updater_script_MiSTer: 2019-08-21
- mister_updater.sh - Version 3.3 - 2019-08-21 - Implemented CREATE_CORES_DIRECTORIES; when "true" (default value), the updater will create the core directory (i.e. /media/fat/Amiga for Minimig core, /media/fat/SNES for SNES core) the first time the core is downloaded.
===========================

Regards.

Locutus73

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Sat Sep 07, 2019 10:38 am

Scripting news:

===========================
Updater_script_MiSTer: 2019-09-07
- mister_updater.sh - Version 3.3.1 - 2019-09-07 - Improved core directories creation; added NeoGeo xml download/update to ADDITIONAL_REPOSITORIES.
===========================
https://github.com/MiSTer-devel/Updater_script_MiSTer

===========================
Scripts_MiSTer: 2019-09-07
- ini_settings.sh - Version 1.1.12 - 2019-09-07 - Added support for hdmi_limited=2 (16-255) for AG620x DACs; to be used with direct_video=1.
===========================
https://github.com/MiSTer-devel/Scripts_MiSTer


Regards.

Locutus73

SegaMan
Atari maniac
Atari maniac
Posts: 83
Joined: Sat Oct 27, 2018 12:59 pm

Re: Scripting news

Postby SegaMan » Sat Sep 21, 2019 5:09 pm

I am a bit confused.

I use the update script for the arcade title with its own .ini

In the .ini:
REPOSITORIES_FILTER="arcade-cores"

When I run the script, it says to me at all cores "new core". Even with those that I have installed.
Is that correct?

high5
Atari User
Atari User
Posts: 31
Joined: Thu Dec 27, 2018 10:29 pm

Re: Scripting news

Postby high5 » Sat Sep 21, 2019 5:59 pm

Did someone manage to update Jotegos cores (external git) via update script?

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Mon Sep 23, 2019 11:04 am

SegaMan wrote:I am a bit confused.

I use the update script for the arcade title with its own .ini

In the .ini:
REPOSITORIES_FILTER="arcade-cores"

When I run the script, it says to me at all cores "new core". Even with those that I have installed.
Is that correct?


Can you post your entire ini files (both the arcade one and the regular one)?

Thank you in advance.
Regards.

SegaMan
Atari maniac
Atari maniac
Posts: 83
Joined: Sat Oct 27, 2018 12:59 pm

Re: Scripting news

Postby SegaMan » Mon Sep 23, 2019 11:17 am

update_arcade.ini

DOWNLOAD_NEW_CORES="false"
SD_INSTALLER_URL="https://github.com/MiSTer-devel/SD-Installer-Win64_MiSTer"
REPOSITORIES_FILTER="arcade-cores"


update_console.ini

DOWNLOAD_NEW_CORES="false"
SD_INSTALLER_URL="https://github.com/MiSTer-devel/SD-Installer-Win64_MiSTer"
REPOSITORIES_FILTER="Atari2600 Gameboy Genesis NeoGeo NES Odyssey2 SMS SNES TurboGrafx16 Vectrex"

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Thu Sep 26, 2019 6:05 pm

SegaMan wrote:update_arcade.ini

DOWNLOAD_NEW_CORES="false"
SD_INSTALLER_URL="https://github.com/MiSTer-devel/SD-Installer-Win64_MiSTer"
REPOSITORIES_FILTER="arcade-cores"


update_console.ini

DOWNLOAD_NEW_CORES="false"
SD_INSTALLER_URL="https://github.com/MiSTer-devel/SD-Installer-Win64_MiSTer"
REPOSITORIES_FILTER="Atari2600 Gameboy Genesis NeoGeo NES Odyssey2 SMS SNES TurboGrafx16 Vectrex"


With these settings the updater should say “New Core” if it finds a core in the wiki which is not in the local SD and not download it. If it finds an update for a core in the SD it should download it, otherwise it should just go on. Can you confirm (doublecheck) this is not working for you?

[EDIT]
Regardless of the possible bug we are analyzing, why are you using both DOWNLOAD_NEW_CORES="false" and REPOSITORIES_FILTER? I mean, it's legit, but usually REPOSITORIES_FILTER is enough to filter cores you want.

Thank you in advance.

SegaMan
Atari maniac
Atari maniac
Posts: 83
Joined: Sat Oct 27, 2018 12:59 pm

Re: Scripting news

Postby SegaMan » Fri Sep 27, 2019 6:41 pm

Locutus73 wrote:
With these settings the updater should say “New Core” if it finds a core in the wiki which is not in the local SD and not download it. If it finds an update for a core in the SD it should download it, otherwise it should just go on. Can you confirm (doublecheck) this is not working for you?



He tells "New Core" about every core, whether it's on my SD card or not.
Tested with an old core of Ghoust'n Goblins. It also tells me "New Core" with the indication of the last version, but does not invite them.

Locutus73 wrote:[EDIT]
Regardless of the possible bug we are analyzing, why are you using both DOWNLOAD_NEW_CORES="false" and REPOSITORIES_FILTER? I mean, it's legit, but usually REPOSITORIES_FILTER is enough to filter cores you want.

Thank you in advance.



I thought this way I would not have to enter each core individually in the repositories filter to keep my cores up to date.
:shrug:

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Sat Sep 28, 2019 8:56 am

SegaMan wrote:
Locutus73 wrote:
With these settings the updater should say “New Core” if it finds a core in the wiki which is not in the local SD and not download it. If it finds an update for a core in the SD it should download it, otherwise it should just go on. Can you confirm (doublecheck) this is not working for you?



He tells "New Core" about every core, whether it's on my SD card or not.
Tested with an old core of Ghoust'n Goblins. It also tells me "New Core" with the indication of the last version, but does not invite them.

Locutus73 wrote:[EDIT]
Regardless of the possible bug we are analyzing, why are you using both DOWNLOAD_NEW_CORES="false" and REPOSITORIES_FILTER? I mean, it's legit, but usually REPOSITORIES_FILTER is enough to filter cores you want.

Thank you in advance.



I thought this way I would not have to enter each core individually in the repositories filter to keep my cores up to date.
:shrug:



I just tried your update_arcade.ini and it worked correctly here.
Here's an excerpt of my updater output.

Code: Select all

Downloading and executing
mister_updater.sh

Checking SD-Installer-Win64
URL: https://github.com/MiSTer-devel/SD-Installer-Win64_MiSTer
Nothing to update

Checking Main
URL: https://github.com/MiSTer-devel/Main_MiSTer
Nothing to update

Checking Menu
URL: https://github.com/MiSTer-devel/Menu_MiSTer
Nothing to update

Checking Arcade-1942
URL: https://github.com/MiSTer-devel/Arcade-1942_MiSTer
Nothing to update

Checking Arcade-1943
URL: https://github.com/MiSTer-devel/Arcade-1943_MiSTer
New core: 1943_20190509.rbf

Checking Arcade-Alibaba
URL: https://github.com/MiSTer-devel/Arcade-Alibaba_MiSTer
Downloading Alibaba_20180313.rbf
URL: https://github.com/MiSTer-devel/Arcade-Alibaba_MiSTer/blob/master/releases/Arcade-Alibaba_20180313.rbf?raw=true
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   167    0   167    0     0    449      0 --:--:-- --:--:-- --:--:--   455
100   178  100   178    0     0    289      0 --:--:-- --:--:-- --:--:--   289
100 3146k  100 3146k    0     0  1860k      0  0:00:01  0:00:01 --:--:-- 3620k
Deleting old Alibaba files

Checking Arcade-Azurian
URL: https://github.com/MiSTer-devel/Arcade-Azurian_MiSTer
Nothing to update

Checking Arcade-Amidar
URL: https://github.com/MiSTer-devel/Arcade-Amidar_MiSTer
Nothing to update

Checking Arcade-Arkanoid
URL: https://github.com/MiSTer-devel/Arcade-Arkanoid_MISTer
New core: Arkanoid_20190227.rbf

Checking Arcade-Asteroids
URL: https://github.com/MiSTer-devel/Arcade-Asteroids_MISTer
New core: Asteroids_20190614.rbf

Checking Arcade-AsteroidsDeluxe
URL: https://github.com/MiSTer-devel/Arcade-AsteroidsDeluxe_MISTer
New core: AsteroidsDeluxe_20190614.rbf

[...]


As you can see:
- Arcade-1942 reported Nothing to update because it was on the SD and it was already updated
- Arcade-1943 reported New core: 1943_20190509.rbf because it was not on the SD and, with DOWNLOAD_NEW_CORES="false", we don't want new cores not on the SD to be downloaded
- Arcade-Alibaba reported Downloading Alibaba_20180313.rbf because it was on the SD and it needed to be updated

All worked as expected on my side: are you using the latest mister_updater.sh or the short, autoupdating, update.sh? Can you doublecheck your setup, including your paths?

Thank you in advance.
Best regards.

SegaMan
Atari maniac
Atari maniac
Posts: 83
Joined: Sat Oct 27, 2018 12:59 pm

Re: Scripting news

Postby SegaMan » Sat Sep 28, 2019 9:10 am

I am using the latest update.sh

Arcade Cores are in "_Arcade" Folder on root of the SDCard.

Core names are all like "Arcade-GnG_20190310.rbf".

It does not matter if the core is in the _arcade folder or not.
It's always called "New Core".

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Sat Sep 28, 2019 9:52 am

Scripting news:

===========================
Scripts_MiSTer: 2019-09-27
- added new other_authors directory for hosting scripts done by other authors.
- added build_mame_roms.sh to other_authors.
===========================
https://github.com/MiSTer-devel/Scripts_MiSTer

===========================
Updater_script_MiSTer: 2019-09-28
- mister_updater.sh - Version 3.3.2 - 2019-09-28 - Implemented MD5 based check in addition to file timestamp for main menu and main MiSTer executable; added https://github.com/MiSTer-devel/Scripts ... er_authors to ADDITIONAL_REPOSITORIES.
===========================
https://github.com/MiSTer-devel/Updater_script_MiSTer



Regards.

Locutus73

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Sat Sep 28, 2019 3:48 pm

SegaMan wrote:Core names are all like "Arcade-GnG_20190310.rbf".

That’s (should be) the culprit.
The updater uses

Code: Select all

#Specifies if the "Arcade-" prefix will be removed in local arcade cores.
REMOVE_ARCADE_PREFIX="true"

by default.
So it changes and expects GnG_20190310.rbf and not Arcade-GnG_20190310.rbf as core name... so it won’t find any of your cores if they are all Arcade- prefixed.

You can either remove the Arcade- prefix from your arcade cores or set REMOVE_ARCADE_PREFIX="false" in your ini file.

Regards.

SegaMan
Atari maniac
Atari maniac
Posts: 83
Joined: Sat Oct 27, 2018 12:59 pm

Re: Scripting news

Postby SegaMan » Sat Sep 28, 2019 6:05 pm

thx @Locutus73 :cheers:

The PREFIX was the problem!

A thought about that.
The arcade cores listed in github carry all the prefix in the name when downloading.
Would not it be better to set REMOVE_ARCADE_PREFIX =" false " as default?
In my opinion, that would be more logical.

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Sun Sep 29, 2019 10:23 am

Scripting news:
===========================
Updater_script_MiSTer: 2019-09-29
- MiSTer Updater script for PC (Windows and Linux)

MiSTer Updater script for PC (Windows and Linux)
Download updater-pc.zip and extract updater-pc directory on the root of your MiSTer SD (don't put it in any SD subdirectory, it must reside in its root). On Windows execute update-win.bat, on Linux execute update-linux.sh.
Windows binaries licenses are under licenses directory in the zip file.

- curl https://curl.haxx.se/ (LICENSE https://github.com/curl/curl/blob/master/COPYING)
- Cygwin https://www.cygwin.com/ (LICENSE https://cygwin.com/COPYING.LIB)
- GNU tools https://www.gnu.org/ (LICENSE https://cygwin.com/COPYING)
===========================
https://github.com/MiSTer-devel/Updater ... updater-pc

Regards.

Locutus73

mutmuthux
Atariator
Atariator
Posts: 22
Joined: Mon Mar 04, 2019 8:11 am

Re: Scripting news

Postby mutmuthux » Thu Oct 10, 2019 7:26 am

Locutus73 wrote:- added build_mame_roms.sh to other_authors.


Hi Locutus73,
many thanks for your code skills on MiSTer :)

Now that build_mame_roms.sh is out i though it time to get my NAS shares mounted to MiSTer. Just hoping to bug you or another helper here as I have some trouble mounting cifs :)

I am getting the error
mount: wrong fs, bad option, bad superblock ... etc
there are some other bits suggesting looking at logs or having helper program ... but this is beyond my knowledge :(

I have the following options in cifs_mount.sh

Code: Select all

#=========   USER OPTIONS   =========
#You can edit these user options or make an ini file with the same
#name as the script, i.e. mount_cifs.ini, containing the same options.

#Your CIFS Server, i.e. your NAS name or its IP address.
SERVER="\\myNASname\MAME_2016_Arcade_Romsets\roms"

#The share name on the Server.
SHARE="MiSTer"

#The user name, leave blank for guest access.
USERNAME="mister"

#The user password, irrelevant (leave blank) for guest access.
PASSWORD="mister123"

#Optional user domain, when in doubt leave blank.
DOMAIN=""

#Local directory/directories where the share will be mounted.
#- It can ba a single directory, i.e. "_CIFS", so the remote share, i.e. \\NAS\MiSTer
#  will be directly mounted on /media/fat/_CIFS (/media/fat is the root of the SD card).
#- It can be a pipe "|" separated list of directories, i.e. "Amiga|C64|NES|SNES",
#  so the share subdirectiories with those names,
#  i.e. \\NAS\MiSTer\Amiga, \\NAS\MiSTer\C64, \\NAS\MiSTer\NES and \\NAS\MiSTer\SNES
#  will be mounted on local /media/fat/Amiga, /media/fat/C64, /media/fat/NES and /media/fat/SNES.
#- It can be an asterisk "*": when SINGLE_CIFS_CONNECTION="true",
#  all the directories in the remote share will be listed and mounted locally,
#  except the special ones (i.e. linux and config);
#  when SINGLE_CIFS_CONNECTION="false" all the directories in the SD root,
#  except the special ones (i.e. linux and config), will be mounted when one
#  with a matching name is found on the remote share.
LOCAL_DIR="_ArcadeRoms"

#Optional additional mount options, when in doubt leave blank.
#If you have problems not related to username/password, you can try "vers=2.0" or "vers=3.0".
ADDITIONAL_MOUNT_OPTIONS=""

#"true" in order to wait for the CIFS server to be reachable;
#useful when using this script at boot time.
WAIT_FOR_SERVER="false"

#"true" for automounting CIFS shares at boot time;
#it will create start/kill scripts in /etc/network/if-up.d and /etc/network/if-down.d.
MOUNT_AT_BOOT="false"



#========= ADVANCED OPTIONS =========
BASE_PATH="/media/fat"
#MISTER_CIFS_URL="https://github.com/MiSTer-devel/CIFS_MiSTer"
KERNEL_MODULES="md4.ko|md5.ko|des_generic.ko|fscache.ko|cifs.ko"
IFS="|"
SINGLE_CIFS_CONNECTION="true"
#Pipe "|" separated list of directories which will never be mounted when LOCAL_DIR="*"
SPECIAL_DIRECTORIES="config|linux|System Volume Information"



I do get a message at the end
_ArcadeRoms mounted
Done!

so the mount works but access to the NAS is failing ??

anyone got any ideas where to start looking please ?
thanks

edit - my nas is a synology with SMB1 and 2 on, basically stock settings with added user 'mister' setup with RO access to the roms

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Tue Oct 15, 2019 3:17 pm

mutmuthux wrote:I am getting the error
mount: wrong fs, bad option, bad superblock ... etc
there are some other bits suggesting looking at logs or having helper program ... but this is beyond my knowledge :(

Hi, usually you can get some meaningful logs using the dmesg command.
It could be something regarding the CIFS protocol version, so something like
ADDITIONAL_MOUNT_OPTIONS="vers=2.0"
could help, but probably we'll understand it better with the dmesg output.

P.S.: I'm not sure you can mount a subdir of a share...

Regards.

mutmuthux
Atariator
Atariator
Posts: 22
Joined: Mon Mar 04, 2019 8:11 am

Re: Scripting news

Postby mutmuthux » Sat Oct 19, 2019 4:47 am

Locutus73 wrote:
mutmuthux wrote:I am getting the error
mount: wrong fs, bad option, bad superblock ... etc
there are some other bits suggesting looking at logs or having helper program ... but this is beyond my knowledge :(

Hi, usually you can get some meaningful logs using the dmesg command.
It could be something regarding the CIFS protocol version, so something like
ADDITIONAL_MOUNT_OPTIONS="vers=2.0"
could help, but probably we'll understand it better with the dmesg output.

P.S.: I'm not sure you can mount a subdir of a share...

Regards.


Hi Locutus, thanks for the suggestions and help :)

my dmesg | tail output is

Code: Select all

/root# dmesg | tail
[  953.450412] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  958.408356] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  969.988330] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  976.914375] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  977.737617] Unable to determine destination address.
[  982.380329] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[ 1063.866428] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[ 1064.684547] Unable to determine destination address.
[ 1080.632440] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[ 1082.450979] Unable to determine destination address.


full dmesg from cold restart here

Code: Select all

/root# dmesg
[    0.194378] usbserial: USB Serial support registered for vivopay
[    0.194420] usbserial: USB Serial support registered for moto_modem
[    0.194464] usbserial: USB Serial support registered for motorola_tetra
[    0.194508] usbserial: USB Serial support registered for novatel_gps
[    0.194562] usbserial: USB Serial support registered for hp4x
[    0.194612] usbserial: USB Serial support registered for suunto
[    0.194649] usbserial: USB Serial support registered for siemens_mpi
[    0.195541] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[    0.195558] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 2
[    0.195598] vhci_hcd: created sysfs vhci_hcd.0
[    0.195838] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.195848] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.195855] usb usb2: Product: USB/IP Virtual Host Controller
[    0.195927] usb usb2: Manufacturer: Linux 4.19.0-socfpga-r1 vhci_hcd
[    0.195934] usb usb2: SerialNumber: vhci_hcd.0
[    0.196454] hub 2-0:1.0: USB hub found
[    0.196502] hub 2-0:1.0: 8 ports detected
[    0.197448] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[    0.197462] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 3
[    0.197582] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    0.197761] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[    0.197770] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.197777] usb usb3: Product: USB/IP Virtual Host Controller
[    0.197784] usb usb3: Manufacturer: Linux 4.19.0-socfpga-r1 vhci_hcd
[    0.197790] usb usb3: SerialNumber: vhci_hcd.0
[    0.198302] hub 3-0:1.0: USB hub found
[    0.198352] hub 3-0:1.0: 8 ports detected
[    0.199465] usbcore: registered new device driver usbip-host
[    0.199691] mousedev: PS/2 mouse device common for all mice
[    0.199819] usbcore: registered new interface driver appletouch
[    0.199959] usbcore: registered new interface driver bcm5974
[    0.200041] usbcore: registered new interface driver synaptics_usb
[    0.200118] usbcore: registered new interface driver iforce
[    0.200574] usbcore: registered new interface driver xpad
[    0.201319] i2c /dev entries driver
[    0.202297] usbcore: registered new interface driver bcm203x
[    0.202379] usbcore: registered new interface driver bpa10x
[    0.202445] usbcore: registered new interface driver bfusb
[    0.202518] usbcore: registered new interface driver btusb
[    0.202597] usbcore: registered new interface driver ath3k
[    0.203000] Synopsys Designware Multimedia Card Interface Driver
[    0.203451] dw_mmc ff704000.dwmmc0: IDMAC supports 32-bit address mode.
[    0.203501] dw_mmc ff704000.dwmmc0: Using internal DMA controller.
[    0.203513] dw_mmc ff704000.dwmmc0: Version ID is 240a
[    0.203577] dw_mmc ff704000.dwmmc0: DW MMC controller at irq 32,32 bit host data width,1024 deep fifo
[    0.203693] dw_mmc ff704000.dwmmc0: Linked as a consumer to regulator.1
[    0.203830] mmc_host mmc0: card is polling.
[    0.215892] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    0.228757] hidraw: raw HID events driver (C) Jiri Kosina
[    0.235671] usbcore: registered new interface driver usbhid
[    0.235678] usbhid: USB HID core driver
[    0.236053] fpga_manager fpga0: Altera SOCFPGA FPGA Manager registered
[    0.236677] altera_hps2fpga_bridge ff400000.fpga_bridge: fpga bridge [lwhps2fpga] registered
[    0.237032] altera_hps2fpga_bridge ff500000.fpga_bridge: fpga bridge [hps2fpga] registered
[    0.243387] MrAudio: CMA addr = 0x1E900000
[    0.256854] MrAudio Audio buffer '/dev/MrAudio' created.
               Class --> 'MrAudio_sys'
               Major --> 257949696
[    0.257148] usbcore: registered new interface driver snd-usb-audio
[    0.257447] oprofile: using arm/armv7-ca9
[    0.258260] NET: Registered protocol family 17
[    0.258283] NET: Registered protocol family 15
[    0.258292] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    0.258301] Bluetooth: HIDP socket layer initialized
[    0.258305] 8021q: 802.1Q VLAN Support v1.8
[    0.258326] lib80211: common routines for IEEE802.11 drivers
[    0.258331] lib80211_crypt: registered algorithm 'NULL'
[    0.258351] Key type dns_resolver registered
[    0.258635] ThumbEE CPU extension supported.
[    0.258646] Registering SWP/SWPB emulation handler
[    0.259727] Loading compiled-in X.509 certificates
[    0.260543] Key type encrypted registered
[    0.284074] rtc-m41t80 1-0068: Can't clear HT bit
[    0.292434] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    0.292496] mmc0: new high speed SDHC card at address 59b4
[    0.293397] mmcblk0: mmc0:59b4       7.36 GiB
[    0.303368]  mmcblk0: p1 p2
[    0.308148] rtc-ds1307: probe of 1-006f failed with error -5
[    0.308199] i2c-gpio i2c_gpio: using lines 2012 (SDA) and 2013 (SCL)
[    0.308303] hctosys: unable to open rtc device (rtc0)
[    0.308309] of_cfs_init
[    0.308384] of_cfs_init: OK
[    0.308603] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    0.312235] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    0.312302] ALSA device list:
[    0.312308]   #0: Dummy 1
[    0.312460] ttyS0 - failed to request DMA
[    0.313207] [EXFAT] trying to mount...
[    0.313468] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    0.313477] cfg80211: failed to load regulatory.db
[    0.345273] [EXFAT] mounted successfully
[    0.363790] EXT4-fs (loop8): mounted filesystem with ordered data mode. Opts: (null)
[    0.363836] VFS: Mounted root (ext4 filesystem) readonly on device 7:128.
[    0.376180] random: fast init done
[    0.376406] devtmpfs: mounted
[    0.379176] Freeing unused kernel memory: 1024K
[    0.379490] Run /sbin/init as init process
[    0.565932] usb 1-1: new high-speed USB device number 2 using dwc2
[    0.745220] usb 1-1: New USB device found, idVendor=1a40, idProduct=0201, bcdDevice= 1.00
[    0.745232] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    0.745240] usb 1-1: Product: USB 2.0 Hub [MTT]
[    0.745806] hub 1-1:1.0: USB hub found
[    0.745937] hub 1-1:1.0: 7 ports detected
[    1.029073] usb 1-1.2: new full-speed USB device number 3 using dwc2
[    1.140932] usb 1-1.2: New USB device found, idVendor=045e, idProduct=0719, bcdDevice= 1.00
[    1.140945] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.140952] usb 1-1.2: Product: Xbox 360 Wireless Receiver for Windows
[    1.140958] usb 1-1.2: Manufacturer: ©Microsoft
[    1.140964] usb 1-1.2: SerialNumber: FF6BFF20
[    1.224289] usb 1-1.4: new full-speed USB device number 4 using dwc2
[    1.317658] usb 1-1.4: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.01
[    1.317671] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.317678] usb 1-1.4: Product: USB Receiver
[    1.317684] usb 1-1.4: Manufacturer: Logitech
[    1.325537] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-ffb40000.usb-1.4/input2
[    1.446127] input: Logitech K400 as /devices/platform/soc/ffb40000.usb/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input0
[    1.447312] logitech-hidpp-device 0003:046D:4024.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K400] on usb-ffb40000.usb-1.4:1
[    1.506884] usb 1-1.6: new high-speed USB device number 5 using dwc2
[    1.598965] usb 1-1.6: New USB device found, idVendor=7392, idProduct=7811, bcdDevice= 2.00
[    1.598975] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.598982] usb 1-1.6: SerialNumber: 00e04c000001
[    1.599821] rtl8192cu: Chip version 0x10
[    1.605110] udevd[1221]: starting version 3.2.1
[    1.636783] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[    1.654768] random: udevd: uninitialized urandom read (16 bytes read)
[    1.658351] random: udevd: uninitialized urandom read (16 bytes read)
[    1.658720] random: udevd: uninitialized urandom read (16 bytes read)
[    1.709377] input: MiSTer virtual input as /devices/virtual/input/input1
[    1.720249] udevd[1225]: starting eudev-3.2.1
[    1.754978] rtl8192cu: Board Type 0
[    1.755214] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[    1.755296] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[    1.755657] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[    1.782719] random: crng init done
[    1.782731] random: 1 urandom warning(s) missed due to ratelimiting
[    1.833910] usb 1-1.7: new full-speed USB device number 6 using dwc2
[    1.928742] usb 1-1.7: New USB device found, idVendor=16c0, idProduct=05e1, bcdDevice= 4.00
[    1.928756] usb 1-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.928763] usb 1-1.7: Product: Xinmotek Controller
[    1.928769] usb 1-1.7: Manufacturer: xin-mo.com
[    1.933619] input: xin-mo.com Xinmotek Controller as /devices/platform/soc/ffb40000.usb/usb1/1-1/1-1.7/1-1.7:1.0/0003:16C0:05E1.0005/input/input2
[    1.935178] xinmo 0003:16C0:05E1.0005: input,hidraw2: USB HID v1.10 Gamepad [xin-mo.com Xinmotek Controller] on usb-ffb40000.usb-1.7/input0
[    2.736240] EXT4-fs (loop0): recovery complete
[    2.736268] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[    3.361128] Micrel KSZ9031 Gigabit PHY stmmac-0:01: attached PHY driver [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
[    3.374018] socfpga-dwmac ff702000.ethernet eth0: No Safety Features support found
[    3.374474] socfpga-dwmac ff702000.ethernet eth0: registered PTP clock
[    3.832078] rtl8192cu: MAC auto ON okay!
[    3.867658] rtl8192cu: Tx queue select: 0x05
[    6.002438] wlan0: authenticate with b0:6e:bf:3b:f1:90
[    6.030888] wlan0: send auth to b0:6e:bf:3b:f1:90 (try 1/3)
[    6.039794] wlan0: authenticated
[    6.040919] wlan0: associate with b0:6e:bf:3b:f1:90 (try 1/3)
[    6.057971] wlan0: RX AssocResp from b0:6e:bf:3b:f1:90 (capab=0x1411 status=0 aid=3)
[    6.149738] wlan0: associated
[  243.244929] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  244.854970] Unable to determine destination address.
[  333.084464] EXT4-fs (loop8): re-mounted. Opts: (null)
[  390.134379] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  392.614306] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  395.044554] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  397.676341] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  600.336326] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  602.744371] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  604.573986] Unable to determine destination address.
[  676.253674] logitech-hidpp-device 0003:046D:4024.0004: HID++ 2.0 device connected.
[  677.596422] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  679.427316] Unable to determine destination address.
[  798.516440] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  830.112399] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  830.932790] Unable to determine destination address.
[  897.312538] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  903.424374] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  904.241575] Unable to determine destination address.
[  953.450412] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  958.408356] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  969.988330] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  976.914375] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[  977.737617] Unable to determine destination address.
[  982.380329] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[ 1063.866428] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[ 1064.684547] Unable to determine destination address.
[ 1080.632440] MiSTer_fb 22000000.MiSTer_fb: width = 640, height = 360, format=8888
[ 1082.450979] Unable to determine destination address.


I've also tried a number of combinations of my NAS addresses (as IP or 'name" and cifs versions (2/3)
I made a new top level folder (mister) and gave a new user (mister) full r/w permissions

heres the current .ini for the mount_cifs script

Code: Select all

#=========   USER OPTIONS   =========
#You can edit these user options or make an ini file with the same
#name as the script, i.e. mount_cifs.ini, containing the same options.

#Your CIFS Server, i.e. your NAS name or its IP address.
SERVER="\\192.168.0.101\mister"

#The share name on the Server.
SHARE="mister"

#The user name, leave blank for guest access.
USERNAME="mister"

#The user password, irrelevant (leave blank) for guest access.
PASSWORD="Mister!"

#Optional user domain, when in doubt leave blank.
DOMAIN=""

#Local directory/directories where the share will be mounted.
#- It can ba a single directory, i.e. "_CIFS", so the remote share, i.e. \\NAS\MiSTer
#  will be directly mounted on /media/fat/_CIFS (/media/fat is the root of the SD card).
#- It can be a pipe "|" separated list of directories, i.e. "Amiga|C64|NES|SNES",
#  so the share subdirectiories with those names,
#  i.e. \\NAS\MiSTer\Amiga, \\NAS\MiSTer\C64, \\NAS\MiSTer\NES and \\NAS\MiSTer\SNES
#  will be mounted on local /media/fat/Amiga, /media/fat/C64, /media/fat/NES and /media/fat/SNES.
#- It can be an asterisk "*": when SINGLE_CIFS_CONNECTION="true",
#  all the directories in the remote share will be listed and mounted locally,
#  except the special ones (i.e. linux and config);
#  when SINGLE_CIFS_CONNECTION="false" all the directories in the SD root,
#  except the special ones (i.e. linux and config), will be mounted when one
#  with a matching name is found on the remote share.
LOCAL_DIR="_ArcadeRoms"

#Optional additional mount options, when in doubt leave blank.
#If you have problems not related to username/password, you can try "vers=2.0" or "vers=3.0".
ADDITIONAL_MOUNT_OPTIONS="vers=2.0"

#"true" in order to wait for the CIFS server to be reachable;
#useful when using this script at boot time.
WAIT_FOR_SERVER="false"

#"true" for automounting CIFS shares at boot time;
#it will create start/kill scripts in /etc/network/if-up.d and /etc/network/if-down.d.
MOUNT_AT_BOOT="false"



#========= ADVANCED OPTIONS =========
BASE_PATH="/media/fat"
#MISTER_CIFS_URL="https://github.com/MiSTer-devel/CIFS_MiSTer"
KERNEL_MODULES="md4.ko|md5.ko|des_generic.ko|fscache.ko|cifs.ko"
IFS="|"
SINGLE_CIFS_CONNECTION="true"
#Pipe "|" separated list of directories which will never be mounted when LOCAL_DIR="*"
SPECIAL_DIRECTORIES="config|linux|System Volume Information"





for the server name i tried it as
\\192.168.0.101
\\myNAS
\\MYNAS
i also tried those with these folders added after
\mister
\volume1
\volume1\mister

I tried all of those and each time i made sure to run the unmount script just in case. and a unhealthy number of warm resets along the way ..

i think its safe to say the networking gods hate me :D
maybe somone with a synology NAS will see this know the mistake I'm making ??? or i'll post over on a synology forum and see what pops up

thanks for your help anyway :) today i've tidied up a number of folders in my mister and added a wifi dongle (after trying the above ;) )

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Sun Oct 20, 2019 7:05 am

mutmuthux wrote:I tried all of those and each time i made sure to run the unmount script just in case. and a unhealthy number of warm resets along the way ..

i think its safe to say the networking gods hate me :D
maybe somone with a synology NAS will see this know the mistake I'm making ??? or i'll post over on a synology forum and see what pops up

thanks for your help anyway :) today i've tidied up a number of folders in my mister and added a wifi dongle (after trying the above ;) )


Hi.
First of all you must launch dmesg command just after a failed mount (after launching the script) for having useful logs.
Second, the SERVER parameter in the ini, as explained in the heading comment, must be the cifs server name or IP address, so no backslashes or subdirectories there.

Regards.

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Sun Oct 20, 2019 10:11 am

Scripting news:
===========================
Updater_script_MiSTer: 2019-10-20
- mister_updater.sh - Version 3.3.4 - 2019-10-20 - Fixed an incompatibility with gamehacking.org anti DDOS system.
===========================
https://github.com/MiSTer-devel/Updater_script_MiSTer

Regards.

Locutus73

mutmuthux
Atariator
Atariator
Posts: 22
Joined: Mon Mar 04, 2019 8:11 am

Re: Scripting news

Postby mutmuthux » Sun Oct 20, 2019 10:49 am

Locutus73 wrote: .. no backslashes ..


I cant believe it was this alone that caused me the problems :/
Sorry for all the troubles
Thanks for your help, it's much appreciated Locutus73

Any synology users that find this in the future, take note :D

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Tue Oct 22, 2019 9:54 am

mutmuthux wrote:Thanks for your help, it's much appreciated Locutus73

You're welcome.
By the way, if you set MOUNT_AT_BOOT="true" and WAIT_FOR_SERVER="true", after you launch the script once, it will set the Linux environment to automatically launch the script at each boot. This setup will be lost when you upgrade the Linux image and it will require the script to be manually launched once.

Regards.

mutmuthux
Atariator
Atariator
Posts: 22
Joined: Mon Mar 04, 2019 8:11 am

Re: Scripting news

Postby mutmuthux » Wed Oct 23, 2019 11:01 am

Locutus73 wrote:
mutmuthux wrote:Thanks for your help, it's much appreciated Locutus73

You're welcome.
By the way, if you set MOUNT_AT_BOOT="true" and WAIT_FOR_SERVER="true", after you launch the script once, it will set the Linux environment to automatically launch the script at each boot. This setup will be lost when you upgrade the Linux image and it will require the script to be manually launched once.

Regards.


thanks for the tips :)
MiSTer keeps getting better thanks to the work of peeps like your self.
if i had a hat i'd doff it :)

Locutus73
Captain Atari
Captain Atari
Posts: 493
Joined: Wed Feb 07, 2018 6:13 pm

Re: Scripting news

Postby Locutus73 » Thu Oct 24, 2019 11:27 am

Scripting news:
===========================
Scripts_MiSTer: 2019-10-24
- other_authors/wifi.sh - Script adapted from RetroPie for use with MiSTer FPGA project by MiSterAddons.
===========================
https://github.com/MiSTer-devel/Scripts_MiSTer

Regards.

Locutus73


Return to “MiSTer”

Who is online

Users browsing this forum: No registered users and 8 guests