Tiny Core Base > TCB Talk

WiFi - Not connecting to access point

<< < (3/13) > >>

coreplayer2:
This is the classic chicken before the egg syndrome. 

I see now your method.  so in this case NO

select only Wifi support and firmware



No need to use Apps in this scenario as all the required extensions are included in the live cd


First, can you connect using the wifi icon whilst booted to the CorePlus live cd ?

lmart:
coreplayer2

#1 - Bootled to LiveCD on desktop and launched TC_Install
#2 - Created tc+ usb-hdd accepting only defaults, no boot options
#3 - On Core+ extensions, selected (a) WiFi support and, (b) Wireless Firmware
#4 - Booted tc+ usb on laptop and launched WiFi
#5 - Same Results - No connection to access point
       scan networks
       send credential to access point
       udhcpc
       failed to connect

Juanito:
What do the last few lines of dmesg say after you fail to connect:
--- Code: ---$ dmesg | tail -20
--- End code ---

lmart:
Juanito
dmesg | tail -20, as requested

intel_rng: FWH not detected
intel_rng: FWH not detected
intel_rng: FWH not detected
ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
lib80211_crypt: registered algorithm 'WEP'
usb 1-1: new high speed USB device number 3 using ehci_hcd
scsi7 : usb-storage 1-1:1.0
scsi 7:0:0:0: Direct-Access     USB 2.0  Flash Disk       8.07 PQ: 0 ANSI: 2
sd 7:0:0:0: Attached scsi generic sg3 type 0
sd 7:0:0:0: [sdc] 511998 512-byte logical blocks: (262 MB/249 MiB)
sd 7:0:0:0: [sdc] Write Protect is off
sd 7:0:0:0: [sdc] Mode Sense: 03 00 00 00
sd 7:0:0:0: [sdc] No Caching mode page present
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] No Caching mode page present
sd 7:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 7:0:0:0: [sdc] No Caching mode page present
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] Attached SCSI removable disk

Juanito:
That looks like what you'd see if the drivers were loaded "onboot" and you have not run the wifi extension script (double-click on wifi icon or "wifi.sh").

I'd expect you would see something like:
--- Code: ---$ dmesg
...
Broadcom 43xx driver loaded [ Features: PLR, Firmware-ID: FW13 ]
firmware: requesting b43/ucode5.fw
firmware: requesting b43/pcm5.fw
firmware: requesting b43/b0g0initvals5.fw
firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
--- End code ---
..with Intel in place of Broadcom

and:
--- Code: ---$ dmesg
...
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
wl 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
wl 0000:02:00.0: setting latency timer to 64
lib80211_crypt: registered algorithm 'TKIP'
eth1: Broadcom BCM4359 802.11 Hybrid Wireless Controller 5.100.82.112
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'

--- End code ---
..with possibly wlan0 or eth0 in place of eth1

Navigation

[0] Message Index

[#] Next page

[*] Previous page