Puppy Linux Discussion Forum

jrb wrote: ↑Sun Feb 19, 2023 5:20 pm

mastofa276 wrote: ↑Sun Feb 19, 2023 4:57 pm

Hello, I am just puppylinux user, and I tried this puppy version on my intel baytrail tablet, and it works well but where I can download devx and kernel source sfs files?,
and thanks you for creating this puppy version, its great

Glad you like it. Haven't posted devx yet, its still early days in development. Day 3 to be exact. Lots more updates to come. Can post devx if you want but I have to leave in 15 minutes so it will have to wait until this afternoon. The Kernel is from @peebee and I'll track down a link when I get back.

Did you update the ISO as mentioned in post2?

Cheers, J

Thanks J, I appreciate it, I still not yet update the ISO, but tried the bugs fix you provided. I think it works well on my tablet because the kernel and system structure very suited for it, I need devx and kernel source to build silead touchscreen module

mastofa276 wrote: ↑Sun Feb 19, 2023 5:36 pm

jrb wrote: ↑Sun Feb 19, 2023 5:20 pm

mastofa276 wrote: ↑Sun Feb 19, 2023 4:57 pm

Hello, I am just puppylinux user, and I tried this puppy version on my intel baytrail tablet, and it works well but where I can download devx and kernel source sfs files?,
and thanks you for creating this puppy version, its great

Glad you like it. Haven't posted devx yet, its still early days in development. Day 3 to be exact. Lots more updates to come. Can post devx if you want but I have to leave in 15 minutes so it will have to wait until this afternoon. The Kernel is from @peebee and I'll track down a link when I get back.

Did you update the ISO as mentioned in post2?

Cheers, J

Thanks J, I appreciate it, I still not yet update the ISO, but tried the bugs fix you provided. I think it works well on my tablet because the kernel and system structure very suited for it, I need devx and kernel source to build silead touchscreen module

I have posted the Devx file for the latest alpha build, upup-22.04-jrb-A3.iso, on page 1 post 2. kernel_sources-5.15.80-kernel-kit.sfs are here

The third Alpha, upup-22.04-jrb-A3.iso is posted on page1 post 1. Its looking good. MPV is playing DVD's and video files, alsaplayer is playing CD's and audio files. @dimkr found the problem with Deadbeef so its in there too although I haven't got it playing CD's yet. I put in osmo-0.2.10-dunfell64 just because I need it, maybe others do too. Fixed an Xournalpp bug. Also put in the traditional gcolor2. I think we're getting close to Beta.

Enjoy, J

Edit: I'm getting confused with all the different md5sums using .delta files, so just ISO's from here.

Quick check before I continue. md5sum for the A3 iso from post 2 is: 219b271cc80c19615a821a19cb3046aa

Downloading the delta and generating A3 I get: b74ca91a84a5f246e7d4eb33fa9d2bcc

I've downloaded and generated twice with the same md5sum for the generated iso... OK to procede?

Marv wrote: ↑Mon Feb 20, 2023 1:35 am

Quick check before I continue. md5sum for the A3 iso from post 2 is: 219b271cc80c19615a821a19cb3046aa

Downloading the delta and generating A3 I get: b74ca91a84a5f246e7d4eb33fa9d2bcc

I've downloaded and generated twice with the same md5sum for the generated iso... OK to procede?

Sorry for the confusion, the md5sum listed is just for the .delta
upup-22.04-jrb-A3.iso md5sum b74ca91a84a5f246e7d4eb33fa9d2bcc

Maybe this Xdelta business is more confusing than its worth.

Once things boil down to smaller fixes, the Xdelta scheme pays its way. I'm used -peebeeland- to just having the md5sums listed for the generated isos. Old dog At any rate, it is looking really good here. The color selector is back, CDs play in all of the options, deadbeef included, and DVDs play straight off in mpv. Offhand, I don't see any missing icons now and after running a ydrv stripped for the first look at A3, I'm back to the Flat-gray-rounded theme with puppy standard icons. If I was chasing anything else, I forget. Posting from Brave portable set as the default browser.

Cheers -and Thanks-, Jim

Marv wrote: ↑Mon Feb 20, 2023 2:43 am

CDs play in all of the options, deadbeef included

Have you got deadbeef working with CD's? I couldn't get it to work. Got any hints?

I just set as default, deadbeef all.cda, put cd in, select play in the dialog box, Then I did have to close a log box and "add an audio CD" (File>add audio CD). A bit clunky, but I have never used it so... Playing now.

Marv wrote: ↑Mon Feb 20, 2023 3:27 am

I just set as default, deadbeef all.cda, put cd in, select play in the dialog box, Then I did have to close a log box and "add an audio CD" (File>add audio CD). A bit clunky, but I have never used it so... Playing now.

Ha Ha, I guess my problem was "operator error" or more likely ignorance. Thanks for walking me through it.

Cheers, J

Thanks J, for devx and kernel source, I just checked the bluetooth manager is not working.
plese someone help, show me how to set up the bluetooth, my bluetooth device is rtl8723bs, the weird thing is according to google this chip have dual use for wifi and bluetooth, but my wifi use broadcomm chip, its confusing

More fixes on the way:

https://github.com/puppylinux-woof-CE/woof-CE/pull/3921
https://github.com/puppylinux-woof-CE/woof-CE/pull/3925
https://github.com/puppylinux-woof-CE/woof-CE/pull/3923

mastofa276 wrote: ↑Mon Feb 20, 2023 4:38 am

Thanks J, for devx and kernel source, I just checked the bluetooth manager is not working.
plese someone help, show me how to set up the bluetooth, my bluetooth device is rtl8723bs, the weird thing is according to google this chip have dual use for wifi and bluetooth, but my wifi use broadcomm chip, its confusing

Sorry to say this mastofa but, retro-grouch that I am, I have no bluetooth tech at all. So, Anyone out there who can help? Try @rockedge 's Puppy Linux Forum Search.
Heres the output for blueman-manager:

root@puppypc15830:~$ blueman-manager
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Python path configuration:
  PYTHONHOME = (not set)
  PYTHONPATH = (not set)
  program name = '/usr/bin/python3'
  isolated = 0
  environment = 1
  user site = 1
  import site = 1
  sys._base_executable = '/usr/bin/python3'
  sys.base_prefix = '/usr'
  sys.base_exec_prefix = '/usr'
  sys.platlibdir = 'lib'
  sys.executable = '/usr/bin/python3'
  sys.prefix = '/usr'
  sys.exec_prefix = '/usr'
  sys.path = [
    '/usr/lib/python310.zip',
    '/usr/lib/python3.10',
    '/usr/lib/lib-dynload',
  ]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007fd90138a500 (most recent call first):
  <no Python frame>

And also for blueman-adapters:

root@puppypc15830:~$ blueman-adapters
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Python path configuration:
  PYTHONHOME = (not set)
  PYTHONPATH = (not set)
  program name = '/usr/bin/python3'
  isolated = 0
  environment = 1
  user site = 1
  import site = 1
  sys._base_executable = '/usr/bin/python3'
  sys.base_prefix = '/usr'
  sys.base_exec_prefix = '/usr'
  sys.platlibdir = 'lib'
  sys.executable = '/usr/bin/python3'
  sys.prefix = '/usr'
  sys.exec_prefix = '/usr'
  sys.path = [
    '/usr/lib/python310.zip',
    '/usr/lib/python3.10',
    '/usr/lib/lib-dynload',
  ]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007f1159012500 (most recent call first):
  <no Python frame>

Sadly my Python skills are minimal to non-exsistant as well so its not looking good. I'll play with it a bit, might stumble into something, stranger things have happened.

Good Luck, J

dimkr wrote: ↑Mon Feb 20, 2023 7:47 am

More fixes on the way:

https://github.com/puppylinux-woof-CE/woof-CE/pull/3921
https://github.com/puppylinux-woof-CE/woof-CE/pull/3925
https://github.com/puppylinux-woof-CE/woof-CE/pull/3923

Thanks for the improvements dimkr. I'm looking forward to using them.

You wouldn't happen to know anything about bluetooth would you? See post above.

@jrb Don't forget the Puppy Linux Forum search here: https://psearch.puppylinux.com

mastofa276 wrote: ↑Mon Feb 20, 2023 4:38 am

Thanks J, for devx and kernel source, I just checked the bluetooth manager is not working.
plese someone help, show me how to set up the bluetooth, my bluetooth device is rtl8723bs, the weird thing is according to google this chip have dual use for wifi and bluetooth, but my wifi use broadcomm chip, its confusing

@BarryK and @plinej have been working on Bluepup. I've converted @plinej 's bluepup.tar.xz into a .pet. After installing bluepup.pet and inotify-tools and bluez-toolz from PPM at least I get a gui on screen.

rockedge wrote: ↑Mon Feb 20, 2023 1:53 pm

@jrb Don't forget the Puppy Linux Forum search here: https://psearch.puppylinux.com

Thanks rockedge, I don't think I knew about this one. But then I'm pretty good at forgetting.

jrb wrote: ↑Mon Feb 20, 2023 1:26 pm

You wouldn't happen to know anything about bluetooth would you? See post above.

I know a little about many things

I'll take a look, Bluetooth should work fine unless Python is broken or fdrv has missing firmware (try dmesg | grep -i firmware).

EDIT: yes, Python is broken. Checking.

EDIT 2: @jrb the Pytho package is broken, at least one Python module is missing. I bet 1download failed to download at least one package. Try ./2createpackages python: if it fails because one package is missing, ./1download; ./2createpackages python. Blueman works fine in https://github.com/puppylinux-woof-CE/w ... 4189614407.

dimkr wrote: ↑Mon Feb 20, 2023 4:39 pm

jrb wrote: ↑Mon Feb 20, 2023 1:26 pm

You wouldn't happen to know anything about bluetooth would you? See post above.

I know a little about many things

I'll take a look, Bluetooth should work fine unless Python is broken or fdrv has missing firmware (try dmesg | grep -i firmware).

EDIT: yes, Python is broken. Checking.

EDIT 2: @jrb the Pytho package is broken, at least one Python module is missing. I bet 1download failed to download at least one package. Try ./2createpackages python: if it fails because one package is missing, ./1download; ./2createpackages python. Blueman works fine in https://github.com/puppylinux-woof-CE/w ... 4189614407.

OK, I renamed the original /packages-upup/python packages and ran ./2createpackages python. No error messages from ./2createpackages. I then created pythonA.files and python.files listing contents. Xdiff tells me the files are identical. Perhaps I should build without python and blueman and then try installing blueman?

dimkr wrote: ↑Mon Feb 20, 2023 4:39 pm

jrb wrote: ↑Mon Feb 20, 2023 1:26 pm

You wouldn't happen to know anything about bluetooth would you? See post above.

I know a little about many things

I'll take a look, Bluetooth should work fine unless Python is broken or fdrv has missing firmware (try dmesg | grep -i firmware).

EDIT: yes, Python is broken. Checking.

EDIT 2: @jrb the Pytho package is broken, at least one Python module is missing. I bet 1download failed to download at least one package. Try ./2createpackages python: if it fails because one package is missing, ./1download; ./2createpackages python. Blueman works fine in https://github.com/puppylinux-woof-CE/w ... 4189614407.

Sorry, forgot to run

dmesg | grep -i firmware

Here's the output:

root@puppypc15830:~$ dmesg | grep -i firmware
[    1.092840] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[   28.641252] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)

jrb wrote: ↑Mon Feb 20, 2023 5:46 pm

Perhaps I should build without python and blueman and then try installing blueman?

No, only make sure you have packages-upup/python/usr/lib/python3.10/encodings/__init__.py. If you don't, something about your build is broken.

2createpackages should say something like:

2023-02-16T01:13:06.8306428Z Processing python
2023-02-16T01:13:06.8325900Z  processing libmpdec3_2.5.1-2build2_amd64.deb
2023-02-16T01:13:06.8385769Z  processing libpython3-stdlib_3.10.6-1~22.04_amd64.deb
2023-02-16T01:13:06.8443379Z  processing libpython3.10-minimal_3.10.6-1~22.04.2_amd64.deb
2023-02-16T01:13:06.9161522Z  processing libpython3.10-stdlib_3.10.6-1~22.04.2_amd64.deb
2023-02-16T01:13:06.9458887Z  processing libpython3.10_3.10.6-1~22.04.2_amd64.deb
2023-02-16T01:13:06.9756006Z  processing media-types_7.0.0_all.deb
2023-02-16T01:13:07.1543961Z  processing python-is-python3_3.9.2-2_all.deb
2023-02-16T01:13:07.1601125Z  processing python3-distutils_3.10.6-1~22.04_all.deb
2023-02-16T01:13:07.1684576Z  processing python3-lib2to3_3.10.6-1~22.04_all.deb
2023-02-16T01:13:07.1765817Z  processing python3-minimal_3.10.6-1~22.04_amd64.deb
2023-02-16T01:13:07.1827667Z  processing python3-pkg-resources_59.6.0-1.2ubuntu0.22.04.1_all.deb
2023-02-16T01:13:07.1896353Z  processing python3-setuptools_59.6.0-1.2ubuntu0.22.04.1_all.deb
2023-02-16T01:13:07.2011811Z  processing python3-wheel_0.37.1-2ubuntu0.22.04.1_all.deb
2023-02-16T01:13:07.2073315Z  processing python3.10-minimal_3.10.6-1~22.04.2_amd64.deb
2023-02-16T01:13:07.2326045Z  processing python3.10_3.10.6-1~22.04.2_amd64.deb
2023-02-16T01:13:07.2395971Z  processing python3_3.10.6-1~22.04_amd64.deb
2023-02-16T01:13:07.3671280Z  executing packages-templates/python_FIXUPHACK

At the very least, libpython3.10-minimal appears to be missing or broken.

dimkr wrote: ↑Mon Feb 20, 2023 7:01 pm

jrb wrote: ↑Mon Feb 20, 2023 5:46 pm

Perhaps I should build without python and blueman and then try installing blueman?

No, only make sure you have packages-upup/python/usr/lib/python3.10/encodings/__init__.py. If you don't, something about your build is broken.

2createpackages should say something like:

Code: Select all

2023-02-16T01:13:06.8306428Z Processing python
2023-02-16T01:13:06.8325900Z  processing libmpdec3_2.5.1-2build2_amd64.deb
2023-02-16T01:13:06.8385769Z  processing libpython3-stdlib_3.10.6-1~22.04_amd64.deb
2023-02-16T01:13:06.8443379Z  processing libpython3.10-minimal_3.10.6-1~22.04.2_amd64.deb
2023-02-16T01:13:06.9161522Z  processing libpython3.10-stdlib_3.10.6-1~22.04.2_amd64.deb
2023-02-16T01:13:06.9458887Z  processing libpython3.10_3.10.6-1~22.04.2_amd64.deb
2023-02-16T01:13:06.9756006Z  processing media-types_7.0.0_all.deb
2023-02-16T01:13:07.1543961Z  processing python-is-python3_3.9.2-2_all.deb
2023-02-16T01:13:07.1601125Z  processing python3-distutils_3.10.6-1~22.04_all.deb
2023-02-16T01:13:07.1684576Z  processing python3-lib2to3_3.10.6-1~22.04_all.deb
2023-02-16T01:13:07.1765817Z  processing python3-minimal_3.10.6-1~22.04_amd64.deb
2023-02-16T01:13:07.1827667Z  processing python3-pkg-resources_59.6.0-1.2ubuntu0.22.04.1_all.deb
2023-02-16T01:13:07.1896353Z  processing python3-setuptools_59.6.0-1.2ubuntu0.22.04.1_all.deb
2023-02-16T01:13:07.2011811Z  processing python3-wheel_0.37.1-2ubuntu0.22.04.1_all.deb
2023-02-16T01:13:07.2073315Z  processing python3.10-minimal_3.10.6-1~22.04.2_amd64.deb
2023-02-16T01:13:07.2326045Z  processing python3.10_3.10.6-1~22.04.2_amd64.deb
2023-02-16T01:13:07.2395971Z  processing python3_3.10.6-1~22.04_amd64.deb
2023-02-16T01:13:07.3671280Z  executing packages-templates/python_FIXUPHACK

At the very least, libpython3.10-minimal appears to be missing or broken.

When I rerun 2createpackages it produces exactly the same results as yours. packages-upup/python/usr/lib/python3.10/encodings/__init__.py is there, BUT the whole /usr/lib/python3.10/encodings/ directory seems to be missing from my build, will get back to you on this.

I think you should try https://github.com/puppylinux-woof-CE/w ... -on-GitHub and https://github.com/puppylinux-woof-CE/w ... ibutor-101. I worked really hard to make woof-CE capable of running directly on GitHub Actions, in a clean container that can successfully (and consistently) build dpup, S15Pup, VoidPup, jammy64 and others. This automation eliminates the differences between build environments that cause build failures and semi-working builds. Also, once you use git to save and track changes, the changes you make are documented and you can always go back or see what broke the build.

Thanks @dimkr that is very good directions!

Should these directions, and example use, be enclosed in some document for users in the General Information Catagory of this forum? Seemingly it will be seen more and used more if users, new/old, found it there. The information there carries with it a sense of trust and accuracy...I think.

No reply expected to this post. If its plausible, I am sure it will surface there or somewhere it can easily found, viewed, and seen by the largest community of users.

Clarity wrote: ↑Fri Feb 17, 2023 9:45 pm

jrb wrote: ↑Fri Feb 17, 2023 1:32 pm

... planning on releasing updates as .delta files. ...

A NEW ISO would be a better solution.

Thanks for your sharing your work.

I agree. Nowadays when most of us have good fibre-based Internet it is not much of a problem to download an iso. I really don't like the delta approach because it puts a barrier in the way prior to being able to use the system. I'm already overloaded trying to remember how to do things and never remember how to apply deltas (even if a simple utility is installed to handle it somewhere, new users won't go for that mechanism at all). Chances are you get less testers or at least many will simply download the provided iso, but not the delta (and thus erroneously miss the new stuff needing tested). In fact that's already happened as some posts above show, where the likes of myself finally just noticed the dotpet for adding missing GTK3-related icons but did not bother with the delta, which I didn't even know existed till re-reading the thread later.

I agree with Wiak. But I'll add, the best solution is the availability of big-fixes and updates using Quickpet. We have the technology. What's lacking is a repo Quickpet accesses. That same absence presents a problem to F-96.

Rockedge, do your websites have room? or would housing a repo being frequently accessed pose a different problem?

Which brings me to Donations. I'd gladly make them if I knew how.

Well, I figured out how. But it wasn't obvious. First I used the Forum's Search with the argument 'Donations'. It found lots of posts, but no instructions. Finally it occurred to me that maybe on the Forum's Front Page there might be a hint. There was.

A small word tucked away at the top. Board Index and Before Installing Puppy, README FIRST screamed for my attention.

rockedge, you should be justly proud of your accomplishments, not the least of which is maintaining a Forum too frequently disrupted by caterwauling. It's one thing to ask to be compensated for the time and effort you devote. It's another thing to have to bear the entire financial burden. Puppy Linux --in its broad sense-- is a Community Project. The financial burden of that project should rightly also be a Community Project.

In addition to making it more obvious how to donate, I recommend that from time-to-time [perhaps in the Announcement Section] we be advised what expenses necessary to maintain the Forum have been incurred but not yet covered by donations or will be incurred in the near future, together with a request for donations.

If additional expenses would be incurred to upgrade the Forum in order that it could serve as a repository, perhaps the Announcement Section could be used to advise us of the additional cost and obtain a consensus of active members whether it should be undertaken.

After I installed packages:

libpython3.10-minimal_3.10.4-3_amd64.deb,
libpython3.10-stdlib_3.10.4-3_amd64.deb,
python3-distutils_3.10.4-0ubuntu1_all.deb

downloaded from ubuntu repo, the python seems working now but the blueman-manager still get error

Maybe the problem is that USR_SYMLINKS=no rather than USR_SYMLINKS=yes. Many Ubuntu packages break when /bin, /sbin, etc' are not symlinks, because they expect something in /usr/lib while it's in /lib (the two directories have the same contents when one is a symlink to the other). Before the major distros switched to this new layout, they used to patch packages that expect the wrong paths, but now many of these patches are gone and if you force the old layout you're basically breaking a fundamental assumption of the distro developers.

@mastofa276 It looks like Blueman is broken.

This is what happens when I try to import the Blueman Python module with Python on dpup:

>>> import blueman
>>> blueman.__path__
['/usr/lib/python3/dist-packages/blueman']

If it's missing (/usr/lib/python3/dist-packages/blueman doesn't exist), it will say:

>>> import blueman
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'blueman'

dimkr wrote: ↑Tue Feb 21, 2023 6:47 am

Maybe the problem is that USR_SYMLINKS=no rather than USR_SYMLINKS=yes.

OK, so maybe I need to be dragged, kicking and screaming, into the future. Anybody got a good debian compatible huge-kernel I can download?

jrb wrote: ↑Tue Feb 21, 2023 6:00 pm

OK, so maybe I need to be dragged, kicking and screaming, into the future. Anybody got a good debian compatible huge-kernel I can download?

Yes, in https://github.com/puppylinux-woof-CE/w ... kernel.yml (5.10.x from Debian 11, 6.1.x from Debian 12, and whatever Debian Unstable has). These kernels are very very big, with wide hardware support, but they don't have aufs (only overlay). I use them in my dpup builds.

I know @dimkr has started incorporating some of the fixes we've come up with here into his Jammy64 WoofCE template. I think that's definitely the future of Puppy. I'm not quite ready to go there, remember "kicking and screaming"? So I'm going to start cataloging the problems and fixes in post 2 on page 1 and continue on with this project. I'll include all of them since then I won't have to remember which ones he's already dealt with.

Edit: After I finish plowing the driveway and shoveling the decks. Honest, we love snow here.