Nick Holland | 1 Aug 04:14 2004
Picon

Re: kern.version

D. E. Evans wrote:
> In response to Matthias, /bsd on wd1a is the release (8 May
> build) kernel.  So how is it that wd1a's /bsd is being loaded
> instead of from wd0a? 
> 
> The solution would seem to lie both in fixing the boot block so
> that it is loading off of wd0a, and fixing the RAID configuration
> so it's actually mirroring (which obviously it doesn't seem to be
> doing).  Or am I still not getting it?

No.  You are still not getting it.
You are trying to get fancy when you don't understand the basics of what 
is happening.

Look at ALL that Dan has said to you, 'specially his comments about your
so-called RAID controller.  He obviously understands the boot process
well, and he spotted your problem before me 8-).

   http://www.openbsd.org/faq/faq14.html#RAID
     (see what is explicitly named in "Non-options")
   http://www.openbsd.org/faq/faq14.html#Boot386

Your system is set up wrong.
Somehow, you got the GENERIC kernel on your second drive.  I don't care
how, but one example would be you installed your system, you then 
mirrored your existing disk using the BIOS in the (non)RAID controller, 
then booted OpenBSD, which promptly ignored the "mirror".

Your [insert rude, obnoxious, and not repeatable in polite company
words here] RAID controler has a BIOS that thinks it can boot from
(Continue reading)

D. E. Evans | 1 Aug 05:34 2004
Picon

Re: kern.version

Nick wrote:
   Somehow, you got the GENERIC kernel on your second drive.  I
   don't care how, but one example would be you installed your
   system, you then mirrored your existing disk using the BIOS in
   the (non)RAID controller, then booted OpenBSD, which promptly
   ignored the "mirror".

   Your [insert rude, obnoxious, and not repeatable in polite
   company words here] RAID controler has a BIOS that thinks it
   can boot from whatever it darned well feels like, and does so
   (in its defense, it probably thinks your mirrored pair is
   corrupt (heh, it us right, actually, and the drive that was
   "corrupted" WAS the wd0 drive, as it was written to "away"
   from the mirror), and thinks the second drive is more likely
   the "intact" one). OpenBSD then picks a drive as wd0, which
   obviously isn't what the BIOS considered hd0, loading the
   wrong kernel.

   Remember: until the machine boots, there is no wd0, that's an
   OpenBSD concept.  The kernel is loaded by the BIOS, which can
   do whatever it wants.

This seems a precise description.  It tooks Dan's verbal 2x4 to
realize this, and your note to confirm it.

So is it worth learning the ins and outs of RAIDframe to make the
RAID controller work, or is there a way I can get the promise
controller to act like a regular EIDE drive?  (A software
controlled RAID controller seems to defeat the whole point:
RAID minus the controller.)
(Continue reading)

Curtis H. Wilbar Jr. | 1 Aug 06:05 2004
Picon

Re: i386 and sparc64 disks

On Sat, 2004-07-31 at 14:18, scott wrote:
> hi
> 
> my trusty Sun Ultra 10 running OBSD 3.4 died on me last week, and in the 
> short term I have had to setup an Intel based box in it's place
> 
> I've installed OBSD 3.5 onto the i386 system (have misplacd my 3.4 
> CD's), and then cabled the EIDE drive from the Sun system in as a slave 
> drive
> 
> I've had a little read and tried a few things like fdisk wd1 and 
> disklabel wd1, but the information it comes back with does not look too 
> good (output below), it's finding MacOS volumes (the whole disk was 
> allocated to OpenBSD under the Sun box)
> 
> am I likely to be able to mount the ex Sparc64 drive in order to pull 
> data across to the new drive, or do they use disk layout in a slightly 
> different manner ?

Byte ordering on Sun and x86 are different.  I would say this is why
it doesn't see your data.

You'll need to mount the disk another big-ending system to get at
your data.

-- Curt

> 
> any suggestions appreciated
> 
(Continue reading)

anakha | 1 Aug 06:33 2004
Picon

Re: Canadian French encoding

---------------------------- Original Message ----------------------------
Subject: Re: Canadian French encoding
From:    "Mathieu Sauve-Frankel" <msf <at> kisoku.net>
Date:    Fri, July 30, 2004 7:43 am
To:      anakha <at> clubinfo.bdeb.qc.ca
--------------------------------------------------------------------------

On Thu, Jul 29, 2004 at 10:14:26PM -0400, anakha <at> age.bdeb.qc.ca wrote:
> I have been looking for some time after a Canadian French keyboard
encoding.
>
> Alternatively, as I didn't find one I tried to mak one myself and got
confused bu the wscons code (specifically where does kbc builds its
traduction tables).
>
> If you have pointers for any of these concerns, your help is appreciated.
>
> -anakha

bonjour

/usr/src/sys/dev/pckbc/wskbdmap_mfii.c

--

-- 
Mathieu Sauve-Frankel
msf <at> kisoku.net || msf <at> openbsd.org

Ok so now I'm ready to do the encoding but I would like to know if anybody
knows of a better way to determine keycodes sent by the keyboard than to
look at what is defined for what for my current encoding.  I have most of
(Continue reading)

D. E. Evans | 1 Aug 07:59 2004
Picon

span

I seem to have been cursed with a Promise onboard 'RAID'
controller (PDC20267).  Would setting each drive (I have two) in
the Promise BIOS to its own spanned array (1 disk per array) turn
the controller essentially into an EIDE controller, allowing me
to mount the second drive as /home?  Does anyone have any
other suggestions?

--

-- 
D. E. Evans <sinuhe <at> xmission.com>
<http://www.deevans.net>

Marc Balmer | 1 Aug 11:39 2004
Picon

Chicken and egg problem after flag day

Hi All

I seem to have a chicken and egg problem here:

I updated my system to -current as of yesterday.  Now I am rebuilding 
X11, which requires Tk.  Tk, however, requires X11 which is not yet 
installed (if I install the port it compiles fine, but it still uses the 
old (pre-flagday) X11 libs an the Wish shell core dumps when startet).

Any hints?

Regards and thanks,
Marc

Matthieu Herrb | 1 Aug 13:06 2004
Picon
Picon

Re: Chicken and egg problem after flag day

Marc Balmer wrote:

> Hi All
> 
> I seem to have a chicken and egg problem here:
> 
> I updated my system to -current as of yesterday.  Now I am rebuilding 
> X11, which requires Tk.  Tk, however, requires X11 which is not yet 
> installed (if I install the port it compiles fine, but it still uses the 
> old (pre-flagday) X11 libs an the Wish shell core dumps when startet).
> 
> Any hints?

As we've advertised here soo many times, use binary snapshots.

Or build X manually in steps. The lazy hack is to just start the build, 
let it fail on xc-old/XF86Setup becuase of the tk dependency, cd 
XF4/xc/lib ; sudo make install. Then build and install tk and restart 
the X build.

--

-- 
					Matthieu

adrian kok | 1 Aug 13:29 2004
Picon

bandwidth software

Hi all

Do you know bandwidth software supports 1000M
ethernet?

Thank you very much

Jochen Eisinger | 1 Aug 15:09 2004

Re: HiFn 7955 makes OpenSSH fail

Hi,

in hifn_crypto() and hifn_compress_enter() there's a block like this:

/*
* We don't worry about missing an interrupt (which a "command wait"
* interrupt salvages us from), unless there is more than one command
* in the queue.
*/
if (dma->cmdu > 1) {
        sc->sc_dmaier |= HIFN_DMAIER_C_WAIT;
        WRITE_REG_1(sc, HIFN_1_DMA_IER, sc->sc_dmaier);
}

well, I thought mabye we should worry and removed the if() { .. } around
this block.

With this patched driver I cannot reproduce the problem (SSH failing)
anymore. Also there are no noticable changes in performance (using
openssl speed)

however, I'm no expert here, this is just the result of poking randomly
at the code :)

any comments on this?

kind regards
-- jochen

(Continue reading)

Marco Peereboom | 1 Aug 15:42 2004
Picon

Re: span

Yes, or as a RAID 0 per drive.

It still will use the same driver though so I am unsure if it'll have 
the results you are hoping for.  Can't you simply disable the RAID part 
in the BIOS?

On Aug 1, 2004, at 12:59 AM, D. E. Evans wrote:

> I seem to have been cursed with a Promise onboard 'RAID'
> controller (PDC20267).  Would setting each drive (I have two) in
> the Promise BIOS to its own spanned array (1 disk per array) turn
> the controller essentially into an EIDE controller, allowing me
> to mount the second drive as /home?  Does anyone have any
> other suggestions?
>
> -- 
> D. E. Evans <sinuhe <at> xmission.com>
> <http://www.deevans.net>


Gmane