(OLD) (ARCHIVED) Puppy Linux Discussion Forum

[bigpup]

HP Stream Laptop 14
Intel(R) Celeron(R) N4000 CPU @ 1.10GHz
4GB memory

Tried frugal install of ScPup-20.01+6-uefi-T.iso and ScPup64-20.01+6-T.iso

Both boot to a kernel panic not syncing and stop booting.

[mash]

Also kernel panic during boot.

HP Probook 6475b
AMD A10-5750M APU with Radeon(tm) HD Graphics

Frugal install and booting from USB sick.

I get kernel panic for every ScPup from 20.01+0. Last working is 19.09+0. Also tried building Slacko and BionicPup from latest Woof-CE. They're both failing to boot with the same kernel panic.

"Official" BionicPup 8.0 and Slacko 6.3.2 are booting without problem.

[peebee]

Thank you for reports. I obviously do not have these problems on the hardware I have available to test.....

Can people:
1. try an alternative kernel: https://sourceforge.net/projects/lxpup/files/Other/huge-kernels/

2. post output from System -> Pup-SysInfo -> Sys-Specs -> Base Report

3. try booting with nox and if get to console run xorgwizard to select different graphics drivers

I notice both problem reports are from HP systems.... but are there other commonalities - e.g. graphics type?

[ozsouth]

Tested HP Intel i3-5005u, HP Intel Celeron 1000M & HP AMD E2-9000e - All machines fine on ScPup64 20.01+2.

20.01+6 on the i3 (HD 5500 graphics) & Celeron (HD 2500 graphics) - using stock kernel & then my 5.4.27 kernel, no problems.

20.01+6 on the E2 (Radeon R2 graphics) using stock kernel, then my 5.4.27 kernel, & then
my 4.14.159 kernel, X wouldn't start - had to run xorgwizard & select modesetting.

Tried nomodeset in command line - X wouldn't start, with following error message:

Cannot access /sys/class/drm/card*/device/vendor
Usage basename FILE [SUFFIX]
Strip directory path and .SUFFIX from FILE

Another point - when I tried adding openssl 1.1.1g to ScPup64-19.06 & 20.01+2, had video issues.
Possibly unrelated, but Oscar Talks had issues with latest openssl using latest Netsurf, although gtk version suspected.

[mash]

Tried alternative kernels 4.19.13, 5.2.11 and 5.4.6 with no luck. Still the same kernel panic.
I attach my PupSysInfo.

I tried also to track breaking change. I know that ScPup 19.09 works and 20.01 don't.
As I was expected, Slacko64 6.9.9.9 - BUILD_FROM_WOOF='HEAD;12196cacc;2019-09-15 07:49:16 +1000' boots without problems.
Next randomly chosen builds Slacko64 6.9.9.9 - BUILD_FROM_WOOF='HEAD;13ab3443f;2019-11-01 23:08:30 +0800' and Slacko64 6.9.9.9 - BUILD_FROM_WOOF='HEAD;2a16b67d5;2019-10-20 09:01:22 +0800' are booting but xorg is failing with error:

[peebee]

These are the systems we should be considering:

ScPup32 System built on: Sat May 2 16:50:32 BST 2020
3ae78a543f5ba2fdb9a1bb7c2098d77d ScPup-20.01+6-T.iso
BUILD_FROM_WOOF='testing;291ac8276;2020-05-02 04:38:20 +1000'
kernel 4.14.160 32bit-pae
====================
ScPup64 System built on: Sat May 2 09:47:03 BST 2020
76edc3612a308d8925c973bedde62883 ScPup64-20.01+6-T.iso
BUILD_FROM_WOOF='testing;291ac8276;2020-05-02 04:38:20 +1000'
kernel 5.4.6 64bit
====================

"We" need to determine whether the problem comes from the kernel or Woof-CE or Slackware Current....

It might be useful if somebody with the problem could try the ScPup32 kernel in UPupEF32.....thanks
====================
UPupEF32 System built on: Sun May 24 11:32:11 BST 2020
2a572a9829a31571abad32ffad10a5bf UPupEF-20.04+3.iso
BUILD_FROM_WOOF='testing;f7dd416c3;2020-05-24 17:20:36 +1000'
kernel 4.14.176 32bit-pae

[peebee]

Can somebody with "the problem" please try 32-bit kernel 5.4.37 from Porteus:

http://www.smokey01.com/peebee/downloads/test/porteus-k5.4.37-scpup32.sfs - open the sfs and copy the 2 files to the ScPup32 frugal install folder. Reboot.

My HP550 laptop does boot ScPup32 with k4.14.160 however there are crash reports in dmesg.... these go away with the Porteus kernel..... clutching at straws ....

Thanks

[mash]

Still the same kernel panic for all mentioned kernels.
Kernel version seems not relevant. (maybe...)

If this might be helpful, I downloaded Slackware live distro https://slackware.nl/slackware-live/ and it boots without problems.

[bigpup]

[peebee]

Thanks for the tests.........

https://github.com/puppylinux-woof-CE/woof-CE/commits/testing/initrd-progs
shows the changes to initrd in recent times.......

ScPup = BUILD_FROM_WOOF='testing;291ac8276;2020-05-02 04:38:20 +1000'
so all commits should be included as at 2 May.....

I can't see anything that might be relevant to "the problem" - can anybody else?

So how to pursue?? Probably the first thing to do is to go back to:
ScPup-20.01+0-T.iso
which was:
BUILD_FROM_WOOF='testing;7890189c5;2019-12-28 08:51:15 +0100'

if "the problem" is not present in +0 - try the initrd from +0 with the other components from +6 ?

if the problem is seen in 20.01+0 we can step back to:
ScPup-19.09+7-uefi-T.iso
which has:
BUILD_FROM_WOOF='testing;5fc3e8fe3;2019-12-01 17:02:13 +1000'

Thanks!

[mash]

Yes, this is initrd with "the problem".

Although initrd from BUILD_FROM_WOOF='testing;7890189c5;2019-12-28 08:51:15 +0100' did not work in my case.

I had to go back to ScPup64-19.09+0-uefi-T.iso which is BUILD_FROM_WOOF='testing;12196cacc;2019-09-15 07:49:16 +1000'. Initrd from this ScPup boots without problems.

[gyro]

[peebee]

@mash & @bigpup

Please try a hybrid install - all the components from 20.01+6 but renamed:

[mash]

19.09+7 works. I already have been testing some other builds and have another one working BUILD_FROM_WOOF='HEAD;f53e2b980;2019-12-01 19:44:38 +1000'. It is from 1st December as yours test initrd.

I was renaming DISTRO_SPECS as gyro sugest. Simple

[mikeslr]