Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #232278 > unrolled thread
| Started by | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| First post | 2021-03-02 21:10 +0100 |
| Last post | 2021-03-11 00:20 +0100 |
| Articles | 20 on this page of 84 — 20 participants |
Back to article view | Back to linux.debian.user
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 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2021-03-05 21:30 +0100 |
| Subject | Re: PARTIAL DIAGNOSIS of Installation problems |
| Message-ID | <BPpfc-8f0-9@gated-at.bofh.it> |
| In reply to | #232398 |
On 3/5/21 4:09 AM, Richard Owlett wrote:
> On 03/04/2021 04:46 PM, David Christensen wrote:
> 2. I _actively_ abhor activating *any* WiFi device. [long OT story]
> My system currently has [from image of DVD1]:
> 1. Debian 10.0 with minimum default configuration of MATE.
That is a security risk. Update it. If you succeed, then you do not
need to install 10.8.
> 2. Debian 9.13 with MATE with lots of extras.
> Neither has any non-free drivers and both connect readily to internet.
How does your computer connect to the Internet?
> Attempting to install Debian 10.8.0 from image of netinst.iso downloaded
> after following default link from Debian homepage.
Ignore the giant "Download" button on the Debian home page and go to
this page:
https://www.debian.org/CD/
ignore this message:
"If you simply want to install Debian and have an Internet
connection on the target computer please consider the Network
Install media which is a smaller download."
Download a complete installer. I use this:
https://cdimage.debian.org/debian-cd/current/amd64/jigdo-cd/debian-10.8.0-amd64-xfce-CD-1.jigdo
> The apparent failure
> point is on the screen offering automatic configuration using DHCP.
You need to load the Wi-Fi packages and get your Wi-Fi interface working
before that point.
Are you following the instructions?
https://www.debian.org/releases/stable/amd64/ch02s02.en.html
https://www.debian.org/releases/stable/amd64/ch06s04.en.html
Have you tried "Expert Mode"?
With a complete installer, if you can install the Wi-Fi packages during
installation, fine. If not, do the installation and figure out the
Wi-Fi later.
David
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2021-03-05 22:20 +0100 |
| Subject | Re: PARTIAL DIAGNOSIS of Installation problems |
| Message-ID | <BPq1A-k9-5@gated-at.bofh.it> |
| In reply to | #232431 |
Please PLEASE *PLEASE* read what I *ACTUALLY* wrote !!!!!!! *BEFORE* replying to what you WISH I had written !
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2021-03-05 22:50 +0100 |
| Subject | Re: PARTIAL DIAGNOSIS of Installation problems |
| Message-ID | <BPquC-u2-7@gated-at.bofh.it> |
| In reply to | #232434 |
On Fri, 5 Mar 2021 15:12:50 -0600 Richard Owlett <rowlett@cloud85.net> wrote: > Please PLEASE *PLEASE* read what I *ACTUALLY* wrote > !!!!!!! *BEFORE* replying to what you WISH I had written ! > > In the beginning, the problem was inability to write an .iso to a USB stick or to use Google. Since then, things seem to have evolved. There are too many posts in this thread to read each one of yours to see what is currently the problem, and you have just chosen to rant in this post rather than explaining (again, if necessary) exactly what the current sticking point is. If it's user-installed non-free firmware for network interfaces, that is the state of manufacturing today: we're back to Winmodems and you're stuck with it. I have one of the last netbooks to come with an Ethernet port. A USB-Ethernet widget is quite useful to have around these days. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2021-03-05 23:30 +0100 |
| Subject | Re: PARTIAL DIAGNOSIS of Installation problems |
| Message-ID | <BPr7j-Xl-5@gated-at.bofh.it> |
| In reply to | #232435 |
On 03/05/2021 03:47 PM, Joe wrote: > On Fri, 5 Mar 2021 15:12:50 -0600 > Richard Owlett <rowlett@cloud85.net> wrote: > >> Please PLEASE *PLEASE* read what I *ACTUALLY* wrote >> !!!!!!! *BEFORE* replying to what you WISH I had written ! >> >> > > In the beginning, the problem was inability to write an .iso to a USB > stick or to use Google. Since then, things seem to have evolved. There > are too many posts in this thread to read each one of yours to see what > is currently the problem, and you have just chosen to rant in this post > rather than explaining (again, if necessary) exactly what the current > sticking point is. > > If it's user-installed non-free firmware for network interfaces, that is > the state of manufacturing today: we're back to Winmodems and you're > stuck with it. I have one of the last netbooks to come with an Ethernet > port. A USB-Ethernet widget is quite useful to have around these days. > install from image of DVD1 works. install from image of netinst.iso fails.
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2021-03-06 00:40 +0100 |
| Subject | Re: PARTIAL DIAGNOSIS of Installation problems |
| Message-ID | <BPsd3-1Eo-1@gated-at.bofh.it> |
| In reply to | #232435 |
On Fri, 5 Mar 2021 21:47:25 +0000 Joe <joe@jretrading.com> wrote: > In the beginning, the problem was inability to write an .iso to a USB > stick or to use Google. Since then, things seem to have evolved. There > are too many posts in this thread to read each one of yours to see > what is currently the problem, and you have just chosen to rant in > this post rather than explaining (again, if necessary) exactly what > the current sticking point is. It would help reduce confusion if the OP would, upon solving a problem, reply indicating that the problem is solved, and how to handle it. Then the OP should start a new, independent, email thread with the new problem, if any. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | Celejar <celejar@gmail.com> |
|---|---|
| Date | 2021-03-07 01:40 +0100 |
| Subject | Re: PARTIAL DIAGNOSIS of Installation problems |
| Message-ID | <BPPCF-7c1-3@gated-at.bofh.it> |
| In reply to | #232435 |
On Fri, 5 Mar 2021 21:47:25 +0000 Joe <joe@jretrading.com> wrote: ... > If it's user-installed non-free firmware for network interfaces, that is > the state of manufacturing today: we're back to Winmodems and you're > stuck with it. I have one of the last netbooks to come with an Ethernet > port. A USB-Ethernet widget is quite useful to have around these days. To be fair, Winmodems have limited hardware and do much of their work in software running on the host hardware. Network devices that require loadable firmware can be quite capable, hardware-wise, and the firmware runs on the NIC hardware itself. Winmodems therefore often lack Linux support, since software has to be written for the host, while loadable firmware doesn't pose any particular technical problem for Linux (aside from the ideological problem of it being non-free). Celejar
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2021-03-06 02:50 +0100 |
| Subject | Re: PARTIAL DIAGNOSIS of Installation problems |
| Message-ID | <BPueR-2Of-5@gated-at.bofh.it> |
| In reply to | #232311 |
On Mon 01 Feb 2021 at 06:46:40 (-0600), Richard Owlett wrote: > I have just installed Debian 10.7 to my Lenovo T510 Thinkpad having > copied debian-10.7.0-amd64-DVD-1.iso to a flash drive [the machine is > intentionally isolated from the internet]. So you have a 10.7 amd64 DVD available. On Wed 03 Mar 2021 at 09:22:45 (-0600), Richard Owlett wrote: > I've one fine machine running i386 flavor of Debian 9.13 . > I've wish to install 64 bit flavor on a second machine. > debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved. > It was copied to a USB flash drive and installation attempted. > Only did minimal install as I could not connect to internet. The netinst image is for people with access to the internet. > Connection to internet is via a T-Mobile Alcatel Linkzone Hotspot. > The WiFi connectivity programmatically disabled (i.e. it is > effectively just a modem). > It is detected by lsusb as: > Bus 002 Device 008: ID 1bbb:0195 T & A Mobile Phones > No non-free driver is needed as none are on the working system. > > I attempted to configure the ethernet device […] Which ethernet device? You don't have one in your universe. Now I realise why you wrote ethernet in quotation marks—you're pretending it's an ethernet connection. > Also I didn't find anything in > https://www.debian.org/releases/stable/amd64/ telling details of how > to set up a "ethernet" device. Why would there be? If you have a real Ethernet device, bought or supplied by your real ISP, you just plug a Cat5 cable into it. . You have a 10.7 amd64 DVD on a stick, . You have a USB port on the laptop, . Install it; . It will work: "install from image of DVD1 works." . Upgrade to 10.8 like everyone else does. . Then ascertain from *your* own *running* system what it requires for connectivity *before* you try to install something from scratch. It's called "bootstrapping": at each stage you need a little bit of a system that *works* to get you to the next stage. For someone who doesn't use WiFi, that gizmo looks like a dud. 3/4/5G devices with ethernet do appear to exist, but the ones I've seen are expensive. They throw in things like a firewall and so on. But they're not a mass market, so it's hardly surprising they cost. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2021-03-08 13:10 +0100 |
| Subject | Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQmRY-2oH-5@gated-at.bofh.it> |
| In reply to | #232311 |
On 03/03/2021 09:22 AM, Richard Owlett wrote:
> I've one fine machine running i386 flavor of Debian 9.13 .
> I've wish to install 64 bit flavor on a second machine.
> debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.
> It was copied to a USB flash drive and installation attempted.
> Only did minimal install as I could not connect to internet.
>
> To eliminate possibility that second was itself defective I attempted a
> multi-boot install to the first machine [Dell Latitude E6410].
> Essentially same result :{
>
> Connection to internet is via a T-Mobile Alcatel Linkzone Hotspot.
> The WiFi connectivity programmatically disabled (i.e. it is effectively
> just a modem).
> It is detected by lsusb as:
> Bus 002 Device 008: ID 1bbb:0195 T & A Mobile Phones
> No non-free driver is needed as none are on the working system.
>
> I attempted to configure the ethernet device with the numeric URL the
> working machine uses when configuring it. The installer was happy until
> it tried to connect to a chosen mirror. I tried 3 in the United States
> and 1 in Canada. None worked.
>
> As I can boot a working Debian on that machine, all installer logs for
> the failed install are conveniently available.
>
> Also I didn't find anything in
> https://www.debian.org/releases/stable/amd64/ telling details of how to
> set up a "ethernet" device.
>
> What do I do now?
> TIA
I was able ONCE to use netinst.iso with Alcatel Linkzone to install
Debian. There seem to be at least two distinct failure modes.
If the Linkzone has not been used to connect to the web since last power
up, it *WILL fail repeatably*.
If it has spent time connected to the web, the install *MAY* succeed.
Otherwise the error log says the server does not have correct release.
I will have to do some checking to verify that.
I hope to prepare a more detailed report later today.
Thank you.
[toc] | [prev] | [next] | [standalone]
| From | "Andrew M.A. Cater" <amacater@einval.com> |
|---|---|
| Date | 2021-03-08 13:30 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQnbk-2uS-5@gated-at.bofh.it> |
| In reply to | #232541 |
On Mon, Mar 08, 2021 at 06:06:17AM -0600, Richard Owlett wrote:
> On 03/03/2021 09:22 AM, Richard Owlett wrote:
> > I've one fine machine running i386 flavor of Debian 9.13 .
> > I've wish to install 64 bit flavor on a second machine.
> > debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.
> > It was copied to a USB flash drive and installation attempted.
> > Only did minimal install as I could not connect to internet.
> >
> > To eliminate possibility that second was itself defective I attempted a
> > multi-boot install to the first machine [Dell Latitude E6410].
> > Essentially same result :{
> >
> > Connection to internet is via a T-Mobile Alcatel Linkzone Hotspot.
> > The WiFi connectivity programmatically disabled (i.e. it is effectively
> > just a modem).
> > It is detected by lsusb as:
> > Bus 002 Device 008: ID 1bbb:0195 T & A Mobile Phones
> > No non-free driver is needed as none are on the working system.
> >
> > I attempted to configure the ethernet device with the numeric URL the
> > working machine uses when configuring it. The installer was happy until
> > it tried to connect to a chosen mirror. I tried 3 in the United States
> > and 1 in Canada. None worked.
> >
> > As I can boot a working Debian on that machine, all installer logs for
> > the failed install are conveniently available.
> >
> > Also I didn't find anything in
> > https://www.debian.org/releases/stable/amd64/ telling details of how to
> > set up a "ethernet" device.
> >
> > What do I do now?
> > TIA
>
> I was able ONCE to use netinst.iso with Alcatel Linkzone to install Debian.
> There seem to be at least two distinct failure modes.
>
> If the Linkzone has not been used to connect to the web since last power up,
> it *WILL fail repeatably*.
>
> If it has spent time connected to the web, the install *MAY* succeed.
> Otherwise the error log says the server does not have correct release.
> I will have to do some checking to verify that.
>
> I hope to prepare a more detailed report later today.
>
> Thank you.
>
This ties into the 20 questions email I posed to you to try and narrow down
failure modes:
If your connectivity is intermittent - how do you tell that the Alcatel is
working correctly, you have IP connectivity and connection to the outside
world?
[In most cases, there's a webpage: if there's an app, how do _you_ access the
app.? ]
If you don't have network connectivity, you won't get to any mirror, obviously.
If the Alcatel is originally designed as a central hot spot to which people
would connect via WiFi - your use of USB to connect is probably an outlying
case that your ISP would have difficulty troubleshooting.
If you could respond to the 20 questions email: that's intended to narrow
down some of the issues :)
All the best, Andy C.
>
>
>
>
[toc] | [prev] | [next] | [standalone]
| From | songbird <songbird@anthive.com> |
|---|---|
| Date | 2021-03-08 17:30 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQqVA-4NF-7@gated-at.bofh.it> |
| In reply to | #232541 |
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. songbird
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2021-03-08 20:20 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQtA5-6t5-9@gated-at.bofh.it> |
| In reply to | #232551 |
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. > If it's a kernel issue, I'll just wait for Debian 11. I had essentially tried the 10.8 netinst to get instant gratification of moving from 32 to 64 bits in one day rather than one week. Thanks
[toc] | [prev] | [next] | [standalone]
| From | songbird <songbird@anthive.com> |
|---|---|
| Date | 2021-03-09 02:10 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQz2O-1ut-3@gated-at.bofh.it> |
| In reply to | #232556 |
Richard Owlett wrote: ... > If it's a kernel issue, I'll just wait for Debian 11. I had essentially > tried the 10.8 netinst to get instant gratification of moving from 32 to > 64 bits in one day rather than one week. certainly understandable. :) hope it works well for you! songbird
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2021-03-09 13:40 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQJOx-8ky-5@gated-at.bofh.it> |
| In reply to | #232551 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Anssi Saari <as@sci.fi> |
|---|---|
| Date | 2021-03-09 14:00 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQK7T-8r4-5@gated-at.bofh.it> |
| In reply to | #232579 |
Richard Owlett <rowlett@cloud85.net> writes: > 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. I have a guess then. Maybe the Linkzone comes up as a storage device and has to be specifically instructed to become a modem. This was a common deal with old cellular USB sticks as I recall. A full Linux OS usually has something to do this switch while an installer doesn't necessarily. As a side note, Google tells me the Linkzone uses bog standard cdc_ether and rndis_host drivers, same as what USB modems and Android phones commonly use.
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2021-03-09 14:20 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQKrg-pe-5@gated-at.bofh.it> |
| In reply to | #232582 |
On Tue, 09 Mar 2021 14:57:47 +0200 Anssi Saari <as@sci.fi> wrote: > Richard Owlett <rowlett@cloud85.net> writes: > > > 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. > > I have a guess then. Maybe the Linkzone comes up as a storage device > and has to be specifically instructed to become a modem. This was a > common deal with old cellular USB sticks as I recall. A full Linux OS > usually has something to do this switch while an installer doesn't > necessarily. > > As a side note, Google tells me the Linkzone uses bog standard > cdc_ether and rndis_host drivers, same as what USB modems and Android > phones commonly use. > > Usbswitch was the software, and I don't think systemd needs it. A long time since I used a mobile dongle. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2021-03-09 14:10 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQKhA-i9-23@gated-at.bofh.it> |
| In reply to | #232579 |
[Multipart message — attachments visible in raw view] — view raw
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. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2021-03-09 14:20 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQKrg-pe-13@gated-at.bofh.it> |
| In reply to | #232583 |
On Tue, 9 Mar 2021 15:00:07 +0200 Andrei POPESCU <andreimpopescu@gmail.com> 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. > Yes, it's fairly common. My desktop (Gigabyte MB, mumble-mumble years old) does it. Only with some things: it won't try to boot from a Kindle or mobile phone, but it will try from a USB stick. Depends on the filesystem/protocol, I suppose. What it won't do is give up after a time and try the next device, it will just hang permanently. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2021-03-09 21:40 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BQRj3-4JQ-3@gated-at.bofh.it> |
| In reply to | #232583 |
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.
>
> Kind regards,
> Andrei
>
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?
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.
I recall having seen the "reset USB device" looping message before but
sometimes there has just been a blank screen.
HTH
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2021-03-10 10:50 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BR3DA-431-17@gated-at.bofh.it> |
| In reply to | #232599 |
[Multipart message — attachments visible in raw view] — view raw
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? > 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. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2021-03-10 11:30 +0100 |
| Subject | Re: Status update {Re: PARTIAL DIAGNOSIS of Installation problems} |
| Message-ID | <BR4gj-4vy-7@gated-at.bofh.it> |
| In reply to | #232659 |
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
[toc] | [prev] | [next] | [standalone]
Page 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
Back to top | Article view | linux.debian.user
csiph-web