* missing piece for starting device on embedded system
@ 2009-07-17 1:19 Jon Smirl
2009-07-17 2:15 ` Jon Smirl
0 siblings, 1 reply; 3+ messages in thread
From: Jon Smirl @ 2009-07-17 1:19 UTC (permalink / raw)
To: linux-wireless
I must be missing a piece of the necessary environment to get wireless
started...
This is an embedded environment that has not had wireless previously.
When I plug my rt73 adapter in:
usb 1-2: USB disconnect, address 6
usb 1-2: new full speed USB device using ppc-of-ohci and address 7
usb 1-2: configuration #1 chosen from 1 choice
phy3 -> rt73usb_validate_eeprom: EEPROM recovery - NIC: 0xffef
phy3 -> rt73usb_validate_eeprom: EEPROM recovery - Led: 0xe000
phy3 -> rt73usb_validate_eeprom: EEPROM recovery - RSSI OFFSET A: 0x0000
phy3 -> rt2x00_set_chip: Info - Chipset detected - rt: 1300, rf: 0002,
rev: 0002573a.
phy3: Selected rate control algorithm 'minstrel'
-----------
UDEV [1247788838.265890] add /class/net/wmaster0 (net)
UDEV_LOG=3
ACTION=add
DEVPATH=/class/net/wmaster0
SUBSYSTEM=net
INTERFACE=wmaster0
IFINDEX=9
SEQNUM=594
UDEV [1247788838.268243] add /class/net/wlan0 (net)
UDEV_LOG=3
ACTION=add
DEVPATH=/class/net/wlan0
SUBSYSTEM=net
INTERFACE=wlan0
IFINDEX=10
SEQNUM=595
MATCHADDR=00:18:f3:2f:0a:de
MATCHIFTYPE=1
COMMENT=USB device 0x:0x (rt73usb)
----------
But I never get a request_firmware event. This seems to be because the
adapter 's start() function is never called.
I'm missing some piece of the system - a kernel module or some part of
user space.
Can someone give me a clue on how to debug this?
I though it was missing crda but adding that didn't fix it.
--
Jon Smirl
jonsmirl@gmail.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: missing piece for starting device on embedded system
2009-07-17 1:19 missing piece for starting device on embedded system Jon Smirl
@ 2009-07-17 2:15 ` Jon Smirl
2009-07-17 6:25 ` Kalle Valo
0 siblings, 1 reply; 3+ messages in thread
From: Jon Smirl @ 2009-07-17 2:15 UTC (permalink / raw)
To: linux-wireless
On Thu, Jul 16, 2009 at 9:19 PM, Jon Smirl<jonsmirl@gmail.com> wrote:
> I must be missing a piece of the necessary environment to get wireless
> started...
> This is an embedded environment that has not had wireless previously.
Duh.. the device does not show in ifconfig until I run "ifconfig wlan0 up".
--
Jon Smirl
jonsmirl@gmail.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: missing piece for starting device on embedded system
2009-07-17 2:15 ` Jon Smirl
@ 2009-07-17 6:25 ` Kalle Valo
0 siblings, 0 replies; 3+ messages in thread
From: Kalle Valo @ 2009-07-17 6:25 UTC (permalink / raw)
To: Jon Smirl; +Cc: linux-wireless
Jon Smirl <jonsmirl@gmail.com> writes:
> On Thu, Jul 16, 2009 at 9:19 PM, Jon Smirl<jonsmirl@gmail.com> wrote:
>> I must be missing a piece of the necessary environment to get wireless
>> started...
>> This is an embedded environment that has not had wireless previously.
>
> Duh.. the device does not show in ifconfig until I run "ifconfig wlan0 up".
'ifconfig -a' shows all interfaces, even the ones which are down.
--
Kalle Valo
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-07-17 6:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-17 1:19 missing piece for starting device on embedded system Jon Smirl
2009-07-17 2:15 ` Jon Smirl
2009-07-17 6:25 ` Kalle Valo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).