TCL as micro web server ~ n00b starts here

[Rich]

Hi cpcnw

I used 'showapps noswap waitusb=5 .....

Did you actually see the names of your apps being listed when it booted? If not, then 5 seconds was not long
enough, try 10. I think this would also account for no disks being found.

It boots ok with one error I cant catch ....

Enter:

Code: [Select]

dmesg | lessYou can use the page and arrow keys to navigate and check for errors/warnings.

[cpcnw]

Thanks Rich - but if no discs are found how is it booting? Or does the kernel not need controller support for the boot process?

Odd thing is about all this, when using my ext usb cd to load tc it doesnt see the cf 'disc' either...

Lastly for life of me cant get a pipe on my keyboard. I know us keymap is default but this is a compact and its getting it wrong ... I get chevrons where pipe should be ...

[Rich]

Hi cpcnw
If I remember correctly, basically, the boot loader finds the disk and loads the kernel into RAM. Then the kernel takes
over and scans the hardware asynchronously. If the process that checks for USB drives hasn't populated the /dev
directory when the kernel is ready for it, the kernel just moves on. The kernel is not aware of the boot loader or which
disk it is loaded from. That's the reason for waitusb=.

Odd thing is about all this, when using my ext usb cd to load tc it doesnt see the cf 'disc' either...

When you get to the screen with the F2, F3, F4  message, enter:

Code: [Select]

tc waitusb=10and see if your cf disk shows up then.
Sorry, can't help with the keyboard.
By the way, when you boot from the CD, is that listed? Enter:

Code: [Select]

ls /mntfor a list of available drives.

[cpcnw]

Cheers Rich - the way I see this is that the tc kernel is not able to support the disc controller whereas puppy does. Im going to boot puppy via cd again and try and get a copy of the dmesg to look at and see whats going on there. Think someone else suggested that on one of my other threads - which is the same issue actually.

[gerald_clark]

You should not double post.  It is a waste of everybody's time and just confuses the issue.

[cpcnw]

Double post? This is an ongoing issue - revisited after a long time because there was no resolution. One thing has led to another. Im still working through that. If a new post was created every time a new issue came up that was the result of asking a question there would literally be millions of posts.

[gerald_clark]

You are the one that said you have another thread which is the same issue, not me.

[cpcnw]

Excuse me for not remembering everything I posted 4 months ago and not forseeing that this thread may actually end up about as far as I got last time.

[Rich]

OK, let's not have this escalate into anything.

@gerald_clark: Point made.

@cpcnw: Point taken.

Now let's move on please.

[tinypoodle]

Excuse me for not remembering everything I posted 4 months ago and not forseeing that this thread may actually end up about as far as I got last time.

Easy:
http://forum.tinycorelinux.net/index.php?action=profile;area=showposts;u=12567

[tinypoodle]

If the process that checks for USB drives hasn't populated the /dev
directory when the kernel is ready for it, the kernel just moves on.

It was no different back when /dev used to be purely static.

[Zendrael]

Hi!

In the CF, do you have extlinux or grub? (or other...?)

After finding the device you can, you can edit the bootline in the config file of your bootload to tell Core which device has persistent data.