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

Message

Sage · #736 Post by **Sage** » Mon 29 Jan 2018, 14:27

Did exactly as requested. Got the diagnostics , all passed.
Declined to plug in USB, just rebooted (third option).
puppy_xslacko_4.4.sfs not found.
Select 0,1,2
Selected third.
Crazy! This absolutely MUST NOT HAPPEN. There is some fundamental block. No other Puppy or any other of dozens of distros do this. Strikes me someone (not necessarily misty) is trying to be far too smart and fails every time.
This is suppose to inherit the crown of smallest, fastest Puppy. It shouldn't be intended to run on SOTA machines, more something from the 1990s IMHO. Frankly I've no time for these wannabees with too much dosh, trying to claim boasting rights for HW that'd take them to Mars and back - possibly their best destination.
Let's get back to basics: K.I.S.S. is ALWAYS the correct answer.

Geoffrey · #737 Post by **Geoffrey** » Mon 29 Jan 2018, 22:07

Sage,

On my Lenovo 2ghz 2gig ram pc it doesn't find the puppy_xslacko_4.4.sfs when booting from the CD, I did a manual frugal install to the HDD, this boots and runs without problem.

My ACER intel laptop boots from CD ok, as for my P4 machine there appears to be no suitable SIS video driver available.

mistfire · #738 Post by **mistfire** » Mon 29 Jan 2018, 22:41

@Sage. What is the name and model of your machine? I try my best to fix the issue on your rig. If your machine passed on the simple diagnotics then you can save the tmp folder of the initrd on your hard drive and send it here. I need that file to troubleshoot that problem on your machine.

@Geoffrey can you tell me the results of the diagnostics. Also can you please tell me the name and model of your lenovo laptop where the xslacko slim failed to boot? On the case on acer, does it the desktop environment start?

Geoffrey · #739 Post by **Geoffrey** » Tue 30 Jan 2018, 00:52

mistfire wrote:@Geoffrey can you tell me the results of the diagnostics. Also can you please tell me the name and model of your lenovo laptop where the xslacko slim failed to boot? On the case on acer, does it the desktop environment start?

It's a Lenovo thinkcentre A61e 6449 with a Sempron cpu of 2ghz with 2 gigs ram, as the pic shows it should work, but it fails to find the puppy_xslacko_4.4.sfs when booted from a CD rom, works fine from a HDD frugal install, weird.

The ACER Aspire laptop boots from CD rom and goes to desktop without a problem, everything seems to function though I may have to play with the mouse as the pad doesn't work double tapping, wireless works ok screen res all good, I'll check it out some more when I find the time.

The P4 tries to run the desktop but fails with the SIS video and falls back to a prompt with the message " VESA BIOS Extensions not detected ".

mistfire · #740 Post by **mistfire** » Tue 30 Jan 2018, 09:45

thanks @geoffrey for the screenshot. @sage can you please send a screenshot the same as geoffrey did?

mistfire · #741 Post by **mistfire** » Wed 31 Jan 2018, 01:14

Here is a test release of X-Slacko Slim. The initrd has a detailed boot logging to trace what went wrong why puppy SFS cant find.

@Sage and @Geoffrey can you please test this release. In the puppy sfs cant find please select SAVE TEMP FILES to a storage device and upload here in this form. If you cant save just select GO TO PROMPT use this command

Code: Select all

cat /tmp/bootinit.log | tail -n (last to 5-15 lines)

and tell me the results

Download: https://drive.google.com/open?id=1y2MZY ... qJLQ7kumJY

Geoffrey · #742 Post by **Geoffrey** » Wed 31 Jan 2018, 03:54

mistfire, it appears to look on the sda1 drive and usb, but fails to load the file from the CD

mistfire · #743 Post by **mistfire** » Wed 31 Jan 2018, 08:51

@Geoffrey you are right the compiled kernel has a problem on reading CD drives. I made a test earlier using USB external CD Drive also it fail to mount CD drive although the filesystem was recognized.

I wonder what kernel configuration that I need to verify?

Sage · #744 Post by **Sage** » Wed 31 Jan 2018, 10:48

Well done, Geoff - it was all getting far too time consuming for me when, clearly, a simple error was all that was involved.
The last fully functional version was 4.2 r57 wr54 initrd. So, for anyone who speaks this bizarre language, the answer lies therein. Don't call me till it's fixed!
Amazing that none of the resident gurus could isolate the fault...

Geoffrey · #745 Post by **Geoffrey** » Wed 31 Jan 2018, 11:07

Booting from the CD I managed to get to a desktop on the P4 machine after fiddling with the xorgwizard, seems stable.

I notice that the CD is found as hdc

mistfire · #746 Post by **mistfire** » Wed 31 Jan 2018, 22:12

Thanks for that @Geoffrey right now I compiled the kernel using fatdog64 source code. Configuring to 32-bit and applied some my preferences. At first I noticed that the output kernel image was 6.1Mb! I try to trim some builtin modules but keeping the disk drive, usb, keyboard, fb, pcmcia, nvme, and mouse kernel modules. but the kernel filesize was 5.9Mb.

Volhout · #747 Post by **Volhout** » Thu 01 Feb 2018, 12:58

Dear mistfire,

Could you please make available, or specify exactly, what WINE sfs you use with this puppy?
I tried several versions out of ppm, and always ended up with missing libraries, and extra packages that had to be found.
A matching WINE PER or SFS (prefer SFS) would be great.

Regards,

Volhout

mistfire · #748 Post by **mistfire** » Thu 01 Feb 2018, 13:02

@Volhaut almost any versions of wine should work. I tried wine 1.7 and 2.x from slackware packages. They work fine for me. You may ignore missing packages sometimes.

mistfire · #749 Post by **mistfire** » Thu 01 Feb 2018, 22:31

I successfully recompile a kernel. The culprit was the source code.

Right now Im trying to simplying the init for searching puppy files. I noticed that the detection of optical drive in the script was less reliable (This might be the culprit on booting Sage's machine). I try to make some improvements on it.

Boot logging is now strictly enforced on the next release and its more readable for easy troubleshooting.

mistfire · #750 Post by **mistfire** » Mon 05 Feb 2018, 01:39

New X-Slacko Slim iteration released:

Changes:
* Bugfix on CD/DVD drive detection (Both initrd and kernel)
* Some revisions on bluetooth detection (thanks argolance)
* Boot logging is now enabled by default (Initrd and rc.sysinit process only). The logs are now more readable and more detailed for easy troubleshooting (see /tmp/puppyboot.log)

* Some init script changes and simplified searching of puppy sfs files.

Download: https://drive.google.com/open?id=1UhOnI ... gUZGFxccBc
MD5 Checksum: 3591553041821f33fd16819ba2fa3c79

Sage · #751 Post by **Sage** » Mon 05 Feb 2018, 12:06

Alleluhia!
Just the weird setup menu, now:

No running instance of xfce-panel was found

Oh yes it was!

execute

:-

The notification area lost selection

Processing, please wait..

the constant, but unwanted, companion.

Otherwise, mostly everything is working. Not bad for a 164Mb .iso. Well done, misty. Notwithstanding, far too many menu entries and options.Probably could cut it to below 100Mb and include non-routine items in a PPM? Would make it even more attractive!

Permit me a few personal observations. This is an .iso run initially from the liveCD. If you want any type of installed version, better to provide an .img file like BK seems to prefer now? The recent fiasco of 'missing' .sfs illustrates a number of considerations. Firstly, look at the number of postings complaining that it 'won't run'. Note the length of time those correspondents so reporting have been around on this forum! Old lags have often been around the system extensively - if they say it 'doesn't work' - it doesn't work! If someone persistently says it doesn't work and there are only a couple saying so, it's because the silent majority can't be bothered, gave up and/or lost interest. Make sure offerings are extensively tested on as many machines as possible. Try to avoid Intel, they belong to the WIntel cartel beloved of the US DoJ, inter alia!
If you're developing a worthwhile project like this, stick at it until everyone wants it and nobody is saying 'it doesn't work'!
Best Regards & thanks.

step · #752 Post by **step** » Mon 05 Feb 2018, 13:53

Thank you, mistfire! Just so as you know it, when I run Slim in a QEMU box on Fatdog64-721, the virtual mouse pointer is jumpy and doesn't always follow the real mouse pointer.

mistfire · #753 Post by **mistfire** » Tue 06 Feb 2018, 10:08

@Sage good to know that it finally boot on your machine. That bug that you encountered was a weird one. I already encountered that many times. But when I rebooted it. The xfce starts normally. But dont worry I wil track that bug and fix that. Right now I'm making some adjustments on the init script to make it compact, reliable, less bugs, and very easy to troubleshoot.

Since that that X-Slacko Slim on your machine. Can you please send me the puppyboot.log located at /tmp?

@Step As of now I suggest to make some tweaks on your qemu vm. Also check out the cpu usage of your qemu program. Also enable qemu acceleration and AMD-V/Intel VTx feature on your computer (if supported)

mistfire · #754 Post by **mistfire** » Wed 07 Feb 2018, 23:41

Thanks Sage for the log file that you sent. I finally traced the weird bug that you encountered. It was on the quicksetup script. Im trying to revise that script

step · #755 Post by **step** » Thu 08 Feb 2018, 21:56

mistfire wrote: @Step As of now I suggest to make some tweaks on your qemu vm. Also check out the cpu usage of your qemu program. Also enable qemu acceleration and AMD-V/Intel VTx feature on your computer (if supported)

OK, thank you. I did a few more tests and CPU usage isn't a problem. I used QEMU to run several other different puppies based on Precise, Tahr Puppy, X-Slacko, (also Fatdog, DebianDog). The mouse mis-behaves only in X-Slacko Slim.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

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

wine pet