Help me please.

[rjames93]

I recently purchased a dream plug to replace my 10 year old power hungry and noisy server. I am currently staying in university halls, meaning I only have access to their wireless network, secured with WPA2-TKIP. Upon delivery I was impressed. I had difficulty getting into the plug using a windows machine because neither device had a static ip, I went to the computer society to use the LAN. We had downloaded wpa_supplicant and updated/upgraded all the packages on the plug and attempted to take the plug into wireless client mode, this however did not work. sudo wlan.sh gives

Code:

ERROR: Module libertas_sdio is in use
ERROR: Module libertas is in use by libertas_sdio
Stopping very small DHCP server: Stopping DNS forwarder and DHCP server: dnsmasqnot running ... (warning).
.
/usr/bin/wlan.sh: line 10: /proc/uap/uap0/hwstatus: No such file or directory
uap0: ERROR while getting interface flags: No such device
ERROR: Module uap8xxx does not exist in /proc/modules
WARNING: All config files need .conf: /etc/modprobe.d/pnp-hotplug, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/display_class, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.

I can now connect to the device through eth1 which we had the good sense to fix a static ip to in case the wireless didn't work. The problem being is that now despite the access point indicator being on, we cannot detect it. I need help in ascertaining why the AP is not working and then if possible allow wlan.sh to work. If you need any more information leave a comment or an email to rjames93@sucs.org

Robert

[rjames93]

Additional information. While the plug shows the power, a flashing blue-tooth indicator and a solid AP light. There is no Access Point available. dmesg information is available below

Code:

uap_probe: vendor=0x02DF device=0x9104 class=0 function=1
UAP FW already running! Skip FW download
uap_get_mac_address fail=2
Fail to get mac address
uap_probe: uap_add_callback failed
uap_sdio: probe of mmc0:0001:1 failed with error -1
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (8027 buckets, 32108 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
Bridge firewalling registered
eth1: no IPv6 routers present
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas: command 0x00a9 timed out
libertas: requeueing command 0x00a9 due to timeout (#1)
libertas: command 0x00a9 timed out
libertas: requeueing command 0x00a9 due to timeout (#2)
libertas: command 0x00a9 timed out
libertas: requeueing command 0x00a9 due to timeout (#3)
libertas: command 0x00a9 timed out
libertas: Excessive timeouts submitting command 0x00a9
libertas: PREP_CMD: command 0x00a9 failed: -110
libertas: CMD_FUNC_INIT cmd failed
libertas: ff:ff:ff:ff:ff:ff, fw 0.0.0p0, cap 0x00000000
libertas: unidentified region code; using the default (USA)
libertas: wlan0: Marvell WLAN 802.11 adapter

[Confusticated]

I recently purchased a dream plug

Where from ? If not from NewIT knowing the serial number helps...(search this forum for why)
What Distro are you running (from internal u-SDHC or external SDHC)
What do you want to use the plug for (Squeezebox Server, Firewall\Router, etc) to what (Laptop running XP, Windows 7 PC, etc)
Which instructions did you follow to set up AP mode ?
I suggest you search this forum and plugcomputer.org for past issues with Wifi, you will then know what to try and what to look for.
Follow one of the available guides, when you hit difficulties post again (linking to the guide you used so we can see what you have tried to do) with any specific error message you got.

From what you have posted I can see your kernel is trying to load both AP Mode and Client Mode drivers at the same time, start by blacklisting the relevant modules.