Closed mrfricks closed 7 years ago
unable to reproduce, send me a pm with a link to the iso
or better yet, post it here and make sure to delete it in about 2 days.
Hi mrfricks! I had the same issue with "testing" branch, in both slacko and devuan. It seems to be fixed in the "rationalise" branch though. :)
thou shalt update
apparently commit https://github.com/puppylinux-woof-CE/woof-CE/commit/587f35d62d8bbae3f05be5779452c687125e4048 (7 aug) fixed several issues
and it seems that in fact there is an extra done message, but (at least on my pc) it goes unnoticed because things happen so fast..
commit https://github.com/puppylinux-woof-CE/woof-CE/commit/ee35e3c73aa7726f05f4c3e75b43202a7e650cbc should remove that extra done message, but i'm not sure.. have to reboot.
ninaholic thanks for the info, i'll give a try.
wdlkmpx the 'done' is still there for me..... i've uploaded a new iso built with the latest testing . http://distro.ibiblio.org/puppylinux/test/xenialpup/xenial-7.0.3.iso
yes i can see it. it only appaers when i restart x. i'll try to figure out why...
well, for xenial, you might want to use DOTconfig-4.4.17-i686-pae
i enabled random modules that looked interesting. the generated modules will be about 17-24MB xz compressed according to my projections. i remember enabling UEFI support following the Arch LInux wiki months ago..
so as a test build that will actually work in most cases so you don't to figure out what enable... this is ok.
hi wdlkmpx,
there were problems for me with your new DOTconfig. when booting at 'searching for puppy files' i get ..pausing...pausing...pausing ... and X doesn't start.
the kernel/firmware combination is all that's holding xenial up..(apart from a few small things) it was pretty much ready over 2months ago . to be honest the 4* kernels have been a real headache! they'll work on one machine, not work on another and freeze on yet another. 4.4 and 4.6 freeze on my desktop , 4.4 freezes on my netbook, so i'm giving 4.7 a try and if that's problematic i'll stick with 4.1 as that has been the least problematic.
BTW i see that gyrog has fixed the errant 'done' in rationalise... can it be merged into testing?
post a link to your latest iso here or send me a pm (and delete the file in about 2 days), i'd like to test it..
From what i read on the forum.. I get it now
Well, you should release a new tahrpup version, 7.0 with kernel 3.14.x .. that's what they want.
I haven't compile a 3.14 kernel in a while, but i think i enabled more stuff since then. It appears the config for kernel 4.4 is buggy or something according to what mrfrcisk previously said in this issue.. i haven't compiled myself. But xenial is indeed a challenge with newer kernels, according to him anyway, maybe systemd is finally interfering?
Although producing a fairly small kernels+firmware without people complaining is not possible anymore, but a few firmware megabytes can be removed if we look with clinical eyes in a per kernel basis..
I used the xenial x86 configs for debian stretch, i deleted about 350 entries (and edited all the rest).. and plan to delete some more.
But i think i identified some issues, these entries should be deleted:
yes|xf86-video-nv||exe,dev,doc,nls| #ubuntu no longer has this. yes|xf86-input-keyboard||exe,dev,doc,nls| #ubuntu no longer has this. yes|xf86-input-mouse||exe,dev,doc,nls| #ubuntu no longer has this.
in xserver_xorg, this makes more sense: xserver-xorg-input-*
Do you want me to fix it for you?
there are also random packages that just seem odd: 'momanager', etc. other packages that are up to date in noarch, but hardcoded for tahr, etc. etc. etc.
reopen as needed
when puppy loads we get a green 'done' after each section of loading. one of these dones is hanging around and reappears at the top of the screen momentarily when X starts... even sometimes appearing after the desktop has appeared.
i initially thought it was a bug in xenial but i've just done a tahrpup64 build and it's there as well.