Re: Longsoon/Godson MIPS boxes, where to buy?
The deal with Lemote is you want free box with no restricted anything its the way to go. For 250 us dollar its not a bad network but for 500 for the 10.9 I can get a used I5 for that price easy. Its just not the same to compair an intel aton or I3 to Lemote product. One is totally free and the other is not On 12/31/2011 09:57 PM, Nomen Nescio wrote: most netbooks with Intel Atom retail in the $250 to $400 range; what's your damage? Because the Longsoon stuff is not on the level of refinement of Intel, not by a long shot. Longsoon is supposed to be cheap. So far it's not.
Re: Longsoon/Godson MIPS boxes, where to buy?
> most netbooks with Intel Atom retail in the $250 to $400 range; what's > your damage? Because the Longsoon stuff is not on the level of refinement of Intel, not by a long shot. Longsoon is supposed to be cheap. So far it's not.
Re: problem with puc(4) on -current
Hi,
On Saturday, December 31, 2011 13:13 CET, Stuart Henderson
wrote:
> On 2011-12-31, Sebastian Reitenbach wrote:
> >> > Right now I'm running 4.6 on it, and thought, its time to upgrade, so
> >> > installed -current from today ;)
> ..
> >> > When I use /dev/tty03 (the first port of the PUC), then it takes the
> >> > speed values I give with cu -s correctly, and I can connect fine to the
> >> > sparc, when its there connected.
> >> > The problems start with tty04, and up to tty0a, I guess all those ports
> >> > just only take 1200 bauds.
>
> > 0:14:0: Sunix 40XX
> > 0x: Vendor ID: 1409 Product ID: 7168
> > 0x0004: Command: 0181 Status ID: 0280
> > 0x0008: Class: 07 Subclass: 00 Interface: 02 Revision: 01
> > 0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size:
> > 00
> > 0x0010: BAR io addr: 0xe500/0x0020
> > 0x0014: BAR io addr: 0xe520/0x0010
> > 0x0018: BAR io addr: 0xe530/0x0008
> > 0x001c: BAR io addr: 0xe538/0x0008
> > 0x0020: BAR io addr: 0xe540/0x0008
> > 0x0024: BAR io addr: 0xe548/0x0008
> > 0x0028: Cardbus CIS:
> > 0x002c: Subsystem Vendor ID: 1409 Product ID: 5066
> > 0x0030: Expansion ROM Base Address:
> > 0x0038:
> > 0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
>
> This was changed in pucdata.c r1.65 so we could get more exact matching on
> the various devices using the same PCI vendor/product ID as your device.
>
> Diff below should put things back how they were for your card, but
> it doesn't quite tie in with what you say as the first *2* ports
> on the puc should have worked, not the first 1.
also naddy pointed me to pucdata.c. Your patch alone did not helped, trying it,
I had the same garbage as without.
Then I removed the SUNIX entry before the chunk that your patch added, and it
suddenly started to work like it did on the 4.6.
The patch to make it work for me would look like the one below.
thanks,
Sebastian
Index: pucdata.c
===
RCS file: /cvs/src/sys/dev/pci/pucdata.c,v
retrieving revision 1.78
diff -u -r1.78 pucdata.c
--- pucdata.c 26 Oct 2011 14:20:25 - 1.78
+++ pucdata.c 31 Dec 2011 15:47:25 -
@@ -1441,17 +1441,17 @@
},
{ /* SUNIX 406X 8S */
- { PCI_VENDOR_SUNIX, PCI_PRODUCT_SUNIX_40XX, 0x1409, 0x4060 },
- { 0x, 0x, 0x, 0xe0f0 },
+ { PCI_VENDOR_SUNIX, PCI_PRODUCT_SUNIX_40XX, 0x1409, 0x5066 },
+ { 0x, 0x, 0x, 0x },
{
{ PUC_COM_POW2(3), 0x10, 0x },
{ PUC_COM_POW2(3), 0x10, 0x0008 },
- { PUC_COM_POW2(3), 0x14, 0x },
- { PUC_COM_POW2(3), 0x14, 0x0008 },
- { PUC_COM_POW2(3), 0x18, 0x },
- { PUC_COM_POW2(3), 0x1c, 0x },
- { PUC_COM_POW2(3), 0x20, 0x },
- { PUC_COM_POW2(3), 0x24, 0x },
+ { PUC_COM_POW2(0), 0x14, 0x },
+ { PUC_COM_POW2(0), 0x14, 0x0008 },
+ { PUC_COM_POW2(0), 0x18, 0x },
+ { PUC_COM_POW2(0), 0x1c, 0x },
+ { PUC_COM_POW2(0), 0x20, 0x },
+ { PUC_COM_POW2(0), 0x24, 0x },
},
},
>
> Index: pucdata.c
> ===
> RCS file: /cvs/src/sys/dev/pci/pucdata.c,v
> retrieving revision 1.78
> diff -u -p -r1.78 pucdata.c
> --- pucdata.c 26 Oct 2011 14:20:25 - 1.78
> +++ pucdata.c 31 Dec 2011 12:09:21 -
> @@ -1455,6 +1455,21 @@ const struct puc_device_description puc_
> },
> },
>
> + { /* SUNIX 406X 8S */
> + { PCI_VENDOR_SUNIX, PCI_PRODUCT_SUNIX_40XX, 0x1409, 0x5066 },
> + { 0x, 0x, 0x, 0x },
> + {
> + { PUC_COM_POW2(3), 0x10, 0x },
> + { PUC_COM_POW2(3), 0x10, 0x0008 },
> + { PUC_COM_POW2(0), 0x14, 0x },
> + { PUC_COM_POW2(0), 0x14, 0x0008 },
> + { PUC_COM_POW2(0), 0x18, 0x },
> + { PUC_COM_POW2(0), 0x1c, 0x },
> + { PUC_COM_POW2(0), 0x20, 0x },
> + { PUC_COM_POW2(0), 0x24, 0x },
> + },
> + },
> +
> { /* SUNIX 407X 2S/1P */
> { PCI_VENDOR_SUNIX, PCI_PRODUCT_SUNIX_40XX, 0x1409, 0x4070 },
> { 0x, 0x, 0x, 0xeff0 },
Re: MIDI over USB
The manual of the MIDI keyboard says: When using USB cable to connect UF keyboard to computer music system, you must install the UF driver to the computer; otherwise the system will not accept the device. So, does > Dec 31 15:11:04 box /bsd: ugen0 at uhub1 port 1 "vendor 0x7104 product > 0x2202" rev 1.00/1.00 addr 2 meanly that my device (CME UF6) is not USB class compliant, and therefore not supported by the umidi driver? Jan
Re: MIDI over USB
On Dec 31 14:23:25, Robert wrote: > On Sat, 31 Dec 2011 13:25:57 +0100 > Jan Stary wrote: > > Reading fag13#midi, in particular the dmesg example, > > makes me think that USB-connected MIDI components > > should be recognized. Am I missing something? > > I just tested - works fine [1]; just try a different port. Mine didn't > work on the EHCI port [2], but on the add-in card with UHCI [3]. I tried all my USB ports now, with the same result: if I plug the USB cable in and then turn the keyboard on, nothing happens; if I turn the keyboard on and then plug the USB cable in, the following device appears: Dec 31 15:11:04 box /bsd: ugen0 at uhub1 port 1 "vendor 0x7104 product 0x2202" rev 1.00/1.00 addr 2 > The question is rather what you are going to do next. I tried to set up > some software environment (synths, sequencer, effects etc.) under > OpenBSD, but I run into a lot of issues since many tools are > unfortunately "Linux-specific", audio/midish Jan
Re: MIDI over USB
On Sat, 31 Dec 2011 13:25:57 +0100 Jan Stary wrote: > Reading fag13#midi, in particular the dmesg example, > makes me think that USB-connected MIDI components > should be recognized. Am I missing something? I just tested - works fine [1]; just try a different port. Mine didn't work on the EHCI port [2], but on the add-in card with UHCI [3]. The question is rather what you are going to do next. I tried to set up some software environment (synths, sequencer, effects etc.) under OpenBSD, but I run into a lot of issues since many tools are unfortunately "Linux-specific", i.e. not usable without a lot of source code changes (if at all). So I ended up using a dedicated Linux machine for this. (I'm not talking about just recording some MIDI events, but rather a full set of tools such as e.g. www.64studio.com provides) If someone had a better experience, please post your setup! kind regards, Robert [1] umidi0 at uhub3 port 1 configuration 1 interface 1 "WORLDE WORLDE CONTROLLER" rev 1.10/0.00 addr 2 umidi0: (genuine USB-MIDI) umidi0: out=1, in=1 midi0 at umidi0: ugen1 at uhub3 port 1 configuration 1 "WORLDE product 0x0201" rev 1.10/0.00 addr 2 [2] addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel (0x8086), rev 1.00 [3] addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA (0x1106), rev 1.00 port 1 addr 2: full speed, power 500 mA, config 1,product 0x0201 (0x0201), vendor 0x0218(0x0218), rev 0.00
Re: MIDI over USB
On Dec 31 13:25:57, Jan Stary wrote: > So I bought me a MIDI keyboard to enter the MIDI world. (It's a CME UF6) > My sound card does not have a MIDI input, so before > I buy one that does, I am connecting the keyboard > via USB, which seems to work fine in Protools and > MacOS's GarageBand. Now I'm trying to use it under > OpenBSD. > > Reading fag13#midi, in particular the dmesg example, > makes me think that USB-connected MIDI components > should be recognized. Am I missing something? OpenBSD 5.0-current (GENERIC.MP) #155: Sat Dec 10 07:57:12 MST 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 1054593024 (1005MB) avail mem = 1012428800 (965MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe4410 (25 entries) bios0: vendor Intel Corp. version "MOPNV10J.86A.0175.2010.0308.0620" date 03/08/2010 bios0: Intel Corporation D510MO acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET SSDT acpi0: wakeup devices SLPB(S4) PS2M(S4) PS2K(S4) UAR1(S4) UAR2(S4) P32_(S4) ILAN(S4) PEX0(S4) PEX1(S4) PEX2(S4) PEX3(S4) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) EHCI(S3) AZAL(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.98 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,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG cpu0: 512KB 64b/line 8-way L2 cache cpu0: apic clock running at 168MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1683.35 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,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG cpu1: 512KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1683.36 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,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG cpu2: 512KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1683.35 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,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG cpu3: 512KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 5 (P32_) acpiprt1 at acpi0: bus 0 (PCI0) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus 2 (PEX1) acpiprt4 at acpi0: bus 3 (PEX2) acpiprt5 at acpi0: bus 4 (PEX3) acpicpu0 at acpi0: C1, PSS acpicpu1 at acpi0: C1, PSS acpicpu2 at acpi0: C1, PSS acpicpu3 at acpi0: C1, PSS acpibtn0 at acpi0: SLPB pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Pineview DMI" rev 0x02 vga1 at pci0 dev 2 function 0 "Intel Pineview Video" rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1: apic 8 int 16 drm0 at inteldrm0 ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: msi pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x03: RTL8168D/8111D (0x2800), apic 8 int 16, address 00:27:0e:07:09:9f rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x01: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x01: msi pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x01: msi pci4 at ppb3 bus 4 uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 8 int 23 uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: apic 8 int 19 uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 8 int 18 uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 8 int 16 ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: apic 8 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe1 pci5 at ppb4 bus 5 pcib0 at pci0 dev 31 function 0 "Intel Tigerpoint LPC" rev 0x01 ahci0 at pci0 dev 31 function 2 "Intel 82801GR AHCI" rev 0x01: msi, AHCI 1.1 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed naa.50014ee25979e46a sd0: 610480MB, 512 bytes/sector, 1250263728 sectors sd1 at scsibus0 targ 1 lun 0: SCSI3 0/direct fixed naa.50014ee2aed8deca sd1: 953869MB, 512 bytes/sector, 1953525168 secto
MIDI over USB
So I bought me a MIDI keyboard to enter the MIDI world. My sound card does not have a MIDI input, so before I buy one that does, I am connecting the keyboard via USB, which seems to work fine in Protools and MacOS's GarageBand. Now I'm trying to use it under OpenBSD. Reading fag13#midi, in particular the dmesg example, makes me think that USB-connected MIDI components should be recognized. Am I missing something? Thank you for your time Jan
Re: problem with puc(4) on -current
On 2011-12-31, Sebastian Reitenbach wrote:
>> > Right now I'm running 4.6 on it, and thought, its time to upgrade, so
>> > installed -current from today ;)
..
>> > When I use /dev/tty03 (the first port of the PUC), then it takes the speed
>> > values I give with cu -s correctly, and I can connect fine to the sparc,
>> > when its there connected.
>> > The problems start with tty04, and up to tty0a, I guess all those ports
>> > just only take 1200 bauds.
> 0:14:0: Sunix 40XX
> 0x: Vendor ID: 1409 Product ID: 7168
> 0x0004: Command: 0181 Status ID: 0280
> 0x0008: Class: 07 Subclass: 00 Interface: 02 Revision: 01
> 0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
> 0x0010: BAR io addr: 0xe500/0x0020
> 0x0014: BAR io addr: 0xe520/0x0010
> 0x0018: BAR io addr: 0xe530/0x0008
> 0x001c: BAR io addr: 0xe538/0x0008
> 0x0020: BAR io addr: 0xe540/0x0008
> 0x0024: BAR io addr: 0xe548/0x0008
> 0x0028: Cardbus CIS:
> 0x002c: Subsystem Vendor ID: 1409 Product ID: 5066
> 0x0030: Expansion ROM Base Address:
> 0x0038:
> 0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
This was changed in pucdata.c r1.65 so we could get more exact matching on
the various devices using the same PCI vendor/product ID as your device.
Diff below should put things back how they were for your card, but
it doesn't quite tie in with what you say as the first *2* ports
on the puc should have worked, not the first 1.
Index: pucdata.c
===
RCS file: /cvs/src/sys/dev/pci/pucdata.c,v
retrieving revision 1.78
diff -u -p -r1.78 pucdata.c
--- pucdata.c 26 Oct 2011 14:20:25 - 1.78
+++ pucdata.c 31 Dec 2011 12:09:21 -
@@ -1455,6 +1455,21 @@ const struct puc_device_description puc_
},
},
+ { /* SUNIX 406X 8S */
+ { PCI_VENDOR_SUNIX, PCI_PRODUCT_SUNIX_40XX, 0x1409, 0x5066 },
+ { 0x, 0x, 0x, 0x },
+ {
+ { PUC_COM_POW2(3), 0x10, 0x },
+ { PUC_COM_POW2(3), 0x10, 0x0008 },
+ { PUC_COM_POW2(0), 0x14, 0x },
+ { PUC_COM_POW2(0), 0x14, 0x0008 },
+ { PUC_COM_POW2(0), 0x18, 0x },
+ { PUC_COM_POW2(0), 0x1c, 0x },
+ { PUC_COM_POW2(0), 0x20, 0x },
+ { PUC_COM_POW2(0), 0x24, 0x },
+ },
+ },
+
{ /* SUNIX 407X 2S/1P */
{ PCI_VENDOR_SUNIX, PCI_PRODUCT_SUNIX_40XX, 0x1409, 0x4070 },
{ 0x, 0x, 0x, 0xeff0 },
Re: problem with puc(4) on -current
On Saturday, December 31, 2011 11:55 CET, "Sebastian Reitenbach"
wrote:
> On Saturday, December 31, 2011 11:47 CET, "Sebastian Reitenbach"
> wrote:
>
> > On Saturday, December 31, 2011 10:58 CET, "Sebastian Reitenbach"
> > wrote:
> >
> > > Hi,
> > >
> > > I have a Soekris box equipped with an 8 port serial card I use to manage
> > > all my hardware using cu.
> > > Right now I'm running 4.6 on it, and thought, its time to upgrade, so
> > > installed -current from today ;)
> > > Luckily I did the new installation on a separate CF card, to easily go
> > > back.
> > >
> > > When I now try to a serial console using a port tty04 or above, then I
> > > only get garbage. For example I call
> > >
> > > cu -l /dev/tty0a -s 9600
> > > to get to my sparc, and I just get garbage back when I enter smth.
> > >
> > > When I try to connect to my procurve switch,
> > >
> > > cu -l /dev/tty09 -s 9600
> > >
> > > then, the switch has speed autonegotiation, and connects fine with 1200
> > > baud, but not the desired 9600 baud.
> > >
> > > When I use /dev/tty03 (the first port of the PUC), then it takes the
> > > speed values I give with cu -s correctly, and I can connect fine to the
> > > sparc, when its there connected.
> > > The problems start with tty04, and up to tty0a, I guess all those ports
> > > just only take 1200 bauds.
> > >
> > > When I change back the CF card with the 4.6 installed, then all ports are
> > > fine again, so I did not damaged anything while updating.
got another off-list request for a 4.6 dmesg:
OpenBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 500
MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX
real mem = 536440832 (511MB)
avail mem = 509902848 (486MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 20/80/26, BIOS32 rev. 0 @ 0xfac40
pcibios0 at bios0: rev 2.0 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc8000/0xa800
cpu0 at mainbus0: (uniprocessor)
amdmsr0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
io address conflict 0x6100/0x100
io address conflict 0x6200/0x200
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x31
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 6 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address
00:00:24:c9:d4:98
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr1 at pci0 dev 7 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 5, address
00:00:24:c9:d4:99
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr2 at pci0 dev 8 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 9, address
00:00:24:c9:d4:9a
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr3 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12, address
00:00:24:c9:d4:9b
ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
puc0 at pci0 dev 14 function 0 "Sunix 40XX" rev 0x01: ports: 8 com
com3 at puc0 port 0 irq 10: ti16750, 64 byte fifo
com3: probed fifo depth: 32 bytes
com4 at puc0 port 1 irq 10: ti16750, 64 byte fifo
com4: probed fifo depth: 32 bytes
com5 at puc0 port 2 irq 10: ti16750, 64 byte fifo
com5: probed fifo depth: 32 bytes
com6 at puc0 port 3 irq 10: ti16750, 64 byte fifo
com6: probed fifo depth: 32 bytes
com7 at puc0 port 4 irq 10: ti16750, 64 byte fifo
com7: probed fifo depth: 32 bytes
com8 at puc0 port 5 irq 10: ti16750, 64 byte fifo
com8: probed fifo depth: 32 bytes
com9 at puc0 port 6 irq 10: ti16750, 64 byte fifo
com9: probed fifo depth: 32 bytes
com10 at puc0 port 7 irq 10: ti16750, 64 byte fifo
com10: probed fifo depth: 32 bytes
glxpcib0 at pci0 dev 20 function 0 "AMD CS5536 ISA" rev 0x03: rev 0, 32-bit
3579545Hz timer, watchdog, gpio
gpio0 at glxpcib0: 32 pins
pciide0 at pci0 dev 20 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 1-sector PIO, LBA, 1918MB, 3928176 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 21 function 0 "AMD CS5536 USB" rev 0x02: irq 15, version 1.0,
legacy support
ehci0 at pci0 dev 21 function 1 "AMD CS5536 USB" rev 0x02: irq 15
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "AMD EHCI root hub" rev 2.00/1.00 addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pcppi0 at isa0 port 0x61
mid
Re: problem with puc(4) on -current
On Saturday, December 31, 2011 11:47 CET, "Sebastian Reitenbach"
wrote:
> On Saturday, December 31, 2011 10:58 CET, "Sebastian Reitenbach"
> wrote:
>
> > Hi,
> >
> > I have a Soekris box equipped with an 8 port serial card I use to manage
> > all my hardware using cu.
> > Right now I'm running 4.6 on it, and thought, its time to upgrade, so
> > installed -current from today ;)
> > Luckily I did the new installation on a separate CF card, to easily go
> > back.
> >
> > When I now try to a serial console using a port tty04 or above, then I only
> > get garbage. For example I call
> >
> > cu -l /dev/tty0a -s 9600
> > to get to my sparc, and I just get garbage back when I enter smth.
> >
> > When I try to connect to my procurve switch,
> >
> > cu -l /dev/tty09 -s 9600
> >
> > then, the switch has speed autonegotiation, and connects fine with 1200
> > baud, but not the desired 9600 baud.
> >
> > When I use /dev/tty03 (the first port of the PUC), then it takes the speed
> > values I give with cu -s correctly, and I can connect fine to the sparc,
> > when its there connected.
> > The problems start with tty04, and up to tty0a, I guess all those ports
> > just only take 1200 bauds.
> >
> > When I change back the CF card with the 4.6 installed, then all ports are
> > fine again, so I did not damaged anything while updating.
>
> got an off-list reply (thanks), suggesting to try cua(4) instead of tty(4),
> but the problem persists.
and here is a pcidump -v
0:14:0: Sunix 40XX
0x: Vendor ID: 1409 Product ID: 7168
0x0004: Command: 0181 Status ID: 0280
0x0008: Class: 07 Subclass: 00 Interface: 02 Revision: 01
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR io addr: 0xe500/0x0020
0x0014: BAR io addr: 0xe520/0x0010
0x0018: BAR io addr: 0xe530/0x0008
0x001c: BAR io addr: 0xe538/0x0008
0x0020: BAR io addr: 0xe540/0x0008
0x0024: BAR io addr: 0xe548/0x0008
0x0028: Cardbus CIS:
0x002c: Subsystem Vendor ID: 1409 Product ID: 5066
0x0030: Expansion ROM Base Address:
0x0038:
0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00
>
> Sebastian
>
>
>
> >
> > anyone can help, dmesg below, and ls -l /dev/tty0*
> >
> > Sebastian
> >
> > OpenBSD 5.0-current (GENERIC) #118: Tue Dec 20 11:09:21 MST 2011
> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> > cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class)
> > 500 MHz
> > cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
> > real mem = 536408064 (511MB)
> > avail mem = 517550080 (493MB)
> > mainbus0 at root
> > bios0 at mainbus0: AT/286+ BIOS, date 20/80/26, BIOS32 rev. 0 @ 0xfac40
> > pcibios0 at bios0: rev 2.0 @ 0xf/0x1
> > pcibios0: pcibios_get_intr_routing - function not supported
> > pcibios0: PCI IRQ Routing information unavailable.
> > pcibios0: PCI bus #0 is the last bus
> > bios0: ROM list: 0xc8000/0xa800
> > cpu0 at mainbus0: (uniprocessor)
> > amdmsr0 at mainbus0
> > pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> > io address conflict 0x6100/0x100
> > io address conflict 0x6200/0x200
> > pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x31
> > glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
> > vr0 at pci0 dev 6 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11,
> > address 00:00:24:c9:d4:98
> > ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> > 0x004063, model 0x0034
> > vr1 at pci0 dev 7 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 5,
> > address 00:00:24:c9:d4:99
> > ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> > 0x004063, model 0x0034
> > vr2 at pci0 dev 8 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 9,
> > address 00:00:24:c9:d4:9a
> > ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> > 0x004063, model 0x0034
> > vr3 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12,
> > address 00:00:24:c9:d4:9b
> > ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> > 0x004063, model 0x0034
> > puc0 at pci0 dev 14 function 0 "Sunix 40XX" rev 0x01: ports: 8 com
> > com3 at puc0 port 0 irq 10: ti16750, 64 byte fifo
> > com3: probed fifo depth: 32 bytes
> > com4 at puc0 port 1 irq 10: ti16750, 64 byte fifo
> > com4: probed fifo depth: 32 bytes
> > com5 at puc0 port 2 irq 10: ti16750, 64 byte fifo
> > com5: probed fifo depth: 32 bytes
> > com6 at puc0 port 3 irq 10: ti16750, 64 byte fifo
> > com6: probed fifo depth: 32 bytes
> > com7 at puc0 port 4 irq 10: ti16750, 64 byte fifo
> > com7: probed fifo depth: 32 bytes
> > com8 at puc0 port 5 irq 10: ti16750, 64 byte fifo
> > com8: probed fifo depth: 32 bytes
> > com9 at puc0 port 6 irq 10: ti16750, 64 byte fifo
> > com9: probed fifo depth: 32 bytes
> > com10 at
Re: problem with puc(4) on -current
On Saturday, December 31, 2011 10:58 CET, "Sebastian Reitenbach"
wrote:
> Hi,
>
> I have a Soekris box equipped with an 8 port serial card I use to manage all
> my hardware using cu.
> Right now I'm running 4.6 on it, and thought, its time to upgrade, so
> installed -current from today ;)
> Luckily I did the new installation on a separate CF card, to easily go back.
>
> When I now try to a serial console using a port tty04 or above, then I only
> get garbage. For example I call
>
> cu -l /dev/tty0a -s 9600
> to get to my sparc, and I just get garbage back when I enter smth.
>
> When I try to connect to my procurve switch,
>
> cu -l /dev/tty09 -s 9600
>
> then, the switch has speed autonegotiation, and connects fine with 1200 baud,
> but not the desired 9600 baud.
>
> When I use /dev/tty03 (the first port of the PUC), then it takes the speed
> values I give with cu -s correctly, and I can connect fine to the sparc, when
> its there connected.
> The problems start with tty04, and up to tty0a, I guess all those ports just
> only take 1200 bauds.
>
> When I change back the CF card with the 4.6 installed, then all ports are
> fine again, so I did not damaged anything while updating.
got an off-list reply (thanks), suggesting to try cua(4) instead of tty(4), but
the problem persists.
Sebastian
>
> anyone can help, dmesg below, and ls -l /dev/tty0*
>
> Sebastian
>
> OpenBSD 5.0-current (GENERIC) #118: Tue Dec 20 11:09:21 MST 2011
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class)
> 500 MHz
> cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
> real mem = 536408064 (511MB)
> avail mem = 517550080 (493MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 20/80/26, BIOS32 rev. 0 @ 0xfac40
> pcibios0 at bios0: rev 2.0 @ 0xf/0x1
> pcibios0: pcibios_get_intr_routing - function not supported
> pcibios0: PCI IRQ Routing information unavailable.
> pcibios0: PCI bus #0 is the last bus
> bios0: ROM list: 0xc8000/0xa800
> cpu0 at mainbus0: (uniprocessor)
> amdmsr0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> io address conflict 0x6100/0x100
> io address conflict 0x6200/0x200
> pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x31
> glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
> vr0 at pci0 dev 6 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address
> 00:00:24:c9:d4:98
> ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> vr1 at pci0 dev 7 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 5, address
> 00:00:24:c9:d4:99
> ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> vr2 at pci0 dev 8 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 9, address
> 00:00:24:c9:d4:9a
> ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> vr3 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12, address
> 00:00:24:c9:d4:9b
> ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
> 0x004063, model 0x0034
> puc0 at pci0 dev 14 function 0 "Sunix 40XX" rev 0x01: ports: 8 com
> com3 at puc0 port 0 irq 10: ti16750, 64 byte fifo
> com3: probed fifo depth: 32 bytes
> com4 at puc0 port 1 irq 10: ti16750, 64 byte fifo
> com4: probed fifo depth: 32 bytes
> com5 at puc0 port 2 irq 10: ti16750, 64 byte fifo
> com5: probed fifo depth: 32 bytes
> com6 at puc0 port 3 irq 10: ti16750, 64 byte fifo
> com6: probed fifo depth: 32 bytes
> com7 at puc0 port 4 irq 10: ti16750, 64 byte fifo
> com7: probed fifo depth: 32 bytes
> com8 at puc0 port 5 irq 10: ti16750, 64 byte fifo
> com8: probed fifo depth: 32 bytes
> com9 at puc0 port 6 irq 10: ti16750, 64 byte fifo
> com9: probed fifo depth: 32 bytes
> com10 at puc0 port 7 irq 10: ti16750, 64 byte fifo
> com10: probed fifo depth: 32 bytes
> glxpcib0 at pci0 dev 20 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit
> 3579545Hz timer, watchdog, gpio
> gpio0 at glxpcib0: 32 pins
> pciide0 at pci0 dev 20 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0
> wired to compatibility, channel 1 wired to compatibility
> wd0 at pciide0 channel 0 drive 0:
> wd0: 1-sector PIO, LBA, 1918MB, 3928176 sectors
> wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
> pciide0: channel 1 ignored (disabled)
> ohci0 at pci0 dev 21 function 0 "AMD CS5536 USB" rev 0x02: irq 15, version
> 1.0, legacy support
> ehci0 at pci0 dev 21 function 1 "AMD CS5536 USB" rev 0x02: irq 15
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "AMD EHCI root hub" rev 2.00/1.00 addr 1
> isa0 at glxpcib0
> isadma0 at isa0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboar
Re: I want buy labtop ,work OpenBSD, wireless network must work
Thanks all guys, but I need guide about Asus or Sony. Can I find Asus or Sony can work great with OpenBSD? On Dec 31, 2011 9:28 AM, "Richard Thornton" wrote: > buy an i3 instead, but what is the deign flaw which cannot be fixed via > microcode updates? > > On Fri, Dec 30, 2011 at 10:16 PM, STeve Andre' wrote: > > > On 12/30/11 21:23, Kevin Chadwick wrote: > > > >> On Fri, 30 Dec 2011 04:42:43 -0500 > >> "STeve Andre'" wrote: > >> > >> It's not the newest model, but the W500 is a wonderful laptop. I > >>> am using it now. 2.8G core two > >>> > >> Should that be w500 with dual core. Core two duos have botched microcode > >> with security risks according to Theo, though I'm not sure of the > >> specifics/severity. > >> > >> > >> Yes, W500's do have that potential problem. It's a real issue, > > which makes me think that not running Windows is a grand > > idea. I'm not sure there is a solution to this. Laptops are > > special--you can't take parts out or add them as easily as a > > desktop. *sigh* > > > > --STeve Andre'
problem with puc(4) on -current
Hi,
I have a Soekris box equipped with an 8 port serial card I use to manage all my
hardware using cu.
Right now I'm running 4.6 on it, and thought, its time to upgrade, so installed
-current from today ;)
Luckily I did the new installation on a separate CF card, to easily go back.
When I now try to a serial console using a port tty04 or above, then I only get
garbage. For example I call
cu -l /dev/tty0a -s 9600
to get to my sparc, and I just get garbage back when I enter smth.
When I try to connect to my procurve switch,
cu -l /dev/tty09 -s 9600
then, the switch has speed autonegotiation, and connects fine with 1200 baud,
but not the desired 9600 baud.
When I use /dev/tty03 (the first port of the PUC), then it takes the speed
values I give with cu -s correctly, and I can connect fine to the sparc, when
its there connected.
The problems start with tty04, and up to tty0a, I guess all those ports just
only take 1200 bauds.
When I change back the CF card with the 4.6 installed, then all ports are fine
again, so I did not damaged anything while updating.
anyone can help, dmesg below, and ls -l /dev/tty0*
Sebastian
OpenBSD 5.0-current (GENERIC) #118: Tue Dec 20 11:09:21 MST 2011
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 500
MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
real mem = 536408064 (511MB)
avail mem = 517550080 (493MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 20/80/26, BIOS32 rev. 0 @ 0xfac40
pcibios0 at bios0: rev 2.0 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc8000/0xa800
cpu0 at mainbus0: (uniprocessor)
amdmsr0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
io address conflict 0x6100/0x100
io address conflict 0x6200/0x200
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x31
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 6 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address
00:00:24:c9:d4:98
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr1 at pci0 dev 7 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 5, address
00:00:24:c9:d4:99
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr2 at pci0 dev 8 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 9, address
00:00:24:c9:d4:9a
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
vr3 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12, address
00:00:24:c9:d4:9b
ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063,
model 0x0034
puc0 at pci0 dev 14 function 0 "Sunix 40XX" rev 0x01: ports: 8 com
com3 at puc0 port 0 irq 10: ti16750, 64 byte fifo
com3: probed fifo depth: 32 bytes
com4 at puc0 port 1 irq 10: ti16750, 64 byte fifo
com4: probed fifo depth: 32 bytes
com5 at puc0 port 2 irq 10: ti16750, 64 byte fifo
com5: probed fifo depth: 32 bytes
com6 at puc0 port 3 irq 10: ti16750, 64 byte fifo
com6: probed fifo depth: 32 bytes
com7 at puc0 port 4 irq 10: ti16750, 64 byte fifo
com7: probed fifo depth: 32 bytes
com8 at puc0 port 5 irq 10: ti16750, 64 byte fifo
com8: probed fifo depth: 32 bytes
com9 at puc0 port 6 irq 10: ti16750, 64 byte fifo
com9: probed fifo depth: 32 bytes
com10 at puc0 port 7 irq 10: ti16750, 64 byte fifo
com10: probed fifo depth: 32 bytes
glxpcib0 at pci0 dev 20 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit
3579545Hz timer, watchdog, gpio
gpio0 at glxpcib0: 32 pins
pciide0 at pci0 dev 20 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 1-sector PIO, LBA, 1918MB, 3928176 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 21 function 0 "AMD CS5536 USB" rev 0x02: irq 15, version 1.0,
legacy support
ehci0 at pci0 dev 21 function 1 "AMD CS5536 USB" rev 0x02: irq 15
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "AMD EHCI root hub" rev 2.00/1.00 addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 10: GPIO VLM TMS
gpio1 at nsclpcsio0: 29 pins
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 "AMD OHCI root hub" rev 1.00/1.00 addr 1
mtrr: K6-family MTRR support (2 registers)
vscsi0 at root
scsibus0 at vscsi0: 256 targets
softraid0 at root
scsibus1 at softraid
