Page 41 of 190 [2845 Posts]   Goto page: Previous 1, 2, 3, ..., 39, 40, 41, 42, 43, ..., 188, 189, 190 Next
Author Message
otropogo
PostPosted: Tue 01 Jan 2013, 21:02    Post subject:

rerwin wrote:
otropogo,
Quote:
Have looked at /initrd/pup_re/lib/modules/2.6.33.2 but don't see any modules there. The folder contains three bin files, modules.alias.bin, modules.dep.bin, and modules.symbols.bin. There are a number of text files, and two further folders, intrd and kernel, that do contain some modules further on. But nothing named "8192".
That is good info. Please look at the /initrd/pup_rw/lib/modules/2.6.33.2/ directory in line mode so you can see the "modify dates". Does the modules.alias.bin date match the modules.alias date? If they do not match or there is no modules.alias file, then that would be the problem. Also, the dates should be of the last time you ran depmod -- yesterday, I assume.

Note that when both of the modules.alias(.bin) files are present, the bin file will prevail. The busybox version of depmod does not update the .bin file, so that the modules.alias file may not be accurate as to what really happens. It appears that the lupuplus puppy does not use the busybox version, although it may still be used during bootup.

Another thing to check: Run pfind for the module in question to verify it is present. Or just look for "8192" to see what versions are present.

Richard


...

I don't know whether to laugh or cry.

I checked the date/time stamps of modules.alias and modules.alias.bin, and they're identical.

Then I had pfind search for "8192" in "all files", and got the following list.

Quote:
/etc/ndiswrapper/net8192se
/etc/ndiswrapper/net8192se/net8192se.inf
/lib/firmware/RTL8192CE
/lib/firmware/RTL8192CE/rtl8192cfw.bin
/lib/firmware/RTL8192CE/rtl8192cfw_test.bin
/lib/firmware/RTL8192SE
/lib/firmware/RTL8192SE/rtl8192sfw492.bin
/lib/firmware/RTL8192SE/rtl8192sfw74.bin
/lib/firmware/RTL8192SE/rtl8192sfw.bin
/lib/modules/2.6.33.2/kernel/drivers/net/wireless/8192cu.ko
/lib/modules/2.6.33.2/kernel/drivers/net/wireless/r8192ce_pci.ko
/lib/modules/2.6.33.2/kernel/drivers/net/wireless/r8192se_pci.ko
/lib/modules/2.6.33.2/kernel/drivers/staging/rtl8192e
/lib/modules/2.6.33.2/kernel/drivers/staging/rtl8192e/r8192_pci.ko
/lib/modules/2.6.33.2/kernel/drivers/staging/rtl8192su
/lib/modules/2.6.33.2/kernel/drivers/staging/rtl8192su/r8192s_usb.ko
/lib/modules/2.6.33.2/kernel/drivers/staging/rtl8192u
/lib/modules/2.6.33.2/kernel/drivers/staging/rtl8192u/r8192u_usb.ko
/lib/modules/all-firmware/rtl8188_8192su.tar.gz
/sys/module/cfg80211/holders/r8192se_pci
/sys/module/r8192se_pci


I was about to go online to post my results, when I thought of trying net wizard one more time, and "presto" wlan0 appeared for the first time.

I checked to be sure that I was indeed running with my main 2fs file - easy to do, as it's the only one that has xfprot installed - and I was. I'll make a hot save after posting this just to be sure (at 1.4GB, it takes a while).

I then proceeded to load the driver without further problems. I couldn't do anything more with it as I have no wifi host within range.

So I'm afraid we may never know with certainty exactly what was wrong, other than the failure to run depmod. IIRC, I did try the net wizard without success after running depmod last night, but possibly without rebooting the system first.

There are two remaining anomalies:

1. - even though the net wizard recognizes the wireless chip now, offers to load the driver for it and apparently does so, I'm still unable to find any 8192 modules (usb or pci) listed in the drop-down menu of available modules. The r8169 module OTOH, which I use for my Realtek ethernet chip, IS listed.

2. - when network wizard offers to install the wireless driver, it refers to it as rtl8191 not 8192, but pfind gets no hits searching "all files" on "8191"

Thanks again for your help. And happy new year!
rerwin
PostPosted: Tue 01 Jan 2013, 12:09    Post subject:

otropogo,
Quote:
Have looked at /initrd/pup_re/lib/modules/2.6.33.2 but don't see any modules there. The folder contains three bin files, modules.alias.bin, modules.dep.bin, and modules.symbols.bin. There are a number of text files, and two further folders, intrd and kernel, that do contain some modules further on. But nothing named "8192".
That is good info. Please look at the /initrd/pup_rw/lib/modules/2.6.33.2/ directory in line mode so you can see the "modify dates". Does the modules.alias.bin date match the modules.alias date? If they do not match or there is no modules.alias file, then that would be the problem. Also, the dates should be of the last time you ran depmod -- yesterday, I assume.

Note that when both of the modules.alias(.bin) files are present, the bin file will prevail. The busybox version of depmod does not update the .bin file, so that the modules.alias file may not be accurate as to what really happens. It appears that the lupuplus puppy does not use the busybox version, although it may still be used during bootup.

Another thing to check: Run pfind for the module in question to verify it is present. Or just look for "8192" to see what versions are present.

Since I am not sure, beyond that, what I am looking for, please reconsider sending me a PM with a pdiag file taken on your regular pupsave that is not performing. Use the latest version of pdiag, to omit the sensitive files. (Pemasu assures me that SNS encrypts the key information, wherever it is kept.)
Richard
fecklesslout
PostPosted: Tue 01 Jan 2013, 07:04    Post subject:

kevin bowers wrote:

First, you don't need to install Puppy at all to use it for data salvage; simply boot to CD and copy whatever data to one of your functioning drives, or burn it to another blank CD.

Unless what you meant is that you can't boot to CD either? That's actually quite different than installing. If that is the case, several things you could try:

boot: puppy pfix=ram vesa

try a different Puppy, maybe Slacko? I'm typing this on a core i5 system in Slacko 5.4-PAE.

BTW will the system boot Windows or any other OS?

If your motherboard has the circuitry to make use of the graphics chip in the processor, try pulling the graphics card out and connecting the monitor straight to the MB. Or if you have another graphics card laying around try it.

Maybe one of the big distros will have more graphics drivers than any Puppy, perhaps try Ubuntu? It will run as a live CD, that is you don't necessarily need to install it, just boot the CD.

Good luck!

P.S. @Playdayz, you are sorely missed! Luck, life & love to you and yours.

Yeah, sorry I didn't mean install, just boot from the CD. Keep getting the black screen. Tried your ram vesa suggestion and same result, black screen.

I'll give ubuntu a try and see how I go, thanks for your help Kevin!

System won't boot OS as the drive that failed is the one with the OS on it.
otropogo
PostPosted: Tue 01 Jan 2013, 03:13    Post subject:

rerwin wrote:
otropogo,
Quote:
(On my desktop) I've just typed "depmod" in a ROX terminal, and absolutely nothing happens.

Quote:
sh-4.1# depmod
sh-4.1#
What you see is what I expect. If you check the properties of /lib/modules/2.6.33.2/modules.alias, you should see that the "modified" date is the time you ran depmod. Depmod simply examines all of the modules in /lib/modules/2.6.33.2 and lists the alias lines for each, in modules.alias, to establish the appropriate module for each device hardware ID. So, that needs to be run any time the mix of modules is changed. That would be the case if you use a regular-lupu pupsave with lupuplus*. Now, try your test on the "depmodded" pupsave setup.


Hi Richard,

Afraid I don't understand your instructions this time. You seem to suggest that running depmod (ie. typing the term and hitting CR in a terminal) will update my older 2fs file and make the wireless module perform as expected.

If so, it had no effect. There is still no module available for loading, and no mention of the r8192_pci module in udev.trace.


Quote:
About those warnings: I infer from them that either the module 8192cu contains the duplicate entries or that there are multiple copies of it in different places within the /lib/modules/2.6.33.2 directory.

If the depmod does not solve the problem, please look at /initrd/pup_rw/lib/modules/2.6.33.2 for any "8192" modules that might interfere with the lupuplus modules. If you find any, please delete them or move them outside of /lib/modules/2.6.33.2/.


Have looked at /initrd/pup_re/lib/modules/2.6.33.2 but don't see any modules there. The folder contains three bin files, modules.alias.bin, modules.dep.bin, and modules.symbols.bin. There are a number of text files, and two further folders, intrd and kernel, that do contain some modules further on. But nothing named "8192".


Quote:
Beyond those thoughts, I think I am out of ideas. I am not going to try to keep up with the drive-swapping activities.
Richard


Well. Thanks for your efforts. I should be used to running into dead ends with Puppy after so many years of it. And I fully understand your reluctance to embark on yet another probably futile quest to unravel its workings.

As with the disappearing wireless module question, I was hoping someone just happened to know how the puppy bootloader's program is structured to search for puppy files.

Not being able to predict except by trial and error how to use the boot commands except by trial and error is a trivial inconvenience compared to having one's wi-fi capability inexplicably nullified. But it should also be a much easier matter to clarify, since anyone with more than one drive can easily replicate the problem.
rerwin
PostPosted: Mon 31 Dec 2012, 17:44    Post subject:

otropogo,
Quote:
(On my desktop) I've just typed "depmod" in a ROX terminal, and absolutely nothing happens.

Quote:
sh-4.1# depmod
sh-4.1#
What you see is what I expect. If you check the properties of /lib/modules/2.6.33.2/modules.alias, you should see that the "modified" date is the time you ran depmod. Depmod simply examines all of the modules in /lib/modules/2.6.33.2 and lists the alias lines for each, in modules.alias, to establish the appropriate module for each device hardware ID. So, that needs to be run any time the mix of modules is changed. That would be the case if you use a regular-lupu pupsave with lupuplus*. Now, try your test on the "depmodded" pupsave setup.

About those warnings: I infer from them that either the module 8192cu contains the duplicate entries or that there are multiple copies of it in different places within the /lib/modules/2.6.33.2 directory.

If the depmod does not solve the problem, please look at /initrd/pup_rw/lib/modules/2.6.33.2 for any "8192" modules that might interfere with the lupuplus modules. If you find any, please delete them or move them outside of /lib/modules/2.6.33.2/.

Beyond those thoughts, I think I am out of ideas. I am not going to try to keep up with the drive-swapping activities.
Richard
kevin bowers
PostPosted: Mon 31 Dec 2012, 17:16    Post subject:

fecklesslout wrote:
Hi all,
I'm new to Linux and am trying to salvage data on a dying SSD in my PC. The PC has three other HDDs in it, of which all are functioning fine. I've tried installing Lucid Puppy from a CD but it goes to a black screen. I've restarted and tried puppy pfix=nox and xorgwizard. No matter what I select at xorgwizard it takes me to a black screen (including vesa). I've tried puppy acpi=noirq and puppy acpi=strict. Nothing is working.

Can someone please help me troubleshoot this?
The PC is a Intel core i5 2500k, with nVidia GTX 570. Let me know if there's any more information you need.


First, you don't need to install Puppy at all to use it for data salvage; simply boot to CD and copy whatever data to one of your functioning drives, or burn it to another blank CD.

Unless what you meant is that you can't boot to CD either? That's actually quite different than installing. If that is the case, several things you could try:

boot: puppy pfix=ram vesa

try a different Puppy, maybe Slacko? I'm typing this on a core i5 system in Slacko 5.4-PAE.

BTW will the system boot Windows or any other OS?

If your motherboard has the circuitry to make use of the graphics chip in the processor, try pulling the graphics card out and connecting the monitor straight to the MB. Or if you have another graphics card laying around try it.

Maybe one of the big distros will have more graphics drivers than any Puppy, perhaps try Ubuntu? It will run as a live CD, that is you don't necessarily need to install it, just boot the CD.

Good luck!

P.S. @Playdayz, you are sorely missed! Luck, life & love to you and yours.
otropogo
PostPosted: Mon 31 Dec 2012, 15:51    Post subject:
Subject description: module stuff

sheldonisaac wrote:
otropogo wrote:

No. I don't recall running depmod under any combination of PC and 2fs. Pdiag is the only line command I've run on either PC during this discussion.I
otropogo, much of what you and Richard have been discussing is beyond me.

However, it seems that if one types

depmod --help

it gives some guidance?

For example, depmod -an | more

gives huge screenfuls of info.

Hopefully, some more knowledgable person will speak up.


Hi sheldonisaac,

Thanks for your suggestion. I looked at the help menu, but didn't find it very enlightening.

The most promising arguments, -a, -A, -m, displayed nothing. The "verbose" argument generated a huge list, but a search on "8192" turned up 0 hits.

The "warning" list generated by
Code:
depmod  -w
has the following reference to the usb version of the Realtek wifi chip, although it, like the 8192se pci version, fails to appear in the connection wizard modules list on this system.

Quote:
usb:v07B8p8178d*dc*dsc*dp*ic*isc*ip* 8192cu
WARNING: duplicate module alias:
usb:v0BDAp8177d*dc*dsc*dp*ic*isc*ip* 8192cu
WARNING: duplicate module alias:


But there's no reference to the pci module.

the -n argument has several lines referencing the 8192 usb module, but again, none for the pci version. As far as I can tell, the output of your -an argument is the same. I copied, pasted, and searched that too, and found only the same 8192 usb module referenced.

There are certainly huge screenfuls of text generated, but the informational content,relative to my problem, eludes me.
otropogo
PostPosted: Mon 31 Dec 2012, 14:52    Post subject: how are 2fs files found, and /mnt/home location determined?

After adding and removing a removable hdd (which became sda1, reshuffling the drive order), and necessarily modifying the linuxsys.cfg file on the usb flash card which I use to boot into Puppy Linux. I rebooted with the new syslinux.cfg, and was surprised by the result.

The last line in the original syslinux.cfg read
Code:
pdev1=sda1 psubdir=pupsave

This would offer only the two lupu-save*.2fs files in the sda1/pupsave folder. And the root directory of sda1 would automatically be named /mnt/home, which is convenient for saving web pages with SMonkey.

When the third hdd was added, and became sda1, this no longer worked, so pdev1... psubdir... was replaced by
Code:
pmedia=atahd
, which allowed me to boot from the renamed sdb1/pupsave.

But after removing the third drive, which changed sdb1 back to sda1, the same
Code:
pmedia=atahd
entry caused only the 2fs files in a pupsaveB folder on sdb1 to be offered, together with a single 2fs file in the root directory of sda1.

The 2fs files sitting in the sda1/pupsave folder were NOT presented.

I didn't notice the path, and simply selected the main 2fs file, unaware that it was on an unusual path. It was only when I tried to save a web page to the /mnt/home directory that I noticed the strange development.

I had always assumed that the linux loader would search the hard drives for the lupu_528.sfs file in ascending hdd order, starting with sda1, and use the first copy it found, then search for 2fs files in the same order, and make the hdd on which the 2fs used is located the /mnt/home directory (ie. automounted, and not unmountable).

Apparently, this is not the case, or pmdia=atahd would have resulted in the 2fs files in sda1/pupsave/ being offered for use.

And so I wonder what the actual mechanism might be?

Can anyone direct me to a comprehensive online explanation of this process and/or explain the situation described above?

I have tried googling this issue, but unfortunately "home" is a word that is commonly found in much more general contexts in Puppy Linux related searches, and I haven't been able to ferret out anything remotely related to the exact search procedure the puppy loader uses when "searching disks for puppy files"
sheldonisaac
PostPosted: Mon 31 Dec 2012, 14:37    Post subject:
Subject description: module stuff

otropogo wrote:

No. I don't recall running depmod under any combination of PC and 2fs. Pdiag is the only line command I've run on either PC during this discussion.I
otropogo, much of what you and Richard have been discussing is beyond me.

However, it seems that if one types

depmod --help

it gives some guidance?

For example, depmod -an | more

gives huge screenfuls of info.

Hopefully, some more knowledgable person will speak up.
otropogo
PostPosted: Mon 31 Dec 2012, 13:59    Post subject:

rerwin wrote:
otropogo,
Thanks for the clarification. When assuming you had copied the module, I also assumed you had run depmod, so that it shows up in modules.alias. Now, it sounds, to me, that maybe you have not run depmod in the regular pupsave. At least that would explain what we see -- or don't see.
Richard


No. I don't recall running depmod under any combination of PC and 2fs. Pdiag is the only line command I've run on either PC during this discussion.

(On my desktop) I've just typed "depmod" in a ROX terminal, and absolutely nothing happens.

Quote:
sh-4.1# depmod
sh-4.1#


I
rerwin
PostPosted: Mon 31 Dec 2012, 13:12    Post subject:

otropogo,
Thanks for the clarification. When assuming you had copied the module, I also assumed you had run depmod, so that it shows up in modules.alias. Now, it sounds, to me, that maybe you have not run depmod in the regular pupsave. At least that would explain what we see -- or don't see.
Richard
otropogo
PostPosted: Mon 31 Dec 2012, 02:22    Post subject:

Quote:
[quote="rerwin"]Let's see if I understand the situation. You are running lupupluslibre and have copied the r8192_pci module from the older lupu SFS file into "staging" in your lupupluslibre sessions.


No. I haven't copied anything to the "staging" folder or anywhere else. I've simply discovered that the module is there natively, even though it doesn't present itself in the network wizards, and can't be found in the list of available modules.

Quote:
Only your "regular" pupsave file (created originally in an earlier version of lupu?) fails to see that module. Right?


That's right.

Quote:
So it is possible that the pupsave could override some lupuplus versions of files and create inconsistencies in the configuration, particularly if you ever installed or uninstalled parts that are different in the "plus" lupus. Wireless drivers are the major difference between plus and original lupu (along with various puppy infrastructure upgrades).


I'm sure you're better qualified to speculate on that than I'll ever be.

IIRC, I brought my main 2fs file from earlier versions of lupu_5xx, then installed the patches for updates (2 and 4, I believe), and finally downloaded the latest version of lupupluslibre.


Quote:

Reviewing your previous postings, I see the regular-pupsave lupupluslibre modules.alias entry
Code:
alias pci:v000010ECd00008192sv*sd*bc*sc*i* r8192_pci
but your wifi device udevtrace entry is
Code:
pci_0x10ec_0x8172_pci:v000010ECd00008172sv000010ECsd00008151bc02sc80i00
That is not a match.


Quite. But I'm not clear how you identified that line as a wifi entry? It sits in the middle of the sound card entry section. I searched for any mention of "wireless" or "wi-fi", but didn't find any in there.

Quote:
I would expect a modules.alias entry
Code:
alias pci:v000010ECd00008172sv*sd*bc*sc*i* r8192_pci
Without that, I don't see how the module would get associated with the copied module, Is there such an entry in the setups that work?

Anyway, other files to check are the "messages" and "bootsysinit.log" file, to see if there is anything related to the wifi device.


Yes, there is.

For simplicity's sake I booted the laptop with no 2fs file at all, installed pdiag (although not the last version, as I couldn't figure out how to download it with Dillo), and ran pdiag.

Udev.trace has the following entry:

Quote:
add_r8192se_pci_module


bootsysinit.log has:

Quote:
Adding r8192se_pci


and "messages" has nine lines referencing r8192, all in user.warn.kernel.



When booting with my main 2fs file, none of these r8192 references appear in either udev.trace, bootsysinit.log, or messages.

Only the modules.alias entry and the 291K "r8192_pci.ko" file in /.../staging/rtl8192e/ are present regardless of the 2fs file used.
rerwin
PostPosted: Sun 30 Dec 2012, 17:43    Post subject:

otropogo wrote:
Correction: in all cases (successful and unsuccessful loading of the wifi module), the lupu_528.sfs file loaded into RAM from the hard drive. The difference in loading consisted of nothing other than the 2fs file loaded with 528.

In all cases, the loader ran from a flash card on the USB bus.

Please note also that the ...ko file is indeed sitting where it's supposed to be, as reported in my previous post. However, the module doesn't show up in the "Load a network module" list of the network setup gui. I can't see how that could be the result of any timing problem, since all the other modules are there, and my ethernet module gets loaded automatically every time (so long as I'm connected by cable to the router).

There has to be another issue.

Note also that in lib/......staging/ there is only ONE 8192 pci module, r8192_pci.ko, the other two, r8192u, and r8192su, are usb wifi modules

I'm on my desktop right now, and unable for the moment to check or try anything on the laptop with the realtek wifi, but shall report if anything is different there later.

Both laptop and desktop run the linux loader from flash media, but load the lupu_528.sfs from the hard drive.

In both the only difference between having the f8192 module listed or not, lies with the 2fs file loaded. With no 2fs, or a barebones one (graphic configuration and pdiag the only changes from stock), the wifi module is listed (and on the laptop, offered for loading by network wizard), with the main 2fs file (which predates lupu_528, IIRC), the module is not listed, although it appears to be on the system, as reported above.
Let's see if I understand the situation. You are running lupupluslibre and have copied the r8192_pci module from the older lupu SFS file into "staging" in your lupupluslibre sessions. Only your "regular" pupsave file (created originally in an earlier version of lupu?) fails to see that module. Right? So it is possible that the pupsave could override some lupuplus versions of files and create inconsistencies in the configuration, particularly if you ever installed or uninstalled parts that are different in the "plus" lupus. Wireless drivers are the major difference between plus and original lupu (along with various puppy infrastructure upgrades).

Reviewing your previous postings, I see the regular-pupsave lupupluslibre modules.alias entry
Code:
alias pci:v000010ECd00008192sv*sd*bc*sc*i* r8192_pci
but your wifi device udevtrace entry is
Code:
pci_0x10ec_0x8172_pci:v000010ECd00008172sv000010ECsd00008151bc02sc80i00
That is not a match. I would expect a modules.alias entry
Code:
alias pci:v000010ECd00008172sv*sd*bc*sc*i* r8192_pci
Without that, I don't see how the module would get associated with the copied module, Is there such an entry in the setups that work?

Anyway, other files to check are the "messages" and "bootsysinit.log" file, to see if there is anything related to the wifi device.

I think what we need to compare, now, is a pdiag from the identical setups but with pupsaves that work and don't work. Then we could look for differences. I would compare the modules.alias files (with the diff command), to start.

However, I understand and share your concern about publishing the diagnostic results because of what they might include. When I created the dialup part (as pmodemdiag) I included logic to change the wvdial.conf logons and passwords to 8 asterisks. But when I added the Frisbee pnetworkdiag logic, I did not check for files that would compromise passwords or pass phrases. I also added files from the other network managers but, again, did not look for sensitive files. Any advice on that is welcome. I do see that pdiag collects network wizard information that is probably too sensitive to publish, so I am removing the command that does that. I need to look further for Frisbee's version of that information, as well as for the simple network setup function.

In the meantime, I recommend that anyone concerned about revealing wireless connection information avoid uploading the pdiag (or pmodemdiag) tarball to a forum thread. But a PM should be safe enough. I will update pdiag in the two places I have put it for downloading (in precise and lucid pup threads), to remove the wireless data capture command (as -20121230).
Richard
fecklesslout
PostPosted: Sun 30 Dec 2012, 16:42    Post subject:

Hi all,
I'm new to Linux and am trying to salvage data on a dying SSD in my PC. The PC has three other HDDs in it, of which all are functioning fine. I've tried installing Lucid Puppy from a CD but it goes to a black screen. I've restarted and tried puppy pfix=nox and xorgwizard. No matter what I select at xorgwizard it takes me to a black screen (including vesa). I've tried puppy acpi=noirq and puppy acpi=strict. Nothing is working.

Can someone please help me troubleshoot this?
The PC is a Intel core i5 2500k, with nVidia GTX 570. Let me know if there's any more information you need.
otropogo
PostPosted: Sun 30 Dec 2012, 14:48    Post subject:

rerwin wrote:
...]After some reflection, because the sometime-success where the flash media installations work but the hard drive setup does not, I suspect there is some kind of timing factor at work. Assuming that the flash-medium boots run slower than a hard-drive boot that actually occurs from the RAM copy of puppy, There might be a delay in the hardware getting ready such that the module is loaded too soon.

This is a "shot in the dark", but the attached pet package contains a modprobe.d configuration file, r8192se_pci.conf, that inserts a 5-second sleep before the actual modprobe of the module is performed. This may not solve the problem, but is a simple thing to try, just in case it does. Use this on a lupupluslibre setup. This experiment is instead of installing the Realtek driver posted above, in case this simpler approach is sufficient.
Richard


Correction: in all cases (successful and unsuccessful loading of the wifi module), the lupu_528.sfs file loaded into RAM from the hard drive. The difference in loading consisted of nothing other than the 2fs file loaded with 528.

In all cases, the loader ran from a flash card on the USB bus.

Please note also that the ...ko file is indeed sitting where it's supposed to be, as reported in my previous post. However, the module doesn't show up in the "Load a network module" list of the network setup gui. I can't see how that could be the result of any timing problem, since all the other modules are there, and my ethernet module gets loaded automatically every time (so long as I'm connected by cable to the router).

There has to be another issue.

Note also that in lib/......staging/ there is only ONE 8192 pci module, r8192_pci.ko, the other two, r8192u, and r8192su, are usb wifi modules

I'm on my desktop right now, and unable for the moment to check or try anything on the laptop with the realtek wifi, but shall report if anything is different there later.

Both laptop and desktop run the linux loader from flash media, but load the lupu_528.sfs from the hard drive.

In both the only difference between having the f8192 module listed or not, lies with the 2fs file loaded. With no 2fs, or a barebones one (graphic configuration and pdiag the only changes from stock), the wifi module is listed (and on the laptop, offered for loading by network wizard), with the main 2fs file (which predates lupu_528, IIRC), the module is not listed, although it appears to be on the system, as reported above.
Display posts from previous:   Sort by:   
Page 41 of 190 [2845 Posts]   Goto page: Previous 1, 2, 3, ..., 39, 40, 41, 42, 43, ..., 188, 189, 190 Next

Powered by phpBB © 2001, 2005 phpBB Group