New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to save puppy-save files in NVMe SSD drive partition #1115
Comments
This is mostly the code suggested by gyrog, but I did add the lines for nvme devices after seeing issue puppylinux-woof-CE#1115
This is mostly the code suggested by gyrog, but I did add the lines for nvme devices after seeing issue #1115
The Slackware-compatible Puppy ISO reported here http://www.murga-linux.com/puppy/viewtopic.php?p=976813#976813 should have sufficient NVMe support. |
Sure, will test after office hours and report back. |
Hi @mavrothal Does that image not UEFI compatible ? It is not booting in my system |
Did not check, but looking at it I do not see any efi.img so probably not. |
With the latest changes nvme drives should be properly handled by most scripts.. if i didn't mess something up. However there's still pup_event_frontend_d.bac .. i'm not going to compile this. I'll try to translate it to C although i lack the motivation and time. |
nvme drive support should be in good shape with the current git revision... i will create a dpup with uefi one of these days for you to test.. or maybe someone is willing to build any i686 puppy with uefi support for mariappan to test?? i added a C version of pup_event_frontend_d(.c) with a couple enhancements and a i686 binary. I can compile the rest of the binaries, but i'll need a 64 bit p****.. not willing to use any other os than my own atm... maybe someone else is willing to compile and add arm and x86_64 binaries to: woof-arch/arm/target/rootfs-skeleton/usr/local/pup_event/.. Although i truly believe the that a c app based on udev should replace this, some code can be added to pup_volume_monitor to make it work with the rox desktop as well, but... Many birds will die of a heart attack on new year's eve.. it's a phantom world |
I think, for uefi_cd.sh to work in Stretch, "syslinux-common" must be added from debian? puppy-common syslinux-3.73.pet doesn't seem to have some of the /usr/lib/syslinux files: |
It probably won't work.. phil downgraded and used a pet pkg. but it's missing the extlinux binary. I'm creating a syslinux 4.0.7 petbuild.. but maybe i'll just pick the same pet pkg.. which i assume is using the official binaries |
phil's pkg seems to be unsuitable, it's missing files.. breaks puppyinstaller and bootflash (even more) |
Hmm but makebootflash only works with syslinux 3.xx stuff. so it's probably ok. the only mystery is the missing extlinux.. it's probably in a zz pkg alongside the 3.xx required files, or maybe a symlink is created ... |
I have a test dpup eufi iso but unfortunately it's not available for download yet, the ftp client on my android phone is buggy, it crashed and overwrote the file twice.. damn |
Test iso with all the recent changes up to 30cefaf.. http://01micko.com/wdlkmpx/stretch-7.0.0b1-uefi-devx.iso |
does this still needs to be open? |
There is no feedback, there it's fixed.. |
While installing puppy-linux in laptop which has nvm-e ssd drive, I was not abe to puppy-save files even though i selected a valid partition.
Rootcause:
In shutdownconfig, there is a if check to verify valid partitions. In that check, nvme* is not added, hence even if we select a valid partition with available space, not able to proceed.
The text was updated successfully, but these errors were encountered: