(old)Puppy Linux Discussion Forum

So trying to boot frugal from various filesystems results in this error as vmlinuz tries to load initrd My hardware is a lenovo flex15 pro i7 laptop. 1TB HDD, 16GB ram

stemsee wrote:So trying to boot frugal from various filesystems results in this error as vmlinuz tries to load initrd

Code: Select all

 error:couldn't find suitable memory target

That's a grub2 error code. How did you install grub2? Or perhaps, what version of grub2 did you install it?
I suspect it has something to do with this: http://www.murga-linux.com/puppy/viewtopic.php?t=109891

My hardware is a lenovo flex15 pro i7 laptop. 1TB HDD, 16GB ram

That should be more than enough to run Fatdog.

Updated information about firmware in the second post: http://murga-linux.com/puppy/viewtopic. ... 929#977929. Especially, we have uploaded an SFS that contains all the firmware known to the mainline Linux kernel.

Hey guys, thanks for the new release! I just wanted to suggest adding the loading of the virtio kernel modules inside the init script. I got FatDog720 running on FreeBSD inside a Bhyve virtual machine booting with UEFI using the VirtioIO drivers for networking and storage. Initially I was able to save the save file/folder to a virtual disk such as /dev/vda2, but when I reboot it does not detect the virtual disk because the init script inside the initrd does not load the virtio kernel modules so it failed to find my savefile. I added loading the virtio modules to the init script and rebuilt the initrd and now everything works fine and I am able to use my save file/folder stored on a virtual disk.

uploaded an SFS that contains all the firmware known to the mainline Linux kernel

SiS900 NIC? No panic, it's gonna take me a century or two to fathom a FULL installation which is central to my continuing use of FD64. Doubting I have the skills however, despite masses of advice from jb...

I use a customised fatdog version of the rEFInd utility, which loads a grub.cfg and boots from there.
Worked with previous fatdog and everything else.

DD'ed the latest iso to a usb thumb drive. Booted from it to fatdog 'rEFInd', then same 'couldn't find suitable memory target' problem for every boot option except the last which nevertheless didn't get me to a desktop.

Tried various boot parameters to no avail!

Does it check ram size? Not expecting 16GBs ;-/ ??

Must be a bug in mergeinitrd.

More about inaction of NIC drivers.
Tested a load of distros for NIC connection with interesting results:
Slacko 5.6 can see and wired-connect to my SiS900 and my ancient RTL8139C NICs. So can almost all other (non-Puppy) distros - even majors like Mint & Fedora.
Surprisingly, though, both of those NICs appear to be detected in Slacko 6.9.9.9, Pyro 0.6, XSlacko 4.4, using SNS and FD64 720 using ControlPanel/Network/Scanner.
None of the later will connect/wired however.
Why? What has changed? I am not doing anything differently this last decade, although my severely limited knowledge prevents knowing how to get these NICs to connect. The older NIC has been working with just about every installation since I stripped it from a turn-of-the-century discard - and still does, even on the latest SOTA kit!

Sage,

Didn't you mention there was firmware missing for you wired NIC or am I thinking of someone else? If you know the file name for the firmware we can possibly add it. You can open a terminal and type dmesg. It will usually log an error about missing firmware.

You could also go to Control Panel -> Utilities -> (then scroll down) -> Bug Report Info Collector. Then attach the report for us to look at. You might have to change the extension of the file name to something the forum is happy with.

Many thanks, kirk. I might've said something like that but getting well out of my ambit! Did a bunch of tests recommended by jb. The whole thing is confusing. Thought I did a dmesg at one time and might've told jb? or not?
The conundrum is simple, though: a year ago or so, all the puppies worked on SiS900/RTL8139C - now they don't, although the HW seems to register them in the NICs setup procedures, maybe not elsewhere? Unfortunately for me, the problems seem to reside in the hinterlands between HW/FW&SW - too difficult for me. Plenty of other distros working, so I'll have to wait for one of you gurus to fathom it out with some dusty kit lost behind the sideboard...

Out of curiosity, I tried the 720 final live-cd on a gaming PC I was setting up over Christmas. I got the following error during initrd loading: H/W specs of gaming PC: Ryzen 1600, 16gb ddr4, gtx 1070.

I don't have access to this PC any more and do not expect a fix. Simply reporting my experience.

jake29 - your problem seems similar to stemsee.
New hardware, new firmware - most probably UEFI.
Something has changed, requiring grub2 update.

Sage - my apology I've been busy, so progress is slow.

Meanwhile, Happy New Year everyone. See you in 2018.

NIC issue resolved - advised to jb.

Replaced grubx64.efi (2013 > 2016) and grub2.efi and booted ok.
ha ha!

Having enabled BC-wl wlan0 is in wired pane on wpagui with no way to connect. Used Wifi-Scanner-2 (Ad) script only and voila! problem solved...

I would like to present some more perspective for those dismissive about the value of Vulkan Graphics Drivers. Some key features include: These points suggest how beneficial it is when used with ageing CPUs, in comparison to alternative GPU drivers.

A cutting-edge graphics card is not a requirement for Vulkan API support; many cards (AMD and Nvidia) that came onto the market at the beginning of 2012 are compatible. https://en.wikipedia.org/wiki/Vulkan_(A ... patibility

Also Media Players can benefit from utilizing Vulkan. MPV Player already has some degree of support implemented.

https://www.phoronix.com/scan.php?page=news_item&px=MPV-Vulkan-Next-Better

SneekyLinux review : https://youtu.be/PmmEimUovmo

Awesome! Couldn't wait for the new release <3 Will be putting it to the test briefly.

will be visible when you run gslapt and you can remove it from gslapt. Any other behaviour is a bug. If you find this, can you please report

One possible bug was that, while uninstalling seemed to work, the menu entry was not removed. Although this could be related to the following 'bug' (which I came here to report and saw 720 under the xmas tree \o/ )

There have been a few files giving input/output error (cant delete them, nor even stat them), one of them related to a package I tried to install. Now, even gslapt wont load (it complains it cannot find said package). This is 710, just to be clear. (sorry to post here, but the goal is to request a new feature, not fix this)

It could be hardware error but I suspect it was some interaction with the Fatdog merging process. Either way the problem is, rebooting with savefile=none and doing a fsck says the FS is clean, I was even tempted to try to umount it and manually recover a superblock backup, as per the next link. (which is pretty much the problem Im having) but it was already getting too dangerous for my skillset (running it on all those overlayed, cryptoed, ram mounts?! ) Now that 720 is out, I'll simply migrate instead

https://ubuntuforums.org/archive/index. ... 45536.html

okay, so this whole post was basically a request to add such capability to the savefile utility, AND to thank you all for the work put into this great distro! My favorite (pre-compiled ) distro. My2018 couldn't have began better!

Cheers.

stemsee wrote: Having enabled BC-wl wlan0 is in wired pane on wpagui with no way to connect. Used Wifi-Scanner-2 (Ad) script only and voila! problem solved...

Great that you can connect using your script! The wireless interface shouldn't show up in the "wired" pane to begin with, so let's dig deeper as to why it happens.

Could you please go back to that system and:
1) Confirm that wlan0 still shows up in the wrong pane (wired)
2) Do _not_ connect through Wifi-Scanner-2
3) Open terminal, run the following commands and post results. Thank you. In the screenshot you posted I can see that wlan0 did actually connect to a DHCP server that allocated an IP address for wlan0. Whether that makes any sense in your environment I can't tell. Was the screenshot taken _before_ or _after_ connecting through your script?

What's the "Ad" in "Wifi-Scanner-2 (Ad)" stand for?
What's "BC-wl" in your post?

Thank you.

Yes it still shows in wired selector.

The ip is there after connecting with my script.

BC-wl is the fatdog service to load the module.

I could not get the last two commands to work in xterm.

the first two returned the following. Ad - advertisement!

The wlan0 interface is now in the wifi pane! I think that when it is discovered in X it goes to wired pane, but during boot with a savefile it gets put into the wireless pane! For a while there was somewhere code flashing in the wpa_gui pane then it settled down and I was able to connect.

I found also that geany 1.31 has a bug which prevents executing in xterm the script which is being edited. I compiled and installed geany 1.32 from source and the problem has gone.