Porteus

Posted: **04 Jan 2016, 02:33**

Great work!!

Posted: **04 Jan 2016, 17:48**

neko wrote:@Ed_P
If you have a chance, please try to convert OK kernel(3.0.1 system) conf to 4.3.3 conf.

Wow!! That's a lot of steps neko.

3. set data
2 partitions are used.

hmmmm

3.1. set manjaro-xfce-15.12-x86_64.iso

Interesting. I haven't worked with anything but Porteus in years. Will be interesting to see what it looks like.

I'm not sure my main problem with Porteus 3.4 is the kernel rather than the DE. Booting with a " 3 " parm works.

Posted: **18 Jan 2016, 01:54**

neko

Does your new kernels follow strictly to the config file from Porteus or have you amended it to allow for more hardware support such as for compiling the new kernel module
mt7601u for mediatek wireless devices?

thanks in advance

Posted: **18 Jan 2016, 04:22**

@aus9
Yes, new kernels are followed almost strictly to the config file from Porteus.
There are 2 reasons.
1. I have few knowledges on linux kernel.
I am afraid to damage something by introduced new kernel functions.
2. I would like to keep the current kernel functional scope and its size.
Introducing new kernel functions might make its size bigger.

The main meaning of introducing these new kernels might be quality-up.

But new functions of a new kernel could be introduced by own build.
Therefor the packages include kernel configuration data
and the build procedure articles are written in this thread.

If you have a good kernel configuration (.config), and it doesn't make its kernel size so much bigger,
would you open it for us ?
(I will try to introduce "mt7601u for mediatek wireless devices" into a kernel at next package release.)

Thanks.

Posted: **18 Jan 2016, 05:22**

@neko

I am afraid to damage something by introduced new kernel functions

very sensible

Introducing new kernel functions might make its size bigger.

agree 100% and to your last question I have compiled my own kernels in the past, when I had time, for purely selfish reasons to limit inbuilt or modules to my hardware.....which won't work for Portesu members.

Therefore I have no configs to share with you at this stage. If I see a security message as I am on a mailing list for "security type things....I will either pm you and/or brokenman/fanthom or more likely post in the security section.

You may be able to tell that I have already posted in the security section on various matters but am not a kernel expert.

Altho I have thanked you on the TP-link post.....once more I hope I have not embarrassed you by saying again
thanks for sharing info about the module mt7601u that is in your recent kernel builds

if interested and I am not trying to spam you ....here is a website that might interest you?

https://www.cvedetails.com/vulnerabilit ... ernel.html

Posted: **23 Jan 2016, 07:59**

upkernel4.4 & upakernel4.4 commands were released.
upkernel4.4 command will update the kernel of "Porteus V3.1 ISO" to kernel 4.4.

Please refer to the top article in this thread.

The new kernel includes the mt7601u driver.
The function 'value' of the script 'functions' in this initrd is corrected the issue that was pointed out by Bogomips.
Bogomips, thank for your point out.

Thanks.

Posted: **23 Jan 2016, 23:56**

@neko
At first I thought it was the new kernel, but now I think my changes got saved on reboot

Code: Select all

guest@porteus:~$ cat /proc/cmdline
quiet from=/tmp/iso/Por-KDE4-v3.1-4.4.1-i486.iso copy2ram ramsize=30% noauto changes=/dev/sda4 changes-ro guiexec=p10/Por/pane.sh timezone=Europe/London volume=40%

8676 blocks
guest@porteus:~/ira$ ls
bin/      etc/       init@      linuxrc*  mnt/     persist   run/  union/
cleanup*  fatal      init_conf  m/        nemesis  porteus/  sys/  usr/
dev/      functions  lib/       memory/   opt/     proc/     tmp/  var/

Logical bug?

Code: Select all

guest@porteus:~/ira$ grep changes-ro functions
param changes-ro
guest@porteus:~/ira$ grep -A 2 changes-ro functions
param changes-ro
PCHANGES_RO=$?
param norootcopy;

guest@porteus:~/ira$ grep -B2 -A5 PCHANGES_RO functions
PCOPY2RAM=$?
param changes-ro
PCHANGES_RO=$?
param norootcopy;
PNOROOTCOPY=$?
param nonetwork;
PNONETWORK=$?
param acct;
--
        if [ "$CHNEXIT" != EXIT ];
        then
                if [ $PCHANGES_RO -ne 0 ]
                then
                        return
                fi
        fi

--
                echo "$CHNEXIT" >/etc/changes-exit
        fi
## At this stage I think PCHANGES_RO can only be zero.
        if [ $PCHANGES_RO -eq 0 ]
        then
                echo $i"""changes will not be saved for this session"""
        else
                echo $i"""changes will be saved only during reboot/shutdown"""
        fi
## Fall through for changes to be saved at reboot (it seems most likely reason)

Posted: **24 Jan 2016, 04:44**

@Bogomips
Excuse me that the tool makes you trouble.
I think that the initrd of the tool has something bug.
Please replace "initrd.xz and kernel-v4.4.1-1-*.sgn" of updated ISO with "initrd.xz and porteus-v3.1-*.sgn" of original ISO.

Thanks.

Posted: **24 Jan 2016, 19:00**

^

Replaced initrd on disk (as boot with Grub Legacy)

Added boot parameter sgnfile:

Code: Select all

quiet from=/tmp/iso/Por-KDE4-v3.1-4.4.1-i486.iso sgnfile=kernel-v4.4.1-1-i486.sgn copy2ram ramsize=30% noauto changes=/dev/sda4 changes-ro

guest@porteus:~$ uname -r
4.4.0-porteus

This seems OK, and changes no longer being saved.

Posted: **28 Jan 2016, 14:02**

@Bogomips
There is a bug in the script 'linuxrc' of my 'initrd.xz'.

Code: Select all

423c423
< 	if [ $PCAHNGES_RO -eq 0 ]
---
> 	if [ $PCHANGES_RO -eq 0 ]

cheatcode 'changes-ro' judgement was not done.

Thank you for your notifying my bug.

@all
If cheatcodes of 'changes and changes-ro' are used on ISO that is updated kernel by this tool,
please replace "initrd.xz and kernel*.sgn" of updated ISO with "initrd.xz and porteus-v3.1-*.sgn" of original ISO.

Thanks.

Posted: **28 Jan 2016, 14:28**

Update Kernel version.

[New tool module]
upkernel-4.3.4-noarch-1.xzm

Please refer to the top article of this thread.

Thanks.

P.S.
upkernel-4.3.4-noarch-1.xzm:
'changes-ro' bug was fixed.

-------------------------------------------------------------------------------
https://www.kernel.org/finger_banner
The latest mainline version of the Linux kernel is: 4.5-rc1
The latest mainline version of the Linux kernel is: 4.4
The latest stable 4.3 version of the Linux kernel is: 4.3.4
The latest longterm 4.1 version of the Linux kernel is: 4.1.16
The latest longterm 3.18 version of the Linux kernel is: 3.18.26
The latest longterm 3.14 version of the Linux kernel is: 3.14.59
The latest longterm 3.12 version of the Linux kernel is: 3.12.53
The latest longterm 3.10 version of the Linux kernel is: 3.10.95
The latest longterm 3.4 version of the Linux kernel is: 3.4.110
The latest longterm 3.2 version of the Linux kernel is: 3.2.76
The latest longterm 2.6.32 version of the Linux kernel is: 2.6.32.69
The latest linux-next version of the Linux kernel is: next-20160128

Posted: **29 Jan 2016, 16:56**

Delete the tool that updates to kernel v4.2.x.
Add the tool that updates to kernel v4.1.x.
Please refer to the top article of this thread.

Thanks.

P.S.
upkernel-4.1.16-noarch-1.xzm:
'changes-ro' bug was fixed.
dose not include the mt7601u driver.

Posted: **05 Feb 2016, 04:32**

Your upkernel 4.4.1 contains /lib/modules/4.4.0-porteus
Is that normal?
I wasn't able to launch DE and on all attempts to "modprobe" got "EXEC format error"
None of the drivers worked...

P.S. Does your kernels have nouveau? I'm just curious.

P.P.S. Can your kernels be used with initrd.xz from porteus 3.1? Probably yes, but I wanted to clarify this. =)

Posted: **05 Feb 2016, 08:38**

@all
upkernel4.1/upakernel4.1 command is updated to v4.1.17.
upkernel4.3/upakernel4.3 command is updated to v4.3.5.

Please refer to the top article of this thread.

Thanks.

----------------------------------------
@Kriss
1. First, excuse me for the mistake of numbering.
I gave the number "4.4.1" to kernel v4.4.
Now, kernel v4.4.1 was released.
So, the problem kernel that you call "4.1.1" is v4.1. (bad #4.4.1).

2. "Your upkernel 4.4.1 contains /lib/modules/4.4.0-porteus
Is that normal?"
Yes, that is normal.

3."I wasn't able to launch DE and on all attempts to "modprobe" got "EXEC format error"
None of the drivers worked"
There might be something wrong in this tool.

4. "Does your kernels have nouveau?"
I do not know on nouveau well.
So, if you know kernel config options on nouveau,
would you tell me the options that insert nouveau into kernel?

5. "Can your kernels be used with initrd.xz from porteus 3.1?"
Yes, it can be used.
Please replace the pair of
ISO@boot/syslinux/initrd.xz
and
ISO@porteus/*.sgn .

6. I have already prepared v3.18.26 and v4.4.1 (real 4.4.1).
But these versions are pending for more testes.
If you give me kernel config parameters,
I will recompile v4.4.1.

Thank you for your report.

Posted: **05 Feb 2016, 11:15**

upkernel/upakernel command is updated to v3.18.26.
upkernel4.4/upakernel4.4 command is updated to v4.4.1.

Please refer to the top article of this thread.

note 1)
There are some instabilities of v3.18.26 in my PC environment.

note 2)
Playing .wmv video was NG at both 32bit/64bit of v4.4.0.
But
It is NG at 32bit of v4.4.1.
It is OK at 64bit of v4.4.1.

note 3)
I feel the sound of v4.4.1 good.
It might be the reason that some sound drivers were added.

Thanks.

Porteus

Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1

Re: Update the kernel of Porteus v3.1