network interface in Slacko 5.3.3 and Racy 5.3 ?
network interface in Slacko 5.3.3 and Racy 5.3 ?
I have a micro usb wifi adapter. uses rtl8192cu driver which the kernel of these packages support. The adapter is a Netgear G54/N150 WNA1000M
On my initial network setup it scans the environment and see my ESSID. I select it on the wlan0 configuratoin, enter my WPA2 password. Save the profile and then select use this one. It doesn't connect. Which I didn't find totally unusual.
However when I reinter the interface and Scan the area it doesn't see anything, no other networks.
It there a script fault somewhere, why does it not see the other networks again?
Does not this interface accept a WPA2 configuration.
Thanks in advance.
On my initial network setup it scans the environment and see my ESSID. I select it on the wlan0 configuratoin, enter my WPA2 password. Save the profile and then select use this one. It doesn't connect. Which I didn't find totally unusual.
However when I reinter the interface and Scan the area it doesn't see anything, no other networks.
It there a script fault somewhere, why does it not see the other networks again?
Does not this interface accept a WPA2 configuration.
Thanks in advance.
network interface in Racy 5.3
Per you instructions attached are read outs for lspic -nn and dmesg
It appears that the driver and firmware are loaded as you indicate, but the interface still works weird.
Thanks for you suggestion and time.
It appears that the driver and firmware are loaded as you indicate, but the interface still works weird.
Thanks for you suggestion and time.
- Attachments
-
- netfile.zip
- (13.6 KiB) Downloaded 655 times
lspci didnt list your wireless. Could you try lsusb command. I would like to get ID code of your wireless. Dmesg shows that it is loaded. If you try to scan and you get your network shown in SNS.....could you run dmesg again.
Also running pmodemdiag after scanning networks gathers and packages a lot useful diagnostic and debug files in compressed ready package. You could attach it.
Some people have got working results with Frisbee when SNS fails.
Also running pmodemdiag after scanning networks gathers and packages a lot useful diagnostic and debug files in compressed ready package. You could attach it.
Some people have got working results with Frisbee when SNS fails.
network Interface Racy 5.3 status 07/11/12
Per you instructions here is a updated list of documents with some more info for you to examine and digest.
The interface initially reports "Unable to establish WPA connection"
I am using a USB 1.1 port if that makes any difference.
Thanks.
The interface initially reports "Unable to establish WPA connection"
I am using a USB 1.1 port if that makes any difference.
Thanks.
- Attachments
-
- status1.zip
- (168.71 KiB) Downloaded 611 times
I checked from my kernel 3.4.2 kernel sources: /kernel_sources-3.4.2-dpup/usr/src/linux/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
{RTL_USB_DEVICE(0x0846, 0x9041, rtl92cu_hal_cfg)}, /*NetGear WNA1000M*/
0x0846, 0x9041
Yeah. My latest kernel has support for it. I dont have kernel sources for Racy or Slacko, so I cant check the support in those kernels for that ID, but it loads so...I suppose the support is right.
I think Slacko has Frisbee in Slickpet or in PPM. Install it and test.
Another test could be that you download my latest dpup with 3.4.2 kernel. It has fairly recent rtl8192cu module with needed firmware and firmware.dep linking...and Frisbee preinstalled. I suggest it just that you could test that if it is possible to establish the connection.
Also....running pmodemdiag in console and attaching the created package here would help.
{RTL_USB_DEVICE(0x0846, 0x9041, rtl92cu_hal_cfg)}, /*NetGear WNA1000M*/
0x0846, 0x9041
Yeah. My latest kernel has support for it. I dont have kernel sources for Racy or Slacko, so I cant check the support in those kernels for that ID, but it loads so...I suppose the support is right.
I think Slacko has Frisbee in Slickpet or in PPM. Install it and test.
Another test could be that you download my latest dpup with 3.4.2 kernel. It has fairly recent rtl8192cu module with needed firmware and firmware.dep linking...and Frisbee preinstalled. I suggest it just that you could test that if it is possible to establish the connection.
Also....running pmodemdiag in console and attaching the created package here would help.
netwrok interface Racy 5.3 test
Thanks for checking out the data, I will download your dpup and see what happens :)
Hopefully good things. Wifi connections can be tricky. I recall I went through various hoops when I was using 2.15CE to get a wifi card to work :)
Hopefully good things. Wifi connections can be tricky. I recall I went through various hoops when I was using 2.15CE to get a wifi card to work :)
network interface in Racy 5.3
I downloaded your Dpup Squeeze, second verse same as the first, same behaviour using the Internet Connect Wizard and the Frisbee interface.
network interface Racy 5.3
I am about to give up. I opened up the wireless router briefly to see if the connect would work.
It saw it claimed to connect, then when I attempted to browse nothing.
when I went to rescan again it didn't see any ESSID at all like before.
I am concluding that the Network interface is broken it should have not difficulty handshaking an open wireless connection I would think.
I will get back to you on the wirless adapter diagnostics.
It saw it claimed to connect, then when I attempted to browse nothing.
when I went to rescan again it didn't see any ESSID at all like before.
I am concluding that the Network interface is broken it should have not difficulty handshaking an open wireless connection I would think.
I will get back to you on the wirless adapter diagnostics.
Well, you got ip address from dhcpcd, and there is attempt to connect but then the wireless has been released. Something goes wrong. I didnt find anything spesific. Someone more experienced is needed.Jul 12 04:17:53 puppypc9071 user.info kernel: [ 122.847701] rtl8192c: Loading firmware file rtlwifi/rtl8192cufw.bin
Jul 12 04:17:53 puppypc9071 user.debug kernel: [ 123.434630] wlan0: authenticate with 00:15:ff:0f:75:fd (try 1)
Jul 12 04:17:53 puppypc9071 user.debug kernel: [ 123.451680] wlan0: authenticated
Jul 12 04:17:53 puppypc9071 user.debug kernel: [ 123.451753] wlan0: associate with 00:15:ff:0f:75:fd (try 1)
Jul 12 04:17:53 puppypc9071 user.debug kernel: [ 123.501231] wlan0: RX AssocResp from 00:15:ff:0f:75:fd (capab=0x421 status=0 aid=1)
Jul 12 04:17:53 puppypc9071 user.debug kernel: [ 123.501239] wlan0: associated
Jul 11 13:17:55 puppypc9071 daemon.info dhcpcd[4306]: version 5.2.12 starting
Jul 11 13:17:55 puppypc9071 daemon.info dhcpcd[4306]: wlan0: broadcasting for a lease
Jul 11 13:17:55 puppypc9071 daemon.info dhcpcd[4306]: wlan0: offered 192.168.6.2 from 192.168.6.1
Jul 11 13:17:55 puppypc9071 daemon.info dhcpcd[4306]: wlan0: acknowledged 192.168.6.2 from 192.168.6.1
Jul 11 13:17:55 puppypc9071 daemon.info dhcpcd[4306]: wlan0: checking for 192.168.6.2
Jul 11 13:17:59 puppypc9071 daemon.info dhcpcd[4306]: wlan0: leased 192.168.6.2 for 86400 seconds
Jul 11 13:18:00 puppypc9071 daemon.info dhcpcd[4306]: forked to background, child pid 4401
Jul 12 04:18:09 puppypc9071 user.info kernel: [ 138.974319] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 12 04:18:09 puppypc9071 user.info kernel: [ 139.024306] nf_conntrack version 0.5.0 (16026 buckets, 64104 max)
Jul 12 04:19:43 puppypc9071 user.debug kernel: [ 232.805971] wlan0: deauthenticating from 00:15:ff:0f:75:fd by local choice (reason=3)
Jul 12 04:19:43 puppypc9071 user.info kernel: [ 232.806200] cfg80211: Calling CRDA for country: US
Jul 11 13:19:43 puppypc9071 daemon.info dhcpcd[4401]: wlan0: carrier lost
Jul 11 13:19:43 puppypc9071 daemon.info dhcpcd[6125]: sending signal 1 to pid 4401
Jul 11 13:19:43 puppypc9071 daemon.info dhcpcd[6125]: waiting for pid 4401 to exit
Jul 11 13:19:43 puppypc9071 daemon.info dhcpcd[4401]: received SIGHUP, releasing
network Racy 5.3
it appears that the adapter is querying the CRDA database and doesn't find a match so it closes the connection.
Well... you could create a match.
Create text file /etc/default/crda and place in it your country code. This is quote I found:
Create text file /etc/default/crda and place in it your country code. This is quote I found:
Just to let you guys know i found an easier fix for this on ubuntu 12.04 LTS.
Just go to /etc/default/ and edit the crda file to REGDOMAIN=GB or whatever country code you like.
Hope this helps.
I found also this post about crda. Not sure how relevant it is to your problem. But the country code setting seems also affects to what channels you are allowed to use.
http://www.brokenhomeboy.co.uk/pierow/b ... to-fix-it/
http://www.brokenhomeboy.co.uk/pierow/b ... to-fix-it/
-
- Posts: 242
- Joined: Tue 26 Jan 2010, 19:37
- Location: Florida
For what it is worth, I had the same exact issue (even how the network manager found it the first time then never again), and here are links to my documentation of it and solution. The realtek driver included (rtl8192cu) in Racy 5.3 does not work. One has to get the updated driver for linux from the realtek site and compile it. Both threads I link to document my exact process from start to finish, including links to the download on realtek's site, links to the dev packages needed to install if you want to compile, and easy instructions how to do so.
http://murga-linux.com/puppy/viewtopic. ... 997#627997
http://puppylinux.info/topic/racy-53-ke ... ver-needed
The only thing I don't think I mentioned in either of those threads is that the original included rtl8192 driver seemed to keep getting loaded even after blacklisting it so I ended up just deleting it, removing it, as I use a frugal install, not a live cd.
I made a .pet package of the newly compiled driver yesterday but I'm not sure if it works as I already had installed the driver a couple months ago when I first took up this issue. Plus I have no idea where to upload it to. And it was my first .pet creation ever.
A side note: Frisbee works great with Racy and this driver.
xpupsay:
http://www.murga-linux.com/puppy/viewto ... h&id=37528
then:
http://ftp.nluug.nl/ftp/pub/os/Linux/di ... 2-spup.pet
(From here: http://murga-linux.com/puppy/viewtopic. ... 001#629001 )
Second side note: I've already been talking about this with ndujoe1 and sent him the .pet but I'm posting this so anyone else reading this knows what's going on as well and can try my solution.
Third side note: I wonder if you are running from live cd, frugal, or full install? And I also wonder if that could make for a problem, especially if it is a live cd. (I've never tinkered with wireless on live cd before either so can't offer anything on that if it is different).
http://murga-linux.com/puppy/viewtopic. ... 997#627997
http://puppylinux.info/topic/racy-53-ke ... ver-needed
The only thing I don't think I mentioned in either of those threads is that the original included rtl8192 driver seemed to keep getting loaded even after blacklisting it so I ended up just deleting it, removing it, as I use a frugal install, not a live cd.
I made a .pet package of the newly compiled driver yesterday but I'm not sure if it works as I already had installed the driver a couple months ago when I first took up this issue. Plus I have no idea where to upload it to. And it was my first .pet creation ever.
A side note: Frisbee works great with Racy and this driver.
xpupsay:
http://www.murga-linux.com/puppy/viewto ... h&id=37528
then:
http://ftp.nluug.nl/ftp/pub/os/Linux/di ... 2-spup.pet
(From here: http://murga-linux.com/puppy/viewtopic. ... 001#629001 )
Second side note: I've already been talking about this with ndujoe1 and sent him the .pet but I'm posting this so anyone else reading this knows what's going on as well and can try my solution.
Third side note: I wonder if you are running from live cd, frugal, or full install? And I also wonder if that could make for a problem, especially if it is a live cd. (I've never tinkered with wireless on live cd before either so can't offer anything on that if it is different).