Re: Network configuration for laptop
On Sun, May 28, 2006 at 08:17:59AM +0200, Jan Johansson wrote: > You want trunk(4) in failover mode, it is pure magic. :-) Ah, very cool. Thanks for the tip. :-) > Blame Intel that won't give out documentation so that developers > have to guess how the card works. On that topic, I tried emailing Mr. Engelbrecht a few days ago as mentioned in the iwi(4) man page, but it bounced. I found a list of Intel contacts in the archives, but I thought I'd bring it up before blanket mailing them; is there a new suggested main email contact?
Re: Network configuration for laptop
"Matthew R. Dempsky" <[EMAIL PROTECTED]> wrote: > Is there a proper way to dynamically manage network interfaces > with OpenBSD? I have been using ``ifconfig iwi0 nwid $ESSID > nwkey $KEY; dhclient iwi0'' to connect to a given wireless > network and ``ifconfig iwi0 down'' to disconnect (and similarly > with em0 for wired networks), but this gives me problems at > times. You want trunk(4) in failover mode, it is pure magic. :-) ifconfig trunk0 trunkproto failover trunkport em0 trunkport iw0 dhclient trunk0 When moving to a new wireless network use ifconfig to set a new nwid and nwkey and it should just work. > For example, sometimes it seems I cannot (re)associate with a > wireless network or dhclient(1) will not give an IP address. > Surely there's a better solution than rebooting anytime my > network setup gets wedged. :-) (Sorry for the vague problem > descriptions---I'm not yet familiar with how to diagnose my > networking issues on OpenBSD.) I have hade some problems with iwi(4), it seems the card can hang when changing nwid but I have not enough info for a bug report. Blame Intel that won't give out documentation so that developers have to guess how the card works. > Finally, the ifconfig(1) man page mentions that the down action > ``automatically disables routes using the interface,'' but if I > run ``ifconfig iwi0 down'' after connecting to my home network, > ``route show'' still lists iwi0. Am I misreading the man page > or is this a bug? Don't know that one.
Re: they say openbsd is not as scalable as others
On 5/26/06, Jason Dixon <[EMAIL PROTECTED]> wrote: Instead of wasting your time with the question and everyone else's time suffering it, JUST TRY THE OS. If it meets your scalability/ performance needs, GREAT! If it doesn't, find something else that does. I don't think your are striking the proper tone here. Someone who asks questions on misc@ such as "why openbsd" really ought to get hit with a big lart (and hopefully become wiser for it) otherwise you are better off using an os that installs with a real pretty gui. Back to the OP: there isn't any situation in the net facing server world that is not best served with OpenBSD.
Network configuration for laptop
I installed OpenBSD 3.9 on my Thinkpad about a week ago, and I'm very happy with it. However, one issue I'm facing is how to manage my network interfaces. Under Debian, I was accustomed to using iwconfig to setup my wireless card and ifup/ifdown to bring up and down my wireless or ethernet connection as necessary. I've looked at hostname.if(5) and netstart(8), but they seem purposed for stable network connections; /etc/netstart tries raising all configured interfaces at boot time and only knows how to bring up interfaces not tear them down. Is there a proper way to dynamically manage network interfaces with OpenBSD? I have been using ``ifconfig iwi0 nwid $ESSID nwkey $KEY; dhclient iwi0'' to connect to a given wireless network and ``ifconfig iwi0 down'' to disconnect (and similarly with em0 for wired networks), but this gives me problems at times. For example, sometimes it seems I cannot (re)associate with a wireless network or dhclient(1) will not give an IP address. Surely there's a better solution than rebooting anytime my network setup gets wedged. :-) (Sorry for the vague problem descriptions---I'm not yet familiar with how to diagnose my networking issues on OpenBSD.) Finally, the ifconfig(1) man page mentions that the down action ``automatically disables routes using the interface,'' but if I run ``ifconfig iwi0 down'' after connecting to my home network, ``route show'' still lists iwi0. Am I misreading the man page or is this a bug? Thanks.
unsuscribe
unsuscribe Ricardo german Kdrcher [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ 1GB gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo http://correo.yahoo.com.ar
unsuscribe
Ricardo german Kdrcher [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ 1GB gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo http://correo.yahoo.com.ar
Re: ioapic0 degraded performance - another dmesg
Antoine Jacoutot wrote:
Hi...
I just got a "new" old system which I installed OpenBSD-3.9 on.
After parsing the dmesg, I found the following lines:
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins
ioapic0: conflicting map entries for pin 0
ioapic0: pin 19 shares different IPL interrupts (40..90), degraded performance
I don't quite understand what it means, should I be worried?
I'm booting of a GENERIC.MP on which I disable apm0 (using config) because
it was causing a panic on boot (I'm reserving this for another thread).
Note that I found some references on Google about disable pcibios in the
kernel but it still does not explain the meaning of this message.
Thanks in advance for any hints.
Complete dmesg provided.
Regards,
Just finished fun/test installing 3.9 mp on a x4000 and seeing the same
message.
OpenBSD 3.9 (GENERIC.MP) #598: Thu Mar 2 02:37:06 MST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Xeon(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID
real mem = 1072205824 (1047076K)
avail mem = 971599872 (948828K)
using 4278 buffers containing 53714944 bytes (52456K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(bc) BIOS, date 03/04/03, BIOS32 rev. 0 @ 0xfd7d2
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xfd7d0/0x830
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde90/336 (19 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #4 is the last bus
bios0: ROM list: 0xc/0xec00 0xcf000/0x4000 0xd3000/0x1800
ipmi0 at mainbus0bmc_io_wait_cold fails : *v=00 m=08 b=08 btswait
: unable to send get device id command
mainbus0: Intel MP Specification (Version 1.4) ( HP_WOMBAT )
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 99 MHz
cpu1 at mainbus0: apid 6 (application processor)
cpu1: Intel(R) Xeon(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID
mainbus0: bus 0 is type PCI
mainbus0: bus 1 is type PCI
mainbus0: bus 2 is type PCI
mainbus0: bus 3 is type PCI
mainbus0: bus 4 is type PCI
mainbus0: bus 5 is type ISA
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 3 pa 0xfec8, version 20, 24 pins
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82860 Host" rev 0x04
ppb0 at pci0 dev 1 function 0 "Intel 82850/82860 AGP" rev 0x04
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA Quadro4 900 XGL" rev 0xa3
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ppb1 at pci0 dev 2 function 0 "Intel 82860 PCI-PCI" rev 0x04
pci2 at ppb1 bus 2
ppb2 at pci2 dev 31 function 0 "Intel 82806AA" rev 0x03
pci3 at ppb2 bus 3
"Intel 82806AA APIC" rev 0x01 at pci3 dev 0 function 0 not configured
siop0 at pci3 dev 5 function 0 "Symbios Logic 53c1010-33" rev 0x01: apic
2 int 22 (irq 11), using 8K of on-board RAM
scsibus0 at siop0: 16 targets
cd0 at scsibus0 targ 2 lun 0: SCSI2 5/cdrom
removable
siop1 at pci3 dev 5 function 1 "Symbios Logic 53c1010-33" rev 0x01: apic
2 int 22 (irq 11), using 8K of on-board RAM
scsibus1 at siop1: 16 targets
siop2 at pci3 dev 8 function 0 "Symbios Logic 53c1010-66" rev 0x01: apic
2 int 23 (irq 11), using 8K of on-board RAM
scsibus2 at siop2: 16 targets
sd0 at scsibus2 targ 1 lun 0: SCSI3 0/direct
fixed
sd0: 34732MB, 49855 cyl, 2 head, 713 sec, 512 bytes/sec, 71132960 sec total
siop3 at pci3 dev 8 function 1 "Symbios Logic 53c1010-66" rev 0x01: apic
2 int 19 (irq 11), using 8K of on-board RAM
scsibus3 at siop3: 16 targets
ppb3 at pci0 dev 30 function 0 "Intel 82801BA AGP" rev 0x04
pci4 at ppb3 bus 4
vendor "Philips", unknown product 0x7146 (class multimedia subclass
miscellaneous, rev 0x01) at pci4 dev 6 function 0 not configured
fxp0 at pci4 dev 13 function 0 "Intel 8255x" rev 0x0c, i82550: apic 2
int 21 (irq 11), address 00:e0:81:00:92:af
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
ichpcib0 at pci0 dev 31 function 0 "Intel 82801BA LPC" rev 0x04
pciide0 at pci0 dev 31 function 1 "Intel 82801BA IDE" rev 0x04: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
pciide0: channel 0 disabled (no drives)
atapiscsi0 at pciide0 channel 1 drive 0
scsibus4 at atapiscsi0: 2 targets
cd1 at scsibus4 targ 0 lun 0: SCSI0
5/cdrom removable
cd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 31 function 2 "Intel 82801BA USB" rev 0x04: apic 2 int
19 (irq 11)
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 rem
Re: Multi-step upgrade failed
Craig Skinner wrote on Sat, May 27, 2006 at 07:13:27PM +0100: > On Sat, May 27, 2006 at 02:32:20PM +0200, Ingo Schwarze wrote: > >> If the machine you are talking about is in any way important and >> if you want to be reasonably sure it will work reliably, you are >> probably best off backing up your data and reinstalling from scratch. > > Once rsnapshot was pointed out to me in packages, I reinstall at every > release. A new car is better than an upgraded one... This comparison does _not_ apply, in my humble opinion. >From OpenBSD 2.7 up to about 3.4 i used to reinstall at every release, too. When i started upgrading instead, not only did the downtimes decrease, but i introduced fewer configuration bugs while i was about it. The official upgrade script is very robust and very easy to use. When your goals are correctness, reliability and efficiency, upgrading to each new release is probably better than reinstalling each new release, both for a typical server and for a typical workstation, unless you have special requirements. Once more some time later, when i started using OpenBSD-binary-upgrade (created by Han Boetes), upgrade downtime went down close to zero - without causing noticeable problems of other kinds. Of course using OpenBSD-binary-upgrade only makes sense when you known reasonably well what you are doing, it is officially unsupported, so if it breaks, you keep the pieces. It is not as robust as the official upgrade script, so if you do not know what you are doing, chances are you *will* wreak havoc while trying to use it. To reiterate, i do not advise against upgrading, quite to the contrary. But i do advise against multi-step upgrades - e.g., if you must go from 3.4 to 3.9, you should better reinstall. Yours, Ingo -- Ingo Schwarze <[EMAIL PROTECTED]>
Re: 3.9 GENERIC.MP hangs on HP NetServer LH II (2x P2 300Mhz)
Jakub G3azik napisa3(a): Srebrenko Sehic napisa3(a): Try to disable pcibios. On boot prompt, type: boot bsd.mp -c disable pcibios quit Thanks, I'll try that next time I will be near this machine. Unfortunatelly, that didn't help, I've just returned from the basement. What to try now? Notice that on GENERIC I have: biomask fb65 netmask ffe5 ttymask ffe7 and on GENERIC.MP: biomask fb65biosmask 0 netmask 0 ttymask 0 whatever that means ;-) Any clues? I believe that kernel hangs when probing for something afer this message: isapic0: pin 11 shares different IML interrputs (40..50), degraded performance If the sequence is same as on GENERIC, I could run GENERIC in verbose mode, check what is probed after "biosmask" message and disable it in MP. Gonna test it tonight or tommorow.. Any other ideas? I would really like to run this machine on GENERIC.MP.. -- .: Jakub G3azik .: zytek(at)ostrow-wlkp.net .: jid:zytek(at)azazel.ostrow-wlkp.net
Re: Sendmail X License reverted back to same as Sendmail 8
On Sat, May 27, 2006, Paul Covello wrote: > Now that the license is no longer "less free" as Sendmail 8, I am > wondering/hoping that someone might port it to OpenBSD. What do you need to "port"? The sendmail X author uses OpenBSD as main development system.
ioapic0 degraded performance
Hi...
I just got a "new" old system which I installed OpenBSD-3.9 on.
After parsing the dmesg, I found the following lines:
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins
ioapic0: conflicting map entries for pin 0
ioapic0: pin 19 shares different IPL interrupts (40..90), degraded performance
I don't quite understand what it means, should I be worried?
I'm booting of a GENERIC.MP on which I disable apm0 (using config) because
it was causing a panic on boot (I'm reserving this for another thread).
Note that I found some references on Google about disable pcibios in the
kernel but it still does not explain the meaning of this message.
Thanks in advance for any hints.
Complete dmesg provided.
Regards,
--
Antoine
OpenBSD 3.9-stable (GENERIC.MP) #1: Wed May 3 17:15:48 CEST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 1.01 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 1073307648 (1048152K)
avail mem = 972611584 (949816K)
using 4278 buffers containing 53768192 bytes (52508K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(95) BIOS, date 06/18/02, BIOS32 rev. 0 @ 0xf0b20
apm at bios0 function 0x15 not configured
pcibios0 at bios0: rev 2.1 @ 0xf/0x1362
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf12d0/144 (7 entries)
pcibios0: PCI Interrupt Router at 000:04:0 ("VIA VT82C586 ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xc000 0xcc000/0x400
mainbus0: Intel MP Specification (Version 1.4) (OEM0 PROD)
cpu0 at mainbus0: apid 3 (boot processor)
cpu0: apic clock running at 133 MHz
cpu1 at mainbus0: apid 0 (application processor)
cpu1: Intel Pentium III ("GenuineIntel" 686-class) 1.01 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
mainbus0: bus 0 is type PCI
mainbus0: bus 1 is type PCI
mainbus0: bus 2 is type ISA
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins
ioapic0: conflicting map entries for pin 0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA VT82C691 PCI" rev 0xc4
ppb0 at pci0 dev 1 function 0 "VIA VT82C598 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Radeon VE QY" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 4 function 0 "VIA VT82C686 ISA" rev 0x40
pciide0 at pci0 dev 4 function 1 "VIA VT82C571 IDE" rev 0x06: ATA100, channel 0
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors
wd1 at pciide0 channel 0 drive 1:
wd1: 16-sector PIO, LBA48, 76319MB, 156301488 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
wd2 at pciide0 channel 1 drive 0:
wd2: 16-sector PIO, LBA, 29314MB, 60036480 sectors
wd3 at pciide0 channel 1 drive 1:
wd3: 16-sector PIO, LBA48, 76319MB, 156301488 sectors
wd2(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5
wd3(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 5
uhci0 at pci0 dev 4 function 2 "VIA VT83C572 USB" rev 0x16: apic 2 int 18 (irq
5)
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 4 function 3 "VIA VT83C572 USB" rev 0x16: apic 2 int 18 (irq
5)
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
viaenv0 at pci0 dev 4 function 4 "VIA VT82C686 SMBus" rev 0x40: HWM disabled
cmpci0 at pci0 dev 9 function 0 "C-Media Electronics CMI8738/C3DX Audio" rev
0x10: apic 2 int 19 (irq 9)
audio0 at cmpci0
bktr0 at pci0 dev 10 function 0 "Brooktree BT878" rev 0x11: apic 2 int 18 (irq
5)
bktr0: Hauppauge Model 44806 D143
bktr0: Warning - Unknown Hauppauge Tuner 0x2b
bktr0: Hauppauge WinCast/TV, Philips NTSC tuner.
"Brooktree BT878 Audio" rev 0x11 at pci0 dev 10 function 1 not configured
sis0 at pci0 dev 11 function 0 "NS DP83815 10/100" rev 0x00, DP83816A: apic 2
int 17 (irq 10), address 00:14:6c:30:60:b2
nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1
pcscp0 at pci0 dev 13 function 0 "AMD 53c974 PCscsi-PCI" rev 0x10: apic 2 int
19 (irq 9)
pcscp0: AM53C974, 40MHz, SCSI ID 7
scsibus0 at pcscp0: 8 targets
cd0 at scsibus0 targ 5 lun 0: SCSI4 5/cdrom
removable
isa0 at pcib0
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 p
Sendmail X License reverted back to same as Sendmail 8
Now that the license is no longer "less free" as Sendmail 8, I am wondering/hoping that someone might port it to OpenBSD. Working with Sendmail 8 makes me lose hair! I would much rather use less hairy configure scripts :) --- Paul.
Re: SCSI disks slow
On 5/26/06, Steve Schaller <[EMAIL PROTECTED]> wrote: Henning Brauer wrote: > * Jeff Ross <[EMAIL PROTECTED]> [2006-05-25 22:53]: >>Same spindle, but 8x as fast as the 10k SCSI disks. > > guess in the dark: the scsi drives have the write cache disabled, the > ide drives enabled. at least that tends to be what the defaults are. > As a fellow SCSI user on sparc64, I've been looking high and low (man pages, google, /usr/src/sys, etc) on how to enable write cache or tagged command queuing, if either is safe enough to use, on my Ultra-2's SCSI drives. Is it using the scsi(8) command? I looked at /usr/share/misc/scsi_modes, but am getting lost in the listing of IOCTLs, and personally I can't figure out what parameters to pass to the drives. Steve Schaller I too would be very interested in seeing more scsi(8) examples than are available in the manpage. Anybody?
Re: they say openbsd is not as scalable as others
* Adam <[EMAIL PROTECTED]> [2006-05-27 04:41]: > On Sat, 27 May 2006 00:18:03 +0200 Matthias Kilian <[EMAIL PROTECTED]> wrote: > > On Fri, May 26, 2006 at 05:48:46PM -0400, Adam wrote: > > > > in soem cases, we blow away everybody else easily. > > > What cases are those? > > PF and spamd, for example. bgpd may be a good candidate, too. > Those scale better on openbsd than they do on freebsd and netbsd? Have > you actually tested this? have you? -- BS Web Services, http://www.bsws.de/ OpenBSD-based Webhosting, Mail Services, Managed Servers, ... Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Lampione solare parabola
Via Martiri Della Libert`, 78 66054 Vasto (CH) Tel. 0873.69659 Fax 0873.753116 Come aumentare la visibilit` della tua azienda? TOTEM SOLARE Una insegna auto-alimentata installabile su punti strategici per aumentare la visibilit` e il business della tua azienda. Cos'h E' totem che funziona senza l'utilizzo alla rete elettrica, esso infatti h alimentato con il sistema fotovoltaico. Benefici - ci permette di risparmiare costi di allaccio elettrico - ci evita bollette di consumo elettrico - posa in opera in qualsiasi luogo - sistema ecologico Come funziona Il modulo fotovoltaico trasforma la radiazione solare in energia elettrica, un regolatore di carica permette al modulo fotovoltaico di caricare la batteria che sar` utilizzata successivamente per il funzionamento del totem luminoso VISITA IL NOSTRO SITO: [demime 1.01d removed an attachment of type image/jpeg which had a name of parabola.jpg]
Re: Sound card with supported digital out
andrew fresh <[EMAIL PROTECTED]> wrote: > I have tried one of those, I had forgotten about that. The > problem with the USB digital output that I have tried is that > it does not do AC3/DTS passthrough, all it does is output 2 > channel PCM over the optical digital connection. > > I believe the one I tried was a Turtle Beach Audio Advantage > Micro. If there is USB audio that will do AC3/DTS passthrough > on OpenBSD, I would be happy with that. I have a Sinovoice UAC-05 which identifies like this uaudio0 at uhub0 port 2 configuration 1 interface 0: ABC C-Media USB Headphone Set, rev 1.10/1.00, addr 2 uaudio0: audio rev 1.00, 8 mixer controls audio0 at uaudio0 it is connected to my NAD T-760 receiver using a toslink (optical) cable. In the following examples I use "Gladiator" (region 2). To get DTS on the receiver: mplayer dvd:// To get Dolby Digital on the receiver: mplayer -ac hwac3 -aid 128 dvd:// (On "Shrek" (region 1) I had to use -aid to get DTS.) -ac hwac3 tells mplayer to let the soundcard do the work and not do it in software. To find the "aid" (audio id) I run mplayer with -v and look for something like this. DVD successfully opened. [open] audio stream: 0 audio format: ac3 (5.1) language: en aid: 128 [open] audio stream: 1 audio format: dts (5.1) language: en aid: 137 [open] audio stream: 2 audio format: ac3 (stereo) language: en aid: 130 Hope this helps.
Re: Multi-step upgrade failed, was: Error in pkg_add
On Sat, May 27, 2006 at 02:32:20PM +0200, Ingo Schwarze wrote: > > If the machine you are talking about is in any way important and > if you want to be reasonably sure it will work reliably, you are > probably best off backing up your data and reinstalling from scratch. Once rsnapshot was pointed out to me in packages, I reinstall at every release. A new car is better than an upgraded one... Craig. -- Craig Skinner | http://www.kepax.co.uk | [EMAIL PROTECTED]
Re: 3.9 GENERIC.MP hangs on HP NetServer LH II (2x P2 300Mhz)
Jakub G3azik napisa3(a): Srebrenko Sehic napisa3(a): Try to disable pcibios. On boot prompt, type: boot bsd.mp -c disable pcibios quit Thanks, I'll try that next time I will be near this machine. Unfortunatelly, that didn't help, I've just returned from the basement. What to try now? Notice that on GENERIC I have: biomask fb65 netmask ffe5 ttymask ffe7 and on GENERIC.MP: biomask fb65biosmask 0 netmask 0 ttymask 0 whatever that means ;-) Any clues? I believe that kernel hangs when probing for something afer this message: isapic0: pin 11 shares different IML interrputs (40..50), degraded performance If the sequence is same as on GENERIC, I could run GENERIC in verbose mode, check what is probed after "biosmask" message and disable it in MP. Gonna test it tonight or tommorow.. Any other ideas? I would really like to run this machine on GENERIC.MP.. -- .: Jakub G3azik .: zytek(at)ostrow-wlkp.net .: jid:zytek(at)azazel.ostrow-wlkp.net
Anyone with a SCSI tape changer with a barcode reader in Calgary?
Also for something that is being worked on at the hackathon we could really use a SCSI tape changer with a barcode reader, and at least a few tapes with barcodes on them. If anyone might have this in Calgary, please contact me or theo off-list. Thanks, -Bob Beck
Any SAS drives to borrow in Calgary?
For something being worked on at the hackathon, we would love to borrow at least one SAS drive (serial attached scsi). Obviously SAS is rather new and the drives are hard to find, so that is why I am asking. If anyone has one, please reply to me directly. Thanks.
Multi-step upgrade failed, was: Error in pkg_add
Hi Federico, Federico Giannici wrote on Sat, May 27, 2006 at 01:14:52PM +0200: > We upgraded an i386 PC from 3.4 to 3.9. We followed the instructions in > every "Upgrade guide" from 3.4->3.5 upto 3.8->3.9, but installed only > the 3.9 disk sets. When you intend to go from one release to the next, upgrading tends to be simpler and less error-prone than reinstalling. But when upgrades were neglected (or, under special circumstances, not necessary) for several years, it is almost always easier, quicker and cleaner to back up the data and to reinstall from scratch than to try a multi-step upgrade. A multi-step upgrade is a long and tedious process. When you have little experience, you will probably get something wrong at some point or other. If you have lots of experience, you will probably find better use for your time. In case anything does break, you will have a hard time finding anybody remembering off the top of their head which particular quirks the update process used to have several years ago. Well, of course there are people who know, but most of them will prefer debugging current problems over revisiting old ones. > Everything seems to work correctly, but we have the following error > when we try to execute a pkg_add: > > Unknown option: preserve > at /usr/libdata/perl5/OpenBSD/PackingElement.pm line 572, > <$fh> line 6. > > Is there something we can do to solve the problem? Chances are something went astray either with one of the upgrades of your Perl interpreter, or (most probably?) with on of the upgrades of the pkg_* tools, or with your /var/db/pkg package database. Maybe it's possible to sort that out in detail, but probably that amounts to an exercise in futility. Even in case you find out where this particular problem comes from, chances are something else went wrong, too, which might cause more harm later. Do you really trust yourself everything you did during the upgrade was sufficiently correct? How do you plan to evalute the potential impact of any errors that might have slipped? If the machine you are talking about is in any way important and if you want to be reasonably sure it will work reliably, you are probably best off backing up your data and reinstalling from scratch. This advice holds even now, even though you have already spent lots of time on the upgrade... :-( Yours, Ingo P.S. I would be rather surprised if your problem were related to any bug in the pkg_* tools. -- Ingo Schwarze <[EMAIL PROTECTED]>
Error in pkg_add
We upgraded an i386 PC from 3.4 to 3.9. We followed the instructions in every "Upgrade guide" from 3.4->3.5 upto 3.8->3.9, but installed only the 3.9 disk sets. Everything seems to work correctly, but we have the following error when we try to execute a pkg_add: Unknown option: preserve at /usr/libdata/perl5/OpenBSD/PackingElement.pm line 572, <$fh> line 6. Is there something we can do to solve the problem? Thanks. -- ___ __ |- [EMAIL PROTECTED] |ederico Giannici http://www.neomedia.it ___
Re: OpenBSD Not booting on E7230 chipset
> Hello, > > I tried to boot OpenBSD on E7230 chipset, but no luck so faar. System > hangs during device recognition in random moments. > Strange thing is that cursor jumps to the center of the screen. > > Has anyone managed to run OpenBSD on E7230 chipset ? Yes, from 3.8, without problems: http://www.armorlogic.com/openbsd_information_server_compatibility_list.html?action=detail&id=pe850 br, Darek
FAQ 10.13 - Setting up Anonymous FTP Services
Hi there, I've just set up an anonymous ftp server on a small LAN and done this differently to the FAQ: $ grep ^ftp /etc/passwd ftp:*:1000:999:anonymous ftp user,,,:/var/spool/ftp:/sbin/nologin $ man hier /var/spool/ ftp/ Commonly ~ftp; the anonymous ftp root directory. $ ls -ldF /var/spool/ftp dr-xr-xr-x 6 root wheel 512 May 24 01:32 /var/spool/ftp/ $ ls -lF /var/spool/ftp total 16 dr-x--x--x 2 root wheel 512 Mar 2 09:04 bin/ dr-x--x--x 2 root wheel 512 Mar 2 09:04 etc/ d--x--x--x 2 root wheel 512 Mar 2 09:04 hidden/ dr-xr-xr-x 3 root wheel 512 May 24 01:33 pub/ So I didn't have to add /bin/false to /etc/shells, nor was /home/ftp needed. $ grep ^ftp /etc/inetd.conf ftp stream tcp nowait root/usr/libexec/ftpd ftpd -llUSA I didn't alter /etc/login.conf Please advise if this is OK. Craig. -- Craig Skinner | http://www.kepax.co.uk | [EMAIL PROTECTED]
Re: ntfs partition not recognised?
On Friday 26 May 2006 19:33, akonsu wrote: > thank you. > > does anyone know if there is software to access a FFS partition from > windows (on a dual boot machine)? trying to avoid creating a FAT > patition... http://www.fs-driver.org/ read/write windows driver for ext2/3 - which OpenBSD supports too, just as any linux. No, I didn't actually test it, I don't have Windows to do so ;) -- viq
