Tiny Core Linux

[bmarkus]

Cloudcentric@

Thanks for trying. ALSA works fine with the onboard chip. As with others, HDMI sound may require hdmi_drive=2 in the boot coonfig.txt file if TV set recognise Pi as DVI device instead of HDMI.

Wireless is really interesting, let me know your findings.

Bela

[Cloudcentric]

Cloudcentric@

Thanks for trying. ALSA works fine with the onboard chip. As with others, HDMI sound may require hdmi_drive=2 in the boot coonfig.txt file if TV set recognise Pi as DVI device instead of HDMI.

Wireless is really interesting, let me know your findings.

Bela

http://tinycorearm.blogspot.co.uk

I have started another blog, but at this time I do not have a wireless router as mine demised and awaiting another one to be delivered.

emilFM2 File Manager, which is in the X86-32 packages, would be welcome.

......looking forward to more adventures with PiCore

[truehl]

I've got Tiny Core Linux running on the Pi, great. I also got dropbear ssh server running but I have issues with that:
1. how can I start dropbear at system start?
2. how an I login from a terminal (Putty) as root? root will not work, so I created an other user.
3. I can login with this user, but I can't get su. I'm not eable to add a named user to the sudoers!

Any one an idea?

[Cloudcentric]

I've got Tiny Core Linux running on the Pi, great. I also got dropbear ssh server running but I have issues with that:
1. how can I start dropbear at system start?
2. how an I login from a terminal (Putty) as root? root will not work, so I created an other user.
3. I can login with this user, but I can't get su. I'm not eable to add a named user to the sudoers!

Any one an idea?

What version of PiCore Beta are you using 4.7.3 ??

[truehl]

I've got Tiny Core Linux running on the Pi, great. I also got dropbear ssh server running but I have issues with that:
1. how can I start dropbear at system start?
2. how an I login from a terminal (Putty) as root? root will not work, so I created an other user.
3. I can login with this user, but I can't get su. I'm not eable to add a named user to the sudoers!

Any one an idea?

I think the latest, but not sure!

What version of PiCore Beta are you using 4.7.3 ??

[Cloudcentric]

http://www.tinycorelinux.net/4.x/armv6

[truehl]

http://www.tinycorelinux.net/4.x/armv6

yes 4.7.3

[Cloudcentric]

Cloudcentric@

Thanks for trying. ALSA works fine with the onboard chip. As with others, HDMI sound may require hdmi_drive=2 in the boot coonfig.txt file if TV set recognise Pi as DVI device instead of HDMI.

Wireless is really interesting, let me know your findings.

Bela

I have installed the updated Midnight Commander and it is a welcome addition, still awaiting my NEW 3G Wired/Wireless Router though!

[Cloudcentric]

I've got Tiny Core Linux running on the Pi, great. I also got dropbear ssh server running but I have issues with that:
1. how can I start dropbear at system start?
2. how an I login from a terminal (Putty) as root? root will not work, so I created an other user.
3. I can login with this user, but I can't get su. I'm not eable to add a named user to the sudoers!

Any one an idea?

Dropbear from the TCE readme

"Use /usr/local/etc/init.d/dropbear start|stop|retart|status to manage service as root"

Have you tried sudo su ?

[truehl]

I've got Tiny Core Linux running on the Pi, great. I also got dropbear ssh server running but I have issues with that:
1. how can I start dropbear at system start?
2. how an I login from a terminal (Putty) as root? root will not work, so I created an other user.
3. I can login with this user, but I can't get su. I'm not eable to add a named user to the sudoers!

Any one an idea?

Dropbear from the TCE readme

"Use /usr/local/etc/init.d/dropbear start|stop|retart|status to manage service as root"

Have you tried sudo su ?

Every thing is running now, except that dropbear will not start at system start! Any idea?

[Cloudcentric]

Every thing is running now, except that dropbear will not start at system start! Any idea?

When you installed dropbear.tcz from the Appbrowser did you choose the 'On Boot' option ?

[truehl]

Every thing is running now, except that dropbear will not start at system start! Any idea?

When you installed dropbear.tcz from the Appbrowser did you choose the 'On Boot' option ?

I can only see these options:

Code: Select all

A)bout I)nstall O)nDemand D)epends T)ree F)iles siZ)e L)ist S)earch P)rovides K)eywords or Q)uit:

[Cloudcentric]

I was presuming you have installed the FLWM Desktop Environment as per the readme on the download page for 4.7.3 PiCore and then used the Appbrowser to install additional software !

[truehl]

I was presuming you have installed the FLWM Desktop Environment as per the readme on the download page for 4.7.3 PiCore and then used the Appbrowser to install additional software !

No, I use the version without desktop. But it should be possible to get it also started automatically with this version, isn't it?

[Cloudcentric]

Cloudcentric@

Wireless is really interesting, let me know your findings.

Bela

Yes now have a Wireless N 150Mbps Wireless Router and the Security is set to WPA/WPA2 - TKIP/AES, by default

PiCore launches the Command Line "Tiny WiFi Scanning Tool" from the tool bar icon and finds all nearby connections without issue with the correct encryption listed.

Unfortunately it will not except my credentials and have tried various router settings:

WPA - TKIP

54G only WPA - TKIP

54G only WPA - AES


I have reset my router to WPA/WPA2 Automatic and booted up Raspbian it works with the WPA_Supplicant and the same RTL81xx USB WiFi Dongle, it is registering as:

WPA2-Personal (PSK)
either TKIP & CCMP (AES) encryption works, but CCMP is more secure.


I have tried to launch the wpa-supplicant from the Terminal but it states no drivers found, should not the wpa-supplicant tool be the default like in Raspbian ??

Keep up the good work, and thanks yet again...

[truehl]

Sorry, still no solution for dropbear Start on Boot without Desktop???

[Cloudcentric]

Cloudcentric@
Wireless is really interesting, let me know your findings.
Bela

Maybe wicd and wicd-gtk would work better for LAN/Wifi as can be used in the CLi ??

[bmarkus]

Sorry, still no solution for dropbear Start on Boot without Desktop???

Add

/usr/local/etc/init.d/dropbear start

to /opt/bootlocal.sh

[Gerrelt]

Yes now have a Wireless N 150Mbps Wireless Router and the Security is set to WPA/WPA2 - TKIP/AES, by default

PiCore launches the Command Line "Tiny WiFi Scanning Tool" from the tool bar icon and finds all nearby connections without issue with the correct encryption listed.

Unfortunately it will not except my credentials and have tried various router settings:

WPA - TKIP

54G only WPA - TKIP

54G only WPA - AES


I have tried to launch the wpa-supplicant from the Terminal but it states no drivers found, should not the wpa-supplicant tool be the default like in Raspbian ??

I am having the same problem.
At first I tried it with the wifi.sh script (see: http://forum.tinycorelinux.net/index.ph ... 491.0.html), and that listed the wifi points but could not connect.

Then I tried it with commands

This command lists all the available wifi networks, so I know my USB dongle is working:

Code: Select all

iwlist wlan0  scanning

But when I execute wpa_supplicant it tells me "no drivers found". This is the command I am using and its result:

Code: Select all

tc@box:/opt$ wpa_supplicant -B -Dwext -i wlan0 -c /opt/wpa_supplicant.conf
No drivers enabled
Failed to initialize wpa_supplicant
tc@box:/opt$

I even pointed it at the generic wifi driver "wext".

(above command found here: http://forum.tinycorelinux.net/index.php?topic=12441.0)

This is the lsusb result:

Code: Select all

tc@box:/opt$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 046d:c52e Logitech, Inc.
Bus 001 Device 005: ID 2101:8500 ActionStar
Bus 001 Device 006: ID 2101:8501 ActionStar
Bus 001 Device 007: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 001 Device 008: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
tc@box:/opt$

The last one is my wifi dongle.
But now I think it isn't a dongle problem, but a configuration problem.

Are the drivers for wpa_supplicant missing in picore?

BTW, I really like this Linux version, it's ability to be unplugged without shutting off the OS is perfect for a Raspberry Pi!
I really hope to get wifi working.

[Cloudcentric]

Yes I do hope that it is fixed as I also use a RTL81xx Realtek USB WiFi Dongle and your problems are same as mine.

WICD I believe is the way forward, but I am being patient because it is a lot of work for the developers............

[Gerrelt]

I just found out some more info, I executed the wpa_supplicant command with a question mark.
This will list all de parameters, but it will also list the drivers.
I executed it on piCore and on Raspbian Wheezy.

The result on piCore:

Code: Select all

tc@box:/opt$ wpa_supplicant -?
  .
  snip
  .
  .
usage:
  wpa_supplicant [-BddhKLqqstuvW] [-P<pid file>] [-g<global ctrl>] \
        -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] [-p<driver_param>] \
        [-b<br_ifname>] [-f<debug file>] [-e<entropy file>] \
        [-o<override driver>] [-O<override ctrl>] \
        [-N -i<ifname> -c<conf> [-C<ctrl>] [-D<driver>] \
        [-p<driver_param>] [-b<br_ifname>] ...]

drivers:
options:
  -b = optional bridge interface name
  -B = run daemon in the background
  .
  .
  .
  etc..

On Raspbian Wheezy:

Code: Select all

pi@raspberry ~ $ wpa_supplicant -?
  .
  snip
  .
  .
usage:
  wpa_supplicant [-BddhKLqqstuvW] [-P<pid file>] [-g<global ctrl>] \
        -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] [-p<driver_param>] \
        [-b<br_ifname>] [-f<debug file>] [-e<entropy file>] \
        [-o<override driver>] [-O<override ctrl>] \
        [-N -i<ifname> -c<conf> [-C<ctrl>] [-D<driver>] \
        [-p<driver_param>] [-b<br_ifname>] ...]

drivers:
  wext = Linux wireless extensions (generic)
  nl80211 = Linux nl80211/cfg80211
  wired = Wired Ethernet driver
  none = no driver (RADIUS server/WPS ER)
options:
  -b = optional bridge interface name
  -B = run daemon in the background
  -c = Configuration file
  .
  .
  .
  etc..

Note the part between "drivers:" and "options:", on raspbian there are drivers present, on piCore not...

[bmarkus]

Cloudcentric@
Wireless is really interesting, let me know your findings.
Bela

Maybe wicd and wicd-gtk would work better for LAN/Wifi as can be used in the CLi ??

wicd has a long list of dependencies and in piCore term is really a bloated application. Personally I liked it but dropped a year ago against the CLI tool on my x86 laptop.

[bmarkus]

I just found out some more info, I executed the wpa_supplicant command with a question mark.
This will list all de parameters, but it will also list the drivers.
I executed it on piCore and on Raspbian Wheezy.

The result on piCore:

Code: Select all

tc@box:/opt$ wpa_supplicant -?
  .
  snip
  .
  .
usage:
  wpa_supplicant [-BddhKLqqstuvW] [-P<pid file>] [-g<global ctrl>] \
        -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] [-p<driver_param>] \
        [-b<br_ifname>] [-f<debug file>] [-e<entropy file>] \
        [-o<override driver>] [-O<override ctrl>] \
        [-N -i<ifname> -c<conf> [-C<ctrl>] [-D<driver>] \
        [-p<driver_param>] [-b<br_ifname>] ...]

drivers:
options:
  -b = optional bridge interface name
  -B = run daemon in the background
  .
  .
  .
  etc..

On Raspbian Wheezy:

Code: Select all

pi@raspberry ~ $ wpa_supplicant -?
  .
  snip
  .
  .
usage:
  wpa_supplicant [-BddhKLqqstuvW] [-P<pid file>] [-g<global ctrl>] \
        -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] [-p<driver_param>] \
        [-b<br_ifname>] [-f<debug file>] [-e<entropy file>] \
        [-o<override driver>] [-O<override ctrl>] \
        [-N -i<ifname> -c<conf> [-C<ctrl>] [-D<driver>] \
        [-p<driver_param>] [-b<br_ifname>] ...]

drivers:
  wext = Linux wireless extensions (generic)
  nl80211 = Linux nl80211/cfg80211
  wired = Wired Ethernet driver
  none = no driver (RADIUS server/WPS ER)
options:
  -b = optional bridge interface name
  -B = run daemon in the background
  -c = Configuration file
  .
  .
  .
  etc..

Note the part between "drivers:" and "options:", on raspbian there are drivers present, on piCore not...

Thank you for trying WIFi and reporting result. Will revisit wpa_supplicant in next days.

[bmarkus]

REQUEST PLEASE READ

Guys, really happy to see increasing interest. I kindly ask you to use the official Tiny Core Linux forum's Raspberry Pi section:

http://forum.tinycorelinux.net/index.ph ... ,57.0.html

There you will get faster response from team and community members. Also, piCore has many unique features which are not Rasberry but Tiny Core Linux specific and common with the x86 version. You will find answers, WiKi articles, etc. on persistense, creating extensions, backup, how to start program at boot time, etc.

Please visit us at http://tinycorelinux.net/

bmarkus
Tiny Core Linux developer

[Cloudcentric]

Thank you for the response..............................