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

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

Update Debian 9 to 10

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

Contents

  Update Debian 9 to 10 Thanos Katsiolis <kls.thanos@gmail.com> - 2021-12-09 15:50 +0100
    Re: Update Debian 9 to 10 David Wright <deblis@lionunicorn.co.uk> - 2021-12-09 16:40 +0100
      Re: Update Debian 9 to 10 Thanos Katsiolis <kls.thanos@gmail.com> - 2021-12-09 18:30 +0100
        Re: Update Debian 9 to 10 David Wright <deblis@lionunicorn.co.uk> - 2021-12-09 20:20 +0100
          Re: Update Debian 9 to 10 Greg Wooledge <greg@wooledge.org> - 2021-12-09 21:30 +0100
          Re: Update Debian 9 to 10 Andrei POPESCU <andreimpopescu@gmail.com> - 2021-12-10 11:30 +0100
            Re: Update Debian 9 to 10 Thanos Katsiolis <kls.thanos@gmail.com> - 2021-12-10 17:30 +0100
              Re: Update Debian 9 to 10 "Andrew M.A. Cater" <amacater@einval.com> - 2021-12-10 18:20 +0100
                Re: Update Debian 9 to 10 Thanos Katsiolis <kls.thanos@gmail.com> - 2021-12-10 19:00 +0100
              Re: Update Debian 9 to 10 Andrei POPESCU <andreimpopescu@gmail.com> - 2021-12-10 18:20 +0100
                Re: Update Debian 9 to 10 Andrei POPESCU <andreimpopescu@gmail.com> - 2021-12-11 10:40 +0100
                  Re: Update Debian 9 to 10 Thanos Katsiolis <kls.thanos@gmail.com> - 2021-12-13 11:10 +0100
              Re: Update Debian 9 to 10 piorunz <piorunz@gmx.com> - 2021-12-10 20:00 +0100
                Re: Update Debian 9 to 10 Thanos Katsiolis <kls.thanos@gmail.com> - 2021-12-13 11:10 +0100
                  Re: Update Debian 9 to 10 Greg Wooledge <greg@wooledge.org> - 2021-12-13 13:40 +0100
    Re: Update Debian 9 to 10 Andrei POPESCU <andreimpopescu@gmail.com> - 2021-12-10 11:30 +0100
    Re: Update Debian 9 to 10 Thanos Katsiolis <kls.thanos@gmail.com> - 2021-12-10 19:50 +0100
    Re: Update Debian 9 to 10 Thanos Katsiolis <kls.thanos@gmail.com> - 2021-12-13 17:20 +0100
      Re: Update Debian 9 to 10 Kent West <westk@acu.edu> - 2021-12-13 20:00 +0100
        Re: Update Debian 9 to 10 Thanos Katsiolis <kls.thanos@gmail.com> - 2021-12-14 14:20 +0100
          Re: Update Debian 9 to 10 Andrei POPESCU <andreimpopescu@gmail.com> - 2021-12-15 21:40 +0100

Page 1 of 2  [1] 2  Next page →

#242804 — Update Debian 9 to 10

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

Hello,

I followed the Release notes
<https://www.debian.org/releases/buster/amd64/release-notes.en.pdf> for
Debian 10, in order to update from Debian 9 to Debian 10. After running

apt-get upgrade

I ran

apt full-upgrade

to complete the update to Debian 10. While the command was running on
terminal, it switched to black background and displayed

/dev/sda5: clean, xxxxxxx/xxxxxx files, xxxxxxx/xxxxxx blocks
[     xxxxxx] kvm: disabled by bios
[     xxxxxx] kvm: disabled by bios
[     xxxxxx] kvm: disabled by bios
[     xxxxxx] kvm: disabled by bios
[ OK ] Started Daily apt upgrade and clean activities.

with a blinking underscore, and the upgrade is interrupted. What is this
about, and how can I proceed?

[toc] | [next] | [standalone]

#242808

On Thu 09 Dec 2021 at 16:39:52 (+0200), Thanos Katsiolis wrote:

> I followed the Release notes
> <https://www.debian.org/releases/buster/amd64/release-notes.en.pdf> for
> Debian 10, in order to update from Debian 9 to Debian 10. After running
> 
> apt-get upgrade
> 
> I ran
> 
> apt full-upgrade
> 
> to complete the update to Debian 10. While the command was running on
> terminal, it switched to black background and displayed
> 
> /dev/sda5: clean, xxxxxxx/xxxxxx files, xxxxxxx/xxxxxx blocks
> [     xxxxxx] kvm: disabled by bios
> [     xxxxxx] kvm: disabled by bios
> [     xxxxxx] kvm: disabled by bios
> [     xxxxxx] kvm: disabled by bios
> [ OK ] Started Daily apt upgrade and clean activities.
> 
> with a blinking underscore, and the upgrade is interrupted. What is this
> about, and how can I proceed?

That sounds as if you might have been in X while upgrading, and
dropped out into a console that was displaying the original startup
messages (which look very much like my own). See §4.1.5.

If you can't find a shell prompt (eg, try Ctrl-Alt-F2 etc for possible
VCs) so you can carry on, it may be necessary to close down as
gracefully as you are able to, and then login as root to a textual VC
to carry on with the upgrade.  APT is pretty clever and picking up
where it left off, though you might benefit from running commands
such as:

  # apt-get -f install
  # dpkg --configure --pending

if things have got somewhat wedged. (See §4.5.3 and the sections
around there.)

Cheers,
David.

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

#242825

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

Thank you David for your fast response,

Indeed, in order to update I opened the terminal and started the procedure
described in Release notes (terminal  was the only running program).
It is the first time I update a Linux system and from your answer I
understand that this is done differently.

Ctrl-Alt-F2 moves me to the graphical interface to login, although
something like a constant refresh doesn't let me insert the root password.
Pressing Ctrl-Alt-F1, I return to the same message with the black
background that I described in my OP.
Ctrl-Alt-F3 opens the tty3 and prompts for login (this must be the "textual
VC" you mentioned in your answer).

Which is the best option to proceed and how can I continue? The message
does not indicate a problem (at least I didn't recognize it).

Thanks again,
- Thanos.

On Thu, Dec 9, 2021 at 5:37 PM David Wright <deblis@lionunicorn.co.uk>
wrote:

> On Thu 09 Dec 2021 at 16:39:52 (+0200), Thanos Katsiolis wrote:
>
> > I followed the Release notes
> > <https://www.debian.org/releases/buster/amd64/release-notes.en.pdf> for
> > Debian 10, in order to update from Debian 9 to Debian 10. After running
> >
> > apt-get upgrade
> >
> > I ran
> >
> > apt full-upgrade
> >
> > to complete the update to Debian 10. While the command was running on
> > terminal, it switched to black background and displayed
> >
> > /dev/sda5: clean, xxxxxxx/xxxxxx files, xxxxxxx/xxxxxx blocks
> > [     xxxxxx] kvm: disabled by bios
> > [     xxxxxx] kvm: disabled by bios
> > [     xxxxxx] kvm: disabled by bios
> > [     xxxxxx] kvm: disabled by bios
> > [ OK ] Started Daily apt upgrade and clean activities.
> >
> > with a blinking underscore, and the upgrade is interrupted. What is this
> > about, and how can I proceed?
>
> That sounds as if you might have been in X while upgrading, and
> dropped out into a console that was displaying the original startup
> messages (which look very much like my own). See §4.1.5.
>
> If you can't find a shell prompt (eg, try Ctrl-Alt-F2 etc for possible
> VCs) so you can carry on, it may be necessary to close down as
> gracefully as you are able to, and then login as root to a textual VC
> to carry on with the upgrade.  APT is pretty clever and picking up
> where it left off, though you might benefit from running commands
> such as:
>
>   # apt-get -f install
>   # dpkg --configure --pending
>
> if things have got somewhat wedged. (See §4.5.3 and the sections
> around there.)
>
> Cheers,
> David.
>
>

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

#242840

On Thu 09 Dec 2021 at 19:22:17 (+0200), Thanos Katsiolis wrote:

> Indeed, in order to update I opened the terminal and started the procedure
> described in Release notes (terminal  was the only running program).
> It is the first time I update a Linux system and from your answer I
> understand that this is done differently.

Actually, the paragraph I referred to in §4.1.5, but did not quote,
is missing from buster (but was in stretch):

 "4.1.5 Prepare a safe environment for the upgrade

 "The distribution upgrade should be done either locally from a
  textmode virtual console (or a directly connected serial terminal),
  or remotely via an ssh link."

I don't use a DM of DE, so I just don't start X. I don't know the
correct way for DEs etc.

> Ctrl-Alt-F2 moves me to the graphical interface to login, although
> something like a constant refresh doesn't let me insert the root password.
> Pressing Ctrl-Alt-F1, I return to the same message with the black
> background that I described in my OP.
> Ctrl-Alt-F3 opens the tty3 and prompts for login (this must be the "textual
> VC" you mentioned in your answer).
> 
> Which is the best option to proceed and how can I continue? The message
> does not indicate a problem (at least I didn't recognize it).

I would check the Release Notes for any relevant advice you might have
missed, like uninstalling 3rd party packages (if practical) and so on.
Then you could login as root, and try carrying on with the update and
upgrade commands that you used previously. You'll quickly find out
whether there's a problem with the previous commands, say, holding a
lockfile. If so, my understanding is that killing them (ps ax
to discover their PIDs) should then make the locks appear stale
as far as your new commands are concerned. It's tricky to be precise
and hold your hand as I've never put myself in this situation.

BTW I see people advising   dpkg --audit   to list broken packages,
so that's another command to try in addition to the two already
given (quoted below). No output is good.

> On Thu, Dec 9, 2021 at 5:37 PM David Wright wrote:
> > On Thu 09 Dec 2021 at 16:39:52 (+0200), Thanos Katsiolis wrote:
> >
> > > I followed the Release notes
> > > <https://www.debian.org/releases/buster/amd64/release-notes.en.pdf> for
> > > Debian 10, in order to update from Debian 9 to Debian 10. After running
> > >
> > > apt-get upgrade
> > >
> > > I ran
> > >
> > > apt full-upgrade
> > >
> > > to complete the update to Debian 10. While the command was running on
> > > terminal, it switched to black background and displayed
> > >
> > > /dev/sda5: clean, xxxxxxx/xxxxxx files, xxxxxxx/xxxxxx blocks
> > > [     xxxxxx] kvm: disabled by bios
> > > [     xxxxxx] kvm: disabled by bios
> > > [     xxxxxx] kvm: disabled by bios
> > > [     xxxxxx] kvm: disabled by bios
> > > [ OK ] Started Daily apt upgrade and clean activities.
> > >
> > > with a blinking underscore, and the upgrade is interrupted. What is this
> > > about, and how can I proceed?
> >
> > That sounds as if you might have been in X while upgrading, and
> > dropped out into a console that was displaying the original startup
> > messages (which look very much like my own). See §4.1.5.
> >
> > If you can't find a shell prompt (eg, try Ctrl-Alt-F2 etc for possible
> > VCs) so you can carry on, it may be necessary to close down as
> > gracefully as you are able to, and then login as root to a textual VC
> > to carry on with the upgrade.  APT is pretty clever and picking up
> > where it left off, though you might benefit from running commands
> > such as:
> >
> >   # apt-get -f install
> >   # dpkg --configure --pending
> >
> > if things have got somewhat wedged. (See §4.5.3 and the sections
> > around there.)

Cheers,
David.

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

#242841

On Thu, Dec 09, 2021 at 01:12:15PM -0600, David Wright wrote:
> Actually, the paragraph I referred to in §4.1.5, but did not quote,
> is missing from buster (but was in stretch):
> 
>  "4.1.5 Prepare a safe environment for the upgrade
> 
>  "The distribution upgrade should be done either locally from a
>   textmode virtual console (or a directly connected serial terminal),
>   or remotely via an ssh link."
> 
> I don't use a DM of DE, so I just don't start X. I don't know the
> correct way for DEs etc.

Log out of the desktop environment.  Then press Ctrl-Alt-F2 (or something
similar) to get to a virtual console, and do the upgrade there.

Stopping the Display Manager shouldn't be necessary.  The reboot will
take care of restarting it anyway.

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

#242885

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

On Jo, 09 dec 21, 13:12:15, David Wright wrote:
> On Thu 09 Dec 2021 at 19:22:17 (+0200), Thanos Katsiolis wrote:
> 
> > Indeed, in order to update I opened the terminal and started the procedure
> > described in Release notes (terminal  was the only running program).
> > It is the first time I update a Linux system and from your answer I
> > understand that this is done differently.
> 
> Actually, the paragraph I referred to in §4.1.5, but did not quote,
> is missing from buster (but was in stretch):
> 
>  "4.1.5 Prepare a safe environment for the upgrade
> 
>  "The distribution upgrade should be done either locally from a
>   textmode virtual console (or a directly connected serial terminal),
>   or remotely via an ssh link."

As far as I recall it was removed because upgrades have gotten reliable 
enough to run from within X. Obviously not 100% though...

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#242918

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

Thank you both for your replies.

I managed to complete the installation (run also apt full-upgrade
successfully) and then reboot.
After the update the system boots only with the ttys (1-6) and not with a
graphical interface, and by that I mean that I tried to change to the
graphical interface with Ctrl-Alt-F7 and Ctrl-Alt-F8.
I verified that Debian 10.10 was installed , ran cleaning commands, reboot
again but again I can only access ttys and not the Graphical Interface.

Is there any possibility that a graphical environment has not been
installed at all?

All the update procedures that I have seen, do not have extra steps. What
am I missing?

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

#242919

On Fri, Dec 10, 2021 at 06:24:19PM +0200, Thanos Katsiolis wrote:
> Thank you both for your replies.
> 
> I managed to complete the installation (run also apt full-upgrade
> successfully) and then reboot.
> After the update the system boots only with the ttys (1-6) and not with a
> graphical interface, and by that I mean that I tried to change to the
> graphical interface with Ctrl-Alt-F7 and Ctrl-Alt-F8.
> I verified that Debian 10.10 was installed , ran cleaning commands, reboot
> again but again I can only access ttys and not the Graphical Interface.
> 
> Is there any possibility that a graphical environment has not been
> installed at all?
> 
> All the update procedures that I have seen, do not have extra steps. What
> am I missing?

Can you tell us your video hardware?

Is there any firmware needed somewhere along the line?

Having safely updated to 10, you could update to 11 now and then 
run tasksel to check what's installed.

DO READ RELEASE NOTES BEFORE UPGRADING [just in case anything changes -
10 -> 11 has some diffferent stanzas for /etc/apt/sources.list

All the very best, as ever,

Andy Cater

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

#242924

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

I though about that too, that the video card somehow could have affected
the update somehow regarding DE.

The VGA compatible controller entry of lspci is NVIDIA Corporation GP107GL
[Quadro P400] (rev a1)

I don't remember anything about firmware during the installation.

On Fri, Dec 10, 2021 at 7:12 PM Andrew M.A. Cater <amacater@einval.com>
wrote:

> On Fri, Dec 10, 2021 at 06:24:19PM +0200, Thanos Katsiolis wrote:
> > Thank you both for your replies.
> >
> > I managed to complete the installation (run also apt full-upgrade
> > successfully) and then reboot.
> > After the update the system boots only with the ttys (1-6) and not with a
> > graphical interface, and by that I mean that I tried to change to the
> > graphical interface with Ctrl-Alt-F7 and Ctrl-Alt-F8.
> > I verified that Debian 10.10 was installed , ran cleaning commands,
> reboot
> > again but again I can only access ttys and not the Graphical Interface.
> >
> > Is there any possibility that a graphical environment has not been
> > installed at all?
> >
> > All the update procedures that I have seen, do not have extra steps. What
> > am I missing?
>
> Can you tell us your video hardware?
>
> Is there any firmware needed somewhere along the line?
>
> Having safely updated to 10, you could update to 11 now and then
> run tasksel to check what's installed.
>
> DO READ RELEASE NOTES BEFORE UPGRADING [just in case anything changes -
> 10 -> 11 has some diffferent stanzas for /etc/apt/sources.list
>
> All the very best, as ever,
>
> Andy Cater
>
>

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

#242921

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

On Vi, 10 dec 21, 18:24:19, Thanos Katsiolis wrote:
> Thank you both for your replies.
> 
> I managed to complete the installation (run also apt full-upgrade
> successfully) and then reboot.
> After the update the system boots only with the ttys (1-6) and not with a
> graphical interface, and by that I mean that I tried to change to the
> graphical interface with Ctrl-Alt-F7 and Ctrl-Alt-F8.
> I verified that Debian 10.10 was installed , ran cleaning commands, reboot
> again but again I can only access ttys and not the Graphical Interface.
> 
> Is there any possibility that a graphical environment has not been
> installed at all?

Yes, it's possible, e.g. in case there was a conflict and APT decided it 
should remove remove your Desktop Environment to resolve the conflict. 

This should be visible in the logs or just try running:

    dpkg -l '*dm'
 
> All the update procedures that I have seen, do not have extra steps. What
> am I missing?

Alternatively (and more likely) Xorg is failing to start for some 
reason.

Anything interesting in the output of `journalctl -ab`, 
/var/log/Xorg.0.log or ~/.local/share/xorg/Xorg.0.log?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#242961

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

[this appears to have been meant for the list]

On Vi, 10 dec 21, 20:25:26, Thanos Katsiolis wrote:
> > Yes, it's possible, e.g. in case there was a conflict and APT decided it
> > > should remove remove your Desktop Environment to resolve the conflict.
> >
> > > This should be visible in the logs or just try running:
> >
> >     > dpkg -l '*dm'
> >
> >
> The output out the command is Desired =Unknown/Install/Remove?Purge/Hold
> |
> Status=Not/inst/Conf-files/Unpacked/half-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status, Err: uppercase=bad)
> ||/Name     Version    Architecture    Description
> un  mdadm   <none>    <none>        (no description available)
> 
> Which means that there is no Desktop Environment installed

More precisely, no Display Manager (DM). Even if you do have a Desktop 
Environment installed, the DM is responsible for automatically starting 
it.

Please try to log in on the console and run:

    startx


If you do get a Desktop Environment (which one?) most likely all you 
need is to install a DM. For Gnome you probably want GDM (package 
'gdm').

> > Alternatively (and more likely) Xorg is failing to start for some
> > reason.
> >
> > > Anything interesting in the output of `journalctl -ab`,
> > > /var/log/Xorg.0.log or ~/.local/share/xorg/Xorg.0.log?
> >
> >
> journalctl -ab /var/log/Xorg.0.log
> returns Couldn't cannonicalize path : No such file or directory
> 
> as well as ~/.local/share/xorg/Xorg.0.log?

Apologies, that should have been clearer, I meant: please post the 
output of:


    journalctl -ab

(requires root or sudo to get useful output)


as well as the *contents* of /var/log/Xorg.0.log or 
~/.local/share/xorg/Xorg.0.log (whichever exists).

Since you don't have a DM installed these are only useful if the Desktop 
Environment fails to start.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#243048

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

Andrei sorry for my late response,


> More precisely, no Display Manager (DM). Even if you do have a Desktop
> Environment installed, the DM is responsible for automatically starting
> it.
>
> Please try to log in on the console and run:
>
>     startx
>
>
>
startx ha the output:

/etc/X11/xinit/xserverrc: 3: exec: /usr/bin/X: not found
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error


> If you do get a Desktop Environment (which one?) most likely all you
> need is to install a DM. For Gnome you probably want GDM (package
> 'gdm').
>




> Apologies, that should have been clearer, I meant: please post the
> output of:
>
>
>     journalctl -ab
>
> (requires root or sudo to get useful output)
>
>
The output is quite large. Which are the interesting entries to post?


>
> as well as the *contents* of /var/log/Xorg.0.log or
> ~/.local/share/xorg/Xorg.0.log (whichever exists).
>
>
Both files do not exist.


> Since you don't have a DM installed these are only useful if the Desktop
> Environment fails to start.
>
> Kind regards,
> Andrei
> --
> http://wiki.debian.org/FAQsFromDebianUser


It appears that neither DM nor DE are installed. Should I start with a DM?

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

#242928

On 10/12/2021 16:24, Thanos Katsiolis wrote:
> I verified that Debian 10.10 was installed , ran cleaning commands,
> reboot again but again I can only access ttys and not the Graphical
> Interface.

What DE you are using?
1. Check if your DE is still installed.
dpkg -l | grep /your-de/name/

2. Install it back, if it it has been uninstalled.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀⠀⠀

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

#243049

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

Thank you Piotr for your response.

As I responded to Andrei lower in the thread, neither DM nor DE must have
been installed.

I would like to get GNOME, so I will try to install it. Does this affect
the DM somehow?

On Fri, Dec 10, 2021 at 8:54 PM piorunz <piorunz@gmx.com> wrote:

> On 10/12/2021 16:24, Thanos Katsiolis wrote:
> > I verified that Debian 10.10 was installed , ran cleaning commands,
> > reboot again but again I can only access ttys and not the Graphical
> > Interface.
>
> What DE you are using?
> 1. Check if your DE is still installed.
> dpkg -l | grep /your-de/name/
>
> 2. Install it back, if it it has been uninstalled.
>
> --
> With kindest regards, Piotr.
>
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
> ⠈⠳⣄⠀⠀⠀⠀
>
>

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

#243057

On Mon, Dec 13, 2021 at 12:04:32PM +0200, Thanos Katsiolis wrote:
> Thank you Piotr for your response.
> 
> As I responded to Andrei lower in the thread, neither DM nor DE must have
> been installed.
> 
> I would like to get GNOME, so I will try to install it. Does this affect
> the DM somehow?

If you install GNOME in any of the "standard" ways (e.g. tasksel), it
will install gdm3 as the Display Manager.

You might wish to double-check that you have the necessary firmware
and/or drivers for your display before installing GNOME.  In some cases,
you can get a "black screen" when the necessary firmware/drivers are
not present, either during login (gdm3), or after login (GNOME).

(When that happens, the workaround is to get to the state you're
*currently* in [console text login], and install firmware from there.
So, you're kind of ahead of the game here.)

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

#242884

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

On Jo, 09 dec 21, 16:39:52, Thanos Katsiolis wrote:
> Hello,
> 
> I followed the Release notes
> <https://www.debian.org/releases/buster/amd64/release-notes.en.pdf> for
> Debian 10, in order to update from Debian 9 to Debian 10. After running
> 
> apt-get upgrade
> 
> I ran
> 
> apt full-upgrade
> 
> to complete the update to Debian 10. While the command was running on
> terminal, it switched to black background and displayed
> 
> /dev/sda5: clean, xxxxxxx/xxxxxx files, xxxxxxx/xxxxxx blocks
> [     xxxxxx] kvm: disabled by bios
> [     xxxxxx] kvm: disabled by bios
> [     xxxxxx] kvm: disabled by bios
> [     xxxxxx] kvm: disabled by bios
> [ OK ] Started Daily apt upgrade and clean activities.
> 
> with a blinking underscore, and the upgrade is interrupted. What is this
> about, and how can I proceed?

Are you sure it is interrupted (how did you check)?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#242927

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

So I have to install a Desktop Environment.

I am thinking of using tasksel to install GNOME.

Thank you for your help.

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

#243066

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

The Display Manager was missing (gdm3), I installed it and the login works
fine.

Now when I log in there is a blue screen and the cursor, nothing else is
displayed.
Is there a problem with GNOME?

Thank you all.

On Thu, Dec 9, 2021 at 4:39 PM Thanos Katsiolis <kls.thanos@gmail.com>
wrote:

> Hello,
>
> I followed the Release notes
> <https://www.debian.org/releases/buster/amd64/release-notes.en.pdf> for
> Debian 10, in order to update from Debian 9 to Debian 10. After running
>
> apt-get upgrade
>
> I ran
>
> apt full-upgrade
>
> to complete the update to Debian 10. While the command was running on
> terminal, it switched to black background and displayed
>
> /dev/sda5: clean, xxxxxxx/xxxxxx files, xxxxxxx/xxxxxx blocks
> [     xxxxxx] kvm: disabled by bios
> [     xxxxxx] kvm: disabled by bios
> [     xxxxxx] kvm: disabled by bios
> [     xxxxxx] kvm: disabled by bios
> [ OK ] Started Daily apt upgrade and clean activities.
>
> with a blinking underscore, and the upgrade is interrupted. What is this
> about, and how can I proceed?
>

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

#243071

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

On Mon, Dec 13, 2021 at 10:14 AM Thanos Katsiolis <kls.thanos@gmail.com>
wrote:

> The Display Manager was missing (gdm3), I installed it and the login works
> fine.
>
> Now when I log in there is a blue screen and the cursor, nothing else is
> displayed.
> Is there a problem with GNOME?
>


Probably.

You might try reinstalling Gnome; "aptitude reinstall task-gnome-desktop"
might do it.

Or you might try creating and logging in as a different user, to see if
that user has the same problem.

Or you might try selecting a different desktop/WM; "aptitude install xfce4"
might do it, and selecting that environment on login.

-- 
Kent

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

#243100

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

Kent thank you for your response.


I also had to install the GNOME, although using dpkg I saw related
packages, so I thought that it was installed.
Is there a way to verify that something like DM (gdm) or GNOMe is
installed, in order to know what to do?

Thank you all for your help.

On Mon, Dec 13, 2021 at 8:58 PM Kent West <westk@acu.edu> wrote:

>
>
> On Mon, Dec 13, 2021 at 10:14 AM Thanos Katsiolis <kls.thanos@gmail.com>
> wrote:
>
>> The Display Manager was missing (gdm3), I installed it and the login
>> works fine.
>>
>> Now when I log in there is a blue screen and the cursor, nothing else is
>> displayed.
>> Is there a problem with GNOME?
>>
>
>
> Probably.
>
> You might try reinstalling Gnome; "aptitude reinstall task-gnome-desktop"
> might do it.
>
> Or you might try creating and logging in as a different user, to see if
> that user has the same problem.
>
> Or you might try selecting a different desktop/WM; "aptitude install
> xfce4" might do it, and selecting that environment on login.
>
> --
> Kent
>
>
>

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web