Porteus-v1.1rc2-i486 ready for testing

[brokenman]

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.

[Falcony]

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

[oranus]

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

[Ahau]

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.

[fanthom]

@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.

[Ahau]

Damnit, I really need to start re-reading the 'Known Bugs' section before posting bug reports!

[brokenman]

Thanks for the report Oranus. At this stage i would say the vga detect is still experimental so keep posting any issues you have. They will help fanthom to refine the function.

[fanthom]

@oranus
this error could not necessairly be vga-detect related. are you able to recreate it?
if yes then please upload whole content of /var/log/ folder to mediafire (or any other storage site) and i'll check what's causing this.

[Seq_Res]

I downloaded rc2 several times, and md5sum check all said okay; but when run lin_start_here.sh, failed at
the md5sum check stage.

@Ahau,
I tried to fire up V1.0 using V09 syslinux, as you suggested on May 26, but it does not work .
lilo works on this computer, but not on other public ones; I hope Porteus works on them, and
hope also V1.1 may work like bootinst.sh in V09 but not lin_start_here.sh in V1.0.

[Ahau]

@ Seq_Res

RE: booting syslinux -- can you still get V09 running? To try and trace all steps, I'd suggest installing V09 to your drive, and making sure that boots up fine; then change out the kernel and initrd, modify the porteus.cfg (without reinstalling syslinux), and then change out all of your modules. If the syslinux menu still comes up but you Porteus wont boot, then you know the problem is in your config, and you can modify it to point to all of the right places.

RE: failing at the md5 check -- I'm not sure what the problem is here -- try calculating the md5 for the whole ISO and compare that against the md5 posted on the server. If that matches, then double check the path you give to your porteus data during the install process, and make sure it's pointing to the new folders and not any old porteus installation. Also, does the md5sum checker running and reporting that some or all of your modules don't match the expected md5sum, or is the checker failing to run in the first place? If it's failing to run, please tell us the error message, if any, and what operating system you are using while running the install script.

I hope this helps

[brokenman]

You should be able to continue passed the failed md5sum check (in the case that i erred in creating the md5sums). If it is in fact the case that the file is corrupt then you WILL have problems.

In any case without more information it will be difficult to ascertain where things went wrong. I would follow Ahau's advice and start from the ground up. I would also make sure you test one one single linux partition and not have the boot and porteus folders on separate partitions.

Unpack the ISO and do: md5sum vmlinuz
and then check it is: 69d94ff5bb591f81193ccfb9e2b42557

[Seq_Res]

@brokenman,
yes, I did it, with only 2 correct md5sums (vmlinuz and initrd). very nice desktop. thanks.

@Ahau,
like in V1.0, grub in this rc2 does not work universally. It stops at a line of messenge on this computer :
"syslinux 4.04 CHS 0x4e616eb0 ... Peter Anvin et al"

I have functional V09 and .lzm modules in my computer. I can only do some elementary manipulation in linux and
am not sure if I can do as you suggested; before i try, I hope to kwow:
1. after installation, can 000-kernel.lzm in V09 and initrd.lz be substituted by kernel.XZM and initrd.XZ respectively ?
and also all the modules in /base ?
2. how many changes should be made in porteus.cfg ? less than 5 or 10 ?
3. is porteus.cfg is the only config file to be changed ?
thank you very much, Ahau !

[brokenman]

There were MANY changes from v09 to v1+ across many files. It will be difficult to successfully mix files from both versions ... but perhaps there is a way. Most notably the linuxrc file is quite different and the kernel changes were also many. Most notably the change from .lz to .xz. Your initrd must be .lz in v09 and .xz anything above.

[Ahau]

Are you using an HP computer? See this thread for reference: http://forum.porteus.org/viewtopic.php?f=41&t=797

The concept that I have in mind would not involve mixing anywhere except for the bootloader and config file, and it would not require any work in the command line beyond running the installation script. I haven't tested this myself, but will do so in order to refine the process if this doesn't work for you, or isn't clear:

Step 1: Start with a clean drive -- that is to say, remove any Porteus installation that you've previously installed

Step 2: Install Porteus V09 by extracting the ISO image to the drive and running /boot/bootinst.sh

Step 3: Reboot and check that SYSLINUX is properly installed and boots you into Porteus V09 from that drive.

Step 4: Extract the Porteus V1.1 ISO image, but place it in a subdirectory (for now) on the drive, for example, PV1.1
At this point, your directory tree will look like this (where sdXY is your target device, such as sda1 or sdb3):
/mnt/sdXY/boot (boot directory, with kernel and initrd from V09)
/mnt/sdXY/porteus (porteus modules for V09)
/mnt/sdXY/PV1.1/boot (boot directory for V1.1)
/mnt/sdXY/PV1.1/porteus (porteus modules for V1.1)

Step 5: open /mnt/sdXY/boot/porteus.cfg (you can do this with a text editor, such as leafpad or kwrite in GUI mode) and modify the first boot entry (each entry starts with the line "LABEL" and ends with the line "ENDTEXT", so that it reads:

Code: Select all

LABEL xconf
MENU LABEL Graphics mode (KDE)
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.xz vga=791 changes=/porteus/
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT

All you are changing is the APPEND line, to point to initrd.xz instead of initrd.lz, and removing some other stuff (autoexec=, etc., ) which is no longer needed to boot V1.1.

Step 6: Change files over to 1.1: This can be done from the GUI also, using your favorite file manager (in Porteus, it would be konqueror or pcmanfm). Copy the files 'vmlinuz' and 'intird.xz' from /mnt/sdXY/PV1.1/boot/ to /mnt/sdXY/boot/, and delete the 'initrd.lz' that is still there in /mnt/sdXY/boot/. Then, go to /mnt/sdXY/porteus, and delete everything in this directory. Finally, go to /mnt/sdXY/PV1.1/porteus, and copy all files and folders, and paste them into /mnt/sdXY/porteus.

Step 7: Reboot and select the first menu item. This should load the new kernel and initrd.xz that you copied into your /boot/ folder, and those will then load and run all the modules for V1.1.

So, what you are doing is preserving your installation of Syslinux 3.86 and using that to boot all of the files (including the newer kernel and initrd) for V1.1. You should be able to use this method (copy over kernel, initrd, and everything from the /porteus directory, without upgrading/installing the bootloader) to use future releases of Porteus as well.

Please let me know if any of this is unclear or if it doesn't work.

Good luck!

[brokenman]

Some extra advice to add to Ahau's great knowledge.

Exchange your UPPERCASE letters for lower case just in case of fat32 naughtiness. I don't remember if it preserves or not.

Also the linuxrc resides inside the initrd.xz .... and this is where many of the changes i spoke of are happening between 09 and 1.0. caching is one i can think of but prob more. This may well work, and going by Ahau's knowledge of Porteus it probably will!!

I havn't tried it ... but i have reservations. Keep us posted.