VectorLinux
April 19, 2014, 02:14:09 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: 1 2 3 [4] 5 6 ... 11
  Print  
Author Topic: Backup a custom kernel installation...  (Read 23789 times)
wcs
Packager
Vectorian
****
Posts: 1144


« Reply #45 on: October 19, 2008, 10:25:10 am »

Quote
Yes, please do

Thank you!
Logged
uelsk8s
Administrator
Vectorian
*****
Posts: 2503



« Reply #46 on: October 19, 2008, 10:34:49 am »

I have vmklive installed and a tried a back up, but had the same results as before....\
no *.iso file in /tmp
this is linux-live-debug.log:
Quote
creating empty directory /tmp/initrd_tree_4023
creating directories
creating some essential devices in rootdisk
copying files to the rootdisk
rcopy /lib/modules/2.6.26.6/kernel/fs/aufs /tmp/initrd_tree_4023
What else should I provide?

If you recompiled the kernel it may not work with the vmklive scripts.
Logged
Cariboo
Vectorite
***
Posts: 289



« Reply #47 on: October 19, 2008, 11:43:03 am »

Sorry...as you can see, I just don't get the big picture..... Huh

So the next thing I would have to to is to get the original back as you said earlier:
Quote
new kernel is here: http://vectorlinux.osuosl.org/veclinux-5.9/kernels/kernel-2.6.26.6-i686-1vl59.tlz
modules: http://vectorlinux.osuosl.org/veclinux-5.9/kernels/kernel-modules-2.6.26.6-i686-1vl59.tlz
......
download them, and install them with installpkg.
then run vliloconf you should have a new 2.6.26.6 boot option reboot and let us know if it works there
Logged

Life is full of setbacks; Success is measured by the way you deal with them!
uelsk8s
Administrator
Vectorian
*****
Posts: 2503



« Reply #48 on: October 19, 2008, 11:51:12 am »

Sorry...as you can see, I just don't get the big picture..... Huh

So the next thing I would have to to is to get the original back as you said earlier:
Quote
new kernel is here: http://vectorlinux.osuosl.org/veclinux-5.9/kernels/kernel-2.6.26.6-i686-1vl59.tlz
modules: http://vectorlinux.osuosl.org/veclinux-5.9/kernels/kernel-modules-2.6.26.6-i686-1vl59.tlz
......
download them, and install them with installpkg.
then run vliloconf you should have a new 2.6.26.6 boot option reboot and let us know if it works there
I would remove everything in /usr/src "rm -rf /usr/src/*" and /tmp "rm -rf /tmp/*
then install the kernel and kernel-modules packages run vliloconf and reboot into the 2.6.26.6 kernel.
after that run vmklive
Logged
Masta
Global Moderator
Vectorian
*****
Posts: 725



« Reply #49 on: October 19, 2008, 02:35:46 pm »

what about the symlinks in /boot? shouldn't those be removed as well, or should the package replace them?

Just thought to make sure on this, as he's already having issues compiling and made symlinks (probably) pointing to other file names. Out of experience, I had to remove those too, when recompiling the kernel.
Logged
Cariboo
Vectorite
***
Posts: 289



« Reply #50 on: October 20, 2008, 12:24:27 am »

That's what I did:
Fresh installation from CD (kernel 2.6.22.14)
Install the new kernel and new kernel-modules packages
run vliloconf and reboot into the 2.6.26.6 kernel
run vmklive

An .iso file was generated,
a md5sum was also generated,
the md5sum check was OK.

Before I tried to burn the iso.image I shutdown the Laptop, to check if the SCSI issue was solved with the kernel 2.6.26.6.
It isn't...boot hangs at line "Loading iSCSI transport class v2.0-724"...see HERE
When I checked the source file with "make menuconfig" I found the low level SCSI driver section still activated <*>
Other observations:
setting up modules FAILED
caching fonts FAILED
Xserver doesn't start..
executing 'vxconf' does not work, screen appears with colored narrow vertical stripes
(earlier generated xorg.conf attached)
I need a break...
It's one o'clock am ...I'm getting tired...and  Huh

« Last Edit: October 20, 2008, 01:10:11 am by Cariboo » Logged

Life is full of setbacks; Success is measured by the way you deal with them!
uelsk8s
Administrator
Vectorian
*****
Posts: 2503



« Reply #51 on: October 20, 2008, 06:34:09 am »

ok if I understand what you wrote above you installed 2.6.26.6 kernel then booted using 2.6.26.6 kernel made a livecd with vmklive tried to boot a 2nd time with same 2.6.26.6 kernel and that's when it hung.

Easiest way to proceed is to blacklist or delete the iscsi modules in /lib/modules/2.6.26.6 run depmod -aq then reboot and make a new livecd
Logged
Cariboo
Vectorite
***
Posts: 289



« Reply #52 on: October 20, 2008, 09:57:10 am »

ok ..... tried to boot a 2nd time with same 2.6.26.6 kernel and that's when it hung.
The hang situation arises only if I boot after shutting down (Power OFF).
But anyhow, after all,
I had a good night sleep and I'm going to start the whole procedure once more right now.....
I want to include this procedure:
Quote
delete the iscsi modules in /lib/modules/2.6.26.6 run depmod -aq then reboot and make a new livecd
but I don't know how to find iscsi modules.
If I go to /lib/modules/2.6.26.6 I see:
-Links 'build' and 'source'
-Diectory 'kernel'
-Fles 'modules.alias, -.ccwmap, -.dep, -.ieee1394map, -.inutmap, -.isapnpmap, -.ofmap, -.pcimap, -.seriomap, -,symbols, -.usbmap

Where do I find 'iscsi modules'?
« Last Edit: October 20, 2008, 10:12:58 am by Cariboo » Logged

Life is full of setbacks; Success is measured by the way you deal with them!
uelsk8s
Administrator
Vectorian
*****
Posts: 2503



« Reply #53 on: October 20, 2008, 05:04:10 pm »

sorry I am away from a computer now typing this from my phone
If you run "find /lib/modules/2.6.26.6 -name iscsi*" you should be able to find them
Logged
Cariboo
Vectorite
***
Posts: 289



« Reply #54 on: October 20, 2008, 05:34:45 pm »

sorry I am away from a computer now typing this from my phone
If you run "find /lib/modules/2.6.26.6 -name iscsi*" you should be able to find them
Shocked Autch... surely I know this command....sorry for bothering you with that... Roll Eyes

They are in
Quote
"/lib/modules/2.6.26.6/kernel/drivers/firmware" and "/lib/modules/2.6.26.6/kernel/drivers/scsi"

Local Time: Mon 20 Oct, 18:14 ---> vmklive started!

Local Time: Mon 20 Oct, 21: 52 ---> vmklive finished (after 3hrs38min)
Message before closing the window "VL-build":
Quote
No space left on device, cannot fwrite 32768*1.

Size of /tmp 1.3GB
*.iso file size: 624.94 MB
md5sum not created.
linux-live-debug.log attached.

I'm going to repartition the harddrive and make /tmp size to 2GB. That's all I can get,
and start over again!
« Last Edit: October 20, 2008, 10:09:58 pm by Cariboo » Logged

Life is full of setbacks; Success is measured by the way you deal with them!
Cariboo
Vectorite
***
Posts: 289



« Reply #55 on: October 21, 2008, 09:30:10 am »


ISO file and md5sum created...
Live DVD burned...

First boot from Live DVD starts promising...but then:

Quote
Fatal Error occured - Vector Data not found.
You are maybe using an unsupported boot device (eg. SCSI or old PCMCIA).
Workaround:
Copy the directory vector from your boot device to an IDE/SATA disk, eg. /mnt/hda1/vector or C:\vector. Then try to boot again.
*Something went wrongand we can't continue. This should never happen.
*Please reboot your computer with Ctrl+Alt+Delete...

I do this and the second boot starts...but then:

Quote
Fatal Error occured - Can't find executable chroot command
*Something went wrongand we can't continue. This should never happen.
*Please reboot your computer with Ctrl+Alt+Delete...

Again, I do this and now I get to the same:

Quote
Fatal Error occured - Can't find executable chroot command
*Something went wrongand we can't continue. This should never happen.
*Please reboot your computer with Ctrl+Alt+Delete...

I'm going to try on another computer how  LiveDVD works there!
 
Logged

Life is full of setbacks; Success is measured by the way you deal with them!
Cariboo
Vectorite
***
Posts: 289



« Reply #56 on: October 21, 2008, 11:39:11 am »

LiveDVD not working here either...

The other computer is my AMD64/3000+ desktop with 2GB memory.

The liveDVD starts to boot
Boot screen splash - blue, radiant with globe and VectorLinux text
'Starting udev'. The action bar (or what it is called?) fills up

Case one: There it stops and only a hardware reset helps to get out of it.
Case two: after 'Starting udev' is finished a terminal window opens and shows the same Fatal Error as it showed on
                the Laptop

 Shocked  Huh  Roll Eyes
« Last Edit: October 21, 2008, 07:56:44 pm by Cariboo » Logged

Life is full of setbacks; Success is measured by the way you deal with them!
Masta
Global Moderator
Vectorian
*****
Posts: 725



« Reply #57 on: October 21, 2008, 07:17:32 pm »

Seems like bad burn or corrupt iso created Sad
Logged
Cariboo
Vectorite
***
Posts: 289



« Reply #58 on: October 21, 2008, 07:55:06 pm »

Seems like bad burn or corrupt iso created Sad

How do I know that? I didn't notice any errors during the remaster procedure.
I created a md5sum and compared it with the md5sum created by "vmklive", both where identical.
Then I used k3b to burn and they also build a md5sum... which was identical too Huh
« Last Edit: October 21, 2008, 07:59:14 pm by Cariboo » Logged

Life is full of setbacks; Success is measured by the way you deal with them!
newt
Vectorian
****
Posts: 1132



« Reply #59 on: October 21, 2008, 08:38:43 pm »

I'm just kind of thinking out loud here...

If I've followed this thread correctly, in it's most simplistic form, you are trying to:
1. Install VL Standard 5.9
2. Compile a new, updated kernel without (i)SCSI support
3. Create a remastered CD so you can install later without all the hassle

I'm no developer, or ISO aficionado, but I wonder if you could simply replace the default kernel on the official cd/iso with your updated kernel minus the (i)SCSI support.  Here's what I'm thinking:
-Create a new cd/iso kernel using the config file used to make the default one minus (i)SCSI support; preferably the same version
-Mount the ISO and replace the existing kernel with the new one; preferably named the same - 'sata'
-Burn the new ISO and test

It sounds too easy so most likely I've over-simplified the process but I wonder if this may prove to be a better method since you really are looking to have a remastered, (normal) installable end product.  It seems that a 'live' end product will only lead to more steps once you actually have a live cd working correctly.

HTH!
Logged
Pages: 1 2 3 [4] 5 6 ... 11
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!