volumio@pi4-streamer:~$ xrandr --query
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 480, current 800 x 480, maximum 800 x 480
default connected 800x480+0+0 0mm x 0mm
800x480 0.00*
v0.061
Networking
- WiFi connection and recovery handling fixed for devices where networking was previously unreliable or broken after boot.
- Improved hotspot fallback logic and corrected initial wireless interface bring-up.
v0.61 fixed the initial wireless interface bring-up with the HP x2 Detachable 10-p0xx and the Dell Wyse 3040 (when used without wired connection).
As for brightness control and mute buttons, they donāt appear to be working on any device reported until now.
Checking a number of my own devices with the current Volumio Buster versions, it appears these buttons did not work on current versions either.
We will investigate, whether there is a simple, generic approach to solve both issues.
But to dampen expectations, this is not top priority for the Bookworm migration.
In case someone already knows how to solve this, we are always very pleased with any additional community help we can get with x86 maintenance and improvement.
@MitchStoner What is the make and model of your display?
Sorry, but I donāt know, itās a generic noname chinese productā¦
Do you have a link where the product is shown and could you post pictures of the display and its back?
Please, is this only happening with the Bookworm Alpha? Not with the current Volumio release?
If current version also, then please let us know which platform so your post can be moved, because this thread is about Alpha Bookworm only
Did this happen while booted from usb or internal disk?
Hey @MitchStoner,
Thanks again for the information.
Expanding on @gvolt, @gkkpch and @Wheaten questions:
Could you please send us copies (or screenshots) of the following files from your working Buster setup?
/boot/config.txt
/boot/volumioconfig.txt
/boot/userconfig.txt
It is important because screen rotation on DSI displays usually depends on having a correct dtoverlay
applied during early boot.
Without seeing these files, we cannot determine whether this is a missing overlay issue, or if something else changed between Buster and Bookworm.
Also, if possible, please confirm if any additional rotation was set in /boot/cmdline.txt
on your old setup.
Thank you for helping us track this down!
Kind Regards,
Internal disk
Hi,
running 0.60 the OTA does not find the 0.61 (Test Mode is on).
Do I have to flash it manually? Or is there a trick how to use OTA?
Ah, I found it myself - Test Mode must be OFF !
Cheers,
Robert
Hi,
running the 0.60 OTA shows 0.61 as a newer version. I startet the update and it seems to be successful. But after the reboot version 0.60 is still active. What went wrong here?
Cheers,
Robert
Hey @Robert.Hecht,
Can you check the process again if 0.061 is still offered?
Can you share logs after OTA?
Can you remind me your hardware specs?
Kind Regards,
Same for me. I also tried with Test Mode off. No luck.
(Pi 3B+ with Allo DigiOne)
info: CoreCommandRouter::executeOnPlugin: metavolumio , requestToMetaVolumio
No test mode
No alpha test mode
info: Update Ready: {"changeLogLink":"","description":"You're already on the latest version","title":"No Updates Available","updateavailable":false}
info: CoreCommandRouter::executeOnPlugin: updater_comm , setUpdateMessageCache
info: CoreCommandRouter::Close All Modals sent
Dear Volumionauts,
OTA updates are available starting from version 0.060 onward.
As already mentioned, Test Mode should only be enabled for plugin testing.
If you enable Test Mode for system updates, your device will point to the production Beta release channel instead of staying within the Alpha track.
Kind Regards,
I do have 0.060 (with test mode OFF) and I donāt see 0.061 as update via OTA.
Hey @Ema82,
Lets take this with methodical steps:
- change your device name in UI (required)
- change back to what it was (not required)
- reboot
- check if OTA is offered in System Settings
Of course, share logs.
Kind Regards,
I changed the device name and it worked. Thank you!
Hereās the log in case you need it for further analysis:
http://logs.volumio.org/volumio/evjHHxC.html
Hi @nerd ,
hereās the log:
http://logs.volumio.org/volumio/eqGHZHl.html
0.61 is still offered.
HW:
volumio@smx:~$ inxi -Fxxxz
System:
Kernel: 6.6.69-volumio arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 Console: pty pts/0
Distro: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: ASRock model: J3455-ITX serial: <superuser required>
UEFI: American Megatrends v: P1.40 date: 07/14/2017
CPU:
Info: quad core model: Intel Celeron J3455 bits: 64 type: MCP smt: <unsupported> arch: Goldmont
rev: 9 cache: L1: 224 KiB L2: 2 MiB
Speed (MHz): avg: 2196 min/max: 800/2300 cores: 1: 2196 2: 2196 3: 2196 4: 2196
bogomips: 11980
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
Device-1: Intel HD Graphics 500 vendor: ASRock driver: i915 v: kernel arch: Gen-9 ports:
active: DP-1 empty: DP-2,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5a85 class-ID: 0300
Display: server: X.org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: iris gpu: i915 tty: 124x87
Monitor-1: DP-1 model: Dell P3223QE serial: <filter> res: 3840x2160 dpi: 140
size: 697x392mm (27.44x15.43") diag: 800mm (31.5") modes: max: 3840x2160 min: 720x400
API: OpenGL Message: GL data unavailable in console and glxinfo missing.
Audio:
Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster vendor: ASRock
driver: snd_hda_intel v: kernel bus-ID: 00:0e.0 chip-ID: 8086:5a98 class-ID: 0403
API: ALSA v: k6.6.69-volumio status: kernel-api
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169
v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.89 TiB used: 787.42 GiB (40.7%)
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1B6Q scheme: GPT
ID-2: /dev/sdb type: USB vendor: Samsung model: PSSD T7 size: 931.51 GiB type: SSD
serial: <filter> scheme: MBR
ID-3: /dev/sdc type: USB vendor: SanDisk model: Ultra Fit size: 57.28 GiB speed: 6.0 Gb/s
type: N/A serial: <filter> rev: 1.00 scheme: GPT
ID-4: /dev/sdd type: USB vendor: SMI (STMicroelectronics) model: USB size: 15 GiB type: N/A
serial: <filter> rev: 1100 scheme: MBR
Partition:
ID-1: /boot size: 168.4 MiB used: 65.4 MiB (38.8%) fs: vfat dev: /dev/sdc1
Swap:
Alert: No swap data was found.
Sensors:
Src: /sys System Temperatures: cpu: 57.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 217 Uptime: 45m wakeups: 0 Memory: 3.7 GiB used: 1.38 GiB (37.4%) Init: systemd
v: 252 target: graphical (5) default: graphical Compilers: N/A Packages: pm: dpkg pkgs: 844
Shell: Bash v: 5.2.15 running-in: pty pts/0 (SSH) inxi: 3.3.26
Hope it helps.
Should I update via flashing the USB stick manually?
Cheers, Robert