I just encountered this with version 20.04. I created an ESP partition
for 259 MB in the installer, but shows as 247 MB in other partition
tools (gparted, fdisk, Windows 10). I didn't notice this until a few
days after installing Ubuntu. This is the main problem: it's not clear
that it deviates
** Description changed:
The keystone endpoint is http://controller:5000 in OpenStack Queens
release. But, in the post-installation script of Gnocchi-api, Gnocchi-
common etc. the endpoint is scripted as http:127.0.0.1:35357 which leads
to failed installation of gnocchi-api.
+
+
Public bug reported:
The keystone endpoint is http://controller:5000 in OpenStack Queens
release. But, in the post-installation script of Gnocchi-api, Gnocchi-
common etc. the endpoint is scripted as http:127.0.0.1:35357 which leads
to failed installation of gnocchi-api.
** Affects: ceilometer
Comment No. 23 by Manuel Baesler worked for me in Windows 10.
lsusb gave me:
Bus 001 Device 040: ID 8564:1000 Transcend Information, Inc. JetFlash
Qemu Flags used:
-device usb-ehci,id=usb,bus=pci.0,addr=0x4 -device
usb-host,vendorid=0x8564,productid=0x1000,id=hostdev0,bus=usb.0
--
You received
Comment No. 23 by Manuel Baesler worked for me in Windows 10.
lsusb gave me:
Bus 001 Device 040: ID 8564:1000 Transcend Information, Inc. JetFlash
Qemu Flags used:
-device usb-ehci,id=usb,bus=pci.0,addr=0x4 -device
usb-host,vendorid=0x8564,productid=0x1000,id=hostdev0,bus=usb.0
--
You received
Christopher,
I just tried Kubuntu 15.04 for AMD64. The problem no longer exists and
the 'wl' module is not installed at all.
Was this fixed but this bug was not updated, or perhaps it was fixed as
part of another bug?
--
You received this bug notification because you are a member of Ubuntu
Christopher,
I don't need a backport. This seems resolved in 15.04 and there is a workaround
in earlier versions, so I am satisfied with this.
You may close this as invalid. If this crops again in future versions, should I
post a comment here or open a new issue?
Thank you for your assistance.
Christopher,
Sorry, I should have been more clear in my previous comment. There was
no checkbox for third party drivers, but I did select a checkbox for
installing third party software, and that apparently also includes third
party drivers (although the user has no way of knowing this).
I had a
From looking at wl_linux.c, it seems to be loading the driver for any
Broadcom device containing the PCI device ID 0x43##. This is incorrect.
In my opinion, this driver should not be installed, or at least not be
loaded, by default in Ubuntu.
If someone would like, they can look at the existing
wl driver supported devices:
http://www.broadcom.com/support/802.11/linux_sta.php
b43 driver supported devices:
http://wireless.kernel.org/en/users/Drivers/b43#Supported_devices
Both 4306 (Me) and 4318 (Todor) are listed for b43 but not wl.
When I first opened this bug, I contacted the support
** Attachment added: dmesg-b43-first.txt
https://bugs.launchpad.net/ubuntu/+bug/1313221/+attachment/4097929/+files/dmesg-b43-first.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313221
Title:
Public bug reported:
I was installing Xubuntu 14.04. It said 'Configuring bcmwl-kernel-source
(amd64)' and in the details DKMS: install completed. and it just froze
there. To continue installation I had to open up a terminal and execute
'sudo killall -9 modprobe'
After getting it installed, I
** Package changed: ubuntu = bcmwl (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313221
Title:
modprobe wl crashes with broadcom 4306
To manage notifications about this bug go to:
Hi Christopher,
I assume your comment is an automated message.
I already tested with the latest daily snapshot and it works fine there. Please
see comment #4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I previously said it was working in 12.04, but that was because it was using
the VESA driver and not radeon.
I did try the latest snapshot of tasty 14.04 and xorg started without issues,
so this bug can be closed.
I also found the following which is the exact same bug:
Public bug reported:
I'm trying Xubuntu 13.10 64-bit. I booted up the live disc and selected 'Try',
and got a blank screen.
I looked at the logs and I'm getting a segmentation fault in my Xorg.0.log file
with the radeon_drv.so module.
I've attached the full Xorg.0.log file. I've also pasted the
Dmesg attached.
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+bug/1259049/+attachment/3925652/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1259049
Title:
17 matches
Mail list logo
