# Problem after updating Raspbian Stretch to Buster

**URL:** <https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278>\
**Category:** General\
**Created:** [21 November 2020 09:27 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278 "2020-11-21T09:27:40Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 09:27 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/1 "2020-11-21T09:27:40Z")

</div>

@dceejay @wb666greene @krambriw I updated my RPI 3B with this tutorial :  
[Stretch to Buster Raspbian](https://discourse.nodered.org/t/beta-testing-nodes-for-live-streaming-mp4/33743/152)  
The problem is, I can't access Node Red anymore.  
It seems that the update did not work well. Secund problem i'm not Linux specialist ...

It looks like the update didn't work well because I can't see an IP address.

- i test `ifconfig`  

- i test the `hostname -i` return **127.0.1.1**

- 

- i test `htop` Node-Red running 17% cpu  

- `sudo apt update`seems to have an error !! :  

- And last `startx` do not start the desktop :  

- `iwconfig` :  

**I remember having accepted, during the update, a program which used the DHCP function. it seems to me that NO was by default, and I put yes ...**

Someone have an idea ?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [21 November 2020 09:56 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/2 "2020-11-21T09:56:59Z")

</div>

Yes, it's no longer on the network.. If you do normally use DHCP then try `sudo dhclient eth0` and then see if that gives you a connection... if so - then `ping 1.1.1.1` to check if internet is there and then redo `sudo apt -y full-upgrade`

If you usually use a static address then try `sudo ifconfig eth0 w.x.y.z/24` (where w.x.y.z) is your normal address etc

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 10:00 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/3 "2020-11-21T10:00:06Z")

</div>

> [@dceejay](#):
>
> sudo dhclient eth0

respond : "cannot find device"eth0" 😨

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 10:04 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/4 "2020-11-21T10:04:02Z")

</div>

> [@dceejay](#):
>
> `ping 1.1.1.1`

is correct :

 ![IMG_20201121_110219](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/4/544eaa62abb0dc4c0984777b5dfc53a2efeaf14a.jpeg)🤔

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [21 November 2020 10:06 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/5 "2020-11-21T10:06:03Z")

</div>

ah so it's back online... does the `sudo apt -y full-upgrade` now proceed ? if not what does `cat etc/resolv.conf` show for the nameserver ?

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 10:12 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/6 "2020-11-21T10:12:10Z")

</div>

> [@dceejay](#):
>
> sudo apt -y full-upgrade

> [@dceejay](#):
>
> sudo ifconfig eth0 w.x.y.z/24

 ![InkedIMG_20201121_110741_LI (2)](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/c/8c1b8b1afa5f45a5c73ebb6f48b51576e48a3ede.jpeg)

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 10:14 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/7 "2020-11-21T10:14:10Z")

</div>

> [@dceejay](#):
>
> cat etc/resolv.conf

"no such file"

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 10:19 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/8 "2020-11-21T10:19:54Z")

</div>

I may have a problem with the ethernet circuit driver? can I put it on a usb stick and reinstall it ?  
the green led on the ethernet port is flashing so it is working ..

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [21 November 2020 10:23 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/9 "2020-11-21T10:23:19Z")

</div>

sorry - should have been `cat /etc/resolv.conf` - but it seems to be ok.  
can you try to start Node-RED... `node-red-stop && node-red-start`

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 10:29 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/10 "2020-11-21T10:29:53Z")

</div>

> [@dceejay](#):
>
> cat /etc/resolv.conf

#Generated by resolvconf  
nameserver 192.168.1.1

> [@dceejay](#):
>
> node-red-stop && node-red-start

yes its working !

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [21 November 2020 10:32 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/11 "2020-11-21T10:32:44Z")

</div>

and maybe this for the desktop `sudo apt-get --reinstall install raspberrypi-ui-mods` - but maybe just need to reboot first...  
(meanwhile - you could also check the ffmpeg version which I think is where this all started...)

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 10:40 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/12 "2020-11-21T10:40:33Z")

</div>

> [@dceejay](#):
>
> check the ffmpeg version which I think is where this all started.

> [@\[beta testing\] nodes for live streaming mp4](https://discourse.nodered.org/t/beta-testing-nodes-for-live-streaming-mp4/33743/156):
>
> ok i got it : frag\_every\_frame is here after Buster update slightly_smiling_face

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 11:01 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/13 "2020-11-21T11:01:27Z")

</div>

> [@dceejay](#):
>
> sudo apt-get --reinstall install raspberrypi-ui-mods

the reinstallation went well without error, but when I set the boot on DESKTOP GUI automatic login,

 ![IMG_20201121_114830](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/1/3179bbed8098a8869ba8ef64143866d966364f8e.jpeg)  
it starts on the Console :  
 ![IMG_20201121_115458](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/c/1c952ff46d20e7eda9d8f930f263d9c164020a01.jpeg)

**PLUS** : SSH is comeback that is great BUT the serial port, and VNC not working

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [21 November 2020 11:15 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/14 "2020-11-21T11:15:07Z")

</div>

what does `/etc/init.d/lightdm start` report ?

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 11:17 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/15 "2020-11-21T11:17:37Z")

</div>

```auto
pi@pi:~ $ /etc/init.d/lightdm start
[....] Starting lightdm (via systemctl): lightdm.service==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentification requise pour démarrer « lightdm.service ».
Multiple identities can be used for authentication:
 1. ,,, (pi)
 2. root
Choose identity to authenticate as (1-2):

```

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [21 November 2020 11:25 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/16 "2020-11-21T11:25:38Z")

</div>

and ? pick pi if that is who you usually are...

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 12:12 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/17 "2020-11-21T12:12:43Z")

</div>

sorry for delay response :  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/5/257f78b7b7ad0505854989fbf46b10cb6d4d0c0e.png)  
_seems to be ok ...._

BUT  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/d/7d5b2c3358add8eed58217202ed92ffdb759270a.png)  
_unable to display desktop_

vnc is well connected to the network, but the Desktop is not displayed. I also note a malfunction of the UART on the GPIO

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/c/9c99e6fa9d93bebf24e81f1031d03789a993847a.png)  
_the processor is overloaded and the swap memory is full_  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/0/40c18b3b179fe21122199520022747b2ad1015a0.png)  
_perhaps because of the UART issue ?_

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/f/ef382d279d3aef89111c3de4f5a842cda0bcdb7c.png)  
_Stop NR and very low cpu charge_

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [21 November 2020 12:31 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/18 "2020-11-21T12:31:21Z")

</div>

Thanks again @dceejay for your help that you already made me redo NR 🙂

1. It's good for the UART, I deleted the node and put it back in my flow: it's working now and I'm running at 5-8% CPU load

2. the Desktop Buster still needs to work ...

---

<div class="post-metadata">

**Author:** ![SuperNinja](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/superninja/32/5761_2.png) [@SuperNinja](https://discourse.nodered.org/u/SuperNinja)\
**Post date:** [22 November 2020 15:13 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/19 "2020-11-22T15:13:43Z")

</div>

Here is my last issue : **i can not open the Buster Desktop**.

When i type `startx` , it does't launch.  
Here is the [xorg log.txt](https://discourse.nodered.org/uploads/short-url/jrEzU8NWgn0B8XGlVXmTDTSTWsH.txt) (3.4 KB) about the problem :

```auto
[8436.792]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[8436.792] Build Operating System: Linux 4.9.0-0.bpo.6-armmp armv7l Raspbian
[8436.792] Current Operating System: Linux pi 5.4.77-v7+ #1371 SMP Tue Nov 17 13:32:02 GMT 2020 armv7l
[8436.793] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.$
[8436.793] Build Date: 27 August 2020 08:51:48AM
[8436.793] xorg-server 2:1.20.4-1+deb10u1 (https://www.debian.org/support)
[8436.793] Current version of pixman: 0.36.0
[8436.794] Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[8436.794] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[8436.794] (==) Log file: "/home/pi/.local/share/xorg/Xorg.0.log", Time: Sat Nov 21 15:31:24 2020
[8436.795] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[8436.796] (==) No Layout section. Using the first Screen section.
[8436.796] (==) No screen section available. Using defaults.
[8436.796] (**) |-->Screen "Default Screen Section" (0)
[8436.796] (**) | |-->Monitor "<default monitor>"
[8436.798] (==) No device specified for screen "Default Screen Section".
        Using the first device section listed.
[8436.798] (**) | |-->Device "Allwinner A10/A13 FBDEV"
[8436.798] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[8436.798] (==) Automatically adding devices
[8436.798] (==) Automatically enabling devices
[8436.799] (==) Automatically adding GPU devices
[8436.799] (==) Max clients allowed: 256, resource mask: 0x1fffff
[8436.799] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[8436.799] Entry deleted from font path.
[8436.799] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[8436.799] Entry deleted from font path.
[8436.799] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[8436.799] Entry deleted from font path.
[8436.799] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[8436.799] Entry deleted from font path.
[8436.799] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[8436.799] Entry deleted from font path.
[8436.799] (==) FontPath set to:
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/100dpi,
        built-ins
[8436.799] (==) ModulePath set to "/usr/lib/xorg/modules"
[8436.799] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[8436.799] (II) Loader magic: 0x1fcf80
[8436.800] (II) Module ABI versions:
[8436.800] X.Org ANSI C Emulation: 0.4
[8436.800] X.Org Video Driver: 24.0
[8436.800] X.Org XInput driver : 24.1
[8436.800] X.Org Server Extension : 10.0
[8436.813] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_33
[8436.814] (II) no primary bus or device found
[8436.814] (II) LoadModule: "glx"
[8436.815] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[8436.836] (II) Module glx: vendor="X.Org Foundation"
[8436.836] compiled for 1.20.4, module version = 1.0.0

```

There are _defaut settings_, _from config file_, _informational_, _warning_ errors but how to solve then ?

PS : `sudo apt-get --reinstall install raspberrypi-ui-mods` did already do

If someone have an idea ?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [6 December 2020 15:13 UTC](https://discourse.nodered.org/t/problem-after-updating-raspbian-stretch-to-buster/36278/20 "2020-12-06T15:13:55Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.