Lubuntu requires much less memory and runs much faster on RoBoard in contrast to the official Ubuntu release. (We suggest that you use Lubuntu 10.04 (LTS) on RoBoard; don't use 11.04 because it isn't compatible to i386~i586 PC.)

To everyone who feels that the official Ubuntu runs very slowly on RoBoard, you may want to try the Lubuntu branch of Ubuntu:

Lubuntu requires much less memory and runs much faster on RoBoard in contrast to the official Ubuntu release. (We suggest that you use Lubuntu 10.04 (LTS) on RoBoard; don't use 11.04 because it isn't compatible to i386~i586 PC.)

Do you know if Lubuntu will work with the eBox 3350, and also whether the installation includes ethernet support? All I want is an OS that will connect to the internet without having to wrangle with grubs and kernels and a lot of new jargon.

Do you know if Lubuntu will work with the eBox 3350, and also whether the installation includes ethernet support? All I want is an OS that will connect to the internet without having to wrangle with grubs and kernels and a lot of new jargon.

ozfiddler wrote:Do you know if Lubuntu will work with the eBox 3350, and also whether the installation includes ethernet support? ...

In our test, Lubuntu works on eBox 3350, and basically you can follow the RB-110 Ubuntu installation guide to install Lubuntu on the eBox (of course, not every step and screen are the same, but is the principle).

ozfiddler wrote:Do you know if Lubuntu will work with the eBox 3350, and also whether the installation includes ethernet support? ...

In our test, Lubuntu works on eBox 3350, and basically you can follow the RB-110 Ubuntu installation guide to install Lubuntu on the eBox (of course, not every step and screen are the same, but is the principle).

Just wanted to say a big thanks for the Lubuntu setup instructions. I have about 95% of it working now on my Roboard - 110. I am really liking the Xing/Putty interface.

At this time I only have the Xing/Putty working through LAN. I am struggling a bit with the VT6655 WiFi card. On unplugging the VGA and inserting the WiFi card I can boot up and still connect up through the Wired LAN connection.

I have issued the iwlist scanning command can see the various networks and grabbed the settings, in my case
eth9
channel 1
managed
etc...

I have entered these settings into /etc/network/interfaces file (I noticed that by default the settings in there wher REM'd out, so I removed the '#' from the beginning of each row and put the settings in (including the wireless WPA2 key). Also alterred the manager-settings.conf file to show as eth9 for wireless_interfaces.

Saved the settings.
Reboot the device, removing the LAN wired cable and leaving the VT6655 in.
But I am not seeing the device show up. I have a ping running on the same IP as it was for Wired LAN but something is amiss, I do not see any responses. If I reboot the device with the wired LAN plugged back in everything is good again. Any gotchas I might be missing?

thanks

Just wanted to say a big thanks for the Lubuntu setup instructions. I have about 95% of it working now on my Roboard - 110. I am really liking the Xing/Putty interface.

At this time I only have the Xing/Putty working through LAN. I am struggling a bit with the VT6655 WiFi card. On unplugging the VGA and inserting the WiFi card I can boot up and still connect up through the Wired LAN connection.

I have issued the iwlist scanning command can see the various networks and grabbed the settings, in my case
eth9
channel 1
managed
etc...

I have entered these settings into /etc/network/interfaces file (I noticed that by default the settings in there wher REM'd out, so I removed the '#' from the beginning of each row and put the settings in (including the wireless WPA2 key). Also alterred the manager-settings.conf file to show as eth9 for wireless_interfaces.

Saved the settings.
Reboot the device, removing the LAN wired cable and leaving the VT6655 in.
But I am not seeing the device show up. I have a ping running on the same IP as it was for Wired LAN but something is amiss, I do not see any responses. If I reboot the device with the wired LAN plugged back in everything is good again. Any gotchas I might be missing?

The Lubuntu is running on my RoBoard RB-110. The wicd (LAN manager in Lubuntu) seem not to switch form wire to wireless automatically when i plug them together on RoBoard and then only remove LAN wired cable. But it works fine after rebooting with "only" VT6655 wireless device.(i has saved the settings in advance)
You can try it again.

hi, kestor

The Lubuntu is running on my RoBoard RB-110. The wicd (LAN manager in Lubuntu) seem not to switch form wire to wireless automatically when i plug them together on RoBoard and then only remove LAN wired cable. But it works fine after rebooting with "only" VT6655 wireless device.(i has saved the settings in advance)
You can try it again.

Firstly I used the kernel proposed in the above web without any exit. Now, I'm trying to compile my own kernel using the 2.6.35.9 Kernel and the same version of the Adeos patch. The Xenomai version is the 2.6. After three hours compiling it, I'm having a lot of compilation errors. It is possible to patch a Kernel starting from the Lubuntu 10.04 as I'm trying? It is necessary use a concrete kernel version to got it?

Firstly I used the kernel proposed in the above web without any exit. Now, I'm trying to compile my own kernel using the 2.6.35.9 Kernel and the same version of the Adeos patch. The Xenomai version is the 2.6. After three hours compiling it, I'm having a lot of compilation errors. It is possible to patch a Kernel starting from the Lubuntu 10.04 as I'm trying? It is necessary use a concrete kernel version to got it?

I totally recommend this distribution for all those who use netbook ike PC’s with very low memory and processors. You can use a fully powered linux system with minimum resources. If already tried XFCE, try this one too. This is much better than that.

I totally recommend this distribution for all those who use netbook ike PC’s with very low memory and processors. You can use a fully powered linux system with minimum resources. If already tried XFCE, try this one too. This is much better than that.