bluez-firmware_1.2-1_all.deb puts the driver in /usr/lib/firmware/
rather than /lib/firmware/. When I create a symlink the driver loads.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Looking at the debian copyright file, it should be possible to include
'bluez-firmware' in restricted repository.
Can someone confirm?
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
Rodrigo,
It appears that the files must be right in the /lib/firmware directory,
not in one of the kernel-specific subdirectories.
This raises a question: if Ubuntu is not going to include these files in
a package, and the Debian package puts the files in an incompatible
location, the proper plac
Oops, my mistake. I forgot that I am still running dapper on the system
that I did this on. I cannot say if the same is still true for feisty or
later versions. I will be upgrading it soon and will check again.
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received thi
Yes, please include the firmwares on restricted.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi I move the files as Dan Lipsitt said:
"find /lib/firmware -iname '*bcm*'"
/lib/firmware/2.6.20-15-386/BCM2033-MD.hex
/lib/firmware/2.6.20-15-386/BCM-LEGAL.txt
/lib/firmware/2.6.20-15-386/BCM2033-FW.bin
still nothing happens:
hcitool dev
Devices:
Any ideas?
--
missing firmware for bcm2033
ht
Available in 8.10 alpha.
** Changed in: linux-restricted-modules (Ubuntu)
Sourcepackagename: bluez-utils => linux-restricted-modules
Status: New => Fix Released
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received this bug notification because you are a membe
Available in 8.10 alpha.
** Changed in: linux-restricted-modules (Ubuntu)
Sourcepackagename: bluez-utils => linux-restricted-modules
Status: New => Fix Released
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received this bug notification because you are a membe
bluez-firmware_1.2-1_all.deb puts the driver in /usr/lib/firmware/
rather than /lib/firmware/. When I create a symlink the driver loads.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Looking at the debian copyright file, it should be possible to include
'bluez-firmware' in restricted repository.
Can someone confirm?
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
Yes, please include the firmwares on restricted.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
bluez-firmware_1.2-1_all.deb puts the driver in /usr/lib/firmware/
rather than /lib/firmware/. When I create a symlink the driver loads.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Looking at the debian copyright file, it should be possible to include
'bluez-firmware' in restricted repository.
Can someone confirm?
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
Rodrigo,
It appears that the files must be right in the /lib/firmware directory,
not in one of the kernel-specific subdirectories.
This raises a question: if Ubuntu is not going to include these files in
a package, and the Debian package puts the files in an incompatible
location, the proper plac
Oops, my mistake. I forgot that I am still running dapper on the system
that I did this on. I cannot say if the same is still true for feisty or
later versions. I will be upgrading it soon and will check again.
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received thi
Hi I move the files as Dan Lipsitt said:
"find /lib/firmware -iname '*bcm*'"
/lib/firmware/2.6.20-15-386/BCM2033-MD.hex
/lib/firmware/2.6.20-15-386/BCM-LEGAL.txt
/lib/firmware/2.6.20-15-386/BCM2033-FW.bin
still nothing happens:
hcitool dev
Devices:
Any ideas?
--
missing firmware for bcm2033
ht
Rodrigo,
It appears that the files must be right in the /lib/firmware directory,
not in one of the kernel-specific subdirectories.
This raises a question: if Ubuntu is not going to include these files in
a package, and the Debian package puts the files in an incompatible
location, the proper plac
Oops, my mistake. I forgot that I am still running dapper on the system
that I did this on. I cannot say if the same is still true for feisty or
later versions. I will be upgrading it soon and will check again.
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received thi
Available in 8.10 alpha.
** Changed in: linux-restricted-modules (Ubuntu)
Sourcepackagename: bluez-utils => linux-restricted-modules
Status: New => Fix Released
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received this bug notification because you are a membe
Hi I move the files as Dan Lipsitt said:
"find /lib/firmware -iname '*bcm*'"
/lib/firmware/2.6.20-15-386/BCM2033-MD.hex
/lib/firmware/2.6.20-15-386/BCM-LEGAL.txt
/lib/firmware/2.6.20-15-386/BCM2033-FW.bin
still nothing happens:
hcitool dev
Devices:
Any ideas?
--
missing firmware for bcm2033
ht
Yes, please include the firmwares on restricted.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Available in 8.10 alpha.
** Changed in: linux-restricted-modules (Ubuntu)
Sourcepackagename: bluez-utils => linux-restricted-modules
Status: New => Fix Released
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received this bug notification because you are a membe
Yes, please include the firmwares on restricted.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Available in 8.10 alpha.
** Changed in: linux-restricted-modules (Ubuntu)
Sourcepackagename: bluez-utils => linux-restricted-modules
Status: New => Fix Released
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received this bug notification because you are a membe
Rodrigo,
It appears that the files must be right in the /lib/firmware directory,
not in one of the kernel-specific subdirectories.
This raises a question: if Ubuntu is not going to include these files in
a package, and the Debian package puts the files in an incompatible
location, the proper plac
Oops, my mistake. I forgot that I am still running dapper on the system
that I did this on. I cannot say if the same is still true for feisty or
later versions. I will be upgrading it soon and will check again.
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received thi
bluez-firmware_1.2-1_all.deb puts the driver in /usr/lib/firmware/
rather than /lib/firmware/. When I create a symlink the driver loads.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Looking at the debian copyright file, it should be possible to include
'bluez-firmware' in restricted repository.
Can someone confirm?
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
Yes, please include the firmwares on restricted.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi I move the files as Dan Lipsitt said:
"find /lib/firmware -iname '*bcm*'"
/lib/firmware/2.6.20-15-386/BCM2033-MD.hex
/lib/firmware/2.6.20-15-386/BCM-LEGAL.txt
/lib/firmware/2.6.20-15-386/BCM2033-FW.bin
still nothing happens:
hcitool dev
Devices:
Any ideas?
--
missing firmware for bcm2033
ht
Rodrigo,
It appears that the files must be right in the /lib/firmware directory,
not in one of the kernel-specific subdirectories.
This raises a question: if Ubuntu is not going to include these files in
a package, and the Debian package puts the files in an incompatible
location, the proper plac
Oops, my mistake. I forgot that I am still running dapper on the system
that I did this on. I cannot say if the same is still true for feisty or
later versions. I will be upgrading it soon and will check again.
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received thi
bluez-firmware_1.2-1_all.deb puts the driver in /usr/lib/firmware/
rather than /lib/firmware/. When I create a symlink the driver loads.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Looking at the debian copyright file, it should be possible to include
'bluez-firmware' in restricted repository.
Can someone confirm?
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
bluez-firmware_1.2-1_all.deb puts the driver in /usr/lib/firmware/
rather than /lib/firmware/. When I create a symlink the driver loads.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Looking at the debian copyright file, it should be possible to include
'bluez-firmware' in restricted repository.
Can someone confirm?
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
Rodrigo,
It appears that the files must be right in the /lib/firmware directory,
not in one of the kernel-specific subdirectories.
This raises a question: if Ubuntu is not going to include these files in
a package, and the Debian package puts the files in an incompatible
location, the proper plac
Oops, my mistake. I forgot that I am still running dapper on the system
that I did this on. I cannot say if the same is still true for feisty or
later versions. I will be upgrading it soon and will check again.
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received thi
Hi I move the files as Dan Lipsitt said:
"find /lib/firmware -iname '*bcm*'"
/lib/firmware/2.6.20-15-386/BCM2033-MD.hex
/lib/firmware/2.6.20-15-386/BCM-LEGAL.txt
/lib/firmware/2.6.20-15-386/BCM2033-FW.bin
still nothing happens:
hcitool dev
Devices:
Any ideas?
--
missing firmware for bcm2033
ht
Available in 8.10 alpha.
** Changed in: linux-restricted-modules (Ubuntu)
Sourcepackagename: bluez-utils => linux-restricted-modules
Status: New => Fix Released
--
missing firmware for bcm2033
https://bugs.launchpad.net/bugs/64792
You received this bug notification because you are a membe
Yes, please include the firmwares on restricted.
--
missing firmware for bcm2033
https://launchpad.net/bugs/64792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi I move the files as Dan Lipsitt said:
"find /lib/firmware -iname '*bcm*'"
/lib/firmware/2.6.20-15-386/BCM2033-MD.hex
/lib/firmware/2.6.20-15-386/BCM-LEGAL.txt
/lib/firmware/2.6.20-15-386/BCM2033-FW.bin
still nothing happens:
hcitool dev
Devices:
Any ideas?
--
missing firmware for bcm2033
ht
42 matches
Mail list logo
