[SOLVED]Penguin Wireless N USB Adapter TPE-N150USBL
wlan0:avahi Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 This also does not happen here. Nor here. The OP's system has failed to get an IP address on the wlan0 interface and has been provided with one by avahi. Maybe the router and/or DHCP provision need exploring as a cause for this. I believe this happened because I applied the command: #ping router-ip-here I don't know if 169.254.10.111 is something that was assigned by the host, or came from outside in which case it might indicate some sort of radio communication has been made. (Hence my statement above.) it was Here's hoping the OP knows how to explore the router and/or DHCP provision. I had set up the router a few months ago to reflect the two channels it delivers, 2.5 and 5.0 GHz respectively. Some of my applications that use the router select 2.5 like a Kobo reader and the Sony PS3. At the moment as WiFi goes only my Sony Xperia phone connects to the 5.0 GHz channel. The OP should be looking at syslog and/or the journalctl output. What avahi-daemon,avahi-autoipd and dhclient get up to should be in there. Posting the relevant lines here could help with a diagnosis and a solution. Thanks for all the suggestions they don't hurt because when looking into one thing something else comes up. I really didn't have a faulty setup for the Penguin USB N type WiFi adapter as I originally thought. I installed a driver from the Penguin site directly into the /lib/firmware directory, the 9k_firmware_free-version/htc_9271.fw I rebooted the computer but this didn't light up the USB adapter. I tried all the available USB sockets and rebooted a few more times, stuff like that, but the Penguin was dead. I was fed up and went to bed shutting off the computer. During the night there was a miraculous like occurrence. When booting up the next morning the 'dead' USB adapter now came on and started trying to connect to the router. Success right? Wrong. Later in the day I was reading about setting up these wireless adapters and ran across this valuable command: #iwlist wlan0 scan by that command all was revealed. There were 19 cells in a 50 yard radius of my adapter (with a hi-gain antenna) including my router but (I guess you've figured it out by now) the adapter or the firmware doesn't 'see' the 5.0-GHz channel. Completely invisible. Only the 2.5 GHz channel was listed in the wlan0 scan. My /etc/network/interfaces file was set up like this: # # # The wireless network interface auto wlan0 iface wlan0 inet dhcp wpa-ssid dlink-5.0GHz what's wrong with this ssid entry wpa-key-mgmt WPA-PSK wpa-psk the passphrase anyway by changing wpa-ssid dlink-5.0GHz to 2.5GHz the adapter connected promptly and voilà. After all that, joy did not manifold. The down speed of the connection was no good. I pay for 20 Mbits from the cable company but..that depends. This is a Debian story. I ran the Ookla speed test (speedtest.net) connected through the Intel Ethernet card in the PCIe slot wired to the back of the router and speedtest did show 21Mbits. (middle of the morning on a business day) 5 minutes after that the best the USB wireless N adapter could do was 7.0 Mbits down speed. I'm looking into a PCIe wireless card duel channel adapter as an upgrade. Any good experiences out there with a particular kind (for desktop computer with PCIe slot) with free or non-free firmware I would like to hear your story. Thanks for the discussion, it's been real -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cra9ulfgog...@mid.individual.net
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Tue 05 May 2015 at 22:02:42 -0500, David Wright wrote: Quoting Charles Kroeger (ckro...@frankensteinface.com): root@mundo:/home/charles# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:1b:21:4f:60:49 inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::21b:21ff:fe4f:6049/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1051 errors:0 dropped:0 overruns:0 frame:0 TX packets:502 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:291611 (284.7 KiB) TX bytes:82072 (80.1 KiB) Interrupt:17 Memory:fbfe-fc00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:55 errors:0 dropped:0 overruns:0 frame:0 TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:15256 (14.8 KiB) TX bytes:15256 (14.8 KiB) wlan0 Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0:avahi Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 inet addr:169.254.10.111 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 root@mundo:/home/charles# lsmod | grep ath ath9k_htc 52702 0 ath9k_common 12687 1 ath9k_htc ath9k_hw 341687 2 ath9k_common,ath9k_htc ath21417 3 ath9k_common,ath9k_htc,ath9k_hw mac80211 358182 1 ath9k_htc cfg80211 319971 3 ath,mac80211,ath9k_htc usbcore 134993 6 usb_storage,ohci_hcd,ehci_hcd,ehci_pci,usbhid,ath9k_htc At this stage, I would run wicd-curses (not as root) and type P. I would make sure the Wireless and Wired Interfaces were correctly named wlan0 and eth0, set automatic reconnection and any other options I wanted, save that, scan for APs with Fn5, select one and press - to configure it. I would remove the ethernet cable because I have that set to take priority. After saving the configuration, I'd press Return and hope to have a wireless connection come up. The wireless interface *does* exist *and* is named wlan0. The modules for the chip are present, The firmware for the device is loaded. All the basic conditions to estabish a connection with e/n/i are met. If there is no connection (which does not happen here with a similar chipset) then there is a deeper problem. wpasupplicant (on which wicd depends for its operation) and four lines in /e/n/i is about as basic as it gets. wlan0:avahi Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 This also does not happen here. The OP's system has failed to get an IP address on the wlan0 interface and has been provided with one by avahi. Maybe the router and/or DHCP provision need exploring as a cause for this. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150506091517.gj3...@copernicus.demon.co.uk
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Wed 06 May 2015 at 14:24:23 -0500, David Wright wrote: Quoting Brian (a...@cityscape.co.uk): wlan0:avahi Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 This also does not happen here. Nor here. The OP's system has failed to get an IP address on the wlan0 interface and has been provided with one by avahi. Maybe the router and/or DHCP provision need exploring as a cause for this. I know nothing about avahi. (Would I be right in thinking that it's something to do with mDNS that I don't need? And that it would be sensible to purge it?) It would be unwise to purge avahi if machines on the network rely on printing services. I don't know if 169.254.10.111 is something that was assigned by the host, or came from outside in which case it might indicate some sort of radio communication has been made. (Hence my statement above.) Here's hoping the OP knows how to explore the router and/or DHCP provision. I'm almost completely unfamiliar with how avahi works in this context. The supplicant and dhclient have always done their jobs for me so there has been no need for me to look into its interaction with ifupdown. The OP should be looking at syslog and/or the journalctl output. What avahi-daemon,avahi-autoipd and dhclient get up to should be in there. Posting the relevant lines here could help with a diagnosis and a solution. I think avahi will assign an address from the link-local 169.254.0.0/16 range if there is no central dhcp server. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150506223234.gk3...@copernicus.demon.co.uk
Re: Penguin Wireless N USB Adapter TPE-N150USBL
Quoting Brian (a...@cityscape.co.uk): On Tue 05 May 2015 at 22:02:42 -0500, David Wright wrote: Quoting Charles Kroeger (ckro...@frankensteinface.com): root@mundo:/home/charles# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:1b:21:4f:60:49 inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::21b:21ff:fe4f:6049/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1051 errors:0 dropped:0 overruns:0 frame:0 TX packets:502 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:291611 (284.7 KiB) TX bytes:82072 (80.1 KiB) Interrupt:17 Memory:fbfe-fc00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:55 errors:0 dropped:0 overruns:0 frame:0 TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:15256 (14.8 KiB) TX bytes:15256 (14.8 KiB) wlan0 Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0:avahi Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 inet addr:169.254.10.111 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 root@mundo:/home/charles# lsmod | grep ath ath9k_htc 52702 0 ath9k_common 12687 1 ath9k_htc ath9k_hw 341687 2 ath9k_common,ath9k_htc ath21417 3 ath9k_common,ath9k_htc,ath9k_hw mac80211 358182 1 ath9k_htc cfg80211 319971 3 ath,mac80211,ath9k_htc usbcore 134993 6 usb_storage,ohci_hcd,ehci_hcd,ehci_pci,usbhid,ath9k_htc At this stage, I would run wicd-curses (not as root) and type P. I would make sure the Wireless and Wired Interfaces were correctly named wlan0 and eth0, set automatic reconnection and any other options I wanted, save that, scan for APs with Fn5, select one and press - to configure it. I would remove the ethernet cable because I have that set to take priority. After saving the configuration, I'd press Return and hope to have a wireless connection come up. The wireless interface *does* exist *and* is named wlan0. The modules for the chip are present, The firmware for the device is loaded. All the basic conditions to estabish a connection with e/n/i are met. Agreed. (Note that when I wrote make sure the Wireless ... Interfaces were correctly named wlan0, this is in the wicd configuration. wlan0 doesn't always get picked up at wicd installation. I don't know why. It may be that an entry in /e/n/i causes it to be ignored for configuration as well as operation.) If there is no connection (which does not happen here with a similar chipset) then there is a deeper problem. Agreed. But I was trying to take one step at a time. I may be wrong but I don't think I've yet seen anything posted that confirms a radio signal being sent or received by the device, eg something from a /sbin/iw... command. A screen showing an access point(s) might inspire confidence, personally. (You're obviously familiar with the chipset whereas I'm not.) wpasupplicant (on which wicd depends for its operation) and four lines in /e/n/i is about as basic as it gets. I guess we need to see what wpa_supplicant says now that there's a wlan0 to operate on. Hopefully more than /sbin/wpa_supplicant daemon failed to start. wlan0:avahi Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 This also does not happen here. Nor here. The OP's system has failed to get an IP address on the wlan0 interface and has been provided with one by avahi. Maybe the router and/or DHCP provision need exploring as a cause for this. I know nothing about avahi. (Would I be right in thinking that it's something to do with mDNS that I don't need? And that it would be sensible to purge it?) I don't know if 169.254.10.111 is something that was assigned by the host, or came from outside in which case it might indicate some sort of radio communication has been made. (Hence my statement above.) Here's hoping the OP knows how to explore the router and/or DHCP provision. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150506192423.GA12225@alum
Re: Penguin Wireless N USB Adapter TPE-N150USBL
Quoting Charles Kroeger (ckro...@frankensteinface.com): On Tue, 05 May 2015 04:00:02 +0200 David Wright deb...@lionunicorn.co.uk wrote: Does dmesg | grep -i firmware show the firmware being loaded? root@mundo:/home/charles# dmesg | grep -i firmware[1.400040] platform microcode: firmware: agent loaded amd-ucode/microcode_amd.bin into memry[ 25.257358] usb 7-2: ath9k_htc: Firmware htc_9271.fw requested[ 25.268624] usb 7-2: firmware: agent loaded htc_9271.fw into memoryroot@mundo:/home/charles# Yes it's there, the ath9k_htc_9271.fw What do /sbin/iwconfig and /sbin/ifconfig show? Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150505130437.GA5597@alum
Re: Penguin Wireless N USB Adapter TPE-N150USBL
Quoting Charles Kroeger (ckro...@frankensteinface.com): root@mundo:/home/charles# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:1b:21:4f:60:49 inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::21b:21ff:fe4f:6049/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1051 errors:0 dropped:0 overruns:0 frame:0 TX packets:502 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:291611 (284.7 KiB) TX bytes:82072 (80.1 KiB) Interrupt:17 Memory:fbfe-fc00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:55 errors:0 dropped:0 overruns:0 frame:0 TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:15256 (14.8 KiB) TX bytes:15256 (14.8 KiB) wlan0 Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0:avahi Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 inet addr:169.254.10.111 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 root@mundo:/home/charles# lsmod | grep ath ath9k_htc 52702 0 ath9k_common 12687 1 ath9k_htc ath9k_hw 341687 2 ath9k_common,ath9k_htc ath21417 3 ath9k_common,ath9k_htc,ath9k_hw mac80211 358182 1 ath9k_htc cfg80211 319971 3 ath,mac80211,ath9k_htc usbcore 134993 6 usb_storage,ohci_hcd,ehci_hcd,ehci_pci,usbhid,ath9k_htc At this stage, I would run wicd-curses (not as root) and type P. I would make sure the Wireless and Wired Interfaces were correctly named wlan0 and eth0, set automatic reconnection and any other options I wanted, save that, scan for APs with Fn5, select one and press - to configure it. I would remove the ethernet cable because I have that set to take priority. After saving the configuration, I'd press Return and hope to have a wireless connection come up. It's too long since I bothered to configure all this through /etc/network/interfaces, which reminds me: for wicd to manage the network, you should comment all but auto lo iface lo inet loopback in that file. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150506030242.GA20972@alum
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Wed, 06 May 2015 01:10:02 +0200 Brian a...@cityscape.co.uk wrote: Please post the outputs of ifconfig -a and lsmod | grep ath root@mundo:/home/charles# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:1b:21:4f:60:49 inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::21b:21ff:fe4f:6049/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1051 errors:0 dropped:0 overruns:0 frame:0 TX packets:502 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:291611 (284.7 KiB) TX bytes:82072 (80.1 KiB) Interrupt:17 Memory:fbfe-fc00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:55 errors:0 dropped:0 overruns:0 frame:0 TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:15256 (14.8 KiB) TX bytes:15256 (14.8 KiB) wlan0 Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0:avahi Link encap:Ethernet HWaddr 00:c0:ca:72:68:d4 inet addr:169.254.10.111 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 root@mundo:/home/charles# lsmod | grep ath ath9k_htc 52702 0 ath9k_common 12687 1 ath9k_htc ath9k_hw 341687 2 ath9k_common,ath9k_htc ath21417 3 ath9k_common,ath9k_htc,ath9k_hw mac80211 358182 1 ath9k_htc cfg80211 319971 3 ath,mac80211,ath9k_htc usbcore 134993 6 usb_storage,ohci_hcd,ehci_hcd,ehci_pci,usbhid,ath9k_htc -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cqt5tnft2i...@mid.individual.net
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Tue 05 May 2015 at 17:10:31 -0400, Charles Kroeger wrote: On Tue, 05 May 2015 21:30:02 +0200 Brian a...@cityscape.co.uk wrote: You could try ifconfig wlan0 up to activate the interface before following the remainder of the advice given. I tried that but it complained about not being able to find wlan0 Please post the outputs of ifconfig -a and lsmod | grep ath -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/0605201526.33c8d3d65...@desktop.copernicus.demon.co.uk
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Tue, 05 May 2015 15:10:02 +0200 David Wright deb...@lionunicorn.co.uk wrote: What do /sbin/iwconfig and /sbin/ifconfig show? ^?ELF^B^A^A^@^@^@^@^@^@^@^@^@^B^@^@^A^@^@^@\^Y@^@^@^@^@^@@^@^@^@^@^@^@^@Xb^@^@^@^@^@^@^@^@^@^@@^@8^@ ^@@^@^\^@^[^@^F^@^@^@^E^@^@^@@^@^@^@^@^@^@^@@^@@^@^@^@^@^@@^@@^@^@^@^@^@ø^A^@^@^@^@^@^@ø^A^@^@^@^@^@^@^H^@^@^@^@^@^@^@^C^@^@^@^D^@^@^@8^B^@^@^@^@^@^@8^B@^@^@^@^@^@8^B@^@^@^@^@^@^\^@^@^@^@^@^@^@^\^@^@^@^@^@^@^@^A^@^@^@^@^@^@^@^A^@^@^@^E^@^@^@^@^@^@^@^@^@^@^@^@^@@^@^@^@^@^@^@^@@^@^@^@^@^@8cX^@^@^@^@^@^@8cX^@^@^@^@^@^@^@^@ ^@^@^@^@^@^A^@^@^@^F^@^@^@^H^^@^@^@^@^@^@^H^`^@^@^@^@^@^H^`^@^@^@^@^@h^C^@^@^@^@^@^@X^E^@^@^@^@^@^@^@^@ ^@^@^@^@^@^B^@^@^@^F^@^@^@0^^@^@^@^@^@^@0^`^@^@^@^@^@0^`^@^@^@^@^@°^A^@^@^@^@^@^@°^A^@^@^@^@^@^@^H^@^@^@^@^@^@^@^D^@^@^@^D^@^@^@T^B^@^@^@^@^@^@T^B@^@^@^@^@^@T^B@^@^@^@^@^@D^@^@^@^@^@^@^@D^@^@^@^@^@^@^@^D^@^@^@^@^@^@^@Påtd^D^@^@^@(S^@^@^@^@^@^@(S@^@^@^@^@^@(S@^@^@^@^@^@¼^@^@^@^@^@^@^@¼^@^@^@^@^@^@^@^D^@^@^@^@^@^@^@Qåtd^F^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^H^@^@^@^@^@^@^@Råtd^D^@^@^@^H^^@^@^@^@^@^@^H^`^@^@^@^@^@^H^`^@^@^@^@^@ø^A^@^@^@^@^@^@ø^A^@^@^@^@^@^@^A^@^@^@^@^@^@^@/lib64/ld-linux-x86-64.so.2^@^D^@^@^@^P^@^@^@^A^@^@^@GNU^@^@^@^@^@^B^@^@^@^F^@^@^@^Z^@^@^@^D^@^@^@^T^@^@^@^C^@^@^@GNU^@94T¡V8d7Í¡8c86^E97V^ZX¦ÒÜä%^@^@^@7^@^@^@^@^@^@^@'^@^@^@^@^@^@^@+^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ @ @ @ @ @ @ @ @ /sbin/iwconfig [noeol][converted] 56L, 33541C ^?ELF^B^A^A^@^@^@^@^@^@^@^@^@^B^@^@^A^@^@^@¾7@^@^@^@^@^@@^@^@^@^@^@^@^@H^D^A^@^@^@^@^@^@^@^@^@@^@8^@ ^@@^@^[^@^Z^@^F^@^@^@^E^@^@^@@^@^@^@^@^@^@^@@^@@^@^@^@^@^@@^@@^@^@^@^@^@ø^A^@^@^@^@^@^@ø^A^@^@^@^@^@^@^H^@^@^@^@^@^@^@^C^@^@^@^D^@^@^@8^B^@^@^@^@^@^@8^B@^@^@^@^@^@8^B@^@^@^@^@^@^\^@^@^@^@^@^@^@^\^@^@^@^@^@^@^@^A^@^@^@^@^@^@^@^A^@^@^@^E^@^@^@^@^@^@^@^@^@^@^@^@^@@^@^@^@^@^@^@^@@^@^@^@^@^@84ë^@^@^@^@^@^@84ë^@^@^@^@^@^@^@^@ ^@^@^@^@^@^A^@^@^@^F^@^@^@^Pî^@^@^@^@^@^@^Pî`^@^@^@^@^@^Pî`^@^@^@^@^@H^U^@^@^@^@^@^@98#^@^@^@^@^@^@^@^@ ^@^@^@^@^@^B^@^@^@^F^@^@^@(î^@^@^@^@^@^@(î`^@^@^@^@^@(î`^@^@^@^@^@Ð^A^@^@^@^@^@^@Ð^A^@^@^@^@^@^@^H^@^@^@^@^@^@^@^D^@^@^@^D^@^@^@T^B^@^@^@^@^@^@T^B@^@^@^@^@^@T^B@^@^@^@^@^@D^@^@^@^@^@^@^@D^@^@^@^@^@^@^@^D^@^@^@^@^@^@^@Påtd^D^@^@^@¼Î^@^@^@^@^@^@¼Î@^@^@^@^@^@¼Î@^@^@^@^@^@ô^C^@^@^@^@^@^@ô^C^@^@^@^@^@^@^D^@^@^@^@^@^@^@Qåtd^F^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^P^@^@^@^@^@^@^@Råtd^D^@^@^@^Pî^@^@^@^@^@^@^Pî`^@^@^@^@^@^Pî`^@^@^@^@^@ð^A^@^@^@^@^@^@ð^A^@^@^@^@^@^@^A^@^@^@^@^@^@^@/lib64/ld-linux-x86-64.so.2^@^D^@^@^@^P^@^@^@^A^@^@^@GNU^@^@^@^@^@^B^@^@^@^F^@^@^@ ^@^@^@^D^@^@^@^T^@^@^@^C^@^@^@GNU^@^S^_9hjMOö«©_Òv.³£Q85J¤^B^@^@^@K^@^@^@^A^@^@^@^F^@^@^@^@^A^@^@^@^@^@^B^@^@^@^@K^@^@^@9ò8b^\^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^M^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@83^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@8c^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@×^A^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Í^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Â^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@·^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@8e^A^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Ç^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^R^A^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@96^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@@^@^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@²^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@I^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@q^B^@^@^R^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ /sbin/ifconfig [noeol][converted] 320L, 87918C Are you a machine that's got loose out there and posing as a good natured Englishman? -- CK and /sbin/ifconfig show? Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cqsiejfo65...@mid.individual.net
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Tue, 05 May 2015 12:10:02 +0200 Brian a...@cityscape.co.uk wrote: The non-free firmware-atheros package has the firmware for the adapter. I have the 'firmware-atheros' package installed. I take it that's the free non-working version of the non-free package I have non-free sources in my sources.list wonder why it didn't show up? You don't have a location for this do you? I'll also have a look out there. Thanks for the suggestion. That may solve the problem. -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cqshlefo65...@mid.individual.net
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Tue 05 May 2015 at 14:49:18 -0400, Charles Kroeger wrote: On Tue, 05 May 2015 12:10:02 +0200 Brian a...@cityscape.co.uk wrote: The non-free firmware-atheros package has the firmware for the adapter. I have the 'firmware-atheros' package installed. I take it that's the free non-working version of the non-free package I have non-free sources in my sources.list wonder why it didn't show up? You don't have a location for this do you? I'll also have a look out there. Thanks for the suggestion. That may solve the problem. I mentioned firmware-atheros because it is in the Debian archives and not because getting the firmware file your adapter needs from elsewhere is a problem. In fact, I don't believe what you have is a problem. You could try ifconfig wlan0 up to activate the interface before following the remainder of the advice given. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/05052015201449.b01cf93a2...@desktop.copernicus.demon.co.uk
Re: Penguin Wireless N USB Adapter TPE-N150USBL
Quoting Charles Kroeger (ckro...@frankensteinface.com): On Tue, 05 May 2015 15:10:02 +0200 David Wright deb...@lionunicorn.co.uk wrote: What do /sbin/iwconfig and /sbin/ifconfig show? ^?ELF^B [...] Perhaps I wasn't clear! iwconfig and ifconfig are programs that you run. Because /sbin isn't in the user's $PATH, you need to prefix with the pathname. You might see output like wlan0 IEEE 802.11abg ESSID:foo Mode:Managed Frequency:2.462 GHz Access Point: 44:... Bit Rate=54 Mb/s Tx-Power=15 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=69/70 Signal level=-41 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:59 Missed beacon:0 lono wireless extensions. eth0 no wireless extensions. and loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:1131 errors:0 dropped:0 overruns:0 frame:0 TX packets:1131 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:101396 (99.0 KiB) TX bytes:101396 (99.0 KiB) wlan0 Link encap:Ethernet HWaddr 00:... inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80.../64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:481394 errors:0 dropped:0 overruns:0 frame:0 TX packets:393808 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:362857903 (346.0 MiB) TX bytes:61878630 (59.0 MiB) Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150505202606.GA13802@alum
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Mon 04 May 2015 at 19:39:33 -0400, Charles Kroeger wrote: After using this adapter for a few months (18 months ago) I committed out all my wireless lines in /etc/network/interfaces and stopped using it because it kept breaking the connection at odd times. I have to take a trip and this computer goes with me where I'll need to use WiFi and so I uncommitted out my network interfaces file, loaded the firmware (from the think penguin help site) plugged in the adapter but nothing happens. The non-free firmware-atheros package has the firmware for the adapter. # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp auto wlan0 I'd be inclined to have 'allow-hotplug wlan0'. iface wlan0 inet dhcp wpa-ssid my ssid, a dlink-dir825 wpa-psk my passphrase I followed these instructions for the latest firmware at the think penguin help site for this adapter: cd /lib/firmware wget https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_9271.fw wget https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_7010.fw rebooted the computer however..the adapter is still not connected It's very surprising a reboot didn't bring up the interface. this after ifup wlan0: # ifup wlan0 wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 Failed to bring up wlan0. any suggestions to what might be missing here? Most of the on-screen message you saw? :) Check if the supplicant is running; 'ps ax | grep wpa'. Terminate it with 'wpa_cli terminate'. Retry 'ifup wlan0'. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/05052015105754.eb9ae86d3...@desktop.copernicus.demon.co.uk
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Tue, 05 May 2015 22:30:02 +0200 David Wright deb...@lionunicorn.co.uk wrote: Perhaps I wasn't clear! iwconfig and ifconfig are programs that you run. Because /sbin isn't in the user's $PATH, you need to prefix with the pathname. I get this from #ifconfig root@mundo:/home/charles# ifconfig eth0 Link encap:Ethernet HWaddr 00:1b:21:4f:60:49 inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::21b:21ff:fe4f:6049/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21946 errors:0 dropped:0 overruns:0 frame:0 TX packets:12589 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12859474 (12.2 MiB) TX bytes:1590982 (1.5 MiB) Interrupt:17 Memory:fbfe-fc00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:72 errors:0 dropped:0 overruns:0 frame:0 TX packets:72 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:17302 (16.8 KiB) TX bytes:17302 (16.8 KiB) and this from #iwconfig root@mundo:/home/charles# iwcofig bash: iwcofig: command not found root@mundo:/home/charles# iwconfig eth0 no wireless extensions. lono wireless extensions. Thanks for the suggestion David, just fun'in you there. -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cqsqj2fo65...@mid.individual.net
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Tue, 05 May 2015 21:30:02 +0200 Brian a...@cityscape.co.uk wrote: You could try ifconfig wlan0 up to activate the interface before following the remainder of the advice given. I tried that but it complained about not being able to find wlan0 -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cqspu7fo65...@mid.individual.net
Re: Penguin Wireless N USB Adapter TPE-N150USBL
Quoting Charles Kroeger (ckro...@frankensteinface.com): On Tue, 05 May 2015 21:30:02 +0200 Brian a...@cityscape.co.uk wrote: You could try ifconfig wlan0 up to activate the interface before following the remainder of the advice given. I tried that but it complained about not being able to find wlan0 That was the idea behind running iwconfig and ifconfig with no arguments: to see if there was a wireless interface present. There's always the possibility that it's called something silly like eth1. After this step, I think I'd rmmod and modprobe the kernel module and watch kern.log for messages to see if it finds anything. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150505214940.GA15504@alum
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Tue, 05 May 2015 04:00:02 +0200 David Wright deb...@lionunicorn.co.uk wrote: Does dmesg | grep -i firmware show the firmware being loaded? root@mundo:/home/charles# dmesg | grep -i firmware[1.400040] platform microcode: firmware: agent loaded amd-ucode/microcode_amd.bin into memry[ 25.257358] usb 7-2: ath9k_htc: Firmware htc_9271.fw requested[ 25.268624] usb 7-2: firmware: agent loaded htc_9271.fw into memoryroot@mundo:/home/charles# Yes it's there, the ath9k_htc_9271.fw might be the adapter is kaputski -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cqqr55fahb...@mid.individual.net
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On Tue, 05 May 2015 03:10:01 +0200 James bjloc...@lockie.ca wrote: What is the output from sudo lsusb? root@mundo:/home/charles# lsusb Bus 007 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n that's it there David Wright ask: Do you use anything like wicd to manage the connection, ie bring it back up automatically? no bit of a mystery. -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cqqqr4fahb...@mid.individual.net
Re: Penguin Wireless N USB Adapter TPE-N150USBL
On 05/04/2015 07:39 PM, Charles Kroeger wrote: After using this adapter for a few months (18 months ago) I committed out all my wireless lines in /etc/network/interfaces and stopped using it because it kept breaking the connection at odd times. I have to take a trip and this computer goes with me where I'll need to use WiFi and so I uncommitted out my network interfaces file, loaded the firmware (from the think penguin help site) plugged in the adapter but nothing happens. # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp auto wlan0 iface wlan0 inet dhcp wpa-ssid my ssid, a dlink-dir825 wpa-psk my passphrase I followed these instructions for the latest firmware at the think penguin help site for this adapter: cd /lib/firmware wget https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_9271.fw wget https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_7010.fw rebooted the computer however..the adapter is still not connected this after ifup wlan0: # ifup wlan0 wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 Failed to bring up wlan0. any suggestions to what might be missing here? The thinkpenquin wireless N USB adapter bears a remarkable resemblance to the Alfa wireless USB adapter: :-) https://tinyurl.com/n98oajh What is the output from sudo lsusb? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5548160a.5060...@lockie.ca
Penguin Wireless N USB Adapter TPE-N150USBL
After using this adapter for a few months (18 months ago) I committed out all my wireless lines in /etc/network/interfaces and stopped using it because it kept breaking the connection at odd times. I have to take a trip and this computer goes with me where I'll need to use WiFi and so I uncommitted out my network interfaces file, loaded the firmware (from the think penguin help site) plugged in the adapter but nothing happens. # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp auto wlan0 iface wlan0 inet dhcp wpa-ssid my ssid, a dlink-dir825 wpa-psk my passphrase I followed these instructions for the latest firmware at the think penguin help site for this adapter: cd /lib/firmware wget https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_9271.fw wget https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_7010.fw rebooted the computer however..the adapter is still not connected this after ifup wlan0: # ifup wlan0 wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 Failed to bring up wlan0. any suggestions to what might be missing here? The thinkpenquin wireless N USB adapter bears a remarkable resemblance to the Alfa wireless USB adapter: :-) https://tinyurl.com/n98oajh -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cqqe9mf8a1...@mid.individual.net
Re: Penguin Wireless N USB Adapter TPE-N150USBL
Quoting Charles Kroeger (ckro...@frankensteinface.com): After using this adapter for a few months (18 months ago) I committed out all my wireless lines in /etc/network/interfaces and stopped using it because it kept breaking the connection at odd times. Do you use anything like wicd to manage the connection, ie bring it back up automatically? I followed these instructions for the latest firmware at the think penguin help site for this adapter: cd /lib/firmware wget https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_9271.fw wget https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_7010.fw rebooted the computer however..the adapter is still not connected Does dmesg | grep -i firmware show the firmware being loaded? Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150505015832.GA21916@alum
