Re: F14 os4 development image released (XO-1 and XO-1.5)
by Daniel Drake
2010/12/5 Christophe Guéret <c.d.m.gueret(a)vu.nl>:
> I would like to compile some stuff to be run on an XO-1 and I would rather
> doing that on my desktop rather than on the XO directly.
You didn't mention what you want to compile so I'll assume its just a
regular application.
You can compile it like you would for any 32bit x86 platform (e.g. on
your main desktop) and it will work on the XO, provided library
dependencies are met.
Almost all of the packages on the XO come directly from Fedora (being
compiled by Fedora's generic build servers) -- there's nothing
XO-specific to worry about.
> How can this image be run with QEMU, if it can?
There's no qemu support at the moment.
Daniel
13 years, 4 months
Re: Modifying 353 (xo-1) to apply the dev.laptop.org/ticket/10195 fix
by Mikus Grinbergs
Quozl wrote:
>> A symptom that I frequently observe is that 'iwlist eth0 scan'
>> (as root) does not show the radio signals that other XO_1s do show.
>
> Use scan-wifi in OpenFirmware in order to exclude the operating
> system configuration from the problem.
Thank you, thank you, thank you. This gives me a 'starting point'.
To 'scan-wifi', the "bad" XO-1s return lines like this:
RSSI: 0 SSID: Channel 1
...
RSSI: 0 SSID: Channel 1
RSSI: 41 SSID: Channel 1
To 'scan-wifi', the "good" XO-1s return lines like this:
RSSI: 0 SSID: Channel 1
... <more such lines than the "bad" XO-1s>
RSSI: 0 SSID: Channel 1
RSSI: 85 SSID: 2WIRE241 Channel 11
Note that both the "bad" XO1-s and the "good" XO-1s __will__ connect via
the (non-adhoc) mesh interface -- to me that says the silicon is working
-- though I do not know if the AP radio signal in the "bad" XO-1s is too
attenuated (bad antenna connection?) to be detected.
Thanks again, mikus
13 years, 4 months