Re: switch the cubie miniroot to cubieboard2
- Original Message -
> si...@slackware.it [si...@slackware.it] wrote:
> > Speaking as a Cubieboard owner here ;-)
> > Would it be too much hassle to provide both images? (and a pony!)
> >
>
> It's fairly easy to take a miniroot image for a similar board, and
> adapt it to your board.
Thanks for the tutorial!
>
> Since both the Cubieboard and Cubieboard2 are Allwinner based,
> the miniroot's general structure does not change.
>
> 1. Install u-boot-2016.07p1 from ports/packages (packages if you don't
> want to wait all day)
>
> 2. Examine /usr/src/distrib/armv7/ramdisk/install.md and find
> a similar board (same or similar chipset).
>
> 3. Find the proper u-boot/dtb stuff in /usr/local/share/u-boot
>
> 4. Download the miniroot image for a board that has the same
> or similar chipset to your board
>
> 5. vnconfig vnd0 miniroot.fs
>
> 6. Install proper u-boot image to the miniroot image. The install.md
> file tells you how to copy the proper u-boot/dtb over. For instance,
> Cubieboard is Allwinner A10/A20, and my Lime is A20.
>
> install.md says:
>
> cubie)
> dd if=$_mdec/u-boot-sunxi-with-spl.bin of=${_disk}c \
> bs=1024 seek=8 >/dev/null 2>&1
>
> So, to get my Lime or Lime2 working, I do this:
>
> dd if=/usr/local/share/u-boot/A20-OLinuXino-Lime2/u-boot-sunxi-with-spl.bin
> of=/dev/rvnd0c bs=1024 seek=8
>
> (Note: Lime and lime2 bootloaders will appear to work on both boards,
> but if you don't use the right one, the Realtek ethernet PHY will
> not be properly initialized.)
>
> 7. vnconfig -u vnd0
>
> 8. Write miniroot.fs to your SD card
>
> You don't have to use vnd, but this is conceptually simpler
> and less error prone than trying to chop it up with dd.
>
> Chris
>
--
Marco Bonetti
Re: switch the cubie miniroot to cubieboard2
Speaking as a Cubieboard owner here ;-) Would it be too much hassle to provide both images? (and a pony!) -- Marco Bonetti
Re: Keyboard resume (zzz) diff
- Original Message - > - Original Message - > > Since it worked before, start bisecting diffs. Once you've narrowed it > > down, > > let us know. > > Tried to do that but I can't boot past the 4th April softraid update :-/ Small update: I spent some time on this over the weekend and can confirm that resuming from suspend or hibernate works great when invoked from the console (i.e. if in X11, hit CTRL+ALT+F1, login, type zzz or ZZZ). If I try to do that from X11, upon resume the laptop switches back to the console and the keyboard outputs random stuff in response to key presses. Cheers, Marco -- Marco Bonetti
Re: Keyboard resume (zzz) diff
- Original Message - > Since it worked before, start bisecting diffs. Once you've narrowed it down, > let us know. Tried to do that but I can't boot past the 4th April softraid update :-/ -- Marco Bonetti
Re: Keyboard resume (zzz) diff
- Original Message - > Considering you don't even have a pckbd, I think this is not likely caused > by the pckbd zzz diff committed last week. AH! Good to know :D > If you want to be sure, revert that single commit and check it again. Yup, obviously confirmed: no changes with pckbd.c 1.42, the keyboard is still not working properly on resume. Any idea about what introduced the need for the fix in pckbd? Might be related to what is happening with wskbd. Cheers, Marco -- Marco Bonetti
Re: Keyboard resume (zzz) diff
Coming late to the party for a negative report: OpenBSD 5.9-current on a MacBookAir5,2 is suspending and hibernating OK but on resuming the keyboard is not working correctly any more, it used to work fine on OpenBSD 5.9-release. If needed, dmesg is below. OpenBSD 5.9-current (GENERIC.MP) #1996: Wed Apr 20 14:57:08 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error fe real mem = 8473612288 (8081MB) avail mem = 8212418560 (7831MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x8ad12000 (54 entries) bios0: vendor Apple Inc. version "MBA51.88Z.00EF.B04.1509111654" date 09/11/2015 bios0: Apple Inc. MacBookAir5,2 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT DMAR MCFG acpi0: wakeup devices P0P2(S4) PEG2(S4) EC__(S4) HDEF(S4) RP02(S4) ARPT(S4) RP05(S4) EHC1(S4) EHC2(S4) XHC1(S4) ADP1(S4) LID0(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz, 1696.44 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz, 1696.15 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz, 1696.15 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz, 1696.15 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xe000, bus 0-153 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P2) acpiprt2 at acpi0: bus -1 (PEG2) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 3 (RP05) acpicpu0 at acpi0: C3(200@198 mwait.1@0x30), C2(500@148 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@198 mwait.1@0x30), C2(500@148 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@198 mwait.1@0x30), C2(500@148 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@198 mwait.1@0x30), C2(500@148 mwait.1@0x10), C1(1000@1 mwait.1), PSS "PNP0103" at acpi0 not configured "APP0001" at acpi0 not configured "ACPI0008" at acpi0 not configured "PNP0C09" at acpi0 not configured "ACPI0002" at acpi0 not configured acpibat0 at acpi0: BAT0 model "3545797981023400290" type 3545797981528607052 oem "3545797981528673619" acpiac0 at acpi0: AC unit offline acpibtn0 at acpi0: LID0 acpibtn1 at acpi0: PWRB "APP0002" at acpi0 not configured acpibtn2 at acpi0: SLPB acpivideo0 at acpi0: IGPU acpivout0 at acpivideo0: DD02 cpu0: Enhanced SpeedStep 1696 MHz: speeds: 1801, 1800, 1700, 1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 drm0 at inteldrm0 inteldrm0: msi inteldrm0: 1440x900 error: [drm:pid0:intel_dp_start_link_train] *ERROR* too many full retries, give up wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) xhci0 at p
Re: Black screen with inteldrm and recent snapshots
Hello tech@, I'm sorry for resurrecting an old thread: I'm seeing intel drm errors in my dmesg, they appeared with the same end of September -current snapshot as the original poster mentioned but I'm having no visible issues other than some noise in the logs. Hardware is an EeePC 701 (i915) running i386 -current, here's dmesg from 13th October snapshot: 9 bios0: ASUSTeK Computer INC. 701 acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC OEMB MCFG acpi0: wakeup devices P0P3(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) MC97(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) EUSB(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 70MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 5 (P0P3) acpiprt2 at acpi0: bus 3 (P0P5) acpiprt3 at acpi0: bus 1 (P0P6) acpiec0 at acpi0 acpicpu0 at acpi0: !C3(@1000 io@0x815), !C2(@100 io@0x814), C1(@1 halt!) acpitz0 at acpi0: critical temperature is 90 degC acpibat0 at acpi0: BAT0 model "701" serial type LION oem "ASUS" acpiac0 at acpi0: AC unit online acpiasus0 at acpi0 acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: PWRB bios0: ROM list: 0xc/0xf800! pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 "Intel 82915GM Host" rev 0x04 vga1 at pci0 dev 2 function 0 "Intel 82915GM Video" rev 0x04 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 error: [drm:pid0:i915_gem_detect_bit_6_swizzle] *ERROR* Couldn't read from MCHBAR. Disabling tiling. inteldrm0: apic 1 int 16 inteldrm0: 800x480 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel 82915GM Video" rev 0x04 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 "Intel 82801FB HD Audio" rev 0x04: msi azalia0: codecs: Realtek ALC662 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 82801FB PCIE" rev 0x04: apic 1 int 16 pci1 at ppb0 bus 4 ppb1 at pci0 dev 28 function 1 "Intel 82801FB PCIE" rev 0x04: apic 1 int 17 pci2 at ppb1 bus 3 lii0 at pci2 dev 0 function 0 "Attansic Technology L2" rev 0xa0: apic 1 int 17, address 00:1e:8c:e6:ca:6e atphy0 at lii0 phy 1: F2 10/100 PHY, rev. 2 ppb2 at pci0 dev 28 function 2 "Intel 82801FB PCIE" rev 0x04: apic 1 int 18 pci3 at ppb2 bus 1 uhci0 at pci0 dev 29 function 0 "Intel 82801FB USB" rev 0x04: apic 1 int 23 uhci1 at pci0 dev 29 function 1 "Intel 82801FB USB" rev 0x04: apic 1 int 19 uhci2 at pci0 dev 29 function 2 "Intel 82801FB USB" rev 0x04: apic 1 int 18 uhci3 at pci0 dev 29 function 3 "Intel 82801FB USB" rev 0x04: apic 1 int 16 ehci0 at pci0 dev 29 function 7 "Intel 82801FB USB" rev 0x04: apic 1 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xd4 pci4 at ppb3 bus 5 ichpcib0 at pci0 dev 31 function 0 "Intel 82801FBM LPC" rev 0x04: PM disabled pciide0 at pci0 dev 31 function 2 "Intel 82801FBM SATA" rev 0x04: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 1 drive 0: wd0: 1-sector PIO, LBA, 3815MB, 7815024 sectors wd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4 ichiic0 at pci0 dev 31 function 3 "Intel 82801FB SMBus" rev 0x04: apic 1 int 19 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-6400CL6 SO-DIMM usb1 at uhci0: USB revision 1.0 uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1 usb3 at uhci2: USB revision 1.0 uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1 usb4 at uhci3: USB revision 1.0 uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 pms0: Synaptics touchpad, firmware 6.5 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 umass0 at uhub0 port 5 configuration 1 interface 0 "ENE UB6225" rev 2.00/1.00 addr 2 umass0: using SCSI over Bulk-Only scsibus1 at umass0: 2 targets, initiator 0 sd0 at scsibus1 targ 1 lun 0: SCSI0 0/direct removable serial.09511606146030377350 vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on wd0a (07102880cf7a51f9.a) swap on wd0b dump on wd0b urtwn0 at uhub0 port 2 configuration 1 interface 0 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 3 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R, address 14:dd:a9:2e:21:13 error: [drm:pid3999:i915_reset
Re: httpd: hsts (rfc 6797)
- Original Message - > There is a non-standard preload token that Google requires to get onto > Chrome's HSTS preload list[0] which is also used by Firefox. Any chance > of supporting this? Or is its omission a conscious decision? > > > [0] https://hstspreload.appspot.com/ > > FWIW, from my experience, the preload token presence is not yet enforced. Having "Strict-Transport-Security: max-age=31536000; includeSubDomains" is just enough. -- Marco Bonetti
Re: using httpd to distribute signify keys
- Original Message - > I'm concerned that this may be confused with a patch level, or a signature. Does a custom HTTP header create less confusion? Something similar to: HTTP/1.1 200 OK Connection: keep-alive Content-Length: 2259 Content-Type: text/html Date: Thu, 18 Jun 2015 13:45:29 GMT Last-Modified: Thu, 06 Feb 2014 04:12:39 GMT Server: OpenBSD httpd 5.7 Openbsd-Signify: RWSvUZXnw9gUb70PdeSNnpSmodCyIPJEGN1wWr+6Time1eP7KiWJ5eAM ...
