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!
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile       

The time now is Tue 11 Aug 2020, 09:50
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
ScPup & ScPup64 - Slackware Current based Woof-CE pups
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 20 of 23 [335 Posts]   Goto page: Previous 1, 2, 3, ..., 18, 19, 20, 21, 22, 23 Next
Author Message
bigpup


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

PostPosted: Thu 11 Jun 2020, 01:03    Post subject:  

perdido wrote:
Hi bigpup,

Compiled a driver in scpup64 kernel 5.4.6 from sources at https://github.com/mid-kid/r8822be

I stuck it here http://ibm-pc.org/puppy/scpup64/k5.4.6/RTL8822BE/r8822be.ko
It needs firmware rtl8822befw.bin

No idea if it will work as I don't have a device with that chipset.

Thanks for compiling the driver!!
I just have not tried using it, yet Embarassed

_________________
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 
gyro

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

PostPosted: Thu 11 Jun 2020, 03:27    Post subject:  

peebee wrote:
Do you know what kernel config is needed?
While the kernel panic issue does not seem to be an "mmc module issue", there is an "mmc module issue" in that "01micko" had to resort to using the 'initrdmdules' utility and the 'initrdmdules' patch to the 'init' script to do his tests.

A place to start with the "mmc module issue" would be to recompile the kernel with a modified 'DOTconfig':
The basic idea is; In the section headed "# MMC/SD/SDIO Host Controller Drivers", replace every "=m" with "=y".

Although this could be slightly modified based on BK's 'DOTconfig-5.4.12'.

BK's 'DOTconfig-5.4.12' leaves the following as modules:
Code:
CONFIG_MMC_REALTEK_PCI=m
CONFIG_MMC_REALTEK_USB=m
At least 1 of these represents a moudle already mentioned in this forum topic, so I suggest changing these to "=y".

BK's 'DOTconfig-5.4.12' also leaves the following unset:
Code:
# CONFIG_MMC_RICOH_MMC is not set
# CONFIG_MMC_SDHCI_F_SDH30 is not set
# CONFIG_MMC_ALCOR is not set
# CONFIG_MMC_SPI is not set
So probably these could be left unset.

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

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

PostPosted: Thu 11 Jun 2020, 04:00    Post subject:  

bigpup wrote:
On my Hp Stream 14

I am booting from an emmc drive.
It is the internal drive for this computer.

I am using the 5.4.6 kernel that comes in ScPup64 20.01

Have to use a different older initrd.gz to get it to boot.

The initrd.gz in ScPup64 20.01 causes kernel panic.
Obviously the drivers for your emmc haredware are builtin to the default kernel, others are not so fortunate.

I have attached a test 'init' script that contains the line:
Code:
#  /sbin/resize_part $FS
so it will never try to do the actual partition resize.
The idea is to identify if the issue is related to the code in the actual 'init' script or the code in '/sbin/resize_part'.
Could you please, replace the 'init' script in the release 'initrd.gz' with this test 'init' script, and reboot using this "patched" 'initrd.gz'.

gyro
init.gz
Description  gunzip to produe 'init' script.
gz

 Download 
Filename  init.gz 
Filesize  14.18 KB 
Downloaded  25 Time(s) 
Back to top
View user's profile Send private message 
gyro

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

PostPosted: Thu 11 Jun 2020, 05:41    Post subject:  

I've attached another test 'init' script.

This one uses a different method of parsing the output from "fdisk -l".

gyro
init.gz
Description  gunzip to produce 'init' script
gz

 Download 
Filename  init.gz 
Filesize  14.18 KB 
Downloaded  22 Time(s) 
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 4391
Location: Worcestershire, UK

PostPosted: Thu 11 Jun 2020, 08:31    Post subject:  

gyro wrote:
A place to start with the "mmc module issue" would be to recompile the kernel with a modified 'DOTconfig':

64-bit kernel 5.7.2 has the suggested config changes:
http://murga-linux.com/puppy/viewtopic.php?p=1060596#1060596

_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
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: Thu 11 Jun 2020, 11:35    Post subject:  

gyro wrote:
bigpup wrote:
On my Hp Stream 14

I am booting from an emmc drive.
It is the internal drive for this computer.

I am using the 5.4.6 kernel that comes in ScPup64 20.01

Have to use a different older initrd.gz to get it to boot.

The initrd.gz in ScPup64 20.01 causes kernel panic.
Obviously the drivers for your emmc haredware are builtin to the default kernel, others are not so fortunate.

I have attached a test 'init' script that contains the line:
Code:
#  /sbin/resize_part $FS
so it will never try to do the actual partition resize.
The idea is to identify if the issue is related to the code in the actual 'init' script or the code in '/sbin/resize_part'.
Could you please, replace the 'init' script in the release 'initrd.gz' with this test 'init' script, and reboot using this "patched" 'initrd.gz'.

gyro


Did not boot.
Only got to point of loading the kernel and stopped,

No kernel panic, but stopped with only something looking like the process stopped.

_________________
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: Thu 11 Jun 2020, 11:46    Post subject:  

gyro wrote:
I've attached another test 'init' script.

This one uses a different method of parsing the output from "fdisk -l".

gyro


No boot.
Stopped at loading kernel.
No kernel panic, but stopped with only something looking like the process stopped.

_________________
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 
gyro

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

PostPosted: Thu 11 Jun 2020, 12:08    Post subject:  

@bigpup,
Thanks for testing.
Unfortunately the result is a little confusing. I had expected that either of those 'init' scripts would have either worked, or produced the kernel panic.

gyro

Last edited by gyro on Thu 11 Jun 2020, 12:20; 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: Thu 11 Jun 2020, 12:17    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've had a look at this kernel package, while it should solve the "mmc module issue" for my Lenovo, I don't think it will do the same for "01micko"s test machine, I think it might also need:
Code:
CONFIG_MISC_RTSX_PCI=y
CONFIG_MMC_REALTEK_PCI=y

I intend to actually try this new kernel on my Lenovo, as soon as I can.

Later edit: Your kernel 5.7.2 worked fine on my Lenovo, both the internal mmc device (mmcblk1) and the mmc sdcard (mmcblk2) were seen by the 'init' script wihout any kernel modules being involved.

gyro

Last edited by gyro on Thu 11 Jun 2020, 13:03; 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: Thu 11 Jun 2020, 12:28    Post subject:  

01micko wrote:
The only thing I can think of is to set a boot parameter to specify if a partition needs resizing. It does work, am booting from the sdcard right now.
Does it work both, when you specify that a partition needs resizing, and when you don't?

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

Joined: 18 Dec 2017
Posts: 14

PostPosted: Thu 11 Jun 2020, 15:50    Post subject:  

@gyro

Both init scripts dropped me to the prompt at boot. I think this is the same point as bigpup wrote.
Back to top
View user's profile Send private message 
bigpup


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

PostPosted: Thu 11 Jun 2020, 22:57    Post subject:  

mash wrote:
@gyro

Both init scripts dropped me to the prompt at boot. I think this is the same point as bigpup wrote.

The same for me.
I was not sure that was actually a prompt it stopped at.
So, I just said stopped.

_________________
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, 02:48    Post subject:  

@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

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


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Fri 12 Jun 2020, 02:59    Post subject:  

@gyro, I didn't test with the presize param set, I would expect to get the kernel panic. I'll attach the init I used and @mash and @bigpup can test it too, without changing boot options.

A thought did occur to me. If the mmc/sd/whatever drive is formatted gpt then fdisk will fail, probably critically.
init.gz
Description  THIS IS NOT an initrd. Replace the init script in your initrd.gz with this script.
This is real gzip file. (.gz)
gz

 Download 
Filename  init.gz 
Filesize  14.35 KB 
Downloaded  23 Time(s) 

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

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

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

01micko wrote:
A thought did occur to me. If the mmc/sd/whatever drive is formatted gpt then fdisk will fail, probably critically.
Hmmm...it could be that the code in 'init' is working too well, after your commit.
Maybe folk who have a problem, also have an "mmcblk0" that can be seen by the 'init' script.

At least you have your own test bed, unfortunately my Lenovo, won't even recognise the micro SD card as a boot device, even though I can successfully boot from it when it is inserted in a usb stick adapter and plug it in as a usb stick.

gyro
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 20 of 23 [335 Posts]   Goto page: Previous 1, 2, 3, ..., 18, 19, 20, 21, 22, 23 Next
Post new topic   Reply to topic 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.0861s ][ Queries: 12 (0.0336s) ][ GZIP on ]