Public bug reported:
I have a StarFive VisionFive 2 v1.2a board and used the
ubuntu-23.04-preinstalled-server-riscv64+visionfive2.img.xz to install.
I'd noticed the end of the release notes at
https://wiki.ubuntu.com/RISC-V/StarFive%20VisionFive%202 and have
performed those steps.
However, networking does not work. (I'm not alone in this observation;
there's another report of this on the rvspace forum.)
The red light near the power connector is lit. Only the orange light on
the network connector (the one near the edge) is flashing.
Henrick advised 'ip -a' but that's not recognized. In my original message, I
offered:
$ sudo ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether XXX39 brd ff:ff:ff:ff:ff:ff
inet6 XXX39/64 scope link
valid_lft forever preferred_lft forever
3: end1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group
default qlen 1000
link/ether XXX:3a brd ff:ff:ff:ff:ff:ff
root@ubuntu:/etc/netplan# ip -a
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
ip [ -force ] -batch filename
where OBJECT := { address | addrlabel | amt | fou | help | ila | ioam | l2tp |
link | macsec | maddress | monitor | mptcp | mroute | mrule |
neighbor | neighbour | netconf | netns | nexthop | ntable |
ntbl | route | rule | sr | tap | tcpmetrics |
token | tunnel | tuntap | vrf | xfrm }
OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
-h[uman-readable] | -iec | -j[son] | -p[retty] |
-f[amily] { inet | inet6 | mpls | bridge | link } |
-4 | -6 | -M | -B | -0 |
-l[oops] { maximum-addr-flush-attempts } | -br[ief] |
-o[neline] | -t[imestamp] | -ts[hort] | -b[atch] [filename]
|
-rc[vbuf] [size] | -n[etns] name | -N[umeric] | -a[ll] |
-c[olor]}
As advised, USB is not working, so the WiFi card isn't recognized, of course. I
don't know how a normal person would attach a keyboard if not through a
USB/Serial bridge as I have, but that's not very satisfactory in X due to the
absence of things like modifier keys. That's a different problem for now.
I think the rare case here is 1.2a - these earlybird boards must be
uncommon. The list isn't being stormed with reports, so the 1.3 boards
must be succeeding. Reports of this issue on rvspace are getting no
answers.
I've swapped network cabling and am sure the cable works and is plugged
into a functional network.
I've re-installed from media twice. There are no actual prompts to mess
up, so I'm a bit baffled.
I suspect DT isn't identifying the hardware correctly somehow, but I
lack the device tree mojo to stare that down.
Troubleshooting advice welcome.
# lsb_release -rd
No LSB modules are available.
Description: Ubuntu Lunar Lobster (development branch)
Release: 23.04
Filing it as a bug and not a support question because a fresh install to
hardware of a relatively known/limited hardware options like this should result
in at least minimally working networking. That's just table stakes in modern
times.
Expected: Glorious networking flowing freely over the wires.
Observed: Not even a DHCP grant requested.
Thank you!
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/2019444
Title:
StarFive VisionFive 2 v1.2a board: no networking after ISL
Status in linux-riscv package in Ubuntu:
New
Bug description:
I have a StarFive VisionFive 2 v1.2a board and used the
ubuntu-23.04-preinstalled-server-riscv64+visionfive2.img.xz to
install. I'd noticed the end of the release notes at
https://wiki.ubuntu.com/RISC-V/StarFive%20VisionFive%202 and have
performed those steps.
However, networking does not work. (I'm not alone in this observation;
there's another report of this on the rvspace forum.)
The red light near the power connector is lit. Only the orange light
on the network connector (the one near the edge) is flashing.
Henrick advised 'ip -a' but that's not recognized. In my original message, I
offered:
$ sudo ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether XXX39 brd ff:ff:ff:ff:ff:ff
inet6 XXX39/64 scope link
valid_lft forever preferred_lft forever
3: end1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
group default qlen 1000
link/ether XXX:3a brd ff:ff:ff:ff:ff:ff
root@ubuntu:/etc/netplan# ip -a
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
ip [ -force ] -batch filename
where OBJECT := { address | addrlabel | amt | fou | help | ila | ioam | l2tp
|
link | macsec | maddress | monitor | mptcp | mroute |
mrule |
neighbor | neighbour | netconf | netns | nexthop | ntable |
ntbl | route | rule | sr | tap | tcpmetrics |
token | tunnel | tuntap | vrf | xfrm }
OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
-h[uman-readable] | -iec | -j[son] | -p[retty] |
-f[amily] { inet | inet6 | mpls | bridge | link } |
-4 | -6 | -M | -B | -0 |
-l[oops] { maximum-addr-flush-attempts } | -br[ief] |
-o[neline] | -t[imestamp] | -ts[hort] | -b[atch]
[filename] |
-rc[vbuf] [size] | -n[etns] name | -N[umeric] | -a[ll] |
-c[olor]}
As advised, USB is not working, so the WiFi card isn't recognized, of course.
I don't know how a normal person would attach a keyboard if not through a
USB/Serial bridge as I have, but that's not very satisfactory in X due to the
absence of things like modifier keys. That's a different problem for now.
I think the rare case here is 1.2a - these earlybird boards must be
uncommon. The list isn't being stormed with reports, so the 1.3 boards
must be succeeding. Reports of this issue on rvspace are getting no
answers.
I've swapped network cabling and am sure the cable works and is
plugged into a functional network.
I've re-installed from media twice. There are no actual prompts to
mess up, so I'm a bit baffled.
I suspect DT isn't identifying the hardware correctly somehow, but I
lack the device tree mojo to stare that down.
Troubleshooting advice welcome.
# lsb_release -rd
No LSB modules are available.
Description: Ubuntu Lunar Lobster (development branch)
Release: 23.04
Filing it as a bug and not a support question because a fresh install to
hardware of a relatively known/limited hardware options like this should result
in at least minimally working networking. That's just table stakes in modern
times.
Expected: Glorious networking flowing freely over the wires.
Observed: Not even a DHCP grant requested.
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2019444/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
