out of swap error?
Hello, I've got a freshly installed amd64 (dual core opteron) system running the latest snapshot (bsd.mp kernel). I have 1GB of ram and a 1GB swap partition. The machine has next to nothing on it at this point, not even X. The only packages I have installed are postfix, fetchmail and procmail (all from the latest openbsd snapshot). After letting the system sit for about 24 hours I sat down on the console to find a dozen or so out of swap errors like this: UVM: pid 23358 (sshd), uid 0 killed: out of swap UVM: pid 11042 (newsyslog), uid 0 killed: out of swap etc... I had an ssh session already open into the box so I was able to execute top. Top showed very little memory usage (about 10MB) and no swap usage. I've searched the net and usenet for similar issues but the only posters I see having such problems are people trying to run extremely minimal systems like 16MB of ram and no swap partition. Any ideas on how I could be out of swap when I seemingly wasn't using hardly any RAM and no swap? Thanks, Jeff
Re: MacPro (Quad Intel Xeon 5150 dual-core) support?
On Mon, 4 Sep 2006, Anon Y. Mous wrote: Is support planned for Woodcrest? MacPro Quad Xeon tower? Sure, if you send us a machine; these beasts generally do not just appear in my (or any other developers') house. -Otto
Re: Unable to build jdk-1.4.2p7 on OpenBSD/i386 3.9-GENERIC
On Mon, Sep 04, 2006 at 09:53:56AM +0400, Bruno Carnazzi wrote: Hi misc, I can't build jdk-1.4.2p7 on my openbsd box (3.9 running in MS-VirtualServer)... Can somebody help ? jdk-1.3.1p6, jre-1.3.1p6 and jdk-linux-1.3.1_16 succeeded. Here's the logs : Target Build Versions: JAVAWS_VERSION = 1.4.2 MILESTONE = p7 BUILD_NUMBER = _04_sep_2006_03_38 ERROR: Your JAVAWS_BOOTDIR environment variable does not point to a valid Java 2 SDK for bootstrapping this build. A Java 2 SDK 1.4 build must be bootstrapped using J2SDK 1.4.0 fcs (or later). Apparently, your bootstrap JDK is version Please update your ALT_JAVAWS_BOOTDIR setting and start your build again. Exiting because of the above error(s). Build it with no_plugin no_webstart flavours first. If you are on your way to 1.5, you wont need these anyway. Same goes for Tomcat, plugin and webstart are GUI desktop items.
netstat, socket, pid
What is the most elegant way to find out which pid/program belongs to which socket? netstat(1) and archive didn't help me in that case. Thanks, -- Stephan A. Rickauer --- Institut f|r Neuroinformatik Tel: +41 44 635 30 50 Universitdt / ETH Z|rich Sek: +41 44 635 30 52 Winterthurerstrasse 190 Fax: +41 44 635 30 53 CH-8057 Z|richWeb: www.ini.ethz.ch RSA public key: https://www.ini.ethz.ch/~stephan/pubkey.asc --- [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: netstat, socket, pid
Stephan A. Rickauer wrote: What is the most elegant way to find out which pid/program belongs to which socket? netstat(1) and archive didn't help me in that case. fstat # Han
tcp flags with tcpdum and pflog0
Hi list, I'm trying to find out if it is possible to see the tcp flags in a tcpdump output of the device pflog0 (blocked packets). When i take a physikal interface like em0 the following command shows me the tcp flags tcpdump -nevvvi em0 tcp But the same with pflog0 only shows me this further informations snip |tcp] (DF) (ttl 114, id 57665, len 48) /snip Thanks in advance. [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: The future of NetBSD
On Fri, Sep 01, 2006 at 11:59:57AM +0200, Gilbert Fernandes wrote: I have a dream. A dream of unification. Having one BSD. Merging the three projects and, why not, keeping incompatible stuff as options that would be either one or another. But when you tell yourself that it cannot be done, you don't even try it. It would require people to not only do it for the sake of their projects, but for the whole BSD people. Even those who really piss you off in other projects. Because someday, those projects will live on without us. We'll pass on like everyone. Am I alone thinking this ? Sure would be kind of nice, but in practice its nearly like saying, I want that the world gets one car. Please unify Mercedes, BMW, Ferrari, VW and all of their models ;-) With design goal: Modularize car in a way, that the different customer demands can be achieved as options. You'll get problems in many ways ... - too many different - partly contradictory - design goals. One car is more a racing car, the other tries to be kind to mother nature - too different customers demands - different company cultures ... - many leaders that have to give up their own goals and synchronize with each other - say good-bye to own companies history and habits and be open to be only part of a new team For a volunteer project it sounds nearly impossible to synchronize all the different people with different goals and culture to the project targets _and_ be productive and write good code ! If the situation of NetBSD is the way like Charles Hannum describes - I'm no insider therefore I formulate it carefully this way - then a possible way could be a fork of NetBSD. But does the world really needs one more BSD ? Maybe the discussion itself is useful for making a cut and trying to reorganize the team by avoiding all that turns out to be a misconception. If this is not possible and people are convinced a fork with a strong leader would bring more merits and productivity, then a fork still could be done later. A fork off alone from NetBSD by keeping all the CPU and architecture support might be very tricky and difficult. Its questionable if one person is able to draw good design decisions that are well for all different NetBSD ports (here I mean the different architectures). Maybe a fork would need to specialize on one or some CPU types that a small team is able to handle. Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? - http://www.apsfilter.org/
Re: The future of NetBSD
On Thu, Aug 31, 2006 at 06:50:00PM -0300, Marc G. Fournier wrote: On Thu, 31 Aug 2006, Constantine A. Murenin wrote: On 31/08/06, Marc G. Fournier [EMAIL PROTECTED] wrote: Just a stupid comment, but ... Linux is one kernel, multiple distributions ... BSD is, what, 4 kernels now? If we worked more together instead of as seperate camps, it might make things a bit easier, no? Isn't there still fewer differences between *BSD operating systems than between different GNU/Linux distributions and kernel releases? :) Put together a *BSD core ... representative from each camp and try and steer the *kernel* itself towards a more common BSD ... I doubt that'll be productive -- NetBSD, FreeBSD and OpenBSD have all different goals... Even at the kernel level? Look at device drivers and vendors as one example ... companies like adaptec have to write *one* device driver, for, what, 50+ distributions of linux ... for us, they need to write one for FreeBSD, one for NetBSD, one for OpenBSD, and *now* one for DragonflyBSD ... if we had *at least* a common API for that sort of stuff, it might be asier to get support at the vendor level, no? Are you really sure ? I see it more this way: For Linux on kernel (or device driver) level they only have to support 2 main trains: 2.4.x and 2.6.x. The 50 distributions are only a burden if it comes to the point what different shared library / Java / TCL / etc ... versions are packaged with the OS. A friend of mine doing Java development had severe issues with all that different Linux versions. But a simple kernel driver only has to honour different CPU types and the 2.4 and 2.6 tree and maybe now a development tree but am not sure on the latter ... Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? - http://www.apsfilter.org/
Re: The future of NetBSD
On Thu, Aug 31, 2006 at 08:14:31PM -0300, Marc G. Fournier wrote: On Thu, 31 Aug 2006, Miod Vallat wrote: If the vendor is supporting the driver, and working with the community, then one would hope that they would also fix the driver as bug reports come in about it ... That's too many ifs to be realworld-compatible. And actually the only vendors I can think of which are working with the community actually provide documentation, if only because it is simpler for them to spend time on documentation than on code for N different systems. ICP Vortex (aka Adaptec) were providing drivers on their web site for FreeBSD 4.x and 5.x that are included in both source trees ... it was a binary driver, as far as I'm aware, but source code ... and Adaptec doesn't provide documentation ... I don't think that binary only drivers are well enough. Surely better than nothing but ... Don't forget that an open source team sometimes makes api changes that might break a binary only driver. And companies sometimes are slow in fixing. Or the vendor did some mistakes in his own driver. First the paying customers are served. All the other folks (open source ..) surely will come last. For some smaller corps supporting open source developers is simply a burden that costs time and so money. I know this from a medium sized german company producing nice audio recording cards. It was impossible to get a card and documentation from them for a FreeBSD developers. And after weeks and months of asking via e-mail they decided finally to tell the truth that they don't want to support open source developers anymore, it makes too much work. They are unable to spend so much time answering open source developers questions although they got documentation. This experience they made with Linux developers. Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? - http://www.apsfilter.org/
Re: tcp flags with tcpdum and pflog0
On Tue, Sep 05, 2006 at 11:17:13AM +0200, J??rg Streckfu?? wrote: Hi list, I'm trying to find out if it is possible to see the tcp flags in a tcpdump output of the device pflog0 (blocked packets). When i take a physikal interface like em0 the following command shows me the tcp flags tcpdump -nevvvi em0 tcp But the same with pflog0 only shows me this further informations snip |tcp] (DF) (ttl 114, id 57665, len 48) /snip Thanks in advance. I believe this means the packet is truncated. I could be wrong, but if this is correct, add -s with an appropriate size [1]. Joachim [1] See tcpdump(8) and pflog(4) for details, or just pick a sufficiently large number - 200 is most likely wasteful already.
sharing ffs filesystems between NetBSD and OpenBSD
Hello! I am trying to understand an odd behaviour in the Berkeley Fast File System as implemented in both NetBSD and OpenBSD. My main concern is not getting a workaround for this problem (hopefully, I found one) but understanding if there are hidden issues than can damage files stored in these shared filesystems in the future. The scenario is the next one: I have three USB flash memory drives and an external USB HDD (a Plextor PX-PH08U). I want to make ffs filesystems on at least two of the flash memory drives and the HDD to share data between my laptop (running NetBSD) and three computers (running OpenBSD). These machines are running the latest stable releases of NetBSD and OpenBSD. All software is relatively updated (but I am not tracking -stable in either NetBSD or OpenBSD). By now, I will refrain using ffs2 filesystems as support for these new filesystems is not available in OpenBSD yet. (this was my filesystem choice when sharing these drives between both OSes was not an issue for me.) I will stay at ffs until ffs2 is available in OpenBSD. The problem: After doing the usual steps to set up a new disk in OpenBSD: # fdisk -i sd0 # disklabel -e sd0 (setting up the disk partition as 4.2BSD) # newfs sd0a (by the way, is the MBR *required* on i386 architectures when there is a single non-bootable primary partition on the drive? Can it be a problem when sharing these drives with non-i386 architectures? What about endianess behaviour in ffs/ffs2 in different architectures?) ...I see this BSD disklabel on OpenBSD with one of the flash memory drives: # Inside MBR partition 3: type A6 start 32 size 2007008 # /dev/rsd0c: type: SCSI disk: SCSI disk label: USB Flash Memory flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 980 total sectors: 2007040 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 200700832 4.2BSD 2048 16384 323 # Cyl 0*- 979 c: 2007040 0 unused 0 0 # Cyl 0 - 979 All is fine, I can mount and use that drive. But NetBSD is unable to identify the HDD. This is the way NetBSD reads the disklabel (the label field and disk partitions are certainly wrong): # /dev/rsd0d: type: SCSI disk: mydisk label: fictitious flags: removable bytes/sector: 512 sectors/track: 32 tracks/cylinder: 16 sectors/cylinder: 512 cylinders: 3920 total sectors: 2007040 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 8 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] d: 2007040 0 unused 0 0# (Cyl. 0 - 3919) h: 200700832unknown # (Cyl. 0*- 3919) disklabel: boot block size 0 disklabel: super block size 0 What I am doing wrong? Why is the disk geometry different on the output of each OS? When I make these filesystems in NetBSD I can see them and use them in OpenBSD too. But it certainly does not assure that problems will not happen in the future. Are there known incompatibilities between NetBSD's ffs and OpenBSD's ffs? Should I open a PR? Can it be related with the third partition in NetBSD? (usually, NetBSD has a partition that fills the entire disk, and another partition that fills the part of the disk that is being used by NetBSD.) By the way, when will ffs2 be available in OpenBSD? From the changelogs I see that there is some work being done in preparation for ffs2, these are excellent news. Thanks in advance for any help! Igor.
Re: ssh problem
Leonard Jacobs [EMAIL PROTECTED] wrote on Mon 4.Sep'06 at 22:22:30 -0400 I've configured a Soekris running OpenBSD 3.9 pf as a firewall, with a read only CF. I am using the default sshd_config file except to run sshd on port 222. /dev mounted read only ? If so, then thats your proplem. Load it as an mfs on boot. (image + vnd ? maybe or sth) My problem is that I cannot connect remotely to this box via ssh except as root. When a legit user who has an account on that box attempts connection, I get Failed password for invalid user lj from 192.168.1.13 port 10962 ssh2. Is there anything obvious that you can suggest that might be causing this problem? I did try changing the file system to read/write, but it did not resolve the problem. Thanks.
Question regarding mailserver setup
Hi, Im using postfix,amavisd,clamav,spamassassin on a OpenBSD 3.9 server. The setup works great. The problem I have is that I would like to use Razor or Pyzor. I tried and installed razor but it doesnt seem to work very well. On another Linux server I have Pyzor and it catches almost all spam I get. What is the best anti-spam solution to use for OpenBSD? Regards Jonas
Re: Question regarding mailserver setup
On Tue, Sep 05, 2006 at 12:58:31PM +0200, Jonas Thambert wrote: Hi, Im using postfix,amavisd,clamav,spamassassin on a OpenBSD 3.9 server. The setup works great. The problem I have is that I would like to use Razor or Pyzor. I tried and installed razor but it doesnt seem to work very well. On another Linux server I have Pyzor and it catches almost all spam I get. What is the best anti-spam solution to use for OpenBSD? as for me, greylisting seems to the most efficient( spamd or postgrey); i also use razor and dcc, but they aren't noticeably effective. Maybe this [1] will give you some hints( it covers DCC setup). - Lukasz Sztachanski [1] http://flakshack.com/anti-spam/wiki/index.php -- 0x058B7133 // 16AB 4EBC 29DA D92D 8DBE BC01 FC91 9EF7 058B 7133 http://entropy.pl http://entropy.pl/?blog
Re: tcp flags with tcpdum and pflog0
Am Tue, 5 Sep 2006 12:34:32 +0200 schrieb Joachim Schipper [EMAIL PROTECTED]: I believe this means the packet is truncated. I could be wrong, but if this is correct, add -s with an appropriate size [1]. Yeah, that's it. Thanks. Joerg [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
OpenBSD/i386 4.0 Install CD successfull boot on IBM HS20 BladeCenter !
Hi misc, I've spent some time in trying to install openbsd on some IBM HS20 and I didn't manage with 3.8 and 3.9. While trying with the 4.0-beta CD, I've found a way to boot. As I don't have some erasable HS20 available, I can't install it. If someone can post here a dmesg after installation, it would be great. The trick is really simple, you just have to disable pckbc driver : * Boot on cd40.iso * Boot in UKC (boot -c) * in UKC : disable pckbc exit That's all folks :) I think this should work too with 3.8 and 3.9. The setting can be made permanent with config(8). Best regards, Bruno
Re: OpenBSD/i386 4.0 Install CD successfull boot on IBM HS20 BladeCenter !
2006/9/5, Bruno Carnazzi [EMAIL PROTECTED]: Hi misc, I've spent some time in trying to install openbsd on some IBM HS20 and I didn't manage with 3.8 and 3.9. While trying with the 4.0-beta CD, I've found a way to boot. As I don't have some erasable HS20 available, I can't install it. If someone can post here a dmesg after installation, it would be great. The trick is really simple, you just have to disable pckbc driver : * Boot on cd40.iso * Boot in UKC (boot -c) * in UKC : disable pckbc exit That's all folks :) I don't know why, but you have to press a key at the beginning of the kernel load, if not, it won't boot... I think this should work too with 3.8 and 3.9. The setting can be made permanent with config(8). Doh... with 3.9-stable CD, this leads to a kernel panic :( Best regards, Bruno
Re: sharing ffs filesystems between NetBSD and OpenBSD
On 9/5/06, Igor Sobrado [EMAIL PROTECTED] wrote: Hello! I am trying to understand an odd behaviour in the Berkeley Fast File System as implemented in both NetBSD and OpenBSD. My main concern [...] Can it be a problem when sharing these drives with non-i386 architectures? Guessing that you are sharing files between big-endian and non-endian machines? You can't do that with ffs. NetBSD apears to have the option FFS_EI. That may help. A quick search indicates that nfs vnd trickery may be required. Good luck.
Replacing a failed HD in a raidframe array
I've had a failed HD in my raid array that I have finally bought a replacement for. It is bigger so it should be large enough. I just want a sanity check that I am doing the right thing. I have read the man pages, but hey it's my data, and even though I've got a backup, it is intimidating doing this for the first time. Anyway here we go. wd0 is the good HD and wd1 is the new drive. Partition tables: # disklabel /dev/wd0c # Inside MBR partition 3: type A6 start 63 size 234484677 # /dev/wd0c: type: ESDI disk: ESDI/IDE disk label: SAMSUNG SP1213N flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 234493056 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 209758563 4.2BSD 2048 16384 328 # Cyl 0*- 2080 b:524160 2097648swap # Cyl 2081 - 2600 c: 234493056 0 unused 0 0 # Cyl 0 -232631 d: 231862932 2621808RAID # Cyl 2601 -232623* # disklabel /dev/wd1c # Inside MBR partition 3: type A6 start 63 size 312576642 # /dev/wd1c: type: ESDI disk: ESDI/IDE disk label: WDC WD1600JB-00R flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 312581808 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 209758563 4.2BSD 2048 16384 328 # Cyl 0*- 2080 b:524160 2097648swap # Cyl 2081 - 2600 c: 234493056 0 unused 0 0 # Cyl 0 -232631 d: 231862932 2621808RAID # Cyl 2601 -232623* Array status: # raidctl -s raid0 raid0 Components: /dev/wd0d: optimal component1: failed No spares. Parity status: DIRTY Reconstruction is 100% complete. Parity Re-write is 100% complete. Copyback is 100% complete. So according to the raidctl(8) once I add the new HD to the system I do a raidctl -a /dev/hd1d to add it as a spare, then do a raidctl -F component1 raid0 to force a rebuild. Then I would modify my /etc/raid0.conf to reflect my new device (which actually won't need modification in my case). First question: do I have this correct? Second question: if the rebuild fails at 48% with bad disk block errors does this mean that wd0 is bad? Thanks in advance.
Re: sharing ffs filesystems between NetBSD and OpenBSD
On Tuesday 05 September 2006 11:13, Igor Sobrado wrote: Hello! I am trying to understand an odd behaviour in the Berkeley Fast File System as implemented in both NetBSD and OpenBSD. My main concern is not getting a workaround for this problem (hopefully, I found one) but understanding if there are hidden issues than can damage files stored in these shared filesystems in the future. The scenario is the next one: I have three USB flash memory drives and an external USB HDD (a Plextor PX-PH08U). I want to make ffs filesystems on at least two of the flash memory drives and the HDD to share data between my laptop (running NetBSD) and three computers (running OpenBSD). These machines are running the latest stable releases of NetBSD and OpenBSD. All software is relatively updated (but I am not tracking -stable in either NetBSD or OpenBSD). https://marc.theaimsgroup.com/?l=openbsd-miscm=115007748827114w=2 Conclusion from that thread seems to be that sharing FFS partitions between BSDs is a Bad Idea. Maybe you should consider using for example ext2 partition? I have that to share data between all 3 major families of systems ;) cut information I can't comment on -- viq
wpi0: could not lock memory
Hello I'm trying to make use of the new wpi(4) wireless driver for my Intel 3945ABG wireless card. I'm using the snapshot dated 09/01/06. After booting the machine for the first time I saw wpi0: could not lock memory repeated over and over. I tried installing the firmware (wpi-firmware-1.13.tgz) as instructed in the wpi(4) man page yet the error persists. Below is dmesg output, I do hope someone can help. Thanks a lot Tom OpenBSD 4.0 (GENERIC) #1103: Thu Aug 31 19:36:08 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Genuine Intel(R) CPU T2050 @ 1.60GHz (GenuineIntel 686-class) 1.61 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,EST,TM2 cpu0: unknown Enhanced SpeedStep CPU, msr 0x06130c2c06000c2c cpu0: using only highest and lowest power states cpu0: Enhanced SpeedStep 1600 MHz (1404 mV): speeds: 1600, 800 MHz real mem = 526544896 (514204K) avail mem = 472383488 (461312K) using 4256 buffers containing 26431488 bytes (25812K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(ab) BIOS, date 06/22/06, BIOS32 rev. 0 @ 0xfd5d0, SMBIOS rev. 2.4 @ 0xdc010 (38 entries) bios0: FUJITSU SIEMENS AMILO Pi 1505 pcibios0 at bios0: rev 2.1 @ 0xfd5d0/0xa30 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdea0/320 (18 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #6 is the last bus bios0: ROM list: 0xc/0xea00! 0xdc000/0x4000! 0xe4000/0x1800! 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 0xb008, 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 azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: irq 7 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: 0x04x/0x1057 (rev. 7.0), HDA version 1.0 azalia0: codec[0]: No support for modem function groups azalia0: codec[0]: No audio function groups azalia0: codec: 0x04x/0x10ec (rev. 3.0), HDA version 1.0 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02 pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02 pci2 at ppb1 bus 4 ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02 pci3 at ppb2 bus 5 wpi0 at pci3 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: irq 11wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory , address ff:ff:ff:ff:ff:ff uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: irq 5 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 10 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 3 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 11 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 5 ehci0: timed out waiting for BIOS 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 ppb3 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe2 pci4 at ppb3 bus 6 vendor O2 Micro, unknown product 0x00f7 (class serial bus subclass Firewire, rev 0x02) at pci4 dev 4 function 0 not configured sdhc0 at pci4 dev 4 function 2 vendor O2 Micro, unknown product 0x7120 rev 0x01: irq 3 sdmmc0 at sdhc0 vendor O2 Micro, unknown product 0x7130 (class mass storage subclass miscellaneous, rev 0x01) at pci4 dev 4 function 3
Re: sharing ffs filesystems between NetBSD and OpenBSD
In message [EMAIL PROTECTED], Jeff Quast writes: On 9/5/06, Igor Sobrado [EMAIL PROTECTED] wrote: Hello! I am trying to understand an odd behaviour in the Berkeley Fast File System as implemented in both NetBSD and OpenBSD. My main concern [...] Can it be a problem when sharing these drives with non-i386 architectures? Guessing that you are sharing files between big-endian and non-endian machines? Quite sure! I am certainly worried about big-endian and little-endian architectures. Sometimes a fix appears that allows a driver (usually written for i386 architectures) working on big-endian architectures. It works for drivers but, obviously, a filesystem is very different. We cannot make a filesystem endianess independent as it will make the new version of the filesystem incompatible with some architectures. You can't do that with ffs. These are bad news, but at least I hope that sharing filesystems between NetBSD and OpenBSD *on the same architecture* will be possible. Something like the Berkeley sockets API functions to convert integers to network byte order would be too expensive for a filesystem, though. Ok, then the second question remains. Why a ffs filesystem created on a HDD added to an OpenBSD system cannot be mounted on NetBSD? To be more precise, I cannot assure that a ffs filesystem created on OpenBSD cannot be mounted on NetBSD, I am guessing that the problem is in the BSD disklabel instead. Is making the BSD disklabel and filesystem on NetBSD the right answer to this problem? (it is the workaround I found when looking at the problem some days ago.) Can we expect other problems related with sharing these storage devices between both operating systems? I think that these external drives (mainly the 80 GB HDD) are not only an excellent way to share data -I certainly prefer using a local network for these purposes, it is faster and more reliable- but excellent media for storing data. But, to be *really* useful, I will need to share these filesystems between both operating systems. FAT32 is not the right answer to this problem. NetBSD apears to have the option FFS_EI. That may help. A quick search indicates that nfs vnd trickery may be required. Excellent advice! Certainly nfs has not endianess issues and the useful vnode driver can help in this matter in the same way it helps when mounting disk images (the first time I used vnd was mounting a disk image stored in a local disk... in few minutes I discovered that vnd is elegant and powerful, as the BSD operating system themselves.) But it is perhaps too complex, better staying at a single architecture. Certainly restricting ffs mounts to a single architecture is not a problem at all, but I would greatly appreciate some advice on the second question: why a disk created on OpenBSD cannot be mounted on NetBSD, if it is a known problem -or not a problem at all but an expected behaviour- and if we can safety share a filesystem created in NetBSD with OpenBSD. If it is a known behaviour of two different ffs implementations, I will need to make two sets of USB drives: one for NetBSD and other for OpenBSD and sharing files using scp. If it is a problem and it is currently not documented, I will do my best to provide as accurate information as possible in a problem report. Best regards! Igor.
Re: 5.1 sound card support in OpenBSD
On Monday 04 September 2006 09:13, you wrote: Hi misc, I can't find informations on 5.1 sound card support in OpenBSD. I know OpenBSD sound system relies on SunAudio, but I'm not aware of its capabilities. Best regards, Bruno. The best I could achive with OpenBSD is 4.1 :) I can't create output through center. see mixerctl(1), basicly you have to enable rear speakers (off by default) and a few other things.
Re: sharing ffs filesystems between NetBSD and OpenBSD
On Tuesday 05 September 2006 19:24, Igor Sobrado wrote: Hi viq! Sorry, I have read your message right now (...I am not subscribed to this mailing list, I was looking at MARC as it seems the most up to date archive, and found your answer.) Thanks a lot for the excellent reference you provided in your email. Indeed, it is a BSD disklabel related problem not a ffs's one. And it seems a serious one! I was about to just mention it, but then thought I'll fish out the link, so there you are ;) Better thinking on using each drive on a single operating system from now... Again, thanks a lot for your feedback. Now I see that there are some issues, not related with ffs itself, that can make information in real risk if I continue sharing these filesystems between both OSes. Ok, I think that it is all clear now. I must decide what OS will have access to each drive. Or reformat the drives to be shared with a different file system. Common solution to that is FAT32, but also pretty much everything (including windows! http://www.fs-driver.org/ ) can read ext2/3 disks - though I had some problems with fsck of an ext2 disk after it was mounted (or formatted) with linux. So, that's some other solution too ;) Though, no, I have NO idea how that is to the endianness of a machine. Thanks! Igor. -- viq
Re: sharing ffs filesystems between NetBSD and OpenBSD
In message [EMAIL PROTECTED], viq writes: On Tuesday 05 September 2006 19:24, Igor Sobrado wrote: Thanks a lot for the excellent reference you provided in your email. Indeed, it is a BSD disklabel related problem not a ffs's one. And it seems a serious one! I was about to just mention it, but then thought I'll fish out the link, so there you are ;) Thanks again for that link. An excellent reference, indeed! Ok, I think that it is all clear now. I must decide what OS will have access to each drive. Or reformat the drives to be shared with a different file system. Common solution to that is FAT32, but also pretty much everything (including windows! http://www.fs-driver.org/ ) can read ext2/3 disks - though I had some problems with fsck of an ext2 disk after it was mounted (or formatted) with linux. So, that's some other solution too ;) Though, no, I have NO idea how that is to the endianness of a machine. I prefer staying away of FAT32... there are a lot of nice features on Unix filesystems (e.g., soft and hard links) I certainly want to use. Don't trust me a lot, but I believe that ext2/3 do not depend on the endianness of the machine. Perhaps it is me, but I prefer avoiding ext2/3 filesystems too. I had some serious challenges recovering data from ext filesystems after power outages in the past. These filesystems do not seem as robust as ffs with softdep. Have a nice day! Igor.
IKE Phase-II fails - GETSPI: Operation not supported
I'm trying implement a IPSec/VPN tunnel and phase-II of the IKE negotiation is failing with the following errors seen from 'isakmpd - dKL -D A=90': 110340.763012 Default pf_key_v2_get_spi: GETSPI: Operation not supported 110340.763362 Default initiator_send_HASH_SA_NONCE: doi-get_spi failed 110340.763933 Default exchange_run: doi-initiator (0x86aa2380) failed This occurs after Phase-II proposals have been accepted. The other peer is functioning fine, I have other tunnels to it from Cisco PIXs and FreeBSD (raccon) boxes. Should this be reported as a bug? I'm running: 4.0-current (GENERIC #1103) - x86 Thanks.
Re: NXE bit on amd64 hardware and i386 kernel
On Tue, Sep 05, 2006 at 07:39:21PM +0200, Piotrek Kapczuk wrote: Hello When I boot 64 bit kernel on amd64 hardware I got NXE bit recognized. When I boot 32 bit kernel on amd64 it doesn't appear. I wonder if it's normal. If it's simply not supported/not done yet are there any plans to support this ? i386 cannot support nxe right now. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: sharing ffs filesystems between NetBSD and OpenBSD
On Tue, Sep 05, 2006 at 07:24:55PM +0200, Igor Sobrado wrote: Indeed, it is a BSD disklabel related problem not a ffs's one. It *is* a FFS problem. The superblocks are different. -p.
IKE Phase-II fails - GETSPI: Operation not supported
***Please ignore previous post. Forgive me for not googling first. Answer: # sysctl net.inet.esp.enable=1 [previous post] I'm trying implement a IPSec/VPN tunnel and phase-II of the IKE negotiation is failing with the following errors seen from 'isakmpd - dKL -D A=90': 110340.763012 Default pf_key_v2_get_spi: GETSPI: Operation not supported 110340.763362 Default initiator_send_HASH_SA_NONCE: doi-get_spi failed 110340.763933 Default exchange_run: doi-initiator (0x86aa2380) failed This occurs after Phase-II proposals have been accepted. The other peer is functioning fine, I have other tunnels to it from Cisco PIXs and FreeBSD (raccon) boxes. Should this be reported as a bug? I'm running: 4.0-current (GENERIC #1103) - x86 Thanks.
ambiguities around burning CD
I am trying to write a CD and I have atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SAMSUNG, CDRW/DVD SN-324S, U303 SCSI0 5/cdrom removable man cdrecord says: Some operating systems or SCSI transport implementations may require to specify a filename in addition. In this case the correct syntax for the device is: dev= devicename:scsibus,target,lun[...] May OpenBSD require to specify a filename in addition? If OpenBSD requires a filename in addition, does cdrecord have any further requirements on the filename apart that it is somehow associated with the writer in question? As dmesg suggests, I have a filename /dev/cd0a and /dev/cd0c. However, cdrecord dev=help suggests another filename: Transport name: SCIOCCOMMAND Transport descr.: SCSI for devices known by *BSD Transp. layer ind.: Target specifier: device or bus,target,lun Target example: /dev/rcd0a:@ or 1,2,0 SCSI Bus scanning: not supported Open via UNIX device: supported In this case it's filename /dev/rcd0a, which I have on my system, too. So the possible values for dev= according to this documentation are so far dev=0,0,0 dev=/dev/cd0a:0,0,0 dev=/dev/cd0c:0,0,0 dev=/dev/rcd0a:0,0,0 $ cdrecord dev=0,0,0 disk1.iso cdrecord: No write mode specified. cdrecord: Asuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. cdrecord: Continuing in 5 seconds... Cdrecord-Clone 2.01 (i386-unknown-openbsd3.9) Copyright (C) 1995-2004 Jvrg Schilling scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. $ cdrecord dev=/dev/cd0a:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/cd0a'. Cannot open SCSI driver. [...] $ cdrecord dev=/dev/cd0c:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/cd0c'. Cannot open SCSI driver. [...] $ cdrecord dev=/dev/rcd0a:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/rcd0a'. Cannot open SCSI driver. [...] Seems like there exists at least one operation which is not supported by these devices. But is it the write operation? Or something else? Does this mean OpenBSD doesn't support writing on my unit? Or does it mean the cryptic identifier I passed to dev= is just not cryptic enough? CL OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1.50GHz (GenuineIntel 686-class) 1.50 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2 cpu0: Enhanced SpeedStep 1500 MHz (1340 mV) (not in table) real mem = 535052288 (522512K) avail mem = 481202176 (469924K) using 4278 buffers containing 26857472 bytes (26228K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 01/28/05, BIOS32 rev. 0 @ 0xffe90 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc590/176 (9 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371 ISA and IDE rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xd800! 0xcd800/0x800 0xce000/0x800 0xce800/0x800 0xcf000/0x800 0xcf800/0x800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82852GM Hub-PCI rev 0x02 Intel 82852GM Memory rev 0x02 at pci0 dev 0 function 1 not configured Intel 82852GM Configuration rev 0x02 at pci0 dev 0 function 3 not configured vga1 at pci0 dev 2 function 0 Intel 82852GM AGP rev 0x02: aperture at 0xf000, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel 82852GM AGP rev 0x02 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 29 function 0 Intel 82801DB 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 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: 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 82801DB USB rev 0x01: 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 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 11 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered ppb0 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x81 pci1 at ppb0 bus 1 cbb0 at pci1 dev 1 function 0 Texas Instruments PCI4510
Re: ambiguities around burning CD
On Tue, 5 Sep 2006, Karel Kulhavy wrote: I am trying to write a CD and I have atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SAMSUNG, CDRW/DVD SN-324S, U303 SCSI0 5/cdrom removable man cdrecord says: Some operating systems or SCSI transport implementations may require to specify a filename in addition. In this case the correct syntax for the device is: dev= devicename:scsibus,target,lun[...] May OpenBSD require to specify a filename in addition? http://www.openbsd.org/faq/faq13.html#burnCD If OpenBSD requires a filename in addition, does cdrecord have any further requirements on the filename apart that it is somehow associated with the writer in question? As dmesg suggests, I have a filename /dev/cd0a and /dev/cd0c. However, cdrecord dev=help suggests another filename: Transport name: SCIOCCOMMAND Transport descr.: SCSI for devices known by *BSD Transp. layer ind.: Target specifier: device or bus,target,lun Target example: /dev/rcd0a:@ or 1,2,0 SCSI Bus scanning: not supported Open via UNIX device: supported In this case it's filename /dev/rcd0a, which I have on my system, too. So the possible values for dev= according to this documentation are so far dev=0,0,0 dev=/dev/cd0a:0,0,0 dev=/dev/cd0c:0,0,0 dev=/dev/rcd0a:0,0,0 $ cdrecord dev=0,0,0 disk1.iso cdrecord: No write mode specified. cdrecord: Asuming -tao mode. cdrecord: Future versions of cdrecord may have different drive dependent defaults. cdrecord: Continuing in 5 seconds... Cdrecord-Clone 2.01 (i386-unknown-openbsd3.9) Copyright (C) 1995-2004 Jvrg Schilling scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. $ cdrecord dev=/dev/cd0a:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/cd0a'. Cannot open SCSI driver. [...] $ cdrecord dev=/dev/cd0c:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/cd0c'. Cannot open SCSI driver. [...] $ cdrecord dev=/dev/rcd0a:0,0,0 disk1.iso [...] cdrecord: Operation not supported by device. Cannot open '/dev/rcd0a'. Cannot open SCSI driver. [...] Seems like there exists at least one operation which is not supported by these devices. But is it the write operation? Or something else? Does this mean OpenBSD doesn't support writing on my unit? Or does it mean the cryptic identifier I passed to dev= is just not cryptic enough? CL OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1.50GHz (GenuineIntel 686-class) 1.50 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2 cpu0: Enhanced SpeedStep 1500 MHz (1340 mV) (not in table) real mem = 535052288 (522512K) avail mem = 481202176 (469924K) using 4278 buffers containing 26857472 bytes (26228K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 01/28/05, BIOS32 rev. 0 @ 0xffe90 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc590/176 (9 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371 ISA and IDE rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xd800! 0xcd800/0x800 0xce000/0x800 0xce800/0x800 0xcf000/0x800 0xcf800/0x800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82852GM Hub-PCI rev 0x02 Intel 82852GM Memory rev 0x02 at pci0 dev 0 function 1 not configured Intel 82852GM Configuration rev 0x02 at pci0 dev 0 function 3 not configured vga1 at pci0 dev 2 function 0 Intel 82852GM AGP rev 0x02: aperture at 0xf000, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel 82852GM AGP rev 0x02 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 29 function 0 Intel 82801DB 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 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: 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 82801DB USB rev 0x01: 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 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 11 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: Intel EHCI root
UTC vs UCT timezone
The FAQ seems to reference UTC (at least in section 8), which would translate at Universal Time, Coordinated, from what I understand. Are these two the same?
Some questions related to 4.0
Hello everybody, I`ve some questions related to the upcomming 4.0 Release. I`ve read that SpeedStep was deactivated for SMP. Could somebody explain me why this was done? I`ve read some AMD announcements and they`ll produce (this year maybe even) a 4 Core CPU. And as advantage they`ve pointed out that Cores could get deactivated or run with different Speeds to save Energy. This would be in fact an advantage and will appear even for home-users some day I think. Something else: cdio(1) can now perform track-at-once burning and rewritable blanking. Is it planed to create a own CD Burn application on OpenBSD? I`ve read a lot peoples do have problems with cdrtools (lets name it Debian and others) and even forked cdrtools. But except of this cdio provides a lot functionality already and now burning support was added too that`s why I ask. OpenBSD does not support a large amount of memory, as far as I know. Link: http://archives.neohapsis.com/archives/openbsd/2004-11/2964.html I didn`t found somethign wich mentions this on the plus.html So: Is that fixed now? I`ve 2GB RAM and would like to buy some more (AMD64). Last but not least: Has Henning something in the backhand? He owns openhttpd.org for some months now.. :) Kind regards, Sebastian
Re: Some questions related to 4.0
On 9/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello everybody, I`ve some questions related to the upcomming 4.0 Release. I`ve read that SpeedStep was deactivated for SMP. Could somebody explain me why this was done? http://marc.theaimsgroup.com/?l=openbsd-miscm=115635621902871 According to that message, setperf isn't currently SMP safe.
Re: The future of NetBSD
I don't think that binary only drivers are well enough. Surely better than nothing but ... No fucking way. No support is FAR FAR better than a blob. Yes, really! Don't forget that an open source team sometimes makes api changes that might break a binary only driver. And companies sometimes are slow in fixing. A.K.A. Never. And when they try it usually doesn't work right. Worst of all *you* have no clue how they kludged a so called fix together. Vendor code is usually pretty darn bad and I wonder why people never revolt against that. Or the vendor did some mistakes in his own driver. First the paying customers are served. All the other folks (open source ..) surely will come last. Open source users paid for the hardware didn't they? Or because they use an alternative OS now they stole the hardware? This argument is retarded. For some smaller corps supporting open source developers is simply a burden that costs time and so money. Docs are part of the development process. If they are not than you don't want that hardware. I know this from a medium sized german company producing nice audio recording cards. It was impossible to get a card and documentation from them for a FreeBSD developers. And after weeks and months of asking via e-mail they decided finally to tell the truth that they don't want to support open source developers anymore, it makes too much work. They are unable to spend so much time answering open source developers questions although they got documentation. This experience they made with Linux developers. I call horseshit on this one too. Vendors do not have to support shit if they free their docs. NOTHING because the OS developers will do it for FREE for them. This argument is a steaming pile of shit with peanuts in it. It is this attitude that is killing Linux and FreeBSD. They will allow anyone to shit and piss in their sandbox and say GREAT THANKS! You people need to get through your heads that blobs are killing your operating system that you pretend to care so much about. Allowing blobs is the equivalent of eating fast food; it is convenient now but 10 years from now your ass wont fit through the door. A man will fight harder for his interests than for his rights. -- Napoleon Bonaparte Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? - http://www.apsfilter.org/
Re: UTC vs UCT timezone
I had always had sych questions and had never had an answer. Good question Plumlee. On 9/5/06, Scott Plumlee [EMAIL PROTECTED] wrote: The FAQ seems to reference UTC (at least in section 8), which would translate at Universal Time, Coordinated, from what I understand. Are these two the same?
Re: ambiguities around burning CD
Hi Karel, On 06/09/2006, at 6:13 AM, Karel Kulhavy wrote: So the possible values for dev= according to this documentation are so far dev=0,0,0 dev=/dev/cd0a:0,0,0 dev=/dev/cd0c:0,0,0 dev=/dev/rcd0a:0,0,0 I use: cdrecord dev=/dev/rcd0c ^ ^ Which works fine for me. Shane
Re: UTC vs UCT timezone
Mark Zimmerman wrote: On Tue, Sep 05, 2006 at 04:27:42PM -0400, Scott Plumlee wrote: The FAQ seems to reference UTC (at least in section 8), which would translate at Universal Time, Coordinated, from what I understand. Are these two the same? Yes, UTC is Coordinated Universal Time. The acronym is a compromise between english and french. I appreciate all the answers, both on and off list. Wikipedia was the first place I looked, so I understand the UTC is the official US abbreviation of Universal Coordinated Time. But I still don't see a reason why, if UTC==UCT, there are two files when it would seem that a link would remove the need for two separate files. # pwd /usr/share/zoneinfo/Etc # ls -lai UCT 87585 -r--r--r-- 2 root bin 56 Mar 2 2006 UCT # ls -lai UTC 87589 -r--r--r-- 6 root bin 56 Mar 2 2006 UTC So one has 6 links, one has 2 links. My guess is that somewhere in the system, there are other files that need both of these, perhaps for historical reasons. That's what I'm trying to figure out, but I don't know if there is a simple method for finding the files that reference a particular inode. Anyway, back to the original questions, if UTC==UCT, what is the reason the a symbolic link from UCT to UTC would not work? Please pardon the stupidity if the answer is blatantly obvious. Clue stick received with a smile, at least the first hundred times.
matrox g450 - unabale to play a simple video? :(
Hello everybody, The Box I`m using for multimedia died so I tried to watch a simple Movie with mplayer. The video is a OGM-File and contains 2 audio streams and 2 Subtitles. The Video Codec is DivX/Xvid and the audio streams are compressed using MP3. When I try to play the movie with mplayer it starts first but then hangs some seconds later and I get audio only. I was suprised because I watched the same video some Versions ago (~3.6-3.7) with OpenBSD and had NO problems (but the Hardware was different). I`ve even recompiled the mplayer with enablexvid (why is it disabled by default?!) but that didn`t helped. OS: OpenBSD AMD64 3.9 STABLE Graficcard: Matrox G450 PCI (dmesg tells me it`s AGP but that Board simply has NO AGP Slot) CPUs: 2x 256 Opteron RAM: 4x512MB Board: Tyan 2882-D (Dualcore-Ready Version) OpenBSD 3.9-stable (GENERIC.MP) #0: Fri May 12 07:48:53 CEST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2147020800 (2096700K) avail mem = 1835290624 (1792276K) using 22937 buffers containing 214908928 bytes (209872K) of memory mainbus0 (root) ipmi0 at mainbus0bmc_io_wait_cold fails : *v=ff m=02 b=00 write_cmd kcs_sendmsg: 18 01 : unable to send get device id command mainbus0: Intel MP Specification (Version 1.1) (TYAN S2882 ) cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Opteron(tm) Processor 252, 2591.33 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,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: AMD Opteron(tm) Processor 252, 2590.91 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,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 mpbios: bus 0 is type PCI mpbios: bus 1 is type PCI mpbios: bus 2 is type PCI mpbios: bus 3 is type PCI mpbios: bus 4 is type PCI mpbios: bus 5 is type ISA ioapic0 at mainbus0 apid 2: pa 0x8373ae24, version 11, 24 pins ioapic1 at mainbus0 apid 3: pa 0x8373ad24, version 11, 4 pins ioapic2 at mainbus0 apid 4: pa 0x8373ac24, version 11, 4 pins pci0 at mainbus0 bus 0: configuration mode 1 ppb0 at pci0 dev 6 function 0 AMD 8111 PCI-PCI rev 0x07 pci1 at ppb0 bus 4 ohci0 at pci1 dev 0 function 0 AMD 8111 USB rev 0x0b: apic 2 int 19 (irq 10), version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: AMD OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1 at pci1 dev 0 function 1 AMD 8111 USB rev 0x0b: apic 2 int 19 (irq 10), version 1.0, legacy support usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: AMD OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered emu0 at pci1 dev 4 function 0 Creative Labs SoundBlaster Live rev 0x08: apic 2 int 16 (irq 9) ac97: codec id 0x43525914 (Cirrus Logic CS4297A rev 4) ac97: codec features headphone, 20 bit DAC, 18 bit ADC, Crystal Semi 3D audio0 at emu0 Creative Labs PCI Gameport Joystick rev 0x08 at pci1 dev 4 function 1 not configured pciide0 at pci1 dev 5 function 0 CMD Technology SiI3114 SATA rev 0x02: DMA pciide0: using apic 2 int 19 (irq 10) for native-PCI interrupt pciide0: port 0: device present, speed: 1.5Gb/s wd0 at pciide0 channel 0 drive 0: HDS722516VLSA80 wd0: 16-sector PIO, LBA48, 157066MB, 321672960 sectors wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 5 fxp0 at pci1 dev 8 function 0 Intel 8255x rev 0x10, i82551: apic 2 int 18 (irq 5), address inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4 pcib0 at pci0 dev 7 function 0 AMD AMD8111 LPC rev 0x05 pciide1 at pci0 dev 7 function 1 AMD 8111 IDE rev 0x03: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd1 at pciide1 channel 0 drive 0: WDC WD1200JB-75CRA0 wd1: 16-sector PIO, LBA, 114440MB, 234375000 sectors wd1(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 2 wd2 at pciide1 channel 1 drive 0: SAMSUNG SP1614N wd2: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd3 at pciide1 channel 1 drive 1: SAMSUNG SP1614N wd3: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd2(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 5 wd3(pciide1:1:1): using PIO mode 4, Ultra-DMA mode 5 amdiic0 at pci0 dev 7 function 2 AMD 8111 SMBus rev 0x02: SCI iic0 at amdiic0 amdpm0 at pci0 dev 7 function 3 AMD 8111 Power rev 0x05: rng active iic1 at amdpm0 lm1 at iic1 addr 0x28: W83627HF adt0 at iic1 addr 0x2e:
Re: matrox g450 - unabale to play a simple video? :(
Some corrections: The old Version was 3.8 (not 2.8, typo..) And the screen (at X) gets fucked even by pressing page-up/down. :-/ But if I would be able to play a little ~300MB file I would be already happy. :) Kind regards, Sebastian
LANPARTY UT NF590 SLI-M2R/G Compatibility?
Hi. I saved money for a new pc and i would like buy this motherboard, but i don't know about compatibily. I read www.openbsd.org/amd64.html and i have doubts with the chipset, audio and lan. Audio: - Realtek ALC885 8-channel High Definition Audio CODEC - 6 audio jacks Lan: - NVIDIA(r) MCP55PXE integrated with Gigabit MAC (Media Access Control) technology - Two Vitesse VSC8601 Gigabit Phy chips - Fully compliant to IEEE 802.3 (10BASE-T),802.3u (100BASE-TX) and 802.3ab (1000BASE-T) standards If the motherboard it is not good, which do you recommend me? (similar) I would buy the motherboard in the next 2 weeks. i need orientation please :S Alejandro. pd. My english is bad, sorry. i'm from Chile.
Re: ssh problem
Well I wish it were this easy, or perhaps I am still missing something. I added AllowUsers username in the sshd_config file and changed the drive to read/write and here's the results: [EMAIL PROTECTED]:~# mount -o rw /dev/wd0a / [EMAIL PROTECTED]:~# ssh -p 222 [EMAIL PROTECTED] [EMAIL PROTECTED]'s password: Permission denied, please try again. [EMAIL PROTECTED]'s password: Permission denied, please try again. [EMAIL PROTECTED]'s password: Permission denied (publickey,password,keyboard-interactive). Sep 5 18:31:23 shakti-taos sshd[10335]: Failed none for invalid user lj from ::1 port 15320 ssh2 Sep 5 18:31:26 shakti-taos sshd[10335]: Failed password for invalid user lj from ::1 port 15320 ssh2 Sep 5 18:31:31 shakti-taos last message repeated 2 times Of course I would love to disallow Root logins but will await the resolution of allowing regular users to connect via ssh first. Any suggestions would be greatly appreciated. Thordur I. Bjornsson wrote: Leonard Jacobs [EMAIL PROTECTED] wrote on Mon 4.Sep'06 at 22:22:30 -0400 I've configured a Soekris running OpenBSD 3.9 pf as a firewall, with a read only CF. I am using the default sshd_config file except to run sshd on port 222. /dev mounted read only ? If so, then thats your proplem. Load it as an mfs on boot. (image + vnd ? maybe or sth) My problem is that I cannot connect remotely to this box via ssh except as root. When a legit user who has an account on that box attempts connection, I get Failed password for invalid user lj from 192.168.1.13 port 10962 ssh2. Is there anything obvious that you can suggest that might be causing this problem? I did try changing the file system to read/write, but it did not resolve the problem. Thanks.
Blobs
On 9/5/06 4:18 PM, Marco Peereboom wrote: Allowing blobs is the equivalent of eating fast food; it is convenient now but 10 years from now your ass wont fit through the door. I don't know why but I feel someone has won here, no idea which contest it was or what but this quote will help a wider audience understand the blob case. xxx chefren
Re: The future of NetBSD
On Tue, 5 Sep 2006 08:55:42 +0200, Andreas Klemm [EMAIL PROTECTED] said: On Thu, Aug 31, 2006 at 06:50:00PM -0300, Marc G. Fournier wrote: On Thu, 31 Aug 2006, Constantine A. Murenin wrote: On 31/08/06, Marc G. Fournier [EMAIL PROTECTED] wrote: Just a stupid comment, but ... Linux is one kernel, multiple distributions ... BSD is, what, 4 kernels now? If we worked more together instead of as seperate camps, it might make things a bit easier, no? Isn't there still fewer differences between *BSD operating systems than between different GNU/Linux distributions and kernel releases? :) Put together a *BSD core ... representative from each camp and try and steer the *kernel* itself towards a more common BSD ... I doubt that'll be productive -- NetBSD, FreeBSD and OpenBSD have all different goals... Even at the kernel level? Look at device drivers and vendors as one example ... companies like adaptec have to write *one* device driver, for, what, 50+ distributions of linux ... for us, they need to write one for FreeBSD, one for NetBSD, one for OpenBSD, and *now* one for DragonflyBSD ... if we had *at least* a common API for that sort of stuff, it might be asier to get support at the vendor level, no? Are you really sure ? I see it more this way: For Linux on kernel (or device driver) level they only have to support 2 main trains: 2.4.x and 2.6.x. The 50 distributions are only a burden if it comes to the point what different shared library / Java / TCL / etc ... versions are packaged with the OS. A friend of mine doing Java development had severe issues with all that different Linux versions. But a simple kernel driver only has to honour different CPU types and the 2.4 and 2.6 tree and maybe now a development tree but am not sure on the latter ... Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? - http://www.apsfilter.org/ For what it's worth: Linux kernel interfaces change every day - I mean every minor release. Linux makes it very hard to support drivers for it. Just look inside a module DEVELOPED OUTSIDE THE KERNEL TREE, you will see an incredible mess of #if KERNEL_VERSION... Virtualy everyone that started some module gave up supporting it. If it is not picked up by the kernel or by some Debian developer, the module dissapears.The internet is littered with orphaned Linux modules. Best Regards -- Stefan Bojilov [EMAIL PROTECTED] -- http://www.fastmail.fm - A no graphics, no pop-ups email service
pf.conf's example of tables using ports
maybe i'm plain stupid or i have a weird install.
All you have the following line at pf.conf ,that comes with OpenBSd 3.9,?
#table httport { 80, 443 }
I have readed the pf.conf 's man page also the FAQ at www.openbsd.org
and it says
A table is used to hold a group of IPv4 and/or IPv6 addresses
PF don't want to load the pf.conf with that line uncommented.
Is that a problem on my version or is a bug ;o) in base install?
Confused about patching X in OBSD 3.9
For OBSD 3.9 there is a patch for X, 002_xorg.patch The patch says it should be applied to the X source located at: cd /usr/src/XF4 But everything I've ever read says the X source, XF4.tar.gz should be unpacked and stored in: /usr/ Example of this: http://www.openbsd.org/anoncvs.html#starting Which is it? And can't we get on the same page here? -Steven -- __ Now you can search for products and services http://search.mail.com
Re: Confused about patching X in OBSD 3.9
On Wed, Sep 06, 2006 at 11:07:22AM +0800, First Last wrote: For OBSD 3.9 there is a patch for X, 002_xorg.patch The patch says it should be applied to the X source located at: cd /usr/src/XF4 But everything I've ever read says the X source, XF4.tar.gz should be unpacked and stored in: /usr/ Example of this: http://www.openbsd.org/anoncvs.html#starting Which is it? And can't we get on the same page here? Some put it one place, and the rest in the other, and SOME people put it in /usr and symlink /usr/src/XF4 to /usr/XF4. It would be nice if there were One True Way, yet it's not much of a stumbling block... -- Darrin Chandler| Phoenix BSD Users Group [EMAIL PROTECTED] | http://bsd.phoenix.az.us/ http://www.stilyagin.com/ |
sk driver
I thought the issue with the watchdog timing out was fixed. I was seeding a torrent file this morning, so when I came home and turned it off, I received these errors: sk0: watchdog timeout sk0: cannot stop transfer of Tx descriptors I am running a kernel compiled as of last Saturday. Here's my dmesg: OpenBSD 4.0 (GENERIC) #0: Sat Sep 2 14:06:26 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1073278976 (1048124K) avail mem = 907919360 (886640K) using 22937 buffers containing 107536384 bytes (105016K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.2 @ 0xf (39 entries) cpu0 at mainbus0: (uniprocessor) cpu0: AMD Athlon(tm) 64 Processor 3000+, 1808.55 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 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 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 adt0 at iic0 addr 0x2e: sch5017 rev 0x89 iic1 at nviic0 adt1 at iic1 addr 0x2e: sch5017 rev 0x89 ohci0 at pci0 dev 2 function 0 NVIDIA nForce4 USB rev 0xa2: irq 5, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0 at pci0 dev 2 function 1 NVIDIA nForce4 USB rev 0xa3: irq 10 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 uhub1: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered auich0 at pci0 dev 4 function 0 NVIDIA nForce4 AC97 rev 0xa2: irq 5, nForce4 AC97 ac97: codec id 0x414c4760 (Avance Logic ALC655 rev 0) audio0 at auich0 pciide0 at pci0 dev 6 function 0 NVIDIA nForce4 IDE rev 0xa2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, DVDRAM GSA-4163B, A103 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 pciide1 at pci0 dev 7 function 0 NVIDIA nForce4 SATA rev 0xa3: DMA pciide1: using irq 10 for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: WDC WD360GD-00FLA2 wd0: 16-sector PIO, LBA48, 35304MB, 72303840 sectors wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1 at pciide1 channel 1 drive 0: WDC WD3200KS-00PFB0 wd1: 16-sector PIO, LBA48, 305245MB, 625142448 sectors wd1(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 5 pciide2 at pci0 dev 8 function 0 NVIDIA nForce4 SATA rev 0xa3: DMA pciide2: using irq 11 for native-PCI interrupt ppb0 at pci0 dev 9 function 0 NVIDIA nForce4 PCI-PCI rev 0xa2 pci1 at ppb0 bus 1 ATI Rage XL rev 0x27 at pci1 dev 5 function 0 not configured VIA VT6306 FireWire rev 0x80 at pci1 dev 6 function 0 not configured skc0 at pci1 dev 10 function 0 D-Link Systems DGE-530T A1 rev 0x11, Marvell Yukon Lite (0x9): irq 5 sk0 at skc0 port A, address 00:15:e9:2e:28:e6 eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 5 nfe0 at pci0 dev 10 function 0 NVIDIA CK804 LAN rev 0xa3: irq 11, address 00:e0:81:56:8f:67 eephy1 at nfe0 phy 1: Marvell 88E Gigabit PHY, rev. 1 ppb1 at pci0 dev 11 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci2 at ppb1 bus 2 ppb2 at pci0 dev 12 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci3 at ppb2 bus 3 ppb3 at pci0 dev 13 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci4 at ppb3 bus 4 bge0 at pci4 dev 0 function 0 Broadcom BCM5721 rev 0x11, BCM5750 B1 (0x4101): irq 11, address 00:e0:81:56:8f:66 brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb4 at pci0 dev 14 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci5 at ppb4 bus 5 vga1 at pci5 dev 0 function 0 NVIDIA GeForce 6600 GT rev 0xa2 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pchb0 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb1 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb2 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb3 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 umass0 at
Re: pf.conf's example of tables using ports
On 06/09/06, Nick Holland [EMAIL PROTECTED] wrote:
Pablo Halamaj wrote:
maybe i'm plain stupid or i have a weird install.
All you have the following line at pf.conf ,that comes with OpenBSd 3.9,?
#table httport { 80, 443 }
no, that's something you (or someone) put in your machine.
Thankz to all, i will track down why that line was at my machine.
i just want to know if the problem was mine.
I have readed the pf.conf 's man page also the FAQ at www.openbsd.org
and it says
A table is used to hold a group of IPv4 and/or IPv6 addresses
PF don't want to load the pf.conf with that line uncommented.
good.
Is that a problem on my version or is a bug ;o) in base install?
No and no.
You are trying to use it as a table of ports. That's not what it is
for. It's for addresses, like you quoted. Those aren't valid IP
addresses.
For two items, use a macro:
httpport={ 80, 443 }
Nick.
Pablo
Re: sk driver
On 9/5/06, Brian [EMAIL PROTECTED] wrote: I thought the issue with the watchdog timing out was fixed. I was seeding a torrent file this morning, so when I came home and turned it off, I received these errors: sk0: watchdog timeout sk0: cannot stop transfer of Tx descriptors I am running a kernel compiled as of last Saturday. Here's my dmesg: OpenBSD 4.0 (GENERIC) #0: Sat Sep 2 14:06:26 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC snip skc0 at pci1 dev 10 function 0 D-Link Systems DGE-530T A1 rev 0x11, Marvell Yukon Lite (0x9): irq 5 sk0 at skc0 port A, address 00:15:e9:2e:28:e6 snip I own this exact card as well and I'm still having this problem with -current snapshots too. -Sam
