Porteus-v1.0-rc2-x86_64 "We are there" (almost)

[fanthom]

All part of Porteus-1.0 puzzle are set in place no. It's a time for the very last release candidate for this version. All seems to work fine, but as always - testing is needed.
I would like to ask the "Doc Team" to have a look on /boot/docs/bloaders.txt and restore-mbr.txt as grub4dos more than likely wont make into this release so these docs needs to be updated. Also some path were changed (ie. MBR-Fix.exe is placed now in /boot/tools folder).
I think we could unify FAQ between 32/64bits and synchronize it with website version so they could look all the same - any volunteer?

I have decided to go with one of the standard Porteus wallpapers as i agree with brokenman that it will be rather quickly changed by user according to his preferences.
I'm not happy with new KDE-4.6.3 oxygen icons (folders looks simply worse) so i may downgrade this package to 4.6.2 in FINAL.

Repo:
http://ponce.cc/porteus/x86_64/testing/ ... -v1.0_rc2/

Promotional videos:
KDE-4 overview:
http://www.youtube.com/watch?v=YMq6oBQ_ ... er&list=UL
Porteus speed:
http://www.youtube.com/watch?v=9nVji588 ... re=related

Announcement for 32bit Porteus-rc1 featuring KDE-3.5.12 "Trinity" (instead of KDE-4 desktop):
http://forum.porteus.org/viewtopic.php?f=53&t=470

Changelog:
- kernel 2.6.38.5
- userland based on Slackware-13.37
- KDE-4.6.3
- LXDE from GIT by ponce compiled on Slack 13.37 - great job, even trash is working

Other - smaller changes:
- updated syslinux to version 4.0.4 (pxelinux.0 must be placed in /boot folder and not /boot/pxelinux.cfg) and removed some unnecessary files like chain.c32
- i have left in /boot folder only files interesting from user's point of view (porteus.cfg, porteus.png, vmlinuz, initrd.xz, etc..) - the rest are hidden inside the folders to make /boot folder look simpler and tidier.
- added new folder /tools which contains Fixmbr.exe, UAC.exe, memtest and /dos loader (should work ok from here, btw: i dont think that anybody is using it)
- added function to win_start_here.hta which disables UAC (Blaze's job)
- updated linuxrc and some other stuff inside initrd
- fixed dhcpcd long delay for IP in rc.inet1 (thanks to crashman for bug report)
- rc.M now creates 10 loops at boot instead of one (Rava request), also moves passwd.xzm automatically to /porteus/modules when is writable (francoise suggestion)
- new script: add_loop_devices which adds requested amount of loops to the system (also Rava)
- /usr/local/bin/man searches netowork when man page is not found in Porteus (82issa and lo-n-behold job)
- changes-time.sh strips module from *.cache files which are causing aufs hang
- activate script add one free module after insertion (it doesn't do anything when free loops are available)
- nouveau is blacklisted by default again as people are having troubles with compilation of nvidia binary driver
- bluetooth starts without problems and dolphin is able to send files to bluetooth with right mouse click
- USB HID is compiled into kernel (thanks to bong for bug report)
- fixed gtk theme and gtk icons in KDE
- added "kcm-gtk-config" package which lets you manage GTK icons/them from Systemsettings in KDE (same function as Lxappearance)
- changed default action for closing the laptop lid - it's 'Turn screen off' now and not suspend
- udisk mounts FAT and NFTS without 'showexec' flag (all files are executable: needed for porteus installation scripts)
- fixed bug in LST where kbd settings were never saved for guest and always for root
- hibernation works ok after upgrading to 2.6.38.5
- added 'Porteus' string to firefox user agent (Hamza's job), bumped ff to version 4.0.1 (thanks beny for help)
- new firefox addon "slackyd search bar" - it's disabled by default as it takes too much size on the bar (beny's finding)
- many, many, many other changes.....

enjoy and please report all bugs as usual.
(beny pls prepare nvidia drives when you have a chance)

Regards,
The Porteus Team

[Hamza]

I'll try it now !

Thanks a lot fanthom!

[82issa]

will have it in a few.

[Blaze]

Hi fanthom,
I have sugession. Remove it from boot:

Probably you can make a tool (for example, as a tool: Porteus save.dat manager) for run it from kde/lxde.
I think it will make Porteus faster & easier for newbies/users who badly knows English language.
Thanks.

[beny]

blaze if you give your password, you can use toroot cheatcode and you don't see this message anymore

[fanthom]

@Blaze
if i remove this function then i doubt that users will ever change their passwords -> whole security concept fails -> we can remove guest account and stick to root only
this is the only way to force (lazy) users for doing it.
GUI tool for changing the password makes no sense as user can run "passwd" command in console to achieve the goal.

@beny
you can use "toroot" without changing default passwords.

@all
i will explain how this "password check" function works:
1) rc.M checks if "toroot" cheatcode was used:
a) if yes, then edits kdm/lxdm configs to autologin root instead of guest (booting continue to GUI without stop)
b) if no, then it checks /etc/shadow and makes sure that root and guest are not using default passwords:
- if passwords are different then booting continue to GUI without stop
- if passwords matches default ones "toor" and "guest" then we have a STOP
2) now user can:
a) press enter twice to force booting with default passwords
b) provide new ones which:
- are saved automatically in /porteus/modules/psswd.xzm module, if this folder is writable (user is notified about this)
- if folder is not writable then psswd.xzm is dropped to /home/guest/Desktop (user is notified about this)

any ideas what i could improve here?
should i drop this function completely or leave it like that?

[beny]

http://www.mediafire.com/?n500id0e2k0fb hi fanthom the link of driver

[Hamza]

@fanthom,

Have you edited the porteus.cfg file for change the version from rc1 to rc2 ?

[fanthom]

@beny
thanks for Nvidia driver - added to official repo.

@Hamza
i have set it for 1.0 Final (i'm too lazy to change it every new alpha/beta/rc release)

Cheers

[Pedro]

Hi

Here are some issues i have found (not sure if they are bugs or not)

- I think there is some kind of problem with porteus save.dat manager when trying to resize files. Here's what i did

created a save file, then resized the size of this file, the manager asks me to select the file, next it asks me a name for the new save.dat file, selected a place for saving , it asks for the size of the file and after this step i get this in konsole:
loop: can't delete device /dev/loop20: Device or resource busy
mknod: `/dev/loop20': File exists
mknod: `/dev/loop20': File exists
cp: cannot stat `/mnt/olddat/*': No such file or directory
At the same time i get a message saying the file has been created. The final result, two files, the old and the new one

- When i try to run wallet managment tool nothing happens

- In pcman file manager if i choose open current folder as root, i get this message: Failed to execute child process "gksu" (No such file or directory)

- Porteus encrypter is giving errors, here is what i get:

Welcome to the Porteus Encrypter tool, which encrypts your exisiting
Porteus installation. As you probably know, keeping Porteus unencrypted on
a usb stick leaves you at risk for loosing private data such as bookmarks,
passwords, contacts, etc. To prevent this, we can encrypt almost
everything--except for the kernel, initrd and a few syslinux files in the
/boot folder. In case you lose your pendrive, whoever finds (or takes) it
will not be able to gain access to your private data. This tool will guide
you through the entire encryption process.

Press enter to continue or ctrl+c to exit.

Provide the desired size (in MB) of the encrypted container. Be aware
that you wont be able to resize it in the future. e.g.: 1024
500
500+0 records in
500+0 records out
524288000 bytes (524 MB) copied, 0.438065 s, 1.2 GB/s
/dev/loop1000: No such file or directory
mount: special device /dev/loop1000 does not exist
Copying /porteus folder to the container, please be patient...
All ok - tweaking initrd now...
umount: /mnt/crypt: not mounted
loop: can't delete device /dev/loop1000: No such file or directory
rmdir: failed to remove `/mnt/crypt': Directory not empty
Press enter to copy porteus.enc and tweaked initrd to /dev/sdc1

All operations are finished succesfully, plese modify your bootloader
config to point to the new initrd-enc.xz Example: 'APPEND initrd=initrd-enc.xz'
Enjoy!

Thanks
Pedro

[Hamza]

Could you post the output of ps-info ?

Could you post the output of this command

Code: Select all

ls /mnt/live/memory/images/*

[toby]

Hi,

I use porteus mainly for internet surfing, watching videos and listening mp3. I discovered porteous when my old notebook Acer 5500Z's harddisk was down. I was using ver0.9 32bit, it works perfectly. I can say porteus is a real small wonder, fast and stable.

Recently I bought a new Ausus model K43U, AMD fusion duo core 1.6GHz come with no operating system. So, naturally, the first thing come up from my mind is the porteus.
I downloaded the latest porteus-v1.0_rc2-x86_64, everything works nicely from live CD including for the monitor sized 1366x768, however there is one problem regarding the sounds output when I playing the videos with the media player and files from youtube.
It would be very much appreciate if someone could help me to solve this problem. Sorry if somebody has already posted the same problem here, in fact I did search and can't locate the specific issue on this forum.

Here are some observation:-


Music can be heard during the kde window startup

rmvb videos can be played flawlessly including sound only when playing the preview within the Dolphin File Manager.

Problems:
1. When videos open with Media Player, no sound output but only video.
2. same thing happen when playing youtube file in the web browser, only video without sound

/////////////////////////////////////////////////

( Phonon - KDE Control Module ) - Audio Output has 2 devices shown
1. HDA ATI SB
2. HD-Audio Generic, HDMI 0 (Audio Output)

Both giving correct sound wave under "test"

////////////////////////////////////////////////

root@porteus:~# lspci -nn
00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1510]
00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:9802]
00:01.1 Audio device [0403]: ATI Technologies Inc Device [1002:1314]
00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:1512]
00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] (rev 40)
00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397]
00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396]
00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397]
00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396]
00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 42)
00:14.1 IDE interface [0101]: ATI Technologies Inc SB700/SB800 IDE Controller [1002:439c] (rev 40)
00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] (rev 40)
00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] (rev 40)
00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] (rev 40)
00:14.5 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller [1002:4399]
00:15.0 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a0]
00:15.1 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a1]
00:16.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397]
00:16.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396]
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1700] (rev 43)
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1701]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1702]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1703]
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1704]
00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1718]
00:18.6 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1716]
00:18.7 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1719]
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
04:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)

///////////////////////////////////////////////////////////////////////////////////////

root@porteus:~# lspci -k
00:00.0 Host bridge: Advanced Micro Devices [AMD] Device 1510
Subsystem: Advanced Micro Devices [AMD] Device 1510
00:01.0 VGA compatible controller: ATI Technologies Inc Device 9802
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: radeon
Kernel modules: radeon
00:01.1 Audio device: ATI Technologies Inc Device 1314
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:04.0 PCI bridge: Advanced Micro Devices [AMD] Device 1512
Kernel driver in use: pcieport
Kernel modules: shpchp
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] (rev 40)
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: ahci
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: ohci_hcd
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: ehci_hcd
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: ohci_hcd
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: ehci_hcd
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 42)
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel modules: i2c-piix4
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller (rev 40)
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: pata_atiixp
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) (rev 40)
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller (rev 40)
Subsystem: ASUSTeK Computer Inc. Device 103c
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (rev 40)
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: ohci_hcd
00:15.0 PCI bridge: ATI Technologies Inc Device 43a0
Kernel driver in use: pcieport
Kernel modules: shpchp
00:15.1 PCI bridge: ATI Technologies Inc Device 43a1
Kernel driver in use: pcieport
Kernel modules: shpchp
00:16.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: ohci_hcd
00:16.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: ehci_hcd
00:18.0 Host bridge: Advanced Micro Devices [AMD] Device 1700 (rev 43)
00:18.1 Host bridge: Advanced Micro Devices [AMD] Device 1701
00:18.2 Host bridge: Advanced Micro Devices [AMD] Device 1702
00:18.3 Host bridge: Advanced Micro Devices [AMD] Device 1703
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge: Advanced Micro Devices [AMD] Device 1704
00:18.5 Host bridge: Advanced Micro Devices [AMD] Device 1718
00:18.6 Host bridge: Advanced Micro Devices [AMD] Device 1716
00:18.7 Host bridge: Advanced Micro Devices [AMD] Device 1719
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Device 103c
Kernel driver in use: r8169
Kernel modules: r8169
04:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: Device 1a3b:2c37
Kernel driver in use: ath9k
Kernel modules: ath9k

///////////////////////////////////////////////////////////////////////////////////

Thanks in advance

Regards

toby

EDIT:\\
merged with proper thread in development section as bugs related to unstable versions must be reported here

fanthom

[fanthom]

@Pedro
"porteus save.dat manager"
will check it...

"When i try to run wallet managment tool nothing happens"
yep - when run in console there is a message about missing/deprecated qt classes. looks like an upstream issue. will check what i can do about it (if nothing than i'm going to remove this app)

"In pcman file manager if i choose open current folder as root, i get this message: Failed to execute child process "gksu" (No such file or directory)"
will check it as well...

"Porteus encrypter is giving errors, here is what i get:"
should be easy to fix will do it for the FINAL.

@toby
yes - i have spotted the same thing yesterday. sound come back after restarting the GUI. will try to track it down.

thanks a lot for bug reports - it's really appreciated.

[ponce]

"In pcman file manager if i choose open current folder as root, i get this message: Failed to execute child process "gksu" (No such file or directory)"
will check it as well...

to fix that we need gksu-polkit (with his dependencies, vala and libgee): I prepared a slackbuild and I'm testing it now, seems to work fine for using it instead of the original gksu, that is not the best solution in a policykit environment.
I'll post the three packages soon

[Ahau]

Here's a draft updated bloaders.txt:

Code: Select all

***********************
* Porteus Bootloaders *
***********************

The bootloader that you install should be determined by the
file system of the partition on which you are installing Porteus.
You can see your file system by opening a console and issuing:
df -T /dev/xxxN  (where xxxN is your partition - e.g. sda1, sdb2, etc.)

EXT2/EXT3/EXT4
 - Use the extlinux bootloader for a graphic boot menu
 - Use the lilo bootloader for automatic textmode boot

FAT/FAT32
 - Use the syslinux bootloader for windows file systems
 - Please note that a save.dat file will be automatically
   created to save your changes. You can access your
   changes files by using the mount-changes command.

NTFS
 - Use the lilo bootloader, as syslinux does not support NTFS
 - If you prefer a graphic boot menu, you can download and install 
   grub4dos, which does support NTFS

Please double check my info for NTFS especially (would you like something else, or something more here?), and I changed the reference to df -T /dev/xxxN. If I leave off the partition number, I don't get useable information.

Here's a draft for restore-mbr.txt:

Code: Select all

Restoring your Master Boot Record

If you have accidentally overwritten your Master Boot Record (MBR) by running 
lin_start_here.sh or win_start_here.hta on a partition holding another 
operating system then you may be able to recover it.

WINDOWS
This applies only if you tried to run win_start_here.hta against a C: drive 
containing a windows install. It also assumes the most common instance where 
windows is on the first hard drive.

Inside the /boot/tools/ folder in the Porteus .iso there is a utility called 
MbrFix.exe. This utility is used to make a backup of the first 512 bytes of 
the first disk found, whenever win_start_here.hta is run. This backup, named 
mbr.bak, is placed on the root of the drive on which the win_start_here.hta 
script is run.

You can restore this backup to your drive's MBR by starting a command prompt 
as administrator, changing into the directory with MbrFix.exe (/boot/tools/) 
and running:
MbrFix /drive 0 restorembr mbr.bak

This utility has many other uses including rewriting a windows XP/Vista/7 MBR. 
You can see these other options by typing only MbrFix.exe

LINUX
If you chose to backup the MBR while running lin_start_here.sh then the first 
512 bytes of the chosen partition was backed up on the root of the drive 
from which you ran the lin_start_here.sh script. You can restore the MBR by 
copying the MBR backup elsewhere and issuing the following from a console:
dd if=/path/to/mbr.bak of=/dev/sdx bs=512 count=1 
(where sdx is the partition you are restoring to).

Again, please proofread, as I'm not positive on all the locations where things go. Is the "dd if=/path/to/mbr.bak of=/dev/sdx reference correct, or should it be of=/dev/sdxN? Or, does it vary depending on whether the user installed the bootloader to the MBR of the device, vs the boot sector of the partition?

Thanks!