You are not logged in. Please login or register.
We are very pleased and happy to announce the newest release of Hyperbola GNU/Linux-libre with v0.4.4.
See our official news for further details.
HyperForum → General → testing HyperbolaBSD-qemu
The HyperbolaBSD-roadmap (https://wiki.hyperbola.info/doku.php?id … la_roadmap) states, that the qemu testing of the non-X-system has begun.
Can i partizipate (and hopefully help writing reports) - is there an qemu-image/installer-image available???
thx
Yes, here: https://repo.hyperbola.info:50000/other … bsd_debug/
But beware as you may have issues when starting and therefore we search also for help in development. If you have interest, please contact Coadde and Emulatorman. Also here with having a time-gap in mind as Emulatorman is on travels for the next three weeks.
Thanks, i will test and help were i can.
Sure, there will be issues. It's pre-alpha 
I assume this behaviour is already known to the devs, but who knows.
Linux libera 5.15.0-86-generic #96+11.0trisquel24 SMP Wed Oct 4 01:43:57 UTC 2023 x86_64 x86_64 x86_64 GNU/Linuxprocessor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i7-2860QM CPU @ 2.50GHz
stepping : 7
microcode : 0x2e
cpu MHz : 800.000
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts flush_l1d
vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknownQEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.15)qemu options as in hbbsd_v0d99pa_debug.shYes, that's known and especially the problem being worked on. But it is right more complicated because the HyperBK- kernel is ported to newer version of GCC and therefore complete different. If you want to support or have more clues on possible fixes, they would be helpful for Coadde.
Also more insights here: https://git.hyperbola.info:50100/hyperb … /?h=stage2
Yes, that's known and especially the problem being worked on. But it is right more complicated because the HyperBK- kernel is ported to newer version of GCC and therefore complete different. If you want to support or have more clues on possible fixes, they would be helpful for Coadde.
Also more insights here: https://git.hyperbola.info:50100/hyperb … /?h=stage2
thx
I will setup the build enviroment and try to get into the build process, this will take some time (i just stumbled upon your roadmap and i am very curious 
)
No problem, the more curious the better. 
cross-compile suite is up and running. kernel build works.
i wasn't able to get the qemu-img mounted (to cross install the new build kernel) - but i guess i get that working.
I am willed to get into kernel development, because it is needed: HyperbolaBSD seems to be the only really sane project right now.
Bothering the main-devs right now would not be good at this point, as i am new to kernel-development/debugging; it would just slow down the process; first I need to get into it by myself.
Do you know any resources/tutorials/entry-points where i can start (oBSD-docs or alike)?
Have forwarded your message towards the current development.
Have forwarded your message towards the current development.
Thanks, you can forward my forum-email (if you have access to it ?!)
Yes, I could do that (if you wish). But personal I would prefer bringing the persons together via forum or else. One first important part of our forum is to protect the users and their data.
Yes, I could do that (if you wish). But personal I would prefer bringing the persons together via forum or else. One first important part of our forum is to protect the users and their data.
Sure, forum+forum-pm's is also sufficiant.
Thanks.
Hello . I would also like to run and test a test version of HyperbolaBSD. Please tell me where I can download the test image?
Here: https://repo.hyperbola.info:50000/other … bsd_debug/
https://repo.hyperbola.info:50000/other … bsd_debug/
has some downloads for images, though should I install these on hardware without using a virtual machine, like qemu, even if these may just be more of a test like image. Or is it better to use a virtual machine at this time.
Also what one do you think is the best one to test? Or are there more new ones than these to test?
And what do you think is the best way to burn them to a flash drive or CD/DVD, the same way as I can burn Milky Way v0.4.4, or another way?
I know how to use dd on Trisquel.
Hey, happy to see that you are eager testing HyperbolaBSD. But for the moment I would encourage you also to wait a bit longer: We are debugging current points that image has like freezing on the boot-process. Also: At best to use for sure a virtual machine. You can use therefore on Hyperbola direct qemu or throughout qtemu.
(Yes, you can also use other systems already through that little nice application, meaning qtemu!)
Hey, happy to see that you are eager testing HyperbolaBSD. But for the moment I would encourage you also to wait a bit longer: We are debugging current points that image has like freezing on the boot-process. Also: At best to use for sure a virtual machine. You can use therefore on Hyperbola direct qemu or throughout qtemu.
(Yes, you can also use other systems already through that little nice application, meaning qtemu!)
Thank you for the information about the boot problem at
ipxe.org/2d03e13b
Could be
iPXE 1.21.1+git-20220112.fbbdc3926-0ubuntu1
I saw it after I used
qemu-img create -f qcow2 hyperbolabsd.qcow2 15G
and
qemu-system-x86_64 -hda hyperbolabsd.qcow2 -boot d -cdrom hbbsd_v0d99pa_debug.img -m 2048 -smp 2 -enable-kvm -nic user,hostfwd=tcp::10037-:4571
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
on Trisquel.
I'm also glad the main HyperbolaBSD develepers and some users are removing the non-free files before compiling this, as OpenBSD has may non-free things.
I did not know OpenBSD even had licenses like this in it! I thought it had some binary blobs, but not this many, and with these types of "conditions" against even reverse engineering and sharing it in source code form, as some code in OpenBSD was under
Firmware is redistributed in object code only.
.
Copyright 2004 Atmel Corporation. All Rights Reserved. Redistribution and use
of the microcode software ("Firmware") is permitted provided that the following
conditions are met:
1. Firmware is redistributed in object code only.
2. Any reproduction of Firmware must contain the above copyright notice,
this list of conditions and the below disclaimer in the documentation
and/or other materials provided with the distribution; and
3. The name of Atmel Corporation may not be used to endorse or promote products
derived from this Firmware without specific prior written consent.DISCLAIMER: ATMEL PROVIDES THIS FIRMWARE "AS IS'' WITH NO WARRANTIES
OR INDEMNITIES WHATSOEVER. ATMEL EXPRESSLY DISCLAIMS ANY
EXPRESS, STATUTORY OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL ATMEL
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
FIRMWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.USER ACKNOWLEDGES AND AGREES THAT THE PURCHASE OR USE OF THE
FIRMWARE WILL NOT CREATE OR GIVE GROUNDS FOR A LICENSE BY
IMPLICATION, ESTOPPEL, OR OTHERWISE IN ANY INTELLECTUAL PROPERTY
RIGHTS (PATENT, COPYRIGHT, TRADE SECRET, MASK WORK, OR OTHER
PROPRIETARY RIGHT) EMBODIED IN ANY OTHER ATMEL HARDWARE OR
FIRMWARE EITHER SOLELY OR IN COMBINATION WITH THE FIRMWARE.
You can look:
https://git.hyperbola.info:50100/~team/ … -issues.md
https://git.hyperbola.info:50100/~team/ … d-files.md
And generic here: https://git.hyperbola.info:50100/~team/ … git/about/
Besides that has nothing to do with ipxe. It is an issue we are already aware of and Coadde is working on it. So to underline: That image is surely not the current state of HyperbolaBSD.
HyperForum → General → testing HyperbolaBSD-qemu
Powered by PunBB, supported by Informer Technologies, Inc.