General TC > Tiny Core Netbooks
HOWTO: Install and tweak Tiny Core for Dell mini-9
Juanito:
--- Quote from: linuxnovo on December 07, 2010, 07:23:36 AM ---Jed, nano as text editors, commandline no incon in tray.
midori and arora gui browsers and an icon each in the tray panel
--- End quote ---
I don't use jed or nano, but I'd guess that the extension does not include an icon
--- Quote ---at command line (terminal) we now try the extentions
nano just works......no problem.....good so far
--- End quote ---
Which version of tc are you using? The reason I ask is that nano has the ncurses extension as a dependency in the most recent versions of tc and, since you seem to be missing the dependencies of your other extensions, I'm surprised you have this one.
--- Quote ---however, the command line gives us the following error message:
error while loading shared libraries libslang.so.2 cannot open shared object file no such file or directory
--- End quote ---
This and the other errors mean that the dependency extensions for jed, midori and aurora were not loaded. In this case the slang extension is not loaded.
I'm puzzled as to why the jed extension loaded, I'm not at a tc machine at the moment to double-check, but normally as long as jed.tcz.dep is present and slang.tcz is not present, then the jed extension should not load.
Do you have the files jed.tcz.dep and slang.tcz in your /tce folder in your hd install? Did you download and load jed and the other extensions with the app browser?
--- Quote ---Now, with a fresh cd boot. all of these work, somehow the hard disk install is not placing software in the
right place.
--- End quote ---
This works because the app browser is downloading and loading the required dependencies for jed, aurora and midori.
linuxnovo:
quite a little morning here. finally got this system working!
The key was to change the kernel boot line:
thus
kernel /tiny/bzImage quiet tce=sda1 (change to 'hda1') and delete completely nodhcp
see earlier posts for the menu.lst lines
thats it!
will update as I HAVE THE TIME
linuxnovo:
The TC system is now functional. Everything, relates to the /boot/grub/menu.lst. The information I was
using required sda1 where the TC was looking for hda1. Really, that simple. Here, is a copy of what is
working for me:
title Tiny Core Linux
root (hd0,0)
kernel /tiny/bzImage quiet norestore tce=hda1 home=hda1 opt=hda1
initrd /tiny/tinycore.gz
compare this to the suggestion from the article:
title Tiny Core Linux
root (0x80,0)
kernel /tiny/bzImage quiet tce=sda1 home=sdb1 opt=sdb1 nodhcp
initrd /tiny/tinycore.gz
Note: I have included the boot option "norestore" because of the speed of bootup. I am just spending
a moment or two to put in my preferences.
Everything works, except for the wireless. I am trying to get the wicd working. It is fine with wired ethernet, but not with wireless.
Thanks for the help and concern all. I am on alot of linux forums and I really think this is the most friendly. Thanks again!
linuxnovo:
Lets look at the whole situation now: I have a dell mini-9 with an aged Linux Mint 7, Gloria, with, essentially an embedded TC, working. The Mint will go out on the net both wired and wireless, but this is no get thing when, of all the major distros, the Mint people, more than any other, try to get their stuff working out of the box. Just load in Ubuntu and Mint as a comparison, and you will see that Mint has everything that Ubuntu has and more.
On the TC side, as you can see from the above, I have a functioning system with the key factor of persistence. It works well with wired a wired connection and runs sweet enough for the time being, with like the beautiful girl with a boil, has a crying defect: no wifi. So let's review where we are:
I have downloaded and installed wicd.tzc . You are required to start wicd with a command line: 'sudo wicd-start'. I have placed this line in bootlocal.sh so that sh with execute this line on startup. All this seems fine. I now follow the instructions from TC wiki:
Easy Way: wicd
"If you want to set up wifi with minimum of fuss, just install wicd package (and its dependencies) from the package repository. You will then be able to setup your connection in a user-friendly GUI. See http://wicd.sourceforge.net/ (external link) for detailed information about wicd.
After installing "wicd.tcz" execute the following command to start the wicd daemon:
sudo wicd-start
Then activate the GUI interface using the application menu.
If you have problems getting wicd to see your wifi card, you may have driver issues. Atheros users can see this Network Setup - Atheros Wireless Cards, but note that tinycore 2.0 and later ships with ath5k and ath9k open source drivers that should handle most Atheros cards."
TIP: For a system that doesn't have wired access, you may find it easier to download the wicd package files and its dependencies first and store them some place convenient. You can then load them into tinycore using the tce-load command.
Now computers are funny things, they are complex, quite strong really, but they fail us because of big things and very little things. So it is very important not to get involved in little things before you look to big things. I made a big mistake one time trying to get my new laptop wired access to the net. I ventured, foolishly into networking at the command line, a complex and scary place without thinking if my connection was good to begin with. There are two providers in my area: Time-Warner and Frontier. I struggled for days in the Mint forum with a kind person from Sweden. As I say, the inner world of computers, is complex and scary and you are provided information in the bundles starting with dmesg. There was a world of pain for both of us. Well, one night I went over to a friend's who had Frontier, instead of Time-Warner, and Deus ex machina, both of us were pulled out of the world of pain.
So I must always check with the Mint that I have a strong wifi connection present, before I look into the particulars. Now, I go as instructed to my applications and click on WicdNetwork Manager. It comes up Wired Network checked as default with a real nice ethernet cable icon. It says: No wireless networks found. I click on connect: it is looking and trying to connect to a wired connection.
(as per above, the Mint Wicd Manager says that there three wireless networks available one unsecured and I connect to it. You will not fool me again!)
Well, on the TC side, we have no wireless networks found. So lets go down:
One article suggests this starting point:
"iwconfig
Your output should look like:
lo no wireless extensions.
eth0 no wireless extensions.
sit0 no wireless extensions.
wlan0 unassociated ESSID:off/any
Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00
Bit Rate=0 kb/s Tx-Power:off
Retry:on RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
If all devices listed say "no wireless extensions." then your wireless card is not configured."
I do this in TC:
tc@box: iwconfig
lo no wireless extensions
dummy0 no wireless extensions
eth0 no wireless extensions
it seems that my wireless card is NOT CONFIGURED.
Now, on the Mint side we issue the same command:
lo no wireless extensions
eth0 no wireless extensions
eth1 IEEE 802.11 Nickname:" "
Access Point: Not-Associated
Link Quality: 5 Signal level:0 Noise level:180
Rx invalid nwid:0 invalid crypt:0 invalid misc:0
pan0 no wireless extensions
Oh, the benefit of running parallel systems!
Our Guru goes on:
"Alternativly, the device may be disabled - you could try
sudo ifconfig wlan0 up
you may also try to wake-up the interface using the keyboard command (Dell)
Then try iwconfig again to see if the device is now recognised. "
when I issue the command above:
sudo ifconfig wlan0 up
I get SIOCGIFFLAGS: no such device
iwconfig gives the same as above.
I do toggle "fn 2" because I have a Dell with no result.
Well, we have a direction now......
tinypoodle:
--- Quote from: linuxnovo on December 07, 2010, 07:16:26 PM ---The TC system is now functional. Everything, relates to the /boot/grub/menu.lst. The information I was
using required sda1 where the TC was looking for hda1. Really, that simple. Here, is a copy of what is
working for me:
title Tiny Core Linux
root (hd0,0)
kernel /tiny/bzImage quiet norestore tce=hda1 home=hda1 opt=hda1
initrd /tiny/tinycore.gz
compare this to the suggestion from the article:
title Tiny Core Linux
root (0x80,0)
kernel /tiny/bzImage quiet tce=sda1 home=sdb1 opt=sdb1 nodhcp
initrd /tiny/tinycore.gz
--- End quote ---
What article exactly are you refering to?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version