Moderators: 666philb, Forum moderators
In a earlier post, I reported difficulty trying to boot fossapup64_9.5 on a Dell Latitude 7480/7490 laptop from micro SDCARD. (I felt I should have reported this issue in a new post.)
In this post, I am attaching a picture of the error message when I have attempted that.
(However, since I have found that I can boot fossapup64_9.6 from my Dell Latitude 7480/7490 laptop from micro SDCARD, this is not a major problem for me.)
Thanks for any help.
Try this.
On the SD card will be the config file for the boot loader menu.
I will assume it is going to be grub.cfg file.
Open this file in a text editor.
Look in the entries for a pmedia=cd
Change this to pmedia=usbflash
Save the change.
Now try to boot with it.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
@oldaolgeezer Here's an easier option to test what @bigpup offers.
When you reboot and the PC stops for you to select which Fossapup64 menu option for you to select, on the option you want, do this simple step:
hit the key to allow you to "edit the boot stanza" line (it will be either 'tab' for 'e' keyboard key to edit it).
On the 'line with pmedia=cd, change it to pmedia=usbflash
Allow the PC to boot and report back here any success/failure you see.
If the PC does not go to desktop and stops again at a prompt, type 'debugsave' and send us the resulting file.
It's a new laptop.................... use a newer kernel 
Hi Jasper:
This linked Dell webpage is definitely for some very new Latitude laptops,
but the webpage says "7490" but hovering the mouse over the 14 inch choices,
displays a "Dell Latitude 7440 13th generation Intel Core i7-1365U, vPro® (12 MB cache, 10 cores, 12 threads)"
My laptop seems to be made in year: 2018 (on bottom of case)
and has a more modest: CPU Core i5 6300U,
PupSysInfo 3.6.3:
BIOS INFORMATION (dmidecode):
Vendor: Dell Inc.
Version: 1.27.0
Release Date: 07/15/2022
I think there might be a typo on this Dell website.
@oldaolgeezer
Have you tried what I posted?
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
bigpup wrote: Sat Oct 26, 2024 1:37 amTry this.
On the SD card will be the config file for the boot loader menu.
I will assume it is going to be grub.cfg file.
Open this file in a text editor.
Look in the entries for a pmedia=cd
Change this to pmedia=usbflash
Save the change.Now try to boot with it.
Hi Bigpup:
There are a number of suggestions swirling around, but I am assuming you mean
the pmedia=cd parameter above....
I don't use pmedia=cd and I believe pmedia=usbflash is in my grub.cfg in all
the fossapup64_9.5 attempts.
Code: Select all
menuentry ' '{
true
}
menuentry "fossapup64_9.5 - ATTEMPT BOOT FROM MICROSDCARD _________________________________" {
search --no-floppy --fs-uuid --set=root 046C95624CF5546B
echo "Loading vmlinuz"
linux /fossapup64_9.5/vmlinuz psubdir=/fossapup64_9.5 PDRV=mmcblk0p1 pmedia=usbflash pfix=fsck,fsckp,trim
echo "Loading initrd.gz"
initrd /fossapup64_9.5/initrd.gz
}
menuentry ' '{
true
}So I don't think there is anything to change.
===
But, I have mentioned in my original post, my old memory of Barry Kauler's SDCARD "driver" boot "fix" inside initrd.gz and now I see this new forum post: Unpacking/Repacking 'Initrd.gz':
Code: Select all
https://forum.puppylinux.com/viewtopic.php?t=12960It is too complex for me to do, but if someone could recompile the vid=0a5c, pid=5832 USB Broadcom 5880 as a driver in fossapup64_9.5, and add that to both initrd.gz and to fossapup64_9.5 post boot libraries, I think that might solve this issue.
@oldaolgeezer
The 'trim' variable has no function unless you are using a SSD to boot from plus this needs to be activated in order for it to work on the SSD.
Once your up and running, consider adding the Intel Ucode for security purposes.
I am running this on Samsung micro-sd card.
Are you aware that you have additional commands available at your disposable in the Grub menu?
This is why I updated the initrd.gz as it contains a newer build of Busybox.
To get access to these, press <ESCAPE> at the menu splashscreen
press <ENTER>
press <ENTER>
Press <C>
Press <TAB>
An example using lspci
Some of this issue is just the issues that the Fossapup64 9.5 boot process has.
There has been a lot of bug fixes and tweaking of the boot process, that is not in Fossapup64 9.5 and never will be.
F96-CE (which is Fossapup64 9.6) does have a lot of these improvements.
From your posted boot menu entry.
search --no-floppy --fs-uuid --set=root 046C95624CF5546B
linux /fossapup64_9.5/vmlinuz psubdir=/fossapup64_9.5 PDRV=mmcblk0p1 pmedia=usbflash pfix=fsck,fsckp,trim
In this part of the boot menu entry.
USE the UUID of the partition to identify the pdrv= location.
So make pdrv=046C95624CF5546B
This is because the UUID is specific identifier for a partition. Only that partition has that UUID.
What the operating system calls a drive partition could change and does sometimes when booting.
mmcblk0p1 may not be identified to the boot process, until the operating system boots far enough to give it that identifier.
The UUID is given to the partition as an identifier when the partition is made.
It will always have that to identify it. Nothing will change it.
Also pdrv should be in lower case letters. Most all Linux commands are in lower case.
I am not sure all upper case letters would even be seen as a proper command to execute.
Also the place you have pmedia=usbflash can have an affect.
You should have it after the vmlinuz
This is all a line of code commands that should be done in a specific order.
Here is a typical example of a proper entry:
search --no-floppy --fs-uuid --set=root b0f092c5-6a1c-4e04-b9d8-ddbeb91d4ab7
linux /bookwormpup641007/vmlinuz pmedia=usbflash pdrv=b0f092c5-6a1c-4e04-b9d8-ddbeb91d4ab7 psubdir=/bookwormpup641007 pfix=fsck,fsckp (whatever else you may want to have on this line)
Actually pdrv= is suppose to be stating where the save will be found, so the boot process knows exactly where to look for it.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
@bigpup :-
Curious.
Even looking through the "BootParameters" section on the Wikki, I see there IS no 'pmedia=' setting specifically for an SD card. We know that if you boot an SD card through an SD card reader, it's usually seen as a USB device, so naturally, 'pmedia=usbflash' is the one you want.
Am I right in thinking that SD cards are normally seen as an mmc 'block' device? That being the case, which of the 'pmedia' parameters would you use if booting direct from an SD card slot?
https://wikka.puppylinux.com/BootParametersPuppy
Mike. 
You are getting into how hardware is connected on a specific computer, make and model, and technology at the time it was made.
Now you are getting into what actual boot process operations are being done in the specific Puppy version.
How the boot process is coded to work in the specific Puppy version.
This stuff as developed, evolved, changed, tweaked ,bug fixed, etc..... over the years.
What I can offer, from booting on different computers, and booting different versions of Puppy.
You just try stuff and see what works.
Fossapup64 9.5 has had this boot issue, from day one, on some computers, but not all computers.
Sometimes not being able to find the SFS files and continue booting.
For external type drives, using pmedia=usbflash seems to usually fix this issue. (external drives are usually USB connected)
An SD card is a type of external drive and works basically the same as a USB flash drive to store data.
Anyway pmedia=usbflash, telling the boot process to do specific things, seems to be very good code, with little issues.
If the install is not on a CD, pmedia=cd on some computers, does not work.
Again a lot of tweaking and code changes, have been done to the boot processes, that are not in Fossapup64 9.5.
Some of the needed changes were found, by what was going on, trying to boot Fossapup64 9.5.
Using UUID to identify the partition the Puppy files are on was one big help to the boot process.
That has to be the specific partition.
Because the partition is given that UUID and it is the only one that has that specific UUID. It never changes.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
One thing to try for what is posted in the first post.
Do you have any USB drives plugged into the computer when you try to boot?
If yes.
Do not have any USB drives plugged in when you try to boot from the SD card install.
If the install on the SD card is a live install, which will be using the boot loader provided in the Fossapup64 ISO.
Fossapup64 9.5 has an issue finding it's files, when booting from a USB drive, if another USB drive is also plugged into the computer.
If the computer is controlling the SD card reader with the USB controller.
This could be the cause of the problem booting.
A frugal install on the drive and using a different boot loader, should not have this issue.
I have a USB drive with aFossapup64 9.5 frugal install.
Using the grub4dos boot loader.
also tried it using Grub2config boot loader.
No problem booting, if another USB drive is also plugged in.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
@oldaolgeezer :-
I'm assuming the SD card reader slot on your Latitude IS "bootable", yes? I only ask because I have an install of BookwormPup64 on a standard SD card. It boots just fine from the slot on my HP desktop rig, but last night - just for the hell of it! - I attempted to boot it from the slot on my E6430 Latitude.
According to the system, although it's detected AS a usable drive, so far as as the system is concerned it doesn't "see" it.....it tells me the bootable partition doesn't actually exist, never mind trying to find any files on the card. Which leads me to suspect that the SD card slot on this particular Latitude - an older model than yours - is NOT in fact "bootable".......that it is in fact simply a "data" slot.
I could be wrong. I haven't yet really had a look around in the BIOS to see if there are any settings related to the SD card slot. If I get time, I may have a look this evening.
Mike. 
Fossapup is really old and its kernel could be misconfigured with MMC/SD drivers left out. I added many of these to the dpup kernel to solve problems like this so I'd recommend BookwormPup64: it's more likely to work.
If there's a distro that boots fine on this computer and recognizes the SD card slot (and it doesn't matter if you boot from a SD card or not), please provide the output of lsmod, lspci and dmesg. I can check if the required driver is in.
Thank you both Jasper and dimkr for both your long term Puppy support and for your more recent support on my own Dell Latitude 7490 laptop which has only a micro SDCARD slot (I never had a PC with such a slot before, let alone trying to boot Puppy on it.)
dimkr wrote: Tue Oct 29, 2024 5:57 amIf there's a distro that boots fine on this computer and recognizes the SD card slot (and it doesn't matter if you boot from a SD card or not), please provide the output of
lsmod,lspcianddmesg. I can check if the required driver is in.
BookwormPup64_10.0.8 boots UEFI fine on this computer and recognizes the micro SD card slot to do so. I'm using that to make the requested files:
I have now attached three of the files that dimkr has requested
(the dmesg data was somewhat large as I have been using my laptop all morning, so I rebooted and attached just a smaller dmesg output file with the first few minutes of powering up.)
@oldaolgeezer Thanks, the required driver is indeed included in all Puppy releases that incorporate my fix.
If anyone is interested in the future, zcat /proc/config.gz | grep CONFIG_MISC_RTSX_PCI is the way to check if the required driver is present: It should say CONFIG_MISC_RTSX_PCI=y.
Makes sense. =m means the driver is loaded later, and isn't available at boot time, hence the kernel can't see the SD card and can't access the Puppy files on it.
No, module name is rtsx_pci.
@dimkr
OOops 
This isn't the default kernel I am using .... 5.4.284-64oz-nskl-ao
Better wait for @oldaolgeezer to reply.
However, since I have found that I can boot fossapup64_9.6 from my Dell Latitude 7480/7490 laptop from micro SDCARD
That is what Fossapup64 9.6 is about.
Update and bug fix for Fossapup64 9.5
Just forget about trying to use Fossapup64 9.5 and be happy using Fossapup64 9.6 
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
bigpup wrote: Wed Oct 30, 2024 3:56 amJust forget about trying to use Fossapup64 9.5 and be happy using Fossapup64 9.6
It's 3+ years older than this new laptop, so it's not going to work well even if you get it to boot from a SD card. I wonder if supports the GPU or understands the difference between P and E cores: if it doesn't, expect slowness, heat and short battery life. Anything based on Ubuntu 20.04 should be way too old for a laptop like this (Mesa, VA-API ... everything is old), so this also rules out F96-CE.
@dimkr
My laptop seems to be made in year: 2018 (on bottom of case)
and has a more modest: CPU Core i5 6300U,PupSysInfo 3.6.3:
BIOS INFORMATION (dmidecode):
Vendor: Dell Inc.
Version: 1.27.0
Release Date: 07/15/2022
