Re: Porteus-v1.0-beta-x86_64 is ready :)
Posted: 09 Apr 2011, 10:33
What is your bluetouth manager?
Maybe , this is an issue with GUID.
Maybe , this is an issue with GUID.
Code: Select all
root@porteus:/mnt/live/memory/images# tail -n 3 /etc/profile
if [ -f /etc/profile.local ];then
. /etc/profile.local
fi
If yesis there a hibernate solution ready for v1.0-beta-x86_64?
Done (via NeoGrub)Hamza wrote: 1. You must install Porteus on a HDD
What's that?2. You must have a function hibernate RAM available.
I try my best to help improving Porteus.3. This is a good idea
Code: Select all
Failed to set up a loop device:
/path/to/containerfile
Is it a frugal installation copied on HDD ?Done (via NeoGrub)
Normally , it is available on KDE-4 , try the hibernate function in KDM Shutdown PanelYou must have a function hibernate RAM available.
Thanks very much.I try my best to help improving Porteus.
Have you included the librairies of TrueCrypt ? If No , looks where you have downloaded the truecrypt pkg.It worked well with V08 and the module created from truecrypt-7.0-i486-1alien.tgz
I think, I copied the files from the img to sda2 and set up the menu.lst accordingly...Hamza wrote: Is it a frugal installation copied on HDD ?
I run LXDE...Normally , it is available on KDE-4 , try the hibernate function in KDM Shutdown Panel
http://connie.slackware.com/~alien/slac ... /pkg/13.1/Have you included the librairies of TrueCrypt ? If No , looks where you have downloaded the truecrypt pkg.
And , Slax Remix is another thing than Porteus
Code: Select all
ldd /path/to/bluetouth-bin | grep "not found"
Code: Select all
bash-4.1$ cat /var/log/porteus-livedbg
# Recognized devices:
/dev/sr0: LABEL="Porteus" TYPE="iso9660"
/dev/sda1: UUID="a789e66e-f462-448b-9e29-0e54c6c9ac1b" TYPE="xfs"
/dev/sda2: UUID="BCE6-FC03" TYPE="vfat"
# Porteus boot device:
sr0
# Porteus data found in:
/memory/copy2ram
# Changes are stored in:
none
# Non standard /rootcopy dir:
none
# Loaded modules:
base/000-kernel.xzm
base/001-core.xzm
base/002-xorg.xzm
base/003-lxde.xzm
base/004-kde.xzm
base/005-devel.xzm
base/006-firefox-flash.xzm
base/vbox-guest-404-porteus-v1.0_beta-x84_64-1ftm.xzm
bash-4.1$
That's great...especially for you edited linuxrc and we have new livedbg (will be placed in /var/log as well as in /mnt/live/var/log)
Code: Select all
root@porteus:/mnt/live/memory/images# mount -t iso9660 -o loop /mnt/sda2/iso/gparted-live-0.8.0-5.iso /mnt/iso
mount: could not find any free loop device
I thought Porteus no longer needs a boot kernel tweak to give enough loop devices?Truecrypt works for me - make sure that you have free loop device.
With V08 I could define a border where no window is placed. So I always had one pixel of background on the right side, going there lets me change the desktop using the mouse wheel. I cannot find that with the above ..."When I click the right-click menu "Change Windowmanager settings" nothing happens."
try lxdemenu -> preferences -> Appearance
I hope I find the userspace acpi there as well..."where do I get the userspace /usr/bin/acpi?"
have no idea
"Which depository has been used for x86_64?"
standard slackware, for example here:
http://ftp.heanet.ie/mirrors/ftp.slackw ... 4-current/
I use this kernel module that enables you to call ACPI methods by writing the arguments to /proc/acpi/call, for example to turn off discrete graphics card in a dual graphics environment.where do I get the userspace /usr/bin/acpi?
Could I get the info about the temperature or the attached battery by that as well?brokenman wrote:I use this kernel module that enables you to call ACPI methods by writing the arguments to /proc/acpi/call, for example to turn off discrete graphics card in a dual graphics environment.
https://github.com/mkottman/acpi_call
Owww.... then LXDE is no longer an alternative to XFCe for me...fanthom wrote:lxde changed much since v08. now 'pcmanfm' is managing the desktop and not openbox (and 'automount' feature always works). this may be not possible anymore i'm afraid.
Code: Select all
bash-4.1$ cat /proc/acpi/battery/BAT0/state
present: yes
capacity state: ok
charging state: discharging
present rate: unknown
remaining capacity: 4384 mAh
present voltage: 11870 mV