Re: [Bug 210066] Re: Can only use cheese once per bootup of computer
With a fully updated Intrepid, actually, it seems to be fine/fixed. On Tue, Dec 16, 2008 at 10:17 PM, Andres Mujica wrote: > Cory, is it possible to test if this issue is still present with > Intrepid fully updated or Jaunty? > > Thanks in advance. > > -- > Can only use cheese once per bootup of computer > https://bugs.launchpad.net/bugs/210066 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in "cheese" source package in Ubuntu: Incomplete > > Bug description: > Binary package hint: cheese > > Source package : > https://launchpad.net/ubuntu/+source/cheese/2.22.0-0ubuntu2 > > 1. Ubuntu Release : fl...@lil-spooky:~$ lsb_release -rd > Description:Ubuntu hardy (development branch) > Release:8.04 > > 2. Version of package I'm using : fl...@lil-spooky:~$ apt-cache policy > cheese > cheese: > Installed: 2.22.0-0ubuntu2 > Candidate: 2.22.0-0ubuntu2 > Version table: > *** 2.22.0-0ubuntu2 0 >500 http://us.archive.ubuntu.com hardy/main Packages >100 /var/lib/dpkg/status > > 3. What I expected to happen : that I could open Cheese, take some pictures > or record a video stream, close Cheese, do other things with the computer, > start up Cheese again and take some more pictures. > > 4. What happened instead : Cheese starts and runs fine the first time. When > closed, then started again, it will start my webcam ( it's little blue light > turns on ) but it won't keep the cam on -- light goes off right away, and > there's just the multicolored test pattern in the Cheese window. I tried > logging out, then logging back in, then starting Cheese again, but that did > not help. Completely rebooting will allow me to use Cheese with no issues -- > until I close it, and then start it again. > -- Can only use cheese once per bootup of computer https://bugs.launchpad.net/bugs/210066 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 197819] [NEW] broadcom wireless not working fresh install of hardy
Public bug reported: [EMAIL PROTECTED]:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" [EMAIL PROTECTED]:~$ uname -a Linux lil-spooky 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 x86_64 GNU/Linux - [EMAIL PROTECTED]:~$ apt-cache policy b43-fwcutter b43-fwcutter: Installed: 1:008-2 Candidate: 1:008-2 Version table: *** 1:008-2 0 500 http://us.archive.ubuntu.com hardy/universe Packages 100 /var/lib/dpkg/status what I expected to happen : after doing a fresh install of Hardy Alpha 5, I started the Restricted Driver Manager to install the broadcom firmware to get my wireless working, just like I did in Gutsy. I expected the fwcutter package to download and install the correct firmware, which is what happened under Gutsy. In Gutsy, the little orange light turned blue right away ( my machine is an HP dv6000 series laptop ) indicating that wireless is up and running. -- what happened instead : started the Restricted Driver manager now called "Hardware Drivers" under System-->Administration, clicked the checkbox for the Broadcom firmware to be downloaded and installed. The Hardware Driver manager told me it had downloaded and installed the firmware, however, the orange light did not turn blue. I tried rebooting to see if that would make a difference. It did not make a difference. No working wireless. This page : http://linuxwireless.org/en/users/Drivers/b43 seems to indicate that various kernel versions need not just different versions of the firmware, but different versions of the fwcutter program/package itself, as well. Would be great if that could be integrated into Hardy before final release. -- ** Affects: ubuntu Importance: Undecided Status: New -- broadcom wireless not working fresh install of hardy https://bugs.launchpad.net/bugs/197819 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 197819] Re: broadcom wireless not working fresh install of hardy
Restricted Manager pops up the "has to install firmware" notice again. I click ok, it installs/runs fwcutter again, which again does not result in working wireless. On the web page I referenced in my original bug report, there's talk of different kernels requiring different fwcutter versions as well as different firmware versions. For what it's worth, I realize this issue is caused by Broadcom not opening up their drivers, and I'm willing to dig around and manually tweak things to get wireless up and running. Just posted the bug because Gutsy automated all this perfectly, which was fantastic. On Mon, Mar 3, 2008 at 4:51 PM, der_vegi <[EMAIL PROTECTED]> wrote: > So it seems to be a problem of b43-fwcutter's install routine or the > restricted-driver-manager jockey? Cory Flick, what happens, if you try > to uninstall b43-fwcutter and then try enabling your wireless card over > the restricted manager again? > > > ** Also affects: jockey (Ubuntu) >Importance: Undecided > Status: New > > -- > broadcom wireless not working fresh install of hardy > https://bugs.launchpad.net/bugs/197819 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Source Package "b43-fwcutter" in Ubuntu: New > Status in Source Package "jockey" in Ubuntu: New > > Bug description: > [EMAIL PROTECTED]:~$ cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=8.04 > DISTRIB_CODENAME=hardy > DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" > [EMAIL PROTECTED]:~$ uname -a > Linux lil-spooky 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 > x86_64 GNU/Linux > > - > [EMAIL PROTECTED]:~$ apt-cache policy b43-fwcutter > b43-fwcutter: > Installed: 1:008-2 > Candidate: 1:008-2 > Version table: > *** 1:008-2 0 >500 http://us.archive.ubuntu.com hardy/universe Packages >100 /var/lib/dpkg/status > > > what I expected to happen : after doing a fresh install of Hardy Alpha 5, > I started the Restricted Driver Manager to install the broadcom firmware to > get my wireless working, just like I did in Gutsy. I expected the fwcutter > package to download and install the correct firmware, which is what happened > under Gutsy. In Gutsy, the little orange light turned blue right away ( my > machine is an HP dv6000 series laptop ) indicating that wireless is up and > running. > > -- > what happened instead : started the Restricted Driver manager now called > "Hardware Drivers" under System-->Administration, clicked the checkbox for > the Broadcom firmware to be downloaded and installed. The Hardware Driver > manager told me it had downloaded and installed the firmware, however, the > orange light did not turn blue. I tried rebooting to see if that would make > a difference. It did not make a difference. No working wireless. This page : > http://linuxwireless.org/en/users/Drivers/b43 seems to indicate that > various kernel versions need not just different versions of the firmware, > but different versions of the fwcutter program/package itself, as well. > Would be great if that could be integrated into Hardy before final release. > > -- > -- broadcom wireless not working fresh install of hardy https://bugs.launchpad.net/bugs/197819 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210066] [NEW] Can only use cheese once per bootup of computer
Public bug reported: Binary package hint: cheese Source package : https://launchpad.net/ubuntu/+source/cheese/2.22.0-0ubuntu2 1. Ubuntu Release : [EMAIL PROTECTED]:~$ lsb_release -rd Description:Ubuntu hardy (development branch) Release:8.04 2. Version of package I'm using : [EMAIL PROTECTED]:~$ apt-cache policy cheese cheese: Installed: 2.22.0-0ubuntu2 Candidate: 2.22.0-0ubuntu2 Version table: *** 2.22.0-0ubuntu2 0 500 http://us.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status 3. What I expected to happen : that I could open Cheese, take some pictures or record a video stream, close Cheese, do other things with the computer, start up Cheese again and take some more pictures. 4. What happened instead : Cheese starts and runs fine the first time. When closed, then started again, it will start my webcam ( it's little blue light turns on ) but it won't keep the cam on -- light goes off right away, and there's just the multicolored test pattern in the Cheese window. I tried logging out, then logging back in, then starting Cheese again, but that did not help. Completely rebooting will allow me to use Cheese with no issues -- until I close it, and then start it again. ** Affects: cheese (Ubuntu) Importance: Undecided Status: New -- Can only use cheese once per bootup of computer https://bugs.launchpad.net/bugs/210066 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148329] Re: cheese crashed with SIGSEGV in gst_value_init_and_copy()
Just installed the latest Cheese update. [EMAIL PROTECTED]:~$ cheese -v device: /dev/video0 Segmentation fault (core dumped) [EMAIL PROTECTED]:~$ apt-policy cheese bash: apt-policy: command not found [EMAIL PROTECTED]:~$ apt-cache policy cheese cheese: Installed: 2.22.0-0ubuntu1 Candidate: 2.22.0-0ubuntu1 Version table: *** 2.22.0-0ubuntu1 0 500 http://us.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status Running Hardy, from a fresh install of the Beta and fully updated, 64-bit. -- cheese crashed with SIGSEGV in gst_value_init_and_copy() https://bugs.launchpad.net/bugs/148329 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 197819] Re: broadcom wireless not working fresh install of hardy
I can confirm that this does work : "Going under package manager, selecting completely remove the b43-fwcutter package, and then installing it again does fix my wireless." Looks like it's just the initial setup under System > Administration > Hardware Drivers that somehow fails to get the firmware properly. Manual install with Synaptic works fine. Thanks to everyone posting here helping make Ubuntu better/nicer to use. On Fri, Mar 7, 2008 at 10:28 PM, Kevin Oberle <[EMAIL PROTECTED]> wrote: > I can confirm this bug on my laptop under hardy alpha 6. I have the > bcm4318 card. If i use the restricted hardware manager and enable the > driver it downloads and installs fine but does not work even after a > reboot. Going under package manager, selecting completely remove the > b43-fwcutter package, and then installing it again does fix my wireless. > This would be consistent with a problem in the installation script or > restricted driver manager itself. > > -- > broadcom wireless not working fresh install of hardy > https://bugs.launchpad.net/bugs/197819 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Source Package "b43-fwcutter" in Ubuntu: New > Status in Source Package "jockey" in Ubuntu: New > > Bug description: > [EMAIL PROTECTED]:~$ cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=8.04 > DISTRIB_CODENAME=hardy > DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" > [EMAIL PROTECTED]:~$ uname -a > Linux lil-spooky 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 > x86_64 GNU/Linux > > - > [EMAIL PROTECTED]:~$ apt-cache policy b43-fwcutter > b43-fwcutter: > Installed: 1:008-2 > Candidate: 1:008-2 > Version table: > *** 1:008-2 0 >500 http://us.archive.ubuntu.com hardy/universe Packages >100 /var/lib/dpkg/status > > > what I expected to happen : after doing a fresh install of Hardy Alpha 5, > I started the Restricted Driver Manager to install the broadcom firmware to > get my wireless working, just like I did in Gutsy. I expected the fwcutter > package to download and install the correct firmware, which is what happened > under Gutsy. In Gutsy, the little orange light turned blue right away ( my > machine is an HP dv6000 series laptop ) indicating that wireless is up and > running. > > -- > what happened instead : started the Restricted Driver manager now called > "Hardware Drivers" under System-->Administration, clicked the checkbox for > the Broadcom firmware to be downloaded and installed. The Hardware Driver > manager told me it had downloaded and installed the firmware, however, the > orange light did not turn blue. I tried rebooting to see if that would make > a difference. It did not make a difference. No working wireless. This page : > http://linuxwireless.org/en/users/Drivers/b43 seems to indicate that > various kernel versions need not just different versions of the firmware, > but different versions of the fwcutter program/package itself, as well. > Would be great if that could be integrated into Hardy before final release. > > -- > -- [Hardy]b43-fwcutter install script fails to fetch firmware in first run https://bugs.launchpad.net/bugs/197819 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 197819] Re: broadcom wireless not working fresh install of hardy
For whatever it's worth : I tried a different approach. I did a clean install of Gutsy, got wireless working that way, then upgraded to Hardy using update-manager -d. Upon reboot, wireless does not work. Tried using "Hardware Drivers" under System-->Administration, it offered to download the fwcutter package, I accepted, and still no working wireless. Rebooted, still no working wireless. This is all 64bit, on an HP dv6000 laptop. On Mon, Mar 3, 2008 at 9:04 PM, Cory Flick <[EMAIL PROTECTED]> wrote: > Restricted Manager pops up the "has to install firmware" notice again. I > click ok, it installs/runs fwcutter again, which again does not result in > working wireless. On the web page I referenced in my original bug report, > there's talk of different kernels requiring different fwcutter versions as > well as different firmware versions. For what it's worth, I realize this > issue is caused by Broadcom not opening up their drivers, and I'm willing to > dig around and manually tweak things to get wireless up and running. Just > posted the bug because Gutsy automated all this perfectly, which was > fantastic. > > > > On Mon, Mar 3, 2008 at 4:51 PM, der_vegi <[EMAIL PROTECTED]> wrote: > > > So it seems to be a problem of b43-fwcutter's install routine or the > > restricted-driver-manager jockey? Cory Flick, what happens, if you try > > to uninstall b43-fwcutter and then try enabling your wireless card over > > the restricted manager again? > > > > > > ** Also affects: jockey (Ubuntu) > >Importance: Undecided > > Status: New > > > > -- > > broadcom wireless not working fresh install of hardy > > https://bugs.launchpad.net/bugs/197819 > > You received this bug notification because you are a direct subscriber > > of the bug. > > > > Status in Source Package "b43-fwcutter" in Ubuntu: New > > Status in Source Package "jockey" in Ubuntu: New > > > > Bug description: > > [EMAIL PROTECTED]:~$ cat /etc/lsb-release > > DISTRIB_ID=Ubuntu > > DISTRIB_RELEASE=8.04 > > DISTRIB_CODENAME=hardy > > DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" > > [EMAIL PROTECTED]:~$ uname -a > > Linux lil-spooky 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 > > x86_64 GNU/Linux > > > > - > > [EMAIL PROTECTED]:~$ apt-cache policy b43-fwcutter > > b43-fwcutter: > > Installed: 1:008-2 > > Candidate: 1:008-2 > > Version table: > > *** 1:008-2 0 > >500 http://us.archive.ubuntu.com hardy/universe Packages > >100 /var/lib/dpkg/status > > > > > > what I expected to happen : after doing a fresh install of Hardy Alpha > > 5, I started the Restricted Driver Manager to install the broadcom firmware > > to get my wireless working, just like I did in Gutsy. I expected the > > fwcutter package to download and install the correct firmware, which is what > > happened under Gutsy. In Gutsy, the little orange light turned blue right > > away ( my machine is an HP dv6000 series laptop ) indicating that wireless > > is up and running. > > > > -- > > what happened instead : started the Restricted Driver manager now called > > "Hardware Drivers" under System-->Administration, clicked the checkbox for > > the Broadcom firmware to be downloaded and installed. The Hardware Driver > > manager told me it had downloaded and installed the firmware, however, the > > orange light did not turn blue. I tried rebooting to see if that would make > > a difference. It did not make a difference. No working wireless. This page : > > http://linuxwireless.org/en/users/Drivers/b43 seems to indicate that > > various kernel versions need not just different versions of the firmware, > > but different versions of the fwcutter program/package itself, as well. > > Would be great if that could be integrated into Hardy before final release. > > > > -- > > > > -- broadcom wireless not working fresh install of hardy https://bugs.launchpad.net/bugs/197819 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 197819] Re: broadcom wireless not working fresh install of hardy
Thank you for the tips and suggestions, I'll do them tonight when I get home from work, and will reply again with my results. On Thu, Mar 6, 2008 at 8:04 AM, der_vegi <[EMAIL PROTECTED]> wrote: > Cory, what i your output of 'dmesg'? This would give an idea, if the > problem is the driver itself, or a problem of not loading the firmware. > > A second aproach would be to do the steps, the install script shoud do, > manually (steps extracted from > /usr/share/b43-fwcutter/install_bcm43xx_firmware.sh): > go to some temporary directory, for example ~/b43-temp and perform the > following steps: > > cd ~ > mkdir b43-temp > cd b43-temp > wget http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o > wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2 > sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o > tar xfvj broadcom-wl-4.80.53.0.tar.bz2 > sudo b43-fwcutter -w /lib/firmware broadcom-wl-4.80.53.0/kmod/wl_apsta.o > sudo chmod o+rx /lib/firmware/b43 /lib/firmware/b43legacy > > Again, output of 'dmesg' would be helpful... Good luck! > > -- > broadcom wireless not working fresh install of hardy > https://bugs.launchpad.net/bugs/197819 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Source Package "b43-fwcutter" in Ubuntu: New > Status in Source Package "jockey" in Ubuntu: New > > Bug description: > [EMAIL PROTECTED]:~$ cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=8.04 > DISTRIB_CODENAME=hardy > DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" > [EMAIL PROTECTED]:~$ uname -a > Linux lil-spooky 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 > x86_64 GNU/Linux > > - > [EMAIL PROTECTED]:~$ apt-cache policy b43-fwcutter > b43-fwcutter: > Installed: 1:008-2 > Candidate: 1:008-2 > Version table: > *** 1:008-2 0 >500 http://us.archive.ubuntu.com hardy/universe Packages >100 /var/lib/dpkg/status > > > what I expected to happen : after doing a fresh install of Hardy Alpha 5, > I started the Restricted Driver Manager to install the broadcom firmware to > get my wireless working, just like I did in Gutsy. I expected the fwcutter > package to download and install the correct firmware, which is what happened > under Gutsy. In Gutsy, the little orange light turned blue right away ( my > machine is an HP dv6000 series laptop ) indicating that wireless is up and > running. > > -- > what happened instead : started the Restricted Driver manager now called > "Hardware Drivers" under System-->Administration, clicked the checkbox for > the Broadcom firmware to be downloaded and installed. The Hardware Driver > manager told me it had downloaded and installed the firmware, however, the > orange light did not turn blue. I tried rebooting to see if that would make > a difference. It did not make a difference. No working wireless. This page : > http://linuxwireless.org/en/users/Drivers/b43 seems to indicate that > various kernel versions need not just different versions of the firmware, > but different versions of the fwcutter program/package itself, as well. > Would be great if that could be integrated into Hardy before final release. > > -- > -- broadcom wireless not working fresh install of hardy https://bugs.launchpad.net/bugs/197819 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 197819] Re: broadcom wireless not working fresh install of hardy
Looks like the firmware version/fwcutter version issues I mentioned/referenced in my first post. Dmesg output attached. On Thu, Mar 6, 2008 at 8:16 AM, Cory Flick <[EMAIL PROTECTED]> wrote: > Thank you for the tips and suggestions, I'll do them tonight when I get > home from work, and will reply again with my results. > > > > On Thu, Mar 6, 2008 at 8:04 AM, der_vegi <[EMAIL PROTECTED]> wrote: > > > Cory, what i your output of 'dmesg'? This would give an idea, if the > > problem is the driver itself, or a problem of not loading the firmware. > > > > A second aproach would be to do the steps, the install script shoud do, > > manually (steps extracted from > > /usr/share/b43-fwcutter/install_bcm43xx_firmware.sh): > > go to some temporary directory, for example ~/b43-temp and perform the > > following steps: > > > > cd ~ > > mkdir b43-temp > > cd b43-temp > > wget http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o > > wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2 > > sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o > > tar xfvj broadcom-wl-4.80.53.0.tar.bz2 > > sudo b43-fwcutter -w /lib/firmware broadcom-wl-4.80.53.0/kmod/wl_apsta.o > > sudo chmod o+rx /lib/firmware/b43 /lib/firmware/b43legacy > > > > Again, output of 'dmesg' would be helpful... Good luck! > > > > -- > > broadcom wireless not working fresh install of hardy > > https://bugs.launchpad.net/bugs/197819 > > You received this bug notification because you are a direct subscriber > > of the bug. > > > > Status in Source Package "b43-fwcutter" in Ubuntu: New > > Status in Source Package "jockey" in Ubuntu: New > > > > Bug description: > > [EMAIL PROTECTED]:~$ cat /etc/lsb-release > > DISTRIB_ID=Ubuntu > > DISTRIB_RELEASE=8.04 > > DISTRIB_CODENAME=hardy > > DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" > > [EMAIL PROTECTED]:~$ uname -a > > Linux lil-spooky 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 > > x86_64 GNU/Linux > > > > - > > [EMAIL PROTECTED]:~$ apt-cache policy b43-fwcutter > > b43-fwcutter: > > Installed: 1:008-2 > > Candidate: 1:008-2 > > Version table: > > *** 1:008-2 0 > >500 http://us.archive.ubuntu.com hardy/universe Packages > >100 /var/lib/dpkg/status > > > > > > what I expected to happen : after doing a fresh install of Hardy Alpha > > 5, I started the Restricted Driver Manager to install the broadcom firmware > > to get my wireless working, just like I did in Gutsy. I expected the > > fwcutter package to download and install the correct firmware, which is what > > happened under Gutsy. In Gutsy, the little orange light turned blue right > > away ( my machine is an HP dv6000 series laptop ) indicating that wireless > > is up and running. > > > > -- > > what happened instead : started the Restricted Driver manager now called > > "Hardware Drivers" under System-->Administration, clicked the checkbox for > > the Broadcom firmware to be downloaded and installed. The Hardware Driver > > manager told me it had downloaded and installed the firmware, however, the > > orange light did not turn blue. I tried rebooting to see if that would make > > a difference. It did not make a difference. No working wireless. This page : > > http://linuxwireless.org/en/users/Drivers/b43 seems to indicate that > > various kernel versions need not just different versions of the firmware, > > but different versions of the fwcutter program/package itself, as well. > > Would be great if that could be integrated into Hardy before final release. > > > > -- > > > > [0.00] Linux version 2.6.24-11-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu1)) #1 SMP Fri Feb 29 21:26:31 UTC 2008 (Ubuntu 2.6.24-11.17-generic) [0.00] Command line: root=UUID=b54d357e-4a50-4363-a0e0-3879cb691870 ro quiet splash noapic [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009dc00 (usable) [0.00]
Re: [Bug 197819] Re: broadcom wireless not working fresh install of hardy
Manual removal of the firmware supplied by Hardy's fwcutter package, and then manual removal of Hardy's fwcutter package itself, followed by manual installation of the fwcutter package referenced on the site I have listed in my original post, followed by running that fwcutter package/program, DOES work. Again, not complaining or whining, just wondering if some of us with older Broadcom chips might have to go through these manual steps with anything beyond Gutsy, when Gutsy automated it all through its Restricted Drivers Manager. And of course, hoping the Ubuntu devs can include the proper fwcutter package for our troublesome Broadcom cards in Hardy, if possible. On Fri, Mar 7, 2008 at 3:49 AM, der_vegi <[EMAIL PROTECTED]> wrote: > And manually installing the firmware did not work either? Hm. What kind > of chip are you using? Looking at > http://linuxwireless.org/en/users/Drivers/b43/ shows, that not all > broadcom devices are supported. Could you please attach the output of > 'lspci -vvnn'? > > -- > broadcom wireless not working fresh install of hardy > https://bugs.launchpad.net/bugs/197819 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Source Package "b43-fwcutter" in Ubuntu: New > Status in Source Package "jockey" in Ubuntu: New > > Bug description: > [EMAIL PROTECTED]:~$ cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=8.04 > DISTRIB_CODENAME=hardy > DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" > [EMAIL PROTECTED]:~$ uname -a > Linux lil-spooky 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 > x86_64 GNU/Linux > > - > [EMAIL PROTECTED]:~$ apt-cache policy b43-fwcutter > b43-fwcutter: > Installed: 1:008-2 > Candidate: 1:008-2 > Version table: > *** 1:008-2 0 >500 http://us.archive.ubuntu.com hardy/universe Packages >100 /var/lib/dpkg/status > > > what I expected to happen : after doing a fresh install of Hardy Alpha 5, > I started the Restricted Driver Manager to install the broadcom firmware to > get my wireless working, just like I did in Gutsy. I expected the fwcutter > package to download and install the correct firmware, which is what happened > under Gutsy. In Gutsy, the little orange light turned blue right away ( my > machine is an HP dv6000 series laptop ) indicating that wireless is up and > running. > > -- > what happened instead : started the Restricted Driver manager now called > "Hardware Drivers" under System-->Administration, clicked the checkbox for > the Broadcom firmware to be downloaded and installed. The Hardware Driver > manager told me it had downloaded and installed the firmware, however, the > orange light did not turn blue. I tried rebooting to see if that would make > a difference. It did not make a difference. No working wireless. This page : > http://linuxwireless.org/en/users/Drivers/b43 seems to indicate that > various kernel versions need not just different versions of the firmware, > but different versions of the fwcutter program/package itself, as well. > Would be great if that could be integrated into Hardy before final release. > > -- > -- broadcom wireless not working fresh install of hardy https://bugs.launchpad.net/bugs/197819 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 197819] Re: broadcom wireless not working fresh install of hardy
Relevant output of lspci -vvnn : 03:00.0 Network controller [0280]: Broadcom Corporation BCM94311MCG wlan mini-PCI [14e4:4311] (rev 01) Subsystem: Hewlett-Packard Company Unknown device [103c:1363] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: b43-pci-bridge Kernel modules: ssb On Fri, Mar 7, 2008 at 8:25 AM, Cory Flick <[EMAIL PROTECTED]> wrote: > Manual removal of the firmware supplied by Hardy's fwcutter package, and > then manual removal of Hardy's fwcutter package itself, followed by manual > installation of the fwcutter package referenced on the site I have listed in > my original post, followed by running that fwcutter package/program, DOES > work. > > Again, not complaining or whining, just wondering if some of us with older > Broadcom chips might have to go through these manual steps with anything > beyond Gutsy, when Gutsy automated it all through its Restricted Drivers > Manager. And of course, hoping the Ubuntu devs can include the proper > fwcutter package for our troublesome Broadcom cards in Hardy, if possible. > > > > On Fri, Mar 7, 2008 at 3:49 AM, der_vegi <[EMAIL PROTECTED]> wrote: > > > And manually installing the firmware did not work either? Hm. What kind > > of chip are you using? Looking at > > http://linuxwireless.org/en/users/Drivers/b43/ shows, that not all > > broadcom devices are supported. Could you please attach the output of > > 'lspci -vvnn'? > > > > -- > > broadcom wireless not working fresh install of hardy > > https://bugs.launchpad.net/bugs/197819 > > You received this bug notification because you are a direct subscriber > > of the bug. > > > > Status in Source Package "b43-fwcutter" in Ubuntu: New > > Status in Source Package "jockey" in Ubuntu: New > > > > Bug description: > > [EMAIL PROTECTED]:~$ cat /etc/lsb-release > > DISTRIB_ID=Ubuntu > > DISTRIB_RELEASE=8.04 > > DISTRIB_CODENAME=hardy > > DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" > > [EMAIL PROTECTED]:~$ uname -a > > Linux lil-spooky 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 > > x86_64 GNU/Linux > > > > - > > [EMAIL PROTECTED]:~$ apt-cache policy b43-fwcutter > > b43-fwcutter: > > Installed: 1:008-2 > > Candidate: 1:008-2 > > Version table: > > *** 1:008-2 0 > >500 http://us.archive.ubuntu.com hardy/universe Packages > >100 /var/lib/dpkg/status > > > > > > what I expected to happen : after doing a fresh install of Hardy Alpha > > 5, I started the Restricted Driver Manager to install the broadcom firmware > > to get my wireless working, just like I did in Gutsy. I expected the > > fwcutter package to download and install the correct firmware, which is what > > happened under Gutsy. In Gutsy, the little orange light turned blue right > > away ( my machine is an HP dv6000 series laptop ) indicating that wireless > > is up and running. > > > > -- > > what happened instead : started the Restricted Driver manager now called > > "Hardware Drivers" under System-->Administration, clicked the checkbox for > > the Broadcom firmware to be downloaded and installed. The Hardware Driver > > manager told me it had downloaded and installed the firmware, however, the > > orange light did not turn blue. I tried rebooting to see if that would make > > a difference. It did not make a difference. No working wireless. This page : > > http://linuxwireless.org/en/users/Drivers/b43 seems to indicate that > > various kernel versions need not just different versions of the firmware, > > but different versions of the fwcutter program/package itself, as well. > > Would be great if that could be integrated into Hardy before final release. > > > > -- > > > > -- broadcom wireless not working fresh install of hardy https://bugs.launchpad.net/bugs/197819 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561140] Re: Boot hangs after update to kernel 2.6.32-20
I can also confirm this. I'm running 64 bit Lucid Beta 2, fresh install and just updated. Kernel 2.6.32-20 hangs during boot, rebooting and selecting 2.6.32-19 kernel brings up the system just fine. Machine is an Asus K60 notebook. Output of sudo lshw -short : fl...@lil-spooky:~$ sudo lshw -short [sudo] password for flick: H/W path Device Class Description == system K60IJ /0 bus K60IJ /0/0 memory 64KiB BIOS /0/4 processor Pentium(R) Dual-Core CPU T4400 /0/4/5 memory 64KiB L1 cache /0/4/7 memory 1MiB L2 cache /0/6 memory 64KiB L1 cache /0/1d memory 4GiB System Memory /0/1d/0memory 2GiB SODIMM DDR2 Synchronous 667 MHz /0/1d/1memory 2GiB SODIMM DDR2 Synchronous 667 MHz /0/100 bridge Mobile 4 Series Chipset Memory Contro /0/100/2 display Mobile 4 Series Chipset Integrated Gr /0/100/2.1 display Mobile 4 Series Chipset Integrated Gr /0/100/1a bus 82801I (ICH9 Family) USB UHCI Control /0/100/1a.1bus 82801I (ICH9 Family) USB UHCI Control /0/100/1a.2bus 82801I (ICH9 Family) USB UHCI Control /0/100/1a.7bus 82801I (ICH9 Family) USB2 EHCI Contro /0/100/1b multimedia 82801I (ICH9 Family) HD Audio Control /0/100/1c bridge 82801I (ICH9 Family) PCI Express Port /0/100/1c.1bridge 82801I (ICH9 Family) PCI Express Port /0/100/1c.1/0 wlan0 network AR9285 Wireless Network Adapter (PCI- /0/100/1c.5bridge 82801I (ICH9 Family) PCI Express Port /0/100/1c.5/0 eth0network Atheros AR8121/AR8113/AR8114 PCI-E Et /0/100/1d bus 82801I (ICH9 Family) USB UHCI Control /0/100/1d.1bus 82801I (ICH9 Family) USB UHCI Control /0/100/1d.2bus 82801I (ICH9 Family) USB UHCI Control /0/100/1d.7bus 82801I (ICH9 Family) USB2 EHCI Contro /0/100/1e bridge 82801 Mobile PCI Bridge /0/100/1f bridge ICH9M LPC Interface Controller /0/100/1f.2scsi0 storage ICH9M/M-E SATA AHCI Controller /0/100/1f.2/0 /dev/sdadisk500GB ST9500325AS /0/100/1f.2/0/1/dev/sda1 volume 14GiB Windows FAT volume /0/100/1f.2/0/2/dev/sda2 volume 97GiB Windows NTFS volume /0/100/1f.2/0/3/dev/sda3 volume 353GiB Extended partition /0/100/1f.2/0/3/5 /dev/sda5 volume 46GiB Linux filesystem partition /0/100/1f.2/0/3/6 /dev/sda6 volume 3812MiB Linux swap / Solaris partitio /0/100/1f.2/0/3/7 /dev/sda7 volume 303GiB Linux filesystem partition /0/100/1f.2/1 /dev/cdrom diskDVDRAM GT10N /1 power F82--22 -- Boot hangs after update to kernel 2.6.32-20 https://bugs.launchpad.net/bugs/561140 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561151] Re: 2.6.32.30 reproducible oops at startup in acpi_ex_read_data_from_field
2.6.32-20.30 also now works fine for me on my Asus K60. On Tue, Apr 13, 2010 at 5:34 AM, Mark Weaver wrote: > 2.6.32-20.30 also works for me on my Lenovo T43. > > -- > 2.6.32.30 reproducible oops at startup in acpi_ex_read_data_from_field > https://bugs.launchpad.net/bugs/561151 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in “linux” package in Ubuntu: Fix Released > > Bug description: > I have Lucid running on an Thinkpad X61s. I've just installed this > mornings updates, and the current kernel 2.6.32-20-generic oopses at startup > in acpi_ex_read_data_from_field as shown in the attachment. > 2.6.32-19-generic works correctly. Booting in recovery mode doesn't help. > I haven't tried noacpi yet but I might do that now. > > I can't page up to get the rest of the traceback and sysrq doesn't work. I > have to hard-power-cycle the machine. > > ProblemType: Bug > DistroRelease: Ubuntu 10.04 > Package: linux-image-2.6.32-20-generic 2.6.32-20.29 > Regression: Yes > Reproducible: Yes > ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 > Uname: Linux 2.6.32-19-generic i686 > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. > Architecture: i386 > ArecordDevices: > List of CAPTURE Hardware Devices > card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] > Subdevices: 2/2 > Subdevice #0: subdevice #0 > Subdevice #1: subdevice #1 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC0: mbp3785 F pulseaudio > /dev/snd/pcmC0D0p: mbp3785 F...m pulseaudio > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: > Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 17' > Mixer name : 'Analog Devices AD1984' > Components : 'HDA:11d41984,17aa20d6,00100400' > Controls : 30 > Simple ctrls : 19 > Card29.Amixer.info: > Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw > 7MHT24WW-1.02' > Mixer name : 'ThinkPad EC 7MHT24WW-1.02' > Components : '' > Controls : 1 > Simple ctrls : 1 > Card29.Amixer.values: > Simple mixer control 'Console',0 > Capabilities: pswitch pswitch-joined penum > Playback channels: Mono > Mono: Playback [on] > Date: Mon Apr 12 12:43:05 2010 > MachineType: LENOVO 76697DM > PccardctlIdent: > Socket 0: > no product info available > PccardctlStatus: > Socket 0: > no card > ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-19-generic > root=/dev/mapper/hostname_ssd-root ro single > ProcEnviron: > PATH=(custom, user) > LANG=en_AU.UTF-8 > SHELL=/bin/zsh > RelatedPackageVersions: linux-firmware 1.33 > SourcePackage: linux > dmi.bios.date: 09/19/2007 > dmi.bios.vendor: LENOVO > dmi.bios.version: 7NET27WW (1.08 ) > dmi.board.name: 76697DM > dmi.board.vendor: LENOVO > dmi.board.version: Not Available > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Not Available > dmi.modalias: > dmi:bvnLENOVO:bvr7NET27WW(1.08):bd09/19/2007:svnLENOVO:pn76697DM:pvrThinkPadX61s:rvnLENOVO:rn76697DM:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.name: 76697DM > dmi.product.version: ThinkPad X61s > dmi.sys.vendor: LENOVO > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/561151/+subscribe > -- 2.6.32.30 reproducible oops at startup in acpi_ex_read_data_from_field https://bugs.launchpad.net/bugs/561151 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583132] Re: Login to forums fails
"Attempting log on thru Launchpad failed to access forums." Does this mean you were trying to log on to Launchpad, or log on to Ubuntu forums? "Tried password reset. That flow worked, but the new password wouldn't take in subsequent log on attempts" Again, is the problem you are experiencing with Launchpad, or Ubuntu forums? Or both? "Ubuntu One search for music is messy. Search for artist "rolling stones" and it returns nothing. Yuck. Ubuntu One is missing lots of stuff." Separate issue and I understand your frustration if your search returned nothing. I just opened Rhythmbox, opened the store, searched for "rolling stones" and most if not all of their albums came right up, available for download. If they weren't there when you did your search, all I can tell you is, they are there now. -- Login to forums fails https://bugs.launchpad.net/bugs/583132 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908203] Re: GRUB2 fails to install on Lenovo IdeaPad V570-1066AJU
Found a workaround. Posted on askubuntu : http://askubuntu.com/questions/107193/cant-boot-ubuntu-on- lenovo-v570/124208#124208 Short version : Boot liveCD. Run graphical installer. Then before rebooting, fire up a terminal. sudo apt-get install efibootmgr sudo modprobe efivars sudo efibootmgr The first line installs efibootmgr, the second line adds efi support to the kernel running in the livecd environment, third line shows all the options for booting in your machine's bios/efi boot screen. When I did this, I saw that Ubuntu was listed, as option 9, and option 9 was not part of the options marked as bootable. So to change the boot order I first researched using man efibootmgr and found : CHANGING THE BOOT ORDER FOR THE NEXT BOOT ONLY Assuming the configuration in Example #1, efibootmgr -n 4 could be called to specify that the Linux entry be taken on next boot. and CHANGING THE BOOT ORDER Assuming the configuration in Example #1, efibootmgr -o 3,4 could be called to specify PXE boot first, then Linux boot. So in my case, with Ubuntu listed as option 9, I did : sudo efibootmgr -o 9,andthensomeotheroptionslikemycddrive I then rebooted, removed the livecd when prompted, and was greeted by a working Ubuntu installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908203 Title: GRUB2 fails to install on Lenovo IdeaPad V570-1066AJU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/908203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908203] Re: GRUB2 fails to install on Lenovo IdeaPad V570-1066AJU
Same laptop. Ubuntu 11.10 and 12.04 beta both will go through their installation routines from desktop livecds just fine, then fail to boot at all from the hard drive. Linux Mint 12 will install just fine from its livecd, then the installation will boot just fine from the hard drive upon reboot ( everything works as expected ). There is something weird about this Lenovo model's bios and hard disk related to GPT partition table vs ms-dos partition table, and it makes life difficult for the Ubuntu installer to correctly figure out whether to install grub-pc, grub2, or grub-efi, IF anecdotal Googling about this issue is to be believed. IIRC, the Mint installer is just a tweaked version of Ubuntu's. I have to believe that if the Mint folks can hit on the right secret sauce, so to speak, so can the parent distro. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908203 Title: GRUB2 fails to install on Lenovo IdeaPad V570-1066AJU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/908203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 669224] Re: Headphone jack not working in Asus K60I
Hi, all. If the status is really Fix Released, something must have changed for the worse in Natty, or I missed something in this bug report that explains how to solve the issue. I am running Natty 64 bit on my Asus K60IJ, and I can either get sound out of both headphones and front speakers, have both headphones and front speakers muted, OR get sound at a very low volume out of my headphones and at a variable volume out of my front speakers at the same time. If anyone knows of a workaround other than removing Pulseaudio I'd be grateful to learn of it. I know that removing Pulseaudio fixes this issue, but of course it breaks the volume control function of the sound indicator applet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669224 Title: Headphone jack not working in Asus K60I To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/669224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 669224] Re: Headphone jack not working in Asus K60I
Ahem. Perhaps I should have searched the forums first. Sorry. In case it helps anyone else, the solution at the following link works perfectly for me : http://ubuntuforums.org/showthread.php?t=1762969&highlight=headphones+asus+k60i It would be a cool thing if we didn't have to faff around with adding extra software and such to get this functionality, on the other hand, it is a cool thing that we have so much community discussion and ideas out there to take advantage of. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669224 Title: Headphone jack not working in Asus K60I To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/669224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561151] hey Bug
Hello Bug i know you can achieve happiness http://weldingjournal.com/redirect.php?to=aHR0cDovL3d3dy5jbmJjNy5jb20vP3BpZD0yMjE2NzI= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561151 Title: 2.6.32.30 reproducible oops at startup in acpi_ex_read_data_from_field -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561151] hi Bug
Hello Bug, keep your family in mind http://email.about.com/gi/dynamic/offsite.htm?zi=1/XJ&sdn=email&zu=http://cnbc7.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561151 Title: 2.6.32.30 reproducible oops at startup in acpi_ex_read_data_from_field -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
