Re: CPU time off by a factor of two
On Fri, 25 Nov 2005 15:43:52 +0800, Uwe Dippel wrote: It's a bug, so it seems now. Sorry, last night I didn't have access so my answer is late: I simply rebooted to single-CPU-kernel; compiled by myself, just as well, and it runs like hell. Exact, I mean. Not a single second off after three hours. (so says ntpdate.) I rebooted again, .mp, and it ran half as fast as it was supposed to. Off-list I was asked to try the one compiled by [EMAIL PROTECTED] I did, good idea, thanks for the suggestion. But the behaviour is identical: half-speed of time calculation. Now I'm back on single, for the time being, that's better than the screwed time. Uwe
Multiple Internet connections with CARP
Hi all, I have searched a bit now, and have not seen anything on this subject. I have 2 different internet connections, which I would like to use for my CARP setup. I was thinking that they would connect to a switch, and from there 2 lines going to each firewall, and then make some CARP setup for those two lines. Anyone knows if this could be done? Regards, Bo
auvia UKC parameters on SONY VAIO PCG-FX77Z_BP(J)
Hi All, Excuse me for disturbing too much if so. Have to 'disable auvia' in UKC to boot up 3.8 GENERIC on my SONY VAIO PCG-FX77Z_BP(J). The same keeps on happening from 3.1 so -current problably will not help. I would be grateful if anyone of you would be so kind to give me basic directions on how to know which devices, functions and flags to use in UKC according to dmesg from FreeBSD, FreeSBIE or Slack where VT82C686A and AC'97 works fine. I did google and I will go to the Source if needed. Just thought that it would be faster to cut to the chase with few lines' assistance. Thank you for your time while reading. OpenBSD 3.8 (GENERIC) #138: Sat Sep 10 15:41:37 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: mobile AMD Athlon(tm) XP 1400+ (AuthenticAMD 686-class, 256KB L2 cache) 1.20 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE cpu0: AMD Powernow: FID VID TTP real mem = 133734400 (130600K) avail mem = 115277824 (112576K) using 1658 buffers containing 6791168 bytes (6632K) of memory User Kernel Config UKC disable auvia 70 auvia* disabled UKC quit Continuing... mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 04/29/02, BIOS32 rev. 0 @ 0xfd6a0 apm0 at bios0: Power Management spec V1.2 apm0: AC on, no battery apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xfd6a0/0x960 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf60/128 (6 entries) pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C596A ISA rev 0x00) pcibios0: PCI bus #3 is the last bus bios0: ROM list: 0xc/0x1 0xd/0x4000! 0xdc000/0x4000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT8363 Host rev 0x03 ppb0 at pci0 dev 1 function 0 VIA VT8363 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Mobility 1 rev 0x64 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C686 ISA rev 0x40 pciide0 at pci0 dev 7 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: HITACHI_DK23DA-30 wd0: 16-sector PIO, LBA, 28615MB, 58605120 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, UJDA720 DVD/CDRW, 1.00 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x1a: irq 9 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 7 function 3 VIA VT83C572 USB rev 0x1a: irq 9 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 7 function 4 VIA VT82C686 SMBus rev 0x40 VIA VT82C686 AC97 rev 0x50 at pci0 dev 7 function 5 not configured VIA VT82C686 Modem rev 0x30 at pci0 dev 7 function 6 not configured cbb0 at pci0 dev 10 function 0 Texas Instruments PCI1420 CardBus rev 0x00: irq 9 cbb1 at pci0 dev 10 function 1 Texas Instruments PCI1420 CardBus rev 0x00: irq 10 Texas Instruments TSB12LV26 FireWire rev 0x00 at pci0 dev 14 function 0 not configured rl0 at pci0 dev 16 function 0 Realtek 8139 rev 0x10: irq 10 address 08:00:46:6d:f1:10 rlphy0 at rl0 phy 0: RTL internal phy 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 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 sb0 at isa0 port 0x220/24 irq 5 drq 1: dsp v3.02 midi0 at sb0: SB MIDI UART audio0 at sb0 opl0 at sb0: model OPL3 midi1 at opl0: SB Yamaha OPL3 pcppi0 at isa0 port 0x61 midi2 at pcppi0: PC speaker spkr0 at pcppi0 sysbeep0 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 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 2 device 0 cacheline 0x8, lattimer 0x20 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 3 device 0 cacheline 0x8, lattimer 0x20 pcmcia1 at cardslot1 biomask ef4d netmask ef4d ttymask ffcf pctr: user-level cycle counter enabled mtrr: Pentium Pro MTRR support dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302
Re: CPU time off by a factor of two
...on Fri, Nov 25, 2005 at 03:43:52PM +0800, Uwe Dippel wrote: It's a bug, so it seems now. Sorry, last night I didn't have access so my answer is late: I simply rebooted to single-CPU-kernel; compiled by myself, just as well, and it runs like hell. Exact, I mean. Not a single second off after three hours. (so says ntpdate.) That sounds quite a bit like what I remember reading about, something like the TSC might run at different speeds on different cores depending on thermal throttling, SpeedStep, ACPI state, whatever. So if you're switching to a counter on another core without taking that into account, you're in trouble. Which doesn't mean that's the problem here :) Alex. (no, I actually have no idea what I'm talking about)
Re: auvia UKC parameters on SONY VAIO PCG-FX77Z_BP(J)
Vladas Urbonas vladas.urbonas at gmail.com writes: Have to 'disable auvia' in UKC to boot up 3.8 GENERIC on my SONY VAIO PCG-FX77Z_BP(J). This is a fairly well known bug. The same keeps on happening from 3.1 so -current problably will not help. Your logic is flawed but regardless AFAIK the bug isn't fixed in -current. I would be grateful if anyone of you would be so kind to give me basic directions on how to know which devices, functions and flags to use in UKC according to dmesg from FreeBSD, FreeSBIE or Slack where VT82C686A and AC'97 works fine. Even unsupported devices shouldn't prevent the kernel from booting. Like I say, it's a bug.
Re: Marvell Yukon-2 / Syskonnect SK-9S22
On 25 Nov 2005 at 2:59, Adam wrote:
Hello,
I'm in need of some help getting an syskonnect SK-9S22 (dual port
gigabit ethernet) to work. I'm currently running on the i386 platform
with openbsd 3.8-current as of 11/25/05.
I believe this is the most relevant part of the dmesg:
skc0 at pci1 dev 3 function 0 Schneider Koch SK-9Sxx rev 0x12: irq 5
skc0: Marvell Yukon-2 XL (0x1)
sk port A at skc0 not configured
sk port B at skc0 not configured
For whatever reason the mac addresses for the ports are not getting
reported so sk0 sk1 aren't getting setup. Any ideas??
Apparently not really supported:
from sys/dev/pci/if_sk.c
sk_probe(struct device *parent, void *match, void *aux)
{
struct skc_attach_args *sa = aux;
if (sa-skc_port != SK_PORT_A sa-skc_port != SK_PORT_B)
return(0);
switch (sa-skc_type) {
case SK_GENESIS:
case SK_YUKON:
case SK_YUKON_LITE:
case SK_YUKON_LP:
#ifdef not_quite_yet
case SK_YUKON_XL:
case SK_YUKON_EC_U:
case SK_YUKON_EC:
case SK_YUKON_FE:
#endif
return (1);
}
return (0);
}
Re: auvia UKC parameters on SONY VAIO PCG-FX77Z_BP(J)
This is a working fix (a nasty workaround, to be honest) found somewhere on the net: --- sys/arch/i386/isa/isa_machdep.c +++ sys/arch/i386/isa/isa_machdep.c @@ -389,7 +389,8 @@ if (irqs = 0x100) /* any IRQs = 8 in use */ irqs |= 1 IRQ_SLAVE; imen = ~irqs; - SET_ICUS(); + if (imen != 0x3DDB) + SET_ICUS(); } /* For speed of splx, provide the inverse of the interrupt masks. */ Regards, -David On 11/25/05, Vladas Urbonas [EMAIL PROTECTED] wrote: Hi All, Excuse me for disturbing too much if so. Have to 'disable auvia' in UKC to boot up 3.8 GENERIC on my SONY VAIO PCG-FX77Z_BP(J). The same keeps on happening from 3.1 so -current problably will not help. I would be grateful if anyone of you would be so kind to give me basic directions on how to know which devices, functions and flags to use in UKC according to dmesg from FreeBSD, FreeSBIE or Slack where VT82C686A and AC'97 works fine. I did google and I will go to the Source if needed. Just thought that it would be faster to cut to the chase with few lines' assistance. Thank you for your time while reading. OpenBSD 3.8 (GENERIC) #138: Sat Sep 10 15:41:37 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: mobile AMD Athlon(tm) XP 1400+ (AuthenticAMD 686-class, 256KB L2 cache) 1.20 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE cpu0: AMD Powernow: FID VID TTP real mem = 133734400 (130600K) avail mem = 115277824 (112576K) using 1658 buffers containing 6791168 bytes (6632K) of memory User Kernel Config UKC disable auvia 70 auvia* disabled UKC quit Continuing... mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 04/29/02, BIOS32 rev. 0 @ 0xfd6a0 apm0 at bios0: Power Management spec V1.2 apm0: AC on, no battery apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xfd6a0/0x960 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf60/128 (6 entries) pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C596A ISA rev 0x00) pcibios0: PCI bus #3 is the last bus bios0: ROM list: 0xc/0x1 0xd/0x4000! 0xdc000/0x4000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT8363 Host rev 0x03 ppb0 at pci0 dev 1 function 0 VIA VT8363 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Mobility 1 rev 0x64 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C686 ISA rev 0x40 pciide0 at pci0 dev 7 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: HITACHI_DK23DA-30 wd0: 16-sector PIO, LBA, 28615MB, 58605120 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, UJDA720 DVD/CDRW, 1.00 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x1a: irq 9 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 7 function 3 VIA VT83C572 USB rev 0x1a: irq 9 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 7 function 4 VIA VT82C686 SMBus rev 0x40 VIA VT82C686 AC97 rev 0x50 at pci0 dev 7 function 5 not configured VIA VT82C686 Modem rev 0x30 at pci0 dev 7 function 6 not configured cbb0 at pci0 dev 10 function 0 Texas Instruments PCI1420 CardBus rev 0x00: irq 9 cbb1 at pci0 dev 10 function 1 Texas Instruments PCI1420 CardBus rev 0x00: irq 10 Texas Instruments TSB12LV26 FireWire rev 0x00 at pci0 dev 14 function 0 not configured rl0 at pci0 dev 16 function 0 Realtek 8139 rev 0x10: irq 10 address 08:00:46:6d:f1:10 rlphy0 at rl0 phy 0: RTL internal phy 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 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 sb0 at isa0 port 0x220/24 irq 5 drq 1: dsp v3.02 midi0 at sb0: SB MIDI UART audio0 at sb0 opl0 at sb0: model OPL3 midi1 at opl0: SB Yamaha OPL3 pcppi0 at isa0 port 0x61 midi2 at pcppi0: PC speaker spkr0 at pcppi0 sysbeep0 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 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec cardslot0 at cbb0 slot 0 flags 0 cardbus0 at
Re: auvia UKC parameters on SONY VAIO PCG-FX77Z_BP(J)
On Fri, Nov 25, 2005 at 06:20:28PM +0900, Vladas Urbonas wrote:
Hi All,
Excuse me for disturbing too much if so.
Have to 'disable auvia' in UKC to boot up 3.8 GENERIC on my SONY VAIO
PCG-FX77Z_BP(J). The same keeps on happening from 3.1 so -current
problably will not help.
I would be grateful if anyone of you would be so kind to give me basic
directions
on how to know which devices, functions and flags to use in UKC according to
dmesg from FreeBSD, FreeSBIE or Slack where VT82C686A and AC'97 works fine.
I did google and I will go to the Source if needed. Just thought that
it would be
faster to cut to the chase with few lines' assistance.
can you try a -current kernel w/ this diff plz?
cu
--
paranoic mickey (my employers have changed but, the name has remained)
Index: auvia.c
===
RCS file: /cvs/src/sys/dev/pci/auvia.c,v
retrieving revision 1.33
diff -u -r1.33 auvia.c
--- auvia.c 6 May 2005 01:45:22 - 1.33
+++ auvia.c 25 Nov 2005 11:34:12 -
@@ -242,13 +242,25 @@
sc-sc_pc = pc;
sc-sc_pt = pt;
+ /* disable SBPro compat others */
+ pr = pci_conf_read(pc, pt, AUVIA_PCICONF_JUNK);
+
+ pr = ~AUVIA_PCICONF_ENABLES; /* clear compat function enables */
+ /* XXX what to do about MIDI, FM, joystick? */
+
+ pr |= (AUVIA_PCICONF_ACLINKENAB | AUVIA_PCICONF_ACNOTRST |
+ AUVIA_PCICONF_ACVSR | AUVIA_PCICONF_ACSGD);
+
+ pr = ~(AUVIA_PCICONF_ACFM | AUVIA_PCICONF_ACSB);
+
+ pci_conf_write(pc, pt, AUVIA_PCICONF_JUNK, pr);
+
if (pci_intr_map(pa, ih)) {
printf(: couldn't map interrupt\n);
bus_space_unmap(sc-sc_iot, sc-sc_ioh, iosize);
return;
}
intrstr = pci_intr_string(pc, ih);
-
sc-sc_ih = pci_intr_establish(pc, ih, IPL_AUDIO, auvia_intr, sc,
sc-sc_dev.dv_xname);
if (sc-sc_ih == NULL) {
@@ -261,19 +273,6 @@
}
printf(: %s\n, intrstr);
-
- /* disable SBPro compat others */
- pr = pci_conf_read(pc, pt, AUVIA_PCICONF_JUNK);
-
- pr = ~AUVIA_PCICONF_ENABLES; /* clear compat function enables */
- /* XXX what to do about MIDI, FM, joystick? */
-
- pr |= (AUVIA_PCICONF_ACLINKENAB | AUVIA_PCICONF_ACNOTRST |
- AUVIA_PCICONF_ACVSR | AUVIA_PCICONF_ACSGD);
-
- pr = ~(AUVIA_PCICONF_ACFM | AUVIA_PCICONF_ACSB);
-
- pci_conf_write(pc, pt, AUVIA_PCICONF_JUNK, pr);
sc-host_if.arg = sc;
sc-host_if.attach = auvia_attach_codec;
unable to use a read-only root with 3.8
Hello list, I'm in a situation where I must configure a couple of soekris boxes (net4801) with very minimal services (pf and syslogd sending all logs to a remote server), they will be unattended and various thousands of kilometers away. Also the system is probable to suffer electrical failures and since OBSD is contained in a CF card I become very interested in running it over an unique read-only partition. The first option was add the ro flag to the fstab file, but it's ignored and the system leaves the root fs in rw mode. The second (and desesperate) option was add mount -o ro / to /etc/rc.local which seems cause a kernel panic (no suprise here) is it possible to have a root fs in read-only mode with OBSD? POST: 0123456789bcefghipajklnopq,,,tvwxy[2J comBIOS ver. 1.28 20050529 Copyright (C) 2000-2005 Soekris Engineering. net4801 CPU Geode 266 Mhz Mbyte Memory0128 Pri Mas SanDisk SDCFB-256 LBA 980-16-32 251 Mbyte Slot Vend Dev ClassRev Cmd Stat CL LT HT Base1Base2 Int --- 0:00:0 1078 0001 0600 0107 0280 00 00 00 0:06:0 100B 0020 0200 0107 0290 00 3F 00 E101 A000 10 0:07:0 100B 0020 0200 0107 0290 00 3F 00 E201 A0001000 10 0:08:0 100B 0020 0200 0107 0290 00 3F 00 E301 A0002000 10 0:18:2 100B 0502 01018001 0005 0280 00 00 00 0:19:0 0E11 A0F8 0C031008 0117 0280 08 38 00 A0003000 11 Seconds to automatic boot. Press Ctrl-P for entering Monitor. 5 4 3 2 1 Using drive 0, partition 3. Loading... probing: pc0 com0 com1 pci mem[639K 127M a20=on] disk: hd0+ OpenBSD/i386 BOOT 2.10 |/-\|/- com0: 19200 baud switching console to com0 OpenBSD/i386 BOOT 2.10 boot booting hd0a:/bsd: ...snip... entry point at 0x100120 [ using 476508 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2005 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 3.8 (GENERIC) #138: Sat Sep 10 15:41:37 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Geode(TM) Integrated Processor by National Semi (Geode by NSC 586-class) 267 MHz cpu0: FPU,TSC,MSR,CX8,CMOV,MMX cpu0: TSC disabled real mem = 133799936 (130664K) avail mem = 115474432 (112768K) using 1658 buffers containing 6791168 bytes (6632K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 20/50/29, BIOS32 rev. 0 @ 0xf7840 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/0x9000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Cyrix GXm PCI rev 0x00 sis0 at pci0 dev 6 function 0 NS DP83815 10/100 rev 0x00: DP83816A, irq 10, address 00:00:24:c4:ff:1c nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1 sis1 at pci0 dev 7 function 0 NS DP83815 10/100 rev 0x00: DP83816A, irq 10, address 00:00:24:c4:ff:1d nsphyter1 at sis1 phy 0: DP83815 10/100 PHY, rev. 1 sis2 at pci0 dev 8 function 0 NS DP83815 10/100 rev 0x00: DP83816A, irq 10, address 00:00:24:c4:ff:1e nsphyter2 at sis2 phy 0: DP83815 10/100 PHY, rev. 1 gscpcib0 at pci0 dev 18 function 0 NS SC1100 ISA rev 0x00 gpio0 at gscpcib0: 64 pins NS SC1100 SMI/ACPI rev 0x00 at pci0 dev 18 function 1 not configured pciide0 at pci0 dev 18 function 2 NS SCx200 IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SanDisk SDCFB-256 wd0: 1-sector PIO, LBA, 245MB, 501760 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 geodesc0 at pci0 dev 18 function 5 NS SC1100 X-Bus rev 0x00: iid 6 revision 3 wdstatus 0 ohci0 at pci0 dev 19 function 0 Compaq USB OpenHost rev 0x08: irq 11, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Compaq OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered isa0 at gscpcib0 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 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 sysbeep0 at pcppi0 nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS gpio1 at nsclpcsio0: 29 pins gscsio0 at isa0 port 0x15c/2: SC1100 SIO rev 1: npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo biomask fbe5 netmask ffe5 ttymask ffe7 pctr: no performance counters in CPU dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 Automatic boot in progress: starting file system checks. /dev/rwd0a: file system is clean; not
Re: auvia UKC parameters on SONY VAIO PCG-FX77Z_BP(J)
On 11/25/05, mickey [EMAIL PROTECTED] wrote:
On Fri, Nov 25, 2005 at 06:20:28PM +0900, Vladas Urbonas wrote:
Hi All,
Excuse me for disturbing too much if so.
Have to 'disable auvia' in UKC to boot up 3.8 GENERIC on my SONY VAIO
PCG-FX77Z_BP(J). The same keeps on happening from 3.1 so -current
problably will not help.
I would be grateful if anyone of you would be so kind to give me basic
directions
on how to know which devices, functions and flags to use in UKC according to
dmesg from FreeBSD, FreeSBIE or Slack where VT82C686A and AC'97 works fine.
I did google and I will go to the Source if needed. Just thought that
it would be
faster to cut to the chase with few lines' assistance.
Wow, thank You all for replies!
can you try a -current kernel w/ this diff plz?
Yes, sure I can.
I will try both (this and also the previous diff send by Mr. David
Coppa ) of them one by one and will give as detailed feedback as I
will manage.
This will take some time.
cu
--
paranoic mickey (my employers have changed but, the name has
remained)
Index: auvia.c
===
RCS file: /cvs/src/sys/dev/pci/auvia.c,v
retrieving revision 1.33
diff -u -r1.33 auvia.c
--- auvia.c 6 May 2005 01:45:22 - 1.33
+++ auvia.c 25 Nov 2005 11:34:12 -
@@ -242,13 +242,25 @@
sc-sc_pc = pc;
sc-sc_pt = pt;
+ /* disable SBPro compat others */
+ pr = pci_conf_read(pc, pt, AUVIA_PCICONF_JUNK);
+
+ pr = ~AUVIA_PCICONF_ENABLES; /* clear compat function enables */
+ /* XXX what to do about MIDI, FM, joystick? */
+
+ pr |= (AUVIA_PCICONF_ACLINKENAB | AUVIA_PCICONF_ACNOTRST |
+ AUVIA_PCICONF_ACVSR | AUVIA_PCICONF_ACSGD);
+
+ pr = ~(AUVIA_PCICONF_ACFM | AUVIA_PCICONF_ACSB);
+
+ pci_conf_write(pc, pt, AUVIA_PCICONF_JUNK, pr);
+
if (pci_intr_map(pa, ih)) {
printf(: couldn't map interrupt\n);
bus_space_unmap(sc-sc_iot, sc-sc_ioh, iosize);
return;
}
intrstr = pci_intr_string(pc, ih);
-
sc-sc_ih = pci_intr_establish(pc, ih, IPL_AUDIO, auvia_intr, sc,
sc-sc_dev.dv_xname);
if (sc-sc_ih == NULL) {
@@ -261,19 +273,6 @@
}
printf(: %s\n, intrstr);
-
- /* disable SBPro compat others */
- pr = pci_conf_read(pc, pt, AUVIA_PCICONF_JUNK);
-
- pr = ~AUVIA_PCICONF_ENABLES; /* clear compat function enables */
- /* XXX what to do about MIDI, FM, joystick? */
-
- pr |= (AUVIA_PCICONF_ACLINKENAB | AUVIA_PCICONF_ACNOTRST |
- AUVIA_PCICONF_ACVSR | AUVIA_PCICONF_ACSGD);
-
- pr = ~(AUVIA_PCICONF_ACFM | AUVIA_PCICONF_ACSB);
-
- pci_conf_write(pc, pt, AUVIA_PCICONF_JUNK, pr);
sc-host_if.arg = sc;
sc-host_if.attach = auvia_attach_codec;
Re: auvia UKC parameters on SONY VAIO PCG-FX77Z_BP(J)
On Fri, Nov 25, 2005 at 08:45:30PM +0900, Vladas Urbonas wrote:
On 11/25/05, mickey [EMAIL PROTECTED] wrote:
On Fri, Nov 25, 2005 at 06:20:28PM +0900, Vladas Urbonas wrote:
Hi All,
Excuse me for disturbing too much if so.
Have to 'disable auvia' in UKC to boot up 3.8 GENERIC on my SONY VAIO
PCG-FX77Z_BP(J). The same keeps on happening from 3.1 so -current
problably will not help.
I would be grateful if anyone of you would be so kind to give me basic
directions
on how to know which devices, functions and flags to use in UKC according
to
dmesg from FreeBSD, FreeSBIE or Slack where VT82C686A and AC'97 works
fine.
I did google and I will go to the Source if needed. Just thought that
it would be
faster to cut to the chase with few lines' assistance.
Wow, thank You all for replies!
can you try a -current kernel w/ this diff plz?
Yes, sure I can.
I will try both (this and also the previous diff send by Mr. David
Coppa ) of them one by one and will give as detailed feedback as I
will manage.
well there is no way that hack gets committed so plz do not waste
your machine room time :(
Index: auvia.c
===
RCS file: /cvs/src/sys/dev/pci/auvia.c,v
retrieving revision 1.33
diff -u -r1.33 auvia.c
--- auvia.c 6 May 2005 01:45:22 - 1.33
+++ auvia.c 25 Nov 2005 11:34:12 -
@@ -242,13 +242,25 @@
sc-sc_pc = pc;
sc-sc_pt = pt;
+ /* disable SBPro compat others */
+ pr = pci_conf_read(pc, pt, AUVIA_PCICONF_JUNK);
+
+ pr = ~AUVIA_PCICONF_ENABLES; /* clear compat function enables */
+ /* XXX what to do about MIDI, FM, joystick? */
+
+ pr |= (AUVIA_PCICONF_ACLINKENAB | AUVIA_PCICONF_ACNOTRST |
+ AUVIA_PCICONF_ACVSR | AUVIA_PCICONF_ACSGD);
+
+ pr = ~(AUVIA_PCICONF_ACFM | AUVIA_PCICONF_ACSB);
+
+ pci_conf_write(pc, pt, AUVIA_PCICONF_JUNK, pr);
+
if (pci_intr_map(pa, ih)) {
printf(: couldn't map interrupt\n);
bus_space_unmap(sc-sc_iot, sc-sc_ioh, iosize);
return;
}
intrstr = pci_intr_string(pc, ih);
-
sc-sc_ih = pci_intr_establish(pc, ih, IPL_AUDIO, auvia_intr, sc,
sc-sc_dev.dv_xname);
if (sc-sc_ih == NULL) {
@@ -261,19 +273,6 @@
}
printf(: %s\n, intrstr);
-
- /* disable SBPro compat others */
- pr = pci_conf_read(pc, pt, AUVIA_PCICONF_JUNK);
-
- pr = ~AUVIA_PCICONF_ENABLES; /* clear compat function enables */
- /* XXX what to do about MIDI, FM, joystick? */
-
- pr |= (AUVIA_PCICONF_ACLINKENAB | AUVIA_PCICONF_ACNOTRST |
- AUVIA_PCICONF_ACVSR | AUVIA_PCICONF_ACSGD);
-
- pr = ~(AUVIA_PCICONF_ACFM | AUVIA_PCICONF_ACSB);
-
- pci_conf_write(pc, pt, AUVIA_PCICONF_JUNK, pr);
sc-host_if.arg = sc;
sc-host_if.attach = auvia_attach_codec;
--
paranoic mickey (my employers have changed but, the name has remained)
Re: CCD Mirroring HOWTO
On Thu, Nov 24, 2005 at 05:14:16PM +0100, Robbert Haarman wrote: For those who are interested, I've uploaded a tutorial on setting up mirroring using ccd(4) to http://inglorion.net/documents/tutorials/ccd/. labeling section is wrong. one MUST never use 'c' partition. one MUST always make an 'a' (for example) to skip first cylinder (at least). please make it into a real faq entry. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: auvia UKC parameters on SONY VAIO PCG-FX77Z_BP(J)
On 11/25/05, mickey [EMAIL PROTECTED] wrote: well there is no way that hack gets committed so plz do not waste your machine room time :( I can live with that. Should i report you the result or not (I will try it on pcg-fx55j_b(j) and pcg-fx77z_bp(j) )?
Re: auvia UKC parameters on SONY VAIO PCG-FX77Z_BP(J)
On Fri, Nov 25, 2005 at 09:02:55PM +0900, Vladas Urbonas wrote: On 11/25/05, mickey [EMAIL PROTECTED] wrote: well there is no way that hack gets committed so plz do not waste your machine room time :( I can live with that. but it would be much better if it gets fixed for everybody right? Should i report you the result or not (I will try it on pcg-fx55j_b(j) and pcg-fx77z_bp(j) )? well yes (: if it boots fine we can commit it then. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: hw.setperf strangeness
On 11/23/05, Lars Hansson [EMAIL PROTECTED] wrote: This seems a bit strange to ne: $ sysctl hw | tail -2 hw.cpuspeed=1296 hw.setperf=100 $ sudo sysctl -w hw.setperf=0 hw.setperf: 100 - 0 $ sysctl hw | tail -2 hw.cpuspeed=1296 hw.setperf=0 Hmm..shouldnt cpuspeed have changed? maybe, speedstep can only be set to fast and slow, and the driver won't move things if it thinks nothing is changing. maybe there's a bug, maybe you need to fiddle it up and down some to make it actually work, but 0 and 100 are the only settings that really mean anything.
Re: unable to use a read-only root with 3.8
On 11/25/05, Josi M. Fandiqo [EMAIL PROTECTED] wrote: is it possible to have a root fs in read-only mode with OBSD? of course it is. there should be numerous postings regarding OpenBSD and CF cards, especially (but not limited to) running on Soekris boxes. Sometimes there is also flashdist mentioned: http://www.nmedia.net/~chris/soekris/ which also turns up on a google search for openbsd soekris as second hit. look at the flashdist script and you'll find a very good implementation of a ro /. but you don't need to go that far. there are recent postings mentioning that it won't be neccessary to have a ro / on a modern CF card. --knitti
Re: auvia UKC parameters on SONY VAIO PCG-FX77Z_BP(J)
Try the mickey@ one, first. It's a real diff and not just a ugly workaround. On 11/25/05, Vladas Urbonas [EMAIL PROTECTED] wrote: On 11/25/05, mickey [EMAIL PROTECTED] wrote: well there is no way that hack gets committed so plz do not waste your machine room time :( I can live with that. Should i report you the result or not (I will try it on pcg-fx55j_b(j) and pcg-fx77z_bp(j) )?
Re: Marvell Yukon-2 / Syskonnect SK-9S22
Adam wrote: Hello, I'm in need of some help getting an syskonnect SK-9S22 (dual port gigabit ethernet) to work. .. Any ideas?? Yukon-2 is completely different from previous one, linux sources exist, no open source for BSDs. zd
Re: unable to use a read-only root with 3.8
--On 25 November 2005 12:36 +0100, JosC) M. FandiC1o wrote: The first option was add the ro flag to the fstab file, but it's ignored and the system leaves the root fs in rw mode. The second (and desesperate) option was add mount -o ro / to /etc/rc.local which seems cause a kernel panic (no suprise here) You're missing the -u parameter to mount. But, don't worry about that, because if you look in /etc/rc you'll see this line: mount -uw / # root on nfs requires this, others aren't hurt try removing it. --On 25 November 2005 13:10 +0100, knitti wrote: there are recent postings mentioning that it won't be neccessary to have a ro / on a modern CF card. from CF longevity point of view, that's correct. but mounting RO will mean the filesystem will be clean after a power failure. given the multi-thousand-Km journey to a remote site which is known to have intermittent power, this is well worth doing.
Re: 3.8: ath(4) card not working in 11a/g mode? (fwd)
Hi, Additional information as requested by private email: I am using two Mini-PCI cards from the manufacturer: Wistron Neweb Corporation Model No: CM9 Anyone got those cards working in 11ag mode in OpenBSD? Maybe does anyone have an alternative 11abg card or ath manufacturer to suggest? I really aim at using the turbo mode of the ath cards so I would prefer to use those... Thanks for the help, Robert * Robert Stepanek ([EMAIL PROTECTED]) wrote: Hi, I have two cards using the atheros chipset. However, setting up one as access point and the other as client only yields a connection when I enforce 11b mode on both cards. I am using a 3.8 GENERIC kernel (dated 27 Oct): OpenBSD 3.8 (GENERIC) #1: Thu Oct 27 18:22:38 CEST 2005 It detects the ath card on both machines: ath0 at pci0 dev 14 function 0 Atheros AR5212 rev 0x01: irq 11 ath0: AR5212 5.9 phy 4.3 rf5112 3.6, FCC1A, address 00:0b:6b:36:fd:a6 ath0 at pci0 dev 14 function 0 Atheros AR5212 rev 0x01: irq 11 ath0: AR5212 5.9 phy 4.3 rf5112 3.6, FCC1A, address 00:0b:6b:36:fe:43 I then clear the ath card settings as indicated in the man page: ifconfig ath0 -bssid -chan media autoselect nwid -nwkey -powersave down I set up the hostap with: ifconfig ath0 10.4.0.1 netmask 0xff00 media autoselect mode 11a mediaopt hostap nwid foo nwkey bar up ifconfig shows that the hostap is running: ath0: flags=8863UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0b:6b:36:fd:a6 media: IEEE802.11 autoselect mode 11a hostap status: active ieee80211: nwid foo chan 36 bssid 00:0b:6b:36:fd:a6 nwkey bar inet6 fe80::20b:6bff:fe36:fda6%ath0 prefixlen 64 scopeid 0x2 inet 10.4.0.1 netmask 0xff00 broadcast 10.255.255.255 I start the client with: ifconfig ath0 10.4.0.2 netmask 0xff00 media autoselect mode 11a nwid foo nwkey bar up but it does not find any network (I let it wait awhile to do some scanning): ath0: flags=8863UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0b:6b:36:fe:43 media: IEEE802.11 autoselect mode 11a (OFDM6 mode 11a) status: no network ieee80211: nwid foo nwkey bar inet6 fe80::20b:6bff:fe36:fe43%ath0 prefixlen 64 scopeid 0x2 inet 10.4.0.2 netmask 0xff00 broadcast 10.255.255.255 Same story with enforced mode 11g However setting mode 11b in the same command line as above immediately yields a connection on the client: ath0: flags=8863UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0b:6b:36:fe:43 media: IEEE802.11 autoselect mode 11b (DS11 mode 11b) status: active ieee80211: nwid foo chan 1 bssid 00:0b:6b:36:fd:a6 nwkey bar inet6 fe80::20b:6bff:fe36:fe43%ath0 prefixlen 64 scopeid 0x2 inet 10.4.0.2 netmask 0xff00 broadcast 10.255.255.255 Not setting any mode at all starts the hostap in 11a mode and the client is not able to connect as well. Note: The boxes are standing right next to each other. I tried it in several buildings so I do not think that this might be due to interference. I wonder if this is a driver issue? Or could it be a problem with the hardware? Thanks a lot, Robert
Re: Marvell Yukon-2 / Syskonnect SK-9S22
Original message from Adam at 25-11-2005 8:59 I'm in need of some help getting an syskonnect SK-9S22 (dual port gigabit ethernet) to work. I'm currently running on the i386 platform with openbsd 3.8-current as of 11/25/05. I believe this is the most relevant part of the dmesg: skc0 at pci1 dev 3 function 0 Schneider Koch SK-9Sxx rev 0x12: irq 5 skc0: Marvell Yukon-2 XL (0x1) sk port A at skc0 not configured sk port B at skc0 not configured For whatever reason the mac addresses for the ports are not getting reported so sk0 sk1 aren't getting setup. Any ideas?? Adam, Take a look at this thread http://marc.theaimsgroup.com/?l=openbsd-miscm=113217946625538w=2 I got a few SK-9S22 cards in the summer and helped Brad@ get some SysKonnect cards. For now they are not supported in OpenBSD. As far as I've been able to determine there is currently no good dual or quad port gigabit card on the market that works with OpenBSD. Some revisions of the Intel gigabit cards work but others don't. Daniel
Re: Enable Solaris Compatibility Mode in version 3.8
On 11/23/05, Simon Morgan [EMAIL PROTECTED] wrote: Tom Pfeifer tpfeifer at tela.com writes: I'd like to know how to enable Solaris Compatibility Mode in version 3.8. I've searched the FAQ's and all man pages and don't seem to be able to find the correct information. $ man 8 compat_sunos I assume that's what you want. compat_svr4 too.
Re: CCD Mirroring HOWTO
http://inglorion.net/documents/tutorials/ccd/. labeling section is wrong. one MUST never use 'c' partition. one MUST always make an 'a' (for example) to skip first cylinder (at least). That's true for real disks, but it doesn't seem to be true for ccd devices. If it were true, ccdconfig shouldn't be setting the c partition to type 4.2BSD, either. I use the c partition created by ccdconfig on one of my ccd devices, and, so far, it works without problems. From what information I have been able to gather from the web, it works for others, too. I will add a warning, but I don't think my labeling section is _wrong_. Of course, if somebody who actually knew the implementation details about ccd could weigh in, that would resolve the issue. Anyway, thanks for your comment. Bob --- In one of the Bard's best-thought-of tragedies, our insistent hero, Hamlet, queries on two fronts about how life turns rotten.
Re: CCD Mirroring HOWTO
On Fri, Nov 25, 2005 at 02:14:35PM +0100, Robbert Haarman wrote: http://inglorion.net/documents/tutorials/ccd/. labeling section is wrong. one MUST never use 'c' partition. one MUST always make an 'a' (for example) to skip first cylinder (at least). That's true for real disks, but it doesn't seem to be true for ccd devices. If it were true, ccdconfig shouldn't be setting the c partition to type 4.2BSD, either. I use the c partition created by ccdconfig on one of my ccd devices, and, so far, it works without problems. From what information I have been able to gather from the web, it works for others, too. I will add a warning, but I don't think my labeling section is _wrong_. Of course, if somebody who actually knew the implementation details about ccd could weigh in, that would resolve the issue. it is wrong. by using 'c' partition one may endup trashing real disk's label. DO NOT USE 'c' PARTITION. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: CCD Mirroring HOWTO
Of course, if somebody who actually knew the implementation details about ccd could weigh in, that would resolve the issue. they just did. http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/ccd.c Ok, thanks for pointing that out. I apologize for my uninformed comments, especially to mickey. -- Bob --- Coal powered the first steam engines, whose killer app was pumping stagnant water out of coal mines. It powered the railroads, whose killer app was moving coal. -- Bruce Sterling
Re: CCD Mirroring HOWTO
On Fri, Nov 25, 2005 at 02:26:08PM +0100, mickey wrote: On Fri, Nov 25, 2005 at 02:14:35PM +0100, Robbert Haarman wrote: by using 'c' partition one may endup trashing real disk's label. DO NOT USE 'c' PARTITION. Ok, I'll change the HOWTO and add a FAQ entry ASAP. Apologies for not believing you earlier; there's posts on the web that claim one way and posts that claim the opposite, I just went by my own experience. This still leaves the issue of ccdconfig setting up the c partition as type 4.2BSD. If this can thrash the disklabel, that sounds like a serious bug. Is that going to be fixed? -- Bob --- The chief cause of problems is solutions. -- Eric Sevareid
Re: unable to use a read-only root with 3.8
Also the system is probable to suffer electrical failures and since OBSD is contained in a CF card I become very interested in running it over an unique read-only partition. The first option was add the ro flag to the fstab file, but it's ignored and the system leaves the root fs in rw mode. The second (and desesperate) option was add mount -o ro / to /etc/rc.local which seems cause a kernel panic (no suprise here) is it possible to have a root fs in read-only mode with OBSD? I think I found a valid solution. OBSD is installed in the soekris box by means of PEX/DHCP/TFTP, so no problems with geometry mismatches as with the flashdist approach. Next copy /dev/MAKEDEV to /root (or whatever place that you like) and modidy /etc/rc around the line 200 (after the mount -a command group) ... mount_mfs -s 1 swap /dev mount_mfs -s 1000 swap /tmp mount_mfs -s 1000 swap /var/log mount_mfs -s 1000 swap /var/run # add mfs mountpoints for other critical directories. cd /dev ; /root/MAKEDEV ramdisk wscons pty pf tun mount -o ro / ... ramdisk, wscons and pty seems to be minimal devices to get basic funcionality. pf permits run pf and tun permits openvpn to work. Regards -- GCS/IT d- s+:+() a31 C+++ UBL+++$ P+ L+++ E--- W++ N+ o++ K- w--- O+ M+ V- PS+ PE+ Y++ PGP t+ 5 X+$ R- tv-- b+++ DI D+ G++ e- h+(++) !r !z --END GEEK CODE BLOCK--
Re: CCD Mirroring HOWTO
On Fri, Nov 25, 2005 at 02:41:47PM +0100, Robbert Haarman wrote: On Fri, Nov 25, 2005 at 02:26:08PM +0100, mickey wrote: On Fri, Nov 25, 2005 at 02:14:35PM +0100, Robbert Haarman wrote: by using 'c' partition one may endup trashing real disk's label. DO NOT USE 'c' PARTITION. Ok, I'll change the HOWTO and add a FAQ entry ASAP. Apologies for not believing you earlier; there's posts on the web that claim one way and posts that claim the opposite, I just went by my own experience. This still leaves the issue of ccdconfig setting up the c partition as type 4.2BSD. If this can thrash the disklabel, that sounds like a serious bug. Is that going to be fixed? of course oif you make a it use 'c' it will reset the type. so do not use it (: please make your writing into real openbsd faq entry. i bet _then_ people will actually pay attention to it in the future (: cu -- paranoic mickey (my employers have changed but, the name has remained)
CARP on vlan(4)
I'm getting the following error when I try to create a carp(4) interface on top of a vlan(4) interface: # ifconfig vlan0 vlan 1 vlandev fxp0 # ifconfig carp0 inet 10.0.0.1 netmask 255.255.255.0 vhid 1 carpdev vlan0 ifconfig: SIOCAIFADDR: Can't assign requested address This feature is supported in 3.8, according to reports in the archive and plus38.html. This system was just installed from the 3.8 CDs. Can anyone tell me what I'm missing? # uname -a OpenBSD server1.dixongroup.net 3.8 GENERIC#138 i386 # ifconfig -A lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33224 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 fxp0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 lladdr 00:d0:b7:bf:c6:95 media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::2d0:b7ff:febf:c695%fxp0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0x0 fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:02:b3:0a:d1:28 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.0.21 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80::202:b3ff:fe0a:d128%fxp1 prefixlen 64 scopeid 0x2 inet 192.168.0.121 netmask 0xff00 broadcast 192.168.0.255 inet 192.168.0.122 netmask 0xff00 broadcast 192.168.0.255 xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:c0:4f:46:8d:ec media: Ethernet autoselect (none) status: no carrier inet 10.255.255.21 netmask 0xff00 broadcast 10.255.255.255 inet6 fe80::2c0:4fff:fe46:8dec%xl0 prefixlen 64 scopeid 0x3 pflog0: flags=0 mtu 33224 pfsync0: flags=0 mtu 1348 enc0: flags=0 mtu 1536 vlan0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 lladdr 00:d0:b7:bf:c6:95 vlan: 1 parent interface: fxp0 groups: vlan inet6 fe80::2d0:b7ff:febf:c695%vlan0 prefixlen 64 scopeid 0x15 carp0: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST mtu 1500 carp: INIT carpdev vlan0 vhid 1 advbase 1 advskew 0 groups: carp Thanks, -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net
Re: Multiple Internet connections with CARP
On Fri, Nov 25, 2005 at 09:13:36AM +0100, Bo Rising Rasmussen wrote: Hi all, I have searched a bit now, and have not seen anything on this subject. I have 2 different internet connections, which I would like to use for my CARP setup. I was thinking that they would connect to a switch, and from there 2 lines going to each firewall, and then make some CARP setup for those two lines. Anyone knows if this could be done? Regards, Bo Yes, but the switch would still be a single point of failure. Joachim
Re: usb2ether hw recommendation
Stephan A. Rickauer wrote: Hello, Stephan A. Rickauer wrote: ugen0 at uhub4 port 1 ugen0: ASIX Electronics AX88178, rev 2.00/0.01, addr 2 I guess I _was_ unlucky. It's a Level one usb-0200. Seems I was to quick. axe(4) should be the right one ... I'll try. I am stuck now. All I could find out was that I have this device connected at hub4, which theoretically is supported by the axe driver: Since the LevelOne thing is not supported (yet) I thought I give it another try, went to the next electronics store and picked the first usb2ether device I could find. Plugging it in it says: axe0 at uhub4 port 1 configuration 1 interface 0 axe0: Linksys USB 2.0 10/100 ethernet controller, rev 2.00/0.01, addr 2, address 00:10:60:85:4a:d4 Strike. For those coming from Switzerland/Germany - it's the Linksys USB200M-DE from Media Markt ... -- Stephan A. Rickauer Institut f|r Neuroinformatik Universitdt / ETH Z|rich Winterthurerstriasse 190 CH-8057 Z|rich Tel: +41 44 635 30 50 Sek: +41 44 635 30 52 Fax: +41 44 635 30 53 http://www.ini.ethz.ch
Re: CCD Mirroring HOWTO
On Fri, Nov 25, 2005 at 04:02:03PM +0100, Robbert Haarman wrote: On Fri, Nov 25, 2005 at 03:03:22PM +0100, mickey wrote: On Fri, Nov 25, 2005 at 02:57:22PM +0100, Robbert Haarman wrote: I'm not sure what you mean here. What I meant is that ccdconfig will automatically create a disklabel with partition c set to type 4.2BSD when you run it the first time. This has bugged many people who were trying to create their own partitions, as disklabel will not let you create any partitions when the type of partition c is set to anything other than unused. before you run ccdconfig you create (say) 'a' partition and then ccdconfig ccd0 16 0 sd0a sd1a sd2a ... Before you run ccdconfig, the device doesn't exist. How do you create an a partition in that case? default 'c' type is unused. at least on default systems... and your 'c' stays as 'unused' just fine. can you see now how much you shoot yourself in the foot by using 'c' ? No, frankly I really don't see it. If I look at my partition tables, I see the following: 1. On my physical disks, there is a DOS/BIOS partition table, which has to be in the first sector (MBR). This is why no partitions can start there, and partitions start after the first cylinder (typically, this means they start at sector 63). 2. The OpenBSD slices of my disks start at sector 24659775. This is also where the a partition of these disks start. It isn't that way because I made it that way, it was set up that way by the initial label editor when I did the installation. some pplz use 'c' for their ccd components -- WRONG! 3. From 2, I conclude that wherever the BSD disklabel is stored, this does not affect where my partitions can be. The disklabel could be stored in my root partition, for all I know. disklabel is the sector #1 of the fdisk partition 4. I have a ccd device starting at sector 41110398, with a size of 32901057 sectors. Inside the ccd device is a c partition of 32901056 sectors, starting at sector 0, with type 4.2BSD. This isn't because I set it up this way, this is how the device was set up when I first ran disklabel. I never changed anything there. oh uhm must be a bug in disklabel spoofing (: There are a number of possibilities now. One possibility is that the set up I got on my ccd device (a c partition with type 4.2BSD) is severely broken, but somehow works for me and for several other people on the net. This seems to be what you are suggesting. Another possibility is that the disklabel is indeed stored somewhere inside a partition, in which case the setup I have should be completely fine. Yet another possibility is that the disklabel is stored in the single missing sector on the ccd device (note that the size of the c partition is one smaller than the size of the ccd device). In this case, also, the setup should be completely fine. Perhaps there are other possibilities, too. Whichever the case is, the setup is either completely fine, or it is not. If it is, then there is little to worry about. If it isn't, then _some_ tool I used in setting up this configuration is wrong, because _I_ didn't set up the c partition on the ccd device that way. I didn't even know it was possible to set a c partition to anything besides unused. I assumed, as others did, that the fact that ccdconfig sets things up this way means that you can use the c partition for storing files on. You just told me this is not true, and it can in fact thrash the disklabel on your real disk. Therefore, it seems to me that ccdconfig setting the type of partition c to 4.2BSD is wrong. So I was wondering aloud if that is indeed a bug and if it will be fixed. ccdconfig does not choose partitions to use. people do. As I've said time and time before, I wasn't the one who set up the c partition this way. From what I've been able to find on the web, ccdconfig sets up the partition this way for everybody. So it's not just me. I'll say it again: if this setup is wrong, the software (either ccdconfig or some other tool involved in the process) is wrong, because that's what creates the setup. Just search the web if you don't believe me, there are posts of people who tried to create an a partition, but couldn't because the c partition had been set to 4.2BSD. it's not about how the 'c' is setup. you can screw it on normal drive as well. just run a newfs on it! the point is that the ccd part must be started w/ an offset as well! unfortunately people are wrong. that why it's important you make it proper and into real docs... Yes, I fully agree. Unfortunately, nobody who has commented on this, and that includes you and me, seems to know exactly how things work and what's happening. Before we figure out exactly how the facts are, we can't write proper and correct documentation. You mean like an entry in the FAQ on the OpenBSD website? How do I go
Re: CCD Mirroring HOWTO
On Fri, Nov 25, 2005 at 04:50:34PM +0100, mickey wrote: default 'c' type is unused. at least on default systems... On REAL disks, yes. On ccd disks, it seems to be different. Or maybe ccdconfig screws it up. 2. The OpenBSD slices of my disks start at sector 24659775. This is also where the a partition of these disks start. It isn't that way because I made it that way, it was set up that way by the initial label editor when I did the installation. some pplz use 'c' for their ccd components -- WRONG! Pardon my rudeness, but are you sure? It works fine for me. Other people have reported it works fine for them. I don't know any implementation details, but maybe you do: what actually goes wrong when you use the c partition on a ccd device? 3. From 2, I conclude that wherever the BSD disklabel is stored, this does not affect where my partitions can be. The disklabel could be stored in my root partition, for all I know. disklabel is the sector #1 of the fdisk partition The fdisk partition that is the OpenBSD slice? Because my a partition starts at the exact same sector as that slice, and there seem not to be any problems. Again, this is how the system set it up for me, I didn't change the start position of my a partition. Maybe ffs can accomodate disk labels and there isn't any problem? 4. I have a ccd device starting at sector 41110398, with a size of 32901057 sectors. Inside the ccd device is a c partition of 32901056 sectors, starting at sector 0, with type 4.2BSD. This isn't because I set it up this way, this is how the device was set up when I first ran disklabel. I never changed anything there. oh uhm must be a bug in disklabel spoofing (: You mean that it's actually unused, but some spoofing code reports it to disklabel as 4.2BSD? I don't think so. If you change the type from 4.2BSD to unused, you can partition as normal. Make your a partition, and all that. And disklabel will report it as unused afterwards. By all appearances, it looks like it _really_ does get set to 4.2BSD. it's not about how the 'c' is setup. you can screw it on normal drive as well. just run a newfs on it! I see how you can screw it up on a real drive, especially one that has fdisk partitions. Can't have an fdisk partition and an ffs filesystem in the same sector. About disklabel, I don't know. What I'm seeing (my a partition starting on the same sector as my OpenBSD slice) suggests that, perhaps, they can coexist. the point is that the ccd part must be started w/ an offset as well! Well, there is that one missing sector. Maybe the ccd driver automatically reserves space for the label? I'm just making wild guesses, trying to explain why it works for me, even though you say it shouldn't. To recap, I would very much like to see the following questions answered beyond all doubt: 1. Is it or is it not wrong to use the 4.2BSD c partition that gets created for you? 2. If it is wrong, why does it get created? So far, there is you answering question 1 with a definite it's wrong, and me answering with an it's not wrong, backed up with the evidence that it works for me without any problems. I hope I'm not being too annoying about this. It's just that I wrote the HOWTO to clarify things and makes sense of the scattered and inconsistent information on ccd and mirroring. I have little desire to incorporate any information in it before I am very sure it is correct. I want to clear up the confusion, not add to it. Cheers, Bob --- The more you learn about Windows, the more you are amazed it works at all -- Pfhreakaz0id on Slashdot [demime 1.01d removed an attachment of type application/pgp-signature]
Re: adjtime and settimeofday
Alexander Hall wrote: From looking through the kernel code, it does not seem that settimeofday(2) resets the action of a previous call to adjtime(2). Would it not be reasonable to assume that to happen? I see four possibilities: 1. It does reset it. I am wrong. And blind. 2. No, it is not reasonable. (Why?) 3. It would be reasonable, but it has not been thought of. 4. It has been thought of, but noone has sent the code to fix it. Can anyone enlighten me in this matter? /Alexander Are there any comments on this? Rickard.
Updated CCD Mirroring HOWTO
Dear list, especially Greg and Mickey, I've updated the working copy of the CCD Mirroring HOWTO. In particular, I've split off the comparison to software RAID into a separate section and clarified that ccd does not do automatic recovery, and I've rewritten the section on labeling to state that the c partition must be set to unused, and normal partitions created instead. Please take a look at http://morgenes.shire.sytes.net/~inglorion/documents/tutorials/ccd/ and let me know what you think about the new wording. Bob --- The only thing you know for sure is that you never know anything for sure.
ISAKMPD / SASYNCD
Hi Folks, Sorry but I need to ask what some will see as an obvious and stupid question, so feel free to shoot me down in flames but please answer the question :-) I have a pair of 3.8 boxes, each with 3 interfaces xl0,xl1 and rl0 configured as a redundant firewall using CARP, PFSYNC and SASYNCD (for my ipsec VPN's configured with isakmpd.conf .policy) Carp0 (Internet) is bound to XL0 on both firewalls, CARP1 (Internal) is bound to XL1 with rl0 being used for PFSYNC and SASYNCD traffic, with me so far? Ok the pair work like a charm, fail over and recovery work, SA SPD's are synced on both boxes, I couldn't be happier. Now for the silly question: I know SASYNCD doesn't do any fail over so by default I have ISAKMPD started on both machines. No looking at the message log on the 'secondary' box I see ISAKMPD logging lots of messages about no response from the remote peer, which sounds right as the VPN's established with the ISAKMPD daemon running on the primary box. Looking at the primary box I get a lot of 'bad cookie' errors which seem to correspond to the secondary's attempts to connect to the remote peer. Although the VPN is running sweetly. Is this right or should I instead use ifstated to monitor the CARP0 interface and start ISAKMPD on the secondary box only when the primary fails? During my testing phase using only OBSD boxes for local and remote peers IPSec fail over worked, now in the 'live' config where the remote peer is a Checkpoint R56 HA pair the primary VPN works but fail over doesn't appear to. Many thanks, asbestos undies at the ready ;-) Simon
Re: HOTO Write bad documentation
On Fri, 25 Nov 2005 11:55:51 -0500, Nick Holland [EMAIL PROTECTED] wrote: people seem to be thrashing around on how to write bad documentation, so here are some tips Thanks Nick! I was wondering which one of the long time folks around here would be the first to blow a fuse over all the OpenBSD HOWTO crap that's been showing up. Kind Regards, JCR
Re: HOTO Write bad documentation
On Fri, Nov 25, 2005 at 06:30:41PM +0059, Han Boetes wrote: 11) Make documentation unnecesarily complicated. Obfusticate it. 12) Treat critique with violence and disdain. 13) Kick down on other peoples efforts rather than encourage them even though they are merely beginners. my all time favourite: 0) never ever bother figuring who actually wrote the stuff you are teaching people to use. when that person shows up (but you cannot identify him obviously) argue to death on your own pointless point of view. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: HOTO Write bad documentation
J.C. Roberts wrote: On Fri, 25 Nov 2005 11:55:51 -0500, Nick Holland [EMAIL PROTECTED] wrote: people seem to be thrashing around on how to write bad documentation, so here are some tips Thanks Nick! I was wondering which one of the long time folks around here would be the first to blow a fuse over all the OpenBSD HOWTO crap that's been showing up. Kind Regards, JCR Oh hell - why stop there?! Rewrite how users ought to post to the list along with hot to top post etc. -- Best regards, Chris When you're not in a hurry, the traffic light will turn green as soon as your vehicle comes to a complete stop.
Re: openvpn to ipsec routing question
Christoph Leser wrote: Hello, the question is about how to route traffic from an openvpn tunnel to an ipsec tunnel. This is my setup: The OpenBSD gateway has an internal (10.0.1.1/24 ) and external (x.x.x.x/30) interface. The internal net is NAT'ed to the external interface to provide internet access to hosts on the internal net. Through the external interface an ipsec SA ( security association ) is established ( tunnel mode ) between my internal net ( 10.0.1/24 ) and another local net of a remote site ( 10.0.2/24 ). So hosts on the internal net can reach hosts on the internet (being NAT'ed ) as well as hosts on the remote private net 10.0.2/24 ( not being NAT'ed ). Now I have setup an openvpn server on this box. This openvpn server gives out addresses from yet another net ( 10.0.3/24 ) to the connected clients. Connections from openvpn clients are NAT'Ed to the internal interface to make them appear as being directly attached to the local private net ( 10.0.1/24 ). So far, it works. Now I want the clients on the openvpn subnet ( 10.0.3/24 ) to get access to the remote side of the ipsec sa ( 10.0.2/24 ). Here is an excerpt of my ipconfig and routing table # ifconfig lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33224 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 fxp0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 address: 00:a0:c9:43:07:20 media: Ethernet autoselect (100baseTX full-duplex) status: active inet 10.0.1.1 netmask 0xff00 broadcast 10.0.1.255 inet6 fe80::2a0:c9ff:fe43:720%fxp0 prefixlen 64 scopeid 0x1 fxp1: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 address: 00:a0:c9:30:b3:34 media: Ethernet autoselect (10baseT) status: active inet x.x.x.254 netmask 0xfffc broadcast x.x.x.255 inet6 fe80::2a0:c9ff:fe30:b334%fxp1 prefixlen 64 scopeid 0x2 pflog0: flags=141UP,RUNNING,PROMISC mtu 33224 pfsync0: flags=0 mtu 2020 enc0: flags=0 mtu 1536 tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1500 inet 10.0.3.1 -- 10.0.3.2 netmask 0x # netstat -rn Routing tables Internet: DestinationGatewayFlags Refs UseMtu Interface defaultx.x.x.254 UGS11 1211734 - fxp1 10.0.3/24 10.0.3.2 UGS 031900 - tun0 10.0.3.2 10.0.3.1 UH 10 - tun0 x.x.x.x/30 link#2 UC 10 - fxp1 127/8 127.0.0.1 UGRS00 33224 lo0 127.0.0.1 127.0.0.1 UH 1 392 33224 lo0 10.0.1/24 link#1 UC 110 - fxp0 224/4 127.0.0.1 URS 00 33224 lo0 Encap: Source Port DestinationPort Proto SA(Address/Proto/Type/Direction) 10.0.2/24 0 10.0.1/24 0 0 y.y.y.y/50/use/in 10.0.1/24 0 10.0.2/24 0 0 y.y.y.y/50/require/out where x.x.x.x is the external address of my box, y.y.y.y is the external address of the remote side of the ipsec tunnel. I expected this to be sufficient for the routing from 10.0.3/24 to 10.0.2/24. But it is not. Using tcpdump I see that packets entering the gateway via the openvpn tun0 interface destined to some host on 10.0.2/24 do not get routed to the ipsec tunnel but are routed directly to the external interface, i.e. a packet with source ip = 10.0.3.10 and destination ip 10.0.2.1 is routed as is to the external interface. I assume that the route through the IPSEC SA is not taken into account, as the packet to be routed is not from the internal interface. If there were a way to source-nat the packet when it comes in via the tun interface, i.e. before the routing is done, maybe all would be fine. But I don't know a way to achieve this. The straight forward solution to setup another ipsec tunnel between 10.0.2/24 and 10.0.3/24 is out of reach due to weird administrative constraints. Any suggestions? Thanks Christoph Try something like... (This was goofy the first time I did it, at least it didn't quite make since to me..) route add -net 10.0.2.0/24 10.0.1.1 This will tell the local OS where to send traffic for the 10.0.2.0/24 network, where as isakmpd only will processes traffic inbound to match an SA. (as far as I can tell). Give it a shot, it should work... -Dave
Re: HOTO Write bad documentation
On Fri, 25 Nov 2005 18:35:17 +0100, mickey [EMAIL PROTECTED] wrote: On Fri, Nov 25, 2005 at 06:30:41PM +0059, Han Boetes wrote: 11) Make documentation unnecesarily complicated. Obfusticate it. 12) Treat critique with violence and disdain. 13) Kick down on other peoples efforts rather than encourage them even though they are merely beginners. my all time favourite: 0) never ever bother figuring who actually wrote the stuff you are teaching people to use. when that person shows up (but you cannot identify him obviously) argue to death on your own pointless point of view. -1) Make certain you are a _CERTIFIED_ professional and make certain you are wearing the proper safety gear before publicly stuffing your foot in your mouth, namely, chocolate shoes and flavored socks. And of course, warn the children not to try this at home... JCR
Re: HOTO Write bad documentation
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nick Holland Sent: Friday, November 25, 2005 11:56 AM To: misc Subject: HOTO Write bad documentation We've been seeing a curious number of people offering various kinds of documentation on various OpenBSD topics. Most of them are somewhere between minimally useful and outright destructive and foolish. I think I've seen precisely one that is looking very promising...and that was sent to me privately, you haven't seen it yet. Obviously, bad documentation is in style now. However, people seem to be thrashing around on how to write bad documentation, so here are some tips based on experience with a number of recent submissions to [EMAIL PROTECTED] Bad hair day Nick?
Re: New idea on CPU fan problem
It's not very clear. May you please elaborate on that. Actually I want to know whether I can replace the kernel (generic kernel of OpenBSD with that of floppy37.fs one) Hugo Villeneuve [EMAIL PROTECTED] wrote: Did you try disabling lm0? (use config for that or the -c boot option) On Thu, Nov 24, 2005 at 11:55:23AM -0800, PARAMVIR DHINDSA wrote: Date : Nov 25, 2005 Dear Sir, I want to know whether I can replace the generic kernel included in the OpenBSD distribution with Kernel included in the bootable(installation) floppy as problem of CPU fan is not present in that (floppy37.fs) case. If yes, please let me know how to perform it. Nov 1,2005 I performed the mentioned steps. I even wrote hw.setperf=10 in /etc/sysctl.conf but it couldn't resolve the problem of CPU fan (running constantly). Is it a bug in the operating system? (I'm not facing this problem while running Windows or FreeDOS) --- ober wrote: I am not sure if celeron supports this but you might try setting hw.setperf to something less than 100%. Again only will work if its supported. sysctl -a|grep setperf If you get something then try setting it down when idle sysctl -w hw.setperf=10 If you do not have it then I am not sure. Hope this helps. -On Oct 29, 2005, at 1:35 PM, PARAMVIR DHINDSA wrote: 29.10.2005 Dear Sir, I installed the OpenBSD 3.7 on my Compaq PC. I'm facing a problem. The CPU fan runs constantly (non-stop) whenever I boot on OpenBSD which has become a nuisance for me as well as my near and dear ones. Although top command shows that my CPU is sitting idle, yet the fan keeps on running until I stop my PC. Can you help me out. Hardware: Intel Celeron D (2.66 GHz). Intel Chipset 845GV chipset. 128 MB RAM. 40 GB HDD. I'm providing dmesg as under: OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(R) CPU 2.66GHz (GenuineIntel 686-class) 2.67 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,PNI,MWAIT,CNXT-ID real mem = 125345792 (122408K) avail mem = 107745280 (105220K) using 1555 buffers containing 6369280 bytes (6220K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(90) BIOS, date 01/25/05, BIOS32 rev. 0 @ 0xfbc30 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown pcibios0 at bios0: rev 2.1 @ 0xf/0xdf54 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde80/192 (10 entries) pcibios0: PCI Exclusive IRQs: 3 5 9 10 11 pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371SB ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xb200! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82845G/GL rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82845G/GL Video rev 0x03: aperture at 0xe000, size 0x800 wsdisplay0 at vga1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x02: irq 10 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x02: irq 11 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x02: irq 9 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x02: irq 11 ehci0: EHCI version 1.0 ehci0: companion controllers, 2 ports each: uhci0 uhci1 uhci2 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: single transaction translator uhub3: 6 ports with 6 removable, self powered ppb0 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x82 pci1 at ppb0 bus 1 vendor ATT/Lucent, unknown product 0x048c (class communications subclass miscellaneous, rev 0x03) at pci1 dev 10 function 0 not configured rl0 at pci1 dev 12 function 0 Realtek 8139 rev 0x10: irq 11 address 00:11:09:fa:ea:ad rlphy0 at rl0 phy 0: RTL internal phy ichpcib0 at pci0 dev 31 function 0 Intel 82801DB LPC rev 0x02
Re: HOTO Write bad documentation
Roy Morris wrote: ... Bad hair day Nick? Not at all. At this point in my life, any hair at all is good. If it wants to look like I just lost a battle with a Tesla coil, that's fine by me. :) Nick.
Re: Compressed File System
On Fri, Nov 25, 2005 at 03:55:53PM -0500, ICMan wrote: A complimentary question would be, does OpenBSD support encrypted volumes or allow encrypted files to be mounted as disk volumes? Mounting compressed files as disk volumes or compressing a disk volume would be solved using the same technique, so where one exists, the other should as well. Have a look at vnconfig(8) and vnd(4) Tobias
Re: Network Analyzer
On Fri, Nov 25, 2005 at 02:23:57PM -0500, Matthew Graham wrote: I am fairly new to OpenBSD with significant experience with Linux. I'm considering switching some of our infrastructure based systems to OpenBSD because of the security reputation and ease of updates. One of the intended boxes is a network monitor that will go inline between a host and an Ethernet switch. I've configured a transparent bridge and it works great. The ease of this alone is impressive. One utility I'm used to using for monitoring is Ethereal. I've seen all of the comments from the OpenBSD user community and understand why it's no longer available through ports. Does anyone know of a similar tool that will work well with OpenBSD and is also secure? I need more information in human readably form that I can get from tcpdump or sniffit. Thank for any advice anyone can give. What about netdude? It's also available as package. http://netdude.sf.net Tobias
Re: Network Analyzer
I would make the remote box run tethereal. Use the http://www.linbsd.org/setuid_tethereal.patch to run with the -u option for say user _ethereal. Once the capture device is opened as root, the privs will be dropped to the user specified. Use tethereal with -z proto,colinfo,$VAR,$VAR for each $VAR you want appended to the default information on each packet line. A complete list can be found with tethereal -G. Correct me if I am wrong, but I would imagine this would make it more secure, short of complete priv sep. Then what ever output can be parsed/stored without exploit concerns. Even tethereal -T pdml could give you everything in xml and you could then customize your parsing. My 2 cents. -Ober -- Forwarded message -- Date: Fri, 25 Nov 2005 13:56:39 -0700 From: Theo de Raadt [EMAIL PROTECTED] To: Matthew Graham [EMAIL PROTECTED] Cc: misc misc@openbsd.org Subject: Re: Network Analyzer One utility I'm used to using for monitoring is Ethereal. I've seen all of the comments from the OpenBSD user community and understand why it's no longer available through ports. Does anyone know of a similar tool that will work well with OpenBSD and is also secure? I need more information in human readably form that I can get from tcpdump or sniffit. It is super dangerous. It went through a period of I think about 30 remote code running bugs in a few months, but bugs are always being found. It is very difficult to write 100% correct packet parsing code. Errors will be made. And exactly where you cannot afford them. For this reason, we audited tcpdump. Then we realized that errors would still be made, and we then privilege seperated it, so that the nasty code runs in a jail. The same approach could be taken by other projects towards their code, but yes, it is a fairly difficult chunk of code to write. In general we supply our user community with any tool they might want. But ethereal was becoming something so often used, so often used poorly, and so often used without any awareness as to how great the risk was. We felt we had to do something, and thus we deleted it. You can compile it up yourself. Right now, though, it is amongst the most dangerous pieces of software people are running. It is your choice..
RAID Controller for UltraATA/133 Drives?
Hello All, I just picked up three Maxtor 200GB UltraATA/133 drives that I'd like to use in a RAID-5 configuration with my OpenBSD web/mail server. I've spent the past couple of hours carefully combing through all of the RAID cards that are listed as supported on http://www.openbsd.org/i386.html#hardware, and unless I'm missing something, there's something of a gap between ATA/100 and SATA/150 there (for example, the MegaRAID 150-4/6 and the MegaRAID i4). I've even seen from the archives that the MegaRAID 133-2 is *not* supported, due to its lack of an integrated I/O processor. That said, I apologize if this question has already been answered, but what would be my best bet for building a RAID-5 with these disks under OpenBSD? Thanks, Alex Kirk
Re: Network Analyzer
Netdude has very little knowledge of application protocols. Would be nice if it could link to libethereal to gather said information. :D -Ober On Fri, 25 Nov 2005, Tobias Ulmer wrote: On Fri, Nov 25, 2005 at 02:23:57PM -0500, Matthew Graham wrote: I am fairly new to OpenBSD with significant experience with Linux. I'm considering switching some of our infrastructure based systems to OpenBSD because of the security reputation and ease of updates. One of the intended boxes is a network monitor that will go inline between a host and an Ethernet switch. I've configured a transparent bridge and it works great. The ease of this alone is impressive. One utility I'm used to using for monitoring is Ethereal. I've seen all of the comments from the OpenBSD user community and understand why it's no longer available through ports. Does anyone know of a similar tool that will work well with OpenBSD and is also secure? I need more information in human readably form that I can get from tcpdump or sniffit. Thank for any advice anyone can give. What about netdude? It's also available as package. http://netdude.sf.net Tobias
Re: Network Analyzer
On Fri, Nov 25, 2005 at 11:57:27PM +0100, Tobias Ulmer wrote: On Fri, Nov 25, 2005 at 02:23:57PM -0500, Matthew Graham wrote: I am fairly new to OpenBSD with significant experience with Linux. I'm considering switching some of our infrastructure based systems to OpenBSD because of the security reputation and ease of updates. One of the intended boxes is a network monitor that will go inline between a host and an Ethernet switch. I've configured a transparent bridge and it works great. The ease of this alone is impressive. One utility I'm used to using for monitoring is Ethereal. I've seen all of the comments from the OpenBSD user community and understand why it's no longer available through ports. Does anyone know of a similar tool that will work well with OpenBSD and is also secure? I need more information in human readably form that I can get from tcpdump or sniffit. Thank for any advice anyone can give. What about netdude? It's also available as package. http://netdude.sf.net Tobias I use tcpick for seeing the traffic just while it gets throw the device. I thought about creating a port for tcpick, do you think thats a good idea? Jonathan -- | /\ ASCII Ribbon | Jonathan Glaschke - Lorenz-Goertz-Stra_e 71, | \ / Campaign Against | 41238 Moenchengladbach, Germany; | XHTML In Mail | jabber: [EMAIL PROTECTED] | / \ And News | http://jonathan-glaschke.de/
Re: Something hosing my msdos/FAT32 file system
A long time ago, Pedro Martelletto wrote: Alexander, can you please try to build a test-case that rules out NFS, if at all possible? I ran into this just this week while moving stuff like crazy. Succeeded to boil stuff down to a very limited set of operations that fscks things up. I run tests on a (disposable :) vnd device but I got the same results on an ordinary partition (wd0n). Upgraded to snapshot from Nov 25 to make sure this wasn't fixed since I noticed some changes but no better luck there. Maybe you, or anyone else, can do somthing of it. Fails like a charm every time for me. /Alexander $ dd if=/dev/zero of=msdos_fs bs=1024 count=1024 1024+0 records in 1024+0 records out 1048576 bytes transferred in 0.014 secs (70148247 bytes/sec) $ sudo vnconfig vnd0 msdos_fs $ sudo newfs_msdos /dev/rvnd0c /dev/rvnd0c: 2008 sectors in 251 FAT12 clusters (4096 bytes/cluster) bps=512 spc=8 res=1 nft=2 rde=512 sec=2048 mid=0xf0 spf=1 spt=63 hds=1 hid=0 $ sudo mount_msdos -m 777 -l /dev/vnd0c /mnt/test/ $ cd /mnt/test $ mkdir a aa ab $ find . . ./a ./aa ./ab $ mv aa ab a $ find . . ./a ./a/aa $ ll a total 16 drwxrwxrwx 1 root wheel 4096 Nov 26 00:52 aa/ drwxrwxrwx 1 root wheel 4096 Nov 26 00:52 ab/ $ find -L . . ./a ./a/aa ./a/ab
Re: Compressed File System
On 2005-11-25 15:55:53 -0500, ICMan wrote: There are a lot of large files moving into the space on a regular basis, and they need to be stored for a long time in active disk space. I have Are you sure that the trouble with compressed file is worth the money saved from buying larger disks? Best Martin PS: Top-quotes :-( -- http://www.tm.oneiros.de
Re: RAID Controller for UltraATA/133 Drives?
--On 25 November 2005 18:06 -0500, Alex Kirk wrote: I just picked up three Maxtor 200GB UltraATA/133 drives that I'd like to use in a RAID-5 configuration with my OpenBSD web/mail server. .. http://www.openbsd.org/i386.html#hardware, and unless I'm missing something, there's something of a gap between ATA/100 and SATA/150 there (for example, the MegaRAID 150-4/6 and the MegaRAID i4). .. I apologize if this question has already been answered, but what would be my best bet for building a RAID-5 with these disks under OpenBSD? i4 (or dell cerc-pata, which is the same thing and possibly easier to find on ebay if that's where you're buying). Have a look at the sustained transfer rate of the drives, I'll be very surprised if it's enough to max out 100MB/sec, and with 3 disks on an i4 you won't need to share channels.
Re: Something hosing my msdos/FAT32 file system
On Sat, Nov 26, 2005 at 12:57:06AM +0100, Alexander Hall wrote: $ dd if=/dev/zero of=msdos_fs bs=1024 count=1024 $ sudo vnconfig vnd0 msdos_fs $ sudo newfs_msdos /dev/rvnd0c $ sudo mount_msdos -m 777 -l /dev/vnd0c /mnt/test/ $ cd /mnt/test $ mkdir a aa ab $ find . . ./a ./aa ./ab Interesting. If you don't do this preliminary 'find', then all is fine. $ mv aa ab a $ find . . ./a ./a/aa $ ll a total 16 drwxrwxrwx 1 root wheel 4096 Nov 26 00:52 aa/ drwxrwxrwx 1 root wheel 4096 Nov 26 00:52 ab/ $ find -L . . ./a ./a/aa ./a/ab And if you try 'rm -rf a' now, you're likely to get: rm: fts_read: No such file or directory -p.
Re: HOTO Write bad documentation
On 11/25/05, Nick Holland [EMAIL PROTECTED] wrote: We've been seeing a curious number of people offering various kinds of documentation on various OpenBSD topics. Most of them are somewhere between minimally useful and outright destructive and foolish. I think I've seen precisely one that is looking very promising...and that was sent to me privately, you haven't seen it yet. Obviously, bad documentation is in style now. However, people seem to be thrashing around on how to write bad documentation, so here are some tips based on experience with a number of recent submissions to [EMAIL PROTECTED] 1) Distribute your document in PDF file format. Yes, the Web is based on HTML, but hey, it is your document, make it PDF! There are at least a couple people who prefer that format (if all else fails, register a hotmail or yahoo e-mail address under another name, and say, I prefer PDF!). That way, people MUST add additional software to their system to read your document. People won't be able to send you diffs, so you can say honestly, I received no useful change suggestions to this document, it MUST be good!. It also hides the fact that while you are claiming to be an OpenBSD expert, the only text editor/formatter you know how to use is MS Word. A PDF creation program will hide that very effectively. Bonus points for formats that are more obscure, less portable, or require over 500M RAM to open a two page document. 2) Write it as a HOWTO. Your reader just wants to know how to do the task they have at hand. After all, we know they are just wanting to accomplish the task, put it on their resume, and be elsewhere by the time it blows up. It won't be their problem by then, anyway! There is only one way to do most tasks, those extra knobs are there and set wrong just to confuse the new user, no one actually uses them differently, EVERYONE does things just like you suggest. Theo delights in adding extra knobs to OpenBSD and making sure they are set incorrectly. Rumors that he actively removes nonsense options are completely untrue. No one cares about life-cycle-related issues like upgrades or recovering from system failures or disasters. Besides, it is funny to watch people for whom English is not their first language think howto is a valid English word, and is often used with a question mark at the end (Howto get my mouse working?), as a replacement for how do I ...?. 3) Write it for an older release. 3.8 was only just shipped, there are surely more 3.7 or 3.6 users that could benefit from your writing then there are 3.8 users, right? The fact that improvements in the most recent release make much of your work incorrect or less than ideal isn't your problem... 4) Publish it, let it rot. Don't waste time bringing/keeping your old documents up to date. There are so many other things you could be doing, instead. People will figure it out. After all, books don't automatically update on your shelf, why should a web page be any different? Besides, PDF files are a pain to edit, and this way, you don't have to keep track of where you left the original source. 5) Write a rough draft, put it on misc@, and let the community decide if it is useful or accurate. That's what the Internet is about, right? Freedom to say any damn thing you wish, regardless of accuracy. You are supporting free speech, that's a good thing, right? BTW, all the people who say you are going about things wrong are just plain dumb, don't let their @openbsd.org e-mail addresses fool you. E-mail can be easily spoofed. Or they are trying to repress you. BTW: The more people you can get irate about your article and tell you so publicly on the mail lists (quoting the link to your article), the higher it will be in Google's rankings, permitting more people to find your wisdom! 6) Good formatting and pretty graphics mean more than actual content. Obviously, if your page LOOKS good, it must be good. Complex things like CSS and browser-specific tricks are great! Compared to the lame OpenBSD website, you will look like an absolute authority! 7) When you don't know what is going on, just tell everyone to do what got things to (sorta) work for you. Don't waste time by researching your topic completely, or privately asking people in-the-know to verify key facts. The difficulty is clearly the result of the sloppy work of the OpenBSD developers. Acknowledging your ignorance of a topic clears your conscience. Just say, I don't understand this, but it worked for me, so everyone should do this. 8) If you got the thing to work, you are qualified to write a HOWTO. The more you investigate something, the more annoying issues and special cases (like maintainability) come up, so don't waste your time. 9) An hour or two is sufficient to spend writing a HOWTO. Anything more than that is just wasting your time. The reader will figure out the things you
Re: RAID Controller for UltraATA/133 Drives?
Quoting Stuart Henderson [EMAIL PROTECTED]: --On 25 November 2005 18:06 -0500, Alex Kirk wrote: I just picked up three Maxtor 200GB UltraATA/133 drives that I'd like to use in a RAID-5 configuration with my OpenBSD web/mail server. .. http://www.openbsd.org/i386.html#hardware, and unless I'm missing something, there's something of a gap between ATA/100 and SATA/150 there (for example, the MegaRAID 150-4/6 and the MegaRAID i4). .. I apologize if this question has already been answered, but what would be my best bet for building a RAID-5 with these disks under OpenBSD? i4 (or dell cerc-pata, which is the same thing and possibly easier to find on ebay if that's where you're buying). Have a look at the sustained transfer rate of the drives, I'll be very surprised if it's enough to max out 100MB/sec, and with 3 disks on an i4 you won't need to share channels. That sounds perfectly reasonable. I had been concerned that the i4 wouldn't even talk to the drives, given that they're rated faster than its top speed, but if it's just an issue of *possibly* sacrificing a bit of speed (which, given your explanation, seems unlikely anyway), then my problem is solved. Thanks! :-) BTW, if anyone is interested in hearing how this information performs (either from a developer's or a user's perspective), shoot me an e-mail in a couple of weeks, when I've had a chance to get everything installed properly. Alex Kirk
Re: Something hosing my msdos/FAT32 file system
Pedro Martelletto wrote: On Sat, Nov 26, 2005 at 12:57:06AM +0100, Alexander Hall wrote: $ dd if=/dev/zero of=msdos_fs bs=1024 count=1024 $ sudo vnconfig vnd0 msdos_fs $ sudo newfs_msdos /dev/rvnd0c $ sudo mount_msdos -m 777 -l /dev/vnd0c /mnt/test/ $ cd /mnt/test $ mkdir a aa ab $ find . . ./a ./aa ./ab Interesting. If you don't do this preliminary 'find', then all is fine. Yes I noticed that, too. :) $ mv aa ab a If I do ``mv aa a; mv ab a'', all is fine, too. AFAICT, this should require the exact same syscalls to perform as ``mv aa ab a''; one for each file to move. It seems that if things happen too fast things go bad. Thinking of it, since the first find is required to get bad results, I get the feeling that some caches/vnodes/... are populated with corrupted values, (but I don't know much about this, so I maybe just better stop guessing). What I mean is that if so, the error must not be within rename. $ find . . ./a ./a/aa $ ll a total 16 drwxrwxrwx 1 root wheel 4096 Nov 26 00:52 aa/ drwxrwxrwx 1 root wheel 4096 Nov 26 00:52 ab/ $ find -L . . ./a ./a/aa ./a/ab This one is funny. Don't ask me how come I tested it. Symlinks on msdosfs? And what are they linking to? :) And if you try 'rm -rf a' now, you're likely to get: rm: fts_read: No such file or directory Actually, after testing copying aa and ab separately, I cannot reproduce the previous errors again. Maybe a reboot will help. FWIW, I think that unmounting and mounting the fs again restored the order (or so it seemed). Please let me know if there is anything else I can do to help you. /Alexander
Re: Something hosing my msdos/FAT32 file system
On Sat, Nov 26, 2005 at 03:05:30AM +0100, Alexander Hall wrote: Actually, after testing copying aa and ab separately, I cannot reproduce the previous errors again. Maybe a reboot will help. FWIW, I think that unmounting and mounting the fs again restored the order (or so it seemed). Please let me know if there is anything else I can do to help you. /Alexander On a side note, I'm fairly convinced it has someting to do with the FTS_PHYSICAL option being passed to fts_open(3). That's why 'find -L' works. -p.
Re: RAID Controller for UltraATA/133 Drives?
On Fri, 25 Nov 2005 18:06:44 -0500, Alex Kirk [EMAIL PROTECTED] wrote: Hello All, I just picked up three Maxtor 200GB UltraATA/133 drives that I'd like to use in a RAID-5 configuration with my OpenBSD web/mail server. I've spent the past couple of hours carefully combing through all of the RAID cards that are listed as supported on http://www.openbsd.org/i386.html#hardware, and unless I'm missing something, there's something of a gap between ATA/100 and SATA/150 there (for example, the MegaRAID 150-4/6 and the MegaRAID i4). I've even seen from the archives that the MegaRAID 133-2 is *not* supported, due to its lack of an integrated I/O processor. That said, I apologize if this question has already been answered, but what would be my best bet for building a RAID-5 with these disks under OpenBSD? Thanks, Alex Kirk Well, late as usual, I'm finally getting around to rolling out 3.8 from the Official OpenBSD Release CD, and oddly enough, I was just testing out a MegaRAID ATA 133-2 on one of the boxes. You are partially correct about the MegaRAID ATA 133-2 HBA; the MegaRAID ATA 133-2 is _partially_ supported in OpenBSD mainly because it is only _partially_ a RAID device. The low-end ATA-133-2 card is actually a fake-RAID device that requires specialized drivers to enable the RAID functionality. Though the ATA 133-2 card can not do it's usual fake-RAID on OpenBSD due to the lack of fake-RAID drivers, the card still works perfectly as standard ATA-133 controller. -Saying it is *not* supported is somewhat unfair, since it actually is supported as well as it can be without adding a closed source binary driver to your system. If you really needed RAID functionality and it was the only card you had, you could easily use it as a normal controller then do SoftRAID on top of it. Personally, I've liked the MegaRAID i4 and rolled them out in 3.6/3.7 systems. They work really well and the suggestion to use them came from someone on this list (C. Bernsend I think). Don't fool yourself into thinking the ATA100 versus ATA133 thing is actually some big deal. It's not. Sustained transfer rates of a single drive are generally between 25 and 40 MB/s, so even having two drives on a single channel does not exceed the max transfer rate of the channel. -You've been caught up by the MAXTOR marketing ploy. Similar nonsense is even more true for the SATA150/SATA300 marketing crap; the sustained transfer rate of a single drive can not saturate the max transfer rate of the interface. In contrast to past experience, at the moment I'm currently fighting with a new SuperMicro dual 1Ghz PIII system that is refusing to boot due to the MegaRAID i4 card. There is something goofy going on with it. MainBoard: SuperMicro P6DGE Procs: (2) P-III 1Ghz RAM:2GB RAID_HBA: LSI Logic MegaRAID i4 Firmware: Current (version N661) Disks: (4) MAXTOR 6Y250P0 250GB EIDE Physical: One Disk Per EIDE Channel Logical:1 Logical Device (RAID 5 across all four disks) Checks: Consistency Check Currently Running... BootMedia: Official OpenBSD 3.8 Release CD-ROM DMESG: (still waiting for CC) PROBLEM:Seems to be waiting in an endless loop ami0: timeout ccb ami0: timeout ccb ami0: timeout ccb ... I'll post a DMESG as soon as I can, probably in a new thread. It will be a while since I'm waiting the 20+ hour long Consistency Check to complete before hooking up serial to capture the DMESG. If you ever hit a problem, always check everything you can before wasting developer time with bug report that may be caused by _you_ or _your_ faulty hardware. Also, it's very unfair to report a bug unless you are willing to do the work necessary to help the developers replicate the problem and do the needed testing for them. If you search the list archives and CVS logs you'll see that the problem I am having has been worked on by both Theo@ and [EMAIL PROTECTED] One of the people who posted a ami0: timeout ccb problem on a LSI MegaRAID STAT 150-4 HBA in May to this list was unwilling to actually help Marco test and debug the issue. Most of my personal hardware is ancient by modern standards (= 1GHz and I kinda like it that way), so if you go with a MegaRAID i4 you probably won't have the same issue I'm currently having, or it might be fixed by the time you actually get the card. Kind Regards, JCR
FileSystem versus File System
I went looking for HIER(7) but didn't know it's name, so I stuffed the words file system into an Apropos keyword search and got nothing. http://www.openbsd.org/cgi-bin/man.cgi?query=file+systemsektion=0manpath=OpenBSD+Currentarch=i386apropos=1format=html Damn, I _KNOW_ the darn thing exists because I've read it before. After think about it, I tried an Apropos search for the keyword layout and finally found HIER(7). The think I found interesting is that HIER(7) uses the term filesystem without a space, while other man pages use file system with a space. Other documentation on the OpenBSD.org web site also shows both spellings are used in fairly equal measure: Google: Results 1 - 100 of about 347 from www.openbsd.org for filesystem. Results 1 - 45 of about 534 from www.openbsd.org for file system My question are: (1) Are patches even wanted to standardize on one of the two? (2) Which do you think is more correct? There's no sense in me spending the time to create and send documentation patches if the discrepancy is a considered non-issue. Kind Regards, JCR
Re: hw.setperf strangeness
On Friday 25 November 2005 20:03, Ted Unangst wrote: maybe, speedstep can only be set to fast and slow, and the driver won't move things if it thinks nothing is changing. maybe there's a bug, maybe you need to fiddle it up and down some to make it actually work, but 0 and 100 are the only settings that really mean anything. It would seem nothing is happening: $ sysctl hw | tail -2 hw.cpuspeed=1296 hw.setperf=100 $ md5 -t MD5 time trial. Processing 1 1-byte blocks... Digest = 52e5f9c9e6f656f3e1800dfa5579d089 Time = 0.691865 seconds Speed = 144536867.741539 bytes/second $ sudo sysctl -w hw.setperf=0 hw.setperf: 100 - 0 $ sysctl hw | tail -2 hw.cpuspeed=1296 hw.setperf=0 $ md5 -t MD5 time trial. Processing 1 1-byte blocks... Digest = 52e5f9c9e6f656f3e1800dfa5579d089 Time = 0.693320 seconds Speed = 144233542.952749 bytes/second $ sudo sysctl -w hw.setperf=80 hw.setperf: 0 - 80 $ sysctl hw | tail -2 hw.cpuspeed=750 hw.setperf=80 $ md5 -t MD5 time trial. Processing 1 1-byte blocks... Digest = 52e5f9c9e6f656f3e1800dfa5579d089 Time = 0.695775 seconds Speed = 143724623.621142 bytes/second Is there any way to determine from the dmesg if speedstep is detected? --- Lars Hansson
Theorical question on dual core vs single CPU in routing setup.
Here a question I found interesting for my own education, and I am trying to come to peace with as far as applications usage with dual core, or multi-processor vs single one. I was asking myself if I would actually benefit from a dual core processor, or multi-processor system in a routing setup and more I think about it, I would think not as the application is not multi-treads to start with and there isn't must else running as well. Am I wrong in my understanding? Looking at the code of bgpd/ospfs, I don't see it design as using multiple treads ( doesn't mean I understand it fully either) so it wouldn't benefit from a dual core server then, and as the routing table basically is process by the kernel, I would think it would be useless to have multi core no? In a setup where multiple applications are running, or where the applications are design with treads in it, yes, but here am I wrong to think that for a setup where routing with multiple Ethernet ports and where bgpd/ospfd is running with pf that it wouldn't really be a benefit? They all are dependent on each other and as such would need to wait anyway if the routing table changed. Can someone correct my understanding, or lack there of, I was curious about that now. Multi-processor is only useful when you can do multiple things, not related to each other at the same time, or the application is design with treads in mind, so here I guess the benefit would be minimal no? Unless I miss something in the code, or something in how bsd.mp works (as it would be required to run dual core CPU), may as well put the money for the speed instead of dual core no? It's not a big issue, but it got me thinking about it at the point that I really got curious as to the outcome now, and wonder if I actually understand it right, or if I am full of it! Thanks for your time. Daniel
