Porteus-v1.1rc2-i486 ready for testing

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Porteus-v1.1rc2-i486 ready for testing

Post#1 by brokenman » 22 Nov 2011, 03:19

Please read the release announcement for further details and post bugs and requests here. This is last release candidate before the official v1.1 release and things are looking quite stable.

As usual please road test and help out with any bug fixes where possible.

If you find a bug, please make sure you have booted to 'always fresh' mode and have no rogue files in your rootcopy folder. If the problem persists then post your question here and a team of highly trained monkeys will be dispatched to look at the problem.

As per usual we will need 'Beny the great' to produce some nvidia modules. Please test the ATI module for me as i am unable to test it on my machine. Also please test the vbox guest addons as i was having troubles getting this to insert (once again).
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Porteus-v1.1rc2-i486 ready for testing

Post#2 by Falcony » 22 Nov 2011, 11:22

Tnks, brockenman,

nice bash shell - liked

regarging bugs -

what i see

please boot up to copy2ram mode(in other modes you 'll not see anything becource booting goes to quick)

I will see at first line upper one error message

"driver/rtc/hctosys.c unable open device (rtc0)"

then system booted ok

other one - warning - when shutdown one last after disk unmounting

"Cannot unmount /mnt/* no such file or directory"

first error maeans somesing wrong with kernel

the second one warning - fantom helps - this is about linuxrc and live script sutdown script

as usial thank you very much!

PS. Not tested PPM yet, but test it later

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v1.1rc2-i486 ready for testing

Post#3 by brokenman » 22 Nov 2011, 13:06

driver/rtc/hctosys.c unable open device (rtc0)
This is a call to the real time clock during boot. /dev/rtc and /sys/class/rtc0 are created so the problem is minimal. I see two possible causes. Either your board is old, or the driver was not functional or did not bind correctly during boot. dmesg or syslog should tell more, look near the start. I will test later to see.
"Cannot unmount /mnt/* no such file or directory"
This is fanthoms world so i am only guessing. Looks to me like a safe call to ensure all is unmounted before shutting down. In your case everything WAS unmounted already hence nothing in /mnt to unmount. Looks fine to me. Thanks.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Porteus-v1.1rc2-i486 ready for testing

Post#4 by Falcony » 22 Nov 2011, 13:38

Either your board is old, or the driver was not functional or did not bind correctly during boot.
no, it is new notebook Toshiba Satellite

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

Re: Porteus-v1.1rc2-i486 ready for testing

Post#5 by fanthom » 22 Nov 2011, 15:19

"driver/rtc/hctosys.c unable open device (rtc0)"
you shouldn't need rtc0 at the very beginning of booting (initrd stage) and this device is created by udev later on (called by rc.S) so no harm at all.
Anyway - kernel help doc says that rtc0 could be helpful for networking (our PXE boot option). dont know the details but i have compiled PC-style 'CMOS' RTC as (*) instead of (M) in 64bit edition.
@brokenman - you may do the same just to shut this warning down and keep the people calm :)
"Cannot unmount /mnt/* no such file or directory"
brokenman is right - this is safe warning as during 'copy2ram' removable media is unmounted during boot (not shutdown) so /mnt/* is empty.
I'll redirect the output to /dev/null for final. didn't do it now as i wanted to know if union and all devices are unmounted properly.
i can observe that sometimes union get's stuck somewhere but can't track what's making it busy.
i'll also tweak cleanup script (from initrd) which gonna inform the user that union was not unmounted properly and running porteus with 'fsck' cheat is recommended for keeping fs consistent.
Please add [Solved] to your thread title if the solution was found.

User avatar
oranus
Contributor
Contributor
Posts: 69
Joined: 25 Aug 2011, 13:46
Location: Turkey

Re: Porteus-v1.1rc2-i486 ready for testing

Post#6 by oranus » 22 Nov 2011, 15:29

Thanks brokenman for rc2

1. The vga-detect cheatcode works very-well on Radeon HD 5400.

2. Porteus pendrive mount with copy2ram and vga-detect cheatcode.

This error occurs copy2ram with vga-detect cheatcode. And couldn't umount pendrive. Without vga-detect cheatcode Porteus pendrive doesn't mount.

Cheers,

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v1.1rc2-i486 ready for testing

Post#7 by brokenman » 22 Nov 2011, 19:06

@ oranus

All credit to fanthom for vga-detect. Great idea

As for your copy2ram cheatcode ... very strange ...

Do you have stuff in your optional folder?

If yes ... can you please try using extramod cheatcode and point it at your 'optional' folder? This will ensure that stuff in optional gets loaded just in case linuxrc is not doing so. I had a quick look through linuxrc but couldn't see ... looks to me like fanthom wrote the script in some strange ancient polish dialect. Damn nice but difficult to follow for me.

:P
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Porteus-v1.1rc2-i486 ready for testing

Post#8 by Falcony » 23 Nov 2011, 07:41

Thanks for explanation, fantom!

if you and brokenmen just redirect this messages to /dev/null it is ok

regarging copy2ram - for me it work well

but i do not tested it together with vga-detect code

Posted after 1 hour 28 minutes 51 second:
Add more one small bug

In previous version of porteus after you press "Print Screen" then KSnapshot appiared with grubbed screeenshot

Now this key doesnt't work

if it easy to fix - please make this fiunction back

it is convinient to get screen in any time

regarging last version of ppm you release yesterday i will post it in ppm thread

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v1.1rc2-i486 ready for testing

Post#9 by brokenman » 23 Nov 2011, 12:27

Can you please run ksnapshot from console and tell me of any errors. It seems to work ok for me.

Also be sure you have no 'function key' activated so printscreen is really being used.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Porteus-v1.1rc2-i486 ready for testing

Post#10 by Falcony » 24 Nov 2011, 05:18

Can you please run ksnapshot from console and tell me of any errors. It seems to work ok for me.
no error
Also be sure you have no 'function key' activated so printscreen is really being used.
How to check binding in Trinity?

I switched to running konsole and pressing several times Print Screen key - it show print ^[[F

xev appication shows me keycode 115 - End key

one other pc the same key shows keycode 111 - Print

I totally confused why it?

Any ideas

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v1.1rc2-i486 ready for testing

Post#11 by brokenman » 24 Nov 2011, 13:20

my xev

Code: Select all

KeyRelease event, serial 34, synthetic NO, window 0x2600001,
    root 0xaa, subw 0x0, time 647204, (-701,-99), root:(308,440),
    state 0x0, keycode 107 (keysym 0xff61, Print), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
In the lmenu go to: Settings/Regional & Accessibility

You can take a look at Input Actions or Keyboard Shortcuts. You have the option to set shortcuts and bind keys here.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Porteus-v1.1rc2-i486 ready for testing

Post#12 by Falcony » 25 Nov 2011, 04:46

ok, thanks

i connected external usb keyboard and it is the same as your post

why keycode is different on notebook keyboard - this is q. to Toshiba L), soory for disturbing

User avatar
oranus
Contributor
Contributor
Posts: 69
Joined: 25 Aug 2011, 13:46
Location: Turkey

Re: Porteus-v1.1rc2-i486 ready for testing

Post#13 by oranus » 25 Nov 2011, 08:48

I test the vga-detect on nVidia:

It recognize driver correctly but :
Sometimes stage at "Triggering udev events:..." it freeze and
sometimes Kde doesn't boot. It freeze on second item of kde "initilazing system services" . It waits aprx 1 min. and kde doesn't start...

Regards

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-v1.1rc2-i486 ready for testing

Post#14 by Ahau » 29 Nov 2011, 16:17

If I boot into LXDE, log out, and then log back in, the panel gets all garbled up (it looks like there is pseudo transparency that is picking up the wrong image(s)?). Restarting the panel clears this up. I haven't done enough digging to figure out exactly why this happens (perhaps the process doesn't get killed on logout to lxdm), but it may be worth adding something to the lxde startup process that checks for a running instance of the panel and restarts it if found.
Please take a look at our online documentation, here. Suggestions are welcome!

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

Re: Porteus-v1.1rc2-i486 ready for testing

Post#15 by fanthom » 29 Nov 2011, 19:56

@Ahau
this is known problem - check KNOWN BUGS in rc1 initial post:
http://porteus.org/forum/viewtopic.php?f=53&t=832
will try to implement your suggestion.
thanks.
Please add [Solved] to your thread title if the solution was found.

Post Reply