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 28 Jul 2014, 00:35
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Drivers
Drivers for Puppy 5.1-5.2.8 with 2.6.33.2 kernel
Post new topic   Reply to topic View previous topic :: View next topic
Page 6 of 13 [182 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, ..., 11, 12, 13 Next
Author Message
WiZard

Joined: 11 Sep 2005
Posts: 43

PostPosted: Mon 01 Aug 2011, 13:23    Post subject:  

@muggins
I have tested tempestuous's wpa fix and it works perfect.
Also, I have some more questions about compiling the drivers, should they be posted in a different thread?

thanks
Gary
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Tue 02 Aug 2011, 22:43    Post subject:  

WiZard wrote:
I have some more questions about compiling the drivers, should they be posted in a different thread?

Yes please. This forum thread is for drivers and utilities for Puppy 5.1/5.2; in other words, end-product.
This is not a forum thread to discuss how to achieve that.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Mon 12 Sep 2011, 00:17    Post subject:  

ath9k wifi driver, country-code issues

Like many/most wifi drivers, the ath9k driver queries your wifi adapter's eeprom to discover its country-code, and this component of the driver has been known to fail, resulting in the driver trying to communicate with the wrong range of channels and frequencies for your country. Obviously, you will fail to connect to a wifi access point in this case.

How will you know? When you run the "dmesg" command you will see something like this -
Quote:
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: xx

or
Quote:
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
...
ath: Country alpha2 being used: xxx


It's feasible that later versions of the ath9k driver may fix this problem, but a solution in the meantime is to manually specify your country-code. This requires a specially modified version of the ath9k driver, now attached.

UPDATE: DON'T install the rfkill-upgrade dotpet! This is likely to conflict with the modified ath9k driver.

Once you have installed the ath9k driver dotpet, use Geany to open /root/my-documents/ath9k-country-codes.txt
and look up your country-code. For example, Australia is "36".
Now add 32768.
36 + 32768 = 32804 - this is the Atheros country-code value for Australia.

Now change your modprobe configuration file;
for older versions of Puppy use Geany to open /etc/modprobe.conf
or for newer versions of Puppy you must create a new text file in /etc/modprobe.d/
I suggest you call this file "ath9k.conf". Any name will do, as long as it ends in ".conf"
In both cases, add this line -
Code:
options ath9k override_eeprom_regdomain=value

Where "value" is the figure we established earlier (32804 for Australia).
Save.

Now reboot, and you should be good.
But it might also be necessary to reset your wifi router, since earlier attempts to connect may have "confused" the router into using the wrong frequency range.
ath9k-set-country-k2.6.33.2.pet
Description  for Puppy 5.1 - 5.2.8
pet

 Download 
Filename  ath9k-set-country-k2.6.33.2.pet 
Filesize  104.08 KB 
Downloaded  393 Time(s) 

Last edited by tempestuous on Sat 17 Sep 2011, 02:26; edited 2 times in total
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Thu 15 Sep 2011, 03:09    Post subject:  

ath5k wifi driver, country-code issues

Same situation as above, but with the ath5k wifi driver.
Follow the instructions above, but when adding the country-code configuration line to your modprobe configuration file, obviously substitute "ath5k" for "ath9k".

And a reminder - DON'T install the rfkill-upgrade dotpet! This is likely to conflict with the modified ath5k driver.
ath5k-set-country-k2.6.33.2.pet
Description  for Puppy 5.1 - 5.2.8
pet

 Download 
Filename  ath5k-set-country-k2.6.33.2.pet 
Filesize  55.3 KB 
Downloaded  369 Time(s) 
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Thu 15 Sep 2011, 07:24    Post subject:  

Here is the jmb38x_xd JMicron jmb38x xD Picture card driver.

The source code was privately emailed to a forum member, details here -
http://www.murga-linux.com/puppy/viewtopic.php?p=563971#563971

As well as the the new xD card driver, 3 other memory stick drivers are upgraded in this package:
jmb38x_ms - JMicron jmb38x MemoryStick driver (supports 2 additional device ID's).
memstick - Sony MemoryStick core driver.
mspro_block - Sony MemoryStickPro block device driver.
jmb38x_xd-k2.6.33.2.pet
Description  for Puppy 5.1 - 5.2.8
pet

 Download 
Filename  jmb38x_xd-k2.6.33.2.pet 
Filesize  48.12 KB 
Downloaded  336 Time(s) 
Back to top
View user's profile Send private message 
rerwin


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

PostPosted: Thu 15 Sep 2011, 12:27    Post subject: Analog Dialup Modem Drivers - Most of them
Subject description: Intel 537s in next posting; SmartLinks not supported.
 

Here (and in next message) are all of the previously available analog dialup modem drivers other than for the SmartLink PCI and USB modems and the HCFPCI modems. The versions are the same as in Wary 5.1.2. The packages can be installed only as needed or all together for a complete set.

The SmartLink modem drivers appear to be almost abandoned by the responsible parties. While work continues on an Ubuntu version of the drivers, the latest from the technion site (3/21/2011, slamr) still fails to connect, spewing "NO CARRIER" messages until stopped manually. As for the USB version, support has apparently been ended altogether. Furthermore, the proprietary component has not kept up with kernel developments and cannot be maintained by anyone but LSI.

Although Barry has included both drivers in Wary, the PCI driver spews "NO CARRIER" and the USB driver spews initialization and shutdown "disaster" messages and may corrupt the data (pupsave) file. Beyond those issues, the PCI modems apparently require reloading of the slamr module and restarting of the user-space daemon (slmodemd) for each connection after the first in a bootup session. Omitting those drivers avoids subjecting users to those risks, which would damage Lucid Pup's reputation for stability.

Note, however, that ALSA modems that use the slmodemd user-space component are still supported.

The HCFPCI driver is omitted because it requires each user to pay the developers US$15 to activate a usable data rate beyond 14.4 kbs. If anyone needs or can use the HCFPCI driver at that speed (or can pay), please tell me and I can add it. My thinking, though, is to avoid suggesting that HCF modems are usable without making the payment, which might be difficult from some parts of the world.

I have tested examples of all of the modems except for HDA modems, modems requiring the non-HDA Agere (agrsm) drivers, and the Intel 537s. Note that the newest driver for the 537s does not support the Dell version of 537EP, making mine useful only for verifying that the variant selector still works.

Regarding the HSF- and Agere HDA drivers: I have my doubts whether they can work, but have no way to experiment with them. There may be mismatches between the versions of ALSA used by Lupu and those expected by the drivers. I believe I saw that the Agere was coded for ALSA 1.0.20 and that the HSF may need a patch to the Intel HDA driver(s) associated with the target ALSA version. Lucid Pup has 1.0.24. Although we could experiment with patching for the HSF HDA driver, my only hope for the Agere is that the newly released version of the HDA driver might help. Beyond that, I have no idea what to do about the Agere HDA mismatch, other than wait for further updates from the developer. Advice from ALSA experts is hereby requested.

EDIT: Peebee reports that the Agere HDA driver works in all recent warys, including 5.1.4.1, but still does not work in Lucid Pup. They all use ALSA 1.0.21a. Unless there is something I have missed about setting up the driver, it appears that the difference in ALSA versions and possibly kernel versions might account for the different behavior.

EDIT: I have concluded that the Agere HDA modem driver cannot be used in lucid pup 5.2.8 because the current ALSA version is different from the version that came with kernel 2.6.33.2 (1.0.24.2 vs. 1.0.21). The driver requires the versions to match. For the future (Three-Headed Dog), we should avoid changing the ALSA version from that of the kernel if we are to have working Agere HDA modem support.

I think I will add logic to the packages containing the Agere 11c11040 driver to prevent installation of the driver if the ALSA versions differ, as shown by these commands:
    cat /proc/asound/version
    alsactl --version
That way, the modem simply will not be detected (because it is not supported) rather than tease the user by detecting it and making it appear to work up to a point.
Richard
dialup_modem_drivers-agere-lucent-k2.6.33.2-20110913.pet
Description  Lucent & Agere modems other than HDA:
- agrsm06pci-2.1.80-20100106-patched1
- agrsm048pci-2.1.60-20100108-patched1
- ltmodem-20100102
pet

 Download 
Filename  dialup_modem_drivers-agere-lucent-k2.6.33.2-20110913.pet 
Filesize  1.37 MB 
Downloaded  247 Time(s) 
dialup_modem_drivers-dgc-ess-i536-pctel-k2.6.33.2-20110913.pet
Description  Modems named in filename:
- dgcmodem-1.13
- ess_2.6-v0.6-patched1
- intel-536EP-537EP_2010_07_19
- pctel-0.9.7-9-rht-11-patched1
pet

 Download 
Filename  dialup_modem_drivers-dgc-ess-i536-pctel-k2.6.33.2-20110913.pet 
Filesize  1.01 MB 
Downloaded  250 Time(s) 
dialup_modem_drivers-hda-hsf-k2.6.33.2-20110913.pet
Description  Conexant HSF & HDA modems and Agere HDA modems:
- hsfmodem-7.80.02.06full-dellhybrid
- agrsm-11c11040-2.1.80-20091225-patched1
pet

 Download 
Filename  dialup_modem_drivers-hda-hsf-k2.6.33.2-20110913.pet 
Filesize  1.57 MB 
Downloaded  267 Time(s) 

Last edited by rerwin on Fri 16 Sep 2011, 22:21; edited 6 times in total
Back to top
View user's profile Send private message 
rerwin


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

PostPosted: Thu 15 Sep 2011, 12:28    Post subject: The 4 variants of the Intel 537 driver.  

(Continuation of previous posting.)

If you know which driver variant you need, you can skip installation of the others, unless you want the complete set.

I changed the .pet names to reflect the origin of the source code. The content is unchanged.
dialup_modem_drivers-intel-537-2010_07_19-k2.6.33.2.pet
Description  Intel 537 modem variant
pet

 Download 
Filename  dialup_modem_drivers-intel-537-2010_07_19-k2.6.33.2.pet 
Filesize  1.4 MB 
Downloaded  255 Time(s) 
dialup_modem_drivers-intel-537EA-2010_07_19-k2.6.33.2.pet
Description  Intel 537EA modem variant
pet

 Download 
Filename  dialup_modem_drivers-intel-537EA-2010_07_19-k2.6.33.2.pet 
Filesize  1.4 MB 
Downloaded  246 Time(s) 
dialup_modem_drivers-intel-537EP-2010_07_19-k2.6.33.2.pet
Description  Intel 537EP modem variant
pet

 Download 
Filename  dialup_modem_drivers-intel-537EP-2010_07_19-k2.6.33.2.pet 
Filesize  1.4 MB 
Downloaded  247 Time(s) 
dialup_modem_drivers-intel-537SP-2010_07_19-k2.6.33.2.pet
Description  Intel 537SP modem variant
pet

 Download 
Filename  dialup_modem_drivers-intel-537SP-2010_07_19-k2.6.33.2.pet 
Filesize  1.4 MB 
Downloaded  245 Time(s) 

Last edited by rerwin on Thu 15 Sep 2011, 19:34; edited 1 time in total
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Thu 15 Sep 2011, 14:54    Post subject:  

Quote:
1a. If you still cannot get a successful wifi connection, you may need to force the b43 driver into PIO mode, which slows down the transfer rate.
Open /etc/modprobe.conf


On the b43 driver, I got my Dell Mini 9 working with only the first step - but only temporarily. Now it again does not connect.

I was going to try your step 1a quoted above, but in 5.2.8 we seem to be in a new regime, as there is no /etc/modprobe.conf to modify. Perhaps your instruction should be updated for late puppies?
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 1369
Location: Malvern, Worcs, UK

PostPosted: Thu 15 Sep 2011, 16:37    Post subject: Re: Analog Dialup Modem Drivers - Most of them  

rerwin wrote:
I have tested examples of all of the modems except for HDA modems, modems requiring the non-HDA Agere (agrsm) drivers, and the Intel 537s. Note that the newest driver for the 537s does not support the Dell version of 537EP, making mine useful only for verifying that the variant selector still works.
Richard


Hi Richard

Started with a pristine frugal install of 528.
Rebooted to create savefile.
Install the Instant Update 001 pet and then
the Agere HDA modem pet dialup_modem_drivers-hda-hsf-k2.6.33.2-20110913.pet

dmesg seemed to suggest the ttyAGS3 had been correctly loaded however when I went into pupdial to test it the driver crashed:

Code:
serial8250_register_ports: BaseAddress 0x4004 Irq 29
ttyAGS3 at I/O 0x4004 (irq = 29) is a AgereModem
agrserial - ret_val 0, call: lt_modem_ops.init_modem
Loading module Agere Modem Interface driver version 2.1.80.0 (2007-10-01)
==> codecType = 0x32
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [<f8f6c9bb>] AzlDmaAllocation+0x81/0x2f9 [agrmodem]
*pde = 00000000
Oops: 0002 [#1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:1c.1/0000:10:00.0/ssb0:0/net/wlan0/statistics/tx_bytes
Modules linked in: agrserial agrmodem i915 drm_kms_helper drm i2c_algo_bit i2c_core snd_hda_codec_analog arc4 ecb snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss b43 snd_pcm mac80211 cfg80211 led_class snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd ohci_hcd soundcore snd_page_alloc serio_raw fbcon tileblit font bitblit softcursor pcspkr shpchp pci_hotplug sg e1000e intel_agp agpgart hp_wmi wmi battery fan container video output thermal evdev button processor ac fuse aufs nls_iso8859_1 nls_cp437 usbhid usb_storage squashfs ssb uhci_hcd ehci_hcd usbcore

Pid: 13479, comm: modem-stats Tainted: P           2.6.33.2 #1 3618/HP 550
EIP: 0060:[<f8f6c9bb>] EFLAGS: 00010202 CPU: 0
EIP is at AzlDmaAllocation+0x81/0x2f9 [agrmodem]
EAX: 00000001 EBX: 00000000 ECX: f4b4d920 EDX: 00000000
ESI: f81e00c4 EDI: f81e0028 EBP: ece5bd34 ESP: ece5bd0c
 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modem-stats (pid: 13479, ti=ece5a000 task=f4ac83c0 task.ti=ece5a000)
Stack:
 00000000 f81ea5f5 f81ea5d8 f81ea5e0 ece5bd28 ece5bda3 000000ff f81e00c4
 f81e00c4 f81e0028 ece5bd54 f8f6d2ad f81e00c4 00000000 f81e0028 ece5bdc4
 c128a594 ece5bda3 ece5bdc4 f8f561e1 f81e00c4 f8151048 00000008 00000001
Call Trace:
 [<f8f6d2ad>] ? CAzlIntelInit+0x381/0x3c4 [agrmodem]
 [<c128a594>] ? printk+0xe/0x11
 [<f8f561e1>] ? LXHardwareStart+0x11de/0x13fb [agrmodem]
 [<c1055bcd>] ? __alloc_pages_nodemask+0xd6/0x470
 [<f8f51998>] ? linux_modem_open+0x45/0x10e [agrmodem]
 [<c102c857>] ? mod_timer+0xea/0xf3
 [<f8eabc0f>] ? modemPortOpen+0x5/0xe [agrmodem]
 [<f8155a6f>] ? serial8250_startup+0x74/0x250 [agrserial]
 [<c11a9348>] ? uart_startup+0x68/0xff
 [<c11a9acd>] ? uart_open+0x10b/0x302
 [<c119a53a>] ? tty_ldisc_setup+0x50/0x58
 [<c11969b9>] ? tty_init_dev+0x17c/0x1e9
 [<c1196d17>] ? tty_open+0x2f1/0x43e
 [<c1073ab0>] ? chrdev_open+0x11f/0x135
 [<c1073991>] ? chrdev_open+0x0/0x135
 [<c107041a>] ? __dentry_open+0x10c/0x1f0
 [<c107058e>] ? nameidata_to_filp+0x29/0x39
 [<c107a6d3>] ? do_filp_open+0x44b/0x82e
 [<c106028a>] ? __do_fault+0x301/0x331
 [<c10616be>] ? handle_mm_fault+0x238/0x4d6
 [<c108168d>] ? alloc_fd+0x52/0xb4
 [<c1070211>] ? do_sys_open+0x49/0xe7
 [<c10184ae>] ? do_page_fault+0x25f/0x275
 [<c10702f3>] ? sys_open+0x1e/0x23
 [<c1002694>] ? sysenter_do_call+0x12/0x26
Code: a5 00 00 89 44 24 08 8d 86 31 a5 00 00 89 44 24 04 c7 04 24 00 00 00 00 e8 63 57 01 00 85 c0 0f 84 71 02 00 00 8b 9e 14 a5 00 00 <c7> 03 01 00 00 00 c7 44 24 04 01 00 00 00 89 34 24 e8 f4 fe fe
EIP: [<f8f6c9bb>] AzlDmaAllocation+0x81/0x2f9 [agrmodem] SS:ESP 0068:ece5bd0c
CR2: 0000000000000000
---[ end trace b84ea72f8dcf64c4 ]---
wlan0: deauthenticated from 94:44:52:0e:80:f3 (Reason: 3)


Let me know if there is anything else I can do to help you test....

Regards
peebee[/code]

_________________
LxPup-14.03 = Puppy + LXDE
Back to top
View user's profile Send private message 
rerwin


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

PostPosted: Thu 15 Sep 2011, 20:22    Post subject: Agere HDA modem issue  

peebee,
This agrsm-HDA thing is maddening, isn't it. I found a posting from a year ago (from someone else) describing the same problem, but with no responses to it. There is a new version of the driver out there, but I do not see any code change that would improve things. You can try it, but don't expect much. You can install it on top of what you have, or start fresh and use it instead of the HDA-HSF combo package.

I see your statements of a year ago about success with wary 060 or 070, or such. Where did all that end up? Does wary 5.12 work for you?

BTW, to keep this thread dedicated to providing drivers without the clutter of debugging conversations, we should take this discussion elsewhere. How about to your original thread on this subject?
http://www.murga-linux.com/puppy/viewtopic.php?p=322455#322455
Richard
agrsm-11c11040-2.1.80-20110811-patched1.pet
Description  New version of agrsm HDA driver - for experimentation
pet

 Download 
Filename  agrsm-11c11040-2.1.80-20110811-patched1.pet 
Filesize  576.55 KB 
Downloaded  254 Time(s) 

Last edited by rerwin on Thu 15 Sep 2011, 20:49; edited 1 time in total
Back to top
View user's profile Send private message 
rerwin


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

PostPosted: Thu 15 Sep 2011, 20:44    Post subject:  

tempestuous wrote:
Now open one of the "modprobe" configuration files, this will depend on which version of Puppy 5.x you have;
for older versions of Puppy it will be /etc/modprobe.conf
and for newer versions it will be /etc/modprobe.d/puppy.conf
The /etc/modprobe.d directory lets us avoid having multiple people maintaining the same file (e.g., puppy.conf, controlled by BK). Any additional module-specific configuration statements should go into separate .conf files named to identify the module(s) affected.

So, the line:
    options ath9k override_eeprom_regdomain=value
might go into ath9k.conf. There are probably other naming schemes that would be good, but the point is to use separate .conf files where appropriate.
Richard
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Fri 16 Sep 2011, 02:05    Post subject:  

Tempestuous, still looking for a modification of your b43 post to take into account the /etc/modprobe.d arrangement in newer Puppies. I cannot see where to put those pio commands. I definitely need to use PIO because dmesg gives "This device does not support DMA on your system. Please use PIO instead." It also says, "ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration."

Anyone?
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Fri 16 Sep 2011, 07:02    Post subject:  

PaulBx1 wrote:
It also says, "ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration."

I can't see where that kernel configuration can be set in the 2.6.33.2 kernel.
Are you really using Puppy 5.2.8? Could it be 529 or Wary?

I really need your full dmesg output. You can do this -
Code:
cd /root
dmesg > dmesg.txt
gzip dmesg.txt

Now you will have a file in /root called "dmesg.txt.gz" which you can attach to the forum.

Last edited by tempestuous on Sat 17 Sep 2011, 02:01; edited 1 time in total
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Fri 16 Sep 2011, 10:26    Post subject:  

Well, I thought I was running 528. Smile At least, in PUPSTATE it says "PUPSFS='sdb1,vfat,/lupu_528.sfs'". There is a 529? Sheesh, I can never keep up.

I too wondered about all those downloads. Did people try your fix, and it works most of the time? I did mention that your fix actually made it work for a short while on my machine. Maybe there is a timing issue or race condition that mostly works out OK? There does seem to be a lot of confusion and difficulty in the forum with this bcmxxxx hardware...

As to the message, doesn't that come from the driver, so it doesn't matter what kernel it is running under? I also thought it was strange the driver wouldn't just fall back to PIO automatically, with maybe a note to the log about it. Yes, I do want to get serious about diagnosing it. Here is the dmesg:
dmesg.txt.gz
Description 
gz

 Download 
Filename  dmesg.txt.gz 
Filesize  8.02 KB 
Downloaded  299 Time(s) 
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Sat 17 Sep 2011, 02:03    Post subject:  

PaulBx1, I have done some digging, and it appears that I need to recompile the b43 wifi driver with PIO mode explicitly (and permanently) enabled ...
... but in the meantime, I have a feeling that the standard b43 driver might "behave" better if it's reloaded after boot up. Pleas try this - once booted, run these two commands:
Code:
rmmod b43
modprobe b43

Now run the "dmesg" command, and see if it looks more healthy - what I'm hoping is that you won't see this -
Code:
b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.

If you do not see this error, then go ahead and run the Network Wizard, and hopefully you will get a successful connection.

But if the error remains, I will have a modified b43 driver shortly.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 6 of 13 [182 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, ..., 11, 12, 13 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Drivers
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.1253s ][ Queries: 12 (0.0065s) ][ GZIP on ]