00:30
omac777_2022 has quit [Quit: Leaving]
01:06
davidlt[m] has quit [Ping timeout: 252 seconds]
01:06
Eighth_Doctor has quit [Ping timeout: 252 seconds]
01:06
mbohun[m] has quit [Ping timeout: 252 seconds]
01:10
davidlt[m] has joined #fedora-riscv
01:12
Eighth_Doctor has joined #fedora-riscv
01:13
mbohun[m] has joined #fedora-riscv
04:04
<
cwt[m] >
<cwt[m]> "I will document it soon, may..." <- Ah... still didn't do anything yet. A lot of house work and playing with my kids.
06:32
zsun has joined #fedora-riscv
10:09
omac777_2022 has joined #fedora-riscv
10:10
omac777_2022 has quit [Client Quit]
10:29
zsun has quit [Quit: Leaving.]
12:41
zsun has joined #fedora-riscv
13:32
zsun has quit [Quit: Leaving.]
14:35
zsun has joined #fedora-riscv
14:41
camrod[m] has joined #fedora-riscv
14:54
zsun has quit [Quit: Leaving.]
19:18
omac777_2022 has joined #fedora-riscv
19:20
<
omac777_2022 >
unxz Fedora-Developer-37-20221130.n.0-nvme.raw.img.xz
19:21
<
omac777_2022 >
parted Fedora-Developer-37-20221130.n.0-nvme.raw.img print
19:21
<
omac777_2022 >
WARNING: You are not superuser. Watch out for permissions.
19:21
<
omac777_2022 >
Sector size (logical/physical): 512B/512B
19:21
<
omac777_2022 >
Disk /var/home/davidm/ksplay/Fedora-Developer-37-20221130.n.0-nvme.raw.img: 10.7GB
19:21
<
omac777_2022 >
Model: (file)
19:21
<
omac777_2022 >
Partition Table: gpt
19:21
<
omac777_2022 >
Disk Flags:
19:21
<
omac777_2022 >
Number Start End Size File system Name Flags
19:21
<
omac777_2022 >
1 17.4kB 734MB 734MB ext4 boot legacy_boot
19:21
<
omac777_2022 >
2 734MB 10.7GB 10.0GB ext4 rootfs
19:23
<
omac777_2022 >
Plunk that onto the VisionFive 2 nvme and overwrite the nvme boot partition with VF2 boot partition contents.
19:24
<
davidlt[m] >
Yeah, that should work.
19:28
<
omac777_2022 >
rsync --archive Fedora-Developer-37-20221130.n.0-nvme.raw.img davidm@192.168.2.53:/home/davidm/
19:28
<
davidlt[m] >
Well it probably cannot boot from NVMe.
19:28
<
davidlt[m] >
(unless there is PCIe driver in U-Boot + a boot device entry)
19:29
<
omac777_2022 >
I've been told that if I redirect the boot from extlinux.conf it should work. There are reports out there that it does. I just didn't succeed yet.
19:29
<
davidlt[m] >
Unless you are loading /boot partition from SD card, loading initramfs (which incl. PCI driver) and systemd does a magic to detect rootfs partition.
19:29
<
omac777_2022 >
Yes, I am looking the /boot partition form the sd card at the moment.
19:29
<
davidlt[m] >
What do you mean by "redirect"?
19:30
<
davidlt[m] >
U-Boot typically has per-board boot device order.
19:30
<
omac777_2022 >
I don't know what I'm talking about. Please ignore "redirect".
19:30
<
omac777_2022 >
I'm a user not a deep hardware guy.
19:30
<
omac777_2022 >
I don't even have a uart-usb dongle yet.
19:31
<
omac777_2022 >
ok my rsync is on the sdcard. I'm going to dd to the nvme now.
19:32
<
davidlt[m] >
From what I can see U-Boot only looks into MMC.
19:33
<
omac777_2022 >
wipefs --all /dev/nvme0n1
19:34
<
omac777_2022 >
ok, I'll just mount the pseudo filesystems and chroot /mnt into the fedora 37 then for the time being.
19:36
<
davidlt[m] >
Looking at their repo I don't see PCIe driver.
19:36
<
davidlt[m] >
It's listed as WIP (work in progress).
19:36
<
omac777_2022 >
dd if=./Fedora-Developer-37-20221130.n.0-nvme.raw.img of=/dev/nvme0n1 bs=4M status=progress conv=fdatasync
19:36
<
omac777_2022 >
You're right.
19:36
<
omac777_2022 >
sorry for misinforming, but there are others reporting they could somehow.
19:36
<
omac777_2022 >
rvalles I believe reported it.
19:38
<
davidlt[m] >
For the kernel it would work, but U-Boot cannot read the kernel from NVMe (it cannot see /boot partition).
19:38
<
davidlt[m] >
If /boot partition lives on NVMe (that incl. kernel, DTB, initramfs, etc.)
19:39
<
davidlt[m] >
U-Boot will load the all those bits and launch the kernel with that initramfs and DTB. It will pass bootargs too.
19:39
<
davidlt[m] >
You cannot have a single disk solution until PCIe driver is in U-Boot.
19:40
<
davidlt[m] >
You need to split disk image into two separate. /boot lives on MMC, rootfs on NVMe.
19:40
<
davidlt[m] >
So it's "two drive" solution.
19:41
<
omac777_2022 >
ok. Good enough for me :)
19:42
<
omac777_2022 >
So for the time being I should delete that first partition on the nvme :)
19:42
<
omac777_2022 >
I'll do that to prevent anything bad from happening.
19:42
<
davidlt[m] >
I would avoid having two identical /boot partition on MMC and NVMe.
19:43
<
davidlt[m] >
That really confused people long time ago when we were doing it on Unmatched in early days.
19:43
<
omac777_2022 >
parted /dev/nvme0n1 print free
19:43
<
davidlt[m] >
That's because users didn't check which one gets mounted as /boot.
19:43
<
omac777_2022 >
Warning: Not all of the space available to /dev/nvme0n1 appears to be used, you can fix the GPT to use all of the space (an extra 479146672 blocks) or continue with the current setting?
19:43
<
omac777_2022 >
Fix/Ignore?
19:43
<
omac777_2022 >
I answered Fix
19:44
<
omac777_2022 >
Model: OSC PCIe 256GB (nvme)
19:44
<
omac777_2022 >
Sector size (logical/physical): 512B/512B
19:44
<
omac777_2022 >
Disk Flags:
19:44
<
omac777_2022 >
Disk /dev/nvme0n1: 256GB
19:44
<
omac777_2022 >
Partition Table: gpt
19:44
<
omac777_2022 >
Number Start End Size File system Name Flags
19:44
<
omac777_2022 >
1 17.4kB 734MB 734MB ext4 boot legacy_boot
19:44
<
omac777_2022 >
2 734MB 10.7GB 10.0GB ext4 rootfs
19:44
<
omac777_2022 >
10.7GB 256GB 245GB Free Space
19:46
<
omac777_2022 >
parted /dev/nvme0n1 rm 1
19:47
<
omac777_2022 >
parted /dev/nvme0n1 resize 2 100%
19:47
<
omac777_2022 >
Error: The resize command has been removed in parted 3.0
19:48
<
omac777_2022 >
parted /dev/nvme0n1 resizepart 2 100%
19:49
<
omac777_2022 >
cat myMountForChroot.sh
19:49
<
omac777_2022 >
# for i in dev dev/pts proc sys run; do umount /mnt/$i; systemctl daemon-reload; done
19:49
<
omac777_2022 >
for i in dev dev/pts proc sys run; do mount -B /$i /mnt/$i; systemctl daemon-reload; done
19:49
<
omac777_2022 >
set -x
19:49
<
omac777_2022 >
set +x
19:50
<
omac777_2022 >
cat myUnmountAfterChroot.sh
19:50
<
omac777_2022 >
# for i in dev dev/pts proc sys run; do mount -B /$i /mnt/$i; systemctl daemon-reload; done
19:50
<
omac777_2022 >
set -x
19:50
<
omac777_2022 >
for i in dev dev/pts proc sys run; do umount /mnt/$i; systemctl daemon-reload; done
19:50
<
omac777_2022 >
set +x
19:55
<
omac777_2022 >
mount /dev/nvme0n1p2 /mnt
19:55
<
omac777_2022 >
cat myMakeChrootPseudoFSDirs.sh
19:55
<
omac777_2022 >
mkdir -p /mnt/dev
19:55
<
omac777_2022 >
set -x
19:55
<
omac777_2022 >
mkdir -p /mnt/dev/pts
19:55
<
omac777_2022 >
mkdir -p /mnt/proc
19:55
<
omac777_2022 >
mkdir -p /mnt/sys
19:55
<
omac777_2022 >
mkdir -p /mnt/run
19:55
<
omac777_2022 >
set +x
19:59
<
omac777_2022 >
./myMakeChrootPseudoFSDirs.sh
19:59
<
omac777_2022 >
./myMountForChroot.sh
20:00
<
omac777_2022 >
chroot /mnt
20:00
<
davidlt[m] >
omac777_2022: could you post long messages into pastebin services?
20:00
<
omac777_2022 >
Sorry about that.
20:00
<
omac777_2022 >
I'm chrooted.
20:01
<
davidlt[m] >
Typically around 3 lines is OK to post. Anything longer should go into some external pastebin service.
20:01
<
davidlt[m] >
If you use Matrix + IRC bridge that will happen automatically.
20:02
<
davidlt[m] >
If you are using a traditional IRC client you will need to do that manually.
20:10
<
omac777_2022 >
../run/systemd/resolve/stub-resolv.conf
20:11
<
omac777_2022 >
I'm trying to add my correct information to dnf install/update.
20:12
<
omac777_2022 >
systemctl start named.service...can't run in the chroot
20:17
<
omac777_2022 >
./service named start...can't run in chroot.
20:21
<
omac777_2022 >
systemd-nspawn -D /mnt/....systemd-nspawn: command not found
20:22
<
omac777_2022 >
apt-get install systemd-container
20:25
<
omac777_2022 >
Ok I need to ensure I'm not mounted on the pseudo filesystems because nspawn will do it for me.
20:25
<
omac777_2022 >
./myUnmountAfterChroot.sh
20:25
<
omac777_2022 >
systemd-nspawn -D /mnt/
20:26
<
omac777_2022 >
And I'm in.
20:28
<
omac777_2022 >
I can't call systemd services...Ok let's try systemd-nspawn -D /mnt /sbin/init
20:38
<
omac777_2022 >
ok with the sbin init, it has access to the services...that's good. But name resolver is on NetworkManager not on named. LOL
20:39
<
omac777_2022 >
nmcli con show
20:39
<
omac777_2022 >
sudo nmcli con modify end0 ipv4.dns "192.168.2.1,207.164.234.129"
20:46
<
omac777_2022 >
sudo dnf install emacs-nox...[Could not resolve host: mirrors.fedoraproject.org]
20:47
<
omac777_2022 >
my name resolver is not configured correctly for sure.
20:55
<
omac777_2022 >
sudo rm /etc/resolv.conf
20:55
<
omac777_2022 >
sudo vi /etc/resolv.conf
21:04
<
omac777_2022 >
LOL emacs was already installed, but the dnf is still having issues.
21:17
<
omac777_2022 >
Within /etc/yum.repos.d, I got rid of all the repos except fedora-riscv-koji.repo
21:17
<
omac777_2022 >
enabled it. and dnf update worked.
21:23
<
omac777_2022 >
dnf upgrade worked!
21:56
<
omac777_2022 >
Ok I can't install podman nor docker directly on riscv64 just yet.
22:04
<
omac777_2022 >
dnf groupinfo "Development Tools"...gives me nothing...Group Development Tools does not exist.
22:55
omac777_2022 has quit [Quit: Leaving]