Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - thriftee

Pages: [1] 2
1
Tips and Tricks / mem - memory used utility
« on: December 21, 2014, 12:41:05 AM »
You will need to save these as executable somewhere in your path, and run with sudo or as root.  Its a utility I have found used by people at a lot of distros.  I didn't write them.  mem is a batch script that runs the ps_mem.py python script.

sudo mem

2
wattOS R9 / Re: R9 Information
« on: December 20, 2014, 05:03:51 PM »
to me...

LXDE is desirable much more than Mate.

microWatt should be a minimalized version of the full LXDE, without the LXDE desktop, and a super-light footprint desktop, like jwm, fluxbox, icewm or openbox/tint2, using light browser


3
wattOS R8 / Re: NVIDIA Legacy Driver Installation Problems :(
« on: December 15, 2014, 04:56:00 AM »
Live is not the same as installed

I'm only talking about this graphics card, only with 3.2.0-4 kernel, only with nvidia proprietary drivers

If everything is working fine, YOU ARE DONE, LOL

I doubt the newer antix can or will work with the proprietary driver because I doubt it can run the old kernel or old xorg server.   I would get the NEWEST antiX 14.3 to try it with, not the 2nd one.  If it can boot, my guess is the video will work out of the box with no xorg.conf at all.  My old Dell 8100 can't boot it, but my others do well with it.  Debian Jessie works on mine, but its very big and slow on the old machine, so you need a tuned version of it, like WattOS 9 will hopefully be, or Crunchbang 12 or antiX 14.x, but none of them are final yet, so keep that in mind if timing as well as stability is critical.

4
wattOS R8 / Re: NVIDIA Legacy Driver Installation Problems :(
« on: December 15, 2014, 01:41:10 AM »
Sorry, that solution has always worked for my nvidia cards. 

Do you have anything odd in your boot lines?

Can you try doing the whole sequence with a different monitor attached?

Those are the only things left that I can think of if 3.2.0-4 kernel, nvidia drivers, and nvidia-xconfig don't solve it. 

If you have space on the drive, crunchbang 11 or antix 13.2 and debian wheezy all have worked for me doing it that way.  Antix is a quick install.

5
wattOS R8 / Re: NVIDIA Legacy Driver Installation Problems :(
« on: December 14, 2014, 11:58:34 PM »
Hmmmm, with the nvidia driver I would say

backup your xorg.conf, and move it out of the way

install nvidia-xconfig

run "init 1"

then sign on as root, and

run "nvidia-xconfig".  it will generate a new xorg.conf. 

then do a reboot, and boot normally into x and see if it works

6
wattOS R8 / Re: NVIDIA Legacy Driver Installation Problems :(
« on: December 09, 2014, 03:22:50 AM »
Sounds like you should be volunteering to help with translations!

I hate that xorg.conf file.  Its always been trouble!  Like on my machine with 3 two headed nVidia vga cards and 6 lcd screens, Oh my!  It took forever to get that to work...

Well, I hope that one works for you.  And you probably would have thought initially that this was going to be EASY!

PS: I have had lots of "illegal instruction" crashes with both qupzilla and midori on my old laptop, seamonkey seems to run fine, though.

7
wattOS R8 / Re: NVIDIA Legacy Driver Installation Problems :(
« on: December 09, 2014, 12:55:36 AM »
  antiX has this program called sgfxi that automates the download and install of the video driver, but i don't know if that would work or is available for Debian Wheezy or WattOS R8. 

Yes Triftee, sgfxi is not specific to antiX, it works with many distros. I've used it a few times and it's interesting. I doubt whether it would help Cuscotravelservice with his specific problem, though.

I think there is another script called smxi which is capable of changing the kernel as well as video driver,  but again, I don't know if it works on WattOS.  It does work on antiX I know because I've used it.   I don't see WattOS listed on the about page.

http://smxi.org/site/about.htm

*IF* he could get to a 3.2.0 kernel, he might be able to use the file and instructions from nVidia's site.  I'm not going to pretend I know if that's possible or not.



8
wattOS R9 / Re: R9 Information
« on: December 05, 2014, 09:50:57 PM »
Thanks for filling us in on where things are going...

I would be most interested in an LXDE / Openbox version, and since most of my systems have 4 gb of memory or less, and some are 32 bit machines, I would hope to see a 32 bit PAE version.

I also would like to see a self regenerating menu that adds new programs added to the menu structure and a "Run" command from the menu.

I wouldn't be upset if there was no automatic upgrade from R8 to R9, and suspect it might be a lot of effort to get it to work.

Your R8 is very quick, and I think you should put that effort into trying to stay with that tradition as much as you can because that's the BIG thing that distinguishes your distro from the others.

Thanks again for your efforts...

9
wattOS R8 / Re: NVIDIA Legacy Driver Installation Problems :(
« on: December 05, 2014, 09:03:59 PM »
I have a similar video card in my Dell Inspiron 8100 that uses the same drivers and has the same problems.  In order to run the nVidia proprietary drivers, I needed to be running the 3.2.0 kernel, and once he gets that running, he can install the nvidia stuff downloaded from nVidia.  I don't know if that can work with WattOS R8 or not, but I think that might be where I ran into trouble.  It will work with Debian Wheezy or antiX13.2 I do know.  antiX has this program called sgfxi that automates the download and install of the video driver, but i don't know if that would work or is available for Debian Wheezy or WattOS R8.  Yes, my guess is that will no longer be a problem with R9 because I would think it would be based on Jessie, and that does work as is, but Jessie is too slow, I think, for older, slower machines that are strapped for memory.

10
wattOS R8 / Re: My touchpad mouse is jittery in R8
« on: June 13, 2014, 12:15:01 PM »
The R8 LXDE version is not haveing the problem, so I'll mark this solved.

11
Followup - I installed the wattOS R8 LXDE (amd64 by mistake), and haven't had any of the broken packages problems

Thanks

12
Thriftee if you are new to Linux I would suggest trying the LXDE version of wattOS R8 unless you have a compelling reason to not. (Which I understand of course).

I will be posting a clean wattOS R8.1 in two weeks or so that will likely not being having the issues you are having with dependencies, installing stuff, etc.

tks
biff


Thanks for the reply Biff.  Yes, I'll mark this solved and give the LXDE version a try, and can wait a couple weeks to try the openbox. again.

Being a "MS Windows Refugee" running mostly on older hardware, I'm looking for an efficient system, both in terms of memory utilization and efficient use of what CPU there is.  Openbox is pretty good there, but not the best, IMO, so its not a bad idea to trry the LXDE

Thanks again for all your efforts :)

13
wattOS R8 / Re: What is the password for su?
« on: June 12, 2014, 12:48:49 PM »
Hinto,

I appreciate the suggestions, but for some unknown reason they aren't working like I would have expected on my pc.  Note that it gave me the authentication failure, but gave me a root login prompt anyway in this case.  If I was to just try su, it would not have given me the root login prompt.

Code: [Select]
bobc@dv9000a:~$ sudo su
[sudo] password for bobc:
su: Authentication failure
(Ignored)
root@dv9000a:/home/bobc#

It did not allow me to change the password, from the looks of it, perhaps because I tried to use the same password again
Code: [Select]
root@dv9000a:/home/bobc# passwd
Enter new UNIX password:
Retype new UNIX password:
passwd: Authentication token manipulation error
passwd: password unchanged
root@dv9000a:/home/bobc#


I get that same authentication failure from sux when I installed it and tried using it
Code: [Select]
bobc@dv9000a:~$ sux
Password:
su: Authentication failure
bobc@dv9000a:~$

I am ok now.  I do appreciate the suggestions because I have almost no experience with ubuntu methodologies, and am floundering in those areas, just trying to accomplish basic tasks to get up and running.

I am now using sudo roxterm from a terminal prompt and able to accomplish those needed tasks.  So I will mark this thread solved.

14
wattOS R8 / Re: su: Authentication failure
« on: June 12, 2014, 12:30:29 PM »
Its like a mosquito that chases me around, LOL.  It bites me in the neck, then goes away for a bit, and when I'm not looking again, it bites me in the leg.  Its a little different each time.  I did search for su authentication failure, but I think its just because nobody else typed in that error message.  The next person looking will find this post.

I tried Ubuntu once and only lasted one day because it felt like I was doing work to make the computer happy instead of the computer working for me.

What I was doing (su from within a terminal session) did work for almost a week, and I don't understand why it stopped working, but I'm guessing you are saying it wasn't really supposed to work in the first place.

Now it appears I can get a root terminal session that can do a copy/paste only by opening a terminal session, then doing a

Code: [Select]
sudo roxterm
The normal admin terminal session on the menu being used here can't do a copy/paste even with clipit installed and that's why I'm using roxterm, so that I can copy and paste the screen output to avoid needing to rekey all the messages by hand.

Anyway, thanks for pointing me to that post.  I'll mark this solved since I now have a root terminal session that can copy/paste.  That was what I was trying to get...

15
I think its gettiing the broken packages error when I try to install g++ (which is also needed for build-essential).

For example, I tried to install enlightenment e19, but can't compile it...

If you need me to run anything to help identify the problem, please let me know .

thanks

PS: I got roxterm running under root now, so am now able to copy/paste the error messages and config.log

If you could take a quick look in case its something simple, please.  I'm not a C programmer, but it appears to me that if the computer is setup properly to compile etc, that this should be able to work...  I just don't know enough to know what's missing...  Google search leads me to think  my repository source list is setup incorrectly, because it looks like I have a newer 2.18 version of libc6 than the standard debian one, so it would make sense to me that anything else I would install would have to be ok with that?

Code: [Select]

root@dv9000a:/home/bobc# cd enlightenment-0.19.0-alpha1
root@dv9000a:/home/bobc/enlightenment-0.19.0-alpha1# ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/bobc/enlightenment-0.19.0-alpha1':
configure: error: C compiler cannot create executables
See `config.log' for more details
root@dv9000a:/home/bobc/enlightenment-0.19.0-alpha1#

Here is the config.log being referred to above.  I have left out the "cache variables" at the end because its so long
Code: [Select]

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by enlightenment configure 0.19.0-alpha1, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure

## --------- ##
## Platform. ##
## --------- ##

hostname = dv9000a
uname -m = i686
uname -r = 3.13-0.bpo.1-486
uname -s = Linux
uname -v = #1 Debian 3.13.10-1~bpo70+1 (2014-04-23)

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:3000: checking build system type
configure:3014: result: i686-pc-linux-gnu
configure:3034: checking host system type
configure:3047: result: i686-pc-linux-gnu
configure:3089: checking for a BSD-compatible install
configure:3157: result: /usr/bin/install -c
configure:3168: checking whether build environment is sane
configure:3223: result: yes
configure:3374: checking for a thread-safe mkdir -p
configure:3413: result: /bin/mkdir -p
configure:3420: checking for gawk
configure:3436: found /usr/bin/gawk
configure:3447: result: gawk
configure:3458: checking whether make sets $(MAKE)
configure:3480: result: yes
configure:3509: checking whether make supports nested variables
configure:3526: result: yes
configure:3621: checking whether make supports nested variables
configure:3638: result: yes
configure:3662: checking for style of include used by make
configure:3690: result: GNU
configure:3761: checking for gcc
configure:3777: found /usr/bin/gcc
configure:3788: result: gcc
configure:4017: checking for C compiler version
configure:4026: gcc --version >&5
gcc (Debian 4.7.2-5) 4.7.2
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:4037: $? = 0
configure:4026: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i486-linux-gnu/4.7/lto-wrapper
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.2-5' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --enable-targets=all --with-arch-32=i586 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.7.2 (Debian 4.7.2-5)
configure:4037: $? = 0
configure:4026: gcc -V >&5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:4037: $? = 4
configure:4026: gcc -qversion >&5
gcc: error: unrecognized command line option '-qversion'
gcc: fatal error: no input files
compilation terminated.
configure:4037: $? = 4
configure:4057: checking whether the C compiler works
configure:4079: gcc    conftest.c  >&5
/usr/bin/ld: cannot find crt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
/usr/bin/ld: cannot find -lc
/usr/bin/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status
configure:4083: $? = 1
configure:4121: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "enlightenment"
| #define PACKAGE_TARNAME "enlightenment"
| #define PACKAGE_VERSION "0.19.0-alpha1"
| #define PACKAGE_STRING "enlightenment 0.19.0-alpha1"
| #define PACKAGE_BUGREPORT "enlightenment-devel@lists.sourceforge.net"
| #define PACKAGE_URL ""
| #define PACKAGE "enlightenment"
| #define VERSION "0.19.0-alpha1"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:4126: error: in `/home/bobc/enlightenment-0.19.0-alpha1':
configure:4128: error: C compiler cannot create executables
See `config.log' for more details

Pages: [1] 2