Page 41 of 190 [2837 Posts]   Goto page: Previous 1, 2, 3, ..., 39, 40, 41, 42, 43, ..., 188, 189, 190 Next
Author Message
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.
otropogo
PostPosted: Sun 30 Dec 2012, 14:27    Post subject: Re: finding a module

sheldonisaac wrote:


I don't have the luplibre, just LuPu 5.2.8-005.


No problem. It's the same kernel, and should have the same modules.

Quote:
I did this:

Code:
~> find /lib/modules/ -name *819*
/lib/modules/2.6.33.2/kernel/drivers/media/video/bt819.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
~>


Perhaps a search similar to that will find the module you want?


Thanks. It turns out that:

/lib/modules/2.6.33.2/kernel/drivers/staging/rtl8192e/r8192_pci.ko

the module my wifi chip requires IS sitting where you found it. It may be that renwin's second solution is the answer, unless some other component is missing.
Semme
PostPosted: Sun 30 Dec 2012, 11:25    Post subject:

Having misplaced my copy.. is there anyone with a spare service pack 4 update lying around?

*Whoops! Embarassed Me's found it. Razz
rerwin
PostPosted: Sun 30 Dec 2012, 10:00    Post subject:

otropogo wrote:
I rebooted from the CD using the barebones 2fs file that showed the wifi module, but didn’t recognize the chip, when booting from the CF card. When used with the CD, however, the wifi chip WAS recognized.
. . .
I then booted from the CF card again, using the same 2fs file, and then, the wifi card was recognized. However, whether I boot from the CD or the CF card, whenever I use my main 2fs file, wifi isn't recognized, and the wifi module doesn't appear in the load list.
. . .
So something about my main 2fs file is preventing the wifi chip from being recognized. Any ideas how this might have happened, or how to fix it?
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
rerwin
PostPosted: Sun 30 Dec 2012, 01:38    Post subject: Realtek driver for RTL8191SEvB Wireless LAN Controller

otropogo,
I used your hardware ID to google for information on it. I found a string of 3 messages that address the issue, here:
http://www.murga-linux.com/puppy/viewtopic.php?p=426398#426398

I used the link in the third posting to find the Realtek source for the appropriate module for lupu's kernel. I compiled it and collected the parts that were produced and put them in the attached pet package. The source tarball actually created 3 variants of rtl8192 as well as some pieces related to making the code compatible with the range of kernels that includes lupu's.

I do not know whether the complete set will work in lupu, so need you to try the package on a test setup. If there is a problem, we could try removing the "compat" parts to see if puppy handles only the firmware and modules without running a "compat" script automatically. This probably make no sense to you, but we can deal with that if we need to.

Simply install the pet and reboot. It contains a depmod command, so the modules will be included in the modules.alias file (at the end).

To respond to your question on how to copy the r8192se_pci module, find it in the older lupu, probably at /lib/modules/2.6.33.2/kernel/drivers/net/wireless, or maybe in an "rtl" directory there, as r8192se_pci.ko. Copy it somewhere that you can access from a lupupluslibre setup, then copy it to the same place in lupupluslibre. But I gather you already figured that out.

And thanks to bigpup and sheldonisaac for working with you on this. I do not understand why the old module works with some of your lupupluslibre installations an not the main hard-drive installation. Usually it is the other way around. Anyway, the nuances of running from flash media are beyond me at this point. Signing off now for some zzzs.
Richard
sheldonisaac
PostPosted: Sat 29 Dec 2012, 22:22    Post subject: finding a module

(portions snipped)
otropogo wrote:
I thought it was impossible to add or remove kernel modules except by recompiling the kernel.
Maybe one can just copy a module from the lupulibre or whereever, to where it needs to be in the Puppy which needs it?
Quote:
You might recall that Puppy documentation has not always been "Spot on".

Oh, I concur with you on that!
Quote:
Renwin has told me to look for the realtek pci wifi module in /lib/modules/2.6.33.2/modules.alias, and it's listed there (three times) as r8192_pci.

But that's just an entry in a text file. I don't know where to look for the actual module and driver, or why they work in lupupluslibre when using one 2fs file, and not when using another.


I don't have the luplibre, just LuPu 5.2.8-005.

I did this:

Code:
~> find /lib/modules/ -name *819*
/lib/modules/2.6.33.2/kernel/drivers/media/video/bt819.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
~>


Perhaps a search similar to that will find the module you want?
otropogo
PostPosted: Sat 29 Dec 2012, 20:22    Post subject:

bigpup wrote:
From page 1 of topic:
Quote:
Notes: 1) If you have previously used the Lucid 5.2.8 Live CD, it may have copied the lupu_528.sfs file to your hard drive. When the new CD boots it will use that lupu_528.sfs without telling you, so you need to delete it from your drive, or rename it, before you boot the new CD. This will happen even if the lupu_528.sfs is in a directory.


Thanks, I understand that bigpup. Although I believe the loader only searches the first level of folders. In this case I was just using an old CD to boot the newer lupupluslibre sfs on the hard drive.

What made me unsure of the process is the fact that modules from the kernel somehow became inaccessible. I thought it was impossible to add or remove kernel modules except by recompiling the kernel. You might recall that Puppy documentation has not always been "Spot on".

Renwin has told me to look for the realtek pci wifi module in /lib/modules/2.6.33.2/modules.alias, and it's listed there (three times) as r8192_pci.

But that's just an entry in a text file. I don't know where to look for the actual module and driver, or why they work in lupupluslibre when using one 2fs file, and not when using another.
bigpup
PostPosted: Sat 29 Dec 2012, 16:43    Post subject:

From page 1 of topic:
Quote:
Notes: 1) If you have previously used the Lucid 5.2.8 Live CD, it may have copied the lupu_528.sfs file to your hard drive. When the new CD boots it will use that lupu_528.sfs without telling you, so you need to delete it from your drive, or rename it, before you boot the new CD. This will happen even if the lupu_528.sfs is in a directory.
otropogo
PostPosted: Sat 29 Dec 2012, 15:12    Post subject:

@Renwin

After saving your revised pdiag pet, I rebooted from the CD using the barebones 2fs file that showed the wifi module, but didn’t recognize the chip, when booting from the CF card. When used with the CD, however, the wifi chip WAS recognized. And when I ran pdiag, udev.trace showed the following entries.

20:51:19 add_r8192se_pci_module___
20:51:19 add_r8169_module___
20:51:19 add_serial8250_platform___platform:serial8250
20:51:19 change_regulatory.0_platform___platform:regulatory
20:51:19 add_rtl819xSE_drivers___
20:51:19 add_0000:14:00.0_pci_0x10ec_0x8172_pci:v000010ECd00008172sv000010ECsd00008151bc02sc80i00
20:51:19 add_r8169_drivers___

I then booted from the CF card again, using the same 2fs file, and then, the wifi card was recognized. However, whether I boot from the CD or the CF card, whenever I use my main 2fs file, wifi isn't recognized, and the wifi module doesn't appear in the load list.

NB. it appears that no matter which medium I'm using to boot the system, it's always the lupupluslibre sfs that's loaded, as both loaders find it on the hard drive, and there doesn't seem to be another copy on the drive.

The CD has only the 125MB lupu_528.sfs, and the CF card has no active sfs file at all, only the loader and intrd.gz. But all the desktops, including the one without a 2fs file, have the libre suite.

So something about my main 2fs file is preventing the wifi chip from being recognized. Any ideas how this might have happened, or how to fix it?
Display posts from previous:   Sort by:   
Page 41 of 190 [2837 Posts]   Goto page: Previous 1, 2, 3, ..., 39, 40, 41, 42, 43, ..., 188, 189, 190 Next

Powered by phpBB © 2001, 2005 phpBB Group