next »

[anna]

Changing the font size, I fear, will be more difficult to figure out

I haven't tried microcore or tinycore, but this is what I do to make almost everything in icewm on Debian big enough to read for my tired old eyes.  Maybe it'll work for you.

Create or edit this file:

~/.gtkrc-2.0

Code:

# Sets the font used by all gtk applications.
gtk-font-name = "Verdana 18"

Of course, choose whatever font or font size you like in that file.  This is just an example of what I use.

[rbacher]

The .gtkrc-2.0 file didn't change the font size but it's ok because the problem of small font size was with fluxbox and I'm using jwm at this time and it has several configuration files in ~/ such as .jwmrc which allow you to set the fonts, and when you edit those configuration files in jwm they are static in microcore, not dynamically reset at each reboot as happened with fluxbox.  For what it's worth I like jwm for the setup I am running on the XO

[Terminator3000]

Unfortunately I wasn't able to get any of those to work.   
All of them, including various permutations resulted in the following error line:

Code:

root@box:~# Could not init font path element /usr/lib/X11/fonts/100dpi/, removing from list!

I did try different "-dpi" of 200, 150, 100 and resolutions of 1200x900, 800x600, and 640x480, all with exactly the same output results.

[rbacher]

I have installed a bare bones microcore with jwm and it works great except for one thing -- I cannot connect to wifi that requires a password.  I am able to connect to an open access point with $ sudo iwconfig eth0 essid <name> so that much is working fine. But I need to connect to WPA-PSK wifi.  I tried to download wpa_supplicant following the instructions at http://wiki.tinycorelinux.com/Setting+up+Wifi.  But when I run $ tce-load -wi wpa_supplicant.tcz (or any of the other wireless files) I get an error message that says "No such file or directory." The file it is looking for is
"wireless-2.6.31_xo1-20100728.1841.1.olpc.a0a0edb7d8cbadb.tcz." Can anyone help? Thanks

[rbacher]

I was just able to download two of the three files: wireless_tools.tcz and wireless-2.6.33.3-tinycore.tcz.  But attempts to download wpa_supplicant produce the same error message. Any help is appreciated.

[mavrothal]

Is some time that I did not use TC but if I remember corrcetly to "fool" TC to (down)load kernel-specific extensions while using another kernel change /usr/bin/tce-load line 15, /user/bin/tce-audt line 6 and /usr/bin/tce-update line 7 from KERNELVER=$(uname -r) to KERNELVER="2.6.33.3". TC appbrowser infrastructure is in constant development but hopefully this still works
Keep in mind that "fooled" extensions may not work with the OLPC kernel or even worse, messup your system, but you can give it a try.
Ideally you should get the source of the kernel-specific tcz from http..../tinycorelinux/3.x/tcz/src/ and recompile against the OLPC kernel.

Happy New Year

[rbacher]

I think I figured this out. The root of the problem was the wireless_tools dep file. It had wireless_KERNEL.tcz in it. When I ran tce-load -wi wireless_tools.tcz, the process jammed up when it tried to find, but couldn't find, a file with the (rather lengthy) name
xo1-20100728.1841.1.olpc.a0a0edb7d8cbadb.tcz. That name
xo1-20100728.1841.1.olpca0a0edb7d8cbadb turns out to be the kernel name. I ran uname -r and that's the result I got. So now (I think) I understand the cause. The solution (or one solution -- I did not try mavrothal's idea in the previous post) was to simply delete the problem line from the wireless dep file (there's only one line in the dep file so you end up with nothing in the file). Then I was able to tce-load -wi wireless_tools.tcz, and after that was able to likewise tce-load -wi wpa_supplicant.

The next surprise, though, was that wpa_supplicant wouldn't work per the instructions at http://wiki.tinycorelinux.com/Setting+up+Wifi. The wpa_passphrase worked fine, and I wrote the configure.conf file with the long psk number I got from passphrase, but wpa_supplicant didn't run right. I got several error messages.

I gave up on trying to connect from the command line and installed wicd. Of course what I learned about getting wireless_tools and wpa_supplicant installed on an XO was necessary, as it turns out, since they are both needed for wicd. My boot time now, with microcore + chromium browser + wicd is still under 40 sec, so I think I got what I need at this point.

[rbacher]

Got the boot time (from cold boot) down to 25 sec. This includes Xfbdev and a window manager (jwm) but I removed Chromium and Wicd from the OnBoot list. I wrote small script files, which I can run from the menu, to install Chromium and/or Wicd, as needed. Boot time with Chromium but w/o Wicd is 34 sec. My wifi at home is open so I don't need Wicd most of the time. My recent activity with the XO was sparked because I realized that I hadn't set it up to work with wifi that requires a password.

[Rao]

I think I figured this out. The root of the problem was the wireless_tools dep file. It had wireless_KERNEL.tcz in it. When I ran tce-load -wi wireless_tools.tcz, the process jammed up when it tried to find, but couldn't find, a file with the (rather lengthy) name
xo1-20100728.1841.1.olpc.a0a0edb7d8cbadb.tcz. That name
xo1-20100728.1841.1.olpca0a0edb7d8cbadb turns out to be the kernel name. I ran uname -r and that's the result I got. So now (I think) I understand the cause. The solution (or one solution -- I did not try mavrothal's idea in the previous post) was to simply delete the problem line from the wireless dep file (there's only one line in the dep file so you end up with nothing in the file). Then I was able to tce-load -wi wireless_tools.tcz, and after that was able to likewise tce-load -wi wpa_supplicant.

The next surprise, though, was that wpa_supplicant wouldn't work per the instructions at http://wiki.tinycorelinux.com/Setting+up+Wifi. The wpa_passphrase worked fine, and I wrote the configure.conf file with the long psk number I got from passphrase, but wpa_supplicant didn't run right. I got several error messages.

I gave up on trying to connect from the command line and installed wicd. Of course what I learned about getting wireless_tools and wpa_supplicant installed on an XO was necessary, as it turns out, since they are both needed for wicd. My boot time now, with microcore + chromium browser + wicd is still under 40 sec, so I think I got what I need at this point.

Hi,
I like the idea of Tiny/Micro core linux for XO-1 (I think that is all the XO-1 is capable of).  But I have a secured WPA wi-fi network at home.  So, I am prepared to do the work needed to get the wi-fi software for wpa to work if somebody can tell me what I should try/experiment.

What I was able to do so far is the following on  Teapot's Ubuntu.
First I did,
kill -15 all the networking processes (in Teapot's running Ubuntu).
So, XO was no more connected to my secured wpa network.
Then I followed the instructions at http://linux.icydog.net/wpa.php running the commands in a terminal window and was able to connect to my home wpa network.
I assume something very similar should be possible to do in TIny/Micro core linux running on XO-1.   What is needed are the three programs  wpa_supplicant,  the driver wext (where does it reside) and the dhclient.  These are all the programs I used  in Teapot's Ubuntu to connect to my secured wpa network. I think the combined size of these three programs is not more 2-3 MB.

I wonder if I can compile the software on my Desktop Ubuntu and use it in Tiny/Micro core linux on XO.
Thanks.
Rao

[Rao]

I think I figured this out. The root of the problem was the wireless_tools dep file. It had wireless_KERNEL.tcz in it. When I ran tce-load -wi wireless_tools.tcz, the process jammed up when it tried to find, but couldn't find, a file with the (rather lengthy) name
xo1-20100728.1841.1.olpc.a0a0edb7d8cbadb.tcz. That name
xo1-20100728.1841.1.olpca0a0edb7d8cbadb turns out to be the kernel name. I ran uname -r and that's the result I got. So now (I think) I understand the cause. The solution (or one solution -- I did not try mavrothal's idea in the previous post) was to simply delete the problem line from the wireless dep file (there's only one line in the dep file so you end up with nothing in the file). Then I was able to tce-load -wi wireless_tools.tcz, and after that was able to likewise tce-load -wi wpa_supplicant.

The next surprise, though, was that wpa_supplicant wouldn't work per the instructions at http://wiki.tinycorelinux.com/Setting+up+Wifi. The wpa_passphrase worked fine, and I wrote the configure.conf file with the long psk number I got from passphrase, but wpa_supplicant didn't run right. I got several error messages.

I gave up on trying to connect from the command line and installed wicd. Of course what I learned about getting wireless_tools and wpa_supplicant installed on an XO was necessary, as it turns out, since they are both needed for wicd. My boot time now, with microcore + chromium browser + wicd is still under 40 sec, so I think I got what I need at this point.

Hi,
I like the idea of Tiny/Micro core linux for XO-1 (I think that is all the XO-1 is capable of).  But I have a secured WPA wi-fi network at home.  So, I am prepared to do the work needed to get the wi-fi software for wpa to work if somebody can tell me what I should try/experiment.

What I was able to do so far is the following on  Teapot's Ubuntu.
First I did,
kill -15 all the networking processes (in Teapot's running Ubuntu).
So, XO was no more connected to my secured wpa network.
Then I followed the instructions at http://linux.icydog.net/wpa.php running the commands in a terminal window and was able to connect to my home wpa network.
I assume something very similar should be possible to do in TIny/Micro core linux running on XO-1.   What is needed are the three programs  wpa_supplicant,  the driver wext (where does it reside) and the dhclient.  These are all the programs I used  in Teapot's Ubuntu to connect to my secured wpa network. I think the combined size of these three programs is not more 2-3 MB.

I wonder if I can compile the software on my Desktop Ubuntu and use it in Tiny/Micro core linux on XO.
Thanks.
Rao

I just want to update the above post even though I haven't gotten any response.

I did manage to get wpa_supplicant to work my XO-1 with  secured wpa wi-fi.  It wasn't that difficult.  The difficulty was mainly in figuring out the different packages in Tiny Core are and how to use them.

[eden]

Hi Rao,

I'm glad you got it to work.  I like Tinycore and Microcore on the XO-1.  Would you mind posting what packages you used to get it to work with WPA?

[Rao]

Hi Rao,

I'm glad you got it to work.  I like Tinycore and Microcore on the XO-1.  Would you mind posting what packages you used to get it to work with WPA?

Hi Eden,

I just saw your post.  I think that something is broken in the forum software.  I thought we are supposed to get an email when something is posted, particularly when the post quotes a previous post.  So, I hope you get an email about this post of mine.

Anyway,  all I did was to open Appbrowser, click on connect and select (after the applications are displayed) wpa_supplicant and next select "install" at the bottom left.  That downloaded all the required packages and installed wpa_supplicant including the wpa_passphrase which is used to create the config file required by wpa_supplicant.
You can find out how to invoke wpa_supplicant by typing in the terminal
wpa_supplicant --help.

You can manually invoke wpa_supplicant from  a terminal or from inside bootlocal.sh (in /opt, I think).

Now, to initially connect to the Tinycore website to install wpa_supplicant, you can go to STARBUCKS!
If you need more details, please post again.

[mavrothal]

Rao,
which version of Tinicore are you using (2, 3, 4)?
Is it your own build?
Is it available?
If from elsewhere, where?

PS: The forum will not notify you for new posts in a thread just because you posted in it. You have to tell it.

[Rao]

Rao,
which version of Tinicore are you using (2, 3, 4)?
Is it your own build?
Is it available?
If from elsewhere, where?

PS: The forum will not notify you for new posts in a thread just because you posted in it. You have to tell it.

Hi,

I ran the command 'version' and got the output "tinycore_2.10."  I don't know if that is the way to find out or not.

In any case I downloaded the bz2 (indicated in one of your posts) file (md5sum:e9c38094f4ad97704b49932a22afa17a) a 2-3 weeks ago.  So, it is not the latest OLPC/XO version of Tinycore, I assume.

I hope that answers your question.

In the past, I believe I had received an email whenever somebody quoted my post in his/her post.  So, that was the basis of my assuming about notification.

Anyway, how would I tell/request to be notified?

Also, how can I uninstall an extension that I don't want anymore?

Rao

[mavrothal]

In any case I downloaded the bz2 (indicated in one of your posts) file (md5sum:e9c38094f4ad97704b49932a22afa17a) a 2-3 weeks ago.  So, it is not the latest OLPC/XO version of Tinycore, I assume.

Wow, I did not even know that 2.x extensions are still available.
I did not make any other after tc-xo_02, but you can make your own if you are good with the command line. Look here

Anyway, how would I tell/request to be notified?.

Press the Notify tab (next to the Reply one at the top or bottom)

Also, how can I uninstall an extension that I don't want anymore?

From AppsAudit>OnBoot>Maintenance
Like this>> <a href="http://www.youtube.com/v/n0-VJPu7xxU" target="_blank">http://www.youtube.com/v/n0-VJPu7xxU</a>