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

Bug#922234: marked as done (Stretch stuck after loading initial ramdisk)

Your message dated Tue, 24 Sep 2019 15:28:32 +0100
with message-id <41ed330c07f5ae0a3f3ef377b8c12b9d53453d29.camel@decadent.org.uk>
and subject line Re: possibly solved
has caused the Debian Bug report #922234,
regarding Stretch stuck after loading initial ramdisk
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.)


-- 
922234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922234
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-amd64
Version: 4.9+80+deb9u6

Trying to boot will lead to a hung system after the message "loading
initial ramdisk". Ctrl-Alt-Del will not work. I have to switch off the
machine the hard way.

Workaround I:
This behavior first appeared a while ago (maybe 2-3 months) after an
update (as usual simply with synaptic) and after switching the machine
off and on again the second try was always successful.

Workaround II:
Today the behavior changed and the problem became more severe. Switching
the machine off and on again will no longer solve the problem. Instead I
boot the same kernel into recovery mode. Then I press Ctrl-D to continue
the boot process and everything seems normal.

Environment:
There are 3 operating systems present on my machine. Windows10, Debian
Jessie and Debian Stretch. All started by the bootloader of Stretch.
I use the XFCE Desktop environment.
Kernel: Linux deb9tst 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27)
x86_64 GNU/Linux

An additional remark:
I remember there was quite recently a kernel update which asked me
something about the configuration. I had the options to view the
configurations, change them and so on. I decided to just use the old
configuration file. The problem started short after this.

--- End Message ---
--- Begin Message --- 
On Tue, 2 Apr 2019 17:24:36 +0200 Franz Danzi <franz.danzi@web.de> wrote:
> Hello.
> 
> It seems as if I found a solution for the problem (Stretch stuck after
> loading initial ramdisk).
> 
> Recently I installed two driver packages:
> firmware-misc-nonfree 20161130-4
> nvidia-driver 390.87-8~deb9u1
> 
> Obviously this replaced the nouveau driver which was used before.
> 
> The boot problem did not happen again since then.

Sorry we didn't find a proper solution to this bug.  The nouveau driver
ought to work reliably even if it doesn't provide the same performance
as the proprietary driver.

If you are still interested in tracking down the bug in the nouveau
driver then I can reopen the bug and we can investigate further.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                         - Albert Camus

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


--- End Message ---
Reply to: