Re: EDID checksum is invalid

[Austin Gilbert]

> On Sep 17, 2015, at 11:51 AM, Raimo Niskanen  
> wrote:
> 
> Hello misc@
> 
> I just installed OpenBSD 5.8 from CD (i386) on an MSI MS 9A19, and it all
> went well, but when I put it in the server rack on the KVM it started to
> produce lots of error messages about "EDID checksum is invalid".  The error
> repeats almost once every minute.
> 

I found the same error message in my logs also. 

I'm running 5.7 release installed from CD. It appears to also be related to the 
use of a USB/HDMI KVM, as the log message was not present immediately after 
installation but is present after the KVM was hooked up.

USB CD/DVD burner

[Austin Gilbert]

I'm looking for recommendations for external USB DVD burners that work with 
OpenBSD 5.7 (amd64).

I did a bit of searching, the Amazon page for Samsung's TSST Ultra-slim optical 
drive SE-208GB/RSLF pulled up. Apparently, there was a comment there at one 
time referring to OpenBSD but it is no longer visible.

Anyone know if the Samsung I mentioned works or have a model they know will 
work?

Thanks in advance,
Austin

Mac Mini

[Austin Gilbert]

I have an amd64 based Mac Mini which I would like to run OpenBSD on. 

With OpenBSD 5.6, the USB keyboard works at the “boot” prompt, but not after 
booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the newly 
minted USB 3 support in current could help, but the nightly snapshot behaved 
the same as the last release version.

Is there anything I can do at the “boot” prompt to try disabling/enabling 
different device drivers for the USB ports so the keyboard will work under 
BSD.rd? 

The other option I thought of would be setting the terminal to a serial port… 
which I can’t do as I don’t have any serial ports on the box. Only Thunderbolt 
2, USB 3, Ethernet.

Re: Mac Mini

[Austin Gilbert]

 On Nov 20, 2014, at 1:27 PM, Otto Moerbeek o...@drijf.net wrote:

 On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote:

 I have an amd64 based Mac Mini which I would like to run OpenBSD on.

 With OpenBSD 5.6, the USB keyboard works at the ?boot? prompt, but not
after booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the
newly minted USB 3 support in current could help, but the nightly snapshot
behaved the same as the last release version.

 Is there anything I can do at the ?boot? prompt to try disabling/enabling
different device drivers for the USB ports so the keyboard will work under
BSD.rd?

 The other option I thought of would be setting the terminal to a serial
port? which I can?t do as I don?t have any serial ports on the box. Only
Thunderbolt 2, USB 3, Ethernet.

 There are many Mac mini models. We can tell nothing without a dmesg.

I'd love to get a dmesg, just need a way for the keyboard to work under
BSD.rd.

I was really asking if there were some tricks I could use at the 'boot' to
maybe change how the USB is getting driven.

I have no PS2 port, only USB 3 for keyboard. I also have no serial ports, so
redirecting console is not an option.

 See the FAQ on how to capture it.

Do you have a specific link that covers my specific situation?

http://www.openbsd.org/faq/faq4.html#getdmesg

Mounting a writable drive requires the keyboard to work. Yeah?

I have no serial ports I can redirect the console to.

I gather I'm just dead in the water then. I assume the normal OS developer
would debug under friendlier conditions. ;(

Re: Mac Mini

[Austin Gilbert]

On Nov 20, 2014, at 2:33 PM, Chris Cappuccio ch...@nmedia.net wrote:

 Austin Gilbert [austin.gilb...@gmail.com] wrote:
 On Nov 20, 2014, at 1:27 PM, Otto Moerbeek o...@drijf.net wrote:
 
 On Thu, Nov 20, 2014 at 12:37:58PM -0600, Austin Gilbert wrote:
 
 I have an amd64 based Mac Mini which I would like to run OpenBSD on.
 
 With OpenBSD 5.6, the USB keyboard works at the ?boot? prompt, but not
 after booting BSD.rd. The Mac Mini has USB 3 ports, I thought perhaps the
 newly minted USB 3 support in current could help, but the nightly snapshot
 behaved the same as the last release version.
 
 Is there anything I can do at the ?boot? prompt to try disabling/enabling
 different device drivers for the USB ports so the keyboard will work under
 BSD.rd?
 
 The other option I thought of would be setting the terminal to a serial
 port? which I can?t do as I don?t have any serial ports on the box. Only
 Thunderbolt 2, USB 3, Ethernet.
 
 
 You might want to try a -current snapshot. They have a USB 3 driver!

I saw the news about the USB 3 driver in current and was very excited about 
that. The first thing I did was grab a snapshot. Sadly, the snapshot BSD.rd 
behaves the same as the stable 5.6 release (as of the 16th).

Re: Mac Mini

[Austin Gilbert]

On Nov 20, 2014, at 4:08 PM, bodie bodz...@openbsd.cz wrote:

 
 What is the date of your bsd.rd and snapshot? They are new most of the time 
 daily.
 Like eg. now 20-Nov-2014 21:407.2M

Perhaps I got burned by cheating? I grabbed install56.iso burned it to a CD and 
booted that. I didn’t verify the bsd.rd on the ISO is the latest version in the 
snapshot folder. 

217M Nov 18 17:37 install56.iso

 
 Did you already try to install complete snapshot on USB flash disk and boot 
 out of it
 to see if it's issue just with bsd.rd or even with regular kernel?

Negative. When I tried installing onto the USB from my MacBook laptop (the only 
other amd64 hardware I have available) the USB wasn’t recognized. I did that 
with the 5.6 release CD not  snapshot/current, no surprise the USB 3 hardware 
wasn’t supported. 

I think at this point, I will try to go with the unattended install + SSH and 
see if I can get her up and running that way. Then I can send a dmesg and 
debugging information along to any interested parties. 

Periodic DNS resolution

[Austin Gilbert]

A problem that seems to come up over and over again with egress filtering 
firewalls are sites that move IPs so the names need to be resolved periodically 
and rules updated. 

I recently migrated to using pf and was wondering if anyone had suggestions for 
how they tackle this problem.

I realize I could create cron jobs with scripts to do this, but was curious if 
there was a better way.

I'd eventually like to track changes and log them as well.

Cheers,
Austin