From: lakester on
Suse V9.0
Between "Loading keymap qwerty/us.map.gz done" and
"Loading compose table winkeys shiftctrl latin1.add done"
the system "sits" for about 4 minutes. At least as long as all the
rest of the boot process together. Does anyone know why?

I can post boot.msg if that would assist. Would it be too big for a
text message? Should I attach it?

Thanks, lakester







From: lakester on
On Sun, 6 Feb 2005 21:40:11 -0000, houghi <houghi(a)houghi.org.invalid>
wrote:

>lakester wrote:
>> I can post boot.msg if that would assist. Would it be too big for a
>> text message? Should I attach it?
>
>Do not attach it. That would make it a binary. What you can do is first
>filter it out till you find the part that could be interesting and then
>take say 20 lines before that and 20 after that.

And so, it was Done...

Mount SMB File System unused
<notice>exit status of (smbfs) is (6)
<notice>start services (sshd fbset alsasound acpid)
<notice>startproc: execve (/usr/sbin/sshd) [ /usr/sbin/sshd -o
PidFile=/var/run/sshd.init.pid ], [ CONSOLE=/dev/console TERM=linux
SHELL=/bin/sh progress=25 INIT_VERSION=sysvinit-2.82
REDIRECT=/dev/tty1 COLUMNS=92
PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin vga=0x314
RUNLEVEL=5 PWD=/ PREVLEVEL=N LINES=29 HOME=/ SHLVL=2 splash=silent
sscripts=37 _=/sbin/startproc DAEMON=/usr/sbin/sshd ]
ACPID: No ACPI support in kernelskipped
Starting SSH daemondone
Starting sound driver: cs46xxdone
Restoring the previous sound settingdone
<notice>exit status of (sshd fbset alsasound acpid) is (0 0 0 5)
<notice>start services (splash postfix kbd cups)
<notice>startproc: execve (/usr/sbin/cupsd) [ /usr/sbin/cupsd ], [
CONSOLE=/dev/console TERM=linux SHELL=/bin/sh progress=29
INIT_VERSION=sysvinit-2.82 REDIRECT=/dev/tty1 COLUMNS=92
PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin vga=0x314
RUNLEVEL=5 PWD=/ PREVLEVEL=N LINES=29 HOME=/ SHLVL=2 splash=silent
sscripts=37 _=/sbin/startproc DAEMON=/usr/sbin/cupsd ]
Starting cupsddone
Starting mail service (Postfix)done
Loading keymap qwerty/us.map.gzdone

<< This is my note: this is where the process sits for about 4
minutes. "loading keymap qwerty/us.map.gz" shows "Done"and then the
cursor sits blinking for the 4 minutes before "loading compose table
winkeys shiftctrl latin1.add" appears and shows "Done".>>

Loading compose table winkeys shiftctrl latin1.adddone
Stop Unicode mode
doneLoading console font lat1-16.psfu -m none (B
done<notice>exit status of (splash postfix kbd cups) is (0 0 0 0)
<notice>start services (nscd hwscan cron)
<notice>startproc: execve (/usr/sbin/nscd) [ /usr/sbin/nscd ], [
CONSOLE=/dev/console TERM=linux SHELL=/bin/sh progress=33
INIT_VERSION=sysvinit-2.82 REDIRECT=/dev/tty1 COLUMNS=92
PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin vga=0x314
RUNLEVEL=5 PWD=/ PREVLEVEL=N LINES=29 HOME=/ SHLVL=2 splash=silent
sscripts=37 _=/sbin/startproc DAEMON=/usr/sbin/nscd ]
Starting hardware scan on boot<notice>startproc: execve
(/usr/sbin/cron) [ /usr/sbin/cron ], [ CONSOLE=/dev/console TERM=linux
SHELL=/bin/sh progress=33 INIT_VERSION=sysvinit-2.82
REDIRECT=/dev/tty1 COLUMNS=92
PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin vga=0x314
RUNLEVEL=5 PWD=/ PREVLEVEL=N LINES=29 HOME=/ SHLVL=2 splash=silent
sscripts=37 _=/sbin/startproc DAEMON=/usr/sbin/cron ]
Starting CRON daemondone
Starting Name Service Cache Daemondone
<notice>exit status of (nscd hwscan cron) is (0 0 0)
<notice>start services (xdm splash_late)
Starting service kdm<notice>startproc: execve (/opt/kde3/bin/kdm) [
/opt/kde3/bin/kdm ], [ LC_MONETARY= CONSOLE=/dev/console TERM=linux
SHELL=/bin/sh LC_NUMERIC= QTDIR=/usr/lib/qt3 LC_ALL= progress=36
INIT_VERSION=sysvinit-2.82 KDEROOTHOME=/root/.kdm REDIRECT=/dev/tty1
COLUMNS=92 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin
LC_MESSAGES= vga=0x314 RUNLEVEL=5 LC_COLLATE= PWD=/ LANG=en_US
PREVLEVEL=N LINES=29 HOME=/ SHLVL=2
XCURSOR_THEME=blueprint-cursor-theme no_proxy=localhost
WINDOWMANAGER=/usr/X11R6/bin/kde LC_CTYPE=en_US splash=silent
sscripts=37 LC_TIME= _=/sbin/startproc DAEMON=/opt/kde3/bin/kdm ]
done
<notice>exit status of (xdm splash_late) is (0 0)
Master Resource Control: runlevel 5 has been reached
Skipped services in runlevel 5: smbfs acpid
<notice>killproc: kill(661,3)


>
>You can do that by doing a search on the things you named.

Not very productive, most of the responses are from other people
posting their boot logs, and the "compose table winkeys shiftctrl
latin1.add" business seems to be near where a lot of people have
trouble with their keyboards. There doesn't seem to be any problem
(that I have observed) with my keyboard.

Thanks for the response, lakester

From: lakester on
On Mon, 7 Feb 2005 06:29:32 -0000, houghi <houghi(a)houghi.org.invalid>
wrote:

>lakester wrote:
>>>You can do that by doing a search on the things you named.
>>
>> Not very productive,
>
>Sorry, I ment to do the search in the file, not on the Internet.

That was how I can up with "compose table winkeys shiftctrl
latin1.add". My assumption was that since that was the next line to
come up after the delay, that "it" was causing the delay. For all I
know, the activity that slows down the process happens 3 lines later
(or more) and it causes a delay in writing previous lines to the
screen.

I guess I should assume that since there haven't been a bunch of
replys saying..."Oh, yeah, sure we've all had *that* problem", that my
symptoms are atypical.

I'm completely new to Linux/Gnu & SuSE, and my biggest problem is
trying to figure out how things operate "normally". I did what I now
suspect was a pretty barebones install of V9.0. from a magazine disk.
The help section doesn't seem to be complete, and I'm struggling to
get a handle on Yast. I've done some on-line updates just to try to
use it and understand how it works, but I'm really in the dark. I've
got a bunch of more disks with all kinds of stuff on 'em if I could
just understand Yast enough to install from a disk.

The Konqueror file manager function drives me crazy, all my training
is Windows-centric, and if it would just start at the Hard Drives and
work its' way down through the folders I would be able to figure out
where things are, where they're supposed to be, and how to find stuff.
It took me an age to find that boot.msg log. I saw somewhere recently
about calling up the man pages in Konqueror. Does that mean the man
pages are on the hard drive somewhere, or is Konqueror reading it off
the Net? That's gotta be a crazy question. But, what I need to find is
the "man pages" for Yast, and so far, I haven't discovered that in
either internal or external sources.

It's a long, sad, tale of woe.

It's good to know that everything is perfect, just the way that it is,
lakester




From: lakester on
On Mon, 07 Feb 2005 16:54:35 GMT, lakester <lakester(a)unknown.invalid>
wrote:

>On Mon, 7 Feb 2005 06:29:32 -0000, houghi <houghi(a)houghi.org.invalid>
>wrote:
>
>>lakester wrote:
>>>>You can do that by doing a search on the things you named.
>>>
>>> Not very productive,
>>
>>Sorry, I ment to do the search in the file, not on the Internet.
>
>That was how I can up with "compose table winkeys shiftctrl
>latin1.add".

<SNIP>

> But, what I need to find is
>the "man pages" for Yast, and so far, I haven't discovered that in
>either internal or external sources.

Holy Web resources Batman, I just found http://www.suseroot.com/
for the first time. There's even a reference to a Web page by some
dude called Houghi. Have you seen it?

lakester
From: lakester on
On Mon, 7 Feb 2005 18:41:14 -0000, houghi <houghi(a)houghi.org.invalid>
wrote:

>lakester wrote:
>> I guess I should assume that since there haven't been a bunch of
>> replys saying..."Oh, yeah, sure we've all had *that* problem", that my
>> symptoms are atypical.
>
>I hope somebody will help you out there.
I'll try patience, I read somewhere it's a Virtue.

>> ... I'm really in the dark....if I could
>> just understand Yast enough to install from a disk.
>
>Install the user and adminguide.
What folder/directory will they be in? When I'm in Yast, will they be
an avaible option to select?

>Linux does not work with hard drives.
I'm agin it.

>For the system there is no such thing as different drives. It just looks
>at directories and YOU decide what YOU put on them.
Got it. Right now I'm not so much looking to put things *on* as I am
to find stuff.
>
>To learn what directories are what, type 'man hier'
Auf Deutsch?

>> But, what I need to find is the "man pages" for Yast,
>> and so far, I haven't discovered that in either internal or external sources.
>
>man pages will (sic) normaly be on your drive. I don't use konqueror. I know
>there is a way to read man pages as well.
Another and/or better way?

> If you REALLY want some GUI to read the pages, try xman.
I have to get some basic competency with Yast before I try to install
more stuff, but what kind of app is xman? Is it included with the
distro?

> I would advide to open a terminal and just
>type 'man whatever'.
The command promt !?! In a terminal console !?! Without adult
supervision !?!

> There are no man pages for everything.
> Install the user guides for YAST.
Good idea. Where are they? Are they a selectable option in Yast ?

Thanks for all help, I'm going to explore that SuseRoot Web page to
see if they have any interessantes Material.

lakester, at mile 3