WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 ... 3 4 [5] 6 7 ... 10
41
This script was inspired by a thread that talked about handling .info files.
What the planned endgame there is, I still don't know.

I did find these statements a bit disturbing:
Quote
... the current info files are intended for human consumption as plain text
not for programmatic / machine readability & processing ...
and
Quote
... Yes, adopting a standard would increase machine readability. ...
It sounds like the idea is to make life easier for computers and more difficult
for people creating the .info file.

Anyway, here's how it works:
Code: [Select]
tc@E310:~/Scripting/RepoScripts/ParseInfoFile$ ./ParseInfoFile.sh PicFormat Title Version Current Size
Title:          PicFormat.tcz
Version:        v0.20
Current:        2021/07/16 v0.20 Added -p resize option.
Size:           8.0K
Give it the file name and field names you are interested in, and it returns their
contents in the same order requested. File name can be  Filename, Filename.tcz, or
Filename.tcz.info and the script will correct it to Filename.tcz.info. The .info must
be present on your machine. The script does not connect to the repo for it.

If you want the field name on a separate line:
Code: [Select]
tc@E310:~/Scripting/RepoScripts/ParseInfoFile$ ./ParseInfoFile.sh PicFormat -s Title Version Current Size
Title:
                PicFormat.tcz
Version:
                v0.20
Current:
                2021/07/16 v0.20 Added -p resize option.
Size:
                8.0K
Some other options include a count of how many field names are in the file, a
list of all of the field names in the file, and a list of all field names and their
starting and ending line numbers:
Code: [Select]
tc@E310:~/Scripting/RepoScripts/ParseInfoFile$ ./ParseInfoFile.sh PicFormat -i
Title.1,1
Description.2,2
Version.3,3
Author.4,4
Original-site.5,5
Copying-policy.6,6
Size.7,7
Extension_by.8,8
Tags.9,9
Comments.10,44
Change-log.45,45
Current.46,46
This is also the order the field names appear in the file.
The field names are not hard coded in the script. They are obtained by scanning
the file in question.

There is also a help message:
Code: [Select]
tc@E310:~/Scripting/RepoScripts/ParseInfoFile$ ./ParseInfoFile.sh -h
Version 0.1 Dec 22, 2024

This script is used to find and display labels and their contents
from a .tcz.info file. Options must be listed separately, -e -s, not -es.

  Usage:

    ParseInfoFile.sh filename [ -n -l -i -s -e ] Label1 Label2 Label3 ...

    -n    Display number of labels in info file.
    -l    List the labels found in info file.
    -i    Like l but includes start/end line numbers for label.
    -s    Place label on a separate line.
    -e    Extra linefeed between label results.

    Labels will be listed in the order requested, example:

ParseInfoFile.sh PicFormat Title Current Size
Title:          PicFormat.tcz
Current:        2021/07/16 v0.20 Added -p resize option.
Size:           8.0K


Script is attached.
42
CorePlus / Re: Can the recent Xorg detect a serial mouse?
« Last post by CNK on December 22, 2024, 07:13:47 PM »
I guess by disabling hotplugging you're trying to stop this in the Xorg log:
Code: [Select]
Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.

The 'mouse' driver accesses the mouse directly from the serial devices like in Juanitos configuration, but it's being disabled.

The other drivers rely on the Linux kernel having detected/configured the serial mouse correctly as described here. But that page doesn't mention serial mice.

I wonder if the Linux kernel's serial mouse driver ("sermouse" - built into the kernel according to the "CONFIG_MOUSE_SERIAL=y" settings in the build configuration) isn't working, so the only way is to force Xorg to access the serial port directly via its 'mouse' driver (maybe by not loading either xf86-input-libinput or xf86-input-evdev but just xf86-input-mouse)?

It sounds like if the sermouse driver is working you should have a /dev/input/mice device that can be used like a PS/2 mouse by X.

I gather you can also check the Linux serial mouse device by loading libinput.tcz and running:

Code: [Select]
sudo libinput list-devices

And see if it lists a /dev/input/event* device that matches your serial mouse.
43
It's amazing that the S-band hadn't been used since 1981 and it still worked. Since they're trying to extend the battery life, I wonder if the weaker S-band uses less energy than the X-band. In any case, all of this  is amazing!
44
Raspberry Pi / Re: Wifi 2.4 GHz channels and regdb in picore 15.x
« Last post by Paul_123 on December 22, 2024, 03:34:57 PM »
wpa_supplicant may override that,  while the program is called wpa_supplicant, you can configure open networks just fine.
45
Raspberry Pi / Re: Wifi 2.4 GHz channels and regdb in picore 15.x
« Last post by ovacikar on December 22, 2024, 02:53:10 PM »
Public Wifi hotspots do not use WPA  / wpa_supplicant at all, so I will try this next time near a public wifi:

Code: [Select]
sudo iw reg set US 
46
Raspberry Pi / Re: Wifi 2.4 GHz channels and regdb in picore 15.x
« Last post by Paul_123 on December 22, 2024, 01:08:52 PM »
The wifi script is very generic it doesn’t support country code, which is becoming more and more restrictive.  Best to manually configure it, so you know exactly what’s going on.
47
Raspberry Pi / Re: Wifi 2.4 GHz channels and regdb in picore 15.x
« Last post by ovacikar on December 22, 2024, 12:52:41 PM »
No , I am using wifi.sh script, but these settings are loaded before running the script.The wpa_supplicant.conf only contains the WPA password, after running the script.

I was wondering if the poor performance of rtl8192cu is caused by the restricted TX power for all channels mentioned for this additional phy0 entry. My rhome outer does not advertise channels 12/13 anyways.


The AP selects channel 2 in auto mode. Using the same channel 2 , local download 2x faster with the legacy 8192cu


48
Raspberry Pi / Re: Wifi 2.4 GHz channels and regdb in picore 15.x
« Last post by Paul_123 on December 22, 2024, 12:13:47 PM »
Drivers are required to be regulatory compliant.  Are you setting country code in your wpa_supplicant?

Channels 12 and 13 are in the US are typically not regulatory compliant. (Very special circumstances allow it, but I've never seen them enabled in the US reg dom)
49
CorePlus / Re: Can the recent Xorg detect a serial mouse?
« Last post by t18 on December 22, 2024, 11:03:55 AM »
AFAIK the serial port 1 is ttyS0 and the mouse is usually plugged in to it.
While the serial port 2 is ttyS1, used for modems or digitizer.
On my pc the keyboard is plugged in to the AT port.
Anyway thank you so much for the time you have devoted to me, I'll keep it like that.
50
Raspberry Pi / Wifi 2.4 GHz channels and regdb in picore 15.x
« Last post by ovacikar on December 22, 2024, 10:16:13 AM »
Are these settings in picore 15 normal? Trying to find out why rtl8192cu is giving me so many problems and noticed this:

Code: [Select]
tc@:~$ iw reg get
tc@:~$ global
country US: DFS-FCC
(2400 - 2483 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A)
(57240 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0
country 99: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 40), (N/A, 20), (N/A), PASSIVE-SCAN
(5140 - 5360 @ 80), (N/A, 30), (N/A)
(5460 - 5860 @ 80), (N/A, 30), (N/A)


iwlist channel
lo        no frequency information.

eth0      no frequency information.

wlan0     13 channels in total; available frequencies :
          Channel 01 : 2.412 GHz
          Channel 02 : 2.417 GHz
          Channel 03 : 2.422 GHz
          Channel 04 : 2.427 GHz
          Channel 05 : 2.432 GHz
          Channel 06 : 2.437 GHz
          Channel 07 : 2.442 GHz
          Channel 08 : 2.447 GHz
          Channel 09 : 2.452 GHz
          Channel 10 : 2.457 GHz
          Channel 11 : 2.462 GHz
          Channel 12 : 2.467 GHz
          Channel 13 : 2.472 GHz


In comparison, legacy 8192cu ( without the rtl prefix. rtl8192cu and 8192cu are different) driver in picore 12.x shows proper channel and regdb, and works perfectly everywhere:

Code: [Select]
tc@:~$ iw reg get
global
country US: DFS-FCC
(2400 - 2483 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A)
(57240 - 71000 @ 2160), (N/A, 40), (N/A)

tc@pi:~$ iwlist channel
wlan0     11 channels in total; available frequencies :
          Channel 01 : 2.412 GHz
          Channel 02 : 2.417 GHz
          Channel 03 : 2.422 GHz
          Channel 04 : 2.427 GHz
          Channel 05 : 2.432 GHz
          Channel 06 : 2.437 GHz
          Channel 07 : 2.442 GHz
          Channel 08 : 2.447 GHz
          Channel 09 : 2.452 GHz
          Channel 10 : 2.457 GHz
          Channel 11 : 2.462 GHz

Pages: 1 ... 3 4 [5] 6 7 ... 10