Feedback for Porteus version 2.0 RC2

[chyang0527]

@fanthom
Thanks, i have checked my hard disk is created with SCSI in vmware. (the one has problem.)
I have tried to add additional disk with IDE type, and it could be mounted automatically while boot time.
And there seems no SATA type hard disk could be added in vmware, so i skip it.

Below are the information of the 'lspci -k' and 'lsmod' from the vmware with SCSI hard disk:
lspci -k

00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01)
Subsystem: VMware Virtual Machine Chipset
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 08)
Subsystem: VMware Virtual Machine Chipset
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
Subsystem: VMware Virtual Machine Chipset
Kernel driver in use: ata_piix
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
Subsystem: VMware Virtual Machine Chipset
00:07.7 System peripheral: VMware Virtual Machine Communication Interface (rev 10)
Subsystem: VMware Virtual Machine Communication Interface
00:0f.0 VGA compatible controller: VMware SVGA II Adapter
Subsystem: VMware SVGA II Adapter
Kernel driver in use: vmwgfx
00:11.0 PCI bridge: VMware PCI bridge (rev 02)
00:15.0 PCI bridge: VMware PCI Express Root Port (rev 01)
Kernel driver in use: pcieport
00:15.1 PCI bridge: VMware PCI Express Root Port (rev 01)
Kernel driver in use: pcieport
...
[skipped the duplicated message from 15.2 to 18.5]
...
00:18.6 PCI bridge: VMware PCI Express Root Port (rev 01)
Kernel driver in use: pcieport
00:18.7 PCI bridge: VMware PCI Express Root Port (rev 01)
Kernel driver in use: pcieport
02:00.0 USB controller: VMware USB1.1 UHCI Controller
Subsystem: VMware Device 1976
Kernel driver in use: uhci_hcd
02:01.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
Subsystem: VMware PRO/1000 MT Single Port Adapter
Kernel driver in use: e1000
02:02.0 Audio device: VMware Device 1977 (rev 09)
Subsystem: VMware Device 1977
Kernel driver in use: snd_hda_intel
02:03.0 USB controller: VMware USB2 EHCI Controller
Subsystem: VMware USB2 EHCI Controller
Kernel driver in use: ehci_hcd
03:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS1068 PCI-X Fusion-MPT SAS (rev 01)
Subsystem: VMware SAS Controller
Kernel driver in use: mptsas

lsmod

Module Size Used by
ipv6 162494 12
coretemp 4173 0
mperf 724 0
ppdev 3813 0
parport_pc 22006 0
parport 20949 2 ppdev,parport_pc
8250_core 17184 0
serial_core 11173 1 8250_core
floppy 39042 0
snd_hda_intel 18849 1
snd_hda_codec 56946 1 snd_hda_intel
snd_hwdep 3063 1 snd_hda_codec
snd_pcm 40216 2 snd_hda_codec,snd_hda_intel
mptsas 25099 1
snd_page_alloc 4783 2 snd_pcm,snd_hda_intel
vmwgfx 74362 0
scsi_transport_sas 13257 1 mptsas
intel_agp 6557 1
snd_timer 10823 1 snd_pcm
ttm 34795 1 vmwgfx
mptscsih 13710 1 mptsas
intel_gtt 9158 1 intel_agp
mousedev 6561 0
snd 28358 7 snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
vmw_balloon 3013 0
i2c_piix4 6521 0
freq_table 1658 0
drm 149339 2 ttm,vmwgfx
shpchp 17340 0
mptbase 43764 2 mptsas,mptscsih
agpgart 17236 4 drm,ttm,intel_agp,intel_gtt
soundcore 521 1 snd
e1000 73779 0
processor 21464 0
i2c_core 12251 2 drm,i2c_piix4
psmouse 48287 0
evdev 5853 7
pci_hotplug 16079 1 shpchp
thermal_sys 9277 1 processor
hwmon 863 2 coretemp,thermal_sys
ac 1537 0
button 3131 0
container 1665 0

I hope these information could be helpful.
Regards.

[Rava]

please provide psinfo log for an audio issue. do you have a sound in standalone player (audacious i guess?)

Code: Select all

----------------------
Output from psinfo
----------------------
script by jayflood
.

====== USER INFO =====
User is: root
.
===== MACHINE INFO =====
Platform: x86_64
Kernel: 3.7.5-porteus
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
Base Board Information
	Manufacturer: ASUSTeK Computer INC.
	Product Name: M2N-E
MemTotal:        3088036 kB
MemFree:         2617696 kB
Bootparam: quiet initrd=initrd.xz xfce changes=/porteus  BOOT_IMAGE=vmlinuz 
.
===== LIVE DEBUG INFO =====
# Recognized devices:
/dev/sda1: LABEL="extUSB03" UUID="0f7f7ee9-f4f3-425b-a92d-f9b1c6d92ba3" TYPE="ext2" 

# Booting device:
/mnt/sda1

# Porteus data found in:
/mnt/sda1/porteus

# Changes are stored in:
/porteus

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/sda1/porteus/base/000-kernel.xzm
/mnt/sda1/porteus/base/001-core.xzm
/mnt/sda1/porteus/base/002-xorg.xzm
/mnt/sda1/porteus/base/006-firefox.xzm
/mnt/sda1/porteus/base/0090-xfce.xzm
/mnt/sda1/porteus/base/0091-xfce-apps.xzm
/mnt/sda1/porteus/base/010-nVidia-310.32-v2.0-rc2-x86_64.xzm
.
===== SOUND INFO =====
Sound card:  0 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xfe024000 irq 21
Sound driver: Advanced Linux Sound Architecture Driver Version k3.7.5-porteus.
.
===== PARTITION INFO =====
Mounted: 
devtmpfs       devtmpfs  1.5G     0  1.5G   0% /dev
/dev/sda1      ext2      3.8G  2.7G  880M  76% /mnt/sda1
.
===== OPTICAl DRIVE =====
sr0
.
===== USB INFO =====
Removables: DataTraveler
Removable status: sd8:0:0:0:[sda]Protect
.
lsusb: Bus 001 Device 002: ID 0951:1603 Kingston Technology DataTraveler 1GB/2GB Pen Drive
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
.
===== SCREEN INFO =====
Screen 0: minimum 8 x 8, current 1440 x 900, maximum 8192 x 8192
.
===== ACTIVATED MODULES =====
000-kernel.xzm
001-core.xzm
002-xorg.xzm
006-firefox.xzm
0090-xfce.xzm
0091-xfce-apps.xzm
010-nVidia-310.32-v2.0-rc2-x86_64.xzm
.
===== NETWORK INFO =====
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:18:f3:ce:b7:d9  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 52  bytes 3432 (3.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 52  bytes 3432 (3.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
.
search example.net
.
===== PCI INFO =====
lspci: 00:00.0 RAM memory [0500]: nVidia Corporation MCP55 Memory Controller [10de:0369] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8239]
00:01.0 ISA bridge [0601]: nVidia Corporation MCP55 LPC Bridge [10de:0360] (rev a2)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8239]
00:01.1 SMBus [0c05]: nVidia Corporation MCP55 SMBus [10de:0368] (rev a2)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8239]
	Kernel driver in use: nForce2_smbus
00:02.0 USB controller [0c03]: nVidia Corporation MCP55 USB Controller [10de:036c] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8239]
	Kernel driver in use: ohci_hcd
00:02.1 USB controller [0c03]: nVidia Corporation MCP55 USB Controller [10de:036d] (rev a2)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8239]
	Kernel driver in use: ehci_hcd
00:04.0 IDE interface [0101]: nVidia Corporation MCP55 IDE [10de:036e] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8239]
	Kernel driver in use: pata_amd
00:05.0 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller [10de:037f] (rev a2)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8239]
	Kernel driver in use: sata_nv
00:05.1 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller [10de:037f] (rev a2)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8239]
	Kernel driver in use: sata_nv
00:05.2 IDE interface [0101]: nVidia Corporation MCP55 SATA Controller [10de:037f] (rev a2)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8239]
	Kernel driver in use: sata_nv
00:06.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI bridge [10de:0370] (rev a2)
00:06.1 Audio device [0403]: nVidia Corporation MCP55 High Definition Audio [10de:0371] (rev a2)
	Subsystem: ASUSTeK Computer Inc. Device [1043:81f6]
	Kernel driver in use: snd_hda_intel
00:08.0 Bridge [0680]: nVidia Corporation MCP55 Ethernet [10de:0373] (rev a2)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8239]
	Kernel driver in use: forcedeth
00:0f.0 PCI bridge [0604]: nVidia Corporation MCP55 PCI Express bridge [10de:0377] (rev a2)
	Kernel driver in use: pcieport
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
	Kernel driver in use: k8temp
02:00.0 VGA compatible controller [0300]: nVidia Corporation G98 [GeForce 8400 GS] [10de:06e4] (rev a1)
	Subsystem: Giga-byte Technology Device [1458:349c]
	Kernel driver in use: nvidia
.
.
===== LOGS INFO =====
dmesg | tail 
.
[   11.609777] Bluetooth: SCO socket layer initialized
[   11.653116] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   11.653121] Bluetooth: BNEP filters: protocol multicast
[   11.653133] Bluetooth: BNEP socket layer initialized
[   12.210078] NET: Registered protocol family 10
[   16.920541] forcedeth 0000:00:08.0: irq 41 for MSI/MSI-X
[   16.920579] forcedeth 0000:00:08.0 eth0: MSI enabled
[   16.920798] forcedeth 0000:00:08.0 eth0: no link during initialization
[   16.921387] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   18.341706] NVRM: GPU at 0000:02:00: GPU-ed181f9a-549f-a46d-0e33-ff99180a9c1d
.
.
cat /var/log/messages | tail
.
Feb  6 00:44:09 porteus gnome-keyring-daemon[1712]: The GPG agent was already initialized
Feb  6 00:44:09 porteus gnome-keyring-daemon[1712]: The PKCS#11 component was already initialized
Feb  6 00:44:09 porteus gnome-keyring-daemon[1712]: The Secret Service was already initialized
Feb  6 00:44:09 porteus gnome-keyring-daemon[1712]: The SSH agent was already initialized
Feb  6 00:44:10 porteus dbus[1109]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Feb  6 00:44:10 porteus dbus[1109]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb  6 00:44:11 porteus dbus[1109]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
Feb  6 00:44:11 porteus udisksd[1848]: udisks daemon version 1.98.0 starting
Feb  6 00:44:12 porteus dbus[1109]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb  6 00:44:12 porteus udisksd[1848]: Acquired the name org.freedesktop.UDisks2 on the system message bus
..

Here you go.

And I have not tested it with audacious, nor did I test it with mplayer and video clips...

[cttan]

Hi fanthom,

Libreoffice 3.6.5 x86_64 is out at Robby Workman page.

http://rlworkman.net/pkgs/14.0/x86_64/

[libernux]

Is it possible to adjust the /boot/syslinux/porteus.cfg file.
Since version 3.8.5 the DEFAULT command is used differently.
The current porteus setting is

Code: Select all

DEFAULT vesamenu.c32

Now if you change that to

Code: Select all

UI vesamenu.c32
DEFAULT putyourlabelhere

then the choice-screen will be visible with your label highlighted.
This way it is easier for lxde-users to highlight the second entry in the menu so that they can just "enter".

[fanthom]

@Rava
logs are looking good.
please test audio with audacious and playing movies through gnome-mpleyer and mplayer (cli version).
i'm pretty sure all will be ok as i have checked on my PC and was ok.

@cttan
unfortunately this is not a "real" slackware 14.0 package and i can't add it to the repo (PPM is very strict about dependencies).
please check my conversation with alienbob:
link

good news is that libreoffice-4.0 is out so Eric should prepare native slackware-14.0 version very soon

@libernux
added.
thanks for suggestion.

[FrosTr]

Tried RC2 Razor, i can't change keyboard layout to portuguese(brazil), keyboard settings at porteus settings centre isn't working
*Edit:Thanks brokenman

[brokenman]

Please open a console as guest and enter: setxkbmap br,us

This will change pt_BR as your default layout and en_US as the second. Click on the flag and it will change to en_US. I frequently use br,us so i know this works ok. When the final v2.0 is released you can use the Language Setup Tool to download all pt_BR files to your system.

The keyboard layout changer is a little buggy. There is now a new version of qxkb but i have found it is also buggy. So in the end i am forced to choose from the 'least buggy' layout switcher.

[Rava]

@Rava
logs are looking good.
please test audio with audacious and playing movies through gnome-mpleyer

and mplayer (cli version).
i'm pretty sure all will be ok as i have checked on my PC and was ok.

Will do, but why was the nvidia module not loaded? Is there any other additional test?
Can I use a cheatcode for booting so that Porteus is move verbose when it comes to modules loading during boot?

[inspector]

Porteus 2.0 XFCE 64 Bugs

1) Bug: tumblerd segfaults when the generation of thumbnails is triggered. Eg. viewing a folder with pictures in it. As a result, thumbnails aren't generated.

2) Bug: /opt/porteus-scripts/xfce/convert_txz script is not working on tgz files. I think its because the package extension is replaced with .txz prior to calling txz2xzm even though the original extension was tgz.

3) Bug: Joysticks/Gamepads not usable by normal users. root can use them with no problems. I noticed neither /dev/js0 nor /dev/input/js0 are created. I'm not sure if they are necessary since root seems to access the gamepad just fine. This might be a udev and/or permission issue, but I was able to fix this once by recompiling the kernel and including the joystick kernel module.

4) Suggestion: Upgrade lcms2 package version to 2.3 (the Slackware 14 version) for evince. Evince no longer relies on gnome, has Forms support, and keeps a record of recently opened pdf files.

Thanks for your hard work.

[Rava]

2) Bug: /opt/porteus-scripts/xfce/convert_txz script is not working on tgz files. I think its because the package extension is replaced with .txz prior to calling txz2xzm even though the original extension was tgz.

tgz was the older file type, and txz is the newer one using a different compressor, so your "though the original extension was tgz" is kinda misleading, since both file type do differ.

And the script does what it says: it converts txz.

When you want to use tgz files try tgz2xzm.
When you want to extract that tgz just run xzm2dir after the above.

[fanthom]

@Rava

Will do, but why was the nvidia module not loaded?

probably you were booting with 'always fresh' option which includes 'base_only' cheatcode. that's why nVidia was rejected and got accepted when you renamed it to 010-nVidia*.xzm.
please revert to original name and make sure you are booting only with 'xfce changes=/porteus' cheats.

Can I use a cheatcode for booting so that Porteus is move verbose when it comes to modules loading during boot?

'debug' wont make booting more verbose but lets you do several manual checks during boot.

@inspector

Bug: /opt/porteus-scripts/xfce/convert_txz script is not working on tgz files.

fixed

Bug: Joysticks/Gamepads not usable by normal users. root can use them with no problems. I noticed neither /dev/js0 nor /dev/input/js0 are created.

will compile support for them for final.
thanks.

[zer0-G]

I am using XFCE 64-bit v2rc2 and noticed that the floppy disk is showing in the removable drives area. I don't have a floppy disk drive? I believe this also was true in v2rc1 but v1.2 displayed properly.

Here is a screen shot: http://i47.tinypic.com/309m2x3.png

Thanks...

[Rava]

Will do, but why was the nvidia module not loaded?
probably you were booting with 'always fresh' option which includes 'base_only' cheatcode. that's why nVidia was rejected and got accepted when you renamed it to 010-nVidia*.xzm.
please revert to original name and make sure you are booting only with 'xfce changes=/porteus' cheats.

Yes, i indeed used "always fresh"... cause I thought it would only do that: not save anything on the USB stick...

What Do is use when I don't want Porteus to write any changes on the media?

Can I use a cheatcode for booting so that Porteus is move verbose when it comes to modules loading during boot?
'debug' wont make booting more verbose but lets you do several manual checks during boot.

Good to know

[fanthom]

@Rava
'Always Fresh' can be translated to "factory defaults" which means that all additional modules (which could break the system) are dropped and files from /rootcopy are not used (as they also could mess something) and magic folders are not bound (same reason).

'Always Fresh' is combined from following cheatcodes: nomagic, norootcopy, base_only and absence of 'changes='. please refer to /boot/docs/cheatcodes.txt for cheatcode descriptions.

What Do is use when I don't want Porteus to write any changes on the media?

you need to remove 'changes=' cheatcode

i think people are confused as used to think that 'always fresh' means that 'changes=' cheatcode is not present (i recon it's a slax-6.x heritage).
in Porteus 'always fresh' does more and brings the real "factory defaults" (as explained above).

[claude]

Some peculiar behavior you might want to look into. I have recently tried Porteus on two Dell Inspiron 8200 laptops,
one has an Nvidia GEFORCE4GO 32MB video card and the other an ATI Radeon 9000 64MB one.
The first one (Nvidia card) works fine with any distribution I've tried on it (including Porteus 1.1) except for Porteus
2.0-rc1...During boot up and right at:
"triggering udev events: /sbin/udevadm trigger --action=add"
after a few seconds, there is the usual bang from the system speakers, the screen goes blank and the system
freezes at that point. Is this video-card related?
Porteus 2.0-rc1 works just fine on the second one, the ATI Radeon 9000 system.

Question: The banging sound at the aforementioned point during boot up takes place on all systems I've tried
2.0-rc1 on... Why is this happening and is this necessary? The unexpected loudness of the "bang" from the
speakers somehow gives the impression that something might be getting damaged in the process...