Fatdog64-800 Alpha / Beta [20 Dec 2018] [CLOSED]

Message

rcrsn51 · #136 Post by **rcrsn51** » Sun 02 Dec 2018, 16:08

You need to boot into Fatdog, run the dmesg command and determine if the firmware file is missing.

Maybe ally will do this for you.

Gordie · #137 Post by **Gordie** » Sun 02 Dec 2018, 16:45

I remember this forum being not so friendly for image uploads. I have booted into Fatdog and took pictures of the screen. Now to type. EGAD!

Code: Select all

Direct firmware load for iwlwifi-6000-6.ucode failed with error -2
Direct firmware load for iwlwifi-6000-5.ucode failed with error -2
Direct firmware load for iwlwifi-6000-4.ucode failed with error -2

Hope this helps. Wiping sweat off brow

rcrsn51 · #138 Post by **rcrsn51** » Sun 02 Dec 2018, 16:50

Here is the firmware file. Unzip it and copy to /lib/firmware.

Reboot.

Gordie · #139 Post by **Gordie** » Sun 02 Dec 2018, 16:53

Thank you. Is there any hope it will be included with the release so my wifi will work OOTB?

rcrsn51 · #140 Post by **rcrsn51** » Sun 02 Dec 2018, 16:58

Gordie wrote:Thank you.

Are you confirming that wifi now works?

Is there any hope it will be included with the release so my wifi will work OOTB?

That will be for the Fatdog team to decide. The full set of Intel WiFi firmware is quite large.

Gordie · #141 Post by **Gordie** » Sun 02 Dec 2018, 17:25

No confirmation as of yet. What I need to do is install FD64 to a USB stick and make a savefile and then reboot. Later today I can do this otherwise I am locked into a reboot cycle with this problem and there is other stuff I need to do. Besides, if it don't work OOTB I just move on. There are lots of choices for Live Linux. My days of jumping through hoops are over. Heck, even Slackware and most other Puppies work for me with no problems

Billtoo · #142 Post by **Billtoo** » Sun 02 Dec 2018, 18:31

I movded the SSD again to my HP desktop:

Computer
Processor 2x Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz
Memory 4042MB (469MB used)
Machine Type Physical machine
Operating System Fatdog64 [800]
User Name root (root)
Date/Time Sun Dec 2 13:20:30 2018
Display
Resolution 1920x1080 pixels
OpenGL Renderer AMD OLAND (DRM 2.50.0, 4.19.1, LLVM 5.0.2)
X11 Vendor The X.Org Foundation
Audio Devices
Audio Adapter HDA-Intel - HDA Intel
Audio Adapter HDA-Intel - HDA ATI HDMI
SCSI Disks
ATA Hitachi HDT72504
HL-DT-ST DVD-RW GSA-H60L
Generic- Compact Flash
Generic- SM/xD-Picture
Generic- SD/MMC
Generic- MS/MS-Pro
Monster Overdrive 3.0 Version
Kernel Linux 4.19.1 (x86_64)
Version #1 SMP Wed Nov 7 18:52:51 EST 2018
C Library Unknown
Distribution Fatdog64 [800]

It's working well on this older HP (2007)
Thanks.

kirk · #143 Post by **kirk** » Sun 02 Dec 2018, 23:55

Thank you. Is there any hope it will be included with the release so my wifi will work OOTB?

Yes it will. Thanks guys for finding that. I have a script that runs modinfo on all the modules and then copies the ones listed from a copy of Linux-firmware git. But many modules don't report what firmware they need and then there's some that aren't in Linux-firmware git. So I have lists that the script reads of firmware to copy even if it's not listed by modinfo. In this case modinfo listed the firmware as iwlwifi-6000-6.ucode, but Linux-firmware had iwlwifi-6000-4.ucode, so it wasn't copied. Every time you update the kernel to a new major revision, a lot of the firmware that various modules require changes, and there's no good way we've found of knowing what firmware we need and what we don't. Maybe that's why firmware isn't included with the kernel source at all anymore. So thanks again guys.

It's working well on this older HP (2007)
Thanks.

Thanks for testing it out!

rufwoof · #144 Post by **rufwoof** » Mon 03 Dec 2018, 00:57

Purely for interest, when I (re)install OpenBSD I do so using a 10MB boot file (bsd.rd i.e. ramdisk), that presents a cli set of questions that mostly involve just pressing Enter and that net connects and downloads the .tgz files for extraction/installation. Typically on my system it then boots to cli, detects missing firmware and downloads and installs that, then you have to reboot again before finally getting the X gui login.

An incentive to use a hard wired eth0 type system to do the initial install, and then with one system up/running using that to download sets for installing to other 'local' wireless only system(s) via usb or whatever.

No idea as to how it detects what firmware is required. In my case its the Radeon firmware (there is a fw_update option cli option that you can alternatively use to scan for/install firmware).

Using internet based installation like that takes less than 5 minutes on my link (that's preparing the full HD, partitioning (slicing), formatting downloading..etc.). By default base OpenBSD includes web server, X (xenodm), a range of windows managers etc.

Gordie · #145 Post by **Gordie** » Mon 03 Dec 2018, 01:46

JOY!
Set up my network and got on the NET. That file did the trick.
Thanks for the help

jamesbond · #146 Post by **jamesbond** » Tue 04 Dec 2018, 02:53

proebler wrote:Has anyone used the 'Fatdog64 Remaster Live CD' provided in the Utilities of the Control Panel ?
I have done two re-masters and on both occasions it produced an .iso without vmlinuz !
The remastered initrd was produced correctly, so that I could use it in my frugal install.

I cannot reproduce the problem. Make sure you have enough space in the target directory where you will be saving the output. And make sure you choose vmlinuz when asked. Check also the "info" page just before the remaster is created - confirm that the kernel points to the correct vmlinuz path.

I have used the 32bit libraries sfs of/in previous FD versions so that I could run XnView under Wine. Meaning to do the same in FD-800, I discovered that the 32bit libraries sfs appears to have ballooned from 87MB to 212MB [!].

Yeah that is because we accidentally put 32-bit python2, python3, llvm, perl and qt4 libraries. I have removed them and the size is now down to a more comfortable 122MB (still bigger than 87MB - but that's the price of progress ...).

Will there again be a FD-800 package list and builder?

Yes, once we get past alpha stage.

jamesbond · #147 Post by **jamesbond** » Tue 04 Dec 2018, 03:01

rufwoof wrote:In seamonkey however (fatdogs default browser), no matter what settings I set in advanced/proxy ... it just doesn't work !!!

I need to test this. I never used a SOCKS proxy.
The normal http/https proxy, however, works well. I use an add-on called MM3-ProxySwitch to manage proxy settings; and locally I'm running privoxy. Seamonkey points to this local proxy almost at all times.

EDIT: I tested with your method (ssh -D) and it worked. As you said, if I exit ssh, the browser would not work when the proxy was active, and it didn't.

EDIT: Grrr I accidentally deleted my mozilla profile directory; losing all my bookmarks etc when I tested the SOCKS proxy above. Nevermind. The problem is now I've lost the MM3-ProxySwitch and the new versions seems to only work with FF60 onwards nd no longer works with seamonkey

EDIT: Got it back thanks to sourceforge: https://sourceforge.net/projects/mm3-proxyswitch/.

chiefengineer · #148 Post by **chiefengineer** » Tue 04 Dec 2018, 04:38

I use German end-to-end encrypted email and it simply fails
in both the agent-switched Seamonkey and 52.9 Firefox. I'd like
to blame it on them but it still works in 720 and every other distro
I use in Firefox, etc. Wonder if there's some waiting-to-be-completed security stack? I noticed Opera failed to install because it depends on "apt-transport-https" which doesn't exist, or I would have tested that too.

jamesbond · #149 Post by **jamesbond** » Tue 04 Dec 2018, 05:26

chiefengineer wrote:I use German end-to-end encrypted email and it simply fails
in both the agent-switched Seamonkey and 52.9 Firefox. I'd like
to blame it on them but it still works in 720 and every other distro
I use in Firefox, etc. Wonder if there's some waiting-to-be-completed security stack? I noticed Opera failed to install because it depends on "apt-transport-https" which doesn't exist, or I would have tested that too.

Please elaborate.

chiefengineer · #150 Post by **chiefengineer** » Tue 04 Dec 2018, 15:46

which is one of two secure emails I use, the other being Protonmail (which works).
Their interface allows me to sign in, but does nothing but throw errors and fails
to be "active" (clickable) for anything, like opening a folder or message. This happens in FF 52 exactly the same. It is NOT a FF or Seamonkey issue because it behaves nicely in FF 52 under Kali Linux. These mails use a lot of cryptic notifications I am not getting...instead it is a pop-up asking "what went wrong" which also fails to populate when typed into.

My kid uses the latest Seamonkey under 721 (2.41?) without any user agent changer and the same mail works fine ... it seems it's not the agent string. I also changed the agent-string in Seamonkey to FF 55 and no change.

There are so many possibilities here that this is no biggy for me (I can wait for a finished Fatdog) but I thought it might point to some lack of support library in the https realm of things, since dpkg told me why Opera wouldn't install.

kirk · #151 Post by **kirk** » Tue 04 Dec 2018, 17:37

chiefengineer,

Could you try installing libicu-full using Gslapt and see if it solves your Seamonkey/Firefox problem?

Also, can you post a link to the email site?

Thanks

chiefengineer · #152 Post by **chiefengineer** » Tue 04 Dec 2018, 18:05

OK.
https://tutanota.com/
But I often get to it through tutanota.de

The email gurus there seem to think this is something
tied to "locale" , which is set to US everything. On the other hand,
it runs flawlessly under a TOR script which changes nodes randomly
all over the globe during the session, and Firefox 52.0.

There's just something different in this Fatdog so I'll report back.

kirk · #153 Post by **kirk** » Tue 04 Dec 2018, 19:35

We don't include all the locals. If you need them, you'll want to install the nls sfs file. http://distro.ibiblio.org/fatdog/pre-re ... s_800a.sfs

chiefengineer · #154 Post by **chiefengineer** » Tue 04 Dec 2018, 22:04

Kirk,
Thanks, the sfs fixed things simply by loading it
with nothing else invloved!

kirk · #155 Post by **kirk** » Wed 05 Dec 2018, 02:37

Glad that worked for you. Installing libicu-full may have fixed it as well. The nls sfs contains libicu-full, and if you're using a non-english local you'll want the nls installed anyway. I did make an account at https://tutanota.com/ and sent a test email. That seemed to work with the default local.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fatdog64-800 Alpha / Beta [20 Dec 2018] [CLOSED]

Fatdog64-800 Alpha [16 Nov 2018]

Re: http ssh proxy

At the risk of seeming like I'm lost

Re: At the risk of seeming like I'm lost

OK

OK

Thanks