Partition resize was broken

No comments
At first bootup of Quirky on the Raspberry Pi, QuickSetup runs. This is a GUI to quickly make basic configuration choices.

One thing it does is check if there is unused space at the end of the drive. This will occur if the drive is bigger than the image-file written to it. Quirky is supplied as a compressed image file, that expands to a nominal 8GB -- but it is actually a bit smaller, so as to fit on any "8GB" SD-card.

So even on an 8GB card there is going to be a bit of unused space at the end. Much more so if you use a 16GB or 32GB SD-card.

QuickSetup checks if there is more than a few hundred MB empty space at the end of the drive, and if so, offers to resize the Quirky partition to fill the entire drive.

OK, this works on the Pi. However, I discovered yesterday that it does not work on a PC. The reason is, I supplied Quirky Xerus 8.1.5 x86_64 as a 8GB USB Flash stick image, with a GPT (Guid Partition Table).

The partition resizing fails with a GPT, due to the use of Busybox 'fdisk'. My "easyinit" ramdisk has Busybox in it, compiled statically. I have written about Easyinit in earlier posts.

However, the full 'fdisk' utility, in the 'util-linux' package, can handle the partition resizing in a drive with GPT.

I have compiled fdisk statically in Buildroot, so have added that to Easyinit.

This fix applies to Quirky Xerus and the soon-to-be-released SlaQ X86_64 Linux distributions.


Win10 locked me out

No comments
Windows 10 continues to be a less than optimal experience for me.

I haven't been able to upgrade since June 2016. I used to be able to upgrade, but no longer. When I click the button to check for upgrades, it just reports there was an error, and provides a code that I am to give to Customer Support.

My Asus E200HA came with Win10, I only purchased it this year. Haven't messed around with it much, just installed a few apps, and shrank the partition (using Microsoft's own partition management tool).

Annoying, yes. I do not want to phone Customer Support and wait in a queue.

Then, last night, Win10 wouldn't let me in, with this message:

This device has been locked for security reasons. Connect your device to a power source for at least two hours, and then restart it to try again

What, locked out of my own computer! What nerve MS has!!!

This problem is discussed here:
https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_security/this-device-has-been-locked-for-security-reasons/bc10bef4-d1cc-4b7a-8659-40187cf516ab



ROX-Filer frozen on E200HA

1 Comment
Ha ha, the saga continues with my Asus E200HA! Yesterday I posted about fixing the keyboard, again:
http://barryk.org/news/?viewDetailed=00489

I then created what I thought was going to be the release version of SlaQ, booted up on the E200HA, all seemed OK, but after a few minutes, ROX-Filer locked up. Everything else kept working. I noticed CPU usage climbing precariously, so shutdown.

Have used SlaQ on the E200HA a few times since then, Rox has been OK. Hmmm...

I am using an old version of ROX-Filer that was compiled in T2. I notice that Fatdog is using more recent source:
https://github.com/jun7/rox-filer/

...this is a fork of the original project, which is mostly dead.

OK, I will compile it in SlaQ, and hope it performs better.


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/


Pages: [1] [2] [3] [4] [5] [6] ...