Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #181072 > unrolled thread

stretch not booting

Back to article view | Back to linux.debian.user

Contents

  stretch not booting Luis Finotti <luis.finotti@gmail.com> - 2017-05-17 19:50 +0200
    Re: stretch not booting Brian <ad44@cityscape.co.uk> - 2017-05-17 20:10 +0200
      Re: stretch not booting Luis Finotti <luis.finotti@gmail.com> - 2017-05-17 20:30 +0200
        Re: stretch not booting didier gaumet <didier.gaumet@gmail.com> - 2017-05-17 20:50 +0200
          Re: stretch not booting bw <apisonco@gmail.com> - 2017-05-18 02:50 +0200
            Re: stretch not booting didier gaumet <didier.gaumet@gmail.com> - 2017-07-10 10:20 +0200
        Re: stretch not booting Brian <ad44@cityscape.co.uk> - 2017-05-17 20:50 +0200
          Re: stretch not booting Luis Finotti <luis.finotti@gmail.com> - 2017-05-17 21:10 +0200
            Re: stretch not booting Brian <ad44@cityscape.co.uk> - 2017-05-18 00:20 +0200
              Re: stretch not booting Luis Finotti <luis.finotti@gmail.com> - 2017-05-18 01:10 +0200
                Re: stretch not booting Brian <ad44@cityscape.co.uk> - 2017-05-18 12:50 +0200
                  Re: stretch not booting Luis Finotti <luis.finotti@gmail.com> - 2017-05-19 18:30 +0200
                    Re: stretch not booting Luis Finotti <luis.finotti@gmail.com> - 2017-05-19 19:10 +0200

#181072 — stretch not booting

[Multipart message — attachments visible in raw view] — view raw

Dear all,

I've installed stretch from a DI RC3 image (from here:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/)
a couple of weeks back on an old Dell Inspiron Mini 1018.

The install went without a problem and I could reboot just fine.  I then
updated it, installed LXDE and a few more packages, but after that I cannot
reboot.  Even in recovery mode it gets stuck.  It seems that the point at
which it gets stuck varies, but it never finishes booting.

Since I don't get a prompt, I don't know how to get more info.  Since I
could reboot, I don't think it was an installation problem.

Any suggestions?

Thanks,

Luis

[toc] | [next] | [standalone]

#181074

On Wed 17 May 2017 at 13:41:03 -0400, Luis Finotti wrote:

> I've installed stretch from a DI RC3 image (from here:
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/)
> a couple of weeks back on an old Dell Inspiron Mini 1018.

Is this the only OS on the machine?

> The install went without a problem and I could reboot just fine.  I then
> updated it, installed LXDE and a few more packages, but after that I cannot
> reboot.  Even in recovery mode it gets stuck.  It seems that the point at
> which it gets stuck varies, but it never finishes booting.

Installing extra packages (if that is all you ever did) should not lead
to non-booting. 

> Since I don't get a prompt, I don't know how to get more info.  Since I
> could reboot, I don't think it was an installation problem.

You obviously get the GRUB menu. When it appears hit the "c" key and type

 set pager=1
 set

What is do "prefix=" and "root=" say?

Press the Esc key and hit the "e" key when the OS to be booted is
highlighted.

What does "set root=" say?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#181076

[Multipart message — attachments visible in raw view] — view raw

Thanks for the reply!

On Wed, May 17, 2017 at 2:03 PM, Brian <ad44@cityscape.co.uk> wrote:

> On Wed 17 May 2017 at 13:41:03 -0400, Luis Finotti wrote:
>
> > I've installed stretch from a DI RC3 image (from here:
> > https://cdimage.debian.org/cdimage/unofficial/non-free/
> cd-including-firmware/)
> > a couple of weeks back on an old Dell Inspiron Mini 1018.
>
> Is this the only OS on the machine?
>

Yes.


> > The install went without a problem and I could reboot just fine.  I then
> > updated it, installed LXDE and a few more packages, but after that I
> cannot
> > reboot.  Even in recovery mode it gets stuck.  It seems that the point at
> > which it gets stuck varies, but it never finishes booting.
>
> Installing extra packages (if that is all you ever did) should not lead
> to non-booting.
>
>
Indeed.  I think I did do a "dist-upgrade", which could be the cause.


> > Since I don't get a prompt, I don't know how to get more info.  Since I
> > could reboot, I don't think it was an installation problem.
>
> You obviously get the GRUB menu. When it appears hit the "c" key and type
>
>  set pager=1
>  set
>
> What is do "prefix=" and "root=" say?
>

prefix=(hd0,msdos1)/boot/grub
root=hd0,msdos1


>
> Press the Esc key and hit the "e" key when the OS to be booted is
> highlighted.
>
> What does "set root=" say?
>
>
Selecting the safe-mode:

set root='hd0,msdos1'

Let me know if I can provide anymore info or if this gives you any idea of
what is wrong...

Best,

Luis

[toc] | [prev] | [next] | [standalone]

#181078

I had exactly the same problem recently with almost the same laptop:
Dell Inspiron Mini 1012 that I had previously given to a friend. I
switched it back to Jessie.

[toc] | [prev] | [next] | [standalone]

#181084

>I had exactly the same problem recently with almost the same laptop:
>Dell Inspiron Mini 1012 that I had previously given to a friend. I
>switched it back to Jessie.

I can confirm this on Dell Mini 1012, installation is successful, first boot is okay.  After reboot all boots fail at various places.
I have tried minimal install (no X) from RC2 with same behavior.  

I have not tried installing sysV and removing systemd after first boot, just sticking with jessie for now.

[toc] | [prev] | [next] | [standalone]

#183494

Le 18/05/2017 à 02:30, bw a écrit :
>> I had exactly the same problem recently with almost the same laptop:
>> Dell Inspiron Mini 1012 that I had previously given to a friend. I
>> switched it back to Jessie.
> 
> I can confirm this on Dell Mini 1012, installation is successful, first boot is okay.  After reboot all boots fail at various places.
> I have tried minimal install (no X) from RC2 with same behavior.  
> 
> I have not tried installing sysV and removing systemd after first boot, just sticking with jessie for now.

Thanks to him, a guy (kozaki) has done thorough research (see 1&2) to
solve this problem. It is caused by a failed attempt to restore the LCD
backlight at boot. Passing 'systemd.restore_state=0' kernel parameter at
boot is a solution.

1) https://bugs.archlinux.org/task/47509
2) https://bbs.archlinux.org/viewtopic.php?id=201523&p=2

[toc] | [prev] | [next] | [standalone]

#181079

On Wed 17 May 2017 at 14:22:47 -0400, Luis Finotti wrote:

> Thanks for the reply!

No problem. There are GRUB experts on this list who are keeping an eye
on this thread, I hope.

> On Wed, May 17, 2017 at 2:03 PM, Brian <ad44@cityscape.co.uk> wrote:
> 
> > On Wed 17 May 2017 at 13:41:03 -0400, Luis Finotti wrote:
> >
> > > I've installed stretch from a DI RC3 image (from here:
> > > https://cdimage.debian.org/cdimage/unofficial/non-free/
> > cd-including-firmware/)
> > > a couple of weeks back on an old Dell Inspiron Mini 1018.
> >
> > Is this the only OS on the machine?
> 
> Yes.
> 
> > > The install went without a problem and I could reboot just fine.  I then
> > > updated it, installed LXDE and a few more packages, but after that I
> > cannot
> > > reboot.  Even in recovery mode it gets stuck.  It seems that the point at
> > > which it gets stuck varies, but it never finishes booting.
> >
> > Installing extra packages (if that is all you ever did) should not lead
> > to non-booting.
> >
> >
> Indeed.  I think I did do a "dist-upgrade", which could be the cause.

Could be. We will put that on one side because we might never know.

> > > Since I don't get a prompt, I don't know how to get more info.  Since I
> > > could reboot, I don't think it was an installation problem.
> >
> > You obviously get the GRUB menu. When it appears hit the "c" key and type
> >
> >  set pager=1
> >  set
> >
> > What is do "prefix=" and "root=" say?
> >
> 
> prefix=(hd0,msdos1)/boot/grub
> root=hd0,msdos1

Thanks.

> > Press the Esc key and hit the "e" key when the OS to be booted is
> > highlighted.
> >
> > What does "set root=" say?
> >
> >
> Selecting the safe-mode:
>
> set root='hd0,msdos1'
> 
> Let me know if I can provide anymore info or if this gives you any idea of
> what is wrong...

At the GRUB menu hit "c" and type

 set root=(hd0,msdos1)
 linux /vmlinuz root=/dev/sda1
 initrd /initrd.img
 boot

and hit the ENTER key.

Do you boot into the OS?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#181080

[Multipart message — attachments visible in raw view] — view raw

> Let me know if I can provide anymore info or if this gives you any idea of

> > what is wrong...
>
> At the GRUB menu hit "c" and type
>
>  set root=(hd0,msdos1)
>  linux /vmlinuz root=/dev/sda1
>  initrd /initrd.img
>  boot
>
> and hit the ENTER key.
>
> Do you boot into the OS?


No.  I get stuck again.

Something weird just happened, though.  I decided to try to disconnect the
ethernet cable.  I started the computer and got to grub, but the keyboard
was not working, so I could not select recovery-mode.  But the system
booted fine in graphical mode (with keyboard and touchpad not working)!  I
forced a reboot (still with ethernet disconnected), grub came up and the
keyboard was working, but now it got stuck again.  I tried in graphical and
recovery modes, both get stuck.

I am not sure if it is relevant at all, but the touchpad did not work
during the installation, but it did work after I installed LXDE.

Thanks again for your help!

[toc] | [prev] | [next] | [standalone]

#181082

On Wed 17 May 2017 at 15:07:54 -0400, Luis Finotti wrote:

> > Let me know if I can provide anymore info or if this gives you any idea of
> 
> > > what is wrong...
> >
> > At the GRUB menu hit "c" and type
> >
> >  set root=(hd0,msdos1)
> >  linux /vmlinuz root=/dev/sda1
> >  initrd /initrd.img
> >  boot
> >
> > and hit the ENTER key.
> >
> > Do you boot into the OS?
> 
> 
> No.  I get stuck again.

You were able to type these commands? What do you mean by "stuck"? After
pressing ENTER do you get anything on the screen? What do you see?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#181083

[Multipart message — attachments visible in raw view] — view raw

> No.  I get stuck again.

>
> You were able to type these commands? What do you mean by "stuck"? After
> pressing ENTER do you get anything on the screen? What do you see?


Yes, I am able to type those and boot starts, but gets stuck in the
middle.  No HD activity and Ctrl+Alt+Del (or any other command) does
nothing.

It starts well.  I see no errors (all green "OK"), the video changes the
dpi (modesetting?).  It stops a different places, seemingly at random.  I
has stopped after setting the swap partition, after changing the name from
wlan0, after adjusting display brightness.  (Those are the last messages
seen before it freezes, but they all seem to have been successfully.)  And
I've seen it pass all of those at times.  (The order in which they happen
doesn't seem to always be the same.)

All In can do is a hard reboot (holding the power button).

[toc] | [prev] | [next] | [standalone]

#181090

On Wed 17 May 2017 at 19:01:20 -0400, Luis Finotti wrote:

> > No.  I get stuck again.
> 
> > You were able to type these commands? What do you mean by "stuck"? After
> > pressing ENTER do you get anything on the screen? What do you see?
> 
> 
> Yes, I am able to type those and boot starts, but gets stuck in the
> middle.  No HD activity and Ctrl+Alt+Del (or any other command) does
> nothing.
> 
> It starts well.  I see no errors (all green "OK"), the video changes the
> dpi (modesetting?).  It stops a different places, seemingly at random.  I
> has stopped after setting the swap partition, after changing the name from
> wlan0, after adjusting display brightness.  (Those are the last messages
> seen before it freezes, but they all seem to have been successfully.)  And
> I've seen it pass all of those at times.  (The order in which they happen
> doesn't seem to always be the same.)
> 
> All In can do is a hard reboot (holding the power button).

GRUB does its job but it appears the problem occurs when control is
handed over to the init system.

At the GRUB menu edit the linux line to add systemd.unit=rescue.target
or systemd.unit=emergency.target.

 https://freedesktop.org/wiki/Software/systemd/Debugging/

You might get to a terminal to look at what the journalctl command and
/var/log/syslog reveal.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#181121

[Multipart message — attachments visible in raw view] — view raw

Thanks for your continued help!

On Thu, May 18, 2017 at 6:46 AM, Brian <ad44@cityscape.co.uk> wrote:

>
> GRUB does its job but it appears the problem occurs when control is
> handed over to the init system.
>
> At the GRUB menu edit the linux line to add systemd.unit=rescue.target
> or systemd.unit=emergency.target.
>
>
systemd.unit=rescue.target gets stuck (just as before).

systemd.unit=emergency.target boots!  I can log in as root, but journalctl
-xb gives nothing.  (And I don't know what else I can do then.  The system
is read-only...)


>  https://freedesktop.org/wiki/Software/systemd/Debugging/
>
> You might get to a terminal to look at what the journalctl command and
> /var/log/syslog reveal.
>

I tried a few of the grub commands in there, such as

  systemd.log_level=debug systemd.log_target=console console=ttyS0,38400

and

  systemd.journald.forward_to_console=1 console=ttyS0,38400

but no new messages seem to go to the boot screen.

I also tried

  systemd.debug-shell=1

but either tty9 looks exactly the same as the one from boot, or it is not
switching.

Any suggestions would be appreciated...

[toc] | [prev] | [next] | [standalone]

#181122

[Multipart message — attachments visible in raw view] — view raw

On Fri, May 19, 2017 at 12:29 PM, Luis Finotti <luis.finotti@gmail.com>
wrote:

[snip]


> Any suggestions would be appreciated...
>
>
>
Never mind.  The screen just went red and opening up to check the video
cable I just broke the trackpad (which was secured only by tape).  (And it
did not fix the screen.)

I will just forget about it.

Thanks for all the help, though!

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web