Relaxation...


Clean...


Weather...


I know, lots of Cinnamon!  Makes VSIDO incredibly beautiful...

Both VSIDO FSA's were updated to the new 6.12.29-amd64 kernel

You can download the btrfs and ext4 fsarchives at the VSIDO download site here

There is also a How To on how to effectively use fsarchiver to get VSIDO installed

There is a current a package list that shows everything that is installed in VSIDO. Please review this file and let me know of anything needed, removed or added

But the music still has a firm grip...

An anonymous friend of mine bought a $360 US dollars 'Vsee Box' that gets like 30,000 channels in perpetuity. He was some pissed off when I showed him VSIDO Linux could also play around the same amount!!! (Give or take a thousand, I'm not counting them all) The channels are from all over the world.



He brought this new device he bought over to my house and I noticed when it powered on it had a splash screen that said 'Android TV'.  I knew right then he'd wasted his money and could've done the same thing with VSIDO.  Once I started reading and researching, sure enough, I've been able to view multiple channels at once like being in a sports bar.  PPV, VOD, Tele Series, old and new movies, you name it, it's there!

QuoteThe FAT TYPE partition is required and has been since the get go. Though the size requirements continue to grow.  I go with 500Mb.  You also have to flag it EFS and check the bootable flags as well...

That is correct; I always use cfdisk now to partition the disk prior to any install. There is an option in the "Type" to make the partition. Then you need to remember to format it FAT32.

Also, different distros require that partition to be mounted to a specific point. On some systems it's /boot/efi, on others it's /efi.

QuoteYour BIOS not allowing a Legacy boot environment is kind of surprising to me.  Should be a spot to disable Secure UEFI, then enable CSM Boot.

Manufacturers started getting away from that a few yeas back; uEFI only now.

QuoteBoot Order: Ensure the Debian entry is not the only EFI boot option available. There might be a way to manually add or prioritize boot entries.

That is usually possible. There is typically an "add boot entry" option in the BIOS/uEFI settings that allow you add an entry - click on the drive that has the file, then scroll like a file manager to select the file. Once the entry is added, you can usually use the UP/Down arrows to prioritize the boot order.

Quote from: jedi on May 08, 2025, 10:11:27 PM

Quote from: VastOne on May 08, 2025, 02:08:50 AMI downloaded the latest Debian ISO and it finally not only worked but also installed properly ONLY after I created a fat EFI partition.
 

You got it.  Debian has a signed EFI key somehow and Arch also will do an EFI boot and install,  Last I heard or read (i.e. more than a couple of years have passed) reFind used Debians signed key.

The FAT TYPE partition is required and has been since the get go. Though the size requirements continue to grow.  I go with 500Mb.  You also have to flag it EFS and check the bootable flags as well...

Your BIOS not allowing a Legacy boot environment is kind of surprising to me.  Should be a spot to disable Secure UEFI, then enable CSM Boot.  (i.e. Legacy boot mode)  After doing this you should also be able to boot to any USB/CD ISO you choose.

I'd for sure delete the signed MS EFI key if your able.  Totally personal choice I suppose but I consider it beneficial to all future installs on that laptop as long as MS isn't in your vocabulary!

That's it, all I know and remember without some actual digging.  From all the digging and research back then, I learned it was futile of me!!!  Don't end up in a rabbit hole VastOne!

Good stuff Jedi.. I did work on this pretty much all day today and have discovered the issues in some areas but no solutions in other.

I had earlier mentioned that Debian created the EFS/EFI fat32 directory and I was able to install VSIDO's efi grub to that same directory but because both were seen as Debian, only the first in order of install was showing up in the Bios uEFI boot section as an option.

I archived that directory and began playing around with it's structure and by using rEFInd to see what was happening, I was finally able to get rid of the Debian install, the Debian grub and everything else that should not have been there. I now have a rEFInd menu AND a VSIDO (Debian) in my EFI settings in my BIOS and I can boot to both.

rEFInd is a great tool, I just wish there was a better real time tool that could do the same things.

Marking this as solved only in that I am now more educated on EFI and that I do have a toy to play with in future needs

Thanks Jedi for the assist!

Simple indulgences and pleasures ...

back...

Ok so my issue with no wireless was pretty bizarre! I'll show you the list of pkg's I installed via dpkg in order to get network access.  Of course as with all VSIDO installs, the system is awesome!  VastOne has obviously built a very tight ship with VSIDO as we're all still here after well over a decade!  Thanks much VastOne, I'm still taking advantage even when you're not looking!  Believe it or not there's been nothing else on my pc's and laptop's since 2012 if memory serves, perhaps a little earlier than that!

Oh yeah, that stuff I installed in order to get connected!  brb with that...



Perhaps not all of the above was needed, but I couldn't get Network Manager to work from the fluxbox menu or the cli and Ceni wasn't picking up any hardware for wireless or ethernet.  That was a first for me btw.  When trying to run the Network Manager from the cli, or nmtui I would get a not installed or configured message that I've forgotten of course!  The last of the message however, was not forgotten or lost;

dpkg: dependency problems prevent configuration of network-manager:
 network-manager depends on libbluetooth3 (>= 4.91); however:
  Package libbluetooth3 is not installed.
 network-manager depends on libndp0 (>= 1.2); however:
  Package libndp0 is not installed.
 network-manager depends on libnm0 (= 1.52.0-6); however:
  Package libnm0 is not installed.
 network-manager depends on libteamdctl0 (>= 1.9); however:
  Package libteamdctl0 is not installed.


I figure you're build sys is not a lappy!!!  Up until now that is!  Congrats on the 'new' hardware.  My last couple of good laptops came from a buddy in the tech industry!  Cheers...