Re: Mount CD/DVD and playback DVD as normal user
On Tue, Nov 12, 2013 at 9:48 PM, Laurence Rochfort laurence.rochf...@gmail.com wrote: Thanks Fred, /cdrom is the mount point, so no I don't think it should be a symlink. The command is: $ mount /dev/cd0a /cdrom mount_cd9660: /dev/cd0a on /cdrom: Operation not permitted You're pretty close. Please read this short thread http://marc.info/?l=openbsd-miscm=121837771306968w=2 which will solve it for you for sure. There are some limitations in combination of /etc/fstab and kern.usermount On 12 November 2013 20:27, Fred open...@crowsons.com wrote: On 11/12/13 18:56, Laurence Rochfort wrote: Thanks Tomas, I have set kern.usermount=1 now and added myself to the operator group, but still get operation denied when trying to mount a cdrom. Does the below look right? Thank you $ sysctl kern.usermount kern.usermount=1 $ groups laurence wheel operator $ ls -l / | grep cdrom drwxrwxr-x 2 root operator 512 Nov 8 14:29 cdrom $ ls -l /dev/cd* brwxrw 1 root operator6, 0 Nov 8 14:13 /dev/cd0a brw-rw 1 root operator6, 2 Nov 8 14:13 /dev/cd0c brw-r- 1 root operator6, 16 Nov 8 14:13 /dev/cd1a brw-r- 1 root operator6, 18 Nov 8 14:13 /dev/cd1c Surely /cdrom should be a symbolic link to /dev/cd0a? ie: ln -fs /dev/cd0a /cdrom hth Fred PS what command are you running that gives an operation denied?
Re: Mount CD/DVD and playback DVD as normal user
This might help too http://undeadly.org/cgi?action=articlesid=20131113030229mode=expanded On Wed, Nov 13, 2013 at 2:04 PM, Tomas Bodzar tomas.bod...@gmail.comwrote: On Tue, Nov 12, 2013 at 9:48 PM, Laurence Rochfort laurence.rochf...@gmail.com wrote: Thanks Fred, /cdrom is the mount point, so no I don't think it should be a symlink. The command is: $ mount /dev/cd0a /cdrom mount_cd9660: /dev/cd0a on /cdrom: Operation not permitted You're pretty close. Please read this short thread http://marc.info/?l=openbsd-miscm=121837771306968w=2 which will solve it for you for sure. There are some limitations in combination of /etc/fstab and kern.usermount On 12 November 2013 20:27, Fred open...@crowsons.com wrote: On 11/12/13 18:56, Laurence Rochfort wrote: Thanks Tomas, I have set kern.usermount=1 now and added myself to the operator group, but still get operation denied when trying to mount a cdrom. Does the below look right? Thank you $ sysctl kern.usermount kern.usermount=1 $ groups laurence wheel operator $ ls -l / | grep cdrom drwxrwxr-x 2 root operator 512 Nov 8 14:29 cdrom $ ls -l /dev/cd* brwxrw 1 root operator6, 0 Nov 8 14:13 /dev/cd0a brw-rw 1 root operator6, 2 Nov 8 14:13 /dev/cd0c brw-r- 1 root operator6, 16 Nov 8 14:13 /dev/cd1a brw-r- 1 root operator6, 18 Nov 8 14:13 /dev/cd1c Surely /cdrom should be a symbolic link to /dev/cd0a? ie: ln -fs /dev/cd0a /cdrom hth Fred PS what command are you running that gives an operation denied?
Re: Cellular network modems
Related to that is problem with new smartphones operating on MTP protocol https://en.wikipedia.org/wiki/Media_Transfer_Protocol and not over regular USB host. Because of recently added fuse support in OpenBSD it may be possible to access at least files, music, video on those phones eg. via http://www.adebenham.com/mtpfs/ . But access to internal GSM modem is not provided anymore. Yeah, there's ability to create Wifi hotspot and share 2G/3G over that, but if one wants to use pppd and such for direct access or com for sheer fun... On Wed, Nov 13, 2013 at 5:16 AM, patrick keshishian pkesh...@gmail.comwrote: On 11/12/13, Stijn mail.st...@telenet.be wrote: On 11/11/2013 22:22, patrick keshishian wrote: Greetings, Saw this semi-related post[1], posting separately not to hijack it. Searching marc.info for cellular modem on misc@ archives finds mostly old, and posts about using mobile phones as cellular modems. Are there standalone cellular modem devices known to work with OpenBSD? Multi-Tech's QuickCarrier USB-D[2] caught my attention. --patrick [1] http://marc.info/?l=openbsd-miscm=138419004519701w=2 [2] http://www.multitech.com/en_US/PRODUCTS/Families/QuickCarrierUSBD/ Not OpenBSD per se, but I've been using the following Huawei device (via wifi) with great success: http://consumer.huawei.com/en/portable-internet/mobile-wifi/tech-specs/e5220-en.htm Thanks. That device is essentially what I'm looking for. A local WiFi to cellular network router. MultiTech also has similar, more industrial grade, cellular routers for local LAN (ethernet). This was a great reference, helping me get to: http://consumer.huawei.com/en/solutions/m2m-solutions/overview/index.htm Cheers, --patrick Basically it sets up a wireless hotspot so as long as your device has a wireless NIC you can have 3G connectivity. FYI, I just tried to see if USB tethering is working on this device but with no luck. Looks like the device ID is unknown(?) Anyway, dmesg and the usbdevs -dv output are available below. I also disconnected and reconnected the device so you can see what it spits out on the console. HTH, Stijn --- dmesg OpenBSD 5.4 (GENERIC) #37: Tue Jul 30 12:05:01 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(R) M processor 900MHz (GenuineIntel 686-class) 901 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,NXE,PERF real mem = 1064366080 (1015MB) avail mem = 1035530240 (987MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 09/11/08, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0xf06f0 (37 entries) bios0: vendor American Megatrends Inc. version 0906 date 09/11/2008 bios0: ASUSTeK Computer INC. 900 acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC OEMB MCFG acpi0: wakeup devices P0P3(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) MC97(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) EUSB(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 100MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 5 (P0P3) acpiprt2 at acpi0: bus 3 (P0P5) acpiprt3 at acpi0: bus 1 (P0P6) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2 acpitz0 at acpi0: critical temperature is 90 degC acpibat0 at acpi0: BAT0 model 900 serial type LION oem ASUS acpiac0 at acpi0: AC unit online acpiasus0 at acpi0 acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: PWRB bios0: ROM list: 0xc/0xf800! pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82915GM Host rev 0x04 vga1 at pci0 dev 2 function 0 Intel 82915GM Video rev 0x04 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x600 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 82915GM Video rev 0x04 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801FB HD Audio rev 0x04: msi azalia0: codecs: Realtek ALC662 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801FB PCIE rev 0x04: apic 1 int 16 pci1 at ppb0 bus 4 ppb1 at pci0 dev 28 function 1 Intel 82801FB PCIE rev 0x04: apic 1 int 17 pci2 at ppb1 bus 3 lii0 at pci2 dev 0 function 0 Attansic Technology L2 rev 0xa0: apic 1 int 17, address 00:22:15:22:f5:9e atphy0 at lii0 phy 1: F2 10/100 PHY, rev. 2 ppb2 at pci0 dev 28 function 2 Intel 82801FB PCIE rev 0x04: apic 1 int 18 pci3 at ppb2 bus 1 uhci0 at pci0 dev 29 function 0 Intel 82801FB USB rev 0x04: apic 1 int 23 uhci1 at pci0
Re: GM45 gpu hung error
Hello dear OpenBSD people, does anyone of the developers have time to look at this issue? It is the same problem I reported here: http://marc.info/?l=openbsd-bugsm=137388801502300w=2 but unfortunately it was not fixed. After Mesa 9.x it got worse, now additionaly there are visual artifacts in mplayer -vo gl, in Firefox images are corrupted, in chromium everything (scroll bars, images) becomes corrupted, openarena now runs, but, for example, neverball does not. GL output in mplayer has become much slower, the computer is not able to play 1080p videos in native resolution anymore. All of this is very sad. I waited for 5.4 to be released so more people report this. Personally I can reproduce this on 2 computers with GM45 as I reported earlier.
Re: GM45 gpu hung error
Please try a most recent snapshot. There have been massive fixes added since 5.4, and some especially important fixes added very recently. On 2013 Nov 13 (Wed) at 10:51:45 +0200 (+0200), ja...@cieti.lv wrote: :Hello dear OpenBSD people, : :does anyone of the developers have time to look at this issue? It is :the same problem I reported here: :http://marc.info/?l=openbsd-bugsm=137388801502300w=2 but :unfortunately it was not fixed. : :After Mesa 9.x it got worse, now additionaly there are visual :artifacts in mplayer -vo gl, :in Firefox images are corrupted, in chromium everything (scroll bars, :images) becomes corrupted, openarena now runs, but, for example, :neverball does not. GL output in mplayer has become much slower, the :computer is not able to play 1080p videos in native resolution :anymore. All of this is very sad. : :I waited for 5.4 to be released so more people report this. :Personally I can reproduce this on 2 computers with GM45 as I :reported earlier. : -- All syllogisms have three parts; therefore this is not a syllogism.
Re: GM45 gpu hung error
Please try a most recent snapshot. There have been massive fixes added since 5.4, and some especially important fixes added very recently. On 2013 Nov 13 (Wed) at 10:51:45 +0200 (+0200), ja...@cieti.lv wrote: :Hello dear OpenBSD people, : :does anyone of the developers have time to look at this issue? It is :the same problem I reported here: :http://marc.info/?l=openbsd-bugsm=137388801502300w=2 but :unfortunately it was not fixed. : :After Mesa 9.x it got worse, now additionaly there are visual :artifacts in mplayer -vo gl, :in Firefox images are corrupted, in chromium everything (scroll bars, :images) becomes corrupted, openarena now runs, but, for example, :neverball does not. GL output in mplayer has become much slower, the :computer is not able to play 1080p videos in native resolution :anymore. All of this is very sad. : :I waited for 5.4 to be released so more people report this. :Personally I can reproduce this on 2 computers with GM45 as I :reported earlier. : I am talking about recent snapshot. I use -current from 7/30/13 and I try out snapshots often to see if the problem is gone but it is not. It got worse. I have seen brutal turn-offs while booting too. It is a very old issue, I suspect it came up after http://freshbsd.org/commit/openbsd/304417ea27d0874895cc4e65c30324b7bd14ac22 but I cannot test it, because noone could explain to me how to build a source from that date as you can see it this thread: http://marc.info/?l=openbsd-bugsm=137388801502300w=2
Re: GM45 gpu hung error
On 2013 Nov 13 (Wed) at 12:33:00 +0200 (+0200), ja...@cieti.lv wrote: :I am talking about recent snapshot. I use -current from 7/30/13 and I Recent as in the last 4 days. The recent fixes are *very* *very* recent. -- I often quote myself; it adds spice to my conversation. -- G. B. Shaw
Re: GM45 gpu hung error
:I am talking about recent snapshot. I use -current from 7/30/13 and I Recent as in the last 4 days. The recent fixes are *very* *very* recent. OK, thanks for now. I'll test it and report the results as soon as I get to my notebook.
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 11:47 AM, ja...@cieti.lv wrote: :I am talking about recent snapshot. I use -current from 7/30/13 and I Recent as in the last 4 days. The recent fixes are *very* *very* recent. OK, thanks for now. I'll test it and report the results as soon as I get to my notebook. Because eg. Claudio has snapshot from 10.11.2013, but here are visible at least two patches for Intel DRM from 11.11.2013 related to hangs and locks of GPU http://marc.info/?l=openbsd-cvsw=2r=1s=drmq=b , as well Mesa 9.2.2 imported 9.11.2013 (but that's supposed to be in 10.10.2013 snapshot)
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 11:47 AM, ja...@cieti.lv wrote: :I am talking about recent snapshot. I use -current from 7/30/13 and I Recent as in the last 4 days. The recent fixes are *very* *very* recent. OK, thanks for now. I'll test it and report the results as soon as I get to my notebook. Because eg. Claudio has snapshot from 10.11.2013, but here are visible at least two patches for Intel DRM from 11.11.2013 related to hangs and locks of GPU http://marc.info/?l=openbsd-cvsw=2r=1s=drmq=b [1] , as well Mesa 9.2.2 imported 9.11.2013 (but that's supposed to be in 10.10.2013 snapshot) Aren't those fixes related to Haswell? I watch CVS commits closely to see if anything goes in that looks like a fix. Jonathan Gray once said that there may be fixes in newer versions of xf86-video-intel, but some gcc extension is required that OpenBSD does not have.
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 12:07 PM, ja...@cieti.lv wrote: On Wed, Nov 13, 2013 at 11:47 AM, ja...@cieti.lv wrote: :I am talking about recent snapshot. I use -current from 7/30/13 and I Recent as in the last 4 days. The recent fixes are *very* *very* recent. OK, thanks for now. I'll test it and report the results as soon as I get to my notebook. Because eg. Claudio has snapshot from 10.11.2013, but here are visible at least two patches for Intel DRM from 11.11.2013 related to hangs and locks of GPU http://marc.info/?l=openbsd-cvsw=2r=1s=drmq=b [1] , as well Mesa 9.2.2 imported 9.11.2013 (but that's supposed to be in 10.10.2013 snapshot) Aren't those fixes related to Haswell? I watch CVS commits closely to see if anything goes in that looks like a fix. Jonathan Gray once said that there may be fixes in newer versions of xf86-video-intel, but some gcc extension is required that OpenBSD does not have. Right, my fault. Missed complete path in output. Those are for Haswell
Re: GM45 gpu hung error
Tomas Bodzar tomas.bodzar at gmail.com writes: Right, my fault. Missed complete path in output. Those are for Haswell Looking at mentioned commits, at least cursor update diffs aren't strictly Haswell related. So Mesa update.
[OT] Loongson hardware in Europe
Having long wanted to run http://www.openbsd.org/loongson.html, I've just seen that the main EU vendor of Loongson/Lemote/Yeeloong has finally —temporarily, they say— significantly cut the hitherto relatively high cost of these machines. I'm not going to spam the URL, but if this interests you and you can't figure out who this is (it's not Wim; it's the other guys), then drop me a line. (I'm not affilitated with any of the aforesaid; I'm just posting because I would have appreciated the heads-up if I hadn't discovered this myself.)
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 2:30 PM, Claudio claudiozu...@gmail.com wrote: On Wed, Nov 13, 2013 at 12:12:47PM +, Alexey E. Suslikov wrote: Tomas Bodzar tomas.bodzar at gmail.com writes: Right, my fault. Missed complete path in output. Those are for Haswell Looking at mentioned commits, at least cursor update diffs aren't strictly Haswell related. So Mesa update. I've tried with the latst snapshot but there are still issues: dmesg: OpenBSD 5.4-current (GENERIC) #126: Tue Nov 12 16:30:10 MST 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 4166717440 (3973MB) avail mem = 4047704064 (3860MB) snip cpu0: Enhanced SpeedStep 798 MHz: speeds: 2534, 2533, 1600, 800 MHz (maybe) not related to GPU hangs, but having CPU run at 798 MHz is strange. have you tried to put hw.setperf=100 to /etc/sysctl.conf ?
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 03:06:08PM +0200, Alexey Suslikov wrote: On Wed, Nov 13, 2013 at 2:30 PM, Claudio claudiozu...@gmail.com wrote: On Wed, Nov 13, 2013 at 12:12:47PM +, Alexey E. Suslikov wrote: Tomas Bodzar tomas.bodzar at gmail.com writes: Right, my fault. Missed complete path in output. Those are for Haswell Looking at mentioned commits, at least cursor update diffs aren't strictly Haswell related. So Mesa update. I've tried with the latst snapshot but there are still issues: dmesg: OpenBSD 5.4-current (GENERIC) #126: Tue Nov 12 16:30:10 MST 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 4166717440 (3973MB) avail mem = 4047704064 (3860MB) snip cpu0: Enhanced SpeedStep 798 MHz: speeds: 2534, 2533, 1600, 800 MHz (maybe) not related to GPU hangs, but having CPU run at 798 MHz is strange. have you tried to put hw.setperf=100 to /etc/sysctl.conf ? I've tried but there was no change, the reason it was running that low I think was apmd.
Re: Mount CD/DVD and playback DVD as normal user
Laurence Rochfort laurence.rochf...@gmail.com wrote: What are the consequences of putting myself in the operator group? Members of group operator may * run shutdown(8), * read disk devices--intended for backups with dump(8), but of course it means that members can bypass any filesystem-permission-based read restrictions. -- Christian naddy Weisgerber na...@mips.inka.de
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 3:18 PM, Claudio claudiozu...@gmail.com wrote: On Wed, Nov 13, 2013 at 03:06:08PM +0200, Alexey Suslikov wrote: On Wed, Nov 13, 2013 at 2:30 PM, Claudio claudiozu...@gmail.com wrote: On Wed, Nov 13, 2013 at 12:12:47PM +, Alexey E. Suslikov wrote: Tomas Bodzar tomas.bodzar at gmail.com writes: Right, my fault. Missed complete path in output. Those are for Haswell Looking at mentioned commits, at least cursor update diffs aren't strictly Haswell related. So Mesa update. I've tried with the latst snapshot but there are still issues: dmesg: OpenBSD 5.4-current (GENERIC) #126: Tue Nov 12 16:30:10 MST 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 4166717440 (3973MB) avail mem = 4047704064 (3860MB) snip cpu0: Enhanced SpeedStep 798 MHz: speeds: 2534, 2533, 1600, 800 MHz (maybe) not related to GPU hangs, but having CPU run at 798 MHz is strange. have you tried to put hw.setperf=100 to /etc/sysctl.conf ? I've tried but there was no change, the reason it was running that low I think was apmd. I think you should disable apmd, cold boot and retest.
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 03:20:58PM +0200, Alexey Suslikov wrote: On Wed, Nov 13, 2013 at 3:18 PM, Claudio claudiozu...@gmail.com wrote: On Wed, Nov 13, 2013 at 03:06:08PM +0200, Alexey Suslikov wrote: On Wed, Nov 13, 2013 at 2:30 PM, Claudio claudiozu...@gmail.com wrote: On Wed, Nov 13, 2013 at 12:12:47PM +, Alexey E. Suslikov wrote: Tomas Bodzar tomas.bodzar at gmail.com writes: Right, my fault. Missed complete path in output. Those are for Haswell Looking at mentioned commits, at least cursor update diffs aren't strictly Haswell related. So Mesa update. I've tried with the latst snapshot but there are still issues: dmesg: OpenBSD 5.4-current (GENERIC) #126: Tue Nov 12 16:30:10 MST 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 4166717440 (3973MB) avail mem = 4047704064 (3860MB) snip cpu0: Enhanced SpeedStep 798 MHz: speeds: 2534, 2533, 1600, 800 MHz (maybe) not related to GPU hangs, but having CPU run at 798 MHz is strange. have you tried to put hw.setperf=100 to /etc/sysctl.conf ? I've tried but there was no change, the reason it was running that low I think was apmd. I think you should disable apmd, cold boot and retest. Still no luck and the cpu still seems to run at a super low frequency? dmesg: OpenBSD 5.4-current (GENERIC) #126: Tue Nov 12 16:30:10 MST 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 4166717440 (3973MB) avail mem = 4047704064 (3860MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (74 entries) bios0: vendor LENOVO version 7UET66WW (2.16 ) date 04/22/2009 bios0: LENOVO 2768HJ2 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P9500 @ 2.53GHz, 798.14 MHz 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 cpu0: 6MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 266MHz cpu at mainbus0: not configured ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus -1 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS: resource for USB0, USB3, USB5, EHC0, EHC1 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 92P1137 serial25 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) cpu0: Enhanced SpeedStep 798 MHz: speeds: 2534, 2533, 1600, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07 vga1 at pci0 dev 2 function 0 Intel GM45 Video rev 0x07 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1440x900 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel GM45 Video rev 0x07 at pci0 dev 2 function 1 not configured Intel GM45 HECI rev 0x07 at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 Intel GM45 PT IDER rev 0x07: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 1 int 18 for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) puc0 at pci0 dev 3 function 3 Intel GM45 KT rev 0x07: ports: 1 com com4 at puc0 port 0 apic 1 int 17: ns16550a, 16 byte fifo com4: probed fifo depth: 15 bytes em0 at pci0 dev 25 function 0 Intel ICH9 IGP M AMT rev 0x03: msi, address 00:22:68:12:2d:ef uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 1 int 21 uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 1 int 22 ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 1 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 4:18 PM, Claudio claudiozu...@gmail.com wrote: After updating the bios and setting setperf I can no longer reproduce the issue :), I'll try enabling apmd again later and check how it runs. (On an unrelated note Firefox uses incredibly high amounts of cpu compared to chromium and is very sluggish, I thought it was because of the low frequency but it still does.) Unless you run firewall on this box, why not GENERIC.MP? P9500 is dual core.
Re: [OT] Loongson hardware in Europe
ropers rop...@gmail.com wrote: Having long wanted to run http://www.openbsd.org/loongson.html, I've just seen that the main EU vendor of Loongson/Lemote/Yeeloong has finally -temporarily, they say- significantly cut the hitherto relatively high cost of these machines. I'm not going to spam the URL, but if this interests you and you can't figure out who this is (it's not Wim; it's the other guys), then drop me a line. What a stupid game. Are you talking about tekmote.nl? -- Christian naddy Weisgerber na...@mips.inka.de
Re: [OT] Loongson hardware in Europe
On Wed, Nov 13, 2013 at 1:35 PM, ropers rop...@gmail.com wrote: Having long wanted to run http://www.openbsd.org/loongson.html, I've just seen that the main EU vendor of Loongson/Lemote/Yeeloong has finally âtemporarily, they sayâ significantly cut the hitherto relatively high cost of these machines. I'm not going to spam the URL, but if this interests you and you can't figure out who this is (it's not Wim; it's the other guys), then drop me a line. (I'm not affilitated with any of the aforesaid; I'm just posting because I would have appreciated the heads-up if I hadn't discovered this myself.) I will spam for you :-) http://www.tekmote.nl/epages/61504599.sf/en_GB/?ViewObjectPath=%2FShops%2F615 04599it's interesting discount, however valid only till 18.11 , still I think that's somewhat overpriced, especially older models. Yeah I know, not so big amount of units and so on, but still those EU rules..
Re: [OT] Loongson hardware in Europe
On 11/13/2013 9:56 AM, Christian Weisgerber wrote: ropers rop...@gmail.com wrote: Having long wanted to run http://www.openbsd.org/loongson.html, I've just seen that the main EU vendor of Loongson/Lemote/Yeeloong has finally -temporarily, they say- significantly cut the hitherto relatively high cost of these machines. I'm not going to spam the URL, but if this interests you and you can't figure out who this is (it's not Wim; it's the other guys), then drop me a line. What a stupid game. Are you talking about tekmote.nl? He is. I was just donated a Loongson-3A laptop from that sale.
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 11:47 AM, ja...@cieti.lv wrote: :I am talking about recent snapshot. I use -current from 7/30/13 and I Recent as in the last 4 days. The recent fixes are *very* *very* recent. OK, thanks for now. I'll test it and report the results as soon as I get to my notebook. Because eg. Claudio has snapshot from 10.11.2013, but here are visible at least two patches for Intel DRM from 11.11.2013 related to hangs and locks of GPU http://marc.info/?l=openbsd-cvsw=2r=1s=drmq=b , as well Mesa 9.2.2 imported 9.11.2013 (but that's supposed to be in 10.10.2013 snapshot) And until 9 hours ago, that code was not built into a snapshot.
Re: GM45 gpu hung error
janis at cieti.lv writes: Hello dear OpenBSD people, does anyone of the developers have time to look at this issue? It is the same problem I reported here: http://marc.info/?l=openbsd-bugsm=137388801502300w=2 but unfortunately bios0: vendor Dell Inc. version A24 date 12/06/2011 bios0: Dell Inc. Latitude E4300 This model has Latitude E4300 System BIOS A26 available.
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 4:54 PM, Tomas Bodzar tomas.bod...@gmail.com wrote: Yeah, however Firefox is running pretty badly after introduction of KMS on my Dell E6320 (tried like 3 weeks ago or so), Chromium was simply just crashing all the time. could you provide dmesg with most recent -current?
Re: [OT] Loongson hardware in Europe
On Wed, Nov 13, 2013 at 10:03:58AM -0500, Brian Callahan wrote: On 11/13/2013 9:56 AM, Christian Weisgerber wrote: ropers rop...@gmail.com wrote: Having long wanted to run http://www.openbsd.org/loongson.html, I've just seen that the main EU vendor of Loongson/Lemote/Yeeloong has finally -temporarily, they say- significantly cut the hitherto relatively high cost of these machines. I'm not going to spam the URL, but if this interests you and you can't figure out who this is (it's not Wim; it's the other guys), then drop me a line. What a stupid game. Are you talking about tekmote.nl? He is. I was just donated a Loongson-3A laptop from that sale. For the same price as of a low-end amd64 laptop you get: Processor: LoongSon 3A, 900MHz [...] Battery duration: 2,5 hours after recharging And then the motto: Apple in Linux hardware! What a joke... Thanks to this thread I remembered the disappointment when the 3A was announced.
Re: GM45 gpu hung error
On 11/13/13 14:54, Tomas Bodzar wrote: my Dell E6320 (tried like 3 weeks ago or so), Chromium was simply just crashing all the time. A fix for chromium went in to ports around the 4 November: http://marc.info/?l=openbsd-portsm=138353073228230 port:fred ~ chrome --version Chromium 30.0.1599.101 solved the crashing issues I was having with chrome. hth Fred
Re: GM45 gpu hung error
bios0: vendor Dell Inc. version A24 date 12/06/2011 bios0: Dell Inc. Latitude E4300 This model has Latitude E4300 System BIOS A26 available. I have updated the BIOS already to A26. The story is that everything was great after KMS was introduced, but then at some point a diff was reduced to Linux or something else, which caused aforementioned problems. Just installed a fresh snapshot -- didn't work. Rebuilt kernel from source -- nothing improves. Here is a fresh dmesg: OpenBSD 5.4-current (GENERIC.MP) #0: Wed Nov 13 20:06:09 EET 2013 ja...@test.apollo.lv:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8523141120 (8128MB) avail mem = 8288120832 (7904MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf64f0 (54 entries) bios0: vendor Dell Inc. version A26 date 06/04/2013 bios0: Dell Inc. Latitude E4300 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET DMAR APIC ASF! MCFG TCPA SLIC BOOT SSDT acpi0: wakeup devices PCI0(S4) PCIE(S4) USB1(S0) USB2(S0) USB3(S0) USB4(S0) USB5(S0) USB6(S0) EHC2(S0) EHCI(S0) AZAL(S3) RP01(S4) RP02(S4) RP03(S3) RP04(S3) RP05(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P9400 @ 2.40GHz, 2394.40 MHz 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,NXE,LONG,LAHF,PERF cpu0: 6MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 265MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P9400 @ 2.40GHz, 2394.00 MHz 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,NXE,LONG,LAHF,PERF cpu1: 6MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 2 (PCIE) acpiprt1 at acpi0: bus 11 (RP01) acpiprt2 at acpi0: bus 12 (RP02) acpiprt3 at acpi0: bus -1 (RP03) acpiprt4 at acpi0: bus 13 (RP04) acpiprt5 at acpi0: bus -1 (RP05) acpiprt6 at acpi0: bus -1 (RP06) acpiprt7 at acpi0: bus 0 (PCI0) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0: critical temperature is 107 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PBTN acpibtn2 at acpi0: SBTN acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model DELL KG87596 serial 5951 type LION oem Samsung SDI acpibat1 at acpi0: BAT1 not present acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: LCD_ acpivideo1 at acpi0: VID2 cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2401, 2400, 1600, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07 vga1 at pci0 dev 2 function 0 Intel GM45 Video rev 0x07 intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) 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:21:70:e6:04:f3 uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 2 int 20 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 2 int 21 uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 2 int 22 ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 2 int 22 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 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: IDT 92HD71B7, Intel/0x2802, using IDT 92HD71B7 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x03: msi pci1 at ppb0 bus 11 ppb1 at pci0 dev 28 function 1 Intel 82801I PCIE rev 0x03: msi pci2 at ppb1 bus 12 iwn0 at pci2 dev 0 function 0 Intel WiFi Link 5100 rev 0x00: msi, MIMO 1T2R, MoW, address 00:22:fb:0e:8b:c4 ppb2 at pci0 dev 28 function 3 Intel 82801I PCIE rev 0x03: msi pci3 at ppb2 bus 13 uhci3 at pci0 dev 29 function 0 Intel 82801I USB rev 0x03: apic 2 int 20 uhci4 at pci0 dev 29 function 1 Intel 82801I USB rev 0x03: apic 2 int 21 uhci5 at pci0 dev 29 function 2 Intel 82801I USB rev 0x03: apic 2 int 22 ehci1 at pci0 dev 29 function 7 Intel 82801I USB rev 0x03: apic 2 int 20 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb3 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x93 pci4 at ppb3 bus 2 Ricoh 5C832 Firewire rev 0x05 at
Re: GM45 gpu hung error
I have updated the BIOS already to A26. The story is that everything was great after KMS was introduced, but then at some point a diff was reduced to Linux or something else, which caused aforementioned problems. Awesome! So since you know it was a diff, can you isolate it specifically? That's the process. Thanks.
Re: GM45 gpu hung error
On 13.11.2013 20:24, Theo de Raadt wrote: I have updated the BIOS already to A26. The story is that everything was great after KMS was introduced, but then at some point a diff was reduced to Linux or something else, which caused aforementioned problems. Awesome! So since you know it was a diff, can you isolate it specifically? That's the process. Thanks. Sure. Please teach me how to get the source from a specific date to build and I'm on it. Last time I tried, it did not work. See here: http://marc.info/?l=openbsd-bugsm=137447697607912w=2 What am I doing wrong?
Re: GM45 gpu hung error
janis at cieti.lv writes: bios0: vendor Dell Inc. version A24 date 12/06/2011 bios0: Dell Inc. Latitude E4300 This model has Latitude E4300 System BIOS A26 available. I have updated the BIOS already to A26. The story is that everything was great after KMS was introduced, but then at some point a diff was reduced to Linux or something else, which caused aforementioned problems. there are not *too* much drm related diffs with reduce+linux in commit message. I've found about 10. if you experience above mentioned ... hung message, I think, you could start by reverting http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/drm/i915/i915_irq.c.diff?r1=1.3;r2=1.4;f=h
Re: GM45 gpu hung error
On 13 November 2013 20:31, ja...@cieti.lv wrote: On 13.11.2013 20:24, Theo de Raadt wrote: I have updated the BIOS already to A26. The story is that everything was great after KMS was introduced, but then at some point a diff was reduced to Linux or something else, which caused aforementioned problems. Awesome! So since you know it was a diff, can you isolate it specifically? That's the process. Thanks. Sure. Please teach me how to get the source from a specific date to build and I'm on it. Last time I tried, it did not work. See here: http://marc.info/?l=openbsd-bugsm=137447697607912w=2 What am I doing wrong? Hello, ahem.. you are not revealing all the needed information Tried to compile, but got an error. Please specify all the commands you used in compiling, thanks. Wild guess, you forgot to make depend? -- Regards, Ville Valkonen
Re: BGP changes to support CARP better
On 13-11-11 11:48 PM, Chris Cappuccio wrote:
Adam Thompson [athom...@athompso.net] wrote:
Well, you could - perhaps - flip this on its head. Instead of changing BGP,
what about forcing one router to be the master (via advbase/advskew),
advertising a lower BGP preference (probably by using both localpref for
iBGP and path prepending for eBGP) from the slave, using pfsync (default,
not defer) to sync the state tables, and simply assuming that if the slave
becomes the master it's because the master is dead, so losing a few packets
isn't the end of the world?
If you're talking about eBGP..or even iBGP for that matter, an interesting
way to go could be:
Two BGP sessions from different IPs (no CARP)
BGP next-hop pointing to CARP-protected IP
I'm trying this, but I'm not sure it's actually working. I suspect
bgpd.conf cluelessness on my part, suggestions appreciated.
Existing situation:
- dedicated VLAN 207 and X.X.X.160/28 for BGP interconnect
- one router on their side (perhaps one logical router, using VRRP),
two routers on my side (R{1,2}).
- carp207 (X.X.X.162) on vlan207 (X.X.X.{163,164}) on trunk0
- existing bgpd.conf works, each router (R1,R2) has 2 IPv4 neighbours:
its redundant copy (R2/R1) and the upstream (.161). Very simple config,
will email off-list if desired.
Change:
- added match to X.X.X.161 set nexthop X.X.X.162 before the existing
allow to any on both R1 R2
(I thought about doing network x.x.x.x/xx set nexthop X.X.X.162
globally, but worried that will affect too many things later.)
Result:
- no change, according to upstream provider
- traceroute inbound shows replies from .163 (right now, anyway)
Am I misunderstanding the syntax, or perhaps making some more
fundamental error? I can also anonymize and post bgpd.conf here if needed.
--
-Adam Thompson
athom...@athompso.net
Re: GM45 gpu hung error
On 13 November 2013 20:31, ja...@cieti.lv wrote: On 13.11.2013 20:24, Theo de Raadt wrote: I have updated the BIOS already to A26. The story is that everything was great after KMS was introduced, but then at some point a diff was reduced to Linux or something else, which caused aforementioned problems. Awesome! So since you know it was a diff, can you isolate it specifically? That's the process. Thanks. Sure. Please teach me how to get the source from a specific date to build and I'm on it. Last time I tried, it did not work. See here: http://marc.info/?l=openbsd-bugsm=137447697607912w=2 What am I doing wrong? Hello, ahem.. you are not revealing all the needed information Tried to compile, but got an error. Please specify all the commands you used in compiling, thanks. Wild guess, you forgot to make depend? -- Regards, Ville Valkonen Hello, back then I did like this: http://marc.info/?l=openbsd-bugsm=137448659410735w=2 When is the make depend needed? I can't see it here: http://openbsd.org/faq/faq5.html#Bld
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 09:07:48PM +0200, Ville Valkonen wrote: ahem.. you are not revealing all the needed information Tried to compile, but got an error. Please specify all the commands you used in compiling, thanks. Wild guess, you forgot to make depend? No he didn't. 'make depend' is the failing build target. *** Error 1 in lib (bsd.subdir.mk:48 'depend') (from http://marc.info/?l=openbsd-bugsm=137447893908485w=2) The info is spread across several posts so it takes some time to hunt it down. Janis later provided the build commands he used: http://marc.info/?l=openbsd-bugsm=137448659410735w=2 I can reproduce the problem on a 5.3 sparc64 system. Janis, if you'd like, contact me off-list, and I'll try to help you with the bisection process.
QEMU CPU cores not showing up
Hello, I have a QEMU instance that works perfectly fine at detecting cpu cores on NetBSD/FreeBSD/Linux. All except OpenBSD 5.4 - I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp snapshot kernel. - I have tried disabling apm and acpi* during boot config I am completely lost as to why this may be happening. You can see the NetBSD boot 6.1.2 on the same machine here: http://pastebin.com/FJeiRp9t You can see OpenBSD snapshot boot (please ignore disable acpi vs acpiprt* - I tried both) here: http://pastebin.com/v9XWv4XY I am using BlueVM (www.BlueVM.comhttp://www.BlueVM.com) as my KVM provider. Can anyone guide me on what I should do or try next? Is it a QEMU issue with the Cloud Services Provider? Thanks, -Bruno
Re: GM45 gpu hung error
On Wed, Nov 13, 2013 at 08:28:14PM +0100, Stefan Sperling wrote: On Wed, Nov 13, 2013 at 09:07:48PM +0200, Ville Valkonen wrote: ahem.. you are not revealing all the needed information Tried to compile, but got an error. Please specify all the commands you used in compiling, thanks. Wild guess, you forgot to make depend? No he didn't. 'make depend' is the failing build target. *** Error 1 in lib (bsd.subdir.mk:48 'depend') (from http://marc.info/?l=openbsd-bugsm=137447893908485w=2) The info is spread across several posts so it takes some time to hunt it down. Janis later provided the build commands he used: http://marc.info/?l=openbsd-bugsm=137448659410735w=2 I can reproduce the problem on a 5.3 sparc64 system. Janis, if you'd like, contact me off-list, and I'll try to help you with the bisection process. The problem is caused by CVS. A date-based checkout gets wrong file versions in kerberosV. See the diff between a tag-based and a date-based checkout below. This is probably due to of bugs^Wfeatures in CVS's vendor branch handling. Janis, this will fix it: cd /usr/src/kerberosV make clean cvs -R up -rOPENBSD_5_3 -dP make obj make depend --- kerberosV-5.3-base/src/lib/hdb/libasn1.hWed Feb 6 09:55:12 2002 +++ kerberosV-2013-06-05/src/lib/hdb/libasn1.h Fri May 25 09:50:17 2001 @@ -1,5 +1,5 @@ /* - * Copyright (c) 1997 - 2001 Kungliga Tekniska HF6gskolan + * Copyright (c) 1997 Kungliga Tekniska HF6gskolan * (Royal Institute of Technology, Stockholm, Sweden). * All rights reserved. * @@ -31,7 +31,7 @@ * SUCH DAMAGE. */ -/* $KTH: libasn1.h,v 1.7 2001/06/23 23:18:50 assar Exp $ */ +/* $KTH: libasn1.h,v 1.4 1999/12/02 17:05:05 joda Exp $ */ #ifndef __LIBASN1_H__ #define __LIBASN1_H__ @@ -41,9 +41,8 @@ #endif #include stdlib.h -#include string.h #include errno.h -#include krb5_asn1.h +#include asn1.h #include der.h #include hdb_asn1.h #include asn1_err.h
Re: sli(4) and emulex LPe11000 dual FC card
* Chris Cappuccio ch...@nmedia.net [13 11:41]: Paolo Aglialoro [paol...@gmail.com] wrote: Hello, just tried today on a sparc64 T1000 running 5.4 release the card, but, unfortunately, sli(4) cannot configure it as dmesg says: pci0 at vpci0 Emulex LPe11000 rev 0x02 at pci0 dev 0 function 0 not configured Emulex LPe11000 rev 0x02 at pci0 dev 0 function 1 not configured The card is correctly seen by prom so this is not likely and architecturally-dependent problem: You need to compile a kernel with the sli driver. GENERIC and GENERIC.MP on sparc64 don't include it by default. That driver is incomplete. Even if you compile it in, you're not going anywhere. jim@
Re: QEMU CPU cores not showing up
On Wed, Nov 13, 2013 at 07:36:58PM +, Bruno Delbono wrote: Hello, I have a QEMU instance that works perfectly fine at detecting cpu cores on NetBSD/FreeBSD/Linux. All except OpenBSD 5.4 - I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp snapshot kernel. Use the GENERIC.MP kernel. - I have tried disabling apm and acpi* during boot config I am completely lost as to why this may be happening. You can see the NetBSD boot 6.1.2 on the same machine here: http://pastebin.com/FJeiRp9t You can see OpenBSD snapshot boot (please ignore disable acpi vs acpiprt* - I tried both) here: http://pastebin.com/v9XWv4XY I am using BlueVM (www.BlueVM.comhttp://www.BlueVM.com) as my KVM provider. Can anyone guide me on what I should do or try next? Is it a QEMU issue with the Cloud Services Provider? Thanks, -Bruno
Re: QEMU CPU cores not showing up
Hi Otto, http://pastebin.com/zfkEUxX8 This is generic.mp with flags of apm and acpi disable http://pastebin.com/PEjCr2vY Generic.MP boot. I am not sure what is wrong and why this works with all the other OS's... -- Bruno Delbono | Cognitive Researcher - Human Behavioural Project | Real Sociedad Española De Antropología | ☎: +1 855 253 5436 ☎: +1 424 354 4700 From: Otto Moerbeek o...@drijf.net Sent: Wednesday, November 13, 2013 3:11 PM To: Bruno Delbono Cc: misc@openbsd.org Subject: Re: QEMU CPU cores not showing up On Wed, Nov 13, 2013 at 07:36:58PM +, Bruno Delbono wrote: Hello, I have a QEMU instance that works perfectly fine at detecting cpu cores on NetBSD/FreeBSD/Linux. All except OpenBSD 5.4 - I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp snapshot kernel. Use the GENERIC.MP kernel. - I have tried disabling apm and acpi* during boot config I am completely lost as to why this may be happening. You can see the NetBSD boot 6.1.2 on the same machine here: http://pastebin.com/FJeiRp9t You can see OpenBSD snapshot boot (please ignore disable acpi vs acpiprt* - I tried both) here: http://pastebin.com/v9XWv4XY I am using BlueVM (www.BlueVM.comhttp://www.BlueVM.com) as my KVM provider. Can anyone guide me on what I should do or try next? Is it a QEMU issue with the Cloud Services Provider? Thanks, -Bruno
Re: sli(4) and emulex LPe11000 dual FC card
Hi Jim, just today I had compiled the kernel (after fiddling with GENERIC and sli_pci.c) with this result: pci0 at vpci0 sli0 at pci0 dev 0 function 0 Emulex LPe11000 rev 0x02: ivec 0x794 sli1 at pci0 dev 0 function 1 Emulex LPe11000 rev 0x02: ivec 0x795 also I have: # pcidump Domain /dev/pci0: 2:0:0: Emulex LPe11000 2:0:1: Emulex LPe11000 Domain /dev/pci1: 2:0:0: ServerWorks PCIE-PCIX 3:4:0: Broadcom BCM5714 3:4:1: Broadcom BCM5714 3:8:0: ServerWorks HT-1000 PCIX 4:1:0: Broadcom BCM5704C 4:1:1: Broadcom BCM5704C 4:2:0: Symbios Logic SAS1064 but haven't tried yet to connect the box to a FC storage, as a colleague should yet give me the correct cable. Now, reading your mail, turned me completely off :((( As far as I get it... I am alone in the desert... or is any light somewhere? On Wed, Nov 13, 2013 at 9:09 PM, Jim Razmus j...@bonetruck.org wrote: * Chris Cappuccio ch...@nmedia.net [13 11:41]: Paolo Aglialoro [paol...@gmail.com] wrote: Hello, just tried today on a sparc64 T1000 running 5.4 release the card, but, unfortunately, sli(4) cannot configure it as dmesg says: pci0 at vpci0 Emulex LPe11000 rev 0x02 at pci0 dev 0 function 0 not configured Emulex LPe11000 rev 0x02 at pci0 dev 0 function 1 not configured The card is correctly seen by prom so this is not likely and architecturally-dependent problem: You need to compile a kernel with the sli driver. GENERIC and GENERIC.MP on sparc64 don't include it by default. That driver is incomplete. Even if you compile it in, you're not going anywhere. jim@
Re: QEMU CPU cores not showing up
On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote: Hi Otto, http://pastebin.com/zfkEUxX8 This is generic.mp with flags of apm and acpi disable http://pastebin.com/PEjCr2vY Generic.MP boot. I am not sure what is wrong and why this works with all the other OS's... No clue then. Maybe some kernel hacker can guess. -Otto -- Bruno Delbono | Cognitive Researcher - Human Behavioural Project | Real Sociedad Espa??ola De Antropolog??a | ???: +1 855 253 5436 ???: +1 424 354 4700 From: Otto Moerbeek o...@drijf.net Sent: Wednesday, November 13, 2013 3:11 PM To: Bruno Delbono Cc: misc@openbsd.org Subject: Re: QEMU CPU cores not showing up On Wed, Nov 13, 2013 at 07:36:58PM +, Bruno Delbono wrote: Hello, I have a QEMU instance that works perfectly fine at detecting cpu cores on NetBSD/FreeBSD/Linux. All except OpenBSD 5.4 - I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp snapshot kernel. Use the GENERIC.MP kernel. - I have tried disabling apm and acpi* during boot config I am completely lost as to why this may be happening. You can see the NetBSD boot 6.1.2 on the same machine here: http://pastebin.com/FJeiRp9t You can see OpenBSD snapshot boot (please ignore disable acpi vs acpiprt* - I tried both) here: http://pastebin.com/v9XWv4XY I am using BlueVM (www.BlueVM.comhttp://www.BlueVM.com) as my KVM provider. Can anyone guide me on what I should do or try next? Is it a QEMU issue with the Cloud Services Provider? Thanks, -Bruno
Re: sli(4) and emulex LPe11000 dual FC card
* Paolo Aglialoro paol...@gmail.com [131113 14:37]: Hi Jim, just today I had compiled the kernel (after fiddling with GENERIC and sli_pci.c) with this result: pci0 at vpci0 sli0 at pci0 dev 0 function 0 Emulex LPe11000 rev 0x02: ivec 0x794 sli1 at pci0 dev 0 function 1 Emulex LPe11000 rev 0x02: ivec 0x795 also I have: # pcidump Domain /dev/pci0: 2:0:0: Emulex LPe11000 2:0:1: Emulex LPe11000 Domain /dev/pci1: 2:0:0: ServerWorks PCIE-PCIX 3:4:0: Broadcom BCM5714 3:4:1: Broadcom BCM5714 3:8:0: ServerWorks HT-1000 PCIX 4:1:0: Broadcom BCM5704C 4:1:1: Broadcom BCM5704C 4:2:0: Symbios Logic SAS1064 but haven't tried yet to connect the box to a FC storage, as a colleague should yet give me the correct cable. Now, reading your mail, turned me completely off :((( As far as I get it... I am alone in the desert... or is any light somewhere? Sorry, I don't have any water for you. I started the sli driver many years back with some guidance from dlg@. Checking cvs, I see that was 6 years ago now. Clearly, I never got back to it. To see just how incomplete the driver is, take a look here: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/ic/sli.c?rev=1.2 Best regards, jim@
Re: QEMU CPU cores not showing up
On Wed, Nov 13, 2013 at 09:44:11PM +0100, Otto Moerbeek wrote: On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote: Hi Otto, http://pastebin.com/zfkEUxX8 This is generic.mp with flags of apm and acpi disable Why would you start trying to disable random devices in the kernel and expect things to get any better? For the past several years, acpi is needed on most machines to do anything useful with those machines. That includes VMs. http://pastebin.com/PEjCr2vY Generic.MP boot. I am not sure what is wrong and why this works with all the other OS's... From your output, there are no APs being presented to the VM. Talk to your cloud provider. -ml No clue then. Maybe some kernel hacker can guess. -Otto -- Bruno Delbono | Cognitive Researcher - Human Behavioural Project | Real Sociedad Espa??ola De Antropolog??a | ???: +1 855 253 5436 ???: +1 424 354 4700 From: Otto Moerbeek o...@drijf.net Sent: Wednesday, November 13, 2013 3:11 PM To: Bruno Delbono Cc: misc@openbsd.org Subject: Re: QEMU CPU cores not showing up On Wed, Nov 13, 2013 at 07:36:58PM +, Bruno Delbono wrote: Hello, I have a QEMU instance that works perfectly fine at detecting cpu cores on NetBSD/FreeBSD/Linux. All except OpenBSD 5.4 - I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp snapshot kernel. Use the GENERIC.MP kernel. - I have tried disabling apm and acpi* during boot config I am completely lost as to why this may be happening. You can see the NetBSD boot 6.1.2 on the same machine here: http://pastebin.com/FJeiRp9t You can see OpenBSD snapshot boot (please ignore disable acpi vs acpiprt* - I tried both) here: http://pastebin.com/v9XWv4XY I am using BlueVM (www.BlueVM.comhttp://www.BlueVM.com) as my KVM provider. Can anyone guide me on what I should do or try next? Is it a QEMU issue with the Cloud Services Provider? Thanks, -Bruno
Re: QEMU CPU cores not showing up
On Wed, Nov 13, 2013 at 09:44:11PM +0100, Otto Moerbeek wrote: On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote: Hi Otto, http://pastebin.com/zfkEUxX8 This is generic.mp with flags of apm and acpi disable Why would you start trying to disable random devices in the kernel and expect things to get any better? For the past several years, acpi is needed on most machines to do anything useful with those machines. That includes VMs. Completely right. As a general policy, if anyone sends a message which indicates that they have disabled ACPI, I recommend that everyone ignore them. ACPI is REQUIRED. Any advice about disabling it is COMPLETELY AND UTTERLY FALSE AND MISLEADING. You will NOT get anywhere by disabling it. You might as well turn off cpu0 while at it.
Re: QEMU CPU cores not showing up
On 11/13/13 22:13, Mike Larkin wrote: On Wed, Nov 13, 2013 at 09:44:11PM +0100, Otto Moerbeek wrote: On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote: Hi Otto, http://pastebin.com/zfkEUxX8 This is generic.mp with flags of apm and acpi disable Why would you start trying to disable random devices in the kernel and expect things to get any better? For the past several years, acpi is needed on most machines to do anything useful with those machines. That includes VMs. He took the advice from me on IRC. I had googled and found a similar mail from someone who could not see 2 cpu's but only 1, people told that person to disable apm, but granted the mails were a little dated. So I was giving the bad advice. I'll keep the acpi thing in mind for next time. Cheers, -peter http://pastebin.com/PEjCr2vY Generic.MP boot. I am not sure what is wrong and why this works with all the other OS's... From your output, there are no APs being presented to the VM. Talk to your cloud provider. -ml No clue then. Maybe some kernel hacker can guess. -Otto -- Bruno Delbono | Cognitive Researcher - Human Behavioural Project | Real Sociedad Espa??ola De Antropolog??a | ???: +1 855 253 5436 ???: +1 424 354 4700 From: Otto Moerbeek o...@drijf.net Sent: Wednesday, November 13, 2013 3:11 PM To: Bruno Delbono Cc: misc@openbsd.org Subject: Re: QEMU CPU cores not showing up On Wed, Nov 13, 2013 at 07:36:58PM +, Bruno Delbono wrote: Hello, I have a QEMU instance that works perfectly fine at detecting cpu cores on NetBSD/FreeBSD/Linux. All except OpenBSD 5.4 - I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp snapshot kernel. Use the GENERIC.MP kernel. - I have tried disabling apm and acpi* during boot config I am completely lost as to why this may be happening. You can see the NetBSD boot 6.1.2 on the same machine here: http://pastebin.com/FJeiRp9t You can see OpenBSD snapshot boot (please ignore disable acpi vs acpiprt* - I tried both) here: http://pastebin.com/v9XWv4XY I am using BlueVM (www.BlueVM.comhttp://www.BlueVM.com) as my KVM provider. Can anyone guide me on what I should do or try next? Is it a QEMU issue with the Cloud Services Provider? Thanks, -Bruno
Re: Mount CD/DVD and playback DVD as normal user
Am Mon, 11 Nov 2013 22:08:20 + schrieb Laurence Rochfort laurence.rochf...@gmail.com: Hello, I'm trying to configure my laptop so that a normal user may mount a CD/DVD or playback a DVD in Xine. So far I've just put an entry in /etc/fbtab. /cdrom permissions look OK, but the devices themselves less so. What are the consequences of putting myself in the operator group? Where can I find a description of those groups? Advice greatly appreciated. Cheers, Laurence. drwxr-xr-x 2 root wheel 512 Nov 8 14:29 cdrom brw-r- 1 root operator6, 0 Nov 8 14:13 /dev/cd0a brw-r- 1 root operator6, 2 Nov 8 14:13 /dev/cd0c brw-r- 1 root operator6, 16 Nov 8 14:13 /dev/cd1a brw-r- 1 root operator6, 18 Nov 8 14:13 /dev/cd1c crw-r- 1 root operator 15, 0 Nov 8 14:13 /dev/rcd0a crw-r- 1 root operator 15, 2 Nov 8 14:13 /dev/rcd0c crw-r- 1 root operator 15, 16 Nov 8 14:13 /dev/rcd1a crw-r- 1 root operator 15, 18 Nov 8 14:13 /dev/rcd1c # $OpenBSD: fbtab.head,v 1.2 1999/05/05 06:56:34 deraadt Exp $ # login(1) reads this file to determine which devices should be chown'd to # the new user. Format is: # login-tty permdevice:[device]:... /dev/ttyC0 0600 /dev/console:/dev/wskbd:/dev/wskbd0:/dev/wsmouse:/dev/wsmouse0:/dev/ttyCcfg /dev/X0 0600/dev/wsmouse:/dev/wsmouse0 # samples #/dev/ttyC0 0600/dev/fd0 /dev/ttyC4 0755/dev/cd0a:/dev/rcd0c Hi Laurence, as this is your own laptop - is your unprivileged user added to sudoers? This is how I manage to handle mounting CDs: ~~~ $ cat /etc/fstab grep cd /dev/cd0a /cdrom cd9660 ro,noauto 0 0 # read only /dev/cd0c /dvd cd9660 rw,noauto 0 0 # for burning CDs/DVDs $ sudo cat /etc/sudoers | grep NOPASSWD %wheel ALL=(ALL) NOPASSWD: SETENV: ALL ~~~ The inconvenience is that I always have to mount it with sudo prepended. You might as well restrict the allowed actions to just a few commands, e.g. 'mount'. See man sudoers As I do not share the laptop with others I can live with any theoretical issues that might go along with this setting. If s.o. gets physical access to the laptop I am in trouble anyway... Cheers, STEFAN Mit freundlichen Grüßen, STEFAN WOLLNY Regulatory Reporting Consultancy Tel.: +49 (0) 177 655 7875 Fax.: +49 (0) 3212 655 7875 Mail: ste...@wollny.de GnuPG-Key ID: 0x9C26F1D0
Re: QEMU CPU cores not showing up
On Wed, Nov 13, 2013 at 10:29:34PM +0100, Peter J. Philipp wrote: He took the advice from me on IRC. I had googled and found a similar mail from someone who could not see 2 cpu's but only 1, people told that person to disable apm, but granted the mails were a little dated. So I was giving the bad advice. I'll keep the acpi thing in mind for next time. Cheers, -peter The issue is how you define cpus as arguments for KVM/qemu. I have seen same issue with RHEVM (KVM/libvirt with fancy UI). The reporter should stop using 3rd party web sites for output, he loses our time, and put as much as info inside the mail. Show qemu/kvm args! Ask provider what does he use, which qemu/KVM, which distro... Try to define 2 sockets, each one core, I bet it will work. jirib
Re: QEMU CPU cores not showing up
Mike, I've asked the provider to look into it. As for why completely random disabling apm and acpi...rant by you and Theo...please see that they are all output that have been tried including booting generic.mp. Its not that it was randomly disabled, it was tested to see if there is a difference. I gave dmesg from all variations I tried before asking misc@ including GENERIC.MP and snapshot MP. I don't get why you and Theo have to go on a rant when the Generic.MP dmesg output is a line below... Sigh. Anyway, I am asking my provider about this. Is there anything specific that OpenBSD may need that none of the other OS's, even Windows Vista that works with, needs? Like telling me ask about AP to them is not very helpful. I need to know what specifically is missing between the same QEMU instance between OpenBSD and any other OS that works fine... Bruno Delbono | Cognitive Researcher - Human Behavioural Project | Real Sociedad Española De Antropología | ☎: +1 855 253 5436 ☎: +1 424 354 4700 From: Mike Larkin mlar...@azathoth.net Sent: Wednesday, November 13, 2013 4:13 PM To: Bruno Delbono; misc@openbsd.org Subject: Re: QEMU CPU cores not showing up On Wed, Nov 13, 2013 at 09:44:11PM +0100, Otto Moerbeek wrote: On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote: Hi Otto, http://pastebin.com/zfkEUxX8 This is generic.mp with flags of apm and acpi disable Why would you start trying to disable random devices in the kernel and expect things to get any better? For the past several years, acpi is needed on most machines to do anything useful with those machines. That includes VMs. http://pastebin.com/PEjCr2vY Generic.MP boot. I am not sure what is wrong and why this works with all the other OS's... From your output, there are no APs being presented to the VM. Talk to your cloud provider. -ml No clue then. Maybe some kernel hacker can guess. -Otto -- Bruno Delbono | Cognitive Researcher - Human Behavioural Project | Real Sociedad Espa??ola De Antropolog??a | ???: +1 855 253 5436 ???: +1 424 354 4700 From: Otto Moerbeek o...@drijf.net Sent: Wednesday, November 13, 2013 3:11 PM To: Bruno Delbono Cc: misc@openbsd.org Subject: Re: QEMU CPU cores not showing up On Wed, Nov 13, 2013 at 07:36:58PM +, Bruno Delbono wrote: Hello, I have a QEMU instance that works perfectly fine at detecting cpu cores on NetBSD/FreeBSD/Linux. All except OpenBSD 5.4 - I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp snapshot kernel. Use the GENERIC.MP kernel. - I have tried disabling apm and acpi* during boot config I am completely lost as to why this may be happening. You can see the NetBSD boot 6.1.2 on the same machine here: http://pastebin.com/FJeiRp9t You can see OpenBSD snapshot boot (please ignore disable acpi vs acpiprt* - I tried both) here: http://pastebin.com/v9XWv4XY I am using BlueVM (www.BlueVM.comhttp://www.BlueVM.com) as my KVM provider. Can anyone guide me on what I should do or try next? Is it a QEMU issue with the Cloud Services Provider? Thanks, -Bruno
Re: QEMU CPU cores not showing up
As for why completely random disabling apm and acpi...rant by you and Theo... Bullshit. Perhaps the solution you are looking for is: boot -c disable pci* You never know, it just might work. We are not ranting. We're telling you that you don't know what the hell you are doing, and you are following bad advice.
Re: QEMU CPU cores not showing up
Sigh, Theo. Seriously I am asking for your help to find out the issue as its unique to OpenBSD. Stop ranting away on the demerits of disabling apm (and now pci - right! wtf?!). Then stop justifying your blind following of what you read on the web. It looks too much like incompetence. Like dude, have you never tried variations of anything except default bsd kernel? Why is tinkering (and not even permanent - just dmesg outputs) considered such an anathema? Hey, stick a screw driver into your ear. Does it help anything? No. And that is why it is discouraged. Don't use boot -c thinking it will fix things for you. It won't. That is not what it is for. boot -c is not a magic tool that solves bugs. From time to time I wonder if we should delete it. It looks like it is only used by people who read web pages.
Re: QEMU CPU cores not showing up
Theo, fine. Truce. I just got advice from jirib@ to ask my provider about: Show qemu/kvm args! Ask provider what does he use, which qemu/KVM, which distro... Try to define 2 sockets, each one core, I bet it will work. . I will report back as soon as they do this. And include full dmesg output in my mail rather than outside providers. My apologies about that.. -- Bruno Delbono | Cognitive Researcher - Human Behavioural Project | Real Sociedad Española De Antropología | ☎: +1 855 253 5436 ☎: +1 424 354 4700 From: Theo de Raadt dera...@cvs.openbsd.org Sent: Wednesday, November 13, 2013 5:29 PM To: Bruno Delbono Cc: misc@openbsd.org; mlar...@azathoth.net Subject: Re: QEMU CPU cores not showing up Sigh, Theo. Seriously I am asking for your help to find out the issue as its unique to OpenBSD. Stop ranting away on the demerits of disabling apm (and now pci - right! wtf?!). Then stop justifying your blind following of what you read on the web. It looks too much like incompetence. Like dude, have you never tried variations of anything except default bsd kernel? Why is tinkering (and not even permanent - just dmesg outputs) considered such an anathema? Hey, stick a screw driver into your ear. Does it help anything? No. And that is why it is discouraged. Don't use boot -c thinking it will fix things for you. It won't. That is not what it is for. boot -c is not a magic tool that solves bugs. From time to time I wonder if we should delete it. It looks like it is only used by people who read web pages.
Re: QEMU CPU cores not showing up
Sigh, Theo. Seriously I am asking for your help to find out the issue as its unique to OpenBSD. Stop ranting away on the demerits of disabling apm (and now pci - right! wtf?!). Like dude, have you never tried variations of anything except default bsd kernel? Why is tinkering (and not even permanent - just dmesg outputs) considered such an anathema? The world didn't collapse by disabling apm and neither did it work. Did I mention I tried the GENERIC.MP too? I am sure I did...oh right, a line below... Look, I am looking for advice from devs like you on why this is happening? Please chill, I come in peace for christ sake! Telling me to ask them about AP (the only advice so far) is not a good question. -- Bruno Delbono | Cognitive Researcher - Human Behavioural Project | Real Sociedad Española De Antropología | ☎: +1 855 253 5436 ☎: +1 424 354 4700 From: Theo de Raadt dera...@cvs.openbsd.org Sent: Wednesday, November 13, 2013 5:13 PM To: Bruno Delbono Cc: misc@openbsd.org; mlar...@azathoth.net Subject: Re: QEMU CPU cores not showing up As for why completely random disabling apm and acpi...rant by you and Theo... Bullshit. Perhaps the solution you are looking for is: boot -c disable pci* You never know, it just might work. We are not ranting. We're telling you that you don't know what the hell you are doing, and you are following bad advice.
Re: QEMU CPU cores not showing up
I'm the tech Bruno has been working with regarding this. QEMU version is 1.5 and the relevant section of the KVM Config file is vcpu4/vcpucputopology sockets='1' cores='4' threads='1'//cpu. We've tried it with 2 sockets, with 4 sockets, with 2 threads, 4 threads, and so on. ACPI and APIC are enabled for the KVM Container. Jeff Fuhrman Level 2 Technician - BlueVM -Original Message- From: Bruno Delbono [mailto:b...@t.gt] Sent: Wednesday, November 13, 2013 2:25 PM To: Theo de Raadt; Theo de Raadt Cc: misc@openbsd.org; mlar...@azathoth.net; misc@openbsd.org; mlar...@azathoth.net Subject: Re: QEMU CPU cores not showing up Sigh, Theo. Seriously I am asking for your help to find out the issue as its unique to OpenBSD. Stop ranting away on the demerits of disabling apm (and now pci - right! wtf?!). Like dude, have you never tried variations of anything except default bsd kernel? Why is tinkering (and not even permanent - just dmesg outputs) considered such an anathema? The world didn't collapse by disabling apm and neither did it work. Did I mention I tried the GENERIC.MP too? I am sure I did...oh right, a line below... Look, I am looking for advice from devs like you on why this is happening? Please chill, I come in peace for christ sake! Telling me to ask them about AP (the only advice so far) is not a good question. -- Bruno Delbono | Cognitive Researcher - Human Behavioural Project Real Sociedad | Española De Antropología | ☎: +1 855 253 5436 ☎: +1 424 354 4700 From: Theo de Raadt dera...@cvs.openbsd.org Sent: Wednesday, November 13, 2013 5:13 PM To: Bruno Delbono Cc: misc@openbsd.org; mlar...@azathoth.net Subject: Re: QEMU CPU cores not showing up As for why completely random disabling apm and acpi...rant by you and Theo... Bullshit. Perhaps the solution you are looking for is: boot -c disable pci* You never know, it just might work. We are not ranting. We're telling you that you don't know what the hell you are doing, and you are following bad advice.
Re: QEMU CPU cores not showing up
2013/11/13 Bruno Delbono b...@t.gt Stop ranting away on the demerits of disabling apm (and now pci - right! wtf?!). He's not. He's rambling about you twisting knobs without having any kind of clue as to why or how it would have helped, probably based on an outdated guide which now also don't know why or how it would help. -- May the most significant bit of your life be positive.
