# Very Strange screen... Help!

**URL:** <https://discussions.flightaware.com/t/very-strange-screen-help/80174>\
**Category:** ADS-B Flight Tracking\
**Created:** [November 16, 2021, 12:48am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174 "2021-11-16T00:48:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![KevinVogt](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kevinvogt/32/110319_2.png) [@KevinVogt](https://discussions.flightaware.com/u/KevinVogt)\
**Post date:** [November 16, 2021, 12:48am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/1 "2021-11-16T00:48:13Z")

</div>

My piaware running 6.1 is sending the ADSB data to all the sites I set it up to send to, but when I browse directly into it, this is the screen I get… I tried multiple browsers and get the same result. Any ideas?

[Screen Shot 2021-11-15 at 3.57.58 PM|512x500](https://discussions.flightaware.com/uploads/short-url/b3tHnB2HKMR4YKtwFs5MakLe6Fa.jpeg)

---

<div class="post-metadata">

**Author:** ![jaymot](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jaymot/32/122023_2.png) [@jaymot](https://discussions.flightaware.com/u/jaymot)\
**Post date:** [November 16, 2021, 1:03am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/3 "2021-11-16T01:03:47Z")

</div>

Is this with the PiAware image or a package install on Raspbian or some other ARM Linux? What led up to this condition? Is it a fresh installation or has it been working in the past?

---

<div class="post-metadata">

**Author:** ![KevinVogt](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kevinvogt/32/110319_2.png) [@KevinVogt](https://discussions.flightaware.com/u/KevinVogt)\
**Post date:** [November 16, 2021, 1:13am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/4 "2021-11-16T01:13:25Z")

</div>

It was working fine in the past… I recently adjusted my settings to automatically change adaptive gain, and this started happening.

---

<div class="post-metadata">

**Author:** ![KevinVogt](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kevinvogt/32/110319_2.png) [@KevinVogt](https://discussions.flightaware.com/u/KevinVogt)\
**Post date:** [November 16, 2021, 1:16am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/5 "2021-11-16T01:16:52Z")

</div>

I believe I am running all of the latest software…

---

<div class="post-metadata">

**Author:** ![jaymot](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jaymot/32/122023_2.png) [@jaymot](https://discussions.flightaware.com/u/jaymot)\
**Post date:** [November 16, 2021, 1:19am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/6 "2021-11-16T01:19:03Z")

</div>

Again, did you burn the piaware image to the SD card or a Raspbian PiOS image then install piaware from packages?

Exactly what steps did you take to enable adaptive gain?

Did you try putting your settings back the way they were before you changed them?

---

<div class="post-metadata">

**Author:** ![KevinVogt](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kevinvogt/32/110319_2.png) [@KevinVogt](https://discussions.flightaware.com/u/KevinVogt)\
**Post date:** [November 16, 2021, 1:35am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/7 "2021-11-16T01:35:57Z")

</div>

I burned the image on an SD card running on a Raspberry Pi 3. Upgraded the OS using the FlightAware settings page, updated and restart both Piaware and dump1090 on that page, watched the process in the log, etc… I did set the adaptive gain back to manual. currently running **PiAware Version:** 6.1  
\*\*Dump1090-fa Version: dump1090-fa 6.1~bpo9+1

---

<div class="post-metadata">

**Author:** ![jaymot](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jaymot/32/122023_2.png) [@jaymot](https://discussions.flightaware.com/u/jaymot)\
**Post date:** [November 16, 2021, 1:39am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/8 "2021-11-16T01:39:10Z")

</div>

> [@KevinVogt](#):
>
> I burned the image on an SD card running on a Raspberry Pi 3

What image exactly? (20 characters)

---

<div class="post-metadata">

**Author:** ![KevinVogt](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kevinvogt/32/110319_2.png) [@KevinVogt](https://discussions.flightaware.com/u/KevinVogt)\
**Post date:** [November 16, 2021, 1:49am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/9 "2021-11-16T01:49:26Z")

</div>

I did it a few months ago and don’t recall. What is the best way to find it. Currently in the terminal…

---

<div class="post-metadata">

**Author:** ![jaymot](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jaymot/32/122023_2.png) [@jaymot](https://discussions.flightaware.com/u/jaymot)\
**Post date:** [November 16, 2021, 1:56am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/10 "2021-11-16T01:56:33Z")

</div>

The PiAware image is a headless Linux image meaning there’s no graphical user interface (GUI) when you connect a monitor, keyboard and mouse to your Pi. Raspbian and similar OSs will display a GUI desktop.

---

<div class="post-metadata">

**Author:** ![KevinVogt](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kevinvogt/32/110319_2.png) [@KevinVogt](https://discussions.flightaware.com/u/KevinVogt)\
**Post date:** [November 16, 2021, 2:11am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/11 "2021-11-16T02:11:19Z")

</div>

Got it. What is the best way to determine exactly what OS I have. I hooked up a monitor to my Pi at one point and could watch it start up and give a running status, but have never interacted with it. I don’t have a wired keyboard or mouse to attach…

---

<div class="post-metadata">

**Author:** ![jaymot](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jaymot/32/122023_2.png) [@jaymot](https://discussions.flightaware.com/u/jaymot)\
**Post date:** [November 16, 2021, 2:47am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/12 "2021-11-16T02:47:37Z")

</div>

> [@KevinVogt](#):
>
> could watch it start up and give a running status,

What does that mean? Did you get a GUI desktop or not?

---

<div class="post-metadata">

**Author:** ![jaymot](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jaymot/32/122023_2.png) [@jaymot](https://discussions.flightaware.com/u/jaymot)\
**Post date:** [November 16, 2021, 3:24am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/13 "2021-11-16T03:24:38Z")

</div>

Also, please answer peoples questions or they can’t help you.

> [@jaymot](#):
>
> Exactly what steps did you take to enable adaptive gain?
> 
> Did you try putting your settings back the way they were before you changed them?

---

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [November 16, 2021, 3:50am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/14 "2021-11-16T03:50:24Z")

</div>

That sort of page display is a symptom that some of the support files (CSS, etc) for the map page are broken. Try clearing your browser cache and try again; if it persists, look for errors in the dev console (e.g. F12 in Chrome, look at the Console or Network tab)

---

<div class="post-metadata">

**Author:** ![jaymot](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jaymot/32/122023_2.png) [@jaymot](https://discussions.flightaware.com/u/jaymot)\
**Post date:** [November 16, 2021, 5:47am UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/15 "2021-11-16T05:47:25Z")

</div>

I think you nailed it. I get the same screen as the OP if I go into the View menu and set Page Style to no style. If I set it back to Basic Page Style I get the normal screen again.

---

<div class="post-metadata">

**Author:** ![KevinVogt](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kevinvogt/32/110319_2.png) [@KevinVogt](https://discussions.flightaware.com/u/KevinVogt)\
**Post date:** [November 16, 2021, 5:56pm UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/16 "2021-11-16T17:56:57Z")

</div>

I cleared browser caches, tried it on my iPhone, iPad, laptop, different browsers with the same result. This is what the developer console shows on Chrome…

 ![Screen Shot 2021-11-16 at 9.54.50 AM.jpg](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/9/8/986182776b511e75bd78a90990e6a067f80c2047.jpeg)

---

<div class="post-metadata">

**Author:** ![KevinVogt](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kevinvogt/32/110319_2.png) [@KevinVogt](https://discussions.flightaware.com/u/KevinVogt)\
**Post date:** [November 16, 2021, 6:02pm UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/17 "2021-11-16T18:02:38Z")

</div>

Also, the Piaware seems to hang up so that I cannot ssh in from the console… To get in, I have to unplug it and try within a few minutes of plugging it back in. Not sure if that is related, though. Still, it is feeding all of the sites data… FA, FR24, ADSBX, OpenSky, Radarbox are all getting data. I also cannot connect to Virtual Radar Server without unplugging it and trying it soon after plugging back in.

![WCCLogoWeb.jpg](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/7/8/7853a753fbb89e6215f5e3e6bf79edd55bbd3a4d.jpeg)

---

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [November 16, 2021, 7:17pm UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/18 "2021-11-16T19:17:55Z")

</div>

If I had to guess I’d say that you have filesystem corruption and one of the support files for skyaware has been damaged. The ssh / VRS problem also implies there’s something badly wrong with that install overall…

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [November 16, 2021, 8:50pm UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/19 "2021-11-16T20:50:38Z")

</div>

> [@KevinVogt](#):
>
> What is the best way to find it. Currently in the terminal

> [@jaymot](#):
>
> The PiAware image is a headless Linux image meaning there’s no graphical user interface (GUI)

It is very eady to find out just by looking at terminal.

If command prompt is:  
**`pi@piaware:~ $`**  
it is a piaware SD card image

If command prompt is:  
**`pi@raspberrypi:~ $`**  
it is Raspbian image with package install of piaware & dump1090-fa

&nbsp;

---

<div class="post-metadata">

**Author:** ![KevinVogt](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/kevinvogt/32/110319_2.png) [@KevinVogt](https://discussions.flightaware.com/u/KevinVogt)\
**Post date:** [November 16, 2021, 8:53pm UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/20 "2021-11-16T20:53:58Z")

</div>

Getting down to brass tacks, what is my best bet for fixing it? I have a lot of stuff on there and would hate to lose it all… RPI monitor, Graphs1090, feeds directing traffic to half a dozen sites, etc…

---

<div class="post-metadata">

**Author:** ![alphanettech](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/alphanettech/32/120522_2.png) [@alphanettech](https://discussions.flightaware.com/u/alphanettech)\
**Post date:** [November 16, 2021, 10:23pm UTC](https://discussions.flightaware.com/t/very-strange-screen-help/80174/21 "2021-11-16T22:23:02Z")

</div>

> [@KevinVogt](#):
>
> Getting down to brass tacks, what is my best bet for fixing it?

By answering the questions you have been asked, without that information it’s not possible to figure out the issue and give instructions on how to resolve.

[Next page](https://discussions.flightaware.com/t/very-strange-screen-help/80174.md?page=2)
