Hyperion Entertainment Message Boards

Posted: **Tue May 17, 2022 1:21 pm**

I tried to set up a printer under Void (For example an HP/Samsung laser printer)

sudo xbps-install -S void-repo-nonfree cups-filters gutenprint system-config-printer cups-pk-helper hplip foomatic-db foomatic-db-nonfree brother-brlaser avahi nss-mdns cups

Code: Select all
```
sudo ln -s /etc/sv/cupsd /var/service
```

Code: Select all

sudo ln -s /etc/sv/avahi-daemon /var/service

Code: Select all
```
sudo sv status cupsd
```
Code: Select all
```
sudo sv status avahi-daemon
```
Code: Select all
```
Reboot
```
Menu System - Administration - Print Settings
Button "Unlock" (Password)
Button "Add"
Select Device - Devices - Network Printer - Samsung ML-2525W
Select Connection "LPD network printer via DNS-SD"
Choose driver "Generic" - "PCL 5e - Generic PCL 5e Printer - CUPS+Gutenprint v5.3.4 Simplified [en] (recommended)"

Device URI: dnssd://Samsung%20ML-2525W%20(SEC001599878270)._printer._tcp.local/

The official HP/Samsung laser printer driver is only for for ARM, i386, and for x86_64 available. But ... the generic PCL 5e printer supports my HP/Samsung laser printer.

Unfortunately it doesn't print (Filters failed). It works on MintPPC with the same settings.

Posted: **Thu Jul 07, 2022 9:02 pm**

Hi All,

I'm attempting to boot my X5000 in to void using a USB key.

I've been able to download the image (20220129), wrote it to a USB key, grow the partition and verify it:

$ sudo resize2fs /dev/sdf2
resize2fs 1.45.5 (07-Jan-2020)
Resizing the filesystem on /dev/sdf2 to 7753364 (4k) blocks.
The filesystem on /dev/sdf2 is now 7753364 (4k) blocks long.

$ sudo e2fsck -f /dev/sdf2
e2fsck 1.45.5 (07-Jan-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
void: 175735/1911168 files (0.2% non-contiguous), 1567045/7753364 blocks

When I boot that USB key using the steps provided I see this output on my main display:

The system stays at this point with periodic disk access indefinitely.

Posted: **Fri Jul 08, 2022 4:21 am**

tekmage wrote: Thu Jul 07, 2022 9:02 pm When I boot that USB key using the steps provided I see this output on my main display:

The system stays at this point with periodic disk access indefinitely.

Which graphics card do you use?

Posted: **Fri Jul 08, 2022 5:24 am**

The issue was my video card and it was a dual problem. My primary OS 4 card is an RX580, the secondary card is an HD7770. When I only run with the HD7770 in the slot (and use the DVI port, HDMI was not working) Linux is fine. When I connect both cards with the HD7770 in any other slot it does not work. Hat tip to skateman for pointing out that his system uses an x1 to x16 adapter that provides additional power to the card. I've ordered one of those and I'm confident it will work once it arrives.

Cheers!

Posted: **Fri Jul 08, 2022 6:10 am**

tekmage wrote: Fri Jul 08, 2022 5:24 am The issue was my video card and it was a dual problem. My primary OS 4 card is an RX580, the secondary card is an HD7770. When I only run with the HD7770 in the slot (and use the DVI port, HDMI was not working) Linux is fine. When I connect both cards with the HD7770 in any other slot it does not work. Hat tip to skateman for pointing out that his system uses an x1 to x16 adapter that provides additional power to the card. I've ordered one of those and I'm confident it will work once it arrives.

Cheers!

Interesting! Good luck!

Posted: **Sat Sep 17, 2022 9:07 am**

16.09.2022

Project status update for 2023
Last year I wrote about the plans for phasing out of big endian support in the project by the end of 2022. This is now being changed. Instead, I will cease maintenance of the project as a whole beginning January 2023.

That means if the project is to continue, somebody else will have to take over. They will need to provide their own build infrastructure as well as everything else, as the public repository hosting will be shutting down as well.

The main reason for dropping of the project is that I have been working on a new distro, Chimera Linux. The new project is fully supported on the POWER architecture (and others) and is currently in heavy development (but expected to stabilize during 2022). Users are encouraged to migrate to it once that happens.

I have been thinking about this a lot and came to the conclusion that there is no reason to keep up maintenance of both projects. Chimera is explicitly designed to address various shortcomings of Void while retaining most, if not all of Void’s good aspects. That means Chimera should make for a good successor of the project.

Additionally, big endian support may be coming back in Chimera, at very least for 64-bit POWER. The viability of 32-bit PowerPC support will be evaluated as well. However, this will only happen after the project has stabilized its tier 1 architectures (ppc64le, x86_64 and aarch64). We will be introducing RISC-V 64-bit support as well for those interested.

In the end, the only loss is support for the glibc C library, as Chimera is a musl-only distribution. However, since musl is first-class in the project, the overall level of polish should be a lot better than in Void, and for most users there should be no need for concern, especially on the POWER architecture where there are no proprietary NVIDIA drivers and other things that would be of concern. Containers, flatpak and other solutions should prove effective enough in addressing glibc application compatibility.

If you are interested, feel free to stop by in any of our main channels. There are links on the Chimera website. I will probably not update this page any more, but will keep it running for the foreseeable future (the repositories will shut down next year, however).

Posted: **Tue Jan 31, 2023 6:02 am**

Please note: Void PPC is EOL so we have to be careful with installing and updating of packages.

Posted: **Wed Feb 22, 2023 2:22 pm**

FYI

Wicknix wrote: Better hurry and install the packages you want. The void ppc repo could get taken offline any day now. Even the old ppc maintainer doesnt know the exact date as its not his server. Otherwise it really is a nice OS. Install octo-xbps for a gui package installer. Makes finding stuff much easier.

Posted: **Fri Mar 17, 2023 3:51 pm**

Hi All,

The latest Void disk image has a boot and a root partition. I was able to mount the root partition from the disk image and copy it to a new disk image with the following commands:

Code: Select all

tar zxvf void-live-powerpc-20220129.img.tar.gz

Code: Select all

ls -ltr

Output:

Code: Select all

-rw-r--r-- 1 christian christian 8036285952 29. Jan 2022  void-live-powerpc-20220129.img

Code: Select all

fdisk -lu void-live-powerpc-20220129.img

Output:

Code: Select all

Disk void-live-powerpc-20220129.img: 7,48 GiB, 8036285952 bytes, 15695871 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd0a60bb8

Device                          Boot  Start      End  Sectors  Size Id Type
void-live-powerpc-20220129.img1        2048   473087   471040  230M  6 FAT16
void-live-powerpc-20220129.img2      473088 15693823 15220736  7,3G 83 Linux

Calculate the offset from the start of the image to the partition start

Sector size * Start = (in the case) 512 * 473088 = 242221056

Code: Select all

bc
bc 1.07.1
Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006, 2008, 2012-2017 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'. 
512 * 473088
242221056
quit

Mount it on /dev/loop0 using the offset.

Code: Select all

sudo losetup -o 242221056 /dev/loop0 void-live-powerpc-20220129.img

Code: Select all

sudo fsck -fv /dev/loop0

Output:

Code: Select all

fsck from util-linux 2.38.1
e2fsck 1.46.6-rc1 (12-Sep-2022)
Pass 1: Checking inodes, blocks, and sizes
Inode 30261 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 30322 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 30660 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 30695 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 30739 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 30785 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 30874 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 30903 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 30907 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 30908 extent tree (at level 1) could be narrower.  Optimize<y>? yes

Inode 153472 extent tree (at level 1) could be shorter.  Optimize<y>? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

void: ***** FILE SYSTEM WAS MODIFIED *****

      175735 inodes used (36.94%, out of 475776)
         288 non-contiguous files (0.2%)
          27 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 163035/24/5
     1476045 blocks used (77.58%, out of 1902592)
           0 bad blocks
           1 large file

      134534 regular files
       13777 directories
           0 character device files
           0 block device files
           0 fifos
         690 links
       27415 symbolic links (12663 fast symbolic links)
           0 sockets
------------
      176416 files

Code: Select all

sudo mount /dev/loop0 /mnt

Code: Select all

ls /mnt

Output:

Code: Select all

bin  boot  dev  etc  home  lib  lib32  lost+found  media  mnt  opt  proc  root  run  sbin  sys  tmp  usr  var

Code: Select all

sudo umount /mnt

Code: Select all

sudo dd if=/dev/loop0 of=void-live-powerpc-20230317.img

Output:

Code: Select all

15222783+0 Datensätze ein
15222783+0 Datensätze aus
7794064896 Bytes (7,8 GB, 7,3 GiB) kopiert, 83,3552 s, 93,5 MB/s

Code: Select all

/sbin/fsck.ext4 void-live-powerpc-20230317.img

Output:

Code: Select all

e2fsck 1.46.6-rc1 (12-Sep-2022)
void: clean, 175735/475776 files, 1476045/1902592 blocks

I increased the Void root disk image:

Code: Select all

qemu-img resize void-live-powerpc-20230317.img +5G

Code: Select all

/sbin/fsck.ext4 -f void-live-powerpc-20230317.img

Output:

Code: Select all

e2fsck 1.46.6-rc1 (12-Sep-2022)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
void: 175735/475776 files (0.2% non-contiguous), 1476045/1902592 blocks

Code: Select all

resize2fs void-live-powerpc-20230317.img

Output:

Code: Select all

resize2fs 1.46.6-rc1 (12-Sep-2022)
Resizing the filesystem on void-live-powerpc-20230317.img to 3213567 (4k) blocks.
The filesystem on void-live-powerpc-20230317.img is now 3213567 (4k) blocks long.

We have copied the root partiton from the Void disk image to a new image and increased it.

Cheers,
Christian

Posted: **Sat Mar 18, 2023 8:12 am**

Hi All,

I was able to update Void in the root disk image yesterday. I think, this is the last Void disk image. Please change to Fienix in the future.

New:

Noboot disk image (image without boot partition)
Fbdev is pre-configured
Renamed the libglamoregl.so to libglamoregl.so.bak
Yaru themes
Arctic Fox 40.1
Pale Moon 31.2

Download: void-live-powerpc-20230317.img.tar.gz (md5sum: 9e663d6045ffc24e58b7adbd4b9c9629)

If you want to enable hardware acceleration manually, then edit the file /etc/X11/xorg.conf. Change the "driver" from fbdev to radeon.

Please test it.

Thanks,
Christian

Hyperion Entertainment Message Boards

Void Linux

Re: Void Linux

Re: Void Linux

Re: Void Linux

Re: Void Linux

Re: Void Linux

Re: Void Linux

Re: Void Linux

Re: Void Linux

Re: Void Linux

Re: Void Linux