Tiny Core Linux
Tiny Core Base => Micro Core => Topic started by: mattrix on March 25, 2011, 08:48:27 PM
-
I have just setup microcore 3.5.1, thank you for a bloat free distro.
My network card isn't detected (no entry in ifconfig, only lo).
How can I get it working?
It is an EISA P&P card based on a realtek 8019, & is novell compatible (NE series).
It has been suggested I may have to get files from another distro that does support it.
If I have to do this, what files do I need to get and how do I install them?
How do I make this persistent?
I'm a little confused about how persistence works. I assume its using some sort of unionfs.
But I'm not sure at what stage everything is done.
EG, If I wanted to have a directory /boot and mount my boot partition on it, would there be any point in modifying fstab, or would fstab have been processed before mydata.tgz is loaded? What would I have to put in filetool.lst to just create the /boot directory?
Similarly from what I can see the initrd is never removed from RAM (how big does it expand to?), so installing drivers would be done early in the process, before mydata.tgz has the chance to overlay the network driver files?
It appears mydata.tgz is loaded after initrd scripts have done all there stuff and just before startlocal.sh is executed and after this tce-load is used to load the "on boot" .tcz's.
thankyou for any suggestions
-
Hi mattrix
What does dmesg have to say about your card? If you decide to post your dmesg output please
attach it as a file.
-
There is no overlay filesystem involved whatsoever.
Onboot extensions get mounted before mydata.gz is extracted.
Initial usage of tmpfs mounted over / is approxymately 17MB.
You could try to symlink an automatically created mount dir to a path of your convenience, e.g.
sudo ln -s /mnt/hda1 /mnt/boot
-
Hey rich,
I am no dmesg expert. but heres what I saw,
the card is seen in P&PBIOS setup, but I cant see any resources allocated to it.
Let me know if you want the whole output.
-
Hi mattrix
Attach a copy and I'll take a look.
-
That was easier said than done, (for a noob)
now if I can attach it, here it is.
-
Have you made this card successfully work under any other Linux system?
If yes, how recent?
-
Yes, I tried puppy recently. and it works with dos.
There is no overlay filesystem involved whatsoever.
OK, I'm MORE than a little confused.
I guess mydata can just get unpacked into the root file structure, overwriting anything thats already there.
But how do extensions work (especially if mounted)
-
You should really read all documentation, starting from main site.
Hint: there is a nice graphic depiction of system architecture ;)
-
Hi mattrix
First try ifconfig eth0 192.168.1.47 and see if the card comes up.
If that's an 8 bit card you may have a problem, but try sudo modprobe ne.ko
You might also try playing with the bootcode
netdev= [NET] Network devices parameters
Format: <irq>,<io>,<mem_start>,<mem_end>,<name>
Note that mem_start is often overloaded to mean
something different and driver-specific.
This usage is only documented in each driver source
file if at all.
-
You should feel lucky, many people are desperate to get an ethernet card work under DOS these days... ;)
You could check all parameters related to card used under Puppy, particularly driver.
-
Card should be supported by ne driver in TC base.
For card specific instructions see:
http://www.faqs.org/docs/ethernet/Ethernet-HOWTO-4.html
-
First try ifconfig eth0 192.168.1.47 and see if the card comes up.
under the condition that router would be on subnet 192.168.1.0, otherwise has to be adapted accordingly ;)
-
He knew enough to use ifconfig so I gave him the benefit of the doubt.
-
He knew enough to use ifconfig so I gave him the benefit of the doubt.
Thanks for that.
I know my way around ms systems, but specific linux is beyond me.
ifconfig eth0 = no such device
modprobe = device found and module installed
ifconfig eth0 = there, but didn't get an address from dhcp server
-
That's ok, but having in mind future users reading posts is a good idea ;)
(And I have observed more than once users failing for taking something too literally)
-
ifconfig eth0 = no such device
modprobe = device found and module installed
ifconfig eth0 = there, but didn't get an address from dhcp server
...as expected
udhcpc -i eth0
-
Hi mattrix
OK, that's good news, it took the driver. Click on the control panel icon and use the network setup
tool to disable DHCP and assign an IP address.
-
Thanks muchly for the help,
more than once users failing for taking something too literally)
whats a noob to do? its the noob's condition
I've seen command sequences that just make no sense to me,
but noone else sees anything wrong with them
udhcpc -i eth0
worked a treat - thankyou
Click on the control panel icon and use the network setup
a bit difficult in micro core
Now how do I make all this persitent? Does bootlocal.sh execute after mydata is restored? More to the point is it run as root?
ps wheres the pretty picture, I thought I read the wiki from front to back, including the page on investing in gold!
EDIT found it, not in the wiki, http://www.tinycorelinux.com/architecture.html
pps how do I run e2fsck on the same partition as microcore, e2fsck tells me to umount it first?
-
Now how do I make all this persitent? Does bootlocal.sh execute after mydata is restored? More to the point is it run as root?
Add the modprobe and udhcp to bootlocal.sh. Yes. Yes.
ps wheres the pretty picture, I thought I read the wiki from front to back, including the page on investing in gold!
vga=xxx
pps how do I run e2fsck on the same partition as microcore, e2fsck tells me to umount it first?
Boot without mounting it "base norestore" and then you can operate on the HD.
-
Wondering why you would use MC while concurrently asking so many most basic questions about the system...
I would highly recommend to use TC and included tools to explore and become a bit more familiar with the system and it's basic architecture, under the condition that you have at least 48-64MB of RAM.
-
Wondering why you would use MC while concurrently asking so many most basic questions
sorry for the stupid questions. :-[
Tiny core seems somewhat different, in the way it does things, than other unix's. And its a bit hard to separate whats tiny core and whats linux.
I'm not unfamiliar with computers, pre se, just with how linux does things.
The object is to learn about linux, the command line seemed to be a good place to start with hardware that I've discovered is, from a linux point of view, very minimal. (besides my mouse is not working properly ;))
Admittedly tiny core seems better documented than microcore for the distro specific stuff.
If I really wanted to do "something" with this hardware, microsoft seems to squeeze more functionality from it, (running win98se and off97). ( I know old)
But maybe thats just because I'm unfamiliar with linux.
Any way thanks so much for your help.
-
Click on the control panel icon and use the network setup
a bit difficult in micro core
Doh! And it was the very first thing he mentioned in his first post.
-
Yes but...
Running microcore does not necessarily mean running without a GUI equivalent to tinycore, i.e. core elements.
You can see that in Reply #2 also I gave the approximate size of mem usage of tinycore.
And as hinted already, difficult to imagine that someone who has a lot of most basic questions would not use a GUI to get familiar with the system first...
-
... difficult to imagine that someone who has a lot of most basic questions would not use a GUI to get familiar with the system first...
Its all about levels of abstraction.
A good GUI is designed to hide the system from you.
Ask almost any (old) windows user about their VMM32.VXD and they'll look at you blank, but ask a dos user about their config.sys and at least they'll know what your talking about.
As you can tell from the 16bit network card, this isn't the most recent hardware.
Besides I thought it would fit better with my previous Unix experience.
Yes but...
Running microcore does not necessarily mean running without a GUI equivalent to tinycore, i.e. core elements.
Now that I've got networking, after I work out what all the tce-* files are for, I will install the GUI components to see all the info about mounted filesystems.
... most basic questions ...
I've got questions that are way more basic than this.
Anyway, did I thank you both for helping me.
-
A good GUI is designed to hide the system from you.
With TC, the particular GUI tool may become the initial motivation to explore their backends, for those who are interested ;)
-
I found it a bit more difficult to find and read the source of a gui tool. cat `which tce-load` is very simple.
All extensions are mounted to /tmp/tcloop/ and then linked into the root filesystem.
-
with 'cp -ais' for accuracy
-
OT: Heh, I didn't know cp was able to do this. In my view it shouldn't.
The use of yes y in order to answer the prompts is also indicating the problem I have with modern cp.
-
The use of yes y in order to answer the prompts is also indicating the problem I have with modern cp.
cat ~/.ashrc
-
You're right, this one is not really a problem with cp itself. I posted a new thread to grumble on. :)
-
"yes n" in tce-load is to avoid overwriting, which can't be done with cp outside of the -i option.
-
fconfig eth0 = no such device
modprobe = device found and module installed
ifconfig eth0 = there, but didn't get an address from dhcp server
You'll need to execute "/etc/init.d/dhcp.sh" as root to start the dhcp client after your last step.