I see on 2014-05-13 it says:
"This bug was fixed in the package bcmwl - 6.30.223.141+bdcom-0ubuntu3"
Why wasn't the updated package, from 9 months ago, included in 14.04.2's
install? That would have fixed the issue easily.
For anyone having this problem, rather than do code editing and
compiling
It's possible, but for your system to see it as an update it'd have to
be a newer version than the one you've installed.
So if the respository is updated with a refresh of the version that
shipped with 14.04.2, and it does an update, that refresh should contain
the fix (according to the info on 20
hi jsmitch -
you'll need to install the package "dkms" for the package listed in #13
to install. Normally it's installed when you attempt to update the
proprietary driver module, but if you're on a fresh install and haven't
done that, worry not.
The dkms package is located on the Ubuntu install m
I was able to recreate this same problem on an ASrock Z87E-ITX with an
mSATA SSD and both Ubuntu 12.04.5 and 14.04.1. Same series of errors in
dmesg. I did manage to get a full install done - not sure how - but when
the system boots it's prone to frequent lockups (also, occasionally, at
boot, it cl
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318218/+attachment/4296305/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318218
** Attachment added: "lshw-short.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318218/+attachment/4296304/+files/lshw-short.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318218/+attachment/4296306/+files/lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318218
So, I used gparted to format the drive with a single ext4 partition,
rebooted the system, mounted it, and the errors came back.
It's not a hardware issue. It's some combination of the OS, chipset,
file system in use, and maybe (?) drive type. I can use the same drive
on a Gigabyte board that uses
8 matches
Mail list logo
