Booting problem of Porteus LXQT from USB memory

Post here if you are a new Porteus member and you're looking for some help.
lin_newbie
White ninja
White ninja
Posts: 4
Joined: 24 Sep 2021, 11:52
Distribution: Porteus

Booting problem of Porteus LXQT from USB memory

Post#1 by lin_newbie » 24 Sep 2021, 13:04

Dear Members;

Good day, I booted Porteus LXQT from USB on a laptop and on an old desktop. Desktop booted without any problem but laptop didn't boot.

When you choose the graphic mode everything went well until one moment. The boot reached to a black screen with mouse cursor but nothing happens after that.You cannot move the cursor.Basically you are just stuck at there.

For your information, laptop also has dual boot Kali/Windows. Porteus LXQT version is v5.0rc3-x86_64. Of course my laptop is 64 bit.

What seems to be the problem? Graphics card or something else?

User avatar
Bicephale
Full of knowledge
Full of knowledge
Posts: 111
Joined: 28 Dec 2010, 19:10
Distribution: Live CDs
Location: Quebec/Qc, Canada

Booting problem of Porteus LXQT from USB memory

Post#2 by Bicephale » 24 Sep 2021, 15:41

Here's a wild reaction not really grounded in anything but some impression: for example is it an eMMC drive accessed via i2C??

:unknown:

lin_newbie
White ninja
White ninja
Posts: 4
Joined: 24 Sep 2021, 11:52
Distribution: Porteus

Booting problem of Porteus LXQT from USB memory

Post#3 by lin_newbie » 28 Sep 2021, 19:48

Bicephale wrote:
24 Sep 2021, 15:41
Here's a wild reaction not really grounded in anything but some impression: for example is it an eMMC drive accessed via i2C??

:unknown:
Dear Bicephale, I'm sorry but I do not know what does it mean? eMMC drive accessing via i2C? By the way, also the so called destktop is a i386 computer. How does it even possible?

Best Regards

User avatar
Bicephale
Full of knowledge
Full of knowledge
Posts: 111
Joined: 28 Dec 2010, 19:10
Distribution: Live CDs
Location: Quebec/Qc, Canada

Booting problem of Porteus LXQT from USB memory

Post#4 by Bicephale » 28 Sep 2021, 22:16

Hello.

I didn't notice you got a '386 CPU but one of my machines is as "old" as i can personally tolerate already and it's actually compatible with "i586" (32 bits) flavours of Linux, in my case for an Acer LapTop having only USB2... These days i tend to avoid anything this much "legacy", one hard lesson of evolution for me now is to just say NO if SATA3/USB3 are missing, since that would be a fair approximative hint of age and it turns out BiOSes got shaped by the passage of time as well. In short, i vaguely remember dealing with USB was frustrating until USB3 arrived, m'well...

eMMC is the type of technology behind the main permanent storage media of my CherryTrail 32/64 (hybrid) UEFi-ONLY LapTop, the Acer one belonging to the BiOS era instead, while GPT was added to the alphabet soup when i wasn't paying enough attention! Euh... Let see.

Ha, by the way... It turns out i downloaded 'fossapup64-9.5.iso' (Puppy Linux) and verified the presence of 'bootia32.efi' in '/EFI/boot'. It was there so this was worth flashing on a 1 GB SD unit - the smaller i could find on my desk... That flavour of Linux weights only 4M28 bytes and yet 'HardInfo' happens to be readily accessible, which is how i can now provide some details right here to address a most relevant question, considering this can interfere with a successful evaluation (imagine the rest!):

Code: Select all

Searching for "SPi"...

intel_spi_platform:  Intel PCH/PCU SPI flash platform driver
intel_spi:  Intel PCH/PCU SPI flash core driver
spi_nor:  framework for SPI NOR
spi_pxa2xx_platform:  PXA2xx SSP SPI Controller
i2c_algo_bit:  I2C-Bus bit-banging algorithm
silead:  Silead I2C touchscreen driver
axp20x_i2c:  PMIC MFD I2C driver for AXP20X
axp20x:  PMIC MFD core driver for AXP20X
i2c_multi_instantiate:  I2C multi instantiate pseudo device driver
spi_pxa2xx_platform:  PXA2xx SSP SPI Controller

Searching for "ACPi"

battery:  ACPI Battery Driver {ACPI Non-volatile Storage}
int3403_thermal:  ACPI INT3403 thermal driver
acpi_thermal_rel:  Intel acpi thermal rel misc dev driver
acpi_pad:  ACPI Processor Aggregator Driver
sdhci_acpi:  Secure Digital Host Controller Interface ACPI driver

Additional details previously gathered from HardInfo provided by Linux Mint (v18.3 Sylvia):

fdp_i2c		: I2C driver for Intel Fields Peak NFC controller
i2c_designware_platform		: Synopsys DesignWare I2C bus adapter
i2c_designware_core		: Synopsys DesignWare I2C bus adapter core
i2c_algo_bit		: I2C-Bus bit-banging algorithm
i2c_hid		: HID over I2C core driver
mmc_block		: Multimedia Card (MMC) block device driver
There's also additional information found in '/var/vlog/dmesg' or similar, if i'm not mistaking. Yet i can add somewhat more global details corresponding to the evolution period, for example:

Intel Atom "Cherrytrail" 64 bits Quad CPU @ 1.44 GHz
2 GB DDR memory
32 GB eMMC mass-storage
128 GB (max.) SD(HC) Flash-Card reader
Dual Band a/b/g/n/AC WiFi with BT4-LE

The most obvious aspect being that this is a 2016 BiOS. So a bootable "Live" Linux may prove successful on that tablet and still fail on the older Acer, one of my argumention point having to do with such data collection, because Puppy Linux did seem to lack a few device drivers indeed and the Mint capture suggests those devices were installed and possibly ready. Impair "i2C" and/or "SPi" support, whatever, and trouble shall occur automatically...

Often enough our primary goal is to get an .ISO that "works" (hence for this it's got to boot 1st...), then lets start from there with some hardware profilers as 'HardInfo' to confirm what works, and hopefully provide hints to continue searching what's broken. Judging from my present example i'd say Linux Mint was better suited, though i equally recall it felt slower/heavier in practice - which would be a context where i'd wish Porteus to kick in - and it is not!

Once a hardware configuration is known such data should serve to generate custom-made .ISOs "on-demand" to ensure at least all device drivers have been loaded, instead of expecting a person to fix the problem as if we were all working for the NASA... All speaking ENGLISH using US keyboards!!

So, good luck reaching your goal long before landing on the moon! Fingers crossed. :thumbsup:


P.S.: 'APorteus' DOES have 'HardInfo' waiting & ready, not to mention even with the display resolution set wrong it may remain accessible... Which i'd optimize to add value. My 2 cents! Please consider trying 'Linuxium' too if your 386 is actually an hybrid as mine.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Booting problem of Porteus LXQT from USB memory

Post#5 by ncmprhnsbl » 29 Sep 2021, 14:25

lin_newbie wrote:
24 Sep 2021, 13:04
What seems to be the problem? Graphics card or something else?
hi lin_newbie, it could be, but without some clues about what graphics hardware you have, i can only guess.. which would be as useful as Bicephale's rambling, tangential, offtopic posts. ie. not very.
in kali, if you could do in terminal(probly as root):

Code: Select all

lspci | grep -i vga
and post that here..
another thing to try:
boot porteus> choose "Text Mode" from the boot menu > log in guest (password: guest) > then try: startx and see if the same thing happens.. if so, try switching tty(Ctrl+Alt+F1)
if this fails try Ctrl+Alt+PrintSc+o to try to shutdown..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Bicephale
Full of knowledge
Full of knowledge
Posts: 111
Joined: 28 Dec 2010, 19:10
Distribution: Live CDs
Location: Quebec/Qc, Canada

Booting problem of Porteus LXQT from USB memory

Post#6 by Bicephale » 30 Sep 2021, 07:22

ncmprhnsbl wrote:
29 Sep 2021, 14:25
...Bicephale's rambling, tangential, offtop posts.
I told you before i think just to remove the credentials but that request was rejected like the rest.

Chop! Chop! Chop! :thumbdown:

lin_newbie
White ninja
White ninja
Posts: 4
Joined: 24 Sep 2021, 11:52
Distribution: Porteus

Booting problem of Porteus LXQT from USB memory

Post#7 by lin_newbie » 03 Oct 2021, 20:04

Bicephale wrote:
28 Sep 2021, 22:16
Hello.

I didn't notice you got a '386 CPU but one of my machines is as "old" as i can personally tolerate already and it's actually compatible with "i586" (32 bits) flavours of Linux, in my case for an Acer LapTop having only USB2... These days i tend to avoid anything this much "legacy", one hard lesson of evolution for me now is to just say NO if SATA3/USB3 are missing, since that would be a fair approximative hint of age and it turns out BiOSes got shaped by the passage of time as well. In short, i vaguely remember dealing with USB was frustrating until USB3 arrived, m'well...

eMMC is the type of technology behind the main permanent storage media of my CherryTrail 32/64 (hybrid) UEFi-ONLY LapTop, the Acer one belonging to the BiOS era instead, while GPT was added to the alphabet soup when i wasn't paying enough attention! Euh... Let see.

Ha, by the way... It turns out i downloaded 'fossapup64-9.5.iso' (Puppy Linux) and verified the presence of 'bootia32.efi' in '/EFI/boot'. It was there so this was worth flashing on a 1 GB SD unit - the smaller i could find on my desk... That flavour of Linux weights only 4M28 bytes and yet 'HardInfo' happens to be readily accessible, which is how i can now provide some details right here to address a most relevant question, considering this can interfere with a successful evaluation (imagine the rest!):

Code: Select all

Searching for "SPi"...

intel_spi_platform:  Intel PCH/PCU SPI flash platform driver
intel_spi:  Intel PCH/PCU SPI flash core driver
spi_nor:  framework for SPI NOR
spi_pxa2xx_platform:  PXA2xx SSP SPI Controller
i2c_algo_bit:  I2C-Bus bit-banging algorithm
silead:  Silead I2C touchscreen driver
axp20x_i2c:  PMIC MFD I2C driver for AXP20X
axp20x:  PMIC MFD core driver for AXP20X
i2c_multi_instantiate:  I2C multi instantiate pseudo device driver
spi_pxa2xx_platform:  PXA2xx SSP SPI Controller

Searching for "ACPi"

battery:  ACPI Battery Driver {ACPI Non-volatile Storage}
int3403_thermal:  ACPI INT3403 thermal driver
acpi_thermal_rel:  Intel acpi thermal rel misc dev driver
acpi_pad:  ACPI Processor Aggregator Driver
sdhci_acpi:  Secure Digital Host Controller Interface ACPI driver

Additional details previously gathered from HardInfo provided by Linux Mint (v18.3 Sylvia):

fdp_i2c		: I2C driver for Intel Fields Peak NFC controller
i2c_designware_platform		: Synopsys DesignWare I2C bus adapter
i2c_designware_core		: Synopsys DesignWare I2C bus adapter core
i2c_algo_bit		: I2C-Bus bit-banging algorithm
i2c_hid		: HID over I2C core driver
mmc_block		: Multimedia Card (MMC) block device driver
There's also additional information found in '/var/vlog/dmesg' or similar, if i'm not mistaking. Yet i can add somewhat more global details corresponding to the evolution period, for example:

Intel Atom "Cherrytrail" 64 bits Quad CPU @ 1.44 GHz
2 GB DDR memory
32 GB eMMC mass-storage
128 GB (max.) SD(HC) Flash-Card reader
Dual Band a/b/g/n/AC WiFi with BT4-LE

The most obvious aspect being that this is a 2016 BiOS. So a bootable "Live" Linux may prove successful on that tablet and still fail on the older Acer, one of my argumention point having to do with such data collection, because Puppy Linux did seem to lack a few device drivers indeed and the Mint capture suggests those devices were installed and possibly ready. Impair "i2C" and/or "SPi" support, whatever, and trouble shall occur automatically...

Often enough our primary goal is to get an .ISO that "works" (hence for this it's got to boot 1st...), then lets start from there with some hardware profilers as 'HardInfo' to confirm what works, and hopefully provide hints to continue searching what's broken. Judging from my present example i'd say Linux Mint was better suited, though i equally recall it felt slower/heavier in practice - which would be a context where i'd wish Porteus to kick in - and it is not!

Once a hardware configuration is known such data should serve to generate custom-made .ISOs "on-demand" to ensure at least all device drivers have been loaded, instead of expecting a person to fix the problem as if we were all working for the NASA... All speaking ENGLISH using US keyboards!!

So, good luck reaching your goal long before landing on the moon! Fingers crossed. :thumbsup:


P.S.: 'APorteus' DOES have 'HardInfo' waiting & ready, not to mention even with the display resolution set wrong it may remain accessible... Which i'd optimize to add value. My 2 cents! Please consider trying 'Linuxium' too if your 386 is actually an hybrid as mine.
Dear Bicephale;

Thank you very much for your comments. I have to say I'm a complete beginner to this scene and what you have written so far is hard to understand for me, so please give me some time to get them. Last week -somehow- I put OpenBSD to that old desktop and downloaded i586 version of Porteus to my usb stick and using it live. My main goal is completely leaving microsoft products. I will try my chance using porteus on that 64bit laptop for the sake of solving the problem.

lin_newbie
White ninja
White ninja
Posts: 4
Joined: 24 Sep 2021, 11:52
Distribution: Porteus

Booting problem of Porteus LXQT from USB memory

Post#8 by lin_newbie » 03 Oct 2021, 20:07

ncmprhnsbl wrote:
29 Sep 2021, 14:25
lin_newbie wrote:
24 Sep 2021, 13:04
What seems to be the problem? Graphics card or something else?
hi lin_newbie, it could be, but without some clues about what graphics hardware you have, i can only guess.. which would be as useful as Bicephale's rambling, tangential, offtop posts. ie. not very.
in kali, if you could do in terminal(probly as root):

Code: Select all

lspci | grep -i vga
and post that here..
another thing to try:
boot porteus> choose "Text Mode" from the boot menu > log in guest (password: guest) > then try: startx and see if the same thing happens.. if so, try switching tty(Ctrl+Alt+F1)
if this fails try Ctrl+Alt+PrintSc+o to try to shutdown..
Dear ncmprhnsbl;

Thank you for your comment. I will do accordingly.

User avatar
Bicephale
Full of knowledge
Full of knowledge
Posts: 111
Joined: 28 Dec 2010, 19:10
Distribution: Live CDs
Location: Quebec/Qc, Canada

Booting problem of Porteus LXQT from USB memory

Post#9 by Bicephale » 04 Oct 2021, 03:04

Good luck! :good:

Post Reply