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

This forum can also be accessed as http://oldforum.puppylinux.com
It is now read-only and serves only as archives.

Please register over the NEW forum
https://forum.puppylinux.com
and continue your work there. Thank you.

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups    
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 22 Jan 2021, 11: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 19 of 23 [335 Posts]   Goto page: Previous 1, 2, 3, ..., 17, 18, 19, 20, 21, 22, 23 Next
Author Message
bigpup


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

PostPosted: Mon 08 Jun 2020, 19:18    Post subject:  

On my HP Stream 14
Having a SD card plugged in or not has no affect.
But, I do need the different initrd.gz to get it to boot.

ScPup64 20.01 is frugal install on internal emmc drive.

_________________
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: Tue 09 Jun 2020, 02:35    Post subject:  

mash wrote:
OK, I think I got it. This post should be prepended by Jean-Luc Picard's facepalm.

"The problem" exists only in some circumstances which I describe. I am curious if anyone of you tried to boot from SD card and succeeded because my SD card and/or reader was the case of the problem.

So, the problem exists only on my HP Probook machine that I boot in UEFI native mode and only if I insert SD card before/during boot. Since I use that card to store big SFS files it is almost always present in my built-in reader.

HP Probooks are known to have a little bit faulty UEFI firmware - e.g. you cannot boot from SD card in UEFI mode even if you set it in UEFI/BIOS settings.

Actually reverting this commit: https://github.com/puppylinux-woof-CE/woof-CE/commit/8eb6e1eb9333de396e2a76ccbee745ce73f08d0b (just edited initrd manually as 01micko wrote) makes problem disappear. So, not waiting text but grep -> tail piping (?).

So for me there are 2 workarounds:
1. remove SD card when booting
2. edit initrd manually from some working puppy

Thanks peebee and 01micko for directing me.


Well maybe my commit is buggy! That shouldn't happen so either I revert the commit or put in further tests to make sure we booted off the particular device. Latter is the real solution.

The facility in question was intended to support usb stick installs also, with a look to the future that possibly more puppy distros may be shipped as image files rather than, or as well as, iso files.

_________________
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: Tue 09 Jun 2020, 04:09    Post subject:  

01micko wrote:
Well maybe my commit is buggy! That shouldn't happen so either I revert the commit or put in further tests to make sure we booted off the particular device. Latter is the real solution.
I still can't get my head aroud the ides that there is a coding bug in that code that is directly causing a kernel panic.
I wonder if it has to do with lack of support for mmc devices in Puppy kernels.

For some hardware, typical Puppy kernels depend on a module from '/lib/modules/4.4.187/kernel/drivers/mmc/host' to support a local mmc device. But for most of the 'init' script, the kernel has no access to it's modules, since the zdrv is not available yet.
This is true for my Lenevo ThinkPad, which has an internal mmc device but needs '/lib/modules/4.4.187/kernel/drivers/mmc/host/sdhci-acpi.ko' to access it. The result is the 'init' script cannot see the mmc device.

This could be tested by "mash" by booting with his SD card out, then after inserting the SD card, see if "lsmod" shows any of the modules in '/lib/modules/4.4.187/kernel/drivers/mmc/host/'

An alternative would be to use http://www.murga-linux.com/puppy/viewtopic.php?t=118416.

If it is a "module" issue, it can be fixed with a recompiled kernel, or http://www.murga-linux.com/puppy/viewtopic.php?t=118416.

I also gather that "Quirky" kernels might have better support for mmc devices.

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


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

PostPosted: Tue 09 Jun 2020, 04:28    Post subject:  

gyro wrote:
If it is a "module" issue, it can be fixed with a recompiled kernel,

Do you know what kernel config is needed?
Thanks

_________________
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: Tue 09 Jun 2020, 04:29    Post subject:  

bigpup wrote:
ScPup64 20.01+6
Frugal install using save folder.
Using the 5.4.6 kernel.

No wifi support for my wifi hardware.
Code:
Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
• Kernel Driver: r8822beS
• Memory Used: 768.00 KB
• Path: /lib/modules/4.19.23/kernel/drivers/staging/rtlwifi/r8822be.ko
• Description: Realtek 802.11n PCI wireless core
• Description: PCI basic driver for rtlwifi
• Description: Realtek 8822BE 802.11n PCI wireless

Got the needed firmware installed.

Need the kernel driver.
r8822be.ko

This source package has the needed driver.
I have used this to get driver for other Puppies.
Realtek source package for wifi
https://github.com/rtlwifi-linux/rtlwifi-next

running make and make install get errors.

Yes I unzipped the package.
Have the devx and kernel sources sfs's loaded.

Can someone try compiling this driver package.

_________________
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: Tue 09 Jun 2020, 05:26    Post subject:  

gyro wrote:
01micko wrote:
Well maybe my commit is buggy! That shouldn't happen so either I revert the commit or put in further tests to make sure we booted off the particular device. Latter is the real solution.
I still can't get my head aroud the ides that there is a coding bug in that code that is directly causing a kernel panic.
I wonder if it has to do with lack of support for mmc devices in Puppy kernels.

For some hardware, typical Puppy kernels depend on a module from '/lib/modules/4.4.187/kernel/drivers/mmc/host' to support a local mmc device. But for most of the 'init' script, the kernel has no access to it's modules, since the zdrv is not available yet.
This is true for my Lenevo ThinkPad, which has an internal mmc device but needs '/lib/modules/4.4.187/kernel/drivers/mmc/host/sdhci-acpi.ko' to access it. The result is the 'init' script cannot see the mmc device.

This could be tested by "mash" by booting with his SD card out, then after inserting the SD card, see if "lsmod" shows any of the modules in '/lib/modules/4.4.187/kernel/drivers/mmc/host/'

An alternative would be to use http://www.murga-linux.com/puppy/viewtopic.php?t=118416.

If it is a "module" issue, it can be fixed with a recompiled kernel, or http://www.murga-linux.com/puppy/viewtopic.php?t=118416.

I also gather that "Quirky" kernels might have better support for mmc devices.

gyro


Regardless, it shouldn't happen.

I introduced the facility to resize an f2fs or ext4 partition specifically for the raspberry pi which essentially needs the mmc/sdcard driver (whatever it is) built in to the kernel to facilitate boot. This enabled me to ship a 4GB or 2GB image that could be copied via dd, copy or unzip directly to the card device no matter the size, so long as it exceeded the the size of the image. As stated, this was to be extended to usb sticks so I do need to revise the code at some point.

I'm suspecting that peebee's kernel has the necessary driver compiled into the kernel image, and that is why @mash sees the problem. I'm not so sure that a debugsave can't be performed (which I bugfixed recently) which may or may not have shed more light.

I'll have to have a think about this one... Confused

_________________
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: Tue 09 Jun 2020, 06:45    Post subject:  

peebee wrote:
gyro wrote:
If it is a "module" issue, it can be fixed with a recompiled kernel,

Do you know what kernel config is needed?
Thanks
Of course not.
Only somone who has the hardware with the problem can say which mcc kernel module gets loaded.

I know which module my Lenevo ThinkPad required, but the HP might require a different one.

Besides, unless someone does some more testing, we'll never know if it's because the "init" script caused the kernel to try to use a non-existent module, or not. And without a HP machine with the issue, I can't test that.

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

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

PostPosted: Tue 09 Jun 2020, 06:56    Post subject:  

01micko wrote:
I'm suspecting that peebee's kernel has the necessary driver compiled into the kernel image.
What evidence do you have for such a statement?

How could "peebee" ensure that the needed module is compiled into the kernel, if he doesn't know which module it is.

At the moment, we don't know if it is a module problem.
If it is, we don't know which module.

I suspect exactly the opposite, that "mash" is experiencing the issue because the needed module, is in fact a module, and not compiled into the kernel, and therefore un-available in "init".

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

Joined: 18 Dec 2017
Posts: 14

PostPosted: Tue 09 Jun 2020, 15:08    Post subject:  

Quote:
This could be tested by "mash" by booting with his SD card out, then after inserting the SD card, see if "lsmod" shows any of the modules in '/lib/modules/4.4.187/kernel/drivers/mmc/host/'


No, it doesn't. I looked into dmesg and run diff on lsmod output before and after inserting SD card, and nothing.
Back to top
View user's profile Send private message 
perdido


Joined: 09 Dec 2013
Posts: 1601
Location: ¿Altair IV , Just north of Eeyore Junction.?

PostPosted: Tue 09 Jun 2020, 20:39    Post subject:  

bigpup wrote:
bigpup wrote:
ScPup64 20.01+6
Frugal install using save folder.
Using the 5.4.6 kernel.

No wifi support for my wifi hardware.
Code:
Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
• Kernel Driver: r8822beS
• Memory Used: 768.00 KB
• Path: /lib/modules/4.19.23/kernel/drivers/staging/rtlwifi/r8822be.ko
• Description: Realtek 802.11n PCI wireless core
• Description: PCI basic driver for rtlwifi
• Description: Realtek 8822BE 802.11n PCI wireless

Got the needed firmware installed.

Need the kernel driver.
r8822be.ko

This source package has the needed driver.
I have used this to get driver for other Puppies.
Realtek source package for wifi
https://github.com/rtlwifi-linux/rtlwifi-next

running make and make install get errors.

Yes I unzipped the package.
Have the devx and kernel sources sfs's loaded.

Can someone try compiling this driver package.


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.
Code:
# modinfo r8822be.ko
filename:       /initrd/mnt/dev_save/scpup64/ScPup64save/root/r8822be-master/r8822be.ko
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger   <Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE   <wlanfae@realtek.com>
author:         lizhaoming   <chaoming_li@realsil.com.cn>
description:    PCI basic driver for rtlwifi
license:        GPL
author:         Larry Finger   <Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE   <wlanfae@realtek.com>
author:         lizhaoming   <chaoming_li@realsil.com.cn>
firmware:       rtlwifi/rtl8822befw.bin
description:    Realtek 8822BE 802.11n PCI wireless
license:        GPL
author:         Larry Finger   <Larry.Finger@lwfinger.net>
author:         Realtek WlanFAE   <wlanfae@realtek.com>
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger   <Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE   <wlanfae@realtek.com>
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger   <Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE   <wlanfae@realtek.com>
alias:          pci:v000010ECd0000B822sv*sd*bc*sc*i*
depends:        mac80211,cfg80211
retpoline:      Y
name:           r8822be
vermagic:       5.4.6-lxpup64 SMP mod_unload modversions
parm:           debug_level:int
parm:           swenc:Set to 1 for software crypto (default 0)
 (bool)
parm:           ips:Set to 0 to not use link power save (default 1)
 (bool)
parm:           swlps:Set to 1 to use SW control power save (default 0)
 (bool)
parm:           fwlps:Set to 1 to use FW control power save (default 1)
 (bool)
parm:           msi:Set to 1 to use MSI interrupts mode (default 1)
 (bool)
parm:           dma64:Set to 1 to use DMA 64 (default 0)
 (bool)
parm:           aspm:Set to 1 to enable ASPM (default 1)
 (int)
parm:           debug:Set debug level (0-5) (default 0)
parm:           debug_mask:Set debug mask (default 0) (ullong)
parm:           disable_watchdog:Set to 1 to disable the watchdog (default 0)
 (bool)
Back to top
View user's profile Send private message 
gyro

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

PostPosted: Wed 10 Jun 2020, 01:02    Post subject:  

Sorry folks.

It looks like my "unavailable mmc kernel module" theory is wrong.

"mash" has reported that inserting an SD card after booting, does not cause the loading of a module.

And I have done some testing on my Lenovo IdeaPad 100S:

I know that it has an "unavailable mmc kernel module" issue.
So I if my theory were correct, I would expect the Lenovo to exhibit the issue, and kernel panic.
But it did not, it boots scpup32 out of the box, fine, i.e. with the "offending" code in the 'init' script.

Without the needed mmc kernel module, the 'init' script is completely unaware of any mmc devices, as seen in '/initrd/tmp/probepart.log'

So, I have nothng.

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


Joined: 11 Oct 2008
Posts: 8787
Location: qld

PostPosted: Wed 10 Jun 2020, 05:48    Post subject:  

I have a Dell Latitude E7270 laptop with builtin card reader. The reader is not available for booting unless I use gyro's initrdmodules tool.

The computer boots fine from a usb stick with the sdcard plugged in, but nothing can be found on it until zdrv is loaded of course.

For the record, I'm running slacko64-6.9.9.10 fresh out of woof-ce.installed to a usb stick with gyro's other utility f2stickpup, part of frugal pup. Secure boot is enabled on this machine.

On my sdcard I installed the same OS as on my stick. On the stick I ran the initrd modules facility which installed the rtsx_pci and rtsx_pci_sdmmc modules to the initrd.gz. Unfortunately, the init script didn't get updated so I manually patched it with the diff in gyro's first post of the related initrdmodules topic.Once I got this sorted I proceeded to boot the card. I was able to reproduce the kernel panic. Completely different OS and kernel. Again for the record, the kernel is freshly compiled 4.19.125.

I also booted the stick with the patched initrd and the sdcard plugged in but no kernel panic. I only got the panic when booting off the sdcard.

Frankly, I don't understand it. There seem to be no syntax errors in the init code and it is a simple operation to grep the probedisk log and decide which way to proceed.It does seem though that the script decides that we should check if the card needs resizing so the error possibly comes from /sbin/resize_part, but that looks ok to me too. Works just fine on raspberry pi boards.

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.

Further thoughts appreciated.

_________________
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: Wed 10 Jun 2020, 12:24    Post subject:  

01micko wrote:
Frankly, I don't understand it.
Hear, hear.

Yes, the code looks benign, if it had any syntax errors etc..., I would expect it to kernel panic on all hardware.
However you could remove any lingering doubt by extracting '/sbin/resize_part' from the initrd.gz and running it from the running system after booting from the usb stick.

It would also be ineresting to see if recompliling the kernel so that the mmc host modules identified by 'initrdmodules' get builtin, makes any difference.
I have a memory of a comment about the kernel, that some drivers only work properly if they are builtin.
If this proves sucessful it would be interesting to see if a test kernel with all mmc host modulles builtin would work for the other folk.
The idea is to remove the need to use 'initrdmodules'.

Another thing that could be tried, is to prove that the 'init' script has working access to the SD card.
Boot from the usb stick, but add some hack code into the 'init' script that mounts the SD card, "cat"s a text file that exists on it, and umounts it. The contents of the text file should appear in '/initrd/tmp/bootinit.log' in the running system.

I must try booting from an SD card in my Lenovo IdeaPad.
All my testing was done booting from a usb stick.

Just a thought on your code:
The SD card in my Lenovo is "mmcblk2" not "mmcblk0", so activating the resizing code with a boot parameter like "sdresize=2" might be an advantage.

I read somewhere in the forum that BK had done some work in compiling a more mmc friendly kernel, in Quirky or EasyOs. We probably should track down the kernel config file he used, and update the woof-CE kernel config files appropriately.

Another 2 cents worth.

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

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

PostPosted: Wed 10 Jun 2020, 13:19    Post subject:  

Is it my late, late, late night stupidity, or is there a problem with '/sbin/resize_part' trying to actually resize the same partition that it's booting from.

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


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

PostPosted: Wed 10 Jun 2020, 15:16    Post subject:  

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.

This is the initrd.gz that is working OK.
Screenshot(2).png
 Description   This is the one that works. Get normal boot up.
 Filesize   35.18 KB
 Viewed   110 Time(s)

Screenshot(2).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 
Display posts from previous:   Sort by:   
Page 19 of 23 [335 Posts]   Goto page: Previous 1, 2, 3, ..., 17, 18, 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.1654s ][ Queries: 12 (0.0842s) ][ GZIP on ]