Porteus-v2.0-x86_64 bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v2.0-x86_64 bug reports

Post#16 by Ahau » 04 Mar 2013, 17:54

hi att, thanks for the report -- can you tell me how you're starting up xfce? Are you booting from cd, flash drive, etc., and are you autlogging in with the 'xfce' cheatcode or are you booting into init 3 and running 'startx' or 'startxfce' to log in? Or, is this only starting up inside a vnc session? When I was testing your vnc bug with the xkb switcher, I believe I noticed this error, but I'm not able to reproduce it outside of vnc.

Please let me know so I head down the correct path on troubleshooting this one :) thanks!

Also, with the vnc xkb-switcher bug, I wasn't able to find the direct cause or a solution yet, but I did notice similar behavior in other desktops (kde and lxde), so there's something at a lower level than xfce that's likely the issue.
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v2.0-x86_64 bug reports

Post#17 by Rava » 04 Mar 2013, 20:08

Like always, x86-64 XFCe version with nVidia drivers.

Seems there is an error in the 2.0 x86 used manpage for wget:
-nv
--no-verbose
Turn off verbose without being completely quiet (use -q for that),
which means that error messages and basic information still get
printed.

-nv
--report-speed=type
Output bandwidth as type. The only accepted value is bits.
Wget uses short version of options and long versions.

But sure, the long named options of --report-speed and --no-verbose cannot have the same short version option as -nv

Man page version is this:
GNU Wget 1.14 2012-08-14

Code: Select all

x@y:/z$ wget -V
GNU Wget 1.14 built on linux-gnu.[/quote]


The --help info suggests that --report-speed has no short option name at all:
[code]x@y:/z$ wget --help|grep -C 2 -- --report 
  -v,  --verbose             be verbose (this is the default).
  -nv, --no-verbose          turn off verboseness, without being quiet.
       --report-speed=TYPE   Output bandwidth as TYPE.  TYPE can be bits.
  -i,  --input-file=FILE     download URLs found in local or external FILE.
  -F,  --force-html          treat input file as HTML.
(Sure this is more of a bug of wget than one of Porteus, still me thinks we should correct all bugs we can? Yes, we can. Hopefully. xD)
_____________________________________________________

When trying to go back from resume on the Intel P2 DualCore Asus Board PC with nVidia graphics card, the monitor stays blank when coming back after suspend.
The PC fires up and seems to be running, but like with 1.2 finale, it seems the old nVidia issue is still not completely solved.

The xorg.conf from the nVidia module got an error and I could not start up X.

Therefore I ran nvidia-xconfig like so:

Code: Select all

nvidia-xconfig --silent --add-argb-glx-visuals --allow-glx-with-composite --composite -d 24 --disable-glx-root-clipping --damage-events --no-dynamic-twinview --enable-acpi-hotkeys --enable-all-gpus --logo --multigpu=Auto --multisample-compatibility --nvagp=3 --probe-all-gpus --randr-rotation --render-accel --render-extension --sli=Auto --use-int10-module --no-use-events --no-xinerama --xvmc-uses-textures --keyboard=de-latin1-nodeadkeys
(I forgot to also save the xorg.conf file... :oops: )

Output from psinfo

Code: Select all

====== USER INFO =====
User is: root
.
===== MACHINE INFO =====
Platform: x86_64
Kernel: 3.7.8-porteus
Processor: Intel(R) Pentium(R) D  CPU 2.66GHz
Base Board Information
	Manufacturer: ASUSTeK Computer INC.
	Product Name: P5PL2-E
MemTotal:        3475672 kB
MemFree:         3218596 kB
Bootparam: quiet initrd=initrd.xz xfce rootcopy=LABEL:extUSBXX1_2/porteus/rootcopy/ fsck delay=5 BOOT_IMAGE=vmlinuz 
.
===== LIVE DEBUG INFO =====
# Recognized devices:
/dev/sda1: LABEL="extUSBbla1" UUID="18FC-blah" TYPE="vfat" 
/dev/sda2: LABEL="extUSBbla1_2" UUID="3d99blah" TYPE="ext2" 

# Booting device:
/mnt/sda1

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

# Changes are stored in:
memory

# Non standard /rootcopy dir:
LABEL:extUSBbla1_2/porteus/rootcopy/

# 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-130220-alldesktops.xzm
/mnt/sda1/porteus/base/0090-xfce.xzm
/mnt/sda1/porteus/base/0091-xfce-apps.xzm
/mnt/sda1/porteus/base/091-heimseite.xzm  <- just local homepages
/mnt/sda1/porteus/base/nVidia-310.32-porteus-v2.0-x86_64-1ftm.xzm
.
===== SOUND INFO =====
Sound card:  0 [Intel          ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xdddf8000 irq 44
Sound driver: Advanced Linux Sound Architecture Driver Version k3.7.8-porteus.
.
===== PARTITION INFO =====
Mounted: 
devtmpfs       devtmpfs  1.7G     0  1.7G   0% /dev
/dev/sda1      vfat      7.2G  2.1G  5.1G  29% /mnt/sda1
/dev/sda2      ext2      310M  4.1M  306M   2% /mnt/sda2
.
===== OPTICAl DRIVE =====

.
===== USB INFO =====
Removables: USB
Removable status: sd4:0:0:0:[sda]Protect
.
lsusb: Bus 001 Device 002: ID 8644:800b  
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
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
.
===== SCREEN INFO =====

.
===== ACTIVATED MODULES =====
000-kernel.xzm
001-core.xzm
002-xorg.xzm
006-firefox-130220-alldesktops.xzm
0090-xfce.xzm
0091-xfce-apps.xzm
091-heimseite.xzm
nVidia-310.32-porteus-v2.0-x86_64-1ftm.xzm
.
===== NETWORK INFO =====
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:1a:92:31:92:08  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 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
.
search example.net
.
===== PCI INFO =====
lspci: 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8178]
00:01.0 PCI bridge [0604]: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port [8086:2771] (rev 02)
	Kernel driver in use: pcieport
00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5LD2-VM Mainboard (Realtek ALC 882 codec) [1043:817f]
	Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 01)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 4 [8086:27d6] (rev 01)
	Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8179]
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8179]
	Kernel driver in use: ata_piix
00:1f.2 IDE interface [0101]: Intel Corporation N10/ICH7 Family SATA Controller [IDE mode] [8086:27c0] (rev 01)
	Subsystem: ASUSTeK Computer Inc. Device [1043:2601]
	Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller [8086:27da] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8179]
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5B [1043:81aa]
	Kernel driver in use: r8169
04:00.0 VGA compatible controller [0300]: nVidia Corporation NV44 [GeForce 6200 LE] [10de:0163] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:820b]
.
.
===== LOGS INFO =====
dmesg | tail 
.
[   18.698256] Bluetooth: HCI device and connection manager initialized
[   18.698273] Bluetooth: HCI socket layer initialized
[   18.698278] Bluetooth: L2CAP socket layer initialized
[   18.698310] Bluetooth: SCO socket layer initialized
[   18.758423] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   18.758430] Bluetooth: BNEP filters: protocol multicast
[   18.758446] Bluetooth: BNEP socket layer initialized
[   19.006319] r8169 0000:02:00.0 eth0: link down
[   19.249405] NET: Registered protocol family 10
[   19.249993] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Now for the failed wakeup after suspend.

I tee'd the /var/log/messages to the USB stick since I run Porteus without the changes= cheatcode.

At 11:00:38 I suspended the system and tried to wake it up at 11:10:27. But the screen kept blank...

Code: Select all

Mar  4 11:00:38 porteus kernel: [ 2310.652542] PM: Syncing filesystems ... done.
Mar  4 11:00:38 porteus kernel: [ 2310.692563] serial 00:0e: disabled
Mar  4 11:00:38 porteus kernel: [ 2310.692627] serial 00:0e: wake-up capability disabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.692703] i8042 aux 00:0c: wake-up capability disabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.692771] i8042 kbd 00:0b: wake-up capability enabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.693214] parport_pc 00:07: disabled
Mar  4 11:00:38 porteus kernel: [ 2310.724117] PM: suspend of devices complete after 47.835 msecs
Mar  4 11:00:38 porteus kernel: [ 2310.724311] PM: late suspend of devices complete after 0.192 msecs
Mar  4 11:00:38 porteus kernel: [ 2310.724510] pcieport 0000:00:1c.3: wake-up capability enabled by ACPI
Mar  4 11:00:38 porteus acpid: client 3022[0:1000] has disconnected
Mar  4 11:00:38 porteus kernel: [ 2310.735182] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.746048] uhci_hcd 0000:00:1d.3: wake-up capability enabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.746079] uhci_hcd 0000:00:1d.2: wake-up capability enabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.746110] uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.746140] uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.746185] PM: noirq suspend of devices complete after 21.870 msecs
Mar  4 11:00:38 porteus kernel: [ 2310.746366] ACPI: Preparing to enter system sleep state S3
Mar  4 11:00:38 porteus kernel: [ 2310.746743] PM: Saving platform NVS memory
Mar  4 11:00:38 porteus kernel: [ 2310.748511] smpboot: CPU 1 is now offline
Mar  4 11:00:38 porteus kernel: [ 2310.749099] ACPI: Low-level resume complete
Mar  4 11:00:38 porteus kernel: [ 2310.749099] PM: Restoring platform NVS memory
Mar  4 11:00:38 porteus kernel: [ 2310.749099] Enabling non-boot CPUs ...
Mar  4 11:00:38 porteus kernel: [ 2310.750279] smpboot: Booting Node 0 Processor 1 APIC 0x1
Mar  4 11:00:38 porteus kernel: [ 2310.763688] CPU1 is up
Mar  4 11:00:38 porteus kernel: [ 2310.764695] ACPI: Waking up from system sleep state S3
Mar  4 11:00:38 porteus kernel: [ 2310.776219] uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.776253] uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.776287] uhci_hcd 0000:00:1d.2: wake-up capability disabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.776320] uhci_hcd 0000:00:1d.3: wake-up capability disabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.787057] ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.809192] PM: noirq resume of devices complete after 44.124 msecs
Mar  4 11:00:38 porteus kernel: [ 2310.809352] PM: early resume of devices complete after 0.119 msecs
Mar  4 11:00:38 porteus kernel: [ 2310.809709] pcieport 0000:00:1c.3: wake-up capability disabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.813578] parport_pc 00:07: activated
Mar  4 11:00:38 porteus kernel: [ 2310.813594] i8042 kbd 00:0b: wake-up capability disabled by ACPI
Mar  4 11:00:38 porteus kernel: [ 2310.814574] serial 00:0e: activated
Mar  4 11:00:38 porteus kernel: [ 2313.992010] 
Mar  4 11:00:38 porteus kernel: [ 2313.992011] floppy driver state
Mar  4 11:00:38 porteus kernel: [ 2313.992011] -------------------
Mar  4 11:00:38 porteus kernel: [ 2313.992024] now=4297271288 last interrupt=4294972475 diff=2298813 last called handler=0xffffffffa0047bb2
Mar  4 11:00:38 porteus kernel: [ 2313.992025] timeout_message=lock fdc
Mar  4 11:00:38 porteus kernel: [ 2313.992026] last output bytes:
Mar  4 11:00:38 porteus kernel: [ 2313.992028]  8 80 4294972459
Mar  4 11:00:38 porteus kernel: [ 2313.992030]  8 80 4294972459
Mar  4 11:00:38 porteus kernel: [ 2313.992031]  8 80 4294972459
Mar  4 11:00:38 porteus kernel: [ 2313.992032]  8 80 4294972473
Mar  4 11:00:38 porteus kernel: [ 2313.992033]  8 80 4294972473
Mar  4 11:00:38 porteus kernel: [ 2313.992034]  8 80 4294972473
Mar  4 11:00:38 porteus kernel: [ 2313.992036]  8 80 4294972473
Mar  4 11:00:38 porteus kernel: [ 2313.992037]  e 80 4294972474
Mar  4 11:00:38 porteus kernel: [ 2313.992038] 13 80 4294972474
Mar  4 11:00:38 porteus kernel: [ 2313.992039]  0 90 4294972474
Mar  4 11:00:38 porteus kernel: [ 2313.992041] 1a 90 4294972474
Mar  4 11:00:38 porteus kernel: [ 2313.992042]  0 90 4294972474
Mar  4 11:00:38 porteus kernel: [ 2313.992043] 12 90 4294972474
Mar  4 11:00:38 porteus kernel: [ 2313.992044]  0 90 4294972474
Mar  4 11:00:38 porteus kernel: [ 2313.992045] 14 90 4294972474
Mar  4 11:00:38 porteus kernel: [ 2313.992047] 18 80 4294972474
Mar  4 11:00:38 porteus kernel: [ 2313.992048]  8 80 4294972475
Mar  4 11:00:38 porteus kernel: [ 2313.992049]  8 80 4294972475
Mar  4 11:00:38 porteus kernel: [ 2313.992050]  8 80 4294972475
Mar  4 11:00:38 porteus kernel: [ 2313.992051]  8 80 4294972475
Mar  4 11:00:38 porteus kernel: [ 2313.992053] last result at 4294972475
Mar  4 11:00:38 porteus kernel: [ 2313.992054] last redo_fd_request at 4294972475
Mar  4 11:00:38 porteus kernel: [ 2313.992060] status=4f
Mar  4 11:00:38 porteus kernel: [ 2313.992061] fdc_busy=1
Mar  4 11:00:38 porteus kernel: [ 2313.992064] do_floppy=0xffffffffa0047bb2
Mar  4 11:00:38 porteus kernel: [ 2313.992065] cont=ffffffffa004d830
Mar  4 11:00:38 porteus kernel: [ 2313.992066] current_req=          (null)
Mar  4 11:00:38 porteus kernel: [ 2313.992067] command_status=-1
Mar  4 11:00:38 porteus kernel: [ 2313.992068] 
Mar  4 11:00:38 porteus kernel: [ 2313.992072] floppy0: floppy timeout called
Mar  4 11:00:38 porteus kernel: [ 2313.992118] PM: resume of devices complete after 3182.761 msecs
Mar  4 11:10:23 porteus acpid: client connected from 3022[0:1000]
Mar  4 11:10:23 porteus acpid: 1 client rule loaded
Mar  4 11:10:25 porteus kernel: [ 2649.538971] Switching to clocksource hpet
Mar  4 11:10:27 porteus kernel: [ 2902.987396] EXT4-fs (sda2): re-mounted. Opts: (null)
Mar  4 11:10:27 porteus NetworkManager[1574]: <info> wake requested (sleeping: yes  enabled: yes)
Mar  4 11:10:27 porteus NetworkManager[1574]: <info> waking up and re-enabling...
Mar  4 11:10:27 porteus NetworkManager[1574]: <info> WWAN now enabled by management service
Mar  4 11:10:27 porteus NetworkManager[1574]: <info> (eth0): now managed
Mar  4 11:10:27 porteus NetworkManager[1574]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Mar  4 11:10:27 porteus NetworkManager[1574]: <info> (eth0): bringing up device.
Mar  4 11:10:27 porteus NetworkManager[1574]: <info> (eth0): preparing device.
Mar  4 11:10:27 porteus NetworkManager[1574]: <info> (eth0): deactivating device (reason 'managed') [2]
Mar  4 11:10:27 porteus kernel: [ 2903.121324] r8169 0000:02:00.0 eth0: link down
Mar  4 11:10:27 porteus kernel: [ 2903.121376] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Mar  4 11:22:14 porteus -- MARK --
Mar  4 11:42:14 porteus -- MARK --
Mar  4 12:02:14 porteus -- MARK --
Mar  4 12:22:14 porteus -- MARK --
Mar  4 12:29:50 porteus init: Switching to runlevel: 0
(And yes, the eth0 cable was not connected...)
Cheers!
Yours Rava

att
Contributor
Contributor
Posts: 131
Joined: 28 Dec 2010, 17:09

Re: Porteus-v2.0-x86_64 bug reports

Post#18 by att » 05 Mar 2013, 14:12

Hi Ahau,

I am booting it from USB using "textmode" + copy2ram + nonetwork + volume 0%
I log in as root in textmode, I do "xconf", then "startx".
The error sometimes shows up just when being in normal xfce mode, with no previous (from text console) started vncserver-windows.
Sometimes, it only shows up inside the vnc session, if I *did* start a vncserver in textmode before starting the x system with "startx".
But only sometimes.

In the meantime I found another bug. :(
When I wanted to log in to the vncserver, I got the "password" prompt from the vncviewer, and exactly at that time, the terminal behind it got weird:

Image

Image

As you can see, the lower part of the terminal, who called the vncviewer, got rotated.
The computer was a Dell Optiplex 960 with no hardware changes, no extra cards, etc.
Strange, isn't it ?

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v2.0-x86_64 bug reports

Post#19 by Ahau » 05 Mar 2013, 18:21

hi att,

I really have no idea what happened with the terminal screen getting flipped around. Seems like some kind of a video driver or xorg anomaly, so if it happens again, let us know (especially how to reproduce it).

Regarding the policykit error you're getting - this seems to be hit or miss (and it sounds like it's the same on your system). I only saw it once while I was testing, and that was starting with copy2ram, nonetwork, and logging in as guest. Since the symptom doesn't present every time, I'm not sure that I've found a solution, but I *think* the problem is that we have to policykit daemons running at the same time, and they are entering some kind of race condition, where if one of them start interacting with the xsession first, everything is fine, otherwise this error crops up.

To test my theory, please disable lxpolkit and see if the problem persists. If you have saved changes (I'm guessing you don't) you can simply delete /etc/xdg/autostart/lxpolkit.desktop. If you don't have saved changes, echo 0 > /etc/xdg/autostart/lxpolkit.desktop and then copy it into your rootcopy folder (/mnt/sdXY/porteus/rootcopy/etc/xdg/autostart/lxpolkit.desktop) so that lxpolkit is not started when you enter an xsession.

32-bit Porteus Xfce does not have lxpolkit, and IIRC it's in 64-bit to make sure a dialog box pops up for network manager when you attempt to connect to a password-protected wireless network. When I disabled lxpolkit I was still able to connect to an unsecured wifi network, but it failed to connect to a password-protected one (that said, I have kind of shotty reception where I was testing), and it sounds like you're not using a network anyway ('nonetwork' might actually be necessary in order for this issue to present since I haven't seen it otherwise). I also didn't get the error popping up when I started a vnc session with lxpolkit disabled.

I hope that helps, please let us know :)
Please take a look at our online documentation, here. Suggestions are welcome!

Falcony
Full of knowledge
Full of knowledge
Posts: 233
Joined: 01 Jan 2011, 12:44
Location: Russia

Re: Porteus-v2.0-x86_64 bug reports

Post#20 by Falcony » 07 Mar 2013, 08:37

Hi Fantom, Brokenman, Ahau & other Porteus contributors,

Thank you your enormous efforts,

Just reviewed Porteus 2.0 looks nice, quick and very useful distro.

Regarding version 2,0 x64 and PXE boot.

As just I reviewed linuxrc and see it changed from initrd to initrdramfs and other possible changese could bring error - /bin/ash chabnged to busybox /bin/sh/

Now if I boot Porteus client from PXE linuxrc show error on row 7:

Code: Select all

if [ -d /m ];then 

Boot scripts says that operand not found(I suppose that it happens due change /bin/ash to /bin/sh)

To work around this problem I try to escape this problem and type all command by hand one by one in console of recovery.

Next code

Code: Select all


cp -a ??* /m



bring Input/Output error due reason I suppose the size of RAM for initrdramfs is not enough as initrdramfs which include initrd plus initrdpxe(network drivers) is bigger that initrdramfs with initrd only.

May be it fails due other reasons. Anyway, please checks PXE booting and if possible fix it. PXE boot is nice option of Porteus Д)


,

User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus-v2.0-x86_64 bug reports

Post#21 by fanthom » 07 Mar 2013, 18:15

@Rava
i think you should report this issue upstream (either to slackware or wget devs) as we do not maintain manual pages here.

@Falcony
welcome back - long time to see :)

Just checked on 64bit standard edition and PXE boot works perfectly fine here. did you modify initrd by any chance?
if yes then please try with original porteus one. if no then please provide a photo of the failure.

thanks
Please add [Solved] to your thread title if the solution was found.

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Porteus-v2.0-x86_64 bug reports

Post#22 by cttan » 08 Mar 2013, 02:26

Hi fanthom,

Awesome release. Thanks for the suggestion to upgrade to release 2.0. I have upgraded with minimal issue.
Normally I set the screen brightness using this command:-
echo 2223333 > /sys/class/backlight/intel_backlight/brightness

After setting this in Porteus 2.0, the value is not sync with the hardware switch value. The above command set to about 80% of brightness but in the GUI it is still showing 100% brightness. It is working fine in Porteus 1.2. Just want to highlight to you and no action is require.

KDE 4.9.5 solved most of the problem especially crash when you right click and press the "Properties" of a file.

Enjoy your well deserved off days from Porteus development! :good:

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Porteus-v2.0-x86_64 bug reports

Post#23 by cttan » 14 Mar 2013, 00:45

Hi fanthom,

Just had my Porteus 2.0 crached after returning from sleep.

Pls see snapshot here:-
http://postimage.org/image/ebtlz8afx/

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v2.0-x86_64 bug reports

Post#24 by Ahau » 14 Mar 2013, 01:40

Hey cttan,

I've had a couple similar events. Everything seems to resume, but a few minutes later, it crashes.

Did you have an SD card or other MMC type card in when it happened? IIRC, I had issues getting to my data on the sdcard, and was messing with it when the system crashed.

I'll do some more testing to see if I can recreate it reliably and report back to help fanthom narrow this down.
Please take a look at our online documentation, here. Suggestions are welcome!

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Porteus-v2.0-x86_64 bug reports

Post#25 by cttan » 14 Mar 2013, 02:27

Hi Ahau,

I have an USB thumb drive and a microSD card inserted. The Porteus is booted up from USB thumb drive.
The microSD card contain Porteus 1.2 and it is still inserted into the laptop.

Luckily after few crashes the data on my USB thumb drive is still intact.
Normally crashed will only make the usb drive unbootable where you will receive a message "Boot error" and require to re-run the Porteus-installer-for-Linux setup. This has been the norm since the remix day.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v2.0-x86_64 bug reports

Post#26 by Rava » 14 Mar 2013, 11:02

Again the up to now unsolved issue with x86-64 Port2.0 and sound via HDMI to the Full-HD TV...

psinfo.txt:

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: Intel(R) Core(TM) i7 CPU       Q 720  @ 1.60GHz
Base Board Information
	Manufacturer: TOSHIBA
	Product Name: NWQAA
--
	Asset Tag: Base Board Asset Tag
	Features:
		Board is a hosting board
MemTotal:        3984404 kB
MemFree:         2856328 kB
Bootparam: quiet initrd=initrd.xz xfce BOOT_IMAGE=vmlinuz 
.
===== LIVE DEBUG INFO =====
# Recognized devices:
/dev/sda1: LABEL="System" UUID="xxxx" TYPE="ntfs" 
/dev/sda2: LABEL="intHDD2" UUID="xxxx" TYPE="ntfs" 
/dev/sda4: LABEL="HDDRECOVERY" UUID="xxxx" TYPE="ntfs" 
/dev/sda5: UUID="xxxx" TYPE="ext3" 
/dev/sdb1: LABEL="xxxx" UUID="xxxx" TYPE="ext2" 
## (rava edited the UUIDs and LABELs above...)

# Booting device:
/mnt/sdb1

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

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/sdb1/porteus/base/000-kernel.xzm
/mnt/sdb1/porteus/base/001-core.xzm
/mnt/sdb1/porteus/base/002-xorg.xzm
/mnt/sdb1/porteus/base/006-firefox.xzm
/mnt/sdb1/porteus/base/0090-xfce.xzm
/mnt/sdb1/porteus/base/0091-xfce-apps.xzm
/mnt/sdb1/porteus/base/010-nVidia-310.32-v2.0-rc2-x86_64.xzm
.
===== SOUND INFO =====
Sound card:  0 [MID            ]: HDA-Intel - HDA Intel MID
                      HDA Intel MID at 0xd8400000 irq 47
 1 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xd3000000 irq 16
Sound driver: Advanced Linux Sound Architecture Driver Version k3.7.5-porteus.
.
===== PARTITION INFO =====
Mounted: 
devtmpfs       devtmpfs  1.9G     0  1.9G   0% /dev
/dev/sda1      ntfs      1.5G  693M  808M  47% /mnt/sda1
/dev/sda2      ntfs      256G  183G   73G  72% /mnt/sda2
/dev/sda4      ntfs      9.2G  8.7G  611M  94% /mnt/sda4
/dev/sda5      ext3       22G   15G  6.1G  71% /mnt/sda5
/dev/sdb1      ext2      3.8G  2.7G  910M  76% /mnt/sdb1
/dev/sdc       vfat      7.6G  6.8G  781M  90% /run/media/guest/USB_xxx
.
===== OPTICAl DRIVE =====
sr0
.
===== USB INFO =====
Removables: DataTraveler
USB
Removable status: sd1:0:0:0:[sda]Protect
sd6:0:0:0:[sdb]Protect
sd7:0:0:0:[sdc]Protect
sd8:0:0:0:[sdc]Protect
.
lsusb: Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0951:1603 Kingston Technology DataTraveler 1GB/2GB Pen Drive
Bus 002 Device 004: ID 046a:0100 Cherry GmbH 
Bus 002 Device 006: ID 1307:0165 Transcend Information, Inc. 2GB/4GB Flash Drive
.
===== SCREEN INFO =====
Screen 0: minimum 8 x 8, current 3286 x 1080, 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 70:5a:b6:c1:eb:ac  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

eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet6 fe80::b682:feff:fee5:ae9d  prefixlen 64  scopeid 0x20<link>
        ether b4:82:fe:e5:ae:9d  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
        device interrupt 17  

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 56  bytes 3840 (3.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 56  bytes 3840 (3.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
.
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line
.
===== PCI INFO =====
lspci: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DMI [8086:d132] (rev 11)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express Root Port 1 [8086:d138] (rev 11)
	Kernel driver in use: pcieport
00:08.0 System peripheral [0880]: Intel Corporation Core Processor System Management Registers [8086:d155] (rev 11)
00:08.1 System peripheral [0880]: Intel Corporation Core Processor Semaphore and Scratchpad Registers [8086:d156] (rev 11)
00:08.2 System peripheral [0880]: Intel Corporation Core Processor System Control and Status Registers [8086:d157] (rev 11)
00:08.3 System peripheral [0880]: Intel Corporation Core Processor Miscellaneous Registers [8086:d158] (rev 11)
00:10.0 System peripheral [0880]: Intel Corporation Core Processor QPI Link [8086:d150] (rev 11)
00:10.1 System peripheral [0880]: Intel Corporation Core Processor QPI Routing and Protocol Registers [8086:d151] (rev 11)
00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
	Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
	Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05)
	Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 [8086:3b44] (rev 05)
	Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 [8086:3b46] (rev 05)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 [8086:3b48] (rev 05)
	Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 [8086:3b4a] (rev 05)
	Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
	Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller [8086:3b09] (rev 05)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller [8086:3b29] (rev 05)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
	Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 05)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
01:00.0 VGA compatible controller [0300]: nVidia Corporation GT216 [GeForce GT 330M] [10de:0a29] (rev a2)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
	Kernel driver in use: nvidia
01:00.1 Audio device [0403]: nVidia Corporation High Definition Audio Controller [10de:0be2] (rev a1)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
	Kernel driver in use: snd_hda_intel
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
	Kernel driver in use: r8169
07:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
	Subsystem: Askey Computer Corp. Device [144f:7175]
	Kernel driver in use: wl
16:00.0 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host Controller [197b:2382] (rev 20)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
	Kernel driver in use: sdhci-pci
16:00.2 SD Host controller [0805]: JMicron Technology Corp. Standard SD Host Controller [197b:2381] (rev 20)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
16:00.3 System peripheral [0880]: JMicron Technology Corp. MS Host Controller [197b:2383] (rev 20)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
	Kernel driver in use: jmb38x_ms
16:00.4 System peripheral [0880]: JMicron Technology Corp. xD Host Controller [197b:2384] (rev 20)
	Subsystem: Toshiba America Info Systems Device [1179:fd30]
ff:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers [8086:2c52] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture System Address Decoder [8086:2c81] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link 0 [8086:2c90] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:02.1 Host bridge [0600]: Intel Corporation Core Processor QPI Physical 0 [8086:2c91] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:03.0 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller [8086:2c98] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:03.1 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder [8086:2c99] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:03.4 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller Test Registers [8086:2c9c] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:04.0 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers [8086:2ca0] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:04.1 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers [8086:2ca1] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:04.2 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers [8086:2ca2] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:04.3 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers [8086:2ca3] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:05.0 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers [8086:2ca8] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:05.1 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers [8086:2ca9] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:05.2 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers [8086:2caa] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
ff:05.3 Host bridge [0600]: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers [8086:2cab] (rev 04)
	Subsystem: Intel Corporation Device [8086:8086]
.
.
===== LOGS INFO =====
dmesg | tail 
.
[ 1707.107254] sd 8:0:0:0: [sdc] Write Protect is off
[ 1707.107258] sd 8:0:0:0: [sdc] Mode Sense: 00 00 00 00
[ 1707.107898] sd 8:0:0:0: [sdc] Asking for cache data failed
[ 1707.107909] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 1707.111804] sd 8:0:0:0: [sdc] Asking for cache data failed
[ 1707.111813] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 1707.213502]  sdc:
[ 1707.428439] sd 8:0:0:0: [sdc] Asking for cache data failed
[ 1707.428451] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 1707.428458] sd 8:0:0:0: [sdc] Attached SCSI removable disk
.
.
cat /var/log/messages | tail
.
Feb 17 19:22:55 porteus logger: ACPI group video / action brightnessdown is not defined
Feb 17 19:22:56 porteus last message repeated 8 times
Feb 17 19:26:43 porteus kernel: [ 1706.013401] usb 2-1.3: new high-speed USB device number 6 using ehci_hcd
Feb 17 19:26:43 porteus kernel: [ 1706.101466] scsi8 : usb-storage 2-1.3:1.0
Feb 17 19:26:44 porteus kernel: [ 1707.105428] scsi 8:0:0:0: Direct-Access     USB2.0   FlashDisk        0.00 PQ: 0 ANSI: 2
Feb 17 19:26:44 porteus kernel: [ 1707.106508] sd 8:0:0:0: [sdc] 15794176 512-byte logical blocks: (8.08 GB/7.53 GiB)
Feb 17 19:26:44 porteus kernel: [ 1707.107254] sd 8:0:0:0: [sdc] Write Protect is off
Feb 17 19:26:45 porteus kernel: [ 1707.213502]  sdc:
Feb 17 19:26:45 porteus kernel: [ 1707.428458] sd 8:0:0:0: [sdc] Attached SCSI removable disk
Feb 17 19:27:06 porteus udisksd[2779]: Mounted /dev/sdc at /run/media/guest/USB_FD07 on behalf of uid 1000
..

Code: Select all

root@porteus:~# grep -i sound /var/log/messages 
Feb 17 17:47:40 porteus kernel: [   23.502202] input: HDA Intel MID Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
Feb 17 17:47:40 porteus kernel: [   23.502324] input: HDA Intel MID Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Feb 17 17:47:40 porteus kernel: [   23.891186] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input12
Feb 17 17:47:40 porteus kernel: [   23.891274] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input13
Feb 17 17:47:40 porteus kernel: [   23.891350] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input14
Feb 17 17:47:40 porteus kernel: [   23.891425] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input15

Code: Select all

guest@porteus:/path/to/sound$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: MID [HDA Intel MID], device 0: ALC269VB Analog [ALC269VB Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 0 [HDMI 0]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
So I tried all 4 devices with mplayer as this:

Code: Select all

guest@porteus:/path/to/sound$ mplayer name.wav -ao alsa:device=hw=1.3
guest@porteus:/path/to/sound$ mplayer name.wav -ao alsa:device=hw=1.7
guest@porteus:/path/to/sound$ mplayer name.wav -ao alsa:device=hw=1.8
guest@porteus:/path/to/sound$ mplayer name.wav -ao alsa:device=hw=1.9
It always did "play" the sound file, but without any sound...

I also wanted to play it like above by using instead aplay, but could not figure out how to use the right parameters for e.g. alsa:device=hw=1.7


Or are the hw=1.3 no longer alsa devices?
But then mplayer would have exited with an error instead of "playing" them?

*scratches head*

_____________________________________________________

Also, mplayer crashes when I try to seek in a digital TV recording. It happens when I seek "by hand" using gnome-mplayer, it also happens when I seek via CLI parameter, like so:

Code: Select all

root@porteus:/path/to/TVREC/# file 000.dvr 
000.dvr: MPEG sequence, v2, program multiplex

root@porteus:/path/to/TVREC/# mplayer -ao alsa -cache 9216 000.dvr -ss 0:13:00 -forceidx
MPlayer SVN-r34180-4.5.1 (C) 2000-2011 MPlayer Team

Playing ALIDVRS2/2013-03-13.17.27.07-The Hard Times O-697/000.dvr.
Cache fill:  0.00% (0 bytes)   

libavformat file format detected.
[mpegts @ 0xd60d20]Could not detect TS packet size, defaulting to non-FEC/DVHS
[mpegts @ 0xd60d20]Continuity check failed for pid 0 expected 1 got 3
[mpegts @ 0xd60d20]parser not found for codec dvb_teletext, packets or times may be invalid.
[mpegts @ 0xd60d20]Continuity check failed for pid 0 expected 1 got 3
[mp3 @ 0xd63fa0]Header missing
[mpegts @ 0xd60d20]max_analyze_duration 5000000 reached at 5016000
[NULL @ 0xd63fa0]start time is not set in estimate_timings_from_pts
[mpegts @ 0xd60d20]PES packet size mismatch
[lavf] stream 0: video (mpeg2video), -vid 0
[lavf] stream 1: audio (mp2), -aid 0
[lavf] stream 2: subtitle (dvb-teletext), -sid 0, -slang deu
LAVF: Program 28670 
LAVF: Program 28671 
LAVF: Program 28673 
LAVF: Program 28674 
LAVF: Program 28675 
LAVF: Program 28676 
LAVF: Program 28677 
LAVF: Program 28679 
LAVF: Program 28680 
LAVF: Program 28682 
VIDEO:  [MPG2]  720x576  0bpp  25.000 fps  9000.0 kbps (1098.6 kbyte/s)
Load subtitles in .
[mpegts @ 0xd60d20]Continuity check failed for pid 0 expected 1 got 3
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffmpeg2] vfm: ffmpeg (FFmpeg MPEG-2)
==========================================================================
==========================================================================
Requested audio codec family [mpg123] (afm=mpg123) not available.
Enable it at compilation.
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
[mp2float @ 0xd63fa0]Header missing
AUDIO: 48000 Hz, 2 ch, floatle, 256.0 kbit/8.33% (ratio: 32000->384000)
Selected audio codec: [ffmp2float] afm: ffmpeg (FFmpeg MPEG layer-1 and layer-2 audio)
==========================================================================
AO: [alsa] 48000Hz 2ch floatle (4 bytes per sample)
Starting playback...


MPlayer interrupted by signal 11 in module: seek
- MPlayer crashed by bad usage of CPU/FPU/RAM.
  Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
  It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  gcc version. If you think it's MPlayer's fault, please read
  DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  won't help unless you provide this information when reporting a possible bug.
This crash happens with or without any parameters (aside from the video file), also with or without the extra parameter "-forceidx"

I also tried to play that file with vlc but to no avail. Usually these video recordings worked okay in Windoze OS using vlc... :(
Cheers!
Yours Rava

User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Porteus-v2.0-x86_64 bug reports

Post#27 by fanthom » 14 Mar 2013, 11:38

@cttan
- picture is a bit too small.
- please post an url to full xpsinfo report.
- i see vbox modules linked in (which are 'tainted crap': link) - does the same happen when you boot in 'always fresh' mode (no extra modules, rootcopy, magic folders, etc). i would like to be sure that it's a kernel fault and not 3rd party drivers.
- does it happen on any other linux distro with fairly recent kernel?
- how often does it happen?

btw: i'll enable P2P for iwlwifi driver for next release.

@Rava
a) hdmi sound:
- please upgrade to full 2.0 (currently you are on rc2)
- please test hdmi sound without nvidia driver
- did it ever work on any previous porteus releases? does it work on any other linux system?

b) mplayer crash
-did you try to convert this file to any other format/codec? i'm wondering if ffmpeg would be able to handle conversion. if not then maybe file is damaged (especially that also vlc is not able to play it)?
Please add [Solved] to your thread title if the solution was found.

cttan
Shogun
Shogun
Posts: 332
Joined: 26 Jan 2011, 16:15
Distribution: Porteus 3.2 64bit KDE
Location: Malaysia

Re: Porteus-v2.0-x86_64 bug reports

Post#28 by cttan » 14 Mar 2013, 14:20

Hi fanthom,

Thanks in advance for the iwlwifi P2P driver.

Here is the link to full size photo:-
https://www.box.com/s/g180ku8405comp06g9x7

I have used copy2ram mode and have activated many modules. Maybe I have activated the Virtualbox as well.
The crash happen randomly.

I will do some test on always fresh mode and report back.

User avatar
Hamza
Warlord
Warlord
Posts: 1847
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: Porteus-v2.0-x86_64 bug reports

Post#29 by Hamza » 14 Mar 2013, 17:11

Memory corruption? Did you made a "memtest check" on your RAM?
NjVFQzY2Rg==

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Porteus-v2.0-x86_64 bug reports

Post#30 by Rava » 16 Mar 2013, 01:08

fanthom wrote:a) hdmi sound:
- please upgrade to full 2.0 (currently you are on rc2)
rc2? Seems I used the wrong USB stick, then. *facedesks*
I restart that machine and give you the heads up...
- please test hdmi sound without nvidia driver
- did it ever work on any previous porteus releases? does it work on any other linux system?
It did work well with 1.2 rc2, but I could not update to 1.2 finale on that machine due to the resume blank screen error of the nvidia driver...
fanthom wrote:b) mplayer crash
-did you try to convert this file to any other format/codec? i'm wondering if ffmpeg would be able to handle conversion. if not then maybe file is damaged (especially that also vlc is not able to play it)?
No, but I try to convert it... Is ffmpeg better than mplayer for converting?
Cheers!
Yours Rava

Post Reply