[Desktop-packages] [Bug 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

2022-06-10 Thread Sebastien Bacher
k, let's try to keep pushing for 1.18 first

** Changed in: modemmanager (Ubuntu)
   Importance: Undecided => Low

** Changed in: modemmanager (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1978057

Title:
  [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized 
correctly.
  With the new rules, the modem devices could be recognized correctly. And also 
could avoid wrong command for other protocols, like send 'AT' to wwan0mbim.

  [Where problems could occur]
  It's just a udev rules, no harm to the system.

  [Fix]
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8

  udev: Match WWAN "type" attribute instead of device name
  Recent changes in the WWAN framework in the kernel changed the WWAN
  port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and
  "wwan0qmi0" [1, 2]. This means that the udev rules no longer match
  since AT/QMI are now lower-case and no longer at the end of the name.

  However, recently additionally a "type" sysfs attribute was added
  for all WWAN ports [3], which makes it much more reliable to match
  the WWAN port names without relying on their exact device name.

  Add some additional udev rules to apply the port hints based on the
  "type" sysfs attributes. This fixes the port enumeration on newer
  Linux kernels that include the aforementioned commits.

  Note that we still need to keep the old udev rules for now since
  Linux 5.13 does not have the "type" attribute yet.

  [1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde
  [3]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c

  (cherry picked from commit 4282c8d8)

  [Test]
  With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 
'Mobile Broadband' item in the top-right menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

2022-06-09 Thread Bin Li
@seb128,

 Thanks for your feedback, I prefer to update to 1.18 than this fix, and
as I know Stephane.Verdy has pushed 1.18 for long time to support more
modem devices, so let's wait for the 1.18.

 IF the 1.18 was dropped in proposed, we could reconsider this fix.
Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1978057

Title:
  [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]
  On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized 
correctly.
  With the new rules, the modem devices could be recognized correctly. And also 
could avoid wrong command for other protocols, like send 'AT' to wwan0mbim.

  [Where problems could occur]
  It's just a udev rules, no harm to the system.

  [Fix]
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8

  udev: Match WWAN "type" attribute instead of device name
  Recent changes in the WWAN framework in the kernel changed the WWAN
  port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and
  "wwan0qmi0" [1, 2]. This means that the udev rules no longer match
  since AT/QMI are now lower-case and no longer at the end of the name.

  However, recently additionally a "type" sysfs attribute was added
  for all WWAN ports [3], which makes it much more reliable to match
  the WWAN port names without relying on their exact device name.

  Add some additional udev rules to apply the port hints based on the
  "type" sysfs attributes. This fixes the port enumeration on newer
  Linux kernels that include the aforementioned commits.

  Note that we still need to keep the old udev rules for now since
  Linux 5.13 does not have the "type" attribute yet.

  [1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde
  [3]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c

  (cherry picked from commit 4282c8d8)

  [Test]
  With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 
'Mobile Broadband' item in the top-right menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

2022-06-09 Thread Sebastien Bacher
No, it's not possible, we only have one proposed pocket. If we want to
do that we need to delete the 1.18 update, do the SRU with the fix only
and then restart the process again for 1.18. Is that the option you want
to go for now?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1978057

Title:
  [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]
  On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized 
correctly.
  With the new rules, the modem devices could be recognized correctly. And also 
could avoid wrong command for other protocols, like send 'AT' to wwan0mbim.

  [Where problems could occur]
  It's just a udev rules, no harm to the system.

  [Fix]
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8

  udev: Match WWAN "type" attribute instead of device name
  Recent changes in the WWAN framework in the kernel changed the WWAN
  port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and
  "wwan0qmi0" [1, 2]. This means that the udev rules no longer match
  since AT/QMI are now lower-case and no longer at the end of the name.

  However, recently additionally a "type" sysfs attribute was added
  for all WWAN ports [3], which makes it much more reliable to match
  the WWAN port names without relying on their exact device name.

  Add some additional udev rules to apply the port hints based on the
  "type" sysfs attributes. This fixes the port enumeration on newer
  Linux kernels that include the aforementioned commits.

  Note that we still need to keep the old udev rules for now since
  Linux 5.13 does not have the "type" attribute yet.

  [1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde
  [3]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c

  (cherry picked from commit 4282c8d8)

  [Test]
  With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 
'Mobile Broadband' item in the top-right menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

2022-06-09 Thread Bin Li
** Patch added: "udev-Match-WWAN-type-attribute-instead-of-device-nam.patch"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+attachment/5595791/+files/udev-Match-WWAN-type-attribute-instead-of-device-nam.patch

** Description changed:

  [Impact]
  On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized 
correctly.
- With the new rules, the modem devices could be recognized correctly. And also 
could avoid wrong command for other protocols, like set 'AT' to wwan0mbim.
+ With the new rules, the modem devices could be recognized correctly. And also 
could avoid wrong command for other protocols, like send 'AT' to wwan0mbim.
  
  [Where problems could occur]
  It's just a udev rules, no harm to the system.
  
  [Fix]
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8
  
  udev: Match WWAN "type" attribute instead of device name
  Recent changes in the WWAN framework in the kernel changed the WWAN
  port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and
  "wwan0qmi0" [1, 2]. This means that the udev rules no longer match
  since AT/QMI are now lower-case and no longer at the end of the name.
  
  However, recently additionally a "type" sysfs attribute was added
  for all WWAN ports [3], which makes it much more reliable to match
  the WWAN port names without relying on their exact device name.
  
  Add some additional udev rules to apply the port hints based on the
  "type" sysfs attributes. This fixes the port enumeration on newer
  Linux kernels that include the aforementioned commits.
  
  Note that we still need to keep the old udev rules for now since
  Linux 5.13 does not have the "type" attribute yet.
  
  [1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde
  [3]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c
  
  (cherry picked from commit 4282c8d8)
  
  [Test]
  With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 
'Mobile Broadband' item in the top-right menu.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1978057

Title:
  [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]
  On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized 
correctly.
  With the new rules, the modem devices could be recognized correctly. And also 
could avoid wrong command for other protocols, like send 'AT' to wwan0mbim.

  [Where problems could occur]
  It's just a udev rules, no harm to the system.

  [Fix]
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8

  udev: Match WWAN "type" attribute instead of device name
  Recent changes in the WWAN framework in the kernel changed the WWAN
  port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and
  "wwan0qmi0" [1, 2]. This means that the udev rules no longer match
  since AT/QMI are now lower-case and no longer at the end of the name.

  However, recently additionally a "type" sysfs attribute was added
  for all WWAN ports [3], which makes it much more reliable to match
  the WWAN port names without relying on their exact device name.

  Add some additional udev rules to apply the port hints based on the
  "type" sysfs attributes. This fixes the port enumeration on newer
  Linux kernels that include the aforementioned commits.

  Note that we still need to keep the old udev rules for now since
  Linux 5.13 does not have the "type" attribute yet.

  [1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde
  [3]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c

  (cherry picked from commit 4282c8d8)

  [Test]
  With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 
'Mobile Broadband' item in the top-right menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

2022-06-08 Thread Bin Li
And I knew there is a plan to upgrade MM to 1.18.6[1], and it's proposed
channel, but it has been hold more than one month because of some risks.

Is it possible that we merge this fix[2] into 1.16.6 first.

[1] https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1965901
[2] 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1978057

Title:
  [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]
  On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized 
correctly.
  With the new rules, the modem devices could be recognized correctly. And also 
could avoid wrong command for other protocols, like set 'AT' to wwan0mbim.

  [Where problems could occur]
  It's just a udev rules, no harm to the system.

  [Fix]
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8

  udev: Match WWAN "type" attribute instead of device name
  Recent changes in the WWAN framework in the kernel changed the WWAN
  port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and
  "wwan0qmi0" [1, 2]. This means that the udev rules no longer match
  since AT/QMI are now lower-case and no longer at the end of the name.

  However, recently additionally a "type" sysfs attribute was added
  for all WWAN ports [3], which makes it much more reliable to match
  the WWAN port names without relying on their exact device name.

  Add some additional udev rules to apply the port hints based on the
  "type" sysfs attributes. This fixes the port enumeration on newer
  Linux kernels that include the aforementioned commits.

  Note that we still need to keep the old udev rules for now since
  Linux 5.13 does not have the "type" attribute yet.

  [1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde
  [3]: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c

  (cherry picked from commit 4282c8d8)

  [Test]
  With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 
'Mobile Broadband' item in the top-right menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp