otropogo,otropogo wrote:Thanks for your interest, renwin. I installed the tool and ran it, but am unable to make sense of the output, as found in the /tmp/pdiag-20121226 folder.
Can you tell me which of the many files generated are relevant to this question? I would feel more comfortable knowing what I'm posting and limiting the content to information relevant to my configuration issue.
BTW - I had another look at the modules available in my copy of lupupluslibre (which I assume to be the latest version, although I don't know of any simple way to check), and there is no rtl8192se_pci in the list. The only wireless pci "rtl" module displayed is rtl8180.
Here is the texty of the file module-list from the above folder in /tmp:
. . .
I also booted the earlier version of lupu 528. This was a boot from a LiveCD with an sfs file dated August 2011. Where the lupupluslibre version recognized only the ethernet chip, this version detecte both eth0 and wlan0.
I didn't run the pdiag this time, but looked at the modules available for loading, and there were two wireless Realtek pci modules listed:
r819se_pci
r819ce_pci
You are right about the absence of rtl8192se_pci. I misread r8192se_pci as rtl8192se_pci in lupupluslibre. The files in the pdiag... directory that I would look at are chipnummod.txt, modules.alias and udevtrace.log. I don't think I have captured or generated any file named modules-list, and do not recognize the content you listed. Where did that come from?
With those 3 files, I would first look for the wifi device description and ID in chipnumod.txt (produced by pupscan), then find a line in the trace log related to your wifi device (vendor, device) hardware ID. That would tell me the device was detected. For example, my Broadcom wifi card has hardware ID 14e4:4320, so my log contains
Code: Select all
add_0000:01:09.0_pci_0x14e4_0x4320_pci:v000014E4d00004320sv00001737sd00000015bc02sc80i00
Code: Select all
alias pci:v000014E4d00004320sv*sd*bc*sc*i* ssb
Most of that probably is obvious to you, but remember I am "flying blind" as to what the user is actually working with, until I find the above information. If you get a pdiag for the older lupu, I could see that the r8192se_pci driver is associated with the device.
The most important info is the hardware ID, which I can use in google searches for information about any driver issues for it. BTW, googling "r8192se_pci" yields only one hit other that this thread. It was not helpful. (Maybe is was actually a mistaken name.)
Given that you have r8192se_pci available, if the kernel version of the lupu CD is the same as that of lupupluslibre (2.6.33.2), try copying the module to that same location in lupupluslibre. Then run depmod. The module should show up in /lib/modules/2.6.33.2/modules.alias and with a "pci:" line containing your hardware ID. Try it even if the older lupu kernel is 2.6.33-anything.
Sorry for my confusion over the module name. I would like to get the correct module for your device, even if I have to compile it, assuming we can find the source tarball.
Richard