Re: Welcome-Mail

2015-11-16 Thread Danny Nguyen 
I hope these are not dumb questions.

Would sftp (secure ftp) be a better alternative than ftp? What was the
logic to remove that option on the network install versus http? is there
even a benefit for the mirrors to be on https (secure http) vs http and
would that allow for a verified download like the openbsd compact disks? I
always got really concerned when the install prompted me that "Directory
does not contain SHA256.sig. Continue without verification?" before
actually using official openbsd compact dics. My intent is to assess the
strengths and weaknesses of the protocols being discussed and comparing
them with respect to security.

On Mon, Nov 16, 2015 at 6:09 AM, Raul Miller  wrote:

> All protocols are, to some degree or another. Especially when you look
> at all the irrelevant complexity of a full implementation.
>
> Sometimes there's no good answers.
>
> --
> Raul
>
> On Mon, Nov 16, 2015 at 8:25 AM, Eric Furman 
> wrote:
> > Yea, but ftp is a shitty protocol that should have died
> > a merciful death a long time ago so
> >
> > On Mon, Nov 16, 2015, at 06:07 AM, Marc Peters wrote:
> >> Am 11/16/15 um 12:00 schrieb Stefan Wollny:
> >> > Hi there,
> >> >
> >> > I may be wrong but I thought usage of ftp to get information and to
> >> > download packages is discouraged. I just noticed (after having done a
> >> > fresh install of amd64-current) reading the welcome mail "Welcome to
> >> > OpenBSD 5.8!" that the ftp-protocol is still given.
> >> >
> >> > Instead
> >> > ftp://ftp.openbsd.org/pub/OpenBSD/5.8/packages
> >> > shouldn't this rather be
> >> > http://ftp.openbsd.org/pub/OpenBSD/5.8/packages
> >>
> >> ftp is still a valid option for packages. The installation via ftp is
> >> not supported anymore.
> >>
> >>
> >> Marc

Re: Welcome-Mail

2015-11-16 Thread Giancarlo Razzolini 
Em 16-11-2015 13:59, Danny Nguyen escreveu:
> I hope these are not dumb questions.
>
> Would sftp (secure ftp) be a better alternative than ftp?

Which "secure ftp" you're referring here? SSH's sftp or ftps? Because if
it's the latter, then I'd say it wouldn't be a better alternative. ftp
is ftp. Putting a TLS layer on top of it won't change the most hated
things about the protocol. And, using SSH's sftp has the added
complexity of host keys to the mix. Do you expect that the OpenBSD team
would manage all ssh host keys for all the sftp mirrors and put them on
the install media? And what if one of them changes?

>  What was the
> logic to remove that option on the network install versus http? is there
> even a benefit for the mirrors to be on https (secure http) vs http and
> would that allow for a verified download like the openbsd compact disks?

You are mixing things here. You can verify any download from any OpenBSD
mirror regardless of protocol (ftp, http). Last I checked, there weren't
any https OpenBSD mirrors.

>  I
> always got really concerned when the install prompted me that "Directory
> does not contain SHA256.sig. Continue without verification?" before
> actually using official openbsd compact dics. My intent is to assess the
> strengths and weaknesses of the protocols being discussed and comparing
> them with respect to security.

This has been answered on this list many times. If you're really
concerned, verify your disks manually, or perform a network install. My
suggestion? Buy the CD's (or donate) to help the project. But perform
the installation using a USB stick. As far as weakness and strengths of
the protocols, they are quite irrelevant for the OpenBSD installation.
Everything is signed using signify. The transfer medium can (and is) be
unencrypted. Of course this pretty much means anyone listening knows
you're downloading/installing OpenBSD. If your concern is this, then
you'll need to figure it for yourself how to hide the fact that you're
installing OpenBSD.

Cheers,
Giancarlo Razzolini

Re: EFI: Booting from other (not the first) GPT partition possible? How? It's an Apple :-O

2015-11-16 Thread Marcel Timm 

Hi there,

one thing I would like to try is to boot from created OpenBSD EFI USB 
stick with


boot -a

and enter the OpenBSD's root partition on the HD.

Unfortunately neither the MacBook Pro 8,2 's integrated
nor an external USB keyboard work at the prompt where to enter the
root device's location. :(

Is there another way of telling the kernel which root device to use
(maybe at boot's prompt - although I haven't found anything in man page..)?

If this seems to be a XY question to you, I am happy about other proposals.

Greetings
Marcel

On 11.11.2015 16:01, Marcel Timm wrote:

Hello!

My computer is a MacBook Pro 8,2.

There is a GPT on the HD (big surprise!) with four partitions,
the last one being of type OpenBSD.

I managed to put a recent OpenBSD 5.8 snapshot there
by booting and installing from an USB stick via EFI created like that 
(in OSX):


dd if=~/install58.fs of=/dev/rdisk2 bs=1m

After installing rEFInd 0.9.2 and putting OpenBSD 5.8 snapshot's 
BOOTX64.EFI file
to the MacBook's EFI partition the rEFInd boot manager shows the 
OpenBSD EFI option.


Selecting that OpenBSD entry starts the boot programm showing hd0 hd1 
hd2 and hd3.


Is it possible to boot my "EFI OpenBSD installation" from here?
If so, how to proceed?

I already played with

set device hd0d

etc. - but it did not work.

I will gladly share more details, if of any help.

Thanks in advance!

Marcel

Re: 5.8 freezes on Shuttle DS87, anybody else?

2015-11-16 Thread Harald Dunkel 
On 11/12/2015 10:22 AM, Stuart Henderson wrote:
> On 2015-11-11, Harald Dunkel  wrote:
>> Hi folks,
>>
>> below you can find the trace and ps for the frozen system,
>> as well as the output of dmesg.
>>
>> Hope this helps. Please mail if I can help to track down this
>> problem.
> 
> Trace for other CPUs might help (ddb{0} shows that you are on cpu 0;
> "mach ddbcpu 1" etc switches to another one). Also the line marked '*'
> in ps output (indicating the currently-running process) from other
> CPUs.
> 

See attachment. Hope this helps.

Regards
Harri

[demime 1.01d removed an attachment of type text/x-log which had a name of 
ddb.log]

Help with diff for Samsung 950 Pro NVMe (unable to map registers)

2015-11-16 Thread Josh 
Hi,

Trying to get it recognized and initialized (Model Code MZ-V5P512BW)
Using 16th November snapshot:
...snip... (full dmesg below)
ppb2 at pci0 dev 28 function 4 "Intel 9 Series PCIE" rev 0xe3: msi
pci3 at ppb2 bus 3
vendor "Samsung", unknown product 0xa802 (class mass storage unknown
subclass 0x08, rev 0x01) at pci3 dev 0 function 0 not configured
ehci0 at pci0 dev 29 function 0 "Intel 9 Series USB" rev 0x03: apic 2 int 23
...

Applied the following diff:

*** ahci_pci.c.orig Sat Mar 14 11:38:48 2015
--- ahci_pci.c  Mon Nov 16 20:21:36 2015
***
*** 152,157 
--- 152,159 
NULL,   ahci_samsung_attach },
{ PCI_VENDOR_SAMSUNG2,  PCI_PRODUCT_SAMSUNG2_SM951,
NULL,   ahci_samsung_attach },
+   { PCI_VENDOR_SAMSUNG2,  PCI_PRODUCT_SAMSUNG2_950PRO,
+   NULL,   ahci_samsung_attach },

{ PCI_VENDOR_VIATECH,   PCI_PRODUCT_VIATECH_VT8251_SATA,
  ahci_no_match,ahci_vt8251_attach }

*** pcidevs.h.orig  Sat Nov 14 19:25:53 2015
--- pcidevs.h   Mon Nov 16 11:48:27 2015
***
*** 6387,6392 
--- 6387,6393 
  #define   PCI_PRODUCT_SAMSUNG2_S4LN053X01 0x1600  /* S4LN053X01
*/
  #define   PCI_PRODUCT_SAMSUNG2_XP941  0xa800  /* XP941 */
  #define   PCI_PRODUCT_SAMSUNG2_SM951  0xa801  /* SM951 */
+ #define   PCI_PRODUCT_SAMSUNG2_950PRO 0xa802  /* 950PRO */

  /* Sangoma products */
  #define   PCI_PRODUCT_SANGOMA_A10X0x0300  /* A10x */

*** pcidevs.origSat Nov 14 19:25:53 2015
--- pcidevs Mon Nov 16 11:47:59 2015
***
*** 6382,6387 
--- 6382,6388 
  product SAMSUNG2 S4LN053X01   0x1600  S4LN053X01
  product SAMSUNG2 XP9410xa800  XP941
  product SAMSUNG2 SM9510xa801  SM951
+ product SAMSUNG2 950PRO 0xa802950PRO

  /* Sangoma products */
  product SANGOMA A10X  0x0300  A10x

*** pcidevs_data.h.orig Sat Nov 14 19:25:53 2015
--- pcidevs_data.h  Mon Nov 16 11:49:24 2015
***
*** 22240,22245 
--- 22240,22249 
"SM951",
},
{
+   PCI_VENDOR_SAMSUNG2, PCI_PRODUCT_SAMSUNG2_950PRO,
+   "950PRO",
+   },
+   {
PCI_VENDOR_SANGOMA, PCI_PRODUCT_SANGOMA_A10X,
"A10x",
},

dmesg after compiling / rebooting:
... snip ...
ppb2 at pci0 dev 28 function 4 "Intel 9 Series PCIE" rev 0xe3: msi
pci3 at ppb2 bus 3
ahci0 at pci3 dev 0 function 0 "Samsung 950PRO" rev 0x01: apic 2 int
16, unable to map registers
ehci0 at pci0 dev 29 function 0 "Intel 9 Series USB" rev 0x03: apic 2 int 23
...

The device is "recognized" but unable to map registers. I am certainly
missing something. Any help would be greatly appreciated. (below full
pcidump and dmesg before and after the above patch).

Cheers

pcidump output

Domain /dev/pci0:
 0:0:0: Intel Core 5G Host
0x: Vendor ID: 8086 Product ID: 1604
0x0004: Command: 0006 Status: 2090
0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: 09
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR empty ()
0x0014: BAR empty ()
0x0018: BAR empty ()
0x001c: BAR empty ()
0x0020: BAR empty ()
0x0024: BAR empty ()
0x0028: Cardbus CIS: 
0x002c: Subsystem Vendor ID: 8086 Product ID: 2057
0x0030: Expansion ROM Base Address: 
0x0038: 
0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
0x00e0: Capability 0x09: Vendor Specific
 0:2:0: Intel Iris Graphics 6100
0x: Vendor ID: 8086 Product ID: 162b
0x0004: Command: 0007 Status: 0090
0x0008: Class: 03 Subclass: 00 Interface: 00 Revision: 09
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR mem 64bit addr: 0x7900/0x0100
0x0018: BAR mem prefetchable 64bit addr: 0x8000/0x4000
0x0020: BAR io addr: 0x4000/0x0040
0x0024: BAR empty ()
0x0028: Cardbus CIS: 
0x002c: Subsystem Vendor ID: 8086 Product ID: 2057
0x0030: Expansion ROM Base Address: 
0x0038: 
0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00
0x0090: Capability 0x05: Message Signaled Interrupts (MSI)
0x00d0: Capability 0x01: Power Management
0x00a4: Capability 0x13: PCI Advanced Features
 0:3:0: Intel Core 5G HD Audio
0x: Vendor ID: 8086 Product ID: 160c
0x0004: Command: 0006 Status: 0010
0x0008: Class: 04 Subclass: 03 Interface: 00 Revision: 09
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR mem 64bit addr: 0x7a234000/0x4000
0x0018: BAR empty ()
0x001c: BAR empty ()
0x0020: BAR empty ()
0x0024: BAR empty ()
0x0028: Cardbus CIS:

Re: Welcome-Mail

2015-11-16 Thread Eric Furman 
Yea, but ftp is a shitty protocol that should have died
a merciful death a long time ago so

On Mon, Nov 16, 2015, at 06:07 AM, Marc Peters wrote:
> Am 11/16/15 um 12:00 schrieb Stefan Wollny:
> > Hi there,
> > 
> > I may be wrong but I thought usage of ftp to get information and to
> > download packages is discouraged. I just noticed (after having done a
> > fresh install of amd64-current) reading the welcome mail "Welcome to
> > OpenBSD 5.8!" that the ftp-protocol is still given.
> > 
> > Instead
> > ftp://ftp.openbsd.org/pub/OpenBSD/5.8/packages
> > shouldn't this rather be
> > http://ftp.openbsd.org/pub/OpenBSD/5.8/packages
> 
> ftp is still a valid option for packages. The installation via ftp is
> not supported anymore.
> 
> 
> Marc

Re: Help with diff for Samsung 950 Pro NVMe (unable to map registers)

2015-11-16 Thread Ted Unangst 
Josh wrote:
> Hi,
> 
> Trying to get it recognized and initialized (Model Code MZ-V5P512BW)
> Using 16th November snapshot:
> ...snip... (full dmesg below)
> ppb2 at pci0 dev 28 function 4 "Intel 9 Series PCIE" rev 0xe3: msi
> pci3 at ppb2 bus 3
> vendor "Samsung", unknown product 0xa802 (class mass storage unknown
> subclass 0x08, rev 0x01) at pci3 dev 0 function 0 not configured
> ehci0 at pci0 dev 29 function 0 "Intel 9 Series USB" rev 0x03: apic 2 int 23
> ...
> 
> Applied the following diff:
> 
> *** ahci_pci.c.orig Sat Mar 14 11:38:48 2015
> --- ahci_pci.c  Mon Nov 16 20:21:36 2015
> ***
> *** 152,157 
> --- 152,159 
> NULL,   ahci_samsung_attach },
> { PCI_VENDOR_SAMSUNG2,  PCI_PRODUCT_SAMSUNG2_SM951,
> NULL,   ahci_samsung_attach },
> +   { PCI_VENDOR_SAMSUNG2,  PCI_PRODUCT_SAMSUNG2_950PRO,
> +   NULL,   ahci_samsung_attach },
> 
> { PCI_VENDOR_VIATECH,   PCI_PRODUCT_VIATECH_VT8251_SATA,
>   ahci_no_match,ahci_vt8251_attach }

Does the 950 pro nvme support sata mode? The quirk for the interrupts isn't
anything like native nvme support. I imagine at some point newer drives are
going to stop pretending to have sata interfaces.

Re: state of SSD by OpenBSD

2015-11-16 Thread Kurt Mosiejczuk 
On Sat, Nov 14, 2015 at 04:58:58PM +0100, Riccardo Mottola wrote:

> Nick Holland wrote:
> >>><* peers over at the case of narrow SCSI drives sitting on the spare
> >>>parts shelf and wonder if they'll still spin up; they probably will *>
> >and before tossing them, let developers know -- 4, 6 and 9G narrow scsi
> >drives are few and far between, and needed to keep some old hw running.
> >(I'm guessing everyone has more than enough 2G and smaller disks).

> If they spin up and don't make terrible noises, they are precious indeed :)
> I agree with Nick! These are getting scarce.
> Although if you have place for 2 drives, even a 2G one is useful, but I'm
> running short even on those. 68->50 pin converters do not fit and do not
> with all bus/drives versions, as I sadly discovered myself while trying to
> revitalize some Sparc and HP-PA boxen.

I don't know how well they work, but just this weekend I came across
these "SCSI2SD" boards:

http://shop.codesrc.com/

They are definitely small enough to fit in spaces, although they might
be small enough to be too small.

When I have some spare cash, I may pick one up for my older sparcs.

--Kurt

Re: irq sharing leads to system freeze

2015-11-16 Thread Stefan Sperling 
On Mon, Nov 16, 2015 at 03:18:37PM +0100, Chris Mailer wrote:
> Hello,
> 
> Im using an old Evo N600c laptop with rtw0 pcmcia cardbus lancard.
> Utilizing the lancard (e.g. through netstart) while playing sound as
> well as playing sound while beeing online leads to an immediate system
> freeze.
> It seems that sound and network share IRQ 11.
> I tried to change the IRQ settings using config(8), which, however,
> doesn't seem to have any effect since the IRQs appear to not been set
> at that early state of boot.
> Here is my dmesg output: http://sprunge.us/KRAa
> Thanks,
> 
>  Chris

PLease always inline dmesg at the bottom of your mail.

Re: Welcome-Mail

2015-11-16 Thread Raul Miller 
All protocols are, to some degree or another. Especially when you look
at all the irrelevant complexity of a full implementation.

Sometimes there's no good answers.

-- 
Raul

On Mon, Nov 16, 2015 at 8:25 AM, Eric Furman  wrote:
> Yea, but ftp is a shitty protocol that should have died
> a merciful death a long time ago so
>
> On Mon, Nov 16, 2015, at 06:07 AM, Marc Peters wrote:
>> Am 11/16/15 um 12:00 schrieb Stefan Wollny:
>> > Hi there,
>> >
>> > I may be wrong but I thought usage of ftp to get information and to
>> > download packages is discouraged. I just noticed (after having done a
>> > fresh install of amd64-current) reading the welcome mail "Welcome to
>> > OpenBSD 5.8!" that the ftp-protocol is still given.
>> >
>> > Instead
>> > ftp://ftp.openbsd.org/pub/OpenBSD/5.8/packages
>> > shouldn't this rather be
>> > http://ftp.openbsd.org/pub/OpenBSD/5.8/packages
>>
>> ftp is still a valid option for packages. The installation via ftp is
>> not supported anymore.
>>
>>
>> Marc

irq sharing leads to system freeze

2015-11-16 Thread Chris Mailer 
Hello,

Im using an old Evo N600c laptop with rtw0 pcmcia cardbus lancard.
Utilizing the lancard (e.g. through netstart) while playing sound as
well as playing sound while beeing online leads to an immediate system
freeze.
It seems that sound and network share IRQ 11.
I tried to change the IRQ settings using config(8), which, however,
doesn't seem to have any effect since the IRQs appear to not been set
at that early state of boot.
Here is my dmesg output: http://sprunge.us/KRAa
Thanks,

 Chris

Spotify client for OpenBSD

2015-11-16 Thread Chris Mailer 
Is there any Spotify client for OpenBSD? I tried Spotify support in
clementine, which doesnt seem to work since the spotify blob seems to
rely on Linux libs. I even tried to get it work using compat_linux and
installing the missing fc10 rpms, but without success.
Thanks,
Chris

Re: Spotify client for OpenBSD

2015-11-16 Thread Aaron Bieber 
On Mon, Nov 16, 2015, at 07:20 AM, Chris Mailer wrote:
> Is there any Spotify client for OpenBSD? I tried Spotify support in
> clementine, which doesnt seem to work since the spotify blob seems to
> rely on Linux libs. I even tried to get it work using compat_linux and
> installing the missing fc10 rpms, but without success.
> Thanks,
> Chris
> 

A long time ago this worked: https://github.com/eest/despotify-obsd

Re: irq sharing leads to system freeze

2015-11-16 Thread Theo de Raadt 
What you are trying to do is insane, wrong, and entirely unsupported.

> Ok, sorry. Here it comes:
> 20 alipm* at pci* dev -1 function -1 flags 0x0
> 221 viapm* at pci* dev -1 function -1 flags 0x0
> 222 amdiic* at pci* dev -1 function -1 flags 0x0
> 223 nviic* at pci* dev -1 function -1 flags 0x0
> 224 sdhc* at pci* dev -1 function -1 flags 0x0
> 225 kate* at pci* dev -1 function -1 flags 0x0
> 226 km* at pci* dev -1 function -1 flags 0x0
> 227 gcu* at pci* dev -1 function -1 flags 0x0
> --- more ---228 auglx* at pci* dev -1 function -1 flags 0x0
> 229 itherm* at pci* dev -1 function -1 flags 0x0
> 230 glxpcib* at pci* dev -1 function -1 flags 0x0
> 231 rtsx* at pci* dev -1 function -1 flags 0x0
> 232 virtio* at pci* dev -1 function -1 flags 0x0
> 233 vio* at virtio* flags 0x0
> 234 vioblk* at virtio* flags 0x0
> 235 viomb* at virtio* flags 0x0
> 236 viornd* at virtio* flags 0x0
> 237 vioscsi* at virtio* flags 0x0
> 238 agp* at aliagp*|amdagp*|intelagp*|sisagp*|viaagp*|intagp* flags 0x0
> 239 aliagp* at pchb* bus -1 flags 0x0
> --- more ---240 amdagp* at pchb* bus -1 flags 0x0
> 241 intelagp* at pchb* bus -1 flags 0x0
> 242 intagp* at inteldrm* flags 0x0
> 243 sisagp* at pchb* bus -1 flags 0x0
> 244 viaagp* at pchb* bus -1 flags 0x0
> 245 drm0 at inteldrm*|radeondrm* flags 0x0
> 246 drm* at inteldrm*|radeondrm* flags 0x0
> 247 inteldrm* at pci* dev -1 function -1 flags 0x0
> 248 radeondrm* at pci* dev -1 function -1 flags 0x0
> 249 pchb* at pci* dev -1 function -1 flags 0x0
> 250 amas* at pci* disable dev -1 function -1 flags 0x0
> 251 elansc* at pci* dev -1 function -1 flags 0x0
> --- more ---252 geodesc* at pci* dev -1 function -1 flags 0x0
> 253 glxsb* at pci* dev -1 function -1 flags 0x0
> 254 amdmsr0 at mainbus0 bus -1 flags 0x0
> 255 pcib* at pci* dev -1 function -1 flags 0x0
> 256 ichpcib* at pci* dev -1 function -1 flags 0x0
> 257 piixpcib* at pci* dev -1 function -1 flags 0x0
> 258 gscpcib* at pci* dev -1 function -1 flags 0x0
> 259 amdpcib* at pci* dev -1 function -1 flags 0x0
> 260 tcpcib* at pci* dev -1 function -1 flags 0x0
> 261 hme* at pci* dev -1 function -1 flags 0x0
> 262 isa0 at 
> mainbus0|pcib*|amdpcib*|tcpcib*|ichpcib*|piixpcib*|gscpcib*|glxpcib*
> bus -1 flags 0x0
> 263 isadma0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 drq2
> -1 flags 0x0
> --- more ---264 fdc0 at isa0 port 0x3f0 size 0 iomem -1
> iosiz 0 irq 6 drq 2 drq2 -1 flags 0x0
> 265 fd* at fdc0 drive -1 flags 0x0
> 266 ast0 at isa0 port 0x1a0 size 0 iomem -1 iosiz 0 irq 5 drq -1 drq2
> -1 flags 0x0
> 267 com0 at isa0 port 0x3f8 size 0 iomem -1 iosiz 0 irq 4 drq -1 drq2
> -1 flags 0x0
> 268 com1 at isa0 port 0x2f8 size 0 iomem -1 iosiz 0 irq 3 drq -1 drq2
> -1 flags 0x0
> 269 com2 at isa0 port 0x3e8 size 0 iomem -1 iosiz 0 irq 5 drq -1 drq2
> -1 flags 0x0
> 270 com3 at isa0 disable port 0x2e8 size 0 iomem -1 iosiz 0 irq 9 drq
> -1 drq2 -1 flags 0x0
> 271 com* at ast0 slave -1 flags 0x0
> 272 com* at pcmcia* function -1 irq -1 flags 0x0
> 273 com* at isapnp0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 flags 0x0
> 274 cy0 at isa0 port -1 size 0 iomem 0xd4000 iosiz 0 irq 12 drq -1
> drq2 -1 flags 0x0
> 275 pckbc0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 drq2
> -1 flags 0x0
> --- more ---UKC> change 263
> 263 isadma0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 drq2
> -1 flags 0x0
> change (y/n) ?
> change (y/n) ?
> port [-1] ?
> size [0] ?
> iomem [-1] ?
> iosiz [0] ?
> irq [-1] ? 8
> drq [-1] ?
> drq2 [-1] ?
> flags [0] ?
> 263 isadma0 changed
> 263 isadma0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq 8 drq -1 drq2
> -1 flags 0x0
> UKC> boot\^H \^H\^H \^H\^H \^H\^H \^Hquit
> Continuing...
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: date 06/02/02, BIOS32 rev. 0 @ 0xf, SMBIOS rev.
> 2.3 @ 0xfc087 (37 entries)
> bios0: vendor Compaq version "686DF v2.49" date 06/02/2002
> bios0: Compaq Evo N600c
> acpi0 at bios0: rev 0
> acpi0: sleep states S0 S1 S3 S4 S5
> acpi0: tables DSDT FACP SSDT SSDT
> acpi0: wakeup devices C052(S5) C17E(S5) C185(S5) C0A4(S3) C0AA(S3)
> C19F(S3) C1A0(S3) C1A3(S4) C1A4(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpiprt0 at acpi0: bus -1 (C03F)
> acpiprt1 at acpi0: bus -1 (C17E)
> acpiprt2 at acpi0: bus -1 (C052)
> acpiprt3 at acpi0: bus -1 (C03E)
> acpicpu0 at acpi0: !C3(250@225 io@0x1085), !C2(500@2 io@0x1014),
> C1(1000@1 halt), FVS, 1066, 733 MHz
> acpipwrres0 at acpi0: C14E, resource for C149
> acpipwrres1 at acpi0: C162, resource for C14F
> acpipwrres2 at acpi0: C167, resource for C166
> acpipwrres3 at acpi0: C16B, resource for C168
> acpipwrres4 at acpi0: C174, resource for C172
> acpipwrres5 at acpi0: C1F3, resource for C1F6
> acpipwrres6 at acpi0: C1F4, resource for C1F7
> acpipwrres7 at acpi0: C1F5, resource for C1F8
> acpitz0 at acpi0: critical temperature is 108 degC
> acpiac0 at acpi0: AC unit online
> acpidock0 at acpi0: C14D not docked (0)
>

Re: irq sharing leads to system freeze

2015-11-16 Thread Chris Mailer 
Ok, sorry. Here it comes:
20 alipm* at pci* dev -1 function -1 flags 0x0
221 viapm* at pci* dev -1 function -1 flags 0x0
222 amdiic* at pci* dev -1 function -1 flags 0x0
223 nviic* at pci* dev -1 function -1 flags 0x0
224 sdhc* at pci* dev -1 function -1 flags 0x0
225 kate* at pci* dev -1 function -1 flags 0x0
226 km* at pci* dev -1 function -1 flags 0x0
227 gcu* at pci* dev -1 function -1 flags 0x0
--- more ---228 auglx* at pci* dev -1 function -1 flags 0x0
229 itherm* at pci* dev -1 function -1 flags 0x0
230 glxpcib* at pci* dev -1 function -1 flags 0x0
231 rtsx* at pci* dev -1 function -1 flags 0x0
232 virtio* at pci* dev -1 function -1 flags 0x0
233 vio* at virtio* flags 0x0
234 vioblk* at virtio* flags 0x0
235 viomb* at virtio* flags 0x0
236 viornd* at virtio* flags 0x0
237 vioscsi* at virtio* flags 0x0
238 agp* at aliagp*|amdagp*|intelagp*|sisagp*|viaagp*|intagp* flags 0x0
239 aliagp* at pchb* bus -1 flags 0x0
--- more ---240 amdagp* at pchb* bus -1 flags 0x0
241 intelagp* at pchb* bus -1 flags 0x0
242 intagp* at inteldrm* flags 0x0
243 sisagp* at pchb* bus -1 flags 0x0
244 viaagp* at pchb* bus -1 flags 0x0
245 drm0 at inteldrm*|radeondrm* flags 0x0
246 drm* at inteldrm*|radeondrm* flags 0x0
247 inteldrm* at pci* dev -1 function -1 flags 0x0
248 radeondrm* at pci* dev -1 function -1 flags 0x0
249 pchb* at pci* dev -1 function -1 flags 0x0
250 amas* at pci* disable dev -1 function -1 flags 0x0
251 elansc* at pci* dev -1 function -1 flags 0x0
--- more ---252 geodesc* at pci* dev -1 function -1 flags 0x0
253 glxsb* at pci* dev -1 function -1 flags 0x0
254 amdmsr0 at mainbus0 bus -1 flags 0x0
255 pcib* at pci* dev -1 function -1 flags 0x0
256 ichpcib* at pci* dev -1 function -1 flags 0x0
257 piixpcib* at pci* dev -1 function -1 flags 0x0
258 gscpcib* at pci* dev -1 function -1 flags 0x0
259 amdpcib* at pci* dev -1 function -1 flags 0x0
260 tcpcib* at pci* dev -1 function -1 flags 0x0
261 hme* at pci* dev -1 function -1 flags 0x0
262 isa0 at mainbus0|pcib*|amdpcib*|tcpcib*|ichpcib*|piixpcib*|gscpcib*|glxpcib*
bus -1 flags 0x0
263 isadma0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 drq2
-1 flags 0x0
--- more ---264 fdc0 at isa0 port 0x3f0 size 0 iomem -1
iosiz 0 irq 6 drq 2 drq2 -1 flags 0x0
265 fd* at fdc0 drive -1 flags 0x0
266 ast0 at isa0 port 0x1a0 size 0 iomem -1 iosiz 0 irq 5 drq -1 drq2
-1 flags 0x0
267 com0 at isa0 port 0x3f8 size 0 iomem -1 iosiz 0 irq 4 drq -1 drq2
-1 flags 0x0
268 com1 at isa0 port 0x2f8 size 0 iomem -1 iosiz 0 irq 3 drq -1 drq2
-1 flags 0x0
269 com2 at isa0 port 0x3e8 size 0 iomem -1 iosiz 0 irq 5 drq -1 drq2
-1 flags 0x0
270 com3 at isa0 disable port 0x2e8 size 0 iomem -1 iosiz 0 irq 9 drq
-1 drq2 -1 flags 0x0
271 com* at ast0 slave -1 flags 0x0
272 com* at pcmcia* function -1 irq -1 flags 0x0
273 com* at isapnp0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 flags 0x0
274 cy0 at isa0 port -1 size 0 iomem 0xd4000 iosiz 0 irq 12 drq -1
drq2 -1 flags 0x0
275 pckbc0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 drq2
-1 flags 0x0
--- more ---UKC> change 263
263 isadma0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 drq2
-1 flags 0x0
change (y/n) ?
change (y/n) ?
port [-1] ?
size [0] ?
iomem [-1] ?
iosiz [0] ?
irq [-1] ? 8
drq [-1] ?
drq2 [-1] ?
flags [0] ?
263 isadma0 changed
263 isadma0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq 8 drq -1 drq2
-1 flags 0x0
UKC> boot\^H \^H\^H \^H\^H \^H\^H \^Hquit
Continuing...
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 06/02/02, BIOS32 rev. 0 @ 0xf, SMBIOS rev.
2.3 @ 0xfc087 (37 entries)
bios0: vendor Compaq version "686DF v2.49" date 06/02/2002
bios0: Compaq Evo N600c
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT
acpi0: wakeup devices C052(S5) C17E(S5) C185(S5) C0A4(S3) C0AA(S3)
C19F(S3) C1A0(S3) C1A3(S4) C1A4(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiprt0 at acpi0: bus -1 (C03F)
acpiprt1 at acpi0: bus -1 (C17E)
acpiprt2 at acpi0: bus -1 (C052)
acpiprt3 at acpi0: bus -1 (C03E)
acpicpu0 at acpi0: !C3(250@225 io@0x1085), !C2(500@2 io@0x1014),
C1(1000@1 halt), FVS, 1066, 733 MHz
acpipwrres0 at acpi0: C14E, resource for C149
acpipwrres1 at acpi0: C162, resource for C14F
acpipwrres2 at acpi0: C167, resource for C166
acpipwrres3 at acpi0: C16B, resource for C168
acpipwrres4 at acpi0: C174, resource for C172
acpipwrres5 at acpi0: C1F3, resource for C1F6
acpipwrres6 at acpi0: C1F4, resource for C1F7
acpipwrres7 at acpi0: C1F5, resource for C1F8
acpitz0 at acpi0: critical temperature is 108 degC
acpiac0 at acpi0: AC unit online
acpidock0 at acpi0: C14D not docked (0)
bios0: ROM list: 0xc/0xf000
cpu0 at mainbus0: (uniprocessor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82830M Host" rev 0x04
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0x6000, size

Re: Spotify client for OpenBSD

2015-11-16 Thread Rick Hanson 
> A long time ago this worked: https://github.com/eest/despotify-obsd

Aaron, thanks for hosting the distro
(http://qbit.devio.us/despotify-1.520.tar.gz).  The original (at
http://despotify.se) seems to be long gone.

No sound on speaker with azalia and Intel HD 3400

2015-11-16 Thread Mike Cond 
Hello, that is my first post on openbsd mailing list.
I have installed openbsd 5.8 stable on HP Elitebook 2540p and encountered a
problem with sound system.
It's a Intel HD 3400 version 0.5 . The kernel uses azalia driver.
There is sound on hp2 (headphone) but no sound on speaker.
I tested all setting on mixerctl without positive result.
The media buttons (mut on/off) is always off. Pressing the button works -
Hp (actually dac 0:1 is muted and unmuted) but button led is always red
(muted). During the power down process is the button for short time unmuted
and there is noise through speaker.
I could not find a solution. Here the dmesg, mixerctl and audioctl:
1. dmesg:OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015
    dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 36
real mem = 4059832320 (3871MB)
avail mem = 3932897280 (3750MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xef800 (26 entries)
bios0: vendor Hewlett-Packard version "68CSU Ver. F.09" date 03/09/2011
bios0: Hewlett-Packard HP EliteBook 2540p
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG TCPA SSDT SSDT SSDT SLIC SSDT SSDT SSDT
ASF!
acpi0: wakeup devices LANC(S5) HDEF(S3) EHC1(S3) EHC2(S3) PCIB(S5) RP02(S4)
ECF0(S4) RP03(S4) RP04(S5) WNIC(S5) RP06(S5) NIC_(S5) RP07(S4) RP08(S4)
PEG3(S4) PEG4(S4) [...]
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) i7 CPU L 640 @ 2.13GHz, 2660.51 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
,PERF,ITSC,SENSOR,ARAT
cpu0: 256KB 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 133MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7 CPU L 640 @ 2.13GHz, 2660.01 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
,PERF,ITSC,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7 CPU L 640 @ 2.13GHz, 2660.01 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
,PERF,ITSC,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 5 (application processor)
cpu3: Intel(R) Core(TM) i7 CPU L 640 @ 2.13GHz, 2660.01 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF
,PERF,ITSC,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 2, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus -1 (PEGP)
acpiprt1 at acpi0: bus 68 (PCIB)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus 67 (RP04)
acpiprt5 at acpi0: bus 0 (PCI0)
acpiec0 at acpi0
acpicpu0 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpicpu1 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpicpu2 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpicpu3 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpipwrres0 at acpi0: APPR, resource for HDEF
acpipwrres1 at acpi0: COMP, resource for COM1
acpipwrres2 at acpi0: LPP_, resource for LPT0
acpitz0 at acpi0: critical temperature is 127 degC
acpitz1 at acpi0: critical temperature is 127 degC
acpitz2 at acpi0: critical temperature is 128 degC
acpitz3 at acpi0: critical temperature is 127 degC
acpitz4 at acpi0: critical temperature is 115 degC
acpitz5 at acpi0: critical temperature is 128 degC
acpitz6 at acpi0: critical temperature is 128 degC
acpitz7 at acpi0: critical temperature is 128 degC
acpitz8 at acpi0: critical temperature is 128 degC
acpitz9 at acpi0: critical temperature is 128 degC
acpibat0 at acpi0: BAT0 model "Primary" serial 02042 2015/01/11 type LIon oem

Re: Spotify client for OpenBSD

2015-11-16 Thread Alexander Hall 
There is, or was, a project called "despotify". 

On November 16, 2015 3:20:55 PM GMT+01:00, Chris Mailer 
 wrote:
>Is there any Spotify client for OpenBSD? I tried Spotify support in
>clementine, which doesnt seem to work since the spotify blob seems to
>rely on Linux libs. I even tried to get it work using compat_linux and
>installing the missing fc10 rpms, but without success.
>Thanks,
>Chris

Re: Spotify client for OpenBSD

2015-11-16 Thread Aaron Bieber 
On Mon, Nov 16, 2015, at 12:15 PM, Rick Hanson wrote:
> > A long time ago this worked: https://github.com/eest/despotify-obsd
> 
> Aaron, thanks for hosting the distro
> (http://qbit.devio.us/despotify-1.520.tar.gz).  The original (at
> http://despotify.se) seems to be long gone.
> 

NP - thanks to Devio.us! There is also a node client that worked, but
there wasn't a UI for it back then:

https://github.com/qbit/spot was my attempt at making one.

Re: Welcome-Mail

2015-11-16 Thread Stuart Henderson 
On 2015-11-16, Marc Peters  wrote:
> Am 11/16/15 um 12:00 schrieb Stefan Wollny:
>> Hi there,
>> 
>> I may be wrong but I thought usage of ftp to get information and to
>> download packages is discouraged. I just noticed (after having done a
>> fresh install of amd64-current) reading the welcome mail "Welcome to
>> OpenBSD 5.8!" that the ftp-protocol is still given.
>> 
>> Instead
>> ftp://ftp.openbsd.org/pub/OpenBSD/5.8/packages
>> shouldn't this rather be
>> http://ftp.openbsd.org/pub/OpenBSD/5.8/packages
>
> ftp is still a valid option for packages. The installation via ftp is
> not supported anymore.

It is still valid for some mirrors. But we shouldn't be directing people
there, pkg_add (and in particular pkg_add -u) works a lot better with http.
Especially if the ftp is going through ftp-proxy.

Re: irq sharing leads to system freeze

2015-11-16 Thread Ted Unangst 
Chris Mailer wrote:
> Ok, thanks for the straight forward reply:)
> Is there any other solution to get lan and wifi working together?

Find the bug. :) Interrupt sharing should not be a problem. It indicates a
some other problem exists, and that's the one that should be fixed.

This is not necessarily easy, but half-hearted workarounds aren't any better.

Re: irq sharing leads to system freeze

2015-11-16 Thread Chris Mailer 
Ok, thanks for the straight forward reply:)
Is there any other solution to get lan and wifi working together?
Thanks,
Chris

On 11/16/15, Theo de Raadt  wrote:
> What you are trying to do is insane, wrong, and entirely unsupported.
>
>> Ok, sorry. Here it comes:
>> 20 alipm* at pci* dev -1 function -1 flags 0x0
>> 221 viapm* at pci* dev -1 function -1 flags 0x0
>> 222 amdiic* at pci* dev -1 function -1 flags 0x0
>> 223 nviic* at pci* dev -1 function -1 flags 0x0
>> 224 sdhc* at pci* dev -1 function -1 flags 0x0
>> 225 kate* at pci* dev -1 function -1 flags 0x0
>> 226 km* at pci* dev -1 function -1 flags 0x0
>> 227 gcu* at pci* dev -1 function -1 flags 0x0
>> --- more ---228 auglx* at pci* dev -1 function -1 flags 0x0
>> 229 itherm* at pci* dev -1 function -1 flags 0x0
>> 230 glxpcib* at pci* dev -1 function -1 flags 0x0
>> 231 rtsx* at pci* dev -1 function -1 flags 0x0
>> 232 virtio* at pci* dev -1 function -1 flags 0x0
>> 233 vio* at virtio* flags 0x0
>> 234 vioblk* at virtio* flags 0x0
>> 235 viomb* at virtio* flags 0x0
>> 236 viornd* at virtio* flags 0x0
>> 237 vioscsi* at virtio* flags 0x0
>> 238 agp* at aliagp*|amdagp*|intelagp*|sisagp*|viaagp*|intagp* flags 0x0
>> 239 aliagp* at pchb* bus -1 flags 0x0
>> --- more ---240 amdagp* at pchb* bus -1 flags 0x0
>> 241 intelagp* at pchb* bus -1 flags 0x0
>> 242 intagp* at inteldrm* flags 0x0
>> 243 sisagp* at pchb* bus -1 flags 0x0
>> 244 viaagp* at pchb* bus -1 flags 0x0
>> 245 drm0 at inteldrm*|radeondrm* flags 0x0
>> 246 drm* at inteldrm*|radeondrm* flags 0x0
>> 247 inteldrm* at pci* dev -1 function -1 flags 0x0
>> 248 radeondrm* at pci* dev -1 function -1 flags 0x0
>> 249 pchb* at pci* dev -1 function -1 flags 0x0
>> 250 amas* at pci* disable dev -1 function -1 flags 0x0
>> 251 elansc* at pci* dev -1 function -1 flags 0x0
>> --- more ---252 geodesc* at pci* dev -1 function -1 flags 0x0
>> 253 glxsb* at pci* dev -1 function -1 flags 0x0
>> 254 amdmsr0 at mainbus0 bus -1 flags 0x0
>> 255 pcib* at pci* dev -1 function -1 flags 0x0
>> 256 ichpcib* at pci* dev -1 function -1 flags 0x0
>> 257 piixpcib* at pci* dev -1 function -1 flags 0x0
>> 258 gscpcib* at pci* dev -1 function -1 flags 0x0
>> 259 amdpcib* at pci* dev -1 function -1 flags 0x0
>> 260 tcpcib* at pci* dev -1 function -1 flags 0x0
>> 261 hme* at pci* dev -1 function -1 flags 0x0
>> 262 isa0 at
>> mainbus0|pcib*|amdpcib*|tcpcib*|ichpcib*|piixpcib*|gscpcib*|glxpcib*
>> bus -1 flags 0x0
>> 263 isadma0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 drq2
>> -1 flags 0x0
>> --- more ---264 fdc0 at isa0 port 0x3f0 size 0 iomem -1
>> iosiz 0 irq 6 drq 2 drq2 -1 flags 0x0
>> 265 fd* at fdc0 drive -1 flags 0x0
>> 266 ast0 at isa0 port 0x1a0 size 0 iomem -1 iosiz 0 irq 5 drq -1 drq2
>> -1 flags 0x0
>> 267 com0 at isa0 port 0x3f8 size 0 iomem -1 iosiz 0 irq 4 drq -1 drq2
>> -1 flags 0x0
>> 268 com1 at isa0 port 0x2f8 size 0 iomem -1 iosiz 0 irq 3 drq -1 drq2
>> -1 flags 0x0
>> 269 com2 at isa0 port 0x3e8 size 0 iomem -1 iosiz 0 irq 5 drq -1 drq2
>> -1 flags 0x0
>> 270 com3 at isa0 disable port 0x2e8 size 0 iomem -1 iosiz 0 irq 9 drq
>> -1 drq2 -1 flags 0x0
>> 271 com* at ast0 slave -1 flags 0x0
>> 272 com* at pcmcia* function -1 irq -1 flags 0x0
>> 273 com* at isapnp0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 flags
>> 0x0
>> 274 cy0 at isa0 port -1 size 0 iomem 0xd4000 iosiz 0 irq 12 drq -1
>> drq2 -1 flags 0x0
>> 275 pckbc0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 drq2
>> -1 flags 0x0
>> --- more ---UKC> change 263
>> 263 isadma0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq -1 drq -1 drq2
>> -1 flags 0x0
>> change (y/n) ?
>> change (y/n) ?
>> port [-1] ?
>> size [0] ?
>> iomem [-1] ?
>> iosiz [0] ?
>> irq [-1] ? 8
>> drq [-1] ?
>> drq2 [-1] ?
>> flags [0] ?
>> 263 isadma0 changed
>> 263 isadma0 at isa0 port -1 size 0 iomem -1 iosiz 0 irq 8 drq -1 drq2
>> -1 flags 0x0
>> UKC> boot\^H \^H\^H \^H\^H \^H\^H \^Hquit
>> Continuing...
>> mpath0 at root
>> scsibus0 at mpath0: 256 targets
>> mainbus0 at root
>> bios0 at mainbus0: date 06/02/02, BIOS32 rev. 0 @ 0xf, SMBIOS rev.
>> 2.3 @ 0xfc087 (37 entries)
>> bios0: vendor Compaq version "686DF v2.49" date 06/02/2002
>> bios0: Compaq Evo N600c
>> acpi0 at bios0: rev 0
>> acpi0: sleep states S0 S1 S3 S4 S5
>> acpi0: tables DSDT FACP SSDT SSDT
>> acpi0: wakeup devices C052(S5) C17E(S5) C185(S5) C0A4(S3) C0AA(S3)
>> C19F(S3) C1A0(S3) C1A3(S4) C1A4(S4)
>> acpitimer0 at acpi0: 3579545 Hz, 24 bits
>> acpiprt0 at acpi0: bus -1 (C03F)
>> acpiprt1 at acpi0: bus -1 (C17E)
>> acpiprt2 at acpi0: bus -1 (C052)
>> acpiprt3 at acpi0: bus -1 (C03E)
>> acpicpu0 at acpi0: !C3(250@225 io@0x1085), !C2(500@2 io@0x1014),
>> C1(1000@1 halt), FVS, 1066, 733 MHz
>> acpipwrres0 at acpi0: C14E, resource for C149
>> acpipwrres1 at acpi0: C162, resource for C14F
>> acpipwrres2 at acpi0: C167, resource for C166
>> acpipwrres3 at acpi0: C16B, resource for C168
>> acpipwrres4 at acpi0:

Re: Spotify client for OpenBSD

2015-11-16 Thread Chris Mailer 
Yes found that already but that is only a very basic command line
client with no option for local storage.
Is there anything else?
Thanks,
Chris

On 11/16/15, Alexander Hall  wrote:
> There is, or was, a project called "despotify".
>
> On November 16, 2015 3:20:55 PM GMT+01:00, Chris Mailer
>  wrote:
>>Is there any Spotify client for OpenBSD? I tried Spotify support in
>>clementine, which doesnt seem to work since the spotify blob seems to
>>rely on Linux libs. I even tried to get it work using compat_linux and
>>installing the missing fc10 rpms, but without success.
>>Thanks,
>>Chris

inteldrm(4) display corruption on MacBook

2015-11-16 Thread Ossi Herrala 
Hi misc@,

Same issue what's described by Bryan Vyhmeister in

  https://marc.info/?l=openbsd-misc=144614435718519
  https://marc.info/?l=openbsd-misc=144622297912025

but with MacBookPro9,2 and Intel HD 4000 graphics (MacBook Pro
(13-inch, Mid 2012)). Snapshot and sources from mirror from today.

I went digging what produces the error

  error: [drm:pid0:inteldrm_attach] *ERROR* failed to init modeset

and it looks like in sys/dev/pci/drm/drm_irq.c:1.66

drm_irq_install() calls 

if (drm_dev_to_irq(dev) == 0)
return -EINVAL;

drm_dev_to_irq(dev) returns 0 and my skills end here to dig this
further.

these lines in dmesg are my debugging from kernel (and "stacktrace"):

error: [drm:pid0:drm_dev_to_irq] *ERROR* irq == 0
error: [drm:pid0:drm_irq_install] *ERROR* oherrala: drm_irq_install: 
drm_dev_to_irq
error: [drm:pid0:i915_load_modeset_init] *ERROR* oherrala: 
i915_load_modeset_init: drm_irq_install
error: [drm:pid0:inteldrm_attach] *ERROR* oherrala: i915_drm.c: failed to init 
modeset


I can help test patches, etc. if this helps anything?


dmesg:

OpenBSD 5.8-current (DEBUG.MP) #0: Mon Nov 16 19:15:35 UTC 2015
r...@cn0022.my.domain:/usr/src/sys/arch/amd64/compile/DEBUG.MP
RTC BIOS diagnostic error 
7f
real mem = 8473620480 (8081MB)
avail mem = 8212676608 (7832MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x8ad14000 (63 entries)
bios0: vendor Apple Inc. version "MBP91.88Z.00D3.B0B.1506081214" date 06/08/2015
bios0: Apple Inc. MacBookPro9,2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT DMAR MCFG
acpi0: wakeup devices P0P2(S3) PEG1(S3) EC__(S4) GMUX(S3) HDEF(S3) RP01(S3) 
GIGE(S3) SDXC(S3) RP02(S3) ARPT(S3) RP03(S3) EHC1(S3) EHC2(S3) XHC1(S3) 
ADP1(S4) LID0(S4)
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) i5-3210M CPU @ 2.50GHz, 2494.67 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz, 2494.34 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz, 2494.34 MHz
cpu2: 
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz, 2494.34 MHz
cpu3: 
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xe000, bus 0-154
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (P0P2)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus 1 (RP01)
acpiprt4 at acpi0: bus 2 (RP02)
acpiprt5 at acpi0: bus 3 (RP03)
acpicpu0 at acpi0: C3(200@198 mwait.1@0x30), C2(500@148 mwait.1@0x10), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@198 mwait.1@0x30), C2(500@148 mwait.1@0x10), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@198 mwait.1@0x30), C2(500@148 mwait.1@0x10), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@198 mwait.1@0x30), C2(500@148 mwait.1@0x10), 
C1(1000@1 mwait.1), PSS
acpibat0 at acpi0: BAT0 model "3545797981023400290" type

Re: Help with diff for Samsung 950 Pro NVMe (unable to map registers)

2015-11-16 Thread Josh 
Thanks Ted for the reply and the hint.
After a bit of research, it seems the 950 Pro use a PCIe NVMe
interface as opposed to the SM951 (already in the CVS tree) using PCIe
AHCI interface.
I did not find any mention of backwards compatibility with AHCI so far
for the 950 Pro and might correlate with your assumption.

A bit more research brought me to the nvme [1] driver found in
FreeBSD. Was there any attempts into porting that?
I am not a developer, but would be happy to help in testing patch/source code.

Cheers,

[1] https://www.freebsd.org/cgi/man.cgi?query=nvme=4


On Mon, Nov 16, 2015 at 11:32 PM, Ted Unangst  wrote:
> Josh wrote:
>> Hi,
>>
>> Trying to get it recognized and initialized (Model Code MZ-V5P512BW)
>> Using 16th November snapshot:
>> ...snip... (full dmesg below)
>> ppb2 at pci0 dev 28 function 4 "Intel 9 Series PCIE" rev 0xe3: msi
>> pci3 at ppb2 bus 3
>> vendor "Samsung", unknown product 0xa802 (class mass storage unknown
>> subclass 0x08, rev 0x01) at pci3 dev 0 function 0 not configured
>> ehci0 at pci0 dev 29 function 0 "Intel 9 Series USB" rev 0x03: apic 2 int 23
>> ...
>>
>> Applied the following diff:
>>
>> *** ahci_pci.c.orig Sat Mar 14 11:38:48 2015
>> --- ahci_pci.c  Mon Nov 16 20:21:36 2015
>> ***
>> *** 152,157 
>> --- 152,159 
>> NULL,   ahci_samsung_attach },
>> { PCI_VENDOR_SAMSUNG2,  PCI_PRODUCT_SAMSUNG2_SM951,
>> NULL,   ahci_samsung_attach },
>> +   { PCI_VENDOR_SAMSUNG2,  PCI_PRODUCT_SAMSUNG2_950PRO,
>> +   NULL,   ahci_samsung_attach },
>>
>> { PCI_VENDOR_VIATECH,   PCI_PRODUCT_VIATECH_VT8251_SATA,
>>   ahci_no_match,ahci_vt8251_attach }
>
> Does the 950 pro nvme support sata mode? The quirk for the interrupts isn't
> anything like native nvme support. I imagine at some point newer drives are
> going to stop pretending to have sata interfaces.

Re: No sound on speaker with azalia and Intel HD 3400

2015-11-16 Thread Jonathan Gray 
On Mon, Nov 16, 2015 at 06:02:38PM +, Mike Cond wrote:
> Hello, that is my first post on openbsd mailing list.
> I have installed openbsd 5.8 stable on HP Elitebook 2540p and encountered a
> problem with sound system.
> It's a Intel HD 3400 version 0.5 . The kernel uses azalia driver.
> There is sound on hp2 (headphone) but no sound on speaker.
> I tested all setting on mixerctl without positive result.
> The media buttons (mut on/off) is always off. Pressing the button works -
> Hp (actually dac 0:1 is muted and unmuted) but button led is always red
> (muted).??During the power down process is the button for short time unmuted
> and there is noise through speaker.
> I could not find a solution. Here the dmesg, mixerctl and audioctl:

Can you try the below patch and include the "pcidump -v" output as well?

Index: sys/dev/pci/azalia_codec.c
===
RCS file: /cvs/src/sys/dev/pci/azalia_codec.c,v
retrieving revision 1.170
diff -u -p -r1.170 azalia_codec.c
--- sys/dev/pci/azalia_codec.c  24 Aug 2015 04:50:40 -  1.170
+++ sys/dev/pci/azalia_codec.c  17 Nov 2015 02:18:38 -
@@ -228,6 +228,7 @@ azalia_codec_init_vtbl(codec_t *this)
break;
case 0x111d7603:
this->name = "IDT 92HD75B3/4";
+   this->qrks |= AZ_QRK_GPIO_UNMUTE_0;
break;
case 0x111d7604:
this->name = "IDT 92HD83C1X";

Welcome-Mail

2015-11-16 Thread Stefan Wollny 

Hi there,

I may be wrong but I thought usage of ftp to get information and to 
download packages is discouraged. I just noticed (after having done a 
fresh install of amd64-current) reading the welcome mail "Welcome to 
OpenBSD 5.8!" that the ftp-protocol is still given.


Instead
ftp://ftp.openbsd.org/pub/OpenBSD/5.8/packages
shouldn't this rather be
http://ftp.openbsd.org/pub/OpenBSD/5.8/packages
?

And consequently the following sentence would be adjusted accordingly 
just like the example download of emacs.


If ftp is still a valid option please excuse the noise.

Best,
STEFAN

Re: Welcome-Mail

2015-11-16 Thread Marc Peters 
Am 11/16/15 um 12:00 schrieb Stefan Wollny:
> Hi there,
> 
> I may be wrong but I thought usage of ftp to get information and to
> download packages is discouraged. I just noticed (after having done a
> fresh install of amd64-current) reading the welcome mail "Welcome to
> OpenBSD 5.8!" that the ftp-protocol is still given.
> 
> Instead
> ftp://ftp.openbsd.org/pub/OpenBSD/5.8/packages
> shouldn't this rather be
> http://ftp.openbsd.org/pub/OpenBSD/5.8/packages

ftp is still a valid option for packages. The installation via ftp is
not supported anymore.


Marc

Re: Help with diff for Samsung 950 Pro NVMe (unable to map registers)

2015-11-16 Thread Janne Johansson 
There is some preliminary work in the obsd tree also from dlg@:
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/nvme_pci.c


2015-11-17 3:00 GMT+01:00 Josh :

> Thanks Ted for the reply and the hint.
> After a bit of research, it seems the 950 Pro use a PCIe NVMe
> interface as opposed to the SM951 (already in the CVS tree) using PCIe
> AHCI interface.
> I did not find any mention of backwards compatibility with AHCI so far
> for the 950 Pro and might correlate with your assumption.
>
> A bit more research brought me to the nvme [1] driver found in
> FreeBSD. Was there any attempts into porting that?
> I am not a developer, but would be happy to help in testing patch/source
> code.
>
> Cheers,
>
> [1] https://www.freebsd.org/cgi/man.cgi?query=nvme=4
>
>
> On Mon, Nov 16, 2015 at 11:32 PM, Ted Unangst  wrote:
> > Josh wrote:
> >> Hi,
> >>
> >> Trying to get it recognized and initialized (Model Code MZ-V5P512BW)
> >> Using 16th November snapshot:
> >> ...snip... (full dmesg below)
> >> ppb2 at pci0 dev 28 function 4 "Intel 9 Series PCIE" rev 0xe3: msi
> >> pci3 at ppb2 bus 3
> >> vendor "Samsung", unknown product 0xa802 (class mass storage unknown
> >> subclass 0x08, rev 0x01) at pci3 dev 0 function 0 not configured
> >> ehci0 at pci0 dev 29 function 0 "Intel 9 Series USB" rev 0x03: apic 2
> int 23
> >> ...
> >>
> >> Applied the following diff:
> >>
> >> *** ahci_pci.c.orig Sat Mar 14 11:38:48 2015
> >> --- ahci_pci.c  Mon Nov 16 20:21:36 2015
> >> ***
> >> *** 152,157 
> >> --- 152,159 
> >> NULL,   ahci_samsung_attach },
> >> { PCI_VENDOR_SAMSUNG2,  PCI_PRODUCT_SAMSUNG2_SM951,
> >> NULL,   ahci_samsung_attach },
> >> +   { PCI_VENDOR_SAMSUNG2,  PCI_PRODUCT_SAMSUNG2_950PRO,
> >> +   NULL,   ahci_samsung_attach },
> >>
> >> { PCI_VENDOR_VIATECH,   PCI_PRODUCT_VIATECH_VT8251_SATA,
> >>   ahci_no_match,ahci_vt8251_attach }
> >
> > Does the 950 pro nvme support sata mode? The quirk for the interrupts
> isn't
> > anything like native nvme support. I imagine at some point newer drives
> are
> > going to stop pretending to have sata interfaces.
>
>


-- 
May the most significant bit of your life be positive.