X-Slacko Slim 4.4r49 (unique, stable, and flexible)
Fantastic! Weird initial (but evidently irrelevant) error messages at boot followed by countdown (not seen that before), straight into setup screen (longish delay finding correct resolution, but did get it right first time), restart after selecting options, DHCP already selected correctly - sound comes up correctly, too (first time).
Excellent work, misty, can really use this item for testing & diagnostics - don't change anything!
Excellent work, misty, can really use this item for testing & diagnostics - don't change anything!
Thank you for 4.4r10. It generally works well in QEMU.
I tried but it didn't help. The mouse still blocks at hidden boundaries. It's never the same boundary, I can't spot a pattern. Sometimes the mouse even works OK for a while.mistfire wrote:@Step try to run xorgwizard from command line. Then select fbdev as xorg driver then run X. If failed then try to Load xorg conf. Select xorg-uefi-failsafe conf file
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
too fast to capture, something about 'early console', several other lines before counter starts. Not worth messing with?! Extra front material not really required if it all works.....what error msg..
Another interesting feature: if I ignore setup, dhcp is active, put valid URL into Midori, it starts to find the website then exits back to setup?
Facebook information..
"an alternative, for testing, try with x-slacko-slim, http://www.murga-linux.com/puppy/viewtopic.php?t=107313 ..have Bluetooth out-of-the-box"
Facebook information.. It would be nice that Puppy easily connect and communicate with Bluetooth equipment.
Facebook information.. It would be nice that Puppy easily connect and communicate with Bluetooth equipment.
- reprise...what error msg..
These upfront messages differ between machines. On a very old A1100+, there were none and no counter, either - it went straight into normal boot. On a 64bit machine, some front material and the counter showed up. On an A2400+, my normal testbed, a whole slew of front data showed, counter included. Good news, though - all rigs successfully boot to a visible screen, albeit extremely slowly on older junk.
This is now a really good vehicle for testing and diagnosis. Probably plenty of scope to strip out utilities less germane to such a basic OS and leave the fancy stuff to FD64, etc? Rather have FF and ditch eg Bluetooth & co.!
New X-Slacko Slim iteration released
Changes:
* Improved network connection management
* Added metric support in Dougal's Network Wizard and Frisbee
* Detecting QEMU machine and use fbdev instead of modesetting (highly experimental)
* xfce-panel does not restart when whisker menu is used upon install/remove packages
* Some fixes
Download: https://drive.google.com/open?id=1kx4BY ... iQxSbzo5jq
MDS Checksum: 26bc9596b173d48c828af0755aa050be
Changes:
* Improved network connection management
* Added metric support in Dougal's Network Wizard and Frisbee
* Detecting QEMU machine and use fbdev instead of modesetting (highly experimental)
* xfce-panel does not restart when whisker menu is used upon install/remove packages
* Some fixes
Download: https://drive.google.com/open?id=1kx4BY ... iQxSbzo5jq
MDS Checksum: 26bc9596b173d48c828af0755aa050be
r10 firwallstatus
Dear mistfire,
Some observations on Xslacko Slim 4.4 r10.
1/
Installed Xslacko Slim 4.4 r10 on SD card and USB stick. Both feature a nasty behaviour.
The "firewallstatus" is eating significant CPU power. Sometimes up to 50% (using "top").
Regardless if I use the firewall, or not.
Have you seen this before ?
I simply kill the PID, and all is okay. So I am managing well with r10.
FYI there is no icon for the firewall in the tray.
If you want some help in debugging, inform me what you need.
2/ tried to play with bluetooth, and once I managed to get contact with my external speakers, once I managed to get the bluetooth icon in the tray. But never succeeded afterwards. I know bluetooth is cursed in linux (around 2010 the debians of this world had it working relatively well, but now it seems an undervalued feature, and it even does not work well in Ubuntu anymore....so I am not disappointed, only want to inform you it is not working in my case).
Some observations on Xslacko Slim 4.4 r10.
1/
Installed Xslacko Slim 4.4 r10 on SD card and USB stick. Both feature a nasty behaviour.
The "firewallstatus" is eating significant CPU power. Sometimes up to 50% (using "top").
Regardless if I use the firewall, or not.
Have you seen this before ?
I simply kill the PID, and all is okay. So I am managing well with r10.
FYI there is no icon for the firewall in the tray.
If you want some help in debugging, inform me what you need.
2/ tried to play with bluetooth, and once I managed to get contact with my external speakers, once I managed to get the bluetooth icon in the tray. But never succeeded afterwards. I know bluetooth is cursed in linux (around 2010 the debians of this world had it working relatively well, but now it seems an undervalued feature, and it even does not work well in Ubuntu anymore....so I am not disappointed, only want to inform you it is not working in my case).
@Volhaut.
I already notice that firewall tray problem but it rarely happen. I want to fix that issue on that tray but it was a binary compiled. Im fluent in bash scripting but not in C thing. Can you help to trace that problem in firewall tray source code and fix it. Also if you have time, can you also modify the follwing source code to add a certain features
* whisker-menu read username from a file instead of hardcoding the username in whisker
* pup-volume-monitor show mounted disk image icon and available to disappear once the disk image was unmounted.
Regarding the bluetooth audio dont forget to set the audio output of the player to alsa in order to stream the sound
I already notice that firewall tray problem but it rarely happen. I want to fix that issue on that tray but it was a binary compiled. Im fluent in bash scripting but not in C thing. Can you help to trace that problem in firewall tray source code and fix it. Also if you have time, can you also modify the follwing source code to add a certain features
* whisker-menu read username from a file instead of hardcoding the username in whisker
* pup-volume-monitor show mounted disk image icon and available to disappear once the disk image was unmounted.
Regarding the bluetooth audio dont forget to set the audio output of the player to alsa in order to stream the sound
I tested 4.4r11 in QEMU on Fatdog64-721 but X-Slacko Slim doesn't detect that it's running in QEMU and it sets the modesetting video driver.
/tmp/puppyboot.log says:
Checking if the computer is Qemu...
The machine is not qemu.
grep -i qemu output in /tmp attached.
/tmp/puppyboot.log says:
Checking if the computer is Qemu...
The machine is not qemu.
grep -i qemu output in /tmp attached.
- Attachments
-
- qemu-xslim.png
- (82.34 KiB) Downloaded 128 times
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
Oops
I would love to....if I had this skill. I am beginning to learn a bit of C in playing with the Arduino, but I am in no way capable of fixing things like this... Sorry. would love to....mistfire wrote:@Volhaut.
I already notice that firewall tray problem but it rarely happen. I want to fix that issue on that tray but it was a binary compiled. Im fluent in bash scripting but not in C thing. Can you help to trace that problem in firewall tray source code and fix it. Also if you have time, can you also modify the follwing source code to add a certain features
* whisker-menu read username from a file instead of hardcoding the username in whisker
* pup-volume-monitor show mounted disk image icon and available to disappear once the disk image was unmounted.
Regarding the bluetooth audio dont forget to set the audio output of the player to alsa in order to stream the sound
Volhout