Installing to SDCARD (won't mount at startup)

[spillz]

Tinycore newbie. need some help.

I have my installation to an SD card working, but can't get the card to mount at boot and therefore can't get my tces to load.

Here's what I did:

1. formatted the card as ext3 from ubuntu with mkfs.ext3. the filesystem is owned by root (after installing files I applied some chmods to allow read/write access to all to no avail)

2. used unetbootin to install tinycore 2.1 iso (again from ubuntu)

3. edited syslinux.cfg:

Code: [Select]

default vesamenu.c32
prompt 0
menu title UNetbootin
timeout 100

label unetbootindefault
menu label Default
kernel /ubnkern
append initrd=/ubninit quiet

label ubnentry0
menu label tinycore
kernel /boot/bzImage noswap tce=LABEL=tinycore home=LABEL=tinycore opt=LABEL=tinycore restore=LABEL=tinycore waitusb=10 pause
append initrd=/boot/tinycore.gz quiet
(I've tried variations on this ... what is pause supposed to do?)

4. I have a folder on the SD card called tce with a bunch of tces in it.

With one exception[1], no matter what I do I can't get the SD card to mount at startup, but I can issue mount -L tinycore and the card mounts up just fine. I've tried using the UID and sdb1 instead of LABEL=tinycore to no use.

Can anyone see where I might have gone wrong?

--

[1] The exception is when the device was formatted as FAT32, but that causes other problems (broken symlinks, no permissions etc)

[spillz]

I realize I should have posted to TCB forum. Maybe a mod could move it there

[curaga]

Any errors visible? Anything in dmesg?

Pause will wait for a keypress before starting X.

[spillz]

Pause will wait for a keypress before starting X.

I thought that was what it was supposed to do. But you've helped me solve the problem. I was editing the wrong file: unetbootin apparently calls the config file extlinux.cfg (instead of syslinux.cfg) on EXT filesystems.  

BUT... now I'm stuck trying to get wifi working. I'm trying to compile madwifi. I have tces of linux headers and all the gcc stuff. But I seem to get linux libs in /lib/modules/2.6.29.1-tinycore/ and /lib/modules/2.6.29.1/build

The error is:

Code: [Select]

Makefile.inc:66: ** /lib/modules/2.6.29.1-tinycore/build is missing, please set KERNELPATH. Stop.

[curaga]

Have you tried ath5k yet? It's a driver in the kernel meant to replace madwifi (get the wireless extension).

[spillz]

Have you tried ath5k yet? It's a driver in the kernel meant to replace madwifi (get the wireless extension).

no, but I'm happy to try. can you point me at some instructions?

[Juanito]

BUT... now I'm stuck trying to get wifi working. I'm trying to compile madwifi. I have tces of linux headers and all the gcc stuff. But I seem to get linux libs in /lib/modules/2.6.29.1-tinycore/ and /lib/modules/2.6.29.1/build

The error is:

Code: [Select]

Makefile.inc:66: ** /lib/modules/2.6.29.1-tinycore/build is missing, please set KERNELPATH. Stop.

This error is caused by the symlink /lib/modules/2.6.29.1-tinycore/build being missing or not pointing to your kernel sources.

I guess this can be solved by the linux-headers-2.6.29.1.tce extension or by installing the full kernel, setting it up and setting KERNELPATH

[^thehatsrule^]

Yes, that error is a known problem in the headers extension and will be fixed.  But the better solution would be to get the (newer) ath?k working in any case.  By wireless extensions, it probably means wireless-2.6.29.1-tinycore.tcem and wireless_tools.tcel

[spillz]

ok I think I have the basics of using ath5k down:

Code: [Select]

modprobe ath5k
ifconfig wlan0 up
iwconfig wlan0 essid "<NetName>"
iwconfig wlan0 key s"<Pashphrase>"
(from memory)

BUT, I still need to figure out how to make this persistent AND how to set up wpa_supplicant (i.e. config files etc) so I can use WPA-PSK. If any one has pointers on these, I'll write up the wiki entry...

btw, I should have mentioned I'm do all of this on a eee pc (1000 HA)

[roberts]

This is not way off the topic's title of SDCARD.
It is best to start a new topic so that other can easily find help.

However, several eeepc TC users are using ath5k and WPA. Use 'search' button.
Instructions for wpa are in the .info file of said extension.

Use /opt/bootlocal.sh for your extra wireless commands.
All commands in /opt/bootlocal.sh run as root, not need to sudo.
You should not need to modprobe ath5k.

[spillz]

This is not way off the topic's title of SDCARD.
It is best to start a new topic so that other can easily find help.

sorry -- didn't realize that was the policy. if an admin wants to move everything from post #5 down to a new thread with a suitable name, say "getting wifi working", that's fine with me. If not I can try to summarize in a new post and then lead with my remaining questions. I'll assume the latter if the posts don't get moved in the next 24 hours.

However, several eeepc TC users are using ath5k and WPA. Use 'search' button.

searching for "ath5k wpa" turned up two results: this thread and one other that wasn't helpful. I have been referring to this one: http://forum.tinycorelinux.net/index.php?topic=738.0 which has helped

Instructions for wpa are in the .info file of said extension.

didn't know that. thanks.

Use /opt/bootlocal.sh for your extra wireless commands.
All commands in /opt/bootlocal.sh run as root, not need to sudo.

done that. I'm still trying to figure out the timings. does wpa_supplicant need to run well before the udhcpc call? is there not some way to get wpa_supplicant to make the udhcp call when it finds a suitable connection? (I may not understand what I'm asking here )

You should not need to modprobe ath5k.

that makes things easier

btw, robert I read your very interesting distro watch interview and am very enthusiastic about this distro. I think you are really onto something. I hope you can make wifi a more out of the box experience in future editions. Its tough selling a web dependant distro if users have to spend hours figuring out wifi.

[roberts]

If I recall there can be some challenges with the timings of wpa_supplicant and udhcpc.
I think I ended up placing udhcpc in .profile, but will have to check. I no longer have easy access to this machine (requires a visit on site). I thought I had posted the setup in the forums, but cannot find it now.
I will take you up on your offer to do a wiki howto.