Re: cvs, cvsup and xenocara advice

[Martin Reindl]

On Thu, Nov 13, 2008 at 01:28:57AM -0800, Ansen Lloyd wrote:
> Let me first say that I looked over all the man pages, the official faqs and
> I searched over the archived mailing lists before sending out these
> questions ... and I'm still a little confused. So:
> 
> 1. What are the main differences between cvs and cvsup when updating sources
> to stable?

opencvs and gnu cvs are in base

> 2. I'm just the typical home user of obsd, so which should I use, cvs or
> cvsup?

opencvs

> 3. As of Nov 13th of 2008 why do only 4 of the 17 cvsup servers have the
> xenocara repository?
> ( according to this list: http://www.openbsd.org/cvsup.html )

for 4.4-stable:

cvs -qd [EMAIL PROTECTED]:/cvs get -rOPENBSD_4_4 xenocara

m

Re: 4.4 Release party in Vienna

[Martin Reindl]

Martin Reindl <[EMAIL PROTECTED]> wrote:

> A handful of developers are coming to Vienna after p2k8 in Budapest next week,
> so we are going to have our 4.4 party on friday, 31st november, 8pm.

oops, should say: 31st october

4.4 Release party in Vienna

[Martin Reindl]

A handful of developers are coming to Vienna after p2k8 in Budapest next week,
so we are going to have our 4.4 party on friday, 31st november, 8pm.

The event will happen in the Siebensternbraeu, Siebensterngasse 19A, 1070 Wien,
Austria (http://www.7stern.at).

Everyone is welcome to join us!

martin

Re: How much RAM is needed for cvs(1)?

[Martin Reindl]

"Karl Sjodahl - dunceor" <[EMAIL PROTECTED]> wrote:

> On Thu, Aug 28, 2008 at 7:23 AM, Tomas Bodzar <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > I tried
> >
> ># cd /usr
> ># export [EMAIL PROTECTED]:/cvs
> ># cvs -d$CVSROOT checkout -P xenocara
> >
> > and after few minutes get Out of memory.I have 256MB RAM.That was running 
> > on tty0,
> > on tty1 was only lynx with OBSD page.Before that I made checkout of src and 
> > every-
> > thing OK.
> >
> > Is this problem with low memory or anything else?
> >
> > Thx
> >
> >
> 
> This is a known limitation in cvs. If you use OpenCVS to check out
> Xenocara it succedes.
> Check http://marc.info/?l=openbsd-misc&m=120765433708331&w=2 and
> numerous other post about this on misc.

Using opencvs on the server side also helps:
[EMAIL PROTECTED]:/cvs

m

Re: 4.3 Install HP BL10eG2 Blade - panic: revarp failed, error=51

[Martin Reindl]

"Mikel Lindsaar" <[EMAIL PROTECTED]> wrote:

> I had OpenBSD 4.2 Running on these blades, installed via PXE fine.
> 
> Seems though, in running the 4.3 pxeboot and kernel, it dies on trying
> to send RARP packets out?
> 
> Anyone have some ideas on how to get this to install?
> 
> Boot sequence and then DMESG attached (with PS and TRACE) at the end.
> 

rarpd(8) needs to be running on your network.

Re: OpenBSD not booting on MacBook Pro v3.1 (Santa Rosa) (Core2Duo)

[Martin Reindl]

On Thu, Feb 14, 2008 at 11:41:16AM +0100, Maximilian-Clemens Anderer wrote:
> I want to install OpenBSD on my MacBook Pro. I used this guide to
> create a bootable CD:
> http://www.sacrideo.us/Sacrificum_Deo/Stuff_files/openbsd_macbook.txt.
> According to the document -current is required in order to get
> wireless which is my only option to connect to the internet. I did
> everything exactly as described in the guide, but substituted 'bsd.rd'
> with 'bsd.mp'. The snapshot I used for 'cdboot', 'cdbr' and 'bsd.mp'
> is from 12.02.2008.

Don't do that. Why on earth do you think bsd.mp is suitable for installing?

> 
> The CD boots fine and I am able to type at the boot> promt without the
> need of an external keyboard. The boot process then stops at the
> following dmesg line:
> .
> .
> 'root device: _'
> 

I'm not surprised.

Re: NIC is not recognized.

[Martin Reindl]

On Mon, Feb 11, 2008 at 10:40:55AM +0100, Badbanchi Hossein wrote:
> Hi,
> I am trying to install OpenBSD 4.2 on a HP Compaq dc7800. After the
> installation is complete, ifconfig doesn't show any NICs other than lo0
> and enc0.
> 
> The output of dmesg has a line:
> vendor "Intel", unknown product 0x10bd (class network subclass ethernet,
> rev 0x02) at pci0 dev 25 function 0 not configured
> 
> Any idea what should I do next?
> 

I had the same machine, it is ICH9. There should be some em(4) variant in it
which is not supported yet.

Re: src tree broken or cvs repo out of sync?

[Martin Reindl]

On Mon, Nov 26, 2007 at 04:27:36PM +0100, Didier Wiroth wrote:
> Hello,
> 
> I updated my src tree (current sources) this morning and updated it a few 
> times this afternoon but I'm not able to build the kernel anymore, is anyone 
> else experiencing this issue?
> I'm able to reproduce this on another PC where I updated the source too.
> 

Someone is slacking and did not put up a note about config(8) changes on
http://www.openbsd.org/faq/current.html. Rebuild your config(8).

Re: CVS server out of memory on anga.funkfeuer.at

[Martin Reindl]

Paulo Rodriguez <[EMAIL PROTECTED]> wrote:

> Hello misc,
> 
> Just wanted to notify of the following. During checkout of -current code for 
> Xenocara on anga, the following happens:
> 
> ...
> CVS server: updating xenocara/font/misc-misc
> U xenocara/font/misc-misc/10x20.bdf
> CVS [server aborted]: out of memory; can not allocate 2937909 bytes
> 
> If I understood correctly this is due to the datasize parameters on anga, not 
> a local client issue on my side. Command line given was nothing funky:
> 
> #cvs -d [EMAIL PROTECTED]:/cvs checkout -P xenocara
> 
> Checkout from skyrock.fr worked fine, so for me everything is ok now.
> Kind regards,
> 
> P

IIRC that's a bug in GNU cvs on 64bit architectures. I thought it was
worked around in xenocara.

Well, I will have to move the machine back to i386 again, sigh.

Re: Porting OpenBSD to OLPC XO laptops.

[Martin Reindl]

Paul de Weerd <[EMAIL PROTECTED]> wrote:

> [diverted to [EMAIL PROTECTED]
> 
> On Wed, Sep 26, 2007 at 08:08:41AM -0700, big one wrote:
> | OLPC (One Laptop Per Child) had released XO AMD Geode LX Laptops
> | using G1G1 (Buy 2 Get 1). One laptop will be sent to the buyer and the
> | 2nd laptop will be sent to a child in a poor, developing country.
> | 
> | According to Mr Theo de Raadt from OpenBSD, it is impossible to
> | write device driver for Wireless chipset inside XO.
> | 
> | According to OLPC developer team:
> | 1. There is no standard BIOS inside XO laptops.
> | 2. There is no VGA/EGA/CGA video mode.
> | 
> | Is it possible to port OpenBSD to XO Laptops without
> | activating/using the wireless chipset?
> | Thank you
> 
> Why not buy some and send them to interested developers. 
> 
> "Buy 2 Send 1 to an OpenBSD developer" ;)
> 

Last week I borrowed a pre-production B2 model from a friendly OLPC
developer. It's true the hardware is more like some embedded appliance
than 'normal' i386. Moreover, it uses Open Firmware and not a BIOS.

You can probably find this information and more on the OLPC wikis but
here are dmesg and lspci for the curious. But keep in mind this is a
pre-production model and the hardware in the production models is
beefed up.

(And no, I'm currently too much of a slacker getting it working with
OpenBSD)

00:01.0 Host bridge: National Semiconductor Corporation Geode GX2 Host Bridge 
(rev 21)
00:01.1 VGA compatible controller: National Semiconductor Corporation Geode GX2 
Graphics Processor
00:0c.0 FLASH memory: Marvell Technology Group Ltd. Unknown device 4100 (rev 10)
00:0c.1 Generic system peripheral [0805]: Marvell Technology Group Ltd. Unknown 
device 4101 (rev 10)
00:0c.2 Multimedia video controller: Marvell Technology Group Ltd. Unknown 
device 4102 (rev 10)
00:0f.0 ISA bridge: Advanced Micro Devices [AMD] CS5536 [Geode companion] ISA 
(rev 03)
00:0f.3 Multimedia audio controller: Advanced Micro Devices [AMD] CS5536 [Geode 
companion] Audio (rev 01)
00:0f.4 USB Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] 
OHC (rev 02)
00:0f.5 USB Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] 
EHC (rev 02)



[0.00] Linux version 2.6.22-20070910.30.olpc.25d22c40e3bef15 ([EMAIL 
PROTECTED]) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 PREEMPT Mon Sep 
10 03:09:19 EDT 2007
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e801:  - 0009f000 (usable)
[0.00]  BIOS-e801: 0010 - 075dd000 (usable)
[0.00] 117MB LOWMEM available.
[0.00] Entering add_active_range(0, 0, 30173) 0 entries of 256 used
[0.00] Zone PFN ranges:
[0.00]   DMA 0 -> 4096
[0.00]   Normal   4096 ->30173
[0.00] early_node_map[1] active PFN ranges
[0.00] 0:0 ->30173
[0.00] On node 0 totalpages: 30173
[0.00]   DMA zone: 32 pages used for memmap
[0.00]   DMA zone: 0 pages reserved
[0.00]   DMA zone: 4064 pages, LIFO batch:0
[0.00]   Normal zone: 203 pages used for memmap
[0.00]   Normal zone: 25874 pages, LIFO batch:7
[0.00] DMI not present or invalid.
[0.00] Allocating PCI resources starting at 1000 (gap: 
075dd000:f8a23000)
[0.00] Built 1 zonelists.  Total pages: 29938
[0.00] Kernel command line: ro root=mtd0 rootfstype=jffs2 
console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22
[0.00] Initializing CPU#0
[0.00] CPU 0 irqstacks, hard=c074a000 soft=c0749000
[0.00] PID hash table entries: 512 (order: 9, 2048 bytes)
[0.00] Detected 362.994 MHz processor.
[   13.994339] Console: colour EGA 80x25
[   13.995511] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[   13.996123] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[   14.022039] Memory: 106348k/120692k available (2325k kernel code, 13804k 
reserved, 842k data, 168k init, 0k highmem)
[   14.00] virtual kernel memory layout:
[   14.022234] fixmap  : 0xd000 - 0xf000   (   8 kB)
[   14.022251] vmalloc : 0xc800 - 0xb000   ( 895 MB)
[   14.022267] lowmem  : 0xc000 - 0xc75dd000   ( 117 MB)
[   14.022284]   .init : 0xc071a000 - 0xc0744000   ( 168 kB)
[   14.022301]   .data : 0xc06455e9 - 0xc07181b4   ( 842 kB)
[   14.022318]   .text : 0xc040 - 0xc06455e9   (2325 kB)
[   14.022777] Checking if this processor honours the WP bit even in supervisor 
mode... Ok.
[   14.174046] Calibrating delay using timer specific routine.. 727.64 BogoMIPS 
(lpj=3638233)
[   14.174543] Security Framework v1.0.0 initialized
[   14.174651] SELinux:  Initializing.
[   14.174857] SELinux:  Starting in permissive mode
[   14.174904] selinux_register_security:  Registering secondary module 
capability
[   14.175015] Capability LSM initialized as secondary
[   14.175269] Mount-cache hash table entries: 512

Re: 19 inch rack (DEC-StoageWorks) available in Munich

[Martin Reindl]

Robert Urban <[EMAIL PROTECTED]> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi Folks,
> 
> is anybody interested in a SWXSC-CB 19" StorageWorks rack? I'm giving it
> away.  For more info, see:
> 
> http://www.spielwiese.de/rob/Stuff/Cabinet/
> 

Would you mind giving the RZ28 disks to the project?
http://www.openbsd.org/want.html

sturm@ and grunk@ are probably real close :)

Re: Thank You OpenBSD

[Martin Reindl]

"Andris" <[EMAIL PROTECTED]> wrote:

> > Question: Is it true there was a developer's comment line in the Linux
> > kernel that said, "Does this belong here?"
>
> Don't know that. But I do see this:
> ftp -Vo -
http://www.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/arch/mac68k/mac68k/m
achdep.c?rev=1.142
> | grep belong
>
> Greetings.

Just means the author was not sure if the Classic II is a LC-Class
Macintosh (could be let's say from the II series as well).

Re: How do I configure Cyclades Z serial ports with OpenBSD?

[Martin Reindl]

"Don Jackson" <[EMAIL PROTECTED]> wrote:

> Hello,
> 
> I am running OpenBSD 4.1 stable.
> I installed a Cyclades Ze PCI card, and hooked it up to the external 1U box.
> 
> When my machine boots, I see:
> 
>   "Cyclades Cyclom-Z" rev 0x01 at pci1 dev 9 function 0 not configured
> 
> So the OS/driver does see the card.
> 
> How do I get from where I am to functioning /dev/ttyZ?? ports?
> 
> Thank you in advance for any advice or pointers you can give me.
> 
> Don

Have a look at the cz(4) driver, you need to comment it out in GENERIC
(preferably in -current).

Re: cvsync borked -- how to fix?

[Martin Reindl]

On Wed, Jun 06, 2007 at 11:27:24AM +0200, Martin Schr?der wrote:
> Hi,
> my cvsync mirror is broken. How can I fix this? I don't want to nuke
> the whole mirror and let it fetch it again...
> 

try the -L option in cvsync

Re: OpenBSD sucks

[Martin Reindl]

Bob Beck <[EMAIL PROTECTED]> wrote:

> * Miod Vallat <[EMAIL PROTECTED]> [2007-05-31 23:05]:
> 
> > Good! You only have to buy a boat then, since you've already got the
> > boat anchor!
> > 
> > Miod
> 
>   This from the man with an mcd(4) hooked up to an isa bus on his
> hp300  That's kinda like a guy with a pierced nipple being 
> called a freak by a guy with a pierced penis. 
> 

But only because he couldn't get interrupts from his wi(4) over the
cardbus ISA bridge. Imagine hp300 AP!

Linuxwochen Vienna 31 May to 2 June

[Martin Reindl]

hi,

We'll be running a booth at Linuxwochen Vienna at the Urania, free entrance.
Everyone is welcome to visit us!

martin

Re: IBM ServeRAID 4Lx

[Martin Reindl]

Dominik Zalewski <[EMAIL PROTECTED]> wrote:

> Dear All,
> 
> I'm going to install OpenBSD 4.1 on IBM xSeries 206. It has raid controller 
> IBM ServerRAID 4Lx. I see that ips driver is supported 
> http://www.openbsd.org/cgi-bin/man.cgi?query=ips&apropos=0&sektion=4&manpath=OpenBSD+4.1&arch=i386&format=html
>  
> 
> Anyways, does anybody had problems with it? What about bioctl?
> 

No bioctl for ips. But just give it a try.

Re: Concerning Filesystem Mini-Hackathon and faster kernel building (distcc)

[Martin Reindl]

f2k7 is not in 2 weeks but from 10th to 15th April and this still does
not help with DISKSPACE and SERVERS to plug them in.

Re: Spamassassin overwrites manual of OpenBSD spamd

[Martin Reindl]

Guido Tschakert <[EMAIL PROTECTED]> wrote:

> Hello,
> 
> while reading the discussion about spamd, I decided to learn a little
> bit about it and have a look in the manual, but man spamd yields to the
> manual of "spamd - daemonized version of spamassassin" what is not
> exactly what I was looking for. (I installed p5-Mail-SpamAssasin from
> ports/packages)
> 
> apropos spamd shows:
> spamd (8) - spam deferral daemon
> spamd-setup (8) - parse and load file of spammer addresses
> spamd.conf (5) - configuration file read by spamd-setup(8) for spamd(8)
> spamdb (8) - spamd database tool
> spamlogd (8) - spamd whitelist updating daemon
> Mail::SpamAssassin::Client (3p) - Client for spamd Protocol
> spamc (1) - client for spamd
> spamd (1) - daemonized version of spamassassin
> spamd (8) - daemonized version of spamassassin
> 
> The first and the last entry are both spamd (8), but spamassassin from
> ports has overwritten /usr/local/man/man8/spamd.8 from the system (which
> I am looking for)
> 
> I don't know if there is an easy solution for this (I don't want to call
> it a problem), but I think this shouldn't happen.
> 
> For now I go to
> http://www.openbsd.org/cgi-bin/man.cgi?query=spamd&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html
> and read the manual online :-)
> 
> thanks
> guido

The manpage of the in-system spamd lives in /usr/share/man/cat8/spamd.0

Re: pcn in VMware, 5KB/s

[Martin Reindl]

"Brad Brad" <[EMAIL PROTECTED]> wrote:

> I'm running OpenBSD 4.0 in VMware workstation 5.5.3 build-34685 linux host.
> 
> Scp's between the guest and host only manage about 5KB/s so I tried going 
> back to le which worked great.  I configured a new kernel with "disable 
> pcn*" but on next boot I had no nics at all, so i tried again "disable pci*" 
> also  since I think le is isa, but it still didn't work.
> 
> How can I get the cards to register as le again?

le at pci was removed some time ago

Re: landisk (plextor) installation question

[Martin Reindl]

Didier Wiroth <[EMAIL PROTECTED]> wrote:

> Hello,
> I got a plextor PX-EH16L yesterday, it has the required serial console
> and I now have a linux login console.
> 
> The following file
> (ftp://ftp.belnet.be/pub/packages/openbsd/snapshots/landisk/INSTALL.landisk)
> mentions this:
> Preparing your System for OpenBSD Installation:
> ---
> To be able to boot the OpenBSD/landisk installation program, you will
> need to copy a miniroot image onto the CF or harddrive that the machine
> uses.
> 
> The plextor has a samsung harddrive. I'm sorry if this sounds stupid,
> but what is the "easiest" or "fastest" way to get this miniroot image
> (miniroot40fs) on the harddrive?
> Do I have to mount the drive in other PC and install this "miniroot"
> image a special way?
> 
> I would really appreciate if someone could give me further directions.

Yes. Swap drive to another box and 'dd if=miniroot40.fs of=/dev/rwd1c'
it over. Swap back and boot.

Sadly your disk will only run in PIO 4 mode because of some DMA bug ...

martin

anoncvs2.at.openbsd down

[Martin Reindl]

The 2nd level mirror anoncvs2.at.openbsd.org aka catai.net is down for
at least one week. I'm trying to get it back into service, please check
other mirrors in the meantime.

Martin

Re: Adaptec AIC-7860/AIC-7890

[Martin Reindl]

Tom <[EMAIL PROTECTED]> wrote:

> Hi
> I'm trying to install a snapshot on a Dell PowerEdge 6300 using the
> floppyB boot disk.

it's on floppy A

Re: quad de, flakiness with 3.9

[Martin Reindl]

David Terrell <[EMAIL PROTECTED]> wrote:

> Since upgrading to 3.9 I've been having a problem with flakiness from
> my older PCI quad ethernet card.  de3 here is a dhcp interface (crappy
> SBC DSL), de2 and de1 are internal (wired and wireless).
> 
> the symptoms of failure are that de3 will stop sending packets.
> tcpdump doesn't show outgoing transmissions, dhclient complains
> "out of buffer space", and even without any active transmissions
> ifconfig shows OACTIVE in the interface flags.
> 
> (the machine is up at the moment so I don't have that ifconfig handy, 
> sorry).
> 
> One other thing I notice is that when I do ask it to do autonegotiate
> it floods the network with requests, but a hardcode to 100baseTX doesn't
> work (I don't exactly have a managed switch on the other end) and 
> 10baseT complains that there is no carrier in ifconfig status and 
> dhclient won't run.
> 
> Any ideas?  Simply bad hardware?  This was working fine with 3.8 and
> even a 3.9 snapshot from two months ago before the CDs arrived monday
> and I did the upgrade.

Give the dc(4) driver a shot instead.

Re: VIA-Chipsets and Hotplug SATA?

[Martin Reindl]

Marco Peereboom <[EMAIL PROTECTED]> wrote:

> There is no such thing as SATA hotplug.  There are hacks by hardware 
> vendors to make it sort of work but it isn't spec'd.
> 
> OpenBSD doesn't support hot plugging besides PCMCIA & USB devices.

Plus macppc mediabay(4) as of 3.9 (:

martin

Re: Cross compiling 3.8-stable on i386 for mac68k

[Martin Reindl]

David Diggles <[EMAIL PROTECTED]> wrote:

> I have a source tree for 3.8-stable, updated using cvsup.  Have
> successfully used this source tree to do a 'make build' for i386,
> however, when I attempt the first step for cross compiling for mac68k:
> ( cd /usr/src; make TARGET=mac68k cross-distrib )
> 
> It hangs at the following:
> (cd /usr/src/gnu/usr.bin/binutils;  MAKEOBJDIR=obj.i386.mac68k
> TARGET_ARCH=`cat /usr/cross/mac68k/TARGET_ARCH`  make -f
> Makefile.bsd-wrapper depend &&  MAKEOBJDIR=obj.i386.mac68k
> TARGET_ARCH=`cat /usr/cross/mac68k/TARGET_ARCH`  make -f
> Makefile.bsd-wrapper all &&  DESTDIR=/usr/cross/mac68k
> MAKEOBJDIR=obj.i386.mac68k  make -f Makefile.bsd-wrapper install)
> # Nothing here so far...
> make: don't know how to make gas/doc/as.cat1. Stop in
> /usr/src/gnu/usr.bin/binutils.
> *** Error code 2
> 
> Stop in /usr/src (line 131 of Makefile.cross).
> 
> Any suggestions on what I could edit (perhaps in
> /usr/src/gnu/usr.bin/binutils/Makefile.bsd-wrapper) to make this work?
> 
> I have moved the same source tree over to the quadra 700 machine using
> rsync, and attempted a build on there too, but it hangs during libc.
> 
> cc -O2 -pipe  -DLIBC_SCCS -DSYSLIBC_SCCS -I/usr/src/lib/libc/include
> -DAPIWARN -DYP -I/usr/src/lib/libc/yp -D__DBINTERFACE_PRIVATE
> -I/usr/src/lib/libc -DRESOLVSORT -DPOSIX_MISTAKE -DFLOATING_POINT -DNLS
>   -c -fpic -fno-function-cse -DPIC /usr/src/lib/libc/gen/times.c -o times.so
> Using $< in a non-suffix rule context is a GNUmake idiom (line 0 of (null))
> *** Error code 2
> 
> Stop in /usr/src/lib.
> *** Error code 1
> 
> Stop in /usr/src (line 72 of Makefile).
> 
> On that same machine, I had previously attempted it with a anon cvs
> obtained src tree for 3.8-stable and the same hang happens, so something
> seems to be not right.  I am well aware that in
> http://www.openbsd.org/faq/faq5.html it states "Compiling your own
> system as a way of upgrading it is not supported.", however, it is the
> most convenient way for me at this time, as for starters, it is a
> headless machine.  Ideally I would like to get cross compiling working,
> as it takes forever to native compile mac68k on the quadra, let alone
> the se/30.
> 
> Any advice to help to get this working would be greatly appreciated.
> 
> .d.d.

Forget it, even the official packages are built native. And if you
really want to cross compile, pick an architecture with similiar
toolchain, which, in case of mac68k, leaves you with other m68k archs,
sparc and vax.

In the end, it's not worth it.

martin

Re: Mac SE/30

[Martin Reindl]

David Diggles <[EMAIL PROTECTED]> wrote:

> I have a Mac SE/30 formatted with the A/UX slice partitions ready for a BSD
> install, just wondering if it's worth bothering to try OpenBSD before
> NetBSD.  Web site says it is untested/unsupported.  Anyone had any luck on
> one yet on one?
> 
> --
> paradox://belief.system

>From a technical point of view there is no reason why it should not
work if you have enough memory. The code base is more or less en par
with NetBSD, it's just that the last time OpenBSD was tested on an SE30
was probably years ago. If you want to try it out, 3.9 includes new ADB
drivers and switched to wscons, hopefully also making the SE30 happy.

Just a word of warning, it will be dead slow and without ethernet as
useful as a 'shoebox'.

Re: SCSI disk from an Alpha box, in a Sparc

[Martin Reindl]

"Larry O'Neill (H.S.A.)" <[EMAIL PROTECTED]> wrote:

> 
> Hi,
>   Thanks for your replies. I have started a dd from the disk to a
> volume mounted over nfs from an i386 box. My hope is that from there I
> will eventually be able to sort out getting the data from it. Right now I
> need to return the disk itself and the Alpha it came in back to where it
> came from.
>   Another approach I had been considering was booting the alpha from
> an openbsd install disk for Alpha (if such a thing exists - I didnt
> install the Alpha), mounting the hard drive from there, and getting the
> data from it that way... assuming the machine can actually boot from the
> cdrom. The OpenBSD CDs I have have i386, amd, sparc, etc... but not
> alpha... Is there a place I can get a CD that has complete install
> components for Alpha???

See bottom of www.openbsd.org/alpha.html.

> Larry
> 
> On Tue, 21 Mar 2006, Martin Reindl wrote:
> 
> > Joachim Schipper <[EMAIL PROTECTED]> wrote:
> >
> > > On Mon, Mar 20, 2006 at 09:31:33PM +, Larry O'Neill (H.S.A.) wrote:
> > > > Hi.
> > > > I have a disk from an Alpha server that I need to get data from... The
> > > > Alpha server no longer boots, and I dont have the time right now to
> > > > diagnose the problem. So I took the disk and lashed it into a Sun 
> > > > Ultra60,
> > > > which is also running OpenBSD. My problem is that I cant remember all of
> > > > the details of the partitioning that the disk had... So in terms of
> > > > getting access to the data, how do I find out what to put into disklabel
> > > > for it? Unfortunately due to other complications, I currently dont have
> > > > fdisk on the machine.
> > > >
> > > > (only 2 slots for Ultra2 SCSI Wide, one was root disk, other was /usr.
> > > > Copied as much stuff onto the root disk that space would alow, so that I
> > > > could remove the origional /usr disk and put in the one I need the data
> > > > from. This caused some stuff not to work because not all of it could be
> > > > copied over)
> > >
> > > As Theo pointed out, this is rather difficult (though I had no idea it
> > > was *that* difficult, honestly).
> > >
> > > A low-level disk recovery is possible, but extremely painful. I have no
> > > idea if such recovery-kits as The Corononer's Toolkit and the Sleuthkit
> > > (newer than TCT) work on Alpha disks (they do claim to work on OpenBSD),
> > > but if they do, they might be a good bet, changing low-level recovery
> > > from 'extremely painful' to something more like 'very painful'.
> > >
> > > Be aware that they are both meant to gather information from a system
> > > after it's been broken into, more than recover a complete filesystem
> > > from scratch, which is one of the reasons for the 'very painful'.
> > > Notably, they seem to deal mainly in deleted inodes, rather than
> > > allocated ones, and I am not at all certain they can even be made to
> > > work with allocated nodes.
> > >
> > > If you can get the Alpha to come up even a bit, you could write a bunch
> > > of NULLs and a large tar file directly to disk, which would be much
> > > easier to recover (the NULLs are optional, but make it easier to see
> > > where the data starts; directly means bypassing the filesystem, which
> > > might scatter stuff all over the place). However, I gather that's not an
> > > option, and if you can get the Alpha up that far you could probably just
> > > nc the whole thing.
> > >
> > > If the data is not too private, you might want to check if there is a
> > > fellow Alpha owner near - that would, by far, be the easiest solution.
> > >
> > > Of course, you can always try hacking the kernel to read Alpha disks,
> > > but that is likely to be far from trivial.
> > >
> >
> > The big task is really endianess, look at NetBSD's 'option FFS_EI'. The
> > easiest solution should be just slapping the drive into a stray i386 box.
> >
> > martin

Re: binutils port

[Martin Reindl]

"Subcommander l0r3zz" <[EMAIL PROTECTED]> wrote:

> Well, I need this too, if you are trying to compile something like L4 (to
> use OpenBSD as a development environment for embedded systems that don't use
> the OpenBSD kernel) you need a separate binutils, for example, to build
> Kenge (An L4:pistachio development environment) you need the gnu nm  and ld
> utilities which is different from the one supplied by OpenBSD. My taret
> hardware is a soekris that is not running OpenBSD, I'd like to use OpenBSD
> and not Linux as my development platform, that's all.
> 
> geoffw
> 
> 
> On 3/20/06, Ted Unangst <[EMAIL PROTECTED]> wrote:
> >
> > On 3/20/06, Niklaus <[EMAIL PROTECTED]> wrote:
> > >  1)  I was trying to install binutils2.16 from source and it didn't make
> > it
> > > 2) So how do i build binutils 2.16 from source and what is target . Why
> > > 3)I wanted to build gcc without propolice gcc-3.4.6. So what is the
> > target
> > > 6)  I saw from the CVS that binutils 2.15 , someone had added a target
> > obsd  .
> >
> > is there a reason why you want all this?  is there a problem you are
> > trying to solve?

Look at ports/devel/avr which already has cross-developments tools,
although for AVR-microcontrollers.

Re: SCSI disk from an Alpha box, in a Sparc

[Martin Reindl]

Joachim Schipper <[EMAIL PROTECTED]> wrote:

> On Mon, Mar 20, 2006 at 09:31:33PM +, Larry O'Neill (H.S.A.) wrote:
> > Hi.
> > I have a disk from an Alpha server that I need to get data from... The
> > Alpha server no longer boots, and I dont have the time right now to
> > diagnose the problem. So I took the disk and lashed it into a Sun Ultra60,
> > which is also running OpenBSD. My problem is that I cant remember all of
> > the details of the partitioning that the disk had... So in terms of
> > getting access to the data, how do I find out what to put into disklabel
> > for it? Unfortunately due to other complications, I currently dont have
> > fdisk on the machine.
> > 
> > (only 2 slots for Ultra2 SCSI Wide, one was root disk, other was /usr.
> > Copied as much stuff onto the root disk that space would alow, so that I
> > could remove the origional /usr disk and put in the one I need the data
> > from. This caused some stuff not to work because not all of it could be
> > copied over)
> 
> As Theo pointed out, this is rather difficult (though I had no idea it
> was *that* difficult, honestly).
> 
> A low-level disk recovery is possible, but extremely painful. I have no
> idea if such recovery-kits as The Corononer's Toolkit and the Sleuthkit
> (newer than TCT) work on Alpha disks (they do claim to work on OpenBSD),
> but if they do, they might be a good bet, changing low-level recovery
> from 'extremely painful' to something more like 'very painful'.
> 
> Be aware that they are both meant to gather information from a system
> after it's been broken into, more than recover a complete filesystem
> from scratch, which is one of the reasons for the 'very painful'.
> Notably, they seem to deal mainly in deleted inodes, rather than
> allocated ones, and I am not at all certain they can even be made to
> work with allocated nodes.
> 
> If you can get the Alpha to come up even a bit, you could write a bunch
> of NULLs and a large tar file directly to disk, which would be much
> easier to recover (the NULLs are optional, but make it easier to see
> where the data starts; directly means bypassing the filesystem, which
> might scatter stuff all over the place). However, I gather that's not an
> option, and if you can get the Alpha up that far you could probably just
> nc the whole thing.
> 
> If the data is not too private, you might want to check if there is a
> fellow Alpha owner near - that would, by far, be the easiest solution.
> 
> Of course, you can always try hacking the kernel to read Alpha disks,
> but that is likely to be far from trivial.
> 

The big task is really endianess, look at NetBSD's 'option FFS_EI'. The
easiest solution should be just slapping the drive into a stray i386 box.

martin

Re: HP ProLiant DL 385

[Martin Reindl]

edgarz <[EMAIL PROTECTED]> wrote:

> So SCSI/RAID is working or no? :)

All i know, the fix is in 3.9 :)

Re: HP ProLiant DL 385

[Martin Reindl]

"Andrew Ng" <[EMAIL PROTECTED]> wrote:

> According to this url ->
> http://www.armorlogic.com/openbsd_information_server_compatibility_list.html,
> SCSI/RAID does not work.

They should test again, the PR was fixed and closed.

Re: Good boot and run on ancient laptop (HP Omnibook 5000), 16MB RAM

[Martin Reindl]

Stefek Zaba <[EMAIL PROTECTED]> wrote:

> I'll be doing the 'config -e' dance to disable the unwanted 
> audio hardware... later... and no, I don't intend running X on this!

What for, your kernel will still be the same size and your laptop does
not seem to have audio(4) hardware anyway.

martin

Re: 3.9beta on macppc snapshot 30-01-06: no keyboard

[Martin Reindl]

Antoine Jacoutot <[EMAIL PROTECTED]> wrote:

> On Tue, 31 Jan 2006, Pete Vickers wrote:
> 
> > on my powerbook5,2 (G4 15"), runs through booting fine, but at the 
> > install,upgrade,shell prompt, the keyboard doesn't work ( but  still 
> > lights the LED)
> 
> Hi.
> 
> I've been experiencing the same problem too since the latest snapshot. It 
> does not happen all the time though. Usually a reboot (via ssh) and 
> everything works fine.
> 
> -- 
> Antoine

still need to see dmesg or at least if there is anything unusual in
dmesg. try to reproduce it, provide more details. try kernel from
sources before 2006/01/18 when the MI adb drivers got in.

martin

Re: APIC

[Martin Reindl]

martin <[EMAIL PROTECTED]> wrote:

> Besides doing a dmesg | grep irq, is there another way at seeing the
> assigned interrupts.  e.g. For Linux  cat /proc/interrupts  reveals:-
> 

vmstat(8)
vmstat -zi

Re: Alpha Disklabel Question

[Martin Reindl]

"Richard P. Koett" <[EMAIL PROTECTED]> wrote:

> Martin Reindl wrote:
> > "J.C. Roberts" <[EMAIL PROTECTED]> wrote:
> > 
> >> On Sat, 17 Dec 2005 18:03:21 +0100, Martin Reindl
> >> <[EMAIL PROTECTED]> wrote: 
> >> 
> >>> "J.C. Roberts" <[EMAIL PROTECTED]> wrote:
> >>> 
> >>>> On Fri, 16 Dec 2005 13:50:48 -0800, "J.C. Roberts"
> >>>> <[EMAIL PROTECTED]> wrote: 
> >>>> 
> >>>>> (2) When doing the installation disklabel, the "suggested"
> >>>>> starting offset for the 'a' partition is 0? I know using an
> >>>>> offset of 0 is discouraged on i386 and other systems (default is
> >>>>> 63), so I figured I'd ask if using a 0 offset is the
> >>>>> "best/correct" way for alpha? 
> >>>> 
> >>>> Just for those searching the misc@ archives...
> >>>> 
> >>>> I received info off-list that disklabel is doing the right thing by
> >>>> using an offset of 0 on the alpha architecture.
> >>> 
> >>> I wonder anyway how you got the impression it was doing wrong and
> >>> the offset would be 63 for the first slice. FAQ 14.1 only talks
> >>> about i386 and amd64 under 'Disklabel tricks and tips/Leave first
> >>> track free'. It's clear imo.
> >> 
> >> There's a difference between thinking disklabel is doing the wrong
> >> thing and just making sure it's doing the right thing. ;-)
> >> 
> >> The alpha PSW is a weird beast with it's "Dual BIOS" where the first
> >> AlphaBIOS/ARC is for running WinNT4 with x86 BIOS emulation support
> >> and the second, the SRM Console, is for running Tru64 and OpenVMS.
> >> 
> >> The guys I've talked to at Digital/Compaq/HP told me the multitude of
> >> alpha SRM's are very much closed source (due to the fact they control
> >> VMS licensing/revenue) and obviously, each SRM is specifically built
> >> for each machine model. On the weird machines like the PSW where
> >> multi/dual-booting NT, VMS and OSF/1 can be done, there *might* be
> >> some mad hackery in this particular SRM with a requirement for
> >> keeping the first (logical) track free for the MBR.
> >> 
> >>> From what I've read, I think the way the linux guys have hacked a
> >>> way 
> >> into supporting the use of AlphaBIOS/ARC on the PSW is by having the
> >> MBR and a small FAT partition for lilo and such. This same approach
> >> is used on the PSW when running WinNT4 with NTFS.
> >> 
> >> In a situation where you are *only* running OpenBSD, using a offset
> >> of 0 is probably just fine. On the other hand, if you happen to have
> >> WinNT installed someplace (i.e. installed on another disk), the
> >> supposedly "harmless" tag that NT writes on all disks might make a
> >> real mess of your OBSD install. 
> >> 
> >> The problem is not so much that the OpenBSD docs are unclear,
> >> instead, the problem is the setup of particular machine,
> >> particularly in muti-boot configs, can be very convoluted. I only
> >> asked because I'm just trying to *understand* what the heck I'm
> >> doing and what all the possible ramifications are. -In other words,
> >> curiosity. ;-) 
> > 
> > So they only problem now is documenting how to multiboot OpenBSD and
> > WinNT on alpha? Pardon me, but i don't expect Nick to put up a section
> > about this in the FAQ. Especially since it would involve explaining
> > AlphaBIOS fiddling which has nothing to do with OpenBSD and is a major
> > PITA anyway.
> > 
> > martin
> 
> Lighten up a bit man. There is nothing in J.C.'s post that implies he
> expects "a section about this in the FAQ".
> 
> Maybe there ought to be a section in the FAQ about how even the most
> tangential reference to it on misc is like kicking a chicken coop.

Obviously you know so much more than me. Reminds my i should go back to
hacking and quit this short digression to [EMAIL PROTECTED]

Re: Alpha Disklabel Question

[Martin Reindl]

"J.C. Roberts" <[EMAIL PROTECTED]> wrote:

> On Sat, 17 Dec 2005 18:03:21 +0100, Martin Reindl <[EMAIL PROTECTED]>
> wrote:
> 
> >"J.C. Roberts" <[EMAIL PROTECTED]> wrote:
> >
> >> On Fri, 16 Dec 2005 13:50:48 -0800, "J.C. Roberts" <[EMAIL PROTECTED]>
> >> wrote:
> >> 
> >> >(2) When doing the installation disklabel, the "suggested" starting
> >> >offset for the 'a' partition is 0? I know using an offset of 0 is
> >> >discouraged on i386 and other systems (default is 63), so I figured I'd
> >> >ask if using a 0 offset is the "best/correct" way for alpha?
> >> 
> >> Just for those searching the misc@ archives...
> >> 
> >> I received info off-list that disklabel is doing the right thing by
> >> using an offset of 0 on the alpha architecture.
> >
> >I wonder anyway how you got the impression it was doing wrong and the
> >offset would be 63 for the first slice. FAQ 14.1 only talks about i386
> >and amd64 under 'Disklabel tricks and tips/Leave first track free'.
> >It's clear imo.
> 
> There's a difference between thinking disklabel is doing the wrong thing
> and just making sure it's doing the right thing. ;-)
> 
> The alpha PSW is a weird beast with it's "Dual BIOS" where the first
> AlphaBIOS/ARC is for running WinNT4 with x86 BIOS emulation support and
> the second, the SRM Console, is for running Tru64 and OpenVMS.
> 
> The guys I've talked to at Digital/Compaq/HP told me the multitude of
> alpha SRM's are very much closed source (due to the fact they control
> VMS licensing/revenue) and obviously, each SRM is specifically built for
> each machine model. On the weird machines like the PSW where
> multi/dual-booting NT, VMS and OSF/1 can be done, there *might* be some
> mad hackery in this particular SRM with a requirement for keeping the
> first (logical) track free for the MBR.
> 
> >From what I've read, I think the way the linux guys have hacked a way
> into supporting the use of AlphaBIOS/ARC on the PSW is by having the MBR
> and a small FAT partition for lilo and such. This same approach is used
> on the PSW when running WinNT4 with NTFS.
> 
> In a situation where you are *only* running OpenBSD, using a offset of 0
> is probably just fine. On the other hand, if you happen to have WinNT
> installed someplace (i.e. installed on another disk), the supposedly
> "harmless" tag that NT writes on all disks might make a real mess of
> your OBSD install.
> 
> The problem is not so much that the OpenBSD docs are unclear, instead,
> the problem is the setup of particular machine, particularly in
> muti-boot configs, can be very convoluted. I only asked because I'm just
> trying to *understand* what the heck I'm doing and what all the possible
> ramifications are. -In other words, curiosity. ;-)

So they only problem now is documenting how to multiboot OpenBSD and
WinNT on alpha? Pardon me, but i don't expect Nick to put up a section
about this in the FAQ. Especially since it would involve explaining
AlphaBIOS fiddling which has nothing to do with OpenBSD and is a major
PITA anyway.

martin

Re: Alpha Disklabel Question

[Martin Reindl]

"J.C. Roberts" <[EMAIL PROTECTED]> wrote:

> On Fri, 16 Dec 2005 13:50:48 -0800, "J.C. Roberts" <[EMAIL PROTECTED]>
> wrote:
> 
> >(2) When doing the installation disklabel, the "suggested" starting
> >offset for the 'a' partition is 0? I know using an offset of 0 is
> >discouraged on i386 and other systems (default is 63), so I figured I'd
> >ask if using a 0 offset is the "best/correct" way for alpha?
> 
> Just for those searching the misc@ archives...
> 
> I received info off-list that disklabel is doing the right thing by
> using an offset of 0 on the alpha architecture.

I wonder anyway how you got the impression it was doing wrong and the
offset would be 63 for the first slice. FAQ 14.1 only talks about i386
and amd64 under 'Disklabel tricks and tips/Leave first track free'.
It's clear imo.

Re: Alpha Disklabel Question

[Martin Reindl]

"J.C. Roberts" <[EMAIL PROTECTED]> wrote:

> On Fri, 16 Dec 2005 23:36:34 +0100 (CET), Tamas TEVESZ <[EMAIL PROTECTED]>
> wrote:
> 
> >On Fri, 16 Dec 2005, J.C. Roberts wrote:
> >
> > > (1) When booting  the cd38.iso with either bsd or bsd.rd you go into UKC
> > > rather than directly into the installation. I'm guessing this is normal
> > > since I'm sure there might be some things that need doing for some of
> > > the more esoteric alpha hardware but it's worth asking to make sure.
> >
> >you probably have a rogue `-s' in boot_osflags (try `show boot_osflags'
> >or even `show boot*' in srm).
> 
> Without an OS installed and booting from CD through the SRM the
> INSTALL.alpha file suggests/requires overriding the both the SRM boot
> file (-fi switch) and the SRM boot flags (-fl switch):
> 
>  >>>boot -fi bsd -fl ac dka0
> 
> Frightening... I added the "c" to the boot flags as instructed and
> didn't even notice it.
> 
> Eventually, the boot_osflags in the SRM needs to be set to "a" but the
> default is "A" -The case would make no difference for some OS's but
> OpenBSD probably won't like it. ;-)

SRM specification requires us to handle the flags equally, regardless
of case.

Re: 3.8 userland build fails on amd64 and sparc64

[Martin Reindl]

Dag Richards <[EMAIL PROTECTED]> wrote:

> After extracting sources from the cd,  checking out current, building 
> installing and booting from the new kernel, make build fails.
> 
> 
> The error message indicates that xargs is being called with an 
> unsupported argument, "-r" as I recall.  If I then just build and 
> install xargs the make build completes.
> 
> This has happened now on both a sparc64 and an amd64 machine.

Read http://www.openbsd.org/faq/current.html, doh.

Re: Drives connected to pcscp0 disappeared.

[Martin Reindl]

Matthias Kilian <[EMAIL PROTECTED]> wrote:

> On Sat, Nov 19, 2005 at 12:02:47AM +0100, Martin Reindl wrote:
> > Cannot reproduce here on amd64, need more details.
> [...]
> > OpenBSD 3.8-current (GENERIC) #4: Fri Nov 18 23:39:43 CET 2005
> > [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC
> [...]
> > associative, 8 4MB entries fully associative [...] pcscp0 at pci0 dev
> > 12 function 0 "AMD 53c974 PCscsi-PCI" rev 0x10: irq 11 pcscp0:
> > AM53C974, 40MHz, SCSI ID 7 scsibus1 at pcscp0: 8 targets
> > cd1 at scsibus1 targ 2 lun 0:  SCSI2
> 
> That's odd.
> 
> I've tried some kernels from my backups, and it seems that the
> problem occured somewhere between nov. 12th and nov. 15th (see
> below).
> 
> What additional details could help? I could boot with verbose
> autoconfig, but I have to do it via serial console, since the output
> is too large for the dmesg buffer.

No changes happened to pcscp in this timeframe. Try with CVS sources in
src/sys/scsi from 12th and then from 15th (or in between as necessary).

martin

Re: Drives connected to pcscp0 disappeared.

[Martin Reindl]

Matthias Kilian <[EMAIL PROTECTED]> wrote:

> Hi,
> 
> I just noticed that the cd and dvd drives connected to my Tekram
> DC-390 host adapter aren't detected since a few days.
> 
> What follows are the dmesg of my current system and a diff against a
> dmesg some months ago. Please note that
> 
> a) in my current system, Ottos patch to sys/sys/queue.h is applied,
> b) I roughly remember to used one of the drives a week ago.
> 
> If this is neither a PEBKAC nor a known issue, I'll have a look at my
> recent backups and search for the very last time the drives have been
> detected.

Cannot reproduce here on amd64, need more details.

Martin

OpenBSD 3.8-current (GENERIC) #4: Fri Nov 18 23:39:43 CET 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 536145920 (523580K)
avail mem = 448176128 (437672K)
using 13140 buffers containing 53821440 bytes (52560K) of memory
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: AMD Athlon(tm) 64 Processor 3000+, 1995.85 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,NXE,MMXX,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 [...] pcscp0 at pci0 dev
12 function 0 "AMD 53c974 PCscsi-PCI" rev 0x10: irq 11 pcscp0:
AM53C974, 40MHz, SCSI ID 7 scsibus1 at pcscp0: 8 targets
cd1 at scsibus1 targ 2 lun 0:  SCSI2
5/cdrom removable sd0 at scsibus1 targ 6 lun 0:  SCSI2 0/direct fixed sd0: 4095MB, 5172 cyl, 10 head, 162 sec, 512 
bytes/sec, 8388314 sec total
[...]

Re: Macppc G3 Powerbook - Install Fails

[Martin Reindl]

On Tue, Nov 15, 2005 at 08:49:30PM -0500, Roy Morris wrote:
> Martin Reindl wrote:
> 
> >On Tue, Nov 15, 2005 at 08:26:03PM -0500, Roy Morris wrote:
> > 
> >
> >>I have a buddy over who wants to put OpenBSD 3.8 on his macppc G3 
> >>powerbook (bronze keyboard) we burn tested the boot cd on a G4 Powerbook 
> >>and it does boot fine. When booting on the G3 none of the normal 
> >>installation methods work, it just seems to go right
> >>by the cd and boot into the mac os. Any ideas what we might be doing 
> >>wrong?
> >>   
> >>
> >
> >How should the hardware know that it should boot from CD? Press 'C' or
> >switch-appel-o-f to get into OF and boot from there as described in the 
> >docs.
> >
> >
> > 
> >
> Thanks we have tried all the examples in the docs. We get to the
> ofw prompt and have tried
> 
> boot cd:,ofwboot /3.8/macppc/bsd.rd
> and putting the two files on the hard drive and booting
> using
> boot hd:,ofwboot bsd.rd
> 
> no go on any of them.

Errors?

Check http://marc.theaimsgroup.com/?l=openbsd-ppc&m=113106400907764&w=2.

Re: Macppc G3 Powerbook - Install Fails

[Martin Reindl]

On Tue, Nov 15, 2005 at 08:26:03PM -0500, Roy Morris wrote:
> I have a buddy over who wants to put OpenBSD 3.8 on his macppc G3 
> powerbook (bronze keyboard) we burn tested the boot cd on a G4 Powerbook 
> and it does boot fine. When booting on the G3 none of the normal 
> installation methods work, it just seems to go right
> by the cd and boot into the mac os. Any ideas what we might be doing wrong?

How should the hardware know that it should boot from CD? Press 'C' or
switch-appel-o-f to get into OF and boot from there as described in the docs.

Re: OpenBSD official media

[Martin Reindl]

Martin Schrvder <[EMAIL PROTECTED]> wrote:

> On 2005-11-08 22:19:55 -0800, J.C. Roberts wrote:
> > On Tue, 8 Nov 2005 12:48:30 +0100, Martin Schrvder <[EMAIL PROTECTED]> 
> > wrote:
> > >Excuse me, but how many vaxen where shipped with CD-ROMs?
> > 
> > I've got eight 4000-90's here and none of them have factory CD-ROM
> > drives but then again, the drives could be added. CD-ROM drives were an
> > option but I can't remember ever actually seeing a vax factory equipped
> > with one.
> 
> This is getting OT, but just for interest: can vaxen handle
> SCSI-DVD-ROM drives without problems?

Why shouldn't they. Attachment is via cd(4), as usual.

Martin

Re: audio input on 3.7 GENERIC#453 sparc64

[Martin Reindl]

"Larry O'Neill (H.S.A.)" <[EMAIL PROTECTED]> wrote:

> Hi,
>   I'm haveing some trouble with trying to get audio input to work on
> my Ultra60 machine. Audio playback is working no problem, but when I try
> to take any input from /dev/audio:
> 
> mymachine$ dd if=/dev/audio of=recorded.raw
> dd: /dev/audio: Device not configured
> 0+0 records in
> 0+0 records out
> 0 bytes transferred in 0.002 secs (0 bytes/sec)
> 
>   Also, what reutrns form audioctl:
> 
> mymachine$ audioctl -a | head
> name=SUNW,CS4231
> version=b
> config=onboard1
> encodings=mulaw:8,alaw:8,slinear_le:16,ulinear:8,slinear_be:16,slinear:8*,uli
> near_le:16*,ulinear_be:16*,adpcm:8 properties=full_duplex
> full_duplex=0
> fullduplex=0
> blocksize=400
> hiwat=163
> lowat=1
> 
> 
> which suggests an audiocs interface, but my dmesg tells me that it's not
> audiocs, but audioce:
> 
> mymachine$ dmesg | grep audio
> audioce0 at ebus0 addr 20-2000ff, 702000-70200f, 704000-70400f,
> 722000-722003 ipl 35 ipl 36: nvaddrs 0
> audio0 at audioce0
> 
> I have been playing about with all of the parameters in mixerctl and
> audioctl, but it doesnt seem to be making any difference, or it complains.
> mixerctl only complains when I try to edit any of the record parameters:
> 
> mymachine$ mixerctl -av
> inputs.dac=8,8 volume
> inputs.dac.mute=off  [ on off ]
> inputs.line=8,8 volume
> inputs.line.mute=off  [ on off ]
> inputs.mic=0 volume
> inputs.mic.mute=on  [ on off ]
> inputs.cd=8,8 volume
> inputs.cd.mute=on  [ on off ]
> monitor.monitor=7 volume
> outputs.monitor.mute=on  [ on off ]
> outputs.output=200,200 volume
> outputs.output.mute=on  [ on off ]
> record.record=0,0 volume
> record.record.source=mic  [ cd mic dac ]
> monitor.output=headphones  [ speaker line headphones ]
> mymachine$ mixerctl monitor.monitor=8
> monitor.monitor: 7 -> 8
> mymachine$ mixerctl record.record.source=dac
> mixerctl: AUDIO_MIXER_WRITE: Invalid argument
> mymachine$
> 
> whereas for anything I try to change in audioctl, I get:
> 
> audioctl: set failed: Invalid argument
> 
> 
> I find it very strange that the audio output is ok, but the input not
> 
> 
> any suggestions?
> thanks
> Larry

audioce(4) is the ebus attached variant of the sbus attached audiocs(4).
As the manpage says, recording is currently not supported in audioce(4).

Martin

Re: OpenBSD i386 and macppc on one HDD

[Martin Reindl]

On Mon, Oct 10, 2005 at 07:00:55AM -0400, Nick Holland wrote:
> Constantine A. Murenin wrote:
> > Hello,
> > 
> > I have an external USB 2.0 storage device with OpenBSD i386
> > installation and some free space. Is it possible to install
> > OpenBSD/macppc on that spare space without breaking my i386
> > installation?
> 
> ew, ick.
> 
> > How will it all work? Would it be possible to share /etc, 
> 
> Since /etc is on the root partition, NO.
> Since /etc holds configuration and your macppc and i386 machines will
> have different configurations, NO.
> 
> > /var and
> > /home partitions between i386 and macppc? Could the HDD be bootable on
> > both i386 and macppc?
> 
> My inital response is "no", you couldn't share a disk like this.
> My secondary response is "maybe", I've got some ideas how it *might* be
> done, but I can think of ONLY one reason to do this: learning the boot
> process on both platforms very intimately.  And that is a lesson best
> taught to one's self.
> 
> If you are trying to save money, go get a job slinging burgers, take
> your income and buy a new disk.  You will invest less time doing that
> than you will fighting this battle.  It is just not worth it.
> 
> BTW: If you try this, count on that "some free space" turning into "all
> free space" a few times, usually accidently, though probably at least
> once deliberately.

Even more, as macppc is big-endian and i386 is little endian you will have
trouble with FFS ...

Re: alpha panic; cpu_initclocks: no clock attached

[Martin Reindl]

On Thu, Sep 15, 2005 at 02:54:44AM +0200, Tamas TEVESZ wrote:
> On Thu, 15 Sep 2005, Martin Reindl wrote:
> 
>  > > i ultimately wanted to try martin reindl's alpha patch on my pws500au
>  > > (even if i wouldn't have scored extra anyway), when i realized my
>  > > alpha was hosed, so i grabbed the sept 10 snapshot, installed it fine,
>  > > cvs'd src/, compiled a generic kernel, and upon reboot:
>  >
>  > I just don't recall what patch this might have could been,
> 
> Date: Wed, 14 Sep 2005 13:47:13 +0200
> To: [EMAIL PROTECTED]
> Subject: Alpha testers needed
> 
> ^- this one (didn't get to the part of even thinking about trying to,
> tho).
> 
>  > but you disabled ISA. The clock attaches to ISA. Don't disable ISA.
> 
> you mean as in `editing arch/alpha/conf/GENERIC'? no i didn't. swear
> to god. not even with config(8). or anything that can do this and i'm
> aware of. i went like:
> 
> netboot bsd.rd as per install.alpha, install it, cvs co src, cd
> /usr/src/sys/alpha/conf, config GENERIC, cd ../compile/GENERIC, make
> clean depend bsd, mv bsd /bsd && chmod 0644 /bsd && chown root:wheel
> /bsd && reboot. this is exactly what resulted in no clocks.
> 
> and i didn't disable it in srm either (if that is possible at all,
> which i do not know, but would nevertheless be quite surprised).
> 
> according to config,
> 
> ukc> find isa
> 111 isa* at pceb*|sio* flags 0x0
> ukc>
> 
> i have followed -current with this box up until maybe one and a half
> weeks ago semi-regularly, never had any problems, except for the
> phenomenon which matthieu described as `the alpha bug' and is known,
> but never anything like that.
> 
> now i'm getting confused...

>From your diff:

-isa0 at sio0
-isadma0 at isa0

Hello? Dunno what you booted but it was not GENERIC.

Re: alpha panic; cpu_initclocks: no clock attached

[Martin Reindl]

On Thu, Sep 15, 2005 at 02:15:58AM +0200, Tamas TEVESZ wrote:
> hi,
> 
> i ultimately wanted to try martin reindl's alpha patch on my pws500au
> (even if i wouldn't have scored extra anyway), when i realized my
> alpha was hosed, so i grabbed the sept 10 snapshot, installed it fine,
> cvs'd src/, compiled a generic kernel, and upon reboot:

I just don't recall what patch this might have could been, but you disabled
ISA. The clock attaches to ISA. Don't disable ISA.

martin

Re: OpenBSD 3.8-beta Alpha panic with pppoe SOS!

[Martin Reindl]

"Roger Neth Jr" <[EMAIL PROTECTED]> wrote:

> Hello List,
> I reinstalled 3.8-beta on the alpha with just the required sets and the 
> hostname.pppoe0 and ppp.conf files with the amap_wipeout panic still 
> occuring.
> 
> I tried UKC> disable amap and pkg_delete -F amap-5.1.tgz and amap-4.5.tgz 
> without any success.
> 
> Any ideas on solving this is much appreciated.

This is an UVM panic, something is messing with kernel memory. Is the machine
stable without pppoe?

> 
> Thank you,
> 
> rogern
> 
> John 3:16
> 
> 
> >From: Roger D Neth Jr <[EMAIL PROTECTED]>
> >To: misc@openbsd.org, [EMAIL PROTECTED]
> >Subject: OpenBSD 3.8-beta Alpha panic with pppoe
> >Date: Mon, 05 Sep 2005 11:58:49 -0700
> >
> >Hello List,
> >I am unable to get pppoe to work with an alpha that I want to use as a 
> >firewall. It panics
> >
> >amap_wipeout: corrupt amap
> >
> >when I connect the ADSL Speedstream modem to any of the three nic's.
> >
> >I have used the same hostname.pppoe0 and ppp.conf files with the same modem 
> >and a secondary nic on an i386 successfully.
> >
> >My assumption is this is hardware related to the alpha and not OpenBSD.
> >
> >Would anyone be able to check this out and verify this or let me know how I 
> >can correct this error.  Would ukc > disable amap  work?
> >
> >I Googled this and did not find any information on this.
> >
> >Thank you,
> >
> >rogern
> >
> >John 3:16
> >
> >
> >
> >ppp.conf
> >
> > pppoedev de1
> > !/sbin/ifconfig de1 up
> >!/usr/sbin/spppcontrol \$if myauthproto=pap myauthname=xx \
> > myauthkey=xx
> > !/sbin/ifconfig \$if inet 0.0.0.0 0.0.0.1 netmask 0x
> > !/sbin/route add default 0.0.0.1
> > up
> >
> > default:
> > set log Phase Chat LCP IPCP CCP tun command
> > set redial 15 0
> > set reconnect 15 0
> >
> > pppoe:
> > set device "!/usr/sbin/pppoe -i de1"
> > disable acfcomp protocomp
> > deny acfcomp
> > set mtu max 1492
> > set speed sync
> > enable lqr
> > set lqrperiod 5
> > set cd 5
> > set dial
> > set login
> > set timeout 0
> > set authname xx
> 
> 
> _
> FREE pop-up blocking with the new MSN Toolbar  get it now! 
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

Re: dmesg/bios question

[Martin Reindl]

Dave Feustel <[EMAIL PROTECTED]> wrote:

> My computer just locked up and I rebooted.
> When I did so the reboot hung right after the line below starting with bios0.
> I powered down, then up, then booted again, this time successfully.
> But I noticed that the bios id seems to be for a 286. I never noticed that
> before. Unfortunately, I don't have any old copies of dmesg to compare.
> I'm running on a Dell 4100. Does the bios id seem correct?

bios(4) says it all

Re: ath(4) support on sparc64

[Martin Reindl]

Edwin Steele <[EMAIL PROTECTED]> wrote:

> Hi,
>I'm wanting to put a 802.11b/g card in my ultra5. I'm having a lot
> of trouble finding a supported card here in Australia so I'm looking
> at chipsets that are supported on i386 and not sparc64.
> 
> Is it just a lack of testing of ath(4) on sparc64 that has prevented
> it from being in GENERIC or are there some platform specific issues
> that would prevent it from running?
> 
> I'm happy to grab a card (probably an ath(4) based DWL-G520) and see
> if I can't make it work but wanted to check first and see what the
> situation is.

There were some efforts at c2k5 getting ath(4) on macppc. Didn't happen
much since then to get alignment and whatnot working on other
architectures. So, yes, just go ahead and make it work.

Re: Linksys EG1032 not SysKonnect anymore as of rev. 3

[Martin Reindl]

Johan P. Lindstrvm <[EMAIL PROTECTED]> wrote:

> It is with great sorrow I must report that the Linksys EG1032 cards as
> of revision 3 no longer features the SySKonnect (sk) chips.
>  I bought 2 of them, they turned out to be revision 2 (SySKonnect), as
>  per
> the hardware section on www.openbsd.org 
> (should probably be updated, im too green to submit a diff, sorry)
>  Now I bought 10 more, and imagine my face when i saw the stupid crab
>  on the
> chip, for those who know these things, it also says:
>  RLT8169S-32

Probably supported by re(4), send a dmesg.

Martin

Re: Alpha - floppy as root device ?

[Martin Reindl]

Steve Murdoch <[EMAIL PROTECTED]> wrote:

> Hi all,
> 
> Can someone throw me in the right direction.
> 
> I have an Alphaserver 1000.
> 
> The SCSI drives have failed so I have installed a PCI IDE contoller
> and  IDE drive.
> 
> The SRM doesnt recognise the IDE so after install I wont be able to
> boot  from the drive.
> 
> Is thee a way to have the floppy as the root device ?

Nope, better get yourself some SCSI drive. Or put root on NFS, but that
can be a pain on alpha.

Martin