Re: Help getting WiFi working on laptop
On Fri, Jun 18, 2010 at 11:26:07AM -0400, Terry Polzin wrote: > On Fri, 2010-06-18 at 11:20 -0400, Terry Polzin wrote: > > On Fri, 2010-06-18 at 10:13 -0500, Dale J. Chatham wrote: > > > I cannot remember the package, but there is a package that will let > > > you run Windows drivers under Linux. I had to do that to get a > > > wireless card working on an Ubuntu machine (get EMC (www.linuxcnc.org) > > > or something better working on Fedora and we'll talk). > > > > > > If you can't dredge it up, I'll try to find the name of the package, > > > but I suspect we're about to see a dozen posts with it :) > > ndiswrapper is NOT the way to go if the device is supported by the > > kernel. > > > As of early June it appears that Intel has released frimware to make the > card work in linux. > > http://ubuntuforums.org/showthread.php?t=1424177 yum install iwl6050-firmware Hth! John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help getting WiFi working on laptop
On Sat, Jun 19, 2010 at 08:44:21AM -0500, Bruno Wolff III wrote: > On Fri, Jun 18, 2010 at 11:35:58 -0400, > "John W. Linville" wrote: > > > > yum install iwl6050-firmware > > Was this needed because iwl6050-firmware is such a new package? Would it > be expected to be installed by default on F14+ ? Yes -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Installing driver for WiFi adapter
On Tue, Aug 23, 2011 at 11:36:06PM +0100, Paul Smith wrote: > On Tue, Aug 23, 2011 at 9:30 PM, Paul Smith wrote: > >>> >> TP-LINK TL-WN821N > >>> > > >>> > > >>> > Can you post output of lsmod and lsusb. Have you installed the firmware > >>> > for the device into /lib/firmware? If the device is supported by the > >>> > kernel you won't be able to load the module without the firmware > >>> > installed. > >>> > > >>> > Google is your friend. > >>> > >>> Thanks, Terry. > >> > >> Why do you believe you need to install some kind of a driver? From the > >> below, it looks like your card is an atheros chip-based one, and you have a > >> bunch of ath9 modules loaded. > >> > >> What exactly is or is not working for you. > > > > Well, I plug the the USB device and nothing happens. According to the > > manual, a led should be turned on when I plug the USB. > > A possible explanation is here: > > http://forums.fedoraforum.org/showthread.php?t=268068 That relates to the carl9170 driver. We don't have that firmware packaged in Fedora either -- no one ever bothered to review my package of the SH cross compiler used to build the firmware, and I haven't bothered to bang the drum about it either. Anyway, that's a different issue. The ath9k_htc firmware used to be in the linux-firmware tree, but apparently they have stopped updating it there? Not sure... Anyway, you can find the firmware and get it installed by starting here: http://wireless.kernel.org/en/users/Drivers/ath9k_htc#Firmware Hth! John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Red Hat employees listed in manpage have blocked addresses? Unreal.
On Wed, Aug 04, 2010 at 11:35:59AM -0400, Gene Heskett wrote: > Greetings list; > > 2 redhat employees are list as the authors of logrotate in the manpage, so > I just sent them a question because it isn't working as expected. On my logrotate man page, the date at the bottom is 2 Nov 2002 -- not terribly surprising that those email addresses are no good anymore! > Both emails bounced in the time it takes my fetchmail script to go suck the > next cycle. Effectively instantly and permanently. > > So how does one go about asking for logrotate help for a non-redhat > distribution? Open a bug at that distros bugzilla instance (or equivalent)? > I am not running fedora atm. Shame on you! :-) John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Realtek RTL8192E drivers for F13?
On Thu, Aug 05, 2010 at 09:39:54PM -0700, Dave Stevens wrote: > Quoting JD : > > I would first try and download a kernel source tarball from kernel.org, > > and run make xconfig and select rtl8192e from among > > drivers -> staging -> rtl8292e > thank you. If the driver is in staging does that imply its routine > availability in F14? No. Drivers are usually in drivers/staging for a reason, and that reason is generally that they are crap. Perhaps those drivers will work for you. OTOH, they may cause random crashes with potential loss of data, etc -- YMMV. Additionally, the coding practices, design, etc used in the Realtek drivers in particular are...substandard... In Realtek's defense, they do seem at least reasonably willing to work with those who may want to fix/refactor/replace the drivers they provide with supportable drivers under drivers/net/wireless. Unfortunately, they don't seem to be particularly interested in doing that work themselves. Worse, they seem to be prefectly satisfied with continuing to turn-out one crap...err..."staging" driver after another... John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F12/13: Ndiswrapper, topdog Wifi, Thunderbird & network degradation...
On Sun, Aug 29, 2010 at 10:55:43AM -0700, Daniel B. Thurman wrote: > > I have a gateway M-6750 laptop which sports a > Marvell TopDog wifi chip. I have obtained the > latest drivers for this chip, and used ndiswrapper > to hook itself to the XP/Vista topdog driver, and > it at first appears to be working... although there > are crash data appearing in the log files but other > than that, it continues on working. I'm sorry, but I can't offer you any support for ndiswrapper. Did you try the mwl8k driver? John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F12/13: Ndiswrapper, topdog Wifi, Thunderbird & network degradation...
On Mon, Aug 30, 2010 at 08:37:14AM -0700, Daniel B. Thurman wrote: > On 08/30/2010 07:49 AM, John W. Linville wrote: > > On Sun, Aug 29, 2010 at 10:55:43AM -0700, Daniel B. Thurman wrote: > > > >> I have a gateway M-6750 laptop which sports a > >> Marvell TopDog wifi chip. I have obtained the > >> latest drivers for this chip, and used ndiswrapper > >> to hook itself to the XP/Vista topdog driver, and > >> it at first appears to be working... although there > >> are crash data appearing in the log files but other > >> than that, it continues on working. > >> > > I'm sorry, but I can't offer you any support for ndiswrapper. Did you > > try the mwl8k driver? > > > > John > > > No I have not tried this driver... where can I get it? It's part of the Fedora kernel. Also make sure the linux-firmware package is installed. While testing mwl8k, you will want to remove ndiswrapper so as to avoid interference with the in-kernel driver. John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F12/13: Ndiswrapper, topdog Wifi, Thunderbird & network degradation...
On Mon, Aug 30, 2010 at 12:04:20PM -0700, Daniel B. Thurman wrote: > On 08/30/2010 11:31 AM, John W. Linville wrote: > > On Mon, Aug 30, 2010 at 08:37:14AM -0700, Daniel B. Thurman wrote: > > > >> On 08/30/2010 07:49 AM, John W. Linville wrote: > >> > >>> On Sun, Aug 29, 2010 at 10:55:43AM -0700, Daniel B. Thurman wrote: > >>> > >>> > >>>> I have a gateway M-6750 laptop which sports a > >>>> Marvell TopDog wifi chip. I have obtained the > >>>> latest drivers for this chip, and used ndiswrapper > >>>> to hook itself to the XP/Vista topdog driver, and > >>>> it at first appears to be working... although there > >>>> are crash data appearing in the log files but other > >>>> than that, it continues on working. > >>>> > >>>> > >>> I'm sorry, but I can't offer you any support for ndiswrapper. Did you > >>> try the mwl8k driver? > >>> > >>> John > >>> > >>> > >> No I have not tried this driver... where can I get it? > >> > > It's part of the Fedora kernel. Also make sure the linux-firmware > > package is installed. > > > > While testing mwl8k, you will want to remove ndiswrapper so as to > > avoid interference with the in-kernel driver. > > > > John > > > I have looked on F12 repos and I cannot find this driver but > I did find this driver for F13. The problem is, I need this for > F12. Is this driver available for F12? If so, can you give me > a clue what to look for and now this driver is to be installed > and configured, please? What kernel are you using? It is part of the kernel package, not a separate driver. Please attach the output of running 'lspci -n'. It seems mwl8k may not work for much "consumer" hardware. John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F12/13: Ndiswrapper, topdog Wifi, Thunderbird & network degradation...
On Mon, Aug 30, 2010 at 01:35:31PM -0700, Daniel B. Thurman wrote: > On 08/30/2010 12:22 PM, John W. Linville wrote: > > lspci -n > # lspci -n > 00:00.0 0600: 8086:2770 (rev 02) > 00:02.0 0300: 8086:2772 (rev 02) > 00:1b.0 0403: 8086:27d8 (rev 01) > 00:1c.0 0604: 8086:27d0 (rev 01) > 00:1c.1 0604: 8086:27d2 (rev 01) > 00:1d.0 0c03: 8086:27c8 (rev 01) > 00:1d.1 0c03: 8086:27c9 (rev 01) > 00:1d.2 0c03: 8086:27ca (rev 01) > 00:1d.3 0c03: 8086:27cb (rev 01) > 00:1d.7 0c03: 8086:27cc (rev 01) > 00:1e.0 0604: 8086:244e (rev e1) > 00:1f.0 0601: 8086:27b8 (rev 01) > 00:1f.1 0101: 8086:27df (rev 01) > 00:1f.2 0101: 8086:27c0 (rev 01) > 00:1f.3 0c05: 8086:27da (rev 01) > 01:00.0 0180: 105a:4d69 (rev 02) > 01:01.0 0200: 8086:1229 (rev 05) > 02:00.0 0200: 1969:2048 (rev a0) Hmmm... I would have expected an 0280 line. Are any of these your wireless device? Is it plugged-in? John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F12/13: Ndiswrapper, topdog Wifi, Thunderbird & network degradation...
On Mon, Aug 30, 2010 at 01:38:02PM -0700, Daniel B. Thurman wrote: > On 08/30/2010 12:22 PM, John W. Linville wrote: > > What kernel are you using? > # uname -r > 2.6.32.16-150.fc12.i686 mwl8k is enabled on that kernel. You can verify that it is present by running 'modinfo mwl8k'. -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Change wireless interface "sens" value how?
On Sat, Feb 12, 2011 at 03:12:53PM +, mike cloaked wrote: > I am trying to resolve some wireless issue with a laptop running F14, > and I need to change the "sens" (i.e. Sensitivity) value for the > wireless interface. > > However when trying to run the following command as root it fails: > > iwconfig wlan0 sens -65 > > gives output: > Error for wireless request "Set Sensitivity" (8B08) : > SET failed on device wlan0 ; Operation not supported. > > and yet the command "man iwconfig" gives for this section: >sens Set the sensitivity threshold. This define how sensitive is the > card to poor operating conditions (low signal, interference). > Positive values are assumed to be the raw value used by the > hardware or a percentage, negative values are assumed to be dBm. > Depending on the hardware implementation, this parameter may > control various functions. > On modern cards, this parameter usually control handover/roaming > threshold, the lowest signal level for which the hardware > remains associated with the current Access Point. When the sig‐ > nal level goes below this threshold the card starts looking for > a new/better Access Point. Some cards may use the number of > missed beacons to trigger this. For high density of Access > Points, a higher threshold make sure the card is always associ‐ > ated with the best AP, for low density of APs, a lower threshold > minimise the number of failed handoffs. > On more ancient card this parameter usually controls the defer > threshold, the lowest signal level for which the hardware con‐ > siders the channel busy. Signal levels above this threshold make > the hardware inhibits its own transmission whereas signals > weaker than this are ignored and the hardware is free to trans‐ > mit. This is usually strongly linked to the receive threshold, > the lowest signal level for which the hardware attempts packet > reception. Proper setting of these thresholds prevent the card > to waste time on background noise while still receiving weak > transmissions. Modern designs seems to control those thresholds > automatically. > Example : >iwconfig eth0 sens -80 >iwconfig eth0 sens 2 > > So the command should work according to the man command section above. Heh...honestly, does that description seem clear to you? This part of the man page is the poster child for all that is wrong with the wireless extensions API. > Can someone tell me if there is some workaround for this or is this a bug? > > I have already reported as https://bugzilla.redhat.com/show_bug.cgi?id=677008 Neither -- the driver (like all mac80211-based drivers) simply does not support that setting. mac80211-based drivers are simple, and they don't do roaming by themselves. Instead they rely on a userland component (e.g. wpa_supplicant) to take care of roaming for them. Unfortunately, I don't know of any roaming "knobs" to turn for wpa_supplicant (or NetworkManager) -- maybe it would be nice to have one. Even if it were there, I suspect that control of that "knob" would have to flow through NetworkManager if you are using it. John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Change wireless interface "sens" value how?
On Mon, Feb 14, 2011 at 04:30:09PM +, mike cloaked wrote: > On Mon, Feb 14, 2011 at 4:12 PM, John W. Linville wrote: > > > Neither -- the driver (like all mac80211-based drivers) simply does > > not support that setting. mac80211-based drivers are simple, and > > they don't do roaming by themselves. Instead they rely on a userland > > component (e.g. wpa_supplicant) to take care of roaming for them. > > > > Unfortunately, I don't know of any roaming "knobs" to turn for > > wpa_supplicant (or NetworkManager) -- maybe it would be nice to > > have one. Even if it were there, I suspect that control of that > > "knob" would have to flow through NetworkManager if you are using it. > > > > John > > Yes I eventually homed in on the reality that you just described. I > was able to get an ipw2200 based laptop to roam nicely as the driver > did support the sens parameter - and it did switch over to another AP > when the signal from the first went near non-existent - which was what > I was after. However it seems that using my netbook with an ath5k > driver based wireless internal simply won't be able to do it whatever > I do - is there anyone working to make mac80211 drivers more > sophisticated in the future? Maybe roaming is not high on most user's > agenda? Obviously wireless users like to be able to roam. I certainly do it around the house, etc. Are you saying that your ath5k device somehow refuses to disconnect even after you are out of range of the old AP? That would be rather strange. > But the main, and separate, issue I have is with initial > selection of a weak AP signal when a strong one (with same ssid) seems > more logical - and I don't know if this is something that is within > the realm of the driver, the NM code or wpa_supplicant? Yes, I remember that thread. I'm still not sure I understand why you care which AP you connect to, so long as the connection works. In any case, if you are using NetworkManager then the decision for which AP to use will lie somewhere between NM and wpa_supplicant. I'm sorry, but I don't know the details to go beyond that. > I am not sufficiently knowledgeable to know what is possible here. > > I would certainly appreciate knowing what is possible, and what > provides the limitations? The driver will only make an association when directed to do so from userland. If you are using very basic tools (like iwconfig) then there is some minimal suppot in the kernel for scanning and finding an AP. If you use wpa_supplicant, it will control the scanning for APs and choosing one as it sees fit. NetworkManager uses wpa_supplicant, but NM exerts some control over the wpa_supplicant configuration and I'm not fluent on those details. If a connection is lost, the kernel will make no effort to reconnect by itself. If you are using iwconfig, you will need to trigger the reconnection manually. wpa_supplicant will reconnect automatically, possibly to a new AP if the old one is no longer available. Hth... John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora Core 14 wireless issue with Intel Centrino Advanced-N 6200)
On Thu, Feb 24, 2011 at 06:34:19PM -0800, JD wrote: > On 02/24/2011 02:43 PM, Sebastian wrote: > > Hi, > > > > I'm running 2.6.35.11-83.fc14.x86_64 on a Precision M6500 and have a > > wireless issue. > > My wireless device is a Intel Centrino Advanced-N 6200. > > > > Here is the output of dmesg. > > > > [root@cupri iwlwifi-6000-ucode-9.221.4.1]# dmesg | grep iwl > > [ 10.439457] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, > > in-tree:d > > [ 10.439460] iwlagn: Copyright(c) 2003-2010 Intel Corporation > > [ 10.439607] iwlagn :0c:00.0: PCI INT A -> GSI 17 (level, low) -> > > IRQ 17 > > [ 10.439651] iwlagn :0c:00.0: setting latency timer to 64 > > [ 10.439796] iwlagn :0c:00.0: Detected Intel(R) Centrino(R) > > Advanced-N 6200 AGN, REV=0x74 > > [ 10.472925] iwlagn :0c:00.0: Unsupported (too old) EEPROM > > VER=0x423 < 0x434 CALIB=0x5 < 0x4 > > [ 10.473002] iwlagn :0c:00.0: PCI INT A disabled > > [ 10.473014] iwlagn: probe of :0c:00.0 failed with error -22 > > > > Any hints to get wirless working? > > > > cheers, > By the way, I found the correct firmware for your card: > *6000 Images – for Intel Centrino Ultimate-N 6300 and Advanced-N 6200 > *** > http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-6000-ucode-9.221.4.1.tgz Which is, of course, the version provided by the Fedora iwl6000-firmware package... Also, the firmware is not stored on the card. Telling people to "reflash" their firmware for this card is sending them on a fool's errand -- please stop. Sebastian, where did you obtain this card? Is it possibly some engineering sample that escaped out into the wild? That happens from time to time... Wey-yi, is it possible that you picked the wrong value for EEPROM_6000_EEPROM_VERSION in commit 1f4b9665? John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora Core 14 wireless issue with Intel Centrino Advanced-N 6200)
On Fri, Feb 25, 2011 at 08:49:02AM -0300, Sebastian wrote: > Thanks for the help. > > Just some background info and a query. > I downloaded and did a fresh install of 64-bit Fedora about a week ago from > Fedora site.. > Do I understand correctly that when I did the install, FC14 loaded the rev > 09 firmware and that > this is already an old firmware? No. FWIW, the "rev 09" you got from lspci is about the _hardware_ revision. The iwl6000-firmware package should be installed by default, especially on a clean install. It is possible that the base Fedora install has an older version (not sure when the last update happened), but if you have done a "yum update" then you should already have the updated firmware package. > Now, do I understand correctly that I need to keep that old firmware > but roll back to an older Fedora Kernel to get the Intel Centrino Advanced-N > 6200 to play nice > with Fedora? This is incorrect. Please forget it. What seems most likely is that you have an older (possibly pre-release) piece of hardware that has EEPROM data on the card that the driver refuses to recognize. Whether or not it is supposed to recognize it is the only remaining question. Hopefully Wey-yi will chime-in. John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora Core 14 wireless issue with Intel Centrino Advanced-N 6200)
On Fri, Feb 25, 2011 at 08:15:02AM -0800, JD wrote:
> On 02/25/2011 03:49 AM, Sebastian wrote:
> > Thanks for the help.
> >
> > Just some background info and a query.
> > I downloaded and did a fresh install of 64-bit Fedora about a week ago
> > from Fedora site..
> > Do I understand correctly that when I did the install, FC14 loaded the
> > rev 09 firmware and that
> > this is already an old firmware?
> >
> > Now, do I understand correctly that I need to keep that old firmware
> > but roll back to an older Fedora Kernel to get the Intel Centrino
> > Advanced-N 6200 to play nice
> > with Fedora?
> >
> >
> > On Thu, Feb 24, 2011 at 11:34 PM, JD > <mailto:jd1...@gmail.com>> wrote:
> >
> > By the way, I found the correct firmware for your card:
> > *6000 Images – for Intel Centrino Ultimate-N 6300 and Advanced-N 6200
> > ***
> >
> > http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-6000-ucode-9.221.4.1.tgz
> >
> For the time being,
> 0. su - root
> 1. just unpack the tar file into an empty directory:
> mkdir ~/tmpdir
> 2. Untar the file there:
> tar -C ~/tmpdir -zxpf {The path leading up
> to}/iwlwifi-6000-ucode-9.221.4.1.tgz
> <http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-6000-ucode-9.221.4.1.tgz>
> 3. cd iwlwifi-6000-ucode-9.221.4.1
> 4. cp iwlwifi-6000-4.ucode /lib/firmware
> 5. sync; sleep 1; sync; sleep 1; reboot
>
> During reboot, the driver will automatically look for iwlwifi-6000-4.ucode
> and load it into the wifi card.
Good grief...
Do this:
rpm -q iwl6000-firmware
If you see this:
iwl6000-firmware-9.221.4.1-1.fc14.noarch
Then rest assured that you have the proper firmware.
John
--
John W. LinvilleThe truth will set you free, but first it will
linvi...@redhat.com make you miserable. -- James A. Garfield
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora Core 14 wireless issue with Intel Centrino Advanced-N 6200)
On Fri, Feb 25, 2011 at 11:23:34PM -0300, Sebastian wrote: > On Fri, Feb 25, 2011 at 1:06 PM, John W. Linville wrote: > > What seems most likely is that you have an older (possibly pre-release) > > piece of hardware that has EEPROM data on the card that the driver > > refuses to recognize. Whether or not it is supposed to recognize it > > is the only remaining question. Hopefully Wey-yi will chime-in. > > > > > Not sure if I have a pre-release piece of hardware. > Is there a way to find this out for sure? The hardware did work with windows > 7. > Who is Wey-yi? Wey-yi is the primary person at Intel paid to make sure that the driver in question works. :-) -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora Core 14 wireless issue with Intel Centrino Advanced-N 6200)
On Fri, Feb 25, 2011 at 10:14:18PM -0300, Sebastian wrote: > Thank you for those who have taken the time to suggest possible ways to get > my card working. > It seems I have the latest firmware, the one that came with the Fedora > 64-bit DVD, that I downloaded from fedora ~1 week ago. > This is the output John was asking, > > [root@cupri Downloads]# rpm -q iwl6000-firmware > > iwl6000-firmware-9.221.4.1-1.fc14.noarch > > > > John, the wireless card was put into a machine I won on ebay by the same > authorised dell ebay reseller, > from Australia. The machine came with windows 7, I tested it in wondowz and > the card appeared to work fine in windows 7. > > Any other hints on the next steps to take to try to get wireless working > for this card, on Fedora 14? Well, it sounds like the hardware you have may not be entirely "legit", and Intel doesn't want to support it. You could try rebuilding your kernel locally, changing the value of EEPROM_6000_EEPROM_VERSION in drivers/net/wireless/iwlwifi/iwl-eeprom.h to 0x423 (I think that was the value your device reported). I doubt if you like that option, but I'm not sure what else to suggest. The problem is that the EEPROM contains information related to regulatory compliance, so using an unsupported data format could allow your device to operate outside of legal parameters. :-( Perhaps you could get your hardware supplier to swap-out the card for one obtained through more "official" channels? John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora Core 14 wireless issue with Intel Centrino Advanced-N 6200)
On Mon, Feb 28, 2011 at 01:27:59PM -0300, Sebastian wrote: > Thanks John for the message. > Did Wey-yi respond to your mail John? I saw a reply from her -- perhaps she only sent it to me. She confirmed that the required value was as intended. > Is the "too old" Eprom, firmware conjecture reasonable, considering the card > DOES work in Windows 7 as verified? "Reasonable" may be in the eye of the beholder, but it depends on what the driver does with the information it gets from the eeprom. It could be that the current linux driver is doing something with the eeprom info that the windows driver you are using doesn't do. Maybe the linux driver could be more conservative about what it does with eeprom info when the eeprom version is too old? Or maybe the windows driver is at risk of doing the wrong thing already? Maybe some later version of the windows driver will refuse to work with your hardware? I have no idea. For the most part, this is a hardware support issue for the Intel folks. If you can convince them that the earlier eeprom version should be supported for your hardware, I'll be happy to merge a patch to enable it. But if they say that your hardware will operate outside of legal limits with your eeprom's values, then I can't enable it in good conscience. John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora Core 14 wireless issue with Intel Centrino Advanced-N 6200)
Well, FWIW I offered to _merge_ a patch. :-) But, if I get some confirmation from a credible source at Intel that simply honoring the earlier version is sufficient I should have no particular problem squeezing-out such a patch. John On Tue, Mar 01, 2011 at 03:51:34PM -0300, Sebastian wrote: > Thanks a million John for offering to write a patch. Today I spoke to Nathalie > from Intel about this issue, ticket number: 8000209173. Nathalie said she > would write to you on behalf of Intel that since Intel are prepared to have > me use this card in Windows 7 (same EEPROM, same hardware), as Wey-wi also > wrote yesterday, and since this card was installed by the Dell > system-integrator/wholesaler and NOT by me then that same EEPROM version > (VER=0x423 < 0x434 CALIB=0x5 < 0x4) should support my hardware. > > hope this is not a big hassle for you, if I can help with the patch, please > advise. > > > > On Mon, Feb 28, 2011 at 1:42 PM, John W. Linville wrote: > > > On Mon, Feb 28, 2011 at 01:27:59PM -0300, Sebastian wrote: > > > Thanks John for the message. > > > Did Wey-yi respond to your mail John? > > > > I saw a reply from her -- perhaps she only sent it to me. > > She confirmed that the required value was as intended. > > > > > Is the "too old" Eprom, firmware conjecture reasonable, considering the > > card > > > DOES work in Windows 7 as verified? > > > > "Reasonable" may be in the eye of the beholder, but it depends on > > what the driver does with the information it gets from the eeprom. > > It could be that the current linux driver is doing something with > > the eeprom info that the windows driver you are using doesn't do. > > Maybe the linux driver could be more conservative about what it > > does with eeprom info when the eeprom version is too old? Or maybe > > the windows driver is at risk of doing the wrong thing already? > > Maybe some later version of the windows driver will refuse to work > > with your hardware? I have no idea. > > > > For the most part, this is a hardware support issue for the Intel > > folks. If you can convince them that the earlier eeprom version > > should be supported for your hardware, I'll be happy to merge a patch > > to enable it. But if they say that your hardware will operate outside > > of legal limits with your eeprom's values, then I can't enable it in > > good conscience. > > > > John > > -- > > John W. LinvilleThe truth will set you free, but first it > > will > > linvi...@redhat.com make you miserable. -- James A. > > Garfield > > -- > > users mailing list > > users@lists.fedoraproject.org > > To unsubscribe or change subscription options: > > https://admin.fedoraproject.org/mailman/listinfo/users > > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora Core 14 wireless issue with Intel Centrino Advanced-N 6200)
On Tue, Mar 01, 2011 at 12:57:57PM -0800, Guy, Wey-Yi wrote: > On Tue, 2011-03-01 at 12:17 -0800, John W. Linville wrote: > > Well, FWIW I offered to _merge_ a patch. :-) > > > > But, if I get some confirmation from a credible source at Intel that > > simply honoring the earlier version is sufficient I should have no > > particular problem squeezing-out such a patch. > > it will be case by case based on what EEPROM version was in the device. > I am not sure it is a good idea to relax the EEPROM version check in > general. Agree? Well, no, I don't agree. If Intel is releasing hardware with that EEPROM version into the wild and is happy to support it on Windows, I am at a loss to understand why it can't be supported under Linux. It would be one thing if these were just a few engineering samples that escaped to ebay through some nefarious means. But the reports from the user suggest that these came through Dell and are being supported by the Windows driver. That suggests that there is enough correct information in the EEPROM to ensure the device is functioning properly...? John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Wireless drivers
On Mon, Nov 22, 2010 at 04:08:43PM -0700, Petrus de Calguarium wrote: > Mike Chambers wrote: > > > wireless drivers > > in laptops that are mostly supported by Fedora, out of the box > > My laptop has a BROADCOM NETXTREME BCM5751M GIGABIT ETHERNET and it uses the > tg3 kernel module. I just booted up after the initial installation and it > just > worked. The kernel module must have been installed by default. That, of course, is an ethernet device. I still can't recommend a Broadcom wireless device at this time -- hopefully that is changing. John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Wireless drivers
On Mon, Nov 22, 2010 at 03:51:34PM -0600, Mike Chambers wrote: > Would someone be able to possibly tell me the most used wireless drivers > in laptops that are mostly supported by Fedora, out of the box and not > require much 3rd party support? For example, intel, realtek (sp?), > atheros, etc..are those open source drivers or at least supported fairly > good? Is there a website that can easily print/look at and see what > works and what needs 3rd party support? Stick to Intel and Atheros for best support at this time. John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Orinoco WiFi card
On Sat, Nov 27, 2010 at 12:33:53PM +, Timothy Murphy wrote: > I have a ThinkPad T43 with an Orinoco Classic Silver PCMCIA card in it. > This works fine under Windows. > It used to work with the orinoco_cs driver under Fedora, > but I don't think it has worked since Fedora-11. > > Now (under Fedora-14) a kernel OOPS is caused when the card is inserted, > or if the machine is booted with the card in. Does it look like this one? https://bugzilla.kernel.org/show_bug.cgi?id=23932 > I googled for orinoco_cs, but didn't find any recent posts on it. > Is this device no longer supported in Linux? > If so, it seems odd that the driver is still in the kernel. Bugs happen -- it is hard to say what might have changed to trigger what you are seeing. If the driver stays broken it might get dropped, but for now let's just submit bug reports and hope someone finds the time and desire to fix it. :-) John -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: mainstream kernel code contain RT3090 support; why Fedora not include it?
On Tue, Dec 28, 2010 at 04:08:14PM -0200, Itamar Reis Peixoto wrote: > On Tue, Dec 28, 2010 at 4:04 PM, Frantisek Hanzlik wrote: > > Know anyone why Fedora not contain drivers for Ralink RT3090/RT3091/RT3092 > > PCI/PCIe and USB wireless adapters? > > > > It seems as these are supported in mainstream kernel sources, but Fedora for > > any reason not compile them (corresponding symbols CONFIG_RT2800PCI_RT30XX > > and > > CONFIG_RT2800USB_RT30XX are not defined). I found some information from > > beginning this year about improper driver support for these device. But now? > > > > Regards, Franta Hanzlik > > may be because the code is still experimental / broken ? We have a winner... -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Dual wireless access points and connection from f14?
On Sun, Jan 30, 2011 at 07:49:35PM +, mike cloaked wrote: > I have a question for any wireless expert who can help. > > At home I have two wireless access points - one upstairs and one > downstairs - to give a good signal anywhere in the house. > > What I would like is to have a seamless wireless access from any > laptop whether mine or a visitor with the appropriate encryption > password. > > Now my thinking is that using the *same* ssid and encryption protocol > and password for both APs should do the trick nicely - so that is how > I have things set up (with different channel for each AP's output) and > indeed if I power up a laptop running F14 upstairs it connects nicely > with a lovely strong signal - but if I then go downstairs and boot the > same machine then it tries to connect to the upstairs AP despite the > nearest signal about 10 feet away being a great deal stronger! So > the system tries to connect to the last AP it connected to even if a > local signal is stronger - this is illogical behaviour and it is not > clear if NetworkManager or wpa_supplicant is the culprit - or if I am > not supposed to expect things to work that way! Roaming and initial AP selection are really different topics. Neither is as simple as some of the responders have asserted. For roaming "seamlessly", simply using the same ssid and encryption info won't matter much if the AP's aren't bridged. Most consumer APs out of the box use a routed NAT configuration. This means that when you switch between APs you will get a different IP address and connection disruptions will result. To avoid that, you need to make sure the APs are bridging between wireless and ethernet, and further you must ensure that both APs plug into the same bridged segment on the ethernet side. Somewhere on that network there needs to be a single (or several coordinated) DHCP servers so that the same IP address is equally valid on the wireless sides of either AP. In the best cases the APs will runn IAPP or something similar to smooth the wireless handoffs between the two APs, but in practice that is not entirely essential. As for the inital AP selection...you assert that it is illogical to select an AP you know over a stronger AP you may not know. I'm not sure I agree. So long as the known AP remains serviceable, there is no particular reason to switch to another AP simply because he registers a stronger signal. In a perfect world you could easily determine which AP is "better" simply by the signal strength of a beacon, but in reality a number of factors can effect real world "better"-ness. I would only consider the AP selection issue a bug if NM insists on using an unreachable AP even when the other is reachable. In either case, if you want to roam between the APs you should ensure that they are both bridging the wireless connections to the same ethernet subnet.[1] John [1] There are other potential configurations for roaming, including mobile IP and the like. If you (i.e. anyone reading) feels like trying to explain them in an email then feel free. :-) -- John W. LinvilleThe truth will set you free, but first it will linvi...@redhat.com make you miserable. -- James A. Garfield -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Miracast/WiDi Support for Fedora Workstation 24?
On Thu, 2016-10-06 at 16:41 +, 8bits1be...@gmail.com wrote: > I have a WiDi enabled chipset on my laptop and when I was on Windows, > really enjoyed using wireless monitors rather than using a HDMI > cable. I've found mentions of MiracleCast, a *nix implementation of > Miracast, but development seems to have fizzled out. Has anyone got > this working with Fedora? Thoughts on why this technology seems to > be lacking in the *nix world? Seems like every TV and even new Dell > monitors have this built in so IMHO it's not some fringe feature > anymore. The technology exists, I've seen it demo'ed. Getting it to work requires unusually high levels of expertise with both wpa_supplicant and GNOME (or similar), and I think that lack of critical developer mass has been the real hinderance. John -- John W. LinvilleHope is a good breakfast, but it is a linvi...@redhat.com bad supper. -- Sir Francis Bacon ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Kernel update causes wireless to disable
On Wed, 2013-11-13 at 16:55 -0500, Don Levey wrote: > On 11/13/2013 16:20, Jim wrote: > > On 11/13/2013 03:32 PM, Don Levey wrote: > >> My wife's laptop was running fine on kernel 3.10.11-200: > >> Linux croweflies.the-leveys.us 3.10.11-200.fc19.x86_64 #1 SMP Mon Sep 9 > >> > >> ... > > > > In doing this yum will never update any kernel above kernel-3.10.11-200 > > and you should never have any more wireless > > problems until you upgrade to the next version of Fedora. That was really _bad_ advice. It would be extremely rare for a device to be randomly dropped from the kernel, especially one that is still modern and available. > Jim, > I had considered that, but am reluctant to purposely avoid new kernels > with potential fixes to other problems known and unknown. If support > was removed from the kernel, do you know if it was added in terms of > (a)kmod support? I've not yet seen anything about it. As you intuit, cutting oneself off from future kernel updates is an overreaction. If your device has stopped working, then open a bug. John -- John W. LinvilleToday's best will not be good enough linvi...@redhat.com tomorrow -- continue to improve! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: More on miracast support
We are expecting to see a presentation of some work done on Miracast at the Wireless Networking mini-conference that is part of the Linux Plumber's Conference in Düsseldorf in October. See you there? John On Wed, 2014-06-25 at 11:14 -0500, Robert Moskowitz wrote: > I am in the WiFi Alliance Automotive group session. It is clear that > the car infotainment system will be using Miracast to all your phones, > ipads, and such to display their content on the car screens. Example > might be a NAV app. > > So if we want Fedora tablets to play in this game, we do need to get > Miracast working. And no, I do not have the bandwidth and more so the > experience to support such an effort... > > On 06/24/2014 02:39 PM, Robert Moskowitz wrote: > > > > > On 06/24/2014 01:32 PM, JD wrote: > > > > > On Tue, Jun 24, 2014 at 12:22 PM, Fred Erickson > > > wrote: > > > > > > > > > > > > On Jun 24, 2014 8:26 AM, "Robert Moskowitz" > > > wrote: > > > > > > > > > > I am at the WiFi Alliance meeting and all the room projectors > > > have miracast as the perfered projecting method. > > > > > > > > > > So I go looking for miracast and fedora via google and got a > > > few hits, mostly looking for support! > > > > > > > > > > one project saying that Fedora 20 is 'too old'. > > > > > > > > > > So is there any work for miracast support? > > > > > > > > I found the link below on Wikipedia. > > > > > > > > http://www.freedesktop.org/wiki/Software/miracle > > > > > > > > > Seems like this project has the potential to open a big hole > > > into a system's security and user's privacy :) :) > > > > > > > Oh, of course! WiFi Alliance is all about making things EASY. > > > > Safe? Well maybe. Of course this is probably worst than VNC, at > > least showing all around you what is on your screen. > > > > But sometimes in meetings you kind of need it. :( > > > > Now I have to build a system to do builds on. > > > > > > > > > -- John W. LinvilleHope is a good breakfast, but it is a linvi...@redhat.com bad supper. -- Sir Francis Bacon -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: More on miracast support
On Thu, 2014-06-26 at 07:14 -0400, Neal Becker wrote: > John W. Linville wrote: > > > We are expecting to see a presentation of some work done on Miracast at > > the Wireless Networking mini-conference that is part of the Linux > > Plumber's Conference in Düsseldorf in October. > > > > See you there? > > > > John > > > > On Wed, 2014-06-25 at 11:14 -0500, Robert Moskowitz wrote: > >> I am in the WiFi Alliance Automotive group session. It is clear that > >> the car infotainment system will be using Miracast to all your phones, > >> ipads, and such to display their content on the car screens. Example > >> might be a NAV app. > >> > >> So if we want Fedora tablets to play in this game, we do need to get > >> Miracast working. And no, I do not have the bandwidth and more so the > >> experience to support such an effort... > >> > >> On 06/24/2014 02:39 PM, Robert Moskowitz wrote: > >> > >> > > >> > On 06/24/2014 01:32 PM, JD wrote: > >> > > >> > > On Tue, Jun 24, 2014 at 12:22 PM, Fred Erickson > >> > > wrote: > >> > > > > >> > > > > >> > > > On Jun 24, 2014 8:26 AM, "Robert Moskowitz" > >> > > wrote: > >> > > > > > >> > > > > I am at the WiFi Alliance meeting and all the room projectors > >> > > have miracast as the perfered projecting method. > >> > > > > > >> > > > > So I go looking for miracast and fedora via google and got a > >> > > few hits, mostly looking for support! > >> > > > > > >> > > > > one project saying that Fedora 20 is 'too old'. > >> > > > > > >> > > > > So is there any work for miracast support? > >> > > > > >> > > > I found the link below on Wikipedia. > >> > > > > >> > > > http://www.freedesktop.org/wiki/Software/miracle > >> > > > >> > > > >> > > Seems like this project has the potential to open a big hole > >> > > into a system's security and user's privacy :) :) > >> > > > >> > > >> > Oh, of course! WiFi Alliance is all about making things EASY. > >> > > >> > Safe? Well maybe. Of course this is probably worst than VNC, at > >> > least showing all around you what is on your screen. > >> > > >> > But sometimes in meetings you kind of need it. :( > >> > > >> > Now I have to build a system to do builds on. > >> > > >> > > >> > > >> > > >> > > > > I just watched google i/o 2014 keynote, and noticed when talking about > chromecast, that google had 'developed their own protocol'. I guess that > means > they are not using miracast? AFAIK, that is true -- they are not using Miracast. :-( -- John W. LinvilleHope is a good breakfast, but it is a linvi...@redhat.com bad supper. -- Sir Francis Bacon -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
