Page 41 of 189 [2827 Posts]   Goto page: Previous 1, 2, 3, ..., 39, 40, 41, 42, 43, ..., 187, 188, 189 Next
Author Message
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?
otropogo
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.
rerwin
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
nooby
PostPosted: Fri 28 Dec 2012, 03:47    Post subject:

Thanks, I where lucky it seemed to work.
But I had problem with getting Adobe flashplayer to work
so not sure what that was about. No need to answer
I will test to run FatDog 64 on it instead. Which has
Flashplayer built into the Seamonkey.
bigpup
PostPosted: Thu 27 Dec 2012, 22:38    Post subject:

nooby wrote:

I had to switch to a new computer on that one
I had Lupu 528-004 instead of latest 005 july.

Is it okay to reuse old savefile for -004
or do I really have to start all over and
manually add all the programs and tweaks and
so much to remember to do in right order?

Have any of you tested and got in trouble?

If save file was made on the same computer, it should be OK.
If save file was made on one computer and you use it on a different computer, there could be problems.
The save file contains specific settings and hardware data for the computer it was originally made on.
The problems you may see are really dependent on the setting changes that have been made, hardware differences between computers, and program settings made in support of specific hardware.
No way of really giving a 100% yes or no answer to question.
otropogo
PostPosted: Thu 27 Dec 2012, 04:34    Post subject: Re: Realtek wireless modules missing in recent Lupu versions
Subject description: Realtek RTL8191SEvB available in lupu v 2, gone in version 4

rerwin wrote:
otropogo wrote:
My Toshiba laptop has built-in Wi-fi which in lupu 528 v.2 is recognized as wlan0 rtl819xSe, and for which the module RTL8191SEvB is available.

However, in the latest version of LupuplusLibre, the wlan is not detected, and no wireless Realtek pci modules are listed.

Is there some way I can load support for this hardware under lupuplus?
As I understand from a google search, the later module for this device is rtl8192se_pci, which is already in lupupluslibre (which I run as my main puppy). Could you install the attached tool package and obtain a pdiag file for your lupupluslibre setup and, if easily do-able, do the same for your older lupu that works? It works the same as the old pmodemdiag tool -- just enter pdiag on a command line and upload the pdiag...tar.gz file it places in your /root directory. Thanks.
Richard


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:

Quote:
3c574_cs |pcmcia| 3Com 3c574 series PCMCIA ethernet driver
3c589_cs |pcmcia| 3Com 3c589 series PCMCIA ethernet driver
8139cp |pci| RealTek RTL-8139C+ series 10/100 PCI Ethernet driver
8139too |pci| RealTek RTL-8139 Fast Ethernet driver
acenic |pci| AceNIC/3C985/GA620 Gigabit Ethernet driver
acx-mac80211 |pci| Driver for TI ACX1xx based wireless cards (CardBus/PCI/USB)
acx |pci| Driver for TI ACX1xx based wireless cards (CardBus/PCI/USB)
adm8211 |pci| Driver for IEEE 802.11b wireless cards based on ADMtek ADM8211
airo_cs |pcmcia| Support for Cisco/Aironet 802.11 wireless ethernet cards. This is the module that links the PCMCIA card with the airo module.
airo |pci| Support for Cisco/Aironet 802.11 wireless ethernet cards. Direct support for ISA/PCI/MPI cards and support for PCMCIA when used with airo_cs.
amd8111e |pci| AMD8111 based 10/100 Ethernet Controller. Driver Version 3.0.7
ar9170usb |usb| Atheros AR9170 802.11n USB wireless
asix |usb| ASIX AX8817X based USB 2.0 Ethernet Devices
at76c50x-usb |usb| Atmel at76x USB Wireless LAN Driver
ath5k |pci| Support for 5xxx series of Atheros 802.11 wireless LAN cards.
ath9k |pci| Support for Atheros 802.11n wireless LAN cards.
atl1c |pci| Atheros 1000M Ethernet Network Driver
atl1e |pci| Atheros Gigabit Ethernet driver
atl1 |pci| Atheros L1 Gigabit Ethernet Driver
atl2 |pci| Atheros Fast Ethernet Network Driver
atmel_cs |pcmcia| Support for Atmel at76c50x 802.11 wireless ethernet cards.
atmel_pci |pci| Support for Atmel at76c50x 802.11 wireless ethernet cards.
axnet_cs |pcmcia| Asix AX88190 PCMCIA ethernet driver
b43legacy |ssb| Broadcom B43legacy wireless driver
b43 |pcmcia| Broadcom B43 wireless driver
b44 |ssb| Broadcom 44xx/47xx 10/100 PCI ethernet driver
bnx2 |pci| Broadcom NetXtreme II BCM5706/5708/5709/5716 Driver
cassini |pci| Sun Cassini(+) ethernet driver
catc |usb| CATC EL1210A NetMate USB Ethernet driver
cdc_eem |usb| USB CDC EEM
cdc_ether |usb| USB CDC Ethernet devices
cdc_subset |usb| Simple 'CDC Subset' USB networking links
de2104x |pci| Intel/Digital 21040/1 series PCI Ethernet driver
dl2k |pci| D-Link DL2000-based Gigabit Ethernet Adapter
dm9601 |usb| Davicom DM9601 USB 1.1 ethernet devices
dmfe |pci| Davicom DM910X fast ethernet driver
donauboe |pci| Toshiba OBOE IrDA Device Driver
e1000e |pci| Intel(R) PRO/1000 Network Driver
e1000 |pci| Intel(R) PRO/1000 Network Driver
e100 |pci| Intel(R) PRO/100 Network Driver
epic100 |pci| SMC 83c170 EPIC series Ethernet driver
fealnx |pci| Myson MTD-8xx 100/10M Ethernet PCI Adapter Driver
fmvj18x_cs |pcmcia| fmvj18x and compatible PCMCIA ethernet driver
forcedeth |pci| Reverse Engineered nForce ethernet driver
gl620a |usb| GL620-USB-A Host-to-Host Link cables
hamachi |pci| Packet Engines 'Hamachi' GNIC-II Gigabit Ethernet driver
hostap_cs |pcmcia| Support for Intersil Prism2-based 802.11 wireless LAN cards (PC Card).
hostap_pci |pci| Support for Intersil Prism2.5-based 802.11 wireless LAN PCI cards.
hostap_plx |pci| Support for Intersil Prism2-based 802.11 wireless LAN cards (PLX).
hp100 |pci| HP CASCADE Architecture Driver for 100VG-AnyLan Network Adapters
i2400m-usb |usb| Driver for USB based Intel Wireless WiMAX Connection 2400M (5x50 & 6050)
igb |pci| Intel(R) Gigabit Ethernet Network Driver
igbvf |pci| Intel(R) 82576 Virtual Function Network Driver
ipg |pci| IC Plus IP1000 Gigabit Ethernet Adapter Linux Driver
ipw2100 |pci| Intel(R) PRO/Wireless 2100 Network Driver
ipw2200 |pci| Intel(R) PRO/Wireless 2200/2915 Network Driver
irda-usb |usb| IrDA-USB Dongle Driver
iwl3945 |pci| Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux
jme |pci| JMicron JMC2x0 PCI Express Ethernet driver
kaweth |usb| KL5USB101 USB Ethernet driver
kingsun-sir |usb| IrDA-USB Dongle Driver for KingSun/DonShine
ks959-sir |usb| IrDA-USB Dongle Driver for KingSun KS-959
ksdazzle-sir |usb| IrDA-USB Dongle Driver for KingSun Dazzle
libertas_cs |pcmcia| Driver for Marvell 83xx compact flash WLAN cards
libertas_tf_usb |usb| 8388 USB WLAN Thinfirm Driver
mcs7780 |usb| IrDA-USB Dongle Driver for MosChip MCS7780
mcs7830 |usb| USB to network adapter MCS7830)
mwl8k |pci| Marvell TOPDOG(R) 802.11 Wireless Network Driver
natsemi |pci| National Semiconductor DP8381x series PCI Ethernet driver
ne2k-pci |pci| PCI NE2000 clone driver
net1080 |usb| NetChip 1080 based USB Host-to-Host Links
nmclan_cs |pcmcia| New Media PCMCIA ethernet driver
ns83820 |pci| National Semiconductor DP83820 10/100/1000 driver
orinoco_cs |pcmcia| Driver for PCMCIA Lucent Orinoco, Prism II based and similar wireless cards
orinoco_nortel |pci| Driver for wireless LAN cards using the Nortel PCI bridge
orinoco_pci |pci| Driver for wireless LAN cards using direct PCI interface
orinoco_plx |pci| Driver for wireless LAN cards using the PLX9052 PCI bridge
orinoco_tmd |pci| Driver for wireless LAN cards using the TMD7160 PCI bridge
pcnet32 |pci| Driver for PCnet32 and PCnetPCI based ethercards
pcnet_cs |pcmcia| NE2000 compatible PCMCIA ethernet driver
pegasus |usb| Pegasus/Pegasus II USB Ethernet driver
plusb |usb| Prolific PL-2301/2302 USB Host to Host Link Driver
prism2_usb |usb|
prism54 |pci| The Prism54 802.11 Wireless LAN adapter
qla3xxx |pci| QLogic ISP3XXX Network Driver v2.03.00-k5
r6040 |pci| RDC R6040 NAPI PCI FastEthernet driver
r8169 |pci| RealTek RTL-8169 Gigabit Ethernet driver
ray_cs |pcmcia| Raylink/WebGear wireless LAN driver
rndis_host |usb| USB Host side RNDIS driver
rndis_wlan |usb| Driver for RNDIS based USB Wireless adapters
rt2400pci |pci| Ralink RT2400 PCI & PCMCIA Wireless LAN driver.
rt2500pci |pci| Ralink RT2500 PCI & PCMCIA Wireless LAN driver.
rt2500usb |usb| Ralink RT2500 USB Wireless LAN driver.
rt2800usb |usb| Ralink RT2800 USB Wireless LAN driver.
rt2870sta |usb| RT2870/RT3070 Wireless Lan Linux Driver
rt61pci |pci| Ralink RT61 PCI & PCMCIA Wireless LAN driver.
rt73usb |usb| Ralink RT73 USB Wireless LAN driver.
rtl8150 |usb| rtl8150 based usb-ethernet driver
rtl8180 |pci| RTL8180 / RTL8185 PCI wireless driver
rtl8187 |usb| RTL8187/RTL8187B USB wireless driver
sc92031 |pci| Silan SC92031 PCI Fast Ethernet Adapter driver
sis190 |pci| SiS sis190/191 Gigabit Ethernet driver
sis900 |pci| SiS 900 PCI Fast Ethernet driver
skge |pci| SysKonnect Gigabit Ethernet driver
sky2 |pci| Marvell Yukon 2 Gigabit Ethernet driver
smc91c92_cs |pcmcia| SMC 91c92 series PCMCIA ethernet driver
smsc9420 |pci|
smsc95xx |usb| SMSC95XX USB 2.0 Ethernet Devices
spectrum_cs |pcmcia| Driver for Symbol Spectrum24 Trilogy cards with firmware downloader
starfire |pci| Adaptec Starfire Ethernet driver
stir4200 |usb| IrDA-USB Dongle Driver for SigmaTel STIr4200
sundance |pci| Sundance Alta Ethernet driver
sungem |pci| Sun GEM Gbit ethernet driver
sunhme |pci| Sun HappyMealEthernet(HME) 10/100baseT ethernet driver
tg3 |pci| Broadcom Tigon3 ethernet driver
tlan |pci| Driver for TI ThunderLAN based ethernet PCI adapters
tulip |pci| Digital 21*4* Tulip ethernet driver
typhoon |pci| 3Com Typhoon Family (3C990, 3CR990, and variants)
uli526x |pci| ULi M5261/M5263 fast ethernet driver
usb8xxx |usb| 8388 USB WLAN Driver
via-ircc |pci| VIA IrDA Device Driver
via-rhine |pci| VIA Rhine PCI Fast Ethernet driver
via-velocity |pci| VIA Networking Velocity Family Gigabit Ethernet Adapter Driver
vlsi_ir |pci| IrDA SIR/MIR/FIR driver for VLSI 82C147
vmxnet3 |pci| VMware vmxnet3 virtual NIC driver
winbond-840 |pci| Winbond W89c840 Ethernet driver
wl3501_cs |pcmcia| Planet wl3501 wireless driver
xirc2ps_cs |pcmcia| Xircom PCMCIA ethernet driver
xircom_cb |pci| Xircom Cardbus ethernet driver
yellowfin |pci| Packet Engines Yellowfin G-NIC Gigabit Ethernet driver
zaurus |usb| Sharp Zaurus PDA, and compatible products
zd1201 |usb| Driver for ZyDAS ZD1201 based USB Wireless adapters
zd1211rw |usb| USB driver for devices with the ZD1211 chip.


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
rerwin
PostPosted: Wed 26 Dec 2012, 13:00    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:
My Toshiba laptop has built-in Wi-fi which in lupu 528 v.2 is recognized as wlan0 rtl819xSe, and for which the module RTL8191SEvB is available.

However, in the latest version of LupuplusLibre, the wlan is not detected, and no wireless Realtek pci modules are listed.

Is there some way I can load support for this hardware under lupuplus?
As I understand from a google search, the later module for this device is rtl8192se_pci, which is already in lupupluslibre (which I run as my main puppy). Could you install the attached tool package and obtain a pdiag file for your lupupluslibre setup and, if easily do-able, do the same for your older lupu that works? It works the same as the old pmodemdiag tool -- just enter pdiag on a command line and upload the pdiag...tar.gz file it places in your /root directory. Thanks.
Richard

Update 12/28/2012: Uploaded correction to archive directory, after download number 9. As with pmodemdiag, the directory should be "pdiag...". But the previous version had it as "tmp/pdiag...". So if you told the tarball to extract to "/tmp", you would find the pdiag directory in /tmp/tmp/ instead of /tmp. There is no functional difference, so the old one is fine for testing.

Update 12/30/2012: Uploaded package to remove collection of potentially sensitive wireless connection data related to the network wizard, after download number 12.
James C
PostPosted: Tue 25 Dec 2012, 02:42    Post subject:

Decided to set up another old Linux box while waiting for Santa ........ so a fresh full install of Lucid 528.005. Zero problems....everything good ootb.

# report-video
VIDEO REPORT: Lucid , version 528

Chip description:
oem: NVIDIA
product: MCP61 - mcp61-86 Chip Rev

Driver used by Xorg:
nvidia

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
# glxgears
8253 frames in 5.0 seconds = 1650.600 FPS
10601 frames in 5.0 seconds = 2120.200 FPS
11040 frames in 5.0 seconds = 2208.000 FPS
11038 frames in 5.0 seconds = 2207.600 FPS
11012 frames in 5.0 seconds = 2202.400 FPS
11020 frames in 5.0 seconds = 2204.000 FPS

-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
Memory : 3375MB (192MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Tue 25 Dec 2012 12:41:29 AM CST
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA NVidia
-Inp-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
Memory : 3375MB (192MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Tue 25 Dec 2012 12:41:29 AM CST
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA NVidia

Code:
# free
              total         used         free       shared      buffers
  Mem:      3375292       488512      2886780            0        20664
 Swap:      6211576            0      6211576
Total:      9586868       488512      9098356
#
otropogo
PostPosted: Tue 25 Dec 2012, 02:11    Post subject: Realtek wireless modules missing in recent Lupu versions
Subject description: Realtek RTL8191SEvB available in lupu v 2, gone in version 4

My Toshiba laptop has built-in Wi-fi which in lupu 528 v.2 is recognized as wlan0 rtl819xSe, and for which the module RTL8191SEvB is available.

However, in the latest version of LupuplusLibre, the wlan is not detected, and no wireless Realtek pci modules are listed.

Is there some way I can load support for this hardware under lupuplus?

UPdate: Have discovered that when booting the latest lupupluslibre without my 2fs file, the wireless realtek 819 wireless pci modules are available in the load list. So it would seem that my 2fs file is somehow substituting another selection which doesn't include these modules.

I've never used the function which permits removal of bundled material, nor have I remastered, so whatever is happening occurred automatically, and I find that disturbing.

I don't want to abandon my 1.4GB 2fs file with all of its added applications and configurations, some of which may not be available in lupus 528.

So - is there a way to fix this problem while keeping my 2fs file?
GeraSats
PostPosted: Fri 21 Dec 2012, 12:22    Post subject:

Take more than a year as the main distribution in the full installation. When changing your computer's hard drive moved to an archive file, opened the drive alive and put grub. No problem.
Excellent distribution, and to fill the program has no equal.
nooby
PostPosted: Thu 20 Dec 2012, 16:39    Post subject:

Yes it works thanks.
Very good distro this one. Thanks
Display posts from previous:   Sort by:   
Page 41 of 189 [2827 Posts]   Goto page: Previous 1, 2, 3, ..., 39, 40, 41, 42, 43, ..., 187, 188, 189 Next

Powered by phpBB © 2001, 2005 phpBB Group