Peter Suh Posted February 15, 2023 Share #526 Posted February 15, 2023 @pocopico There are users who want to use transcoding on DS918+,DS920+,DS1019+, but want to use 7.0.1-42218 as FRIEND to avoid the genuine SN required by AME in DSM 7.1.0 or later. Currently 7.0.1-42218 has had another DSM file update The config checksums are mismatched. I did some tweaking to get the checksum right, but it reboots with KP as if your tcrpfriend module doesn't support 7.0.1-42218. Can you modify the above 3 models to be usable with 7.0.1-42218 with friend? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted February 19, 2023 Share #527 Posted February 19, 2023 (edited) On 2/15/2023 at 11:50 PM, Peter Suh said: @pocopico There are users who want to use transcoding on DS918+,DS920+,DS1019+, but want to use 7.0.1-42218 as FRIEND to avoid the genuine SN required by AME in DSM 7.1.0 or later. Currently 7.0.1-42218 has had another DSM file update The config checksums are mismatched. I did some tweaking to get the checksum right, but it reboots with KP as if your tcrpfriend module doesn't support 7.0.1-42218. Can you modify the above 3 models to be usable with 7.0.1-42218 with friend? @pocopico It looks like you've been very busy lately. I solved the issue I was asking about a few days ago on my own. As of 02/02/2023, I noticed that the DSM in 7.0.1-42218 has been modified and the bsp files need to be rebuilt accordingly. Below is the new menu for DSM 7.0.1-42218 of M SHELL for TCRP and supports only DS918+, DS920+, DS1019+ with transcoding. If you want your TCRP to work with 7.0.1-42218 you will need to do the same as me. Edited February 19, 2023 by Peter Suh 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted February 19, 2023 Share #528 Posted February 19, 2023 Last time TCRP FRIEND's DS3615xs was also a bsp problem. Applying it again in the build solved the KP issue. M SHELL reopened the model. 2 Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted February 20, 2023 Share #529 Posted February 20, 2023 I had two storage pools. One failed and off course my config was on this one, so luckily data is safe. I configured 2 way verification. In an original synology you can reset the nas in what they call a modus 1 reset. So can this be done with xpenology TCRP? Quote Link to comment Share on other sites More sharing options...
keasee Posted March 11, 2023 Share #530 Posted March 11, 2023 (edited) Hi @Peter Suh installed bare metal with your fork tcrp friend and used a DS920+ and could update to DSM 7.1.1-42962 Update 4. Everything seems fine , but it doesn't connect for additional Packages from Synology. Do I need to download each package and install manually ? ... Wait ... I changed from German to English language and now the packages of the Package Center are available as usual ! Maybe a bug ? ... in español the packages are also not available , maybe other languages as well ... see attachment best keasee Edited March 11, 2023 by keasee Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted March 11, 2023 Share #531 Posted March 11, 2023 55 minutes ago, keasee said: Hi @Peter Suh installed bare metal with your fork tcrp friend and used a DS920+ and could update to DSM 7.1.1-42962 Update 4. Everything seems fine , but it doesn't connect for additional Packages from Synology. Do I need to download each package and install manually ? ... Wait ... I changed from German to English language and now the packages of the Package Center are available as usual ! Maybe a bug ? ... in español the packages are also not available , maybe other languages as well ... see attachment best keasee This is the first report of Package Center issues in multilingual situations in XPE. My native language is Korean. Sometimes I switch to English for exams. It doesn't seem to be a problem specific to my M SHELL in particular. It may be the overall situation of REDPILL. It would be nice if it was reported to the TTG group, I don't know how to report. Quote Link to comment Share on other sites More sharing options...
AleAmadoC Posted March 11, 2023 Share #532 Posted March 11, 2023 This started to happen today, I will check my physical synology’s to check if its not an issue with them, its happening to me on bare metal and virtual environments, that previously where working with no issues and language is english. Quote Link to comment Share on other sites More sharing options...
gabe565 Posted March 11, 2023 Share #533 Posted March 11, 2023 (edited) I just installed Xpenology for the first time so I haven't seen the Package Center work, but I'm seeing the same errors. The package manager shows connection failed, and /var/log/synoscgi.log shows a 502 response code for Synology's getList endpoint. Edit: Seems to be working now. It must have been a server issue Edited March 11, 2023 by gabe565 Quote Link to comment Share on other sites More sharing options...
Zac_Nas Posted March 16, 2023 Share #534 Posted March 16, 2023 Hi, I have installed TCRp with friend (tinycore-redpill.v0.9.4.0-1.m-shell) on baremetal J-4205 ITX. I am seeing Dm esg being flooded with this message ( synobios get empty ttyS current). Adding a screenshot to show how frequently it happens. Any idea what is causing it ? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted March 16, 2023 Share #535 Posted March 16, 2023 1 hour ago, Zac_Nas said: Hi, I have installed TCRp with friend (tinycore-redpill.v0.9.4.0-1.m-shell) on baremetal J-4205 ITX. I am seeing Dm esg being flooded with this message ( synobios get empty ttyS current). Adding a screenshot to show how frequently it happens. Any idea what is causing it ? Answer from chatGPT. Seems like a mostly correct answer, isn't it? "synobios get empty ttyS current" is an error message that can occur on Synology NAS devices. This error message typically indicates that the system is unable to detect a serial port device on the specified ttyS interface. There are a few potential reasons why this error message might appear. One possibility is that the serial device connected to the NAS is not functioning properly or has been disconnected. Another possibility is that there is a configuration issue or a driver problem that is preventing the system from detecting the device. If you are experiencing this error message, some steps you can take to troubleshoot the issue include checking the physical connections of the serial device, verifying that the correct drivers are installed on the NAS, and ensuring that the serial device is configured correctly in the NAS settings. If you are still unable to resolve the issue, you may need to contact Synology support for further assistance. Quote Link to comment Share on other sites More sharing options...
Zac_Nas Posted March 16, 2023 Share #536 Posted March 16, 2023 7 minutes ago, Peter Suh said: Answer from chatGPT. Seems like a mostly correct answer, isn't it? "synobios get empty ttyS current" is an error message that can occur on Synology NAS devices. This error message typically indicates that the system is unable to detect a serial port device on the specified ttyS interface. There are a few potential reasons why this error message might appear. One possibility is that the serial device connected to the NAS is not functioning properly or has been disconnected. Another possibility is that there is a configuration issue or a driver problem that is preventing the system from detecting the device. If you are experiencing this error message, some steps you can take to troubleshoot the issue include checking the physical connections of the serial device, verifying that the correct drivers are installed on the NAS, and ensuring that the serial device is configured correctly in the NAS settings. If you are still unable to resolve the issue, you may need to contact Synology support for further assistance. Since I cannot technically "contact" the OEM, any tips on debugging would be helpful. The board does have a serial port, can check if it is enabled in the BIOS.. Quote Link to comment Share on other sites More sharing options...
nemesis122 Posted March 16, 2023 Share #537 Posted March 16, 2023 On 3/11/2023 at 1:01 AM, keasee said: Hi @Peter Suh installed bare metal with your fork tcrp friend and used a DS920+ and could update to DSM 7.1.1-42962 Update 4. Everything seems fine , but it doesn't connect for additional Packages from Synology. Do I need to download each package and install manually ? ... Wait ... I changed from German to English language and now the packages of the Package Center are available as usual ! Maybe a bug ? ... in español the packages are also not available , maybe other languages as well ... see attachment best keasee Hi You have to update your time synchronisation in DSM itself 1 Quote Link to comment Share on other sites More sharing options...
Zac_Nas Posted March 17, 2023 Share #538 Posted March 17, 2023 On 3/16/2023 at 12:04 PM, Peter Suh said: Answer from chatGPT. Seems like a mostly correct answer, isn't it? "synobios get empty ttyS current" is an error message that can occur on Synology NAS devices. This error message typically indicates that the system is unable to detect a serial port device on the specified ttyS interface. There are a few potential reasons why this error message might appear. One possibility is that the serial device connected to the NAS is not functioning properly or has been disconnected. Another possibility is that there is a configuration issue or a driver problem that is preventing the system from detecting the device. If you are experiencing this error message, some steps you can take to troubleshoot the issue include checking the physical connections of the serial device, verifying that the correct drivers are installed on the NAS, and ensuring that the serial device is configured correctly in the NAS settings. If you are still unable to resolve the issue, you may need to contact Synology support for further assistance. On 3/16/2023 at 12:17 PM, Zac_Nas said: Since I cannot technically "contact" the OEM, any tips on debugging would be helpful. The board does have a serial port, can check if it is enabled in the BIOS.. It appears to happen to only device tree based RP. The board has a single COM port but the user_config.json has 2 ports. Is this mandatory ? the ttyS1 points to a port that does not exist on the hardware syno_ttyS1=serial,0x2f8 syno_ttyS0=serial,0x3f8 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted March 17, 2023 Share #539 Posted March 17, 2023 38 minutes ago, Zac_Nas said: It appears to happen to only device tree based RP. The board has a single COM port but the user_config.json has 2 ports. Is this mandatory ? the ttyS1 points to a port that does not exist on the hardware syno_ttyS1=serial,0x2f8 syno_ttyS0=serial,0x3f8 It seems you are right. In all of the models below based on DT, the second serial port is defined. I don't know why it was defined and used in the first place, Looking at the definition, in console and earlycon syno_ttyS1: serial,0x2f8 I can't see the part that maps and uses. It seems like an unnecessary definition. I'll do a log test after cleaning up those values today. I also confirmed that the message was appearing. https://github.com/PeterSuh-Q3/redpill-load/blob/master/config/DS920%2B/7.1.1-42962/config.json https://github.com/PeterSuh-Q3/redpill-load/blob/master/config/DS923%2B/7.1.1-42962/config.json https://github.com/PeterSuh-Q3/redpill-load/blob/master/config/DS1621%2B/7.1.1-42962/config.json thank you for reporting Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted March 17, 2023 Share #540 Posted March 17, 2023 52 minutes ago, Zac_Nas said: It appears to happen to only device tree based RP. The board has a single COM port but the user_config.json has 2 ports. Is this mandatory ? the ttyS1 points to a port that does not exist on the hardware syno_ttyS1=serial,0x2f8 syno_ttyS0=serial,0x3f8 Removed second serial port definition, ttyS1(COM2), from all DT-based models. Rebuild the M SHELL for TCRP loader and check the log. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted March 17, 2023 Share #541 Posted March 17, 2023 2 hours ago, Zac_Nas said: It appears to happen to only device tree based RP. The board has a single COM port but the user_config.json has 2 ports. Is this mandatory ? the ttyS1 points to a port that does not exist on the hardware syno_ttyS1=serial,0x2f8 syno_ttyS0=serial,0x3f8 [ 1.407348] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.428828] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 1.429516] console [ttyS0] enabled [ 1.429516] console [ttyS0] enabled [ 1.429952] bootconsole [uart0] disabled [ 1.429952] bootconsole [uart0] disabled [ 1.548869] BUG: unable to handle kernel NULL pointer dereference at 0000000000000088 [ 1.549484] IP: [<ffffffff8138fe48>] serial8250_register_8250_port+0x428/0xb20 [ 1.549934] PGD 8e40e067 PUD 8f291067 PMD 0 [ 1.550255] Oops: 0000 [#1] SMP [ 1.550478] Modules linked in: [ 1.550718] CPU: 3 PID: 1 Comm: swapper/0 Tainted: G OE 4.4.180+ #42962 [ 1.551194] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 [ 1.552013] task: ffff880094580000 ti: ffff88009453c000 task.ti: ffff88009453c000 [ 1.552535] RIP: 0010:[<ffffffff8138fe48>] [<ffffffff8138fe48>] serial8250_register_8250_port+0x428/0xb20 [ 1.553143] RSP: 0018:ffff88009453fdd0 EFLAGS: 00010246 [ 1.553478] RAX: 0000000000000000 RBX: ffffffff81a07ca0 RCX: 0000000000000005 [ 1.553516] RDX: 0000000000000008 RSI: 0000000000000002 RDI: ffff880090f71800 [ 1.553532] RBP: ffff88009453fe08 R08: 00000000000003f8 R09: 0000000000000000 [ 1.554374] R10: 0000000000000010 R11: f000000000000000 R12: ffff880090f71800 [ 1.554418] R13: ffffffff8175886a R14: 00000000000002f8 R15: 0000000000000001 [ 1.554434] FS: 0000000000000000(0000) GS:ffff88009acc0000(0000) knlGS:0000000000000000 [ 1.555429] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1.555445] CR2: 0000000000000088 CR3: 000000008fbc7000 CR4: 00000000003606f0 [ 1.555461] Stack: [ 1.555477] ffffffff8116eb01 ffff880094401840 ffff880090f71800 0000000000000001 [ 1.556375] 0000000000000001 ffffffff81892f08 ffffffff813b5980 ffff88009453fe20 [ 1.556426] ffffffffa0003eb2 0000000000000000 ffff88009453fe58 ffffffffa00019e3 [ 1.557373] Call Trace: [ 1.557444] [<ffffffff8116eb01>] ? kmem_cache_alloc_trace+0x141/0x150 [ 1.557460] [<ffffffff813b5980>] ? driver_find+0x40/0x40 [ 1.557476] [<ffffffffa0003eb2>] serial8250_ready_watcher+0x2d2/0x570 [redpill] [ 1.558455] [<ffffffffa00019e3>] driver_register_shim+0x1c3/0x270 [redpill] [ 1.558471] [<ffffffff813b6ac1>] __platform_driver_register+0x31/0x40 [ 1.558487] [<ffffffff819287fc>] serial8250_init+0x116/0x152 [ 1.558503] [<ffffffff819286e6>] ? serial8250_isa_init_ports+0x2d0/0x2d0 [ 1.558519] [<ffffffff81000340>] do_one_initcall+0x80/0x130 [ 1.558535] [<ffffffff818f26e7>] ? do_early_param+0x90/0x90 [ 1.558550] [<ffffffff818f2fb4>] kernel_init_freeable+0x14d/0x1de [ 1.558566] [<ffffffff8156740d>] ? rest_init+0x74/0x74 [ 1.558582] [<ffffffff81567416>] kernel_init+0x9/0xd3 [ 1.558598] [<ffffffff8156cbef>] ret_from_fork+0x3f/0x80 [ 1.558614] [<ffffffff8156740d>] ? rest_init+0x74/0x74 [ 1.558630] Code: 67 00 00 0f 84 be 03 00 00 80 3d 33 7e 67 00 00 0f 84 89 04 00 00 80 3d e6 7d 67 00 00 0f 84 9d 04 00 00 4d 8b 8c 24 28 01 00 00 <4d> 8b b1 88 00 00 00 4d 85 f6 74 4c 49 8b 3e b9 03 00 00 00 48 [ 1.561373] RIP [<ffffffff8138fe48>] serial8250_register_8250_port+0x428/0xb20 [ 1.561411] RSP <ffff88009453fdd0> [ 1.561427] CR2: 0000000000000088 [ 1.561443] ---[ end trace aaf25d7537ae6534 ]--- [ 1.561511] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 [ 1.561511] [ 1.562482] Kernel Offset: disabled [ 17.351079] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 I tested after removing the settings below, and a kernel panic occurs. The settings are back again. I guess I'll have to look into it more accurately and make adjustments. "syno_ttyS1": "serial,0x2f8", Quote Link to comment Share on other sites More sharing options...
Zac_Nas Posted March 17, 2023 Share #542 Posted March 17, 2023 18 minutes ago, Peter Suh said: [ 1.407348] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.428828] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 1.429516] console [ttyS0] enabled [ 1.429516] console [ttyS0] enabled [ 1.429952] bootconsole [uart0] disabled [ 1.429952] bootconsole [uart0] disabled [ 1.548869] BUG: unable to handle kernel NULL pointer dereference at 0000000000000088 [ 1.549484] IP: [<ffffffff8138fe48>] serial8250_register_8250_port+0x428/0xb20 [ 1.549934] PGD 8e40e067 PUD 8f291067 PMD 0 [ 1.550255] Oops: 0000 [#1] SMP [ 1.550478] Modules linked in: [ 1.550718] CPU: 3 PID: 1 Comm: swapper/0 Tainted: G OE 4.4.180+ #42962 [ 1.551194] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 [ 1.552013] task: ffff880094580000 ti: ffff88009453c000 task.ti: ffff88009453c000 [ 1.552535] RIP: 0010:[<ffffffff8138fe48>] [<ffffffff8138fe48>] serial8250_register_8250_port+0x428/0xb20 [ 1.553143] RSP: 0018:ffff88009453fdd0 EFLAGS: 00010246 [ 1.553478] RAX: 0000000000000000 RBX: ffffffff81a07ca0 RCX: 0000000000000005 [ 1.553516] RDX: 0000000000000008 RSI: 0000000000000002 RDI: ffff880090f71800 [ 1.553532] RBP: ffff88009453fe08 R08: 00000000000003f8 R09: 0000000000000000 [ 1.554374] R10: 0000000000000010 R11: f000000000000000 R12: ffff880090f71800 [ 1.554418] R13: ffffffff8175886a R14: 00000000000002f8 R15: 0000000000000001 [ 1.554434] FS: 0000000000000000(0000) GS:ffff88009acc0000(0000) knlGS:0000000000000000 [ 1.555429] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1.555445] CR2: 0000000000000088 CR3: 000000008fbc7000 CR4: 00000000003606f0 [ 1.555461] Stack: [ 1.555477] ffffffff8116eb01 ffff880094401840 ffff880090f71800 0000000000000001 [ 1.556375] 0000000000000001 ffffffff81892f08 ffffffff813b5980 ffff88009453fe20 [ 1.556426] ffffffffa0003eb2 0000000000000000 ffff88009453fe58 ffffffffa00019e3 [ 1.557373] Call Trace: [ 1.557444] [<ffffffff8116eb01>] ? kmem_cache_alloc_trace+0x141/0x150 [ 1.557460] [<ffffffff813b5980>] ? driver_find+0x40/0x40 [ 1.557476] [<ffffffffa0003eb2>] serial8250_ready_watcher+0x2d2/0x570 [redpill] [ 1.558455] [<ffffffffa00019e3>] driver_register_shim+0x1c3/0x270 [redpill] [ 1.558471] [<ffffffff813b6ac1>] __platform_driver_register+0x31/0x40 [ 1.558487] [<ffffffff819287fc>] serial8250_init+0x116/0x152 [ 1.558503] [<ffffffff819286e6>] ? serial8250_isa_init_ports+0x2d0/0x2d0 [ 1.558519] [<ffffffff81000340>] do_one_initcall+0x80/0x130 [ 1.558535] [<ffffffff818f26e7>] ? do_early_param+0x90/0x90 [ 1.558550] [<ffffffff818f2fb4>] kernel_init_freeable+0x14d/0x1de [ 1.558566] [<ffffffff8156740d>] ? rest_init+0x74/0x74 [ 1.558582] [<ffffffff81567416>] kernel_init+0x9/0xd3 [ 1.558598] [<ffffffff8156cbef>] ret_from_fork+0x3f/0x80 [ 1.558614] [<ffffffff8156740d>] ? rest_init+0x74/0x74 [ 1.558630] Code: 67 00 00 0f 84 be 03 00 00 80 3d 33 7e 67 00 00 0f 84 89 04 00 00 80 3d e6 7d 67 00 00 0f 84 9d 04 00 00 4d 8b 8c 24 28 01 00 00 <4d> 8b b1 88 00 00 00 4d 85 f6 74 4c 49 8b 3e b9 03 00 00 00 48 [ 1.561373] RIP [<ffffffff8138fe48>] serial8250_register_8250_port+0x428/0xb20 [ 1.561411] RSP <ffff88009453fdd0> [ 1.561427] CR2: 0000000000000088 [ 1.561443] ---[ end trace aaf25d7537ae6534 ]--- [ 1.561511] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 [ 1.561511] [ 1.562482] Kernel Offset: disabled [ 17.351079] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 I tested after removing the settings below, and a kernel panic occurs. The settings are back again. I guess I'll have to look into it more accurately and make adjustments. "syno_ttyS1": "serial,0x2f8", I recall that there was a need for 2 serial ports during the ThorGroup days (I lost my login ID when the forum transitioned to emails hence the new one !). ttyS0 was used as console and ttyS1 is used to communicate with the speaker/fans/buttons.. which was supposed to be emulated in the kernel.. That could be the pointer to why the kernel panics. Not sure how this works in non DT builds Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 19, 2023 Share #543 Posted March 19, 2023 (edited) @pocopico Regarding Keyboard layout in TiniCore, I have an azerty keyboard... I had to do some trick to make TCRP azerty at boot for my needs : once TCRP started : In command line : tce-load -wi kmaps cp /usr/share/kmap/azerty/fr-pc.kmap /home/tc/fr-pc.kmap I edited /opt/bootsync.sh (sudo vi /opt/bootsync.sh) to add the following lines at the end of file : mkdir -p /usr/share/kmap/azerty/ cp /home/tc/fr-pc.kmap /usr/share/kmap/azerty/ loadkmap < /usr/share/kmap/azerty/fr-pc.kmap then backed up the configuration with ./rploader backup There is probably a better way to do so but at least for me it works... After running "tce-load -wi kmaps There are a lot of keyboard options available : Quote tc@box:~$ tce-load -wi kmaps Downloading: kmaps.tcz Connecting to repo.tinycorelinux.net (128.127.66.77:80) saving to 'kmaps.tcz' kmaps.tcz 100% |*******************************************************************************************************************************************************************************************| 140k 0:00:00 ETA 'kmaps.tcz' saved kmaps.tcz: OK tc@box:~$ cd /usr/share/kmap/ tc@box:/usr/share/kmap$ ls -Rtl .: total 4 lrwxrwxrwx 1 root root 47 Mar 19 12:13 th-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/th-latin1.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 th-win-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/th-win-latin1.kmap -rw-rw-r-- 1 root root 2055 Feb 13 2021 us.kmap drwxr-xr-x 2 root root 380 Dec 22 2010 qwertz/ drwxr-xr-x 2 root root 160 Dec 22 2010 dvorak/ drwxr-xr-x 2 root root 80 Dec 22 2010 fgGIod/ drwxr-xr-x 2 root root 80 Dec 22 2010 olpc/ drwxr-xr-x 2 root root 2360 Dec 22 2010 qwerty/ drwxr-xr-x 2 root root 200 Dec 22 2010 azerty/ drwxr-xr-x 2 root root 60 Dec 22 2010 colemak/ ./qwertz: total 0 lrwxrwxrwx 1 root root 50 Mar 19 12:13 croat.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/croat.kmap lrwxrwxrwx 1 root root 57 Mar 19 12:13 cz-us-qwertz.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/cz-us-qwertz.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 cz.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/cz.kmap lrwxrwxrwx 1 root root 65 Mar 19 12:13 de-latin1-nodeadkeys.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/de-latin1-nodeadkeys.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 de-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/de-latin1.kmap lrwxrwxrwx 1 root root 53 Mar 19 12:13 de-mobii.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/de-mobii.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 de.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/de.kmap lrwxrwxrwx 1 root root 57 Mar 19 12:13 de_CH-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/de_CH-latin1.kmap lrwxrwxrwx 1 root root 57 Mar 19 12:13 fr_CH-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/fr_CH-latin1.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 fr_CH.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/fr_CH.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 hu.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/hu.kmap lrwxrwxrwx 1 root root 60 Mar 19 12:13 sg-latin1-lk450.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/sg-latin1-lk450.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 sg-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/sg-latin1.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 sg.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/sg.kmap lrwxrwxrwx 1 root root 59 Mar 19 12:13 sk-prog-qwertz.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/sk-prog-qwertz.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 sk-qwertz.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/sk-qwertz.kmap lrwxrwxrwx 1 root root 52 Mar 19 12:13 slovene.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwertz/slovene.kmap ./dvorak: total 0 lrwxrwxrwx 1 root root 56 Mar 19 12:13 ANSI-dvorak.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/dvorak/ANSI-dvorak.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 dvorak-fr.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/dvorak/dvorak-fr.kmap lrwxrwxrwx 1 root root 53 Mar 19 12:13 dvorak-l.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/dvorak/dvorak-l.kmap lrwxrwxrwx 1 root root 53 Mar 19 12:13 dvorak-r.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/dvorak/dvorak-r.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 dvorak.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/dvorak/dvorak.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 no.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/dvorak/no.kmap ./fgGIod: total 0 lrwxrwxrwx 1 root root 56 Mar 19 12:13 tr_f-latin5.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/fgGIod/tr_f-latin5.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 trf.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/fgGIod/trf.kmap ./olpc: total 0 lrwxrwxrwx 1 root root 45 Mar 19 12:13 es.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/olpc/es.kmap lrwxrwxrwx 1 root root 45 Mar 19 12:13 pt.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/olpc/pt.kmap ./qwerty: total 0 lrwxrwxrwx 1 root root 52 Mar 19 12:13 bashkir.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/bashkir.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 bg-cp1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/bg-cp1251.kmap lrwxrwxrwx 1 root root 53 Mar 19 12:13 bg-cp855.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/bg-cp855.kmap lrwxrwxrwx 1 root root 58 Mar 19 12:13 bg_bds-cp1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/bg_bds-cp1251.kmap lrwxrwxrwx 1 root root 56 Mar 19 12:13 bg_bds-utf8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/bg_bds-utf8.kmap lrwxrwxrwx 1 root root 58 Mar 19 12:13 bg_pho-cp1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/bg_pho-cp1251.kmap lrwxrwxrwx 1 root root 56 Mar 19 12:13 bg_pho-utf8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/bg_pho-utf8.kmap lrwxrwxrwx 1 root root 52 Mar 19 12:13 br-abnt.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/br-abnt.kmap lrwxrwxrwx 1 root root 53 Mar 19 12:13 br-abnt2.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/br-abnt2.kmap lrwxrwxrwx 1 root root 60 Mar 19 12:13 br-latin1-abnt2.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/br-latin1-abnt2.kmap lrwxrwxrwx 1 root root 57 Mar 19 12:13 br-latin1-us.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/br-latin1-us.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 by-cp1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/by-cp1251.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 by.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/by.kmap lrwxrwxrwx 1 root root 57 Mar 19 12:13 bywin-cp1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/bywin-cp1251.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 cf.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/cf.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 cz-cp1250.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/cz-cp1250.kmap lrwxrwxrwx 1 root root 57 Mar 19 12:13 cz-lat2-prog.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/cz-lat2-prog.kmap lrwxrwxrwx 1 root root 52 Mar 19 12:13 cz-lat2.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/cz-lat2.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 cz.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/cz.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 defkeymap.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/defkeymap.kmap lrwxrwxrwx 1 root root 59 Mar 19 12:13 defkeymap_V1.0.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/defkeymap_V1.0.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 dk-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/dk-latin1.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 dk.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/dk.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 emacs.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/emacs.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 emacs2.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/emacs2.kmap lrwxrwxrwx 1 root root 53 Mar 19 12:13 es-cp850.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/es-cp850.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 es.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/es.kmap lrwxrwxrwx 1 root root 58 Mar 19 12:13 et-nodeadkeys.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/et-nodeadkeys.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 et.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/et.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 fi-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/fi-latin1.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 fi-latin9.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/fi-latin9.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 fi.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/fi.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 gr-pc.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/gr-pc.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 gr.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/gr.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 hu101.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/hu101.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 il-heb.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/il-heb.kmap lrwxrwxrwx 1 root root 56 Mar 19 12:13 il-phonetic.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/il-phonetic.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 il.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/il.kmap lrwxrwxrwx 1 root root 57 Mar 19 12:13 is-latin1-us.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/is-latin1-us.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 is-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/is-latin1.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 it-ibm.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/it-ibm.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 it.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/it.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 it2.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/it2.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 jp106.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/jp106.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 kazakh.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/kazakh.kmap lrwxrwxrwx 1 root root 60 Mar 19 12:13 ky_alt_sh-UTF-8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ky_alt_sh-UTF-8.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 kyrgyz.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/kyrgyz.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 la-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/la-latin1.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 lt.baltic.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/lt.baltic.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 lt.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/lt.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 lt.l4.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/lt.l4.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 mk-cp1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/mk-cp1251.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 mk-utf.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/mk-utf.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 mk.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/mk.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 mk0.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/mk0.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 nl.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/nl.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 nl2.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/nl2.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 no-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/no-latin1.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 no.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/no.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 pc110.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/pc110.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 pl.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/pl.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 pl1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/pl1.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 pl2.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/pl2.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 pl3.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/pl3.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 pl4.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/pl4.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 pt-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/pt-latin1.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 pt-latin9.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/pt-latin9.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 ro.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ro.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 ro_std.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ro_std.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 ro_win.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ro_win.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 ru-cp1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ru-cp1251.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 ru-ms.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ru-ms.kmap lrwxrwxrwx 1 root root 55 Mar 19 12:13 ru-yawerty.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ru-yawerty.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 ru.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ru.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 ru1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ru1.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 ru2.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ru2.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 ru3.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ru3.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 ru4.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ru4.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 ru_win.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ru_win.kmap lrwxrwxrwx 1 root root 61 Mar 19 12:13 ruwin_alt-CP1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_alt-CP1251.kmap lrwxrwxrwx 1 root root 61 Mar 19 12:13 ruwin_alt-KOI8-R.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_alt-KOI8-R.kmap lrwxrwxrwx 1 root root 60 Mar 19 12:13 ruwin_alt-UTF-8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_alt-UTF-8.kmap lrwxrwxrwx 1 root root 62 Mar 19 12:13 ruwin_cplk-CP1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_cplk-CP1251.kmap lrwxrwxrwx 1 root root 62 Mar 19 12:13 ruwin_cplk-KOI8-R.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_cplk-KOI8-R.kmap lrwxrwxrwx 1 root root 61 Mar 19 12:13 ruwin_cplk-UTF-8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_cplk-UTF-8.kmap lrwxrwxrwx 1 root root 63 Mar 19 12:13 ruwin_ct_sh-CP1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_ct_sh-CP1251.kmap lrwxrwxrwx 1 root root 63 Mar 19 12:13 ruwin_ct_sh-KOI8-R.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_ct_sh-KOI8-R.kmap lrwxrwxrwx 1 root root 62 Mar 19 12:13 ruwin_ct_sh-UTF-8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_ct_sh-UTF-8.kmap lrwxrwxrwx 1 root root 62 Mar 19 12:13 ruwin_ctrl-CP1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_ctrl-CP1251.kmap lrwxrwxrwx 1 root root 62 Mar 19 12:13 ruwin_ctrl-KOI8-R.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_ctrl-KOI8-R.kmap lrwxrwxrwx 1 root root 61 Mar 19 12:13 ruwin_ctrl-UTF-8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ruwin_ctrl-UTF-8.kmap lrwxrwxrwx 1 root root 56 Mar 19 12:13 se-fi-ir209.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/se-fi-ir209.kmap lrwxrwxrwx 1 root root 55 Mar 19 12:13 se-fi-lat6.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/se-fi-lat6.kmap lrwxrwxrwx 1 root root 53 Mar 19 12:13 se-ir209.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/se-ir209.kmap lrwxrwxrwx 1 root root 52 Mar 19 12:13 se-lat6.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/se-lat6.kmap lrwxrwxrwx 1 root root 59 Mar 19 12:13 sk-prog-qwerty.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/sk-prog-qwerty.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 sk-qwerty.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/sk-qwerty.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 sr-cy.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/sr-cy.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 sv-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/sv-latin1.kmap lrwxrwxrwx 1 root root 56 Mar 19 12:13 tj_alt-UTF8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/tj_alt-UTF8.kmap lrwxrwxrwx 1 root root 56 Mar 19 12:13 tr_q-latin5.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/tr_q-latin5.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 tralt.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/tralt.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 trf.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/trf.kmap lrwxrwxrwx 1 root root 48 Mar 19 12:13 trq.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/trq.kmap lrwxrwxrwx 1 root root 60 Mar 19 12:13 ttwin_alt-UTF-8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ttwin_alt-UTF-8.kmap lrwxrwxrwx 1 root root 61 Mar 19 12:13 ttwin_cplk-UTF-8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ttwin_cplk-UTF-8.kmap lrwxrwxrwx 1 root root 62 Mar 19 12:13 ttwin_ct_sh-UTF-8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ttwin_ct_sh-UTF-8.kmap lrwxrwxrwx 1 root root 61 Mar 19 12:13 ttwin_ctrl-UTF-8.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ttwin_ctrl-UTF-8.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 ua-cp1251.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ua-cp1251.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 ua-utf-ws.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ua-utf-ws.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 ua-utf.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ua-utf.kmap lrwxrwxrwx 1 root root 50 Mar 19 12:13 ua-ws.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ua-ws.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 ua.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/ua.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 uk.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/uk.kmap lrwxrwxrwx 1 root root 55 Mar 19 12:13 us-acentos.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/us-acentos.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 us.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/qwerty/us.kmap ./azerty: total 4 lrwxrwxrwx 1 root root 51 Mar 19 12:13 azerty.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/azerty.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 be-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/be-latin1.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 fr-latin1.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/fr-latin1.kmap lrwxrwxrwx 1 root root 54 Mar 19 12:13 fr-latin9.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/fr-latin9.kmap lrwxrwxrwx 1 root root 47 Mar 19 12:13 fr.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/fr.kmap lrwxrwxrwx 1 root root 51 Mar 19 12:13 wangbe.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/wangbe.kmap lrwxrwxrwx 1 root root 52 Mar 19 12:13 wangbe2.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/azerty/wangbe2.kmap -rw-r--r-- 1 root root 2055 Mar 19 12:07 fr-pc.kmap ./colemak: total 0 lrwxrwxrwx 1 root root 55 Mar 19 12:13 en-latin9.kmap -> /tmp/tcloop/kmaps/usr/share/kmap/colemak/en-latin9.kmap we could also : cd /tmp/tcloop/kmaps/usr/share/kmap/ tar zcvf /home/tc/keymaps.tgz * then in /opt/bootsync.sh add : tar xvf /home/tc/keymap.tgz -C /usr/share/kmap/ loadkmap < /usr/share/kmap/azerty/fr-pc.kmap and ./rploader.sh backup Edited March 19, 2023 by Orphée Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted March 20, 2023 Share #544 Posted March 20, 2023 (edited) 15 hours ago, Orphée said: @pocopico Regarding Keyboard layout in TiniCore, I have an azerty keyboard... I had to do some trick to make TCRP azerty at boot for my needs : once TCRP started : In command line : tce-load -wi kmaps cp /usr/share/kmap/azerty/fr-pc.kmap /home/tc/fr-pc.kmap I edited /opt/bootsync.sh (sudo vi /opt/bootsync.sh) to add the following lines at the end of file : mkdir -p /usr/share/kmap/azerty/ cp /home/tc/fr-pc.kmap /usr/share/kmap/azerty/ loadkmap < /usr/share/kmap/azerty/fr-pc.kmap then backed up the configuration with ./rploader backup There is probably a better way to do so but at least for me it works... After running "tce-load -wi kmaps There are a lot of keyboard options available : we could also : cd /tmp/tcloop/kmaps/usr/share/kmap/ tar zcvf /home/tc/keymaps.tgz * then in /opt/bootsync.sh add : tar xvf /home/tc/keymap.tgz -C /usr/share/kmap/ loadkmap < /usr/share/kmap/azerty/fr-pc.kmap and ./rploader.sh backup @Orphée https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/menu_m.sh#L664 I already configured kmap in M SHELL for TCRP a long time ago and It is being saved permanently as in the script below. sudo echo "kmaps.tcz" >> /mnt/${tcrppart}/cde/onboot.lst However, Korea also uses the us keyboard structure I haven't received any feedback on whether it works properly using the keyboard layout of non-English speaking countries. Can you test if kmap and French key layout are working properly in my M SHELL? https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.4.0-1 Edited March 20, 2023 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Zac_Nas Posted March 20, 2023 Share #545 Posted March 20, 2023 On 2/19/2023 at 6:16 PM, Peter Suh said: @pocopico It looks like you've been very busy lately. I solved the issue I was asking about a few days ago on my own. As of 02/02/2023, I noticed that the DSM in 7.0.1-42218 has been modified and the bsp files need to be rebuilt accordingly. Below is the new menu for DSM 7.0.1-42218 of M SHELL for TCRP and supports only DS918+, DS920+, DS1019+ with transcoding. If you want your TCRP to work with 7.0.1-42218 you will need to do the same as me. Hi @pocopicoare the extensions built for 7.1.1.42962 ? I am trying to add the hwmon and nct6775 extension. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted March 20, 2023 Share #546 Posted March 20, 2023 35 minutes ago, Zac_Nas said: Hi @pocopicoare the extensions built for 7.1.1.42962 ? I am trying to add the hwmon and nct6775 extension. My M shell for TCRP supports that version. https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.4.0-1 All models of nct6775 are supported except v1000/r1000 platform. Assuming that user_config.json has already been set up, try the command as below. ./myv.sh DS3622xs+F noconfig The following ext selection screen appears. nct6775 is number 47. The loader build will be done with the TCRP FRIEND version. 1 Quote Link to comment Share on other sites More sharing options...
Zac_Nas Posted March 21, 2023 Share #547 Posted March 21, 2023 On 3/20/2023 at 8:05 PM, Peter Suh said: My M shell for TCRP supports that version. https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.4.0-1 All models of nct6775 are supported except v1000/r1000 platform. Assuming that user_config.json has already been set up, try the command as below. ./myv.sh DS3622xs+F noconfig The following ext selection screen appears. nct6775 is number 47. The loader build will be done with the TCRP FRIEND version. Thanks Peter, am building a DS920+, assume that works for the DT based models as well. Will give it a try and report. 1 Quote Link to comment Share on other sites More sharing options...
Rebutia Posted March 25, 2023 Share #548 Posted March 25, 2023 Hi Peter, have you ever thought about making separate thread of your M shell? Say, like a loader setup assistant. Not only it is less confusing for people when reading this tcrp thread, you can also use this chance to write tutorial/documentation for your M shell and pin the first thread as a guide on your recent development. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted March 25, 2023 Share #549 Posted March 25, 2023 5 hours ago, Rebutia said: Hi Peter, have you ever thought about making separate thread of your M shell? Say, like a loader setup assistant. Not only it is less confusing for people when reading this tcrp thread, you can also use this chance to write tutorial/documentation for your M shell and pin the first thread as a guide on your recent development. Thank you for your interest. It's already here. 2 Quote Link to comment Share on other sites More sharing options...
David Rollin Posted March 25, 2023 Share #550 Posted March 25, 2023 Hi Everyone, I have this issue installing TCRP Friend on a x10sdv-6c-tln4f mobo : installation goes well using 3 SATA drives but when I reboot, I got nothing. I experimented several changes, and this is what I found out: When using only one drive all is fine, rebooting, the sytem is there. but using 3 drives, I have to disconnect the 3 drives, reinstall on a spare and then connect the 3 and then i have access to the array. Out of 10 reboots, I got it back only one time with the 3 drive array. The difference I noticed is that with only one drive, the 2x 10ge port turn blue (connected) . When using 3 drives the 2 x 10ge ports stays green (usually green mean 1gbe but i got no ip) I have no idea what is the readon this is doing this, so i reformated all the 3 drives individually and they reinstalled TCRP friend and rebooted but it is still doing the same. The only way I could get it to work is to install one drive in pool n°1 of one drive and another pool n°2 of 3 drives. When rebooting all is coming up but using a drive just for that . Any ideas? Mobo booting : TCRP friend loading : notice the 2 x 10Gbe port coming up Then the 3 first port are green when 3 drives are in, no ip found With one drive that ports 1 and 2 will be blue and the 3 and 4 green all having IPs Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.