login error after 3.1 upgrade

Upgraded my Q840 from 2.1 to 3.1.  Unpacked kernel,
rebooted, unpacked 
base, comp, man, text, and xcomp, rebooted.  Now I cannot
login.  I get 
this after entering a username:

schroeder login: in openpam_configure(): No required or
binding 
component in service login, facility auth
login: pam_start failed
schroeder login: pam_start failed: system error

Any ideas?

Thanks,
Tim
-- 
Tim & Alethea
christtrek.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Nov 18, 2006, at 22:20, Tim & Alethea Larson wrote:

> Upgraded my Q840 from 2.1 to 3.1.  Unpacked kernel,
rebooted, unpacked 
> base, comp, man, text, and xcomp, rebooted.  Now I
cannot login.  I 
> get this after entering a username:
>
> schroeder login: in openpam_configure(): No required or
binding 
> component in service login, facility auth
> login: pam_start failed
> schroeder login: pam_start failed: system error
>
> Any ideas?

Save your config files and upgrade /etc as well, then PAM
should work.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRV/QOspnzkX8Yg2nAQJncgf+LLSFrc/BQm7FOihedOS6dA9+zZZ/
CX1M
aonj8wUccmNjc/pRh7nH7Mg/VlVeHyhvSvVwwTHiOADZ3yutlknucASKNN/u
vYY7
NBUh/IDbwKY7880s278o624k0OVzciOtubv2kjb/oI0a3cokVWbS4EOhYO8a
ciXt
7nInNARumu1ahJlNwg8CrhSjWpiFnaUIAj0Pix32zOcVu9toeOGktKcPd4xP
ir/K
gbkQ1Tx3QdxeJLALxCq76NaV3XGBXVc6uFRvQy1GomaQz3julntF9w63ZDP1
QND9
t0GfWXQ1FMT4quGFXfsdGCJ4SF+HE2Br/IMPs1A875RYjYcPo7op4A==
=s3Ub
-----END PGP SIGNATURE-----

On Sat, Nov 18, 2006 at 09:20:40PM -0600, Tim & Alethea
Larson wrote:
> Upgraded my Q840 from 2.1 to 3.1.  Unpacked kernel,
rebooted, unpacked 
> base, comp, man, text, and xcomp, rebooted.  Now I
cannot login.  I get 
> this after entering a username:
> 
> schroeder login: in openpam_configure(): No required or
binding 
> component in service login, facility auth
> login: pam_start failed
> schroeder login: pam_start failed: system error
> 
> Any ideas?

Sounds like you also need to update your /etc. postinstall
will do it for
you--boot into single-user mode, mount your filesystems
read-write, unpack
the etc.tgz from 3.1 into a temporary directory, then run 
postinstall -s /path/to/temporarydir -d / fix
-- 
Name: Dave Huang         |  Mammal, mammal / their names are
called /
INet: khymazeotrope.org |  they raise a paw / the bat, the cat
/
FurryMUCK: Dahan         |  dolphin and dog / koala bear and
hog -- TMBG
Dahan: Hani G Y+C 30 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F-
Q+++ P+ B+ PA+ PL++

On 2006/11/19 00:22, khymazeotrope.org wrote:
> On Sat, Nov 18, 2006 at 09:20:40PM -0600, Tim &
Alethea Larson wrote:
>> Upgraded my Q840 from 2.1 to 3.1.  Unpacked kernel,
rebooted, unpacked 
>> base, comp, man, text, and xcomp, rebooted.  Now I
cannot login.  I get 
>> this after entering a username:
>>
>> schroeder login: in openpam_configure(): No
required or binding 
>> component in service login, facility auth
>> login: pam_start failed
>> schroeder login: pam_start failed: system error
>>
>> Any ideas?
> 
> Sounds like you also need to update your /etc.
postinstall will do it for
> you--boot into single-user mode, mount your filesystems
read-write, unpack
> the etc.tgz from 3.1 into a temporary directory, then
run 
> postinstall -s /path/to/temporarydir -d / fix

For a brief explanation of what happened to you, see the
section
"Compatibility Issues With Previous NetBSD
Releases" in the INSTALL docs for 3.1.

HTH,
Mark

At 21:20 Uhr -0600 18.11.2006, Tim & Alethea Larson
wrote:
>Upgraded my Q840 from 2.1 to 3.1.  Unpacked kernel,
rebooted, unpacked
>base, comp, man, text, and xcomp, rebooted.  Now I
cannot login.

Missing /etc/pam.d/* -- boot to single-user, unpack the 3.1
etc.tgz
somewhere, and  'cp -pR pam.d /etc/'.

FTR, it's best to do that _before_ upgrading from
NetBSD/mac68k < 3.

	hauke

--
"It's never straight up and down"     (DEVO)

Mark E. Perkins wrote:
> For a brief explanation of what happened to you, see
the section
> "Compatibility Issues With Previous NetBSD
Releases" in the INSTALL docs for 3.1.

Thanks for all the responses!  I guess the moral of the
story is "always 
read the release docs, EVEN when you know what you're
doing".  Oddly, 
this didn't happen on the first box I upgraded, but that was
a very 
minimal upgrade (kernel + base) and it boots to X so maybe
it is different.

THANKS!
Tim
-- 
Tim & Alethea
christtrek.org

Tim & Alethea Larson wrote:
> Upgraded my Q840 from 2.1 to 3.1.  Unpacked kernel,
rebooted, unpacked 
> base, comp, man, text, and xcomp, rebooted.  Now I
cannot login.  I get 
> this after entering a username:

Now a separate problem.  I did all those needed steps, but
now I can't 
seem to get a correct boot without a monitor attached.  This
box used to 
run fine as a server; I only connected the monitor to
diagnose the 
problem with the upgrade.

I heard the startup chime, the drive spinup for MacOS, a
pause about as 
long as the delay I've got in Booter, and then another round
of disk 
activity as NetBSD boots.  But no matter how long I wait, I
cannot 
connect by telnet nor ssh as I could before.  The address
isn't even 
pingable.  I guess I'll have to go back and read every line
of the 
INSTALL file to see if there's any networking changes.

Certainly been an interesting upgrade so far.


Tim

-- 
Tim & Alethea
christtrek.org

At 15:22 Uhr -0600 19.11.2006, Tim & Alethea Larson
wrote:

[Headless Mac]

>I heard the startup chime, the drive spinup for MacOS, a
pause about as
>long as the delay I've got in Booter, and then another
round of disk
>activity as NetBSD boots.  But no matter how long I
wait, I cannot
>connect by telnet nor ssh as I could before.  The
address isn't even
>pingable.

Try a serial console to see how far it gets?

	hauke

--
"It's never straight up and down"     (DEVO)

On 11/19/06, Hauke Fath <haukeespresso.rhein-neckar.de> wrote:
> At 15:22 Uhr -0600 19.11.2006, Tim & Alethea Larson
wrote:
>
> [Headless Mac]
>
> >I heard the startup chime, the drive spinup for
MacOS, a pause about as
> >long as the delay I've got in Booter, and then
another round of disk
> >activity as NetBSD boots.  But no matter how long I
wait, I cannot
> >connect by telnet nor ssh as I could before.  The
address isn't even
> >pingable.
>
> Try a serial console to see how far it gets?
>
>         hauke
>
> --
> "It's never straight up and down"     (DEVO)
>
>
>

There's a local Mom & Pop computer shop where I live
that sells mac
style monitor adapters to fit a normal PC style CRT, if the
lack of a
mac style monitor is what's hurting things. I know that
they're easier
to get/make than a DB8 (or whatever they're called) >
DIN9 adapter.
The shop sells them for $4 or so, perhaps check ebay since
the shop
owner sells his junk there too.

- mngrif

At 15:22 Uhr -0600 19.11.2006, Tim & Alethea Larson
wrote:
>Now a separate problem.  I did all those needed steps,
but now I can't
>seem to get a correct boot without a monitor attached.

My Quadra 650 defaults to

intvid0 at obio0  f9001000: DAFB video subsystem, monitor
sense 0
intvid0: 32 x 32, monochrome
macfb0 at intvid0

when it boots to serial console without a monitor attached.
In your case,
the kernel may decide that a 32x32 pixel screen won't do for
a console, and
panic.

Apart from using a serial console, you could either pick up
an apple-to-vga
adapter with dip switches, prepare a 15 pin SUB-D plug with
the appropriate
wire bridge for your preferred screen resolution, or use a
paper clip.

	hauke

--
"It's never straight up and down"     (DEVO)