Porteus-v1.0-rc1-x86 ready for testing

[Hamza]

Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory

Another problem of corrupted ISO.

[wread]

@fanthom
Now I heard you are in charge of rc1-x86; the mystery of the empty boxes instead of characters in Google Earth is still there, until you get to it, I think. I posted it here http://www.porteus.org/forum/viewtopic. ... =100#p3154.

Brokenman thought it had to be with a bug in gtk to be solved in rc1 (negative results); I'll be when we do solve that.

Regards

[fanthom]

@all
nearly finished with 32bits, will need on more day (or two) to make sure that i have closed as many bugs as i could.

stay tuned.

@wread
launching google-earth with '-fn something' brings back all fonts except 3D ones (dont know why).

[Blaze]

fanthom, 1) I have suggestion.

I think need to cut code with part xconf of Linux Live scripts and paste it at beginning of LLS.
startx need to leave in the end code of LLS.

So it is possible to avoid problems with black screen for many "cases".

2) Are you downloaded my audacious-porteus-skin.xzm ?

[Ahau]

See MasterSplinters post here: http://www.porteus.org/forum/viewtopic. ... 4&start=10

the right-click service menus for konqueror are outdated and link to a utility, deb2sq4; it should be updated to deb2xzm. A quick look through the other entries (rpm2xzm, etc.) would probably be useful -- I spent some time looking for where this configuration takes place, and couldn't find it...but I know brokenman and fanthom know where it is

[Hamza]

Hello,

For konqueror menu , you can go to

Code: Select all

/usr/share/apps/konqueror/servicemenus

After, you will see all services-menus in konqueror. You can update them if you want.

Also , you can add your own services-menus.

[fanthom]

@Blaze and all
so far i have focused on bugfixing - tomorrow gonna put new stuff in (including audacious skin).

@Ahau
all konqueror services are fixed

@all
32bit are in good shape here but pls give me another 2-3 days as i would like to be sure that all is working as it should.
current screenshot:
http://oi51.tinypic.com/33ud2j6.jpg

please keep posting bug reports and feature requests.

Cheers

[Hamza]

Thanks a lot for screenshot!

[brokenman]

Looking very good. I might implement a hardware tester tool for v1.0 and integrate the power-saver, mouse/touchpad tweaker, xpns, and some other acpi functions for people with new i3/i5/i7 and switchable graphics.

I also made a list of all the important kernel modules and how to load them. The list may be useful for people with different models of laptops.

[Seq_Res]

This testing version does not boot up my old computer (mainboard 845, usb1.1, 1.7GHz);
syslinux 4.04 loops inside BIOS, and restart again and again. Remix/porteus09 worked perfectly.
Installation is okay, no error happened, and new notebook was booted without any problem.
Any suggestion ? thanks.

[Ahau]

@Seq_Res

I don't know what the cause might be, unless there's some kind of regression in syslinux.... my first thought was that maybe you'd tried installing the 32-bit version from a 64-bit linux OS, but since this stick boots fine on a newer laptop, that must not be the case.

So, I'm at a loss for how to fix this globally, but I do have a workaround for you -- the old syslinux from v09 should be able to fire up v1.0. Just download V09 again, mount the iso, copy the /boot folder to your USB device (rename the V1.0 boot folder to v1boot or something else), run the bootinst.sh script to install the old syslinux, then rename the V09 /boot folder (v09boot), and change the V1.0 /boot folder back to /boot. Don't run the new installer for V1.0. The only concern I have is that something in the porteus.cfg may changed...in which case you could copy the .cfg from the v09 /boot into the v1.0 /boot, and modify it (primarily, you'll need to adjust the initrd to be initrd.xz instead of initrd.lz).

I feel like I'm throwing out a bunch of instructions without much explanation...if I'm talking gibberish here, let me know.

[Blaze]

fanthom, what about this suggestion

I think need to cut code with part xconf of Linux Live scripts and paste it at beginning of LLS.
startx need to leave in the end code of LLS.

?

What do you think about this wallpaper http://imageshack.us/m/837/7254/bluebac ... stract.jpg for 32 bit?

[fanthom]

@Tonio
we wont go with 2.6.39 for 2 reasons:
1) 2.6.38.x kernel works just perfect while 2.6.39 brings some regressions:
http://www.phoronix.com/scan.php?page=a ... orks&num=1
2) aufs is not ready for 2.6.39 yet

@Blaze
nice wallpaper could you include a porteus logo in it?

Tomorrow morning rc2 is out

EDIT:\\
audacious Porteus skin is done in bmp files (huge size). any chance to get it in png?

[Blaze]

nice wallpaper could you include a porteus logo in it?

I tweaked it. Look at this wallpaper http://imageshack.us/m/805/2134/porteus ... r32bit.jpg

audacious Porteus skin is done in bmp files (huge size). any chance to get it in png?

The skin from bmp files is default for audacious. I check support a png files.

Добавлено спустя 38 минут 18 секунд:
Yes, this player is support png skins.
Download this update skin for Porteus: http://www.mediafire.com/?14pl4eekez7dq1v

fanthom, you are removed a floppy drive from porteus 32 bit?

[Tonio]

@Tonio
we wont go with 2.6.39 for 2 reasons:
1) 2.6.38.x kernel works just perfect while 2.6.39 brings some regressions:
http://www.phoronix.com/scan.php?page=a ... orks&num=1
2) aufs is not ready for 2.6.39 yet

No problem from me. It is my nephew that will b*tch at me for this

I will have to help him compile the Broadcom 14???b32 drivers that are on his laptop so that the wireless can work 8)

This is a fact of life. Some folks are happy that 2.6.39 is out except the ones in 1)

I hope in summer to have more time to check if some old drivers/scripts work to create new modules for xzm format and/or help in other areas. Thanks for all the work & time you dedicate to fixing things in both 32 and 64 bit porteus