(old)Puppy Linux Discussion Forum

Here is patched rt2800pci module.
It includes pinstall.sh script, which unloads previous rt2800pci, and loads the new one.

Cheers and please give feedback if this one fixes the connection problem.

Thank you a lot!!!
I will try and send feedback!!

It would be helpful if you first provided an update on your blacklisting situation.

Rapidly getting nowhere. Can blacklist from the menu/system/Boot...
Can then modprobe or LOAD it back in again, but,
a) it thinks it's WEP only, maybe it is, - I have WEP switch off in my router and don't want to switch it back on.
b) can't find your earlier reference to an rt28x0 alternative and there doesn't seem to be one available for loading
We are now well beyond my pay-grade in SW manipulation... (try cosmology, medicine, politics?)

It worked!! Thank you so much!! Puppy linux community is awesome!!!!

dam973. Great. I am relieved that the patched rt28000pci worked. If it is not too much work, could you post again the pmodemdiag tarball so that I can confirm that the error message has dissapeared from kernel messages. If it has, I will include the patched driver to the next Upup Precise.

There has been request of rt2800usb fix also. I dont know what is the problem in Sage`s case. I checked the thread of rt2800usb patches and there seems to bunch of them. Depending of the problem.

It would need much better explanation of what is the problem....and in such dialect that it is understandable. My comprehension of Sage`s case lacks the description of the problem. Other thread followers probably know better...

Anyway pmodemdiag tarball would help a lot.

There has been request of rt2800usb fix also. I dont know what is the problem in Sage`s case. I checked the thread of rt2800usb patches and there seems to bunch of them. Depending of the problem.
It would need much better explanation of what is the problem....and in such dialect that it is understandable. My comprehension of Sage`s case lacks the description of the problem. Other thread followers probably know better...
Anyway pmodemdiag tarball would help a lot.

Sorry, I have no idea what you are driving at or your intent. Since I am a sometime editor in my language, it would appear that there is a chasm in comprehension. This doesn't exist with my other Scandinavian friends. Goddag, hur jor ni?!

Oh yes, the rt2800usb doesn't work, as indicated. What else should one say?

Oh yes, the rt2800usb doesn't work, as indicated. What else should one say?

Anyway pmodemdiag tarball would help a lot.

Anyway pmodemdiag tarball would help a lot.

That's the problem. I don't have a clue what that means. Generally I don't mess with SW, it's just not within my ambit, as I said above and many, many times before.

Sage,

So, it's your chasm in comprehension.

Jasper

Always guarantee this Jerk or his side-kick will pop-up for a cheap laugh at someone else's expense. Can't think why John keeps that pair in tow. OK, I'm an advocate of free speech.
Anyone here want some coaching in Physics, Chemistry, Biology, Medicine, Heavy Engineering, Quantum Theory - but NOT SOFTWARE - how many times do I have to tell this Jerk. I don't like it, I don't speak it, I don't do it.
If we had a decent moderator, we wouldn't get these inappropriate interventions, whatever their aliases.

.

reserved

In the Pinboard click Console icon. Type in it: pmodemdiag. The tarball something like pmodemdiag-20121216.tar.gz will be created to the /root.
Attach that file to your post here when you next time post something in this thread.

The debugging information provided by diagnostic data is essential to those people who does not have working crystal ball in the table and talent to see into it. Lol.

Dobre den!

Sage. You have:
Manufacturer=Ralink
Product=802.11 n WLAN
VendorID=148f ProductID=2870 KERNEL-DRIVER(builtin)=(none) > should show kernel driver info here.

...which means the kernel included rt2800usb is the driver for it. But you have problems with connections.
The needed firmware 2870.bin has been included.

Next....I didnt see any rt2800usb loading attempt in kernel messages. Because there is no attempt to load it, I cant see if there is any errors with loading...or is it problem with wpa/wpa2 connection. You have possibly blacklisted or disabled it other way. Could you reverse your blacklisting or load the module manually:
Again in console: modprobe rt2800usb
And then again provide that pmodemdiag tarball.

There is possibility for proprietary rt2870sta driver provided by Ralink. Which should support your 2870 chip.

Also I understood that there is still some unsupported features with rt2800usb which might explain your problems.

I tried several things, including loading all four available rt28xxusb modules, for which the attached pertains. Results seems to be the same in all cases - no detection - but I can select any particular option you suggest. This dongle does get detected on some Puppies (can't remember which) but never connects. It does connect on other distros, but I'd need to confirm which ones during a protracted re-testing regime.It is very valuable to have this detailed information; the downloads of my attachment suggests that there are others wishing to know the outcome, also (presuming the idiot fringe has now disappeared).

Sage,

Think, before you write.

Sage. Now we get to somewhere.
From kernel messages:
Feb 25 15:48:47 puppypc14330 user.info kernel: [ 10.270561] usbcore: registered new interface driver rt2800usb
Feb 25 15:48:47 puppypc14330 user.info kernel: [ 10.436800] usbcore: registered new interface driver rt73usb
Feb 25 15:48:47 puppypc14330 user.info kernel: [ 10.511336] usbcore: registered new interface driver rt2500usb

You seem to have rt73usb, rt2500usb and rt2800usb loaded which leads to conflicting situation and possibly failed network connection due to 3 loaded wireless driver. This need to be eliminated first.

You can install the attached pet, which has updated /etc/rc.d/MODULESCONFIG where the preference of rt73usb and rt2800usb has been created for the favor of rt2800usb, rt73usb and rt2500usb has been blacklisted and rt2800usb will be loaded as forced. If you install the pet you need to reboot and check how it goes and post once again pmmodemdiag tarball.

EDIT. I saw that you posted that you had loaded 4 different wireless drivers. Dont try now on anything other than rt2800usb so that pmodemdiag tarball diagnostic data does not have obscuring trials.

This pet is only to test Sage`s problem, not generic fix for all Precise users.

pemasu, sage,
I am one of the downloaders of the preference fix package, to see what it contains. I do not want to interfere with Pemasu's efforts, but may have something that might help.

It would be useful to get the diagnostics of a clean setup (with or without the preference fix) that has all of the modules-of-interest installed but not forced to load. But first, be sure that, once they are installed, the 'depmod' command is run to ensure the modules can recognize the hardware (if they can). Reboot, to get the benefit of the depmod during bootup.

Then use my brand-new, super diagnostic collector, attached. It is used the same way as pmodemdiag, but is named "pdiag", since it is intended to be all-purpose. It now captures the modules.alias file, so we can see what the modules think they support, and can update the preference items as appropriate.

Note that when a module is forced to load, preferences are ignored, since the user "knows what he/she is doing".
Richard

Update 12/26/2012: Re-uploaded package to add minor changes after download 13. No need to replace an already-downloaded version.

Update 12/28/2012: Re-uploaded package to correct the archive directory from tmp/pdiag... to pdiag... after download number 17, but with no functional change.

Update 12/30/2012: Uploaded package to remove collection of potentially sensitive wireless connection data related to the network wizard, after download number 19.

Update 1/17/2013: Uploaded package to add splash messages when run within the new frisbee-1.0, after download #38.

Update 1/23/2013: Uploaded internationalized version that uses dialog windows and control over saving of potentially sensitive WPA files.