[Touch-packages] [Bug 2061311] Re: dev's major/minor not captured in /sys/power/resume

2024-04-14 Thread monochromec
Please note that the work-around only works with one swap file.
Alternatively simply hardcode the device in the above statement.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2061311

Title:
  dev's major/minor not captured in /sys/power/resume

Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate 
complains about
  "Failed to find location to hibernate to: Invalid argument" caused by a "0:0" 
entry in /sys/power/resume

  Current configuration:

  1) Legacy boot configuration (non-UEFI!)

  2) Dual swap space configuration (/etc/fstab excerpt for swap partition and 
file):
  UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 noneswapsw  
0   0
  /swap noneswapsw,pri=2
0   0

  (swap file is the primary and only option for hibernation as partition
  is too small)

  2) resume config in /etc/initramfs-tools/conf.d/resume with the
  correct UUID and offset:

  RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320

  (blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
  BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")

  3) Correct grub config:

  GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320 acpi_enforce_resources=lax"

  Suspect a regression issue with systemd-255 as the issue did *not*
  appear with Focal Fossal (system-245) and only surfaced after the
  upgrade to 24.04.

  Work-around:

  Amend /etc/rc.local (if this is enabled via systemd) with:

  "lsblk | fgrep $(basename $(df -P $(fgrep swap /etc/fstab | grep '^/'
  | cut -d' ' -f1) | grep '^/' | cut -d' ' -f1)) | cut -d' ' -f4
  >/sys/power/resume"

  Please let me know if more info is required - more than happy to help!

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


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


[Touch-packages] [Bug 2061311] Re: dev's major/minor not captured in /sys/power/resume

2024-04-14 Thread monochromec
** Description changed:

  When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate 
complains about
  "Failed to find location to hibernate to: Invalid argument" caused by a "0:0" 
entry in /sys/power/resume
  
  Current configuration:
  
  1) Legacy boot configuration (non-UEFI!)
  
  2) Dual swap space configuration (/etc/fstab excerpt for swap partition and 
file):
  UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 noneswapsw  
0   0
  /swap noneswapsw,pri=2
0   0
+ 
+ (swap file is the primary and only option for hibernation as partition
+ is too small)
  
  2) resume config in /etc/initramfs-tools/conf.d/resume with the correct
  UUID and offset:
  
  RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b resume_offset=39608320
  
  (blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
  BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")
  
  3) Correct grub config:
  
  GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320 acpi_enforce_resources=lax"
  
  Suspect a regression issue with systemd-255 as the issue did *not*
  appear with Focal Fossal (system-245) and only surfaced after the
  upgrade to 24.04.
  
  Work-around:
  
  Amend /etc/rc.local (if this is enabled via systemd) with:
  
- "lsblk | fgrep  | cut -d' '
- -f4 >/sys/power/resume"
+ "lsblk | fgrep $(basename $(df -P $(fgrep swap /etc/fstab | grep '^/' |
+ cut -d' ' -f1) | grep '^/' | cut -d' ' -f1)) | cut -d' ' -f4
+ >/sys/power/resume"
+ 
+ Please let me know if more info is required - more than happy to help!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2061311

Title:
  dev's major/minor not captured in /sys/power/resume

Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate 
complains about
  "Failed to find location to hibernate to: Invalid argument" caused by a "0:0" 
entry in /sys/power/resume

  Current configuration:

  1) Legacy boot configuration (non-UEFI!)

  2) Dual swap space configuration (/etc/fstab excerpt for swap partition and 
file):
  UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 noneswapsw  
0   0
  /swap noneswapsw,pri=2
0   0

  (swap file is the primary and only option for hibernation as partition
  is too small)

  2) resume config in /etc/initramfs-tools/conf.d/resume with the
  correct UUID and offset:

  RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320

  (blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
  BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")

  3) Correct grub config:

  GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320 acpi_enforce_resources=lax"

  Suspect a regression issue with systemd-255 as the issue did *not*
  appear with Focal Fossal (system-245) and only surfaced after the
  upgrade to 24.04.

  Work-around:

  Amend /etc/rc.local (if this is enabled via systemd) with:

  "lsblk | fgrep $(basename $(df -P $(fgrep swap /etc/fstab | grep '^/'
  | cut -d' ' -f1) | grep '^/' | cut -d' ' -f1)) | cut -d' ' -f4
  >/sys/power/resume"

  Please let me know if more info is required - more than happy to help!

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


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


[Touch-packages] [Bug 2061311] Re: dev's major/minor not captured in /sys/power/resume

2024-04-14 Thread monochromec
Swap file is the primary and only option  for hibernation as partition
is too small.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2061311

Title:
  dev's major/minor not captured in /sys/power/resume

Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate 
complains about
  "Failed to find location to hibernate to: Invalid argument" caused by a "0:0" 
entry in /sys/power/resume

  Current configuration:

  1) Legacy boot configuration (non-UEFI!)

  2) Dual swap space configuration (/etc/fstab excerpt for swap partition and 
file):
  UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 noneswapsw  
0   0
  /swap noneswapsw,pri=2
0   0

  2) resume config in /etc/initramfs-tools/conf.d/resume with the
  correct UUID and offset:

  RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320

  (blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
  BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")

  3) Correct grub config:

  GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320 acpi_enforce_resources=lax"

  Suspect a regression issue with systemd-255 as the issue did *not*
  appear with Focal Fossal (system-245) and only surfaced after the
  upgrade to 24.04.

  Work-around:

  Amend /etc/rc.local (if this is enabled via systemd) with:

  "lsblk | fgrep  | cut -d' '
  -f4 >/sys/power/resume"

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


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


[Touch-packages] [Bug 2061311] Re: dev's major/minor not captured in /sys/power/resume

2024-04-14 Thread monochromec
Please let me know if more info is required - more than happy to help!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2061311

Title:
  dev's major/minor not captured in /sys/power/resume

Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate 
complains about
  "Failed to find location to hibernate to: Invalid argument" caused by a "0:0" 
entry in /sys/power/resume

  Current configuration:

  1) Legacy boot configuration (non-UEFI!)

  2) Dual swap space configuration (/etc/fstab excerpt for swap partition and 
file):
  UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 noneswapsw  
0   0
  /swap noneswapsw,pri=2
0   0

  2) resume config in /etc/initramfs-tools/conf.d/resume with the
  correct UUID and offset:

  RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320

  (blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
  BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")

  3) Correct grub config:

  GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320 acpi_enforce_resources=lax"

  Suspect a regression issue with systemd-255 as the issue did *not*
  appear with Focal Fossal (system-245) and only surfaced after the
  upgrade to 24.04.

  Work-around:

  Amend /etc/rc.local (if this is enabled via systemd) with:

  "lsblk | fgrep  | cut -d' '
  -f4 >/sys/power/resume"

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


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


[Touch-packages] [Bug 2061311] [NEW] dev's major/minor not captured in /sys/power/resume

2024-04-14 Thread monochromec
Public bug reported:

When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate 
complains about
"Failed to find location to hibernate to: Invalid argument" caused by a "0:0" 
entry in /sys/power/resume

Current configuration:

1) Legacy boot configuration (non-UEFI!)

2) Dual swap space configuration (/etc/fstab excerpt for swap partition and 
file):
UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 noneswapsw
  0   0
/swap noneswapsw,pri=2  
  0   0

2) resume config in /etc/initramfs-tools/conf.d/resume with the correct
UUID and offset:

RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b resume_offset=39608320

(blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")

3) Correct grub config:

GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
resume_offset=39608320 acpi_enforce_resources=lax"

Suspect a regression issue with systemd-255 as the issue did *not*
appear with Focal Fossal (system-245) and only surfaced after the
upgrade to 24.04.

Work-around:

Amend /etc/rc.local (if this is enabled via systemd) with:

"lsblk | fgrep  | cut -d' '
-f4 >/sys/power/resume"

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2061311

Title:
  dev's major/minor not captured in /sys/power/resume

Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate 
complains about
  "Failed to find location to hibernate to: Invalid argument" caused by a "0:0" 
entry in /sys/power/resume

  Current configuration:

  1) Legacy boot configuration (non-UEFI!)

  2) Dual swap space configuration (/etc/fstab excerpt for swap partition and 
file):
  UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 noneswapsw  
0   0
  /swap noneswapsw,pri=2
0   0

  2) resume config in /etc/initramfs-tools/conf.d/resume with the
  correct UUID and offset:

  RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320

  (blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
  BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")

  3) Correct grub config:

  GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320 acpi_enforce_resources=lax"

  Suspect a regression issue with systemd-255 as the issue did *not*
  appear with Focal Fossal (system-245) and only surfaced after the
  upgrade to 24.04.

  Work-around:

  Amend /etc/rc.local (if this is enabled via systemd) with:

  "lsblk | fgrep  | cut -d' '
  -f4 >/sys/power/resume"

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


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


[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

2016-11-15 Thread monochromec
Hi David,

As this issue is still persisting (and none of the above work-arounds
worked for me): What's the bug # of the new bug you filed a few days
ago?

Thanks for your help!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1464917

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  This bug is resolved.  Do not follow up to this bug.  Shutdown bugs
  are specific to the software installed and its configuration.  If you
  are experiencing a shutdown hang, please file a separate bug report
  and follow the debugging instructions described in the "Debugging
  boot/shutdown problems" section of
  /usr/share/doc/systemd/README.Debian.gz to check if there are any
  hanging jobs at shutdown. Capturing a screen photo of "journalctl -b"
  in the rescue shell might be enlightening.

  [Original report]
  I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth 
shutdown screen.  Hitting esc to reveal the console showed a normal set of 
shutdown messages, ending with 'Reached target Shutdown' (paraphrased from 
memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions

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


[Touch-packages] [Bug 1234252] Re: [MacBookPro8, 1, CS4206] Left speaker low volume and absence of low freqs

2015-01-21 Thread monochromec
Same situation in 14.10.

Is anybody upstream looking at this?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1234252

Title:
  [MacBookPro8,1, CS4206] Left speaker low volume  and absence of low
  freqs

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.04 fresh install or fully updated - no difference.
  While listening music through internal speakers I noticed that left speaker 
sounds differently from the right one. I would describe left speaker's sound as 
those from the headphones lying on the table: low volume level and mostly high 
frequences are heard.
  1) Trying to check mixer levels in alsamixer, muting/unmuting, balance 
channels etc didnt help.
  2) In alsamixer there is a mixer item called Bass Speaker. If I mute it, 
other playback items (including Master) are muted too. If I make its level to 
0, then sound from both speakers become identical: low volume and without bass 
frequences. Level of the Bass Speaker resets if I adjust volume level from 
Unity volume control tool.
  3) Trying to set model parameter for intel_hda module to mbp55 or imac27 
didnt help.
  4) Sound from headphones is perfectly ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vkat   1970 F pulseaudio
   /dev/snd/pcmC0D0c:   vkat   1970 F...m pulseaudio
  Date: Wed Oct  2 19:12:40 2013
  InstallationDate: Installed on 2013-10-02 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: High background noise, or volume is too low
  Title: [MacBookPro8,1, Cirrus Logic CS4206, Speaker, Internal] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B27.1201241646
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:
  dmi.product.name: MacBookPro8,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1234252/+subscriptions

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