Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #219689 > unrolled thread
| Started by | "k. jantzen" <kdjmailing@mailbox.org> |
|---|---|
| First post | 2020-03-01 19:40 +0100 |
| Last post | 2020-03-02 18:50 +0100 |
| Articles | 6 — 3 participants |
Back to article view | Back to linux.debian.user
Buster 10.2 hangs while booting "k. jantzen" <kdjmailing@mailbox.org> - 2020-03-01 19:40 +0100
Re: Buster 10.2 hangs while booting Felix Miata <mrmazda@earthlink.net> - 2020-03-01 19:50 +0100
Re: Buster 10.2 hangs while booting Greg Wooledge <wooledg@eeg.ccf.org> - 2020-03-02 15:10 +0100
Re: Buster 10.2 hangs while booting Felix Miata <mrmazda@earthlink.net> - 2020-03-02 15:50 +0100
Re: Buster 10.2 hangs while booting "k. jantzen" <kdjmailing@mailbox.org> - 2020-03-02 16:40 +0100
Re: Buster 10.2 hangs while booting Felix Miata <mrmazda@earthlink.net> - 2020-03-02 18:50 +0100
| From | "k. jantzen" <kdjmailing@mailbox.org> |
|---|---|
| Date | 2020-03-01 19:40 +0100 |
| Subject | Buster 10.2 hangs while booting |
| Message-ID | <zFBFp-8uj-7@gated-at.bofh.it> |
Hello, I have installed Buster without any problems. When booting however it hangs with the following messages (seen in recovery mode): [...] r8169 0000:03: 00,0 enp3s0: Link is Up - 1Gps/Full - flowcontrol off [...] IPv6: ADDRCONF (NETDEV_CHANGE): enp3s0: link becomes ready Obviously it does not become ready so that the boot process cannot continue. Where do I have a problem? -- K.D.J.
[toc] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2020-03-01 19:50 +0100 |
| Message-ID | <zFBP3-65-1@gated-at.bofh.it> |
| In reply to | #219689 |
k. jantzen composed on 2020-03-01 19:17 (UTC+0100): > I have installed Buster without any problems. > When booting however it hangs with the following messages (seen in > recovery mode): > [...] r8169 0000:03: 00,0 enp3s0: Link is Up - 1Gps/Full - flowcontrol off > [...] IPv6: ADDRCONF (NETDEV_CHANGE): enp3s0: link becomes ready > Obviously it does not become ready so that the boot process cannot continue. > Where do I have a problem? Are you sure a login prompt didn't sneak in out of expected order? That has happened fairly routinely here. I Alt-F2 or Alt-F3 at that point to find a login prompt. On a recovery mode boot immediately subsequent to a normal boot attempt I would try journalctl -b -1 to search for clues. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2020-03-02 15:10 +0100 |
| Message-ID | <zFTVD-3aI-3@gated-at.bofh.it> |
| In reply to | #219690 |
On Sun, Mar 01, 2020 at 01:44:18PM -0500, Felix Miata wrote: > Are you sure a login prompt didn't sneak in out of expected order? That has > happened fairly routinely here. I Alt-F2 or Alt-F3 at that point to find a login > prompt. Or just hit Enter on tty1 to get another login prompt.
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2020-03-02 15:50 +0100 |
| Message-ID | <zFUyl-3qG-9@gated-at.bofh.it> |
| In reply to | #219712 |
Greg Wooledge composed on 2020-03-02 09:07 (UTC-0500): > On Sun, Mar 01, 2020 at 01:44:18PM -0500, Felix Miata wrote: >> Are you sure a login prompt didn't sneak in out of expected order? That has >> happened fairly routinely here. I Alt-F2 or Alt-F3 at that point to find a login >> prompt. > Or just hit Enter on tty1 to get another login prompt. I don't login on tty1, unless I've already committed all others to use and need another. I have noclear set on it, to preserve tail of init messages. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | "k. jantzen" <kdjmailing@mailbox.org> |
|---|---|
| Date | 2020-03-02 16:40 +0100 |
| Message-ID | <zFVkK-3Y9-17@gated-at.bofh.it> |
| In reply to | #219690 |
On 3/1/20 7:44 PM, Felix Miata wrote: > k. jantzen composed on 2020-03-01 19:17 (UTC+0100): > >> I have installed Buster without any problems. >> When booting however it hangs with the following messages (seen in >> recovery mode): > >> [...] r8169 0000:03: 00,0 enp3s0: Link is Up - 1Gps/Full - flowcontrol off >> [...] IPv6: ADDRCONF (NETDEV_CHANGE): enp3s0: link becomes ready > >> Obviously it does not become ready so that the boot process cannot continue. > >> Where do I have a problem? > > Are you sure a login prompt didn't sneak in out of expected order? That has > happened fairly routinely here. I Alt-F2 or Alt-F3 at that point to find a login > prompt. > > On a recovery mode boot immediately subsequent to a normal boot attempt I would try > journalctl -b -1 > > to search for clues. > Thank very much for the quick reply. With Alt-F2/F3 I found a login prompt in tty2 and tty3!! How do I get rid of these logins? With a 'journalctl -b -1' I got "Specifying boot id of boot offset has no effect, no persistent journal was found" K.D.J.
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2020-03-02 18:50 +0100 |
| Message-ID | <zFXmy-5c2-9@gated-at.bofh.it> |
| In reply to | #219716 |
k. jantzen composed on 2020-03-02 16:19 (UTC+0100): > Felix Miata wrote: >> Are you sure a login prompt didn't sneak in out of expected order? That has >> happened fairly routinely here. I Alt-F2 or Alt-F3 at that point to find a login >> prompt. >> On a recovery mode boot immediately subsequent to a normal boot attempt I would try >> journalctl -b -1 >> to search for clues. > Thank very much for the quick reply. > With Alt-F2/F3 I found a login prompt in tty2 and tty3!! > How do I get rid of these logins? They are tools you need not use if you do not wish to. What you probably really want is to find out how to get your X environment working normally. That is one of the things these tools can be, and typically needs be, used for, after enabling persistent journal.... > With a 'journalctl -b -1' I got > "Specifying boot id of boot offset has no effect, no persistent journal > was found" You can turn on persistent journal various ways. The simplest IMO is to create the directory /var/log/journal, then reboot. https://manpages.debian.org/buster/systemd/systemd-journald.service.8.en.html In addition to journal examination, /var/log/Xorg.0.log from an attempt at a normal boot should be done. This may require Xorg.0.log.old from the subsequent rescue boot if that boot went so wrong that it could not be accessed. Pastebinit can be used to share Xorg.0.log, and/or the journal if it is first saved to disk by redirecting journalctl output to a text file. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web