Quantcast
Channel: Puppy Linux Help & Forum » Forum: Beginners - Puppy Linux Questions and News - Recent Posts
Viewing all 3243 articles
Browse latest View live

david on "Latex (texlive) not working"

$
0
0

I installed Puppy version based on Ubuntu 18.04 (the actual image name, upupbb-18.05+28.iso)

Everything seems to work fine.

I installed texlive, and Texstudio.
If trying to compile a simple tex file, I get an error (even if I launch pdflatex from terminal):

Can't locate Pod/Usage.pm in @INC (you may need to install the Pod::Usage module) (@INC contains: /usr/share/texlive/tlpkg /usr/share/texlive/texmf-dist/scripts/texlive /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 /usr/lib/i386-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/i386-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/i386-linux-gnu/perl-base) at /usr/share/texlive/texmf-dist/scripts/texlive/mktexlsr.pl line 97. BEGIN failed--compilation aborted at /usr/share/texlive/texmf-dist/scripts/texlive/mktexlsr.pl line 97. Compilation failed in require at /usr/bin/mktexfmt line 23. BEGIN failed--compilation aborted at /usr/bin/mktexfmt line 25.

There're missing perl modules. None of the guides I've come across seem to work. Missing modules could be installed using CPAN. But CPAN is not installed, and it is not in the package manager. On other distros there's a perl-cpan package.

#perl -MCPAN -e shell
outputs:
Can't locate CPAN.pm in @INC (you may need to install the CPAN module)

Does anyone know how to install CPAN on Puppy?
Does anyone know how could I use latex on Puppy?

Thank you


aarf on "bionicpup64-8.0 CE released 2019-Mar-14 by 666philb"

$
0
0

booted
had to put the savesfs on sda2 when i want it in the boot folder on sda6. but sda6 isnt offered. this has been the case since the first bionic pup IIRC

aarf on "bionicpup64-8.0 CE released 2019-Mar-14 by 666philb"

$
0
0

SLIMJET
spotslim

ash: exec: line 4: exec: not found
Script completed hit RETURN to close window.

as before in bionicpup

aarf on "bionicpup64-8.0 CE released 2019-Mar-14 by 666philb"

$
0
0

removed the mangy dog from the desktop

aarf on "bionicpup64-8.0 CE released 2019-Mar-14 by 666philb"

aarf on "bionicpup64-8.0 CE released 2019-Mar-14 by 666philb"

aarf on "bionicpup64-8.0 CE released 2019-Mar-14 by 666philb"

$
0
0

pipepanic is in the ppm :)
so along with also there ace of penguins, and gtkball a large portion of my current life is catered for LOL

aarf on "bionicpup64-8.0 CE released 2019-Mar-14 by 666philb"

$
0
0

seem to be getting more freezes than before, often come while/after playing mentioned games for long periods

freezing of mouse clicks, mouse movement, keyboard, or combinations of these, often have to hardshutdown but not always. tray icon says still got 400MB+ of free space in save sfs

cant recall having these freezes in easyos but i dont use easyos as much as i use bionicpup


aarf on "bionicpup64-8.0 CE released 2019-Mar-14 by 666philb"

aarf on "bionicpup64-8.0 CE released 2019-Mar-14 by 666philb"

$
0
0

manually copied my games into easyos 1014 and made it my default boot due to freezing to often in bionicpup

mikewalsh on "Mozilla-based 'portables' inspired by fredx181's FF-Quantum portable...."

$
0
0

Hallo, all.

Just thought I'd post some links here for a series of Mozilla-based portables I've recently put together for Puppies.

Fredx181's Quantum-portable auto-updates, looks after itself, and can be run from /mnt/home, so as to keep it outside of 'Puppyspace'. Since the profile directory is integral to the browser directory, it's totally self-contained. These builds all work on the same principle.

They can also be run from a flash drive, so are truly portable. You can run them in any mainstream Linux distro as well, since there's nothing Puppy-specific about them.

Releases are as follows:-

a) FF60esr-portable:
32-bit - https://drive.google.com/file/d/1PefIFHY8jiQzO0wBV3RXHNQW23V6Jc26/view?usp=sharing
64-bit - https://drive.google.com/file/d/1H1vLGZQZNUKmJQZ-dQ0p_-QIsFz4sKsx/view?usp=sharing

b) Palemoon-portable:
32-bit - https://drive.google.com/file/d/1H1vLGZQZNUKmJQZ-dQ0p_-QIsFz4sKsx/view?usp=sharing
64-bit - https://drive.google.com/file/d/1H1vLGZQZNUKmJQZ-dQ0p_-QIsFz4sKsx/view?usp=sharing

c) A 'special' build, based on Puppy Forum member watchdog's special SSE-only build of Palemoon 27.9.4 with a self-contained glibc 2.19 'tweak' to allow running in older Pups:
32-bit only - https://drive.google.com/file/d/1H1vLGZQZNUKmJQZ-dQ0p_-QIsFz4sKsx/view?usp=sharing

d) SeaMonkey-2.46-portable:
32-bit only - https://drive.google.com/file/d/1H1vLGZQZNUKmJQZ-dQ0p_-QIsFz4sKsx/view?usp=sharing

--------------------------

In all cases, the procedure is the same. D/l the appropriate tarball, and extract it. Place the resulting directory (firefox32/64, palemoon32/64, or seamonkey32) in the location you want to run it from (/mnt/home, on a USB flash drive, wherever).

Start from the appropriate 'start-script':-

Firefox - 'ff'
Palemoon - 'plmn'
Seamonkey - 'smky'

First run will set-up your profile within the browser directory. Second & subsequent runs, so long as you always start with the script, will run the browser from the self-contained profile.

That's all there is to it!

Mike. ;)

Lobster on "New OS"

aarf on "arduino IDE in tahrpup64"

aarf on "ubuntu phone: Meizu PRO 5 Ubuntu Edition."

$
0
0

doubt you have missed this but anyway here it is ...

Google v Huawei hits millions of smartphone users

Tech May 20, 2019 20:56

By AFP

Hundreds of millions of smartphone users will be affected by Google's decision to sever its Android operating system ties with Chinese handset maker Huawei.

The decision, in the midst of a US trade war with China, means that Huawei users will start losing access to Google's proprietary services such as Gmail and Maps, and be shut out of future upgrades to Android on their phones.

The move by the California internet giant on the software front was compounded by news that US chipmakers have stopped supplying Huawei, hitting the hardware of its phones.

Many customers affected

Huawei sold nearly 203 million phones last year, up from 150 million in 2017, according to data tracking firm Gartner, overtaking Apple to threaten Samsung atop the global charts.

For the first quarter of 2019, before its recent run-in with President Donald Trump's administration, Huawei sold 59 million handhelds, IDC calculated.

Those users risk losing access to important upgrades to Android released by Google in future, although for now Huawei said it would continue to provide security updates.

The Chinese company will only be able to access software patches and distribute them from Android's open source project, not proprietary information retained by Google, meaning that apps on Huawei phones could become unusable.

No easy fix for Huawei

To get around the Google ban, Huawei would ultimately have to build its own operating system, as Apple has for its iPhones. That cannot be done in a hurry.

Microsoft offers a salutary example. Between 2010 and 2017, the US company tried to entice users to buy phones built on its own Windows mobile operating system. But the phones never took off and the company pulled the plug on the OS.

Huawei does have a big advantage over Microsoft, given the bigger scale of its mobile market penetration.

Software developers might feel compelled to offer a Huawei-specific version of their apps. Or the Chinese manufacturer could start a new branch of the Android family based on the open source version available now.

But that will all take time.

Risks for Google too

The widespread mobile usage of Maps, Gmail and Google's other services has helped the US company build a market-leading position with Android alongside its crushing dominance in desktop browsing.

But in cutting off Huawei, Google risks being deprived of the revenue-generating data of all those phone owners around the world.

And other Chinese smartphone makers, such as Xiaomi, Oppo and OnePlus, will be watching closely.

Should Huawei build its own system, it's conceivable that those companies might join it, in a bid to end their own vulnerability to future actions by the US government or companies.

from http://www.nationmultimedia.com/detail/breakingnews/30369719

tivo on "bionicpup32-8.0 install on Intel 815 graphics chipset?"

$
0
0

Puppy Precise gets this right and makes the display work well, but Precise packages don't work for me. Most install but won't run, or at least the ones I need. (LibreOffice and a reasonably up to date browser, Firefox or Chrome probably. Seamonkey isn't adequate for today's https protocols.)

It was suggested that I just try bionicpup32. The hardware in this case is perhaps barely enough but it seems it should work. Dell Optiplex GX115: Pentium III @ 1.2 GHz, 512 MB RAM, 33 MHz bus, Intel 815 graphics chipset, 40 GB HD space.

The bionicpup32 install or live CD run, even with the xorgwizard, fails to create a working xorg.conf. I tried copying the good one (which was apparently specific to i815) from Precise into Bionic, but it still gives a black screen. The Xorg.0.log says it could not find a working screen combination, even though the older Xorg found at least two, one for 1280x1024 and one for 1024x768. Monitor is Compaq 1725, which generally works with other Linux distributions without tweaking.

So far, though, I can't find a configuration to satisfy the X driver in bionicpup32. Any ideas?

Addendum: Tried the Xubuntu Bionic Beaver 32bit installation and that has the same symptoms. It appears to be using a graphical display mode to begin the install, because an atypical font is used etc., but when it starts X, black screen with blinking cursor at top left is always the result. I will try with a flat panel monitor instead of the CRT to see if that matters, but I don't expect that to correct the problem. I can escape the black screen with CTRL-ALT-BS but in that state, though I have command line access, there seems to be no editor (vi? nano? something else) to let me modify the xorg.conf to see if I can get it running. This is true for both Bionicpup and Xubuntu. Seems like an oversight to me, including a small editor is surely a good idea. Geany is nice but doesn't work on a text screen. :(


tivo on "bionicpup32-8.0 install on Intel 815 graphics chipset?"

$
0
0

Just tried Bodhi Linux 32 bit with similar results. Like Xubuntu 32bit, it launches X into a non-functional configuration that gives a black screen. At least Puppy lets you zap the X session and return to the console to try to figure things out. Bodhi and Xubuntu appear to have "Dontzap" set to disable CTRL-ALT-BS so you are helpless and have to reset the CPU to recover.

Puppy Precise apparently has a driver for the Intel 82815 chipset called "i810" and that makes the difference. Bionic lacks this driver, because when started on an xorg.conf that calls for it, an error message saying the driver can't be found will appear. A lot of older 32 bit systems used this Intel chipset and I find it disturbing that Linux developers seem to be unaware of that.

When I start Puppy Precise on this machine, a message line appears early on saying

"Intel 800/900 series VBIOS Hack version 0.5.3"

which is also very likely relevant. If I could get that patch into Xubuntu or BionicPup I'd be in good shape probably. No idea how that is done. I remember years ago Slackware installation had a point where you could specify patch files to be loaded. Nowadays, install scripts seem to leave the user out of the loop entirely.

tivo on "bionicpup32-8.0 install on Intel 815 graphics chipset?"

$
0
0

RESOLVED

The fix is simple, but implementing it is difficult. The default xorg.conf created by the installation has one fatal flaw. For "Card0" the driver is set to "vesa" and that line is commented out to allow the default (probably "vesa" anyway) to take effect. Unfortunately, for the older Intel Accelerated Graphics chipsets, the vesa driver doesn't work. In this machine, the chipset is 82815, and the driver must be set to "intel".

This entails removing the "#" comment marker at the beginning of that line, and changing "vesa" to "intel", then saving the file. When X fails on a blank screen, CTRL-ALT-BACKSPACE takes you to a shell prompt as root, where you could easily fix /etc/X11/xorg.conf with a text editor, but it seems that no text editor is available in the installation setup. Inclusion of a small editor such as nano would be an excellent idea.

What I had to do was use sftp (which is available) to send the xorg.conf file to another machine, where I edited it to make the correction. Then sftp again from the machine being installed copied it back to the live CD installation environment. Restart X with the "xwin" command and you can continue the install.

However, the install does not copy the repaired xorg.conf file to the new installation, but places the default invalid one there. When you restart from the installed system, the same problem with X reappears and you have to repeat the process once more: sftp to another location, edit file, sftp to copy it back. Then reboot or restart X and you are in business.

I now have a full install of Bionic Pup 32 on my Dell workstation that has an Intel 815 graphics chipset.

Ideally the installer should be fixed so that it recognizes these chipsets and sets the driver to "intel" but I also strongly suggest that a small/simple text editor such as nano be included in the installation environment to make such fixes easier to implement when the installer goes wrong.

--Altivo

aarf on "bionicpup32-8.0 install on Intel 815 graphics chipset?"

$
0
0

well done

philb the creator of bionicpup is/was often available at puppy chat from the desktop icons
usually goes by the name of mrfricks there but sometimes just by a bionicpup handle
ask for mrfricks and he should out himself. if you have any further issues, he will provide the best advice you are going to get.

tivo on "bionicpup32-8.0 install on Intel 815 graphics chipset?"

$
0
0

Thanks for the tip. Unfortunately my rural internet connection is not very effective for live chat or watching "instructional" videos, etc. It tends to drop out and return erratically and is often very s..l...o....w.

Next problem is getting a working web browser. The "Light" browser included in the install ought to work but it gets an "illegal instruction" message and exits. Both chromium and palemoon, if installed via get-browser, do the same. Firefox has a different game. It just refuses to run, after giving a snippy message about the CPU not being SSE2 compatible. Seamonkey seems to work, but as always, is incredibly slow.

aarf on "bionicpup32-8.0 install on Intel 815 graphics chipset?"

$
0
0

mostly i use TOR these days and for sites that dont like tor am using seamonkey in BKs Easy Pyro64

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4
Build identifier: 20180807020626

and
sometimes for some site opera

About Opera
Version information
Version
12.16
Build
1860
Platform
Linux
System
x86_64, 4.14.105

i use this opera as portable across all puppys
its old and fails with quite a few sites these days but it has feature i like which are not in other browsers or even current operas

tor is from an old install in an old easy64-0.4 that updates it self and is also portable across various puppys
the said seamonkey usually always renders things that fail in the other browsers mentioned but i find it a pain to use and only use it as last resort

Viewing all 3243 articles
Browse latest View live