Install Porteus on SD card

[user0815]

Can we submit a bug report for this case?

[beny]

hi, try in console fdisk -l , mount the sd on and try to install sylinux, bug report maybe but mmc isn't sd card

[wread]

@all
on November 2017 I posted Porteus on a Memory Card with the work around of putting the boot folder on a USB. Now I see you want discover America again....

Please open your bios and go to "boot device order"....you won't find mmc listed as boot device....

Then you will have to use a work around, or write your own bios. I chose the first option.
There is another work around: put the boot folder on the hard disk and use grub...

Regards!

[Ed_P]

I am desperate, trying FAT32 takes me indeed to the boot menu from Porteus (where you can choose to boot graphical, copy2ram, fresh etc.)

Another idea, in the /boot/syslinux/porteus.cfg file on the SD on the APPEND line add the "from=" cheat code pointing to the SD drive. To eliminate the confusion of dev vs mnt and sda vs sdc using the UUID code of the drive insures no mistake. As in

Code: Select all

LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND from=UUID:8486-DDC5 changes=EXIT:UUID:8486-DDC5/changes/porteussave.dat extramod=UUID:8486-DDC5/Modules
 :
 etc

Obviously don't use the UUID of my USB flash drive.

[user0815]

Obviously don't use the UUID of my USB flash drive.

hmm, let´s see. My UUID shown in my other post is completely different, so you are right, I cannot use your UUID. ;)

Seriously: bad news: none of the above suggestions work.

try in console fdisk -l , mount the sd on and try to install sylinux

tried it again, mount sd card into something else than mmc, but got again error code 2 when executing the Porteus-installer-for-Linux.com as already reported here

But there is also good news: I tried Porteus-v3.2.2, both 32 and 64 bit, and it works flawlessly. Quick and simple procedure, mount the iso, copy the files, execute the porteus installer, and that´s it, smooth booting into porteus 3.2.2. So my request would be that somebody has a look into version 4.0, there must be something missing for realtek sd card reader.

Please open your bios and go to "boot device order"....you won't find mmc listed as boot device....
Then you will have to use a work around, or write your own bios. I chose the first option.

The sd card reader is not listed in bios as mmc, but with clear name "secure digital card reader", there is also an option in the bios to disable/enable "secure digital card reader" for boot, so the bios definitely supports boot from sd card, I don´t have to write my own bios. The issue decribed in this thread is also not directly related to "boot", boot was always possible, the boot kernel vmlinuz can be loaded. Otherwise I wouldn´t be able to see this error screenshot as already reported in my previous post. Please read my report before doing such sarcastic comment.

Another idea, in the /boot/syslinux/porteus.cfg file on the SD on the APPEND line add the "from=" cheat code pointing to the SD drive

Ed, thank you very much indeed for your incredible patience with me, and for all the advise and guidance. The above successful boot of v3.2.2 was under fat32 formatted sd card. I will try the ext2 format option later on.
Best regards

[jssouza]

Try using the kernel (vmlinuz) and 000-kernel.xzm from porteus 3.2.2 on your porteus 4.

[user0815]

Try using the kernel (vmlinuz) and 000-kernel.xzm from porteus 3.2.2 on your porteus 4.
Top

Can I indeed just replace the 000-kernel with the old one? Isn´t better just to stick with v3.2.2, since the kernel (4.9) is anyway outdated even if you can use it in v4.0?

[jssouza]

Can I indeed just replace the 000-kernel with the old one?

You should be able to. Note that you need to replace not just the 000-kernel.xzm but also vmlinuz.

Isn´t better just to stick with v3.2.2, since the kernel (4.9) is anyway outdated even if you can use it in v4.0?

If porteus 4 boots with the older kernel, then we might be able to narrow it down to either a kernel module not present in porteus 4's kernel, or it is a case of missing firmware, which I think might be the case. In that case you could download firmware from slackware current.
But all these are later steps. You have to try if porteus 4 works with the older kernel.

[Ed_P]

Happy to hear you got the SD to boot Porteus.

While you can try the kernel replacement options for 4.0 I think trying the from= cheatcode would be quicker to test.

-edit-

oops, just saw this.

Seriously: bad news: none of the above suggestions work.

So you already tried the from= suggestion. Dang.

[user0815]

You should be able to. Note that you need to replace not just the 000-kernel.xzm but also vmlinuz.

ok, using v4.0 with 000-kernel and vmlinuz from v.3.2.2 works, with some shortcomings after a quick test:
1. shutdown/poweroff hangs after porteussave.dat is created and changes saved. I have to force push power button. Fresh boot without changes works fine.
2. Booting into porteus GUI seems to take longer than with v3.2.2. I didn´t stopwatch, but gut feeling says it´s double as long.

Some additional notes: At the moment, it is only possible to use sd card on my hardware in fat32 format with save.dat. Attempt to completely switch to linux fs (ext2,4) fails. Executing Porteus-installer-for-Linux.com ends up again with error code 2 as already reported here. I am having two sd cards, one is micro-sd with adapter, the other one standard sd. Both Porteus v4 and v3 can only see the micro-sd, the other one is not visible at all.
Also efi boot (secure boot disabled) with sd does not work, whereas it works fine for usb flash drive.

It would be great if v4.0 can work on SD card with linux ext2. The main benefit when using sd card is that you can plug in and forget, and you always have your speedy os with you.

cheers

[Ed_P]

Advantages of a save.dat file when used with the changes=EXIT cheatcode; less IO on the plugin drive, faster execution when booted due to less IO to the drive, the ability to not save changes if something doesn't go as planned.

Disadvantage of a save.dat file is it can unexpectedly fill up, crash when exiting and you loose everything. I save modules and downloads directly to the flash drive so they don't end up in the save.dat file. I also periodically backup my save.dat file, as a save.dat.xzm module. I have used save.dat files of 256KB, 320KB, 512KB and have now settled on a 384KB one.

[user0815]

Hi Ed, do u think it’s safe to use v3.2 since it’s from 2016 with quite old linux kernel?

[Ed_P]

There are certainly short comings but a big problem was fixed with installing the script shown here: Re: SAVE.DAT, XZM & MLOOP (Post by Ed_P #47636)

[user0815]

You have to try if porteus 4 works with the older kernel.

Another finding: wifi is not available, nor on v3.2 neither on v.4 with 000-kernel from v3. Are there any instruction or guidelines how I can integrate firmware and build new kernel myself?
I am trying the 64bit-kernel4.19.27 from the porteus kernel builder thread, it does not help.

[jssouza]

You have to try if porteus 4 works with the older kernel.

Another finding: wifi is not available, nor on v3.2 neither on v.4 with 000-kernel from v3.

Wifi hardware info please.