[Kernel-packages] [Bug 49052] Re: no hfs+ journal write support by default (gets mounted as read only)

2020-04-06 Thread James Cuzella 
Still seems to be an issue in modern Ubuntu 18.04.4 bionic LTS.  The
upstream Apple source for HFS+ projects can be found here:

https://opensource.apple.com/source/hfs/
https://opensource.apple.com/source/diskdev_cmds/

Debian package for hfsprogs seems woefully out of date (based on macOS
10.4 diskdev_cmds from ~6 years ago)

Also see Launchpad bug #1507170
https://bugs.launchpad.net/ubuntu/+source/hfsprogs/+bug/1507170

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

Title:
  no hfs+ journal write support by default (gets mounted as read only)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-source-2.6.15 package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: linux-686

  Dapper Drake does not appear to support a HFS+ journaled file system. This 
manifests when I connect my ipod mini, and dmesg warns that:
  'HFS+-fs: write access to a jounaled filesystem is not supported, use the 
force option at your own risk, mounting read-only.'
  Using force appears to work to mount the device read/write. This was not a 
problem under Breezy, which makes me think that it's a kernel compilation issue.

  This occurs while running kernel linux-686 2.6.15.22

  Thanks! :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/49052/+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 1487666] Re: non-fatal error right after login (just upgraded the kernel to 4.1)

2017-11-01 Thread James Cuzella 
** Also affects: linux-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  non-fatal error right after login (just upgraded the kernel to 4.1)

Status in bbswitch package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During kernel install, the log said (see attachment for the complete log): 
  [...]
  Entering directory '/var/lib/dkms/nvidia-340/340.76/build'
  NVIDIA: calling KBUILD...
  make[2]: Entering directory '/usr/src/linux-headers-4.1.0-040100rc2-generic'
  test -e include/generated/autoconf.h -a -e include/config/auto.conf || (  
\
  echo >&2; \
  echo >&2 "  ERROR: Kernel configuration is invalid."; \
  echo >&2 " include/generated/autoconf.h or include/config/auto.conf 
are missing.";\
  echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";\
  [...]

  but following that instruction I get more errors: 
  /usr/src/linux-headers-4.1.0-040100rc2-generic$ sudo make oldconfig && make 
prepare
  [sudo] password for presence: 
  scripts/kconfig/conf  --oldconfig Kconfig
  #
  # configuration written to .config
  #
  arch/x86/Makefile:129: CONFIG_X86_X32 enabled but no binutils support
  Makefile:657: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector 
not supported by compiler
  scripts/kconfig/conf  --silentoldconfig Kconfig

  *** Error during update of the configuration.

  scripts/kconfig/Makefile:37: recipe for target 'silentoldconfig' failed
  make[2]: *** [silentoldconfig] Error 1
  Makefile:541: recipe for target 'silentoldconfig' failed
  make[1]: *** [silentoldconfig] Error 2
  make[1]: *** No rule to make target 'arch/x86/syscalls/syscall_32.tbl', 
needed by 'arch/x86/syscalls/../include/generated/asm/syscalls_32.h'.  Stop.
  arch/x86/Makefile:181: recipe for target 'archheaders' failed
  make: *** [archheaders] Error 2

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: bbswitch-dkms 0.7-2ubuntu1
  Uname: Linux 4.1.0-040100rc2-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  DKMSKernelVersion: 4.1.0-040100rc2-generic
  Date: Fri Aug 21 21:43:25 2015
  InstallationDate: Installed on 2014-05-31 (447 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageVersion: 0.7-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: bbswitch
  Title: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1487666/+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 285392] Re: Softreset failed (device not ready)

2017-11-03 Thread James Cuzella 
Since the bug-watch-updater updated this...  Just want to make it clear
that I was no longer seeing this problem since 16.04.  Since then I've
upgraded multiple times, and even swapped the motherboard and a lot of
hardware out.  Still no recurrence of the problem for me.

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

Title:
  Softreset failed (device not ready)

Status in linux package in Ubuntu:
  Won't Fix
Status in Debian:
  New
Status in linux package in Fedora:
  Fix Released
Status in linux package in Red Flag Midinux:
  Confirmed

Bug description:
  INSTALLATION problem for Hardy and IBEX as well.
  During the install process I got the next messages [during an extremely slow 
installation process]
  Hardy producess similar messages (30 min)
  Ibex stops,

  Let me lists messages when Ibex install stops
  I got the mesages below

  BusyBox V1.10.2 (Ubuntu 1:1.10.2-1 ubuntu6) built-in shell (ash)

  [66.064009] ata7:Softreset failed (device not ready)
  [76.084008] ata8:Softreset failed (device not ready)
  [86.088009] ata8:Softreset failed (device not ready)
  [121.128011] ata8:Softreset failed (device not ready)
  [126.148007] ata8:Softreset failed (device not ready)

  What is the problem rally here with the install DVD? (regardless is it
  Hardy or Intrepid the same messages I got)

  GA-EP45-DQ6 motherboard
  
(http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2831)

  [ The South Bridge: 6 x SATA 3Gb/s connectors (SATAII0, SATAII1, SATAII2, 
SATAII3, SATAII4, SATAII5) supporting up to 6 SATA 3Gb/s devices are connected 
but
  I did not connected any sata cables to 2 x SiI5723 chips : -4 x SATA 3Gb/s 
connectors (GS0-Source, GS1, GS2-Source, GS3) supporting up to 4 SATA 3Gb/s 
devices - Support for Smart Backup (RAID 1) ]

  I suspect that messages comes around the Jmicron & Sis5723 chips. Is it 
driver problem, not providing during the install ?
  See schematic 
http://www.hardwarezone.com/img/data/articles/2008/2559/dq6-sketch.jpg
  Or more info on the motherboard  at 
http://forums.tweaktown.com/f69/ep45-ds5-dq6-27384/

  How to provide driver, if it is so? (There is no Ubuntu driver at 
ftp://driver.jmicron.com.tw/jmb36x/? [there is driver for e.g. fedora but none 
for ubuntu])
  How to continue the installation, skip searching the ATA drivers for not used 
chip, get able to install the Ibex?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285392/+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 810791] Re: Softreset failed (device not ready) with Gigabyte motherboard

2015-09-14 Thread James Cuzella 
Apologies for not responding sooner (I get waaay too many emails and
have filtered automated mailings like the ones sent by launchpad to
Gmail labels which generally never get looked at).

After upgrading to the next LTS release (12.04) I believe I stopped
seeing this bug.  Upgraded since to latest LTS release of 14.04, and
still not having this issue anymore.  Just for the record, I believe
this can be called fixed!

** Changed in: linux (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  Softreset failed (device not ready) with Gigabyte motherboard

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I originally reported this in Bug 285392.   However, I'm not sure that
  this is the same bug, or a different one with the same symptom.

  I am seeing this problem on a Gigabyte GA-MA74GM-S2 motherboard. I
  have tried changing the BIOS setting for both AHCI and IDE modes. I
  get the same error upon boot.

  After a reboot I have been seeing this error randomly all the time.  
Sometimes it seems to work ok, sometimes not.
  I have done 2 dist-upgrades from Lucid (10.04.2 LTS ) to Maverick ( 10.10 ) 
to Natty ( 11.04 ).  This bug has been present in all of these versions of 
Ubuntu.

  Boot messages follow:

  The disk drive for / is not ready yet or not present
  Continue to wait; or Press S to skip mounting or M for manual recovery
  [ 1.740026] ata3: softreset failed (device not ready)
  [ 1.740032] ata6: softreset failed (device not ready)
  [ 1.740058] ata5: softreset failed (device not ready)
  [ 1.740062] ata4: softreset failed (device not ready)

  init: udevtrigger main process (467) terminated with status 1
  init: udevtrigger post-stop process (471) terminated with status 1
  init: udevmonitor main process (466) killed by TERM signal
  udevd[453]: specified group 'camera' unknown

  Ever since Lucid, there are 2 problems with this motherboard that I've
  been having:

  1) It doesn't seem to boot correctly from the first HDD if USB-HDD or CDROM 
are anywhere above in the boot priority list
  2) Every so often I still get the "softreset" and "The disk drive for /home 
is not ready yet or not present" errors (This is random.. it's usually /home, 
/, or whatever other partition happens to complain).

  AHCI vs IDE modes in the BIOS don't change anything. I'm guessing it's
  a Gigabyte motherboard issue, or something to do with the ATI SB7x0
  chipset. So far I haven't tried compiling a new kernel with
  "CONFIG_SATA_PMP=n" yet... but that seems like it might work...

  References:
  https://bugzilla.redhat.com/show_bug.cgi?id=468800
  http://kerneltrap.org/mailarchive/git-commits-head/2008/6/14/2122314
  http://ubuntuforums.org/archive/index.php/t-1052987.html
  http://lime-technology.com/forum/index.php?topic=2642.msg33590#msg33590
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices: aplay: device_list:240: no soundcards found...
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  trinitronx   2433 F pulseaudio
   /dev/snd/controlC0:  trinitronx   2433 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CheckboxSubmission: d6dd0471f36d4aed9362bfdc71eb18b9
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  DistroRelease: Ubuntu 11.04
  HibernationDevice: RESUME=UUID=19b226f0-b1dc-4c53-99c8-c585ffe9d167
  InstallationMedia: Mythbuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA74GM-S2
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   LC_COLLATE=en_US.utf8
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=fcd55128-66e2-41ad-ab3a-606c165b2102 ro quiet splash noacpi noapm 
vt.handoff=7
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-8-generic N/A
   linux-backports-modules-2.6.38-8-generic  N/A
   linux-firmware1.52
  RfKill:
   
  Tags:  natty running-unity
  Uname: Linux 2.6.38-8-generic x86_64
  UpgradeStatus: Upgraded to natty on 2011-06-30 (19 days ago)
  UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video
  WifiSyslog:
   Jul 19 12:52:53 saturn kernel: [260899.520036] TCP: Peer 
77.114.168.45:54569/49317 unexpectedly shrunk window 1213338602:1213342756 
(repaired)
   Jul 19 12:54:01 saturn kernel: [260967.520038] TCP: Peer 
77.114.168.45:54569/49317 unexpectedly shrunk window 1213338602:1213342756 
(repaired)
   Jul 19 12:56:02 saturn kernel: [261087.840039] T

[Kernel-packages] [Bug 759725] Re: The kernel is no longer readable by non-root users

2022-01-20 Thread James Cuzella 
The "statoverride" script appears to work on the first run for each
kernel.  However, any subsequent times the `dpkg-statoverride` command
exits with errorcode 2:

$ apt-get install something-triggering-dkms

Processing triggers for linux-image-5.4.0-96-generic (5.4.0-96.109) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.0-96-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-96-generic
/etc/kernel/postinst.d/statoverride:
dpkg-statoverride: error: an override for '/boot/vmlinuz-5.4.0-96-generic' 
already exists; aborting
run-parts: /etc/kernel/postinst.d/statoverride exited with return code 2
dpkg: error processing package linux-image-5.4.0-96-generic (--configure):
 installed linux-image-5.4.0-96-generic package post-installation script 
subprocess returned error exit status 1
Errors were encountered while processing:
 linux-image-5.4.0-96-generic

E: Sub-process /usr/bin/dpkg returned an error code (1)

Adding the `--force-statoverride-add` flag fixed the issue:

#!/bin/sh

# https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725

set -e
version="$1"
if [ -z "$version" ]; then
exit 0
fi
exec dpkg-statoverride --force-statoverride-add --update --add root root 
0644 "/boot/vmlinuz-${version}"


After that change, now the kernel dkms trigger succeeds:

Setting up linux-image-5.4.0-96-generic (5.4.0-96.109) ...
Processing triggers for linux-image-5.4.0-96-generic (5.4.0-96.109) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.0-96-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-96-generic
/etc/kernel/postinst.d/statoverride:
dpkg-statoverride: warning: an override for 
'/boot/vmlinuz-5.4.0-96-generic' already exists, but --force specified so will 
be ignored
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-96-generic
Found initrd image: /boot/initrd.img-5.4.0-96-generic
Found linux image: /boot/vmlinuz-5.4.0-94-generic
Found initrd image: /boot/initrd.img-5.4.0-94-generic
Found linux image: /boot/vmlinuz-5.4.0-91-generic
Found initrd image: /boot/initrd.img-5.4.0-91-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Ubuntu 20.04.3 LTS (20.04) on /dev/md126p1
done

If this is to be added as a postinst.d to the libguestfs-tools package,
please don't forget the `--force-statoverride-add` flag... or else we
introduce a new dkms / kernel postinst.d trigger idempotency bug.

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

Title:
  The kernel is no longer readable by non-root users

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  The mode of the latest kernel has changed so it is no longer readable
  by non-root users:

  -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 
/boot/vmlinuz-2.6.35-22-generic
  -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 
/boot/vmlinuz-2.6.35-23-generic
  -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic
  -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic

  This prevents people from using this kernel to boot qemu
  virtual machines as non-root.

  Please change the mode back to make the kernel readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: aplay: device_list:240: no soundcards found...
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  CRDA: Error: [Errno 2] No such file or directory
  Date: Wed Apr 13 13:05:01 2011
  HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash
  RelatedPackageVersions:
   linux-restricted-

[Kernel-packages] [Bug 1535840] Re: systemd ignoring /etc/modules due to blacklist

2023-05-19 Thread James Cuzella 
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  systemd ignoring /etc/modules due to blacklist

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Opinion

Bug description:
  I tried the daily build of 16.04 32-bit to test out the watchdog
  daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
  /etc/modules so it is loaded at boot-time, as watchdog timer modules
  are not normally auto-loaded due to the risk of an unexpected reboot.

  However I now find that systemd is choosing to ignore my command to
  load the module in /etc/modules since it appears in the watchdog
  blacklist. Typical syslog entries look like this:

  Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is 
blacklisted
  Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is 
blacklisted

  This is just dumb! I have explicitly told the system to load the
  module, an action that works perfectly well using modprobe or by
  adding it to the start script for the watchdog, and yet systemd
  chooses to override that because of the blacklist for auto-loaded
  modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf).

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy systemd
  systemd:
Installed: 228-4ubuntu1
Candidate: 228-4ubuntu1
Version table:
   *** 228-4ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  What I expect to happen is modules added to /etc/modules are loaded at
  boot time, and not subject to the blacklist for hardware detect /
  automatic loading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535840/+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