Dual boot WindowsXP and VL [SOLVED]

[uelsk8s]

All we are doing is moving a couple of modules.
they will be in /root until we figure out if you need them at all.
there is nothing dangerous about this operation.

[Cariboo]

I moved the files to /root.
No improvement..
After Shutdown and Restart the boot sequence stops/hangs...
Again, after loading Knoppix and then restart from there, everything is fine again....

[uelsk8s]

well then, if your sure the modules were removed from /lib/modules then there is nothing more you can do but compile a custom kernel

[Cariboo]

How can I be sure? I tried to find them but I always get this:

vector:/~
root:# find /lib/modules/ -name *iscsi*
find: paths must precede expression
Usage: find [-H] [-L] [-P] [path...] [expression]
vector:/~
root:# find /root -name *iscsi*
find: paths must precede expression
Usage: find [-H] [-L] [-P] [path...] [expression]

I absolutely don't know how to compile a kernel....
can you tell me what I would have to do?

[uelsk8s]

The easiest and best path for you, and anyone that runs into this in the future would be to remove the modules, if that will work.
so try this first.

Code: [Select]

ls /lib/modulesif that shows either the iscsi_tcp.ko or libiscsi.ko then delete them
then try

Code: [Select]

ls /lib/modules/2.6.22.14/kernel/drivers/scsi/and if that shows either the iscsi_tcp.ko or libiscsi.ko then delete them
then run

Code: [Select]

depmod -aqand reboot

If that works, then great, if not post back the output of lsmod there and well work on walking you through building a kernel

[Cariboo]

Here is the output of the two list commands.

r

oot:# ls /lib/modules
2.6.22.14/
vector:/~
root:# ls /lib/modules/2.6.22.14/kernel/drivers/scsi/
ch.ko  ide-scsi.ko  imm.ko  osst.ko  pcmcia/  ppa.ko  scsi_wait_scan.ko  st.ko
vector:/~
root:#

I had nothing to delete, right?

so I ran "depmod -aq" and rebooted.

Then came the 'shutdown'  test....
and boot stops at line "Loading....", boot from a Knoppix CD, restart,
....and here we are again!

This is the output of lsmod:

vector:/~
root:# lsmod
Module                  Size  Used by
freq_table              4768  0
lp                     10888  0
parport_pc             37092  1
parport                32072  2 lp,parport_pc
i915                   23296  0
drm                    74388  1 i915
snd_seq_dummy           3716  0
snd_seq_oss            32128  0
snd_seq_midi_event      7168  1 snd_seq_oss
snd_seq                48720  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          7692  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            38048  0
snd_mixer_oss          15232  1 snd_pcm_oss
snd_intel8x0           29980  2
snd_ac97_codec         98084  1 snd_intel8x0
ac97_bus                2944  1 snd_ac97_codec
snd_pcm                69764  3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer              19972  2 snd_seq,snd_pcm
snd                    45796  14 snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore               7008  1 snd
snd_page_alloc          8712  2 snd_intel8x0,snd_pcm
martian_dev            17940  0
serio_raw               6276  0
intel_agp              22164  1
agpgart                28108  3 drm,intel_agp
iTCO_wdt                9640  0
i2c_i801                8592  0
shpchp                 30228  0
i2c_i810                5380  0
i2c_algo_bit            6532  1 i2c_i810
pci_hotplug            28616  1 shpchp
i2c_core               20992  3 i2c_i801,i2c_i810,i2c_algo_bit
evdev                   8704  0
vector:/~

BTW, I want to say, thank you, for the support...

[Cariboo]

If that works, then great, if not post back the output of lsmod there and well work on walking you through building a kernel

Hi Uelsk8s,
I did some reading about kernel compilation...it's obviously part of daily Linux life...
I'm kind of ready to go..but I still have no idea what I would have to do...
Are you still working on my issue?

[uelsk8s]

Sorry, I must have missed your last post.

first thing I am going to have you do is get the kernel source from here: http://vectorlinux.osuosl.org/veclinux-5.9/kernels/kernel-src-2.6.22.19-i586-1vl59.tlz
(It solves some security issues, remains compatible, and will be easy to distinguish from your default kernel)

frst su to root then
install it with "installpkg kernel-src-2.6.22.19-i586-1vl59.tlz" in the same dir you downloaded it into

then change into the kernel source directory "cd /usr/src/linux-2.6.22.19" and run "make menuconfig"
that will get you a menu that looks like this


choose the device drivers menu and then scroll down to this section


uncheck it so it looks like this


push the up arrow then enter to get into the scsi device menu
and choose the scsi low level drivers menu shown here


remove the M or * from all the drivers in this section so it looks like this


then exit out till it asks if you want to save


after saving run "make && make modules_install"

when that completes (could be hours later)
copy the kernel to /boot "cp arch/i386/boot/bzimage /boot/vmlinuz-2.6.22.19"

then run vliloconf and you should see an additional kernel selection
reboot and choose it

let us know how it goes,
Uelsk8s

[nightflier]

Now that is support, you couldn't buy that kind of service! 

Uelsk8s post could be made into a nice howto.

[fuelinux]

Now that is support, you couldn't buy that kind of service! 

Uelsk8s post could be made into a nice howto.

+1

Indeed, it HAS TO be made into the HowTo

[Cariboo]

............
when that completes (could be hours later)
copy the kernel to /boot "cp arch/i386/boot/bzimage /boot/vmli
nuz-2.6.22.19"
 
Let us know how it goes,
Uelsk8s

Hi Uelsk8s,
 Sorry for answering so late but I got stuck.......
I tried several times following your very clear instructions and all went well and without any noticeable warnings or errors until I came to the "copy the kernel to /boot" instruction. Here i got the message:

cp: cannot stat `arch/i386/boot/bzimage': No such file or directory

I'll post the root terminal outputs after each step as screenshots HERE.
What other info would you need to track the proplem?

[uelsk8s]

sorry for the typo
the command is

cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.22.19

[Cariboo]

sorry for the typo
the command is
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.22.19

Small things huge I(mpact), it's OK, although it cost me some nerves....
Now /boot looks like this:

vector://usr/src/linux-2.6.22.19
root:# cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.22.19
vector://usr/src/linux-2.6.22.19
root:# cd /boot
vector://boot
root:# ls -l
total 8996
lrwxrwxrwx 1 root root      37 2008-05-04 15:19 README.initrd -> /usr/doc/mkinitrd-1.1.2/README.initrd
lrwxrwxrwx 1 root root      20 2008-05-04 15:19 System.map -> System.map-2.6.22.14
-rw-r--r-- 1 root root 1183469 2007-11-26 02:28 System.map-2.6.22.14
drwxr-xr-x 2 root root    4096 2007-10-31 04:25 bitmap/
-rw-r--r-- 1 root root     512 2008-05-04 15:47 boot.0300
-rw-r--r-- 1 root root     193 2005-01-22 23:37 boot.label
lrwxrwxrwx 1 root root      16 2008-05-04 15:19 config -> config-2.6.22.14
-rw-r--r-- 1 root root   68615 2007-11-26 02:28 config-2.6.22.14
drwxr-xr-x 2 root root    4096 2007-10-02 03:00 grub/
-rw-r--r-- 1 root root  210922 2007-11-13 17:59 initrd
-rw------- 1 root root  333312 2008-05-04 15:47 map
drwxr-xr-x 2 root root    4096 2008-05-04 15:47 tamu/
lrwxrwxrwx 1 root root      17 2008-05-04 15:19 vmlinuz -> vmlinuz-2.6.22.14
-rw-r--r-- 1 root root 4158168 2007-11-26 02:28 vmlinuz-2.6.22.14
-rw-r--r-- 1 root root 3200856 2008-05-18 15:21 vmlinuz-2.6.22.19
vector://boot

Three questions:
1) What is the command line for lilo.config?
2) Do I have to change mod for the new kernel?
3) If it works, how can I replace vmlinuz ->vmlinuz-2.6.22.14 with vmlinuz -> vmlinuz-2.6.22.19?

[uelsk8s]

Three questions:
1) What is the command line for lilo.config?
 vliloconf is the vector linux lilo config utility
2) Do I have to change mod for the new kernel?
 modules? not sure what your asking here, but you built and installed modules for the new kernel above
3) If it works, how can I replace vmlinuz ->vmlinuz-2.6.22.14 with vmlinuz -> vmlinuz-2.6.22.19?
 vliloconf will add a boot option for both kernels so all you have to do is choose the one you want to use at each boot.
If you want to remove the 2.6.22.14 kernel just run removepkg kernel and removepkg kernel-modules
then symllink the new kernel "ln -s /boot/vmlinuz-2.6.22.19 /boot/vmlinuz
and run vliloconf again to update lilo

[Cariboo]

After running 'vliloconf' this is the etc/lilo.conf file.
two things are missing:
1) image for WindowsP on hda1
2) image for new kernel on hda5
although I check marked both in the config menu.

/etc/lilo.conf

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
default = linux
compact
prompt
timeout = 100
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
bitmap = /boot/bitmap/boot.bmp
# VESA framebuffer console @ bootsplash-high
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769


# End LILO global section
# Partition 1: Linux GUI mode
image = /boot/vmlinuz
    root = /dev/hda5
    label = linux
    append = "splash=silent "
    read-only
    initrd = /boot/initrd
# Partition 2: Linux TUI mode
image = /boot/vmlinuz
    root = /dev/hda5
    label = linux-tui
    append = "2 splash=silent "
    read-only
    initrd = /boot/initrd
# Partition 3: Linux GUI mode
image = /boot/vmlinuz
    root = /dev/hda5
    label = linux-gui
    append = "4 splash=silent "
    read-only
    initrd = /boot/initrd

See HERE the vliloconf screenshots