Quirky Xerus 8.6 (Aug. 16), Beaver 8.7.1 (Sept. 21), 2018

[Billtoo]

Can I ask which april64 version you took the b43 drivers from?

The latest version, April64-7.2

[rcrsn51]

If I may interject to avoid any confusion: Billtoo got a FIRMWARE file, not a DRIVER. The firmware files should be the same across all the versions.

[Belham]

Can I ask which april64 version you took the b43 drivers from?

The latest version, April64-7.2

Dang, didn't work for me, Billtoo From April64-7.2, copied over the b43 and b43 legacy folders & put them in the /lib/firmware of my Xerus 8.0, and nada, nothing. Xerus still is saying my laptop doesn't even have wireless hardware---which I know is crap since Tahr64, Slacko64 and Fatdog64 all bootup on this laptop & quickly load the broadcom b43 firmware (sorry, rscn51). Something is screwy in Quirky Xerus, especially since I booted up the April64-7.2 off a USB, and bang, immiedately my laptop had wireless and April64 shows it loaded the b43 firmware.

This is over my head in attempting to fix. Regarding puppies, I can copy directories, make small changes here and there, know my way around them and can play with remastering, vmlinuz, etc., etc. I even know how to do the simple stuff like completely disable and/or remove a firewall (which I did in Quirky, preventing it from loading any firewall on startup). Heck i even downloaded Quirky 8.0 Xerus 3 different times, to make sure I did have a corrupted download. So, anyhow, finding why the b43 wireless won't work in Quirky Xerus while it somehow works in April64-7.2 on this laptop (along with s many other puppy variations mentioned earlier), I am going to have to say goodbye to Xerus. I don't have the brains for the solution. I hate the thought now of leaving Xerus because it quickly became one of my, if not thee, favorite after I got it setup like I like with ffox, chrome, and other stuff

Thanks again, Billtoo, for responding so quickly.


Update: Success! It never occurred to me to just completely delete the firmware folder in Quirky 8.0 Xerus and replace it with the complete firmware folder from April64-7.2. I did this, and sure enough, Quirky 8.0 Xerus booted up, immediately loaded the b43 firmware, and told me I had both lan and wireless cpapability. Woohooo. It is now running off wireless smoothly. Thanks again Billtoo!! I'd never went down this road if you hadn't posted

[slackfan]

how to start it frugal using grub?

[slavvo67]

Belham:

I am trying to address your wireless issue via an RUXerus build by adding the b43 firmware to the next version. It will be posted in the I am creating it now so if you have an extra usb stick hanging around, I would appreciate it if you could do test on this.

I did not delete the entire firmware folder and recreate the April. I'm curious if the WoofQ will handle it properly.

Thanks,

Slavvo67

[Billtoo]

Belham:

I am trying to address your wireless issue via an RUXerus build by adding the b43 firmware to the next version. It will be posted in the I am creating it now so if you have an extra usb stick hanging around, I would appreciate it if you could do test on this.

I did not delete the entire firmware folder and recreate the April. I'm curious if the WoofQ will handle it properly.

Thanks,

Slavvo67

Barry posted this on his blog about firmware that was left out of
Quirky 8.0.
---------------------------------------------------------------------------------------
I have created a PET with lots of firmware for the 4.4.x Linux kernel (34.4MB):

http://distro.ibiblio.org/quirky/quirky ... 160423.pet

This will be in the next release.

Some Quirky 8.0 and earlier users reported needing Broadcom b43 and brcm network firmware -- this PET has what you need, I think.
---------------------------------------------------------------------------------------

[slavvo67]

Good reminder. If I recall, that pet didn't help me but still it's good to add it into my WoofQ for future releases. It will help someone....

Thanks,

Slavvo67

[charlie6]

First download of xerus-8.0

Burned the .iso to to a DVD... no problem, runs just fine.

Next installed a few personal programs...etc..
Rebooted the computer with the new remastered DVD and got this...

Failed to load ldlinux.c32
Boot failed:press a key to retry...

Hi,
one possible solution: once xerus runs from livecd
1. before erasing the DVD, copy ldlinux.c32 from iso to /boot/iso;
2. edit /usr/sbin/remasterpup2, line 448 as follow, and save:

Code: Select all

   for F in vmlinuz initrd.gz ${ZDRVSFS} grldr menu.lst '*.xpm' isolinux.bin isolinux.cfg '*.msg' '*.16' ldlinux.c32 '*.HTM*' '*.ICO' '*.INF'

Afterwards, click on the save ico, then REMASTER, step2, step3.

Have fun, Charlie

[BarryK]

We are getting trio's SVG Wallpaper Maker working in Quirky, see this thread:

http://murga-linux.com/puppy/viewtopic. ... 430#915430

Put in that new /usr/sbin/qwallpaper, then await trio updating of Wallmaker PET to use the new qwallpaper.

[Billtoo]

ETP's DLNA Quirky Xerus64 Pup V1 - released 2nd July 2016 seems to have
many drivers included.

I have it running from a 32gb flash drive on a computer that came with
Windows 10.

video-info-glx 1.5.3 Sun 31 Jul 2016 on Quirky Xerus64 8.0 Linux 4.4.7 x86_64
0.0 VGA compatible controller:
Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] (rev f0 )
oem: AMD ATOMBIOS
product: TONGA 01.00

X Server: Xorg Driver: amdgpu
X.Org version: 1.18.3
dimensions: 3840x1080 pixels (1013x285 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD TONGA (DRM 3.1.0, LLVM
3.8.0 )

OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.2.0

Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz
Core 0: @800 1: @800 2: @800 3: @800 MHz

Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter

Wireless,sound,and graphics card are all supported.

[ETP]

Hi Billtoo,

Barry's own additional firmware pet is one of the many extras in the DLNA Pup as keeping the size down was not a factor.
See:
http://www.barryk.org/news/?viewDetailed=00351

[Billtoo]

Hi Billtoo,

Barry's own additional firmware pet is one of the many extras in the DLNA Pup as keeping the size down was not a factor.
See:
http://www.barryk.org/news/?viewDetailed=00351

The built-in wireless of my emachines D620 laptop isn't seen when
network wizard is run, tried loading a couple of broadcom modules but
no luck there so using the wired network.

Network controller Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)20

Computer
Processor AMD Athlon(tm) Processor 2650e
Memory 1794MB (111MB used)
Machine Type Physical machine
Operating System Quirky Xerus64
User Name root (root)
Date/Time Sun Jul 31 17:17:47 2016
Display
Resolution 1280x800 pixels
OpenGL Renderer Gallium 0.4 on ATI RS690
X11 Vendor The X.Org Foundation
Audio Devices
Audio Adapter HDA-Intel - HDA ATI SB

That the OS works so well on a laptop with a single core processor and
2gb ram is amazing.

I have an usb adapter that is supported if the laptop ever travels
(unlikely),it uses the only free usb port though.

D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT2571W]

Edit: I have LxPupSc installed on the hard drive of the laptop so I
copied all the broadcom stuff in /lib/firmware to /lib/firmware of the
flash drive install of DLNA Quirky Xerus64 and rebooted.
Then ran the network wizard and my built-in broadcom wireless works
now.

[slavvo67]

Barry,

Woof2 seems to be pointing to the wrong repositories for Quirky Unicorn. Can you help me resolve this? I'm revisiting the 32bit idea.

Thank you,

Slavvo67

[stemsee]

@Billtoo

I think you meant BCM43142, source is available here
AMD64
http://packages.ubuntu.com/trusty-updat ... e/download
i386
http://packages.ubuntu.com/trusty-updat ... e/download

[BarryK]

Barry,

Woof2 seems to be pointing to the wrong repositories for Quirky Unicorn. Can you help me resolve this? I'm revisiting the 32bit idea.

Thank you,

Slavvo67

Do you mean the PETs?

http://distro.ibiblio.org/quirky/quirky ... s-unicorn/

The URLs for PETs might have changed from the woof2 days.

[BarryK]

Barry,

Woof2 seems to be pointing to the wrong repositories for Quirky Unicorn. Can you help me resolve this? I'm revisiting the 32bit idea.

Thank you,

Slavvo67

Do you mean the PETs?

http://distro.ibiblio.org/quirky/quirky ... s-unicorn/

The URLs for PETs might have changed from the woof2 days.

Oh, woof2, do you really mean that? It got retired a very long time ago.

For Quirky builds, I use woofQ, see latest that has been uploaded:

http://barryk.org/news/?viewDetailed=00345

[slavvo67]

Oops, sorry, WoofQ it is. It seems that some of the repositories are no longer there for the QU. I'll check again but it think it was the Ubuntu ones.

[slavvo67]

This directory is gone:

http://archive.ubuntu.com/ubuntu/dists/ ... ckages.bz2

Looks like the utopic directory is missing in action...

WoofQ gives me a failed to download and aborts right at the beginning of the 0setup script.

[BarryK]

This directory is gone:

http://archive.ubuntu.com/ubuntu/dists/ ... ckages.bz2

Looks like the utopic directory is missing in action...

WoofQ gives me a failed to download and aborts right at the beginning of the 0setup script.

Oh, yes, gone. That's unfortunate.

[rufwoof]

Tried installing using the 'alternative' choice. Running from DebDog64

First run, said I needed gdisk ... so apt-get install gdisk .... second run said I needed syslinux ... so apt-get syslinux .... third run said wrong type of syslinux, needed the efi or something like that, so install syslinux efi version using Synaptic. Ran again and ... still said wrong type of sylinux (version 6.x)

By that stage I had a /usr/lib/SYSLINUX folder (with a mbr file and others in it) and a /usr/lib/SYSLINUX-EFI folder with efi32 and efi64 folders in it, so I copied those two folders across to the SYSLINUX folder ... and reran the installation and it worked OK. Playing videos (and sound), straight to desktop and net connected ...etc OK. (USB booted, 2GB ram, nvidia graphics card).

Short story, if run from Debian then the 4install-quirky-to-drive-gpt script needs to check for SYSLINUX ... OR ... SYSLINUX-EFI folders for efi32 (efi64) sub-directories/files (would also have been nice to have checked for gdisk and syslinux versions before running through all of the other uncompressing ...etc stuff).