Hi @nerd ,
OTA on an X86 from 0.062 to 0.063 did work well.
Screen resolution: 3840x2160 (DELL P3223QE) connected to HDMI
âDisplay Zoom Factor = 120%â seems to be default? I donât remember changing this parameter ever.
Cheers, Robert
Hi @nerd ,
OTA on an X86 from 0.062 to 0.063 did work well.
Screen resolution: 3840x2160 (DELL P3223QE) connected to HDMI
âDisplay Zoom Factor = 120%â seems to be default? I donât remember changing this parameter ever.
Cheers, Robert
Brand: Toshiba Satellite Click Mini L9W-B-100 (x86)
Native resolution: 1920x1200 (WUXGA)
Connected: DSI-1
Rotation: 0Deg
Brand: Dell Latitude 3189 (x86)
Native resolution: 1366x768 (WXGA Wide)
Connected: eDP-1
Rotation: 0Deg
Brand: Dell Latitude E4200 (x86)
Native resolution: 1280x800 (WXGA)
Connected: LVDS-1
Rotation: 0Deg
Brand: Dell Wyse 3040 (x86)
Native resolution: n.a => Used screen 1920x1080
Connected: DP-1
Rotation: 0Deg
OTA update or fresh install?
Since it only involves the primary boot screen, just a random SD/USB with 0.063 will do
Dear Volumionauts,
Boot logo testing is in full swing - and already proving its worth.
To everyone whoâs shared photos, details, and setups so far: thank you. Youâve saved me from debugging blind on a pile of mystery screens. Itâs already clear that splash rendering in the real world is half engineering, half cartography.
But weâre not done yet.
The more edge cases we gather now, the less breakage, triage, and last-minute hacks weâll face when Volumio hits beta and final release.
If youâve got screens left to test, orientations you didnât post, or just a fresh power cycle to spare:
Please include:
This isnât polish - this is preemptive pain relief. Every photo now saves us a forum thread later.
Letâs keep the momentum. More data now = smoother launch later.
Kind Regards,
Ran out of screens
Hi @nerd !
Yesterday I successful mounted my Nas.
Today I tried to add/mount my usb hd but it was not recognized.
I can see all music files through filezilla sftp with my rpi:s ip-number.
Hey @ClaesM,
Thanks for sharing the log.
Iâve thoroughly analyzed the NAS mounting process, focusing on CIFS activity. Hereâs whatâs going on:
Volumio attempts to mount your NAS during boot with the following command:
mount -t cifs -o username=,password=,ro,dir_mode=0777,file_mode=0666,iocharset=utf8,noauto,soft,vers=2.0 //192.168.50.242/Musik /mnt/NAS/NAS
This fails consistently with:
CIFS: VFS: Error connecting to socket. Aborting operation.
CIFS: VFS: cifs_mount failed w/return code = -113
Error -113
corresponds to No route to host, indicating that either:
This is likely a boot-time race condition. The system retries, but networking or the NAS availability still isnât ready at that stage.
To move forward, please try the following:
vers=3.0
or 2.1
if needed)Also, from SSH, please verify:
ping -c 3 192.168.50.242
smbclient -L //192.168.50.242/ -N
sudo mount -t cifs -o username=guest,password=,vers=2.0 //192.168.50.242/Musik /mnt/NAS/NAS
This will help confirm if the mount works when the system is fully up.
Kind Regards,
Hi again!
Thanks for answering me! I will give it a new try tomorrov.
I´m not at all convinced that this is problem with alpha 0.063
Best Regards and huge respect for all your work!
/ C
I run Volumio 3 on an old toshiba laptop. Tried .063 today, got to the wizard, but could not connect to my wireless network.
Going back to 3
Cheers
Hey @jocoman,
Thank you for reporting.
Does your old Toshiba laptop have a model number? Or, perhaps WiFi adapter details? On VolumioOS v 3.xxx you can retrieve hardware details with lspci command. Without these, there is not possible to understand the problem; a simple search returned 38k pages to go through.
Kind Regards,
Hi again!
Well, I started up my system this morning and everything just work.
Probably it just needed a reboot?
Best Regards / C
First bootscreen
Second bootscreen
Seems exactly the same as in posting 156 from @ClaesM
Warm regards,
Ralf
Hey @rkorell,
Boot-screen:
Since you are on Raspberry Pi 5, you will need to add to the /boot/userconfig.txt
(or upgrade):
[all]
# Match your rotation counter clockwise 0, 90, 180, 270 degree
dtoverlay=vc4-kms-dsi-ili9881-7inch,rotation=270
which should produce v0.063 - calibrated (MICRO:0 = FULL)
Kind Regards,
Dear @nerd,
thanks for this.
The first shot taken is v0.063 - first attempt - NOW disappeared somehowâŚ
Display doesnt change neither for rotation=270 nor for rotation=90.
Touchdisplay config is: rotate=90° which works well.
userconfig.txt is as follows:
# Add your custom config.txt options to this file, which will be preserved during updates
# Power-LED und Status LED vom Raspberry Pi abschalten
dtparam=pwr_led_trigger=default-on
dtparam=pwr_led_activelow=off
dtparam=act_led_trigger=none
dtparam=act_led_activelow=off
dtparam=eth_led0=4
dtparam=eth_led1=4
[all]
display_auto_detect=1
#display 7Zoll
# raspi 4
#dtoverlay=vc4-kms-v3d-pi4,nohdmi
#dtoverlay=vc4-kms-dsi-ili9881-7inch
#Raspi 5:
dtoverlay=vc4-kms-dsi-ili9881-7inch,rotation=90
#### Touch Display rotation setting below: do not alter ####
display_lcd_rotate=1
display_hdmi_rotate=1
???
Iâve taken photos but they are essentially identical to the already posted image (2nd) so I do not repost.
Iâve just even tried rotate instead of rotation
dtoverlay=vc4-kms-dsi-ili9881-7inch,rotate=90
Regards,
Ralf
Just found a hint for /boot/cmdline.txt:
Add video=DSI-1:800x480@60,rotate=90 to /boot/cmdline.txt
does something like this make sense?
Regards,
Ralf