• Registered: 2010-04-13
  • Posts: 4

Topic: Problems connecting to WLAN

I recently got my chumby and in general I absolutely LOVE it. But there's one problem that drives me crazy, it has huge problems connecting to my WLAN.

So far I haven't seen any pattern. Connecting to my WLAN doesn't work at least 8 out of 10 times, it always shows:

wlan0 link is down
failed to obtain IP address
chumby.com is unreachable

But then, without anything being changed, it suddenly works. Sometimes right after I switch it on, but it usually takes 5-20 connection attempts. And once it works, the connection seems to be quite stable, as I have never seen the connection being lost once it was connected. If the connection is up, the link quality is about 80%, which I guess is not great but not critical either. I have a few other WLAN devices and I have never experienced any WLAN problems with any of them until now.
There is a setting on my WLAN router to automatically reduce the WLAN signal strength (for example signal strength is lowered if no WLAN device is connected) - I thought that might be problem, but switching the setting off and always sending at 100% signal strength didn't change a thing.

I don't know what else to try - does anyone else have an idea what the problem might be?

  • From: San Diego, CA
  • Registered: 2007-08-09
  • Posts: 112

Re: Problems connecting to WLAN

I would try attaching your chumby to another network to see if the problem persists, if it does, the issue may be with the chumby.  If not, then the issue may be with your router or something else environmental.



-Sam

sam m's Website

  • Registered: 2010-04-13
  • Posts: 4

Re: Problems connecting to WLAN

Thank you very much for trying to help, that really sounds like a good idea!

I actually already tried connecting to another WLAN. I took my chumby over to a friend of mine to show it to him. I had the same problems connecting to his WLAN, but after the third unsuccessful connection attempt I gave up and decided to show it to him another time, so I can't really tell if it was really exactly the same problem. Theoretically I could have entered the wrong encryption key or something, though I don't believe that.

But I will look into this more deeply when I'm going to visit another friend of mine later today.

  • Registered: 2010-04-13
  • Posts: 4

Re: Problems connecting to WLAN

I just tried to connect my chumby to another WLAN. It didn't work.
After about three connection attempts the "Connecting to network" screen suddenly stayed much longer than before (about two minutes I guess), and afterwards the message "wlan0 interface is down" was shown (in addition to the usual "wlan0 link is down / failed to obtain IP address / chumby.com is unreachable" error message). I can't remember having seen that error before.
I tried a few more times without success before I gave up. Signal strength definitely wasn't the problem as I placed the chumby directly next to the WLAN access point. I also double-checked the encryption key, made sure there is no MAC filter enabled etc.
I even reinstalled the firmware and factory reset the chumby to see if that changes anything, but it didn't.

Since I have now tried three different WLANs with three different WLAN access points, I'm starting to wonder if my chumby has some kind of hardware problem. What do you think?

  • From: San Diego
  • Registered: 2007-10-25
  • Posts: 205

Re: Problems connecting to WLAN

Please contact Customer Support - http://www.chumby.com/pages/help_support

Chumbymatt's Website

  • Registered: 2009-05-06
  • Posts: 81

Re: Problems connecting to WLAN

We have two Chumby One units that are doing the same exact thing.

After a reboot 90% of the time these units will come up with wlan0 is unavailable. We did some digging into the dmesg output (as compared to dmesg on a good unit) and it appears that the wifi radio is not working.

On a good working system you will see 8021 message around the 15sec mark and wlan0 messages around the 30sec mark. On a bad system you don't see any of these messages.

It would appear that this is defective hardware. Is this a known issue? Should we send these units back to be replaced?

Missing section from dmesg output

[   15.130000] cfg80211: Using static regulatory domain info
[   15.130000] cfg80211: Regulatory domain: US
[   15.140000]     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   15.140000]     (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[   15.150000]     (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[   15.170000]     (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[   15.170000]     (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[   15.190000]     (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[   15.190000]     (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[   15.210000] cfg80211: Calling CRDA for country: US
[   15.960000] phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
[   15.970000] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
[   15.990000] usbcore: registered new interface driver rt2500usb
[   16.470000] phy1: Selected rate control algorithm 'minstrel'
[   16.480000] Registered led device: rt73usb-phy1::radio
[   16.480000] Registered led device: rt73usb-phy1::assoc
[   16.490000] Registered led device: rt73usb-phy1::quality
[   16.510000] usbcore: registered new interface driver rt73usb
[   16.740000] rt73usb 1-1.2:1.0: firmware: requesting rt73.bin
[   19.680000] scsi 0:0:0:0: Direct-Access     Generic  USB Flash Disk   0.00 PQ: 0 ANSI: 2

and
[   28.230000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   29.180000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   32.140000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   34.420000] wlan0: deauthenticating from c2a5652c by local choice (reason=3)
[   34.430000] wlan0: direct probe to AP c2a5652c (try 1)
[   34.430000] wlan0: direct probe responded
[   34.430000] wlan0: authenticate with AP c2a5652c (try 1)
[   34.440000] wlan0: authenticated
[   34.440000] wlan0: associate with AP c2a5652c (try 1)
[   34.440000] wlan0: RX AssocResp from c293c03e (capab=0x411 status=0 aid=1)
[   34.440000] wlan0: associated
[   34.480000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   45.120000] wlan0: no IPv6 routers present

Full dmesg from bad device

[    0.330000] regulator: vddd: 800 <--> 1575 mV fast normal 
[    0.340000] regulator: vddd_bo: 800 <--> 1575 mV fast normal 
[    0.340000] regulator: vdda: 1500 <--> 2275 mV fast normal 
[    0.350000] regulator: vddio: 2800 <--> 3575 mV fast normal 
[    0.350000] regulator: overall_current: 0 <--> 2147483 mA fast normal 
[    0.360000] regulator: stmp3xxx-fb-1: 0 <--> 2147483 mA fast normal 
[    0.360000] regulator: stmp3xxx-bl-1: 0 <--> 2147483 mA fast normal 
[    0.370000] regulator: stmp3xxx_ts-1: 0 <--> 2147483 mA fast normal 
[    0.370000] regulator: stmp37xx-dbguart-1: 0 <--> 2147483 mA fast normal 
[    0.380000] regulator: stmp3xxx_wdt-1: 0 <--> 2147483 mA fast normal 
[    0.380000] regulator: stmp3xxx-rtc-1: 0 <--> 2147483 mA fast normal 
[    0.390000] regulator: stmp3xxx-rotdec-1: 0 <--> 2147483 mA fast normal 
[    0.390000] regulator: i2c_stmp-1: 0 <--> 2147483 mA fast normal 
[    0.400000] regulator: stmp3xxx-persistent-1: 0 <--> 2147483 mA fast normal 
[    0.400000] regulator: stmp3xxx-dcp-1: 0 <--> 2147483 mA fast normal 
[    0.410000] regulator: stmp3xxx-battery-1: 0 <--> 2147483 mA fast normal 
[    0.410000] regulator: mmc_ssp-1: 0 <--> 2147483 mA fast normal 
[    0.420000] regulator: mmc_ssp-2: 0 <--> 2147483 mA fast normal 
[    0.420000] regulator: charger-1: 0 <--> 2147483 mA fast normal 
[    0.430000] regulator: power-test-1: 0 <--> 2147483 mA fast normal 
[    0.430000] regulator: cpufreq-1: 0 <--> 2147483 mA fast normal 
[    0.440000] stmp378x_devb.c - stmp378x_devb_init():387 - Adding 15 platform-specific devices
[    0.500000] chumbyfbfw.c - chumbyfwfb_probe():1246 - resolution 320x240, bpp 2
[    0.500000] chumbyfbfw.c - get_max_memsize():1060 - get_max_memsize: mem_size now 153600 (320 x 240 x 16)
[    0.510000] chumbyfbfw.c - get_max_memsize():1060 - get_max_memsize: mem_size now 1382400 (480 x 720 x 32)
[    0.510000] chumbyfbfw.c - get_max_memsize():1060 - get_max_memsize: mem_size now 1658880 (576 x 720 x 32)
[    0.520000] chumbyfbfw.c - chumbyfwfb_probe():1259 - memory to allocate for screen: 1658880
[    0.530000] chumbyfbfw.c - chumbyfwfb_probe():1268 - allocated screen at ff600000:0x43a00000
[    0.540000] chumbyfbfw.c - chumbyfwfb_probe():1306 - memory to allocate for plane 0: 831488
[    0.550000] chumbyfbfw.c - chumbyfwfb_probe():1316 - allocated at ff795000:0x43c00000
[    0.550000] chumbyfbfw.c - chumbyfwfb_probe():1306 - memory to allocate for plane 1: 831488
[    0.560000] chumbyfbfw.c - chumbyfwfb_probe():1316 - allocated at ff860000:0x43d00000
[    0.570000] chumbyfbfw.c - chumbyfwfb_probe():1306 - memory to allocate for plane 2: 831488
[    0.580000] chumbyfbfw.c - chumbyfwfb_probe():1316 - allocated at ff92b000:0x43e00000
[    0.580000] chumbyfbfw.c - chumbyfwfb_probe():1306 - memory to allocate for plane 3: 831488
[    0.590000] chumbyfbfw.c - chumbyfwfb_probe():1316 - allocated at ff9f6000:0x43f00000
[    0.600000] Going to copy splash image from c03204d7 (153600 bytes) to ff600000 (not 43a00000)
[    0.610000] Panel init finished.
[    0.610000] unsupported display_on call
[    0.620000] chumbyfbfw.c - pxp_setup():1124 - Pointing S0 at 43c00000
[    0.620000] stmp37xx-dbguart.0: ttyAM0 at MMIO 0xf0070000 (irq = 0) is a Debug UART
[    0.670000] NET: Registered protocol family 2
[    0.680000] Switched to high resolution mode on CPU 0
[    0.780000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.780000] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.790000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    0.800000] TCP: Hash tables configured (established 2048 bind 2048)
[    0.810000] TCP reno registered
[    0.840000] NET: Registered protocol family 1
[    0.850000] ashmem: initialized
[    0.910000] Registering unionfs 2.5.2 (for 2.6.28.10)
[    0.930000] NTFS driver 2.1.29 [Flags: R/O].
[    0.940000] fuse init (API version 7.10)
[    0.950000] msgmni has been set to 117
[    0.960000] alg: No test for stdrng (krng)
[    0.970000] cryptodev: driver loaded.
[    0.970000] io scheduler noop registered (default)
[    0.980000] init_bl
[    0.980000] init_bl finished
[    0.980000] set_bl_intensity with 100
[    0.990000] intensity after modifiers: 100
[    0.990000] setting with parameters 600
[    0.990000] done.
[    1.060000] logger: created 64K log 'log_main'
[    1.070000] logger: created 256K log 'log_events'
[    1.070000] logger: created 64K log 'log_radio'
[    1.080000] STMP3xxx RTC driver v1.0 hardware v2.0.0
[    1.080000] stmp3xxx-rtc stmp3xxx-rtc: rtc core: registered stmp3xxx-rtc as rtc0
[    1.090000] power_supply battery: uevent
[    1.090000] power_supply battery: No power supply yet
[    1.090000] power_supply battery: power_supply_changed
[    1.090000] power_supply ac: uevent
[    1.090000] power_supply ac: No power supply yet
[    1.090000] power_supply battery: power_supply_changed_work
[    1.090000] power_supply battery: power_supply_update_bat_leds 3
[    1.090000] power_supply battery: uevent
[    1.090000] power_supply battery: POWER_SUPPLY_NAME=battery
[    1.090000] power_supply battery: Static prop TYPE=Battery
[    1.090000] power_supply battery: 9 dynamic props
[    1.090000] power_supply battery: prop STATUS=Not charging
[    1.090000] power_supply battery: prop PRESENT=0
[    1.090000] power_supply battery: prop HEALTH=Unknown
[    1.090000] power_supply battery: prop TECHNOLOGY=Li-ion
[    1.090000] power_supply battery: prop VOLTAGE_NOW=3648000
[    1.090000] power_supply battery: prop VOLTAGE_AVG=3648000
[    1.090000] power_supply battery: prop CURRENT_NOW=0
[    1.090000] power_supply battery: prop TEMP=4027
[    1.090000] power_supply battery: prop CAPACITY=92
[    1.090000] power_supply ac: power_supply_changed
[    1.090000] power_supply usb: uevent
[    1.090000] power_supply usb: No power supply yet
[    1.100000] power_supply ac: power_supply_changed_work
[    1.100000] power_supply ac: power_supply_update_gen_leds 1
[    1.100000] power_supply ac: uevent
[    1.100000] power_supply ac: POWER_SUPPLY_NAME=ac
[    1.100000] power_supply ac: Static prop TYPE=Mains
[    1.100000] power_supply ac: 2 dynamic props
[    1.100000] power_supply ac: prop ONLINE=1
[    1.100000] power_supply ac: prop TEMP=54
[    1.100000] power_supply usb: power_supply_changed
[    1.110000] ddi_bc_Init: success
[    1.110000] stmp3xxx-battery stmp3xxx-battery.0: bc_sm_restart: no battery present
[    1.120000] power/linux.c - bc_sm_restart():981 - Returning from sm_restart()
[    1.130000] power_supply usb: power_supply_changed_work
[    1.130000] power_supply usb: power_supply_update_gen_leds 0
[    1.130000] power_supply usb: uevent
[    1.130000] power_supply usb: POWER_SUPPLY_NAME=usb
[    1.130000] power_supply usb: Static prop TYPE=USB
[    1.130000] power_supply usb: 2 dynamic props
[    1.130000] power_supply usb: prop ONLINE=0
[    1.130000] power_supply usb: prop TEMP=53
[    1.440000] oprofile: using timer interrupt.
[    1.450000] nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
[    1.450000] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
[    1.460000] nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or
[    1.470000] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[    1.480000] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.490000] arp_tables: (C) 2002 David S. Miller
[    1.490000] TCP cubic registered
[    1.500000] NET: Registered protocol family 17
[    1.510000] RPC: Registered udp transport module.
[    1.510000] RPC: Registered tcp transport module.
[    1.520000] stmp3xxx-rtc stmp3xxx-rtc: setting system clock to 1970-01-01 00:09:49 UTC (589)
[    1.530000] Waiting for root device /dev/mmcblk0p3...
[    1.540000] mmc0: new SD card at address 0002
[    1.550000] mmcblk0: mmc0:0002 00000 971 MiB 
[    1.550000]  mmcblk0: p1 p2 p3 p4 < p5 p6 >
[    1.650000] EXT3-fs: mounted filesystem with ordered data mode.
[    1.660000] VFS: Mounted root (ext3 filesystem) readonly.
[    1.660000] Freeing init memory: 120K
[    1.670000] kjournald starting.  Commit interval 5 seconds
[    2.870000] kjournald starting.  Commit interval 5 seconds
[    2.870000] EXT3 FS on mmcblk0p5, internal journal
[    2.880000] EXT3-fs: mounted filesystem with journal data mode.
[    3.020000] kjournald starting.  Commit interval 5 seconds
[    3.100000] EXT3 FS on mmcblk0p6, internal journal
[    3.100000] EXT3-fs: mounted filesystem with ordered data mode.
[    3.660000] power_supply ac: uevent
[    3.660000] power_supply ac: POWER_SUPPLY_NAME=ac
[    3.660000] power_supply ac: Static prop TYPE=Mains
[    3.660000] power_supply ac: 2 dynamic props
[    3.660000] power_supply ac: prop ONLINE=1
[    3.660000] power_supply ac: prop TEMP=54
[    3.690000] power_supply battery: uevent
[    3.690000] power_supply battery: POWER_SUPPLY_NAME=battery
[    3.690000] power_supply battery: Static prop TYPE=Battery
[    3.690000] power_supply battery: 9 dynamic props
[    3.690000] power_supply battery: prop STATUS=Not charging
[    3.690000] power_supply battery: prop PRESENT=0
[    3.690000] power_supply battery: prop HEALTH=Good
[    3.690000] power_supply battery: prop TECHNOLOGY=Li-ion
[    3.690000] power_supply battery: prop VOLTAGE_NOW=32000
[    3.690000] power_supply battery: prop VOLTAGE_AVG=3648000
[    3.690000] power_supply battery: prop CURRENT_NOW=0
[    3.690000] power_supply battery: prop TEMP=4025
[    3.690000] power_supply battery: prop CAPACITY=92
[    3.710000] power_supply usb: uevent
[    3.710000] power_supply usb: POWER_SUPPLY_NAME=usb
[    3.710000] power_supply usb: Static prop TYPE=USB
[    3.710000] power_supply usb: 2 dynamic props
[    3.710000] power_supply usb: prop ONLINE=0
[    3.710000] power_supply usb: prop TEMP=55
[    4.120000] Chumby bend sensor driver version 2.3-Falconwing initializing (scross@chumby.com)...
[    4.150000] input: bend-sensor as /devices/platform/bend-sensor/input/input0
[    7.010000] input: STMP3XXX touchscreen as /devices/virtual/input/input1
[    8.220000] mice: PS/2 mouse device common for all mice
[   11.080000] usbcore: registered new interface driver usbfs
[   11.100000] usbcore: registered new interface driver hub
[   11.120000] usbcore: registered new device driver usb
[   11.190000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   11.200000] fsl-ehci fsl-ehci: Freescale On-Chip EHCI Host Controller
[   11.220000] fsl-ehci fsl-ehci: new USB bus registered, assigned bus number 1
[   12.350000] fsl-ehci fsl-ehci: irq 11, io mem 0xf0080000
[   12.370000] fsl-ehci fsl-ehci: USB 2.0 started, EHCI 1.00
[   12.390000] usb usb1: configuration #1 chosen from 1 choice
[   12.390000] hub 1-0:1.0: USB hub found
[   12.400000] hub 1-0:1.0: 1 port detected
[   12.720000] usb 1-1: new high speed USB device using fsl-ehci and address 2
[   12.890000] usb 1-1: configuration #1 chosen from 1 choice
[   12.900000] hub 1-1:1.0: USB hub found
[   12.900000] hub 1-1:1.0: 4 ports detected
[   13.190000] usb 1-1.1: new high speed USB device using fsl-ehci and address 3
[   13.320000] usb 1-1.1: configuration #1 chosen from 1 choice
[   13.330000] hub 1-1.1:1.0: USB hub found
[   13.330000] hub 1-1.1:1.0: 4 ports detected
[   13.480000] usb 1-1.2: new high speed USB device using fsl-ehci and address 4
[   13.670000] usb 1-1.2: config index 0 descriptor too short (expected 32, got 9)
[   13.680000] usb 1-1.2: config 1 has 0 interfaces, different from the descriptor's value: 1
[   13.710000] usb 1-1.2: string descriptor 0 read error: -71
[   13.710000] usb 1-1.2: string descriptor 0 too short
[   13.750000] usb 1-1.2: configuration #1 chosen from 1 choice
[   13.860000] usb 1-1.1.2: new low speed USB device using fsl-ehci and address 5
[   13.990000] usb 1-1.1.2: configuration #1 chosen from 1 choice
[   14.230000] usb 1-1.1.3: new high speed USB device using fsl-ehci and address 6
[   14.410000] usb 1-1.1.3: configuration #1 chosen from 1 choice
[   14.620000] usb 1-1.1.4: new full speed USB device using fsl-ehci and address 7
[   14.630000] input: NOVATEK USB Keyboard as /devices/platform/stmp3xxx-usb/fsl-ehci/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/input/input2
[   14.730000] generic-usb 0003:0461:0010.0001: input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-fsl-ehci-1.1.2/input0
[   14.810000] usb 1-1.1.4: configuration #1 chosen from 1 choice
[   14.840000] input: NOVATEK USB Keyboard as /devices/platform/stmp3xxx-usb/fsl-ehci/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/input/input3
[   14.950000] generic-usb 0003:0461:0010.0002: input: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-fsl-ehci-1.1.2/input1
[   15.000000] usbcore: registered new interface driver usbhid
[   15.000000] usbhid: v2.6:USB HID core driver
[   15.690000] SCSI subsystem initialized
[   15.870000] Initializing USB Mass Storage driver...
[   15.890000] scsi0 : SCSI emulation for USB Mass Storage devices
[   15.940000] usb-storage: device found at 6
[   15.940000] usb-storage: waiting for device to settle before scanning
[   15.940000] usbcore: registered new interface driver usb-storage
[   15.940000] USB Mass Storage support registered.
[   20.290000] cdc_acm 1-1.1.4:1.0: This device cannot do calls on its own. It is no modem.
[   20.300000] cdc_acm 1-1.1.4:1.0: ttyACM0: USB ACM device
[   20.340000] usbcore: registered new interface driver cdc_acm
[   20.340000] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
[   20.850000] i2c /dev entries driver
[   20.950000] scsi 0:0:0:0: Direct-Access     Generic  USB Flash Disk   0.00 PQ: 0 ANSI: 2
[   21.010000] usb-storage: device scan complete
[   21.420000] Driver 'sd' needs updating - please use bus_type methods
[   21.440000] sd 0:0:0:0: [sda] 3948544 512-byte hardware sectors: (2.02 GB/1.88 GiB)
[   21.450000] sd 0:0:0:0: [sda] Write Protect is off
[   21.450000] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
[   21.450000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   21.460000] sd 0:0:0:0: [sda] 3948544 512-byte hardware sectors: (2.02 GB/1.88 GiB)
[   21.480000] sd 0:0:0:0: [sda] Write Protect is off
[   21.480000] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
[   21.480000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   21.490000]  sda:<6>ASoC version 0.13.2
[   22.010000] STMP378X ADC/DAC Audio Codec 0.1
[   22.010000] asoc: stmp378x adc/dac <-> stmp3xxx adc/dac mapping ok
[   22.110000] 
[   22.150000] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   22.370000] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   23.830000] Chumby timerx[2] driver version 3.0-Falconwing initializing (bunnie@chumby.com)... show me your jiffies!!!
[   25.660000] input: stmp3xxx-rotdec as /devices/virtual/input/input4
[   29.940000] NET: Registered protocol family 10
[   62.530000] usb 1-1.1.2: USB disconnect, address 5
[   65.840000] usb 1-1.1.2: new low speed USB device using fsl-ehci and address 8
[   65.970000] usb 1-1.1.2: configuration #1 chosen from 1 choice
[   66.030000] input: NOVATEK USB Keyboard as /devices/platform/stmp3xxx-usb/fsl-ehci/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/input/input5
[   66.120000] generic-usb 0003:0461:0010.0003: input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-fsl-ehci-1.1.2/input0
[   66.220000] input: NOVATEK USB Keyboard as /devices/platform/stmp3xxx-usb/fsl-ehci/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/input/input6
[   66.350000] generic-usb 0003:0461:0010.0004: input: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-fsl-ehci-1.1.2/input1
[   67.280000] Console: switching to colour frame buffer device 80x40
  • Registered: 2010-04-13
  • Posts: 4

Re: Problems connecting to WLAN

FYI:
My Chumby retailer told me to return my chumby to get it replaced.
I did so and got my replacement chumby today. Unfortunately the replacement chumby has exactly the same problem, so I suppose that my first chumby wasn't simply a defective unit and it's a common problem all chumbys would have.
It's a bit annoying, but since the connection seems to be stable once it is up, I guess I can live with it.

My replacement chumby doesn't have a defective pixel like my first one, so in a way I still benefitted from replacing it.

My retailer told me that it's common that the chumby has problems connecting to WLANs, especially if there are many other WLANs in reach. Since this is indeed the case where I live, I guess the problem might have to do with the other WLANs. On the other hand, that doesn't explain why my chumby had problems connecting to my friend's WLAN, because he doesn't have many other WLANs in reach.

Maybe I'll try switching the radio channel that my WLAN access point is using, if it's really the other WLANs causing that problem that might eventually help.

  • From: Australia
  • Registered: 2009-03-19
  • Posts: 503

Re: Problems connecting to WLAN

I had troubles connecting to my WLAN with a couple of Chumbies and found that things improved when I set them to have a static IP address each.
My connection problem was a little different to yours, from what I remember, I don't think I used to get the 'wlan0 link is down' message. However, it won't hurt to give it a try.