Re: Allwinner D1 riscv64 mango pi SBC
On Sun, Jul 16, 2023 at 06:25:50PM +, Mike Larkin wrote: > On Sun, Jul 16, 2023 at 11:56:51AM +0200, Peter J. Philipp wrote: > > Hi *, > > > > I'm back for the moment. I was wondering who has a Allwinner D1 riscv64 > > SBC? > > This is the Mango Pi SBC. > > > > I have one which has linux on it currently but I'm trying to boot OpenBSD on > > it. But I'm fairly lazy and haven't done much with this lately. I can get > > to the riscv64 loader but when it loads the kernel, it goes blind. So there > > is more than just getting the GPIO pins configured which I think I have been > > able to adjust. > > > > I use a QEMU-based riscv64 emulation to compile kernels which is slow but > > this > > SBC isn't much faster either (1000 Mhz it claims). > > > > I use this u-boot directive to get into the boot loader: > > > > setenv bootobsd 'load mmc 0:1 0x4FA0 > > /boot/dtbs/5.19.0-1009-allwinner/allwinner/sun20i-d1-nezha-memory.dtb ; > > load mmc 0:f 0x4008 /EFI/OpenBSD/BOOTRISCV64.EFI ; bootefi 0x4008 > > 0x4FA0' > > > > followed by a: > > > > run bootobsd > > > > I am unsure how to save this though in the u-boot itself. Any hints would > > be > > appreciated. > > > > I think we need a specific riscv mailing list for this sort of stuff perhaps > > it's too technical for misc. Regarding to the nostradamus stuff of someone > > from chicago (Re: A couple of Questions) , check out "1st wave" and > > "cade foster" on youtube (reruns), this will feed you more ideas. my > > personal > > opinion is that time travel of information is possible, contributing to > > major > > headaches when events get changed (for the prometheus seers). > > > > Back to "reality" I'm looking for a group of people to help getting the > > mango > > pi working. I'm hampered by pride to ask knowledged people and these people > > have their own directions and I don't want to bother their efforts. The > > more > > we are the more we could possibly get something done. > > > > The best way to get that done is to get hardware in the hands of developer(s). > Wishing on misc@ is likely not going to get anyone interested. Check the > commit > logs for people working in this area, reach out to them, and see if they are > interested in helping. > > -ml Hi Mike, Thanks. This will take a bit, I'm in talks to get a new job soon, which will put extra money in my pocket. Then I may be able to get a handful of these perhaps. Do you still keep tabs on Shivam, Mars, Brian, and Wenyan? Are they still interested in riscv64 after the initial port with yours and Dales guidance? I think I paid something like 30 EUR for a Mango Pi from AliExpress buying 4 would work but I can only do this when I have secured the job. Best Regards, -peter -- Over thirty years experience on Unix-like Operating Systems starting with QNX.
anything like top but for USB?
Hi, Is there a tool to show statististics of USB devices? Like how much there is free bandwidth, which endpoints are hogging bandwidth and so on? Ideally it could be like top but for USB or a page on systat or something like that. Are there technical reasons or am I just bad at searching? Best regards, Hannu Vuolasaho
Re: Allwinner D1 riscv64 mango pi SBC
On Sun, Jul 16, 2023 at 11:56:51AM +0200, Peter J. Philipp wrote: > Hi *, > > I'm back for the moment. I was wondering who has a Allwinner D1 riscv64 SBC? > This is the Mango Pi SBC. > > I have one which has linux on it currently but I'm trying to boot OpenBSD on > it. But I'm fairly lazy and haven't done much with this lately. I can get > to the riscv64 loader but when it loads the kernel, it goes blind. So there > is more than just getting the GPIO pins configured which I think I have been > able to adjust. > > I use a QEMU-based riscv64 emulation to compile kernels which is slow but this > SBC isn't much faster either (1000 Mhz it claims). > > I use this u-boot directive to get into the boot loader: > > setenv bootobsd 'load mmc 0:1 0x4FA0 > /boot/dtbs/5.19.0-1009-allwinner/allwinner/sun20i-d1-nezha-memory.dtb ; load > mmc 0:f 0x4008 /EFI/OpenBSD/BOOTRISCV64.EFI ; bootefi 0x4008 > 0x4FA0' > > followed by a: > > run bootobsd > > I am unsure how to save this though in the u-boot itself. Any hints would be > appreciated. > > I think we need a specific riscv mailing list for this sort of stuff perhaps > it's too technical for misc. Regarding to the nostradamus stuff of someone > from chicago (Re: A couple of Questions) , check out "1st wave" and > "cade foster" on youtube (reruns), this will feed you more ideas. my personal > opinion is that time travel of information is possible, contributing to major > headaches when events get changed (for the prometheus seers). > > Back to "reality" I'm looking for a group of people to help getting the mango > pi working. I'm hampered by pride to ask knowledged people and these people > have their own directions and I don't want to bother their efforts. The more > we are the more we could possibly get something done. > The best way to get that done is to get hardware in the hands of developer(s). Wishing on misc@ is likely not going to get anyone interested. Check the commit logs for people working in this area, reach out to them, and see if they are interested in helping. -ml
installboot: no OpenBSD partition
Hi, I have trouble with installboot on a small embedded amd64 system. I get the following error during sysupgrade and also when I run installboot manually: installboot: no OpenBSD partition. You can find the output of installboot, fdisk and disklabel below. I also attached a full dmesg. I initially installed with 7.2 and I just upgraded to 7.3. This should be a GPT install but installboot seems to find an MBR, maybe this is the source of the problem. If possible, I would like to be able to fix this problem without reinstalling the system. Do you have some idea what's going on? Best regards, Jona # installboot -v sd0 /usr/mdec/biosboot /usr/mdec/boot Using / as root installing bootstrap on /dev/rsd0c using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot copying /usr/mdec/boot to //boot looking for superblock at 65536 found valid ffs2 superblock //boot is 6 blocks x 16384 bytes fs block shift 2; part offset 1024; inode block 56, offset 2928 expecting 64-bit fs blocks (incr 4) master boot record (MBR) at sector 0 partition 0: type 0xEE offset 1 size 4294967295 installboot: no OpenBSD partition # fdisk sd0 Disk: sd0 Usable LBA: 34 to 234441614 [234441648 Sectors] #: type [ start: size ] 0: EFI Sys [ 64: 960 ] 1: OpenBSD [ 1024: 234440591 ] # disklabel sd0 # /dev/rsd0c: type: SCSI disk: SCSI disk label: KINGSTON SA400S3 duid: 09a9344c23abff6c flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 14593 total sectors: 234441648 boundstart: 1024 boundend: 234441615 16 partitions: # size offset fstype [fsize bsize cpg] a: 230692352 1024 4.2BSD 2048 16384 12960 # / b: 3748239 230693376 swap # none c: 234441648 0 unused OpenBSD 7.3 (GENERIC) #1072: Sat Mar 25 10:26:08 MDT 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 7933616128 (7566MB) avail mem = 7673876480 (7318MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xcce1b000 (22 entries) bios0: vendor American Megatrends Inc. version "P1.30" date 11/27/2020 bios0: ASRock 4X4 BOX efi0 at bios0: UEFI 2.7 efi0: American Megatrends rev 0x50010 acpi0 at bios0: ACPI 6.0Undefined scope: \\_SB_.PCI0.SBRG.EC0_ acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SDEV SSDT FIDT MCFG AAFT IADT IAMT HPET SSDT VFCT TPM2 SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT FPDT acpi0: wakeup devices GPP0(S4) GPP2(S4) GPP3(S4) GPP4(S4) GPP5(S4) GP17(S4) XHC0(S4) XHC1(S4) GP18(S4) GP19(S4) SIO1(S3) GPP1(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 5 4500U with Radeon Graphics, 2375.00 MHz, 17-60-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 7 pa 0xfec0, version 21, 24 pins ioapic1 at mainbus0: apid 8 pa 0xfec01000, version 21, 32 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (GPP0) acpiprt2 at acpi0: bus 3 (GPP3) acpiprt3 at acpi0: bus -1 (GPP4) acpiprt4 at acpi0: bus 4 (GP17) acpiprt5 at acpi0: bus 5 (GP18) acpiprt6 at acpi0: bus -1 (GP19) acpiprt7 at acpi0: bus 2 (GPP1) acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x acpicmos0 at acpi0 acpibtn0 at acpi0: PWRB "ACPI0010" at acpi0 not configured acpicpu0 at acpi0: C3(0@350 io@0x415), C2(0@400 io@0x414), C1(0@1 mwait), PSS acpicpu1 at acpi0: no cpu matching ACPI ID 2 acpicpu2 at acpi0: no cpu matching ACPI ID 3 acpicpu3 at acpi0: no cpu matching ACPI ID 4 acpicpu4 at acpi0: no cpu matching ACPI ID 5 acpicpu5 at acpi0: no cpu matching ACPI ID 6 acpicpu6 at acpi0: no cpu matching ACPI ID 7 acpicpu7 at acpi0: no
Re: Cologne/Bonn BSD user group?
On Fri, Jul 07, 2023 at 12:35:54PM +, Marco van Hulten wrote: > Hello, > > Is anyone interested helping setting up a user group in or around Bonn? > > Marco, Bonn (Germany) Hello Marco, I'm not in the Bonn region unfortunately. I'm looking for an OpenBSD or BSD group near Schweinfurt, Bayern region. Schweinfurt is no Bonn, we are a larger smaller town in comparison. Best Regards, -peter -- Over thirty years experience on Unix-like Operating Systems starting with QNX.
Re: Allwinner D1 riscv64 mango pi SBC
On 2023-07-16, Peter J. Philipp wrote: > Hi *, > > I'm back for the moment. I was wondering who has a Allwinner D1 riscv64 SBC? > This is the Mango Pi SBC. > > I have one which has linux on it currently but I'm trying to boot OpenBSD on > it. But I'm fairly lazy and haven't done much with this lately. I can get > to the riscv64 loader but when it loads the kernel, it goes blind. So there > is more than just getting the GPIO pins configured which I think I have been > able to adjust. The SoC is not on the supported hardware list so will probably need some development work to get it to run. > I think we need a specific riscv mailing list for this sort of stuff perhaps > it's too technical for misc. I don't think it's too technical. The existing hw-specific lists aren't really that widely used so there doesn't seem a lot of point in setting up another.
subscribe
subscribe
Allwinner D1 riscv64 mango pi SBC
Hi *, I'm back for the moment. I was wondering who has a Allwinner D1 riscv64 SBC? This is the Mango Pi SBC. I have one which has linux on it currently but I'm trying to boot OpenBSD on it. But I'm fairly lazy and haven't done much with this lately. I can get to the riscv64 loader but when it loads the kernel, it goes blind. So there is more than just getting the GPIO pins configured which I think I have been able to adjust. I use a QEMU-based riscv64 emulation to compile kernels which is slow but this SBC isn't much faster either (1000 Mhz it claims). I use this u-boot directive to get into the boot loader: setenv bootobsd 'load mmc 0:1 0x4FA0 /boot/dtbs/5.19.0-1009-allwinner/allwinner/sun20i-d1-nezha-memory.dtb ; load mmc 0:f 0x4008 /EFI/OpenBSD/BOOTRISCV64.EFI ; bootefi 0x4008 0x4FA0' followed by a: run bootobsd I am unsure how to save this though in the u-boot itself. Any hints would be appreciated. I think we need a specific riscv mailing list for this sort of stuff perhaps it's too technical for misc. Regarding to the nostradamus stuff of someone from chicago (Re: A couple of Questions) , check out "1st wave" and "cade foster" on youtube (reruns), this will feed you more ideas. my personal opinion is that time travel of information is possible, contributing to major headaches when events get changed (for the prometheus seers). Back to "reality" I'm looking for a group of people to help getting the mango pi working. I'm hampered by pride to ask knowledged people and these people have their own directions and I don't want to bother their efforts. The more we are the more we could possibly get something done. Best Regards, -peter PS: I'm looking at employment shortly as a stockboy internship. -- Over thirty years experience on Unix-like Operating Systems starting with QNX.
