Brian McKee wrote:

>> The only way for me to get the messages is to log the actual console
>> output that is shown upon boot.
>
> untested - but hook another PC using screen or an honest to goodness
> serial terminal to a serial port and add
>
> console=/dev/ttySx
>
> to the boot line in grub.
>
> Or is there something I'm missing here?
>
LOL. There's a solution I haven't seen in a while - does anybody still
_have_ a serial port?
--
derek


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On Wed, 25 Jun 2008, Derek Broughton wrote:

..............snip................

> Sheesh. Ctrl-S/Q is just the most basic TTY technology. Look up any
> 30-year old teletype manual (that's why our consoles have names
> like /dev/tty*). But if you really need a citation, I said it here, last
> week.

Never had occasion to work with them before, hence the unfamiliarity.

...............snip................

> I get so tired of reading unique problems and hearing users claim that it
> makes Ubuntu useless for everybody.

I never claimed that.

>>> As a workaround to these circumstances, you may try:
>>> Crtl-S/Q,
>>> Crtl-Alt-F8, or
>>> modify a bootscript to 'tee' output to a user-created file...
>>
>> Again, sources please. Thanks.
>
> Why? Is there any way that these options can be destructive? You're
> essentially refusing to take the advice you're given, and then complaining
> that the Ubuntu developers ignore our needs. If you try what's been
> suggested and _still_ can't find the messages, then there's a problem, but
> I don't think you're looking hard enough.

1. Cool it. You re not tallking to Karl.
2. I'm not complaining. It was a comment.
3. What makes you think I'm refusing to take advice? Read my post again.
4. The reason I asked for sources is that being unfamiliar with TTYS
technology, I was looking for some background information. I dislike
trying things blindly without attempting to research them.

Farshteyn?

--
Bob Holtzman
"If you think you're getting free lunch,
check the price of the beer"

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Derek Broughton wrote:

Brian McKee wrote:




The only way for me to get the messages is to log the actual console
output that is shown upon boot.


untested - but hook another PC using screen or an honest to goodness
serial terminal to a serial port and add

console=/dev/ttySx

to the boot line in grub.

Or is there something I'm missing here?



LOL. There's a solution I haven't seen in a while - does anybody still
_have_ a serial port?


Yes.





--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Clifford Haynes wrote:

> Derek Broughton wrote:
>> Brian McKee wrote:
>>
>>
>>>> The only way for me to get the messages is to log the actual console
>>>> output that is shown upon boot.
>>>>
>>> untested - but hook another PC using screen or an honest to goodness
>>> serial terminal to a serial port and add
>>>
>>> console=/dev/ttySx
>>>
>>> to the boot line in grub.
>>>
>>> Or is there something I'm missing here?
>>>
>>>
>> LOL. There's a solution I haven't seen in a while - does anybody still
>> _have_ a serial port?
>>
> Yes.

Maybe it's a desktop-type thing. I haven't bought a desktop machine in at
least 5 years, but none of the 4 laptops I've bought since then have a
serial port, and I expect for this purpose that a usb-serial converter
wouldn't do the job :-)

I thought it worthy of comment because, not so very long ago, this was _the_
advice when you had a kernel problem.
--
derek


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Hello,

Robert Holtzman <holtzm@cox.net>
>>> I've since read that Crtl-S/Q may control the rate of start-up
>>> messages,
>>> and/or that Crtl-Alt-F8 makes them viewable in that console. HTH.
>>
>> Can you cite a source for this, please?

First of all, thank you for your reply, and sorry for the delay in
getting back.

I have been up and down my Firefox history several times today looking
for anything that would a) jog my increasingly pathetic memory, or b)
qualify as a source for a citation, but with no obvious candidates. I'm
reasonably sure I'm not hallucinating, at least about having read about
Crtl-S/Crtl-Q (for start/stop), and/or Crtl-Alt-F8. But the short answer
to your entirely reasonable question, I'm sad to say, is still "no", or
at least until my memory unlocks and I can find where I read it. I'm
feeling a bit like Winston Smith after he'd seen the photo...

The other option to which I'm willing to give a shot: simply re-boot,
try the keyboard sequence(s), and see what happens. Back in the days
when I was out of my depth in FreeBSD, (has it been that long?) I used
to hit Pause to get the bootlog messages to stand still for a while. Or
something along those lines. So I do have long-ish-term memories of
actually doing something along the lines of hitting Crtl-S and Crtl-Q
and having it produce the desired outcomes. But in any case, I'll let
the list know, assuming I don't bork everything irretrievably! Cover me!
I'm goin' in!


>> My /boot (on 8.04) contains no init.d. Instead, /etc/init.d contains:
>>
>> case "$BOOTLOGD_ENABLE" in
>> [Nn]*)
>> exit 0
>> ;;
>> esac
>>
>> Which to me is unintelligible
It's essentially unintelligible to me also, but guessing mode ON, I'd
suppose something along the lines of: if your environment variable for
enabling a bootloggin' daemon says anything vaguely negatory, ... then
get the f*** outta there and find something more productive to occupy
yourself with. OWTTE. :c)





--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

David Armour wrote:
> [...]
> I have been up and down my Firefox history several times today looking
> for anything that would a) jog my increasingly pathetic memory, or b)
> qualify as a source for a citation, but with no obvious candidates. I'm
> reasonably sure I'm not hallucinating, at least about having read about
> Crtl-S/Crtl-Q (for start/stop), and/or Crtl-Alt-F8. But the short answer
> to your entirely reasonable question, I'm sad to say, is still "no", or
> at least until my memory unlocks and I can find where I read it. I'm
> feeling a bit like Winston Smith after he'd seen the photo...
>
> The other option to which I'm willing to give a shot: simply re-boot,
> try the keyboard sequence(s), and see what happens. Back in the days
> when I was out of my depth in FreeBSD, (has it been that long?) I used
> to hit Pause to get the bootlog messages to stand still for a while. Or
> something along those lines. So I do have long-ish-term memories of
> actually doing something along the lines of hitting Crtl-S and Crtl-Q
> and having it produce the desired outcomes. But in any case, I'll let
> the list know, assuming I don't bork everything irretrievably! Cover me!
> I'm goin' in!
>
>

These codes seem to be documented in "man 4 console_codes"

I too have used Ctrl-S and Ctrl-Q to stop the bootup messages long
enough for me to see them.


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users