Rauli

As I told on another topic, yesterday I installed Armbian 5.90 buster 4.19.57 on my OrangePi One. Now, when it boots, all the output text goes to the bottom line of the screen, with each line overwritting the previous one (no scroll). Then it asks for username, and when I type it it asks for password, overwritting the username I typed. And it probably displays the wellcome banner, but I just see the last line of the banner. Once logged, I have to type "clear" and then I can use the full screen, and it scrolls. That happens on the console, if I start a new session from another machine (using PuTTY) it works fine. My password doesn't overwrite my username, and I can see the full wellcome banner. I don't need to type "clear". Note: While botting, apart from text in the bottom line, also the Armbian name with big red letters is displayed in the middle of the screen. That's all, Armbian in the middle and text in the bottom line.

After some months not using my OrangePi One, yesterday I installed Armbian 5.90 buster 4.19.57 (previously I had a stretch release). I did a clean install, downloading the image and burning the microSD with it. I noticed the button now works for 1st time since I bought the OrangePi One. It shuts down the device, no need to install or configure nothing. But, previous Armbian versions I had, were able to set the machine CPU speed at 1.2 and 1.1 GHz. Now (with Armbian 5.90) the maximum is 1 GHz. On previous releases, the file /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies contained: 240000 480000 648000 816000 912000 960000 1008000 1104000 1200000 (being the last one 1.2 GHz) But now it contains: 120000 240000 480000 648000 816000 960000 1008000 (being the first one 120 MHz, not 1.2 GHz) In addition, the file /etc/default/cpufrequtils contains: MIN_SPEED=408000 MAX_SPEED=1200000 Where none of those speeds are available speeds, according to scaling_available_frequencies Is there a mistake, or were 1.2 and 1.1 GHz removed for any reason?

But at least evtest worked for you, that's better than nothing :) Have you upgraded Armbian since then? (your message is one year old). And does evtest still work for you?

The same problem with my Orange Pi One button, but I can't solve it. Installed ACPID and create an event/action file in /etc/acpi/events, but the button doesn't trigger any event. acpi_listen never displays any event when I press the button. And neither does the aforementioned utility "evtest /dev/input/event0", last line of text ever displayed is "Testing ... (interrupt to exit)". I thought the button was not properly soldered to the board, but I tested with multimeter the 2 pins (*) on the back side of the board and it changes from infinite to 0 ohms when I press the button, so I suppose it's OK. Using ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.18-sunxi (*) In fact I tested continuity of one pin with the screws holding the board to the case, and then I tested resistance between the other pin and a screw.

I have an Orange Pi One, with Armbian installed. *sometimes* when I log in it displays: "Welcome to ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.18-sunxi" Then some system statistics and a line with the CPU temperature, for example: "CPU temp: 58ºC" I can also get the current temperature with armbianmonitor -m or reading a file called "temp" in a directory under /etc/system (I don't remember the full path now). If I log in again, I see again the temperature in the welcome message, running armbianmonitor or reading the aforementioned file. Until I shutdown and boot again. Then, all 3 methods of getting the temperature work (like I have just told), or all 3 methods don't (no temperature shown at log in, no temperature column in armbianmonitor, and temp file does not exist). It's like the thermal sensor being detected randomly on some boots, but not on other. I plan to have this board on and unnatedned for long periods of time, so I would like to have the temperature/speed control working, to prevent overheating, but I don't know what's the problem here. The only changes I did from fresh install were international configuration and modify DTB to change micro-USB port mode from OTG to HOST. But with the new DTB, thermal sensor works *sometimes* and with the old DTB (which I backed-up), thermal sensor works *sometimes* too. I also run apt-get update and apt-get upgrade, but the problem remains. I haven't disabled any item for the welcome screen in armbian-config.