|Main Archive Page > Month Archives > fedora-users archives|
On Sat, Feb 12, 2011 at 1:59 PM, mike cloaked <email@example.com>wrote:
> On Sat, Feb 12, 2011 at 6:09 PM, JD <firstname.lastname@example.org> wrote:
> > On 02/12/2011 07:48 AM, mike cloaked wrote:
> >> On Sat, Feb 12, 2011 at 3:30 PM, mike cloaked<email@example.com>
> >>> I tested a different laptop with different wireless card:
> >>> 03:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG
> >>> [Calexico2] Network Connection (rev 05)
> >>> [root@lapmike2 ~]# lsmod|grep ipw
> >>> ipw2200 116546 0
> >>> libipw 21037 1 ipw2200
> >>> cfg80211 110951 2 ipw2200,libipw
> >>> lib80211 4107 3 lib80211_crypt_ccmp,ipw2200,libipw
> >>> For that laptop I can change the value of sens!
> >> This driver seems to refuse sens values in dBm - but only as positive
> >> numbers - so I am unsure what the appropriate value is in this case -
> >> but it seems that if the wireless driver is able to change the sens
> >> value and it can be set in dBm then your advice is good - however I
> >> did not realise there was so much variation in support on the driver
> >> side and this whole issue is a lot more complicated than I first
> >> realised!
> > I am also plagued by the same problem for rt2xxx driver.
> > So I opened a bug:
> > https://bugzilla.kernel.org/show_bug.cgi?id=28972
> > You might want to add your comment to this bug and report
> > your device and loaded wireless drivers.
> I am unsure if the responsibility for drivers is directly kernel? Or
> is there an upstream driver devel list for each of the drivers
> separately? For example in my case the ath5k driver does not support
> the sens parameter but the ipw2200 driver on another laptop I use does
> support it but not measured in dBm but a positive integer - so it is
> quite hard to know what those numbers mean in terms of the signal
> level. It seems that there is wide variation in the way the drivers
> were written and minimal documentation about this in an easy to access
> form. Certainly you seem to have to chase up info and spend time doing
> the research!
> I have been getting help from the networkmanager upstream list but in
> the end it looks like it is necessary to get onto whichever upstream
> list corresponds to the driver for your hardware - and I have a
> collection of different chipsets all having different drivers
> (ipw2200, iwl3945, iwl4965, ath5k, rtl8712 which is also supported by
> 8912 etc)
> So I think I will have to do some looking up on which the relevant
> upstream list should be in each case - I guess in your case it will be
> the list for the Realtek driver which is of course not full gpl! There
> is an 8912 driver which is in the kmod staging tree but is not in the
> mainstream kernel - though can be loaded via rpmfusion - not sure if
> this will drive your device though?
> Certainly there is lots to learn for sure!
> mike c
Actually, my chipset is the RalinkTech RT2860, which is now supported
by mainline (AFAIK). It seems serialmonkey no longer maintains this
At any rate, I have had other issues with the rt2xxx driver re: setting the
After I opened a bug at bugzilla.kernel.org, I received a patch which took
of the problem.
So, I am hoping that they will pay attention to this and provide a patch.
-- users mailing list firstname.lastname@example.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines