PCLinuxOS Openbox Bonsai 2010.11<s>.13</s> who wants to test ?

[melodie]

Logs are there and not numerous. You might as well look in your's to seek for errors and warnings. If you can do a copy/pasteI would like to see the content of the prcsys.log and of any of the files if containing errors and warnings : coming from a usb stick that just hang : but mounted on another system once the usb live is not running anymore.

[Was_Just19]

Logs are there and not numerous. You might as well look in your's to seek for errors and warnings. If you can do a copy/pasteI would like to see the content of the prcsys.log and of any of the files if containing errors and warnings : coming from a usb stick that just hang : but mounted on another system once the usb live is not running anymore.

Contents of
/changes/var/log/prsys.log

Code: [Select]

Stopping HAL daemon: [  OK  ]
Saving mixer settings [  OK  ]
Shutting down ntpd: [  OK  ]
Stopping acpi daemon: [  OK  ]
Stopping uuidd: [  OK  ]
Stopping system message bus: [  OK  ]
Shutting down interface eth0:  [  OK  ]
Shutting down loopback interface:  [  OK  ]
Stopping resolvconf: [  OK  ]
Total time: 2 seconds

[melodie]

Contents of
/changes/var/log/prsys.log

Code: [Select]

Stopping HAL daemon: [  OK  ]
Saving mixer settings [  OK  ]
Shutting down ntpd: [  OK  ]
Stopping acpi daemon: [  OK  ]
Stopping uuidd: [  OK  ]
Stopping system message bus: [  OK  ]
Shutting down interface eth0:  [  OK  ]
Shutting down loopback interface:  [  OK  ]
Stopping resolvconf: [  OK  ]
Total time: 2 seconds

Here is mine:

Code: [Select]

Stopping HAL daemon: [  OK  ]
Saving mixer settings [  OK  ]
Shutting down ntpd: [  OK  ]
Stopping acpi daemon: [  OK  ]
Stopping uuidd: [  OK  ]
Stopping system message bus: [  OK  ]
Shutting down interface eth0:  [  OK  ]
Shutting down loopback interface:  [  OK  ]
Stopping resolvconf: [  OK  ]
Total time: 1 seconds
Next time resolvconf won't be there anymore. I even wonder if we still need this package anyhow ? (?)

Now what, as far as errors are concerned on your side ? Here:

$ pwd
/media/disk-1/changes/var/log

$ grep -R error *
dmesg:EXT2-fs (sda2): error: unable to read superblock
dmesg:EXT2-fs (sda3): error: couldn't mount because of unsupported optional features (240)
dmesg:EXT2-fs (sda6): error: couldn't mount because of unsupported optional features (240)
dmesg:EXT2-fs (sda7): error: couldn't mount because of unsupported optional features (240)
dmesg:EXT2-fs (sda8): error: couldn't mount because of unsupported optional features (240)

// Theses above are the hard drive partitions it tries to mount. I think it doesn't matter too much.

gdm/:0.log:   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
gdm/:0.log:error setting MTRR (base = 0xc0000000, size = 0x0ff00000, type = 1) Invalid argument (22)
gdm/:0.log:error setting MTRR (base = 0xc0000000, size = 0x0ff00000, type = 1) Invalid argument (22)

I get the same "MTRR" errors in one tty on my Archlinux installs and they don't bother normal functionning. I had once tried to find out what it was related to, but as it seemed not that important I forgot about what I had found that can be related to mtrr.

gdm/:0.log.1:   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
gdm/:0.log.1:error setting MTRR (base = 0xc0000000, size = 0x0ff00000, type = 1) Invalid argument (22)
Xorg.0.log:   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Xorg.0.log.old:   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

In Xorg.0.log, one warning, no error:

Code: [Select]

(WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
dri makes me think to the issue reported by Jeff with his ati Mach64 card.

and in Xorg.0.log.old the same warning plus one more on v4l:

Code: [Select]

(WW) Falling back to old probe method for v4l
There are no other log files.

Does this gives you any idea ?

Specs of the machine used:

Dell GX280

BIOS version: A08 (03/03/2006)
//firmware up to date to last version
CPU Pentium(R) 4 CPU 2.80GHz
memory 1GiB
display VGA compatible controller G86 [GeForce 8400 GS]

[Was_Just19]

Here ye go for comparison

Code: [Select]

$ pwd
/media/LivePCLinuxOS/changes/var/log


$ grep -R error *
dmesg:end_request: I/O error, dev sr0, sector 0
dmesg:end_request: I/O error, dev sr0, sector 0
dmesg:EXT2-fs (sr0): error: unable to read superblock
dmesg:end_request: I/O error, dev sr0, sector 0
dmesg:EXT2-fs (sda2): error: unable to read superblock
dmesg:EXT2-fs (sda6): error: couldn't mount because of unsupported optional features (240)
dmesg:EXT2-fs (sda7): error: couldn't mount because of unsupported optional features (240)
dmesg:EXT2-fs (sdb3): error: unable to read superblock
gdm/:0.log:     (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
gdm/:0.log.1:   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
gdm/:0.log.1:error setting MTRR (base = 0xc0000000, size = 0x0ff00000, type = 1) Invalid argument (22)
Xorg.0.log:     (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Xorg.0.log.old: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
I think that the delay is after the logs have been written.

I would have thought of blaming the writing of the persistence data as the culprit, but the delay is exactly the same even before persistence is used.

Sorry, no ideas ......

regards.

[melodie]

Hi,

I don't get Input/Output errors on /dev/sr0 : what kind of device do you have behind ? Maybe a CD/DVD combo ? SATA or SCSI ? ...

trying to find a clue...

[Was_Just19]

Code: [Select]

dmesg:end_request: I/O error, dev sr0, sector 0
Most likely because there was a blank DVD RW in the drive and the OS could not find any formatting on it.

[melodie]

Code: [Select]

dmesg:end_request: I/O error, dev sr0, sector 0
Most likely because there was a blank DVD RW in the drive and the OS could not find any formatting on it.

What would you think about posting the content of a full dmesg invoked as root right at the end of the boot, before doing anything else ? (even before starting firefox), just incase it would bring an information. This, done without a CD or a DVD in the tray.

[Was_Just19]

I don't know if it is normal or not but what I noticed is that it has difficulties apparently with partitions that are ext3 and ext4 .....

Code: [Select]

EXT2-fs (sda2): error: unable to read superblock
EXT2-fs (sda6): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda7): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda8): warning: mounting ext3 filesystem as ext2
EXT2-fs (sda9): warning: mounting ext3 filesystem as ext2
sda2                 is Swap
sda6 & sda7      are ext4
sda8 & sda9      are ext3

[melodie]

I don't know if it is normal or not but what I noticed is that it has difficulties apparently with partitions that are ext3 and ext4 .....

Code: [Select]

EXT2-fs (sda2): error: unable to read superblock
EXT2-fs (sda6): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda7): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda8): warning: mounting ext3 filesystem as ext2
EXT2-fs (sda9): warning: mounting ext3 filesystem as ext2
sda2                 is Swap
sda6 & sda7      are ext4
sda8 & sda9      are ext3

Hi,

It's interesting, however I would need to know the context : what log file does it come from, with what command did you get it (is it an extract of dmesg ?) and have you indeed obtained it just after a boot of the live ?

[Dragynn]

Hey Melodie, made something for ya 

http://www.pclinuxos.com/forum/index.php/topic,81957.0.html

http://oi52.tinypic.com/23sj3iu.jpg

[melodie]

Hey Melodie, made something for ya 

http://www.pclinuxos.com/forum/index.php/topic,81957.0.html

http://oi52.tinypic.com/23sj3iu.jpg

Oh just great !!! Thank you !

[melodie]

Hi,

I am happy to announce all the new PCLinuxOS Openbox Base version.

http://melodie.tyruiop.org/pclinuxos-core-cli-and-children/

[ ]   pclinuxos-openbox-base-2010.10-finaltests.iso   02-Nov-2010 00:07    266M
[ ]   pclinuxos-openbox-base-2010.10-finaltests.md5sum   02-Nov-2010 00:07    69

The changes are that I deactivated resolvconf as said previously, I re-installed ntfs-3g after I noticed it's necessary to access to ntfs partitions from within PCManFM : but ntfs-config is not necessary : don't configure fstab to mount the partitions, it's done dynamically by gvfs. I tried with fstab, (through ntfs-config) and after the access is all messed up.

I still notice in my main machine that once a while there is problem with access : when so, I check if hal is still running, and alas in theses cases it's not: restarting it from console is the fast solution.
As root:

Code: [Select]

# /etc/init.d/haldaemon restart
In some other distros, hal starts to be replaced by udisk... but for PCLOS, this might not be in near future. (?)

When you will check md5sum, if you run the "md5sum -c" option it won't work. It will work if you rename the 2 files, and remove the "finaltests" from the name.

Thank you and good final testings to all.
Regards,
Mélodie

[Was_Just19]

I don't know if it is normal or not but what I noticed is that it has difficulties apparently with partitions that are ext3 and ext4 .....

Code: [Select]

EXT2-fs (sda2): error: unable to read superblock
EXT2-fs (sda6): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda7): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda8): warning: mounting ext3 filesystem as ext2
EXT2-fs (sda9): warning: mounting ext3 filesystem as ext2
sda2                 is Swap
sda6 & sda7      are ext4
sda8 & sda9      are ext3

Hi,

It's interesting, however I would need to know the context : what log file does it come from, with what command did you get it (is it an extract of dmesg ?) and have you indeed obtained it just after a boot of the live ?

It is from dmesg ...  sorry thought that was obvious .....  and yes from one boot using persistence, with no changes made.

[melodie]

It is from dmesg ...  sorry thought that was obvious .....  and yes from one boot using persistence, with no changes made.

I thought so but I wanted to be sure. Why not a full dmesg next time ?
I have been seeking for clues about the fs type, but didn't find any yet. Been in /usr/share/mylivecd, seen reference to fs types it rc.sysinit, but not in the rc.sysinit which is under /etc/rc.d. Started a Lxde 2010.10 in vbox and compared : it's all the same.

Still no solid clue but as soon as I will find a new idea to dig in I will.

[jlf001]

I am happy to announce all the new PCLinuxOS Openbox Base version.

http://melodie.tyruiop.org/pclinuxos-core-cli-and-children/

[ ]   pclinuxos-openbox-base-2010.10-finaltests.iso   02-Nov-2010 00:07    266M
[ ]   pclinuxos-openbox-base-2010.10-finaltests.md5sum   02-Nov-2010 00:07    69

I'm unable to download it at present.  It looks like the server is down.  I'll try again later.

Jeff