amd64: can't boot 6.4, can boot 6.3
Hello, I can't install 6.4 nor snapshot. Boot hangs after: wsdisplay0 at efifb0 mux 1: console (std, vt100 emulation), using wskbd0 Motherboard is MSI B85M-G43. Can't provide full dmesg because can't boot :(
Re: amd64: can't boot 6.4, can boot 6.3
>Hello, >I can't install 6.4 nor snapshot. >Boot hangs after: >wsdisplay0 at efifb0 mux 1: console (std, vt100 emulation), using wskbd0 > >Motherboard is MSI B85M-G43. >Can't provide full dmesg because can't boot :( Oh, I forgot to add that 6.3 hangs a bit on the same line and outputs this: uhub0: port 9, set config 0 at addr3 failed uhub0: device problem, disabling port 9 and then continues booting just fine.
device node for sd1 not present
Hi,
I need to mount sd1(install media) in install shell, but it only has device
nodes for sd0(hdd).
How do I create device nodes for sd1 ?
Also, I can't execute /dev/MAKEDEV("Permission denied").
Re: device node for sd1 not present
>On Fri, Feb 08, 2019 at 04:42:42PM +0300, ??\_(???)_/?? ??\_(???)_/?? wrote:
>> Hi,
>> I need to mount sd1(install media) in install shell, but it only has device
>> nodes for sd0(hdd).
>> How do I create device nodes for sd1 ?
>> Also, I can't execute /dev/MAKEDEV("Permission denied").
>
># cd /dev && sh MAKEDEV sd1
>
**Also, I can't execute /dev/MAKEDEV("Permission denied")**
Re: device node for sd1 not present
>>On Fri, Feb 08, 2019 at 05:00:16PM +0300, ??\_(???)_/?? ??\_(???)_/?? wrote:
>>
>> >On Fri, Feb 08, 2019 at 04:42:42PM +0300, ??\_(???)_/?? ??\_(???)_/?? wrote:
>> >> Hi,
>> >> I need to mount sd1(install media) in install shell, but it only has
>> >> device nodes for sd0(hdd).
>> >> How do I create device nodes for sd1 ?
>> >> Also, I can't execute /dev/MAKEDEV("Permission denied").
>> >
>> ># cd /dev && sh MAKEDEV sd1
>> >
>> **Also, I can't execute /dev/MAKEDEV("Permission denied")**
>
>And, that is why I recommended using the "sh" command. It might work for
>you. If I recall correctly, it has been working for me on RAMDISK kernels
>since OpenBSD 3.3.
Oh I see. Thanks a lot Josh!
Re: amd64: can't boot 6.4, can boot 6.3
>On Fri, Feb 08, 2019 at 02:23:21PM +0300, ¯\_(ツ)_/¯ ¯\_(ツ)_/¯ wrote: >> Hello, >> I can't install 6.4 nor snapshot. >> Boot hangs after: >> wsdisplay0 at efifb0 mux 1: console (std, vt100 emulation), using wskbd0 >> >> Motherboard is MSI B85M-G43. >> Can't provide full dmesg because can't boot :( >> >If it boots 6.3 then you can post a dmesg from 6.3, >that will be really helpfull. ok, after some fiddling around trying to get dmesg I determined that 6.4 hangs when it can't configure usb install media, whereas 6.3 disables it and continues.
Re: CPU platform
>Hello all, > >I usually take my computers for OpenBSD from used/refurbished market >since they are much cheaper and I don't need edge hardware. Lately, >AMD processors platforms are not so easy to find ( I prefer a >combination of cpu + video + brand name). >I have a much bigger offer from Intel side. There are many options. >Regarding the Meltdown and Spectre issues, is it still fine to go for >an Intel platform? >How did you folks with Intel based production systems mitigated this? > >Thank you. AMD(and ARM for that matter) CPUs are also affected by these exploits. They're mitigated in software. OpenBSD, as well as other OS distributors, have patched it. For more information visit https://meltdownattack.com/
Re: dell universal d6000 dock
try running stable.
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
>
--
¯\_(ツ)_/¯ ¯\_(ツ)_/¯
Re: Thinkpad donation
>Hi, > >I may have one spare Thinkpad X270 in mint conditions, which I would be >willing to donate to one of the OpenBSD developers. Not sure how to >proceed with this. >I would probably prefer a developer located somewhere close to me (Czech >Republic, eastern part of Germany,…) as it will be possible for me to >hand it over personally. > >Regards > >Jan TL;DR: email dera...@openbsd.org https://www.openbsd.org/want.html
How does OpenBSD probe for I/O devices?
I've search for the answer to this question, but I can't find it. I also read the source code, but I still don't get how it works. Help pl0x
Re[2]: How does OpenBSD probe for I/O devices?
>Look under /usr/src/sys/arch/* for functions with "_attach_" in their >names, which should give you a very rough idea of where to start >looking. thanks.
