[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2019-07-25 Thread Jelle de Jong
I can confirm the same behaviour:

$ sudo dmidecode -t bios
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x000E, DMI type 0, 24 bytes
BIOS Information
Vendor: LENOVO
Version: H6ETA0WW (2.18 )
Release Date: 06/01/2018
Address: 0xE
Runtime Size: 128 kB
ROM Size: 12288 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
NEC PC-98
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 2.18
Firmware Revision: 2.1

Handle 0x0020, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Abbreviated
Installable Languages: 7
en-US
fr-FR
ja-JP
ko-KR
zh-CHT
zh-CHS
ru-RU
Currently Installed Language: en-US


$ sudo dmidecode -t system
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x000F, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 33533MG
Version: ThinkPad T430u
Serial Number: PB88L27
UUID: 507a2801-5144-11cb-8738-9d5ba3e2b1ee
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_3353
Family: ThinkPad T430u

Handle 0x001F, DMI type 12, 5 bytes
System Configuration Options

Handle 0x002D, DMI type 15, 81 bytes
System Event Log
Area Length: 98 bytes
Header Start Offset: 0x
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x00F0
Status: Valid, Not Full
Change Token: 0x0005
Header Format: Type 1
Supported Log Type Descriptors: 29
Descriptor 1: Single-bit ECC memory error
Data Format 1: Multiple-event handle
Descriptor 2: Multi-bit ECC memory error
Data Format 2: Multiple-event handle
Descriptor 3: Parity memory error
Data Format 3: None
Descriptor 4: Bus timeout
Data Format 4: None
Descriptor 5: I/O channel block
Data Format 5: None
Descriptor 6: Software NMI
Data Format 6: None
Descriptor 7: POST memory resize
Data Format 7: None
Descriptor 8: POST error
Data Format 8: POST results bitmap
Descriptor 9: PCI parity error
Data Format 9: None
Descriptor 10: PCI system error
Data Format 10: None
Descriptor 11: CPU failure
Data Format 11: None
Descriptor 12: EISA failsafe timer timeout
Data Format 12: None
Descriptor 13: Correctable memory log disabled
Data Format 13: None
Descriptor 14: Logging disabled
Data Format 14: None
Descriptor 15: System limit exceeded
Data Format 15: None
Descriptor 16: Asynchronous hardware timer expired
Data Format 16: None
Descriptor 17: System configuration information
Data Format 17: None
Descriptor 18: Hard disk information
Data Format 18: None
Descriptor 19: System reconfigured
Data Format 19: None
Descriptor 20: Uncorrectable CPU-complex error
Data Format 20: None
Descriptor 21: Log area reset/cleared
Data Format 21: None
Descriptor 22: System boot
Data Format 22: None
Descriptor 23: OEM-specific
Data Format 23: None
Descriptor 24: OEM-specific
Data Format 24: None
Descriptor 25: OEM-specific
Data Format 25: None
Descriptor 26: OEM-specific
Data Format 26: None
Descriptor 27: OEM-specific
Data Format 27: None
Descriptor 28: OEM-specific
Data Format 28: None
Descriptor 29: OEM-specific
Data Format 29: None

$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 root=/dev/mapper/lvm0--vol-root ro 
noacpi

$ uname -a
Linux yoad 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u1 (2019-07-19) x86_64 
GNU/Linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1777527] Re: 'ELAN0618 Touchpad' is not recognized on a fresh install

2018-07-13 Thread Jelle Witteveen
I just installed the mainline 4.18 rc4 kernel, it does not work yet.

$ uname -r
4.18.0-041800rc4-generic

ii  linux-image-unsigned-4.18.0-041800rc4-generic
4.18.0-041800rc4.201807082030   amd64Linux kernel
image for version 4.18.0 on 64 bit x86 SMP

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

Title:
  'ELAN0618 Touchpad' is not recognized on a fresh install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I tried ubuntu 16, 17 and 18. None of them were able to recongize my touchpad 
at all.
  I tried to boot from a windows installation USB, the touchpad worked right 
away.

  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ uname -a
  Linux Mazen-PC 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ dmesg > ~/dmesg
  OUTPUT ATTACHED

  $ cat /proc/bus/input/devices > ~/devices
  OUTPUT ATTACHED

  /var/log/Xorg.0.log
  Doesn't Exist!

  Note: I got the touchpad manufacturer and model (Elan0618) by
  installing Windows to get more info as Ubuntu was unable to detect the
  touchpad at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 18 16:24:57 2018
  InstallationDate: Installed on 2018-06-16 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777527/+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 1774425] [NEW] i915 driver limits virtual resolution to 8192x8192

2018-05-31 Thread Jelle De Loecker
Public bug reported:

I have an Intel Iris Pro 580 in my Intel Skull Canyon NUC6I7KYK, a nice
little device that has 3 video outputs:

* HDMI 2.0
* Mini DisplayPort
* Thunderbolt USB-C

The product specifications states that the device is able to output
three 4K signals. Unfortunately, whenever I tried this in Ubuntu it
failed, without any clear error message.

After fiddling with other DEs, Kubuntu told me the virtual resolution
was not supported. And indeed, as soon as I limited the virtual
resolution of the 3 screens to fit in 8192x8192 pixels, all screens
worked.

Apparently, the i915 driver (in "drivers/gpu/drm/i915/intel_display.c")
has not been updated for newer devices when reporting the maximum
resolution.

As you can see here:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c#L14671

Only GEN_2 & GEN_3 are checked for, but since the 7th generation max
virtual resolutions of 16384x16384 are supported.

This issue has been reported to the i915 maintainers a few times, but
nothing has changed yet :/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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

Title:
  i915 driver limits virtual resolution to 8192x8192

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Intel Iris Pro 580 in my Intel Skull Canyon NUC6I7KYK, a
  nice little device that has 3 video outputs:

  * HDMI 2.0
  * Mini DisplayPort
  * Thunderbolt USB-C

  The product specifications states that the device is able to output
  three 4K signals. Unfortunately, whenever I tried this in Ubuntu it
  failed, without any clear error message.

  After fiddling with other DEs, Kubuntu told me the virtual resolution
  was not supported. And indeed, as soon as I limited the virtual
  resolution of the 3 screens to fit in 8192x8192 pixels, all screens
  worked.

  Apparently, the i915 driver (in
  "drivers/gpu/drm/i915/intel_display.c") has not been updated for newer
  devices when reporting the maximum resolution.

  As you can see here:
  
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c#L14671

  Only GEN_2 & GEN_3 are checked for, but since the 7th generation max
  virtual resolutions of 16384x16384 are supported.

  This issue has been reported to the i915 maintainers a few times, but
  nothing has changed yet :/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774425/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2017-07-05 Thread Jelle De Loecker
Follow up to my post 54: I applied the fix posted in bug #1577120 and
now unmounting the NFS drive works, and the system shuts down just fine.

So I would guess the real underlying issue many people here have is
that, even though systemd is terminating timed out jobs it doesn't
actually shut down the system.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2017-07-05 Thread Jelle De Loecker
I have a Dell XPS 13 developer edition, I upgraded to Ubuntu 17.04 and
it still doesn't shutdown properly.

By the way: 6 shutdown jobs (5 that are for unmounting the encrypted
home folder and 1 for my NFS mount) time out before the "shutdown
target" is reached.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+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 1240940] Re: Need support for Realtek Wifi card rtl8723be [10ec:b723]

2015-11-07 Thread Jelle
Hi,

I'm experiencing the same issue as @avirup-das. I have the RTL8723BE on
my HP Stream 11. I verified the wifi works great in Windows (8) so the
internal card is okay.

Using Xubuntu-amd64 15.10 with new installed kernel 4.3.0 (same results
as in kernel 4.2.0)

Wifi does work and the laptop connects to the network, but my wireless
controller reports a very weak signal from my laptop. Ubuntu also
reports a weak signal with connection to the AP. I can only connect to
wifi when sitting next to the AP. (All my other devices can connect fine
from a certain distance from the AP.)

Signal is stable (very near the AP) when sitting in the same place and
there's no interference. Bandwidth/speed is between 1kb/sec and
100kb/sec max.

 # iwlist wlo1 txpower
returns Tx-Power at 20dBm (100mW), so that seems okay.

I've tried;
- Using newest lwfinger git driver: Getting the above results
- With and without the modprobe config options (tried on and off 'ips', 'msi', 
'fwlps' and 'swlps'): "msi:Y" results in no connection, msi:N does give above 
results. No difference setting other options.
- Use ndiswrapper to use Windows drivers for this card: This doesn't change 
anything to the above.

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

Title:
  Need support for Realtek Wifi  card rtl8723be [10ec:b723]

Status in HWE Next:
  Fix Released
Status in HWE Next trusty series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released

Bug description:
  This device is appearing in some OEM machines, but driver is not yet
  available upstream.

  This bug is only for the initial support of this WiFi adapter, it's
  not working 100% well yet, please report new "not working bug" or
  contact upstream but not keep posting comments, thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1240940/+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