Re: massive memory leak in 3.8-stable samba
On Tue, 7 Mar 2006, Steve Fairhead wrote: One of my production machines (3.8-stable) has suddenly started panicing every couple of hours. I found out that the culprit is smbd, eating through memory like there's no tomorrow (approx. 10Mb / minute! ). Can't figure out what has triggered it, nothing changed on the machine lately and there is only one active w2k client, writing a 2.5kB file every 15 seconds or so. I'd be glad of any assistance, even pointing out any stupid mistakes I have made, because this is driving me nuts. I ran into something very similar recently. In my case I eventually discovered that one user was writing to a folder containing 22,000 files. Avoiding this folder has entirely solved the problem. (Or at least worked around it.) FWIW, the Samba logs were helpful only inasmuch as they pointed me to the user who was "causing" the problem. I had to sit down and watch her operate to find out what she was doing... Perhaps (indeed probably) not relevant to your problem, but might give you some ideas. If you're writing a file every 15s, perhaps your problem is related to mine. Steve http://www.fivetrees.com Have a similar problem, though mine appears when moving files between various directories when either has a large number of files in it. Finally decided to delve into the Samba code to see if I could track down the cause. I believe I tracked it to code that scans the directories prior to the file rename operation. The code that scans the directories does some odd things (like hammer on the system lib call: telldir() which appears to leak memory like a sieve if unaccompanied by a matching seekdir() -- approximately 16 bytes per file per directory scanned). This can add up to signifant loss if the directory has, say, 10,000 files or more in it, especially if the directory is scanned multiple times per operation and repeatedly over time. I'm at a bit of a loss how to proceed from here. Given the state and conventions of *BSD-ish directory library calls, Samba isn't scanning directories in a very memory efficient manner -- at least in the case of OpenBSD. But the directory traversals and possible dependencies on the scanning methods could spider badly to fix it properly and reliably within Samba. (ie, I believe that to fix the issue in Samba "properly" is a heck of a lot of work and effort, but I'm also not exactly a Samba expert/developer either) On the other hand, the fact that the system library call telldir() can leak as badly as it does probably isn't a good thing either as outlined here: http://mail-index.netbsd.org/netbsd-bugs/2004/02/05/0008.html It would appear that at least in OpenBSD 3.8-release, the library implementation suffers similar potental issues. I have no idea if the patch proposed in the URL above ever made it into NetBSD, since I don't run NetBSD anywhere; however, the patch looks promising. Changing the implementation of telldir() and related functions would likely fix this particular memory leak in Samba as well, though there may be underlying OS/userland issues about which I am unaware. I guess the bottom line here is that I can see that if you have a process writing into a directory that contains a LOT of files, Samba (or your client, or both) may be scanning the directory prior to any write, and possibly multiple times. If that's the case, the telldir() issue will likely affect you as well. While reducing the number of files in the directory in question won't stop the leak, it may significantly slow it ... I suppose this also assumes that your problem is related to the one I am seeing, and that my preliminary analysis is correct. Hope this helps, - Paul
Re: SGI's
On 3/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > On Sat, 11 Mar 2006 11:51:24 -0500, "Jason Crawford" > <[EMAIL PROTECTED]> wrote: > > >I am soon going to be getting an Octane with dual R12000SC CPUs. I was > >wondering how well OpenBSD would work on this computer (I am pretty > >sure there isn't SMP support on the SGI stuff yet) and how much help > >is needed in getting the SGI port to work even better. > > > >Jason > > Hi Jason, > > Octane support is a "planned project" but currently there is no support > for Octane as far as I know. > > The only currently supported model is the SGI O2. The "little blue > toaster" O2 systems are a lot of fun and amazingly quick when they have > lots of RAM. When you stuff them full of RAM, they just scream, moreso > than any other arch I've used. > > I've got a few O2 systems over here but I haven't touched the for months > and haven't used them with OpenBSD since 3.6/3.7. Even with the earlier > OpenBSD releases, once you get past the SGI-isms, they work very well. Well on the OpenBSD sgi page, it says that the R12000 CPUs are supported. Is it some other piece of hardware like disk controller or something that prevents OpenBSD from running on an Octane? Jason
ath0 panic with snapshot
panic: ieee80211_newstate: bogus xmit rate 0 setup
Stopped at Debugger+0x4: leave
ddb> ps
PID PPID PGRPUID S FLAGS WAIT COMMAND
5980 22770 22770 0 3 0x4006 biowaithttpd
25714 1 22770 0 3 0x44106 uvn_getsendmailhb
9405 18220 18220 83 3 0x184 poll ntpd
18220 1 18220 0 30x84 select ntpd
29478 23617 23617 70 3 0x184 select named
23617 1 23617 0 3 0x184 netio named
30251 19714 19714 74 3 0x184 bpfpflogd
19714 1 19714 0 30x84 netio pflogd
28108 27618 27618 73 3 0x184 poll syslogd
27618 1 27618 0 30x84 netio syslogd
24555 1 24555 0 30x84 mfsidl mount_mfs
22770 1 22770 0 3 0x4086 pause sh
13 0 0 0 30x100204 crypto_wa crypto
12 0 0 0 30x100204 aiodoned aiodoned
11 0 0 0 30x100204 syncer update
10 0 0 0 30x100204 cleanercleaner
9 0 0 0 30x100204 reaper reaper
8 0 0 0 30x100204 pgdaemon pagedaemon
7 0 0 0 30x100204 pftm pfpurge
6 0 0 0 30x100204 timeoutsensors
5 0 0 0 30x100204 usbtsk usbtask
4 0 0 0 30x100204 usbevt usb0
3 0 0 0 30x100204 cardslote cardslot0
2 0 0 0 30x100204 kmallockmthread
1 0 1 0 3 0x4084 wait init
0 -1 0 0 3 0x80204 scheduler swapper
db> trace
Debugger(d08cf000,d6693960,d08cd030,0,d08d6c00) at Debugger+0x4
panic(d0522679,d0522698,0,0,d29d7400) at panic+0x63
ieee80211_rssadapt_choose(d08cd030,4,,919f7) at ieee80211_rssadapt_choo
se
ath_newstate(d08cd030,4,,64,0) at ath_newstate+0x181
ieee80211_create_ibss(d08cd030,d08cd28a,d070bcd4,d04600a1,d08cf000) at ieee8021
1_create_ibss+0x11b
ieee80211_end_scan(d08cd030,d020f706,d08a3200,d070be24) at ieee80211_end_scan+0
x21c
ath_next_scan(d08cd000,d08a3c80,d08a31c0,0,0) at ath_next_scan+0x3d
softclock(d08a0058,10,d08a0010,d08a0010,d070a000) at softclock+0x22c
Bad frame pointer: 0xd070be44
3.8 dmesg with ath (below that is my 3.9 box that paniced but with a
prism card in it):
OpenBSD 3.8 (GENERIC) #0: Sun Jan 8 23:39:30 PST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 697 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXS
R,SSE
real mem = 267952128 (261672K)
avail mem = 237613056 (232044K)
using 3296 buffers containing 13500416 bytes (13184K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(98) BIOS, date 12/21/99, BIOS32 rev. 0 @ 0xfd820
apm0 at bios0: Power Management spec V1.2
apm0: battery life expectancy 98%
apm0: AC on, battery charge high
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xfd7b0/0x850
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdee0/208 (11 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #3 is the last bus
bios0: ROM list: 0xc/0xc000 0xe/0x1
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "S3 Savage/IX-MV" rev 0x11
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
cbb0 at pci0 dev 2 function 0 "Texas Instruments PCI1450 CardBus" rev 0x03: irq
11
cbb1 at pci0 dev 2 function 1 "Texas Instruments PCI1450 CardBus" rev 0x03: irq
11
"AT&T/Lucent LTMODEM" rev 0x01 at pci0 dev 3 function 0 not configured
clcs0 at pci0 dev 5 function 0 "Cirrus Logic CS4280/46xx CrystalClear" rev 0x01:
irq 11
ac97: codec id 0x43525914 (Cirrus Logic CS4297A rev 4)
ac97: codec features headphone, 20 bit DAC, 18 bit ADC, Crystal Semi 3D
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 wi
red to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 11509MB, 23572080 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0
5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x01: 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
"Intel 82371AB Power" rev 0x03 at pci0 dev
Re: SGI's
On Sat, 11 Mar 2006 11:51:24 -0500, "Jason Crawford" <[EMAIL PROTECTED]> wrote: >I am soon going to be getting an Octane with dual R12000SC CPUs. I was >wondering how well OpenBSD would work on this computer (I am pretty >sure there isn't SMP support on the SGI stuff yet) and how much help >is needed in getting the SGI port to work even better. > >Jason Hi Jason, Octane support is a "planned project" but currently there is no support for Octane as far as I know. The only currently supported model is the SGI O2. The "little blue toaster" O2 systems are a lot of fun and amazingly quick when they have lots of RAM. When you stuff them full of RAM, they just scream, moreso than any other arch I've used. I've got a few O2 systems over here but I haven't touched the for months and haven't used them with OpenBSD since 3.6/3.7. Even with the earlier OpenBSD releases, once you get past the SGI-isms, they work very well. Kind Regards, JCR
Re: home VPN
Hey Chris, 2006/3/11, Chris Kuethe <[EMAIL PROTECTED]>: > why would you trust us, and why should we trust you? I would trust some one else, because there may be some one around having the same problem and that could trust it for such a matter. > i'm not saying > you're evil, i'm just saying that not everyone is going to want to > allow you to move arbitrary bits around. and if you're that worried > about monitoring, you're not going to want to use just any old bsd box > as your proxy. how do you know the other guy isn't going to sell you > out? > > while you think about that, can i point you at a few ports > net/tor > security/gnupg > security/stunnel > > if you can find someplace that offers shell accounts, you should have > everything you need to move bits around. use gnupg or mixmaster to > send encrypted email, tor to route tcp sessions and stunnel to ssl-ize > anyting. > > CK (i get paid to think like that) > > > On 3/11/06, Gustavo Rios <[EMAIL PROTECTED]> wrote: > > Dear folks, > > > > i live in brazil, and it is a common practice for local > > corporation/institutions to monitor our phone calls, internet access > > and personal email. I would like to be able to access Internet by > > means of a proxy. My initial ideia is to get some peer (personnel) > > outside brazil that would allow me to connect through it. > > > > I am publicly request some one from the OpenBSD user base because of > > the trust i have on all those i believe share some of the ideology of > > the project and since, make uses of it. > > > > I would really appreciate your help. > > > > All the best. > > > > > > > -- > GDB has a 'break' feature; why doesn't it have 'fix' too?
Re: Good boot and run on ancient laptop (HP Omnibook 5000), 16MB RAM
Stefek Zaba <[EMAIL PROTECTED]> wrote: > I'll be doing the 'config -e' dance to disable the unwanted > audio hardware... later... and no, I don't intend running X on this! What for, your kernel will still be the same size and your laptop does not seem to have audio(4) hardware anyway. martin
Good boot and run on ancient laptop (HP Omnibook 5000), 16MB RAM
Unearthed an ancient laptop recently, intending to add it to the collection
of 'near-transparent' logging bridges available. Keen-eyed dmesg readers
will note the massive 16MB of RAM, and the absence of a floppy device
(though the controller is found) - and a Pentium old enough to need the F00F
workaround!!
Not only no floppy, but no CD drive to hand either, and though unusually
this laptop model has built-in SCSI, it won't boot off SCSI devices.
Installed OpenBSD by taking the hard drive out, putting it in a
USB-to-laptop-drive adaptor on another machine, booting off the OpenBSD
install CD (which detected that adaptor and the disk attached to it just
fine: how lovely!).
First boot when reinstalled went just fine (though if I had a brain I'd have
edited the /etc/fstab to change the mountpoint for / from /dev/sd6a to
/dev/wd0a while it was still in the write-the-install machine - but a swift
'mount -u -w /dev/wd0a /' fixed it up fine for that boot). As the laptop is
very slow processorwise, *much* patience was needed during the sshd
'generating DSA key' stage - took several *minutes*! I did have some memory
of reading what turns out to be FAQ 4.12.3, and I was patient, but not smart
enough to take the steps described there about doing the keygen on a
respectable box and creating a site38.tgz!
Though slow, the machine seems to work just fine in its intended role - it
just captured packets to and from a new box running Kn*ppix (purely to
compare hardware detection results, honest ;-) with two classic 3com 3C589
PCMCIA NICs in its two slots. And the dmesg below comes to you via a Jaz
cartridge written on the laptop in question and read on this other box, so
that 'works' too. No serious stress-testing yet, of course - but a large
thumbs up to OpenBSD putting otherwise-ancient hardware to good network
monitoring use! I'll be doing the 'config -e' dance to disable the unwanted
audio hardware... later... and no, I don't intend running X on this!
Cheers, Stefek
OpenBSD 3.8 (GENERIC) #138: Sat Sep 10 15:41:37 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium (P54C) ("GenuineIntel" 586-class) 120 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8
cpu0: F00F bug workaround installed
real mem = 16359424 (15976K)
avail mem = 6701056 (6544K)
using 225 buffers containing 921600 bytes (900K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(c9) BIOS, date 12/23/94, BIOS32 rev. 0 @ 0xea830
apm0 at bios0: Power Management spec V1.1
apm0: AC on, battery charge unknown, estimated 0:00 hours
apm0: flags 30101 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xe8000/0x6f7
pcibios0: PCI BIOS has 5 Interrupt Routing table entries
pcibios0: PCI Interrupt Router at 000:01:0 ("Opti 82C558 ISA" rev 0x00)
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc/0xa000 0xca000/0x800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Opti 82C557 Host" rev 0x00
pcib0 at pci0 dev 1 function 0 "Opti 82C558 ISA" rev 0x00
vga1 at pci0 dev 2 function 0 "Chips and Technologies 65545" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcic3 at pci0 dev 3 function 0 "Cirrus Logic CL-PD6729" rev 0xfe
pcic3 controller 0: has sockets A and B
pcmcia0 at pcic3 controller 0 socket 0
ep1 at pcmcia0 function 0 "3Com Corporation, 3C589, TP/BNC LAN Card Ver. 2a"
port 0x400/16, irq 3: address 00:a0:24:ab:fc:a0, utp/aui/bnc (default utp)
pcmcia1 at pcic3 controller 0 socket 1
pcic3: interrupting at irq 4
pcic3: irq 4, polling enabled
pcscp0 at pci0 dev 4 function 0 "AMD 53c974 PCscsi-PCI" rev 0x10: irq 15
pcscp0: AM53C974, 40MHz, SCSI ID 7
pcscp0: SCSI bus reset
scsibus0 at pcscp0: 8 targets
sd0 at scsibus0 targ 6 lun 0: SCSI2 0/direct removable
sd0: drive offline
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
wdc0 at isa0 port 0x1f0/8 irq 14
wd0 at wdc0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 1160MB, 2376864 sectors
wd0(wdc0:0:0): using BIOS timings
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
home VPN
Dear folks, i live in brazil, and it is a common practice for local corporation/institutions to monitor our phone calls, internet access and personal email. I would like to be able to access Internet by means of a proxy. My initial ideia is to get some peer (personnel) outside brazil that would allow me to connect through it. I am publicly request some one from the OpenBSD user base because of the trust i have on all those i believe share some of the ideology of the project and since, make uses of it. I would really appreciate your help. All the best.
Re: Problems upgrading to 3.8-stable
> Setting flags on /bsd is not part of the standard install. If you have > done so, you should be able to fix it yourself. Ok, I understand what the problem is and this comment triggered my memory. A while back I was experimenting with different things to harden the system a bit more. One of the things I did, obviosuly, was to set the immutable flag on /bsd. When I went to copy the new kernel over, I forgot that I had done that and ASSumed that this was the default flag. Clearly, it is not. In any event I reinstalled the original kernel with the default flags (nothing) in place and reset the securelevel back to the default of 1. I've removed the new kernel, am in the process of fetching a complete copy of the source tree and will do the upgrade to -stable once that is done. All should be ok now. After years of working with FreeBSD, this is my first attempt at an OpenBSD upgrade. The upgrade process is, in principal, the same, but the commands are a bit different. Clearly, setting immutable flags on the kernel and sycning to a temporarily borked mirror didn't help this go any easier! Thanks. -- Mike Loiterman grantADLER Tel: 630-302-4944 Fax: 773-442-0992 Email: [EMAIL PROTECTED] PGP Key: 0xD1B9D18E
Re: Problems upgrading to 3.8-stable
> Setting flags on /bsd is not part of the standard install. If you have done so, you should be able to fix it yourself. Understood. It seems to be ok, as the new kernel version is reported correctly, but I do want to do it the correct way. However, the way listed in the instruction page is not working for me and I don't know why. I have tried the cp command using sudo and I have tried it using "su -". In both cases, I get the Operation not permitted error. Is this something I need to do from the console? I'm doing this remotely via ssh. -- Mike Loiterman grantADLER Tel: 630-302-4944 Fax: 773-442-0992 Email: [EMAIL PROTECTED] PGP Key: 0xD1B9D18E
Re: Problems upgrading to 3.8-stable
On Sat, 11 Mar 2006, Mike Loiterman wrote: > I'm following the instructions at http://openbsd.org/stable/html to upgrade > to 3.8-stable. > > Everything works as it is supposed to until I get to the part where I am > supposed to copy the newly compiled kernel into /. I execute the command > and get this error: > > # cp bsd /bsd > cp: /bsd: Operation not permitted > > I got around this by setting /etc/rc.securelevel to 0, rebooting, and then > executing the commands: > > # chflags noschg /bsd > # cp /usr/src/sys/arch/i386/compile/GENERIC/bsd /bsd > # chflags schg /bsd > > Then changing /etc/rc.securelevel back to 1 and rebooting. Setting flags on /bsd is not part of the standard install. If you have done so, you should be able to fix it yourself. > > Now uname -a is reported as: > OpenBSD host.hostname.net 3.8 GENERIC#0 i386 > > So it appears that the kernel upgrade was successful...I hope. Check dmesg for more details. The first few lines contain the details your're looking for. > > Now I'm tryig to upgrade the binaries by executing the following commands: > > # cd /usr/src/ > # rm -r /usr/obj/* > # make obj && make build > > It starts to compile but then gives me this error: > > ===> lib/libpthread > "Makefile", line 29: Could not find > /usr/src/lib/libpthread/include/Makefile.inc > Fatal errors encountered -- cannot continue > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > > I'm not sure why it's missing that file as I performed a cvs checkout just > last night using this command: > > # cd /usr; cvs checkout -P -rOPENBSD_3_8 src > > I just did: > > # cd /usr/src; rm -rf * > # cd /usr; cvs checkout -P -rOPENBSD_3_8 src Some mirrors seem to be borked; try again in a few hours. > > So, my questions are these: > > 1. Was this an appropriate way of doing the kernel upgrade? > 2. How do I correctly clean up from the failed binary build? Is this ok: > # cd /usr/obj/; rm -r * Yes. > 3. How do I fix the error so it compiles correctly...assuming that the file > shows up from the second cvs checkout just do "make obj" and "make build" > 4. Once it compiles correctly, how do I install the binaries? The upgade > page does not include this information. Make build installs the binaries.. -Otto
Re: Problems upgrading to 3.8-stable
I followed the steps in that page using sudo, no problems. On 3/11/06, Mike Loiterman <[EMAIL PROTECTED]> wrote: > I'm following the instructions at http://openbsd.org/stable/html to upgrade > to 3.8-stable. > > Everything works as it is supposed to until I get to the part where I am > supposed to copy the newly compiled kernel into /. I execute the command > and get this error: > > # cp bsd /bsd > cp: /bsd: Operation not permitted > > I got around this by setting /etc/rc.securelevel to 0, rebooting, and then > executing the commands: > > # chflags noschg /bsd > # cp /usr/src/sys/arch/i386/compile/GENERIC/bsd /bsd > # chflags schg /bsd > > Then changing /etc/rc.securelevel back to 1 and rebooting. > > Now uname -a is reported as: > OpenBSD host.hostname.net 3.8 GENERIC#0 i386 > > So it appears that the kernel upgrade was successful...I hope. > > Now I'm tryig to upgrade the binaries by executing the following commands: > > # cd /usr/src/ > # rm -r /usr/obj/* > # make obj && make build > > It starts to compile but then gives me this error: > > ===> lib/libpthread > "Makefile", line 29: Could not find > /usr/src/lib/libpthread/include/Makefile.inc > Fatal errors encountered -- cannot continue > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > > I'm not sure why it's missing that file as I performed a cvs checkout just > last night using this command: > > # cd /usr; cvs checkout -P -rOPENBSD_3_8 src > > I just did: > > # cd /usr/src; rm -rf * > # cd /usr; cvs checkout -P -rOPENBSD_3_8 src > > So, my questions are these: > > 1. Was this an appropriate way of doing the kernel upgrade? > 2. How do I correctly clean up from the failed binary build? Is this ok: > # cd /usr/obj/; rm -r * > 3. How do I fix the error so it compiles correctly...assuming that the file > shows up from the second cvs checkout > 4. Once it compiles correctly, how do I install the binaries? The upgade > page does not include this information. > > Thanks for the help. > > -- > Mike Loiterman > grantADLER > Tel: 630-302-4944 > Fax: 773-442-0992 > Email: [EMAIL PROTECTED] > PGP Key: 0xD1B9D18E
Problems upgrading to 3.8-stable
I'm following the instructions at http://openbsd.org/stable/html to upgrade to 3.8-stable. Everything works as it is supposed to until I get to the part where I am supposed to copy the newly compiled kernel into /. I execute the command and get this error: # cp bsd /bsd cp: /bsd: Operation not permitted I got around this by setting /etc/rc.securelevel to 0, rebooting, and then executing the commands: # chflags noschg /bsd # cp /usr/src/sys/arch/i386/compile/GENERIC/bsd /bsd # chflags schg /bsd Then changing /etc/rc.securelevel back to 1 and rebooting. Now uname -a is reported as: OpenBSD host.hostname.net 3.8 GENERIC#0 i386 So it appears that the kernel upgrade was successful...I hope. Now I'm tryig to upgrade the binaries by executing the following commands: # cd /usr/src/ # rm -r /usr/obj/* # make obj && make build It starts to compile but then gives me this error: ===> lib/libpthread "Makefile", line 29: Could not find /usr/src/lib/libpthread/include/Makefile.inc Fatal errors encountered -- cannot continue *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. I'm not sure why it's missing that file as I performed a cvs checkout just last night using this command: # cd /usr; cvs checkout -P -rOPENBSD_3_8 src I just did: # cd /usr/src; rm -rf * # cd /usr; cvs checkout -P -rOPENBSD_3_8 src So, my questions are these: 1. Was this an appropriate way of doing the kernel upgrade? 2. How do I correctly clean up from the failed binary build? Is this ok: # cd /usr/obj/; rm -r * 3. How do I fix the error so it compiles correctly...assuming that the file shows up from the second cvs checkout 4. Once it compiles correctly, how do I install the binaries? The upgade page does not include this information. Thanks for the help. -- Mike Loiterman grantADLER Tel: 630-302-4944 Fax: 773-442-0992 Email: [EMAIL PROTECTED] PGP Key: 0xD1B9D18E
Re: Pre-orders for our releases.
On 3/11/06, Diana Eichert <[EMAIL PROTECTED]> wrote: > On Fri, 10 Mar 2006, Kevin wrote: > SNIP > > Right. > > Because for-profit businesses wants to see return on their "investment", > > thus a company will seldom give stuff away because it feels good. > > Then you ( the generic you ) needs to do a better job of explaining to > management the cost savings associated with using OpenBSD. Management is > only interested in ROI, I know I used to be one. Part of the cost savings is that there is no need for a per-machine license, so the company purchases one copy of each release CD set. On 3/11/06, L. V. Lammert <[EMAIL PROTECTED]> wrote: > That's a bunch of crap, really - funds spent purchasing OBSD product is a > valid business expense. As such, it if fully 'deductible' according to the > IRS rules. And again, the company buys exactly one release set every six months. > When you kick in a few more dollars, there's no problem > 'deducting' it as a normal business expense for 'consulting' - which it > is, expending budget for technical advice obtained. I'll have to try this argument on management, but I don't think I'll get very far :) Kevin
Re: SGI's
On Sat, 11 Mar 2006 10:21:55 -0800 "Roger Neth Jr" <[EMAIL PROTECTED]> wrote: > -- Forwarded message -- > From: Roger Neth Jr <[EMAIL PROTECTED]> > Date: Mar 11, 2006 10:19 AM > Subject: Re: SGI's > To: Jason Crawford <[EMAIL PROTECTED]> > > > On 3/11/06, Jason Crawford <[EMAIL PROTECTED]> wrote: > > On 3/11/06, Roger Neth Jr <[EMAIL PROTECTED]> wrote: > > > On 3/11/06, Jason Crawford <[EMAIL PROTECTED]> wrote: > > > > I am soon going to be getting an Octane with dual R12000SC CPUs. I was > > > > wondering how well OpenBSD would work on this computer (I am pretty > > > > sure there isn't SMP support on the SGI stuff yet) and how much help > > > > is needed in getting the SGI port to work even better. > > > > > > > > Jason > > > > > > > > > > > > > > Hello, I setup an SGI 02 with 3.8 last year and runs without a > > > problem. The only problem I had was understanding the SGI boot methods > > > and partitions. Once I understood that no problem. > > > > > > As far as I know there isn't any X yet and I connect serially. I think > > > X is being worked on. > > > > Serial would be best for me, the SGI monitor I have is like 21+ > > inches. I am pretty excited about trying this out, mips is one of the > > archs I don't have much experience with yet (some basic IRIX admin > > before, but that's it), so when I found one I thought I'd add it to my > > already somewhat large personal collection of differnet archs. I just > > wish I had a second one I could donate to the OpenBSD guys (SMP > > support would kick ass). > > > > Jason > > > > Last year I put OpenBSD on Sun Sparc (web server), DEC Alpha > (firewall), plethora of i386's (laptops & desktops), one SMP on IBM > x220 P3 (test machine). > > I would like to use OpenBSD with world wide missionaries as it is easy > to setup and use, especially on older hardware. I anticipate that with > Microsoft Vista coming out there will be a lot of old hardware > available for OpenBSD. : ) > > OpenBSD just keeps getting better and better all the time. Which > reminds me to pre-order my CD's and t-shirt. > > rogern > > John 3:16 Hi there Past few years (in fact since 2.6) i installed OpenBSD on several arches such as sparc 'n sparc 64 Dec Alpha 'n decstation even old 68k macs and i really love to have the same OS on these . Only my old powermac and my old indy are still running under the vendor operating system . Except this fairly old pc , all the computers i use are running OpenBSD. That's why each time i can ... i donate ... ~~ http://www.chatou-informatic.com Maintenance, infogerance, interventions sur site, telemaintenance
SGI's
-- Forwarded message -- From: Roger Neth Jr <[EMAIL PROTECTED]> Date: Mar 11, 2006 10:19 AM Subject: Re: SGI's To: Jason Crawford <[EMAIL PROTECTED]> On 3/11/06, Jason Crawford <[EMAIL PROTECTED]> wrote: > On 3/11/06, Roger Neth Jr <[EMAIL PROTECTED]> wrote: > > On 3/11/06, Jason Crawford <[EMAIL PROTECTED]> wrote: > > > I am soon going to be getting an Octane with dual R12000SC CPUs. I was > > > wondering how well OpenBSD would work on this computer (I am pretty > > > sure there isn't SMP support on the SGI stuff yet) and how much help > > > is needed in getting the SGI port to work even better. > > > > > > Jason > > > > > > > > > > Hello, I setup an SGI 02 with 3.8 last year and runs without a > > problem. The only problem I had was understanding the SGI boot methods > > and partitions. Once I understood that no problem. > > > > As far as I know there isn't any X yet and I connect serially. I think > > X is being worked on. > > Serial would be best for me, the SGI monitor I have is like 21+ > inches. I am pretty excited about trying this out, mips is one of the > archs I don't have much experience with yet (some basic IRIX admin > before, but that's it), so when I found one I thought I'd add it to my > already somewhat large personal collection of differnet archs. I just > wish I had a second one I could donate to the OpenBSD guys (SMP > support would kick ass). > > Jason > Last year I put OpenBSD on Sun Sparc (web server), DEC Alpha (firewall), plethora of i386's (laptops & desktops), one SMP on IBM x220 P3 (test machine). I would like to use OpenBSD with world wide missionaries as it is easy to setup and use, especially on older hardware. I anticipate that with Microsoft Vista coming out there will be a lot of old hardware available for OpenBSD. : ) OpenBSD just keeps getting better and better all the time. Which reminds me to pre-order my CD's and t-shirt. rogern John 3:16
Re: Pre-orders for our releases.
On Fri, 10 Mar 2006, Kevin wrote: SNIP > Right. > Because for-profit businesses wants to see return on their "investment", > thus a company will seldom give stuff away because it feels good. Then you ( the generic you ) needs to do a better job of explaining to management the cost savings associated with using OpenBSD. Management is only interested in ROI, I know I used to be one. > I'm working right now to donate hardware (mostly for Todd and Marco). > About to ship the small stuff (SCSI and FCAL gear), but it's non-trivial > to convince a Fortune 500 to "donate" anything without even getting a > tax write-off in return. Try this with a government agency someday. I see G5's already in our reapplication area. > Last year I gave ten weeks of electricity for the machine room to OpenBSD. > Meanwhile my employer bought exactly *two* CDs, and I had to push for that. > > Kevin Kadow Good to hear, now just keep doing this and hope that others will join in. diana
Re: SGI's
On 3/11/06, Jason Crawford <[EMAIL PROTECTED]> wrote: > On 3/11/06, Roger Neth Jr <[EMAIL PROTECTED]> wrote: > > On 3/11/06, Jason Crawford <[EMAIL PROTECTED]> wrote: > > > On 3/11/06, Roger Neth Jr <[EMAIL PROTECTED]> wrote: > > > > On 3/11/06, Jason Crawford <[EMAIL PROTECTED]> wrote: > > > > > I am soon going to be getting an Octane with dual R12000SC CPUs. I was > > > > > wondering how well OpenBSD would work on this computer (I am pretty > > > > > sure there isn't SMP support on the SGI stuff yet) and how much help > > > > > is needed in getting the SGI port to work even better. > > > > > > > > > > Jason > > > > > > > > > > > > > > > > > > Hello, I setup an SGI 02 with 3.8 last year and runs without a > > > > problem. The only problem I had was understanding the SGI boot methods > > > > and partitions. Once I understood that no problem. > > > > > > > > As far as I know there isn't any X yet and I connect serially. I think > > > > X is being worked on. > > > > > > Serial would be best for me, the SGI monitor I have is like 21+ > > > inches. I am pretty excited about trying this out, mips is one of the > > > archs I don't have much experience with yet (some basic IRIX admin > > > before, but that's it), so when I found one I thought I'd add it to my > > > already somewhat large personal collection of differnet archs. I just > > > wish I had a second one I could donate to the OpenBSD guys (SMP > > > support would kick ass). > > > > > > Jason > > > > > > > Last year I put OpenBSD on Sun Sparc (web server), DEC Alpha > > (firewall), plethora of i386's (laptops & desktops), one SMP on IBM > > x220 P3 (test machine). > > > > I would like to use OpenBSD with world wide missionaries as it is easy > > to setup and use, especially on older hardware. I anticipate that with > > Microsoft Vista coming out there will be a lot of old hardware > > available for OpenBSD. : ) > > > > OpenBSD just keeps getting better and better all the time. Which > > reminds me to pre-order my CD's and t-shirt. > > Yeah I put it just about everywhere, and use it at work. My personal > collection of archs is now at: x86, sparc, sparc64, sgi, hppa, hp300, > alpha, and an old mac68k somewhere. Already pre-ordered my CD's, I > just wish they had SGI and Alpha on them. I might be able to get a > commador 64 at some point, but I think my fiance is going to shoot me > if I bring another computer home. > > Jason > LOL, I know what you mean about all the computers. I am thankful that I have an office and the power bill is part of the monthly rent. I promised my Father in Heaven I was not going to buy any more computers! And I haven't! Best regards, rogern Job 23:10
Re: SGI's
On 3/11/06, Roger Neth Jr <[EMAIL PROTECTED]> wrote: > On 3/11/06, Jason Crawford <[EMAIL PROTECTED]> wrote: > > I am soon going to be getting an Octane with dual R12000SC CPUs. I was > > wondering how well OpenBSD would work on this computer (I am pretty > > sure there isn't SMP support on the SGI stuff yet) and how much help > > is needed in getting the SGI port to work even better. > > > > Jason > > > > > > Hello, I setup an SGI 02 with 3.8 last year and runs without a > problem. The only problem I had was understanding the SGI boot methods > and partitions. Once I understood that no problem. > > As far as I know there isn't any X yet and I connect serially. I think > X is being worked on. Serial would be best for me, the SGI monitor I have is like 21+ inches. I am pretty excited about trying this out, mips is one of the archs I don't have much experience with yet (some basic IRIX admin before, but that's it), so when I found one I thought I'd add it to my already somewhat large personal collection of differnet archs. I just wish I had a second one I could donate to the OpenBSD guys (SMP support would kick ass). Jason
Re: SGI's
On 3/11/06, Jason Crawford <[EMAIL PROTECTED]> wrote: > I am soon going to be getting an Octane with dual R12000SC CPUs. I was > wondering how well OpenBSD would work on this computer (I am pretty > sure there isn't SMP support on the SGI stuff yet) and how much help > is needed in getting the SGI port to work even better. > > Jason > > Hello, I setup an SGI 02 with 3.8 last year and runs without a problem. The only problem I had was understanding the SGI boot methods and partitions. Once I understood that no problem. As far as I know there isn't any X yet and I connect serially. I think X is being worked on. rogern Romans 6:23
SGI's
I am soon going to be getting an Octane with dual R12000SC CPUs. I was wondering how well OpenBSD would work on this computer (I am pretty sure there isn't SMP support on the SGI stuff yet) and how much help is needed in getting the SGI port to work even better. Jason
Re: FW: Pre-orders for our releases.
On Fri, 10 Mar 2006, Greg Thomas wrote: > On 3/10/06, Craig Ryhorchuk <[EMAIL PROTECTED]> wrote: > > > > > > > I wouldn't go quite that far. Corporate anywhere cares about charity. > > No, they don't care about charity. They care about tax deductions. > There is a big difference between the two. I think this is a reason > why Theo is loathe to start a non-profit organization and I completely > agree. > That's a bunch of crap, really - funds spent purchasing OBSD product is a valid business expense. As such, it if fully 'deductible' according to the IRS rules. When you kick in a few more dollars, there's no problem 'deducting' it as a normal business expense for 'consulting' - which it is, expending budget for technical advice obtained. Anyone looking for charity is telling the bean counters 'hey, look at us! we want you to ask more questions! We need more problems!' Lee Leland V. Lammert[EMAIL PROTECTED] Chief Scientist Omnitec Corporation Network/Internet Consultants www.omnitec.net
Re: akbd.c:akbd_capslockwrapper() kills remapping of capslock
On Sat, Mar 11, 2006 at 01:26:25PM +, Miod Vallat wrote: > > Isn't there any reliable way to detect *what* kind of keyboard is > > in use and then decide wether the hack in akbd_capslockwrapper() > > is necessary or not? > > No. But what about this diff? As you note, quite messy, but it works for me. However, I didn't test the behaviour of the reset key wrt status of caps lock. Ciao, Kili
Re: akbd.c:akbd_capslockwrapper() kills remapping of capslock
> Hi,
>
> last weekend, I noticed that after a
>
> $ wsconsctl keyboard.map+="keysym Caps_Lock = Control_L"
>
> on my PowerBook G4 the capslock key did *not* any longer behave
> like a control key. Instead it just has *no* effect at all, which
> isn't very surprising when looking at akbd_capslockwrapper() in
> akbd.c.
>
> Isn't there any reliable way to detect *what* kind of keyboard is
> in use and then decide wether the hack in akbd_capslockwrapper()
> is necessary or not?
No. But what about this diff?
Miod
Index: akbd.c
===
RCS file: /cvs/src/sys/dev/adb/akbd.c,v
retrieving revision 1.4
diff -u -p -r1.4 akbd.c
--- akbd.c 2006/02/12 21:49:08 1.4
+++ akbd.c 2006/03/11 13:23:07
@@ -128,6 +128,7 @@ akbdattach(struct device *parent, struct
sc->handler_id = aa_args->handler_id;
sc->sc_leds = (u_int8_t)0x00; /* initially off */
+ sc->sc_caps = 0;
adbinfo.siServiceRtPtr = (Ptr)akbd_adbcomplete;
adbinfo.siDataAreaAddr = (caddr_t)sc;
@@ -453,6 +454,30 @@ akbd_rawrepeat(void *v)
#endif
/*
+ * The ``caps lock'' key is special: since on earlier keyboards, the physical
+ * key stays down when pressed, we will get a notification of the key press,
+ * but not of the key release. Then, when it is pressed again, we will not get
+ * a notification of the key press, but will see the key release.
+ *
+ * This is not exactly true. We see the missing release and press events both
+ * as the release of the power (reset) key.
+ *
+ * To avoid confusing them with real power key presses, we maintain two
+ * states for the caps lock key: logically down (from wscons' point of view),
+ * and ``physically'' down (from the adb messages point of view), to ignore
+ * the power key. But since one may press the power key while the caps lock
+ * is held down, we also have to remember the state of the power key... this
+ * is quite messy.
+ */
+
+/*
+ * Values for caps lock state machine
+ */
+#defineCL_DOWN_ADB 0x01
+#defineCL_DOWN_LOGICAL 0x02
+#defineCL_DOWN_RESET 0x04
+
+/*
* Given a keyboard ADB event, decode the keycodes and pass them to wskbd.
*/
void
@@ -468,10 +493,24 @@ akbd_processevent(struct akbd_softc *sc,
* 0x on release, and we ignore it.
*/
if (event->bytes[0] == event->bytes[1] &&
- ADBK_KEYVAL(event->bytes[0]) == ADBK_RESET)
- break;
- akbd_capslockwrapper(sc, event->bytes[0]);
- akbd_capslockwrapper(sc, event->bytes[1]);
+ ADBK_KEYVAL(event->bytes[0]) == ADBK_RESET) {
+ if (event->bytes[0] == ADBK_KEYDOWN(ADBK_RESET))
+ SET(sc->sc_caps, CL_DOWN_RESET);
+ else {
+ if (ISSET(sc->sc_caps, CL_DOWN_RESET))
+ CLR(sc->sc_caps, CL_DOWN_RESET);
+ else if (ISSET(sc->sc_caps, CL_DOWN_ADB)) {
+ akbd_input(sc, ISSET(sc->sc_caps,
+ CL_DOWN_LOGICAL) ?
+ ADBK_KEYDOWN(ADBK_CAPSLOCK) :
+ ADBK_KEYUP(ADBK_CAPSLOCK));
+ sc->sc_caps ^= CL_DOWN_LOGICAL;
+ }
+ }
+ } else {
+ akbd_capslockwrapper(sc, event->bytes[0]);
+ akbd_capslockwrapper(sc, event->bytes[1]);
+ }
break;
default:
#ifdef DIAGNOSTIC
@@ -486,22 +525,11 @@ akbd_processevent(struct akbd_softc *sc,
void
akbd_capslockwrapper(struct akbd_softc *sc, int key)
{
- /*
-* Caps lock is special: since on earlier keyboards, the physical
-* key stays down when pressed, we will get a notification of the
-* key press, but not of the key release. Then, when it is pressed
-* again, we will not get a notification of the key press, but will
-* see the key release.
-* For proper wskbd operation, we should report each capslock
-* notification as both events (press and release).
-*/
- if (ADBK_KEYVAL(key) == ADBK_CAPSLOCK) {
- akbd_input(sc, ADBK_KEYDOWN(ADBK_CAPSLOCK));
- akbd_input(sc, ADBK_KEYUP(ADBK_CAPSLOCK));
- } else {
- if (key != 0xff)
- akbd_input(sc, key);
- }
+ if (ADBK_KEYVAL(key) == ADBK_CAPSLOCK)
+ sc->sc_caps ^= CL_DOWN_ADB;
+
+ if (key != 0xff)
+ akbd_input(sc, key);
}
int adb_polledkey;
Index: akbdvar.h
===
RCS file: /cvs/src/sys/dev/adb/akbdvar.h,v
retrieving revision 1.1
diff -u -p -r1.1 akbdvar.h
--- akbd
akbd.c:akbd_capslockwrapper() kills remapping of capslock
Hi, last weekend, I noticed that after a $ wsconsctl keyboard.map+="keysym Caps_Lock = Control_L" on my PowerBook G4 the capslock key did *not* any longer behave like a control key. Instead it just has *no* effect at all, which isn't very surprising when looking at akbd_capslockwrapper() in akbd.c. Isn't there any reliable way to detect *what* kind of keyboard is in use and then decide wether the hack in akbd_capslockwrapper() is necessary or not? Ciao, Kili dmesg: [ using 339044 bytes of bsd ELF symbol table ] console out [ATY,Jasper_A]console in [keyboard] USB and ADB found, using USB using parent ATY,JasperParent:: memaddr b800 size 800, : consaddr b8008000, : ioaddr b002, size 2: memtag 8000, iotag 8000: width 1280 linebytes 1280 height 854 depth 8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2006 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 3.9-current (GENERIC) #139: Fri Mar 10 22:32:10 CET 2006 [EMAIL PROTECTED]:/var/compile/GENERIC real mem = 1073741824 (1048576K) avail mem = 978173952 (955248K) using 1254 buffers containing 53686272 bytes (52428K) of memory mainbus0 (root): model PowerBook5,4 cpu0 at mainbus0: 7447A (Revision 0x101): 1333 MHz: 512KB L2 cache memc0 at mainbus0: uni-n "hw-clock" at memc0 not configured ki2c0 at memc0 offset 0xf8001000 iic0 at ki2c0 adt0 at iic0 addr 0xae: adt7460 (ADT7460) rev 62 "lmu-controller" at iic0 addr 0x42 not configured mpcpcibr0 at mainbus0 pci: uni-north, Revision 0xff pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 "Apple UniNorth AGP" rev 0x00 vgafb0 at pci0 dev 16 function 0 "ATI Radeon Mobility M10 NP" rev 0x00, mmio wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation) mpcpcibr1 at mainbus0 pci: uni-north, Revision 0x5 pci1 at mpcpcibr1 bus 0 pchb1 at pci1 dev 11 function 0 "Apple UniNorth PCI" rev 0x00 "Broadcom BCM4306" rev 0x03 at pci1 dev 18 function 0 not configured cbb0 at pci1 dev 19 function 0 "Texas Instruments PCI1510 CardBus" rev 0x00: irq 53 macobio0 at pci1 dev 23 function 0 "Apple Intrepid" rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 macgpio0 at macobio0 offset 0x50 "modem-reset" at macgpio0 offset 0x1d not configured "modem-power" at macgpio0 offset 0x1c not configured macgpio1 at macgpio0 offset 0x9 irq 47 "programmer-switch" at macgpio0 offset 0x11 not configured "cpu-vcore-select" at macgpio0 offset 0x6b not configured "gpio4" at macgpio0 offset 0x1e not configured "gpio5" at macgpio0 offset 0x6f not configured "gpio6" at macgpio0 offset 0x70 not configured "extint-gpio4" at macgpio0 offset 0x5c not configured "gpio11" at macgpio0 offset 0x75 not configured "extint-gpio15" at macgpio0 offset 0x67 not configured "escc-legacy" at macobio0 offset 0x12000 not configured zsc0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zsc0 channel 0 zstty1 at zsc0 channel 1 aoa0 at macobio0 offset 0x1: irq 30,1,2 audio0 at aoa0 "timer" at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000 irq 25: via-pmu, 3 targets akbd0 at adb0 addr 2: iBook keyboard with inverted T (ISO layout) wskbd0 at akbd0 mux 1 wskbd0: connecting to wsdisplay0 ams0 at adb0 addr 3: EMP trackpad 4-button, 400 dpi wsmouse0 at ams0 mux 0 abtn0 at adb0 addr 7: brightness/volume/eject buttons apm0 at adb0: battery flags 0x5, 99% charged pi2c0 at adb0 iic1 at pi2c0 "battery" at macobio0 offset 0x0 not configured "backlight" at macobio0 offset 0xf300 not configured ki2c1 at macobio0 offset 0x18000 iic2 at ki2c1 wdc0 at macobio0 offset 0x2 irq 24: DMA atapiscsi0 at wdc0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom removable cd0(wdc0:0:0): using BIOS timings, DMA mode 2 ohci0 at pci1 dev 24 function 0 "Apple Intrepid USB" rev 0x00: irq 0, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Apple OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ohci1 at pci1 dev 25 function 0 "Apple Intrepid USB" rev 0x00: irq 0, version 1.0, legacy support usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: Apple OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ohci2 at pci1 dev 26 function 0 "Apple Intrepid USB" rev 0x00: irq 29, version 1.0, legacy support usb2 at ohci2: USB revision 1.0 uhub2 at usb2 uhub2: Apple OHCI root hub, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ohci3 at pci1 dev 27 function 0 "NEC USB" rev 0x43: irq 63, version 1.0 usb3 at ohci3: USB revision 1.0 uhub3 at usb3 uhub3: NEC OHCI root hub, rev 1.00/1.00, addr 1 uhub3: 3 ports with 3 removable, self powered ohci4 at pci1 dev 27 function 1 "NEC USB" rev 0x43: irq 63, version 1.0 usb4 at ohci4: USB revision 1.0 uhub4 at usb4 uhub4: NEC OHCI root hub, rev 1.00/1.00, addr 1 uhub4: 2 ports with 2 removable, self powered ehci0 at pci1 dev 27 function 2 "NEC
ath0 testing - good news and bad news
Ok, so I have two ath devices, one Netgear WAB501 which is an
AR5211-based chip and one Cisco AIR-CB21AG-A-K9 which is AR5212-based.
Originally I had posted that if I set the Cisco to mode 11b I could
connect to my current 802.11b network. For some reason that has
stopped working. I get the following console messages when inserting
or trying to set the mode:
cbb1: bad Vcc request. sock_ctrl 0x0, sock_status 0x3b69
cbb1: bad Vcc request. sock_ctrl 0x30, sock_status 0x3b20
cbb1: bad Vcc request. sock_ctrl 0x0, sock_status 0x3b69
ar5k_ar5212_nic_wakeup: failed to resume the AR5212 (again)
ath0: ath_chan_set: unable to reset channel 11 (2462 Mhz)
ath0 detached
cbb1: bad Vcc request. sock_ctrl 0x0, sock_status 0x3386
cbb1: bad Vcc request. sock_ctrl 0x30, sock_status 0x3b20
ath0 at cardbus1 dev 0 function 0 "Atheros Communications, Inc.,
AR5001--
, Wireless LAN Reference Card": irq 11
ath0: AR5212 5.6 phy 4.1 rf5112 3.6, FCC1A, address 00:40:96:a2:fa:f4
So I gave up on that for now and popped the Netgear in and configured
it for hostap. And it worked! I threw the Cisco into an XP laptop
and had them talking in no time. My current AP is running 3.7 so I
haven't tried the Netgear in it yet.
However, with the Netgear still in this OpenBSD laptop I tried to get
it to connect to my AP. With the Cisco the only success I had was
when I set the mode to 11b which doesn't work for the Netgear either.
With it set to the default auto it just cycles through all the mode
combos.
So to sum up: the Netgear WAB501 is working in hostap mode. The
Cisco isn't working as an AP or to connect to my existing 802.11b
network, and I can't get the Netgear to connect to an existing network
either.
OpenBSD 3.8 (GENERIC) #0: Sun Jan 8 23:39:30 PST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 697 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXS
R,SSE
real mem = 267952128 (261672K)
avail mem = 237613056 (232044K)
using 3296 buffers containing 13500416 bytes (13184K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(98) BIOS, date 12/21/99, BIOS32 rev. 0 @ 0xfd820
apm0 at bios0: Power Management spec V1.2
apm0: battery life expectancy 98%
apm0: AC on, battery charge high
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xfd7b0/0x850
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdee0/208 (11 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #3 is the last bus
bios0: ROM list: 0xc/0xc000 0xe/0x1
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "S3 Savage/IX-MV" rev 0x11
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
cbb0 at pci0 dev 2 function 0 "Texas Instruments PCI1450 CardBus" rev 0x03: irq
11
cbb1 at pci0 dev 2 function 1 "Texas Instruments PCI1450 CardBus" rev 0x03: irq
11
"AT&T/Lucent LTMODEM" rev 0x01 at pci0 dev 3 function 0 not configured
clcs0 at pci0 dev 5 function 0 "Cirrus Logic CS4280/46xx CrystalClear" rev 0x01:
irq 11
ac97: codec id 0x43525914 (Cirrus Logic CS4297A rev 4)
ac97: codec features headphone, 20 bit DAC, 18 bit ADC, Crystal Semi 3D
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 wi
red to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 11509MB, 23572080 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0
5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x01: 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
"Intel 82371AB Power" rev 0x03 at pci0 dev 7 function 3 not configured
cbb0: bad Vcc request. sock_ctrl 0x0, sock_status 0x3b20
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 2 device 0 cacheline 0x8, lattimer 0xb0
pcmcia0 at cardslot0
cbb1: bad Vcc request. sock_ctrl 0x0, sock_status 0x3386
cardslot1 at cbb1 slot 1 flags 0
cardbus1 at cardslot1: bus 3 device 0 cacheline 0x8, lattimer 0xb0
pcmcia1 at cardslot1
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
sysbeep0 at pcppi0
lpt2 at isa0 port 0x3bc/4: pol
