580 replies to this topic

[fpignon]

That may work, depending on what the other side is, and how the files got stored on "that other side".

 

In this case it is probably because CIFS assumes Windows at the other side (so it uses cp437 instead of utf8 ), but you use a Linux server running Samba (in this case from Synology) which probably defaults to utf8, being linux.

Indeed, Synology uses UTF8  by default (My file name is garbled. What can I do? - Synology Kunskapscenter). As explained in the article (The Purpose of iocharset=utf8 in Mounting Windows SMB Shares to Linux | DeviceTests), it seems Linux uses the iso8859-1 character encoding for mounts. Note also that I'm not using mount manager (maybe mount manager adds iocharset=utf8 ?). But if other folks are facing similar issue, this is the way to go.

[Beeker]

I was back on 8.3 since last weekend and lcd4linux worked like a charm. now i did a flash to nightly, after that online update, after that i did your telnet commands and looked for the file you mentioned.

 

Second screen is black. logile says, only internal lcd is working, i didn´t see anything about my external display. No error message or anything like that...

Try this config file.
Rename it to: lcd4config and upload it to

/etc/enigma2/

LCD4linux OpenPLi 8.3 comes with this file.
LCD4linux OpenPLi 9.0 has no default lcd4config file.

Some users using the old 8.3 lcd4config file with OpenPLi 9.0 to fix the display, I recall.


 

 

Attached Files

•  lcd4config.txt   2.19KB   12 downloads

Edited by Beeker, 29 November 2023 - 08:20.

[WanWizard]

it seems Linux uses the iso8859-1 character encoding for mounts. Note also that I'm not using mount manager (maybe mount manager adds iocharset=utf8 ?). But if other folks are facing similar issue, this is the way to go.

 

In Windows speak they are codepages, and cp437 is the standard codepage used by Windows.

 

They key here is not as such which codepage you use, but how consistent you are, as it is only a solution if ALL connections to the share, and the host itself if that creates files, use the same characterset.

 

And in this lies the problem: Windows (PC or Server) is a platform that can create files, and Windows to Windows connections always use their native characterset, and you can't change that when opening a share.

 

Samba, as a CIFS server, is able to convert, which is a feature that Synology uses in their NAS.

So if you create a file called "âêîôû.txt" in Windows, copy that (in Windows) to a share on a Synology, then look at that share on the NAS, it is still "âêîôû.txt", so correctly converted to utf-8. If you name an NFS mount from a linux machine (like your box) to that share, you will also see "âêîôû.txt". But if you make a CIFS mount from a linux machine, and you don't specifiy the other side uses utf-8, the connection defaults to a Windows characterset, and you will see "�����.txt".

 

In other words, if you connect to a Windows machine from linux, use CIFS. If you connect to a Linux machine, use NFS. Or know what you're doing and add iocharset to the mount options.
 

[Yobnned]

Has anybody flashed a Sab Triple Tuner with OpenPli 9?

Will it cause any problems?

[rauldelavega]

if [ $ROOTNAME != "rootfs.tar.bz2" -o $SEARCH = "h9" -o $SEARCH = "i55plus" -o $SEARCH = "i55se" -o $SEARCH = "hzero" -o $SEARCH = "h8" -o $SEARCH = "h8.2h" -o $SEARCH = "h9.s" -o $SEARCH = "h9.t" -o $SEARCH = "h9.2h" -o $SEARCH = "h9.2s" ] ; then
	log "Kernel resides on $MTDPLACE" 					# Just for testing purposes
	$NANDDUMP /dev/$MTDPLACE -qf "$WORKDIR/$KERNELNAME"
	if [ -f "$WORKDIR/$KERNELNAME" ] ; then
		echo -n "Kernel dumped  :"  >> $LOGFILE
		ls $LS1 "$WORKDIR/$KERNELNAME" | sed 's/-r.*   1//' >> $LOGFILE
	else
		log "$WORKDIR/$KERNELNAME NOT FOUND"
		big_fail
	fi
	log "--------------------------"
else

stop this

$NANDDUMP /dev/$MTDPLACE -qf "$WORKDIR/$KERNELNAME"

maybe

$NANDDUMP /dev/$MTDPLACE -q > "$WORKDIR/$KERNELNAME"

hi, I did the following test, I inserted the version of nanddump (2.0.0) present in openpli 8.3, and I inserted it in openpli 9 (2.1.2) and it works

[Dimitrij]

 

hi, I did the following test, I inserted the version of nanddump (2.0.0) present in openpli 8.3, and I inserted it in openpli 9 (2.1.2) and it works

 

Need test in telnet version nanddump (2.0.0)/nanddump (2.1.2):

chmod 755 /tmp/nanddump

 

/tmp/nanddump /dev/mtd0 -qf /hdd/kernel.bin

 

[Dimitrij]

mtd-utils rollback to 2.0.0 mtd-utils-2.0.2 in ATV 6.4 has an issue o…

[rauldelavega]

I confirm that the nanddump 2.0.0 version works (osmega, os nino +) , with telnet and  openpli 9

[WanWizard]

Has anybody flashed a Sab Triple Tuner with OpenPli 9?

Will it cause any problems?

 

Not recently, but I wouldn't know why it would cause problems.

[Frenske]

I must check whether I still have one. If so I could test the 9.0 image.

But what’s the reason that others must test so you could lay back in your chair? You can also test it. It won’t break your hardware. If it doesn’t work you can simply go back to your present image with a proper backup.

[massydeep]

hi

 

Thank you my friend for replying to me. Can you please tell me what I should do to resolve it this problem with backupsuite? I'm using release 9.0 version of openpli but it doesn't work with my zgemma h5.2.plus.. release 8.3 works very well. if you can please find me a solution. thanks a lot to everyone

[raffadb]

Octagon sfx6018 / 6008 FTP problem I changed the password via telnet, but FTP does not work

 

passwd root

[massydeep]

 

Octagon sfx6018 / 6008 FTP problem I changed the password via telnet, but FTP does not work

 

passwd root

 

hi bro use dcc editor

it work ok

[kalehrl]

When I go to Main menu - Setup - System - Expert settings - Select a network adapter - Network configuration then press EXIT or RED button on the remote, I always get a green screen and enigma2 crashes:
 enigma2_crash.log   12.33KB   5 downloads

[WanWizard]

Does your box have a wireless network interface?

[Dimitrij]

https://github.com/O...rkSetup.py#L499

This need check,e.g.

	def cleanup(self):
		iNetwork.stopLinkStateConsole()
 +               try:
		    config.plugins.wlan.encryption.removeNotifier(self.createSetup)
 +               except:
                    pass
		self.activateInterfaceEntry.removeNotifier(self.createSetup)
		self.dhcpConfigEntry.removeNotifier(self.createSetup)
		self.hasGatewayConfigEntry.removeNotifier(self.createSetup)

 

[WanWizard]

Yes, I already informed Taapat who made this change. Fixing it like this is a bit crude though...

[Dimitrij]

Yes, I already informed Taapat who made this change. Fixing it like this is a bit crude though...

or

if iNetwork.isWirelessInterface(self.iface):
    config.plugins.wlan.encryption.removeNotifier(self.createSetup)

 

[WanWizard]

A lot cleaner .

[kalehrl]

Does your box have a wireless network interface?

It doesn't. I also don't use any wireless dongles.

I think I uninstalled wireless or wpa_supplicant or something like that to free some place on the box.