E200HA keyboard dead again

1 Comment
Sigh...

I thought that SlaQ is ready for release, but have learnt a little bit of prudence and patience is essential, so thought had better test it on other computers than my main work laptop.

So, plugged the SlaQ USB stick into my Asus E200HA baby laptop, and... no sound, no keyboard.

The no-sound I know about, and there is a fix on the horizon, as I posted about recently:
http://barryk.org/news/?viewDetailed=00481

But the keyboard. That was dead way back, early 2016, and I posted a fix:
http://barryk.org/news/?viewDetailed=00319

...the problem is, I did not identify just what kernel config option did the trick. Furthermore, I have used that config file as the template for compiling later kernels, so why now does the 4.8.15 kernel fail me?

Today I will have to carefully compare kernel config files! And probably have another go compiling 4.8.15. One does hope that the kernel developers haven't changed something that has rendered my E200HA keyboard inoperative.


a2dp-alsa for Bluetooth audio

No comments
Puppy Forum member 'fr33land' has undertaken a great new initiative, Bluetooth support in Puppy Linux:
http://www.murga-linux.com/puppy/viewtopic.php?t=109145

There have been other efforts, my own, named BluePup, found in the latest releases of Quirky x86_64 and Raspberry Pi, and Forum member 'rcrsn51' created peasyBT.

jamesbond has done excellent work with Bluetooth, and has created a utility, 'a2dp-alsa', that fr33land is using. It is described here:
http://www.lightofdawn.org/blog/?viewDetailed=00032

I obtained the source of a2dp-alsa from here:
http://www.lightofdawn.org/wiki/wiki.cgi/-wiki/files/a2dp-alsa-2016-01-02.tar.bz2

However, I then discovered that a2dp-alsa only works with bluez version 4.x. Right now, I am running SlaQ, a Quirky built from Slackware 14.2 binary packages, and bluez is version 5.4.

Phillip Berndt to the rescue. He has posted a patch for a2dp-alsa to support bluez5:
https://gist.github.com/phillipberndt/fcb01bad5cd18b4ebb2f

I have compiled it and created a PET, but not yet tested. I have uploaded the source and patch here:
http://distro.ibiblio.org/quirky/quirky6/sources/alphabetical/a/


Xkb Configuration Manager fixed

No comments
The Advanced Xorg Keyboard Configuration Manager is an old script, written by Puppy Forum member Dougal, around 2009 I think.

Since then, Puppy Forum member rodin internationalised it, and I made some small modifications. The last release was version 1.2, about 2013:
http://distro.ibiblio.org/quirky/quirky6/noarch/packages/pet_packages-noarch/xkbconfigmanager-1.2.pet

The problem is, it is designed for the keyboard information to be in /etc/X11/xorg.conf, however, these days we are moving to configuration files in folder /etc/X11/xorg.conf.d

Quirky 8.1.4+ has the keyboard settings in file /etc/X11/xorg.conf.d/10-evdev-puppy.conf.

I have modified Xkb Configuration Manager to work with the old xorg.conf and the new 10-evdev-puppy.conf. I decided not to "burn my bridges", just in case I every want to go back to the old way of doing things.

I decided that Xkb Configuration Manager should be built-in to woofQ, not a separate PET.

If anyone wants to see the new code, it is in /usr/local/apps/XkbConfigurationManager, and can be seen in the next release of Quirky.


Keep on finding bugs

1 Comment
Bugs keep getting unearthed, even in code that has been working OK for years.

Desktop icons
First though, a mention of icon sets. Yesterday I installed the Oranchelo and Sarai icon set PETs. After selecting them, I discovered that there were no icons in the JWM menu.
This is because the developer renamed SVG icons with .png extensions.
I have sent a PM to the developer, with advise how to fix this. He will have to fix and re-upload those PETs.

Package installing
/usr/local/petget is where all the scripts are for the PPM (Package Manager).
Yesterday, I installed a PET that has /lib and /lib64 folders in it, where /lib64 is a symlink to /lib
Yikes, in my SlaQ Quirky, which has /lib64 NOT a symlink, it got wiped out and a symlink /lib64 to /lib created.

This is obviously dangerous behaviour! Yet the code has been there for years. In my woofQ, until yesterday anyway, and yep, still in woof-CE:
https://github.com/puppylinux-woof-CE/woof-CE/blob/testing/woof-code/rootfs-skeleton/usr/local/petget/installpkg.sh

...look at line 343 onwards, that is where the naughty code is. I don't know what my thinking was at the time. Anyway, i have deleted the entire if - else -fi, from lines 344 to 367.

The woof-CE and woofQ 'petget' scripts have changed a lot since forking from Woof2, my woofQ scripts are going in their own direction. However, they both have that section of offending code.


SlaQ Linux x86_64 progress

No comments
I posted about a new project, SlaQ Linux:
http://barryk.org/news/?viewDetailed=00483

Well, I have scratched the itch. Wanted to do a build in woofQ based on Slackware packages. The problem is, a new build like this, lots of bugs get discovered, and it goes on, day after day, finding and fixing things.

One bug I have not fixed: Notecase personal information manager 0.9.8, the last open source version, cannot load images from the gtk theme. Looks like the source will have to be patched. Curious, as no other app has this problem. Also, Notecase works fine in Quirky Xerus64.

A small list of things still to fix.

What I am trying to do is create a distribution that is only about 200MB download. This was one reason why I chose Slackware, thought that there will be less dependencies.

Will I release it? Maybe. If it looks pretty solid in the next couple of days, I can upload it, for anyone who is interested.



Pages: ... [4] [5] [6] [7] [8] [9] ...