armv6 and realtek firmware

[Rich]

Hi stephanmg
Things that need to run before a GUI are started (like kmaps) should go into  /opt/bootsync.sh.
Things that need to run after a GUI are started (like starting a GUI app) should go into  ~/.X.d.
Things that are not sensitive to when they are started should go into  /opt/bootlocal.sh  which runs in the background.

.X.d  is a hidden subdirectory in your home directory. Any files you place in there will have their contents (commands) read
line by line and executed. For example, a file containing:

Code: [Select]

exec aterm &will launch a terminal after the GUI is running. The  &  tells it to launch in the background so it does not block other commands
from being run.

[stephanmg]

Thanks, great!

I cannot change the subset of the thread... it should really read: "armv6 and realtek firmware".

[Rich]

Hi stephanmg

... I cannot change the subset of the thread... it should really read: "armv6 and realtek firmware".

Done.

[Greg Erskine]

I don't understand how your wifi is working?

I think, firmware-rpi-wifi.tcz is the firmware for Raspberry Pi built-in wifi which is not a Realtek device.

For Realtek you need firmware-rtlwifi.tcz (Did I miss this somewhere in your posts?)

[Greg Erskine]

Created a shell script:

Code: [Select]

#!/bin/sh
tce-load -i firmware-rpi-wifi
tce-load -i libnl
tce-load -i libudev
tce-load -i libusb
tce-load -i usb-ids
tce-load -i wifi
tce-load -i wireless-4.19.81-piCore
tce-load -i wireless_tools
tce-load -i wpa_supplicant


This script is unnecessary.

/mnt/mmcblk0p2/tce/onboot.lst contains a list extensions to load during boot.

Your onboot.lst should contain something like this:

Code: [Select]

firmware-rtlwifi.tcz
wireless_tools.tcz
wpa_supplicant.tcz
piCore will load these extensions plus ALL their dependencies for you. Load firmware first.

[stephanmg]

No you did not miss anything.

I am just now realizing this, the firmware must then have been provided by another extension?
I did not load

Code: [Select]

firmware-rtlwifi.tcz by myself.

I don't understand how your wifi is working?

I think, firmware-rpi-wifi.tcz is the firmware for Raspberry Pi built-in wifi which is not a Realtek device.

For Realtek you need firmware-rtlwifi.tcz (Did I miss this somewhere in your posts?)

[stephanmg]

Thanks! I will make the changes accordingly now on my system.

I stored in /home/tc the extensions I load with my script. Should I then specify the path to these extensions in the onboot.lst? Or can I somehow make these persistent, but preferably not in my /home/tc directory?

Created a shell script:

Code: [Select]

#!/bin/sh
tce-load -i firmware-rpi-wifi
tce-load -i libnl
tce-load -i libudev
tce-load -i libusb
tce-load -i usb-ids
tce-load -i wifi
tce-load -i wireless-4.19.81-piCore
tce-load -i wireless_tools
tce-load -i wpa_supplicant


This script is unnecessary.

/mnt/mmcblk0p2/tce/onboot.lst contains a list extensions to load during boot.

Your onboot.lst should contain something like this:

Code: [Select]

firmware-rtlwifi.tcz
wireless_tools.tcz
wpa_supplicant.tcz
piCore will load these extensions plus ALL their dependencies for you. Load firmware first.

[Rich]

Hi stephanmg

... I stored in /home/tc the extensions I load with my script. Should I then specify the path to these extensions in the onboot.lst? Or can I somehow make these persistent, but preferably not in my /home/tc directory? ...

Copy the extensions to your  tce/optional/  directory.

[stephanmg]

Thanks!

Is this the commonly refered to persistent TCE directory?

Hi stephanmg

... I stored in /home/tc the extensions I load with my script. Should I then specify the path to these extensions in the onboot.lst? Or can I somehow make these persistent, but preferably not in my /home/tc directory? ...

Copy the extensions to your  tce/optional/  directory.

[Rich]

Hi stephanmg

Is this the commonly refered to persistent TCE directory?

Yes it is.

[stephanmg]

Thank you kindly for confirming.