Here is the latest. 'make olddefconfig' resorts to arch/x86/configs/* for a default config so I needed the script to copy the DDOTconfigs there too so as not to get a prompt.
DOTconfigs now up to date with 3.18.3 features. The no-pae config, no-smp, 4g, 300mhz, i486.
pae and x86_64 smp=8cpus, 1000mhz, i686.
I am running the script now.
kernel compiling in woof-ce
-
stemsee
OK test run reached end of first compile then tried to move non-existing file (renamed) then exited code 1.
Two bugs squashed. Script should work as expected.
To Do: Re-enable user interaction when desiring to build only one or two, not three kernels. And 'make menuconfig' real option so as to update configs (consecutively pre-compile).
Two bugs squashed. Script should work as expected.
To Do: Re-enable user interaction when desiring to build only one or two, not three kernels. And 'make menuconfig' real option so as to update configs (consecutively pre-compile).
- Attachments
-
- unattended-kernel-kit.zip
- (119.5 KiB) Downloaded 709 times
-
stemsee
Uh oh!
Found another bug which prevented the script continuing. Same one as before which I thought I fixed - apparently not. But it is now!!
Found another bug which prevented the script continuing. Same one as before which I thought I fixed - apparently not. But it is now!!
- Attachments
-
- unattended-kernel-kit.zip
- (119.5 KiB) Downloaded 698 times
Hi, @stemsee
First I want to appologize for the stand I took on you last time I posted to you ! Due to my ignorance , I missunderstood your good advice about solving hardware related problems I have and building a specific kernel with the necessary modules. I should simply have said I lack skills to achieve that .Reading more on old posts about Puppy , helped me understand a little more what's going on until the desktop shows up.
About your kernel-kit . I gave it a go on your Emsee V2.3-Cafe Editon 64bit. It took a little less than 10 minutes to complete .798 MB built.
Then I tried it on Fatdog630 editing very little of the config files .It took a little more than 10 minutes . 832 MB built. For this last try I attached the build log .
I don't know if these builds are working , it's early for me to implement them - need more study first .
First I want to appologize for the stand I took on you last time I posted to you ! Due to my ignorance , I missunderstood your good advice about solving hardware related problems I have and building a specific kernel with the necessary modules. I should simply have said I lack skills to achieve that .Reading more on old posts about Puppy , helped me understand a little more what's going on until the desktop shows up.
About your kernel-kit . I gave it a go on your Emsee V2.3-Cafe Editon 64bit. It took a little less than 10 minutes to complete .798 MB built.
Then I tried it on Fatdog630 editing very little of the config files .It took a little more than 10 minutes . 832 MB built. For this last try I attached the build log .
I don't know if these builds are working , it's early for me to implement them - need more study first .
- Attachments
-
- k_kit_log.tar.gz
- (149.3 KiB) Downloaded 686 times
-
stemsee
Hi Gobbi
We are people, fallible, impatient, lacking knowledge and experience! Learning from mistakes is our second best chance, being perfectly obedient and not making mistakes is too difficult for most of us - look at Adam!!
Here is the latest unattended-kernel-kit. With a few more 'bugs' sorted out. This should be much improved. It should take at least two hours on a newer machine; even three to four hours is not unexpected, as three kernels are being built consecutively, not in parallel.
So you can safely assume that you didn't have a successful build even of the first kernel, maybe only the kernel-headers package!
Anyway, disregard previous ubuild.sh and replace with this one. If you have already downloaded the kernel source.tar.xz it should use it without re-downloading. Make sure /tmp/64 and /tmp/32-pae and /tmp/32-nopae are deleted if you didn't restart your machine first.
We are people, fallible, impatient, lacking knowledge and experience! Learning from mistakes is our second best chance, being perfectly obedient and not making mistakes is too difficult for most of us - look at Adam!!
Here is the latest unattended-kernel-kit. With a few more 'bugs' sorted out. This should be much improved. It should take at least two hours on a newer machine; even three to four hours is not unexpected, as three kernels are being built consecutively, not in parallel.
So you can safely assume that you didn't have a successful build even of the first kernel, maybe only the kernel-headers package!
Anyway, disregard previous ubuild.sh and replace with this one. If you have already downloaded the kernel source.tar.xz it should use it without re-downloading. Make sure /tmp/64 and /tmp/32-pae and /tmp/32-nopae are deleted if you didn't restart your machine first.
- Attachments
-
- unattended-kernel-kit.zip
- (120.12 KiB) Downloaded 720 times
PXE booted (RAM) a slacko 5.3.3 variant, downloaded the tar file and extracted. Created a /DV directory and copied devx sfs to that and loaded that sfs. Ran the ubuild.sh script and around 1 minute later after pages and pages of text.
No idea what I'm doing and appreciate that you should be running using a full installed version of puppy etc - but may be of some interest/purpose (some feedback better than nowt).
No idea what I'm doing and appreciate that you should be running using a full installed version of puppy etc - but may be of some interest/purpose (some feedback better than nowt).
- Attachments
-
- dt.jpg
- (72.11 KiB) Downloaded 953 times
You uploaded another as I was posting. For info: downloaded that latest version and ran and similar sort of thing, downloads sources, cofigures ok, headers, pages of stuff and same error/fail point.
Quad with 4GB ram.
Redirected output to file and error messages shown (starting from around half way down)
Quad with 4GB ram.
Redirected output to file and error messages shown (starting from around half way down)
- Attachments
-
- dt2.jpg
- (80.75 KiB) Downloaded 948 times
Last edited by rufwoof on Sun 25 Jan 2015, 16:43, edited 1 time in total.
-
stemsee
hi rufwoof
I think the problem is that in order to build a 64bit kernel (the first third of the script is for building a 64bit kernel) you need to be running on a 64bit distro/machine!
To get around this create the file '/tmp/64' and directory distro/packages64 then the script will build the next two kernels 32bit-pae and 32bit-nopae. If that doesn't work it will take me some time to research the errors.
regards
stemsee
I think the problem is that in order to build a 64bit kernel (the first third of the script is for building a 64bit kernel) you need to be running on a 64bit distro/machine!
To get around this create the file '/tmp/64' and directory distro/packages64 then the script will build the next two kernels 32bit-pae and 32bit-nopae. If that doesn't work it will take me some time to research the errors.
regards
stemsee
Using a 64 bit machine, but running a 32 bit puppy (slacko 5.3.3) and its corresponding devx sfs. I'll give your suggestion a go.......stemsee wrote:hi rufwoof
I think the problem is that in order to build a 64bit kernel (the first third of the script is for building a 64bit kernel) you need to be running on a 64bit distro/machine!
To get around this create the file '/tmp/64' and directory distro/packages64 then the script will build the next two kernels 32bit-pae and 32bit-nopae. If that doesn't work it will take me some time to research the errors.
regards
stemsee
Nope.
Deleted, clean reinstalled your tar, created those directories and
- Attachments
-
- dt3.jpg
- (49.71 KiB) Downloaded 935 times
-
stemsee
I see ... so it downloaded the kernel source to dist/sources/vanilla/*.tar.xz is there already an aufs package there? Delete it. Or in build32-pae.conf line 32-33 comment out 32 and uncomment 33 for a different server for aufs.
I cannot so far replicate your error, it may be a connection or server related error. However I did find another bug after running the last script!
So here is yet another update.
I cannot so far replicate your error, it may be a connection or server related error. However I did find another bug after running the last script!
So here is yet another update.
- Attachments
-
- unattended-kernel-kit.zip
- (120.13 KiB) Downloaded 666 times
-
stemsee
Still seeing the same on a different machine, with that most recent copy of the tar file, and with your suggested changes. Otherwise not changing anything - just running the extracted files as-is.
Running with sh -x ./ubuild.sh - see attached image
I suspect its because I'm running in ram (frugal) rather than against a full install - but that's just a pure guess.
Running with sh -x ./ubuild.sh - see attached image
I suspect its because I'm running in ram (frugal) rather than against a full install - but that's just a pure guess.
- Attachments
-
- s1.jpg
- (113.4 KiB) Downloaded 910 times
-
stemsee
You are running in ram? Where was the kernel kit extracted to?? Mine is on a roomy usb drive. Extracted sources use about 700mb of disk space, plus the 105mb compressed kernel source download, plus aufs tools, etc, I am guessing you will need about 1.2GB dis/ram space (conservatively) on top of other usage.
However to check this kit I will boot without a savefile and leave it on compiling overnight to see if any problems arise in a pristine environment.
However to check this kit I will boot without a savefile and leave it on compiling overnight to see if any problems arise in a pristine environment.
- Attachments
-
- capture24759.jpg
- (21.75 KiB) Downloaded 881 times
-
- capture22851.jpg
- (35.61 KiB) Downloaded 908 times
-
- capture22860.jpg
- (22.65 KiB) Downloaded 902 times
-
- capture22083.jpg
- (16.58 KiB) Downloaded 907 times
Oooerr - not sure, I just installed/ran it all in/from / (ram space) with no HDD's mounted (frugal boot not full installed). I created a /DV directory and dropped the DEVX sfs into that and sfs_loaded with no copy. Downloaded your tar file to / and also extracted it to there.You are running in ram? Where was the kernel kit extracted to??
The space available icon in my tray indicates 148GB - so enough space there as being a frugal boot that indicates ram space not disk space.
I did swap out the slacko 5.3.3 kernel 3.01 for a 3.10 one as the former was non-PAE whilst the latter is PAE
50Mbit internet connect speed so usually there's no problems with downloading larger files, often I run puppy from the cloud (download a 500MB 'office' sfs from my google drive that supplements a PXE booted 100MB basic/core puppy).
I guess I should do a full install of FatDog or 64 Lighthouse and test using that as that's the more formal/usual/correct way as I understand it.
Downloaded FatDog 7beta2 to my old dog, extracted out of the iso the initrd and vmlinuz files and dropped them into my tftpboot (PXE) directory and fired up the PXE server.
On another more powerful PC (my son's Windows box), booted, F12 to net boot and PXE booted fatdog. Used that session to download fatdog's devx and your tar files. Copied devx to a new /DV directory and sfs loaded that. Extracted your tar file and terminal, #./ubuild.sh ..... and its whirring away ... pages of stuff whizzing by - that looks something like a lot of CC'ing and pruning. All four cores running at 100%.
Started that off at 10pm, so probably wont see it run all the way through but looking promising.
EDIT: 10:25pm, still whirring away. Off to bed for a early morning start, powered down the PC's - my guess is that it would have run through to completion OK.
On another more powerful PC (my son's Windows box), booted, F12 to net boot and PXE booted fatdog. Used that session to download fatdog's devx and your tar files. Copied devx to a new /DV directory and sfs loaded that. Extracted your tar file and terminal, #./ubuild.sh ..... and its whirring away ... pages of stuff whizzing by - that looks something like a lot of CC'ing and pruning. All four cores running at 100%.
Started that off at 10pm, so probably wont see it run all the way through but looking promising.
EDIT: 10:25pm, still whirring away. Off to bed for a early morning start, powered down the PC's - my guess is that it would have run through to completion OK.
Extracted Fatdog vmlinuz and initrd from its ISO, dropped those into a PXE server and booted that FatDog on a 4 core, 4GB ram Windows PC. Downloaded and sfs_loaded FatDog's DEVX sfs
Copied the unattended build tar file from this posing http://www.murga-linux.com/puppy/viewto ... 783#823783 to / and extracted. i.e. fatdog running in ram with no HD drives mounted
Plugged in a USB HDD and dragged the / copy of the unattended directory over to that (moved) and then dragged back again and created a symbolic link
Opened a terminal, cd to that /unattended.. directory and ran
#./ubuild.sh
All whirring away. Will progress update later.
This is all new to me so I've no idea what to expect or what/where the final output/files from a successful run might be. No changes were made to configs/scripts - all just run as-is. Guessing that they'll be some vmlinuz files for the three (64, 32-PAE, 32-nonPAE) builds, my intent is to drop one of those into a PXE server, boot to command prompt and see if that works.
Copied the unattended build tar file from this posing http://www.murga-linux.com/puppy/viewto ... 783#823783 to / and extracted. i.e. fatdog running in ram with no HD drives mounted
Plugged in a USB HDD and dragged the / copy of the unattended directory over to that (moved) and then dragged back again and created a symbolic link
Opened a terminal, cd to that /unattended.. directory and ran
#./ubuild.sh
All whirring away. Will progress update later.
This is all new to me so I've no idea what to expect or what/where the final output/files from a successful run might be. No changes were made to configs/scripts - all just run as-is. Guessing that they'll be some vmlinuz files for the three (64, 32-PAE, 32-nonPAE) builds, my intent is to drop one of those into a PXE server, boot to command prompt and see if that works.
-
stemsee
Your leading the blind in my case. For instance I've no idea what you were saying in http://murga-linux.com/puppy/viewtopic. ... 914#812914 and whether I should have downloaded something (DOT) or whether its ok to just run everything as is - as I'm doing.You can see how devs use a lot of time trying to figure out what a remote system's problem is ... so I often say the script is working for me.
Nor do I have a clue where any of the final file(s) might be i.e
Just hope that whatever I do/highlight is of some help/use to you. Don't want to be a burden so if you feel the noob is getting in the way just say so - I wouldn't be offended.There is a bug ...'conf' is missing from one place which means kernel number 3 -nopae will be pae.
After around a hour of running (and still going) I'm seeing a dist directory filling up with some directories/files as per the attached, which to me implies that its running ok
- Attachments
-
- 1hr.jpg
- (30.6 KiB) Downloaded 1067 times