File names in Russian

[Vladimir]

Hi gurus,
I found out that files named in Russian are not displayed anywhere under Solaris Express (in file managers, in open dialogs of different applications like Star Office, etc.). So I have no access to them. Does anybody know how to tweak the system to "see" such files? I also tried to save a Star Writer document with a name in Russian and got an odd error "The ... file doesn't exist".
I tried selecting Russian as the default language in the login window, but this only changed the items of menus to Russian counterparts and didn't enable the system to gt access to problematic files.
Thank you in advance for any help.


This message posted from opensolaris.org

[Lars Tunkrans]

Hi,

I must admit that I never tried to run cyrillic myself.

There is a manual for international Locale support

http://docs.sun.com/app/docs/doc/817-2521

and UTF-8 supports Cyrrilic.

http://docs.sun.com/app/docs/doc/817-2521/utf8-21349?a=view


basically you need to set up /etc/default/init

with the locale parameters you need and reeboot the system
The locale libraries needs to be present in /usr/lib/locale
The locales present are dependent on which languages YOU SELECT
when you install solaris .


you should select

ru_RU.UTF-8

according to :
http://docs.sun.com/app/docs/doc/817-2521/overview-13667?a=view

This is about what I do with Swedish

/etc/default/init

TZ=Europe/Stockholm
CMASK=022
LC_COLLATE=sv_SE.ISO8859-1
LC_CTYPE=sv_SE.ISO8859-1
LC_MESSAGES=C
LC_MONETARY=sv_SE.ISO8859-1
LC_NUMERIC=sv_SE.ISO8859-1
LC_TIME=en_US.ISO8859-1


/usr/lib/locale/

$ ls -ld sv_SE*
drwxr-xr-x 3 root bin 512 Sep 14 22:06 sv_SE
drwxr-xr-x 7 root bin 512 Sep 14 22:06 sv_SE.ISO8859-1
drwxr-xr-x 7 root bin 512 Sep 14 21:59 sv_SE.ISO8859-15
drwxr-xr-x 3 root bin 512 Sep 14 21:59 sv_SE.ISO8859-***@euro
drwxr-xr-x 8 root bin 512 Sep 14 21:59 sv_SE.UTF-8
drwxr-xr-x 3 root bin 512 Sep 14 21:59 sv_SE.UTF-***@euro


You need to do the same for the Russian Locale

//Lars


This message posted from opensolaris.org

[Vladimir]

Hi Lars,
Well, I selected ru_RU.ANSI1251 during installation. It looks like the libraries for ru_RU.UTF-8 were installed too as I found them in the /usr/lib/locale/ folder. I'm able to select Russian Unicode language in the login window and get localized interface, I also tried to manually edit the /etc/default/init file (change values ru_RU.ANSI1251 to ru_RU.UTF-8), rebooted, but still don't see files and folders named in Russian. I would try to re-install Solaris with the Russian Unicode locale, but I'm doubting that this would give me the desired result.
On one of the pages of the International Language Environments Guide I have read that the Solaris Express installation includes only partial locales and for better support of internatiolization one needs to install full locale from the Language CD. Maybe, I need to get this CD and try installing full Cyrillic locale ...


This message posted from opensolaris.org

[Lars Tunkrans]

Hmm,

I think you need to question where the " russian " files came from ?
( as you obvioulsy did not create them on solaris )
If I make a file on a Windows PC with a Swedish name such as

" räksmörgås " I have three Non-ascii characters in it. depending on the character set
used on the PC these three characters will have interesting binary values.

A PC could use codepage 437 or codepage 850 or ISO8859-1 or combination thereof on
different peripherals and so on.

When a PC filesystem is viewed from unix ( maybe by using some form of SAMBA )
the binary value of the PC filename is usually not changed but just represented in
whatever characterset is used on the UNIX box .

So I would not be suprised if a file with a cyrillic filename in Windows is unrecognizable
when its transfered to UNIX and the binary value of the filename is represented in
a different characterset ( like UTF-8 )

Historically even in Swedish , where only 5 characters are added to US_ASCII ,
the people how designed all these stuff could not manage to place the same
additional character at the same binary value in the differernt character sets.

I cant even begin to comprehend how bad it must be in cyrrilic


Anyway Solaris will probably never be able to guess what graphical representation
was used for a string of bytes on a machine form another Arcithecture.

//Lars


This message posted from opensolaris.org

[Vladimir]

Of course, the Russian names were given under Windows - where else? ;-)
However, I don't believe that Sun just gave up to support localized file names - it is unlikely that I'm the only person who needs it :-) Moreover, it includes 6 (!) different Russian encodings and there are quite a few parts in the documentation where they explain how to set up support for Cyrillic input, etc. I do not see complaints about the lack of support for Russian file names on the Web either. So I tend to think that there is something wrong with my system. By now I only used my Flash card to exchange files between different OSes. Today I inserted a CD and found out that the problem doesn't concern this carrier: I was able to see Russian files burned to the CD, copy them to a solaris partition and open with text editors. I verified that I can save a file with a Russian name using S
tar Writer. However, I'm unable to copy this file to my Flash card - I get the "Wrong parameters" error. So the problems seems to be related to USB Flash drivers only. I'm stuck at this poin
t.


This message posted from opensolaris.org

[W. Wayne Liauh]

I am attaching a screenshot showing a file with a Russian-charactered filename is correctly saved in StarOffice8/SXCE76 without any problem. I was able to copy this file to a USB stick, also no problemo. The Russian filename was correctly displayed in both StarOffice and Nautilus. This system does not have Russian locale installed, which, as you are aware, will be necessary only if you need a localized environment.

If, however, this file were created in Windows, then, as you and Lars pointed out, there may be a different story. The world is getting flat, and we are in a desperate need for a "truly international" OS like Solaris to become dominant.


This message posted from opensolaris.org

[Vladimir]

Hmm, in fact I don't really need the environment to be localized in Russian. I feel myself pretty comfortable with English items in the menu. I only need to be able to switch input language from English to Russian in text editors and of course, I want ot see all files on my drives :-)
It is really odd that you can copy a Russian file to a USB drive while I cannot. Which version of Solaris do you have? Which locale did you select when installing the OS?


This message posted from opensolaris.org

[Lars Tunkrans]

However, I'm unable to copy this file to my Flash card - I get the "Wrong parameters" error. So >the problems seems to be related to USB Flash drivers only. I'm stuck at this point.

Nice Catch,

I cant copy my file "räksmörgås" to my sandisk reader either. looks like flashmedia
only accepts US_ASCII , I get the same error

Error "Invalid parameters" while copying "/export/ho...räksmörgås".


Artem are you reading this ?

full thread is in the opensolaris_help forum.

You will need to set up an execrise to copy files with Non-US_Ascii filenames back and
forth from USB/FLASH media and make it handle file with names that have
characters with hex values larger than 0x80


//Lars


This message posted from opensolaris.org

[Vladimir]

You calmed me a bit :)
If I am correctly guessing from waynel's posts, he is using build 76 of SXCE and does not reproduce the problem. Whihch build of Solaris is running on your PC?


This message posted from opensolaris.org

[W. Wayne Liauh]

Post by Vladimir
You calmed me a bit :)
If I am correctly guessing from waynel's posts, he is
using build 76 of SXCE and does not reproduce the
problem. Whihch build of Solaris is running on your
PC?

Your guess is correct. :-) But I don't think it would make any difference what version of Solaris your are running. SXCE 72 is a very rare (& "unique") aberration. The problem(s) experienced there never happened before and should never happen again.

I am running the en_US.UTF-8 locale. I have logged into the C/POSIX locale, but also did not experience any problem. I was able to copy a Russian file into and out of a number of USB sticks; the results are the same.

Perhaps your USB stick is formatted in the 8-bit FAT? That could pose a problem. All my USB sticks are in FAT16.


This message posted from opensolaris.org

[Vladimir]

Thank you for the response. Now I see that most of the problems I'm experiencing would not exist if I used the latest build :-( Please excuse me for bothering you with extra questions.


This message posted from opensolaris.org

[Lars Tunkrans]

Post by Vladimir
You calmed me a bit :)
If I am correctly guessing from waynel's posts, he is using build 76 of SXCE and does not >reproduce the problem. Whihch build of Solaris is running on your PC?

Im not sure , I can reproduce the problem on both B72 and B76 .
This is an old problem thats been reported over the last 3 years.

http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=4089052

It was supposed to have been fixed in B71.

http://dlc.sun.com/osol/on/downloads/b71/on-changelog-b71.html

Issues Resolved:
PSARC case 2005/428 : PCFS support of non-ASCII filenames
BUG/RFE:4089052RFE: pcfs needs to support non ASCII character filename.
Files Changed:
update:usr/src/uts/common/fs/pcfs/pc_dir.c
update:usr/src/uts/common/fs/pcfs/pc_subr.c
update:usr/src/uts/common/fs/pcfs/pc_vnops.c
update:usr/src/uts/common/sys/fs/pc_dir.h


Maybe its fixed for floppies but not for USB
I dont have a floppy unit anymore so I cant test it.

CD's and DVD's use another filesystem, High Sierra, or HSFS

//Lars


This message posted from opensolaris.org

[Lars Tunkrans]

O.K.

Last entry in this thread I Hope.

After I switched my Build 76 machine to use UTF8 instead of iso8859-1
I can read and write filenames with NON_US_Ascii characters to/from an USB stick.
And I can read the filenames correctly with Nautilus.

so I guess the the ability to read/write PCFS filenames is dependent on ctype(3c)

LC_CTYPE=sv_SE.ISO8859-1 does not work
LC_CTYPE=sv_SE.UTF-8 does work correctly.


However I am not sure that I find this dependency desirable
If its left this way many poor users are going to be frustrated as they
dont understand the difference between an 8 bit and a multibyte character set.

//Lars


This message posted from opensolaris.org

[Vladimir]

Thank you, Lars, for the investigation. I should have searched the bug database myself before posting the problem here - this would save yours and my time :-(
I'm running build 57, that is why even switching to UTF-8 locale doesn't help, I believe. Well, this is the second reason to get the latest build, so I have just registered a request for a DVD on Sun's Web site.
Now there is only one problem that still persists and it is very important for me to solve it - I'm talking about my network card. I posted the problem description to an existing thread (http://www.opensolaris.org/jive/thread.jspa?threadID=45138&tstart=0), but nobody replied to me for two days. Maybe, I should start a new thread, what do you think?
I checked the bug database and found this entry
http://bugs.opensolaris.org/view_bug.do?bug_id=6431573
It confirms that my network card is definitely supported by the build I have, so I have no idea what prevents it from establishing a connection to my router.
I appreciate your ongoing assistance in setting up Solaris on my machine and really sorry that I flood the forum with another problem every day.


This message posted from opensolaris.org

[Lars Tunkrans]

Yes you network NIC is supported
Here is a fragment of /etc/driver_aliases from B72.


qlc "pci1077,2422"
qlc "pciex1077,2432"
qlc "pciex1077,5432"
ral "pci1814,201"
rge "pci10ec,8169"
rge "pci10ec,8168"
rge "pci10ec,8167"
rge "pci16ec,0116"
rtls "pci10ec,8139"
rtls "pci1186,1301"
rtls "pci1113,1211"
rtw "pci10ec,8180"


Maybe you just need to make sure that the PC is powered off completely
( pull the power cord out of the machine for 60 seconds.) when switching from windows
to Solaris.

I have had two PC's where the NIC's are not properly reset by a windows
shutdown .


//Lars


This message posted from opensolaris.org

[Vladimir]

Unfortunately, your advice didn't help. I also tried to install the system again: the installer went to the stage where it is "attempting to configure interface rge0 using RPC bootparams", spent some time and informed me that it "skipped interface rge0". And every time my installed system boots, it writes "Failed to configure IPv4 protocol" or something like that. In the Network properties I see that interface rge0 is active, but I'm not sure what does this mean: whether there is a suitable driver for it or that it is ready to work with my network card. Right now I would like to figure out what exactly is wrong: the driver was not installed or it recognized my network card and attached to it but is unable to communicate with my router. Do you know how I could check this? Thanks.


This message posted from opensolaris.org

[Lars Tunkrans]

Hi,

"attempting to configure interface rge0 using RPC bootparams"
"skipped interface rge0"

These lines actually means that it tried to find a Solaris JUMPSTART server and Falied.
This happends everywhere without a jumpstart server.

"Failed to configure IPv4 protocol"

This should not happend.

You need another server/pc to send some data to the problematic machine.

While trying to telnet or FTP or something to the prblem machine you could :

1) run netstat -i

and see if the receive/transmit counters increase.

2) run snoop -d rge0

an try to see some traffic passing by.


If the software cant properly attach to the rge0 I/F you might have
some hardware in conflict inside the machine.
reccomend that you verify that IRQ interupt vectors and DMA Channels
is not in conflict between different pieces of hardware in the machine.

//Lars


This message posted from opensolaris.org

[Vladimir]

Thanks, Lars. I'll see if I can perform the tests. In the meantime, let me ask you an additional question: if my network card works properly under Windows, how can it be that there is a hardware conflict under Solaris?


This message posted from opensolaris.org

[Lars Tunkrans]

Unix does not appreciate the same IRQ shared between several pieces of hardware
Windows is more foregiveing of this error.

//Lars


This message posted from opensolaris.org

[Vladimir]

Apparently, your assumption is correct. I turned off the power for a while, and started installing the system from scratch (deleted the existing Solaris partition). There were no errors when configuring network during installation. When I booted the installed system and logged in to the command line (as you remember, my video card is not supported by the build I have, so I need to install the driver for it first), I tried to ping my router (192.168.1.1) and it replied (!). Both my router's address and my computer network address (192.168.1.2) could be successfully pinged. Then I installed the NVIDIA driver for my video card and installed the Open Sound driver collection to enable my sound card. Rebooted - and got the same "Failed to configure IPv4 interface(s)" error message in console. So
, if I correctly understand the situation, either my video card or my sound card somehow conflicts with my network card. Maybe, this happens because the installer doesn't includ a driver for
my video card and thus installs the network driver on "its place". I'm too far from the hardware level, so cannot speak more correctly about these things. Do you think that this is the case? If there is indeed a conflict between either video card or sound card and the network card, can I resolve it by manually editing their drivers configuration or executing some commands that will change their IRQs?


This message posted from opensolaris.org

[Lars Tunkrans]

Assuming that the video card is either AGP or PCI express, I would suspect the sound card to be the culprit.
Can you change the IRQ used by the soundcard in the PC BIOS ?

Or if its an ON-Mother-BOARD sound chip disable it and install a PCI based sound card ?
( and put the PCI soundcard in a PCI slot where you can Assign the IRQ. )


This message posted from opensolaris.org

[Vladimir]

Well, I checked IRQs under Windows and it appeared that my video card and network card share the same IRQ (16). Sound card is integrated into the motherboard, so I cannot change its IRQ, but it has nothing to do with the conflict anyway as it uses IRQ 23. Under Solaris the hardware components get different IRQs. However, the video card and network card still share the same IRQ (11). My video card is plugged into the PCI Express 16 bit slot and the network card is integrated into the motherboard. I suspect that the network card is internally connected to a PCI Express bus as its model is Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC - I guess "PCI-E'" means the PCI Express bus. My BIOS allows me to only set IRQs for PCI slots, so I'm unable to explicitly change the IRQ for my video card.
I tried disabling COM port, LPT port and my Floopy drive to release some IRQs, but my video card and network card still share the same IRQ, now it is IRQ 10. Maybe, my motherboard is designe
d so that all PCI Express buses share the same IRQ, I don't know. However, I do not see a way to separate IRQs for the conflicting devices under Solaris, so I'm frustrated a bit. It seems that I won't be able to work under this OS in the near future :-(


This message posted from opensolaris.org

[Lars Tunkrans]

I'm sorry to hear that you motherbord is unsuitable.
Maybe you should contact the manufacturer and tell them that you need
IRQ separation between the devices on the motherboard .

Can you tell us what motherboard it is ?
So we can note it in the little black book of kit to avoid.

//Lars


This message posted from opensolaris.org

[Vladimir]

I don't think that the manufacturer would modify my motherboard or replace it with another one to allow me to run Solaris <g>. I will try installing the latest Debian to see if this motherboard is not compatible with all non-Windows systems.
The motherboard model is Gigabyte P35-DS3.
The only thng that is not clear enough to me is that the conflict happens only after I install the NVIDIA driver for my video card. Does this mean that when the driver is not installed and I'm working in onsole mode, the display controller doesn't use IRQ at all? Why the network and display controllers start to conflict only after I install the driver for the latter?


This message posted from opensolaris.org

[Lars Tunkrans]

I read a few pages in the motherboard manual. Looks like you can buy a PCI LAN Card and install in a PCI slot and configure an interupt vector of you choise . And disable the ON board NIC.

//Lars


This message posted from opensolaris.org

[Vladimir]

Yeah, I have read it too. There are 3 PCI slots and I can assign IRQs to them.
However, I'm going to puzzle you. I was not completely sure that I correctly concluded that the problem is related to my video card. I seen that it uses IRQ 10 in the NVIDIA control panel. When the system boots, it shows the table with IRQs of different controllers and Display and Network controllers are linked to IRQ 10 also. Yet I could not understand why under Windows these devices share IRQ16. I assumed that under Solaris I see hexadecimal IRQ number, and hex 10 corresponds to dec 16. I found your advice to execute dmesg command in the thread started by majorero and did it. To my surprise, the output informed me that several drivers share IRQ16 (!) with different interrupt levels. I recalled that you suspected that the sound card can be the culprit. Hence I dared to perform one more cl
ear experiment. I installed Solaris Express from scratch and boot in console mode. There were no error about configuring IPv4 interface, but my router didn't reply to a ping. I turned off th
e computer and switched the power for a while (to reset any info cached in the network card). When I booted Solaris, I could ping the router - so you were right that simple rebooting from Windows to Solaris doesn't allow to work with LAN. The next step was installing the NVIDIA driver for the video card. I rebooted the system and loaded GNOME: I was able to surf the Web with Firefox! Cool, and I started to think that it is the sound card what kills my network card. I went further to confirm this and installed the Open Sound package and rebooted. Well, I still can access the Internet, display is working and I can play music ... Now I'm totally lost. I read that majorero gets inconsistent behavior of his network card and sound card, so I expect that some of the components can suddenly stop
working on my machine too. I already got an error from an audio player about a problem in the data flow stream and the quality of the sound is very poor. So I guess that I would rather purch
ase a PCI sound card in order to reveal a part of IRQ16 and get good sound. I would accept this as a norm if Windows would not handle this situation better. I hope that Solaris will be improved in this regard as I like it more than Windows and will try to work under Solaris anyway.
Thank you very much, Lars. I would leave the Solaris community without your timely support. I really appreciate your help.


This message posted from opensolaris.org

[Lars Tunkrans]

All right , thank you for you kind words.

The file that holds Solaris view of the systems hardware devices is

/etc/path_to_inst

Probably depending on the order in which you install drivers and reconfigure the system
either with a reboot or online with devfsadm(1m) you might get different results written
to this file. if you do the reinstall exersice again , verify if the contents of /etc/path_to_inst
is identical or not.

( PS. you are not supposed to edit this file manually . if you do expect Trial, Tribulations and Horror )

//Lars


This message posted from opensolaris.org

[Shawn Walker]

Post by Lars Tunkrans
I'm sorry to hear that you motherbord is unsuitable.
Maybe you should contact the manufacturer and tell them that you need
IRQ separation between the devices on the motherboard .
Can you tell us what motherboard it is ?
So we can note it in the little black book of kit to avoid.

The point is, these "unsuitable" systems often work with GNU/Linux,
BSD or Windows. Therefore, in my mind, there is no good reason why
they can't work for Solaris/OpenSolaris.

[W. Wayne Liauh]

If you did not have the right locale installed, you should search the i18n forum to see how to do that.

There is another possibility. I have experienced the same problem with SXCE 72 (and only with SXCE 72), even though the proper locales were installed. If this is the case, then either install SXDE or upgrade to SXCE 76.


This message posted from opensolaris.org