Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 01 Sep 2014, 18:01
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Lucid Puppy 5.2.8 - Updated ISO Version 005 - APR 05 2012
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 149 of 190 [2845 Posts]   Goto page: Previous 1, 2, 3, ..., 147, 148, 149, 150, 151, ..., 188, 189, 190 Next
Author Message
rerwin


Joined: 24 Aug 2005
Posts: 1513
Location: Maine, USA

PostPosted: Fri 28 Dec 2012, 18:47    Post subject: Re: Realtek wireless modules missing in recent Lupu versions
Subject description: Realtek RTL8191SEvB available in lupu v 2, gone in version 4
 

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
otropogo,
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:
add_0000:01:09.0_pci_0x14e4_0x4320_pci:v000014E4d00004320sv00001737sd00000015bc02sc80i00

In my modules.alias file, I find
Code:
alias pci:v000014E4d00004320sv*sd*bc*sc*i* ssb
The module is ssb; yours may not show a module in chipnummod.txt and may not have a match in modules.alias.

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
Back to top
View user's profile Send private message 
otropogo


Joined: 24 Oct 2009
Posts: 702
Location: Southern Rocky Mt. Trench

PostPosted: Sat 29 Dec 2012, 12:44    Post subject: Re: Realtek wireless modules missing in recent Lupu versions
Subject description: Realtek RTL8191SEvB available in lupu v 2, gone in version 4
 

Hi Richard,

rerwin wrote:


...
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?


IIRC, the text I posted is the content of a file /tmp/pdiag-20121226/module-list. However, it doesn't appear in the pdiag folder generated today, nor in the one I saved yesterday...

Quote:
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:
add_0000:01:09.0_pci_0x14e4_0x4320_pci:v000014E4d00004320sv00001737sd00000015bc02sc80i00

In my modules.alias file, I find
Code:
alias pci:v000014E4d00004320sv*sd*bc*sc*i* ssb
The module is ssb; yours may not show a module in chipnummod.txt and may not have a match in modules.alias.


OK. I ran pdiag again on my regular lupupluslibre setup (ie. with the usual 2fs file) in which the the connection module doesn't detect the Realtek wireless chip and the modules list doesn't show any r819 module.

I looked at the three files you mention, and found the following in chipnummod.txt:

Quote:
DESCRIPTION: Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller
VENDOR: 10ec DEVICE: 8172

and from modules.alias

Quote:
alias pci:v000007AAd00000047sv*sd*bc*sc*i* r8192_pci
alias pci:v000007AAd00000044sv*sd*bc*sc*i* r8192_pci
alias pci:v000010ECd00008192sv*sd*bc*sc*i* r8192_pci


But I wasn't able to identify anything relating to this device in udev.trace. So here is the entire text of that file:
Quote:

18:50:56 add_processor_module___
18:50:56 add_cpuidle_cpu___
18:50:56 add_cooling_device0_thermal___
18:50:56 add_LNXCPU:00_acpi___acpi:LNXCPU:
18:50:56 add_cooling_device1_thermal___
18:50:56 add_button_drivers___
18:50:56 add_button_module___
18:50:56 add_ac_module___
18:50:56 add_LNXCPU:02_acpi___acpi:LNXCPU:
18:50:56 add_LNXPWRBN:00_acpi___acpi:LNXPWRBN:
18:50:56 add_cpuidle_cpu___
18:50:56 add_processor_drivers___
18:50:56 add_state0_cpu___
18:50:56 add_state1_cpu___
18:50:56 add_LNXCPU:01_acpi___acpi:LNXCPU:
18:50:56 add_ac_drivers___
18:50:56 add_state2_cpu___
18:50:56 add_ACPI0003:00_acpi___acpi:ACPI0003:
18:50:56 add_state2_cpu___
18:50:56 add_state0_cpu___
18:50:56 add_state1_cpu___
18:50:56 add_LNXSYBUS:00_acpi___acpi:LNXSYBUS:
18:50:56 add_LNXCPU:03_acpi___acpi:LNXCPU:
18:50:56 add_LNXSYSTM:00_acpi___acpi:LNXSYSTM:
18:50:56 add_ACAD_power_supply___
18:50:56 change_ACAD_power_supply___
18:50:56 add_PNP0103:00_acpi___acpi:PNP0103:PNP0C01:
18:50:56 add_PNP0100:00_acpi___acpi:PNP0100:
18:50:56 add_PNP0000:00_acpi___acpi:PNP0000:
18:50:56 add_PNP0200:00_acpi___acpi:PNP0200:
18:50:56 add_PNP0303:00_acpi___acpi:PNP0303:
18:50:56 add_video_output_class___
18:50:56 add_output_module___
18:50:56 add_video_module___
18:50:56 add_acpi_video0_backlight___
18:50:56 add_cooling_device2_thermal___
18:50:56 add_acpi_video0_video_output___
18:50:56 add_LNXVIDEO:01_acpi___acpi:LNXVIDEO:
18:50:56 add_video_drivers___
18:50:56 add_input3_input___input:b0019v0000p0005e0000-e0,5,kramlsfw0,
18:50:56 add_evdev_module___
18:50:56 add_thermal_drivers___
18:50:56 add_thermal_module___
18:50:56 add_LNXVIDEO:00_acpi___acpi:LNXVIDEO:
18:50:56 add_PNP0C0F:00_acpi___acpi:PNP0C0F:
18:50:56 add_LNXTHERM:00_acpi___acpi:LNXTHERM:
18:50:57 add_input5_input___input:b0019v0000p0001e0000-e0,1,k74,ramlsfw
18:50:57 add_input4_input___input:b0019v0000p0001e0000-e0,1,k74,ramlsfw
18:50:57 add_PNP0C0F:01_acpi___acpi:PNP0C0F:
18:50:57 add_PNP0A08:00_acpi___acpi:PNP0A08:PNP0A03:
18:50:57 add_PNP0C0F:02_acpi___acpi:PNP0C0F:
18:50:57 add_event1_input___
18:50:57 add_PNP0C09:00_acpi___acpi:PNP0C09:
18:50:57 add_event0_input___serio:ty06pr00id00ex00
18:50:57 add_PNP0C04:00_acpi___acpi:PNP0C04:
18:50:57 add_PNP0C02:01_acpi___acpi:PNP0C02:
18:50:57 add_event5_input___
18:50:57 add_PNP0B00:00_acpi___acpi:PNP0B00:
18:50:57 add_event2_input___
18:50:57 add_PNP0C02:00_acpi___acpi:PNP0C02:
18:50:57 add_PNP0C0F:03_acpi___acpi:PNP0C0F:
18:50:57 add_PNP0C0D:00_acpi___acpi:PNP0C0D:
18:50:57 add_PNP0C0F:04_acpi___acpi:PNP0C0F:
18:50:57 add_event3_input___
18:50:57 add_PNP0C0F:05_acpi___acpi:PNP0C0F:
18:50:57 add_PNP0C0C:00_acpi___acpi:PNP0C0C:
18:50:57 add_event4_input___
18:50:57 add_PNP0C0F:06_acpi___acpi:PNP0C0F:
18:50:57 add_PNP0C0F:07_acpi___acpi:PNP0C0F:
18:50:57 add_input6_input___input:b0019v0000p0006e0000-e0,1,kE0,E1,E3,F0,F1,F2,F3,F4,F5,ramlsfw
18:50:57 add_event6_input___
18:50:57 add_battery_module___
18:50:57 add_PNP0C32:00_acpi___acpi:PNP0C32:
18:50:57 add_battery_drivers___
18:50:57 add_PNP0C0A:00_acpi___acpi:PNP0C0A:
18:50:57 add_PNP0C32:01_acpi___acpi:PNP0C32:
18:50:57 add_PNP0C32:02_acpi___acpi:PNP0C32:
18:50:57 add_PNP0C32:03_acpi___acpi:PNP0C32:
18:50:57 add_SYN0712:00_acpi___acpi:SYN0712:SYN0700:SYN0002:PNP0F13:
18:50:57 add_TOS620A:00_acpi___acpi:TOS620A:
18:50:57 add_device:00_acpi___acpi:device:
18:50:57 add_TOS1900:00_acpi___acpi:TOS1900:
18:50:57 add_device:01_acpi___acpi:device:
18:50:57 add_device:02_acpi___acpi:device:
18:50:57 add_device:03_acpi___acpi:device:
18:50:57 add_device:04_acpi___acpi:device:
18:50:57 add_device:05_acpi___acpi:device:
18:50:57 add_device:06_acpi___acpi:device:
18:50:57 add_device:07_acpi___acpi:device:
18:50:57 add_device:08_acpi___acpi:device:
18:50:57 add_device:09_acpi___acpi:device:
18:50:57 add_device:0a_acpi___acpi:device:
18:50:57 add_device:0b_acpi___acpi:device:
18:50:57 add_device:0c_acpi___acpi:device:
18:50:57 add_device:0d_acpi___acpi:device:
18:50:57 add_device:0e_acpi___acpi:device:
18:50:57 add_device:0f_acpi___acpi:device:
18:50:57 add_device:10_acpi___acpi:device:
18:50:57 add_device:11_acpi___acpi:device:
18:50:57 add_device:12_acpi___acpi:device:
18:50:57 add_device:13_acpi___acpi:device:
18:50:57 add_device:14_acpi___acpi:device:
18:50:57 add_device:15_acpi___acpi:device:
18:50:57 add_device:16_acpi___acpi:device:
18:50:57 add_device:17_acpi___acpi:device:
18:50:57 add_device:18_acpi___acpi:device:
18:50:57 add_device:19_acpi___acpi:device:
18:50:57 add_device:1a_acpi___acpi:device:
18:50:57 add_device:1b_acpi___acpi:device:
18:50:57 add_device:1c_acpi___acpi:device:
18:50:57 add_device:1d_acpi___acpi:device:
18:50:58 add_device:1e_acpi___acpi:device:
18:50:58 add_device:1f_acpi___acpi:device:
18:50:58 add_device:20_acpi___acpi:device:
18:50:58 add_device:21_acpi___acpi:device:
18:50:58 add_device:22_acpi___acpi:device:
18:50:58 add_device:23_acpi___acpi:device:
18:50:58 add_device:24_acpi___acpi:device:
18:50:58 add_device:25_acpi___acpi:device:
18:50:58 add_device:26_acpi___acpi:device:
18:50:58 add_device:27_acpi___acpi:device:
18:50:58 add_device:28_acpi___acpi:device:
18:50:58 add_device:29_acpi___acpi:device:
18:50:58 add_device:2a_acpi___acpi:device:
18:50:58 add_device:2b_acpi___acpi:device:
18:50:58 add_device:2c_acpi___acpi:device:
18:50:58 add_device:2d_acpi___acpi:device:
18:50:58 add_device:2e_acpi___acpi:device:
18:50:58 add_device:2f_acpi___acpi:device:
18:50:58 add_device:30_acpi___acpi:device:
18:50:58 add_device:31_acpi___acpi:device:
18:50:58 add_device:32_acpi___acpi:device:
18:50:58 add_device:33_acpi___acpi:device:
18:50:58 add_device:34_acpi___acpi:device:
18:50:58 add_device:35_acpi___acpi:device:
18:50:58 add_device:36_acpi___acpi:device:
18:50:58 add_device:37_acpi___acpi:device:
18:50:58 add_device:38_acpi___acpi:device:
18:50:58 add_device:39_acpi___acpi:device:
18:50:58 add_device:3a_acpi___acpi:device:
18:50:58 add_device:3b_acpi___acpi:device:
18:50:58 add_device:3c_acpi___acpi:device:
18:50:58 add_device:3d_acpi___acpi:device:
18:50:58 add_device:3e_acpi___acpi:device:
18:50:58 add_device:3f_acpi___acpi:device:
18:50:58 add_device:40_acpi___acpi:device:
18:50:58 add_device:41_acpi___acpi:device:
18:50:59 add_0000:00:1c.0_pci_0x8086_0x2940_pci:v00008086d00002940sv00000000sd00000000bc06sc04i00
18:50:59 add_0000:00:1a.2_pci_0x8086_0x2939_pci:v00008086d00002939sv00001179sd0000FF00bc0Csc03i00
18:50:59 add_0000:00:1a.1_pci_0x8086_0x2938_pci:v00008086d00002938sv00001179sd0000FF00bc0Csc03i00
18:50:59 add_0000:00:1a.7_pci_0x8086_0x293c_pci:v00008086d0000293Csv00001179sd0000FF00bc0Csc03i20
18:50:59 add_pci_hotplug_module___
18:50:59 add_shpchp_drivers___
18:50:59 add_0000:00:1a.0_pci_0x8086_0x2937_pci:v00008086d00002937sv00001179sd0000FF00bc0Csc03i00
18:50:59 add_0000:00:01.0_pci_0x8086_0x2a41_pci:v00008086d00002A41sv00001179sd0000FF00bc06sc04i00
18:50:59 add_shpchp_module___
18:50:59 add_0000:00:1e.0_pci_0x8086_0x2448_pci:v00008086d00002448sv00001179sd0000FF00bc06sc04i01
18:50:59 add_0000:00:1f.0_pci_0x8086_0x2919_pci:v00008086d00002919sv00001179sd0000FF00bc06sc01i00
18:50:59 add_0000:00:1d.1_pci_0x8086_0x2935_pci:v00008086d00002935sv00001179sd0000FF00bc0Csc03i00
18:50:59 add_0000:00:1f.2_pci_0x8086_0x2929_pci:v00008086d00002929sv00001179sd0000FF00bc01sc06i01
18:50:59 add_0000:00:1d.0_pci_0x8086_0x2934_pci:v00008086d00002934sv00001179sd0000FF00bc0Csc03i00
18:50:59 add_0000:00:1c.5_pci_0x8086_0x294a_pci:v00008086d0000294Asv00000000sd00000000bc06sc04i00
18:50:59 add_0000:00:1c.3_pci_0x8086_0x2946_pci:v00008086d00002946sv00000000sd00000000bc06sc04i00
18:50:59 add_0000:01:00.0_pci_0x10de_0x0a74_pci:v000010DEd00000A74sv00001179sd0000FF00bc03sc00i00
18:50:59 add_agpgart_module___
18:50:59 add_intel_agp_module___
18:50:59 add_agpgart-intel_drivers___
18:50:59 add_0000:00:00.0_pci_0x8086_0x2a40_pci:v00008086d00002A40sv00001179sd0000FF00bc06sc00i00
18:50:59 add_0000:00:1c.2_pci_0x8086_0x2944_pci:v00008086d00002944sv00000000sd00000000bc06sc04i00
18:50:59 add_0000:00:1d.2_pci_0x8086_0x2936_pci:v00008086d00002936sv00001179sd0000FF00bc0Csc03i00
18:50:59 add_0000:00:1d.7_pci_0x8086_0x293a_pci:v00008086d0000293Asv00001179sd0000FF00bc0Csc03i20
18:50:59 add_sound_class___
18:50:59 add_0000:14:00.0_pci_0x10ec_0x8172_pci:v000010ECd00008172sv000010ECsd00008151bc02sc80i00
18:50:59 add_snd_page_alloc_module___
18:50:59 add_soundcore_module___
18:50:59 add_snd_module___
18:50:59 add_timer_sound___
18:50:59 add_snd_seq_device_module___
18:50:59 add_snd_timer_module___
18:50:59 add_snd_pcm_module___
18:50:59 add_snd_seq_module___
18:50:59 add_seq_sound___
18:50:59 add_snd_mixer_oss_module___
18:50:59 add_snd_pcm_oss_module___
18:50:59 add_snd_hda_intel_module___
18:50:59 add_snd_hda_codec_module___
18:50:59 add_snd_seq_midi_event_module___
18:50:59 add_0000:20:00.3_pci_0x197b_0x2383_pci:v0000197Bd00002383sv00001179sd0000FF02bc08sc80i00
18:50:59 add_snd_rawmidi_module___
18:50:59 add_0000:20:00.4_pci_0x197b_0x2384_pci:v0000197Bd00002384sv00001179sd0000FF02bc08sc80i00
18:50:59 add_i2c_bus___
18:50:59 add_snd_seq_midi_module___
18:50:59 add_i2c_core_module___
18:50:59 add_i2c_i801_module___
18:50:59 add_snd_seq_oss_module___
18:50:59 add_dummy_drivers___
18:50:59 add_sequencer_sound___
18:50:59 add_sequencer2_sound___
18:50:59 add_i8042_platform___platform:i8042
18:50:59 add_snd_seq_dummy_module___
18:50:59 add_r8169_module___
18:50:59 add_mii_module___
18:50:59 add_serial8250_platform___platform:serial8250
18:50:59 add_0000:20:00.2_pci_0x197b_0x2381_pci:v0000197Bd00002381sv00001179sd0000FF02bc08sc05i01
18:50:59 add_r8169_drivers___
18:50:59 add_vesafb.0_platform___platform:vesafb
18:50:59 add_snd_hda_codec_realtek_module___
18:50:59 add_0000:0e:00.0_pci_0x10ec_0x8168_pci:v000010ECd00008168sv00001179sd0000FF00bc02sc00i00
18:50:59 add_i801_smbus_drivers___
18:50:59 add_0000:20:00.0_pci_0x197b_0x2382_pci:v0000197Bd00002382sv00001179sd00002382bc08sc80i00
18:50:59 add_sg3_scsi_generic___
18:50:59 add_sg4_scsi_generic___
18:50:59 add_sg2_scsi_generic___
18:50:59 add_0000:00:1f.3_pci_0x8086_0x2930_pci:v00008086d00002930sv00001179sd0000FF00bc0Csc05i00
18:50:59 add_1:0:0:0_scsi_ATA__scsi:t-0x00
18:50:59 add_scsi_generic_class___
18:50:59 add_sg5_scsi_generic___
18:50:59 add_sg_module___
18:50:59 add_4:0:0:0_scsi_HL-DT-ST__scsi:t-0x05
18:50:59 add_sg0_scsi_generic___
18:50:59 add_sg1_scsi_generic___
18:50:59 add_pcspkr_drivers___
18:50:59 add_pcspkr_module___
18:50:59 add_eth1_net_0x10ec_0x8168_pci:v000010ECd00008168sv00001179sd0000FF00bc02sc00i00
18:50:59 add_pcspkr_platform___platform:pcspkr
18:50:59 add_8:0:0:0_scsi_Generic__scsi:t-0x00
18:50:59 add_8:0:0:1_scsi_Generic__scsi:t-0x00
18:50:59 move_eth1_net___
18:50:59 add_8:0:0:2_scsi_Generic__scsi:t-0x00
18:50:59 add_8:0:0:3_scsi_Generic__scsi:t-0x00
18:50:59 add_input7_input___input:b0010v001Fp0001e0100-e0,12,kramls1,2,fw
18:50:59 add_serio0_serio___serio:ty06pr00id00ex00
18:50:59 add_event7_input___
18:50:59 add_serio_raw_drivers___
18:50:59 add_serio_raw_module___
18:50:59 add_serio1_serio___serio:ty01pr00id00ex00
18:50:59 add_1-0:1.0_usb___usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00
18:50:59 add_1-6:1.1_usb___usb:v04F2pB128d4007dcEFdsc02dp01ic0Eisc02ip00
18:50:59 add_2-0:1.0_usb___usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_v4l1_compat_module___
18:51:00 add_video4linux_class___
18:51:00 add_videodev_module___
18:51:00 add_uvcvideo_module___
18:51:00 add_uvcvideo_drivers___
18:51:00 add_1-6:1.0_usb___usb:v04F2pB128d4007dcEFdsc02dp01ic0Eisc01ip00
18:51:00 add_video0_video4linux___
18:51:00 add_2-1:1.0_usb___usb:v05E3p0608d0702dc09dsc00dp01ic09isc00ip00
18:51:00 add_2-1.2:1.0_usb___usb:v058Fp6362d0126dc00dsc00dp00ic08isc06ip50
18:51:00 add_4-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_3-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_2-1.4:1.0_usb___usb:v046DpC016d0340dc00dsc00dp00ic03isc01ip02
18:51:00 add_input8_input___input:b0003v04F2pB128e4007-e0,1,kD4,ramlsfw
18:51:00 add_6-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_5-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_8-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_7-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_bitblit_module___
18:51:00 add_tileblit_module___
18:51:00 add_softcursor_module___
18:51:00 add_event8_input___usb:v04F2pB128d4007dcEFdsc02dp01ic0Eisc01ip00
18:51:00 add_fbcon_graphics___
18:51:00 add_font_module___
18:51:00 add_fbcon_module___
18:51:00 add_1-0:1.0_usb___usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_1-6:1.0_usb___usb:v04F2pB128d4007dcEFdsc02dp01ic0Eisc01ip00
18:51:00 add_1-6:1.1_usb___usb:v04F2pB128d4007dcEFdsc02dp01ic0Eisc02ip00
18:51:00 add_HDA Intel_drivers___
18:51:00 add_0000:01:00.1_pci_0x10de_0x0be3_pci:v000010DEd00000BE3sv00001179sd0000FF00bc04sc03i00
18:51:00 add_2-0:1.0_usb___usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_card1_sound___
18:51:00 add_mixer1_sound___
18:51:00 add_0000:00:1b.0_pci_0x8086_0x293e_pci:v00008086d0000293Esv00001179sd0000FF00bc04sc03i00
18:51:00 add_card0_sound___
18:51:00 add_2-1.2:1.0_usb___usb:v058Fp6362d0126dc00dsc00dp00ic08isc06ip50
18:51:00 add_audio_sound___
18:51:00 add_pcmC0D0c_sound___
18:51:00 add_dsp_sound___
18:51:00 add_pcmC0D0p_sound___
18:51:00 add_mixer_sound___
18:51:00 add_pcmC0D1p_sound___
18:51:00 add_adsp_sound___
18:51:00 add_2-1.4:1.0_usb___usb:v046DpC016d0340dc00dsc00dp00ic03isc01ip02
18:51:00 add_2-1:1.0_usb___usb:v05E3p0608d0702dc09dsc00dp01ic09isc00ip00
18:51:00 add_4-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_3-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_controlC0_sound___
18:51:00 add_controlC1_sound___
18:51:00 add_5-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_7-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 change_card1_sound___
18:51:00 change_card0_sound___
18:51:00 add_6-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:00 add_8-0:1.0_usb___usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
18:51:01 add_fan_drivers___
18:51:01 add_fan_module___
09:51:03 add_nf_defrag_ipv4_module___
09:51:03 add_ip_tables_module___
09:51:03 add_nf_conntrack_module___
09:51:03 add_nf_conntrack_ipv4_module___
09:51:03 add_xt_state_module___
09:51:03 add_iptable_filter_module___
09:51:03 add_nf_conntrack_irc_module___
09:51:03 add_nf_conntrack_ftp_module___
09:51:03 add_ipt_REJECT_module___
09:51:03 add_nf_nat_module___
09:51:03 add_iptable_nat_module___
09:51:03 add_iptable_mangle_module___
09:51:03 add_vcsa2_vc___
09:51:03 add_vcs2_vc___
09:51:03 add_vcsa3_vc___
09:51:03 add_vcs3_vc___
09:51:07 add_vcsa4_vc___
09:51:07 add_vcs4_vc___
09:51:43 change_4:0:0:0_scsi_HL-DT-ST__scsi:t-0x05
09:51:43 change_sr0_block___
09:51:53 change_4:0:0:0_scsi_HL-DT-ST__scsi:t-0x05
09:51:53 change_sr0_block___



Quote:
Most of that probably is obvious to you,


I wish...

Quote:
.. If you get a pdiag for the older lupu, I could see that the r8192se_pci driver is associated with the device.



...

On booting with the CD version and a barebones 2fs file (only the graphics configured), no browser installed), I checked the kernel, and it's the same 1.6.33.2 as in lupupluslibre.

With this combination, the wireless realtek chip is automatically recognized by network connection wizard. I couldn't run pdiag, because I didn't have a browser to go get and install it, but I ran pupscan, and got the following info:

kernel driver: rtl819xSE
Kernel module: r8192se_pci

I then rebooted from the CF card with lupupluslibre but used another barebones 2fs file.

With this combination, the wireless chip is not detected, but the module r8192se_pci is displayed on the drop down load list



Quote:
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.


What's the procedure for copying the module from lupu528 to lupupluslibre?

Quote:
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.

...


Hmm. Well, as indicated above, the module already shows up in that file, although I haven't copied it nor run depmod. And yet, the wireless chip isn't recognized, and the module doesn't appear in the list of modules available for loading in the connection wizards.

_________________
otropogo@gmail.com facebook.com/otropogo
Back to top
View user's profile Send private message Visit poster's website 
otropogo


Joined: 24 Oct 2009
Posts: 702
Location: Southern Rocky Mt. Trench

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?

_________________
otropogo@gmail.com facebook.com/otropogo
Back to top
View user's profile Send private message Visit poster's website 
bigpup


Joined: 11 Oct 2009
Posts: 5106
Location: Charleston S.C. USA

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.

_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
Back to top
View user's profile Send private message 
otropogo


Joined: 24 Oct 2009
Posts: 702
Location: Southern Rocky Mt. Trench

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.

_________________
otropogo@gmail.com facebook.com/otropogo
Back to top
View user's profile Send private message Visit poster's website 
sheldonisaac

Joined: 21 Jun 2009
Posts: 405
Location: Philadelphia, PA

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?
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1513
Location: Maine, USA

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
rtl8192ce_-se_-de-0005.1230.2011-k2.6.33.2.pet
Description  Realtek rtl8192xx drivers for lupu 528
pet

 Download 
Filename  rtl8192ce_-se_-de-0005.1230.2011-k2.6.33.2.pet 
Filesize  493.52 KB 
Downloaded  283 Time(s) 
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1513
Location: Maine, USA

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
r8192se_pci_timing_experiment-1.pet
Description  Delays module loading, as timing experiment.
pet

 Download 
Filename  r8192se_pci_timing_experiment-1.pet 
Filesize  414 Bytes 
Downloaded  285 Time(s) 
Back to top
View user's profile Send private message 
Semme

Joined: 07 Aug 2011
Posts: 3808
Location: World_Hub

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
Back to top
View user's profile Send private message 
otropogo


Joined: 24 Oct 2009
Posts: 702
Location: Southern Rocky Mt. Trench

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.

_________________
otropogo@gmail.com facebook.com/otropogo
Back to top
View user's profile Send private message Visit poster's website 
otropogo


Joined: 24 Oct 2009
Posts: 702
Location: Southern Rocky Mt. Trench

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@gmail.com facebook.com/otropogo
Back to top
View user's profile Send private message Visit poster's website 
fecklesslout

Joined: 30 Dec 2012
Posts: 2

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.
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1513
Location: Maine, USA

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
Back to top
View user's profile Send private message 
otropogo


Joined: 24 Oct 2009
Posts: 702
Location: Southern Rocky Mt. Trench

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.

_________________
otropogo@gmail.com facebook.com/otropogo
Back to top
View user's profile Send private message Visit poster's website 
rerwin


Joined: 24 Aug 2005
Posts: 1513
Location: Maine, USA

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
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 149 of 190 [2845 Posts]   Goto page: Previous 1, 2, 3, ..., 147, 148, 149, 150, 151, ..., 188, 189, 190 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.2584s ][ Queries: 13 (0.0429s) ][ GZIP on ]