Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

READ-ONLY-MODE: PLEASE DO NOT POST NEW STUFF!
  New Forum: http://puppylinux.rockedge.org
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 11 Aug 2020, 14:55
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
ScPup & ScPup64 - Slackware Current based Woof-CE pups
Moderators: Flash, JohnMurga
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
Page 21 of 23 [335 Posts]   Goto page: Previous 1, 2, 3, ..., 19, 20, 21, 22, 23 Next
Author Message
gyro

Joined: 28 Oct 2008
Posts: 1799
Location: Brisbane, Australia

PostPosted: Fri 12 Jun 2020, 04:52    Post subject:  

peebee wrote:
64-bit kernel 5.7.2 has the suggested config changes:
http://murga-linux.com/puppy/viewtopic.php?p=1060596#1060596
I just compiled kernel 5.4.46 in ScPup64 with DOTconfig changes.
After the compile, I noticed that the produced DOTconfig contained an additional configuration set,
Code:
CONFIG_MISC_RTSX=y
I have attached 'DOTconfig-5.4.46-120620'.
I've also attached 'mmc.diff' which shows the changes that I now consider to be those required for mmc support, well at least a starting point that is better than our current kernel configs.
Using these changes, the resultant kernel should support "01micko"s Realtek mmc card reader, without any need to use 'initrdmodules',
as should my new 64-bit kernel 5.4.46.

gyro
mmc.diff.gz
Description  gunzip to produce file
gz

 Download 
Filename  mmc.diff.gz 
Filesize  515 Bytes 
Downloaded  26 Time(s) 
DOTconfig-5.4.46-120620.gz
Description  gunzip to produce file
gz

 Download 
Filename  DOTconfig-5.4.46-120620.gz 
Filesize  47.84 KB 
Downloaded  30 Time(s) 
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1799
Location: Brisbane, Australia

PostPosted: Fri 12 Jun 2020, 06:19    Post subject:  

I've uploaded 'huge-5.4.46-gyro-64.tar.bz2' to http://www.mediafire.com/folder/21fyvbi4xglau/kernels, for ScPup64.

This kernel package does not contain any firmware, it requires the presence of an fdrv...sfs.

gryo

Last edited by gyro on Fri 12 Jun 2020, 15:16; edited 1 time in total
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1799
Location: Brisbane, Australia

PostPosted: Fri 12 Jun 2020, 15:15    Post subject:  

I've uploaded 'huge-4.14.184-gyro-pae.tar.bz2' to http://www.mediafire.com/folder/21fyvbi4xglau/kernels, for ScPup.

This kernel package does not contain any firmware, it requires the presence of an fdrv...sfs.

This kernel provides much improved mmc support, the equivalent of 'huge-5.4.46-gyro-64.tar.bz2'.

Note that the kernel config variables required for Realtek support are slightly different between kernel v4 and kernel v5.

gyro
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 13981
Location: S.C. USA

PostPosted: Fri 12 Jun 2020, 15:52    Post subject:  

01micko wrote:
@bigpup and @mash.. just before the prompt doesn't it say "To save debug info to a partition, type 'debugsave'" Question '

Do it and post the results (just zip up the resulting directory on your drive)

DISCLAIMER: probably doesn't support nvme type drives

Using the initrd.gz that only boots to a prompt.
I see this:
Loading vmlinuz
Loading initrd.gz
stops at a prompt

Type debugsave
Get a bunch of errors about stuff not being found.
Ends with no partitions found.
So, I cannot provide debugsave info.

I tried this with the original initrd.gz that is in ScPup64 20.01.
This boots to point of kernel loading, but stops with bunch of error messages and kernel panic.
No prompt provided.
So, cannot provide debugsave.

Bionicpup64 8.0 boots OK.

ScPup64 20.01 using the the initrd.gz from ScPup64 19.09+0-uefi-T.iso boots OK.


The boot loader, is the UEFI boot loader, installed by Frugalpup Installer.
Secure boot is enabled in the UEFI bios.

This is the drive I am using.
Screenshot.png
 Description   
 Filesize   62.15 KB
 Viewed   280 Time(s)

Screenshot.png


_________________
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
YaPI(any iso installer)
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Fri 12 Jun 2020, 16:29    Post subject:  

@bigpup if you plug in a usb stick you might be able to save the debug logs on that.

Also try @gyro's kernel and init script. (edit.. gyro's init wont work.. see below for explanation)

Your drive is indicated as gpt via that screen shot which explains the kernel panic as fdisk will error because it only supports mbr so init stops and boot can't go on which confirms my initial hunch.

The problem I now face is that I either have to do an early init check on the partition type or find a utility other than fdisk to check the partition sizes in the init function check_resize_part().

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
bigpup


Joined: 11 Oct 2009
Posts: 13981
Location: S.C. USA

PostPosted: Fri 12 Jun 2020, 16:52    Post subject:  

OK.

But Booting Bionicpup64 8.0
I see information about e2fsck doing a check and giving the results of that check.
e2fsck 1.44.1 (24-Mar-2018)
The boot process continues as a normal boot to working desktop.

Same e2fsck checking drive information, with results.
Booting ScPup64 20.01, using the the initrd.gz from ScPup64 19.09+0-uefi-T.iso.
e2fsck 1.45.6 (20-Mar-2020)
It also boots OK.

_________________
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
YaPI(any iso installer)
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Fri 12 Jun 2020, 17:31    Post subject:  

bigpup wrote:
OK.

But Booting Bionicpup64 8.0
I see information about e2fsck doing a check and giving the results of that check.
e2fsck 1.44.1 (24-Mar-2018)
The boot process continues as a normal boot to working desktop.

Same e2fsck checking drive information, with results.
Booting ScPup64 20.01, using the the initrd.gz from ScPup64 19.09+0-uefi-T.iso.
e2fsck 1.45.6 (20-Mar-2020)
It also boots OK.


fsck just checks filesystems, it doesn't care about partitioning.

I have an init script for you to try.

For the record it is a simple check with fdisk (which won't error, just skip the offending code) to see if we have a GPT partition.

It works before any of the probedisk log checks.

Code:
--- init   2020-05-31 11:46:29.210999690 +1000
+++ /root/spot/init   2020-06-13 07:22:03.702212647 +1000
@@ -667,6 +667,7 @@ umount_unneeded() {
 
 check_resize_part() { #must be fast, no partitions can be mounted, can't work out pupmode at this stage
  DEVICE=/dev/mmcblk0 # sd card only for now
+ fdisk -l $DEVICE | grep -qm1 "using GPT" && return
  grep "$DEVICE" /tmp/probedisk.log | grep -q 'card' || return
  FS=`grep "$DEVICE" /tmp/probepart.log | tail -n1 | cut -f 2 -d '|'`
  case $FS in


I'll attached the file as a tar. Untar and insert it into your initrd-expanded overwriting the init script and repack the initrd.gz
init.tar
Description  untar and pack it up in initrd.gz
tar

 Download 
Filename  init.tar 
Filesize  50 KB 
Downloaded  26 Time(s) 

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
bigpup


Joined: 11 Oct 2009
Posts: 13981
Location: S.C. USA

PostPosted: Fri 12 Jun 2020, 17:57    Post subject:  

OK, I will try it.

I was looking at fdisk information.
Quote:
fdisk supports GPT since util-linux 2.23

util-linux
https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/

_________________
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
YaPI(any iso installer)
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Fri 12 Jun 2020, 18:53    Post subject:  

Thanks bigpup

In the meantime, I found the source of @mash 's bug!

A stupid assumption grepping for GB! Embarassed I've put in code for KB|MB|GB and that will fix it. I tested on a 8GB card which in fdisk shows up at ~8000MB. I tested with KB too because (and I don't know, but it doesn't hurt to add) smaller cards do have the possibility I guess as showing up in KB.

I'm going to commit the changes to woof-ce.

I'm still hoping your machine boots bigpup because that code shouldn't be reached at all when your machine boots.

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
bigpup


Joined: 11 Oct 2009
Posts: 13981
Location: S.C. USA

PostPosted: Fri 12 Jun 2020, 19:04    Post subject:  

OK.

Do you have a newer initrd.gz to try or do you want me to still try what you posted above?

_________________
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
YaPI(any iso installer)
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Fri 12 Jun 2020, 19:23    Post subject:  

Give me a few minutes bigpup and I'll upload an initrd.gz

I'm using gyro's kernel 5.4.46 and the init I'm going to commit to woof in slacko64-6.9.9.10. My reason is to exclude that it was a scpup issue. Now I'll be using scpup64 when I update the initrd.gz.. is that ok for you?

EDIT:

I've uploded an initrd.gz for scpup64

http://01micko.com/packages/initrd.gz

Code:
# md5sum initrd.gz
c68615601ab676ade73a3c0eab774cba  initrd.gz


Make sure to change kernels to gyros, however you may need a wireless driver compiled, but it is needed for a thorough test.

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
bigpup


Joined: 11 Oct 2009
Posts: 13981
Location: S.C. USA

PostPosted: Fri 12 Jun 2020, 22:48    Post subject:  

01micko wrote:
I have an init script for you to try.

For the record it is a simple check with fdisk (which won't error, just skip the offending code) to see if we have a GPT partition.

It works before any of the probedisk log checks.

I'll attached the file as a tar. Untar and insert it into your initrd-expanded overwriting the init script and repack the initrd.gz

Before seeing your last post. I tried this init.
It boots OK to working desktop.

Now, I will try the new kernel and initrd.gz you now offer.

I got to delete some of these hacked initrd.gz's.
I am starting to get confused on which one to use Rolling Eyes Laughing Laughing

_________________
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
YaPI(any iso installer)
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 13981
Location: S.C. USA

PostPosted: Fri 12 Jun 2020, 23:23    Post subject:  

01micko wrote:
Give me a few minutes bigpup and I'll upload an initrd.gz

I'm using gyro's kernel 5.4.46 and the init I'm going to commit to woof in slacko64-6.9.9.10. My reason is to exclude that it was a scpup issue. Now I'll be using scpup64 when I update the initrd.gz.. is that ok for you?

EDIT:

I've uploded an initrd.gz for scpup64

http://01micko.com/packages/initrd.gz

Code:
# md5sum initrd.gz
c68615601ab676ade73a3c0eab774cba  initrd.gz


Make sure to change kernels to gyros, however you may need a wireless driver compiled, but it is needed for a thorough test.

Did this changing kernel to 5.4.46 and using this initrd.gz.

This boots, with no problem, to working desktop! Very Happy

Note to 01micko:
Your change_kernels program.
http://www.murga-linux.com/puppy/viewtopic.php?t=101144
Could you please edit the information on the main window.
It is confusing.
It needs to just say the vmlinuz and zdrv sfs or kernel-modules sfs need to come from the new kernel package.
Only stuff from new kernel go into the input slots.

I have had to explain, to many people trying to use this, to only input stuff from new kernel package.

Really nice and easy to use, when you understand this.

Thanks very much for coding it!!! Very Happy Very Happy

PS:
This Hp Stream 14 laptop is very new hardware.
So, the newer the kernel, probably the better.

_________________
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
YaPI(any iso installer)
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Sat 13 Jun 2020, 18:09    Post subject:  

bigpup, I'm presently doing an overhaul of change_kernels with support for just dragging the whole tarball to a window as well as retaining the old method. It will also support changing /usr/lib64 to /usr/lib for deb based distros in the zdrive.
_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
mash

Joined: 18 Dec 2017
Posts: 14

PostPosted: Sat 13 Jun 2020, 18:46    Post subject:  

Quote:
Give me a few minutes bigpup and I'll upload an initrd.gz

I'm using gyro's kernel 5.4.46 and the init I'm going to commit to woof in slacko64-6.9.9.10. My reason is to exclude that it was a scpup issue. Now I'll be using scpup64 when I update the initrd.gz.. is that ok for you?

EDIT:

I've uploded an initrd.gz for scpup64

http://01micko.com/packages/initrd.gz

Code:
# md5sum initrd.gz
c68615601ab676ade73a3c0eab774cba initrd.gz


Make sure to change kernels to gyros, however you may need a wireless driver compiled, but it is needed for a thorough test.


This init works for me too. Either with gyro's or with original lxpup kernel.

Quote:
In the meantime, I found the source of @mash 's bug!

A stupid assumption grepping for GB! Embarassed I've put in code for KB|MB|GB and that will fix it. I tested on a 8GB card which in fdisk shows up at ~8000MB. I tested with KB too because (and I don't know, but it doesn't hurt to add) smaller cards do have the possibility I guess as showing up in KB.


My problem was also GPT partitioning I believe. If I look at fdisk output there are `GiB` used, so your regexp should take this into consideration too? Or maybe it doesn't matter?

Quote:
Type debugsave
Get a bunch of errors about stuff not being found.
Ends with no partitions found.
So, I cannot provide debugsave info.


Yes, had the same result. Done some random guessing looking at `/sbin` directory and you have to run `usablefs` before `debugsave`. But I think it is not needed anymore.

I will try new Woof-CE build tomorrow.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 21 of 23 [335 Posts]   Goto page: Previous 1, 2, 3, ..., 19, 20, 21, 22, 23 Next
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1777s ][ Queries: 12 (0.0500s) ][ GZIP on ]