[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
I bought MX4 when it was released in Europe and Italy (more then 1 year ago), I don't remember what number of version it was. Maybe OTA-10? I'm never been able to pair MX4 with Nissan Connect system. What can I do? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
In my own case the problem remain the same. No difference between OTA-12 and 13 on Meizu MX4, pairing process always fail. Also I can't remove "Nissan Connect" device, to remove it I needed to use the terminal again. How can I provide more details? Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, I tryed to pair again the phone with my car, but it don't work. The car say "Pairing failed". After this, to remove the device, I needed to use the terminal again. To resolve, I need to wait for OTA-13, or I need instruction for installing the new bluez silo. Thank you, Marco Il 29/07/2016 12:43, Konrad Zapałowicz ha scritto: > Marco, > > this is super strange, I will think of possible solutions however in > the meantime what is the output from > > info 60:38:0E:59:32:39 > > Thanks, > K > > On Fri, Jul 29, 2016 at 12:40 PM, Marco Graziotti > <graziottima...@gmail.com <mailto:graziottima...@gmail.com>> wrote: > > Hi Konrad, > > I tried to remove the "Nissan Connect" device, but i got this > error: "*Failed to remove device: org.bluez.Error.NotReady*". > Here you can read what I'm doing: > > *user@user-laptop:~$ adb shell* > * daemon not running. starting it now on port 5037 * > * daemon started successfully * > > phablet@ubuntu-phablet:~$ $ bluetoothctl > bash: $: command not found > > *phablet@ubuntu-phablet:~$ bluetoothctl* > [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] > [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# devices* > Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# remove 60:38:0E:59:32:39** > **Failed to remove device: org.bluez.Error.NotReady* > > What can I do? > > Thank you > > > Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: >> Hey, >> >> I'll try to help a bit here. >> >> First as for the unknown or unwanted entries on the paired devices lists >> [and such] you can try to remove them from the bluetoothctl level. >> >> ) enable developers mode & connect it via usb cable >> ) login with adb shell to the deivce >> ) type $ bluetoothctl >> ) then type: devices - to list the known devices >> ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address >> of the device [not it's name] >> >> Second we are in the of releasing the newest bluez 5.41 which is now in >> silo 37. If you are familiar with installing silos on your device you >> can try it out and check if it improves anything. It includes fixes for >> link management and pairing therefore there is a chance [although not >> certain] that there might be joy. >> >> If unsure please ask. >> >> Best, >> Konrad >> > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, the problem was that my bluetooth is turned off :D :D Now I'm able to remove the NISSAN CONNECT device [bluetooth]# remove 60:38:0E:59:32:39 [DEL] Device 60:38:0E:59:32:39 NISSAN CONNECT Device has been removed Now I will try to pair it again. Thank you, Marco Il 29/07/2016 12:43, Konrad Zapałowicz ha scritto: > Marco, > > this is super strange, I will think of possible solutions however in > the meantime what is the output from > > info 60:38:0E:59:32:39 > > Thanks, > K > > On Fri, Jul 29, 2016 at 12:40 PM, Marco Graziotti > <graziottima...@gmail.com <mailto:graziottima...@gmail.com>> wrote: > > Hi Konrad, > > I tried to remove the "Nissan Connect" device, but i got this > error: "*Failed to remove device: org.bluez.Error.NotReady*". > Here you can read what I'm doing: > > *user@user-laptop:~$ adb shell* > * daemon not running. starting it now on port 5037 * > * daemon started successfully * > > phablet@ubuntu-phablet:~$ $ bluetoothctl > bash: $: command not found > > *phablet@ubuntu-phablet:~$ bluetoothctl* > [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] > [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# devices* > Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# remove 60:38:0E:59:32:39** > **Failed to remove device: org.bluez.Error.NotReady* > > What can I do? > > Thank you > > > Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: >> Hey, >> >> I'll try to help a bit here. >> >> First as for the unknown or unwanted entries on the paired devices lists >> [and such] you can try to remove them from the bluetoothctl level. >> >> ) enable developers mode & connect it via usb cable >> ) login with adb shell to the deivce >> ) type $ bluetoothctl >> ) then type: devices - to list the known devices >> ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address >> of the device [not it's name] >> >> Second we are in the of releasing the newest bluez 5.41 which is now in >> silo 37. If you are familiar with installing silos on your device you >> can try it out and check if it improves anything. It includes fixes for >> link management and pairing therefore there is a chance [although not >> certain] that there might be joy. >> >> If unsure please ask. >> >> Best, >> Konrad >> > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, I tried to remove the "Nissan Connect" device, but i got this error: "*Failed to remove device: org.bluez.Error.NotReady*". Here you can read what I'm doing: *user@user-laptop:~$ adb shell* * daemon not running. starting it now on port 5037 * * daemon started successfully * phablet@ubuntu-phablet:~$ $ bluetoothctl bash: $: command not found *phablet@ubuntu-phablet:~$ bluetoothctl* [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT *[bluetooth]# devices* Device 90:F1:AA:7B:80:0F [Samsung] Soundbar Device 60:38:0E:59:32:39 NISSAN CONNECT *[bluetooth]# remove 60:38:0E:59:32:39** **Failed to remove device: org.bluez.Error.NotReady* What can I do? Thank you Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: > Hey, > > I'll try to help a bit here. > > First as for the unknown or unwanted entries on the paired devices lists > [and such] you can try to remove them from the bluetoothctl level. > > ) enable developers mode & connect it via usb cable > ) login with adb shell to the deivce > ) type $ bluetoothctl > ) then type: devices - to list the known devices > ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the > device [not it's name] > > Second we are in the of releasing the newest bluez 5.41 which is now in > silo 37. If you are familiar with installing silos on your device you > can try it out and check if it improves anything. It includes fixes for > link management and pairing therefore there is a chance [although not > certain] that there might be joy. > > If unsure please ask. > > Best, > Konrad > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, thank you for your answer, I will try to apply the procedure that you have described during this weekend. I never installed a silos, so maybe it's better to wait the OTA-13 that incude bluez 5.41. Thank you, Marco Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: > Hey, > > I'll try to help a bit here. > > First as for the unknown or unwanted entries on the paired devices lists > [and such] you can try to remove them from the bluetoothctl level. > > ) enable developers mode & connect it via usb cable > ) login with adb shell to the deivce > ) type $ bluetoothctl > ) then type: devices - to list the known devices > ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the > device [not it's name] > > Second we are in the of releasing the newest bluez 5.41 which is now in > silo 37. If you are familiar with installing silos on your device you > can try it out and check if it improves anything. It includes fixes for > link management and pairing therefore there is a chance [although not > certain] that there might be joy. > > If unsure please ask. > > Best, > Konrad > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
After the OTA-12 update, my MX4 still not working. Also I cant remove the "Nissan Connect" as paired device (see the image attached). I never been able to pair MX4 with Nissan Connect, so I don't know why it results as paired. ** Attachment added: "screenshot20160727_225309929.png" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4708302/+files/screenshot20160727_225309929.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1407505] Re: Unable to boot
** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650659/+files/AlsaInfo.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650660/+files/CRDA.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650661/+files/CurrentDmesg.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650662/+files/JournalErrors.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650663/+files/Lspci.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650664/+files/Lsusb.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650665/+files/ProcCpuinfo.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650666/+files/ProcEnviron.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650667/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650668/+files/ProcModules.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650669/+files/PulseList.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650670/+files/UdevDb.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407505/+attachment/4650671/+files/WifiSyslog.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/1407505 Title: Unable to boot Status in linux package in Ubuntu: Invalid Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled.
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
In my own case the bug persists with OTA 11 (Meizu MX4). @Stunts for this bug the milestone it's OTA12. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1407505] Re: No UMS support in radeon module
It's necessary to open a new bug report? Because this report it's for Ubuntu Utopic (no longer supported) and Ubuntu Vivid (that it's supported yet). -- 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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] Re: No UMS support in radeon module
I'm was running: "apport-collect 1407505", all of my comments up there are autogenerated by apport-collect, I'm sorry for the quantities. I have updated from Ubuntu 15.10 to Ubuntu 16.04 LTS and now I'm affected from this bug. The kernel version is: 4.4.0-21-generic Running: dmesg | egrep 'drm|radeon' I'm getting this error: [1.127347] [drm] Initialized drm 1.1.0 20060810 [1.159659] [drm] VGACON disable radeon kernel modesetting. [1.159734] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [1.196474] [drm] VGACON disable radeon kernel modesetting. [1.196549] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 18.569430] [drm] VGACON disable radeon kernel modesetting. [ 18.569467] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! I'm tried to edit the /etc/default/grub from GRUB_CMDLINE_LINUX_DEFAULT: "quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT: "radeon.modeset=1" without success. -- 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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).
[Kernel-packages] [Bug 1407505] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650670/+files/UdevDb.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650668/+files/ProcModules.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650664/+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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650662/+files/JournalErrors.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650671/+files/WifiSyslog.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650669/+files/PulseList.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650666/+files/ProcEnviron.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650667/+files/ProcInterrupts.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650665/+files/ProcCpuinfo.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650661/+files/CurrentDmesg.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650659/+files/AlsaInfo.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650663/+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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1407505] Re: No UMS support in radeon module
ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: marco 1976 F pulseaudio /dev/snd/controlC0: marco 1976 F pulseaudio /dev/snd/controlC1: marco 1976 F pulseaudio /dev/snd/controlC2: marco 1976 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-22 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp9s0no wireless extensions. enp7s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=dc0372d0-03d5-4b50-9cbb-a83a7c27da67 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/03/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0610 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd09/03/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Tags added: apport-collected xenial -- 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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810
[Kernel-packages] [Bug 1407505] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1407505/+attachment/4650660/+files/CRDA.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/1407505 Title: No UMS support in radeon module Status in linux package in Ubuntu: Confirmed Status in linux source package in Utopic: Won't Fix Status in linux source package in Vivid: Confirmed Bug description: System: Kubuntu (adm64) 14.10. Last update: 4-Jan-2015 No proprietary drivers. No 3rd party software. The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28. From syslog for -28 kernel: Jan 4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module! Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting. Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module! From syslog for -17 kernel: Jan 4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 20060810 Jan 4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel modesetting enabled. Jan 4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb from VESA VGA Jan 4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA). Jan 4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 0xFDDC Jan 4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 131072 Jan 4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
In my own case it don't work. It's impossible to pair the MX4 (OTA-10.1) to "Nissan Connect" bluetooth. Also, it's now impossible to forget the "Nissan Connect" paired before. The "forget" button isn't cliccable (see pictures attached). You can find my bluetooth log file (with OTA-9) attached at the message number 22 ( https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/comments/22 ). If needed, I can prepare a new log file. ** Attachment added: "MX4_bluetooth_car_pair_problem.zip" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4635443/+files/MX4_bluetooth_car_pair_problem.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Problem persist for me too after updating to OTA-10. I'm using Meizu MX4 with "Nissan Connect" (first version, 2011 edition, see pic: https://launchpadlibrarian.net/236039500/Nissan-Connect-First-Version.jpg ). The phone finds "Nissan Connect", but when the pair procedure starts, it stops by itself before than asks me to enter the pin code "1234" to pair the device. After this stops the Nissan Connect display says "connection failed". "Nissan Connect" can connect phones with bluetooth 4, for example, I have also a Samsung S3 mini, and it works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
@Stunts: No way. When I'm trying to save the file pressing "enter", nothing happen. Editor ask me for a format (M-D DOS format; M-M Mac format; M-A Append; ecc), see the picture attached at message #25 This is the procedure that I have applied: - connect MX4 via terminal adb - insert command: sudo mount -o remount,rw / - edit file with: sudo nano /etc/init/bluetooth.conf - remove -d option from: exec /usr/sbin/bluetoothd -d - press CTRL + O for saving - trying to press enter for apply changes, but nothing happen What can I do? Thank you Marco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
@Stunts: I have followed the instruction that you shared here: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/comments/14 now I'm trying to remove "-d" option from "/etc/init/bluetooth.conf" but when I'm saving the file, nano's editor ask me if I wanna save the file as: - M-D DOS format - M-M Mac format - M-A Append - M-P Prepend - M-B Backup file (see picture attached) How did you save the file? *** @Simon Fels: Can the log file I attached in message 22 be useful? ** Attachment added: "problema_rimozione_opzione_-d.png" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4597999/+files/problema_rimozione_opzione_-d.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Thanks to the instruction provided by "Stunt" ( https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/comments/14 ), I have generated a bluetooth log file that you can find attached at this message. My own hands free system it's a NISSAN CONNECT, I'm using a Meizu MX4 with OTA 9.1. I hope that this log file contains what you need and let me know if you require anything else. Thank you. P.S.: I think I have removed any sensitive information from that log. ** Attachment added: "syslog_bluetooth pair_MX4.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4596895/+files/syslog_bluetooth%20pair_MX4.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi, today I've tried to make a log file about the bluetooth pair problem. I followed this istruction: https://wiki.ubuntu.com/DebuggingBluetooth for generating log files with debugging information. After this, I tried to pair my phone with car bluettoth system, and I have copied the "bluetoothhd" file from my phone (/usr/sbin/) to my desktop. I have opened this file but only a little part it's readable, part of this file contain unreadable characters; so I attach at this message only the readable parts. Please, let me know if this procedure is correct. This file attached it's useful for debugging? Thank you ** Attachment added: "bluetoothd.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4576690/+files/bluetoothd.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
I asked this because I read that it's dangerous switch in RW mode. At this url: http://askubuntu.com/questions/600065/consequences-of-using-apt-get-in-ubuntu-touch I read this: http://askubuntu.com/a/600313 ['evergreen' answer] "By default the system is read-only. You can switch to read-write mode, although this disables Ubuntu system upgrades.The main purpose for this is developing the Ubuntu system directly. This is not required for developing apps or using the system normally. Recovering from read-write mode is possible but requires reinstalling the system from scratch. Warning: Switching a device to read-write mode (and/or recovering from it) is an advanced feature and may result in complete data loss. Warning: Switching a device to read-write mode disables automatic over-the-air delta updates. Accepting a full over-the-air update after making a device writable may undo changes you have made." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
@Stunts Thank you for your reply. For generating bluetooth log files with debugging information it's necessary to switch in read and write mode ( sudo mount -o remount,rw / ), after this, how can I restore the read only mode? Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Where I can find the bluetooth syslog file? I wanna attach my own log to helping the fix procedure. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
I can't pair the device to the system. I'm using MX4 with OTA9. I have a Nissan, with "Nissan Connect" (first version, 2011 edition, see pic attached). The car finds the phone "Meizu MX4 Ubuntu Edition", and then asks me to enter the code "1234" to pair the device, but after this it says "connection failed". This system can connect phones with bluetooth 4; for example, I have also a Samsung S3, and it works. ** Attachment added: "Nissan-Connect-First-Version.jpg" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4562226/+files/Nissan-Connect-First-Version.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
@Stunts: No. I'm never been able to pair them. It never work in my own case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1113779] Re: 14e4:170c Broadcom bcm4401-b0 network card no longer functional
In a forum where I partecipate we solved the problem.
We found that the problem is caused about a file called blacklist-bcm43.conf
that put all the broadcom driver in blacklist after the installation (that no
happened during live cd session).
This is the cause of the issue.
You have to move this file from /etc/modprobe.d and reboot, later
network card works fine.
This is the content of /etc/modprobe.d/blacklist-bcm43.conf
***
paola@paola-Inspiron-1520:/etc/modprobe.d$ cat blacklist-bcm43.conf
# Warning: This file is autogenerated by bcmwl. All changes to this file will
be lost.
blacklist b43
blacklist b43legacy
blacklist ssb
blacklist bcm43xx
blacklist brcm80211
blacklist brcmfmac
blacklist brcmsmac
blacklist bcma
blacklist b44
install wl modprobe -r b43 b44 b43legacy ssb; modprobe --ignore-install wl ;
modprobe --ignore-install b44
***
Can see that all broadcom are blacklisted.
I solved moving this file to Desktop and after a reboot the network card works
fine.
From terminal I used command mv to move the file to Desktop:
***
paola@paola-Inspiron-1520:~$ sudo mv /etc/modprobe.d/blacklist-bcm43.conf
/home/paola/Scrivania
***
And after a reboot the network card works.
We talk about this problem on this thread:
http://www.linux-magazine.it/forum/index.php/topic,15933.msg53955.html#msg53955
but it's only in italian, I'm sorry.
I hope that solution works for other people that have this problem.
I dont know how this thread works, but if is possible someone report
this solution and what is the problem to whom it may concern.
Thank you.
--
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/1113779
Title:
14e4:170c Broadcom bcm4401-b0 network card no longer functional
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This actually happedned when I did an upgrade to 3.2.0-36-generic
about a week ago. The network card was working fine until I rebooted
after the update. Now to get internet access on this machine I have
had to use a pcmcia network card. It appears though I have been
unable to confirm this, that the bcmlw update blacklisted all broadcom
drivers.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-37-generic 3.2.0-37.58
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tom9780 F pulseaudio
/dev/snd/pcmC0D0p: tom9780 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 42'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801d4,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 14
Simple ctrls : 7
Date: Sat Feb 2 13:17:39 2013
HibernationDevice: RESUME=UUID=bb8dbb09-d641-48d1-a1ca-e4f9296956e5
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
MachineType: Dell Inc. Latitude D520
MarkForUpload: True
PccardctlStatus:
Socket 0:
5.0V
16-bit
PC Card
Subdevice 0 (function 0) bound to driver axnet_cs
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic
root=UUID=98c0e985-6278-48f4-832d-b54216f77312 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-37-generic N/A
linux-backports-modules-3.2.0-37-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2013-01-30 (2 days ago)
dmi.bios.date: 10/13/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0NF743
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA02:bd10/13/2006:svnDellInc.:pnLatitudeD520:pvr:rvnDellInc.:rn0NF743:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D520
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1113779/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1214348] Re: package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to install/upgrade
I followed your instructions, and now it works. Thank you. -- 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/1214348 Title: package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to install/upgrade Status in “linux” package in Ubuntu: Incomplete Bug description: I get this error every time I turn on the computer. ProblemType: Package DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 2198 F pulseaudio /dev/snd/pcmC0D0p: marco 2198 F...m pulseaudio CRDA: country BN: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5735 - 5835 @ 40), (N/A, 30) Date: Sun Aug 18 17:51:50 2013 DuplicateSignature: package:linux-image-3.8.0-19-generic:3.8.0-19.30: ErrorMessage: HibernationDevice: RESUME=UUID=cce8dc62-c1cf-40fb-a2db-3378f4d619c1 InstallationDate: Installed on 2012-10-23 (300 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Vostro 1500 MarkForUpload: True ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=04987d58-eccb-4118-869d-0631c949d080 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.00-13ubuntu3 SourcePackage: linux Title: package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to install/upgrade UpgradeStatus: Upgraded to raring on 2013-04-27 (114 days ago) dmi.bios.date: 08/02/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0WY040 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd08/02/2007:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1214348] [NEW] package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to install/upgrade
Public bug reported: I get this error every time I turn on the computer. ProblemType: Package DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 2198 F pulseaudio /dev/snd/pcmC0D0p: marco 2198 F...m pulseaudio CRDA: country BN: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5735 - 5835 @ 40), (N/A, 30) Date: Sun Aug 18 17:51:50 2013 DuplicateSignature: package:linux-image-3.8.0-19-generic:3.8.0-19.30: ErrorMessage: HibernationDevice: RESUME=UUID=cce8dc62-c1cf-40fb-a2db-3378f4d619c1 InstallationDate: Installed on 2012-10-23 (300 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Vostro 1500 MarkForUpload: True ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=04987d58-eccb-4118-869d-0631c949d080 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.00-13ubuntu3 SourcePackage: linux Title: package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to install/upgrade UpgradeStatus: Upgraded to raring on 2013-04-27 (114 days ago) dmi.bios.date: 08/02/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0WY040 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd08/02/2007:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1500 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package need-duplicate-check raring varlogdistupgradeapttermlog-examined -- 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/1214348 Title: package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to install/upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I get this error every time I turn on the computer. ProblemType: Package DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 2198 F pulseaudio /dev/snd/pcmC0D0p: marco 2198 F...m pulseaudio CRDA: country BN: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5735 - 5835 @ 40), (N/A, 30) Date: Sun Aug 18 17:51:50 2013 DuplicateSignature: package:linux-image-3.8.0-19-generic:3.8.0-19.30: ErrorMessage: HibernationDevice: RESUME=UUID=cce8dc62-c1cf-40fb-a2db-3378f4d619c1 InstallationDate: Installed on 2012-10-23 (300 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Vostro 1500 MarkForUpload: True ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=04987d58-eccb-4118-869d-0631c949d080 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.00-13ubuntu3 SourcePackage: linux Title: package linux-image-3.8.0-19-generic 3.8.0-19.30 failed to install/upgrade UpgradeStatus: Upgraded to raring on 2013-04-27 (114 days ago) dmi.bios.date: 08/02/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0WY040 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd08/02/2007:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Vostro 1500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1113779] Re: 14e4:170c Broadcom bcm4401-b0 network card no longer functional
I have the same problem on Ubuntu 13.04 (amd64). But when i try to
uninstall broadcom-sta-common and bcmwl the terminal answer me:
***
paola@paola-Inspiron-1520:~$ sudo apt-get remove broadcom-sta-common
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Il pacchetto broadcom-sta-common non è installato e quindi non è stato rimosso
--- Transl: The package broadcom-sta-common is not installed, and then was not
removed
0 aggiornati, 0 installati, 0 da rimuovere e 308 non aggiornati.
paola@paola-Inspiron-1520:~$ sudo apt-get remove bcmwl
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
E: Impossibile trovare il pacchetto bcmwl --- Transl: Could not find package
bcmwl
***
but broadcom-sta-common exist:
***
paola@paola-Inspiron-1520:~$ sudo dpkg -l bcmwl-kernel-source
Voluto=U (non noto)/I (installato)/R (rimosso)/P (rimosso totale)/H (in attesa)
| Stato=Non/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(nessuno)/R (reinstallazione richiesta) (Stato,Err: maiuscolo=grave)
||/ Nome Versione Architettura Descrizione
+++-==---=
ii bcmwl-kernel-s 6.20.155.1+b amd64Broadcom 802.11 Linux STA wireles
***
and b44 is already installed, but doesn't work:
***
paola@paola-Inspiron-1520:~$ modinfo b44
filename:
/lib/modules/3.8.0-19-generic/kernel/drivers/net/ethernet/broadcom/b44.ko
version:2.0
license:GPL
description:Broadcom 44xx/47xx 10/100 PCI ethernet driver
author: Felix Fietkau, Florian Schirmer, Pekka Pietikainen, David S.
Miller
srcversion: 5C684C4C68DF8EDC52F7285
alias: pci:v14E4d170Csv*sd*bc*sc*i*
alias: pci:v14E4d4402sv*sd*bc*sc*i*
alias: pci:v14E4d4401sv*sd*bc*sc*i*
alias: ssb:v4243id0806rev*
depends:ssb
intree: Y
vermagic: 3.8.0-19-generic SMP mod_unload modversions
parm: b44_debug:B44 bitmapped debugging message enable value (int)
***
What can I do? wired connection and wifi doesn't work...
--
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/1113779
Title:
14e4:170c Broadcom bcm4401-b0 network card no longer functional
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
This actually happedned when I did an upgrade to 3.2.0-36-generic
about a week ago. The network card was working fine until I rebooted
after the update. Now to get internet access on this machine I have
had to use a pcmcia network card. It appears though I have been
unable to confirm this, that the bcmlw update blacklisted all broadcom
drivers.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-37-generic 3.2.0-37.58
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tom9780 F pulseaudio
/dev/snd/pcmC0D0p: tom9780 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 42'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801d4,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 14
Simple ctrls : 7
Date: Sat Feb 2 13:17:39 2013
HibernationDevice: RESUME=UUID=bb8dbb09-d641-48d1-a1ca-e4f9296956e5
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
MachineType: Dell Inc. Latitude D520
MarkForUpload: True
PccardctlStatus:
Socket 0:
5.0V
16-bit
PC Card
Subdevice 0 (function 0) bound to driver axnet_cs
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic
root=UUID=98c0e985-6278-48f4-832d-b54216f77312 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-37-generic N/A
linux-backports-modules-3.2.0-37-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2013-01-30 (2 days ago)
dmi.bios.date: 10/13/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0NF743
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
