[SOLVED]Installer hangs up on Lithium 3 32-bit .iso

Len E. · 2021-09-09 05:22:21

After downloading the new subject .iso yesterday
and trying to install it,
I found that after the initial installer entries
and the setting of the network connections,
the installer hangs up showing a blank screen.

Cntrl-alt-delete key entry triggers a shutdown.

The SHA256sum of the downloaded .iso verified o.k.
Burned the 674MB .iso to a CD, and then to
a DVD+RW; same difficulty with either media.

What to try next ??

Len E.

unklar · 2021-09-09 06:50:21

Len E. wrote:

What to try next ??

^The crystal ball of the forum is unfortunately in Reperatur. wink Perhaps you start with the details of the computer on which you want to install:

inxi -Fxz

parted -l

rbh · 2021-09-09 20:31:49

Len E. wrote:

What to try next ??

I suggest you read Guide to getting help

Len E. · 2021-09-09 23:35:43

user@debian:~$ inxi -Fxz
System:    Host: debian Kernel: 4.19.0-17-686 i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: Openbox 3.6.1 
           Distro: BunsenLabs GNU/Linux 10.5 (Lithium) base: Debian GNU/Linux 10 
Machine:   Type: Desktop System: Compaq-Presario product: NY540AA-ABL CQ5210F v: N/A serial: <filter> 
           Mobo: PEGATRON model: NARRA5 v: 5.00 serial: <filter> BIOS: Phoenix v: 5.52 date: 09/14/2009 
CPU:       Topology: Dual Core model: AMD Athlon II X2 215 bits: 64 type: MCP arch: K10 rev: 2 L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 10849 
           Speed: 800 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 800 2: 800 
Graphics:  Device-1: NVIDIA C61 [GeForce 6150SE nForce 430] vendor: Hewlett-Packard driver: nouveau v: kernel bus ID: 00:0d.0 
           Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1152x864~75Hz 
           OpenGL: renderer: NV4C v: 2.1 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: NVIDIA MCP61 High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel 
           bus ID: 00:05.0 
           Sound Server: ALSA v: k4.19.0-17-686 
Network:   Device-1: NVIDIA MCP61 Ethernet vendor: Hewlett-Packard type: network bridge driver: forcedeth v: kernel port: fc00 
           bus ID: 00:07.0 
           IF: enp0s7 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 469.50 GiB used: 2.29 GiB (0.5%) 
           ID-1: /dev/sda vendor: Western Digital model: WD5000AAKS-65V0A0 size: 465.76 GiB temp: 40 C 
           ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 3.73 GiB 
Partition: ID-1: / size: 1.42 GiB used: 262.9 MiB (18.1%) fs: overlay source: ERR-102 
Sensors:   Missing: Required tool sensors not installed. Check --recommends 
Info:      Processes: 123 Uptime: 24m Memory: 2.83 GiB used: 303.3 MiB (10.4%) Init: systemd runlevel: 5 Compilers: gcc: N/A 
           Shell: bash v: 5.0.3 inxi: 3.0.32 

*************************************************************************
user@debian:~$ sudo parted -l
Model: ATA WDC WD5000AAKS-6 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size    Type      File system     Flags
 1      1049kB  106MB  105MB   primary   ntfs            boot
 2      106MB   129GB  129GB   primary   ntfs
 3      129GB   142GB  12.6GB  primary   ntfs
 4      142GB   500GB  359GB   extended
 5      142GB   143GB  1074MB  logical   ext4
 6      143GB   181GB  38.8GB  logical   ext4
 7      181GB   220GB  38.8GB  logical   ext4
 8      220GB   259GB  38.8GB  logical   ext4
 9      259GB   298GB  38.8GB  logical   ext4
10      298GB   336GB  38.8GB  logical   ext4
11      336GB   375GB  38.8GB  logical   ext4
12      375GB   414GB  38.8GB  logical   ext4
13      414GB   438GB  23.6GB  logical   ext4
14      438GB   439GB  1074MB  logical   ext4
15      439GB   493GB  53.9GB  logical   ext4
16      493GB   500GB  7570MB  logical   linux-swap(v1)


Model: Lexar USB Flash Drive (scsi)
Disk /dev/sdb: 4010MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      24.6kB  4010MB  4010MB  primary  fat32        boot, lba

Machine 2:

user@debian:~$ inxi -Fxz
System:    Host: debian Kernel: 4.19.0-17-686 i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: Openbox 3.6.1 
           Distro: BunsenLabs GNU/Linux 10.5 (Lithium) base: Debian GNU/Linux 10 
Machine:   Type: Desktop System: Hewlett-Packard product: HP Compaq dc5800 Small Form Factor v: N/A serial: <filter> 
           Mobo: Hewlett-Packard model: 2820h serial: <filter> BIOS: Hewlett-Packard v: 786F2 v01.60 date: 10/26/2015 
CPU:       Topology: Dual Core model: Intel Core2 Duo E6750 bits: 64 type: MCP arch: Core Merom rev: B L2 cache: 4096 KiB 
           flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 10640 
           Speed: 1995 MHz min/max: 1998/2667 MHz Core speeds (MHz): 1: 1995 2: 1995 
Graphics:  Device-1: Intel 82Q33 Express Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa resolution: 1280x1024~60Hz 
           OpenGL: renderer: Mesa DRI Intel Q33 x86/MMX/SSE2 v: 1.4 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.19.0-17-686 
Network:   Device-1: Intel 82566DM-2 Gigabit Network vendor: Hewlett-Packard driver: e1000e v: 3.2.6-k port: 1100 
           bus ID: 00:19.0 
           IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 301.83 GiB used: 2.29 GiB (0.8%) 
           ID-1: /dev/sda vendor: Seagate model: ST3320418AS size: 298.09 GiB temp: 34 C 
           ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 3.73 GiB 
Partition: ID-1: / size: 995.2 MiB used: 262.9 MiB (26.4%) fs: overlay source: ERR-102 
Sensors:   Missing: Required tool sensors not installed. Check --recommends 
Info:      Processes: 125 Uptime: 11m Memory: 1.94 GiB used: 288.8 MiB (14.5%) Init: systemd runlevel: 5 Compilers: gcc: N/A 
           Shell: bash v: 5.0.3 inxi: 3.0.32
******************************************************************************
user@debian:~$ sudo parted -l
Model: ATA ST3320418AS (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system     Flags
 1      32.3kB  32.2GB  32.2GB  primary   ntfs            boot
 2      32.2GB  33.3GB  1074MB  primary   ext4
 3      33.3GB  195GB   162GB   primary   ext4
 4      195GB   320GB   125GB   extended
 5      195GB   209GB   13.3GB  logical   ext4
 6      209GB   234GB   25.8GB  logical   ext4
 7      234GB   248GB   14.0GB  logical   ext4
 8      248GB   253GB   4295MB  logical   linux-swap(v1)
 9      253GB   267GB   14.0GB  logical   ext4
10      267GB   280GB   13.3GB  logical   ext4
11      280GB   291GB   10.7GB  logical   ext4
12      291GB   308GB   17.6GB  logical   ext4
13      308GB   320GB   11.8GB  logical   ext4


Model: Lexar USB Flash Drive (scsi)
Disk /dev/sdb: 4010MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      24.6kB  4010MB  4010MB  primary  fat32        boot, lba


Model: TSSTcorp CDDVDW TS-H653Z (scsi)
Disk /dev/sr0: 4700MB
Sector size (logical/physical): 2048B/2048B
Partition Table: msdos
Disk Flags: 

Number  Start  End     Size    Type     File system  Flags
 1      131kB  2827MB  2827MB  primary               boot, hidden

****************************************************************************

Len E.

Last edited by Len E. (2021-09-11 21:37:48)

rbh · 2021-09-10 06:08:20

Len E. wrote:

user@debian:~$ inxi -Fxz
System: Host: debian Kernel: 4.19.0-17-686 i686 bits:
[...]
CPU: Topology: Dual Core model: AMD Athlon II X2 215 bits: 64 type: MCP arch: K10 rev: 2 L2 cache: 1024 KiB

Ok, that answers the most important question, can you boot live session.
Another important question is if there is any errors in logs in the system you tried to install: /var/log/installer/*.

You have installed 32 bit os on 64 bit pc, Any special reason for that choise?
Most of the popular Linux distributions as Arch Linux, Ubuntu and Fedora has dropped the support for this older architecture. Some programs is not available in 32 bit versions anymore. You might get another result installing 64-bit iso.

Number Start End Size Type File system Flags
1 1049kB 106MB 105MB primary ntfs boot
2 106MB 129GB 129GB primary ntfs
3 129GB 142GB 12.6GB primary ntfs
4 142GB 500GB 359GB extended
5 142GB 143GB 1074MB logical ext4
6 143GB 181GB 38.8GB logical ext4
7 181GB 220GB 38.8GB logical ext4
8 220GB 259GB 38.8GB logical ext4
9 259GB 298GB 38.8GB logical ext4
10 298GB 336GB 38.8GB logical ext4
11 336GB 375GB 38.8GB logical ext4
12 375GB 414GB 38.8GB logical ext4
13 414GB 438GB 23.6GB logical ext4
14 438GB 439GB 1074MB logical ext4
15 439GB 493GB 53.9GB logical ext4
16 493GB 500GB 7570MB logical linux-swap(v1)

You have some linuxpartitions before? You are experienced linux user? Good to know when phrasing answer.

Btw, any particular reason why you ignoreed forum rule to post terminal output between [ code ] / [ / code ] tags?

unklar · 2021-09-10 08:28:28

@Len E.

Looking at the parted issues, I can't believe you've never heard of code-tags in the forums of this world. No human can read that reasonably!
Please, correct that.

Otherwise, rbh has already referred to their problem. Boot the 64bit ISO on your 64bit CPU's!
If against all expectations it still doesn't work, use the kernel parameter nomodeset.

Len E. · 2021-09-12 05:46:11

Hi rbh, unklar,

You’ve posed several questions in your recent posts which I’ll try to answer:

I am an experienced Linux user in that my first installation was Debian 6.0.6, with
the intent of migrating away from Windows for my software requirements. At the
time, 32-bit software was better supported than 64-bit software. Because of
economic constraints, my computer equipment has always been a collection of
low-end, hand-me-downs, some 32-bit machines, some 64-bit machines.
Consequently, in the interest of portability, I’ve stayed predominantly with
32-bit distros, with only some 64-bit installations to support 64-bit-only
software such as the Zoom conferencing package.

To this day, my favourite distribution is Debian, because I’ve never experienced
any trouble with 32-bit releases on 64-bit machines. In theory, 32-bit software
should run fine on 64-bit machines, and that has certainly been the case with Debian.

Experienced or not, my knowledge gaps surface from time-to-time, and my ignorance
of code-tags is an instance of that. Thanks to you both for bringing it to my attention.
(This hasn’t been the first such instance, and assuredly won’t be the last).

One suggestion I don’t know how to react to is the one about checking for any
reported installation errors in /var/log/installer. Given that the installer hangs up
and the only way out is to abort the live session, I don’t see any way to check the
log.

**********************************************************************
My latest test was on an Acer Netbook 32-bit machine. The results were the same as
with the previous tests. Because the Netbook has no CD drive, booting up the live cd
was problematic because the standard Debian FAQ recommendations in the post
“How to install Lithium with USB stick” using the cp or dd approaches didn’t work.
Fortunately, I came across the balenaEtcher-1.5.121 package, available for 32-bit
Linux, and I was able to create a bootable USB stick with it.

The following is the terminal output from the Acer Netbook, WITH code-tags.

user@debian:~$ inxi -Fxz
System:    Host: debian Kernel: 4.19.0-17-686 i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: Openbox 3.6.1 
           Distro: BunsenLabs GNU/Linux 10.5 (Lithium) base: Debian GNU/Linux 10 
Machine:   Type: Laptop System: Acer product: Aspire one v: V1.12 serial: <filter> 
           Mobo: Acer model: Aspire one v: V1.12 serial: <filter> BIOS: Acer v: 1.12 date: 08/17/2009 
Battery:   ID-1: BAT0 charge: 60.6 Wh condition: 60.6/62.6 Wh (97%) model: PANASONIC UM08B52 status: Full 
CPU:       Topology: Single Core model: Intel Atom N280 bits: 32 type: MT arch: Bonnell rev: 2 L2 cache: 512 KiB 
           flags: pae sse sse2 sse3 ssse3 bogomips: 6650 
           Speed: 1106 MHz min/max: 800/1333 MHz Core speeds (MHz): 1: 998 2: 998 
Graphics:  Device-1: Intel Mobile 945GSE Express Integrated Graphics vendor: Acer Incorporated ALI driver: i915 v: kernel 
           bus ID: 00:02.0 
           Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa 
           resolution: 1024x600~60Hz, 1024x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Acer Incorporated ALI driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.19.0-17-686 
Network:   Device-1: Broadcom Limited BCM4312 802.11b/g LP-PHY 
           vendor: Foxconn T77H106.00 Wireless Half-size Mini PCIe Card driver: b43-pci-bridge v: N/A port: 4000 
           bus ID: 01:00.0 
           IF-ID-1: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 266.50 GiB used: 30.80 GiB (11.6%) 
           ID-1: /dev/sda type: USB vendor: Lexar model: USB Flash Drive size: 3.73 GiB 
           ID-2: /dev/sdb vendor: Western Digital model: WD2500BEVT-22ZCT0 size: 232.89 GiB temp: 44 C 
           ID-3: /dev/sdc type: USB vendor: Lexar model: USB Flash Drive size: 29.88 GiB 
Partition: ID-1: / size: 496.5 MiB used: 263.0 MiB (53.0%) fs: overlay source: ERR-102 
Sensors:   Missing: Required tool sensors not installed. Check --recommends 
Info:      Processes: 137 Uptime: 57m Memory: 992.9 MiB used: 271.4 MiB (27.3%) Init: systemd runlevel: 5 Compilers: 
           gcc: N/A Shell: bash v: 5.0.3 inxi: 3.0.32 

user@debian:~$ sudo parted -l
Model: Lexar USB Flash Drive (scsi)
Disk /dev/sda: 4010MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      32.8kB  707MB  707MB  primary               boot, hidden


Model: ATA WDC WD2500BEVT-2 (scsi)
Disk /dev/sdb: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system     Flags
 1      1049kB  17.2GB  17.2GB  primary   ext4
 2      17.2GB  27.9GB  10.7GB  primary   ext4
 3      27.9GB  34.4GB  6442MB  primary   ext4            boot
 4      34.4GB  250GB   216GB   extended
 5      34.4GB  36.5GB  2147MB  logical   linux-swap(v1)
 6      36.5GB  53.7GB  17.2GB  logical   ext4
 7      53.7GB  70.9GB  17.2GB  logical   ext4
 8      70.9GB  88.0GB  17.2GB  logical   ext4
 9      88.0GB  105GB   17.2GB  logical   ext4
10      105GB   122GB   17.2GB  logical   ext4
11      122GB   129GB   6443MB  logical   ext4
12      129GB   146GB   17.2GB  logical   ext4
13      146GB   163GB   17.2GB  logical   ext4
14      163GB   187GB   23.6GB  logical   ext4
15      187GB   204GB   17.2GB  logical   ext4
16      204GB   250GB   46.0GB  logical   ext4


Model: Lexar USB Flash Drive (scsi)
Disk /dev/sdc: 32.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  32.0GB  32.0GB  primary  ext4         boot
 2      32.0GB  32.1GB  51.4MB  primary  fat32        esp


user@debian:~$

Len E.

rbh · 2021-09-12 08:59:46

Len E. wrote:

You’ve posed several questions in your recent posts which I’ll try to answer:

You don't give respons on if you tried to add "nomodeset" as kernel boot parameter. It is quite common it needs to be done, since the graphic stack moved in to the kernel.

At the time, 32-bit software was better supported than 64-bit software.

And today it is the opposite situation. There is even the possibility that some hardware drivers is not available for 32-bit,only as 64 bit...

In theory, 32-bit software should run fine on 64-bit machines, and that has certainly been the case with Debian.

Yes, that was true once, but as you noted, the 32 bit code base is reduced.

One suggestion I don’t know how to react to is the one about checking for any
reported installation errors in /var/log/installer. Given that the installer hangs up
and the only way out is to abort the live session, I don’t see any way to check the
log.

You schoose to boot the BL iso ta a live session or the installer. The live session has no installer!
So, when you have aborted the installation, boot to the live session.

You have quite many partitions. Have you partioned yourself, or have you kept the partition that was before you got it? Do you know what partition you installed to or is the table dumped before you installed?

If you have installed / to /dev/sdb6, mount that as root:

# mkdir /mnt/sdb6
# mount /dev/sdb6 /mnt/sdb6

Navigate to /mnt/sdb6/var/log/installer.
Page through the logs with less or use geany.
If you use the graphical installer, you can take screenshots of the installation.

using the cp or dd approaches didn’t work.

I have not burned a boot cd/dvd for at least 15 years, dont recal dd ever has failed. That problem deserves an own thread in Basic Help & Support (as should - I think - this thread also be moved to...)

user@debian:~$ inxi -Fxz
[...]
Machine: Type: Laptop System: Acer product: Aspire one v: V1.12 serial: <filter>
Mobo: Acer model: Aspire one v: V1.12 serial: <filter> BIOS: Acer v: 1.12 date: 08/17/2009

In the Linux hardware database, there is 25 probes of your netbook

One probe of Acer Aspire one, with Debian 10
(dmidecode, gives better info of pc modell)

So, the hardware should work with Debian and hence with BunsenLabs.

Can you install Debian?
You can allways make a workaround; install Debian withuat X, run bunsen-netinstal for Bunsenlabs (still only for BunsenLabsLithium), or just add the BL repo and apt-key for a Package-based install https://www.bunsenlabs.org/installation.html

Len E. · 2021-09-13 02:32:24

Hi rbh:

In following up on your nomodeset recommendation, I’ve stumbled onto a
very clear definition of what the bug is, and a possibly-unreliable workaround.

My Acer Netbook requires a USB-to-internet adapter for internet access because
the original internet port no longer functions. When I attempted the install Lithium
specifying the nomodeset kernel parameter, the installer had difficulty with the
peculiar internet connection, was unable to complete it, and gave the option of
cancelling the connection configuration altogether. When I did that, the installer
moved on to the next installation phase, defining the host name. I didn’t proceed
any further with the installation, knowing that the internet connection was incomplete.

On my Machine 2 described earlier in this post, I started the installer, and in
the last portion of the network configuration phase, I hit the cancel button.
My timing happened to be just right, because simultaneously there was
a network configuration complete message and the prompt to define the host name.
I was then able to complete the installation normally, and to my joy, found that
the internet connection on the installed Lithium 3 worked normally !

***************************************************************
My conclusion is that there is something not right in the installer process in the
transition from completion of the network configuration phase to the start of
the host name definition phase. If this can be corrected, all will be well.
****************************************************************
To address your queries about partition definitions, I’d like to explain how
my terminal output printouts were prepared:

-Boot the livecd, reload synaptic packages lists
-From synaptic, install abiword and lxterminal
(There were file protection error messages with these installs,
but they did complete successfully).
-Open a new document in abiword, from lxterminal, generate
the terminal outputs and copy/paste them into the abiword document
-Save the abiword document to a mounted flash drive

In summary, prior to the successful installation just completed, there has been no
Lithium installations to a hard drive, and therefore no partitions to consider.
(I have several distros installed on each of my machines, and I’ve defined/created
all the partitions to contain them. Among them are a Debian 10.9-LXDE distro
and a Debian 11.0-LXDE distro, each installed, customized and then remastered
with remastersys-debian-3.10.19-3 downloaded from SourceForge).

I hope I’ve addressed all your questions.

Len E.

unklar · 2021-09-13 07:24:14

It is noticeable that all their three machines have this error:

Drives:    Local Storage: total: 469.50 GiB used: 2.29 GiB (0.5%) 
           ID-1: /dev/sda vendor: Western Digital model: WD5000AAKS-65V0A0 size: 465.76 GiB temp: 40 C 
           ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 3.73 GiB 
Partition: ID-1: / size: 1.42 GiB used: 262.9 MiB (18.1%) fs: overlay source: ERR-102

Drives:    Local Storage: total: 301.83 GiB used: 2.29 GiB (0.8%) 
           ID-1: /dev/sda vendor: Seagate model: ST3320418AS size: 298.09 GiB temp: 34 C 
           ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 3.73 GiB 
Partition: ID-1: / size: 995.2 MiB used: 262.9 MiB (26.4%) fs: overlay source: ERR-102

Drives:    Local Storage: total: 266.50 GiB used: 30.80 GiB (11.6%) 
           ID-1: /dev/sda type: USB vendor: Lexar model: USB Flash Drive size: 3.73 GiB 
           ID-2: /dev/sdb vendor: Western Digital model: WD2500BEVT-22ZCT0 size: 232.89 GiB temp: 44 C 
           ID-3: /dev/sdc type: USB vendor: Lexar model: USB Flash Drive size: 29.88 GiB 
Partition: ID-1: / size: 496.5 MiB used: 263.0 MiB (53.0%) fs: overlay source: ERR-102

For this I only found people with Uefi machines that could not install Linux because WINDOWS started in the bios from RAID or IDE. After they switched to AHCI, it was possible to install Linux.

I do not know if this is also true in their case.

Likewise, I don't understand (apart from 32 vers. 64bit) why a USB stick is always present during "installation". In my opinion, this contradicts an experienced Linux user. I don't even want to talk about dd....

As for your network connection problems, a look at the network output of their three machines will help. It is known that Debian, according to its philosophy, does not ship non-free drivers. So, the user has to take care of it himself accordingly.

Finally, I would like to say that your problems with the installation of BL are not due to a bug in the installer. Sorry. smile

rbh · 2021-09-13 11:56:16

Len E. wrote:

In following up on your nomodeset recommendation,

It was @unklar, who recommended that, I merely reminded you.

I’ve stumbled onto a very clear definition of what the bug is, and a possibly-unreliable workaround.

You do not describe things so well... But it seems that you are having problems with ill configured ipv6 network. To disable ipv6 in install iso, add ”ipv6.disable=1” as boot parameter.

My Acer Netbook requires a USB-to-internet adapter

No, you are using an usb-nic (nic = Network interface card) if RJ-45 connected (cable) or usb wifi dongle.
I recommend you to download your PC's manuals from Acer and read them.

the original internet port no longer functions.

No, your built in Network hardware does not function. Your network is your lan (Local area network) and your lan has a gateway (a gw, your router, modem or..) to wan (Wide area network) or Internet. there is no such thing as an "Internet port".

When I attempted the install Lithium specifying the nomodeset kernel parameter, the installer had difficulty with the peculiar internet connection,

So, the screen no longer get blank, the installer continued longer than before?

was unable to complete it, and gave the option of cancelling the connection configuration altogether.

That problem should disapear if you disable ipv6.

On my Machine 2 described earlier in this post, I started the installer, and in
the last portion of the network configuration phase, I hit the cancel button.
My timing happened to be just right, because simultaneously there was
a network configuration complete message and the prompt to define the host name.
I was then able to complete the installation normally, and to my joy, found that
the internet connection on the installed Lithium 3 worked normally !

Ok, so you have now one good installation of BL. But, you do not know if the installation had proceeded without you hitting "cancel", as you have not tested to do that...

***************************************************************
My conclusion is that there is something not right in the installer process in the
transition from completion of the network configuration phase to the start of
the host name definition phase. If this can be corrected, all will be well.
****************************************************************

The only similar installer error described, is remedied with disabling ipv6. It conserns not only BL, but also Debian. The Debian installer is not coded by the BL-team. But, I am no6t convinced it need to be "fixed".

To address your queries about partition definitions, I’d like to explain how my terminal output printouts were prepared:

I did not ask you how you created the screendump, I asked "Have you partioned yourself, or have you kept the partition that was before you got it? Do you know what partition you installed to or is the table dumped before you installed?"
But you answer, gives me reason to an advice.

It is good to save hardware info of computer, in file on usb-stick or other safe place. But, very unnessecary to go your way.
Instead;

Mount the usb stick, lets say /dev/sdc1
Create infofile on usb-stick:

touch "/dev/sdc1/hw-info-dell#1-$(date +%F_%R).txt"

Redirect output of inxi, parted and dmidecode (dmidecode is not installed in live iso, but gives good info and is small addition to install) to the textfile on usb-stick:

$ inxi -Fxz >> /dev/sdc1/hw-info-dell#1-[TAB]
$ echo " "  >> /dev/sdc1/hw-info-dell#1-[TAB]
$ sudo parted -l >> /dev/sdc1/hw-info-dell#1-[TAB]
$ echo " "  >> /dev/sdc1/hw-info-dell#1-[TAB]
$ sudo dmidecode >> /dev/sdc1/hw-info-dell#1-[TAB]

Tab is to get autocompletion of file-name.

Last edited by rbh (2021-09-13 11:59:54)

Len E. · 2021-09-14 06:21:01

Hi unklar, rbh

I'd like to apologize to you both for wasting your time on this installation issue.
If I had been smart enough in the very beginning, I would have checked the recent bug
reports and come across the one entitled "BunsenLabs Lithium not installing", and
discovered that entries # 4 and # 15 contained EXACTLY the information I needed to
solve my problem.

[Dummy me: the correct placement of "ipv6.disable=1" in the grub menu entry is
just before --quiet, not after]

With this information in hand, I installed Lithium 3 on my Acer Netbook, removed the
dubious Lithium 3 installation on my Machine #2, and installed Lithium 3 on the
machine afresh in the proper way. Both installations work just fine.

In spite of wasting your time, I've gained from this exercise by learning about code
tags and balenaEtcher, both useful in going forward.

Thanks for everything !
Len E.

unklar · 2021-09-14 06:28:32

^Gladly! big_smile

rbh · 2021-09-14 07:27:16

Good!

Can you edit subjectline of your first post and prepend [Solved]?

damo · 2021-09-14 07:29:08

I edited the title and added "[SOLVED]" on your behalf wink NB it is something you can do yourself if you are the thread initiator smile

#1 2021-09-09 05:22:21

[SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#2 2021-09-09 06:50:21

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#3 2021-09-09 20:31:49

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#4 2021-09-09 23:35:43

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#5 2021-09-10 06:08:20

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#6 2021-09-10 08:28:28

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#7 2021-09-12 05:46:11

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#8 2021-09-12 08:59:46

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#9 2021-09-13 02:32:24

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#10 2021-09-13 07:24:14

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#11 2021-09-13 11:56:16

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#12 2021-09-14 06:21:01

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#13 2021-09-14 06:28:32

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#14 2021-09-14 07:27:16

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

#15 2021-09-14 07:29:08

Re: [SOLVED]Installer hangs up on Lithium 3 32-bit .iso

Board footer