** Attachment added: lspci-vnvn.log
http://launchpadlibrarian.net/30992412/lspci-vnvn.log
--
STA/wl driver will not activate
https://bugs.launchpad.net/bugs/289360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hi Leann,
Despite previous, brief success, this has once again become an issue for
me. I have not had a functional wireless connection for months now. I
have attached the two requested files. Please let me know if you need
anything else.
** Attachment added: dmesg.log
Public bug reported:
Not sure, but this problem might be what is preventing my machine from
booting up correctly.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from
resuming properly.
Architecture: amd64
ArecordDevices:
List of CAPTURE
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/30290003/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/30290004/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/30290005/BootDmesg.txt
**
Can anyone knowledgeable on the subject explain to me why vino-server is
suddenly enabled on so many machines? Unless this is an innocent typo
in a script, I'm troubled by the idea of a VNC server suddenly up and
running on my machine (unbeknownst to me). Dare we be concerned that
something
Al,
I'm not sure if this will work on 8.10, but I'm running 9.04 and the
latest Nvidia driver (v.180) seems to have restored my STA driver. I'm
able to connect wirelessly now.
By the way, it wasn't just an x64 issue.
Regards
--
STA/wl driver will not activate
I'm running Ubuntu 9.04 (64-bit), and I received the error after
upgrading the following packages today:
apport (0.143) to 0.144
apport-gtk (0.143) to 0.144
compiz-core (1:0.8.2-0ubuntu1) to 1:0.8.2-0ubuntu2
compiz-fusion-plugins-extra (0.7.9+git20090213-0ubuntu1) to 0.8.2-0ubuntu1
After a couple of fresh installs, Ubuntu finally began detecting the
wireless card again. But each time this happened, I would select the
B44 driver, which typically disappeared after shutting down and
restarting.
Once again (and after another fresh install), the system detected the
wireless
Update: I restarted the machine and lost wireless...here is the before
and after for dmesg and lsmod.
** Attachment added: dmesg-lsmod-outputs.txt
http://launchpadlibrarian.net/20388006/dmesg-lsmod-outputs.txt
--
Jockey Not Detecting Broadcom Wireless Card, When It Should Provide Use of
Today, after running apt-get upgrade, I received the Restricted Drivers
Available tray notification. I clicked it, enabled the STA driver,
rebooted, and I've been happily enjoying wireless since.
--
Jockey Not Detecting Broadcom Wireless Card, When It Should Provide Use of
B43 or STA Driver
Scratch that. After shutting down and rebooting, I lost wireless
again...ugh.
--
Jockey Not Detecting Broadcom Wireless Card, When It Should Provide Use of
B43 or STA Driver
https://bugs.launchpad.net/bugs/291271
You received this bug notification because you are a member of Ubuntu
Bugs,
My version of the log doesn't look all that much different...
** Attachment added: jockey.log
http://launchpadlibrarian.net/19438146/jockey.log
--
Jockey Not Detecting Broadcom Wireless Card, When It Should Provide Use of
B43 or STA Driver
https://bugs.launchpad.net/bugs/291271
You
Cryptic, try updating your blacklist file as follows:
1, sudo gedit /etc/modprobe.d/blacklist
2. Find the following section and add the three blacklist items:
# replaced by b43 and ssb.
blacklist bcm43xx
#add these three items
blacklist b43
blacklist b43legacy
blacklist ssb
3. Reboot.
4. Open
I just installed updates for jockey and nividia, and now my solution
doesn't work.
--
Jockey Not Detecting Broadcom Wireless Card, When It Should Provide Use of
B43 or STA Driver
https://bugs.launchpad.net/bugs/291271
You received this bug notification because you are a member of Ubuntu
Bugs,
Yes, in fact, I've been posting to Bug #289360, but this report is more
applicable. I cannot always get jockey to detect my wireless (Broadcom
4313 Rev.2). It detects my ATI drivers without error, but after several
clean installs using both x64 and x86 install CDs, the drivers are
detected
The video driver is definitely involved with the wireless setup. Each
time I upgrade the video driver, it cycles the network connection.
--
Jockey Not Detecting Broadcom Wireless Card, When It Should Provide Use of
B43 or STA Driver
https://bugs.launchpad.net/bugs/291271
You received this bug
Guys, it looks to be an x64 issue. I performed a fresh install of the
Ubuntu 8.10 x86 release today and after installing, rebooting, shutting
down, and restarting, the STA driver continues to work.
My previous, failed attempts all used the x64 version of Ubuntu. I'm
afraid I won't be of much
Thanks Al, your version of rc.local did not work for me. As a follow-up
to one of your previous posts, on the couple of occasions where the STA
driver was available to me in jockey, it was no longer available (or
visible) in jockey after I selected it and rebooted, and I'm still
without wireless.
Today, I performed a clean install using the 8.10 RC CD. I still have
no wireless. My Broadcom 4312 Rev.2 is not being recognized, and I'm
beginning to think that Nvidia is the source of the issue. As you can
see from the attached image, neither the STA nor the B43 wireless
drivers are
Like Al Erola, I selected restricted hardware driver for Broadcom STA, system
requested reboot.
Unlike Al, after rebooting, the STA driver is no longer available and I have no
wireless connectivity. I have installed/removed/reinstalled b43-fwcutter and
the ndiswrapper files, but the STA (or
Here are the contents of my /etc/rc.local file:
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will exit 0 on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
#
** Visibility changed to: Public
--
kino crashed with signal 7 in ORBit_c_stub_invoke()
https://bugs.launchpad.net/bugs/285740
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Matthias, are we stuck without Java support in Firefox until a fix comes
out, or do you have an alternative? Thanks!
--
icedtea-gcjwebplugin broken dependency on icedtea6-plugin
https://bugs.launchpad.net/bugs/284299
You received this bug notification because you are a member of Ubuntu
Bugs,
I had the very same problem. It turns out that each time the kernel was
upgraded on my machine, I chose to keep the current file rather than
using the package maintainer's version. After manually editing
/boot/grub/menu.lst to include the most-recent kernel, I rebooted and
voila - the problem
24 matches
Mail list logo
