[Kernel-packages] [Bug 1569484] Re: Auto Ethernet connection profile appears. Wifi does not work anymore.

2016-04-18 Thread Markus Kohli
I've tried kernel 4.6rc3 to no avail (same machine, Dell XPS 13 9350).
The thing has the broadcom 4350 card.

I'm running a 4.4 lowlatency kernel on this machine, which is not
upgraded automatically or anything, so the problem can IMHO not come
from a kernel change, but it must be something network-manager (or
external driver) related.

The "error getting signal strenght" is only a consequence of the wifi
not being recognized as a wifi, but as an ethernet connection. Ethernet
doesn't have the parameter "signal strength".

The problem lies here:
GERÄTTYP   STATUS   VERBINDUNG 
docker0  bridgeverbundendocker0
wlp3s0   ethernet  verbundenwlp3s0 

wlp3s0 is found to be an ethernet connection.

Since today also my MacBook Pro shows the same behaviour, with a
broadcom BCM43602.

I manage to get wifi running by defining the ssid/passphrase with 
wpa_passphrase, starting wpa_supplicant manually and then running dhclient on 
the interface and setting a nameserver in /etc/resolv.conf by hand.
I ordered an Intel wifi card for now, want to see if this changes anything.

Strange enough, every 26th (or something around that) will let the wifi
show up like it's supposed to, so the problem is really very hard to
grasp.

-- 
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/1569484

Title:
  Auto Ethernet connection profile appears. Wifi does not work anymore.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I ran sudo apt-get upgrade && sudo apt-get dist-upgrade. Some
  installation have done and Auto Ethernet profile emerged in internet
  settings. After those installations I could not connect to internet.
  My laptop is Dell xps 13 9350.

  I used my TP-LINK wireless adapter to be able to send you this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 12 20:18:04 2016
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-10 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlxc4e98417061b  proto static  metric 600
   169.254.0.0/16 dev wlxc4e98417061b  scope link  metric 1000
   192.168.1.0/24 dev wlxc4e98417061b  proto kernel  scope link  src 
192.168.1.63  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH
   berkaywifi 1  3f5048a4-32e9-4ca5-ad31-f615ca2bc0e9  802-11-wireless  
1460481455  Sal 12 Nis 2016 20:17:35 EEST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlxc4e98417061b  
activated  /org/freedesktop/NetworkManager/ActiveConnection/1
   berkaywifi 2  6afc325f-3765-4687-b4dd-47c17a93f185  802-11-wireless  
1460480549  Sal 12 Nis 2016 20:02:29 EEST  yes  0 
no/org/freedesktop/NetworkManager/Settings/2  no  --   
-- --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH   
   CONNECTIONCON-UUID  CON-PATH
   wlxc4e98417061b  wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  berkaywifi 1  
3f5048a4-32e9-4ca5-ad31-f615ca2bc0e9  
/org/freedesktop/NetworkManager/ActiveConnection/1
   wlp58s0  ethernet  disconnected  
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
   lo   loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  ---- 
   --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569484/+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 1569484] Re: Auto Ethernet connection profile appears. Wifi does not work anymore.

2016-04-21 Thread Markus Kohli
Definitely seems to be brcm-driver related; I swapped my card for an intel 8260 
and everything works like a charm.
If any logs are needed I can provide from my macbook pro with the same issue.

-- 
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/1569484

Title:
  Auto Ethernet connection profile appears. Wifi does not work anymore.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I ran sudo apt-get upgrade && sudo apt-get dist-upgrade. Some
  installation have done and Auto Ethernet profile emerged in internet
  settings. After those installations I could not connect to internet.
  My laptop is Dell xps 13 9350.

  I used my TP-LINK wireless adapter to be able to send you this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 12 20:18:04 2016
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-10 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlxc4e98417061b  proto static  metric 600
   169.254.0.0/16 dev wlxc4e98417061b  scope link  metric 1000
   192.168.1.0/24 dev wlxc4e98417061b  proto kernel  scope link  src 
192.168.1.63  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH
   berkaywifi 1  3f5048a4-32e9-4ca5-ad31-f615ca2bc0e9  802-11-wireless  
1460481455  Sal 12 Nis 2016 20:17:35 EEST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlxc4e98417061b  
activated  /org/freedesktop/NetworkManager/ActiveConnection/1
   berkaywifi 2  6afc325f-3765-4687-b4dd-47c17a93f185  802-11-wireless  
1460480549  Sal 12 Nis 2016 20:02:29 EEST  yes  0 
no/org/freedesktop/NetworkManager/Settings/2  no  --   
-- --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH   
   CONNECTIONCON-UUID  CON-PATH
   wlxc4e98417061b  wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  berkaywifi 1  
3f5048a4-32e9-4ca5-ad31-f615ca2bc0e9  
/org/freedesktop/NetworkManager/ActiveConnection/1
   wlp58s0  ethernet  disconnected  
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
   lo   loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  ---- 
   --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569484/+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 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)

2023-02-04 Thread Markus Kohli
Regarding 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990700/comments/13:
I'm still seeing the same issue on Ubuntu 22.10 with mainline kernel 6.1.8 and 
6.1.9.
Did this somehow get kicked again, or am I misinterpreting the kernel-versions?

Dmesg states:
[   93.276679] mtk_t7xx :57:00.0: [PM] SAP suspend error: -110
[   93.276736] mtk_t7xx :57:00.0: PM: pci_pm_suspend(): 
t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110
[   93.276800] mtk_t7xx :57:00.0: PM: dpm_run_callback(): 
pci_pm_suspend+0x0/0x1b0 returns -110
[   93.276832] mtk_t7xx :57:00.0: PM: failed to suspend async: error -110
[   93.277194] PM: Some devices failed to suspend, or early wake event detected

Kernel:
Linux zephyr 6.1.9-060109-generic #202302010835 SMP PREEMPT_DYNAMIC Wed Feb  1 
08:41:31 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1990700

Title:
   Fibocom WWAN FM350-GL suspend error (notebook not suspend)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Fibocom WWAN FM350-GL equipped platform fails to suspend.

  [Fix]

  Full t7xx driver is still under development and some of them have
  already accepted and merged in mainline kernel. The following commits
  are once in the mainline and are reverted in v6.0:

    d20ef656f994 net: wwan: t7xx: Add AP CLDMA
    007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration
    140424d90165 net: wwan: t7xx: PCIe reset rescan
    87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and
     coredump collection

  The first patch implemented the other AP-CLDMA, and with that applied,
  platforms in question may suspend and resume normally as every bits are in 
position.

  However, while these patches had been reverted for another revision
  that is still being worked on by the hardware vendor, a minimum,
  sauced patch is created to work-around this first to meet project
  schedules, and will be reverted and superseded with a final, mainline
  landing revision.

  [Test Case]

  Trigger suspend and there should be no more suspend errors from t7xx:

    mtk_t7xx :58:00.0: [PM] SAP suspend error: -110
    mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 
[mtk_t7xx] returns -110
    mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 
returns -110
    mtk_t7xx :58:00.0: PM: failed to suspend async: error -110

  [Where problems could occur]

  The t7xx driver is still incomplete and we're staging aforementioned 4
  patches in internal experimental kernels for development use.

  [Other Info]

  This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0
  are nominated for fix.

  == original bug report ==

  Hi,
  I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module 
mtk_t7xx . Power management for this modem is bad. When the notebook goes to 
sleep/suspend, kernel module mtk_t7xx return an error:

  mtk_t7xx :58:00.0: [PM] SAP suspend error: -110
  mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 
[mtk_t7xx] returns -110
  mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 
returns -110
  mtk_t7xx :58:00.0: PM: failed to suspend async: error -110

  So power management failed to suspend:
  PM: Some devices failed to suspend, or early wake event detected

  And the notebook not suspend and wake up again.
  It must be this module, because if I remove the module first (modprobe -r), 
the laptop goes to sleep and wakes up normally.
  However, after reinserting the module, the modem no longer appears in the 
system.

  Expected state: sleep occurs when the device is put to sleep -
  including the modem. When you wake up, you will wake up, including
  activating the modem and logging into the operator's network.

  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  lspci -v:
  58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01)
  Subsystem: Device 1cf8:3500
  Flags: bus master, fast devsel, latency 0, IRQ 17
  Memory at 601e80 (64-bit, prefetchable) [size=32K]
  Memory at 5e80 (64-bit, non-prefetchable) [size=8M]
  Memory at 601e00 (64-bit, prefetchable) [size=8M]
  Capabilities: [80] Express Endpoint, MSI 00
  Capabilities: [d0] MSI-X:

[Kernel-packages] [Bug 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)

2023-02-23 Thread Markus Kohli
About the 5G support:
nm-applet reports LTE, but it does work on 5G.
I just got 400+ Mbps yesterday when testing, which obviously is not LTE.
Might just be a naming issue there.
The sleep issue persists however, latest tests with 6.1.12 are the same as 
before.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1990700

Title:
   Fibocom WWAN FM350-GL suspend error (notebook not suspend)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Fibocom WWAN FM350-GL equipped platform fails to suspend.

  [Fix]

  Full t7xx driver is still under development and some of them have
  already accepted and merged in mainline kernel. The following commits
  are once in the mainline and are reverted in v6.0:

    d20ef656f994 net: wwan: t7xx: Add AP CLDMA
    007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration
    140424d90165 net: wwan: t7xx: PCIe reset rescan
    87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and
     coredump collection

  The first patch implemented the other AP-CLDMA, and with that applied,
  platforms in question may suspend and resume normally as every bits are in 
position.

  However, while these patches had been reverted for another revision
  that is still being worked on by the hardware vendor, a minimum,
  sauced patch is created to work-around this first to meet project
  schedules, and will be reverted and superseded with a final, mainline
  landing revision.

  [Test Case]

  Trigger suspend and there should be no more suspend errors from t7xx:

    mtk_t7xx :58:00.0: [PM] SAP suspend error: -110
    mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 
[mtk_t7xx] returns -110
    mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 
returns -110
    mtk_t7xx :58:00.0: PM: failed to suspend async: error -110

  [Where problems could occur]

  The t7xx driver is still incomplete and we're staging aforementioned 4
  patches in internal experimental kernels for development use.

  [Other Info]

  This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0
  are nominated for fix.

  == original bug report ==

  Hi,
  I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module 
mtk_t7xx . Power management for this modem is bad. When the notebook goes to 
sleep/suspend, kernel module mtk_t7xx return an error:

  mtk_t7xx :58:00.0: [PM] SAP suspend error: -110
  mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 
[mtk_t7xx] returns -110
  mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 
returns -110
  mtk_t7xx :58:00.0: PM: failed to suspend async: error -110

  So power management failed to suspend:
  PM: Some devices failed to suspend, or early wake event detected

  And the notebook not suspend and wake up again.
  It must be this module, because if I remove the module first (modprobe -r), 
the laptop goes to sleep and wakes up normally.
  However, after reinserting the module, the modem no longer appears in the 
system.

  Expected state: sleep occurs when the device is put to sleep -
  including the modem. When you wake up, you will wake up, including
  activating the modem and logging into the operator's network.

  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  lspci -v:
  58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01)
  Subsystem: Device 1cf8:3500
  Flags: bus master, fast devsel, latency 0, IRQ 17
  Memory at 601e80 (64-bit, prefetchable) [size=32K]
  Memory at 5e80 (64-bit, non-prefetchable) [size=8M]
  Memory at 601e00 (64-bit, prefetchable) [size=8M]
  Capabilities: [80] Express Endpoint, MSI 00
  Capabilities: [d0] MSI-X: Enable+ Count=34 Masked-
  Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
  Capabilities: [f8] Power Management version 3
  Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 
Len=008 
  Capabilities: [108] Latency Tolerance Reporting
  Capabilities: [110] L1 PM Substates
  Capabilities: [200] Advanced Error Reporting
  Capabilities: [300] Secondary PCI Express
  Kernel driver in use: mtk_t7xx
  Kernel modules: mtk_t7xx

  lshw:
  *-generic
  description: Wireless