Puppy Linux Discussion Forum

@TerryH
Does internal SSD was detected on probedisk and probepart command?

May I know what changes in the root were not saved?

Did you hear any sound when inserting a new device?

mistfire wrote: ↑Thu Aug 27, 2020 10:21 pm @TerryH
Does internal SSD was detected on probedisk and probepart command?

May I know what changes in the root were not saved?

Did you hear any sound when inserting a new device?

probedisk & probepart identifies all disks & partitions correctly.

The issue I am still having is creating folders. I have created folders many times in pcmanfm and also using mkdir as root in terminal, on reboot they are not there. These folders have been created in /media or /mnt. They are not retained at next boot, so currently need to recreate.

To test I also created a folder in /root/Downloads. That folder is saved and there when rebooting.

As for the sound, I generally have sound muted, so hadn't noticed any sound when I plugged a usb drive. There are sounds played when plugging or unplugging a usb drive, they each play twice. The plug and unplug are different. I also checked with an SD card, which is also not visoble after inserting.

Edit: I have also just confirmed that the creation of /etc/asound.conf does not get saved when shutting down/rebooting. I have created it using the soundcard wizard and also created it manually. After booting it is not included and needs to be created again for sound to work.

Edit 2: This is very strange. I booted with a different puppy and checked the save folder and /etc/asound.conf is present. I was going to add it manually in the save folder. I then booted back into tazpuppy and it isn't there. I checked initrd/pup_rw/etc and there is no asound.conf. So there appears to be an issue with the layered filesystem.

It gets stranger, there is a version of /asound/conf.old included in the pup_rw/etc. The timestamp indicates it is from one of my attempts running the sound card wizard.

Edit 3: To do some further checking I swapped kernels to 4.19.128, the issues with asound.conf still exist.

@TerryH
What files did you put on /media or /mnt?

Ok, I will check the soundcard config.

mistfire wrote: ↑Fri Aug 28, 2020 11:01 pm @TerryH
What files did you put on /media or /mnt?

Ok, I will check the soundcard config.

None directly, I created the folders/directories to use to mount the partitions I can't access as they are not shown in pcmanfm until I mount them.

@TerryH

TazPuppy stores soundcard settings at /etc/asound.state
/etc/asound.conf is used to override the /etc/asound.state

See this links
https://wiki.archlinux.org/index.php/Ad ... chitecture
https://wiki.parabola.nu/Advanced_Linux ... chitecture

mistfire wrote: ↑Sat Aug 29, 2020 1:46 pm @TerryH

TazPuppy stores soundcard settings at /etc/asound.state
/etc/asound.conf is used to override the /etc/asound.state

See this links
https://wiki.archlinux.org/index.php/Ad ... chitecture
https://wiki.parabola.nu/Advanced_Linux ... chitecture

This doesn't answer the issue. The issue is that asound.conf doesn't survive a reboot. It is in the save folder, but is not being written to the pup_rw on bootup. Why?

The asound.conf is generated by the multiple soundcard wizard. The sound defaults to HDMI, the asound.conf directs sound to the internal sound.

@TerryH
Thanks for clarification I will investigate that issue

TazPuppy 5.0 RC8 released

Changes:
* Built from latest slitaz rolling core release
* Fixed file and folder permission issue
* Fixed soundcard auto configuration
* Some bugfixes

Download: https://drive.google.com/file/d/1zVAwej ... zJENbs9zr_
MD5 Checksum: eea4a3cdf820cfb19269d507ba415db3

Build-kit: https://drive.google.com/file/d/1jWeuS4 ... YjryME4ljv

@TerryH

I finally found the problem why /etc/asound.conf disappears

Upon shutdown TazPuppy remembers the hardware setup. In case of sound card it relies on /proc/asound/card. However it fails to remember the soundcard because /proc/asound/card disappears when ALSA was stopped. So when the TazPuppy boot again, it sees that the soundcard was changed and delete the /etc/asound.conf.

This issue is now fixed on TazPuppy 5.0 RC8

mistfire wrote: ↑Sun Aug 30, 2020 4:30 pm @TerryH

I finally found the problem why /etc/asound.conf disappears

Upon shutdown TazPuppy remembers the hardware setup. In case of sound card it relies on /proc/asound/card. However it fails to remember the soundcard because /proc/asound/card disappears when ALSA was stopped. So when the TazPuppy boot again, it sees that the soundcard was changed and delete the /etc/asound.conf.

This issue is now fixed on TazPuppy 5.0 RC8

Issues from RC7 are OK now. RC8 running very smoothly now. Thank you.

mistfire wrote: ↑Fri Aug 21, 2020 8:08 am @Pazzo
Could please boot tazpuppy and get the files located at /var/hwdata and send also here.

I've been unable to keep testing for the past few weeks. Back now. Will download the latest RC8 and see what happens with syncing time.

mistfire wrote: ↑Fri Aug 21, 2020 8:08 am @Pazzo
Could please boot tazpuppy and get the files located at /var/hwdata and send also here.

Still not syncing time. I ran Time Zone configuration, selected Brazil/Sao_Paulo. Ok
Rebooted, nothing. Ran SliTaz Config Dialogs/Set Date, nothing again. When I run 'Time is', it recongnizes I'm in Sao Paulo, shows my local time, but the panel clock never changes from UTC.

These are the files ate /var/hwdata:

file:///var/hwdata/backlights.lst
file:///var/hwdata/kernel.lst
file:///var/hwdata/onboard-devices.lst
file:///var/hwdata/screen.lst
file:///var/hwdata/soundcards.lst
file:///var/hwdata/videocards.lst

Do you need the actual files? How do I upload them here?

Another bug: now Slitaz Panel never enters. Tried both 'Package Manager' (that was working previously) and 'Slitaz Panel'. Nothing. Both open an empty TazWeb Browser window (realized just now that it runs in this browser window). When booting, I click on the "check updates" that shows up as a notification of the packages, and same happens.

Can I upgrade packages in terminal?

@Pazzo

Yes I need that. Put those files in a tarball and upload it here
Did you boot TazPuppy without save file?
You upgrades from command line just type

mistfire wrote: ↑Sat Sep 05, 2020 4:39 am Did you boot TazPuppy without save file?

I believe I did use a save file. I made a mistake on my first boot with RC8, and did not save at first shutdown, but I think it is ok, now. My settings from last night are all ok.

mistfire wrote: ↑Sat Sep 05, 2020 4:39 am You upgrades from command line just type

Code: Select all

sudo tazpkg up

Great, did just that and it went ok. About 150 package upgrades.

Files from my /var/hwdata are attached.

Hey, I was concentrated replying the message, didn't notice the time is synced. Panel clock is showing correctly my local time. It didn't happened last night after the reboot. I did nothing.

About the Slitaz Panel not loading, after a while on the blank screen, it shows a message "Could not connect: Connection timed out".

Does the same if through Package Manager or Slitaz Panel, on the menu, or clicking in the packages notification ant bootup.

TazPuppy 5.0 RC9 released

Changes:
* Fixed networking issue
* Fixed broken TazPanel
* Added ndiswrapper management and loading
* Added gpm
* Improvements on initrd
* Some bugfixes

Download: https://drive.google.com/file/d/1kuJi3Z ... 8kZ8Gf1tLV
MD5 Checksum: f00405ebe021634811012382da3ead61

Build-kit: https://drive.google.com/file/d/138P0Ri ... DhDLRypEEt

@Pazzo
Could you please test this latest TazPuppy release?

Up and running!
Upgrade was easy, easy. Flashed the iso to USB, booted from USB and savefile was found with my settings. Did the install to the same directory (frugal), rebooted, and checked upgrades.

TazPanel is back, ok!

Time sync still not working. I've made a screenshot of 'Time is' just to show you. File attached.

**Just a note: the download file is still named "RC8", but I checked against the actual RC8, to make sure this was a new one.**

(I edited so the attached file is a tar, because the image was disturbingly showing up)

Updated to RC9. There are still issues with asound.conf, not being present after booting, following running the soundcard wizard to select PCH as default soundcard on previous boot. This occurs on a clean boot and a new save folder created.

TazPuppy 5.0 RC10 released

Changes:
* Improvements on soundcard auto configuration
* Improvements on system clock
* Improvements on time sync. To enable auto sync, Just turn on "ALWAYS ENABLE" on TazPanel->Settings->Summary. The time sync runs on every boot if active network connection is detected.
* Improved TazPanel

Download: https://drive.google.com/file/d/18fCzH5 ... ZEzM5WdFxL
MD5 Checksum: 8afa9b86bc8040308de5ce4407cc0e39

Build Kit: https://drive.google.com/file/d/1gPMTeE ... J1vK2vJsyE

@Pazzo
@TerryH

Could please test this latest release? Thanks

Soundcard settings still not being maintained following reboot. I replaced rc9 with rc10 and booted with pfix=ram. I ran default soundcard wizard to get sound output. I created a new save folder. On reboot there is still no sound and the /etc/asound.conf was still not being restored from save.

TerryH wrote: ↑Tue Sep 15, 2020 10:33 pm Soundcard settings still not being maintained following reboot. I replaced rc9 with rc10 and booted with pfix=ram. I ran default soundcard wizard to get sound output. I created a new save folder. On reboot there is still no sound and the /etc/asound.conf was still not being restored from save.

I'm fixing this issue. I created a new method for saving installed soundcards correctly and reliably. I hoped it works

TazPuppy 5.0 RC11 released

Changes
* Improved ALSA and soundcard auto configuration

Download: https://drive.google.com/file/d/1L8ebDp ... 3oXwGLWWfg
MD5 Checksum: f2bd8cf6f19f2c93a60bc07b6ed77b6c

Build kit: https://drive.google.com/file/d/1POff8U ... 0m0NCF6g6a

To test sound setup I replaced RC10 with RC11 and then booted with pfix=ram. I ran soundcard wizard and set up wifi then reboot creating a new save folder. On boot up sound was working. To test further I did a further 5 shutdown/reboot cycles. Sound OK on all attempts.

To further test I used a previously created save folder. On first boot I needed to run soundcard wizard to get sound working. On 2 reboots sound was OK. On the 3rd boot the asound.conf was not included, so had no sound again. I re-ran soundcard wizard. Sound has been working on 3 subsequent boots.

It seems like it is OK now, but will have to check moving forward. I will probably use the new save folder and copy changes I want to keep from old save folder.

TerryH wrote: ↑Wed Sep 16, 2020 9:33 pm To test sound setup I replaced RC10 with RC11 and then booted with pfix=ram. I ran soundcard wizard and set up wifi then reboot creating a new save folder. On boot up sound was working. To test further I did a further 5 shutdown/reboot cycles. Sound OK on all attempts.

To further test I used a previously created save folder. On first boot I needed to run soundcard wizard to get sound working. On 2 reboots sound was OK. On the 3rd boot the asound.conf was not included, so had no sound again. I re-ran soundcard wizard. Sound has been working on 3 subsequent boots.

It seems like it is OK now, but will have to check moving forward. I will probably use the new save folder and copy changes I want to keep from old save folder.

This issue is not resolved. The problem still intermittently occurs. I logged in with the newly created save folder, sound was not working. I rebooted sound worked on this boot. So the issue with not including /etc/asound.conf still occurs.

@TerryH
Did you always installed external audio device/soundcard on your computer?

ALSA auto configuration triggers if the last installed audio devices upon shutdown does not match with audio devices installed upon boot.

Can you please do the following?

• 1. Boot tazpuppy on pristine state, run alsa wizard and create new save file and reboot

• 2. Upon reboot load the newly save file. Wait until it boot to desktop

• 3. Get the boot.log file located at /var/log/slitaz and paste it on /home/tux and rename it as boot-1.log (first boot with save file)

• 4. Reboot TazPuppy again with loaded save file loaded

• 5. Do step 3 and 4 for boot-2.log, boot-3.log, boot-4.log

Upload these four boot log files to this thread

mistfire wrote: ↑Fri Sep 18, 2020 9:19 am @TerryH
Did you always installed external audio device/soundcard on your computer?

No, as mentioned in prior posts, only internal sound is used.

ALSA auto configuration triggers if the last installed audio devices upon shutdown does not match with audio devices installed upon boot.

Can you please do the following?

• 1. Boot tazpuppy on pristine state, run alsa wizard and create new save file and reboot

• 2. Upon reboot load the newly save file. Wait until it boot to desktop

• 3. Get the boot.log file located at /var/log/slitaz and paste it on /home/tux and rename it as boot-1.log (first boot with save file)

• 4. Reboot TazPuppy again with loaded save file loaded

• 5. Do step 3 and 4 for boot-2.log, boot-3.log, boot-4.log

Upload these four boot log files to this thread

Ok iwill be out for the day, will do this this eveening when i return home.

As requested I booted and created a new save folder.
First reboot the sound worked without needing to run soundcard wizard.
Second reboot - no sound ran soundcard wizard
Third reboot - no sound ran soundcard wizard
Fourth reboot - sound worked
Fifth reboot - sound worked
Sixth reboot - no sound ran souncard wizard

It also didn't appear to matter whether the sound was muted or unmuted at shutdown in determining whether sound would work following booting.

I also included the shutdown log present from the last reboot, so is for the shutdown following boot 5.