Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #232278 > unrolled thread

Installation problems

Started byRichard Owlett <rowlett@cloud85.net>
First post2021-03-02 21:10 +0100
Last post2021-03-11 00:20 +0100
Articles 4 on this page of 84 — 20 participants

Back to article view | Back to linux.debian.user


Contents

  Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-02 21:10 +0100
    Re: Installation problems Brian <ad44@cityscape.co.uk> - 2021-03-02 21:40 +0100
      Re: Installation problems Weaver <weaver@riseup.net> - 2021-03-02 22:20 +0100
        Re: Installation problems <tomas@tuxteam.de> - 2021-03-02 22:30 +0100
          Re: Installation problems Brian <ad44@cityscape.co.uk> - 2021-03-03 00:10 +0100
      Re: Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-02 22:50 +0100
        Re: Installation problems "Andrew M.A. Cater" <amacater@einval.com> - 2021-03-02 23:20 +0100
          Re: Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-03 02:40 +0100
            Re: Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-03 02:50 +0100
        Re: Installation problems Keith Bainbridge <ke1thozgroups@gmx.com> - 2021-03-03 00:00 +0100
          Re: Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-03 10:30 +0100
            Re: Installation problems David Christensen <dpchrist@holgerdanske.com> - 2021-03-03 15:40 +0100
              Re: Installation problems Celejar <celejar@gmail.com> - 2021-03-03 16:40 +0100
              Re: Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-03 16:40 +0100
                Re: Installation problems David Christensen <dpchrist@holgerdanske.com> - 2021-03-03 22:40 +0100
                  Re: Installation problems Joe <joe@jretrading.com> - 2021-03-03 23:00 +0100
                    Re: Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-04 13:00 +0100
                      Re: Installation problems Tixy <tixy@yxit.co.uk> - 2021-03-04 13:30 +0100
                        Re: Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-04 14:00 +0100
                      Re: Installation problems Felix Miata <mrmazda@earthlink.net> - 2021-03-04 17:30 +0100
      Re: Installation problems Keith Bainbridge <ke1thozgroups@gmx.com> - 2021-03-02 23:50 +0100
        Re: Installation problems David Wright <deblis@lionunicorn.co.uk> - 2021-03-03 03:50 +0100
          Re: Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-03 10:50 +0100
            Re: Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-03 11:20 +0100
      Re: Installation problems Keith Bainbridge <ke1thozgroups@gmx.com> - 2021-03-03 00:00 +0100
    PARTIAL DIAGNOSIS of Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-03 16:30 +0100
      Re: PARTIAL DIAGNOSIS of Installation problems David Christensen <dpchrist@holgerdanske.com> - 2021-03-03 22:30 +0100
        Re: PARTIAL DIAGNOSIS of Installation problems Stefan Monnier <monnier@iro.umontreal.ca> - 2021-03-03 23:00 +0100
          Re: PARTIAL DIAGNOSIS of Installation problems David Christensen <dpchrist@holgerdanske.com> - 2021-03-04 02:50 +0100
            Re: PARTIAL DIAGNOSIS of Installation problems Stefan Monnier <monnier@iro.umontreal.ca> - 2021-03-04 03:50 +0100
              Re: PARTIAL DIAGNOSIS of Installation problems David Christensen <dpchrist@holgerdanske.com> - 2021-03-04 04:20 +0100
                Re: PARTIAL DIAGNOSIS of Installation problems Stefan Monnier <monnier@iro.umontreal.ca> - 2021-03-04 05:10 +0100
                  Re: PARTIAL DIAGNOSIS of Installation problems <tomas@tuxteam.de> - 2021-03-04 10:00 +0100
            Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems] <tomas@tuxteam.de> - 2021-03-04 09:50 +0100
              Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation  problems] Joe <joe@jretrading.com> - 2021-03-04 10:50 +0100
                Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems] <tomas@tuxteam.de> - 2021-03-04 14:20 +0100
                  Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation  problems] Celejar <celejar@gmail.com> - 2021-03-04 15:30 +0100
                    Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems] tomas@tuxteam.de - 2021-03-04 16:20 +0100
                      Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation  problems] Celejar <celejar@gmail.com> - 2021-03-04 17:20 +0100
                        Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems] tomas@tuxteam.de - 2021-03-04 19:10 +0100
                          Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation  problems] Celejar <celejar@gmail.com> - 2021-03-04 19:30 +0100
                          Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems] Stefan Monnier <monnier@iro.umontreal.ca> - 2021-03-04 23:20 +0100
                            Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems] <tomas@tuxteam.de> - 2021-03-04 23:40 +0100
                              Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation  problems] Joe <joe@jretrading.com> - 2021-03-04 23:50 +0100
                  Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation  problems] Celejar <celejar@gmail.com> - 2021-03-04 15:30 +0100
                Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation  problems] Celejar <celejar@gmail.com> - 2021-03-04 14:20 +0100
                  Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation  problems] Joe <joe@jretrading.com> - 2021-03-04 16:10 +0100
                    Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation  problems] Celejar <celejar@gmail.com> - 2021-03-04 17:20 +0100
                    OT: Bathroom scales (was: Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems]) rhkramer@gmail.com - 2021-03-04 17:40 +0100
              Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems] David Christensen <dpchrist@holgerdanske.com> - 2021-03-04 23:30 +0100
                [OFFTOPIC] Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems] Stefan Monnier <monnier@iro.umontreal.ca> - 2021-03-05 04:00 +0100
                  Re: [OFFTOPIC] Re: Trusting trust [was: PARTIAL DIAGNOSIS of  Installation problems] David Christensen <dpchrist@holgerdanske.com> - 2021-03-05 06:30 +0100
                    Re: [OFFTOPIC] Re: Trusting trust [was: PARTIAL DIAGNOSIS of  Installation problems] David Christensen <dpchrist@holgerdanske.com> - 2021-03-05 06:40 +0100
                    Re: [OFFTOPIC] Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems] Stefan Monnier <monnier@iro.umontreal.ca> - 2021-03-05 07:40 +0100
                      Re: [OFFTOPIC] Re: Trusting trust [was: PARTIAL DIAGNOSIS of  Installation problems] <tomas@tuxteam.de> - 2021-03-05 09:20 +0100
                        Re: [OFFTOPIC] Re: Trusting trust [was: PARTIAL DIAGNOSIS of Installation problems] Gene Heskett <gheskett@shentel.net> - 2021-03-05 15:10 +0100
      Re: PARTIAL DIAGNOSIS of Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-04 13:30 +0100
        Re: PARTIAL DIAGNOSIS of Installation problems David Wright <deblis@lionunicorn.co.uk> - 2021-03-04 18:50 +0100
        Re: PARTIAL DIAGNOSIS of Installation problems David Christensen <dpchrist@holgerdanske.com> - 2021-03-04 23:50 +0100
          Re: PARTIAL DIAGNOSIS of Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-05 13:20 +0100
            Re: PARTIAL DIAGNOSIS of Installation problems David Christensen <dpchrist@holgerdanske.com> - 2021-03-05 21:30 +0100
              Re: PARTIAL DIAGNOSIS of Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-05 22:20 +0100
                Re: PARTIAL DIAGNOSIS of Installation problems Joe <joe@jretrading.com> - 2021-03-05 22:50 +0100
                  Re: PARTIAL DIAGNOSIS of Installation problems Richard Owlett <rowlett@cloud85.net> - 2021-03-05 23:30 +0100
                  Re: PARTIAL DIAGNOSIS of Installation problems Charles Curley <charlescurley@charlescurley.com> - 2021-03-06 00:40 +0100
                  Re: PARTIAL DIAGNOSIS of Installation problems Celejar <celejar@gmail.com> - 2021-03-07 01:40 +0100
      Re: PARTIAL DIAGNOSIS of Installation problems David Wright <deblis@lionunicorn.co.uk> - 2021-03-06 02:50 +0100
      Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Richard Owlett <rowlett@cloud85.net> - 2021-03-08 13:10 +0100
        Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} "Andrew M.A. Cater" <amacater@einval.com> - 2021-03-08 13:30 +0100
        Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} songbird <songbird@anthive.com> - 2021-03-08 17:30 +0100
          Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Richard Owlett <rowlett@cloud85.net> - 2021-03-08 20:20 +0100
            Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} songbird <songbird@anthive.com> - 2021-03-09 02:10 +0100
          Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Richard Owlett <rowlett@cloud85.net> - 2021-03-09 13:40 +0100
            Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Anssi Saari <as@sci.fi> - 2021-03-09 14:00 +0100
              Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Joe <joe@jretrading.com> - 2021-03-09 14:20 +0100
            Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Andrei POPESCU <andreimpopescu@gmail.com> - 2021-03-09 14:10 +0100
              Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Joe <joe@jretrading.com> - 2021-03-09 14:20 +0100
              Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Richard Owlett <rowlett@cloud85.net> - 2021-03-09 21:40 +0100
                Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Andrei POPESCU <andreimpopescu@gmail.com> - 2021-03-10 10:50 +0100
                  Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Richard Owlett <rowlett@cloud85.net> - 2021-03-10 11:30 +0100
                    Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Andrei POPESCU <andreimpopescu@gmail.com> - 2021-03-10 14:40 +0100
                      Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Richard Owlett <rowlett@cloud85.net> - 2021-03-10 15:50 +0100
                        Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} Andrei POPESCU <andreimpopescu@gmail.com> - 2021-03-10 21:50 +0100
                    Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} "Andrew M.A. Cater" <amacater@einval.com> - 2021-03-11 00:20 +0100

Page 5 of 5 — ← Prev page 1 2 3 4 [5]


#232694 — Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems}

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2021-03-10 14:40 +0100
SubjectRe: Status update {Re: PARTIAL DIAGNOSIS of Installation problems}
Message-ID<BR7ea-6f8-7@gated-at.bofh.it>
In reply to#232662

[Multipart message — attachments visible in raw view] — view raw

On Mi, 10 mar 21, 04:26:06, Richard Owlett wrote:
> On 03/10/2021 03:45 AM, Andrei POPESCU wrote:
> > 
> > The boot process has three major stages.
> > 
> > 1. POST: https://en.wikipedia.org/wiki/Power-on_self-test
> > 2. Bootloader (grub, etc.)
> > 3. Operating System (in this case Debian)
> > 
> > In which of the above stages does the boot hang?
> 
> In yesterday's case, it was definitely case 3.
> In the case of getting a hang with blank screen I suspect it also was case
> 3, but I wasn't recording detailed symptoms the last time it happened.
> 
> I all cases I've heard the beep from POST.

Well, it should be pretty obvious if you are past the bootloader (grub) 
stage or not ;)

Assuming the hang happens in the OS stage a first step would be to 
remove 'quiet' from the boot command line. Both the kernel and systemd 
(assuming the boot is progressing that far) should be significantly more 
verbose then.
 
> Consider this sequence of events.
> 1. PC and LinkZone powered off
> 2. Turn on PC
> 3. Debian boots normally
> 4. Turn on LinkZone
> 5. Browse a web site
> 6. Shut off PC power leaving LinkZone running on its battery
> 7. Wait
> 8. Turn on PC
> 9. Failure occurs

After a failed boot you could try to boot normally and check the output 
of

    journalctl -alb -1

('-1' means the logs from the previous boot)

Based on the timestamps you should be able to determine whether this is 
the failed boot (assuming it got far enough to save the logs to 
persistent storage) or the previous one.

This may not work unless you enable persistent storage for 
systemd-journal (see /usr/share/doc/systemd/README.Debian).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]


#232699 — Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems}

FromRichard Owlett <rowlett@cloud85.net>
Date2021-03-10 15:50 +0100
SubjectRe: Status update {Re: PARTIAL DIAGNOSIS of Installation problems}
Message-ID<BR8jT-6Wz-3@gated-at.bofh.it>
In reply to#232694
On 03/10/2021 07:29 AM, Andrei POPESCU wrote:
> On Mi, 10 mar 21, 04:26:06, Richard Owlett wrote:
>> On 03/10/2021 03:45 AM, Andrei POPESCU wrote:
>>>
>>> The boot process has three major stages.
>>>
>>> 1. POST: https://en.wikipedia.org/wiki/Power-on_self-test
>>> 2. Bootloader (grub, etc.)
>>> 3. Operating System (in this case Debian)
>>>
>>> In which of the above stages does the boot hang?
>>
>> In yesterday's case, it was definitely case 3.
>> In the case of getting a hang with blank screen I suspect it also was case
>> 3, but I wasn't recording detailed symptoms the last time it happened.
>>
>> I all cases I've heard the beep from POST.
> 
> Well, it should be pretty obvious if you are past the bootloader (grub)
> stage or not ;)
> 
> Assuming the hang happens in the OS stage a first step would be to
> remove 'quiet' from the boot command line. Both the kernel and systemd
> (assuming the boot is progressing that far) should be significantly more
> verbose then.
>   
>> Consider this sequence of events.
>> 1. PC and LinkZone powered off
>> 2. Turn on PC
>> 3. Debian boots normally
>> 4. Turn on LinkZone
>> 5. Browse a web site
>> 6. Shut off PC power leaving LinkZone running on its battery
>> 7. Wait
>> 8. Turn on PC
>> 9. Failure occurs
> 
> After a failed boot you could try to boot normally and check the output
> of
> 
>      journalctl -alb -1
> 
> ('-1' means the logs from the previous boot)
> 
> Based on the timestamps you should be able to determine whether this is
> the failed boot (assuming it got far enough to save the logs to
> persistent storage) or the previous one.
> 
> This may not work unless you enable persistent storage for
> systemd-journal (see /usr/share/doc/systemd/README.Debian).
> 

I may not be able to do until tomorrow as I have errands to run before 
much rain in next several days.

Looking at /usr/share/doc/systemd/README.Debian prompts me to ask:
  "What logs might be created when attempting to run a netinst.iso?"

I have a spare laptop whose HDD I can wipe and use for experiments.
My  mindset still shows influence of doing component level debug in 
mid/late 70's. I just have no pre-retirement *nix experience.

Any other reading assignments?

My motto:
If retirement is not for learning, what use is it? <GRIN>

[toc] | [prev] | [next] | [standalone]


#232732 — Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems}

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2021-03-10 21:50 +0100
SubjectRe: Status update {Re: PARTIAL DIAGNOSIS of Installation problems}
Message-ID<BRdWh-1ZX-1@gated-at.bofh.it>
In reply to#232699

[Multipart message — attachments visible in raw view] — view raw

On Mi, 10 mar 21, 08:49:06, Richard Owlett wrote:
> 
> Looking at /usr/share/doc/systemd/README.Debian prompts me to ask:
>  "What logs might be created when attempting to run a netinst.iso?"

The Debian Installation Guide should have more information on the 
Installer's logs and where they are to be found on the final install.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]


#232753 — Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems}

From"Andrew M.A. Cater" <amacater@einval.com>
Date2021-03-11 00:20 +0100
SubjectRe: Status update {Re: PARTIAL DIAGNOSIS of Installation problems}
Message-ID<BRghs-3CL-1@gated-at.bofh.it>
In reply to#232662
On Wed, Mar 10, 2021 at 04:26:06AM -0600, Richard Owlett wrote:
> On 03/10/2021 03:45 AM, Andrei POPESCU wrote:
> > On Ma, 09 mar 21, 14:35:54, Richard Owlett wrote:
> > > On 03/09/2021 07:00 AM, Andrei POPESCU wrote:
> > > > On Ma, 09 mar 21, 06:32:33, Richard Owlett wrote:
> > > > > On 03/08/2021 10:18 AM, songbird wrote:
> > > > > > Richard Owlett wrote:
> > > > > > ...
> > > > > > 
> > > > > > before chasing down this rabbit hole, see if there is an
> > > > > > upgrade for your current kernel on the debian backports
> > > > > > site (for your processor and distribution type).  i just
> > > > > > had an issue with a new device not being recognized and
> > > > > > updated my kernel (for stretch) and it worked fine after
> > > > > > that.
> > > > > > 
> > > > > 
> > > > > The more I think about my observed symptoms, it would seem logical to be
> > > > > kernel related.
> > > > > 
> > > > > If the Linkzone is physically connected when PC is turned on, the boot
> > > > > process will hang until the Linkzone is disconnected.
> > > > 
> > > > Please also provide info like the exact stage of the boot process, any
> > > > (error) messages on screen, etc.
> > > > 
> > > > I've seen this symptom with a laptop before, though it would hang at the
> > > > BIOS stage (it was probably trying to boot from it), while you imply
> > > > it's later.
> > > 
> > > I think there are 2 separate states of the Linkzone may have when attempting
> > > to boot the PC.
> > > 
> > > 1. The Linkzone is off but plugged into the PC.
> > >     Boot appeared normal.
> > > 
> > > 2. The Linkzone is turned on and I have waited for its indicator lights to
> > > indicate connection to network.
> > >      This time the the screen was looping very quickly repeating that it was
> > > attempting to reset a USB device.
> > > 
> > > What log should I look in for such an error message?
> > > I know I've seen description of how to interpret the boot process to gather
> > > information. But where?
> > 
> > The boot process has three major stages.
> > 
> > 1. POST: https://en.wikipedia.org/wiki/Power-on_self-test
> > 2. Bootloader (grub, etc.)
> > 3. Operating System (in this case Debian)
> > 
> > In which of the above stages does the boot hang?
> 
> In yesterday's case, it was definitely case 3.
> In the case of getting a hang with blank screen I suspect it also was case
> 3, but I wasn't recording detailed symptoms the last time it happened.
> 
> I all cases I've heard the beep from POST.
> 
> > 
> > > I suspect also there is a subset of Case 2 -- The LinkZone had been used to
> > > interact with a website before being plugged into the PC under test.
> > 
> > Sorry, can't imagine how a modem can be used to "interact with a web
> > page" without being connected to a PC.
> 
> Consider this sequence of events.
> 1. PC and LinkZone powered off
> 2. Turn on PC
> 3. Debian boots normally
> 4. Turn on LinkZone
> 5. Browse a web site
> 6. Shut off PC power leaving LinkZone running on its battery
> 7. Wait
> 8. Turn on PC
> 9. Failure occurs
> 
Consider that the 4G connectivity device from the ISP probably needs to be on
BEFORE the PC connects to it. [I swear we've had almost exactly this message
before in one of the other threads].

The hotspot connects to 4G then serves out DHCP addresses - if you were using
WiFi, you'd get a WiFi connection. The hotspot is probably not meant to be
switched on and off repeatedly but to be used for a peroiod of hours 
per session.

1. Turn hotspot on. Check that it is working by using the app and/or 
connecting another device and checking connectivity.

2. Boot Debian.

3. Obtain Web connectivity *Profit*

If you're turning the PC on and off with a USB device physically connected, 
it's no wonder that things get confused - *especially* if USB enumeration
is unclear as to what sort of device it is.

I note also that you apparently have a cap of 2GB per month: in that situation
I'd not use a netinst to install anything but it does seem a crazily low
data amount for 30 days.

> 

All best, as ever,

Andy C.

[toc] | [prev] | [standalone]


Page 5 of 5 — ← Prev page 1 2 3 4 [5]

Back to top | Article view | linux.debian.user


csiph-web