X-Slacko Slim 4.4r49 (unique, stable, and flexible)

[mistfire]

@Sage it means initrd is the culprit. I currently revising the initrd to fix that error

[mistfire]

@Lyfrost probably yes. For C/C++ programming, use devx sfs. The link was in the first post of this thread. And also download dev files when needed.

[Volhout]

@belham2

Not sure what your audience is for the USB sticks, but modern PC's (laptops) often require firmware for WIFI, and have nothing other than WIFI (or Bluetooth).
The size of the WIFI firmwares often exceed the size of the linux minimal image. And without firmwares, a browser does not have much functionality on laptops.

Look at Tinycore: the core is 17 Mbyte, with WIFI and all the firmwares it exceeds 100Mbyte (*) and 4 simple GTK1 window managers.

I will follow your challenge, but doubt it is usefull for anything other than older desktops. I really hope you succeed though !!!
Please keep SFS-on the fly option in.

Volhout.

[LyFrost]

@Lyfrost probably yes. For C/C++ programming, use devx sfs. The link was in the first post of this thread. And also download dev files when needed.

Ok thanks for your quick response, i'll try it

[mistfire]

New X-Slacko Slim iteration released

Changes:
* New initrd. The initrd is based from the X-Slacko 4.2 initrd. It is more user friendly than before, it has improved resume from hibernation support, sfs mountpoint logging, and multisession logging for easy troubleshooting.

* Problem on loading multisession is fixed

* Bug on edit-initramfs on xz compression is fixed.

Download: http://www.mediafire.com/file/z1y7ph2w3 ... 4.2r58.iso
MD5 Checksum: b31cbab24520da682505877388dbbc43

[mistfire]

@Sage can you please test this latest release on your machine?

[Sage]

Yes - doing...
Report here:
Nope! Sorry! - doesn't work. "....puppy_xslacko_4.2.sfs not found."
but the one I modified with your instructions still works well.

[mistfire]

@Sage can you please send me all the contents of /initrd/tmp folder from your sucessfully modified x-slacko slim live cd?

[Sage]

Done - had a few moments.

[Volhout]

Dear mistfire,

Is it possible for you to include 'modesetting_drv.la' or 'modesetting_drv.so' into Xslacko Slim.
This is the video driver needed for Intel Atom N2600/2800 video.

It is located (in previous XSlacko's) in /usr/lib/xorg/modules/drivers
Maybe you can use the one from R54 (slightly different kernel 4.12.2 versus 4.12.8 in R58).

Dear Regards.

Volhout

[mistfire]

Dear mistfire,

Is it possible for you to include 'modesetting_drv.la' or 'modesetting_drv.so' into Xslacko Slim.
This is the video driver needed for Intel Atom N2600/2800 video.

It is located (in previous XSlacko's) in /usr/lib/xorg/modules/drivers
Maybe you can use the one from R54 (slightly different kernel 4.12.2 versus 4.12.8 in R58).

Dear Regards.

Volhout

Okay I will try to include that. Intel N2600/2800 uses intel GMA 3600 but it works through fbdev driver?

[jss83]

Super build this, my wifi is detected right away , will test this further and see if everything I use works on this and then I can make a shift.

Thanks mistfire

[mistfire]

New X-Slacko Slim iteration released

Changes:
* More user friendly error-handling in initrd
* Some bugfix


Download: https://drive.google.com/open?id=0B2FRk ... XNuWWI4ajg
MD5 Checksum:7d5ddfa7f1626d464dafcc0a8fc36c1b

[mistfire]

@Sage can you please test this latest release?

[Sage]

Worst yet!

White oblong - FATAL ERROR.
pup...... .sfs not found
Select SAVE FILES for diagnostic purposes (there aren't any - didn't run)
...
GO TO PROMPT for advanced purposes (no point!)
...
...
0. Save temp files (there aren't any)
1. Go to prompt
2.Reboot! (why? in desperation!)

None of the comments have any point if it doesn't run further than the opening boot screen.

Sorry.

More: No idea where it all goes wrong, but r59 DOES contain xslacko_4.2/puppy_xslacko_4.2.sfs and
xslacko_4.2/zdrv_xslacko_4.2.sfs

[mistfire]

@Sage thanks for your comment. If you encounter that dialog just select "Save temp files" select the partition where to saved those files (in tarball format) then upload that to this thread instead of PM. Those files will give a clue to me what went wrong on searching puppy files to your machine

[Sage]

Misunderstanding, misty. That message shows BEFORE anything starts up. There's nothing to save, there's no partition!
This version doesn't start on any machine, 32 or 64bit, radeon or nV, no combination of HW. There's something radically wrong because r54 works just fine on every machine and so does r57 modified according your instructions.

[mistfire]

@Sage Did you boot that on a real machine? If yes, then If there is no partition to save just plugged a usb flash drive before selecting "save temp file" in fatal error dialog in order to get that temp files.

Upon booting, did you see these messages before fatal error dialog shown?
Loading modules to access drives...
Searching for Puppy Files...

[mistfire]

Fatal error message dialog explained.

This dialog is the unique feature of X-Slacko Slim's initrd. Its more user friendly than the vanilla one. The user gives options what to do next.

Options:

1. Save Temp Files - This will save the contents of /tmp of initrd to a disk (When puppy sfs is sucessfully loaded and perform switch root, it moves to /initrd/tmp). the /tmp folder of the initrd contains log files created by init script. Which is useful for troubleshooting. When the user choose this option. It shows list of storage device and the user must choose where to save the temp files in tarball file.

2. Go to prompt - Just access the ramdisk shell

3. Reboot - Just restart the computer

[Sage]

Upon booting, did you see these messages before fatal error dialog shown?
Loading modules to access drives...
Searching for Puppy Files...

Yes.

The Fatal Error message becomes irrelevant - nothing started, nothing to save.