Re: startx fail on Lenovo G50-80 amd64
On Fri, Nov 27, 2015 at 09:47:23AM +, freeu...@ruggedinbox.com wrote: > I installed OpenBSD 5.8 on USB flash memory. It's fine:) > Then Lenovo G50-80 could booting. but, startx fail and xdm was fail. I would focus on startx. > 1.background is blank(black) screen, mouse icon(X and arrow) couldn't move. Was there an error message in the console about the mouse? > 3.X will draw window manager's background, but behave was strange. What WM are you using? > 5.couldn't get X.0.log If you startx, let it load and then either kill it or switch back to the console, does it show any errors? Are there any /var/log/Xorg.*.log files? > dmesg|grep drm: Could you post the full dmesg? In our dmesg archive, I see someone report that their Lenovo G50-80 works more than your report indicates. However, theirs didn't load inteldrm properly and yours did. I can't compare the two dmesgs since you snipped it. > xorg.conf: Can you try it without a xorg.conf file? It's usually not necessary. In general, try to make things simpler to debug by using startx, no xorg.conf file, a simple WM like cwm and try to find a way to get us a log file or error message. If possible, could you try installing an amd64 snapshot from tomorrow to see if it was fixed between 5.8 and -current?
Re: syslogd: Syscall 28 (SYS_sendmsg) in 18 October (i386) snapshot
On Sun, Oct 18, 2015 at 03:42:07PM -0400, Sonic wrote: > No clue if my bug is related. Attempting to upgrade -current today and I get: > Oct 18 14:29:39 stargate /bsd: ksh(4880): syscall 131 > Oct 18 14:29:46 stargate /bsd: ksh(30776): syscall 131 > etc. I don't think it's related since it's complaining about different syscalls. You ran into this situation: Old kernel: accepts "flock" pledge but doesn't require it Old ksh: no "flock" pledge New kernel: accepts "flock" and requires it for the syscall New ksh: added "flock" pledge You went from old kernel + old ksh to new kernel + old ksh. It killed ksh because old ksh didn't request "flock" pledge before calling it. The solution for me was to rebuild the userland programs that require "flock" with the old kernel and then reboot with the new kernel. However, that was yesterday and I did it shortly after that commit. It's a fast moving target. You may be better off upgrading from a snapshot and then rebuilding -current.
Re: CD's arrived
On Wed, Oct 07, 2015 at 02:51:28PM +, M Wheeler wrote: > CD's arrived today UK. Thanks again. 5.8 CD arrived today in California.
Re: problems compiling latest 5.7 patches
On Sat, Aug 22, 2015 at 02:21:49PM -0600, luke...@onemodel.org wrote: OK, I must have run an errant CVS command somewhere. (Sigh.) Thanks much for seeing that pointing it out. While you're at it, you should try running 'make -j num'. I noticed you're using GENERIC.MP but running 'make build'. My kernel compiles normally take 50s with make -j8. Without -j8, it takes around 150s. The best -j num depends on your hardware so try a few settings.
Re: smtpd.conf.5 relay tls | verify
On Tue, Aug 04, 2015 at 04:02:10PM +0200, L?VAI D?niel wrote: I maybe have overlooked something, but this syntax mentioned in the manual didn't work: accept from any for domain ... relay backup verify expire 30d ... on the other hand, this has been working: accept from any for domain ... relay backup tls verify expire 30d ... and writing only 'tls' also did work. This looks like the correct documentation fix to me. In usr.sbin/smtpd/parse.y, opt_relay allows TLS or TLS VERIFY. opt_relay_via allows for VERIFY but that's not reachable from RELAY relay. Index: smtpd.conf.5 === RCS file: /cvs/src/usr.sbin/smtpd/smtpd.conf.5,v retrieving revision 1.126 diff -p -u -r1.126 smtpd.conf.5 --- smtpd.conf.5 4 Jun 2015 14:23:00 - 1.126 +++ smtpd.conf.5 4 Aug 2015 13:53:50 - @@ -311,7 +311,7 @@ This parameter may use conversion specif .Op Ic hostname Ar name .Op Ic hostnames No Ns Ar names Ns .Op Ic pki Ar pkiname -.Op Ic tls | verify +.Op Ic tls | tls verify .Ek .Xc .Pp
New LibreSSL mailing lists
We have two new lists for LibreSSL: libre...@openbsd.org - public list for technical discussion about LibreSSL on any operating system. libressl-secur...@openbsd.org - private list for reporting severe vulnerabilities in OpenSSL or LibreSSL to the core LibreSSL team. See http://www.openbsd.org/mail.html for more details.
Re: Update OpenBSD Remotely
On Sun, May 17, 2015 at 11:52:19PM +0100, Raf Czlonka wrote: There are several things which this script does not check for - some of those are on my TODO list: I didn't review your script, but I did ctrl+s... TODO item #0 should be to use signify with SHA256.sig rather than checking SHA256 directly. There's an example in the man page. :) SHA-256 checks if the files were downloaded properly, but it does not check if the files are from us. signify with SHA256.sig provides both integrity and authentication.
Re: OpenBSD -current AHCI on HP Probook 450 G0
On Sun, Dec 21, 2014 at 10:05:22AM +, ali wrote: Atanas Vladimirov vlado at bsdbg.net writes: This is the first time when I try to install OpenBSD on a such hardware. I used bsd.rd to install it on a usb flash drive. After reboot I choose to boot from the usb drive. Bootloader can't load bsd kernel and the laptop restarts without error. If I change SATA mode in BIOS from AHCI to IDE I can boot from the usb drive. I have the same problem with my HP ProBook 4530s. I don't want to switch to AHCI. Is there another way to install OpenBSD? One of my laptops is a 4530s. I was able to install by using a CD. It's running snapshots so I upgrade with bsd.rd. I'm using BIOS F.41 if that helps.
Re: Zenocara Intel Crestline Graphics
On Sat, Oct 11, 2014 at 02:13:05PM -0700, Raymond Lillard wrote: I have the opportunity to purchase a Dell laptop with Intel Crestline Graphics hardware. Crestline appears to be marketing speak for: intel GM965/GMA X3100 Can someone advice me as to the likelihood of using the h/w or will I be limitied to the framebuffer? I think Crestline means the GMA X3100 core but not necessarily the GM965. According to Intel's ARK, it could be GM965, GME965, GL960 or GLE960. In practice, I don't think it will matter. http://ark.intel.com/products/codename/2672/Crestline One of my old laptops has a GM965 and it works fine in X. It's a Dell Inspiron 1525 that was advertised as having Crestline graphics. The only problem that I've run into on the laptop is that suspend/resume is flaky. I have 106x36 characters in the console and 1280x800 resolution in X. It uses inteldrm as Chris mentioned so you can leave machdep.allowaperture=0 and still run X. It's currently running the latest i386 snapshot. dmesg: OpenBSD 5.6-current (GENERIC.MP) #380: Sat Oct 11 15:49:59 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP ... pchb0 at pci0 dev 0 function 0 Intel GM965 Host rev 0x0c vga1 at pci0 dev 2 function 0 Intel GM965 Video rev 0x0c intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 composite sync not supported composite sync not supported inteldrm0: 1280x800 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel GM965 Video rev 0x0c at pci0 dev 2 function 1 not configured /var/log/Xorg.0.log: [67.307] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [67.307]linear framebuffer access unavailable [67.325] (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) [68.366] X.Org X Server 1.16.1 Release Date: 2014-09-21 [68.366] X Protocol Version 11, Revision 0 [68.366] Build Operating System: OpenBSD 5.6 i386 [68.366] Current Operating System: OpenBSD test.my.domain 5.6 GENERIC.MP#380 i386 [68.367] Build Date: 08 October 2014 07:48:45AM [68.367] [68.367] Current version of pixman: 0.32.6 [68.367]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [68.367] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [68.367] (==) Log file: /var/log/Xorg.0.log, Time: Sat Oct 11 21:25:51 2014 [68.370] (==) Using system config directory /usr/X11R6/share/X11/xorg.conf.d [68.372] (==) No Layout section. Using the first Screen section. [68.372] (==) No screen section available. Using defaults. [68.372] (**) |--Screen Default Screen Section (0) [68.372] (**) | |--Monitor default monitor [68.373] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [68.373] (==) Disabling SIGIO handlers for input devices [68.373] (==) Automatically adding devices [68.373] (==) Automatically enabling devices [68.373] (==) Not automatically adding GPU devices [68.373] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [68.373] (==) ModulePath set to /usr/X11R6/lib/modules [68.374] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [68.374] (II) Loader magic: 0x35fa1920 [68.374] (II) Module ABI versions: [68.374]X.Org ANSI C Emulation: 0.4 [68.374]X.Org Video Driver: 18.0 [68.374]X.Org XInput driver : 21.0 [68.374]X.Org Server Extension : 8.0 [68.375] (--) PCI:*(0:0:2:0) 8086:2a02:1028:022f rev 12, Mem @ 0xfea0/1048576, 0xe000/268435456, I/O @ 0xeff8/8 [68.375] (--) PCI: (0:0:2:1) 8086:2a03:1028:022f rev 12, Mem @ 0xfeb0/1048576 [68.375] (II) LoadModule: glx [68.377] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [68.413] (II) Module glx: vendor=X.Org Foundation [68.413]compiled for 1.16.1, module version = 1.0.0 [68.413]ABI class: X.Org Server Extension, version 8.0 [68.413] (==) AIGLX enabled [68.413] (==) Matched intel as autoconfigured driver 0 [68.413] (==) Matched vesa as autoconfigured driver 1 [68.413] (==) Assigned the driver to the xf86ConfigLayout [68.413] (II) LoadModule:
