Tiny Core Base > CorePlus

WiFi Cannot Scan

<< < (22/30) > >>

eltone:
hi,
'udhcpc' passed burn-in on PC #2, BUT now is NON-functional, just like what was reported earlier!
This malfunction does NOT occur on other distros.   Please help.


--- Code: ---sudo udhcpc -S -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid

--- End code ---

The '-S' switch was enabled to ammend attached syslog . . .

Excellent CLI Network Configuration Article:
http://ubuntuforums.org/showthread.php?t=684495

THX4HLP!
eltone
* udhcpclg.txt FAILED
   udhcpcl2.txt PASSED

eltone:

--- Quote from: Juanito on January 26, 2014, 01:27:53 AM ---

It would be better to make a personal extension out of a large amount of static data like the b43 firmware rather than making it part of your backup.

Once you've made a personal extension out of the b43 firmware, you can place it before wicd in onboot.lst

--- End quote ---

tc-5.x Guru's,

I have researched HOW2 make a personal extension for someone that's cutting-their-teeth w/tc-5.1 and find nothing but outdated material.  Any help from those that have done this before?

I hate to reinvent the . . .
eltone

Rich:
Hi eltone
This doesn't look outdated to me:
http://wiki.tinycorelinux.net/wiki:extension_for_settings

coreplayer2:
The wiki is a great place to learn and source of reference..

Meanwhile, try creating your extension in /tmp

For this example we'll call the firmware b43cut.img, and
the extension firmware-b43cut.tcz

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

create a file (in this case a udevadm trigger)
    touch /tmp/pkg/usr/local/tce.installed/firmware-b43cut

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 ---

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

Juanito:

--- Quote from: eltone on January 31, 2014, 08:23:05 PM ---'udhcpc' passed burn-in on PC #2, BUT now is NON-functional, just like what was reported earlier!
This malfunction does NOT occur on other distros.   Please help.

--- End quote ---

Hundreds of tinycore users are using udhcpc every day without problems - the problem is not with udhcpc, but with what comes before the the udhcpc command. Several users, myself included, have tried to help, but you need to follow what is suggested in the order it is suggested for things to work.

I sent you a pm two or three weeks ago offering to make a firmware extension for you, but (so far) you've ignored it.

Again, the order to do things is:

1. Load firmware

2. Load wireless module

3. Associate with wap

4. Run udhcpc

Navigation

[0] Message Index

[#] Next page

[*] Previous page