Edit of
FuguIta/Report/19
https://fuguita.org/?FuguIta/Report/19
-- Use page as template --
(no template pages)
* 7.6-amd64 on Nipogi [#p98fbd48] -Posted by Psycho at 2024-10-19 (Sat) 21:43:30 -Release: 7.6-amd64-202410141 -Media: USB flashdrive -Hardware: Nipogi (CPU: Alder Lake n95, Memory: 16GB DDR4) ** Remarks [#bb868b08] #setlinebreak(on) I can not boot. I got the following message : Process (pid 1) got a signal 4 I did not write URL here. I have bought my computer from amazon Japan. #FuguIta ---- I received a similar report (got signal 4) on FuguIta-7.5-amd64 on Hyper-V How about uniprosessor? Try like this: boot> bsd-fi 2024-10-20 (Sun) 00:05:27 - kaw - #FuguIta,I got same message. www.amazon.co.jp/gp/product/B0C1MR16G7/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1 -- [[Psycho]] &new{2024-10-20 (Sun) 21:01:37}; - I found a similar case in github.com/yellowman/flashrd/issues/30 , then I built a test version ''/test/FuguIta-7.6_pie-amd64-202410221.{iso,img}.gz'' with PIE enabled /boottmp/init . Please try this. &br;#FuguIta -- [[kaw]] &new{2024-10-22 (Tue) 11:16:10}; - current test version is ''/test/FuguIta-7.6_rvmk-amd64-202410231.{iso,img}.gz'', try this if you can.&br;#FuguIta -- [[kaw]] &new{2024-10-23 (Wed) 12:48:58}; - Thank you. but I got same error. I typed both enter key and bsd-fi at boot. #FuguIta -- [[Psycho]] &new{2024-10-23 (Wed) 18:01:17}; - Thank you for your report. will continue to researching/debugging&br;#FuguIta -- [[kaw]] &new{2024-10-23 (Wed) 18:17:19}; - Next is ''/test/FuguIta-7.6_init-amd64-202410241.{iso,img}.gz''. In this version, /boottmp/init is now an independent executable, not a part of crunched binary /boottmp/bootbin.&br;#FuguIta -- [[kaw]] &new{2024-10-24 (Thu) 02:09:49}; - Sorry double post! I only reloaded. #FuguIta -- [[Psycho]] &new{2024-10-24 (Thu) 03:29:59}; - On Intel's 12th or later generation CPUs, OpenBSD crunch binaries may not work properly with E-cores enabled; try disabling E-cores in the BIOS.&br;#FuguIta -- [[kaw]] &new{2024-10-25 (Fri) 00:09:23}; - I downloaded FuguIta-7.6_init-amd64-202410241.{iso,img}.gz. It does not boot wheter E-core is 0 or ALl. But I got another message. wsdisplay0: screen 1-5 added (std, vt100 emulation) init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter pathname of shell or RETURN for sh: #FuguIta -- [[Psycho]] &new{2024-10-25 (Fri) 19:32:50}; - Thank you very much for your multiple reports. I got an another similar report. Your and that reports mean that there is any problem on FuguIta's crunched binary /boottmp/bootbin (although OpenBSD installer's crunched binary instbin works properly). More further debugging continues.&br;#FuguIta. -- [[kaw]] &new{2024-10-25 (Fri) 22:31:13}; - Would you check /test/FuguIta-7.6_tst4-amd64-202410262.img.gz ?&br;#FuguIta -- [[kaw]] &new{2024-10-26 (Sat) 16:06:51}; - Process (pid 1) got a signal 4 It appears both enter key and bsd-fi at boot. I tried both E-core is 0 and ALL in the Bios. #FuguIta -- [[Psycho]] &new{2024-10-26 (Sat) 21:03:04}; - The newest is /test/FuguIta-7.6_cts8-amd64-202411021.{iso,img}.gz. Would you test this?&br;#FuguIta -- [[kaw]] &new{2024-11-02 (Sat) 11:08:17}; - You wrote "Enter mfs size. ... otherwise considered "megabytes" [default: 755M] ->" . But it says "[default: M]" . It does not accept any values such as enter,50%,16000M. #FuguItaM -- [[Psycho]] &new{2024-11-02 (Sat) 16:44:34}; - Intel's 12th generation and newer CPUs have introduced a feature called IBT (Indirect Branch Tracking), which can detect illegal indirect branch instructions. OpenBSD 7.5 and later are designed to detect illegal branches using IBT, and the initial execution binary of #FuguIta violates this feature, so it does not start up correctly. Currently, we are generating the binary with an option to bypass this check function in the compiler, but it is not running completely. We are currently investigating the cause. &br;[[Mandatory enforcement of indirect branch targets>https://undeadly.org/cgi?action=article;sid=20230714121907]]&br; -- [[kaw]] &new{2024-11-03 (Sun) 08:32:58}; - I also purchased the same model MiniPC as yours and am doing investigating. Could you please test /test/FuguIta-7.6_ctsf-amd64-202411081.{iso,img}.gz? This worked on my machine. (#FuguIta-7.6_ctsf-amd64-202411081 is based on the -current release of OpenBSD. Please note that it is not a -stable release) -- [[kaw]] &new{2024-11-08 (Fri) 03:05:10}; - Pkg_add doesn't seem to work. #FuguIta -- [[Psycho]] &new{2024-11-08 (Fri) 19:23:46} - Note that this test release is -current, not -stable. https://www.openbsd.org/faq/faq5.html#Flavors&br;pkg_add may not work correctly. Wait normal fixed release for daily use, please. #FuguIta -- [[kaw]] &new{2024-11-08 (Fri) 23:01:28}; #comment #setlinebreak(off) ~ #navi(FuguIta/Report)
Do not change timestamp
* 7.6-amd64 on Nipogi [#p98fbd48] -Posted by Psycho at 2024-10-19 (Sat) 21:43:30 -Release: 7.6-amd64-202410141 -Media: USB flashdrive -Hardware: Nipogi (CPU: Alder Lake n95, Memory: 16GB DDR4) ** Remarks [#bb868b08] #setlinebreak(on) I can not boot. I got the following message : Process (pid 1) got a signal 4 I did not write URL here. I have bought my computer from amazon Japan. #FuguIta ---- I received a similar report (got signal 4) on FuguIta-7.5-amd64 on Hyper-V How about uniprosessor? Try like this: boot> bsd-fi 2024-10-20 (Sun) 00:05:27 - kaw - #FuguIta,I got same message. www.amazon.co.jp/gp/product/B0C1MR16G7/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1 -- [[Psycho]] &new{2024-10-20 (Sun) 21:01:37}; - I found a similar case in github.com/yellowman/flashrd/issues/30 , then I built a test version ''/test/FuguIta-7.6_pie-amd64-202410221.{iso,img}.gz'' with PIE enabled /boottmp/init . Please try this. &br;#FuguIta -- [[kaw]] &new{2024-10-22 (Tue) 11:16:10}; - current test version is ''/test/FuguIta-7.6_rvmk-amd64-202410231.{iso,img}.gz'', try this if you can.&br;#FuguIta -- [[kaw]] &new{2024-10-23 (Wed) 12:48:58}; - Thank you. but I got same error. I typed both enter key and bsd-fi at boot. #FuguIta -- [[Psycho]] &new{2024-10-23 (Wed) 18:01:17}; - Thank you for your report. will continue to researching/debugging&br;#FuguIta -- [[kaw]] &new{2024-10-23 (Wed) 18:17:19}; - Next is ''/test/FuguIta-7.6_init-amd64-202410241.{iso,img}.gz''. In this version, /boottmp/init is now an independent executable, not a part of crunched binary /boottmp/bootbin.&br;#FuguIta -- [[kaw]] &new{2024-10-24 (Thu) 02:09:49}; - Sorry double post! I only reloaded. #FuguIta -- [[Psycho]] &new{2024-10-24 (Thu) 03:29:59}; - On Intel's 12th or later generation CPUs, OpenBSD crunch binaries may not work properly with E-cores enabled; try disabling E-cores in the BIOS.&br;#FuguIta -- [[kaw]] &new{2024-10-25 (Fri) 00:09:23}; - I downloaded FuguIta-7.6_init-amd64-202410241.{iso,img}.gz. It does not boot wheter E-core is 0 or ALl. But I got another message. wsdisplay0: screen 1-5 added (std, vt100 emulation) init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter pathname of shell or RETURN for sh: #FuguIta -- [[Psycho]] &new{2024-10-25 (Fri) 19:32:50}; - Thank you very much for your multiple reports. I got an another similar report. Your and that reports mean that there is any problem on FuguIta's crunched binary /boottmp/bootbin (although OpenBSD installer's crunched binary instbin works properly). More further debugging continues.&br;#FuguIta. -- [[kaw]] &new{2024-10-25 (Fri) 22:31:13}; - Would you check /test/FuguIta-7.6_tst4-amd64-202410262.img.gz ?&br;#FuguIta -- [[kaw]] &new{2024-10-26 (Sat) 16:06:51}; - Process (pid 1) got a signal 4 It appears both enter key and bsd-fi at boot. I tried both E-core is 0 and ALL in the Bios. #FuguIta -- [[Psycho]] &new{2024-10-26 (Sat) 21:03:04}; - The newest is /test/FuguIta-7.6_cts8-amd64-202411021.{iso,img}.gz. Would you test this?&br;#FuguIta -- [[kaw]] &new{2024-11-02 (Sat) 11:08:17}; - You wrote "Enter mfs size. ... otherwise considered "megabytes" [default: 755M] ->" . But it says "[default: M]" . It does not accept any values such as enter,50%,16000M. #FuguItaM -- [[Psycho]] &new{2024-11-02 (Sat) 16:44:34}; - Intel's 12th generation and newer CPUs have introduced a feature called IBT (Indirect Branch Tracking), which can detect illegal indirect branch instructions. OpenBSD 7.5 and later are designed to detect illegal branches using IBT, and the initial execution binary of #FuguIta violates this feature, so it does not start up correctly. Currently, we are generating the binary with an option to bypass this check function in the compiler, but it is not running completely. We are currently investigating the cause. &br;[[Mandatory enforcement of indirect branch targets>https://undeadly.org/cgi?action=article;sid=20230714121907]]&br; -- [[kaw]] &new{2024-11-03 (Sun) 08:32:58}; - I also purchased the same model MiniPC as yours and am doing investigating. Could you please test /test/FuguIta-7.6_ctsf-amd64-202411081.{iso,img}.gz? This worked on my machine. (#FuguIta-7.6_ctsf-amd64-202411081 is based on the -current release of OpenBSD. Please note that it is not a -stable release) -- [[kaw]] &new{2024-11-08 (Fri) 03:05:10}; - Pkg_add doesn't seem to work. #FuguIta -- [[Psycho]] &new{2024-11-08 (Fri) 19:23:46} - Note that this test release is -current, not -stable. https://www.openbsd.org/faq/faq5.html#Flavors&br;pkg_add may not work correctly. Wait normal fixed release for daily use, please. #FuguIta -- [[kaw]] &new{2024-11-08 (Fri) 23:01:28}; #comment #setlinebreak(off) ~ #navi(FuguIta/Report)
View Text Formatting Rules
![[PukiWiki]](image/pukiwiki.png "[PukiWiki]")
