Page 3 of 11

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 15 Apr 2011, 00:45
by Tonio
fanthom wrote: @Tonio
is it a usb dongle? maybe try 'lsusb' or at least 'dmesg'?

@all
please avoid rt2860 wifi cards for now. it's loosing signal very often running staging driver and (still) gives me occasional hangs during boot. i see that rt2800 is maturing in 2.6.39 (no more marked as EXPERIMENTAL) so i'm hoping to get it working correctly with this driver.
Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter

obtained with lsusb.

lsmod returns rtl8187 which is the driver that supports this card. Before it somehow appeared to work, but did not, now it at least connects for a while then it dies off. Hope this helps.

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 15 Apr 2011, 01:21
by Ahau
oddly enough, closing my laptop lid suspends my computer, and opening it starts it back up. It does take a while to get into suspension. Also, I got a segfault KDE crash after it resumed the second time. Screen went black, but came back to KDE.

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 15 Apr 2011, 07:51
by fanthom
@Tonio
ndiswrapper, ndiswrapper, ndiswrapper - try it and report back :)

@Ahau
"oddly enough, closing my laptop lid suspends my computer"
well - at least suspend works for you, int not my case unfortunately :(
as mentioned earlier - i have changed default action for closing the lid - it's 'Turn screen off' now and not suspend.

@all
seems that 'showexec' mount option for udisk is causing our troubles with missing 'x' bit on FAT/NTFS.
Probelm: http://ubuntuforums.org/archive/index.p ... 06193.html
Git commit: http://cgit.freedesktop.org/udisks/comm ... ea32589d0c

Solution means digging into source code (pity that theres no 'config' 'rules' etc... to set these perms)
I'm going to do it the faster/hackish way: http://ubuntuforums.org/showthread.php?t=1665289

@brokenman
please add this string to your cleanup/postconfig script for 002-xorg (or where you keep udisk package)
sed -i -e 's|showexec|\x00\x00\x00\x00\x00\x00\x00\x00|g' /usr/libexec/udisks-daemon

tried and works like a charm (all files has 'x' bit and lin_start_here.sh works correctly).
If anybody knows better solution (hidden udisk config?) - let us know

EDIT:\\
the above hack is solution for the case when user is installing Porteus on usb drive from PORTEUS itself. it's not a solution for all scenarios. Issue will be still present in all modern distros like Ubuntu, Fedora, Mandriva, etc which uses 'udisk' in version 1.0.2 or higher.

We must take another approach.
Ahau - please edit installation doc with information that Porteus can be installed on FAT/NTFS partitions only by mounting the device manually as root (it can't be automounted by KDE/LXDE/Gnome daemons) example:
"mkdir /tmp/media
mount /dev/sdXY /tmp/media
/tmp/media/boot/lin_start_here.sh"

this is the only way i'm afraid.... any other ideas?

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 15 Apr 2011, 14:43
by Ahau
@fanthom

I've added a note to the end of step #3 in the "install to usb drive from linux" section, so it reads:

Code: Select all

3) Open a console and change directories to the boot folder that you just copied into the flash drive, e.g.

cd /mnt/sdb1/boot

Execute the lin_start_here.sh script:

./lin_start_here.sh

*NOTE* If you are not running as root already, you must use the su or sudo command and enter your root password before starting this script, or it will not be able to configure your device properly.

*NOTE* Some modern linux distributions, such as Ubuntu, Fedora, Mandriva, etc, use 'udisk' to automount usb drives from within KDE/Gnome/LXDE, etc.  In versions higher than 1.0.2, udisk will not automount these drives with executable permissions (attempting to run the script will result in an error stating that permissions have been denied), and you must mount your device manually as root in order to execute the script.  For example:

	mkdir /tmp/media
	mount /dev/sdXY /tmp/media
	/tmp/media/boot/lin_start_here.sh

	(where sdXY is the device and partition to which you are installing Porteus)

This script will bring up a menu.

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 16 Apr 2011, 11:37
by Pedro
Hi
I'm having one problem with porteus language selection tool, here's what i tryed:
First i answer yes to utf/8 encoding, then i select pt_PT.utf8, porteus then asks me to download glibc-i18n, i press enter, then it asks me for my preffered keymap and says this "If you are not going to work in console mode, you can skip this step by leaving it blank and pressing enter", i leave it blank, i press enter and i get this message:

Please adjust the KDE4 (X mode) keyboard layout settings NOW and don't
forget to 'Apply' (save) your setup! then click 'OK' to continue!...

Press enter when done
kcmshell(3707): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)

KCrash: Application 'kcmshell4' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
sock_file=/root/.kde4/socket-porteus/kdeinit4__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi directly
drkonqi(3708): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)

Is there a problem in this tool or am i doing something wrong?
Thanks

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 16 Apr 2011, 20:32
by fanthom
@Ahau
thanks!

@Pedro
Thanks for bug report, i have fixed dbus issue (and another one: kbd settings were always saved for root and never for guest). LST is not updated yet - please wait for 1.0 Final as i need to upload localization files on ponce's server first.

Cheers

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 16 Apr 2011, 23:43
by Pedro
Hi
When i try to start magic folders setup tool a window opens asking for the root password but after that the window just closes. Running from the command-line i get this:

bash-4.1$ magic_folders
Please enter your root password below
Password:
/usr/bin/magic_folders: line 76: syntax error near unexpected token `else'
/usr/bin/magic_folders: line 76: `else'
bash-4.1$


PCMan file manager does not display icons but since i never worked before with this file manager is this normal?

Thanks
Pedro

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 17 Apr 2011, 16:18
by fanthom
hi Pedro,
1) fixed magic_folders
2) fixed also pcmanfm missing icons (also - KDE-4 now uses NODOKA-AQUA gtk-2 theme same as LXDE)

thanks a lot for testing and other bug reports are welcome :)

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 18 Apr 2011, 23:57
by 82issa
I have run into a problem I don't know if it has been addressed yet.
While building some xzm's and stripping out man files and docs and Crap icons.

Under lxterm
when I try to run

Code: Select all

rm -rf * /whatever
Nothing gets removed.
My work arround I am using different termminal emulator.
If I start dvtm (not included, home build)under lxde's term. It will work.
Kinda mysterious to me.

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 19 Apr 2011, 06:07
by Hamza
You must use the full path , e.g

Code: Select all

 rm -Rf /home/hamza/Documents/archive/* 

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 20 Apr 2011, 14:50
by cttan
Hi fanthom,

Is there a way for me to set a default password for the bluetooth?

Thanks in advance.

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 20 Apr 2011, 18:20
by Rava
fanthom wrote:Issue will be still present in all modern distros like Ubuntu, Fedora, Mandriva, etc which uses 'udisk' in version 1.0.2 or higher.
Why use that version of udisk then?

I am no expert on all that... but why not only use udev for automounting?

...

Or is udisk now a part of udev? Image

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 20 Apr 2011, 19:57
by fanthom
@cttan
do you mean the PIN? if yes then bluedevil should remember paired devices.
not sure if you can set default one for all devices around....

@Rava
"Why use that version of udisk then?"
"why not only use udev for automounting?"
i think you have missed the point - this is not about Porteus but about all other modern distros. wider explanation:
we can "fix" udisk in Porteus by removing 'showexec' flag, but we cant "fix" udisk in other distros. In case when user is running Mandriva with udisk version 1.0.2, all files on his usb stick will be non executable and he won't be able to use our installation scripts. There is nothing what we can do about it, just to advise to mount usb stick manually and skip automounting daemons.

Cheers

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 20 Apr 2011, 23:25
by Rava
fanthom wrote:we can "fix" udisk in Porteus by removing 'showexec' flag, but we cant "fix" udisk in other distros. In case when user is running Mandriva with udisk version 1.0.2, all files on his usb stick will be non executable and he won't be able to use our installation scripts. There is nothing what we can do about it, just to advise to mount usb stick manually and skip automounting daemons.
I see... so we will fix that issue for any running porteus, right, but need to put the info into the readme cause else the installation scripts won't work.

Re: Porteus-v1.0-rc1-x86_64 last call for testing

Posted: 21 Apr 2011, 00:14
by Tonio
fanthom wrote:@Tonio
ndiswrapper, ndiswrapper, ndiswrapper - try it and report back :)
I don't have original drivers(windows) a friend installed them for me :(
I am afraid to screw up, plus the distance the machine is from the router does not help, it connects but at slow speed. Hope I am forgiven for not reporting back on this one, as I lack experience with ndiswrapper and am afraid to screw up :(