Pleased to announce that we made Alpine Linux boot and work with mainline u-boot, opensbi and linux kernel, with some patches for u-boot and more patches for kernel.
Yes (switch: 1 is up=off, 2 is down=on)
could you break u-boot to get prompt (pressing enter while it count down timeout before menu) and issue version command and post what it says?
Also, result of printenv fdtfile command would be useful to see.
You are first who test this image with v1.2a board so all information would be useful for better testing and debugging. BTW, /dev/fb0 (framebuffer) not present but supported in Debian kernel from VF2. How 2 enable?
We are using only mainline tools/software, i.e. u-boot, opensbi and kernel (with some patches), while Debian/starfive use kernel 5.15 with vendor (starfive) drivers and patches which are not yet upstream-ed to mainline kernel.
There is no DRM driver in mainline kernel yet and because this there is no/dev/fb0
We hope that with kernel 6.6 DRM driver will work
You are first who test this image with v1.2a board so all information would be useful for better testing and debugging.
BTW, /dev/fb0 (framebuffer) not present but supported in Debian kernel from VF2. How 2 enable?
We are using only mainline tools/software, i.e. u-boot, opensbi and kernel (with some patches), while Debian/starfive use kernel 5.15 with vendor (starfive) drivers and patches which are not yet upstream-ed to mainline kernel.
There is no DRM driver in mainline kernel yet and because this there is no/dev/fb0
We hope that with kernel 6.6 DRM driver will work
Likewise. I use a Smalltalk IDE in a framebuffer as its own window system (Cuis Smalltalk includes SVG, unicode, and truetype fonts), so I am very interested in getting /dev/fb0.
All looks good and it is very strange it didn’t boot automatically your board properly.
Likewise. I use a Smalltalk IDE in a framebuffer as its own window system (Cuis Smalltalk includes SVG, unicode, and truetype fonts), so I am very interested in getting /dev/fb0.
I like Alpine. Thanks much for this!
You can join alpine IRC channel #alpine-riscv64 on OFTC where we discuss riscv and alpine, it is low in traffic
Hmmm… Clean vf2.img and select alpine option 3 (vf1.2a) allows eth1, but apk update seems to kill this. Clue?
rv64alpine:~# rc-service networking restart
* WARNING: you are stopping a boot service
* Stopping chronyd ... [ ok ]
* Stopping networking ...
* lo ...
* Starting networking ...
* lo ... [ ok ]
* eth1 ...
ip: ioctl 0x8913 failed: No such device
udhcpc: ioctl 0x8933 failed: No such device
ifup: failed to change interface eth1 state to 'up'
No no no. I did a few apk adds then an apk update and rebooted. After reboot, Eth1 is unavailable.
rv64alpine:~# rc-service networking restart
* WARNING: you are stopping a boot service
* Stopping chronyd ... [ ok ]
* Stopping networking ...
* lo ...
* Starting networking ...
* lo ... [ ok ]
* eth1 ...
ip: ioctl 0x8913 failed: No such device
udhcpc: ioctl 0x8933 failed: No such device
ifup: failed to change interface eth1 state to 'up'
apk update just update local packages database, it doesn’t upgrade any package.
apk upgrade upgrade all available packages to new versions.
So, if you didn’t upgrade kernel then modules are not removed.
What uname -a and lsmod says after reboot.
Also, I noticed that ethernet interface couldn’t be brought up if cable is not plugged in.
Check this by ip link set dev eth0 up without cable plugged.