Re: Linux emulation fedora/base or redhat/base
Pieter Verberne wrote: http://www.openbsd.org/faq/faq9.html#Interact says I should use fedora_base for Linux emulation but compat_linux(8) says I should use redhat_base. What is your advice? Use fedora_base, it contains much newer linux components than the redhat_base package.
Re: how to clear dmesg outpout
smonek wrote: How to clear kern msg buffer (dmesg output ) without restart system Turn computer off. Breathe out calmly for a few minutes. Turn computer on.
Re: new X sets problems
Paul Irofti wrote: I'm sorry I don't understand what you're pointing at, the mainbus? No, I'm talking about all the screwed up characters in your dmesg: acpi @t mainbus0 not configured ^ should be an a c0u0 at mainbus0 ^ should be a p pchb0 at pci0 dev 0 fufction 0 Intel 82805G/GL rev 0x01 ^ should be an n These are fallen over bits, pointing to corruption.
Re: OpenBSD's bind: CVE-2007-0493 and CVE-2007-0494
Stephan A. Rickauer wrote: CVE-2007-0493: If recursion is enabled, a remote attacker can dereference a freed fetch context causing the daemon to abort / crash. CVE-2007-0494: By sending specific DNS query responses with multiple RRSETS attackers could cause BIND to exit abnormally. Is this of relevance also for OpenBSD's bind? I guess not, but maybe some insider could shed some photons on it. This was fixed on 2007-01-25: http://marc.theaimsgroup.com/?l=openbsd-cvsm=116970956517411w=2
Re: ACPI tests on a Jetway J7F2 board
Mark Zimmerman wrote: I almost didn't submit this because there were no outright failures, but then I noticed that with acpi enabled, the hw.setperf sysctl is missing. Without acpi, it is present and works properly. This is because the traditional EST mechanism is currently disabled when ACPI is running, because ACPI provides the same functionality through acpicpu(4). However, you need to enable acpicpu in your kernel configuration to use it. It's currently still in development, so watch out for bumps in the road. ;) Please report any weird failures or strange error messages if you enable it.
Re: ACPI tests on a Jetway J7F2 board
Mark Zimmerman wrote: You will notice the sucky DMA of the Jetway board in all of them. ... wd0a: aborted command, interface CRC error reading fsbn 671456 of 671456-0 (wd0 bn 5571281; cn 5527 tn 1 sn 2), retrying wd0: transfer error, downgrading to Ultra-DMA mode 4 wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 4 wd0a: aborted command, interface CRC error reading fsbn 671456 of 671456-0 (wd0 bn 5571281; cn 5527 tn 1 sn 2), retrying wd0: soft error (corrected) wd0: transfer error, downgrading to Ultra-DMA mode 3 wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 3 wd0a: aborted command, interface CRC error reading fsbn 671168 of 671168-0 (wd0 bn 5570993; cn 5526 tn 12 sn 29), retrying wd0: soft error (corrected) These sorts of errors are usually caused by bad cabling, connectors, or dying drives. Try replacing the cables or drives, to see if it helps.
Re: Screen resolution and ACPI
Passeur wrote: Also I would like the PC to actualy shut down when I do shutdown -h now instead of having to press the power button. This option is supported but disabled by default as far I have read, but how to enable it ? Use the -p option, as it says in shutdown(8). Or read and edit /etc/rc.shutdown.
Re: disable SpeedStep ?
Rich Dunkle wrote: How can I disable the SpeedStep feature in OpenBSD 4.0 ? You can't, yet. The machine hangs during cpu0 checks: ... cpu0: unknown Enhanced SpeedStep CPU, msr 0x0b280b2886000b28 cpu0: using only highest and lowest power states cpu0: Enhanced SpeedStep 2933 MHz (1340 mV)kernel: integer divide fault Your CPU reports strange information in its msr; it looks like the highest and lowest speed are exactly the same, which, as usual, shouldn't really happen. :) Please update to sys/arch/i386/i386/est.c rev 1.26 (may take some time to arrive on your nearest mirror), which contains a quick fix.
Re: ASUS P5L-MX
Frank Bax wrote: ... 2) is this a problem: cpu0: unknown Core FSB_FREQ value 0 (0x41c8) ... cpu0: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz (GenuineIntel 686-class) 1.87 GHz This is one of the newer Intel Core 2 CPU's, with 266 MHz FSB. There is support for those in -current, but it didn't make it into 4.0, due to insufficient testing. You can try the following patch, which should apply to 4.0 release and stable. Note that you won't notice much, except for the message disappearing. The bus clock detection is currently only important for SpeedStep, and that doesn't work yet on MP kernels. Index: sys/arch/i386/i386/machdep.c === RCS file: /cvs/src/sys/arch/i386/i386/machdep.c,v retrieving revision 1.364 diff -u -d -p -r1.364 machdep.c --- sys/arch/i386/i386/machdep.c20 Aug 2006 01:42:51 - 1.364 +++ sys/arch/i386/i386/machdep.c20 Dec 2006 09:58:39 - @@ -2090,6 +2090,9 @@ p3_get_bus_clock(struct cpu_info *ci) case 3: bus_clock = 1; break; + case 0: + bus_clock = 2; + break; case 4: bus_clock = 3; break;
Re: LineWrap Failure in Text-Terminal
Sebastian Neuper wrote:
Hi. With OpenBSD 4.0, I encounter a wrong line wrapping
in the text-terminals.
...
So I looked through all the changes and noticed the new jump
scroll feature for vt220 introduced in OpenBSD 4.0 and corrected
in OpenBSD Current. My computer is a 200MMX with a 2,5GB
Harddrive and compiling the complete source will be heavy or
impossible. So I cannot check, if this is the problem or if it
is already solved, and didn't send a bug-report.
Yes, this is precisely what was solved. Just for reference, the
following diff should fix these problems also on 4.0 release or stable.
You could consider building a 4.0 release or stable kernel with only
this patch on a fast machine, and then transfer it to your slow machine.
--- sys/dev/wscons/wsemul_vt100.c 17 Aug 2006 06:27:04 - 1.13
+++ sys/dev/wscons/wsemul_vt100.c 19 Oct 2006 17:35:09 - 1.15
@@ -1015,7 +1015,9 @@ wsemul_vt100_output(cookie, data, count,
}
break;
default:
- if (++pos = NCOLS) {
+ if ((curchar 0x7f) 0x20)
+ break;
+ if (pos++ = NCOLS) {
pos = 0;
curchar = ASCII_LF;
}
Re: 4.0 frozen
Jacob Yocom-Piatt wrote: wd0d: device timeout reading fsbn 234162112 of 234162112-234162239 (wd0 bn 235334857; cn 14648 tn 233 sn 58), retrying wd0: soft error (corrected) Maybe dying disks? i must second this suggestion. almost every time i've seen these IDE timeout messages, it means that the disk(s) are damaged, close to dead or totally dead. Note that these errors can also be caused by any other part of the IDE subsystem, e.g. the controller, the cables, etc. Or even by bad RAM... For sanity's sake, do a full hardware diagnostic of the machine.
Re: vmstat -m : negative Requests value for UVM amap?
Maxim Bourmistrov wrote: vmstat -m reports negative value for UVM amap Requests. ... === UVM amap 87670 8352K 28908K157284K-20682868430 0 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768 That is just a 32 bit signed integer wrapping around, probably because your machine has been up for a long time. Nothing to worry about, this counter is not needed for your tax office...
Re: 4.0 frozen
Stephen Schaff wrote: Yesterday it inexplicably went dark. ... wd0(pciide1:0:0): timeout type: ata c_bcount: 65536 c_skip: 0 pciide1:0:0: bus-master DMA error: missing interrupt, status=0x21 wd0d: device timeout reading fsbn 234162112 of 234162112-234162239 (wd0 bn 235334857; cn 14648 tn 233 sn 58), retrying wd0: soft error (corrected) wd0(pciide1:0:0): timeout type: ata c_bcount: 65536 c_skip: 0 pciide1:0:0: bus-master DMA error: missing interrupt, status=0x21 ... more of those IDE errors ... Maybe dying disks?
Re: help! 855 chipset resolution
Vim Visual wrote: Logging as su and without X running I get 1280pgm 30 1280 768 Unable to open /dev/mem: Operation not permitted You must run this before securelevel gets raised. 3d 1920 1440 is one mode I don't want to use; you have to overwrite one of them like that I guessed that one because I have a logbook from my experimentations with the same laptop and Linux + 915resolution. In linux it was working like that To set this stuff up interactively, it's easiest to start OpenBSD in single user mode (enter -s at the boot prompt), and do it from there. First use 915resolution -l to list the available modes from your BIOS, choose the one you'd like to overwrite, and you can immediately try out running 915resolution with the proper parameters. Once you got those, just put those in rc.securelevel.
Re: help! 855 chipset resolution
Vim Visual wrote: ... vga1 at pci0 dev 2 function 0 Intel 82852GM AGP rev 0x02: aperture at 0xd800, 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 ... NOT CONFIGURED! rgh! Don't panic. This is normal: it is the *second* head that is not configured. The first head is configured as vga1, and the AGP aperture is also detected properly. and of course 915resolution doesn't work!! This might be due to you using it incorrectly, since it works fine for quite a lot of people. :) In cases like this, always post the *exact* command line and options that you tried, and include *complete* logs of any error messages. 1280patch-845g-855gm-865g.c:307: warning: assignment makes pointer from integer without a cast Unfortunately, your attachment got stripped, since misc@ doesn't accept any attachments. Also, I would be surprised if Linux code compiled as-is on any other operating system. :) If the source code is not too large, you might want to post it inline, but preferably give the URL where you downloaded it from.
Re: help! 855 chipset resolution
Vim Visual wrote: I cannot afford to have a non-functional (I know this is an exaggerated statement) production laptop for longer than, say, a few hours. As a matter of fact I am reinstalling GNU/Linux right now because I HAVE to work this evening (the installation and set up takes ~20 min) You should always verify that everything works, before taking any machine into production. :) As others have already said, a separate partition for OpenBSD is a good way to get started. 1- Why should I give gcc the path to io.h? (and where is it, btw, a locate will be random in my case because I do not know what io.h is) In GNU/Linux I don't have to do it and seemingly the folks of FreeBSD/NetBSD neither. Does it depend on the gcc version? If you don't know what the problem is, you should not be the one trying to fix it. :) 2- Another BIG problem for me is that apm does not work. I NEED apm As far as can be seen from your previously posted dmesg, your laptop doesn't support apm at all, only acpi. Please complain to your laptop manufacturer about it. We see this all the time with newer machines, vendors don't bother to test anything but Windows these days. If all goes well, acpi support will probably make it into OpenBSD 4.1, and there are already some snapshots with partial acpi support on the ftp site. But please don't count on this to work perfectly, it's still in development. 1- I need wlan connection (guess it'll work just as it's working on this one, same chipset) It's an Intel 2200BG, which works, if you accept Intel's weird licensing policies for their firmware. 2- I need the full screen resolution As I asked you before: post the exact command lines you were using with 915resolution, and the exact error messages which prevented it from working. We would rather have a chance to fix the 915resolution port, if it somehow didn't work on your machine, than try to get some weird Linux-only program running. 3- I need apm working Try looking for a BIOS update from your vendor, complain to your vendor about dropping support for established standards, or try a snapshot with acpi support enabled (but DON'T expect everything to work in this case!).
Re: help! 855 chipset resolution
Otto Moerbeek wrote: I'm might be compleetly wrong, but isn't the 915resolution-0.5.2.tgz package what Vim needs? That's already ported, precompiled and tested on a variety of harware using that chipset. I've asked him several times now to post the exact problems he is having using the port. I'm not going to do so again.
Re: i810-series video BIOS + 855GM resolution
Vim Visual wrote: I plan to install o'bsd 4.0 on a fujitsu siemens laptop which has a screen of 1280x768 pixels. With GNU/Linux this was always a pain and I had to manually patch the VBIOS because otherwise only 1024x768 are recognised. I would like to ask around whether somebody has such a chipset and what's the workaround in o'bsd. Use the x11/915resolution port.
Re: i810-series video BIOS + 855GM resolution
Sam Fourman Jr. wrote: Can you still use 11/915resolution on a device that says Driver not configured? ... vga1 at pci0 dev 2 function 0 Intel 82945GM Video rev 0x03: aperture at 0xd020, 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 You probably mean that pci0 dev 2 device? As far as I know, that's the second head, and there's no way at the moment to get at its video BIOS. Maybe newer versions of X.org have a workaround for this, but you'll have to wait a while before these can be tried out...
Re: Via C7 fully supported?
Greg Mortensen wrote: Have a look at the LE565 with (IIRC) 4*1Gb ... It does (4 x Realtek 8169). The dmesg that I posted earlier is from a LE-565. According to the Commell specs, those are actually 4x Realtek 8110S.
Re: internal modem
ivorob wrote: Within my notebook I have internal modem. How Can I force to work my modem? Is it possible? Almost always, these notebook modems are soft modems. This means that the modem functionality (connection, protocols, error-correction, etc) is implemented completely in a closed-source, Windows-only driver. The chance of getting these modems working on any non-Windows platform is almost zero. Please complain to your vendor(s). :)
Re: Libretto L1 xorg.conf
Bryan Vyhmeister wrote: ... (--) SAVAGE(0): 1280x600 TFT LCD panel detected and active (--) SAVAGE(0): - Limiting video mode to 1280x600 (--) SAVAGE(0): Found 13 modes at this depth: [10f] 320 x 200, 70Hz [112] 640 x 480, 60Hz, 72Hz, 75Hz, 85Hz, 100Hz [115] 800 x 600, 60Hz, 72Hz, 75Hz, 85Hz, 100Hz [118] 1024 x 768, 60Hz, 70Hz, 75Hz, 85Hz, 43Hz, 100Hz [11b] 1280 x 1024, 60Hz, 75Hz, 85Hz, 43Hz [11e] 640 x 400, 70Hz [124] 1600 x 1200, 48Hz, 60Hz, 75Hz, 85Hz [134] 320 x 240, 72Hz [13e] 1400 x 1050, 60Hz, 75Hz [144] 400 x 300, 72Hz [154] 512 x 384, 70Hz [175] 720 x 480, 75Hz [17a] 720 x 576, 75Hz ... (--) SAVAGE(0): No suitable BIOS mode found for 1280x600 60Hz. (II) SAVAGE(0): Not using mode 1280x600c (no mode of this name) This is your problem; it's caused by the VESA BIOS not having any defined mode for 1280x600. For other chipsets (e.g. Intel 915), there are tools to patch the BIOS image in memory, just before securelevel is raised. But I'm not sure if there is something similar for Savage adapters...
Re: Libretto L1 xorg.conf
ICMan wrote: Try the following modelines: Modeline 1280x600 77.82 1280 1344 1480 1680 600 601 604 626 Modeline 1280x600 76.04 1280 1336 1472 1664 600 601 604 626 Modeline 1280x600 75.00 1280 1336 1472 1664 600 601 604 626 If they don't work with the VESA driver, look up the videocard type for your Libretto, and use that accellerated driver with these modelines. Raja's already using the accelerated driver, but I think the following setting (from savage(4)) might also be needed, in addition to the modelines: Option UseBIOS boolean Enable or disable use of the video BIOS to change modes. Ordinarily, the savage driver tries to use the video BIOS to do mode switches. This generally produces the best results with the mobile chips (/MX and /IX), since the BIOS knows how to handle the critical but unusual timing requirements of the various LCD panels supported by the chip. To do this, the driver searches through the BIOS mode list, looking for the mode which most closely matches the xorg.conf mode line. Some purists find this scheme objectionable. If you would rather have the savage driver use your mode line timing exactly, turn off the UseBios option. Note: Use of the BIOS is required for dualhead operation. Default: on (use the BIOS). Raja, can you try experimenting with this setting?
Re: trying to build mod_python on OpenBSD
edgar mortiz wrote: trying to build mod_python on OpenBSD 3.7 with the following configuration. Python 2.4 (source build) --disabled-share Apache 2.0.59 --enable-so mod_python 3.2.10 --with-apxs OpenBSD comes with Apache 1.3.29, so you should try mod_python 2.7.1 instead. A quick test here shows that at least compiles and installs without any problems, using the system Apache and the python 2.4 port. Whether it actually works in the chroot, I haven't tried yet... :)
Re: openBSD 3.9 on hp/comapq proliant 8000
Czes3aw Liebert wrote: my h/w is: hp/comapq proliant 8000: - 8x Xeon 550MHz - 8GB ram - compaq array controller 4250ES - 1x intel 82558b lan - 1x intel 82559 lan - 8x 18GB scsi u160 Try to get at least a dmesg and post it here, see: http://www.openbsd.org/faq/faq4.html#getdmesg
Re: iwi(4): contact info for Intel is out of date
Alec Berryman wrote: I just tried to contact Intel about the Intel PRO/Wireless 2200BG firmware, but my email to [EMAIL PROTECTED] (the suggested contact in iwi(4)) bounced because it's now invalid. Does anyone know the new official contact point? I don't know anyone at Intel, but you might want to try some others from Theo's original announcement: http://marc.theaimsgroup.com/?l=openbsd-miscm=109994542424009w=2
Re: 4.0 i386 MP/clock issue?
Darrin Chandler wrote: XP and all other versions of Windows set the clock to local time, whereas OpenBSD sets it to GMT/UTC. It's probably better to say all non-braindead OSes set the clock to UTC. ;) That said, if Jason just runs config -ef /bsd and sets the timezone properly, his problem should be resolved; at least, until the next DST change...
Re: OpenBSD-current (Changelog): Disable Speedstep and p4tcc setperf mechanisms on SMP systems
Brian Curtis wrote: I was reviewing the changelog for OpenBSD-current and came across the following: Disable Speedstep and p4tcc setperf mechanisms on SMP systems. This was done because the current setperf implementation isn't smp-safe. Fixing this is a rather large undertaking, however; but if you've got patches, post them to -tech. ;)
Re: cpu1: unknown i686 model 1, can't get bus clock
Sevan / Venture37 wrote: I have just installed the 4.0-beta snapshot noticed a error message when booting GENERIC.MP cpu1: unknown i686 model 1, can't get bus clock the machine is a old IBM PC 365, dual p-pro. the machine was previously running 3.9-STABLE without any such errors. Can you please try the following patch? Note that this error isn't harmful at all, I just never saw this code tested by someone with a Pentium Pro CPU. :) Index: sys/arch/i386/i386/machdep.c === RCS file: /cvs/src/sys/arch/i386/i386/machdep.c,v retrieving revision 1.362 diff -u -d -p -r1.362 machdep.c --- sys/arch/i386/i386/machdep.c10 Jul 2006 19:45:22 - 1.362 +++ sys/arch/i386/i386/machdep.c9 Aug 2006 00:07:30 - @@ -2095,6 +2095,7 @@ p3_get_bus_clock(struct cpu_info *ci) break; } break; + case 0x1: /* Pentium Pro, model 1 */ case 0x3: /* Pentium II, model 3 */ case 0x5: /* Pentium II, II Xeon, Celeron, model 5 */ case 0x6: /* Celeron, model 6 */
Re: Logging failed console login attempts
Will H. Backman wrote: The console on OpenBSD 3.9 release doesn't seem to log unknown username or failed login attempts anywhere. See this commit: http://www.openbsd.org/cgi-bin/cvsweb/src/etc/syslog.conf#rev1.14 Make the default syslog.conf not make the console and root logins unusable when problems occur. Provide commented out examples showing people how to direct output to /dev/console or as messages to root, for situations where such output might acutally be useful, rather than something that keeps you from fixing a problem due to the screen getting spewed at.
Re: slow realloc: alternate method?
Jacob Yocom-Piatt wrote: an alternative to this procedure would be to scan through the CSV file to determine how many array entries i would need, realloc it all at once, then go back through the CSV file again to read the data into the array. Try starting with a reasonable number of lines, e.g. the average number of lines in most of your csv files, and doubling the buffer each time you fill it up.
Re: C++ problem in current snapshot (2006-05-22)
Toni Mueller wrote:
-
#include iostream.h
int main(){ cout Hello World! endl; return 0;}
-
Compiling it goes like this:
$ c++ testit.cc
/tmp//cch21612.o(.text+0x1c): In function `main':
: undefined reference to `endl(ostream)'
/tmp//cch21612.o(.text+0x29): In function `main':
: undefined reference to `cout'
/tmp//cch21612.o(.text+0x2e): In function `main':
: undefined reference to `ostream::operator(char const*)'
/tmp//cch21612.o(.text+0x37): In function `main':
: undefined reference to `ostream::operator(ostream (*)(ostream))'
collect2: ld returned 1 exit status
You must have screwed up your compiler installation. This program
compiles and links fine on my -current machines, although it of course
spits out a huge warning about the deprecated iostream.h header.
Are you sure there is no rogue iostream.h file lying around somewhere in
your compiler include path? You shouldn't use includes unless you
know that you need them.
Re: Intel 945GM + Dell Latitude D620 resolution woes
http://saba.island.nu/openbsd/Xorg.0.log.txt First of all, are you sure your screen is really 1440x900? The driver thinks not: (II) I810(0): Display Info: LFP (local flat panel): attached: TRUE, present: TRUE, size: (1280,800) ... (II) I810(0): Lowest common panel size for pipe B is 1280 x 800 ... (II) I810(0): PanelID returned panel resolution : 1280x800 Dell seems to sell these laptops with both 1280x800 and 1440x900 screens, so maybe you're just aiming for the impossible. :) Second, your video mode table seems quite busted up, most entries contain only zeroes? If this is only the case if you run 915resolution, it might be some bug in 915resolution. Also, try just running without a xorg.conf file. For a laptop display panel, you should never need to specify refresh frequencies manually, and all your other devices should be detected automatically anyway. Cheers, Dimitry
Re: [patch] Intel 945G/GM AGP support (including 945GM for X.org)
vladas wrote: making all in programs/Xserver/Xext/extmod... make: don't know how to make /usr/include/stdarg.h. Stop in /usr/Xbld/xc/program s/Xserver/Xext/extmod. *** Error code 2 You probably don't have the compiler installed at all. Did you install comp39.tgz? If not, see section 4.10 of the FAQ. Btw, there should be snapshots coming up now which already include the 945 patches for both the kernel and X.org, so maybe it's easier to try one of those. Cheers, Dimitry
Re: BSD-licensed Camellia 128-bit block cipher
Alexey E. Suslikov wrote: Camellia was certified as the IETF standard cipher (Proposed Standard) for SSL/TLS cipher suites (RFC4132) and IPsec (RFC4312). Source: https://info.isl.ntt.co.jp/crypt/eng/camellia/source_s.html Hmm, isn't the notice on that page incompatible with the BSD license? Any product equipped with Camellia encryption algorithm (including the open sources) is a controlled product regulated under the Japanese Foreign Exchange and Foreign Trade Law, though the algorithm is public. When you plan to export or take this product out of Japan, or provide any juridical person having its main office in Japan, concerning property or business of such a juridical person which is located overseas, please obtain a permission, as required by the Law and related regulations, from the Japanese Government.
Re: gcc miscompiles ntohs16() inline assembly in OpenBSD 3.8
Otto Moerbeek wrote: We notice that the upcoming OpenBSD 3.9 still uses gcc 3.3.5. Is the gcc 3.3 branch still a supported product for the gcc people, and this a fix that slipped through the cracks in their usual maintenance process? I have no idea if the 3.3 branch is actively maintained by the gcc people. http://gcc.gnu.org/gcc-3.3/ says 3.3.6, released 2005-05-03, is the last 3.3.x version.
Re: X11 Issue - Integrated Intel Media Accelerator 900 Graphics (Intel 915GM)
d 269330400 wrote: I recently installed OpenBSD 3.8 (I haven't received my 3.9 CD in the mail yet), and am having problems getting X to work (among other things). It's a Dell Inspiron 1300 notebook w/ Integrated Intel Media Accelerator 900 Graphics (Intel 915GM). The full dmesg is below. Wait for your 3.9 CD or use -current, support for Intel 915 has gone in after 3.8. (See also the release notes for 3.9.) Until then, try using X with the VESA driver, which will work, albeit a bit slow... :)
Re: security hole in sendmail
Oliver Peter wrote: A race condition exists in sendmail's handling of asynchronous signals. A remote attacker may be able to execute arbitrary source code with the privileges of the user running sendmail, typically root. Excuse my question - I don't want to attack our loved project but does that mean that we've got a second remote hole? Don't kick my ass. Not in the default install. :) From afterboot(8): For the default installation, sendmail is configured to only accept connections from the local host and to not accept connections on any external interfaces.
Re: multibooting X40 / lenovo load
Chris Paul wrote: Now, after creating slice a, the OpenBSD disklabel does not do the math for me. It give me the same beginning offset as for wd0a. So I then: did the math (added all the offsets created the partitions), but now it won't boot (it just goes ahead and boots XP). Show us fdisk wd0 and disklabel wd0 output, or it's difficult to help at all. :) For reference, my X41 triple boots XP, Ubuntu and OpenBSD without a hitch. Oh and OpenBSD is at the end of the disk, 1024 cylinder problems were solved quite some time ago.
Re: ADSL and PPPoA
Joel Gudknecht wrote: The netmask is 255.0.0.0 and yes, it's a speedtouch. What part would you recommend reconfiguring? I had a look at the web-interface and nothing jumped out that I should have changed. I'm trying to avoid having to mess with pppoe in userland if at all possible. Try this (warning, Dutch): http://www.mixfix.nl/helpfiles/alcatel/sipspoof.asp
Re: Apple MacBook Pro support
Constantine A. Murenin wrote: I know it's kind of early, but is OpenBSD/i386 going to run peacefully on the yesterday-announced Apple MacBook Pro, or for that matter the iMac with Intel Code Duo processor? :-) Probably, once you donate a few of them to the OpenBSD developers. ;) [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: Broadcom BCM5721 driver for OpenBSD 3.6
Reeann Zhang wrote: Do you have driver of Broadcom BCM5721 Gigabit Ethernet Controllers for openBSD 3.6 The card is not detected when installing. Try updating to 3.7 or 3.8, this should at least detect the card. You might have some problems with the link detection though. (At least, this occurs for me with a BCM5751.) [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: IBM Thinkpad X41 report?
On 2005-10-26 at 23:52:52 Mattieu Baptiste wrote: just resumed my work on i386-laptop.html after vacation, and I noticed we don't have any reports on the IBM/Lenovo Thinkpad X41. It's not an X41, but I want to give some feedback on new IBM/Lenevo T Series (T43 2668 in my case). Just FYI, see my previous message about the X41 on the misc@ list. Basic functionality works, but some things are still a bit quirky. [demime 1.01d removed an attachment of type application/pgp-signature]
Re: ibm x41
Theo wrote: Hi there, i was searching info on installing openBSD on the x41 when i saw your reply in an mailinggroup(http://www.mail-archive.com/misc@openbsd.org/msg09090.html). I am wondering if you know if this is going to be possible, I just got the feeling from the message that you are trying to getting it work properly. I apologise if I am wasting your time, but it would make me so happy if I finally got an answer to this. No problem. I've indeed installed OpenBSD on my X41, but the results aren't completely satisfactory. All in all, most hardware gets detected properly, but a few problems remain: - The Broadcom ethernet interface sometimes has problems coming up or down. This depends a bit on the type of switch or hub you connect it to. I'm still investigating the driver, to see what's wrong with it, since e.g. Windows XP and Linux 2.6.x have no problems with the card. Most of the time, if I manually up the interface after logging in, it works ok. - The Intel wireless interface gets detected, but since I have no wireless basestation at home (yet), I can't really test it. Also, you need to have some extra proprietary firmware for it, which you need to download from sourceforge. It's not clear which files are needed, since the names in the manpage don't match those on sourceforge. - I can only get X.org working in vesa mode, which works okay, but rather slow, of course. The X.org i810 should work too, but it always crashes with a garbled screen, and some fatal errors in the log file: ... (WW) xf86AcquireGART: AGPIOC_ACQUIRE failed (Device busy) ... (WW) I810(0): xf86AllocateGARTMemory: allocation of 1 pages failed (Cannot allocate memory) (EE) I810(0): Failed to allocate HW cursor space. (WW) I810(0): xf86AllocateGARTMemory: allocation of 4 pages failed (Cannot allocate memory) (EE) I810(0): Failed to allocate HW (ARGB) cursor space. (WW) I810(0): xf86AllocateGARTMemory: allocation of 1 pages failed (Cannot allocate memory) (EE) I810(0): Failed to allocate Overlay register space. (II) I810(0): Allocated 64 kB for the scratch buffer at 0xfff (WW) I810(0): Disabling HW cursor because the cursor memory allocation failed. (WW) I810(0): Disabling Xv because the overlay register buffer allocation failed. ... (WW) I810(0): Extended BIOS function 0x5f05 failed. (II) I810(0): xf86BindGARTMemory: bind key 5 at 0x007bf000 (pgoffset 1983) (II) I810(0): xf86BindGARTMemory: bind key 4 at 0x0fff (pgoffset 65520) (WW) I810(0): xf86BindGARTMemory: binding of gart memory with key 4 at offset 0xfff failed (Invalid argument) This is rather strange, since it works fine under Linux, even with exactly the same version of X.org (6.8.2)! As for the rest, everything works except the more or less proprietary devices in the machine, e.g: - The accelerometer (aka Active Protection System) can be read through the hw.sensors sysctls: $ sysctl hw.sensors hw.sensors.0=aps0, X_ACCEL, raw, 439 hw.sensors.1=aps0, Y_ACCEL, raw, 433 hw.sensors.2=aps0, X_VAR, raw, 439 hw.sensors.3=aps0, Y_VAR, raw, 433 hw.sensors.4=aps0, Temp1, temp, 33.00 degC / 91.40 degF hw.sensors.5=aps0, Temp2, temp, 33.00 degC / 91.40 degF hw.sensors.6=aps0, KBD_ACT, raw, 0 hw.sensors.7=aps0, MS_ACT, raw, 0 hw.sensors.8=aps0, LID_OPEN, raw, 1 hw.sensors.9=aps0, unknown, raw, 7 but I haven't really looked around yet for a program that actually does something with this data. - The fingerprint reader, which is recognized as a ugen(4) device. I have no idea whether there is any publicly available spec to communicate with it. Would be nice to have, but not critical of course. - The TPM (aka Fritz chip), which should be somewhere under the Intel 82801FBM LPC controller, is simply not reported anywhere. I also have no idea if there's any spec for this thing. Would be nice to store some private keys in. ;) For your reference, here's a dmesg of a GENERIC kernel built from -current CVS: OpenBSD 3.8-current (GENERIC) #0: Tue Oct 18 12:43:55 CEST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1.50GHz (GenuineIntel 686-class) 599 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2 cpu0: Enhanced SpeedStep 600 MHz (988 mV): speeds: 1500, 1200, 1000, 800, 600 MHz real mem = 1600561152 (1563048K) avail mem = 1453129728 (1419072K) using 4278 buffers containing 80130048 bytes (78252K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(24) BIOS, date 08/09/05, BIOS32 rev. 0 @ 0xfd750 apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 63% apm0: AC off, battery charge high, estimated 2:23 hours apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xfd6e0/0x920 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdec0/240 (13 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #3 is the last bus
Re: OpenBSD on IBM X40 ...
On 2005-09-29 at 12:19:12 Waldemar Brodkorb wrote: ... just rocks :} On an X41, there are still some problems, though. I've not been able to get the onboard Broadcom BCM5751M interface working, it always reports 'no carrier'. Also, the X41 supposedly always comes with the Intel 2915 wireless stuff, and I was unable to find the correct firmware files (ones that work, in any case). At least OpenBSD's boot loader doesn't crash on this machine, as FreeBSD's does. ;)
Re: USB-CDROM with X40
On 2005-09-29 at 20:37:11 Marcus Glocker wrote: I am soon receiving a IBM Thinkpad X40 to use it with OpenBSD-current. As I don't really want to have an Ultrabase, I am wondering if it's possible to boot OpenBSD with a USB-CDROM. Any experiences? I had no problems booting OpenBSD 3.7 release, and recent 3.8 snapshots on my X41, using an external Lite-On DVD+-RW drive. The UltraBase is somewhat nice, but way too expensive IMHO. :-) Since I now have given back the drive to the person I borrowed it from, I'm still searching for a nice alternative way to boot OpenBSD installation. Anyone have experience booting OpenBSD from a USB stick? My BIOS seems to support it, I'll go look into it tomorrow, or or this weekend, probably.
Re: How to mount cdrom
On 2005-09-25 at 20:56:19 Jeff Roach wrote: mount -t cd9660 -r /dev/cd0a /mnt/cdrom and variations using cd0c and /cdrom I get an error message either saying device not configured or Invalid argument ---snip--- Sep 25 12:59:46 puffy /bsd: cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x28 Sep 25 12:59:46 puffy /bsd: SENSE KEY: Illegal Request Sep 25 12:59:46 puffy /bsd: ASC/ASCQ: Illegal Mode For This Track Your CD is probably rotten. Replace it with a good one. :) Is there any way to copy dmesg from the terminal and past it into an x window? Or just to copy anything between a terminal and x? Why the horrible, clunky GUI-mindedness? Just run the dmesg(8) command, and redirect the output anywhere you want... [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Receiving mail
On 9/16/2005 at 05:47:29 Jeffrey Roach wrote: Can anyone tell me why I don't receive mail from the list? I receive only my own posts. My preference is set to receive it daily. Probably because you're using Hotmail, which filters out anything not approved by Microsoft? :) Just check your junk mail settings. [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Hard Disk Password Security Info
On 2005-08-18 at 00:46:39 Dave Feustel wrote: With most notebooks it is possible to secure the hard disk against unauthorized access with the aid of a password. See the atactl(8) manpage, in particular the sec* commands. However, I don't believe these harddisks actually encrypt all data on the disk, so it's not really a security measure. By zapping the firmware, or triggering some other magic switch, you're probably always able to unlock these disks. [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Writing to console...
On 2005-06-15 at 17:17:30 kevin wrote: I was downloading GNU gcc on a machine and when I looked over after the download, the screen was writing: All work and no play makes Jack a dull boy It's probably just your screensaver, don't panic. :P See http://www.jwz.org/xscreensaver/screenshots.html and search for XJack. [demime 1.01d removed an attachment of type application/pgp-signature]
Re: DNS Configuration Problem
On 2005-05-21 at 16:02:46 Michael wrote: This is when I check again, and yes, /etc/rndc.key is there but /usr/sbin/named again tells me that it is not there. Read the named(8) manpage; it uses a chroot to /var/named by default. Put your rndc.key file in /var/named/etc, and you should be ok. Also, a symlink from /var/named/etc/namedb to /etc/namedb can be handy.
Re: error messages
On 2005-05-16 at 17:45:29 Kaj Mdkinen wrote: I connect to my firewall with putty. How can I get rid of messages like these from appearing in my ssh terminal session? These appeared twice a second so it is wery hard to work with the console. (It was obviously someone trying to get access to something?) - Fix your syslog.conf - Don't login as root, use sudo - Add those script kiddies and worms to your blacklist(s) [demime 1.01d removed an attachment of type application/pgp-signature]
Re: apachectl - Too many open files
On 2005-05-08 at 20:40:53 GV wrote:
/usr/sbin/apachectl: /etc/rc.conf.local[90]: .: /etc/rc.conf.local: Too
many
open files
Maybe you copied /etc/rc.conf to /etc/rc.conf.local, edited some
stuff, but forgot to remove these last few lines:
local_rcconf=/etc/rc.conf.local
[ -f ${local_rcconf} ] . ${local_rcconf} # Do not edit this line
In this case, just remove them. :)
[demime 1.01d removed an attachment of type application/pgp-signature]
