Re: Find duplicate files
On Sun, Dec 14, 2008 at 02:25:48PM +0100, Pc Nicolas wrote: > Hi > > Do you know a command line utility to find duplicate files with OpenBSD ? > > Thanks > fdupes, in ports.
Re: Backup strategies
On 1 fivr. 09, at 18:11, Toni Mueller wrote: On Sun, 01.02.2009 at 13:01:52 +, Matthew Szudzik > wrote: See http://en.wikipedia.org/wiki/ISO_9660#The_4_GiB_.28or_2_GiB_depending_on_impl ementation.29_file_size_limit Thanks for the heads-up, but Some operating systems can handle files up to 4GB on an ISO 9660 filesystem, and other operating systems can handle more than 4GB. But if you want your ISO 9660 filesystem to be fully portable, you should stick to the 2GB limit. if I'm not mistaken, quite a bit of software today comes on DVDs, crammed to the brim. So I wonder whether the standard has been extended, whether there's a convention about how to deal with larger files, or whether it's sheer accident that it works. Besides, having media types that can't be fully utilized is neither useful nor acceptable, imho, but the solution can't be "make only smaller media". You seem to be mistaken. The 4GB file limitation is for files *INSIDE* an ISO file system, not for the ISO itself. You can use the UDF format to store larger files (and avoid other limitations too, like filename length), but it might not be as portable as an ISO file system.
Re: Reset root password on system with console insecure?
On Thu, Feb 05, 2009 at 02:44:49PM +0100, Hannah Schroeter wrote: > Hi! > > On Thu, Feb 05, 2009 at 02:39:18PM +0100, Hannah Schroeter wrote: > >On Thu, Feb 05, 2009 at 07:27:56AM -0600, Phusion wrote: > >>I am looking for advice on how to reset the root password on an > >>OpenBSD system that has console set to insecure in /etc/ttys. I have > >>booted off the install CD and into the shell and mounted the / > >>partition read-write, but don't have access to vi to modify > >>/etc/master.passwd. I was thinking I could clear out the root password > >>and afterwards run pwd_mkdb. Let me know. Thanks. > > >If you mount the original / partition (like in mount /dev/wd0a /mnt), > >you can then mount /usr, /var, too (e.g. mount /dev/wd0d /mnt/usr, mount > >/dev/wd0e /mnt/var). Then you can chroot into your system: > >/mnt/usr/sbin/chroot /mnt /bin/ksh. Then you can setup the terminal > >(export TERM=pcvt25) and the editor (export EDITOR=/usr/bin/vi) and > >use vipw. > > Of course, after chroot you could also use the passwd command (passwd > root) to directly set a new password for root (and perhaps your own > user account if you've lost that password too). passwd doesn't ask the > old password if you use it as root. > > And then, perhaps setup sudo so you can get root from your user account... > > Kind regards, > > Hannah. > Or learn to use ed :)
Re: TBB on OBSD
On 25 fivr. 09, at 07:17, Jack Woehr wrote: Anyone working with TBB ( http://www.threadingbuildingblocks.org/ ) on OpenBSD? http://marc.info/?l=openbsd-ports&m=122559493912076&w=2
Re: Inexpensive, low power, "wall wart" computer
On Wed, Feb 25, 2009 at 11:26 AM, Lars Noodin wrote: > David Vasek wrote: >> What would be firewire good for? > > Data transfer such as for full backups or cloning or audio/video. > Haven't tested it yet on OpenBSD, I still have USB-only / ethernet-base > storage for those systems. Subjectively, I find FW to be much faster > than USB2 on my hardware using OS X and Ubuntu. FireWire is not supported on OpenBSD.
Re: Go order your 4.5 CD
On Thu, Mar 5, 2009 at 10:47 PM, Daniel Ouellet wrote: > The new puffy looks nice too. Look to me that may be we have a new disco > puffy with the improvements on the audio in the system, but I could be > wrong. Disco puffy? Looks to me that you need to improve your geek culture.
Re: openbsd in virtualization
On Wed, Mar 18, 2009 at 05:45:17AM -0400, Daniel Ouellet wrote: >> - XEN > > I could be wrong here, but if my memory is somewhat intact, I think XEN > is not playing to well with OpenBSD. There was worked done to port it to > OpenBSD, I think it was two years ago, but I can't remember exactly, > it's in the archive anyway and as far as I know, there wasn't to much > good exchange on misc@ about it and not great success. > > So, I would strongly suggest to research it first, I know there was some > real try about it but somehow fail in the end to finish I think. > > Again, don't take my word on this one, that's what I kind of recall, but > my memory is known to fail at time! (;p> Xen is not limited to paravirtualization (as you recall, a port of OpenBSD as a Xen paravirtualized DomU was being developed but was not finished). It also offers full-virtualization relying on CPUs with hardware virtualization capabilities.
Re: Odd problem, may be related to relayd
On Wed, Apr 08, 2009 at 03:06:37PM -0400, Daniel Ouellet wrote: >> Which will soon be no longer. > > I only have one small question left if I may. I do see plenty of changes > from Henning and others on this and still plenty going in pf in CVS. > > I am not sure I follow it all yet and may be it's because it's not all > finish, but scrub isn't going to be remove all together from pf is it? > > I am not clear as to what part of scrub is changing or being removed. > > Can just a quick summary, or even one line answer provide some details > as to what is actually being removed, or changed from it? > > I can wait until the man page is changed too, but I wonder what is it > actually really going on there if I may? > > Best, > > Daniel > The scrub rule was removed, and a scrub option was added (among other changes, read the commit messages, it is not THAT complicated), allowing for fine-grain scrubbing (i.e. different rules can have different scrubbing options).
Re: generic.mp on laptop question: resolved
On Fri, Apr 17, 2009 at 05:48:00PM -0500, Denny White wrote: > On Fri, Apr 17, 2009 at 10:48:58AM -0400, Dan Harnett spoke thusly: > > On Fri, Apr 17, 2009 at 12:02:35AM -0500, Denny White wrote: > > > Okay, dumb-ass me. Sitting here looking at the screen it finally > > > dawned on me I'm not looking at 2 physical cpu's, per se, but > > > instead 2 built onto one chip. Gee, I wish I would've come up > > > with that beforehand instead of opening my mouth and removing > > > any doubt in regards to my hardware ignorance. Only thing in > > > my defense is I've never owned anything like that before. Before > > > getting this laptop given to me, my fastest box was an aging dell > > > dimension Pentium IV 2.66. No dual-cores, no dual-cpu's. Time to > > > slink off now. ;) > > > > A processor can have multiple sensors even though it is only a single > > physical package. It varies between processors. > > > > $ sysctl hw.model hw.sensors > > hw.model=Intel(R) Core(TM)2 Duo CPU L7500 @ 1.60GHz > > hw.sensors.cpu0.temp0=44.00 degC > > hw.sensors.cpu1.temp0=44.00 degC > > hw.sensors.acpitz0.temp0=45.05 degC (zone temperature) > > hw.sensors.acpitz1.temp0=44.05 degC (zone temperature) > > hw.sensors.acpibat0.volt0=14.40 VDC (voltage) > > hw.sensors.acpibat0.volt1=16.53 VDC (current voltage) > > hw.sensors.acpibat0.watthour0=36.62 Wh (last full capacity) > > hw.sensors.acpibat0.watthour1=1.83 Wh (warning capacity) > > hw.sensors.acpibat0.watthour2=0.20 Wh (low capacity) > > hw.sensors.acpibat0.watthour3=36.45 Wh (remaining capacity), OK > > hw.sensors.acpibat0.raw0=0 (battery idle), OK > > hw.sensors.acpibat0.raw1=0 (rate) > > hw.sensors.acpiac0.indicator0=On (power supply) > > hw.sensors.acpithinkpad0.temp0=45.00 degC (TMP0) > > hw.sensors.acpithinkpad0.temp1=34.00 degC (TMP1) > > hw.sensors.acpithinkpad0.temp2=34.00 degC (TMP2) > > hw.sensors.acpithinkpad0.temp3=38.00 degC (TMP3) > > hw.sensors.acpithinkpad0.temp4=24.00 degC (TMP4) > > hw.sensors.acpithinkpad0.temp6=24.00 degC (TMP6) > > hw.sensors.acpithinkpad0.fan0=0 RPM (fan) > > hw.sensors.iwn0.temp0=56.00 degC > > hw.sensors.aps0.temp0=34.00 degC > > hw.sensors.aps0.temp1=34.00 degC > > hw.sensors.aps0.indicator0=On (Keyboard Active) > > hw.sensors.aps0.indicator1=Off (Mouse Active) > > hw.sensors.aps0.indicator2=On (Lid Open) > > hw.sensors.aps0.raw0=507 (X_ACCEL) > > hw.sensors.aps0.raw1=513 (Y_ACCEL) > > hw.sensors.aps0.raw2=507 (X_VAR) > > hw.sensors.aps0.raw3=513 (Y_VAR) > > Yup, so I've learned. Thanks, Dan. Like I said before, never > owned anything that modern before. ;) But, since last night, > I've done a lot of reading up on it. Should've done it before > but I didn't know I was gonna be given a new dual-core laptop. > That doesn't happen very often. Not around here anyway. ;) It's just that the code creating hw.sensors.cpuX.temp0 is a little different between i386 and amd64, so amd64 shows one sensor for each core (but with the same temperature) while i386 shows only one sensor for all cores.
Re: OpenBSD kernel janitors
On Wed, Oct 31, 2007 at 10:30:24AM -0400, Nick Guenther wrote: > On 10/31/07, Theo de Raadt <[EMAIL PROTECTED]> wrote: > > > They don't need a list. They could already have started coding. Yet > > we see how few people actually do start coding. Instead, they choose > > to write in english... > > How can we get started on the code unless we have some idea of where > to start on the code? Sure we could just code whatever, but why would > we waste time on things that may be useless? > > > > Obviously patches will be subject to peer review. Even if a patch isn't > > > approved, the coder should have learned something new and useful. > > > > Yeah, right. > > I don't understand. Is newbies learning new things a waste to you? Do > you think they won't really learn anything unless the patch is > approved? Or will the patches not be subject to peer review? Or are > you worried at who would pass for peer review getting overwhelmed by a > huge volume of poor quality patches? > > -Nick > Remember the motto guys: it's ``shut up and hack'', not whine about getting something to do, then whine about how to do it, and hack. If you don't know what to do, read source code, then hack. If you don't know how to read source code, then learn by reading books, then read source code, then hack. If you don't want to read, just shut up. Pierre Riteau -- a modest contributor who like the way it is.
Re: wpi 3945 firmware error
On Sun, Nov 04, 2007 at 02:52:52PM +0100, Johannes Krampf wrote:
> My wireless network uses 11a and 128bit-WEP. I can successfully set
> the nwid, nwkey and IP with ifconfig and start the interface, but when
> I try to scan (ifconfig -M wpi0), the wireless light will blink once
> and immediately I see a "wpi0: fatal firmware error" (or similar)
> message on the terminal.
>From a recent CVS commit:
CVSROOT:/cvs
Module name:src
Changes by: [EMAIL PROTECTED] 2007/11/03 07:10:29
Modified files:
sys/dev/pci: if_wpi.c if_iwn.c
Log message:
fix ENETRESET handling in {wpi,iwn}_ioctl() so that the firmware won't
panic when resetting the device - requested by many
fix ifconfig -M (the interface still has to be down though ie it won't
work while the interface is up).
fix AMPDU window for 4965AGN (has no effect since 802.11n is not
supported yet).
So you should try with -current (no snapshot is available with that
code yet, wait a few days if you want to use a snapshot) AND make sure
your interface is down when running the scan.
Pierre Riteau
Re: scp doesn´t recognizes 127.0.0.1* as filename
On Nov 26, 2007 10:24 PM, Eduardo Alvarenga <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] crash]# scp -r 127.0.0.1-2007-11-26-18:31 [EMAIL > PROTECTED]:/u02/snap > ssh: 127.0.0.1-2007-11-26-18: Name or service not known What if you try 'scp -r ./127.0.0.1-2007-11-26-18:31 [EMAIL PROTECTED]:/u02/snap' ? -- Pierre Riteau
Re: Intel DQ35MP
c, 625142448 sec > total > ichiic0 at pci0 dev 31 function 3 "Intel 82801I SMBus" rev 0x02: irq 9 > iic0 at ichiic0 > spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-6400CL5 > spdmem1 at iic0 addr 0x52: 1GB DDR2 SDRAM non-parity PC2-5300CL5 > usb2 at uhci0: USB revision 1.0 > uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1 > usb3 at uhci1: USB revision 1.0 > uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1 > usb4 at uhci2: USB revision 1.0 > uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1 > usb5 at uhci3: USB revision 1.0 > uhub5 at usb5 "Intel UHCI root hub" rev 1.00/1.00 addr 1 > usb6 at uhci4: USB revision 1.0 > uhub6 at usb6 "Intel UHCI root hub" rev 1.00/1.00 addr 1 > usb7 at uhci5: USB revision 1.0 > uhub7 at usb7 "Intel UHCI root hub" rev 1.00/1.00 addr 1 > isa0 at ichpcib0 > 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 > pcppi0 at isa0 port 0x61 > midi0 at pcppi0: > spkr0 at pcppi0 > npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 > biomask fffd netmask fffd ttymask > mtrr: Pentium Pro MTRR support > uhidev0 at uhub7 port 1 configuration 1 interface 0 "vendor 0x13ba Generic USB > K/B" rev 1.10/0.01 addr 2 > uhidev0: iclass 3/1 > ukbd0 at uhidev0: 8 modifier keys, 6 key codes > wskbd1 at ukbd0 mux 1 > wskbd1: connecting to wsdisplay0 > uhidev1 at uhub7 port 1 configuration 1 interface 1 "vendor 0x13ba Generic USB > K/B" rev 1.10/0.01 addr 2 > uhidev1: iclass 3/1, 2 report ids > ums0 at uhidev1 reportid 1: 3 buttons and Z dir. > wsmouse0 at ums0 mux 0 > uhid0 at uhidev1 reportid 2: input=1, output=0, feature=0 > dkcsum: sd0 matches BIOS drive 0x80 > root on sd0a swap on sd0b dump on sd0b > umass0 at uhub0 port 5 configuration 1 interface 0 "USB Audio Player" rev > 2.00/0.02 addr 2 > umass0: using SCSI over Bulk-Only > scsibus1 at umass0: 2 targets > sd1 at scsibus1 targ 1 lun 0: <, Audio Player, \\001> SCSI0 0/direct > removable > sd1: 968MB, 123 cyl, 255 head, 63 sec, 512 bytes/sec, 1984000 sec total > > Regards, > > Marcos Laufer > > -- Pierre Riteau
Re: BOINC software on OpenBSD
On Dec 18, 2007 8:17 AM, Tasmanian Devil <[EMAIL PROTECTED]> wrote: > Hello! > > > I just want to know if somebody has running any Boinc client on > > OpenBSD. But that's only the client, then each project provides binaries, and often no binaries for OpenBSD. >From a quick google search, I find only Seti and SIMAP providing OpenBSD binaries. You can probably use Linux emulation to get it running. But maybe you will have to make it believe it is a Linux system to get it to download the Linux binaries. -- Pierre Riteau
Re: Using the C programming language
On Dec 24, 2007 4:40 AM, Rico Secada <[EMAIL PROTECTED]> wrote: > Linus agreed that following OpenBSD's lead was the right way forward, > and strlcpy() is in his BitKeeper repository, waiting for 2.5.71. There > has also been a flurry of activity to convert kernel code over to the > new function. By the time 2.6.0 comes out, strncpy() may no longer have > a place in the Linux kernel. We are nearly in 2008, 2.6.24 is on its way to the release, and strncpy bugs still appear in the Linux kernel. I just stumbled upon this, it's a commit from yesterday in Linus' tree: From: Eric Sandeen <[EMAIL PROTECTED]> Date: Sat, 22 Dec 2007 22:03:24 + (-0800) Subject: ecryptfs: fix string overflow on long cipher names X-Git-Url: http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=commitdiff_plain;h=b88629060b03adc58639f818fe0968bf5fe81b5d ecryptfs: fix string overflow on long cipher names Passing a cipher name > 32 chars on mount results in an overflow when the cipher name is printed, because the last character in the struct ecryptfs_key_tfm's cipher_name string was never zeroed. Signed-off-by: Eric Sandeen <[EMAIL PROTECTED]> Acked-by: Michael Halcrow <[EMAIL PROTECTED]> Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]> --- diff --git a/fs/ecryptfs/crypto.c b/fs/ecryptfs/crypto.c index bbed2fd..67e8b16 100644 --- a/fs/ecryptfs/crypto.c +++ b/fs/ecryptfs/crypto.c @@ -1847,6 +1847,7 @@ ecryptfs_add_new_key_tfm(struct ecryptfs_key_tfm **key_tfm, char *cipher_name, mutex_init(&tmp_tfm->key_tfm_mutex); strncpy(tmp_tfm->cipher_name, cipher_name, ECRYPTFS_MAX_CIPHER_NAME_SIZE); + tmp_tfm->cipher_name[ECRYPTFS_MAX_CIPHER_NAME_SIZE] = '\0'; tmp_tfm->key_size = key_size; rc = ecryptfs_process_key_cipher(&tmp_tfm->key_tfm, tmp_tfm->cipher_name, -- Pierre Riteau
Re: No acpi0 on ASUS A7N8X Deluxe?
On Jan 7, 2008 2:30 PM, Markus Bergkvist <[EMAIL PROTECTED]> wrote:
> Thanks for the pointer! I totally missed those lines.
> I was only seeing the
>
> iic1: addr 0x48 ...
> and
> iic1: addr 0x49 ...
>
> lines. Last time we spoke those lines disappeared when asbtm0 and wbenv0
> appeared.
>
> Also, I get different output on those iic1 if asbtm0 and/or wbenv0 is
> found or not. Strange.
I think it is because it's a full dump of the iic data so you have the
values reported by sensors in there, which may change at any time.
>
> Setting the delay to 500 and both of the devices are found.
>
> /Markus
>
>
> Pierre Riteau wrote:
> > On Jan 7, 2008 9:13 AM, Markus Bergkvist <[EMAIL PROTECTED]> wrote:
> >> Markus Bergkvist wrote:
> >>> Pierre Riteau wrote:
> >>>> I noticed that increasing the delay in sys/dev/pci/nviic.c from 100
> >>>> to 500 fixes this problem but I haven't took the time to file a bug
> >>>> report yet.
> >>> Seems to work here too.
> >>>
> >> Just increasing the delay doesn't work here any longer on a recent
> >> -current, have tested increasing it to 5000 even. Anyone else
> >> experiencing this?
> >> dmesg below.
> >>
> >>
> >> /Markus
> >>
> >>
> >> OpenBSD 4.2-current (GENERIC) #2: Sun Jan 6 18:06:15 CET 2008
> >> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> >> cpu0: AMD Athlon(tm) XP 2400+ ("AuthenticAMD" 686-class, 256KB L2 cache)
> >> 2 GHz
> >> cpu0:
> >> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
> >> real mem = 1073250304 (1023MB)
> >> avail mem = 1029881856 (982MB)
> >> mainbus0 at root
> >> bios0 at mainbus0: AT/286+ BIOS, date 09/14/04, BIOS32 rev. 0 @ 0xfb470,
> >> SMBIOS rev. 2.2 @ 0xf (43 entries)
> >> bios0: vendor Phoenix Technologies, LTD version "ASUS A7N8X Deluxe ACPI
> >> BIOS Rev 1008" date 09/14/2004
> >> bios0: ASUSTeK Computer INC. A7N8X
> >> apm0 at bios0: Power Management spec V1.2 (slowidle)
> >> apm0: AC on, battery charge unknown
> >> acpi at bios0 function 0x0 not configured
> >> pcibios0 at bios0: rev 2.1 @ 0xf/0xdf84
> >> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdeb0/208 (11 entries)
> >> pcibios0: PCI Exclusive IRQs: 5 11 12
> >> pcibios0: no compatible PCI ICU found
> >> pcibios0: Warning, unable to fix up PCI interrupt routing
> >> pcibios0: PCI bus #3 is the last bus
> >> bios0: ROM list: 0xc/0xd000 0xd/0x4000! 0xd4000/0x1800
> >> 0xd6000/0x800
> >> cpu0 at mainbus0
> >> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> >> pchb0 at pci0 dev 0 function 0 "NVIDIA nForce2 PCI" rev 0xa2
> >> agp at pchb0 not configured
> >> "NVIDIA nForce2" rev 0xa2 at pci0 dev 0 function 1 not configured
> >> "NVIDIA nForce2" rev 0xa2 at pci0 dev 0 function 2 not configured
> >> "NVIDIA nForce2" rev 0xa2 at pci0 dev 0 function 3 not configured
> >> "NVIDIA nForce2" rev 0xa2 at pci0 dev 0 function 4 not configured
> >> "NVIDIA nForce2" rev 0xa2 at pci0 dev 0 function 5 not configured
> >> pcib0 at pci0 dev 1 function 0 "NVIDIA nForce2 ISA" rev 0xa3
> >> nviic0 at pci0 dev 1 function 1 "NVIDIA nForce2 SMBus" rev 0xa2
> >> iic0 at nviic0
> >> spdmem0 at iic0 addr 0x50: 256MB DDR SDRAM non-parity PC2700CL2.5
> >> spdmem1 at iic0 addr 0x51: 256MB DDR SDRAM non-parity PC2700CL2.5
> >> spdmem2 at iic0 addr 0x52: 512MB DDR SDRAM non-parity PC2700CL2.5
> >> iic1 at nviic0
> >> asbtm0 at iic1 addr 0x2d
> >> wbenv0 at iic1 addr 0x2e: W83L785TS-L
> >> lm1 at iic1 addr 0x2f: W83791D
> >> iic1: addr 0x48 00=7f 01=00 02=4b 04=7f 05=08 06=4b 08=7f 09=08 0a=4b
> >> 0b=50 0c=7f 0e=4b 0f=50 10=7f 12=4b 13=50 14=7f 16=4b 17=50 18=7f 1a=4b
> >> 1b=50 1c=7f 1e=4b 1f=50 20=7f 22=4b 23=50 24=7f 26=4b 27=50 28=7f 2a=4b
> >> 2b=50 2c=7f 2e=4b 2f=50 30=7f 32=4b 33=50 34=7f 36=4b 37=50 38=7f 3a=4b
> >> 3b=50 3c=7f 3e=4b 3f=50 40=7f 42=4b 43=50 44=7f 46=4b 47=50 4a=4b 4b=50
> >> 4d=08 4e=4b 4f=50 50=7f 52=4b 53=50 54=7f 56=4b 57=50 58=7f 5a=4b 5b=50
> >> 5c=7f 5e=4b 5f=50 60=7f 62=4b 63=50 64=7f 66=4b 67=50 68=7f 6a=4b 6b=50
> >> 6c=7f 6e=4b 6f=50 70=7f 72=4b 73=50 74=7f 76=4b 77=50 78=7f 7a=4b 7b=50
> >> 7c=7f 7e=4b 7f=50 80=7f 82=4b 83=50 84=7f 86=4b 87=50 88=7f 8a=4b 8b=50
> >>
Re: ksh / csh / jobs discrepancy
Forgot to Cc: [EMAIL PROTECTED] On Jan 11, 2008 8:02 PM, Lars Noodin <[EMAIL PROTECTED]> wrote: > Jason McIntyre wrote: > ... > > generally speaking, the docs have a bias towards ksh, since ksh is the > > default shell. i'm not sure that that means having jobs(1) be a link to > > csh(1) is wrong though. if it points to ksh(1), csh users lose out. and > > vice versa. > > Ok. It's not a big deal either way, just that since OpenBSD defaults to > ksh, there is a reason to have the built-in shell commands default to ksh. > > What about saving space by using a symlink instead? Saving space? It is already a hardlink (check the inode numbers). > > Regards > -Lars > > A solution would be to make a dummy page for built-in commands, and in this page tell the user to lookup the manpage of the shell he is using. But there is the problem of collision between built-in commands and binaries (e.g. time). So I think Jason's fix is better: drop the MLINKs, and tell the user to read the manpage of his shell in help(1) (I think that stuff doesn't belong in afterboot(8)). -- Pierre Riteau
Re: azalia0 on hp nx7300
On Jan 14, 2008 12:38 AM, Bachman Kharazmi <[EMAIL PROTECTED]> wrote: > > On 13/01/2008, Deanna Phillips <[EMAIL PROTECTED]> wrote: > > Bachman Kharazmi writes: > > > > > OpenBSD 4.2 (GENERIC) #375: Tue Aug 28 10:38:44 MDT 2007 > > > [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC > > > > Please try with -current. > OK, I've spent some time trying with a CURRENT snapshot. Right after > the boot prompt when the kernel starts executing the laptop reboots. > bsd.rd does work, so something in bsd trigger a reboot :( > I don't have any usb/serial dongle at home so I can't debug this at > the moment. But are there anything you can think of that might cause > the resets in bsd which can be enabled/disabled? > /Bachman > > I would bet on acpi. It is enabled now, it was not enabled in 4.2. Try "disable acpi" after a boot -c. -- Pierre Riteau
Re: PERC 4/DI RAID controller on OBSD - best practice?
On Jan 15, 2008 8:17 PM, Nick Holland <[EMAIL PROTECTED]> wrote: > Matt wrote: > > Hi all, > > > > I got hold of an older Dell server with a PERC 4/DI raid controller, > > including 2 SCSI disks. I found the docs over at Dell. > > Am I right in understanding once I have my array in place through the > > BIOS the OpenBSD OS has nothing to do with the RAID setup? > > setup, no. > however, "bioctl ami0" will tell you how it is doing, and will permit > you to make certain configuration changes on the fly. > > For example, if you get a third disk, you can install it, and mark it as > a "hot spare" using bioctl. > > (just happen to be working with one of these right now. :) > > > Or should I leave the bios setup alone and work directly through OpenBSD > > (if possible at all)..? > > you can't establish the basic array via bioctl, but you can do a lot > of maintenance with it. > > > Not sure, I've only done software RAID setups before and am kind of > > confused here, especially because a lot of older talk on misc@ about > > these particular controllers. > > To put it more simple; what is best / suggested practice with this thing > > for mirroring? > > > > Any pointers / docs are appreciated- Thanks! > > GET TO KNOW THE THING BEFORE YOU GO INTO PRODUCTION WITH IT. Your task > is not complete when it is configured. You have to know how to detect a > failure, replace a failed drive, move drives to a new controller, etc. > Don't have a spare controller? How will you get your data off if the > controller fails? If you DO have a spare, how do you use it? If you > think it's easy or magic happens, you may end up in big trouble. > > btw: at least in my case, the PE2800 with a 4/Di card has no beeper. If > the drive fails, you either need bioctl to tell you or notice the color > change on the display of the machine. "bioctl ami0" makes a really good > line in your daily.local file... > > Nick. > > I've never used such hardware, but isn't sensorsd a good tool to monitor the drives attached? ami(4) tells me that disk status is exposed under hw.sensors. -- Pierre Riteau
Re: getopt(3) differences OpenBSD/GNU
On Jan 16, 2008 10:35 PM, Sebastian Reitenbach
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> I run into troubles with getopt(3). the test program below shows the
> problem. It produces different output on Linux and OpenBSD, when it is
> called like this on Linux it looks like this:
>
> ./a.out asdf -n
> option char: 110, n
>
> on OpenBSD, getopt returns -1 and no output is shown.
> what would be the best way to make it work on OpenBSD?
Define POSIXLY_CORRECT in your Linux program to make it work like on OpenBSD ;)
See the getopt(3) on your Linux system for more details, but
basically, OpenBSD getopt(3) stops when it encounters the first
non-option argument, while GNU getopt(3) parses the whole argv array.
If you really need your "asdf" argument before the option, you can
parse it and do the argv++, argc-- dance before calling getopt(3).
Otherwise, just use ./a.out -n asdf.
>
> cheers
> Sebastian
>
> #include
> #include
> #include
>
> extern char *optarg;
> extern int opterr;
> extern int optind;
> extern int optopt;
> extern int optreset;
>
> int main (int argc, char **argv)
> {
> char *optstr = "mpn";
> int option_char;
> do
> {
> option_char = getopt(argc, argv, optstr);
> if (option_char == -1) {
> break;
> }
> switch (option_char) {
> case 'm':
> case 'p':
> case 'n':
> default:
> printf("option char: %i, %c\n",
> option_char, option_char);
> break;
> }
> } while (1);
>
> return 0;
> }
>
>
--
Pierre Riteau
Re: OpenCVS?
On 20 Jan 2008 10:15:15 -0800, Unix Fan <[EMAIL PROTECTED]> wrote: > Stuart Henderson wrote: > > > See for yourself: http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/cvs/ > > > > I'm slighly confused by something if the "cvs" command in OpenBSD 4.2 is > "OpenCVS", why does "cvs --help" refer to places like cvshome.org for updates > etc? > > > > -Nix Fan. > > Forgot to cc: misc... Sorry. The cvs version shipped with OpenBSD is still GNU CVS, even in -current. -- Pierre Riteau
Re: halt -p does not work with GENERIC.MP on 4.2-STABLE
On Jan 25, 2008 9:13 AM, Nicolas Letellier <[EMAIL PROTECTED]> wrote: > I use OpenBSD 4.2-stable with a core2duo laptop. When I use GENERIC > kernel, 'halt -p' works perfectly. However, when I use GENERIC.MP, > 'halt -p' does not work and says : > > apm0: APM set power state: interface not connected (3) > the operating system has halted > Please press any key to reboot > You should try with -current. Much work was done on ACPI since 4.2. And I don't think the developers are interested in these kind of bugs in -stable. -- Pierre Riteau
Re: package tools misbehaving
On Feb 4, 2008 12:18 AM, Edd Barrett <[EMAIL PROTECTED]> wrote: > Hi, > > pkg_add appears to be exiting straight away without installing anything. > > ---8<--- > # pkg_info > # echo $PKG_PATH > ftp://ftp.rt.fm/pub/OpenBSD/snapshots/packages/i386/ > # pkg_add -i rxvt jwm zsh xpdf vim mplayer pidgin silc irssi feh > Ambiguous: choose package for vim > 0: > 1: vim-7.1.175-gtk2 > 2: vim-7.1.175-no_x11 > Your choice: 1 > Ambiguous: choose package for mplayer > 0: > 1: mplayer-1.0pre8p17 > 2: mplayer-1.0pre8p17-no_x11 > 3: mplayer-1.0pre8p17-sdl > Your choice: 1 > Ambiguous: choose package for pidgin > 0: > 1: pidgin-2.3.1p0 > 2: pidgin-2.3.1p0-gtkspell > Your choice: 1 > Can't resolve silc > Ambiguous: choose package for irssi > 0: > 1: irssi-0.8.12p1 > 2: irssi-0.8.12p1-socks > Your choice: 1 > # > ---8<--- > > Is anyone else experiencing this? > > -- > > Best Regards > > Edd > > http://students.dec.bournemouth.ac.uk/ebarrett > > You should try with the -v option to get more details about what is going on. -v Turn on verbose output. Several -v turn on more verbose output. -- Pierre Riteau
Re: slow network
On Feb 4, 2008 9:18 PM, Gabri Mati <[EMAIL PROTECTED]> wrote: > Mon, 4 Feb 2008 14:10:37 -0600 (CST) -n > "L. V. Lammert" <[EMAIL PROTECTED]> C-rta: > > > > On Mon, 4 Feb 2008, [UTF-8] GC!bri MC!tC) wrote: > > > > > Hey there! > > > > > > I've installed OpenBSD 4.2 on a Compaq DL580 machine and i dunno why > > > but the initial phase of the network connections are really slow. > > > The machine is behing a linksys router with fix ip address, > > > resolv.conf set up correclty. It has an intel pro 100 ethernet > > > card. PF is disabled. If i try to reach it with ssh from the local > > > network i have to wait for the password prompt for 30 seconds but > > > after that the data flow is normal. When i give the netstat command > > > i only see the columns name and then it halts. Though other > > > machines on the network can be accessed normally. > > > Do You know why can this be happening? > > > > > > Thank You! > > > > > Sounds like your DNS server is not resolving? > > > > Lee > > > Then why is it slow on the local network using ip addresses? :) > > > -- > Gabri Mate > [EMAIL PROTECTED] > DUOSOL Bt. > http://www.duosol.hu > > [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] > > I suspect DNS not resolving too. And for your ssh connection freezing when using an IP address, maybe because of UseDNS Specifies whether sshd should lookup the remote host name and check that the resolved host name for the remote IP address maps back to the very same IP address. The default is ``yes''. -- Pierre Riteau
Re: marvell yukon GigE freezes the bootup
A first start would be to tell us what version of OpenBSD you are running, and to send a full dmesg. If you are not running -current, you should try a snapshot. On 2/6/08, LIVAI Daniel <[EMAIL PROTECTED]> wrote: > Hi! > > I have an Acer 7520G notebook with a Marvell Yukon gigabit ethernet card > onboard. After the amd64 install, I get until this line with the > bootup, and then nothing, it hangs: > > [...] > mskc0 at pci2 dev 0 function 0 "Marvell Yukon 88E8071" rev 0x15 > > Tried with both bsd and bsd.mp. > > I see on the msk(4) page, that the marvell devices are supported up to > 88E806x. Is this 88E807 all that different from the previous ones? I > would be more than happy to test anything and everything (patches, > drivers etc...), provide more information, or answer any questions. > > Thanks! > > Daniel > > -- > LIVAI Daniel > Public key ID = 4AC0A4B1 > Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1 > > -- Pierre Riteau
Re: /usr/include/ headers in the kernel source
On Feb 6, 2008 9:00 PM, Joco Salvatti <[EMAIL PROTECTED]> wrote: > Hi all, > > I've downloaded the OpenBSD 4.2 current source tree to my 4.2 release > machine. Then I've made small modifications to my kernel, but when I > run make depend I get the following error messages: > > /usr/src/sys/kern/kern_sysctl.c:91:21: ifaddrs.h: No such file or directory > /usr/src/sys/kern/kern_sysctl.c:92:17: err.h: No such file or directory > /usr/src/sys/kern/kern_sysctl.c:93:19: ctype.h: No such file or directory > > I've already read style(9) and even made some search on the web, but I > could not find a thing. So I would like to hear from you where I could > find information about this issue or if it is possible to use > /usr/include headers in the kernel (I guess so because I've seen this > in other kernel files) adnd if it links to user libraries. > > Thanks in advance for the time wasted reading this e-mail. > > -- > Joao Salvatti > Undergraduating in Computer Science > Federal University of Para - UFPA > web: http://www.openbsd-pa.org > e-mail: [EMAIL PROTECTED] > > You should upgrade to a snapshot before. This is in the FAQ... -- Pierre Riteau
Re: Hot spare synchronisation?
On Feb 8, 2008 10:32 PM, Matt <[EMAIL PROTECTED]> wrote: > Stuart Henderson schreef: > > On 2008/02/08 20:48, Matt wrote: > > > >> Alexander Hall schreef: > >> > >>> Marti Martinez wrote: > >>> > >>>> Do the rsync over SSH -- unless you don't allow root ssh access? > >>>> > >>> I think that was the "solution" Matt tried to avoid. I suppose he does > >>> not seem confident with (automated) root access/logins from other boxes. > >>> > >>> > >> I'd like to avoid root access as OpenBSD disables it by default for a > >> good reason. > >> > > > > some OS do that, but not OpenBSD: > > > > # The strategy used for options in the default sshd_config shipped with > > # OpenSSH is to specify options with their default value where > > # possible, but leave them commented. Uncommented options change a > > # default value. > > > > #PermitRootLogin yes > > > > Would you believe I have been using OpenBSD for years and have *never* > noticed this? > And yes, I did read afterboot once or twice - but clearly not well > enough. (just checked...) > Always thought uncommenting that specific line made root logins > possible. Weird. > Assumption, mother of etc. > > Makes me wonder why it is enabled by default though. > > To check who is actually reading afterboot(8) ;) -- Pierre Riteau
Re: rtorrent + OpenBSD = freeze
On Tue, Feb 19, 2008 at 08:08:50PM +0100, Jon Olsson wrote: > On Tue, Feb 19, 2008 at 06:11:12PM +0100, Daniel Andersson wrote: > > I don't think it is the NICs, I bought two Intel PRO/1000 something. > > FWIW, I also saw this freeze while using rtorrent, and I also have > an Intel PRO/1000 NIC: > > em0 at pci0 dev 2 function 0 "Intel PRO/1000MT (82540EM)" rev 0x02: irq 10, > address 00:c0:9f:1e:26:2c > > I have no more data than this, it's just a mere 'me too' and one thing > we have in common (the NIC). > > Cheers, > -- > Jon > I have seen this freeze with both xl(4) and nfe(4). -- Pierre Riteau
Re: -current, softraid on root?
Hijacking this thread to ask another question related to softraid: is it possible to disassemble a RAID volume? I wanted to test RAID0, typed 1 instead, searched the manpages... seems the only solution is wiping metadata and rebooting? On Tue, Feb 19, 2008 at 11:55:44AM -0600, Marco Peereboom wrote: > Enabled are RAID 0 and RAID 1. RAID 0 is for all intents and purposes > good to go. RAID 1 misses rebuilds (hi henning!) at this moment. > Crypto is being evaluated to ensure the crypto is strong enough to be > trusted. It will remain disabled until that evaluation is complete. > More on that one later. > > RAID 5 is a post 4.3 item for me. > > On Tue, Feb 19, 2008 at 12:22:42PM -0500, bofh wrote: > > On Feb 18, 2008 10:17 PM, Marco Peereboom <[EMAIL PROTECTED]> wrote: > > > Not just yet! > > > > > > You can boot of something non-softraid and do the rest on softraid. > > > This will be a feature I will work on once I have the initial 3 > > > disciplines ready and we can handle foreign metadata. Then I'll work on > > > booting/rooting a softraid. My todo list is still on my website if > > > you'd like to contribute. > > > > Ah! Unfortunately, my coding-fu is non-existent. I take it you > > want raid-0, raid-1 and raid-5? OK. I think I'm going to just live > > with a 2pm nightly rsync to the backup drive. :) > > > > > > -- > > http://www.glumbert.com/media/shift > > http://www.youtube.com/watch?v=tGvHNNOLnCk > > "This officer's men seem to follow him merely out of idle curiosity." > > -- Sandhurst officer cadet evaluation. > > "Securing an environment of Windows platforms from abuse - external or > > internal - is akin to trying to install sprinklers in a fireworks > > factory where smoking on the job is permitted." -- Gene Spafford > > learn french: http://www.youtube.com/watch?v=j1G-3laJJP0&feature=related
Re: Watching the prgress of dd if=drive1 of=drive2
On Sat, Feb 23, 2008 at 9:15 PM, Jon <[EMAIL PROTECTED]> wrote: > I'm using dd to clone a drive. How can I watch the progress of this or > see the transfer rate in real time? > > >From the manpage: If dd receives a SIGINFO (see the ``status'' argument for stty(1)) sig- nal, the current input and output block counts will be written to the standard error output in the same format as the standard completion mes- sage. -- Pierre Riteau
Re: xenocara source
On Sat, Mar 01, 2008 at 12:13:53PM +, Stuart Henderson wrote: > On 2008-03-01, hyjial <[EMAIL PROTECTED]> wrote: > > You can simply add a newline like > > /xenocara/// # I don't really remember the syntax > > in the list of directories in a file under > > /usr/src/CVS thus making all of your sources updated > > at once without any error. > > Ah, perhaps I did that at some point then... > If you checkout xenocara with cvs it will add the entry for you. But of course it won't happen if you just untar xenocara.tar.gz. -- Pierre Riteau
Re: floppy.fs
On Fri, Mar 7, 2008 at 1:10 AM, Edd Barrett <[EMAIL PROTECTED]> wrote: > Alright Theo and misc@, > > > On Wed, Mar 5, 2008 at 6:55 PM, Theo de Raadt <[EMAIL PROTECTED]> wrote: > > There is one thing that some people out there could work on. Noone > > in our group is currently working on it, and it would be nice. > > I had another idea recently. > > I need to disable apm for proper power management on my i386. > > It would be nice if the installer offered to run config(8) so that you > can rip out apm/acpi if so required. I always forget and then I > require a fsck after a halt -p as it crashes the system :( > > Thoughts? > > -- > > Best Regards > > Edd > > http://students.dec.bournemouth.ac.uk/ebarrett > > I have an upgrade.site on my disk for that. You can create an install.site too, but you will need to use your own ftp server to get it. -- Pierre Riteau
Re: serial console on macbook?
On 2/19/07, Otto Moerbeek <[EMAIL PROTECTED]> wrote: On Mon, 19 Feb 2007, Paul de Weerd wrote: > On Sun, Feb 18, 2007 at 08:27:54PM -0800, Ben Calvert wrote: > | can't install 4.0 or snapshots on my macbook due to what appear to be > | issues with the usb controller. ( lots of errors about the usb > | controller, and the keyboard is nonresponsive... no capslock light, > | no input ) > | > | does anyone have any ideas about how to capture the dmesg so i can > | submit? > > I'm reading MacBook, so I think you're not talking about the MacBook > Pro (just to make sure). I had similar issues with the MacBook Pro, so > maybe this helps. > > I got things working on the MacBook Pro. See [1]. This required the > latest snapshot (where you can type at the bootprompt, some changes > went in to support this) and enabling acpi in UKC. What I did > initially (burn a CD with a bsd.rd kernel that I had config'd on > another machine to enable acpi) should not be necessary anymore. > > On a side note, audio *does* work albeit *extremely* low volume. If I > crank everything up in mixerctl I can barely hear something. You may > experience similar issues on your MacBook. > > And X looks like it'll be a while. There's no new Radeon support in > xorg yet and I've found no one working on a driver. It works with > vesa(4) for now, but that doesn't support the 1440x900 resolution of > the machine. > > Ben, let us know how you proceed with the MacBook. The MacBook is different from the MacBook Pro. The first sign of trouble is that the UKC prompt doesn't work. It won't accept input. When booting without going to UKC, it shows various USB related error messages and the after a very long time comes to the install prompt, which doesn't accept input either. This happens both with an acpi-enabled bsd.rd and the default bsd.rd. I didn't have a chanche yet to diagnose this further. -Otto One easy method to install OpenBSD on a Macbook is to plug an external usb keyboard before booting on the CD. Booting takes a while but then you can use the external keyboard to install OpenBSD. Be sure not to use the network, msk0 will hang the machine without some acpi features IIRC. Then reboot, you will get errors about ehci, ignore them and still use the external keyboard. Compile a GENERIC.MP kernel with all acpi option enabled on another machine and copy it to the macbook with a CD, or grab -current sources on CD from another machine and copy them to the macbook. Reboot and enjoy, built-in keyboard works, ethernet (msk0) works, usb sticks work. But wireless device (ath0) doesn't. I haven't tried X11 for a while but I think it works too. Pierre Riteau
Re: New W83627HF Watchdog Driver
On 4/27/07, Jon Steel <[EMAIL PROTECTED]> wrote:
Thanks for the pointers. Heres the update.
And just a quick question for anybody, why do some of the macros in the
OS look like:
#define DEBUG(x) do { ... } while(0);
Is this some kind of compiler trick?
style(9) :
If the macro encapsulates a compound statement, enclose it in a ``do''
loop, so that it can safely be used in ``if'' statements.
Thanks Again
Jonathan Steel
Re: Lenovo 8744-J2U - several questions
Le 7 ao{t 07 ` 05:23, Frank Bax a icrit :
At 06:26 PM 8/6/07, Matthieu Herrb wrote:
On 8/6/07, Frank Bax <[EMAIL PROTECTED]> wrote:
> Just got a new Lenovo 8744-J2U laptop and installed the Aug.1
snapshot:
>
> 1) When I shutdown X, text resolution is messed up. Chars are
bigger, they
> are 40 per line, with wrap. All Ctrl-Alt-Fn sessions are
affected. If I
> issue a command like 'date', then hit enter several time, I find
that the
> command and its output are finally visible.
Since you're using the vesa driver, it means that the VESA BIOS on
your laptop is broken.
Check for updates on Lenovo's web site.
> 2) ATI adapter is not recognized. Changing depth to 24 works;
but I can't
> seem to change resolution - always comes up 1280x1024; but this
is a 15.4
> widescreen display; which i believe should run at 1680x1050.
Again, broken bios. Lenovo should provide a bios with resolutions
matching the physical size of the screen.
Try using i915resolution from ports. It has been reported to work
with
other BIOSes too.
Thanks for the prompt response. I updated BIOS from 1.08 to 1.11;
one line changed in dmesg.
$ diff dmesg_0803.txt dmesg_0806.txt
8c8
< bios0 at mainbus0: AT/286+ BIOS, date 04/30/07, BIOS32 rev. 0 @
0xfd6b0, SMBIOS rev. 2.4 @ 0xe0010 (68 entries)
---
> bios0 at mainbus0: AT/286+ BIOS, date 07/13/07, BIOS32 rev. 0 @
0xfd6b0, SMBIOS rev. 2.4 @ 0xe0010 (68 entries)
Still no change on initial problems though.
I tried 915resolution, but I'm thinking it's not compatible:
$ sudo /usr/local/sbin/915resolution -l
Intel 800/900 Series VBIOS Hack : version 0.5.2
Unable to open the BIOS file: Operation not permitted
IIRC it must be run in secure level -1.
From the description of the port :
Because 915resolution requires write access to /dev/mem, the system
must be
at a securelevel <= 0.
Pierre Riteau
> vga1 at pci1 dev 0 function 0 vendor "ATI", unknown product
0x71d4 rev 0x00
Oh and I forgot: this is a Mobility FireGL V5250, which is indeed not
supported by the current X.Org ati driver. It should be supported by
the new 'avivo' driver, but this driver is not yet available for
OpenBSD.
Is there someplace where I can monitor OpenBSD status of this?
Re: uvm_fault on Asus M2V-MX
Le 12 ao{t 07 ` 02:18, Soner Tari a icrit :
Today I was trying to install OpenBSD/amd64 4.1 GENERIC on a system
with
the following motherboard:
http://www.asus.com/products4.aspx?
modelmenu=2&model=1418&l1=3&l2=101&l3=324&l4=0
But during installation I got the following blue lines (which I've
noted
on a piece of paper by hand):
uvm_fault (0xfe80 0a2de810, 0x7f8000267000, 0, 1) -> e
fatal page fault in supervisor mode
trap type 6 code 0 rip 802540a7 cs 8 vflags 10216 cr2
7f8000267fb0 cpl1 0 rsp 800067015c80
syncing discs ...done
At which time system halts, or becomes unresponsive. (Actually, this
error occurs during my custom install script, in site41.tgz, after
usual
OpenBSD installation finishes.)
I was suspicious about pciide, but VIA 8237A is in the supported
hardware list.
So I've installed OpenBSD on the same HD, but now on another hardware,
then inserted the HD back into this system again, but after a
couple of
services start, I got another uvm_fault error (it's similar but not
the
same, if I recall correctly), and the system hangs.
Some of the other parts are: Athlon64 4200+ X2, Kingston 1GB RAM, WD
250GB SATA2 HD.
I've disabled many options in the bios, but nothing changed. If I
cannot
find a solution, the board will be returned.
Does anybody else use this motherboard too? Do you have any
problems? If
you had a similar issue, how did you fix it, any special bios
settings?
What could be the source of the uvm_fault error: motherboard, RAM, or
even the processor itself?
Otherwise I have installed OpenBSD with my custom script on other
amd64
hardware without major problems.
I would appreciate any help.
Maybe this is due to bad memory ? Test with memtest86+:
http://www.memtest.org
You should try the snapshots to see if the problem has been fixed and
will be
fixed for 4.2.
You could also try with acpi enabled and/or GENERIC.MP.
To enable acpi: at the boot prompt, type boot -c, then:
enable acpi
enable acpiec
quit
and the kernel will boot with acpi.
To boot the MULTIPROCESSOR kernel, boot bsd.mp (and you can enable acpi
on this one too).
Pierre Riteau
Re: unstable and multiple reboot for 4.2 on Sun X4100 M2 with ACPI enable on AMD64 bsd.mp with SAS RAID 1 setup.
Le 12 sept. 07 ` 23:42, Daniel Ouellet a icrit : Here is the new dmesg for current. So far the boot process is much faster and do not hang anymore. I am doing install on three more boxes now and will do a bunch of reboot cycles to see the end results. Still some acpi not configure in the dmesg, but so far does look better. Those devices (acpicpu, acpibtn...) are not compiled in GENERIC or GENERIC.MP, if you want to test them you must compile your own kernel. Also, note this is on the latest bios and ilom as well as the latest SAS drivers as well. Not the one that comes directly from Sun. ILOM: 1.1.8 BIOS: 39, not the standard 34 version. SAS: 1.16.40, not the 1.16.00 More later. Daniel == OpenBSD 4.2-current (GENERIC.MP) #1384: Tue Sep 11 22:09:44 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/ GENERIC.MP real mem = 3757625344 (3583MB) avail mem = 3635904512 (3467MB) User Kernel Config UKC> enable acpi 270 acpi0 enabled UKC> exit Continuing... mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xfbd50 (70 entries) bios0: vendor American Megatrends Inc. version "0ABJX039" date 04/11/2007 bios0: Sun Microsystems Sun Fire X4100 M2 acpi0 at mainbus0: rev 2 acpi0: tables DSDT FACP APIC SPCR SLIT OEMB HPET IPET SRAT SSDT acpitimer at acpi0 not configured acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Dual-Core AMD Opteron(tm) Processor 2216, 2393.94 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE3 6,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG, 3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Dual-Core AMD Opteron(tm) Processor 2216, 2393.64 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE3 6,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG, 3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu2 at mainbus0: apid 2 (application processor) cpu2: Dual-Core AMD Opteron(tm) Processor 2216, 2393.64 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE3 6,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG, 3DNOW2,3DNOW cpu2: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu2: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu2: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu3 at mainbus0: apid 3 (application processor) cpu3: Dual-Core AMD Opteron(tm) Processor 2216, 2393.64 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE3 6,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG, 3DNOW2,3DNOW cpu3: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu3: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu3: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0 apid 15 pa 0xfec0, version 11, 24 pins ioapic1 at mainbus0 apid 16 pa 0xfeafd000, version 11, 7 pins ioapic1: misconfigured as apic 0, can't remap to apid 16 ioapic2 at mainbus0 apid 17 pa 0xfeafc000, version 11, 7 pins ioapic2: misconfigured as apic 1, can't remap to apid 17 ioapic3 at mainbus0 apid 14 pa 0xfeaff000, version 11, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpiprt2 at acpi0: bus 4 (P0P4) acpiprt3 at acpi0: bus 5 (P0P5) acpiprt4 at acpi0: bus 128 (PCIB) acpiprt5 at acpi0: bus 133 (POGA) acpiprt6 at acpi0: bus 134 (POGB) acpiprt7 at acpi0: bus 131 (BR5D) acpiprt8 at acpi0: bus 132 (BR5E) acpiprt9 at acpi0: bus 255 (PCIC) acpiprt10 at acpi0: bus -1 (POGA) acpiprt11 at acpi0: bus -1 (POGB) acpicpu at acpi0 not configured acpicpu at acpi0 not configured acpicpu at acpi0 not configured acpicpu at acpi0 not configured acpibtn at acpi0 not configured ipmi0 at mainbus0: version 1.5 interface KCS iobase 0xca4/2 spacing 1 pci0 at mainbus0 bus 0: configuration mode 1 "NVIDIA nForce4 DDR" rev 0xa3 at pci0 dev 0 function 0 not configured pcib0 at pci0 dev 1 function 0 "NVIDIA nForce4 ISA" rev 0xa3 nviic0 at pci0 dev 1 function 1 "NVIDIA nForce4 SMBus" rev 0xa2 iic0 at nviic0: disabled to avoid ipmi0 interactions iic1 at nviic0: disabled to avoid ipmi0 interactions ohci0 at pci0 dev 2 function 0 "NVIDIA nForce4 USB" rev 0xa2: apic 15 int 11 (irq 11), version 1.0, legacy support ehci0 at pci0 dev 2 function 1 "NVIDIA nForce4 USB" rev 0xa3: apic 15 int 5
Re: Thank You OpenBSD
Le 16 sept. 07 ` 01:25, Sean Darby a icrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello fellows from the OpenBSD community, I just wanted to stop and smell the roses. I occasionally play around with other systems, of the Unix variety and, for the sake of seeing things through the looking glass, taking an outside perspective, the occasional logging into MS Windows. The use of MS Windows and so many Linux systems definitely puts me into perspective. So much of it is, for lack of a better word, crap. I suppose you can say I'm still "a lot like a Linux guy except I have kissed girls". ;) I focus on the glass being half full rather than half empty (love Unix more than hate MS Windows). I'm simply writing this message to say that I am thankful for OpenBSD. Of the various systems we have to choose from - a few wonderful and powerful ones and many that are frightening and senseless - it helps to remind oneself of things like, "secure by default" and... "Free, Functional, and Secure." Security was the original reason for my change to OpenBSD but I have since discovered there is so much more than that. There are so many features, one can quickly become overwhelmed. It shocked me to discover all of the supported architectures/ platforms. Use of PF is, simply putting it: wow! And OpenSSH... how much better can it get?! It just keeps getting better! What else is there? A lot! I don't even know all of the greatness in it. (Thought I'd be glad to be enlightened of even more tasty features.) I'm learning that it seems pointless to be shocked at the amazing features: for OpenBSD has established a higher standard than the rest. These high standards are only to be expected, and that's certainly something to be thankful for. I'm no programmer but can tell that this system has the famously claimed "high quality code". No doubt about it. I'm just an average guy who is working on the final stages of his doctorate in music. It feels good to know that I'm running a system that I can fully trust and depend on. With the reputation of the system and if that continues, I will certainly continue to use OpenBSD throughout my entire career on at least one of my computers. Going back to those three words, I am honored to use a system that is secure, functional and *free*! It's hard to say which of the three I like having more, I don't think I could do without any of them. Was it Benjamin Franklin who said this general message? "They that can give up liberty to obtain a little temporary safety deserve neither liberty nor safety." Question: Is it true there was a developer's comment line in the Linux kernel that said, "Does this belong here?" http://www.forbes.com/intelligentinfrastructure/2005/06/16/linux-bsd- unix-cz_dl_0616theo.html It was in a forbes.com interview of Theo, but it was not Theo speaking. I don't know what file contained this comment, but it can be significant or insignificant, depending of what the code is doing. You can find many XXX in the OpenBSD kernel too, I don't think this comment alone, without any details, shows anything about Linux. If you want to bash Linux, there are better arguments than that :) Thank you OpenBSD. - -- Gabriel Sean Darby Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG7Gn6TyBbgn+aIvwRAkvbAKC6RtJn1Mot1ilxfT5cJ0olTsJj5QCfdf/t sfV7BJd9YNU9pKm+RVGpeeU= =1Plq -END PGP SIGNATURE-
Re: problems with ral0 and OBSD 4.0
Le 18 sept. 07 ` 18:41, Alessandro Roncari a icrit : Hello I have the following issue with ralink wireless card, acting in hostap mode hardware: ral-rt2561s board acting as access point on a Soekris Net4501, running OpenBSD 4.0. can't seem to make it work like it should, even with a 9dBi antenna the signal is very weak and much weaker than my old netgear AP. weak and unstable everything is set up correctly # dmesg | grep ral0 ral0 at pci0 dev 16 function 0 "Ralink RT2561S" rev 0x00: irq 10, address 00:12:0e:61:80:98 ral0: MAC/BBP RT2561C, RF RT5225 ral0: flags=8843 mtu 1500 lladdr 00:12:0e:61:80:98 media: IEEE802.11 autoselect hostap (autoselect mode 11a hostap) status: active ieee80211: nwid xxx chan 11 bssid 00:12:0e:61:80:98 nwkey 100dBm inet 192.168.x.x netmask 0xff00 broadcast 192.168.x.xxx inet6 fe80::212:eff:fe61:8098%ral0 prefixlen 64 scopeid 0x1 but it seems it's all working at very small % of its power. question is: is this a known bug in the driver?? or is there anything I could do to improve the situation? Update to OpenBSD 4.1 or -current, there were some changes in ral(4) code. e.g. replace rssadapt(9) with amrr for automatic rate control. as a side-effect, this should fix all the "bogus xmit rate" panics users have been complaining about for some time when operating in HostAP mode. Thanks, Alessandro Soekris docs & rulesets http://sekureshell.altervista.org
Re: OpenCVS
Le 20 sept. 07 ` 07:10, Karl Sjvdahl - dunceor a icrit : On 9/19/07, Adrian Fisher <[EMAIL PROTECTED]> wrote: 1. Who here knows about OpenCVS? 2. How is it used? 3. When will it be released? Will it be released at the same time as 4.2? Regards, A. 1. OpenCVS is developed by several of the OpenBSD developers, those I see commit most is xsa@, niallo@, ray@ and lateley a lot by [EMAIL PROTECTED] You forgot [EMAIL PROTECTED] 2. It's a replacement for GNU CVS so it's compatiable with it. Their goal is first to make sure everything supported in GNU CVS should be supported in OpenCVS. 3. Do not know about release, probobly not ready for prime time yet. But I'm sure it needs testers, that will speed up the development. Ps. I'm not a developer. ds. br Dunceor
Re: Thank you developers... 4.2 arrived in the mail today
Le 9 oct. 07 ` 17:02, Edd Barrett a icrit : On 05/10/2007, Chad M Stewart <[EMAIL PROTECTED]> wrote: My 4.2 CDs and t-shirt arrived in the mail today (near Buffalo, NY) and this has to be the earliest I've ever gotten mine. I hope that is more of an indication of my getting my order in early, than the number of CD orders being that low. Here in the UK we have postal strikes grinding the whole mail system to a halt (-p?). No chance of getting anything in the UK anytime soon. :( Aren't all European orders sent by UPS? -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: OpenBSD 4.2-current | ASUS P5VD2-X and E2140 problems
Le 8 oct. 07 ` 17:44, [EMAIL PROTECTED] a icrit :
Hi guys,
I ask at misc because I#m unsure if these problems are known.
During reading the CHangelog I noticed the ALC883 Chip was added to
Azalia.
Well this Chip is at this Motherboard but I can't get it working.
The BIOS supports to either set it into the HDA Mode or into the AC97
mode. neither works (wont even get displayed in the dmesg).
A 3rd mode for Vista compatibility wa salso checked with no success.
Except this OpenBSD 4.2-current (and so 4.2) does boot fine.
I noticed just 2 further issues.
1. The Intel E2140 supports SpeedStep but it isn't ntoiced (even after
activation in the BIOS).
2. SMP doesn#t work
- I tried also twith ACPI-ENABLE
I just wanna know: Is there a solution known for the last 2 things?
Does somebody own the same Board (or familiar with VIA 890!).
Single-Core works fine.
I may would have the possibility to change the Board (to a MSI MSI
P4M890M
Rev 1.2).
I need to replace a Desktop Board so the MSI would even provide
integrated
Grafic (wich is ok for this case).
So are these things Board related (well the Crash in SMP mode propably
isn't but the issue with the Soundchip may is) or maybe OpenBSD
related?
I have an Asrock motherboard with a VIA chipset (but not the same).
If I want my azalia device to be detected, I need to go in the BIOS
and change
it's PCI bus from 0x80 to 0x2 (there is an option for this).
Maybe your card has a similar setting?
Here's a dmesg with a generic Kernel from install42.iso
--
OpenBSD 4.2-current (GENERIC) #410: Fri Oct 5 22:31:12 MDT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Genuine Intel(R) CPU 2140 @ 1.60GHz ("GenuineIntel" 686-
class) 1.60 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE3
6,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-
CPL,EST,TM2,CX16,xTPR
real mem = 535261184 (510MB)
avail mem = 509779968 (486MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/29/07, BIOS32 rev. 0 @
0xf1d70,
SMBIOS rev. 2.4 @ 0xf (52 entries)
bios0: vendor Phoenix Technologies, LTD version "ASUS P5VD2-X ACPI
BIOS
Revision 0501" date 06/29/2007
bios0: ASUSTeK Computer INC. P5VD2-X
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 70102 dobusy 1 doidle 1
pcibios0 at bios0: rev 3.0 @ 0xf/0xdc94
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdad0/400 (23 entries)
pcibios0: PCI Exclusive IRQs: 5 10 11
pcibios0: PCI Interrupt Router at 000:17:0 ("VIA VT82C596A ISA" rev
0x00)
pcibios0: PCI bus #4 is the last bus
bios0: ROM list: 0xc/0xd000 0xd/0x3000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA P4M890 Host" rev 0x00
pchb1 at pci0 dev 0 function 1 "VIA P4M890 Host" rev 0x00
pchb2 at pci0 dev 0 function 2 "VIA P4M890 Host" rev 0x00
pchb3 at pci0 dev 0 function 3 "VIA P4M890 Host" rev 0x00
pchb4 at pci0 dev 0 function 4 "VIA P4M890 Host" rev 0x00
"VIA P4M890 IOAPIC" rev 0x00 at pci0 dev 0 function 5 not configured
pchb5 at pci0 dev 0 function 6 "VIA P4M890 Security" rev 0x00
pchb6 at pci0 dev 0 function 7 "VIA P4M890 Host" rev 0x00
ppb0 at pci0 dev 1 function 0 "VIA VT8377 AGP" rev 0x00
pci1 at ppb0 bus 1
ppb1 at pci0 dev 2 function 0 "VIA P4M890 PCI-PCI" rev 0x00
pci2 at ppb1 bus 2
vga1 at pci2 dev 0 function 0 "ATI Radeon X300" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
"ATI Radeon X300 Sec" rev 0x00 at pci2 dev 0 function 1 not configured
ppb2 at pci0 dev 3 function 0 "VIA P4M890 PCI-PCI" rev 0x00
pci3 at ppb2 bus 3
jmb0 at pci3 dev 0 function 0 "JMicron JMB363 IDE/SATA" rev 0x02
ahci0 at jmb0: irq 11, AHCI 1.0
scsibus0 at ahci0: 32 targets
pciide0 at jmb0: DMA, channel 0 wired to native-PCI, channel 1
wired to
native-PCI
pciide0: using irq 11 for native-PCI interrupt
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 disabled (no drives)
pciide1 at pci0 dev 15 function 0 "VIA VT8237A SATA" rev 0x80: DMA
pciide1: using irq 11 for native-PCI interrupt
pciide2 at pci0 dev 15 function 1 "VIA VT82C571 IDE" rev 0x07: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
wd0 at pciide2 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 117246MB, 240121728 sectors
wd0(pciide2:0:0): using PIO mode 4, DMA mode 2
atapiscsi0 at pciide2 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: SCSI0
5/cdrom removable
cd0(pciide2:1:0): using PIO mode 4, DMA mode 2
uhci0 at pci0 dev 16 function 0 "VIA VT83C572 USB" rev 0xa0: irq 5
uhci1 at pci0 dev 16 function 1 "VIA VT83C572 USB" rev 0xa0: irq 5
uhci2 at pci0 dev 16 function 2 "VIA VT83C572 USB" rev 0xa0: irq 5
uhci3 at pci0 dev 16 function 3 "VIA VT83C572 USB" rev 0xa0: irq 5
ehci0 at pci0 dev 16 function 4 "VIA VT6202 USB" rev 0x86: irq 5
usb0 at ehci0: USB revision 2.0
uhub0 at usb0: "VIA EHCI root hub", rev 2.00/1.00, addr 1
via
Re: No acpi0 on ASUS A7N8X Deluxe?
On Thu, Oct 18, 2007 at 04:35:38PM +0200, Markus Bergkvist wrote:
> Even though bios0 reports "ASUS A7N8X Deluxe ACPI BIOS" during boot, I
> see no acpi0 in the dmesg, w/o acpi enabled. Unsupported, or am I just not
> supposed to see a acpi0 device?
disable apm0 if you want to see use acpi.
> On the other hand, asbtm0 is found when acpi is enabled so I guess
> something is working as intended. Anyone care to explain?
I have the same motherboard and I noticed that devices on the iic bus
are not always detected. There is no causal link with acpi, you just
happened to see that behavior after enabling acpi but it would have
been the same without it.
I noticed that increasing the delay in sys/dev/pci/nviic.c from 100
to 500 fixes this problem but I haven't took the time to file a bug
report yet.
Pierre Riteau
>
> Below is a diff from dmesg with acpi disabled and enabled. And a complete
> dmesg.
>
> /Markus
>
>
> $ diff -u dmesg.boot_noacpi /var/run/dmesg.boot
> --- dmesg.boot_noacpi Thu Oct 18 16:06:18 2007
> +++ /var/run/dmesg.boot Thu Oct 18 16:18:22 2007
> @@ -33,8 +33,8 @@
> spdmem1 at iic0 addr 0x51: 256MB DDR SDRAM non-parity PC-2700CL2.5
> spdmem2 at iic0 addr 0x52: 512MB DDR SDRAM non-parity PC-2700CL2.5
> iic1 at nviic0
> +asbtm0 at iic1 addr 0x2d
> wbenv0 at iic1 addr 0x2e: W83L785TS-L
> -iic1: addr 0x48 04=7f 08=50 0b=50 0f=50 13=50 16=4b 1a=4b 1d=08 1e=4b
> 21=08 22=4b 25=08 26=4b 2a=4b 31=08 32=4b 35=08 36=4b 3a=4b 3d=08 3e=4b
> 42=4b 45=08 46=4b 4a=4b 4d=08 4e=4b 51=08 52=4b 54=7f 5a=4b 5b=50 61=08
> 62=4b 63=50 68=7f 6a=4b 6e=4b 70=7f 75=08 76=4b 78=7f 7d=08 7e=4b 80=7f
> 85=08 86=4b 88=7f 8d=08 8e=4b 90=7f 95=08 96=4b 97=50 9d=08 9e=4b 9f=50
> a5=08 a6=4b a7=50 b5=08 b6=4b b7=50 bd=08 be=4b bf=50 c5=08 c6=4b c7=50
> cc=7f ce=4b d3=50 d5=08 d6=4b da=4b dd=08 de=4b e1=08 e2=4b e5=08 e6=4b
> e8=7f ed=08 ee=4b ef=50 f5=08 f6=4b f7=50 fd=08 fe=4b ff=50
> ohci0 at pci0 dev 2 function 0 "NVIDIA nForce2 USB" rev 0xa3: irq 12,
> version 1.0, legacy support
> ohci1 at pci0 dev 2 function 1 "NVIDIA nForce2 USB" rev 0xa3: irq 12,
> version 1.0, legacy support
> ehci0 at pci0 dev 2 function 2 "NVIDIA nForce2 USB" rev 0xa3: irq 11
>
>
> OpenBSD 4.2-current (GENERIC) #0: Sat Oct 13 18:12:02 CEST 2007
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: AMD Athlon(tm) XP ("AuthenticAMD" 686-class, 256KB L2 cache) 1.20 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
> real mem = 1073250304 (1023MB)
> avail mem = 103640 (982MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 09/14/04, BIOS32 rev. 0 @ 0xfb470,
> SMBIOS rev. 2.2 @ 0xf (43 entries)
> bios0: vendor Phoenix Technologies, LTD version "ASUS A7N8X Deluxe ACPI
> BIOS Rev 1008" date 09/14/2004
> bios0: ASUSTeK Computer INC. A7N8X
> apm0 at bios0: Power Management spec V1.2
> apm0: AC on, battery charge unknown
> apm0: flags 70102 dobusy 1 doidle 1
> pcibios0 at bios0: rev 2.1 @ 0xf/0xdf84
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdeb0/208 (11 entries)
> pcibios0: PCI Exclusive IRQs: 5 11 12
> pcibios0: no compatible PCI ICU found
> pcibios0: Warning, unable to fix up PCI interrupt routing
> pcibios0: PCI bus #3 is the last bus
> bios0: ROM list: 0xc/0xd000 0xd/0x1800 0xd2000/0x800
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "NVIDIA nForce2 PCI" rev 0xa2
> "NVIDIA nForce2" rev 0xa2 at pci0 dev 0 function 1 not configured
> "NVIDIA nForce2" rev 0xa2 at pci0 dev 0 function 2 not configured
> "NVIDIA nForce2" rev 0xa2 at pci0 dev 0 function 3 not configured
> "NVIDIA nForce2" rev 0xa2 at pci0 dev 0 function 4 not configured
> "NVIDIA nForce2" rev 0xa2 at pci0 dev 0 function 5 not configured
> pcib0 at pci0 dev 1 function 0 "NVIDIA nForce2 ISA" rev 0xa3
> nviic0 at pci0 dev 1 function 1 "NVIDIA nForce2 SMBus" rev 0xa2
> iic0 at nviic0
> spdmem0 at iic0 addr 0x50: 256MB DDR SDRAM non-parity PC-2700CL2.5
> spdmem1 at iic0 addr 0x51: 256MB DDR SDRAM non-parity PC-2700CL2.5
> spdmem2 at iic0 addr 0x52: 512MB DDR SDRAM non-parity PC-2700CL2.5
> iic1 at nviic0
> asbtm0 at iic1 addr 0x2d
> wbenv0 at iic1 addr 0x2e: W83L785TS-L
> ohci0 at pci0 dev 2 function 0 "NVIDIA nForce2 USB" rev 0xa3: irq 12,
> version 1.0, legacy support
> ohci1 at pci0 dev 2 function 1 "NVIDIA nForce2 USB" rev 0xa3: irq 12,
> version 1.0, legacy support
> ehci0 at pci0 dev 2 function 2 "NVIDIA nForce2 USB" rev 0xa3: irq 11
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0
Re: Apple Macbook Xorg synchronization problems
On Wed, Aug 20, 2008 at 11:56:38AM -0400, Nick Guenther wrote: > On Wed, Aug 20, 2008 at 8:20 AM, Karl Sjodahl - dunceor > <[EMAIL PROTECTED]> wrote: > > On Tue, Aug 19, 2008 at 9:32 PM, Nick Guenther <[EMAIL PROTECTED]> wrote: > >>> > >> > >> You have a 2,1? How did you get it installed in the first place? The > >> install kernel hangs for me. I got around that by putting the > >> harddrive in a different computer, but I'm wondering if I missed an > >> easier way. > >> > >> -Nick > >> > >> > > > > Last time I installed it there was a long pause in the install process > > when it tried to find something. > > It finally timed out and then just continued. > > > > I get that long pause too, but then after that the USB hubs don't work > (there's a bunch of errors about that) and so the keyboard doesn't > work. You don't see that? > -Nick > Make sure you plug the USB keyboard in the USB port the closest from you (farthest from the screen).
Re: Can one dd to /dev/rwd0c?
On Sat, Sep 20, 2008 at 10:28:07PM -0700, Aaron Stellman wrote: > On Sun, Sep 21, 2008 at 06:02:37AM +0100, Sunnz wrote: > > OK I am trying to completely erase the data of a hard disk so I though > > I can just do `dd if=/dev/arandom of=/dev/rwd0c` as to my > > understanding that is the entire hard disk (slice c) of wd0 in 'raw' > > mode? > > > > But that dd refuse to do it. > security(7): > "Once you have set the security level to 1, write access to raw > devices will be denied" I guess you're quoting from a FreeBSD man page. On OpenBSD, securelevel(7) says that in securelevel 1, raw disk devices of mounted file systems are read-only. It's securelevel 2 that denies write access to all devices. Sunnz says he's running off an install CD so he should not run into problems related to securelevel. I guess he's root too. Sunnz, you don't say exactly what error dd reports. Have you created the arandom character device file? It is not available by default on the install CD. > > > > So now I am doing the same thing but to wd0c instead. Is this any > > worse? This is the "character device" right? Does that mean dd won't > > write random bits as low as going to the raw device? > > > > This is running off a OpenBSD 4.3 CD, there are no intention to > > actually destroy the hard disk in any way, just erasing the data off > > the hard disk so that it can be reused, re-sold, whatever. The data > > are not some military top secret, but it is interesting to know of > > what can be done in a home/small office environment when it comes to > > erasing the hard drive. > > > > Thanks. > > > > -- > > This e-mail may be confidential. You may not copy, forward, > > distribute, or, use any part of it. Note, like all disclaimers on the > > net, there are no effective legal binding on your part and disclaimers > > can be ignored. For more information about disclaimers, please see: > > http://www.goldmark.org/jeff/stupid-disclaimers/
Re: Wireless once again being a pain, this time ipw
On Wed, Sep 24, 2008 at 05:51:00PM +0100, Edd Barrett wrote: > Hi, > > I have an X31 which I have installed -current on. It has an ipw card: > ipw0 at pci2 dev 2 function 0 "Intel PRO/Wireless 2100" rev 0x04: irq 11 > > Its function seems to work for a while, then I get: > Sep 24 15:22:35 x31 /bsd: ipw0: fatal firmware error > Sep 24 15:22:36 x31 /bsd: ipw0: timeout waiting for disabled state > Sep 24 15:22:36 x31 /bsd: ipw0: association failed (error=35) > Sep 24 15:22:37 x31 /bsd: ipw0: scan request failed (error=35) > > Which you must reboot for. I'm not sure scanning for AP's is working > correctly either as it scrolls up many times: > ipw0: scan request failed (error=35) > ipw0: scan request failed (error=35) > ipw0: scan request failed (error=35) > ... > > I'm not having much luck with wireless support on OpenBSD :( > > Is it the firmware which is at fault? Can the firmware be flushed are > reloaded? > > I have a wi(4) which I will try when I get a chance. (and yes tpwireless). > > -- > > Best Regards > > Edd > > http://students.dec.bournemouth.ac.uk/ebarrett > This could be the same problem than Linux users are seeing: http://kerneltrap.org/mailarchive/linux-kernel/2008/9/21/3358724
Re: cannot alloc NNN bytes for blockmap
Adding more RAM won't change anything with your current software configuration. You are running 4.3 which limits dynamic memory allocation to 1 GB per process. You could boot off a snapshot where the limit is bigger (and fsck uses less memory as Chris said). On Wed, Sep 24, 2008 at 12:25:53PM -0500, Jason Sidabras wrote: > Thanks Ted and Chris, > > I have to go pick up some more RAM, i don't have a system I can take down to > shift this over. > > Jason > > On Wed, Sep 24, 2008 at 12:17 PM, Jason Sidabras > <[EMAIL PROTECTED]>wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Thanks Chris, > > > > I am a little worried about running `fsck -p` in case of loss of data > > but I did it and edited my fstab. > > > > once booted I still have no luck running fsck_ffs: > > > > error is now: > > > > cannot alloc NNN bytes for statemap > > dmesg follows: > > > > OpenBSD 4.3 (GENERIC.MP) #1582: Wed Mar 12 11:16:45 MDT 2008 > > > > [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 2138632192 (2039MB) > > avail mem = 2065088512 (1969MB) > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (31 entries) > > bios0: vendor Award Software International, Inc. version "F5" date > > 03/25/2008 > > bios0: Gigabyte Technology Co., Ltd. 945GCM-S2C > > acpi0 at bios0: rev 0 > > acpi0: tables DSDT FACP HPET MCFG APIC SSDT SSDT > > acpi0: wakeup devices PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5) > > PEX5(S5) HUB0(S5) UAR1(S1) USB0(S1) USB1(S1) USB2(S1) USB3(S1) > > USBE(S1) AZAL(S5) PCI0(S5) > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > acpihpet0 at acpi0: 14318179 Hz > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz, 2533.64 MHz > > cpu0: > > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,CX16,xTPR,NXE,LONG > > cpu0: 3MB 64b/line 8-way L2 cache > > cpu0: apic clock running at 266MHz > > cpu1 at mainbus0: apid 1 (application processor) > > cpu1: Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz, 2533.33 MHz > > cpu1: > > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,CX16,xTPR,NXE,LONG > > cpu1: 3MB 64b/line 8-way L2 cache > > ioapic0 at mainbus0 apid 2 pa 0xfec0, version 20, 24 pins > > ioapic0: misconfigured as apic 0, remapped to apid 2 > > acpiprt0 at acpi0: bus 0 (PCI0) > > acpiprt1 at acpi0: bus 4 (PEX0) > > acpiprt2 at acpi0: bus 5 (PEX1) > > acpiprt3 at acpi0: bus -1 (PEX2) > > acpiprt4 at acpi0: bus -1 (PEX3) > > acpiprt5 at acpi0: bus -1 (PEX4) > > acpiprt6 at acpi0: bus -1 (PEX5) > > acpiprt7 at acpi0: bus 6 (HUB0) > > acpicpu0 at acpi0: FVS, 2400, 1600 MHz > > acpicpu1 at acpi0 > > acpibtn0 at acpi0: PWRB > > pci0 at mainbus0 bus 0: configuration mode 1 > > pchb0 at pci0 dev 0 function 0 "Intel 82945G Host" rev 0x02 > > agp0 at pchb0: aperture at 0xc000, size 0x1000 > > ppb0 at pci0 dev 1 function 0 "Intel 82945G PCIE" rev 0x02: apic 2 int > > 16 (irq 5) > > pci1 at ppb0 bus 1 > > ppb1 at pci1 dev 0 function 0 "Intel IOP333 PCIE-PCIX" rev 0x00 > > pci2 at ppb1 bus 2 > > arc0 at pci2 dev 14 function 0 "Areca ARC-1220" rev 0x00: apic 2 int 18 > > (irq 10) > > arc0: 8 ports, 256MB SDRAM, firmware V1.43 2007-4-17 > > scsibus0 at arc0: 16 targets > > sd0 at scsibus0 targ 0 lun 0: SCSI3 > > 0/direct fixed > > sd0: 2861022MB, 44966 cyl, 511 head, 255 sec, 512 bytes/sec, > > 5859374592 sec total > > ppb2 at pci1 dev 0 function 2 "Intel IOP333 PCIE-PCIX" rev 0x00 > > pci3 at ppb2 bus 3 > > vga1 at pci0 dev 2 function 0 "Intel 82945G Video" rev 0x02 > > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > > wsdisplay0: screen 1-5 added (80x25, vt100 emulation) > > azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x01: > > apic 2 int 16 (irq 5) > > azalia0: codec[s]: Realtek/0x0662 > > audio0 at azalia0 > > ppb3 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: apic 2 > > int 16 (irq 5) > > pci4 at ppb3 bus 4 > > ppb4 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x01: apic 2 > > int 17 (irq 12) > > pci5 at ppb4 bus 5 > > re0 at pci5 dev 0 function 0 "Realtek 8101E" rev 0x01: RTL8101E > > (0x3400), apic 2 int 17 (irq 12), address 00:1f:d0:63:70:5f > > rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1 > > uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 2 > > int 23 (irq 3) > > uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: apic 2 > > int 19 (irq 11) > > uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 2 > > int 18 (irq 10) > > uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 2 > > int 16 (irq 5) > > ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: apic 2 > > int 23 (irq 3) > > usb0 at ehci0: USB revision 2.0 > > uhub0 at usb0 "Intel EHCI root
Re: slow network performance behind cisco
On Fri, Oct 24, 2008 at 03:54:01PM +0200, Christoph Leser wrote: > > -Urspr|ngliche Nachricht- > > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Im Auftrag von Otto Moerbeek > > Gesendet: Freitag, 24. Oktober 2008 13:11 > > An: Sebastian Reitenbach > > Cc: misc@openbsd.org > > Betreff: Re: slow network performance behind cisco > > > > > > On Fri, Oct 24, 2008 at 12:58:27PM +0200, Sebastian Reitenbach wrote: > > > > > Hello everybody, > > > > > > I'm experiencing a very bad network performance, when I try > > to connect > > > to a remote server. The point-to-point connection is a E3 > > line, with > > > 34MBit/s, with a cisco 2800 router on each side, terminating the > > > point-to-point connection. > > > > > > These cisco routers have two gigabit interfaces, and a serial > > > point-to-point E3 controller. Below my network layout: > > > > > > +-+ > > > |Remote Server| > > > +-+ > > > |GigaBit Ethernet > > > ++ > > > |Remote Cisco| > > > ++ > > > |Serial E3 Line > > > | > > > ++ GigaBit Ethernet+-+ > > > |Local Cisco |-|Linux Box| > > > ++ +-+ > > > |GigaBit Ethernet > > > +---+ > > > |BSD Box| > > > +---+ > > > > > > I use iperf to measure the connection speed. > > > The OpenBSD box, and the Linux box are in two different > > networks, so > > > the connection between these two is also routed. When I use iperf > > > between the Linux-Box and the BSD-Box, then iperf measures about > > > 500MBit/s, so thats fine. When I use iperf between the > > Linux Box and > > > the remote server, then I get sth. about 32 MBits, that's fine too. > > > When I use iperf between the BSD box and the remote server, > > > I only get 2MBit/s. > > > Then I thought, maybe the interface where the BSD box is connected > > > is the problem, so I connected it to the interface on the cisco, > > > where the Linux box was connected before, but still only the > > > 2MBit/s speed to the remote host. > > > I also tried different OpenBSD boxes, with different > > network adaptors, > > > one with bge, another one with fxp, but also, no difference. > > > With both BSD boxes, connection to the Linux box is fast, > > > connections to the remote server is slow. > > > Then I tried to fiddle around with pf, scrub rules on the BSD box. > > > I tested with disabled firewall, with > > > scrub no-df > > > scrub set-tos lowdelay > > > scrub set-tos throughput > > > and some more, but without any observable difference in the speed. > > > The Linux box and the BSD boxes both had the same MTU on > > their interfaces, > > > and also no dropped packets, or errors on the interfaces. > > > > > > When I connect the Linux box behind the OpenBSD box, and > > then try to > > > connect from the Linux box to the OpenBSD box, the > > performance becomes > > > slow. > > > > > > So right now I'm a bit puzzled, and have no idea, why the > > connection > > > to the remote host is fast when using a Linux box, but so slow when > > > using OpenBSD. Are there any differences in the IP packets that > > > OpenBSD and Linux creates? I'm going to capture the network > > traffic on > > > the Linux and OpenBSD box to be able to compare the IP packets. > > > Is there any tool where I can replay the packet sequence on > > OpenBSD that I > > > have > > > recorded with tcpdump on the Linux box? > > > > > > Unfortunately, I don't have access to the remote cisco, or remote > > > server, so I cannot check anything there. > > > > > > any hint is greatly appreciated. > > > > OpenBSD uses a pretty low default send and receive buffer > > size for sockets. Try increasing net.inet.tcp.recvspace and > > net.inet.tcp.sendspace, after reading a bit about bandwidth * > > delay products. > > > > -Otto > > > > > > > > If there is more information needed from my side, to explain the > > > problem, don't hesitate to ask. > > > > > > kind regards > > > Sebastian > > > > > > > > __ > > > _ > > > Jetzt neu! Sch|tzen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage > > > kostenlos testen. > > http://www.pc-sicherheit.web.de/startseite/?mc=00 > > > > > > If it is a buffer size problem, why can he transmit 500mb/sec between bsd and > local linux? > Because the delay between the two machines is very low. It appears you need to read about bandwidth-delay product as well.
Re: httpdump?
2008/11/23 ropers <[EMAIL PROTECTED]>: >>> On Wed, Nov 19, 2008 at 08:18:00PM -0800, Jeff Simmons wrote: > >>> Just increase the snaplen. >>> >>> tcpdump -s 65000 -w dump port 80 > > With some tcpdump(8) versions on non-OpenBSD Unix-like OSes (e.g. > tcpdump version 3.9.8/Ubuntu 8.10), the man page says: > > -s Snarf snaplen bytes of data from each packet (...) Set‐ > ting snaplen to 0 means use the required length to catch > whole packets. > > The man page for OpenBSD's tcpdump doesn't mention anything about > setting the snaplen to 0, and trying to invoke OpenBSD's tcpdump with > -s 0 results in an error of: > >> tcpdump: invalid snaplen 0 > > (tested with OpenBSD 4.3 GENERIC) > > This is probably a naive question, but how would one best replicate > the -s 0 functionality with OpenBSD's tcpdump? Is there a reason why > Jeff specifically suggested -s 65000? > > Many thanks and regards, > --ropers > > Since the size of a IPv4 packet is coded on 16 bits it can't be more than 65536 octets. So -s 65536 and -s 0 should behave the same for IPv4 packets. Note that IPv6 has a jumbogram feature enabling the use of bigger packets but I never saw it in action. And since tcpdump doesn't reassemble framented IP packets, your network interface MTU should be enough anyway. -- Pierre Riteau
Re: Disable power button
On Sat, Apr 12, 2008 at 03:00:02PM +0200, =?ISO-8859-1?Q?Mikael_Nystr=F6m_ wrote: > Is there a way to disable the power button on OpenBSD, like FreeBSD's > sysctl hw.acpi.power_button_state=NONE or similar? > I'm running OpenBSD 4.2. > > //Micke > I'm quite sure this is not possible at runtime, but I guess that disabling acpibtn(4) in your kernel with UKC/config(8) should do the trick. -- Pierre Riteau
Re: Got 'em !
On Thu, Apr 10, 2008 at 10:29:26AM +0200, Paul de Weerd wrote: > Hi all, > > The new 4.3 CD set has just arrived here in Zurich, Switzerland ! I've > put up a pic on http://www.weirdnet.nl/images/openbsd43set.jpg .. > looking very cool yet again ;) > > Thanks to all the developers for another very cool release. > > Cheers, > > Paul 'WEiRD' de Weerd > > -- > >[<++>-]<+++.>+++[<-->-]<.>+++[<+ > +++>-]<.>++[<>-]<+.--.[-] > http://www.weirdnet.nl/ > Got mine yesterday, with a nice "#1 !" on the package :) Very nice packaging as usual, the comics are really nice. I really like the one behind the CDs. Thanks for this great release! -- Pierre Riteau
Re: azalia
On Thu, May 01, 2008 at 02:01:27PM +0200, [EMAIL PROTECTED] wrote: > # dmesg |grep azalia > > azalia0 at pci0 dev 27 function0 "Intel 82801GB HDAudio" rev > 0x02:apic2 int 22(irq10) > > azalia0: codec[s]: Realtek/0x861, audio at azalia 0 > > p.s. #cdio play gives no sound either > thx > cdio play tells your CD drive to play to its analog output. If your CD drive is not plugged to your sound card, you will not hear any sound. You can use cdio cdplay instead. -- Pierre Riteau
Re: Editing C with...
On Sat, May 03, 2008 at 07:56:33PM +0200, Jordi Espasa Clofent wrote: > Yes, I know, it's completely a dumb question; but I'm curious about it. > > I'm just learning C applied in networking area and I wonder what editor is > preferred by OpenBSD developers. > > At present moment I use vim. > > -- > Thanks, > Jordi Espasa Clofent > http://xkcd.com/378/ -- Pierre Riteau
Re: ral(4) hostap plea
On Wed, May 07, 2008 at 04:15:23PM +1000, Rod Whitworth wrote: > On Tue, 6 May 2008 23:26:26 -0600, Daniel Melameth wrote: > > >On Tue, May 6, 2008 at 9:05 PM, James Turner <[EMAIL PROTECTED]> wrote: > >> I've been trying to get my new ral(4) card to work like I would expect it > >> to. I've read through most if not all the talk on misc@ about running these > >> cards in hostap mode. I would really like to replace my wi(4), which > >> works really well, with my new ral(4) and enjoy 11g and later wpa. > >> Sadly, the performance is just not there in both 11b or 11g modes. > >> > >> Some info, the ral(4) is a Gigabyte GN-WP01GS which is an RT2561S. My > >> basic hostname.ral0 reads: inet 192.168.1.1 255.255.255.0 NONE media > >> autoselect mode 11g mediaopt hostap nwid my_net nwkey secret chan 11. > >> I've enabled RAL_DEBUG in my kernel and selected one of the standard > >> channels with the highest power. This is on 4.2 -release + patches. If > >> anyone has any new or additional information that might be helpful I > >> would greatly appreciate it, otherwise I guess I'll stick to my trusted > >> wi(4). > > > >Personally, I've given up on using OpenBSD as an AP--though I have for > >years. Back when I used wi, everything worked very well. However, > >802.11g drivers/cards work very poorly as APs. While speed with them > >can be good at times, different wireless clients performed erratically > >and frequently the AP would lock up. I have since moved on and now > >use commercial APs. > > > >Sorry if this is not what you were looking for. I'd love to say > >802.11g, OpenBSD and APs work swimmingly, but that has never been the > >case for me. > > > H. MMMV (My Mileage Must Vary) > > I have a ral (MSI54G PCI card in a Soekris 4801 pf firewall) that I use > for laptop connectivity inside my Faraday Cage house. It also talks to > a wireless router hacked to be a wireless interface for my PVR > (Topfield) so that the Toppy can get its EPG updates every day and > transfer recorded stuff to a PC for editing. It looks like this: > $ ifconfig ral0 > ral0: flags=8943 mtu > 1500 > lladdr 00:13:d3:6b:a9:be > media: IEEE802.11 autoselect mode 11g hostap > status: active > ieee80211: nwid puffy2 chan 11 bssid 00:13:d3:6b:a9:be nwkey > 100dBm > inet 192.168.181.1 netmask 0xff00 broadcast 192.168.181.255 > inet6 fe80::213:d3ff:fe6b:a9be%ral0 prefixlen 64 scopeid 0x4 > > and it does ftp which talks to the Toppy through USB 1 connection: > ftp> get HDDInfo.tap > local: HDDInfo.tap remote: HDDInfo.tap > 227 Entering Passive Mode (192,168,181,81,4,68) > 150 Opening BINARY mode data connection for 'HDDInfo.tap' (189924 > bytes). > 100% |**| 185 KB > 00:00 > 226 Transfer complete. > 189924 bytes received in 0.38 seconds (487.06 KB/s) > $ > > Not too shabby and it does stuff lots faster talking to the laptop > quite reliably. > > FWIW. > > Rod/ > (Any off-list replies to the reply-to address only, please. Others are > tarpitted.) > -- > Did you hear about the Buddhist who refused his dentist's Novocain > during root canal work? He wanted to transcend dental medication. > I agree this is a good card, I have the very same: ral0 at pci1 dev 8 function 0 "Ralink RT2560" rev 0x01: irq 11, address 00:13:d3:00:43:fc ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525 and I can easily get 2.6 MB/s with sftp. -- Pierre Riteau
Re: Problems going from 4.3-release to -stable
On Thu, May 08, 2008 at 09:08:54PM +, Mike wrote: > Hello, > > After a fresh install of obsd on a new server, I cannot update my system to > -stable. > > The src has been obtained from cvs in the usual manner. > > Here is the error :- > > # cd /usr/src/sys/arch/sparc64/conf/ > # ls > CVS GENERIC.MP RAMDISK RAMDISKU5 > GENERIC Makefile.sparc64RAMDISKU1 files.sparc64 > # config GENERIC > ../../../../conf/files:1005: syntax error > ../../../../conf/files:1006: syntax error > ../../../../conf/files:1007: syntax error > ../../../../conf/files:1008: syntax error > ../../../../conf/files:1009: syntax error > ../../../../conf/files:1010: syntax error > ../../../../conf/files:1011: syntax error > ../../../../conf/files:1012: syntax error > ../../../../conf/files:1013: syntax error > ../../../../conf/files:1014: syntax error > ../../../../conf/files:1015: syntax error > ../../../../conf/files:1016: syntax error > ../../../../conf/files:1017: syntax error > ../../../../conf/files:1018: syntax error > ../../../../conf/files:1019: syntax error > ../../../../conf/files:1020: syntax error > ../../../../conf/files:1021: syntax error > ../../../../conf/files:1022: syntax error > ../../../../conf/files:1023: syntax error > ../../../../conf/files:1024: syntax error > ../../../../conf/files:1025: syntax error > ../../../../conf/files:1026: syntax error > ../../../../conf/files:1027: syntax error > ../../../../conf/files:1028: syntax error > ../../../../conf/files:1029: syntax error > ../../../../conf/files:1030: syntax error > ../../../../conf/files:1031: syntax error > ../../../../conf/files:1032: syntax error > ../../../../conf/files:1033: syntax error > ../../../../conf/files:1034: syntax error > ../../../../conf/files:1035: syntax error > ../../../../conf/files:1036: syntax error > ../../../../conf/files:1037: syntax error > ../../../../conf/files:1038: syntax error > *** Stop. > # uname -a > OpenBSD atom 4.2 GENERIC#1427 sparc64 > > Am i missing something obvious? This has not occured on 4.2 > > Cheers, Mike > Well, the error is pretty obvious. Whatever you did, you are on OpenBSD 4.2 trying to build OpenBSD 4.3. This doesn't work. -- Pierre Riteau
Re: ssh_exchange_identification: Connection closed by remote host
On Tue, May 20, 2008 at 02:32:08PM +0200, Maxim Belooussov wrote: > Hi, > > > when I try to remotely ssh connect to a OpenBSD 4.3 box via port 80 I get: > > Not enough info, but in case you are trying to ssh into box as root, > you will most probably fail. Root login is disabled by default in > OpenBSD. > > Maxim > No it is not. -- Pierre Riteau
Re: cwm keybindings misbehavior
On Thu, Jun 12, 2008 at 01:13:05PM -0300, Daniel B. wrote: > Hi, > > I can't get the response desired to some of the default keybindings in > cwm. > > Some of them: M-/, C-/, M-?. With the first and the third, I just hear a > beep (or a Wuff!! in screen). The second delete my window if not in > screen, or just "Wuff!!" in screen. > > Any hints? Thank you. > non-US keyboard layout?
Re: 4.3: netstat question
On Fri, Jun 13, 2008 at 12:47:25AM +0200, Toni Mueller wrote: > Hi, > > as of today (I didn't notice it earlier), I see this problem on one of > my machines: > > # netstat -rnf inet > netstat: sysctl of routing table: Cannot allocate memory > > This machine receives two full feeds @ ~255k routes each. > > Any idea about how to combat this, please? By sending a dmesg with your message? > > > > Kind regards, > --Toni++
Re: in-kernel pppoe problems
On Fri, Jun 13, 2008 at 11:24:32PM +0200, misc(at)openbsd.org wrote:
> Hello,
>
> it looks like the in-kernel pppoe causes systems to hang up sometimes. I
> testet with two systems (completly different hardware) and two different
> dsl-modems (I'm from germany - standard tcom modems).
> Did someone else notice such problems?
>
> Here is my hostname.pppoe0:
> #cat /etc/hostname.pppoe0
> inet 0.0.0.0 255.255.255.255 NONE \
> pppoedev bge1 authproto pap \
> authname 'USERNAME' authkey 'PASSWORD' up
> dest 0.0.0.1
> !/sbin/route add default 0.0.0.1
>
> # cat /etc/hostname.bge1
> up
>
> Here is the output from the kernel panic:
>
> cached lines from terminal server:
> ddb{0}>
> <13/6/2008 11:49:39>pppoe0: LCP keepalive timeout
> <13/6/2008 11:49:39>kernel: page fault trap, code=0
> <13/6/2008 11:49:41>Stopped at softclock+0x2d: movl
> %edx,0x4(%eax)
> <13/6/2008 11:49:41>ddb{0}>
> <13/6/2008 18:29:27>ddb{0}>
>
You don't provide information about which version of OpenBSD you are
running. Anyway, this seems identical to PR 5794 which was fixed in
-current on May 17.
Re: use boot.conf boot into GENERIC.MP with the 5 second pause at boot-time
On Mon, Jun 16, 2008 at 05:19:16PM +0800, Dongsheng Song wrote: > I use a amd64 MP server, default boot into GENERIC, not GENERIC.MP. > > I can use boot.conf boot into GENERIC.MP, but this remove the 5 > second pause at boot-time. > > How can I default boot into GENERIC.MP, and not remove the 5 second > pause at boot-time? > > Thanks for some help, > > Dongsheng Song > set image bsd.mp It's documented in boot.conf(8)...
Re: OpenBSD project goals
On Tue, Jun 24, 2008 at 10:10:37PM +0200, Samo Jelovsek wrote: > On 24. 06. 2008 16:41, Marco Peereboom wrote: >>> Understood, but I wrote about functionality conciously: I would mean >>> "ability to write a letter" rather than OO.org. >> >> mg and vi come to mind... >> >> > > Hm, I'm just curious how do you imagine writing a letter with vi or mg > (ok, i really don't know mg so well..). Don't understand this the wrong > way I really want to know, because you maybe know something I don't. > I would consider using latex for writing a letter.. > > Best regards, > Samo > As someone already said earlier, you can write your letter in troff with mg or vi and create a postscript file from that.
Re: OpenBSD project goals
On Tue, Jun 24, 2008 at 10:28:27PM +0200, Otto Moerbeek wrote: > On Tue, Jun 24, 2008 at 10:18:05PM +0200, Pierre Riteau wrote: > > > On Tue, Jun 24, 2008 at 10:10:37PM +0200, Samo Jelovsek wrote: > > > On 24. 06. 2008 16:41, Marco Peereboom wrote: > > >>> Understood, but I wrote about functionality conciously: I would mean > > >>> "ability to write a letter" rather than OO.org. > > >> > > >> mg and vi come to mind... > > >> > > >> > > > > > > Hm, I'm just curious how do you imagine writing a letter with vi or mg > > > (ok, i really don't know mg so well..). Don't understand this the wrong > > > way I really want to know, because you maybe know something I don't. > > > I would consider using latex for writing a letter.. > > > > > > Best regards, > > > Samo > > > > > > > As someone already said earlier, you can write your letter in troff > > with mg or vi and create a postscript file from that. > > One of the more important features of unix always has been document > processing and typesetting. > > -Otto Exactly. The first user of Unix besides the developers of the system was the Patent departement at Bell Labs, as early as 1971, to prepare patent applications (http://www.cs.bell-labs.com/who/dmr/hist.html).
Re: How can the bootprompt be removed from the bootloader on an amd64 system?
On Thu, Jul 03, 2008 at 02:41:11PM +0200, Alexander Hall wrote: > Jason Crawford wrote: >> On Wed, Jul 2, 2008 at 6:36 PM, Jon <[EMAIL PROTECTED]> wrote: >>> I would like the bootloader to accept no user input and do nothing but >>> load the kernel. >> >> man boot.conf >> look for timeout > > Another possibility, from "man boot", section EXAMPLES: > > Remove the 5 second pause at boot-time permanently, causing > boot to load the kernel immediately without prompting: > ># echo "boot" > /etc/boot.conf > > Note that for 4.3 and older systems, boof.conf can be overridden (i.e. > not processed) by pressing and holding Contrl when booting. Looking at > it now, I see that it's been removed from the -current manpage, so I > guess maybe it's not available anymore. First, this functionality appeared in 4.2, so you won't find it in every "older system". Secondly, it is still in -current man page and the feature is still here. > > /Alexander
Re: How can the bootprompt be removed from the bootloader on an amd64 system?
On Thu, Jul 03, 2008 at 03:17:13PM +0200, Alexander Hall wrote: > Pierre Riteau wrote: >> On Thu, Jul 03, 2008 at 02:41:11PM +0200, Alexander Hall wrote: >>> Jason Crawford wrote: >>>> On Wed, Jul 2, 2008 at 6:36 PM, Jon <[EMAIL PROTECTED]> wrote: >>>>> I would like the bootloader to accept no user input and do nothing but >>>>> load the kernel. >>>> man boot.conf >>>> look for timeout >>> Another possibility, from "man boot", section EXAMPLES: >>> >>> Remove the 5 second pause at boot-time permanently, causing >>> boot to load the kernel immediately without prompting: >>> >>># echo "boot" > /etc/boot.conf >>> >>> Note that for 4.3 and older systems, boof.conf can be overridden >>> (i.e. not processed) by pressing and holding Contrl when booting. >>> Looking at it now, I see that it's been removed from the -current >>> manpage, so I guess maybe it's not available anymore. >> >> First, this functionality appeared in 4.2, so you won't find it in >> every "older system". > > Ok, I wasn't sure about that. I thought it'd been along for longer. (I > obviously have not used it a lot). > >> Secondly, it is still in -current man page and the feature is still >> here. > > Oops. I see now that > http://www.openbsd.org/cgi-bin/man.cgi?query=boot&arch=i386 actually > gave me the SOCPPC manpage... And I cannot seem to find the i386 one > through man.cgi at all... > > Sorry for the misinformation and thanks for the clarifications. > > /Alexander That's because there was a timeframe when socppc boot.conf manpage was installed as a machine independent manpage (this has been fixed a few weeks ago). Unfortunately, in the manpages web interface, deleted pages are kept around and that's why you get the socppc manpage (for example you can still find the vpn man page which was removed more than 2 years ago). CC:ing Bob who seems to be in charge of this manpage web interface. Pierre Riteau
Re: does SiI3124 sata controller work under openbsd
On Sun, Jul 06, 2008 at 12:43:39PM +0300, Imre Oolberg wrote: > Hallo! > > I am choosing (probably from ebay) a sata adapter to connect four newer > generation sata disks to little older computer (ibm x200, with 32bit pci > slots) to make myself an home-made storage for home use backup. I have > not yet decided whether to use for it openbsd or debian. People > recommended sil3124 chip based sata controllers for linux which come > also with 32bit pci 4 sata port flavors. > > I checked > > http://www.openbsd.org/i386.html#hardware > > and saw there that the following silicon images are supported > > Silicon Image SiI3112 (including ATI IXP SATA), SiI3512, SiI3114 > > but to make sure i would like to ask if this sil3124 chip is also > working under openbsd now or maybe some near time in the future? Or what > model is so to say classic openbsd sata controller which is also sold > nowdays? > > And if somebody shares from their experience how reasonable is to put > together PIII generation 32bit pci computer from year of 2002 with new > sata controller and new harddisks. And how much it practically makes > difference to distribute four disks between one such four port sata > controller or two two port sata controllers in terms of performance? > > At the moment i am thinking of backup solution but if it is performing > very well then i expect to use the same solution for nfs file server > also, though it needs a second thought how much to separate the two. > > > Best regards > Imre > > PS I intend to use those sata controllers only as sata controllers and > use software raid, e.g. not their on-chip raid features. > Your chipset should be supported by the sili(4) driver: http://www.openbsd.org/cgi-bin/man.cgi?query=sili&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html
Re: rtorrent problems - solved?
On Sun, Jul 13, 2008 at 10:16:13AM +0200, viq wrote: > Sorry for the "carpet bombing", I grabbed the list of people who I saw > report problems with rtorrent. > > I'm writing to ask those who had problems with rtorrent try it again > with newest snapshots, I was not able to reproduce the problem on a > box that used to freeze. Please test and report, maybe Otto just fixed > another obscure bug ;) > > -- > viq I will try again and report, but if this is fixed I think it would be from a kernel change (biomem? pagedaemon?) rather than the userland malloc ;) -- Pierre Riteau
Re: ath(4) testers needed: AR2413, AR5413, AR5424 and AR5212 11a mode
On 9/19/06, Reyk Floeter <[EMAIL PROTECTED]> wrote:
hi,
i recently enabled support for some newer wireless chipsets from
atheros, like the AR2413, AR5413, and AR5424 single chip solutions.
please also test it if you have an intel-based mac - the integrated
wireless NIC is based on the pci express AR5424 chipset.
I just tested it with a snapshot from the 23th, on a 2Ghz Macbook (non Pro).
Here is my dmesg :
OpenBSD 4.0-current (RAMDISK_CD) #40: Sat Sep 23 12:43:03 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Genuine Intel(R) CPU T2500 @ 2.00GHz ("GenuineIntel" 686-class) 2.01 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2
real mem = 503730176 (491924K)
avail mem = 452964352 (442348K)
using 4256 buffers containing 25288704 bytes (24696K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 07/29/05, SMBIOS rev. 2.4 @
0xe7440 (37 entries)
bios0: Apple Computer, Inc. MacBook1,1
pcibios at bios0 function 0x1a not configured
bios0: ROM list: 0xc/0xe600!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM MCH" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
vendor "Intel", unknown product 0x27a3 (class DASP subclass Time and
Frequency, rev 0x03) at pci0 dev 7 function 0 not configured
"Intel 82801GB HD Audio" rev 0x02 at pci0 dev 27 function 0 not configured
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02
pci1 at ppb0 bus 1
mskc0 at pci1 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x22,
Marvell Yukon-2 EC rev. A3 (0x2): irq 11
msk0 at mskc0 port A, address 00:16:cb:cb:66:74
eephy0 at msk0 phy 0: Marvell 88E Gigabit PHY, rev. 2
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02
pci2 at ppb1 bus 2
ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: irq 11
ar5k_ar5212_nic_wakeup: failed to resume the AR5212 (again)
ath0: unable to attach hardware; HAL status 22
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: irq 11
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: irq 11
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: irq 11
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: irq 10
usb3 at uhci3: USB revision 1.0
uhub3 at usb3
uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: irq 11
usb4 at ehci0: USB revision 2.0
uhub4 at usb4
uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
ppb2 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci3 at ppb2 bus 3
"AT&T/Lucent FW322 1394" rev 0x61 at pci3 dev 3 function 0 not configured
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM disabled
pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0
5/cdrom removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
pciide0: channel 1 disabled (no drives)
pciide1 at pci0 dev 31 function 2 "Intel 82801GBM SATA" rev 0x02: DMA,
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide1: using irq 11 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 1:
wd0: 16-sector PIO, LBA48, 57231MB, 117210240 sectors
wd0(pciide1:0:1): using PIO mode 4, Ultra-DMA mode 5
"Intel 82801GB SMBus" rev 0x02 at pci0 dev 31 function 3 not configured
isa0 at ichpcib0
isadma0 at isa0
npx0 at isa0 port 0xf0/16: using exception 16
biomask netmask ttymask
rd0: fixed, 3800 blocks
uhub4: device problem, disabling port 4
uhidev0 at uhub3 port 1 configuration 1 interface 0
uhidev0: vendor 0x05ac product 0x1000, rev 2.00/19.65, addr 2, iclass 3/1
uhidev1 at uhub1 port 1 configuration 1 interface 0uhidev2 at uhub2
port 2 configuration 1 interface 0ukbd0 at uhidev0
uhidev1: Logitech Logitech USB Keyboard, rev 1.10/15.00, addr 2, iclass 3/1
uhidev2: Apple Computer, Inc. IR Receiver, rev 2.00/1.10, addr 2, iclass 3/0
ukbd1 at uhidev1
uhidev2: 38 report ids
uhid at uhidev2 reportid 36 not configured
uhid at uhidev2 reportid 37 not configured
uhid at uhidev2 reportid 38 not
Re: ath(4) testers needed: AR2413, AR5413, AR5424 and AR5212 11a mode
On 9/24/06, Karsten McMinn <[EMAIL PROTECTED]> wrote:
On 9/24/06, Pierre Riteau <[EMAIL PROTECTED]> wrote:
> ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: irq 11
> ar5k_ar5212_nic_wakeup: failed to resume the AR5212 (again)
> ath0: unable to attach hardware; HAL status 22
is that on a fresh power-on?
Yes. I installed OpenBSD this evening, and tried with latest GENERIC
and GENERIC.MP.
Same result.
OpenBSD 4.0-current (GENERIC) #: Sun Sep 24 20:49:17 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Genuine Intel(R) CPU T2500 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2
cpu0: unknown Enhanced SpeedStep CPU, msr 0x06130c2c06040613
cpu0: using only highest and lowest power states
cpu0: Enhanced SpeedStep 1000 MHz (1004 mV): speeds: 2000, 1000 MHz
real mem = 515354624 (503276K)
avail mem = 462118912 (451288K)
using 4256 buffers containing 25870336 bytes (25264K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 07/29/05, SMBIOS rev. 2.4 @
0xe7440 (37 entries)
bios0: Apple Computer, Inc. MacBook1,1
pcibios at bios0 function 0x1a not configured
bios0: ROM list: 0xc/0xe600!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM MCH" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03: aperture
at 0x9038, size 0x1000
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
vendor "Intel", unknown product 0x27a3 (class DASP subclass Time and
Frequency, rev 0x03) at pci0 dev 7 function 0 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: irq 11
azalia0: host: High Definition Audio rev. 1.0
azalia0: codec: Sigmatel STAC9221 (rev. 52.1), HDA version 1.0
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02
pci1 at ppb0 bus 1
mskc0 at pci1 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x22,
Marvell Yukon-2 EC rev. A3 (0x2): irq 11
msk0 at mskc0 port A, address 00:16:cb:cb:66:74
eephy0 at msk0 phy 0: Marvell 88E Gigabit PHY, rev. 2
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02
pci2 at ppb1 bus 2
ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: irq 11
ar5k_ar5212_nic_wakeup: failed to resume the AR5212 (again)
ath0: unable to attach hardware; HAL status 22
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: irq 11
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: irq 11
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: irq 11
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: irq 10
usb3 at uhci3: USB revision 1.0
uhub3 at usb3
uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: irq 11
usb4 at ehci0: USB revision 2.0
uhub4 at usb4
uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
ppb2 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci3 at ppb2 bus 3
"AT&T/Lucent FW322 1394" rev 0x61 at pci3 dev 3 function 0 not configured
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM disabled
pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0
5/cdrom removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
pciide0: channel 1 disabled (no drives)
pciide1 at pci0 dev 31 function 2 "Intel 82801GBM SATA" rev 0x02: DMA,
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide1: using irq 11 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 1:
wd0: 16-sector PIO, LBA48, 57231MB, 117210240 sectors
wd0(pciide1:0:1): using PIO mode 4, Ultra-DMA mode 5
ichiic0 at pci0 dev 31 function 3 "Intel 82801GB SMBus" rev 0x02: irq 11
iic0 at ichiic0
isa0 at ichpcib0
isadma0 at isa0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
Re: ath(4) testers needed: AR2413, AR5413, AR5424 and AR5212 11a mode
On 9/27/06, Reyk Floeter <[EMAIL PROTECTED]> wrote:
On Sun, Sep 24, 2006 at 02:58:34PM +0200, Pierre Riteau wrote:
> On 9/19/06, Reyk Floeter <[EMAIL PROTECTED]> wrote:
> >hi,
> >
> >i recently enabled support for some newer wireless chipsets from
> >atheros, like the AR2413, AR5413, and AR5424 single chip solutions.
> >
> >please also test it if you have an intel-based mac - the integrated
> >wireless NIC is based on the pci express AR5424 chipset.
> >
>
> I just tested it with a snapshot from the 23th, on a 2Ghz Macbook (non Pro).
> Here is my dmesg :
>
please retry with the attached diff from kettenis. you may see some
11b aps but it doesn't seem to work, yet (the channels are wrong).
> ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: irq 11
> ar5k_ar5212_nic_wakeup: failed to resume the AR5212 (again)
> ath0: unable to attach hardware; HAL status 22
reyk
Index: ar5212.c
===
RCS file: /cvs/src/sys/dev/ic/ar5212.c,v
retrieving revision 1.33
diff -u -p -r1.33 ar5212.c
--- ar5212.c19 Sep 2006 17:49:13 - 1.33
+++ ar5212.c24 Sep 2006 18:22:33 -
@@ -304,6 +304,7 @@ ar5k_ar5212_nic_wakeup(struct ath_hal *h
* Reset and wakeup the device
*/
+#if 0
/* ...reset chipset and PCI device */
if (hal->ah_single_chip == AH_FALSE &&
ar5k_ar5212_nic_reset(hal,
@@ -311,6 +312,7 @@ ar5k_ar5212_nic_wakeup(struct ath_hal *h
AR5K_PRINT("failed to reset the AR5212 + PCI chipset\n");
return (AH_FALSE);
}
+#endif
/* ...wakeup */
if (ar5k_ar5212_set_power(hal,
I patched my kernel, here are the results.
- the chip gets recognized.
ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: irq 11
ath0: AR5424 10.3 phy 6.1 rf 10.2, WORAW, address 00:16:cb:bd:08:f4
- My AP is 11b, it's a ral(4) (RT2560) on OpenBSD 4.0, sometimes I see one
from one of my neighbours, both don't show the SSID in ifconfig.
ath0: flags=8863 mtu 1500
lladdr 00:16:cb:bd:08:f4
media: IEEE802.11 autoselect (OFDM6)
status: no network
ieee80211: nwid ""
nwid "" chan 2 bssid 00:13:d3:00:43:fc 20% 11M
inet6 fe80::216:cbff:febd:8f4%ath0 prefixlen 64 scopeid 0x2
- When I first start the ath0 interface, I can see probe requests.
Then I found that doing `ifconfig ath0 mediaopt hostap` and then
`ifconfig ath0 -mediaopt hostap` makes the probe run again.
# tcpdump -y ieee802_11_radio -eni ath0
tcpdump: WARNING: ath0: no IPv4 address assigned
tcpdump: listening on ath0, link-type IEEE802_11_RADIO
23:38:43.383940 0:16:cb:bd:8:f4 > ff:ff:ff:ff:ff:ff, bssid
ff:ff:ff:ff:ff:ff: 802.11: probe request,
23:38:43.584264 0:16:cb:bd:8:f4 > ff:ff:ff:ff:ff:ff, bssid
ff:ff:ff:ff:ff:ff: 802.11: probe request,
23:38:43.784279 0:16:cb:bd:8:f4 > ff:ff:ff:ff:ff:ff, bssid
ff:ff:ff:ff:ff:ff: 802.11: probe request,
23:38:43.984357 0:16:cb:bd:8:f4 > ff:ff:ff:ff:ff:ff, bssid
ff:ff:ff:ff:ff:ff: 802.11: probe request,
(51 requests each time).
- I also see my AP "beacons".
21:37:18.686664 0:13:d3:0:43:fc > ff:ff:ff:ff:ff:ff, bssid
0:13:d3:0:43:fc: 802.11: beacon, ssid (POUET), rates, ds, tim,
21:37:18.789530 0:13:d3:0:43:fc > ff:ff:ff:ff:ff:ff, bssid
0:13:d3:0:43:fc: 802.11: beacon, ssid (POUET), rates, ds, tim,
21:37:23.397563 0:13:d3:0:43:fc > ff:ff:ff:ff:ff:ff, bssid
0:13:d3:0:43:fc: 802.11: beacon, ssid (POUET), rates, ds, tim,
21:37:58.417322 0:13:d3:0:43:fc > ff:ff:ff:ff:ff:ff, bssid
0:13:d3:0:43:fc: 802.11: beacon, ssid (POUET), rates, ds, tim,
21:37:58.519206 0:13:d3:0:43:fc > ff:ff:ff:ff:ff:ff, bssid
0:13:d3:0:43:fc: 802.11: beacon, ssid (POUET), rates, ds, tim,
And it goes on at the same rate.
I hope it will be useful. Keep up the good work.
Pierre Riteau
Re: Mac Mini (intel) status
On 12/1/06, Marco S Hyman <[EMAIL PROTECTED]> wrote: Not working for me. I get this far: CD_ROM: 90 Loading /CDBOOT probing: pc0 com0 mem(699K 991M a20=on) disk: hd0+* cd0 boot> c and there it stays forever. I suspect the "c" following the boot prompt is left over from "hold c to boot from cd". The keyboard at this point is dead. Any ideas? I'd really like to get OpenBSD up on this beasty. I've tried several different home grown CDs plus the 11/29 snapshot CD from ftp.openbsd.org. // marc Hold the "alt" key instead of "c". It will show a menu where you can double click on the cd (labelled "Windows") to boot on it. It should then recognize your usb keyboard while booting.
Re: OpenBSD and KVM switch.
On Tue, Apr 27, 2010 at 04:44:06AM -0700, J.C. Roberts wrote: > On Tue, 27 Apr 2010 16:31:02 +0930 David Walker > wrote: > > > Hiya JCR. > > > > A snapshot also re-attaches with the default layout (QWERTY). > > It doesn't matter if I use wsconsctl.conf or the kbdtype file. > > > > uname -rv > > 4.7 GENERIC#628 > > > > Bummer. Now we need to figure out why. IIRC it's simply because the keyboard layout configuration is applied by the rc script. When a keyboard is attached no layout configuration takes place.
