kernel compiling in woof-ce

Message

Dry Falls · #496 Post by **Dry Falls** » Fri 27 Apr 2018, 17:52

vis k4.16.3, everyhing works except...

shutdown. This may be the culprit: (line 536 or so)

# CONFIG_NUMA is not set

df

stemsee · #497 Post by **stemsee** » Fri 27 Apr 2018, 19:47

Thanks DF

I respin one now!

stemsee

Dry Falls · #498 Post by **Dry Falls** » Sat 28 Apr 2018, 01:48

np. However, this kernel itself is no good for me. I' running from your configuration now, but I've tried three different compilations and each one throws this error in syslog:

Code: Select all

dbus-daemon[21432]: Cannot setup inotify for '/usr/share/dbus-1/system.d'; error 'Permission denied'

Probably fine for a normal pup, but JL64 has polkit and consolekit2 which are required not only for pulse, but running other DE than openbox or JWM. About 20 fewer processses running.

To make sure it's not just my build environment, I tried under another lighthouse I know to be good. No diff.

Have to put in the aufs tools manually. Acording to the readme in the aufs sources package, this probably is because there isn't a package available as of yet. He says the previous one should be ok.

My problem is the kernel itself. It's like my old bank. They were so paranoid about security, the upgrades prevented even regular users from gaining access to their own accounts. Needless to say, everyone (welll, enough anyway) switched over to the local credit union and that franchise closed down.

Personally, I'm sticking with the less-new-and-improved kernels. Funny, but k4.16.1 didn't have this issue. Of the new batch of kernels, I've had the most luck wirh k4.15.8.

thanks, This is a real learning experience.

df

stemsee · #499 Post by **stemsee** » Sat 28 Apr 2018, 08:07

Thanks for input DF, I will try compiling next one on your jlh.

But for now here is huge k4.16.5-x86_64
https://drive.google.com/open?id=1czFwV ... gYoSbB7wXs

sources
https://drive.google.com/open?id=1rfuJf ... WbJPcq3Hf7

Dry Falls · #500 Post by **Dry Falls** » Sun 29 Apr 2018, 08:09

As near as I can tell, this kernel (> k4.16.2) is, independent of the DOTconfig used, designed for the big boys who don't use busybox (post X) and do use runlevels. Ie, root autologin is taboo. I've seen no documentation, but this is what's happening for me. I think it must be for further security. As well, this kernel doesn't load my usb keyboard but leaves it for xorg/sysinit to do and at shutdown, the late-loaded keyboard is dropped so there is no response available to console dialogs (this is also independent of firmware). A hunch anyway. I think my previous bank anecdote is a spot-on analogy.

df

stemsee · #501 Post by **stemsee** » Sun 29 Apr 2018, 08:13

k4.16.2?

Dry Falls · #502 Post by **Dry Falls** » Sun 29 Apr 2018, 08:21

Peebee used k4.16.2 but I haven't tried it. k4.16.1 worked for me whether I used his configuration or my own. The problem started with k4.16.3, which I tested inside and out and just plain can't get to work. k4.16.5 is behaving the same.

peebee · #503 Post by **peebee** » Sun 29 Apr 2018, 08:39

Dry Falls wrote:Peebee used k4.16.2 but I haven't tried it. k4.16.1 worked for me whether I used his configuration or my own. The problem started with k4.16.3, which I tested inside and out and just plain can't get to work. k4.16.5 is behaving the same.

4.16.5 ok for me.....

Dry Falls · #504 Post by **Dry Falls** » Sun 29 Apr 2018, 21:41

Thanks Peebee. Just downloaded 18.04 with B3 delia and it ships with k4.15.15 (very nice, by the way). Put in Stemsee's k4.16.5 and as you observed, runs well, as it does in Lighthouse --except powerdown which has the same 'lockup' (for lack of a better word) issue. If you compiled a k4.16.5-lxpup64 for your trial, I'd sure like to see your .config file.

Of course, lxpup doesn't use full pulseaudio or consolekit2 so so won't experience the same 'other' issues. I'm going over your .xinitrd now to see if I can change the startup proceedure in JL64.

Again,
thanks!

df

peebee · #505 Post by **peebee** » Sun 29 Apr 2018, 22:21

Basically from Fatdog....remove -false.gz

Dry Falls · #506 Post by **Dry Falls** » Mon 30 Apr 2018, 02:58

Ok, Peebee. That fixed the console-keyboard issue and powerdown works correctly. Still the problem with dbus:

Code: Select all

dbus-daemon[7465]: Cannot setup inotify for '/usr/share/dbus-1/system.d'; error 'Permission denied'

Use alsa mixer which calls up retrovol icon tray and everything looks right.

There are umpteen new variables added building the kernel than your (or my) Dotconfig accommadates. My usuall practice is to accept all defaults. I hate to do it, but will have to track down the unusable features and start over if I'm to use this, and it would seem, any future kernels in JL64.

df

Dry Falls · #507 Post by **Dry Falls** » Tue 01 May 2018, 02:46

Recompiled k4.16.5. All working in both JL64 and lxpup64:

stemsee · #508 Post by **stemsee** » Sat 19 May 2018, 13:17

I got this working, and I have tested it out building x86_64 kernels, 4.16.8. All packages faithfully created. Sources with /lib/modules/(build,source) links; and /usr/include (headers). kernel-modules/lib/modules/ free from build and source links...finally!

aufs-util builds immediately after configuring kernel and creating headers package, recoded and working; when internet connection is likely to be alive.

stemsee · #509 Post by **stemsee** » Sat 19 May 2018, 13:30

If b, is entered at firmware download input then big firmware is downloaded and installed, likewise for s, cut-down firmware is added.

If no entry is made (carraige return) then firmware from the running system will be copied over.

stemsee · #510 Post by **stemsee** » Mon 04 Jun 2018, 11:45

This kernel package contains 4.16.13 - x86_64 sources and huge
Based on easy config.
https://drive.google.com/drive/folders/ ... AP9-sQ1Wre

rockedge · #511 Post by **rockedge** » Mon 04 Jun 2018, 23:11

I have compiled a 4.17 pae enabled kernel but I had to use the aufs=4.16 as the kernel-kit script could not find a version for 4.17

I am about to test it out with a 32bit Bionic build from woof-CE..just waiting for the ISO to finish writing...

peebee · #512 Post by **peebee** » Tue 05 Jun 2018, 08:25

rockedge wrote:I have compiled a 4.17 pae enabled kernel but I had to use the aufs=4.16 as the kernel-kit script could not find a version for 4.17

I am about to test it out with a 32bit Bionic build from woof-CE..just waiting for the ISO to finish writing...

With a new kernel version it is usually best to use the 4.x-rcN aufs branch until the specific branch for the new kernel becomes available.....I've done a 64-bit kernel-kit build in that way.

smokey01 · #513 Post by **smokey01** » Tue 05 Jun 2018, 10:28

rockedge wrote:I have compiled a 4.17 pae enabled kernel but I had to use the aufs=4.16 as the kernel-kit script could not find a version for 4.17

I am about to test it out with a 32bit Bionic build from woof-CE..just waiting for the ISO to finish writing...

I discovered the same problem and did the same as you.

Maybe next time I will try peebee's suggestion and use the 4.x-rcN aufs branch.

rockedge · #514 Post by **rockedge** » Wed 06 Jun 2018, 05:21

I will also try a version with peebee's suggestion...meanwhile I have the finished pup running the 4.17 kernel

peebee · #515 Post by **peebee** » Sun 10 Jun 2018, 22:13

Now available:
https://github.com/sfjro/aufs4-standalone/tree/aufs4.17

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

kernel compiling in woof-ce

run levels