porteus 32bit alpha testers required

[brokenman]

CONFIG="/opt/porteus-scripts/modtoolsrc"
CONFPATH="/$USER/.kde3/share/config/porteus-scripts"

Am I wrong here, or should CONFIG be /#USER/.kde3/share/config/porteus-scripts/modtoolsrc, correct?

CONFIG=/$USER/.kde3/share/config/modtoolsrc
CONFIGPATH=/$USER/.kde3/share/config
This would be ideal solution but i will have to check when i get home. From memory CONFIGPATH is used to check for the CONFIG file. Probably only need CONFIG and can get rid of CONFIGPATH

[brokenman]

I am hoping someone has a copy of the patch in this thread that fixed the problem where root couldn't boot to text mode and then startx.

startx-patch.lzm
Three files to fix problem with Porteus v09 alpha startx not working after root text mode login
(4 KiB) Downloaded 4 times

The file has been deleted from the server and i would like a copy of it. I can't remember what i did in the patch.

Thanks (hopefully)

[Ahau]

I can't verify that this is exactly what you had in that patch, but here's what I have:

http://www.mediafire.com/?4c2yxnlx7u9ywxw

My actual .xzm patch was removed when I downloaded the SVN update, but I found a folder in my /porteus/modules folder, where I had extracted the patch. I don't *think* I made any modifications...and of course it was saved to a FAT filesystem while extracted, so permissions are probably messed up. I hope this is helpful.

[brokenman]

Exactly what i was after! Thanks very much.

[hypomania]

hello,
why there are "*.xzm" and "*.lzm" modules !
and what will happen if I delete all *.xzm ??
and what will happen if I delete all *.lzm ??

I tried to install it on USB with bootins.sh and I run wizard success , but when I did reboot then not worked !

[Hamza]

The XZM is the new extension for Porteus Module , now , you will see this extension in BETA (v1.0) of Porteus x86_64

The LZM is the old extension for Porteus Module , now , you will see this extension in v0.9 of Porteus , but i think , it will be replaced by new extension in the v1.0.

Regards,

[hypomania]

I know it's new extension, but I asked to know why both modules !!

[Hamza]

For that , please ask the admin of the branch (Br0kenman)

[brokenman]

why there are "*.xzm" and "*.lzm" modules !

I don't understand. Where is there both modules?

[hypomania]

===========

when I copied all data to USB, then I executed "bootinst.sh" , was fail to make it bootable

Code: Select all

Flushing filesystem buffers, this may take a while...
Setting up MBR on /dev/sdb...
The Master Boot Record of  /dev/sdb  has been updated.
Activating partition /dev/sdb1...
No partition table modifications are needed.
Updating MBR on /dev/sdb...
Setting up boot record for /dev/sdb1...
./boot/syslinux/extlinux: invalid option -- 'd'
Usage: ./boot/syslinux/extlinux [options] directory
  --install    -i  Install over the current bootsector
  --update     -U  Update a previous EXTLINUX installation
  --zip        -z  Force zipdrive geometry (-H 64 -S 32)
  --sectors=#  -S  Force the number of sectors per track
  --heads=#    -H  Force number of heads
  --raid       -r  Fall back to the next device on boot failure
  --once=...   -o  Execute a command once upon boot
  --clear-once -O  Clear the boot-once command
  --reset-adv      Reset auxilliary data

  Note: geometry is determined at boot time for devices which
  are considered hard disks by the BIOS.  Unfortunately, this is
  not possible for devices which are considered floppy disks,
  which includes zipdisks and LS-120 superfloppies.

  The -z option is useful for USB devices which are considered
  hard disks by some BIOSes and zipdrives by other BIOSes.

I tried with option -z , but there is same problem,
./boot/syslinux/syslinux -z boot/syslinux

I think the code miss '$TARGET'
./boot/syslinux/syslinux -d boot/syslinux $TARGET

Posted after 3 hours 29 minutes 11 seconds:
by the way, boot image for porteus-v09 in water better than porteus-v1 with shark

[Ahau]

Just thought I'd mention (since I haven't heard it mentioned before specific to 32-bit) that the "modesetting" bug exists for 32 bit. I was fooling around with it this morning, and found 002-xorg.xzm lacking the nouveau driver--it was moved to lxde and kde modules, as a workaround. Brokenman, I suppose I'll leave it up to you, whether to leave modesetting in place and continue with the workaround, or pull modesetting and move nouveau back to 002.

[wread]

@brokenman
I'm afraid I am too late to test the alpha version now; so many issues have been already taken care of.
BTW, will you be calling for beta testers too? I downloaded it (the beta) to take a look at. It is a beauty, congratulations!
Only the keyboards I tried (en-int, es, fr, de) are broken. But the same keyboards of the alfa version are OK!
Maybe the keyboard maps got lost on the way from alfa to beta. Could you check on that? Maybe I have a corrupted download!

EDIT: Running "setxkbmap -query" you can notice that the KDE Keyboard Configuration Tool does not set the correct kbx map; I will try to fix it....

[hypomania]

porteus-v1-i486-alpha.iso
==================
1-
in menu system tools => should replace scripts from
konsole -e /opt/porteus-scripts/porteus-usb.sh <=To=> xterm -e /opt/porteus-scripts/porteus-usb.sh
konsole -e pns-tool <=To=> xpns-tool.sh
-------------------------------

[brokenman]

Please leave all comments for ALPHA in this thread. When BETA is released a new thread will be made. This will avoid confusion ... i am easily confused.

EDIT: Running "setxkbmap -query" you can notice that the KDE Keyboard Configuration Tool does not set the correct kbx map; I will try to fix it....
Any progress?
Can you try this please: setxkbmap -model pc104 -layout tr -variant basic
It should change the layout. Replace tr with us to get back to normal. After running this the keyboard switcher seems to work for me.

konsole -e /opt/porteus-scripts/porteus-usb.sh <=To=> xterm -e /opt/porteus-scripts/porteus-usb.sh
I agree ... other desktops will be able to use. This is now set by /tmp/.terminal care of fanthom (great idea too!)

konsole -e pns-tool <=To=> xpns-tool.sh
This is already done n BETA

[wread]

Can you try this please: setxkbmap -model pc104 -layout tr -variant basic
It should change the layout. Replace tr with us to get back to normal. After running this the keyboard switcher seems to work for me.

The switcher seems to work for me too!,

Bingo! It is the font we are now (beta) using for the konsole. It has not either á (a-accent), é, etc., nor ñ (for spanish coño!). Whereis the damm setting for the konsole font?