request for testing: bootstrapping time
Hi, If you ever wanted to be more involved in OpenBSD here's a chanche: https://marc.info/?l=openbsd-tech=155950103825035=2 It requires setting up a test machine running a recent snapshot, so that's a nice first step. Then get the sources and apply the patch, build and test You'll find help getting src and bulding the system in the FAQ. Much appreciated! -Otto
Re: firefox, sndiod and pledge
Alexandre Ratchov wrote: > On Thu, May 30, 2019 at 09:07:45PM -, Stuart Henderson wrote: > > On 2019-05-30, Hrvoje Popovski wrote: > > > Hi all, > > > > > > i'm not sure is this intended or not, but if sndiod isn't running and if > > > i want to open youtube video with firefox i got this log > > > firefox[54192]: pledge "tty", syscall 54 and firefox crashes > > > when sndiod is running everything seems fine .. > > > > Similar with chromium's main process and audio. > > > > Maybe it would be nice if libsndio had an option to say "I'm a pledged > > program, error out instead of trying to talk to the device direct > > and killing the process" ... > > I see no reason to not add the "audio" promise to programs using > audio. There are few situations where using the device directly makes > perfectly sense. I see no reason not to give firefox's main process every pledge known to man, and maybe invent a few more pledges to keep it happy. Oh come on. It is ridiculous. Thse programs are not designed to run with such restrictions. They believe they can do anything.
Re: firefox, sndiod and pledge
On Thu, May 30, 2019 at 09:07:45PM -, Stuart Henderson wrote: > On 2019-05-30, Hrvoje Popovski wrote: > > Hi all, > > > > i'm not sure is this intended or not, but if sndiod isn't running and if > > i want to open youtube video with firefox i got this log > > firefox[54192]: pledge "tty", syscall 54 and firefox crashes > > when sndiod is running everything seems fine .. > > Similar with chromium's main process and audio. > > Maybe it would be nice if libsndio had an option to say "I'm a pledged > program, error out instead of trying to talk to the device direct > and killing the process" ... I see no reason to not add the "audio" promise to programs using audio. There are few situations where using the device directly makes perfectly sense.
Re: Can't update BIOS on alix2d13 with flashrom
Did you try booting in single mode? "boot -s" at the boot prompt, then mount -a
to mount /usr/bin.
On 3 June 2019 1:47:40 am AEST, "Артур Истомин" wrote:
>I'm trying update BIOS on alix2d13 board with flashrom ver 1.0 on
>OpenBSD 6.5
>
># flashrom -w alix1.bin -p internal
>flashrom v1.0 on OpenBSD 6.5 (i386)
>flashrom is free software, get the source code at https://flashrom.org
>
>Calibrating delay loop... delay loop is unreliable, trying to continue
>OK.
>No DMI table found.
>Found chipset "AMD CS5536".
>Enabling flash write... Error while opening /dev/amdmsr: Device not
>configured
>FAILED!
>Warning: unexpected second chipset match: "AMD CS5536"
>ignoring, please report lspci and board URL to flash...@flashrom.org
>with 'CHIPSET: your board name' in the subject line.
>No EEPROM/flash device found.
>Note: flashrom can never write if the flash chip isn't found
>automatically.
>
>What's wrong?
>
>dmesg:
>
>OpenBSD 6.5 (GENERIC) #1: Wed Apr 24 22:04:27 CEST 2019
>r...@syspatch-65-i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
>real mem = 267931648 (255MB)
>avail mem = 247779328 (236MB)
>mpath0 at root
>scsibus0 at mpath0: 256 targets
>mainbus0 at root
>bios0 at mainbus0: date 11/05/08, BIOS32 rev. 0 @ 0xfd088
>pcibios0 at bios0: rev 2.1 @ 0xf/0x1
>pcibios0: pcibios_get_intr_routing - function not supported
>pcibios0: PCI IRQ Routing information unavailable.
>pcibios0: PCI bus #0 is the last bus
>bios0: ROM list: 0xe/0xa800
>cpu0 at mainbus0: (uniprocessor)
>cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD"
>586-class) 499 MHz, 05-0a-02
>cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
>mtrr: K6-family MTRR support (2 registers)
>pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
>glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
>vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10,
>address 00:0d:b9:2b:d9:3c
>ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
>0x004063, model 0x0034
>vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11,
>address 00:0d:b9:2b:d9:3d
>ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
>0x004063, model 0x0034
>vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 15,
>address 00:0d:b9:2b:d9:3e
>ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
>0x004063, model 0x0034
>athn0 at pci0 dev 12 function 0 "Atheros AR9280" rev 0x01: irq 9
>athn0: AR9280 rev 2 (2T2R), ROM rev 21, address a8:54:b2:3e:02:e7
>glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3,
>32-bit 3579545Hz timer, watchdog, gpio, i2c
>gpio0 at glxpcib0: 32 pins
>iic0 at glxpcib0
>maxtmp0 at iic0 addr 0x4c: lm86
>pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA,
>channel 0 wired to compatibility, channel 1 wired to compatibility
>wd0 at pciide0 channel 0 drive 0:
>wd0: 1-sector PIO, LBA, 15279MB, 31293360 sectors
>wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
>pciide0: channel 1 ignored (disabled)
>ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 12,
>version 1.0, legacy support
>ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 12
>usb0 at ehci0: USB revision 2.0
>uhub0 at usb0 configuration 1 interface 0 "AMD EHCI root hub" rev
>2.00/1.00 addr 1
>isa0 at glxpcib0
>isadma0 at isa0
>com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
>com0: console
>com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
>pcppi0 at isa0 port 0x61
>spkr0 at pcppi0
>npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
>usb1 at ohci0: USB revision 1.0
>uhub1 at usb1 configuration 1 interface 0 "AMD OHCI root hub" rev
>1.00/1.00 addr 1
>nvram: invalid checksum
>vscsi0 at root
>scsibus1 at vscsi0: 256 targets
>softraid0 at root
>scsibus2 at softraid0: 256 targets
>root on wd0a (93235fc23433e834.a) swap on wd0b dump on wd0b
>clock: unknown CMOS layout
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: Can't update BIOS on alix2d13 with flashrom
Flashrom isn't part of OpenBSD.
>I'm trying update BIOS on alix2d13 board with flashrom ver 1.0 on OpenBSD 6.5
>
># flashrom -w alix1.bin -p internal
>flashrom v1.0 on OpenBSD 6.5 (i386)
>flashrom is free software, get the source code at https://flashrom.org
>
>Calibrating delay loop... delay loop is unreliable, trying to continue OK.
>No DMI table found.
>Found chipset "AMD CS5536".
>Enabling flash write... Error while opening /dev/amdmsr: Device not configured
>FAILED!
>Warning: unexpected second chipset match: "AMD CS5536"
>ignoring, please report lspci and board URL to flash...@flashrom.org
>with 'CHIPSET: your board name' in the subject line.
>No EEPROM/flash device found.
>Note: flashrom can never write if the flash chip isn't found automatically.
>
>What's wrong?
>
>dmesg:
>
>OpenBSD 6.5 (GENERIC) #1: Wed Apr 24 22:04:27 CEST 2019
>r...@syspatch-65-i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
>real mem = 267931648 (255MB)
>avail mem = 247779328 (236MB)
>mpath0 at root
>scsibus0 at mpath0: 256 targets
>mainbus0 at root
>bios0 at mainbus0: date 11/05/08, BIOS32 rev. 0 @ 0xfd088
>pcibios0 at bios0: rev 2.1 @ 0xf/0x1
>pcibios0: pcibios_get_intr_routing - function not supported
>pcibios0: PCI IRQ Routing information unavailable.
>pcibios0: PCI bus #0 is the last bus
>bios0: ROM list: 0xe/0xa800
>cpu0 at mainbus0: (uniprocessor)
>cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 499
>MHz, 05-0a-02
>cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
>mtrr: K6-family MTRR support (2 registers)
>pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
>glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
>vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10, address
>00:0d:b9:2b:d9:3c
>ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
>0x004063, model 0x0034
>vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address
>00:0d:b9:2b:d9:3d
>ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
>0x004063, model 0x0034
>vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 15, address
>00:0d:b9:2b:d9:3e
>ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
>0x004063, model 0x0034
>athn0 at pci0 dev 12 function 0 "Atheros AR9280" rev 0x01: irq 9
>athn0: AR9280 rev 2 (2T2R), ROM rev 21, address a8:54:b2:3e:02:e7
>glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit
>3579545Hz timer, watchdog, gpio, i2c
>gpio0 at glxpcib0: 32 pins
>iic0 at glxpcib0
>maxtmp0 at iic0 addr 0x4c: lm86
>pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0
>wired to compatibility, channel 1 wired to compatibility
>wd0 at pciide0 channel 0 drive 0:
>wd0: 1-sector PIO, LBA, 15279MB, 31293360 sectors
>wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
>pciide0: channel 1 ignored (disabled)
>ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 12, version
>1.0, legacy support
>ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 12
>usb0 at ehci0: USB revision 2.0
>uhub0 at usb0 configuration 1 interface 0 "AMD EHCI root hub" rev 2.00/1.00
>addr 1
>isa0 at glxpcib0
>isadma0 at isa0
>com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
>com0: console
>com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
>pcppi0 at isa0 port 0x61
>spkr0 at pcppi0
>npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
>usb1 at ohci0: USB revision 1.0
>uhub1 at usb1 configuration 1 interface 0 "AMD OHCI root hub" rev 1.00/1.00
>addr 1
>nvram: invalid checksum
>vscsi0 at root
>scsibus1 at vscsi0: 256 targets
>softraid0 at root
>scsibus2 at softraid0: 256 targets
>root on wd0a (93235fc23433e834.a) swap on wd0b dump on wd0b
>clock: unknown CMOS layout
>
--
¯\_(ツ)_/¯ ¯\_(ツ)_/¯
Can't update BIOS on alix2d13 with flashrom
I'm trying update BIOS on alix2d13 board with flashrom ver 1.0 on OpenBSD 6.5
# flashrom -w alix1.bin -p internal
flashrom v1.0 on OpenBSD 6.5 (i386)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... delay loop is unreliable, trying to continue OK.
No DMI table found.
Found chipset "AMD CS5536".
Enabling flash write... Error while opening /dev/amdmsr: Device not configured
FAILED!
Warning: unexpected second chipset match: "AMD CS5536"
ignoring, please report lspci and board URL to flash...@flashrom.org
with 'CHIPSET: your board name' in the subject line.
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
What's wrong?
dmesg:
OpenBSD 6.5 (GENERIC) #1: Wed Apr 24 22:04:27 CEST 2019
r...@syspatch-65-i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem = 267931648 (255MB)
avail mem = 247779328 (236MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 11/05/08, BIOS32 rev. 0 @ 0xfd088
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xe/0xa800
cpu0 at mainbus0: (uniprocessor)
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 499
MHz, 05-0a-02
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
mtrr: K6-family MTRR support (2 registers)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10, address
00:0d:b9:2b:d9:3c
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address
00:0d:b9:2b:d9:3d
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 15, address
00:0d:b9:2b:d9:3e
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
athn0 at pci0 dev 12 function 0 "Atheros AR9280" rev 0x01: irq 9
athn0: AR9280 rev 2 (2T2R), ROM rev 21, address a8:54:b2:3e:02:e7
glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit
3579545Hz timer, watchdog, gpio, i2c
gpio0 at glxpcib0: 32 pins
iic0 at glxpcib0
maxtmp0 at iic0 addr 0x4c: lm86
pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 1-sector PIO, LBA, 15279MB, 31293360 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 12, version 1.0,
legacy support
ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 12
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "AMD EHCI root hub" rev 2.00/1.00
addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "AMD OHCI root hub" rev 1.00/1.00
addr 1
nvram: invalid checksum
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (93235fc23433e834.a) swap on wd0b dump on wd0b
clock: unknown CMOS layout
Re: Installer doesn't see sd0 on qemu guest 6.5-current
Roderick wrote: > > The Install script creates device nodes as required, because pre-creating > > 32 inodes per potential drive overflows the limited space inside the > > ramdisk. > > Well, a very good reason not to put vi in bsd.rd > > But ed is perhaps not the most comfortable in difficult situations ... The installer is meant for installation and upgrades. It is not meant for anything else. If people make their own changes to extend the mandate, we actually don't want to hear about it, because every proposal like that ignores the reality that additional features will break the media on smaller machines.
Re: Installer doesn't see sd0 on qemu guest 6.5-current
On Sun, 2 Jun 2019, Theo de Raadt wrote: The Install script creates device nodes as required, because pre-creating 32 inodes per potential drive overflows the limited space inside the ramdisk. Well, a very good reason not to put vi in bsd.rd But ed is perhaps not the most comfortable in difficult situations ... Rodrigo
Re: amd64 snapshot very broken (Jun 1 02:24:13)
I can confirm the issue. After upgrading to the newest snapshot and rebooting, boot(8) freezes while listing hard drives (hd0, hd1 etc.). On 6/1/19 4:32 PM, Christian Weisgerber wrote: The amd64 snapshot with BUILDINFO Build date: 1559355853 - Sat Jun 1 02:24:13 UTC 2019 is very broken. Specifically, the boot loader is broken. If you upgrade and the new boot(8) is installed, you may no longer be able to boot the machine. Recovering from this will require booting from a different medium. i386 may also be affected.
Re: Installer doesn't see sd0 on qemu guest 6.5-current
Maksym Sheremet wrote: > The VM is installed on a dedicated drive with FDE. It is detected as sd0 > by bsd.rd booted from install65.iso. But once installer is started the > drive disappears. Here is full output: ... > (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s > # bioctl -c C -l /dev/sd0a softraid0 > bioctl: could not open /dev/sd0a: No such file or directory > # ls /dev > MAKEDEV cua01 klogrcd0c rrd0c rwd0g rwd0o ttyC0 wd0gwd0o > bio diskmap kmemrd0arst0rwd0h rwd0p urandom wd0hwd0p > bpf enrst0 ksyms rd0crwd0a rwd0i stderr wd0awd0iwskbd0 > bpf0erst0 mem rfd0a rwd0b rwd0j stdin wd0bwd0jwskbd1 > cd0afd0anrst0 rfd0b rwd0c rwd0k stdout wd0cwd0kwskbd2 > cd0cfd0bnullrfd0c rwd0d rwd0l tty wd0dwd0lxf86 > console fd0crandom rfd0i rwd0e rwd0m tty00 wd0ewd0mzero > cua00 fd0ircd0a rrd0a rwd0f rwd0n tty01 wd0fwd0n > > > Does anyone know the cause of this problem? The Install script creates device nodes as required, because pre-creating 32 inodes per potential drive overflows the limited space inside the ramdisk.
