- The added line is THIS COLOR.
- The deleted line is THIS COLOR.
#author("2023-05-09T11:57:46+09:00","","")
#author("2024-08-22T22:33:22+09:00","","")
*Do you have any message for us? [#z65bec72]
To avoid posts by spam, a message body without the word ''#FuguIta'' is rejected. Please include the word in your message text. ~
URLs in the body of the message will also be judged as spam. If you wish to express a URL, please omit the scheme (http://, https://, etc.).
----
#contents
----
#article
**mfs stays at 1024M [#lfa0876f]
>[[Santos]] (2024-07-27 (Sat) 07:19:56)~
~
Hi,~
~
I'm using #FuguIta i386, booting from a 2GB compact flash adaptor. I can boot with it, no problem. I have a uniprocessor laptop x32 with 3GB of RAM. At boot time. Whenever I try to assign more memory for 'mfs' the amount defaults to 1024M. If I do: 2048M, 100% or 100%%. The boot message indicates: set mfs size to 1024MB. No matter what I do mfs stays at 1GB.~
~
Couple of question. What exactly is mfs? I know is the memory filesystem, but what does that mean? will it hold all files in the filesystem, like /root files and packages I install? can be extended after boot? is it only for files?~
~
#FuguIta does detects my 3GB of RAM but refuses to assign more than 1024MB to mfs. In linux usually there is no need to assign any percentage to the filesystem and to RAM memory. The more files I put in ram, the less RAM I have to run programs. It's the same space for files and memory for programs to run. Can It be the same for FuguIta? I make the comparison, linux is my main point of reference.~
//
- The limitation of only allocating a maximum of 1GB of space in mfs is an OpenBSD/i386 limitation, caused by the implementation of a memory protection mechanism called W^X on the i386 platform. For a detailed discussion, see [[these articles>https://marc.info/?l=openbsd-misc&m=165156014421856&w=2]].~
About mfs of OpenBSD, see [[the manpage>https://man.openbsd.org/mount_mfs]] for OpenBSD's mfs and [[a description of FuguIta's mfs-centric file system layout>FuguItaGuide/3-Operation#content_1_11]].~
The more files you put in mfs, the less RAM you need to run your programs, both in Linux and FuguIta. However, the resources of memory required to run the program can be mitigated by making a swap partition.
~-- [[kaw]] &new{2024-07-27 (Sat) 11:32:41};
- I'll check them out, thanks! #FuguIta -- [[Santos]] &new{2024-07-27 (Sat) 15:28:54};
- Alternatively, you could [[remaster #FuguIta, which uses tmpfs instead of mfs>FuguItaGuide/3-Operation#e78a60b2]]. Note that this method does not have the 1GB size limit for i386, but may panic if the swap partition is frequently page in/page out. -- [[kaw]] &new{2024-07-27 (Sat) 15:45:37};
- Okay, I read all the links you provided. You tell me if I got this correctly. 1) mfs is a system that is limit to 1024M. That means installing chromium is not possible using RAM only, correct? / 2) Based on what I understood, swap is available only if there is a drive attached since I have to format a partition a disk to get a swap partition set up to be activated later on. Am I right? / 3) My system has 3G of RAM. Does that means if I fill out all my 1024M I cannot do anything else even though I still have 2048M of freem RAM to get programs running? #FuguIta -- [[Santos]] &new{2024-07-30 (Tue) 11:52:12};
- I did not mention it, but I rather stay with mfs over tmpfs. I prefer stability. #FuguIta -- [[Santos]] &new{2024-07-30 (Tue) 11:54:32};
-A1) Yes, on the i386 platform this is correct.~
~
A2) Correct. To be precise, it is possible to create a swap partition even after it has been formatted, making full use of fdisk and disklabel.~
~
A3) There are several solutions.~
--create a new partition on your disk device (including FuguIta LiveUSB itself) and [[mount this on /usr/local>FuguItaGuide/3-Operation#fstab_tail]].~
Applications added with pkg_add will be placed under /usr/local, so mounting the disk device here will not consume mfs.~
--Alternatively, install regular OpenBSD instead of FuguIta. This may be easiest.~
--There are some ways to solve this problem with on-memory only.
+++Add several more mfs mounts.
+++Fill the created mfs file system with a single file.
+++Bind these files to the vnode device with vnconfig.
+++Create RAID partitions on these vnode devices.
+++Combine these RAID partitions as a single disk device with the bioctl utility.
+++Create an FFS partition on this RAID-concatenated device and mount it in /usr/local.
>This is a very complicated method and is not recommended. You will also need to automate the way you configure this disk device and implement your own means of saving and restoring files on the device.~
At the very least, you should be able to see the following example implementation and understand its contents.
test# uname -a
OpenBSD test.local 7.5 RDROOT.MP#19 i386
test# top -b 5
load averages: 0.05, 0.01, 0.01 test.local 07:41:44
33 processes: 32 idle, 1 on processor up 0 days 01:06:55
CPU states: 1.7% user, 0.0% nice, 1.9% sys, 0.1% spin, 2.4% intr, 94.0% idle
Memory: Real: 1739M/2803M act/tot Free: 195M Cache: 334M Swap: 16M/16M
PID USERNAME PRI NICE SIZE RES STATE WAIT TIME CPU COMMAND
65593 root 10 0 769M 744M idle mfsidl 0:06 0.00% mount_mfs
61622 root 10 0 769M 357M sleep mfsidl 0:04 0.00% mount_mfs
74185 root 10 0 769M 348M sleep mfsidl 0:03 0.00% mount_mfs
72783 root 18 0 1380K 896K sleep sigsusp 0:02 0.00% ksh
23542 _ntp 2 -20 1420K 1396K sleep kqread 0:00 0.00% ntpd
test# mount
/dev/rd0a on / type ffs (local)
/dev/sd0a on /sysmedia type ffs (local, read-only)
/dev/vnd5a on /fuguita type ffs (local, read-only)
mfs:19329 on /ram type mfs (local, wxallowed, size=524288 512-blocks)
mfs:74185 on /ram/root/mfs/0 type mfs (asynchronous, local, size=1572864 512-blocks)
mfs:61622 on /ram/root/mfs/1 type mfs (asynchronous, local, size=1572864 512-blocks)
mfs:65593 on /ram/root/mfs/2 type mfs (asynchronous, local, size=1572864 512-blocks)
/dev/sd1d on /ram/usr/local type ffs (local)
test# vnconfig -l
vnd0: covering 0/fill on ??, inode 3
vnd1: covering 1/fill on ??, inode 3
vnd2: covering 2/fill on ??, inode 3
vnd3: not in use
vnd4: not in use
vnd5: covering /sysmedia/fuguita-7.5-i386.ffsimg on sd0a, inode 4
test# ls -l /root/mfs/*/*
-rw-r--r-- 1 root wheel 778272768 Jul 30 06:56 /root/mfs/0/fill
-rw-r--r-- 1 root wheel 778272768 Jul 30 06:56 /root/mfs/1/fill
-rw-r--r-- 1 root wheel 778272768 Jul 30 06:54 /root/mfs/2/fill
test# bioctl softraid0
Volume Status Size Device
softraid0 0 Online 2333810688 sd1 CONCAT
0 Online 777936896 0:0.0 noencl <vnd0d>
1 Online 777936896 0:1.0 noencl <vnd1d>
2 Online 777936896 0:2.0 noencl <vnd2d>
test# df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/rd0a 1.5M 927K 625K 60% /
/dev/sd0a 900M 891M 9.1M 99% /sysmedia
/dev/vnd5a 871M 865M 5.1M 100% /fuguita
mfs:19329 247M 39.6M 195M 17% /ram
mfs:74185 743M 743M -37.1M 106% /ram/root/mfs/0
mfs:61622 743M 743M -37.1M 106% /ram/root/mfs/1
mfs:65593 743M 743M -37.1M 106% /ram/root/mfs/2
/dev/sd1d 2.1G 1.1G 877M 58% /ram/usr/local
test# ls /var/db/pkg
adwaita-icon-theme-45.0 libiconv-1.17
aom-3.8.3 librsvg-2.57.2
at-spi2-core-2.50.1 libudev-openbsd-20230921p0
avahi-libs-0.8p3 libvpx-1.14.1v0
bzip2-1.0.8p0 libxkbcommon-1.6.0p0
cairo-1.18.0 libxml-2.12.9
chromium-122.0.6261.111p0 libxslt-1.1.39
cups-libs-2.4.7 lz4-1.9.4
dav1d-1.2.1p3 lzo2-2.10p2
dbus-1.14.10v0 noto-emoji-20211101
dconf-0.40.0p0 noto-fonts-20201206
desktop-file-utils-0.27 nspr-4.35
epoll-shim-0.0.20230411 nss-3.98
fribidi-1.0.13 openh264-2.4.1p1
gdk-pixbuf-2.42.10 opus-1.4
gettext-runtime-0.22.5 pango-1.52.1
glib2-2.78.6 pcre2-10.37p2
graphite2-1.3.14 png-1.6.43
gtk+3-3.24.41 pv-1.8.0
gtk+3-cups-3.24.41 python-3.10.14
gtk4-update-icon-cache-4.12.5 quirks-7.14
harfbuzz-8.3.0 rlwrap-0.46.1
hicolor-icon-theme-0.17 rsync-3.2.7p1
icu4c-74.2v0 shared-mime-info-2.4
intel-firmware-20240514v0 sqlite3-3.44.2
jpeg-3.0.2v0 tiff-4.6.0
libevent-2.1.12p0 updatedb-0p0
libexif-0.6.24 wayland-1.22.0p0
libffi-3.4.4p1 xdg-utils-1.2.1
libgcrypt-1.10.3p1 xz-5.4.5
libgpg-error-1.48 zstd-1.5.5
I have included this just to show that it is not impossible.~
...and for your interest.
~-- [[kaw]] &new{2024-07-30 (Tue) 16:38:12};
- Thank you very much. It is exactly what I also wondered about. Whether there was a way to mount multiple points to not be limited by the hard coded 1024M. Very interesting the output you posted. I'll check how I can do it. Installing OpenBSD is definitively a solution but a live system like #FuguIta is what works for me since I can break the system (which has happened a lot recently) and just restart and boot again instead of reinstalling the entire OS. For now I'm not in a hurry to save any kind of files I would like to go step by step and get the mfs expanded first. -- [[Santos]] &new{2024-08-05 (Mon) 23:41:58};
- By the way. If I'm correct, that output is like my set up. 3GB of RAM and 3 mfs mounted in a RAID configuration. All in memory (RAM). Correct? #FuguIta -- [[Santos]] &new{2024-08-06 (Tue) 02:08:57};
- You are correct. In addition, don't forget to create a single file with the largest size in each mfs and associate it with the vnode device in vnconfig. #FuguIta -- [[kaw]] &new{2024-08-09 (Fri) 10:47:58};
- @Santos, don;t waste your time, pkg_add does not even work for me, can't find the command! lolz #FuguIta -- [[chris]] &new{2024-08-22 (Thu) 22:33:22};
#comment
**How to install firefox? [#t73672b6]
>[[Santos]] (2024-07-19 (Fri) 23:43:36)~
~
Loving #FuguIta, trying to learn by doing but I hit a wall. I can't do: 'pkg_add firefox'. It can't be located. I tried setting up a mirror with the PKG_PATH, didn't work. What is changing in FuguIta from any regular OpenBSD install? And How can I install firefox? RAM is no problem.~
~
Thanks!~
//
-Please describe the problem in detail (with exact error message, etc.).~
There are several possible reasons:
-- Is the PC clock accurate? - If the system time is incorrect, TLS communication will fail.
-- Check the /etc/installurl file. It is common now to use installurl instead of $PKG_PATH when running pkg_add.
-- Firefox packages are not already provided for the i386 platform.
>#FuguIta has no special mechanism for pkg_add.~
Again, please be specific about the problem.
~-- [[kaw]] &new{2024-07-21 (Sun) 20:04:35};
- You nailed it. I'm using i386. Sorry for the lack of details. PC clock is accurate. PKG_PATH is correct (I can download other packages). Good to know #FuguIta is streamlined. So firefox is not available as a package. Excuse my linux lingo, but are there repos out there that provide i386 firefox packages? -- [[Santos]] &new{2024-07-25 (Thu) 04:35:57};
- See the ports source repository - https://github.com/openbsd/ports/commit/86d76bdc ~
FireFox builds are disabled on the i386 platform for reasons of not providing enough memory. ~
If you really want FireFox for i386, you have to modify the ports and build it by yourself (I don't know it's possible...). ~
Otherwise, you will have to use other browsers such as chromium or ungoogled-chromium. -- [[kaw]] &new{2024-07-25 (Thu) 05:30:31};
- I see. Good to know I still have options. Thank you for taking the time to help. Long live #FuguIta -- [[Santos]] &new{2024-07-25 (Thu) 06:41:09};
#comment
**Safe Graphics Mode? [#cc7f94e6]
>[[Santos]] (2024-06-01 (Sat) 19:43:23)~
~
As per your previous post.~
~
"firmware that has no effect" (2023-10-09 (Mon) 13:53:36)~
~
There seems to be the process to resolved the issue with Radeon graphics cards, but that assumes an active internet connection, plus I do not know in which boot stage should be done.~
~
So, in order to avoid that, is there any 'Safe Graphic Mode' or a way to start a graphic environment without having to rely on the graphic chip?~
~
Thank you for #FuguIta!~
//
- Do you have any problems with it? If so, could you elaborate on your case?&br;#FuguIta -- [[kaw]] &new{2024-06-02 (Sun) 19:11:15};
- Yes, I have an issue. I have a laptop with an integrated Radeon card (AMD CPU). I had no problems setting up the USB device to boot from. The first screen I got is the kernel selection, I have tried with both the single core and multiple core kernel but once I select the kernel I can't pass the boot sequence. #FuguIta gets stuck when loading the Radeon driver. I'll add the error messages in a second message. Thank you for your patience. :) -- [[Santos]] &new{2024-06-03 (Mon) 00:29:57};
- #FuguIta radeondrm0: KABINI cik_cp: Failed to load firmware "radeon/KABINI_pfp.bin" [drm] *ERROR* Failed to load firmware! drm:pid0:radeondrm_attachhook *ERROR* Fatal error during GPU init drm0 detached radeondrm0 detached amdgpu0 at pci0 dev 1 function 0 "ATI Kabini" rev 0x00 drm0 at amdgpu0 amgpu0: msi [drm] *ERROR* amdgpu_discovery_init failed drm:pid0:amdgpu_driver_load_kms *ERROR* Fatal error during GPU init -- [[Santos]] &new{2024-06-03 (Mon) 02:18:13};
- #FuguIta The laptop has no issues with linux in framebuffer mode and when I load the drivers, I have no errors and the graphics are initiated without issues. So, it likely is not a hardware error. -- [[Santos]] &new{2024-06-03 (Mon) 02:19:51};
- What happens if you avoid using radeomdrm0 in the following way? #FuguIta -- [[kaw]] &new{2024-06-03 (Mon) 11:02:54};
>> OpenBSD/amd64 BOOT 3.65
/
>> bsd-fi.mp is for
>> multiprocessor kernel (default).
>> Enter 'bsd-fi' for Uniprocessor.
boot> -c
cannot open hd0a:/etc/random.seed: No such file or directory
booting hd0a:/bsd-fi.mp: 17872725+4297744+2363424+0+1236992 [1555784+128+1398216+1093260]=0x1c72620
entry point at 0xffffffff81001000
[ using 4048416 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2024 OpenBSD. All rights reserved. https://www.OpenBSD.org
OpenBSD 7.5-stable (RDROOT.MP) #15: Sun Jun 2 11:14:48 JST 2024
root@nimbus12.localnet:/opt/fi/7.5/sys/arch/amd64/compile/RDROOT.MP
real mem = 1056952320 (1007MB)
avail mem = 1002065920 (955MB)
User Kernel Config
UKC> disable radeomdrm0
UKC> quit
Continuing...
- #FuguIta Amazing! It worked, there is a typo tough. It should be 'disable radeondrm' and it allows me to boot succesfully, it still prints the *ERROR* message but let's me pass that. Can I load the driver once I fully boot up? The performance (specially for video) is pretty bad. -- [[Santos]] &new{2024-06-03 (Mon) 13:24:19};
- Sorry for my typo.&br;Once #FuguIta is up and running without radeondrm by UKC, try to incorporate KABINI_pfb.bin (and related binaries, if any) into the ramdisk root following the instructions in [[firmware that has no effect>FuguIta/BBS#od721234]].~
This firmware is in the tarball http://firmware.openbsd.org/firmware/7.5/radeondrm-firmware-20240220.tgz . -- [[kaw]] &new{2024-06-03 (Mon) 15:34:44};
- That's fine. Your help pointed me in the right direction. I was happy to get it to work on my computer, plus #FuguIta fulfilled its intent, I'm learning OpenBSD. I'll try to load the driver and see how it goes. -- [[Santos]] &new{2024-06-03 (Mon) 23:34:41};
- :-)&br;-- [[kaw]] &new{2024-06-04 (Tue) 12:19:18};
#comment
**Upcoming release [#v7662427]
>[[kaw]] (2024-05-12 (Sun) 09:17:07)~
~
#FuguIta-7.5-*-202405111~
- OpenBSD 7.5 patch-003 has been applied~
- ISO images for arm64 platform are now available
>This is not an official release, as the arm64 version has not yet been tested on an actual machine (they can be used normally).~
It is placed under the test directory of the [[mirror servers>FuguIta/Download]].~
//
- Glad to know about the ongoing development, your efforts are appreciated! #FuguIta -- [[dude]] &new{2024-06-01 (Sat) 19:30:32};
- Thank you! from #FuguIta -- [[kaw]] &new{2024-06-03 (Mon) 11:07:42};
#comment
**Test version of FuguIta 7.5/arm64 [#u33ea334]
>[[kaw]] (2024-04-19 (Fri) 13:09:13)~
~
Test version of FuguIta-7.5-arm64-* has been uploaded to the mirror.~
~
Now only tested on emulator.~
If you tested this on real RPi3/4, please inform us the result especially about frame buffer and/or X11.~
#FuguIta~
//
#comment
**Test version of FuguIta 7.5/i386 [#gdcc3d8f]
>[[kaw]] (2024-04-14 (Sun) 00:03:24)~
~
Test version of FuguIta-7.5-i386-* has been uploaded to the mirror.~
#FuguIta~
//
#comment
**Test version of FuguIta 7.5/amd64 [#tfd85ef9]
>[[kaw]] (2024-04-12 (Fri) 17:07:03)~
~
[[Test version of FuguIta-7.5-amd64-*>FuguIta/Download]] has been uploaded to the mirror. I'm looking forward to hearing from you!~
~
What I would like to know are:~
-How it works on newer hardware (device detection, X Window, suspend/resume, etc.)~
-Comments and suggestions for improvement using the #FuguIta's original tools etc.~
>Thank you in advance.~
//
- Please fix typo s/7\.4/7.5/ #FuguIta -- [[hoge]] &new{2024-04-13 (Sat) 05:55:03};
- fixed. thank you #FuguIta -- [[kaw]] &new{2024-04-13 (Sat) 07:44:00};
#comment
**New build tools released [#baf9d135]
>[[kaw]] (2023-12-20 (Wed) 15:29:17)~
~
I have released new build tools for #FuguIta.~
This tool allows you to build FuguIta from scratch without relying on supplementary files.~
For more information, see Part 4 of the FuguIta Guide, [[Building a FuguIta LiveDVD>fge4:build_fuguita]].
//
#comment
**Revised: Testing new build tools [#daa73898]
>[[kaw]] (2023-12-09 (Sat) 16:17:40)~
~This tool is %%tools-4.7-amd64-test.tar.gz%% tools-4.7-test.tar.gz located in the test directory of the mirror server, and is currently for both i386 and amd64.~
The build method is as follows.
~
+Download and extract the #FuguIta build tools.
~
+Download and extract the OpenBSD kernel (sys.tar.gz) and userland (src.tar.gz) source code under /usr/src. Then perform CVS updates if necessary.
~
+Run "make init".
~
+Place the OpenBSD install set (*74.tgz) under install_sets.~
If you want to customize FuguIta, please create site74.tgz as described in https://www.openbsd.org/faq/faq4.html#site and place it under install_sets. If install.site is included in site74.tgz, it will be added to /etc/rc.firsttime.~
''Please note:'' if the size of the created media/fuguita-7.4-adm64.ffsimg exceeds 2GB, the ISO image will not be created correctly due to a limitation of the mkhybrid utility.
~
+Run "make setup && make".
//
- An optional step is to create ''mode0symlinks.cpio.gz''. This file is intended to reduce the time required to boot at mode 0 (especially with LiveDVD).&br;To create mode0symlinks.cpio.gz, boot the completed LiveDVD at mode 0 and run the ''gen_mode0sldir'' command as root. Then, the /etc/fuguita/mode0symlinks.cpio.gz file will be created, so place it in the build tool's lib directory with the file name ''mode0symlinks.cpio.gz.amd64''.&br;Then run ''"make'' again and #FuguIta with mode0symlinks.cpio.gz will be created. -- [[kaw]] &new{2023-12-09 (Sat) 16:38:10};
- There is one more thing to provide feedback to the build tool after the first version is completed.&br;In the configuration file lib/global.conf.amd64, there is a variable assignment called fuguita_sys_mb, which represents the size of the LiveUSB system area, that is, the partition a.&br;This is roughly the same size as the livecd.iso generated at build time, but considering the fiupdate utility, it is safe to make it approximately 10MB larger than the livecd.iso size to provide some extra space.&br;After resetting the fuguita_sys_mb value, run "make" again to generate the #FuguIta LiveDVD ISO image. -- [[kaw]] &new{2023-12-09 (Sat) 22:25:26};
- Changes:&br; 1) the name of the tarball changed. On i386, it's also OK.&br; 2) userland source codes also needed to build crunched binary in /boottmp.&br;#FuguIta -- [[kaw]] &new{2023-12-13 (Wed) 17:44:25};
#comment
**Testing new build tools [#h0144f8d]
>[[kaw]] (2023-12-04 (Mon) 16:46:50)~
~
I am currently testing new #FuguIta build tools. This tool is tools-4.7-amd64-test.tar.gz located in the test directory of the mirror server, and is currently only for amd64.~
The build method is as follows.~
1. Expand the build tools.~
2. Extract the kernel source under /usr/src/sys.~
3. Run ''make initdir'' in the top directory of the build tool.~
4. Place the OpenBSD 7.4/amd64 installation set (*74.tgz) under install_sets.~
5. Place the OpenBSD 7.4/amd64 rsync, rlwrap, and pv package files under install_pkgs. And install (pkg_add) rsync and pv on the build host.~
6. Run ''make setup && make''.~
//
#comment
**Add another WM and if possible to install on HDD? [#c92b5adb]
>[[Rasat]] (2023-12-03 (Sun) 22:31:51)~
~
I installed Fvwm3 and imagemagick (for iconified thumbnails) and all work well with the Fvwm-kise configs (scripts), besides a few minor problems that can be fixed. There is no permission to edit xenodm config in #FuguIta directory. Made one new symlink from /usr/X11R6/bin/fvwm to /usr/local/bin/fvwm3. Is there a better option to do? Same with any added WM.~
The usbfadm tool is great. The expand/newfs option allowing to use and storage of full USB capacity. I added many new packages (pkg_add). Is there an option to install everything on the HDD?~
//
- /etc/X11/xenodm/xenodm-config is set to 0444, which is the same setting as in OpenBSD. When editing, please give write permission using chmod. There are no set rules regarding symbolic links, so use whatever method you like. Installing #FuguIta on internal storage such as a hard disk is the same as [[remastering FuguIta on a new USB flashdrive>fge3:liveusb_remaster]]. Please set the remaster destination to internal storage. Please note that in this case, all existing data in the internal storage will be deleted. -- [[kaw]] &new{2023-12-04 (Mon) 12:28:26};
#comment
**Fvwm Kise -- ready-made configs [#w268975f]
>[[Rasat]] (2023-11-30 (Thu) 05:37:41)~
~
I was searching for a distro with Fvwm as default and found #FuguIta . Fvwm Keep-It-Simple & elegant (Kise) is a simple and elegant base, and feature-rich to use, modify or add your own. The default Fvwm config file is the base. Currently, there are 23 scripts of functions, styles, menus, decor, and modules. Works well also on Fvwm2.~
~
Screenshots and download on Pling:~
www.pling.com/p/2095462~
//
- Fvwm is the default window manager in OpenBSD, and #FuguIta follows suit.&br;I also prefer a simple but useful window environment to today's gorgeous and complex desktops.&br;Did your project actually work on FuguIta?&br;Thank you very much for the useful information. -- [[kaw]] &new{2023-11-30 (Thu) 15:27:19};
- I tested #FuguIta , nice to see the classic Fvwm 1. Also, this was the first time using BSD, an impressive speed and performance. My project scripts don't work on this old Fvwm version. In general, I am suggesting FuguIta upgrade to Fvwm2 for more functionality and better configuration. Users can add their configs/scripts directly in .fvwm/config. FuguIta is a nice project. -- [[Rasat]] &new{2023-12-02 (Sat) 01:10:04};
- I did another test on #FuguIta checking for BSD packages. It has the latest Fvwm3 1.0.8. -- [[Rasat]] &new{2023-12-02 (Sat) 02:21:19};
- I tried your Fvwm Kise, too. It seems to work well on #FuguIta. Japanese window titlebar is well displayed. -- [[kaw]] &new{2023-12-04 (Mon) 12:14:32};~
#ref(fvwm_kise.png,wrap,50%);
- I have fixed the transparency and wallpaper switch problem on #FuguIta . Check version 1.7.1. OpenBSD uses the command "fvwm3-root" instead of "fvwm-root". And the transparency requires option "-r" (fvwm3-root -r). The window shadow with Picom compositor (pkg_add picom) on OpenBSD, doesn't allow seamless wallpapers to tile. But works well with "feh --bg-scale" (pkg_add feh). Try it by left-click on the screen, <Wallpapers><3D-Desk>. www.rasatpc.net/Fvwm-KISe/fvwm-kise-3d-desk.png -- [[Rasat]] &new{2023-12-05 (Tue) 22:01:45};
#comment
**Directory structure of mirror server changed [#se252b3d]
>[[kaw]] (2023-11-02 (Thu) 11:11:34)~
~
All the files of the latest release of #FuguIta were placed directly under the document root, but now we have created subdirectories (LiveDVD, LiveUSB and LiveSD) for each supported media and placed them there.~
~
Please be careful when [[downloading>FuguIta/Download]].~
//
#comment
**ISO for arm64 [#z0c7a894]
>[[Dan]] (2023-10-26 (Thu) 02:35:43)~
~
Would it be possible to have an ISO image for the arm64 architecture?~
~
Either #FuguIta version 7.3 or 7.4, whichever is more practical to build now.~
~
PS: the wheels are in motion to build daily snapshots for OpenBSD arm64 install CD-ROM images, at ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/~
//
- Like OpenBSD stable release, #FuguIta also does not supply ISO images for the arm64 platform.
This is because arm64 does not boot from CD or DVD.
For arm64, write the disk image file (FuguIta-7.3-arm64-*.img.gz) to a micro SD card.
We are currently in the process of creating 7.4. Please wait.
Please refer to the [[FuguIta Guide>fge1:m3ea6fcf]] for details. -- [[kaw]] &new{2023-10-26 (Thu) 07:49:33};
- Thanks, yes I'm waiting patiently for arm64 #FuguIta 7.4 disk image. But just to reiterate, I expect OpenBSD to deliver bootable CD/DVD images from next version (indeed the snapshot ISOs don't work perfectly for now 😇) -- [[Dan]] &new{2023-10-26 (Thu) 08:00:55};
- If OpenBSD/arm64 will support ISO images in the future, it will be good for #FuguIta as well, since the build process will be the same as i386/amd64. -- [[kaw]] &new{2023-10-26 (Thu) 08:12:33};
- The future is now: github.com/openbsd/src/blob/master/distrib/arm64/iso/Makefile so maybe arm64 #FuguIta 7.4 can be built similarly -- [[Dan]] &new{2023-10-28 (Sat) 00:48:50};
- Hi again. Is there any chance to release FuguIta-7.4-arm-202311211.iso.gz? I'd use the #FuguIta CD-ROM image to boot a virtual machine -- [[Dan]] &new{2023-11-26 (Sun) 06:22:09};
- Once OpenBSD-stable/arm64 (not OpenBSD-current) supports ISO images, #FuguIta will follow suit. Until then, we should research how the FuguIta build tools need to be modified for OpenBSD-stable/arm64 ISO image builds. -- [[kaw]] &new{2023-11-26 (Sun) 23:33:53};
- I'm working quick dirty hack on #FuguIta-7.4-arm64-*.iso. -- [[kaw]] &new{2023-11-27 (Mon) 01:16:59};
----
- I put FuguIta-7.4-arm64-202311211.iso.gz in the mirror's test directory.~
Please note that this is a test version and is not official. Also, it has been tested only on qemu-system-aarch64, and operation has not been verified on an actual machine.~
This was created by replacing the cdbr file with the snapshot version before [[running remaster_dvd.sh>fge4:livedvd_remaster]].~
If you try to create a LiveUSB from this ISO image and run usbfadm newdrive, it probably won't work. -- [[kaw]] &new{2023-11-27 (Mon) 01:42:51};
- Support for arm64 ISO #FuguIta is available. Please refer to [[this document>EBUG勉強会/20240525_FuguItaISO]] for more information about the plan for implementation and problems to be solved. If you cannot read Japanese documents, please use automatic translation service. -- [[kaw]] &new{2024-06-04 (Tue) 15:46:34};
#comment
**Test version of FuguIta 7.4 [#xf164c68]
>[[kaw]] (2023-10-21 (Sat) 09:48:11)~
~
[[Test version of FuguIta-7.4-{i386,amd64}>FuguIta/Download]] has been uploaded to the mirror. I'm looking forward to [[hearing from you>FuguIta/Report]]!
>What I would like to know are~
-How it works on newer hardware (device detection, X Window, suspend/resume, etc.)
//-How does it work with RPi4?
//-How the framebuffer and X Window work on RPi3/RPi4.
//-Operation status on arm64-based SBCs and Apple M1/M2 other than RPis.
-Comments and suggestions for improvement using the #FuguIta's original tools
-etc.
>Published files are for LiveUSB. If you wish to run LiveDVD, please [[remaster ISO image from LiveUSB>fge4:livedvd_remaster]].
>FuguIta-7.4-arm64 is now under working. Please wait.
>Thank you in advance.
//
#comment
**firmware that has no effect [#od721234]
>[[kaw]] (2023-10-09 (Mon) 13:53:36)~
~
When starting #FuguIta, the downloaded firmware may not take effect despite running fw_update.
In this case, you may find messages similar to the following in /var/run/dmesg.boot:
radeondrm0: RS400
radeon_cp: Failed to load firmware "radeon/R300_cp.bin"
[drm] *ERROR* Failed to load firmware!
drm:pid0:rs400_startup *ERROR* failed initializing CP (-2).
drm:pid0:rs400_init *ERROR* Disabling GPU acceleration
This example is for the ATI Radeon XPRESS 200M, but can also be seen with other video chips and WiFi devices.
This is because FuguIta's root file system is the kernel's built-in [[rd(4)>man:rd]], "ramdisk root."
>In FuguIta, when the kernel starts, rd is mounted to /, and after initialization, /etc is renamed to /boottmp, and then /etc is built again on MFS.
Therefore, the type of firmware that is loaded at kernel startup attempts to be loaded from /etc/firmware on the ramdisk root, but since the firmware does not exist there, an error occurs.
>To resolve this, you need to write the required firmware to /etc/firmware on the ramdisk root.
Here are the steps to do so:
>First, download and extract the firmware.
# ftp http://firmware.openbsd.org/firmware/7.3/radeondrm-firmware-20230310.tgz
Trying 2a04:4e42:36::820...
Requesting http://firmware.openbsd.org/firmware/7.3/radeondrm-firmware-20230310.tgz
100% |**************************************************| 3371 KB 00:02 ETA
3452257 bytes received in 2.22 seconds (1.47 MB/s)
# tar xzpf radeondrm-firmware-20230310.tgz
Next, extract the ramdisk root image from the kernel and mount the file system.
# zcat /sysmedia/bsd-fi.mp > bsd-fi.mp
# rdsetroot -x bsd-fi.mp rdroot.img
# vnconfig vnd0 rdroot.img
# mount /dev/vnd0a /mnt
Write the downloaded firmware to ramdisk root.
# mkdir -p /mnt/etc/firmware/radeon
# cp firmware/radeon/R300_cp.bin /mnt/etc/firmware/radeon
# umount /mnt
# vnconfig -u vnd0
# rdsetroot bsd-fi.mp rdroot.img
# mount -uw /sysmedia
# gzip -c9 bsd-fi.mp > /sysmedia/bsd-fi.mp
# mount -ur /sysmedia
Currently, the capacity of the ramdisk root is about 1.5 MB, but about 3/4 of it is used. Please note that the size of the firmware that can be written is just under 500 kilobytes.
//
- This is just what I needed. The live system hangs with my Radeon laptop. I'm just starting with #FuguIta, hopefully I can get this working. I'll see. -- [[Santos]] &new{2024-06-01 (Sat) 19:35:13};
#comment
**Fuguita 7.3 defaults to Japanese [#i35160ef]
>[[tetsuo]] (2023-10-02 (Mon) 04:22:13)~
~
#FuguIta Hi, is there a way to change the language of Fuguita? It's defaulting to Japanese and I don't know how to change it.~
//
- Which version of #FuguIta did you download? -- [[kaw]] &new{2023-10-02 (Mon) 10:12:00};
#comment
**FuguIta use case [#s83beed8]
>[[Bob]] (2023-09-05 (Tue) 23:31:23)~
~
#FuguIta. Hi, this looks interesting. When would someone use FuguIta instead of a plain OpenBSD install? What was the motivation behind the project? I could not find an "about" page.~
//
-#FuguIta is useful for verifying that OpenBSD will run on the desired hardware without installation.~
Of course, it is also possible to use FuguIta as a daily driver. In this case, you can take the USB stick with you and recreate the environment on your PC at your destination.~
See the [[Work with other products>FuguIta/ScreenShots#n89939db]] section at the bottom of the "Screenshot" page for examples.
There is also [[a video with auto-translated subtitles>https://youtu.be/4wPSr1WPH3U?si=CgiCmusjrZopHHK7]] showing an example of FuguIta's use.~
My initial motivation for developing FuguIta was to use OpenBSD everywhere, but now I also want to help spread the word about OpenBSD.
~-- [[kaw]] &new{2023-09-06 (Wed) 00:38:38};
#comment
**Larger ffsimg [#q578b09e]
>[[Kikk]] (2023-06-07 (Wed) 02:40:44)~
~
First of all: fuguita is wonderful. Keep up the good work!~
~
I wanted to build a custom version with more tools pre-installed.~
~
It is possible to enlarge the ffsimg over 1GB (fuguita-7.3-amd64.ffsimg)?~
~
I enlarged it to 3GB via disklabel + growfs but the remastered image no longer work.~
~
Is there a procedure or 1GB is the maximum size?~
~
#FuguIta~
//
----
To enlarge ''fuguita-7.3-amd64.ffsimg'', enlarge ''fuguita-7.3-amd64-ffsimg'' and ''media.img'' that contains it in the process of building FuguIta as described in the FuguIta Guide. The following is the procedure.
First, follow the [[FuguIta Guide to set up the build tool>fge4:build_fuguita]].
After settng up the build tool, delete or rename ''lib/mode0symlinks.cpio.gz.amd64''.
# mv lib/mode0symlinks.cpio.gz.amd64 lib/mode0symlinks.cpio.gz.amd64.bak
Run up to ''make stage''.
Once the ''staging'' directory is created, make your desired customizations in the tree.
# chroot staging /bin/ksh
# (YOUR COSTOMIZATIONS HERE)
# exit
Once your customization is complete, measure the size of the staging directory and the number of files it contains.
# du -sk staging | awk '{print $1/1024}' # size of staging directory in MB
# find staging -print | wc -l # the number of files which staging directory holds
Based on this size and number of files, use ''setup_fsimg.sh'' to create ''media.img''.
# make open-rdroot
# cp rdroot/boottmp/setup_fsimg.sh .
# make close-all
# ./setup_fsimg.sh media.img $((xxxxx+40)) 10 # xxxxx is the size of staging directory in MB.
Create ''fuguita-7.3-amd64.ffsimg'' in ''media.img''.
# make open-media
# cd media
# ../setup_fsimg.sh fuguita-7.3-amd64.ffsimg $((xxxxx+10)) yyyyy # yyyyy is the number of files which staging directory holds.
# cd ..
# make close-all
Edit ''staging/etc/fuguita/global.conf'' as follows
fuguita_sys_mb=1028 # size of media.img <-- Rewrite this value to current size of media.img
newdrive_defswap=16M # default swap size
# at usbfadm newdrive
memfstype=mfs # 'mfs' or 'tmpfs'
mfs_max_mb=30720 # mfs hard limit - 30GB
Copy the contents of ''staging'' to ffsimg.
# make sync
Create an ISO image and gzip it.
# make iso && make gz
Run the resulting LiveDVD and usbfadm newdrive to create a LiveUSB.
That's it for the procedure.
In general, it is much easier to use FuguIta LiveUSB to save your customizations to a USB flash drive with usbfadm sync and load them in boot mode 3.
See the following articles for an example of creating these.
- [[FuguIta/BBS#b01edbf7]]
- [[FuguIta/BBS/12#z6fb44cc]]
[[kaw]] &new{2023-06-07 (Wed) 09:44:19};
- Thanks, i'll try <3 <3 <3 #FuguIta -- [[Kikk]] &new{2023-06-10 (Sat) 16:24:24};
#comment
**日本語デスクトップ環境ãŠè©¦ã—版 [#b01edbf7]
>[[kaw]] (2023-05-23 (Tue) 09:37:56)~
~
河豚æ¿ã«æ—¥æœ¬èªžãƒ‡ã‚¹ã‚¯ãƒˆãƒƒãƒ—環境を入れãŸãŠè©¦ã—版を作ã£ã¦ã¿ã¾ã—ãŸã€‚
[[ダウンãƒãƒ¼ãƒ‰ã‚µã‚¤ãƒˆ>FuguIta/Download]]ã®oldディレクトリより FuguIta-7.3-amd64-202305211-DEDemoJa.img.xz をダウンãƒãƒ¼ãƒ‰ã—ã€xzã§è§£å‡ã—ã¦8GB以上ã®ã‚µã‚¤ã‚ºã®USBメモリã«æ›¸ã込んã§ä¸‹ã•ã„。~
# xz -dc FuguIta-7.3-amd64-202305211-DEDemoJa.img.xz | dd of=/dev/XXXX bs=1m
~
-起動途ä¸ã§demoユーザã®ãƒ‘スワードをè¨å®šã—ã¾ã™ã®ã§ã€å…¥åŠ›ã—ã¦ä¸‹ã•ã„([[doas>man:doas]]用ã€ã‚¹ã‚¯ãƒªãƒ¼ãƒ³ãƒãƒƒã‚¯è§£é™¤ç”¨ãªã©ã§ã™)。
>
-åŽéŒ²ã‚½ãƒ•ãƒˆã¯ä»¥ä¸‹ã®ã¨ãŠã‚Šã§ã™ã€‚~
--Xfce 4.18~
--日本語環境: kterm 6.2.0, 日本語フォントå„種, Fcitx-Anthy 5.0.10~
--FireFox 112.0.2~
--Sylpheed 3.7.0~
--Audacious 4.3~
--VLC 3.0.18~
--LibreOffice 7.5.1
>
-root権é™ã§[[/etc/rc.shutdownを編集>河豚æ¿ã‚¬ã‚¤ãƒ‰/3-é‹ç”¨ç·¨#autosave]]ã™ã‚‹ã“ã¨ã§ã€çµ‚了時ã«ãƒ•ã‚¡ã‚¤ãƒ«ã‚’自動ã§ä¿å˜ã™ã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚
>
-pkg_add / pkg_deleteã§ãƒ‘ãƒƒã‚±ãƒ¼ã‚¸ã‚’è¿½åŠ /削除ã—ãŸå¾Œã¯root権é™ã§ã€Œusbfadm -rã€ã‚’実行ã—ã¦ä¸‹ã•ã„。
>
-ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã¯æœ‰ç·šLANã®æ–¹ãŒç¢ºå®Ÿã«ç¹‹ãŒã‚Šã¾ã™ã€‚WiFiã¯ã€ãƒ•ã‚¡ãƒ¼ãƒ ウェアãŒè¿½åŠ ä¸è¦ãªãƒãƒƒãƒ—を使用ã—ã¦ãŠã‚Šã€ã‹ã¤ã€ãƒ‘スワードãªã—ã®å ´åˆã«æŽ¥ç¶šã§ãã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。起動後ã€WiFiを使用ã™ã‚‹è¨å®šã‚’è¡Œã„ãŸã„å ´åˆã¯[[ã“ã¡ã‚‰>河豚æ¿ã‚¬ã‚¤ãƒ‰/3-é‹ç”¨ç·¨#content_1_21]]ã‚’å‚ç…§ã—ã¦ä¸‹ã•ã„。
>
-root権é™ã§ä»¥ä¸‹ã®æ“作を行ã†ã¨ã€åˆæœŸçŠ¶æ…‹ã«æˆ»ã‚Šã¾ã™ã€‚
# mount -o async,noatime /dev/XXXd /mnt ... (XXXã¯LiveUSBã®ãƒ‡ãƒã‚¤ã‚¹å)
# cd /mnt/livecd-config/7.3/amd64/fugudemoja-init
# rsync -avxHS --delete . ../fugudemoja/.
# cd
# umount /mnt
>
-試作å“ã§ã™ã®ã§ã€ä¸å…·åˆä¿®æ£ã‚„改良ã¯è¡Œã„ã¾ã›ã‚“。fiupdateã«ã‚ˆã‚‹ã‚¢ãƒƒãƒ—デートã¯å¯èƒ½ã§ã™ã€‚at your own riskã§ã”使用下ã•ã„。
//
----
- FireFoxã®ãƒ•ã‚¡ã‚¤ãƒ«ãƒ€ã‚¤ã‚¢ãƒã‚°ãŒæ–‡å—化ã‘ã™ã‚‹ã®ã§ã€[[ã“ã®æ‰‹é †>FuguIta/BBS/9#content_1_2]]ã§ä¿®æ£ã—ã¦ä¸‹ã•ã„。#FuguIta -- [[kaw]] &new{2023-05-24 (Wed) 11:01:17};
#comment
**dd of #FuguIta to a USB-SSD ... gives a bootable XFCE desktop!!! [#z81d2579]
>[[Mark B]] (2023-05-09 (Tue) 11:30:12)~
~
Wow, no install process or anything. The image I "dd'd" of #FuguIta that I dd'd to a USB-SATA SSD (SSD on a USB-3 interface/cable) booted directly into an "LiveUSB-XFCE-gaytratri..." X11 session, with the usual OpenBSD puffer banner and Login/Password! How do I login to this? Your documentation does not cover this at all. It's supposed to be going into the Installation process...~
~
Thank you! ----mark~
//
- "LiveUSB-XFCE-gaytratri..." is what? (Post in progress...) #FuguIta -- [[kaw]] &new{2023-05-09 (Tue) 11:57:46};
- "LiveUSB-XFCE-gaytratri..." is what? Could it be [[the Xfce version of LiveUSB-OpenBSD>https://liveusb-openbsd.sourceforge.io/]] provided by Gayatri Hitech in India?
If so, it is a completely different product from my project #FuguIta.
If not, and you want to know exactly what FuguIta is, please read [[Getting Started with FuguIta>FuguIta/StartGuide]].
~-- [[kaw]] &new{2023-05-09 (Tue) 11:57:46};
#comment
**su exits with an error [#obc9ca3f]
>[[kaw]] (2023-05-05 (Fri) 12:42:47)~
~
In boot mode 0, su complains that /usr/libexec/auth/login_passwd is not found and exits with an error.~
A fixed version has been uploaded to the test directory of the mirrors. Please update with fiupdate for i386/amd64 LiveUSB version of #FuguIta.~
//
#comment
**Test version of FuguIta 7.3 [#gc8f8dec]
>[[kaw]] (2023-04-17 (Mon) 13:38:19)~
~
[[Test version of FuguIta 7.3>https://jp1.dl.fuguita.org/test/]] has been uploaded to the mirror. I'm looking forward to [[hearing from you>FuguIta/Report]]!
>What I would like to know are~
-How it works on newer hardware (device detection, X Window, suspend/resume, etc.)
-How does it work with RPi4?
-How the framebuffer and X Window work on RPi3/RPi4.
-Operation status on arm64-based SBCs and Apple M1/M2 other than RPis.
-Comments and suggestions for improvement using the #FuguIta's original tools
-etc.
>Thank you in advance.
//
#comment
----
Former articles are at [[FuguIta/BBS/13]].
![[PukiWiki]](image/pukiwiki.png "[PukiWiki]")
