OpenBSD Journal

Developer blog: marco

Contributed by marco on from the who-said-we-don't-need-u320-on-hppa? dept.

I want to point out the outstanding work done by dlg on the mpi(4) driver which in -current replaced mpt(4). During the hackathon dlg & deraadt decided together that mpt(4) sucked enough and wasn't maintainable enough to add SAS and RAID support. So dlg went on a mad hacking spree and rewrote the driver from scratch. Within a few days he had something that worked well enough to play with; in fact it was so good that it was actually used to boot an Ultra Sparc 3 machine. Why is that significant? Well it proves that the driver is 64 bit AND endian safe. I debugged some issues, fixed dlg's attempt at PPR and here comes the kicker... the code is in fact so well written that the driver simply "just worked" on hppa as well. So courtesy of dlg now we have U320 support on hppa. Enjoy.

To-Do:

  • PPR on IM/IS/IME RAID device
  • Firmware Download Boot (for on-board 1030 chips)
  • Some additional printing of dmesg devices for SAS/FC/SATA
  • bio support

Just for fun I installed a FC, SAS and SCSI mpi on my development machine. Here is an excerpt of the dmesg:

mpi0 at pci1 dev 8 function 0 "Symbios Logic 53c1030" rev 0x07: irq 10
mpi1 at pci1 dev 8 function 1 "Symbios Logic 53c1030" rev 0x07: irq 10
mpi2 at pci1 dev 9 function 0 "Symbios Logic FC919X" rev 0x00: irq 10
mpi3 at pci2 dev 8 function 0 "Symbios Logic SAS1068" rev 0x01: irq 10

Full dmesg:

OpenBSD 3.9-current (GENERIC) #3: Sat Jun 17 14:04:21 CDT 2006
    root@dev.peereboom.us:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) XEON(TM) CPU 2.20GHz ("GenuineIntel" 686-class) 2.20 GHz
cpu0: FPU,V86,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
real mem = 4209520640 (4110860K)
avail mem = 3863076864 (3772536K)
using 4256 buffers containing 210579456 bytes (205644K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(1c) BIOS, date 10/09/02, BIOS32 rev. 0 @ 0xfd91e, SMBIOS rev. 2.3 @ 0xf0150 (70 entries)
bios0: Intel SHG2
pcibios0 at bios0: rev 2.1 @ 0xfd880/0x780
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdec0/288 (16 entries)
pcibios0: no compatible PCI ICU found: ICU vendor 0xffff product 0xffff
pcibios0: Warning, unable to fix up PCI interrupt routing
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc0000/0x8000 0xc8000/0x4000 0xcc000/0x4000 0xd0000/0x4800 0xde000/0x2000!
ipmi at mainbus0 not configured
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "ServerWorks CMIC-WS Host (GC-LE)" rev 0x13
pchb1 at pci0 dev 0 function 1 "ServerWorks CMIC-WS Host (GC-LE)" rev 0x00
pchb2 at pci0 dev 0 function 2 "ServerWorks CMIC-LE" rev 0x00
pci1 at pchb2 bus 1
em0 at pci1 dev 4 function 0 "Intel PRO/1000XT (82544GC)" rev 0x02: irq 10, address 00:02:b3:52:3c:f8
mpi0 at pci1 dev 8 function 0 "Symbios Logic 53c1030" rev 0x07: irq 10
scsibus0 at mpi0: 16 targets
sd0 at scsibus0 targ 0 lun 0: <SEAGATE, ST336752LW, EE31> SCSI3 0/direct fixed
sd0: 35003MB, 18496 cyl, 8 head, 484 sec, 512 bytes/sec, 71687369 sec total
sd1 at scsibus0 targ 1 lun 0: <SEAGATE, ST318406LW, 8A03> SCSI3 0/direct fixed
sd1: 17366MB, 26302 cyl, 2 head, 676 sec, 512 bytes/sec, 35566478 sec total
mpi0: target 0 Sync at 80MHz width 16bit offset 63 QAS 0 DT 1 IU 0
mpi0: target 1 Sync at 80MHz width 16bit offset 63 QAS 0 DT 1 IU 0
mpi1 at pci1 dev 8 function 1 "Symbios Logic 53c1030" rev 0x07: irq 10
scsibus1 at mpi1: 16 targets
sd2 at scsibus1 targ 0 lun 0: <FUJITSU, MAP3147NP, 5605< SCSI3 0/direct fixed
sd2: 140014MB, 47926 cyl, 8 head, 747 sec, 512 bytes/sec, 286749480 sec total
mpi1: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1
mpi2 at pci1 dev 9 function 0 "Symbios Logic FC919X" rev 0x00: irq 10
scsibus2 at mpi2: 32 targets
sd3 at scsibus2 targ 0 lun 0: <SEAGATE, ST118202FC, FDF6> SCSI2 0/direct fixed
sd3: 17366MB, 6962 cyl, 24 head, 212 sec, 512 bytes/sec, 35566480 sec total
sd4 at scsibus2 targ 1 lun 0: <SEAGATE, ST318203FC, F304> SCSI2 0/direct fixed
sd4: 17366MB, 9772 cyl, 12 head, 303 sec, 512 bytes/sec, 35566480 sec total
sd5 at scsibus2 targ 2 lun 0: <SEAGATE, ST318203FC, F304> SCSI2 0/direct fixed
sd5: 17366MB, 9772 cyl, 12 head, 303 sec, 512 bytes/sec, 35566480 sec total
sd6 at scsibus2 targ 3 lun 0: <SEAGATE, ST318203FC, F304> SCSI2 0/direct fixed
sd6: 17366MB, 9772 cyl, 12 head, 303 sec, 512 bytes/sec, 35566480 sec total
sd7 at scsibus2 targ 4 lun 0: <SEAGATE, ST318203FC, F304> SCSI2 0/direct fixed
sd7: 17366MB, 9772 cyl, 12 head, 303 sec, 512 bytes/sec, 35566480 sec total
sd8 at scsibus2 targ 5 lun 0: <SEAGATE, ST318203FC, F304> SCSI2 0/direct fixed
sd8: 17366MB, 9772 cyl, 12 head, 303 sec, 512 bytes/sec, 35566480 sec total
sd9 at scsibus2 targ 6 lun 0: <SEAGATE, ST318203FC, F304> SCSI2 0/direct fixed
sd9: 17366MB, 9772 cyl, 12 head, 303 sec, 512 bytes/sec, 35566480 sec total
vga1 at pci0 dev 2 function 0 "ATI Rage XL" rev 0x27
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
piixpm0 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93
iic0 at piixpm0
pciide0 at pci0 dev 15 function 1 "ServerWorks CSB5 IDE" rev 0x93: DMA
ohci0 at pci0 dev 15 function 2 "ServerWorks OSB4/CSB5 USB" rev 0x05: irq 10, version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: ServerWorks OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 4 ports with 4 removable, self powered
pchb3 at pci0 dev 15 function 3 "ServerWorks CSB5 LPC" rev 0x00
pchb4 at pci0 dev 17 function 0 "ServerWorks CIOB-X2 PCIX" rev 0x03
pchb5 at pci0 dev 17 function 2 "ServerWorks CIOB-X2 PCIX" rev 0x03
pci2 at pchb5 bus 2
mpi3 at pci2 dev 8 function 0 "Symbios Logic SAS1068" rev 0x01: irq 10
scsibus3 at mpi3: 126 targets
sd10 at scsibus3 targ 8 lun 0: <FUJITSU, MAV2036RC, 0F12> SCSI3 0/direct fixed
sd10: 17534MB, 43338 cyl, 2 head, 414 sec, 512 bytes/sec, 35909748 sec total
sd11 at scsibus3 targ 9 lun 0: <FUJITSU, MAV2036RC, 0F09> SCSI3 0/direct fixed
sd11: 17534MB, 65178 cyl, 2 head, 275 sec, 512 bytes/sec, 35909748 sec total
sd12 at scsibus3 targ 10 lun 0: <FUJITSU, MAV2073RC, 0F16> SCSI3 0/direct fixed
sd12: 70136MB, 52363 cyl, 4 head, 685 sec, 512 bytes/sec, 143638992 sec total
isa0 at mainbus0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask ef65 netmask ef65 ttymask ffe7
pctr: user-level cycle counter enabled
dkcsum: sd0 matches BIOS drive 0x80
dkcsum: sd1 matches BIOS drive 0x81
dkcsum: sd2 matches BIOS drive 0x82
dkcsum: sd3 matches BIOS drive 0x83
dkcsum: sd4 matches BIOS drive 0x84
dkcsum: sd5 matches BIOS drive 0x85
dkcsum: sd6 matches BIOS drive 0x86
dkcsum: sd7 matches BIOS drive 0x87
root on sd0a
rootdev=0x400 rrootdev=0xd00 rawdev=0xd02

hppa dmesg:

OpenBSD 3.9-current (GENERIC) #0: Tue Jul 9 22:05:45 CDT 1974
    root@humppa360.peereboom.us:/usr/src/sys/arch/hppa/compile/GENERIC
HP 9000/780/C360 (Raven W 360) PA-RISC 2.0a
real mem = 1342177280 (524288 reserved for PROM, 7962624 used by OpenBSD)
avail mem = 1166573568
using 8421 buffers containing 134184960 bytes of memory
mainbus0 (root) [flex fff80000]
pdc0 at mainbus0
power0 at mainbus0 offset 140000
mem0 at mainbus0 offset ffb1000: size 1280MB
cpu0 at mainbus0 offset ffa0000 irq 31: PCXW L1-A 367MHz, FPU PCXW rev 1
cpu0: 512K(32b/l) Icache, 1024K(32b/l) wr-back Dcache, 160 coherent TLB
uturn0 at mainbus0 offset ff8a000: U2 rev 15
"Bus Converter Port" at uturn0 (type 7 sv c mod 50 hv 11) offset 103f000 not configured
dino0 at uturn0 offset 1000000 irq 26: Cujo V2.0
pci0 at dino0
mpi0 at pci0 dev 2 function 0 "Symbios Logic 53c1030" rev 0x01: irq 3
scsibus0 at mpi0: 16 targets
sd0 at scsibus0 targ 0 lun 0: <SEAGATE, ST336752LW, EE31> SCSI3 0/direct fixed
sd0: 35003MB, 18496 cyl, 8 head, 484 sec, 512 bytes/sec, 71687369 sec total
sd1 at scsibus0 targ 1 lun 0: <SEAGATE, ST318406LW, 8A03> SCSI3 0/direct fixed
sd1: 17366MB, 26302 cyl, 2 head, 676 sec, 512 bytes/sec, 35566478 sec total
mpi0: target 0 Sync at 80MHz width 16bit offset 63 QAS 0 DT 1 IU 0
mpi0: target 1 Sync at 80MHz width 16bit offset 63 QAS 0 DT 1 IU 0
mpi1 at pci0 dev 2 function 1 "Symbios Logic 53c1030" rev 0x01: irq 4
scsibus1 at mpi1: 16 targets
uturn1 at mainbus0 offset ff88000: U2 rev 15
"Bus Converter Port" at uturn1 (type 7 sv c mod 50 hv 11) offset 203f000 not configured
lasi0 at uturn1 offset fd00000 irq 28: rev 3.0
gsc0 at lasi0: wordleds
gsckbc0 at gsc0 offset 8100 irq 26
gsckbc1 at gsc0 offset 8000 irq 26
osiop0 at gsc0 offset 6000 irq 9: NCR53C710 rev 2, 40MHz, SCSI ID 7
scsibus2 at osiop0: 8 targets
osiop0: target 2 now using 8 bit 10 MHz 8 REQ/ACK offset xfers
cd0 at scsibus2 targ 2 lun 0: <TOSHIBA, CD-ROM XM-6201TA, 1037> SCSI2 5/cdrom removable
com0 at gsc0 offset 5000 irq 5: ns16550a, 16 byte fifo
com0: console
harmony0 at gsc0 offset 4000 irq 13: rev 1
audio0 at harmony0
lpt0 at gsc0 offset 2000 irq 7
dino1 at uturn1 offset 2000000 irq 25: Dino V3.1
com1 at dino1 irq 11: ns16550a, 16 byte fifo
pci1 at dino1
siop0 at pci1 dev 19 function 0 "Symbios Logic 53c875" rev 0x04: irq 4, using 4K of on-board RAM
scsibus3 at siop0: 16 targets
sd3 at scsibus3 targ 0 lun 0: <SEAGATE, ST318436LW, 0005> SCSI3 0/direct fixed
sd3: 17522MB, 14384 cyl, 6 head, 415 sec, 512 bytes/sec, 35885168 sec total
sd4 at scsibus3 targ 5 lun 0: <IBM, DDRS-34560WS, HP01> SCSI2 0/direct fixed
sd4: 4095MB, 8387 cyl, 5 head, 200 sec, 512 bytes/sec, 8388314 sec total
dc0 at pci1 dev 20 function 0 "DEC 21142/3" rev 0x30: irq 1, address 00:10:83:05:43:6a
lxtphy0 at dc0 phy 1: LXT970 10/100 PHY, rev. 1
biomask 0xb netmask 0xf ttymask 0x3f
boot path: 8/0/19/0.0 class=1 flags=80 hpa=0xf2ffd000 spa=0x0 io=0x16000
root on sd3a swap on sd3b
siop0: target 0 now using tagged 16 bit 20.0 MHz 16 REQ/ACK offset xfers
rootdev=0x430 rrootdev=0xa30 rawdev=0xa32
WARNING: preposterous time in file system -- CHECK AND RESET THE DATE!
siop0: target 5 now using tagged 16 bit 20.0 MHz 15 REQ/ACK offset xfers

(Comments are closed)


Comments
  1. By Anonymous Coward (69.70.207.240) on

    Ultra-Sweet! Thank you!

  2. By Anonymous Coward (198.54.202.18) on

    Wow.

    You guys never stop, do you :-)

    This just goes to show one of the values of good clean code - immediate support for all available platforms.

  3. By Jason LaRiviere (142.161.35.129) jsunn@mts.net on

    dlg is a bot what says `i need disks'.
    ...and a good example of what makes openbsd great.

    kudos and thanks,
    jason.

  4. By Anonymous Coward (82.71.120.74) on

    How about stopping patting yourself on the back for a minute and writing/fixing drivers for hardware that people actually use?

    Comments
    1. By Brad (216.138.195.228) brad at comstyle com on

      > How about stopping patting yourself on the back for a minute and writing/fixing drivers for hardware that people actually use?

      The mpi(4) driver covers a wide range of LSI Logic SCSI, FC and SAS supporting chipsets. These chipsets are being used in quite a number
      of workstations and servers as well as being emulated by VMware. This
      is hardware people are actually using. Maybe you have a suggestion for
      something that needs fixing, if so you can file a PR letting us know what that is. Or is there a particular piece of hardware that is not supported which you would like to see support for?

      Comments
      1. By Anonymous Coward (82.71.120.74) on

        > The mpi(4) driver covers a wide range of LSI Logic SCSI, FC and SAS supporting chipsets. These chipsets are being used in quite a number
        > of workstations and servers as well as being emulated by VMware. This
        > is hardware people are actually using. Maybe you have a suggestion for
        > something that needs fixing, if so you can file a PR letting us know what that is. Or is there a particular piece of hardware that is not supported which you would like to see support for?

        All the PR I've ever filed have been ignored despite my best efforts to make them as informative as possible. This leads me to believe that OpenBSD developers would rather focus on their current pet projects than fixing and improving existing code. This wouldn't be so bad if they didn't go around patting themselves on the back about how "correct" the operating system is.

        Comments
        1. By Anonymous Coward (216.138.195.228) on

          You could at least give some hint as to what the issue is or point out particular PR numbers..

          Comments
          1. By Anonymous Coward (82.71.120.74) on

            > You could at least give some hint as to what the issue is or point out particular PR numbers..

            The issue is that the developers ignore bug reports and make out that their drivers and general code quality is above that of other operating systems which, in my opinion, is pretty far from the truth.

            http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=4504
            http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=5143
            http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=5146
            http://marc.theaimsgroup.com/?l=openbsd-misc&m=114934436115916&w=2

            The reason the last one isn't a PR is because I've given up trying to get things fixed.

            Comments
            1. By Matthias Kilian (84.134.63.90) on

              Well, all your PRs were about sound and video, and multimedia doesn't have such a high priority in OpenBSD.

              BTW: for you auvia problem, if *disabling* pcibios doesn't give usable results, try *changing* it's flags to 4 (Fixup PCI interrupt routing) or other options. See pcibios(4).

            2. By tedu (64.254.239.165) on

              > > You could at least give some hint as to what the issue is or point out particular PR numbers..
              >
              > The issue is that the developers ignore bug reports and make out that their drivers and general code quality is above that of other operating systems which, in my opinion, is pretty far from the truth.
              >
              > http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=4504
              > http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=5143
              > http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=5146
              > http://marc.theaimsgroup.com/?l=openbsd-misc&m=114934436115916&w=2
              >
              > The reason the last one isn't a PR is because I've given up trying to get things fixed.

              and what? i'm supposed to run out and buy all the same hardware you have to make it work?

              Comments
              1. By Anonymous Coward (82.71.120.74) on

                > and what? i'm supposed to run out and buy all the same hardware you have to make it work?

                No, you're supposed to admit that your drivers are riddled with bugs and you have no intention/way of fixing it.

                Comments
                1. By mathias (81.10.192.234) on

                  > No, you're supposed to admit that your drivers are riddled with bugs and you have no intention/way of fixing it.

                  maybe the driver works fine for him? you can still donate/lendhardware if you want to see it fixed.

                2. By borhtej (64.81.117.235) on

                  > > and what? i'm supposed to run out and buy all the same hardware you have to make it work?
                  >
                  > No, you're supposed to admit that your drivers are riddled with bugs and you have no intention/way of fixing it.

                  Yes that sound card is going to keep that box up and running RIGHT !!??
                  Hey I'll send you a sound card if you stop crying about such trivial crap and appreciate what we are all very fortunate to have access to.



                3. By Lars Hansson (203.65.246.6) on


                  > No, you're supposed to admit that your drivers are riddled with bugs and you have no intention/way of fixing it.

                  Ah yes, because it cant possibly be the hardware that's bad. No, that's just not possible.
                  Btw, "it works in Linux" does not mean it's not a hardware problem.

            3. By andrew fresh (66.185.224.6) andrew@mad-techies.org on http://openbsd.somedomain.net

              > The issue is that the developers ignore bug reports and make out that their drivers and general code quality is above that of other operating systems which, in my opinion, is pretty far from the truth.

              I have had good luck getting stuff fixed.

              This was a driver issue, and it was fixed.
              http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=4935

              This was an issue with pfctl, and after a few messages back and forth with henning, it was fixed in under 24 hours.
              http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=5130

              and I had some very good luck with a couple of USB audio cards that Just Worked.
              http://marc.theaimsgroup.com/?l=openbsd-misc&m=115016551901864&w=2

              It has been my experience that the devs do care about fixing stuff, and I have had several computers where the sound card Just Worked.

    2. By Marco Peereboom (67.64.89.177) on

      > How about stopping patting yourself on the back for a minute and writing/fixing drivers for hardware that people actually use?

      I use this driver on virtually all my machines. Don't know what you are talking about when you say "actually use". Care to be more specific or are you just trolling?

      If your PRs are ignored maybe you should look at the lowest common denominator; you. Maybe your PRs are not as useful as you think. Maybe it's different hardware than what I use on a daily basis.

      Criticism is fine but expect introspection.

      Comments
      1. By Anonymous Coward (82.71.120.74) on

        > I use this driver on virtually all my machines. Don't know what you are talking about when you say "actually use". Care to be more specific or are you just trolling?

        See the list of PR I posted in this thread. Soundcard support seems to be particularly bad on OpenBSD. Some guy responded that video and sound isn't really a priority for OpenBSD which would only serve to reinforce my point that there is a lot of half-assed, "we can't be bothered" code lying around.

        > If your PRs are ignored maybe you should look at the lowest common denominator; you. Maybe your PRs are not as useful as you think. Maybe it's different hardware than what I use on a daily basis.

        Maybe they aren't, but the fact is I'm trying to improve things and nobody can even be bothered to tell me what information would help (ie. they don't really care whether the bug gets fixed or not).

        Comments
        1. By Anonymous Coward (67.64.89.177) on

          I use a disk everyday. On the other hand I never use a soundcard. Maybe you are confused about what hardware is used day to day. I am sorry but since I don't use (own really) any sound equipment and can't therefore not even begin to fix it. You are simply hijacking this conversation.

          Comments
          1. By Anonymous Coward (82.71.120.74) on

            > I use a disk everyday. On the other hand I never use a soundcard. Maybe you are confused about what hardware is used day to day. I am sorry but since I don't use (own really) any sound equipment and can't therefore not even begin to fix it. You are simply hijacking this conversation.

            My post wasn't aimed directly at you but at the constant posting on this site about how awesomely outrageous OpenBSD drivers are and how everything "just works".

            Comments
            1. By Anonymous Coward (67.64.89.177) on

              > My post wasn't aimed directly at you but at the constant posting on this site about how awesomely outrageous OpenBSD drivers are and how everything "just works".

              And it doesn't it strike you as odd that OpenBSD code that is written from scratch actually works whereas ported code ends up causing your bad experience?

              Comments
              1. By Anonymous Coward (82.71.120.74) on

                > And it doesn't it strike you as odd that OpenBSD code that is written from scratch actually works whereas ported code ends up causing your bad experience?

                Eh? What I've been saying so far should illustrate the fact that in my experience this simply isn't the case. All the PR I listed are problems with either OpenBSD code or software that's part of the base system.

                Comments
                1. By deanna (70.48.231.70) on

                  This entry is a tribute to some excellent work that *many* people are very happy to have. It's too bad that someone with an axe to grind (about some extremely petty problems) has derailed it.

                  I'm sorry that you have problems with your onboard sound and video playback. I've been happily using OpenBSD as a desktop system for many years and have never experienced these problems. If it means so much to you, why don't you check the platform pages where you'll find the list of supported devices, and choose your hardware more carefully? Check mailing list archives, and ask other users what works for them.

                  Comments
                  1. By Anonymous Coward (82.71.120.74) on

                    > This entry is a tribute to some excellent work that *many* people are very happy to have. It's too bad that someone with an axe to grind (about some extremely petty problems) has derailed it.
                    >
                    > I'm sorry that you have problems with your onboard sound and video playback. I've been happily using OpenBSD as a desktop system for many years and have never experienced these problems. If it means so much to you, why don't you check the platform pages where you'll find the list of supported devices, and choose your hardware more carefully? Check mailing list archives, and ask other users what works for them.

                    I bought 2 standalone soundcards in an effort to get sound working on OpenBSD. The Sound Blaster Live! driver didn't work with that particular hardware version and the C-Media one sounded like total shit. I finally managed to get my onboard sound working by disabling pcibios, without this workaround the machine freezes when it tries to initialise the sound card. I even offered to give the Sound Blaster card to anyone who might want to fix the problem but nobody has shown any interest.

                    Given the response I've had here today and the constant modding down of my posts I think it's fairly obvious that both OpenBSD users and developers would rather ignore problems and deride people who point them out than actually acknowledge or fix them. That being the case I think it's in everyones best interest if I not waste time by pointing them out.

                    Comments
                    1. By Anonymous Coward (67.64.89.177) on

                      As I said, those drivers were ported from other operating systems.

                    2. By Anonymous Coward (68.104.220.48) on

                      > > This entry is a tribute to some excellent work that *many* people are very happy to have. It's too bad that someone with an axe to grind (about some extremely petty problems) has derailed it.
                      > >
                      > > I'm sorry that you have problems with your onboard sound and video playback. I've been happily using OpenBSD as a desktop system for many years and have never experienced these problems. If it means so much to you, why don't you check the platform pages where you'll find the list of supported devices, and choose your hardware more carefully? Check mailing list archives, and ask other users what works for them.
                      >
                      > I bought 2 standalone soundcards in an effort to get sound working on OpenBSD. The Sound Blaster Live! driver didn't work with that particular hardware version and the C-Media one sounded like total shit. I finally managed to get my onboard sound working by disabling pcibios, without this workaround the machine freezes when it tries to initialise the sound card. I even offered to give the Sound Blaster card to anyone who might want to fix the problem but nobody has shown any interest.

                      Good realization. Bugs are fixed in order of importance. Importance can be a subjective measure of how useful it is to a developer at the time they view the bug to fix it. And somehow its just not shocking that support for disks on a BSD system trumps support for you multimedia devices. Almost makes you think that disks are more important than having sound cards for most people. Weird.

                      > Given the response I've had here today and the constant modding down of my posts I think it's fairly obvious that both OpenBSD users and developers would rather ignore problems and deride people who point them out than actually acknowledge or fix them. That being the case I think it's in everyones best interest if I not waste time by pointing them out.

                      Oh, come off it. Quit feeling sorry for yourself. You busted into the thread with an obnoxious attitude and demeaning tone, and you expect to be catered to? What universe does that happen in?

                      I daresay no one owes you anything.

        2. By Anonymous Coward (128.171.90.200) on

          > they don't really care whether the bug gets fixed or not

          you are quite right, all this talk of being a secure stable operating system is a complete smoke screen for lazy slackness, evidenced by the fact you cannot get your soundcard to work. I for one am going back to using Windows and smoking crack.

          Comments
          1. By Anonymous Coward (69.246.68.23) on

            > > they don't really care whether the bug gets fixed or not
            >
            > you are quite right, all this talk of being a secure stable operating system is a complete smoke screen for lazy slackness, evidenced by the fact you cannot get your soundcard to work. I for one am going back to using Windows and smoking crack.
            >

            Here, here!

    3. By Anonymous Coward (203.65.246.6) on

      > How about stopping patting yourself on the back for a minute and writing/fixing drivers for hardware that people actually use?

      How about stopping being a worthless troll and write something usefull?

    4. By Tyler (129.89.253.134) on

      > How about stopping patting yourself on the back for a minute and >writing/fixing drivers for hardware that people actually use?

      I've got a good suggestion for you: Since you're having so much trouble with these different new (probably expensive) soundcards, try stepping back a bit. I bet you can pick up an AWE64 for a song and it'll probably "just work".

      To keep this comment on topic: Thanks for the drivers. I don't have U320, but my shit "just works". I appreciate that. :-)

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]