Sorry if I bother you again with the thread. The minipc will be on business from tomorrow and I will use it together with a little student of mine: it is enough critical that the "not configured" hello! doesn't reppresent anything "risky". Eg: I tried to tweak the custom bios of Fujitsu for a more perfomant fan/cpu but the machine started litterally to fly while booting. Precautially I hanged manually the booting process.
The part of dmesg I'm wondering about is the following: "FUJ02E3" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C32" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu0 at acpi0: C1(@1 halt!), PSS acpicpu1 at acpi0: C1(@1 halt!), PSS acpicpu2 at acpi0: C1(@1 halt!), PSS acpicpu3 at acpi0: C1(@1 halt!), PSS cpu0: using Broadwell MDS workaround And for your own concerns: azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x06: msi azalia0: No codecs found Thanks! -- Daniele Bonini Feb 1, 2023 23:24:20 Daniele B. <my2...@aol.com>: > Just a small boot summary to attach to the thread.. > > ( I'm not that easy to share more about my config and sorry about that) > > The Fujitsu mini-pc has a custom made Ami Bios configuration. > > It went immidiately up and running although with some "not configured" hello! > that didn't impact the correct system launch in all its main components. > > The software configuration instead had a serious problem with Netbeans Ide > that was not able to > open and it crashed just after the splash. Unfortunately, I'm sure the > problem is related to the hardware conf > change that somehow was referenced in the local files (cache, user conf or > both) that I erased to > left Netbeans regenerating them. Between the hardware changes that I care > most: > - cpu0 -> acpitz0 in the sensors > - the name of the ethernet (java somehow likes the net) > > Cosmetic stuff: I cut off xorg.conf device "overclocking" parameters to a > standard configuration to > get the new video card much more speedy: my xorg.conf was aged and probably > xorg has already been > optimized to survive best without "my optimal hints". > > :D > > -- Daniele Bonini > > Feb 1, 2023 12:48:45 Peter N. M. Hansteen <pe...@bsdly.net>: > >> On Wed, Feb 01, 2023 at 12:36:18PM +0100, Daniele B. wrote: >>> The mini-pc arrived in three working days, from Germany to Italy. 30 bucks >>> of DHL delivery but.. >>> I could be certainly happy of such a service.. >>> >>> (although at time I can't still be sure about the possibility to openbsd >>> it..). >>> >>> Can we arrange these situation in a better bsd fashion? >>> >>> I will update you to bugs@ as soon I can boot this mini-pc, hopefully >>> I will not.... :D >> >> As several of us have said already, more likely than not the install will be >> easy and >> straightforward. If it isn't, bugs@ is the place to report. >> >> And anyway as soon as you have the thing running, sending the dmesg as >> described >> in https://www.openbsd.org/faq/faq4.html#SendDmesg will be much appreciated. >> >> - Peter >> >> -- >> Peter N. M. Hansteen, member of the first RFC 1149 implementation team >> https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ >> "Remember to set the evil bit on all malicious network traffic" >> delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
