Regular/riscv64: Difference between revisions

From ALT Linux Wiki
No edit summary
 
(8 intermediate revisions by 3 users not shown)
Line 6: Line 6:
|}
|}


[[Regular|Regular image]] builds are intended to test and develop the [[Ports/riscv64|RISC-V (rv64gc) port]] of [[Sisyphus]] repository.
[[Regular|Regular image]] builds are intended for testing and development of the [[Ports/riscv64|RISC-V (rv64gc) port]] of [[Sisyphus]] repository.


Additional information:
Additional information:
* on Regular images: [[Regular]];
* on Regular images: [[Regular]];
* on riscv64 Sisyphus port: [[Ports/riscv64]];
* on riscv64 Sisyphus port: [[Ports/riscv64]];
* #Feedback.
* [[#Feedback]].


Аfter booting from one of the images below, use the following credentials to login:  
The images are intended to be run in qemu without modification and written according to the instructions to removable storage devices for sequent loading on target boards. Аfter booting from one of the images below, use the following credentials to login:  


   login: root
   login: root
   password: alt
   password: altlinux


For the recent images with graphics support (both [https://en.wikipedia.org/wiki/Xfce XFCE] and [https://ru.wikipedia.org/wiki/MATE MATE]), these credentials work at the first boot. All the images with graphics support have a graphical setup wizard that is activated on the first boot and allows to do initial configuration of the system, including setting the root password, via GUI.
For images with graphics the user will be asked to complete the initial setup in a graphical setup wizard at the first boot. During configuration, you can set the timezone, root password, password for connecting to VNC (if launched via VNC), create a new user, etc. On boards without a graphics adapter the graphical setup wizard must be run via VNC.


The developer image ('''builder''') has another pre-created user:
== Download ==


  login: altlinux
=== '''Direct download links''' ===
  password: alt


{{Attention|It is highly recommended to '''change the password''' right after the first log-in into the system.}}
These images are marked as '''tested''':
 
* jeos-systemd: [http://nightly.altlinux.org/sisyphus-riscv64/tested/regular-jeos-systemd-latest-riscv64.img.xz riscv64] <ref>No GUI </ref>
 
* lxqt: [http://nightly.altlinux.org/sisyphus-riscv64/tested/regular-lxqt-latest-riscv64.img.xz riscv64]
 
* mate: [http://nightly.altlinux.org/sisyphus-riscv64/tested/regular-mate-latest-riscv64.img.xz riscv64]
 
* xfce: [http://nightly.altlinux.org/sisyphus-riscv64/tested/regular-xfce-latest-riscv64.img.xz riscv64]


== HiFive Unmatched and Unleashed ==


For [[HiFive Unmatched]] and [[HiFive Unleashed]] boards we recommend fresh images build by jqt4@: http://ftp.altlinux.org/pub/people/jqt4/images/hifive/
=== Additional downloads ===


Setup instructions are available on the corresponding board page: [[HiFive Unmatched]], [[HiFive Unleashed]]
Some additional images  are available on http://nightly.altlinux.org/sisyphus-riscv64/:


See [[#VNC]] section below on how to access graphical setup for Xfce and MATE images.
* images in other formats (e.g. rootfs tarballs, or ISO images with installer);
* stapshots -- builds from the past weeks, and the newest images that were not tested yet (if any).


== QEMU ==
== QEMU ==
The images for the [https://www.qemu.org QEMU] listed below:
* Minimal system with systemd -- [http://nightly.altlinux.org/sisyphus-riscv64/alpha/regular-jeos-systemd-latest-riscv64.qcow2c link] ([http://nightly.altlinux.org/sisyphus-riscv64/alpha/MD5SUM MD5], [http://nightly.altlinux.org/sisyphus-riscv64/alpha/SHA1SUM SHA1])
* Minimal sytem with SysV -- [http://nightly.altlinux.org/sisyphus-riscv64/alpha/regular-jeos-sysv-latest-riscv64.qcow2c link] ([http://nightly.altlinux.org/sisyphus-riscv64/alpha/MD5SUM MD5], [http://nightly.altlinux.org/sisyphus-riscv64/alpha/SHA1SUM SHA1])
* Minimal system for developer (rpmbuild, [https://www.altlinux.org/Hasher hasher], gcc, ssh) -- [http://nightly.altlinux.org/sisyphus-riscv64/alpha/regular-builder-latest-riscv64.qcow2c link] ([http://nightly.altlinux.org/sisyphus-riscv64/alpha/MD5SUM MD5], [http://nightly.altlinux.org/sisyphus-riscv64/alpha/SHA1SUM SHA1])
* Graphical system with XFCE (VNC, X11) -- [http://nightly.altlinux.org/sisyphus-riscv64/alpha/regular-xfce-latest-riscv64.qcow2c link] ([http://nightly.altlinux.org/sisyphus-riscv64/alpha/MD5SUM MD5], [http://nightly.altlinux.org/sisyphus-riscv64/alpha/SHA1SUM SHA1])


The instructions on how to run these images on QEMU are on a separate page: [[Ports/riscv64/QEMU]].
The img.xz images must be unpacked and run according to the instructions: [[Ports/riscv64/QEMU]].
 
== HiFive Unmatched and Unleashed ==


See [[#VNC]] section below on how to access graphical setup for images with graphics support.
Images write in instructions are available on the board pages: [[HiFive Unmatched]] and [[HiFive Unleashed]].  


== VNC ==
== VNC ==
Xfce and MATE images include a setup wizard that is activated on first boot. It allows to do the initial system setup, including selecting the timezone, setting the root password, creating a new user, setting VNC password, etc.


In the case of QEMU, if port forwarding for port 5900 is used, connecting to VNC is straightforward. For example, in the case of [https://en.wikipedia.org/wiki/TigerVNC tigerVNC]:
Images with graphical desktop environments provide an option to work remotely via VNC, which is especially useful if your board does not have a (working) video card. To use this option:
<source lang="shell">
 
$ vncviewer 127.0.0.1
* enable vnc mode in alterator-setup by uncommenting or adding a line to /etc/alterator-setup/config:
</source>
 
<source lang="shell">ALTERATOR_SETUP_VNC=1</source>


"Real" machines (e.g. HiFive Unmatched board) obtain the IP address via DHCP, and one needs to find out that address to connect to the VNC server.
or add a --vnc=1 argument for alt-rootfs-installer when it writes to a removable storage device.


One way to do it is to connect to the board serial console. For HiFive boards, you should connect your PC to the console port (microUSB) and use, for example, <tt>screen</tt> command:
* connect to the board's serial port and wait for the information about the board network address and the VNC connection password:
<source lang="shell">
<source lang="shell">
$ screen /dev/ttyUSB1 115200
localhost login: ALTERATOR SETUP === VNC access enabled
ALTERATOR SETUP === VNC Password="cobra-angel"
ALTERATOR SETUP === Default network device: "eth0"
ALTERATOR SETUP === IPv4: "10.0.2.15/24"
ALTERATOR SETUP === IPv6: "fec0::bee1:6f2d:ce4a:9c1d/64
fe80::6a0:ddd0:df03:e44d/64"
PORT=5900
</source>
</source>


During first boot the IPv4 and IPv6 addresses will be print to the console. It looks like this:
To connect to a serial console (usually /dev/ttyUSB1) you can use GNU/screen:
<source lang="shell">
<source lang="shell">
[  128.084540] xinit[276]: ALTERATOR SETUP === Default device: "eth0"
$ screen /dev/ttyUSB1 115200
[  128.084888] xinit[276]: ALTERATOR SETUP === IPv4: "192.168.88.216/24"
[  128.085110] xinit[276]: ALTERATOR SETUP === IPv6: "fe80::72b3:d5ff:fe92:f229/64"
</source>
</source>


You can use any of these addresses to connect to the VNC server, for example:
* connect to the VNC server. You can use <tt>remote-viewer</tt> -- a VNC client from the virt-viewer package:
<source lang="shell">
<source lang="shell">$ remote-viewer vnc://<ip_address>:<Port></source>
$ vncviewer 192.168.88.216
</source>


== Feedback ==
== Feedback ==


'''• Bug reports''' are tracked at [https://bugzilla.altlinux.org ALT Linux Team bugzilla] (see also: [[BugTracking]]):
'''• Bug reports''' are tracked at [https://bugzilla.altlinux.org ALT Linux Team bugzilla] (see also: [[BugTracking]]):
* In the case of any issue with a package please choose product ''Sisyphus''.
* In the case of any issue with a package choose product ''Sisyphus''.
* In the case of an issue with the images please choose product ''Regular'' .
* In the case of an issue with the images choose product ''Regular'' .


'''IMPORTANT''':
'''IMPORTANT''':
Line 83: Line 90:
* assign the issue to <tt>iv@altlinux.org</tt>.
* assign the issue to <tt>iv@altlinux.org</tt>.


'''• Mailing list:''' riscv-devel@lists.altlinux.org
'''• Mailing list:''' [https://lists.altlinux.org/mailman/listinfo/riscv-devel riscv-devel@lists.altlinux.org]
 
== Footnotes ==


[[Category:Sisyphus]]
[[Category:Regular]]
[[Category:RISC-V]]
[[ru:Regular/riscv64]]
[[ru:Regular/riscv64]]
[[Category:Regular]]
[[Category:Sisyphus]]

Latest revision as of 09:15, 27 January 2023

Русский

Regular image builds are intended for testing and development of the RISC-V (rv64gc) port of Sisyphus repository.

Additional information:

The images are intended to be run in qemu without modification and written according to the instructions to removable storage devices for sequent loading on target boards. Аfter booting from one of the images below, use the following credentials to login:

 login: root
 password: altlinux

For images with graphics the user will be asked to complete the initial setup in a graphical setup wizard at the first boot. During configuration, you can set the timezone, root password, password for connecting to VNC (if launched via VNC), create a new user, etc. On boards without a graphics adapter the graphical setup wizard must be run via VNC.

Download

Direct download links

These images are marked as tested:


Additional downloads

Some additional images are available on http://nightly.altlinux.org/sisyphus-riscv64/:

  • images in other formats (e.g. rootfs tarballs, or ISO images with installer);
  • stapshots -- builds from the past weeks, and the newest images that were not tested yet (if any).

QEMU

The img.xz images must be unpacked and run according to the instructions: Ports/riscv64/QEMU.

HiFive Unmatched and Unleashed

Images write in instructions are available on the board pages: HiFive Unmatched and HiFive Unleashed.

VNC

Images with graphical desktop environments provide an option to work remotely via VNC, which is especially useful if your board does not have a (working) video card. To use this option:

  • enable vnc mode in alterator-setup by uncommenting or adding a line to /etc/alterator-setup/config:
ALTERATOR_SETUP_VNC=1

or add a --vnc=1 argument for alt-rootfs-installer when it writes to a removable storage device.

  • connect to the board's serial port and wait for the information about the board network address and the VNC connection password:
localhost login: ALTERATOR SETUP === VNC access enabled
ALTERATOR SETUP === VNC Password="cobra-angel"
ALTERATOR SETUP === Default network device: "eth0"
ALTERATOR SETUP === IPv4: "10.0.2.15/24"
ALTERATOR SETUP === IPv6: "fec0::bee1:6f2d:ce4a:9c1d/64
fe80::6a0:ddd0:df03:e44d/64"
PORT=5900

To connect to a serial console (usually /dev/ttyUSB1) you can use GNU/screen:

$ screen /dev/ttyUSB1 115200
  • connect to the VNC server. You can use remote-viewer -- a VNC client from the virt-viewer package:
$ remote-viewer vnc://<ip_address>:<Port>

Feedback

• Bug reports are tracked at ALT Linux Team bugzilla (see also: BugTracking):

  • In the case of any issue with a package choose product Sisyphus.
  • In the case of an issue with the images choose product Regular .

IMPORTANT:

  • set platform field (drop-down list at the right) to riscv64;
  • assign the issue to iv@altlinux.org.

• Mailing list: riscv-devel@lists.altlinux.org

Footnotes

  1. No GUI