resolution, is at present, the
SeaVGABIOS does not have support for mode switching on Intel graphics
adapters. So even if we had more than one resolution available, the
SeaVGABIOS can't switch to it.
On Fri, Oct 9, 2015 at 9:14 PM, edward wandasiewicz <0.w3...@gmail.com> wrote:
> Is it possibl
Is it possible to boot OpenBSD on a device which only has one video
mode available through the BIOS?
At present, we boot in text mode via vga(4) and wscons(4).
If we have a machine compatible with inteldrm(4), it attaches, and the
dmesg output is then set to the highest resolution.
Works nicely on the Chrombook Pixel 2015 i7.
Thanks for the update Peter.
OpenBSD 5.8-current (GENERIC.MP) #1749: Wed Dec 16 01:22:42 MST 2015
real mem = 17094049792 (16302MB)
avail mem = 16571850752 (15804MB)
Update to 5.8 -current. It now works.
See 1.65 of
On 16 Dec 2015 3:14 p.m., "Mark Carroll" <m...@ixod.org> wrote:
> On 20 Nov 2015, edward wandasiewicz wrote:
> > If I try to plu
rd disk -- this indicates a disk that
> does not seem to have a valid OpenBSD disk label on it.
So hd2* means
- cannot be accessed via LBA
- no OpenBSD disklabel
> On 2015-11-30 19:28, edward wandasiewicz wrot
If I have the following showing after a probe during biosboot
disk: hd0+ hd1+* h2*
What is the meaning of '+', '+*' and '*' next to each disk?
PM, Ted Unangst <t...@tedunangst.com> wrote:
> edward wandasiewicz wrote:
>> If I have the following showing after a probe during biosboot
>> disk: hd0+ hd1+* h2*
>> What is the meaning of '+', '+*' and '*' next to each disk?
> + means big d
If I try to plug in various USB 3.0 umass(4) devices into a USB 3.0 or
USB 3.1 Type C port, nothing gets registered via dmesg, even if I add
and compile a kernel. No dmesg output upon attachment of USB 3.0 devices.
If I try, via config(8)
On 20 Nov 2015 5:54 p.m., "Martin Pieuchot" <m...@openbsd.org> wrote:
> On 20/11/15(Fri) 17:32, edward wandasiewicz wrote:
> > If I try to plug in various USB 3.0 umass(4) devices into a USB 3.0 or
> > USB 3.1 Type C port, nothing gets registered via dmesg,
what it's worth.
On Fri, Nov 20, 2015 at 5:32 PM, edward wandasiewicz <0.w3...@gmail.com>
> If I try to plug in various USB 3.0 umass(4) devices into a USB 3.0 or
> USB 3.1 Type C port, nothing gets registered via dmesg, even if I add
> option USB_DEBUG
The man page on boot(8) for amd64 says we should be able to print the
contents of the processor registers if compiled with DEBUG.
If we can do so on amd64, it seems we are missing a few debug.* files
in the amd64 source tree to do so.
% find /usr/src/sys/ -type f | xargs grep -l "DUMP_REGS"
>From your dmesg, your machine has USB 3.0 hardware ports
usb0 at xhci0: USB revision 3.0
and you're using a USB 2.0 flash drive - rev 2.00/1.10
umass0 at uhub0 port 2 configuration 1 interface 0 "Kingston
DataTraveler 2.0" rev 2.00/1.10 addr 6
You could upgrade to a USB 3.0 flash drive.
I am noticing a loss of USB connection if I accidentally / purposely
wiggle the cable near the USB type-C device end, using 6.0-current
I have 2 USB-A male to type-C cables, one implements USB 2.1, the other USB
I get the same problem with both cables.
The problem doesn't happen all
Mail list logo