1 0

Using Synergy with YellowDog Linux 6

Hi Everyone,

The title says it all. This is for people who use their monitor with the Playstation3 and especially for those, who develop using the PS3. Now, I have a single monitor where I have both my PS3 and my computer attached through a Tuner and a VGA connection respectively. Starting development with the PS3 and not having my LAN and computer around would have created so many problems for me. Furthermore, I already have a jungle of wires behind my PC cabinet and I did not want to add a KVM switch and two more hardware peripherals for the PS3. I needed a software solution to this and Remote Desktop/VNC would not do it for me, since my PS3 is already connected physically to my monitor. This is where this amazing app called “Synergy” comes into play.

What is Synergy?
Synergy is a software KVM switch. If you do not know what a KVM switch is, you can read this article. A typical KVM switch allows you to use a single set of hardware devices to work with two or more machines, which can be on different Operating Systems. You can learn more about Synergy on its homepage here. I don’t want to explain all that here, since they can explain it way better than I can.

Requirements:

You will need to have the following things in order for this setup to work:

- PS3 connected to a network/internet.
- PC connected to the same network or the internet.
- Synergy installer for Windows/OSX/Linux/PS3 YDL 6.

Downloading the installers depends entirely on your selection. I was unable to find a later release for Synergy 1.3.1 for YDL 6. However, I might compile one on my own and upload it here (I am not making any promises :P ).

From here on, you can follow the official Synergy guide:

Step 1 – Choose a server
The first step is to pick which keyboard and mouse you want to share. The computer with that keyboard and mouse is called the “primary screen” and it runs the synergy server. All of the other computers are “secondary screens” and run the synergy client.

Step 2 – Install the software

Second, you install the software. Choose the appropriate package and install it. For example, on Windows you would run SynergyInstaller. You must install the software on all the computers that will share the mouse and keyboard (clients and server). On OS X you’ll just have a folder with some documentation and two programs. You can put this folder anywhere.

Step 3 – Configure and start the server

Next you configure the server. You’ll tell synergy the name of the primary and secondary screens, which screens are next to which, and choose desired options. On Windows there’s a dialog box for setting the configuration. On other systems you’ll create a simple text file.

Note that when you tell synergy that screen A is to the left of screen B this does not imply that B is to the right of A. You must explicitly indicate both relations. If you don’t do both then when you’re running synergy you’ll find you’re unable to leave one of the screens.

Windows
On Windows run synergy by double clicking on the synergy file. This brings up a dialog. Configure the server:

* Click the Share this computer's keyboard and mouse (server) radio button
* Click the Screens & Links Configure... button
* Click the + button to add the server to the Screens list
o Enter the name of server (the computer's name is the recommended name)
o Optionally enter other names the server is known by
o Click OK
* Use the + button to add your other computers
o Using a computer's name as its screen name is recommended
o Choose desired screen options on the Add Screen dialog
* Use the controls under Links to link screens together
o Click (once) on the server's name in the Screens list
o Choose the screen to the left of the server; use --- if there is no screen
to the left of the server
o Choose the screens to the right, above and below the server
o Repeat the above steps for all the other screens
* Click OK to close the Screens & Links dialog
* Use Options... to set desired options
* If the server's screen name is not the server's computer name:
o Click Advanced...
o Enter the server's screen name next to Screen Name
o Click OK

Now click Test. The server will start and you’ll see a console window with log messages telling you about synergy’s progress. If an error occurs you’ll get one or more dialog boxes telling you what the errors are; read the errors to determine the problem then correct them and try Test again. See Step 5 for typical errors.

Unix or Mac OS X
Create a text file named synergy.conf with the following:

section: screens
screen1:
screen2:
end
section: links
screen1:
right = screen2
screen2:
left = screen1
end

Replace each occurrence of screen1 with the host name of the primary screen computer (as reported by the hostname program) and screen2 with the host name of a secondary screen computer. In the above example, screen2 is to the right of screen1 and screen1 is to the left of screen2. If necessary you should replace right and left with left, right, up, or down. If you have more than two computers you can add those too: add each computer’s host name in the screens section and add the appropriate links. See the configuration guide for more configuration possibilities.

Now start the server. Normally synergy wants to run “in the background.” It detaches from the terminal and doesn’t have a visible window, effectively disappearing from view. Until you’re sure your configuration works, you should start synergy “in the foreground” using the -f command line option.

On unix type the command below in a shell. If synergys is not in your PATH then use the full pathname.

synergys -f --config synergy.conf

On OS X open Terminal in the Utilities folder in the Applications folder. Drag the synergys program from the synergy folder onto the Terminal window. The path to the synergys program will appear. Add the following to the same line, type a space at the end of the line but don’t press enter:

-f --config

Now drag the synergy.conf file onto the Terminal window and press enter. Check the reported messages for errors. Use ctrl+c to stop synergy if it didn’t stop automatically, correct any problems, and start it again.

The Client

Ok, I am not going to go over configuring different clients in this post, since we are only concerned with Yellow Dog Linux. However, if you still want to do that, you can read about it on their homepage. This is where the tricky part starts. Configuring the PS3 for Synergy turned out to be way more difficult than I imagined. This was not because of Synergy itself but because the PS3′s network configuration kept breaking all the time. I am going to make a seperate post about that, so let’s move on to configuring it.

First install the Synergy RPM that you downloaded from link in the earlier part of this post. You need to make sure that you are connected to the internet for the RPM to install correctly. Once you install it, you can test if synergy can connect to your server by typing:

synergy -f

For example, I did:

synergy -f 192.168.1.2

AutoStarting Synergy with YellowDog Linux

All of this won’t be of any use until this setup always runs automatically whenever we start YDL on the PS3. So firstly, you need to configure your Server to AutoStart Synergy everytime it boots. To configure that, you can follow their official guide on this page.

Synergy requires an X server. That means a server must be running and synergy must be authorized to connect to that server. It’s best to have the display manager start synergy. You’ll need the necessary (probably root) permission to modify the display manager configuration files. If you don’t have that permission you can start synergy after logging in via the .xsession file.

Typically, you need to edit three script files. The first file will start synergy before a user logs in, the second will kill that copy of synergy, and the third will start it again after the user logs in.

The files we need to edit are:

gdm/Init/Default
gdm/PostLogin/Default
gdm/PreSession/Default
gdm/PostSession/Default

You need to be logged in as root to perform the steps below. Open up a terminal and type:

su -

Enter the root password when it asks you to. Now navigate to the following directory:

cd /etc/gdm

Then Type

gedit Init/Default

you need to write the following lines into the file. You should write them somewhere on the top of this file:

/usr/bin/killall synergyc
sleep 1
/usr/bin/synergyc

Save it and then open the next file using gedit and enter the following lines into it. Note that this file may be called, Default.sample and you will need to rename it to make it work. It might be empty as well.

gedit /PostLogin/Default

and enter the following lines

/usr/bin/killall synergyc
sleep 1

You need to enter the following lines in the next two files at gdm/PreSession/Default and gdm/PostSession/Default.

/usr/bin/killall synergyc
sleep 1
/usr/bin/synergyc

Save all the files and verify the changes. Logout and restart the client and once you get past booting screen, you will notice that you can now switch between the server and client screens. The server should also display that the client is connected now. This setup will work for all users but you always need to make sure that your server is running.

So, there you have it.

Regards,
M.H.A.Q.S.

Read full story »

Updating DSL-2640T to RouterTech Firmware

WARNING: Always check the firmware you need to download using RUC first (linked below).

Before you start, I must say that updating a router’s firmware is not for the faint hearted and I take no responsibility if anything goes wrong with your router. This is pretty much a n00b friendly tutorial, so you should be okay, if you follow everything as written in the RouterTech’s help docs and in this tutorial. Now over to the tutorial:

Please download the following tools and confirm the settings following afterward.

1- Download RUC (Router Update Checker, available here)
2- Download WEB (Wireless Environment Builder, available here).
3- Download your router’s latest official firmware (you should have a copy, in case this goes kaput).

Now whatever you do, don’t blame me. Next open up RUC and enter your router login info, defaults are:

ip: 192.168.1.1
web user: admin
web pass: admin
telenet user: root
telnet pass: admin
no of ethernet ports: 4
router description: dlink g624T

check all boxes at the bottom (they are there for a reason).

* You can edit the routers.txt and make an entry for DSL-2640T as follows too:

DSL-2640T 4

Once RUC gives you a report, it should be similar to the following:

Router Upgrade Check 1.2.9 19/09/2008 09:49:15
Router IP: 192.168.1.1
CLI is needed
Description: Dlink G624T
Board type: AR7VW
Product ID: AR7WRD
Bootloader: psbl
RAM 16.0 MB
Flash (ROM) 4.0 MB
ADAM2: No
No default env: No
Linux version: 2.4.17_mvl21-malta-mips_fp_le
Firmware build:
Firmware version: V3.02B01T01.ME-A.20080125
Firmware stamp: 20080125143616
CPU: MIPS 4KEc V4.8
DSP: 6.00.04.00
Annex: A
/proc/wlan: Yes
/usr/sbin/wlan: Yes
TIAP: Yes
TNETW: Yes
Wireless: Yes
WIFI chip: TNETW1350A
WIFI chip conf: Yes
Ports: 4
Marvell (or Marvell like): No
NSP: V3.02B01T01.ME-A.20080125
Manufacturers: D-link Corporation
RNDIS: Telogy Networks Inc

Now, the things to make sure in the above log are:

Product ID or Board type: AR7WRD
Bootloader: psbl
RAM 16.0 MB
Flash (ROM) 4.0 MB
WIFI chip: TNETW1350A
Marvell (or Marvell like): No

The above settings will qualify you for a RouterTech firmware upgrade. The reason to run RUC was to backup all your settings and configurations at one place. If you have not backed-up your settings, do it now. No one will be responsible, if you do this carelessly and brick your router.

Download RouterTech firmware from http://routertech.org/forum.php. You must register on the forum to download the firmware. For DSL2640T, you’ll need the RoHS 4-port PSP firmware. It should be named something as follows:

routertech-rohs-ar7wrd-pspboot-firmware-xxxxxxx.zip

extract it to some directory and open up the upgrade.html file and DO WHAT IT SAYS.

1- back-up all your settings
a- /proc/ticfg/env
b- /proc/interrupts
c- /etc/led.conf
d- config.bin (using your router’s “save config to hard disk” option in the web panel)
2- reset your router to factory default settings. reboot.
3- once the router comes back online, save all settings and reboot again.
4- open up the update firmware panel in the router’s web panel; Tools->Firmware and browse to where you extracted the above zip file and select:

routertech_ar7wrd_1350a_pspboot_firmware_xxxxxxx_xxx

Now click on Apply and pray to God that all goes well. Leave the router alone for about

8-10 MINUTES…

After ten minutes, telnet into your router again and see if it lets you log in using:

telnet 192.168.1.1

Log in using user:Admin and pass:Admin.

If the router let you log in, go to your Router’s web panel and into the System panel. Click on Restore Factory Settings and Reboot. Once the router comes online. Telnet back into your router:

type

cat /proc/ticfg/env

and take a look at the variables and back them up.

Next perform the following steps:

setenv led_conf led.2640t && /sbin/reboot

once again, when the router comes back online. Telnet again into the router and type:

setenv vlynq_polarity low

Reboot the router once again and you should have a working DSL-2640T running with everything on a custom routertech firmware. You can issue all the commands above in a single go but I say, do not mess with your router, unless you are confident of your actions.

For the people, who do not have their WLAN working, after the upgrade or even so before the upgrade, please follow the steps below:

A common issue for many people on a router exists, where the AP stays off and only comes online by using

"echo NVS_TFTP_LOAD 0 > /proc/ticfg/env"

However, this can create issues on the environment side and the solution itself is temporary too. The actual issue is a corrupted WLAN EEPROM, which needs to be fixed:

- Extract WEB (Wireless Environment Builder) somewhere in a directory and open it up.
- Fill up the information it asks for.
- If you do not have a TWNET ID, go to your router’s system logs. They can be found in Status->SystemLog. Browse them and find the line where it says:

"Failed to get DIE ID from wlan driver. Cannot validate EEPROM Image"
....
....
"Setting bootloader env NVS_TFTP_LOAD to 1"

- Look for a string similar to this:

"Retrieving EEPROM image file nvs_5e015cf4a901151d.bin from TFTP Server"
"ERROR: TFTP of file : nvs_5e015cf4a901151d.bin failed"

- there, the string next to “nvs_” is your TWNETID i.e.5e015cf4a901151d. It should be different for you.
- copy it in WEB and click on “get router details” or “build environment”. It should work and after a while, it will ask you that it can send the script directly to the router. Do so, and let the router reboot after that. You’re done, once the Router comes back online, go check your environment now and you’re good to go.

I hope this will help many people. You might wanna head over to RouterTech for more help and if you run into any issues. Those guys are a great help and they have some fantastic stuff there.

Regards,
M.H.A.Q.S.

Read full story »

Introduction to Papervision3D

Update: I received many requests from people to have an FLV version of the video uploaded. So, here it is. The original MP4 is still linked below:

Hi Everyone,

I wanted to do an introductory tutorial for PV3D for a long time but I never had the time (motivation, honestly :P ) to complete it. I also had the view that there were already so many other PV3D intro tutorials floating around the web right after its first beta release. However, I did have some issues with those introductory tutorials. So yesterday, I whipped up this tutorial despite all the noise around me (you’ll notice it). I think it is fairly long and can really help a flash or AS3 user begin understanding and use PV3D. One more reason to create this tutorial was the launch of PV3D forums and the newly added competition that asks for such a tutorial. If you think you like the tutorial or if not, you can always create better stuff.

Here’s a link to, it. Also, here’s a link to the project files. I have given a direct link to an MP4 file, so that you can watch it using your favorite movie player ;) .

Thanks,
MHAQS

Read full story »
Page 3 of 141234510...Last »