Re: Wifi connection issues with Intel?
by poma
On 11.06.2014 13:33, Josh Boyer wrote:
> On Wed, Jun 11, 2014 at 12:35:36PM +0200, poma wrote:
>> On 11.06.2014 10:18, poma wrote:
>>> On 11.06.2014 04:34, Richard Shaw wrote:
>>>> On Tue, Jun 10, 2014 at 6:09 PM, poma <pomidorabelisima(a)gmail.com> wrote:
>>>>
>>>>> Firmware, kernel module or userspace? :)
>>>>>
>>>>
>>>> # uname -r
>>>> 3.14.5-200.fc20.x86_64
>>>>
>>>> No clue on firmware, I'm not exactly sure how to check which is being
>>>> loaded...
>>>>
>>>>
>>>> Did you mention an exact hardware in question?
>>>>>
>>>>
>>>> 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev
>>>> 24)
>>>> Subsystem: Intel Corporation Centrino Advanced-N 6235 AGN
>>>> Flags: bus master, fast devsel, latency 0, IRQ 48
>>>> Memory at f0200000 (64-bit, non-prefetchable) [size=8K]
>>>> Capabilities: [c8] Power Management version 3
>>>> Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>>>> Capabilities: [e0] Express Endpoint, MSI 00
>>>> Capabilities: [100] Advanced Error Reporting
>>>> Capabilities: [140] Device Serial Number c8-f7-33-ff-ff-f4-2d-ba
>>>> Kernel driver in use: iwlwifi
>>>> Kernel modules: iwlwifi
>>>>
>>>>
>>>> BTW how are you sure RF environment ain't changed?
>>>>>
>>>>
>>>> Nothing new has come in or left the house since the problem...
>>>>
>>>> Thanks,
>>>> Richard
>>>
>>>
>>> - KERNEL:
>>> $ curl -s https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.6 | grep iwlwifi
>>>
>>> So pick up kernel-3.14.6-200.fc20.x86_64.rpm
>>> http://koji.fedoraproject.org/koji/buildinfo?buildID=531773
>>>
>>> You can also try with kernel-core-3.15.0-1.fc21.x86_64.rpm
>>> http://alt.fedoraproject.org/pub/alt/rawhide-kernel-nodebug/x86_64/
>>>
>>>
>>> - FIRMWARE:
>>> $ modinfo -F firmware iwlwifi
>>>
>>> # yum --enablerepo updates-testing install iwl6000g2b-firmware
>>>
>>> $ rpm -qf /usr/lib/firmware/iwlwifi-6000g2b-6.ucode
>>> iwl6000g2b-firmware-17.168.5.2-38.fc20.noarch
>>>
>>> According to
>>> http://wireless.kernel.org/en/users/Drivers/iwlwifi#Firmware
>>> Intel® Centrino® Advanced-N 6235 goes with iwlwifi-6000g2b-ucode-18.168.6.1.tgz
>>> i.e. iwlwifi-6000g2b-6.ucode
>>> also stated within firmware itself:
>>> https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/...
>>> "IWL.6000g2b.fw.v18.168.6.1.build.0"
>>>
>>> However in Fedora it is packaged as "17" i.e. iwl6000g2b-firmware-17.168.5.2-38.fc20.noarch
>
> Probably because I forgot to increment the version number.
>
>>> Josh, do these two firmwares should be in their own packages as "18"?
>
> No.
>
>>>
>>> Intel® Centrino® Advanced-N 6235 - iwlwifi-6000g2b-ucode-18.168.6.1
>>> i.e. iwlwifi-6000g2b-6.ucode - "IWL.6000g2b fw v18.168.6.1 build 0"
>>> in iwl6000g2b-firmware-18.168.6.1-1.f$releasever.noarch.rpm
>>>
>>> and
>>>
>>> Intel® Centrino® Advanced-N 6205 - iwlwifi-6000g2a-ucode-18.168.6.1
>>> i.e. iwlwifi-6000g2a-6.ucode - "IWL.6000g2a fw v18.168.6.1 build 0"
>>> in iwl6000g2a-firmware-18.168.6.1-1.f$releasever.noarch.rpm
>>
>> e.g.
>>
>> - Intel® Centrino® Advanced-N 6235
>>
>> 1. Rename
>> iwl6000g2b-firmware-17.168.5.2-38.fc20.noarch
>> to
>> iwl6000g2b5-firmware-17.168.5.2-38.fc20.noarch
>> /usr/lib/firmware/iwlwifi-6000g2b-5.ucode
>>
>> 2. Create
>> iwl6000g2b6-firmware-18.168.6.1-1.f20.noarch.rpm
>> /usr/lib/firmware/iwlwifi-6000g2b-6.ucode
>>
>>
>> - Intel® Centrino® Advanced-N 6205
>>
>> 3. Rename
>> iwl6000g2a-firmware-17.168.5.3-38.fc20.noarch
>> to
>> iwl6000g2a5-firmware-17.168.5.3-38.fc20.noarch
>> /usr/lib/firmware/iwlwifi-6000g2a-5.ucode
>>
>> 4. Create
>> iwl6000g2a6-firmware-18.168.6.1-1.f20.noarch.rpm
>> /usr/lib/firmware/iwlwifi-6000g2a-6.ucode
>
> No. That's really pointless work and makes the linux-firmware package
> even more complicated that it already is.
>
> The firmware is getting installed and it's correct. Most times people
> don't need to worry about which firmware they have, and if they do they
> can consult the WHENCE file installed in /usr/share/doc/linux-firmware/.
>
> josh
>
IF I correctly understood
http://wireless.kernel.org/en/users/Drivers/iwlwifi#Firmware
Fedora is shipping at least one unnecessary firmware version compared to the kernels used,
e.g. for
Intel® Centrino® Advanced-N 6205
IS required only iwlwifi-6000g2a-6.ucode - kernel 3.2+
and NOT iwlwifi-6000g2a-5.ucode - kernel 2.6.35+
iwlwifi-6000g2b-[56].ucode is a bit more complex case because it refers to four devices i.e.
Intel® Centrino® Advanced-N 6230
Intel® Centrino® Wireless-N 1030
Intel® Centrino® Wireless-N 130
Intel® Centrino® Advanced-N 6235
IF I correctly understood
http://wireless.kernel.org/en/users/Drivers/iwlwifi#Firmware
even the module itself "incorrectly" advertises some of the firmwares,
$ modinfo -F firmware iwlwifi
iwlwifi-100-5.ucode
iwlwifi-1000-5.ucode
iwlwifi-135-6.ucode
iwlwifi-105-6.ucode
iwlwifi-2030-6.ucode
iwlwifi-2000-6.ucode
iwlwifi-5150-2.ucode
iwlwifi-5000-5.ucode
iwlwifi-6000g2b-6.ucode
iwlwifi-6000g2a-5.ucode <-
iwlwifi-6050-5.ucode
iwlwifi-6000-4.ucode
iwlwifi-7265-8.ucode
iwlwifi-3160-8.ucode
iwlwifi-7260-8.ucode
iwlwifi-8000-8.ucode
Comment by you folks at Intel? :)
poma
9 years, 10 months
Wireless connect fails on laptop wake
by Bill Murray
Dear Fedorians,
I am using F20 gnome on my laptop, and have great
suspend/resume
as I wander from meeting to meeting in different rooms. Except for the
wireless.
Maybe 1 time in 3 or 50-50 the wireless fails to connect on resume - it
just loops.
It is easily fixed: I disable the wireless either in software or
hardware and re-enable
and it works 100%. So it seems something is not optimal in the wireless
recovery.
I compare /var/log/mesages from good and bad sessions, and I find for a
resume session:
NetworkManager[1801]: <info> (wlp2s0): supplicant interface state:
disconnected -> inactive
NetworkManager[1801]: <info> (wlp2s0): supplicant interface state:
inactive -> scanning
wlp2s0: authenticate with XXX.YY....
wlp2s0: direct probe to XXX.YY.. (try 1/3)
This then goes into an authenticate -> disconnect loop
while for a good session where I switch off wireless in NM and on again:
NetworkManager[1801]: <info> (wlp2s0): supplicant interface state:
inactive -> scanning
wlp2s0: authenticate with XXX.YY....
wlp2s0: send auth to to XXX.YY.. (try 1/3)
this goes on to connect just fine.
Any ideas what is wrong with my suspended session? It would be nice to
be able to open
my laptop and have it just work....
Thanks for your ideas!
Bill
--
Bill Murray ---- ATLAS
STFC/Warwick at: Bat 40-4-C28, CERN,1211 Meyrin, Geneve 23, Switzerland
Tel:- CERN +41 22 7678432
9 years, 10 months
f18 keyboard and panel volume controls
by Mike Wright
Hi all,
I put f18 onto a system three days ago and am having a lot of trouble
making some basic things work.
The old way of setting up keyboard shortcuts is gone and the mapping
between the keyboard and XF86, such as Volume Mute <=> XF86Mute are
gone. They now map to Pragha. We'll have to chalk that one up to sheer
brilliance on somebody's part.
The standard Volume Control on the top panel is also gone and I haven't
been able to find a replacement for it either. Having to open Audio
Mixer and/or Pulseaudio Volume Control (whose title bar makes no mention
of Pulseaudio) is absurd to the extreme.
Side note: there is now so much bloat that the only way to get VLC to
play video and audio in sync is to run it --high-priority. That's a
first for me.
If anybody knows how to bring back keyboard control of volume and
muting, and how to put a volume control back on the top panel I'd be
most appreciative.
Thanks a million for any help,
Mike Wright
ps. If someone finds a bunch of marbles please be so kind as to return
them to me.
9 years, 10 months
Save everybody some surprises in Fedora 22!
by Andre Robatino
> The time when DNF will take over from Yum in Fedora is nearing. We're
> wondering: is there stuff people are still missing from DNF that they
> have got recently in Yum? Or even something else! We've put together a
> very short and simple survey. Let your opinion be heard!
> http://dnf.baseurl.org/2014/06/06/vote-for-yum-features-that-you-miss-in-...
The list of missing yum options is both outdated and incomplete. For
example, it's missing "includepkgs" (a repository option), for people who
need to access specific packages from non-Fedora compatible repos. On the
other hand, it includes "deltarpm", although dnf has supported this for a
while now.
Sorry for replying out of thread, but I normally use Gmane to reply, and for
some reason this thread never showed up there. (Normally there's just a
delay, but it's past that point now.)
9 years, 10 months
Trying do get F20 up
by don fisher
All of the configuration files have changed from my previous version (I
think it is F17). Is there documentation on how to set up acpi? Is there
documentation of all of these other changes? I am command line
orientated and have trouble finding where things are. Pleases help a
non-windows orientated person.
Thanks
9 years, 10 months
losing WiFi Access - prompted for password
by SternData
F18...
Over the last few days, I'm getting prompted to re-enter my password for
my WiFi network. It's not the router because no other device on the
network seems to be having problems.
Potential changes on my system include
May 07 21:39:32 Updated: 1:wpa_supplicant-1.1-1.fc18.x86_64
May 25 15:33:44 Installed: kernel-3.9.3-201.fc18.x86_64
May 27 08:06:42 Updated:
1:NetworkManager-glib-0.9.8.1-3.git20130514.fc18.x86_64
May 27 08:06:47 Updated: 1:NetworkManager-0.9.8.1-3.git20130514.fc18.x86_64
May 27 08:06:53 Updated:
network-manager-applet-0.9.8.1-4.git20130514.fc18.x86_64
Given that this has really started the day before yesterday, I suspect
it has something to do with the NetworkManager update. Is anyone else
having this problem?
(Please -- do not tell me to "dump the evil NetworkManager". I'm trying
to solve a problem here, not make some stand against the tide. Thanks.)
--
-- Steve
9 years, 10 months
Install problem (Fedora 20-32bit
by Doug
Trying to install Fedora 20 32-bit version on a multiboot system
(Windows 8.1 + PCLOS 32 + PCLOS 64) into a standard partition.
Got up past setting passwords for root and user. Then it crashed with
the following message:
***********************************
The following error occurred whil installing. This is a fatal error and
installation will be aborted.
error population transaction: failure:
Packages/s/systemd-python-208-9.fe20.:686.rpm from anaconda:
[Errno 256] No more mirrors to try.
*************************************
Machine is desktop 64-bit Intel processor with 8GB ram, connected to
Internet, Nvidia graphics. Uses BIOS, not UEFI.
I want to install Fedora in order to run Linux version of DraftSight cad
program, which has a Fedora rpm available and
which does not run on PCLOS, for unknown reasons.
Suggestions, please.
Thanx--doug
9 years, 10 months
REALLY quiting skype
by Robert Moskowitz
So I have Skype on a f20 i686 system and actually USED it for a business
call. I then quited Skype.
But later I was looking into some things on the system and found that
Skype still had a process running. I could not find it on the Gnome
desktop anywhere, so I just killed the process. But I should be able to
do this 'more normally'?
thanks
9 years, 10 months
systemctl restart network, VMs and suspend
by Aleksandar Kostadinov
Hello,
I already filed a bugzilla issue with this [1] but I'd like to know if
anybody else has troubles with VMs' network after suspend. And if others
are able to do a "systemctl restart network" successfully.
I mean, am I an isolated case because of some unknown configuration I
have or is this common?
What I do is:
launch VM
suspend laptop
wake up laptop after awhile (1 hour maybe)
network of VM loses default route
systemctl restart network # fails on both fedora 20 - guest and host
I'll appreciate if somebody else with same experience comments in the
bugzilla issue directly.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1100034
9 years, 10 months
Joining the modern era: Xinerama to XRandR
by Noah Cutler
Got RandR setup in place here with a 3 monitor setup, but have hit a sticky
wicket relative to previous Xinerama setup (which I have reverted to until
I find a suitable workaround).
With Xinerama we can stich together separate X screens under a single large
display. This allows me to use my monitor calibration/screen inversion
application *xcalib*, on a per screen basis.
For example, by default all screens are inverted (i.e. black background)
but sometimes I need to see a website I'm working on as it really looks
against a white background. With Xinerma I can toggle background color on a
single monitor. With RandR all 3 screens invert at once, which is jarring
on the eyes.
Is there way to get RandR to simulate Xinerma multiple pseudo separate X
screens? Barring that, another calibration/inversion program that allows
one to change state on a per physical monitor basis?
*xcalib* only works with screen x/display :x and RandR only has a single
screen, thus the all-at-once jarring state change.
Thanks for ideas
9 years, 10 months