penalvch, I've now been on 14.04 LTS since it came out, and my wifi is
100% stable. This is without patches or workarounds etc.
Consider this issue closed.
Thank you for all your help!
James.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Yes, this bug definitely occurs at 14.04. I'm not sure if it did NOT
occur under 13.10, because I upgraded to 14.04 immediately after
installing 13.10, and didn't log back into Ubuntu in between.
I have since found this issue reported here:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/
penalvch, I apologize for the delay getting back to you.
A couple days' ago, I tried making the wireless backport code for 3.12,
but I immediately got several errors in the C compilation. I am sorry,
but I can't give you the errors right now as I'm at work, but I remember
they were to do with a s
penalvch, sorry but the command failed at the point of cloning the linux
repository. To make it clear what the error is, I've run the git clone
command on its own:
jamesmeast:~$ git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-stable.git
Cloning into 'linux-stable'...
fatal
penalvch, sorry but on the make -j.. command I get loads of the
following errors referring to what appears to be a corrupt generated
arch/x86/include/generated/asm/syscalls_64.h file:
__SYSCALL_COMMON(ESC[35mESC[K/home/jamesmeast/linux-stable/arch/x86/syscalls/syscall_64.tblESC[mESC[KESC[36mESC[K:
penavlch, The new git clone command worked OK last night. However, I
think the commit status of the fix I'm checking out has changed, because
I now get:
jamesmeast:~/linux$ git checkout 755ca0109f973f23fced94f8dcd8c60e013f270a
fatal: reference is not a tree: 755ca0109f973f23fced94f8dcd8c60e013f27
penalvch, at last the custom kernel build worked OK! I am now running a custom
version:
jamesmeast:~$ uname -a
Linux Rogan-Josh-JME 3.12.0-custom #1 SMP Sun Dec 29 13:28:56 EST 2013 x86_64
x86_64 x86_64 GNU/Linux
However, I was expecting the time/date of the 7260 firmware to change to
today's d
penalvch, thank you for confirming what the commit was for.
I have now reverted back to the original firmware from Ubuntu. FYI, the
firmware is dated 10/21/2013. I will let you know how I get on in due
course.
Thank you!
--
You received this bug notification because you are a member of Kernel
penalch, I've been trying this custom kernel for the past 2 days, and
I've yet to notice any wifi disconnects or errors in the log. NOTE:
This is with the original 10/21/2013 firmware, too.
I'll monitor wifi stability over the next week or so -- and will report
it if I find further issues -- but
penalvch, later today internet download speed became significantly
reduced -- although connectivity was not lost. I looked in dmesg to see
the following trace repeating over and over again:
[28021.389611] ieee80211 phy0: Hardware restart was requested
[28021.389995] iwlwifi :02:00.0: L1 Disab
penalvch, thank you for your patience. The URL in your last post looks
to be for the 3160 card, whereas I have the 7260. So I have instead
downloaded the version from
http://wireless.kernel.org/en/users/Drivers/iwlwifi?action=AttachFile&do=get&target=iwlwifi-7260-ucode-22.1.7.0.tgz,
and upgraded
penalvch, I've been running with the iwlwifi patch + the new 22.1.7.0 7260
firmware for the past few days, and I haven't seen a single error written to
dmesg, ie. it's been running flawlessly!
Therefore, unless you'd like to test further, please feel free to close this
issue!
Following adrien-l
Hi, I am also getting this EXACT problem on my Toshiba P55-A5312 laptop
which uses an Intel 7260 (rev. 73) wireless network controller. Once
the abort occurs, wifi is very unstable, crashing every 5 mins.
Looking at dmesg, the failure appears to originate as:
[ 398.780636] ieee80211 phy0: Hardw
Public bug reported:
I've just upgraded to Ubuntu 13.10. This morning, I couldn't type my
password in at the login prompt. It was as if the keyboard was not
being recognized. I verified that there was a prompt in the password
box, so it's not an input focus issue.
What's interesting is that if
I am sorry for the ambiguity. I initially installed an official 13.10
release (totally wiping over my previous 12.04 install). But the first
time I checked for updates, it immediately upgraded me to 14.04 -- even
though the "System About" box from the gnome desktop still tells me I'm
on 13.10!
I
I'm not sure I would say it 100% works in the 13.10 live environment. I
just noticed that iwlwifi didn't crash while testing for a number of
hours. Even when the crash did occur on my installed 14.04, I'd been
running it without crashes for a significantly longer period of time
than the live 13.1
16 matches
Mail list logo
