a few stupid questions

Post here if you are a new Porteus member and you're looking for some help.
Post Reply
alchimik
White ninja
White ninja
Posts: 6
Joined: 24 Nov 2011, 12:31
Location: Varna / Bulgaria

a few stupid questions

Post#1 by alchimik » 28 Nov 2011, 13:28

Hi everybody !

1. where i wrong ?

This is my porteus.cfg file

Code: Select all

PROMPT 0
TIMEOUT 90
DEFAULT /boot/syslinux/vesamenu.c32
MENU BACKGROUND /boot/porteus.png
MENU TITLE Porteus-v1.1 64bit

MENU WIDTH 30
MENU MARGIN 2
MENU ROWS 10
MENU HELPMSGROW 17
MENU TIMEOUTROW 28
MENU TABMSGROW 15
MENU CMDLINEROW 22
MENU HSHIFT 4
MENU VSHIFT 5

	menu color screen	37;40      #00000000 #00000000 none
	menu color border	30;44      #00000000 #00000000 none
	menu color title	1;36;44    #ffA32F2F #30003f07 none
	menu color unsel	37;44      #ff111B78 #003f7fbf none
	menu color hotkey	1;37;44    #ff8037b7 #00000000 none
	menu color sel		7;37;40    #ff809aef #00000000 none
	menu color hotsel	1;7;37;40  #ffaf67f7 #003f7fbf none
	menu color scrollbar	30;44      #00000000 #00000000 none

	menu color tabmsg	31;40      #ffA32222 #00000000 none
	menu color cmdmark	1;36;40    #ffff0000 #00000000 none
	menu color cmdline	37;40      #ffffffff #ff000000 none
	menu color pwdborder	30;47      #ffff0000 #00000000 std
	menu color pwdheader	31;47      #ffff0000 #00000000 std
	menu color pwdentry	30;47      #ffff0000 #00000000 std
	menu color timeout_msg	37;40      #ff809aef #00000000 none
	menu color timeout	1;37;40    #ffb72f9f #00000000 none
	menu color help		37;40      #ff666C85 #00000000 none
	menu color msg07	37;40      #90ffffff #00000000 std

LABEL kde
MENU LABEL Graphics mode (KDE)
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.xz vga=791 changes=/mnt/sdb/porteus/0.dat
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL lxde
MENU LABEL Graphics mode (LXDE)
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.xz vga=791 lxde changes=/mnt/sdb/porteus/0.dat 
TEXT HELP
    Run Porteus the same as above.
    Lightweight LXDE to be
    launched as default desktop
ENDTEXT

LABEL fresh
MENU LABEL Always Fresh
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.xz nomagic 
TEXT HELP
    Normally Porteus saves all changes
    to the /porteus/changes/ directory
    on the boot media (if writable)
    and restores them next boot.
    Use this option to start a fresh
    system, changes are not read from
    or written to any device
ENDTEXT

LABEL copy2ram
MENU LABEL Copy To RAM
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.xz vga=791 copy2ram changes=/mnt/sdb/porteus/0.dat
TEXT HELP
    Run Porteus the same as above,
    but first copy all data to RAM
    to get a huge speed increase
    (needs >768MB)
ENDTEXT

LABEL vesa
MENU LABEL Graphics VESA mode
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.xz autoexec=vesa-mode changes=/mnt/sdb/porteus/0.dat 
TEXT HELP
    Run Porteus with KDE, but skip
    the graphics card autoconfig.
    This forces 1024x768 resolution
    using a standard VESA driver
ENDTEXT

LABEL text
MENU LABEL Text mode
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.xz autoexec=telinit~3 
TEXT HELP
    Run Porteus in text mode and
    start the command prompt only
ENDTEXT

LABEL pxe
MENU LABEL Porteus as PXE server
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.xz autoexec=pxe-boot 
TEXT HELP
    Run Porteus as usual, but also
    initialize a PXE server.
    This will allow you to boot Porteus
    on other computers over a network
ENDTEXT

MENU SEPARATOR

LABEL plop
MENU LABEL PLoP BootManager
KERNEL /boot/syslinux/plpbt
TEXT HELP
    Run the plop boot manager.
    This utility provides handy
    boot-USB options for machines
    with vintage/defective BIOS
ENDTEXT

LABEL memtest86
MENU LABEL Run Memtest utility
KERNEL /boot/tools/mt86p
TEXT HELP
    Don't start Porteus at all, but
    rather run the MemTest utility
    to diagnose your computer's RAM
    for possible errors
ENDTEXT
but every time when i start system - KDE crash ( many times , many variants cheatcode 'changes' ) . where the error ? When can't find file - OK , says can't find location and loading "Always fresh" - no my settings and work fine . When KDE crash ( freeze ) twice Ctrl+Alt+Del -> root console . write "startX" and report Error . Remove tmp/.X0-lock and start again . Follow instruction and .... other error :wall: What i wrong :cry:

2. Can't start Ktorrent .
Download from this site Ktorrent put in folder - OK . Click link with torrent - download . When click file - report "Can't lauch /usr/bin/ktorrent " ?
When start app from submenu "Internet" - icon jump 1-2 second ... hide and nothing :(

3 . Can i start x32 and x64 version Porteus in same Flash drive , same partition - without make 2 partitions ( like a universal Porteus ) .

4. Where find manual a clamav ( standart command no work ) , and why can't work - dowloaded from this site .

Kriss
Samurai
Samurai
Posts: 133
Joined: 06 Jul 2011, 07:07
Location: Russia

Re: a few stupid questions

Post#2 by Kriss » 28 Nov 2011, 14:26

1. I think your save file is corrupted.
Personally I'd create it anew (but I use custom module to store changes)...
Added: Forgot to add... I've noticed that new Porteus mounts its boot partition to /mnt/live/mnt/sdb instead of /mnt/sdb

2. Can you post a link? Probably you're using 32 bit module?
If that's not the case, then try to run ktorrent from console and post output here...

3. Yes. You can have many different versions on one partition, just remember that (as far as I know) different versions require different "vmlinuz" and "initrd.xz"
But if you're planning to do so it won't be wise if you have no idea what you're doing.
Here's my test porteus.cfg sample:

Code: Select all

PROMPT 0
TIMEOUT 90
DEFAULT /boot/syslinux/vesamenu.c32
MENU BACKGROUND /boot/porteus.png
MENU TITLE Porteus

MENU WIDTH 30
MENU MARGIN 2
MENU ROWS 10
MENU HELPMSGROW 17
MENU TIMEOUTROW 28
MENU TABMSGROW 15
MENU CMDLINEROW 22
MENU HSHIFT 4
MENU VSHIFT 5

	menu color screen	37;40      #00000000 #00000000 none
	menu color border	30;44      #00000000 #00000000 none
	menu color title	1;36;44    #ffA32F2F #30003f07 none
	menu color unsel	37;44      #ff111B78 #003f7fbf none
	menu color hotkey	1;37;44    #ff8037b7 #00000000 none
	menu color sel		7;37;40    #ff809aef #00000000 none
	menu color hotsel	1;7;37;40  #ffaf67f7 #003f7fbf none
	menu color scrollbar	30;44      #00000000 #00000000 none

	menu color tabmsg	31;40      #ffA32222 #00000000 none
	menu color cmdmark	1;36;40    #ffff0000 #00000000 none
	menu color cmdline	37;40      #ffffffff #ff000000 none
	menu color pwdborder	30;47      #ffff0000 #00000000 std
	menu color pwdheader	31;47      #ffff0000 #00000000 std
	menu color pwdentry	30;47      #ffff0000 #00000000 std
	menu color timeout_msg	37;40      #ff809aef #00000000 none
	menu color timeout	1;37;40    #ffb72f9f #00000000 none
	menu color help		37;40      #ff666C85 #00000000 none
	menu color msg07	37;40      #90ffffff #00000000 std


LABEL porteus64clean
MENU LABEL Porteus 64 v1.1 rc2
KERNEL /boot/64.clean/vmlinuz
APPEND initrd=/boot/64.clean/initrd.xz copy2ram toroot vga-detect from_dir=boot/64.clean sgnfile=porteus-v1.1-x86_64.USB
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL porteus64
MENU LABEL Porteus 64 v1.1 rc2
KERNEL /boot/64/vmlinuz
APPEND initrd=/boot/64/initrd.xz copy2ram toroot vga-detect from_dir=boot/64 sgnfile=porteus-v1.1-x86_64.USB
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL porteus64old
MENU LABEL Porteus 64 v1.1 rc1
KERNEL /boot/64.old/vmlinuz
APPEND initrd=/boot/64.old/initrd.xz copy2ram toroot vga-detect from_dir=boot/64.old sgnfile=porteus-v1.1-x86_64.old.USB
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL porteus32
MENU LABEL Porteus 32 v1.1 rc1
KERNEL /boot/32/vmlinuz
APPEND initrd=/boot/32/initrd.xz copy2ram toroot vga-detect from_dir=boot/32 sgnfile=porteus-v1.1-x86.USB
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

LABEL memtest86
MENU LABEL Run Memtest utility
KERNEL /boot/tools/mt86p
TEXT HELP
    Don't start Porteus at all, but
    rather run the MemTest utility
    to diagnose your computer's RAM
    for possible errors
ENDTEXT
4. I can't understand what you're trying to say. Sorry...
Last edited by Kriss on 29 Nov 2011, 12:05, edited 1 time in total.
Suggestions/corrections/additions are always welcome.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: a few stupid questions

Post#3 by Ahau » 28 Nov 2011, 15:46

Welcome, alchimik!

1) In your porteus.cfg, you are pointing to /mnt/sdb/porteus/0.dat. Is that the correct path to the file? Boot into 'Always Fresh' mode and check that path and file. You should have a number for the partition (right now, you have the device but not the partition listed) for example: /mnt/sdb1/porteus/0.dat, or /mnt/sdb2/porteus/0.dat. If adding the number doesn't help, please let us know how large (how many megabytes) 0.dat is -- if it is too small, it may fill up with data before KDE can finish loading, and that will cause errors. I agree with Kriss, it may be a good idea to create a new one.

2) Ktorrent is probably missing a dependency -- as Kriss suggested, try running it from a console and let us know the output (it should tell you the missing library).

3) Again, Kriss is correct, this can be done. See this doc for more information, and let us know if you have more questions: http://porteus.org/info/docs/37-install ... ition.html

4) I don't use ClamAV, but I have found some documentation for it, perhaps this is helpful?
http://www.clamav.net/doc/latest/clamdoc.pdf
http://linux.die.net/man/8/clamd
http://linux.die.net/man/1/clamdscan

For Ktorrent and ClamAV, please provide links to the locations from which you downloaded them. Or, if you downloaded them through the Porteus Package Manager, let us know that and I'll do some testing. I think you need to activate the modules through PPM in order to activate dependencies as well.

Cheers!
Please take a look at our online documentation, here. Suggestions are welcome!

Kriss
Samurai
Samurai
Posts: 133
Joined: 06 Jul 2011, 07:07
Location: Russia

Re: a few stupid questions

Post#4 by Kriss » 29 Nov 2011, 12:07

Edited my post with a bit of obsevation...
Suggestions/corrections/additions are always welcome.

alchimik
White ninja
White ninja
Posts: 6
Joined: 24 Nov 2011, 12:31
Location: Varna / Bulgaria

Re: a few stupid questions

Post#5 by alchimik » 01 Dec 2011, 18:47

So sorry for my late answer .

I find right path cheatcode in porteus.cfg - relative changes=/porteus/my.dat and changes=/mnt/sdb/porteus/my.dat ( dolphin manager preview ) - work but ...

try size 64 , 128 , 256 , 512 MB - same result - not remember settings :-(

the location where download package ktorrent and clamav is : http://www.ponce.cc/porteus/x86_64/modules/

This is snapshot for problem with him [img=http://lzw.hit.bg/temp/snapshot1.png]Click[/img]

User avatar
fanthom
Site Admin
Site Admin
Posts: 4614
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: a few stupid questions

Post#6 by fanthom » 02 Dec 2011, 17:47

hello alchimik,

try to use 1GB .dat file as 512MB may be not enough for KDE-4.
please use changes= cheatcode and boot Porteus, then run 'psinfo' tool and upload log file (will be placed on your desktop) to pastebin.com
please post a link to it in this thread.
log file will help up debugging KDE-4 startup issues.
Please add [Solved] to your thread title if the solution was found.

Kriss
Samurai
Samurai
Posts: 133
Joined: 06 Jul 2011, 07:07
Location: Russia

Re: a few stupid questions

Post#7 by Kriss » 10 Dec 2011, 11:01

2.
Ktorrent requires:
libktorrent-1.0.5_3-x86_64-1.xzm
nepomuk-4.6.4-x86_64-1ftm.xzm
soprano-2.6.0-x86_64-1ftm.xzm
They can be found here:
http://www.ponce.cc/porteus/x86_64/modules/libraries/

Many packages have some other packages they depend upon, so expect something like this in the future.
Just open console and execute program from there (like you typed "ktorrent") and look for output.
If it says that there's missing library or some other file, then google for it to understand what package it's in.
Then download that package, from Ponce's site (Porteus packages) or from some other distro.
If you downloaded files from other distro then use scripts to convert it to xzm (like deb2xzm txz2xzm or others) and activate them.
Suggestions/corrections/additions are always welcome.

User avatar
Hamza
Warlord
Warlord
Posts: 1847
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: a few stupid questions

Post#8 by Hamza » 10 Dec 2011, 11:33

No needs to use google for this.

Uses slackyd -d to resolve deps.
NjVFQzY2Rg==

Post Reply