WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
piCore Final Releases / Re: piCore-8.1.5 released
« Last post by Misalf on February 16, 2017, 01:26:17 PM »
Hi bmarkus,
can we expect the extension loading while booting will be the same as in x86* at some point?
And if so, is it at high or low priority?
In particular,  tce-bootload  currently isn't checking for  /usr/local/tce.installed/tcz-name
and files of extensions will be overwritten by those loaded later, which  tce-load  only does if the  -f  flag (force) is used.
22
Raspberry Pi / Re: Add lrzsz to the repo?
« Last post by bambadoo on February 16, 2017, 11:20:43 AM »
Just checked.
Quote
tc@piCorePlayer:/usr/bin$ sudo cat /etc/inittab
# /etc/inittab: init configuration for busybox init.
# Boot-time system configuration/initialization script.
#
::sysinit:/etc/init.d/rcS

# /sbin/getty respawn shell invocations for selected ttys.
tty1::respawn:/sbin/getty -nl /sbin/autologin 38400 tty1
#tty2::respawn:/sbin/getty 38400 tty2
#tty3::respawn:/sbin/getty 38400 tty3
#tty4::askfirst:/sbin/getty 38400 tty4
#tty5::askfirst:/sbin/getty 38400 tty5
#tty6::askfirst:/sbin/getty 38400 tty6

# Stuff to do when restarting the init
# process, or before rebooting.
::restart:/etc/init.d/rc.shutdown
::restart:/sbin/init
::ctrlaltdel:/sbin/reboot
::shutdown:/etc/init.d/rc.shutdown

However - maybe this is a clue?
Installing lrzsz from the repo should install the ymodem, xmodem and zmoden protocols
in
/usr/bin/sx
/usr/bin/rx
/usr/bin/zx

and so on.
However these "files" are not present. Could they be installed somewhere else by default in tiny core?

EDIT: Voila!!
In this lrzsz install these are installed in, and are called something else
Quote
usr/local/bin/lrx
usr/local/bin/lrb
usr/local/bin/lsx
usr/local/bin/lsb
usr/local/bin/lsz
usr/local/bin/lrz

Edited in minicom config and everything works.
So easy and still so difficult.

23
Raspberry Pi / Re: Add lrzsz to the repo?
« Last post by patrikg on February 16, 2017, 10:56:27 AM »
I don't know if picoreplayer uses the original way of starting getty in the initttab file.
You could look at
Code: (bash) [Select]
sudo cat /etc/inittab
And maybe remark that line with your serial terminal starting...

Code: (bash) [Select]
sudo nano /etc/inittab

Saying something like this.
From:
Code: (bash) [Select]
ttyAMA0::respawn:/sbin/getty -L 115200 /dev/ttyAMA0 vt100

To:
Code: (bash) [Select]
# ttyAMA0::respawn:/sbin/getty -L 115200 /dev/ttyAMA0 vt100

24
TCE Bugs / Re: wifi.sh does not connect wap frequency chosen in list
« Last post by Juanito on February 16, 2017, 05:42:28 AM »
The patch was suggested by the wpa_supplicant people.

I get 4x the throughput with 5GHz as compared to 2.4GHz, which tends to support the changed s/n threshold.
25
TCE Bugs / Re: wifi.sh does not connect wap frequency chosen in list
« Last post by hiro on February 16, 2017, 05:06:44 AM »
Code: [Select]
a0:55:4f:66:d5:18 freq=2447 qual=0 noise=-89~ level=-49 snr=40* flags=0xb age=0 est=65000
a0:55:4f:66:d5:10 freq=5240 qual=0 noise=-92~ level=-67 snr=25 flags=0xb age=0 est=390001

Quote
although the SNR for both is good. Generally, wpa_s considers any SNR above 30 as good).

the second one has snr 25, which is not above 30, so why do they claim it's "good" ?
your fix also seems to be based on this assumption, so i guess you agree.
26
Programming & Scripting - Unofficial / Re: depfinder: script to find dependencies
« Last post by halma on February 16, 2017, 03:35:18 AM »
bugfix update to Version 0.1c

the argument "-e" did not take the minus character correctly, on version 01.b (pcre-dev) gets only (pcre) :(
now version 0.1c will get (pcre-dev) correct.
27
Raspberry Pi / Re: Add lrzsz to the repo?
« Last post by bambadoo on February 16, 2017, 03:19:38 AM »
Hi and thanks for your effort.
I have rpi 2
No reference to startserialgetty in bootlocal.sh
Quote
#!/bin/sh
# put other system startup commands here
GREEN="$(echo -e '\033[1;32m')"
echo
echo "${GREEN}Running bootlocal.sh..."
#pCPstart------
/home/tc/www/cgi-bin/do_rebootstuff.sh 2>&1 | tee -a /var/log/pcp_boot.log
#pCPstop------
Regarding baudrate etc. I have set the right parameters in minicom serial programme (115200 8n1 - HW and Flow control =0)



28
TCE Bugs / Re: wifi.sh does not connect wap frequency chosen in list
« Last post by Juanito on February 16, 2017, 02:39:51 AM »
Using this patch
Code: [Select]
--- wpa_supplicant/scan.c.orig 2017-02-16 13:39:16.809997441 +0000
+++ wpa_supplicant/scan.c 2017-02-16 13:39:53.536663769 +0000
@@ -1738,7 +1738,7 @@
  * recommends 25 as a minimum SNR for 54 Mbps data rate. 30 is chosen here as a
  * conservative value.
  */
-#define GREAT_SNR 30
+#define GREAT_SNR 25
 
 #define IS_5GHZ(n) (n > 4000)

..wifi.sh connects to the 5GHz band most of the time - I appear to be sitting at the edge of the area where it gets a s/n ratio of 25  :)
29
Raspberry Pi / Re: Add lrzsz to the repo?
« Last post by patrikg on February 16, 2017, 12:52:29 AM »
And the serial maybe occupied with the console.
In picore the startserialtty starts the serial console.

You may remove/remark the startserialtty from the file:

Code: (bash) [Select]
sudo nano /opt/bootlocal.sh
From:
Code: (bash) [Select]
/usr/sbin/startserialtty &
To:
Code: (bash) [Select]
# /usr/sbin/startserialtty &

And one more thing... is the serial port the uart initialized with the correct things like baudrate.
Can't find any settings of that in the lrzsz, it has to be done before running lrzsz.
30
TCE Bugs / Re: wifi.sh does not connect wap frequency chosen in list
« Last post by Juanito on February 16, 2017, 12:32:39 AM »
After examining the wpa_supplicant log:
Code: [Select]
a0:55:4f:66:d5:18 freq=2447 qual=0 noise=-89~ level=-49 snr=40* flags=0xb age=0 est=65000
a0:55:4f:66:d5:10 freq=5240 qual=0 noise=-92~ level=-67 snr=25 flags=0xb age=0 est=390001

The wpa_supplicant people say:
Quote
According to the wpa_supplicant AP scoring, it would indeed seem that the 2.4GHz AP is prefered since it has better SNR (although the SNR for both is good. Generally, wpa_s considers any SNR above 30 as good).
...
perhaps the scoring can be tweaked to more aggressively favor 5.2 in case of close good SNR.

At the place where I usually sit/work, about 10m from the wap with a structural wall in between, wpa_supplicant almost always chooses 2.4ghz.

Using iperf to test, I got 4x the throughput when I forced wpa_supplicant to choose 5ghz.

Anyway - it would seem the issue is not with wifi.sh, but with wpa_supplicant.

This been said, wifi.sh does give the impression that it is going to connect to 5ghz, when in fact it allows wpa_supplicant to choose between 2.4ghz and 5ghz.
Pages: 1 2 [3] 4 5 ... 10