OpenBSD 4.4 amd64 bsd.mp can't detect 4GB memory
Enabling bigmem=1: -real mem = 3734757376 (3561MB) -avail mem = 3624775680 (3456MB) +real mem = 4271632384 (4073MB) +avail mem = 4148350976 (3956MB) Also, from sys/arch/amd64/amd64/machdep.c: /* Tweakable by config(8) */ How? 2008/12/16 Toni Mueller : > Hello, > > On Mon, 15.12.2008 at 15:47:06 +0100, Paul de Weerd wrote: >> On Mon, Dec 15, 2008 at 10:40:44PM +0800, C. Soragan Ong wrote: >> | I am using OpenBSD 4.4 and is having problem detecting 4GB ram. Below is >> the >> | dmesg >> >> Well, all memory is found (see the spdmem entries in your dmesg), but > > these messages suggest that he has 4GB of RAM installed in his machine, > right? > >> not all of it is supported by the default kernel. You'll have to >> enable bigmem and compile a new kernel yourself. > > I thought that 4GB of RAM *are* supported in the default kernel? > > But apart from that, I'm having a quite similar problem with a > completely different machine. It turns out that very much RAM is eaten, > depending on various BIOS settings. I haven't figured out how to tune > it, but currently I'm losing some 700+MB this way (really AWFUL!). I > have found out that enabling PXE eats some 20MB per NIC on which it is > enabled, though. > > > Kind regards, > --Toni++
Only one headphone jack working with Intel 82801
I hadn't noticed this until now and I don't know if this is a known issue(sorry I didn't find anything in the lists) or something I am doing wrong. My laptop has a dual headphone jack but only the left jack is working in OpenBSD. The hardware is okay and everything else seems to be working. Thank you $ dmesg | grep azalia # current GENERIC.MP with azalia debug enabled azalia0 at pci0 dev 27 function 0 "Intel 82801H HD Audio" rev 0x02: apic 2 int 21 (irq 9) azalia0: host: High Definition Audio rev. 1.0 azalia0: host: 4 output, 4 input, and 0 bidi streams azalia_attach: resetting azalia_attach: reset counter = 4999 azalia_attach: reset counter = 4985 azalia0: found a codec at #0 azalia0: found a codec at #2 azalia_init_corb: CORB allocation succeeded. azalia_init_corb: CORBWP=0; size=256 azalia_init_rirb: RIRB allocation succeeded. azalia_init_rirb: RIRBRP=0, size=256 azalia0: codec[0] vid 0x83847616, subid 0x02091028, rev. 2.1, HDA version 1.0 azalia0: nidstart=1 #functions=1 azalia_codec_init: FTYPE result = 0x0101 azalia_codec_init: There are 35 widgets in the audio function. azalia0: dac02 wcap=d0c05 azalia0: dac03 wcap=d0c05 azalia0: dac04 wcap=d0c05 azalia0: dac05 wcap=d0c05 azalia0: vendor06 wcap=fd0c05 azalia0: adc07 wcap=1d0541 azalia0: adc08 wcap=1d0541 azalia0: adc09 wcap=1d0541 azalia0: black0a wcap=400181 azalia0: unknown0b wcap=400181 azalia0: unknown0c wcap=400181 azalia0: unknown0d wcap=400181 azalia0: black0e wcap=400181 azalia0: black0f wcap=400181 azalia0: unknown10 wcap=400181 azalia0: unknown11 wcap=400181 azalia0: unknown12 wcap=41 azalia0: unknown13 wcap=41 azalia0: unknown14 wcap=41 azalia0: sel15 wcap=30010d azalia0: sel16 wcap=30010d azalia0: sel17 wcap=30010d azalia0: sel18 wcap=300103 azalia0: sel19 wcap=300103 azalia0: sel1a wcap=300103 azalia0: sel1b wcap=30090d azalia0: sel1c wcap=30090d azalia0: sel1d wcap=30090d azalia0: dac1e wcap=40211 azalia0: vendor1f wcap=f30201 azalia0: adc20 wcap=140311 azalia0: gray21 wcap=400301 azalia0: unknown22 wcap=430681 azalia0: beep23 wcap=7c azalia0: volume24 wcap=60 azalia_generic_codec_add_convgroup: looking for analog DACs azalia_generic_codec_add_convgroup: looking for digital DACs azalia_generic_codec_add_convgroup: looking for analog ADCs azalia_generic_codec_add_convgroup: looking for digital ADCs azalia0: dacgroup[0]: 02 03 05 04 azalia0: dacgroup[1]: 1e azalia0: adcgroup[0]: 07 08 09 azalia0: codec[2] vid 0x10951392, subid 0x02091028, rev. 0.0, HDA version 1.0 azalia0: nidstart=1 #functions=1 azalia_codec_init: FTYPE result = 0x0001 azalia_codec_init: There are 2 widgets in the audio function. azalia0: dac02 wcap=6211 azalia0: unknown03 wcap=40738d azalia_generic_codec_add_convgroup: looking for analog DACs azalia_generic_codec_add_convgroup: looking for digital DACs azalia_generic_codec_add_convgroup: looking for analog ADCs azalia_generic_codec_add_convgroup: looking for digital ADCs azalia0: dacgroup[0]: 02 azalia0: codecs: Sigmatel STAC9228X, CMD Technology/0x1392, using Sigmatel STAC9228X audio0 at azalia0 $ mixerctl -a inputs.dac_mute=off inputs.dac=126,126 inputs.dac2_mute=off inputs.dac2=126,126 inputs.dac4_mute=off inputs.dac4=126,126 inputs.dac3_mute=off inputs.dac3=126,126 inputs.vendor_mute=off inputs.vendor=126,126 outputs.hp_source=dac outputs.hp_dir=output outputs.hp_boost=off outputs.spkr_source=dac outputs.spkr_dir=output outputs.spkr_boost=off outputs.mic_source=dac4 outputs.mic_dir=input outputs.line_source=dac3 outputs.line_dir=output inputs.sel_source=mic outputs.sel=126,126 inputs.sel2_source=mic outputs.sel2=126,126 inputs.sel3_source=mic outputs.sel3=126,126 inputs.sel4_source=sel inputs.sel4_sel=126,126 inputs.sel5_source=sel2 inputs.sel5_sel2=126,126 inputs.sel6_source=sel3 inputs.sel6_sel3=126,126 record.adc_source=sel4 record.adc_mute=off record.adc2_source=sel5 record.adc2_mute=off record.adc3_source=sel6 record.adc3_mute=off outputs.SPDIF_source=dig-dac inputs.beep=85 outputs.hp_sense=plugged outputs.mic_sense=plugged outputs.line_sense=unplugged outputs.master=126,126 outputs.master.mute=off outputs.master.slaves=dac,vendor record.volume=0,0 record.volume.mute=off record.volume.slaves=adc,adc2,adc3 inputs.usingdac=02030504
Re: Only one headphone jack working with Intel 82801
Sorry, I always screw my reports. Now I see the mess.
The only option I get is dac3. I don't know what the hell they are - I
know nothing about sound hardware - but both work exactly the same in
Linux with regular earphones, if there is some technical difference I
am not aware of it. Next you will tell me I don't have a teacup tray
;)
I assumed they are made to fit those earphones with two sticks like
the ones you get in planes. They do in fact fit and sound right with
stereo sound. In OpenBSD I only get sound in one ear when the
earphones are plugged to both jacks at the same time.
1 2 Mic What happens(Linux in parentheses)
| | |
o o Stereo sound(Stereo sound)
o o No sound(Stereo sound)
o___o o Sound in one ear(Stereo sound)
$ mixerctl -v
inputs.dac_mute=off [ off on ]
inputs.dac=126,126
inputs.dac2_mute=off [ off on ]
inputs.dac2=126,126
inputs.dac4_mute=off [ off on ]
inputs.dac4=126,126
inputs.dac3_mute=off [ off on ]
inputs.dac3=126,126
inputs.vendor_mute=off [ off on ]
inputs.vendor=126,126
outputs.hp_source=dac [ dac dac2 ]
outputs.hp_dir=output [ input output ]
outputs.hp_boost=off [ off on ]
outputs.spkr_source=dac [ dac ]
outputs.spkr_dir=output [ input output ]
outputs.spkr_boost=off [ off on ]
outputs.mic_source=dac4 [ dac4 ]
outputs.mic_dir=input [ input output ]
outputs.line_source=dac3 [ dac3 ]
outputs.line_dir=output [ input output ]
inputs.sel_source=mic [ mic line spkr hp ]
outputs.sel=126,126
inputs.sel2_source=mic [ mic line spkr hp ]
outputs.sel2=126,126
inputs.sel3_source=mic [ mic line spkr hp ]
outputs.sel3=126,126
inputs.sel4_source=sel [ sel ]
inputs.sel4_sel=126,126
inputs.sel5_source=sel2 [ sel2 ]
inputs.sel5_sel2=126,126
inputs.sel6_source=sel3 [ sel3 ]
inputs.sel6_sel3=126,126
record.adc_source=sel4 [ sel4 mic2 ]
record.adc_mute=off [ off on ]
record.adc2_source=sel5 [ sel5 mic2 ]
record.adc2_mute=off [ off on ]
record.adc3_source=sel6 [ sel6 mic2 ]
record.adc3_mute=off [ off on ]
outputs.SPDIF_source=dig-dac [ dig-dac vendor2 adc adc2 adc3 ]
inputs.beep=85
outputs.hp_sense=plugged [ unplugged plugged ]
outputs.mic_sense=plugged [ unplugged plugged ]
outputs.line_sense=plugged [ unplugged plugged ]
outputs.master=126,126
outputs.master.mute=off [ off on ]
outputs.master.slaves=dac,vendor { dac dac2 dac4 dac3 vendor sel sel2
sel3 beep }
record.volume=0,0
record.volume.mute=off [ off on ]
record.volume.slaves=adc,adc2,adc3 { adc adc2 adc3 }
inputs.usingdac=02030504 [ 02030504 1e ]
and dmesg for good measure:
OpenBSD 4.4-current (GENERIC.MP) #7: Wed Jan 7 04:59:17 JST 2009
r...@amaterasu.amaterasu:/sys/arch/amd64/compile/GENERIC.MP
real mem = 3747008512 (3573MB)
avail mem = 3624816640 (3456MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf71c0 (44 entries)
bios0: vendor Dell Inc. version "A11" date 06/19/2008
bios0: Dell Inc. XPS M1330
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP HPET APIC MCFG BOOT SSDT
acpi0: wakeup devices PCI0(S5) PCIE(S4) USB1(S0) USB2(S0) USB3(S0)
USB4(S0) USB5(S0) EHC2(S0) EHCI(S0) AZAL(S3) RP01(S3) RP02(S3)
RP03(S3) RP04(S3) RP05(S3) RP06(S5) LID_(S3) PBTN(S4) MBTN(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz, 2394.42 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,NXE,LONG
cpu0: 3MB 64b/line 8-way L2 cache
cpu0: apic clock running at 199MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz, 2394.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,NXE,LONG
cpu1: 3MB 64b/line 8-way L2 cache
ioapic0 at mainbus0 apid 2 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiprt0 at acpi0: bus 3 (PCIE)
acpiprt1 at acpi0: bus -1 (AGP_)
acpiprt2 at acpi0: bus 11 (RP01)
acpiprt3 at acpi0: bus 12 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus 13 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiprt7 at acpi0: bus 9 (RP06)
acpiprt8 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpitz0 at acpi0: critical temperature 104 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PBTN
acpibtn2 at acpi0: SBTN
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT0 model "DELL KP4058" serial 108 type LION oem "Sanyo"
acpivideo at acpi0 not configured
acpivideo at acpi0 not configured
acpivideo at acpi0 not configured
cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2401, 2400, 2000, 1600, 1200, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1
pchb0 at pci0 dev 0 function 0 "Intel GM965 Host" rev 0x0c
vga1 at pci0 dev 2 function 0 "Intel GM965 Video" rev 0x
Re: Only one headphone jack working with Intel 82801
> I'm not familiar with airplane headphones. from your description, it > sounds like one is the left channel and one is the right channel. > do the plugs look different? that is, is the "ring" in the same place > on both? I would expect it to be in different places. The ones I have can be used in normal mode and two plugs mode. The second one looks like a retractile mono plug. If it is out, one of the channels of the regular stereo plug is muted. I guess it is an alternative way of having stereo sound. I just happened to notice that one of the jacks didn't have sound output because I had the airplane headphones plugged in.
Re: dmesglog
2009/2/14 Hannah Schroeter : > Hi! > > On Fri, Feb 13, 2009 at 01:23:07PM -0700, Theo de Raadt wrote: >>I want to remind everyone of two things > >>First, it is nice if you mail a dmesglog entry once in a while. > >> (dmesg | sysctl hw.sensors) | mail -s "type of machine" >> dm...@openbsd.org > > I guess you mean > (dmesg ; sysctl hw.sensors) | mail -s "type of machine" dm...@openbsd.org > ^ > >>[...] > > Kind regards, > > Hannah. > > Hello, Forgive me, but wouldn't (echo "Subject: type of machine" ; dmesg ; sysctl hw.sensors) | sendmail -f$YOUR_EMAIL dm...@openbsd.org be better? Else, if the hostname is not a valid domain, the mail does not get through. Regards,
What happened to citrus?
Hello, Why wasn't citrus i18n support merged in the end? Was it for technical reasons, lack of testing, licensing, NIHS or what? Thank you,
Re: Browsers was: Re: firefox starts two times
2009/3/24 Jacob Meuser : >> > I only got feedback from one person about swfdec update/sndio backend >> > addition. >> >> do you read that as no interest in said port? > > somewhat. > > -- > jake...@sdf.lonestar.org > SDF Public Access UNIX System - http://sdf.lonestar.org > > Sorry, I had downloaded the patches right away but they didn't apply cleanly on my tree and I had forgotten about it but I am interested in flash support as well. As much as we'd like it disappearing from the web it seems it's here to stay. It is working fine here(6.5-current amd64), better than in Linux, and a lot better than gnash. Thank you for all the sound related work.
UTF-8 on the file system?
utf-8 is ignored as regular valid ASCII in most utilities. This is what makes utf-8 so nice. The main problem(1) is for utilities like for example ls and ed that use isprint to determine if they are allowed to print a character and print '?' or an octal escape sequence on nonprint chars. With a hacked libc and a utf-8 version of multibyte functions as well as a few fixes on apps solve most of these problems, gtk apps and scim will be happy with just being able to set the locale(2). However, advanced console applications will need the full character support and also support in the console driver for full glitch-less functionality. Your problem is likely 1 or 2. 2009/5/13 Toni Mueller : > Hi Otto, > > thanks for the quick answer. > > On Wed, 13.05.2009 at 10:50:37 +0200, Otto Moerbeek wrote: >> On Wed, May 13, 2009 at 10:35:25AM +0200, Toni Mueller wrote: >> > fd = open(filename_with_utf8_characters); >> > >> > succeed on a standard OpenBSD disk (FFS, if I'm not mistaken), using >> > open(2) and fopen(3). >> >> OpenBSD does not restrict or interpret filenames in any way, apart >> from the obvious: / and NUL are not allowed in filenames. > > I guess, but don't know, that NUL is not part of any UTF-8 character... > >> So we accept funny chars in filenames, but do nothing special with them. > > Ok, that sounds great for a start. It means that the user can do > whatever he likes, in terms of weird filenames. > >> > I'm currently debugging a third-party application that happens to want >> > to use UTF-8 filenames, but doesn't seem to find them, and, FWIW, the >> > file names I get with "ls" are ISO-Latin-1 encoded, anyway. >> I suppose hwta you are seeing depends on your terminal. > > Erm... I did: > > ls -al | od -c > ls-output.txt > > and looked at that to determine what was on the file system, because > I've been bitten by weird encoding problems often enough already. > This way I determined that the special chars were indeed Latin1 > encoded. Just saying 'ls -al' would only yield blanks in the offending > places, and otherwise only tends to garble my display. > >> The kernel and base utilities encode nothing. Some utilities might >> protect funny chars being printed on a terminal (e.g. see ls -q). > > Thanks for the hint. > >> The kernel and libc do not do any encoding or decoding. What third >> part libs and applications do, who nows. > > B ;) > > > Kind regards, > --Toni++
Re: removing a pesky file
rm `ls | grep E` would delete that file leaving others alone. Regards,
Re: removing a pesky file
2009/5/15 Ryan Flannery : > tarski> rm `ls | grep E` > ~,u?} w=R1 T)U7r 5\4gm(_EW]W-sn^[[?1;2c: No such file or directory > B B B B B B B B B Ec?J9 K%Mx/!...@s S,W7g?5 > 0,z: No such file or directory B B B B B B M}OWDt?Yw?rB~[*6t?0h|7 tarski> True, I had checked it using the shell to recreate your file. I get that now. However, rm *EV* does delete it without complaining at all(rm -i will print the name and thus fail), still it doesn't seem like you had tried everything...
Re: OpenBSD 4.3 running in VirtualBox? Anyone have it working properly?
I tried to run a recent i386 4.4 beta on a KVM/QEMU virtual machine under Ubuntu and there are some problems with the emulated network. The driver constantly reports timeouts. > re0: watchdog timeout As a side effect the connection is very slow. I assume that doesn't happen on the actual hardware that QEMU is supposed to emulate, but other OSes don't have the same problem. 2008/8/7 Tomas Bodzar <[EMAIL PROTECTED]>: > VirtualBox sucks to version 1.6.2 .There is a 1.6.4 now,but I don't test it. > I use Qemu on BSD/Linux/Windows,it's better in my opinion. > (work with VirtualBox,Vmware Server 1.0.x,2.x,MS Virtual Server,MS Virtual PC) > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Daemon > Sent: Thursday, August 07, 2008 3:31 AM > To: misc > Subject: OpenBSD 4.3 running in VirtualBox? Anyone have it working properly? > > OpenBSD 4.3 running in VirtualBox? Anyone have it working properly and if so, > how? > > Same problems as reported here: http://www.virtualbox.org/ticket/192 > > Regards,
OpenBSD 4.3 running in VirtualBox? Anyone have it working properly?
Thanks, I had just found this out and was writing about it. Apparently, KVM or the distributions have changed the default from ne2k. Either way, rtl8139 works in real machines so it is unclear whether the problem is a bug in OpenBSD or QEMU. 4.3 is affected as well. 2008/8/7 william dunand <[EMAIL PROTECTED]>: > 2008/8/7 Jordi Beltran Creix <[EMAIL PROTECTED]>: >> I tried to run a recent i386 4.4 beta on a KVM/QEMU virtual machine >> under Ubuntu and there are some problems with the emulated network. >> The driver constantly reports timeouts. >>> re0: watchdog timeout >> As a side effect the connection is very slow. I assume that doesn't >> happen on the actual hardware that QEMU is supposed to emulate, but >> other OSes don't have the same problem. > > I had this problem too. > qemu allows you to work around it easily just by changing the model of > the emulated network card. > "ne2k_pci" is working just fine. > > Cheers, > William
The correct way to use bsd.rd
I am using a virtual machine to try and follow -CURRENT.I have installed a snapshot, downloaded the cvs source, built it and run to see if it worked, up to there everything is okay. Reading the FAQ I found out that the "official" way to follow current more or less closely is to build a ramdisk image(or download a bsd.rd image from the servers) and boot from that. However, when I place my newly generated image in / and boot from it, it tells me that it lacks a root filesystem. Obviously it is lacking a ramdisk, but I don't know where to get that from and I have been unable to find the appropriate manpage or piece of documentation. Could you please point it out to me? Thank you
The correct way to use bsd.rd
I am NOT trying to boot my root partition using bsd.rd. Although I see that I can using the -a option. I was trying to get a bsd.rd image like the one from the CDs, with the Install Upgrade and Shell options. I followed the instructions from release(8) closely but the generated binary is the same - it tells me it tries to boot from the ramdisk device and that it has size 0 and reboots. I don't intend it to use as a way to upgrade, it is easier to download the newer snapshots, I was just testing the functionality. I am obviously missing something and this is why I asked. I've just downloaded the one from the snapshots and see it is RAMDISK_CD. Do I need to build the RAMDISK_CD kernel instead of RAMDISK and it will work? Thank you 2008/9/28 Stijn <[EMAIL PROTECTED]>: > Jordi Beltran Creix wrote: >> >> I am using a virtual machine to try and follow -CURRENT.I have >> installed a snapshot, downloaded the cvs source, built it and run to >> see if it worked, up to there everything is okay. >> Reading the FAQ I found out that the "official" way to follow current >> more or less closely is to build a ramdisk image(or download a bsd.rd >> image from the servers) and boot from that. However, when I place my >> newly generated image in / and boot from it, it tells me that it lacks >> a root filesystem. Obviously it is lacking a ramdisk, but I don't know >> where to get that from and I have been unable to find the appropriate >> manpage or piece of documentation. Could you please point it out to >> me? >> Thank you >> >> >> >> > > From the FAQ: > http://openbsd.org/faq/faq4.html#bsd.rd > > bsd.rd is used to install, upgrade or doing system maintenance. It's not > used to boot of your machine for normal usage. > > HTH, > Stijn
The correct way to use bsd.rd
Okay, thank you. This is what I wanted to know. 2008/9/30 Nigel J. Taylor <[EMAIL PROTECTED]>: > The RAMDISK_CD kernel bsd in > /usr/src/sys/arch/`machine`/compile/RAMDISK_CD is not the same as bsd.rd > as you have found out it has an empty ramdisk, it the initial stage, to > get a bsd.rd you need to build a release after building the userland. > Details for building a release are in the FAQ's and man pages. > > Building the release will use the RAMDISK_CD to build the kernel in bsd, > reserving space for the ramdisk, and then the make release process adds > the ramdisk (miniroot) into this creating the bsd.rd. You will find what > the build release does under > > /usr/src/distrib/ramdisk > > The install / update shells are in > > /usr/src/distrib/miniroot > > The resulting bsd.rd created by the release is placed into > $DESTDIR/snapshot, and then into the release directory $RELEASEDIR. > > The RAMDISK - is for the floppynn.fs, RAMDISKB, RAMDISKC for > floppynnB.fs, and floppynnC.fs. > > It all works for building a release, but as pointed out never needed for > following current. I build a release so I have an install with all the > patches for stable, I can use on a number of machines which use stable, > rather than applying the patches on each. > > If what your are asking is can you just build bsd.rd without building > the full release - possibly, maybe setting DESTDIR, RELEASEDIR and a > make in /usr/src/distrib/ramdisk might work, really your on your own if > your trying to do that. > > Regards > > Nigel Taylor > > > Jordi Beltran Creix wrote: >> I am NOT trying to boot my root partition using bsd.rd. Although I see >> that I can using the -a option. I was trying to get a bsd.rd image >> like the one from the CDs, with the Install Upgrade and Shell options. >> I followed the instructions from release(8) closely but the generated >> binary is the same - it tells me it tries to boot from the ramdisk >> device and that it has size 0 and reboots. I don't intend it to use as >> a way to upgrade, it is easier to download the newer snapshots, I was >> just testing the functionality. I am obviously missing something and >> this is why I asked. >> I've just downloaded the one from the snapshots and see it is >> RAMDISK_CD. Do I need to build the RAMDISK_CD kernel instead of >> RAMDISK and it will work? >> >> Thank you >> >> 2008/9/28 Stijn <[EMAIL PROTECTED]>: >>> Jordi Beltran Creix wrote: >>>> I am using a virtual machine to try and follow -CURRENT.I have >>>> installed a snapshot, downloaded the cvs source, built it and run to >>>> see if it worked, up to there everything is okay. >>>> Reading the FAQ I found out that the "official" way to follow current >>>> more or less closely is to build a ramdisk image(or download a bsd.rd >>>> image from the servers) and boot from that. However, when I place my >>>> newly generated image in / and boot from it, it tells me that it lacks >>>> a root filesystem. Obviously it is lacking a ramdisk, but I don't know >>>> where to get that from and I have been unable to find the appropriate >>>> manpage or piece of documentation. Could you please point it out to >>>> me? >>>> Thank you >>>> >>>> >>>> >>>> >>> From the FAQ: >>> http://openbsd.org/faq/faq4.html#bsd.rd >>> >>> bsd.rd is used to install, upgrade or doing system maintenance. It's not >>> used to boot of your machine for normal usage. >>> >>> HTH, >>> Stijn
Dell XPS M1330 Ethernet support?
I recently acquired a Dell "opensource" laptop and am trying to install OpenBSD on it. But I am having a problem with the Ethernet. The device is detected as a Broadcom chipset and is managed by the bge driver. This is all from a i386 4.3 CD but I had the same problem with an old 4.4 snapshot. > bge0 at pci4 dev 0 function 0 "Broadcom BCM5906NP rev 0x02, > BCM5906A2(0xc002): irq 10, address ... If I ifconfig from the (s)hell I can set up everything but it complains that status: no carrier. And indeed there is no light whatsoever in the socket. The device works in Ubuntu with the Tigon3 driver, so I suspected it could need some sort of firmware, but this is not the Intel wireless and everything else is supposed to be more or less open. The laptop is listed as working(minus ACPI) as of 4.2 in /i386-laptop.html although its dmesg doesn't quite agree: "Broadcom BCM5906M" rev 0x02 at pci4 dev 0 function 0 not configured Has anyone managed to get 1330 Ethernet to work? Thank you
Re: Dell XPS M1330 Ethernet support?
Thank you for the information, but does it actually work for you? I have tested the latest AMD64 4.4 snapshot and while I can bring the device up and LEDs are blinking I get no response from my router. Should I try again with i386? Also, slightly unrelated, is it possible to break out of some unresponsive setup item(say ftp to openbsd.org without a connection) without leaving the setup altogether? Thank you 2008/10/27 Kevin Cornies <[EMAIL PROTECTED]>: > On Sat, Oct 25, 2008 at 09:20:14PM +0900, Jordi Beltran Creix wrote: >> I recently acquired a Dell "opensource" laptop and am trying to >> install OpenBSD on it. But I am having a problem with the Ethernet. >> The device is detected as a Broadcom chipset and is managed by the bge >> driver. This is all from a i386 4.3 CD but I had the same problem with >> an old 4.4 snapshot. >> > bge0 at pci4 dev 0 function 0 "Broadcom BCM5906NP rev 0x02, >> > BCM5906A2(0xc002): irq 10, address ... >> If I ifconfig from the (s)hell I can set up everything but it >> complains that status: no carrier. And indeed there is no light >> whatsoever in the socket. >> The device works in Ubuntu with the Tigon3 driver, so I suspected it >> could need some sort of firmware, but this is not the Intel wireless >> and everything else is supposed to be more or less open. The laptop is >> listed as working(minus ACPI) as of 4.2 in /i386-laptop.html although >> its dmesg doesn't quite agree: >> "Broadcom BCM5906M" rev 0x02 at pci4 dev 0 function 0 not configured >> Has anyone managed to get 1330 Ethernet to work? >> >> Thank you >> > > Works in Oct 15th -current. > > bge0 at pci4 dev 0 function 0 "Broadcom BCM5906M" rev 0x02, BCM5906 A2 > (0xc002): apic 2 int 17 (irq 10), address 00:1d:09:39:50:49 > brgphy0 at bge0 phy 1: BCM5906 10/100baseTX PHY, rev. 0
Re: bsd.mp hangs on boot
Shouldn't you *disable* acpi? 2008/11/16 Daniel Bareiro <[EMAIL PROTECTED]>: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all! > > I am trying to boot a qemu virtual machine of OpenBSD 4.4 (previous to > November release) with smp kernel on AMD Athlon 64 X2 Dual Core > Processor 3800+, but it hangs on "setting tty flags". > > I read that somebody could solve it booting with: > > boot> bsd.mp -c > > and then: > > UKC> enable acpi0 > > but this did not work for me. Somebody had this problem and could solve > it somehow? > > Thanks in advance. > > Regards, > Daniel > iEYEARECAAYFAkkgM7oACgkQZpa/GxTmHTf8PACfSZC2H/Xl+3p/dtz+1gdNF4We > OUAAnRZVMnRIQHcYipAc4eHwY7uusyqM > =p2I0 > -END PGP SIGNATURE-
Re: "remove any unwanted devices from the kernel. "
Then what is the meaning of this comment in the kernel's memcpy? A few kbs don't matter, yet a dozen bytes do? > /* > * This is designed to be small, not fast. > */ 2008/6/6, Nick Holland <[EMAIL PROTECTED]>: > Jon wrote: >>> I usually name the kernel to the machine hostname, but you can give it >>> any name. Edit the kernel config file: >>> >>> Remove any hardware related options that are not relevant to your >>> machine. >>> >> http://www.muine.org/~hoang/openpf.html#customize >> >> Why would someone want to do this? Is this nothing more than saving a >> negligible amount of memory? > > The biggest reasons to do this are because you have too much time > on your hands, and you want to impress people by having things > break, then you swoop in to rescue everyone from your fabricated > disaster. See, computers are supposed to be unreliable and > impossible to understand and take lots of effort just to keep > running and such. If they Just Work, you haven't proven anything > other than your skill at careful design and planning, People > don't appreciate that, they much prefer to see you in action. > Heroes rescue people from obvious danger, they don't avoid problems > proactively. Hey, if you gotta encourage them out onto the ledge > so you can be a hero, whatever. > > Fortunately, most computer people would rather be fighting with > existing computer systems than planning avoiding future problems > or documenting things. After all, it's not the quality of job > that counts, it's the effort people see you putting into it. > > > > Any fool can put up a website and say anything they want. Just > because you saw it on the 'net doesn't make it true. After that > crap of an introduction, I'm not going to bother reading the > rest of what this person has to say. > > See FAQ5 for the official line on this topic. > > (alternate response: a few k here, a few k there, soon you are > still talking about nothing of significance...) > > Nick.
Re: "remove any unwanted devices from the kernel. "
> That comment comes from a time when memory cost ten bucks a byte. We > don't necessarily keep all the comments up to date with the current > market prices, though, figuring anybody reading kernel comments is > moderately rational. Apparently not. Well, according to previous answers, the 25 years old comment was actually justified, but if it weren't, style(9) would come to mind. Been eating your own dog food lately? If we understand that custom kernels are unsupported, that some kernel options can be modified without recompiling, and that some changes could have security implications, why do you care? Do you have to kill a kitten each time we build a custom kernel? Two if we actually tinker with the code? Maybe you should close the source, then.
Re: kde4 dead?
2010/3/16 Marc Espie : > Of course, it makes it completely impossible to hack on KDE if you're in > the "C++ is crap, everything that matters should be written in C" mentality. > (in fact, KDE is probably the biggest example of readable C++ code I give > to people. Doesn't hurt that it follows on the steps of Qt, which is itself > awesome). > > So there. > > Even among OpenBSD porters, there are just a few of us who do grok enough C++ > to hack on kde or qt. That probably explains a lot. B The fact that it's > incredibly more efficient than that java crap won't stop newcomers from > learning java instead of C++, though. > > clang+LLVM is barely able of bootstrapping itself while already generating highly optimized code for C and Objective-C for a long time. If compiler-crafting C++ wizards have such a hard time getting it right, what chance is there for "newcomers"? I prefer C programs because they don't depend on boost, libstdc++, g++ and company. If I remember correctly, groff(and maybe something else?) is directly responsible for a big portion of time spent when you build the base system. I like C++ dependencies more than "you need autotools > x.53 but < x.53.2" dependencies, though.
47.html typo
In 47.html, in "Assorted Improvements", there is: # malloc(2) now has an S flag to turn on the options that help debugging and improve security. It links to malloc(3) correctly, though.
EM_MIPS==LOONGSON?
Hi, I was reading ELF headers from different arches when I found that for Loongson binaries em_machine==EM_MIPS. However, elf(5) and elf_abi.h->sys/exec_elf.h describe EM_MIPS as "/* MIPS R3000 Big-Endian only */", whereas I think Loongson processors are little endian(objdump says elf64-littlemips). So, do these descriptions need to be changed or is it something else?
Re: UTF-8
2010/8/4 Christopher Zimmermann : > On 07/28/10 21:45, Christian Weisgerber wrote: >> Christian Weisgerber wrote: >> >>> == xterm == >> >> What doesn't work: UTF-8 mode is incompatible with 8-bit control >> sequences. If that doesn't ring a bell for you, then you don't >> need to worry about it. ;-) >> >> I only noticed because the RMC on my AlphaServer 800 inserts 8-bit >> controls to set bold and blink attributes in its status output. > > ls(1) does not seem to be 100% UTF-8 ready: > > > madro...@madthought:~% /bin/ls testb8-C4-D5-b/-\# > testo?=o?=-C4-D5-o?=o?=-# > madro...@madthought:~% /bin/ls testb8-C4-D5-b/-\# |cat > testb8-C4-D5-b/-# > > still it is a great thing that UTF-8 is working that well now. Thanks > very much to all people that have been involved with this update!! > > > Christopher > > ls(1) needs to use wcwidth(3) instead of just assuming 1 for alignment and if I remember correctly it also mangles the strings using isprint(3) or hardcoded values instead of iswprint(3) when printing to terminal which is probably what you are seeing here. ed(1) is broken by the latter and ksh(1) for both reasons. wcwidth(3) doesn't seem to have been added yet, though.
Re: UTF-8
2010/8/5 Matthew Dempsky : > On Wed, Aug 4, 2010 at 6:22 AM, Jordi Beltran Creix > wrote: >> ls(1) needs to use wcwidth(3) instead of just assuming 1 for alignment >> and if I remember correctly it also mangles the strings using >> isprint(3) or hardcoded values instead of iswprint(3) when printing to >> terminal which is probably what you are seeing here. ed(1) is broken >> by the latter and ksh(1) for both reasons. > > Is there any useful documentation that explains how you're supposed to > write C code and what's changed under the i18n New World Order? B From > your message, it sounds like we're going to have to rewrite nearly all > of our user-space code... > Not everything, but utilities that do ls-like alignment with file names and other user provided strings, do need small modifications if they are to be made Unicode friendly. The names should still print correctly as long as they aren't mangled but anything that uses 0 or 2 char-wide glyphs will be misaligned. Reading user input interactively from terminal needs to account for glyph width as well, but that mostly happens in the libraries. String and input mangling occurs when the programs try to sanitize control characters. In the case of UTF-8, terminal control sequences over 0x80 can be a valid part of a printable character. And then there is collation which means people get angry when IJ.txt is listed after II.txt. However, many Unicode aware programs ignore it and it is optional in POSIX regexes. All programs that output raw strings, don't attempt alignment, and don't work with glyphs or code points(stuff like regexes is out but not simple matching and replacement), are safe from i18n. If you ignore its features, UTF-8 is just like ASCII and nothing has to change, no need to use Unicode functions for everything. This old FAQ is the best resource there is by far about supporting UTF-8 and locales in POSIX programs: http://www.cl.cam.ac.uk/~mgk25/unicode.html ... and then there are many other implementations of the same utilities that have been adapted to different degrees before.
