Puppy Linux Discussion Forum

Alert! Just completed a SG2D pristine boot on an old BIOS HP desktop (days of Core2).

interesting that a different behavior resulted. I am attaching the DMESG from it and the Hardinfo opening page. DMESG errors lines 217-221 & 757-760 & 793.

Unlike my 1st report on a PC with wireless keyboard-mouse, this PC has USB wired. On the UEFI AIO, the prnt-scrn and all keys behaved as expected, while this BIOS PC is exhibiting the exact KEYBOARD misbehavior reported weeks ago on Slacko v7/eSlacko, IIRC.

Further, this PC has no HDD nor DVD drive and is operating solely via the booted single SG2D USB booting the v8.0.1 ISO file.

I am trying to sort "why" these behavior are so different???

I have posted on this before with other PUPs/DOGs as it is a "general" problem with all at this point in time for PUP/DOG development for OOTB pristine use by any member booting a PC.

This post addresses something which is NOT a BUG but is certainly A PROBLEM ... TVs now replace old monitors.

Scenario
As it relates to our PCs, it is well known that, when compared to our OLD monitors, all TVs have

• better resolution

• larger viewing area

• built-in speakers

• HDMI connection

For those of us who have them connected, WE KNOW of 2 major benefits

• HDMI carries both video AND audio signaling

• No speaker space and NO speaker wiring is needed which reduces cable manaagement to the PC

My core i5 version 4xx series ONLY has a HDMI connection to the TV without any external PC speakers. Thus the ONLY wires connected to the desktop PC is an HDMI to the nVidia card and the PC power cable. Keyboard-mouse is USB wrieless.

Problem
The PC pristine boot to FirstRUN sets up the nouveau driver, OOTB, to TV. Yet the system does NOT allow mp3/mp4 audio to the TV no matter what I try via the audio wizard. NOr does a youtube via Firefox produce any audio.

But an important finding is that the current Chrome browser rnning Youtube DOES PRODUCE AUDIO VIA TV's speakers.
Thus, Chrome is the ONLY means of getting audio from the system from this pristine system using the nouveau means shown in FirstRUN.
This is a "key" anomaly for successful OOTB experience when using a TV as a monitor???

TVs and a PC offer a real benefit where it negates the wiring and the space that speakers take up.

HELP is needed in

1. having some test vehicle for users to use to have general PUP setup for sound available to all apps
   OR

2. a set of instructions for users to follow to get sound active to the TV in a pristine boot.

HELP!

P.S. Yes, I do realize that the instructions-steps may differ beyond a pristine boot when nVidia is the TV servicer. But,this post is aimed more at pristine booting rather than setup changes for drivers after a pristine boot.

the system does NOT allow mp3/mp4 audio to the TV no matter what I try

In /etc/libao.conf in BionicPup64, default_driver=pulse

I found some programs, like ogg123, would try to use pulse.
When I set default_driver=alsa then ogg123 used the alsa driver.

Setting default_driver=alsa does not seem to affect Firefox at all.

I think that for Puppy, default_driver should be set to alsa,
but I do not think it would make much difference to most people, most of the time.

As an additional finding for audio via the TV's speakers:

• Not only can I get audio from this pristine system ONLY via Chrome to youtube, BUT,

• Chrome will play my local files; namely mp3/ogg/mp4/etc.

To do so via Chrome, merely url to

file://(full-path-name)

Again, clicking on them from the file-manager will show video but will NOT audio the active files playing in their app windows. So, Chrome "knows somethng" about audio pathing in this PUP that is not obvious to the rest of this system.

I KNOW I am missing something and it may be obvious, but ???

In BionicPup32 there is a Multiple Sound Card Wizard (Right click on speaker icon in the Tray), that lets me select HDMI as audio output. Default is the internal sound card.

So far I couldn't find that Multiple Sound Card Wizard in Slacko64 8.0 pre-alpha.

@MagicZaurus and community, Slacko64-v8.0.1 development did something VERY clever: Its integrated in the speaker selection in the taskbar icon. Go look via right-click.

Hope that helps

ALPHA2 Report

• Hooray, sound across HDMI thru TV works OOTB for this nVidia card using "nouveau"

  

  FirstRUN.jpg (34.1 KiB) Viewed 1561 times

• Sound working across all desktop apps

• FirstRUN problem with arrow-keys emerging upon 'OK' still remains

• To get arrow-keys to perform properly, one MUST exit desktop and reload

• Question: Is FirstRUN no longer referred to as "QuickSetup 'FirstRUN' "? I see a Menu>Setup name change which might be in error.

• QEMU GUI entry in Menu is gone

• Keyboard arror-key issues disappear upon desktop restart

• QEMU and its Control Panel installed via PPM; BUT, QEMU-Gui entry is not installed in the Menus

Testing will continue in the morning.

It's worth mentioning that new test releases are uploaded to https://github.com/puppylinux-woof-CE/woof-CE/releases and enthusiastic users/testers can follow the woof-CE project to get notified

.. and there is one there right now hot off the cooker (491MB )

dimkr wrote: ↑Sat Mar 20, 2021 4:39 pm

It's worth mentioning that new test releases are uploaded to https://github.com/puppylinux-woof-CE/woof-CE/releases and enthusiastic users/testers can follow the woof-CE project to get notified

01micko wrote: ↑Sun Mar 21, 2021 10:07 am

.. and there is one there right now hot off the cooker (491MB )

dimkr wrote: ↑Sat Mar 20, 2021 4:39 pm

It's worth mentioning that new test releases are uploaded to https://github.com/puppylinux-woof-CE/woof-CE/releases and enthusiastic users/testers can follow the woof-CE project to get notified

Are those your builds?

amethyst wrote: ↑Sun Mar 21, 2021 10:13 am

01micko wrote: ↑Sun Mar 21, 2021 10:07 am

.. and there is one there right now hot off the cooker (491MB )

dimkr wrote: ↑Sat Mar 20, 2021 4:39 pm

It's worth mentioning that new test releases are uploaded to https://github.com/puppylinux-woof-CE/woof-CE/releases and enthusiastic users/testers can follow the woof-CE project to get notified

Are those your builds?

Not exactly. They are built locally and when I'm satisfied I run an action at GitHub that reproduces my build. It saves me uploading. This will be the 'new normal' through the testing phase.

Updates from 'and a bit'

01micko wrote: ↑Sat Feb 20, 2021 12:17 pm

just dust

4 bit Updates
(part 1)

• abiword > rebuilt

• arp-scan > rebuilt

• curlftpfs > rebuilt

• dunst > upgraded

• fpm2 > rebuilt

• gexec > rebuilt

• glipper-lite > rebuilt

• gmeasures > rebuilt

• hexchat > removed

• htop > upgraded

• irssi > added

• libtubo > rebuilt

• mokutil > rebuilt

• mpscan > rebuilt

• musl > upgraded

• pnscan > rebuilt

• pure-ftpd > rebuilt

• samba > upgraded

• sane-backends > upgraded

• sbsigntools > rebuilt

• simple-mtpfs > rebuilt

• switch2 > rebuilt

• usb-modeswitch > upgraded

• vamps > rebuilt

• vobcopy > rebuilt

• wv > rebuilt

• xfdiff > rebuilt

• xsane > rebuilt

(part 2)

• a52dec > rebuilt

• aaa_publibs64 > added

• ffmpeg > rebuilt +speex

• galculator > rebuilt +gtk3

• hiawatha > upgraded

• irssi > rebuilt -perl

• libart > added

• libgnome* > rebuilt

• libgtkhtml > rebuilt

• musl > rebuilt

• samba > rebuilt

• streamripper > rebuilt -faac (non-free)

.. and numerous woof-ce fixes and features.

Just a very minor thing which I observed. Gnumeric is in the menu twice, once under Business and once under Personal.

PeasyPort and YASSM working now in this release.

Downloaded latest alpha ISO to a SG2D USB into folder "/BOOTISOS" where prior ISOs reside.

Booted the USB, selecting the Slacko v8.1. Allowed Slacko's GRUB2 to default boot to desktop on tis Intel PC (circa 2009) that has no HDD/DVD.

Filled FirstRUN fields as I normally do for all PUPs and upon hitting OK, the direction-key problem surfaced.

.
This is a bug I am familiar with, so restarting the desktop the keys return to normal behavior.

I shutdown without saving and rebooted pristine, again. Upon desktop I did NOT change the default FirstRUN screen and merely hit OK. No direction-problem follows. Reopen QuickSetup and filled in a single field; namely the GMT+Hardware clock checkbox. Hit OK and again ... No problem. Reopened and change the Time from Internet and hit OK...NO problem. Re opened and set the Hostname; again NO problem.

So, its obvious that filling the multiple selections on its 1st use somehow causes the deriction-key problem. But at this point I have no clue.

Again, I know the circumvention for now. Excepting for these reports on this, I am at a lost to diagnose.

This problem may disappear as Slackware moves to GA or it may be related to the GTK upgrade.

Testing other system elements will continue.

Could the QEMU GUI launcher be added back into the PUP Menus? Gone missing since 1st alpha. Its an excellent alert to how to get QEMU active.

Currently one has to be knowledgible of the qemu-gui "terminal" command, to get started.

Getting QEMU into the system is made simple by selecting ONLY the QEMU v5.2 as it installs both QEMU and an its accompanying GUI.

The GUI has a bug if you select Enable SSH/SAMBA the QEMU command generated has a bad entry and the virtual PC wont start due to command failure.

Further, after QEMU is installed via PPM, it is NOT showing up in the PUP Menus. Also, tried "fixmenu" on the console to no avail.

So far, other PUP subsystems are as expected...solid & responsive.

Funny...v8.0.1 gave me a nouveau delivered sound experience via pristine OOTB to the TV over the nVidia HDMI connection. This OOTB meant no nVidia driver was needed for such.

But, this version is not. The sound search, again, begins.

Hmmm???

EDIT: HOLD THE PRESSES! Update. The desktop music player is not playing my audio files, yet Chrome browser is. I can Youtube with audio and I can run the local media file in the browser with sound as well. Now, a new Hmmm???

EDIT2: Firefox, like the desktop apps, are not playing audio.

EDIT3: There appears to be a problem with TV & sleep that may be affecting distro's audio operation when awakening (in my TV's case, awakening is a TV power-on to get back to the HDMI session where Slacko is running. When re-awakening, no audio. To get audio back, I must exit the desktop to the prompt and re-enter.

is the alsa Auto-Mute DISABLED in the menu Setup/ALSA? Used to be the default was ON.

Regards
8Geee

Now fixed in Woof-CE - https://github.com/puppylinux-woof-CE/w ... 96f45203f5

There was a problem with Gnumeric when working with .xls files
/usr/lib64/gconv from glibc was not being put into the build..........