[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#777243: marked as done (Boot fails due to missing ext4 module)



Your message dated Thu, 10 Dec 2015 03:47:37 +0000
with message-id <1449719257.2824.224.camel@decadent.org.uk>
and subject line Re: Boot fails due to missing ext4 module
has caused the Debian Bug report #777243,
regarding Boot fails due to missing ext4 module
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
777243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777243
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kernel-package
Version: 13.014+nmu1
Severity: grave
Tags: newcomer
Justification: renders package unusable

I've upgraded my LG notebook (X-note: LS50a) from wheezy to jessie and:
1. the upgrade have installed kernel "version-i585" in addition to my earlier
(automatically installed during an upgrade to wheezy) "version-i486".
2. when booting "i486", it fails to modprobe "ext4-fs" during the boot. It
breaks boot sequence, but manual (from shell prompt) modprobe ext4 does not
load the module into the kernel.
3. when booting "i586", it fails to load kernel module responsible for notebook
keyboard (touchpad is loaded OK). USB keyboard works fine.
4. DRM:i9xx fails to configure with "*ERROR* pipe A underrun"



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-586
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages kernel-package depends on:
ii  bc               1.06.95-9
ii  binutils         2.24.90.20141023-1
ii  build-essential  11.7
ii  bzip2            1.0.6-7+b2
ii  dpkg-dev         1.17.23
ii  file             1:5.20-2
ii  gettext          0.19.3-2
ii  kmod             18-3
ii  lzma             9.22-2
ii  po-debconf       1.0.16+nmu3
ii  xmlto            0.0.25-2
ii  xz-utils [lzma]  5.1.1alpha+20120614-2+b3

Versions of packages kernel-package recommends:
ii  cpio           2.11+dfsg-4
ii  docbook-utils  0.6.14-3
ii  kernel-common  13.014+nmu1
pn  uboot-mkimage  <none>

Versions of packages kernel-package suggests:
ii  libncurses5-dev [libncurses-dev]  5.9+20140913-1+b1
pn  linux-source                      <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Sorry, I'm out of ideas here.  We already established that the bug
appears some time after the real init system is running, so it's not a
bug in initramfs-tools, but it's not clear what *is* at fault.

If the problem has not somehow been solved already, you should use one
of the support mailing lists or web site to get help:
<https://www.debian.org/support>.

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply to: