Re: mutt can't sent smtps after upgrade to 6.7-beta
On Tue, Apr 07, 2020, Vitaliy Makkoveev wrote: > send mail via yahoo's smtps. Error is "SSL failed: error:1404B3F2:SSL > routines:ST_CONNECT:sslv3 alert unexpected message". mutt on this machine > set smtp_url = 'smtps://lo...@smtp.mail.yahoo.com:465/' Try to reproduce the problem using the openssl command and turn on various debug option to get more info, something like: openssl s_client -connect smtp.mail.yahoo.com:465 -state -debug -crlf -tlsextdebug -showcerts That will hopefully show where the problem is, e.g., TLS protocol, cipher suite, certs, ... -- Address is valid for this mailing list only, please do not reply to it direcly, but to the list.
Re: Failed to install bootblocks. You will not be able to boot OpenBSD
On Sat, Apr 4, 2020 at 1:14 AM Justin Noor wrote: > > Hello OpenBSD Community, > Hi! > [SNIP] > had no data on them, other than the FreeBSD installation sets, I decided > not to clean the boot code area with 'dd if=/dev/zero of=/dev/rsd0c bs=1 > count=1'. > > That clears one byte. You may have intended this: dd if=/dev/zero of=/dev/rsd0c bs=1M count=1 -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
Re: X start failure - OpenGL Version
On Mon, Apr 06, 2020 at 02:23:20PM +0200, Riccardo Mottola wrote: > Hi Marcus, > > Marcus MERIGHI wrote: > > Hello Riccardo, > > > > startx(1) had it's setuid bit removed. I think in the timeframe you are > > upgrading over. The canonical advice is to use xenodm(1). > > > > Marcus > > > > exactly, that was it... the error message wasn't that helpful. > > xenodm works.. but since I prefer to run X11 "when I need it" on that > machine, I just +s startx and it works fine too. > Uh, no. When you need it. doas rcctl -f start xenodm -f is to force it without enabling it in /etc/rc.conf.local You can also turn it off when done with X, but not going to shutdown. Chris
i386/amd64 boot (and pxeboot) compatibility
Hi, For a long time, the /boot and pxeboot of i386 would boot amd64's kernel and amd64's would boot i386's kernel. My tftp server had both amd64 and i386 bsd.rd files named "bsdamd64.rd" and "bsdi386.rd", snapshots downloaded daily. But recently, I discovered I could not PXE boot i386's bsd.rd from the amd64 pxeboot. I then grabbed a spare laptop, and confirmed this problem happened the other way as well -- an amd64 installed machine could not boot i386 from the amd64 /boot file. I also see the i386 and amd64 boot files have different version numbers now. So...I'm kinda inclined to guess this is not an accident, but figured I'd ask just in case it is. Nick.
mutt can't sent smtps after upgrade to 6.7-beta
After upgrading from 3 days old snapshot to 6.7-beta snapshot mutt can't send mail via yahoo's smtps. Error is "SSL failed: error:1404B3F2:SSL routines:ST_CONNECT:sslv3 alert unexpected message". mutt on this machine restored from backup to old snapshot works fine. .muttrc contains: cut begin set smtp_pass = 'password' set smtp_url = 'smtps://lo...@smtp.mail.yahoo.com:465/' set ssl_starttls = yes set ssl_force_tls = yes cut end Can anybody help?
Re: Mouse problem
Hello again, I do not have a recent dmesg, but here is one from before the incident: OpenBSD 6.6-current (GENERIC.MP) #401: Sat Oct 26 19:43:34 MDT 2019 My ThinkPad is actually running OpenBSD 6.6-current (GENERIC.MP) #107 from yesterday Apr 05 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8299085824 (7914MB) > avail mem = 8037482496 (7665MB) > warning: no entropy supplied by boot loader > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbfaa0020 (8 entries) > bios0: vendor coreboot version "CBET4000 3774c98" date 09/07/2016 > bios0: LENOVO 7459M78 > acpi0 at bios0: ACPI 3.0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP SSDT MCFG TCPA APIC DMAR HPET > acpi0: wakeup devices HDEF(S4) USB1(S4) USB2(S4) USB3(S4) EHC1(S4) > USB4(S4) USB5(S4) USB6(S4) EHC2(S4) SLT1(S4) SLT2(S4) SLT3(S4) SLT6(S4) > LANC(S3) LANR(S3) SLPB(S3) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimcfg0 at acpi0 > acpimcfg0: addr 0xf000, bus 0-63 > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM)2 CPU P8600 @ 2.40GHz, 1600.29 MHz, 06-17-0a > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI > \ > ,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN > > cpu0: 3MB 64b/line 8-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 266MHz > cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: Intel(R) Core(TM)2 CPU P8600 @ 2.40GHz, 1600.06 MHz, 06-17-0a > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI > \ > ,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN > > cpu1: 3MB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > acpihpet0 at acpi0: 14318179 Hz > acpi0: WARNING EC not initialized > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus -1 (PEGP) > acpiprt2 at acpi0: bus 1 (RP01) > acpiprt3 at acpi0: bus 2 (RP02) > acpiprt4 at acpi0: bus 3 (RP03) > acpiprt5 at acpi0: bus 4 (RP04) > acpiprt6 at acpi0: bus -1 (RP05) > acpiprt7 at acpi0: bus -1 (RP06) > acpiprt8 at acpi0: bus 5 (PCIB) > acpiec0 at acpi0 > acpicpu0 at acpi0: C1 (bogo buffer): C2 (bogo buffer): C3 (bogo buffer): > C1(@1 halt!), PSS > acpicpu1 at acpi0: C1 (bogo buffer): C2 (bogo buffer): C3 (bogo buffer): > C1(@1 halt!), PSS > acpitz0 at acpi0: critical temperature is 127 degC > acpitz1 at acpi0: critical temperature is 99 degC > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 > acpithinkpad0 at acpi0: version 1.0 > acpiac0 at acpi0: AC unit online > acpibat0 at acpi0: BAT0 not present > acpibat1 at acpi0: BAT1 not present > acpibtn0 at acpi0: SLPB > acpibtn1 at acpi0: LID_ > acpicmos0 at acpi0 > "WACF004" at acpi0 not configured > acpiac1 at acpi0: AC unit offline > acpidock0 at acpi0: DOCK docked (1) > acpivideo0 at acpi0: GFX0 > acpivout0 at acpivideo0: LCD0 > cpu0: Enhanced SpeedStep 1600 MHz: speeds: 2401, 2400, 1600, 800 MHz > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 > inteldrm0 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 > drm0 at inteldrm0 > intagp0 at inteldrm0 > agp0 at intagp0: aperture at 0xd000, size 0x1000 > inteldrm0: apic 2 int 16 > "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured > em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: msi, > address 00:1f:16:24:67:28 > uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 2 int > 16 > uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 2 int > 17 > uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 2 int > 18 > ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 2 int > 18 > usb0 at ehci0: USB revision 2.0 > uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev > 2.00/1.00 addr 1 > azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03: msi > azalia0: codecs: Conexant CX20561 > audio0 at azalia0 > ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x03 > pci1 at ppb0 bus 1 > ppb1 at pci0 dev 28 function 1 "Intel 82801I PCIE" rev 0x03 > pci2 at ppb1 bus 2 > athn0 at pci2 dev 0 function 0 "Atheros AR9285" rev 0x01: apic 2 int 17 > athn0: AR9285 rev 2 (1T1R), ROM rev 13, address 78:dd:08:c5:b3:23 > ppb2 at pci0 dev 28 function 2 "Intel 82801I PCIE" rev 0x03 > pci3 at ppb2 bus 3 > ppb3 at pci0 dev 28 function 3 "Intel 82801I PCIE" rev 0x03 > pci4 at ppb3 bus 4 > uhci3 at pci0 dev 29 function 0 "Intel
ssh-agent confirmation for use by default
Hi all, After a discussion at work, I started looking at enabling confirmation before authentication through ssh-agent by default. When logging in through xdm, the default Xsession runs `ssh-add < /dev/null` (see line 36 in /etc/X11/xdm/Xsession). My keys are loaded and I can log in to remote hosts. On some machines, I skip loading the keys or unload them after logging in and then load or re-add them using ssh-add -c, so I am asked for confirmation every time the agent is used. However, I would like this to be the default on my machines. Is there an easy way to achieve this without carrying a local diff? I checked the ssh-keygen manpage to see if there are any key-options that force this, but couldn't find anything (the options are generally to limit what happens on the remote end). ssh-add allows for it (obviously), but then you need a change to the command line, and that's in a system file: I don't want to propose that as a diff, as I don't think this makes sense in all cases (I have other machines where I wouldn't want this to happen by default). How are others doing this? Thanks, Paul -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: sysupgrade is constantly failing
On 2020-04-01, Stephan Mending wrote: > I've been experiencing issues upgrading my -current machines to the > next snapshots by upgrading via `sysupgrade -ns`. Feeding out to some mirrors isn't going great at the moment so it's likely to be a bit intermittent.
Mouse problem
Hello, I have been using OpenBSD snapshots since autumn 2018 on a ThinkPad X200. My machine is librebooted and apart from the well-known framebuffer issue during boot, everything works fine. A couple of weeks ago i accidentally spilled a glass of red wine over the keyboard. I opened the machine and cleaned it up immediately. No wine at all on the motherboard, only the keyboard was a bit soaked. I let it dry for a few days before reassembling everything. The keyboard was dry and worked normally, but the mouse function had gone wild and was out of control, both the internal TrackPoint on the keyboard and my external Logitech mouse. I had a Devuan Xfce disk in a bag and was able to deactivate the TrackPoint (separate mouse drivers and config in Devuan/Xfce/Linux). I had work to be done and kept it like that, while waiting for a new keyboard to come. Some days ago I replaced the old wine-soaked French keyboard with a brand new Norwegian keyboard and everything was perfect and normal in Devuan. When I slid the OpenBSD disk back, I discovered that the mouse function was 'frozen' (no mouse config at all obviously). I might have touched or accidentally deleted the wscons/wsmouse config when the accident initially happened. Since then I have been been trying to set up a new, working config again, reading MAN pages, forum messages and other docs on the Internet. Recovering the OpenBSD wsmouse/pointing function is probably not an extremely complicated operation, but I have not succeeded yet. Do any of you have a working clue? I should like to avoid a complete reinstall of the system. Cheers, Oddm.
Re: X start failure - OpenGL Version
Hi Marcus, Marcus MERIGHI wrote: > Hello Riccardo, > > startx(1) had it's setuid bit removed. I think in the timeframe you are > upgrading over. The canonical advice is to use xenodm(1). > > Marcus > exactly, that was it... the error message wasn't that helpful. xenodm works.. but since I prefer to run X11 "when I need it" on that machine, I just +s startx and it works fine too. Thanks for the quick help. Riccardo
Re: X start failure - OpenGL Version
Hello Riccardo,
startx(1) had it's setuid bit removed. I think in the timeframe you are
upgrading over. The canonical advice is to use xenodm(1).
Marcus
riccardo.mott...@libero.it (Riccardo Mottola), 2020.04.06 (Mon) 11:57 (CEST):
> Hi,
>
> lockdown times gave me finally times to update my workstation/home
> server to 6.6 too, after my successful laptop upgrades.
>
> I was a moment scared when fw_update told me to reboot due to microcode
> update :-P But it went fine.
>
> I followed 6.5 -> 6.6 upgrade. All packages are upgraded too (although X
> should not depent on any pkg, right?)
>
> startx fails:
>
> (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
> Require OpenGL version 2.1 or later.
> (EE)
> Fatal server error:
> (EE) AddScreen/ScreenInit failed for driver 0
> (EE)
> (EE)
> Please consult the The X.Org Foundation support
> at http://wiki.x.org
> for help.
> (EE) Please also check the log file at
> "/home/multix/.local/share/xorg/Xorg.0.log" for additional information.
> (EE)
> (EE) Server terminated with error (1). Closing log file.
>
>
> $ glxinfo | grep "OpenGL version"
> OpenGL version string: 3.1 Mesa 19.0.8
>
> and 3.1 is > 2.1 I do think...
>
> However, if I look into xorg.log, there is no "EE"! I am confused.
>
> I have an Intel graphics card and from Xorg.log everything looks fine:
>
> [ 89.926] ABI class: X.Org Video Driver, version 23.0
> [ 89.926] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
> i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
> 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
> Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35,
> Q33,
> GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
> [ 89.927] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
> [ 89.927] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
> [ 89.927] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics:
> 5200, 6200, P6300
> [ 89.930] (II) intel(0): Using Kernel Mode Setting driver: i915,
> version 1.6.0 20151010
> [ 89.933] (--) intel(0): Integrated Graphics Chipset: Intel(R) 915G
> [ 89.933] (--) intel(0): CPU: x86, sse2, sse3
> [ 89.933] (II) intel(0): Creating default Display subsection in
> Screen section
> "Default Screen Section" for depth/fbbpp 24/32
> [ 89.933] (==) intel(0): Depth 24, (--) framebuffer bpp 32
> [ 89.934] (==) intel(0): RGB weight 888
> [ 89.934] (==) intel(0): Default visual is TrueColor
> [ 89.935] (II) intel(0): Output VGA1 has no monitor section
> [ 89.935] (II) intel(0): Enabled output VGA1
> [ 89.935] (--) intel(0): Using a maximum size of 256x256 for hardware
> cursors
> [ 89.935] (II) intel(0): Output VIRTUAL1 has no monitor section
> [ 89.935] (II) intel(0): Enabled output VIRTUAL1
> [ 89.935] (--) intel(0): Output VGA1 using initial mode 1024x768 on
> pipe 0
> [ 89.936] (==) intel(0): TearFree disabled
> [ 89.936] (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
> [ 89.936] (==) intel(0): DPI set to (96, 96)
> [ 89.936] (II) Loading sub module "dri3"
> [ 89.936] (II) LoadModule: "dri3"
> [ 89.936] (II) Module "dri3" already built-in
> [ 89.936] (II) Loading sub module "dri2"
> [ 89.936] (II) LoadModule: "dri2"
> [ 89.936] (II) Module "dri2" already built-in
> [ 89.936] (II) Loading sub module "present"
> [ 89.936] (II) LoadModule: "present"
> [ 89.936] (II) Module "present" already built-in
> [ 89.936] (==) Depth 24 pixmap format is 32 bpp
> [ 89.970] (II) intel(0): SNA initialized with Alviso (gen3) backend
> [ 89.970] (==) intel(0): Backing store enabled
> [ 89.970] (==) intel(0): Silken mouse enabled
> [ 89.970] (II) intel(0): HW Cursor enabled
> [ 89.970] (II) intel(0): RandR 1.2 enabled, ignore the following
> RandR disabled message.
> [ 89.973] (==) intel(0): DPMS enabled
> [ 89.974] (II) intel(0): [DRI2] Setup complete
> [ 89.974] (II) intel(0): [DRI2] DRI driver: i915
> [ 89.974] (II) intel(0): [DRI2] VDPAU driver: i915
> [ 89.974] (II) intel(0): direct rendering: DRI2 DRI3 enabled
> [ 89.974] (II) intel(0): hardware support for Present enabled
> [ 89.974] (--) RandR disabled
> [ 90.163] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
> [ 90.163] (II) AIGLX: enabled GLX_ARB_create_context
> [ 90.163] (II) AIGLX: enabled GLX_ARB_create_context_profile
> [ 90.163] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
> [ 90.164] (II) AIGLX: enabled GLX_INTEL_swap_event
> [ 90.164] (II) AIGLX: enabled GLX_SGI_swap_control
> [ 90.164] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
> [ 90.164] (II) AIGLX: enabled GLX_ARB_fbconfig_float
> [ 90.164] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
> [ 90.164] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer
> objects
> [ 90.172] (II) AIGLX: Loaded and initialized i915
> [ 90.172]
X start failure - OpenGL Version
Hi,
lockdown times gave me finally times to update my workstation/home
server to 6.6 too, after my successful laptop upgrades.
I was a moment scared when fw_update told me to reboot due to microcode
update :-P But it went fine.
I followed 6.5 -> 6.6 upgrade. All packages are upgraded too (although X
should not depent on any pkg, right?)
startx fails:
(==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
Require OpenGL version 2.1 or later.
(EE)
Fatal server error:
(EE) AddScreen/ScreenInit failed for driver 0
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at
"/home/multix/.local/share/xorg/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.1 Mesa 19.0.8
and 3.1 is > 2.1 I do think...
However, if I look into xorg.log, there is no "EE"! I am confused.
I have an Intel graphics card and from Xorg.log everything looks fine:
[ 89.926] ABI class: X.Org Video Driver, version 23.0
[ 89.926] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35,
Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 89.927] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 89.927] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 89.927] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics:
5200, 6200, P6300
[ 89.930] (II) intel(0): Using Kernel Mode Setting driver: i915,
version 1.6.0 20151010
[ 89.933] (--) intel(0): Integrated Graphics Chipset: Intel(R) 915G
[ 89.933] (--) intel(0): CPU: x86, sse2, sse3
[ 89.933] (II) intel(0): Creating default Display subsection in
Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 89.933] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 89.934] (==) intel(0): RGB weight 888
[ 89.934] (==) intel(0): Default visual is TrueColor
[ 89.935] (II) intel(0): Output VGA1 has no monitor section
[ 89.935] (II) intel(0): Enabled output VGA1
[ 89.935] (--) intel(0): Using a maximum size of 256x256 for hardware
cursors
[ 89.935] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 89.935] (II) intel(0): Enabled output VIRTUAL1
[ 89.935] (--) intel(0): Output VGA1 using initial mode 1024x768 on
pipe 0
[ 89.936] (==) intel(0): TearFree disabled
[ 89.936] (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
[ 89.936] (==) intel(0): DPI set to (96, 96)
[ 89.936] (II) Loading sub module "dri3"
[ 89.936] (II) LoadModule: "dri3"
[ 89.936] (II) Module "dri3" already built-in
[ 89.936] (II) Loading sub module "dri2"
[ 89.936] (II) LoadModule: "dri2"
[ 89.936] (II) Module "dri2" already built-in
[ 89.936] (II) Loading sub module "present"
[ 89.936] (II) LoadModule: "present"
[ 89.936] (II) Module "present" already built-in
[ 89.936] (==) Depth 24 pixmap format is 32 bpp
[ 89.970] (II) intel(0): SNA initialized with Alviso (gen3) backend
[ 89.970] (==) intel(0): Backing store enabled
[ 89.970] (==) intel(0): Silken mouse enabled
[ 89.970] (II) intel(0): HW Cursor enabled
[ 89.970] (II) intel(0): RandR 1.2 enabled, ignore the following
RandR disabled message.
[ 89.973] (==) intel(0): DPMS enabled
[ 89.974] (II) intel(0): [DRI2] Setup complete
[ 89.974] (II) intel(0): [DRI2] DRI driver: i915
[ 89.974] (II) intel(0): [DRI2] VDPAU driver: i915
[ 89.974] (II) intel(0): direct rendering: DRI2 DRI3 enabled
[ 89.974] (II) intel(0): hardware support for Present enabled
[ 89.974] (--) RandR disabled
[ 90.163] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 90.163] (II) AIGLX: enabled GLX_ARB_create_context
[ 90.163] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 90.163] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 90.164] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 90.164] (II) AIGLX: enabled GLX_SGI_swap_control
[ 90.164] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 90.164] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 90.164] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 90.164] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer
objects
[ 90.172] (II) AIGLX: Loaded and initialized i915
[ 90.172] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 90.184] (II) intel(0): switch to mode 1024x768@60.0 on VGA1 using
pipe 0, position (0, 0), rotation normal, reflecti
on none
[ 90.195] (II) intel(0): Setting screen physical size to 270 x 203
[ 90.699] (II) config/wscons: checking input device /dev/wskbd
[ 90.699] (II) wskbd: using layout it
[ 90.700] (II) LoadModule: "kbd"
[ 90.729] (II) Loading
Re: npppd pptp hangs
On Sat, Apr 04, 2020 at 08:22:27PM +0200, Marko Cupać wrote: > On 2020-03-31 10:07, Marko Cupać wrote: > > On Mon, 30 Mar 2020 14:33:46 +0300 > > Vitaliy Makkoveev wrote: > > > > > On Mon, Mar 30, 2020 at 02:28:08PM +0300, Vitaliy Makkoveev wrote: > > > > You have pipex(4) disabled. Is it still hangs with disabled > > > > pipex(4)? As I discovered > > > > (https://marc.info/?t=15852997681=1=2), npppd with pipex(4) > > > > enabled and non-NULL "idle-timeout" option will crash kernel. You > > > > can disable this option in yout npppd.conf an reenable pipex(4). > > > > Looks like crashes should gone. > > > And don't use pppac(4) with pipex enabled, use pppx(4). Crash you > > > reported https://marc.info/?t=15850622592=1=2 is actual for > > > pppac(4). > > > > > > > Thanks for the instruction. > > > > I have: > > - left net.pipex.enable=1 > > - replaced tun1 with pppx0 in npppd.conf > > - removed 'pipex no' from npppd.conf > > > > So far so good, I'll send update if I experience further hangs. > > No crash since changing interface from tun to pppx. > > Thanx! Ok :) > > -- > Before enlightenment - chop wood, draw water. > After enlightenment - chop wood, draw water. > > Marko Cupać > https://www.mimar.rs/ >
