Tiny Core Base > CorePlus
WiFi Cannot Scan
eltone:
--- Quote from: coreplayer2 on January 31, 2014, 11:55:19 PM ---The wiki is a great place to learn and source of reference..
--- Quote ---1
--- End quote ---
Meanwhile, try creating your extension in /tmp
--- Quote ---2
--- End quote ---
For this example we'll call the firmware b43cut.img, and
the extension firmware-b43cut.tcz
--- Quote ---3
--- End quote ---
start by creating your directory structure, at the command line
mkdir -p /tmp/pkg/usr/local/lib/firmware/b43cut
mkdir -p /tmp/pkg/usr/local/tce.installed
--- Quote ---4
--- End quote ---
create a file (in this case a udevadm trigger)
touch /tmp/pkg/usr/local/tce.installed/firmware-b43cut
--- Quote ---5
--- End quote ---
open file "/tmp/pkg/usr/local/tce.installed/firmware-b43cut" and enter on the first two lines
the following, then save it
--- Code: ---#!/bin/sh
udevadm trigger
--- End code ---
--- Quote ---6
--- End quote ---
copy (your firmware file) to /tmp/pkg/usr/local/lib/firmware/b43cut/
set permissions (note the own/perm. of tce.installed)
sudo chmod 644 /tmp/pkg/usr/local/lib/firmware/b43cut/b43cut.img
sudo chown -R root:root /tmp/pkg/usr
sudo chown -R root:staff /tmp/pkg/usr/local/tce.installed
sudo chmod -R 775 /tmp/pkg/usr/local/tce.installed
Now you're ready to squash it
cd /tmp
tce-load -i squashfs-tools-4.x.tcz && mksquashfs pkg/ firmware-b43cut.tcz
then copy the new extension to tce/optional dir, load it
tc@box:/$ tce-load -i firmware-b43cut.tcz
firmware-b43cut.tcz: OK
and test it
see also http://wiki.tinycorelinux.net/wiki:creating_extensions
--- End quote ---
hi,
Indexing to #5, no problem, then #6 states:
--- Quote ---copy (your firmware file) to /tmp/pkg/usr/local/lib/firmware/b43cut/
--- End quote ---
Your instructions say to call the firmware 'b43cut.img'
Q1: Is this IMG file what goes into the 'b43cut' directory?
Q2: If correct, how are the numerous FW files made into an IMG file w/TCP 5.1?
Suspect an extension is needed.
eltone
PS. keep the pile to a minimum
eltone:
--- Quote from: tinypoodle on February 01, 2014, 01:45:53 AM ---And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead ;)
--- End quote ---
hi,
'dhcpcd' does not follow udhcpc Standards. Also, tc5.x man pages has nothing on it either:
--- Quote ---tc@box:~$ dhcpcd --help
usage: dhcpcd [-dgknpqwxyADEGHJKLOTV] [-c script] [-f file] [-e var=val]
[-h hostname] [-i classID ] [-l leasetime] [-m metric] [-o option]
[-r ipaddr] [-s ipaddr] [-t timeout] [-u userclass]
[-F none|ptr|both] [-I clientID] [-C hookscript] [-Q option]
[-X ipaddr] <interface>
tc@box:~$
--- End quote ---
Q1: Has anyone been able to get dhcpcd to find a valid IP address & with what syntax?
Q2: Could dhcpcd be compiled from source w/TCP 5.1, following this protocol:
http://www.linuxfromscratch.org/blfs/view/svn/basicnet/dhcpcd.html
eltone
coreplayer2:
--- Quote from: eltone on February 01, 2014, 08:25:55 PM ---
--- Quote ---For this example we'll call the firmware b43cut.img, and
the extension firmware-b43cut.tcz
--- End quote ---
Your instructions say to call the firmware 'b43cut.img'
Q1: Is this IMG file what goes into the 'b43cut' directory?
Q2: If correct, how are the numerous FW files made into an IMG file w/TCP 5.1?
--- End quote ---
They're not exactly instructions to be followed to the letter, more of an example (though the example does in fact work as advertised).. If they were instructions it would say rename the file to this, etc etc. if that were necessary. I believe the original file name should remain unchanged, I simply didn't know the final cut file name is all. the dir name in this case is less important though ought to reflect the contents. Similar for the extension name which additionally should not conflict with any in the repo (name could be myb43, whatever..)
Rarely are two extensions alike, they differ greatly due to their contents.
better to examine how a similar extension is constructed, sometimes names and permissions are important, use
this to examine an extension
--- Code: ---unsquashfs -d extension_name extension_name.tcz
--- End code ---
tinypoodle:
--- Quote from: eltone on February 01, 2014, 10:01:23 PM ---
--- Quote from: tinypoodle on February 01, 2014, 01:45:53 AM ---And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead ;)
--- End quote ---
hi,
'dhcpcd' does not follow udhcpc Standards. Also, tc5.x man pages has nothing on it either:
--- End quote ---
Huh?? ???
Both udhcpc and dhcpcd follow dhcp protocol as described in the relevant RFC's.
The manpage of dhcpcd could be found within less than a minute on the web, like almost all manpages... ::)
--- Quote ---Q1: Has anyone been able to get dhcpcd to find a valid IP address & with what syntax?
Q2: Could dhcpcd be compiled from source w/TCP 5.1, following this protocol:
http://www.linuxfromscratch.org/blfs/view/svn/basicnet/dhcpcd.html
eltone
--- End quote ---
dhcpcd.tcz is already in 5.x repo, I checked that before even suggesting so...
eltone:
--- Quote from: tinypoodle on February 02, 2014, 01:29:21 AM ---
dhcpcd.tcz is already in 5.x repo, I checked that before even suggesting so...
--- End quote ---
My Dear Friend!
Q: Shouldn't ALL remnants of udhcpc be completely removed before installing the .TCZ?
It appears to be original settings of TCP 5.1 . . .
'udhcpc' has no .TCZ and suspect it to be part of the OS Standards.
Faithfully,
eltone
* FIX what's BROKEN *
:)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version