Page 4 of 4 FirstFirst ... 234
Results 31 to 39 of 39

Thread: BackTrack 4 Pre Final Kernel Update

  1. #31
    Just burned his ISO
    Join Date
    Oct 2009
    Posts
    1

    Default Hi to all!

    I'm a new in BT that why I'm looking for a little help... I'm sure that somebody can help me. Don't forget that everybody was a beginner once. All the problems until now I took care myself reading the forum, but now I'm stuck. I'm trying to update the kernel to version 2.6.30.5. Everything is going perfectly until I receive an error message "Memory Low" and the process stops. I used first a 4GB USB Memory and I thought the memory stick is full, and I changed with another one of 16GB. But the same problem. In this case I think, the problem is my RAM . How can I fix it? Is it any solution or any script to create the "VAR" folder on the stick and not in RAM? I know that maybe I'm looking like a stupid, but I didn't work with Linux. Only with Windows until now. Thank's to all great peoples which are creating every day great programs like this. Sorry for my imperfect English... and thank's in advance for your help!

  2. #32
    Just burned his ISO
    Join Date
    Jan 2010
    Posts
    5

    Default

    I tried to update kernel to 2.6.30.5
    after I execute the command
    dpkg -i –force all linux-image-2.6.30.5_2.6.30.5-10.00.Custom_i386.deb

    An Errors showed up

    Code:
    root@awa-desktop:~# (Reading database ... 217862 files and directories currently installed.)
    bash: Reading: command not found
    root@awa-desktop:~# Unpacking linux-image-2.6.30.5 (from .../linux-image-2.6.30.5_2.6.30.5-10.00.Custom_i386.deb) ...
    bash: syntax error near unexpected token `('
    root@awa-desktop:~# Done.
    bash: Done.: command not found
    root@awa-desktop:~# dpkg: error processing /root/linux-image-2.6.30.5_2.6.30.5-10.00.Custom_i386.deb (--install):
    bash: syntax error near unexpected token `('
    root@awa-desktop:~#  trying to overwrite `/lib/firmware/whiteheat.fw', which is also in package linux-image-2.6.29.4
    > Running postrm hook script /sbin/update-grub.
    > Searching for GRUB installation directory ... found: /boot/grub
    > Searching for default file ... found: /boot/grub/default
    > Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
    > Searching for splash image ... found: /boot/grub/splash.xpm.gz
    > Found kernel: /boot/vmlinuz-2.6.29.4
    > Found kernel: /boot/memtest86+.bin
    > Updating /boot/grub/menu.lst ... done
    >
    > Errors were encountered while processing:
    >  /root/linux-image-2.6.30.5_2.6.30.5-10.00.Custom_i386.deb

  3. #33
    Just burned his ISO Nokii's Avatar
    Join Date
    Sep 2008
    Posts
    17

    Thumbs up BT4 in VMWare (with VMWare USB Install too)

    Quote Originally Posted by 5p4wn View Post
    Not working for me.

    I have a BT4 running in a vmware machine, after I did this kernel update following the steps in the blog, the machine has been having slow downs, the mouse pointer moves too slow and I can't type neither.

    Any help?

    I did this:

    xxxx:// xxx.offensive-security.com/videos/backtrack-security-training-video/up-and-running-backtrack.html


    then this, to repair Postgresql and update everything:

    xxxx:// longjidin.wordpress.com/2009/10/03/error-with-postgresql-in-backtrack-4-pre-final/

    (with these mods)

    cd /etc/ssl/certs/
    make-ssl-cert generate-default-snakeoil -force-overwrite
    apt-get update
    apt-get install -d linux-image
    cd /var/cache/apt/archives/
    cp -R --preserve=all /lib/modules/2.6.30.7/kernel /lib/modules/2.6.30.7/kernel.old
    dpkg -i --force all linux-image-2.6.30.7_2.6.30.7-10.00.Custom_i386.deb
    apt-get dist-upgrade
    apt-get install madwifi-drivers
    reboot
    fix-splash


    Now I used VMWare's "Install VMWare Tools" (Ver.: 7.8.6 build-185404) to mount the CD and copied the .tar.gz file.


    tar -xzf VMwareTools-7.8.6-185404.tar.gz
    cd vmware-tools-distrib/
    ./vmware-install.pl
    /usr/bin/vmware-user
    exit


    Everything seems to work fine for me ...

    PS: Hate the Grub Bootscreen since the selected line is not highlited.

    Nokii

  4. #34
    Just burned his ISO
    Join Date
    Jun 2009
    Posts
    19

    Default VMware installation in bt4 pre-final kernel 2.6.30.7 problem

    Hello,
    @Nokii, thanks for the write up.
    It works for me.

    However,my VMware seems doesn`t work.. It complains about not having kernel headers. So I follow a tutorial from here ...

    hxxp://forums.remote-exploit.org/backtrack-4-howto/26710-howto-make-vmtools-autofit-guest-work-new-kernel.html

    until I got "VMware Blocking Filesysytem" not working

    After following the Nokii`s solution, I did the following:
    Code:
    apt-get install linux-source-2.6.30.7
    cd /usr/src/
    tar jxvf /usr/src/linux-source-2.6.30.7.tar.bz2
    rm -f /usr/src/linux
    ln -s /usr/src/linux-source-2.6.30.7 /usr/src/linux
    
    cd /usr/src/linux
    zcat /proc/config.gz > .config
    make scripts
    make bzImage
    ln -s /usr/src/linux /lib/modules/2.6.30.7/build
    
    #I also did:
    
    cd linux-source-2.6.30.7
    zcat /proc/config.gz > .config
    make menuconfig
    make
    make modules
    make modules_install
    mkinitramfs -o /boot/initrd.img-2.6.30.7 2.6.30.7
    Here is the snapshot:

    hxxp://img687.imageshack.us/img687/3245/snapshot2v.png


    The content of the log is: (cat /tmp/vmware-root/setup-13742.log)
    Code:
    Nov 01 09:56:10.629: app| Log for VMware Workstation pid=5508 version=6.5.2 build=build-156735 option=Release
    Nov 01 09:56:10.629: app| Host codepage=UTF-8 encoding=UTF-8
    Nov 01 09:56:10.629: app| Logging to /tmp/vmware-root/setup-5508.log
    Nov 01 09:56:22.694: app| Extracting the sources of the vmmon module.
    Nov 01 09:56:22.836: app| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.30.7/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.3.2
    Nov 01 09:56:33.122: app| The vmmon module loads perfectly in the running kernel.
    Nov 01 09:56:33.122: app| 
    Nov 01 09:56:33.173: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/2.6.30.7/misc/vmmon.o
    Nov 01 09:56:34.727: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/2.6.30.7/misc/vmmon.ko
    Nov 01 09:56:43.216: app| Extracting the sources of the vmnet module.
    Nov 01 09:56:43.317: app| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmnet-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.30.7/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.3.2
    Nov 01 09:56:53.404: app| The vmnet module loads perfectly in the running kernel.
    Nov 01 09:56:53.404: app| 
    Nov 01 09:56:53.410: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/2.6.30.7/misc/vmnet.o
    Nov 01 09:56:53.675: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/2.6.30.7/misc/vmnet.ko
    Nov 01 09:56:54.411: app| Extracting the sources of the vmblock module.
    Nov 01 09:56:54.470: app| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmblock-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.30.7/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.3.2
    Nov 01 09:56:56.277: app| Extracting the sources of the vmci module.
    Nov 01 09:56:56.371: app| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmci-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.30.7/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.3.2
    Nov 01 09:57:03.316: app| The vmci module loads perfectly in the running kernel.
    Nov 01 09:57:03.316: app| 
    Nov 01 09:57:03.324: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/2.6.30.7/misc/vmci.o
    Nov 01 09:57:03.603: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/2.6.30.7/misc/vmci.ko
    Nov 01 09:57:04.408: app| Extracting the sources of the vmci module.
    Nov 01 09:57:04.425: app| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmci-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.30.7/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.3.2
    Nov 01 09:57:06.646: app| The vmci module loads perfectly in the running kernel.
    Nov 01 09:57:06.646: app| 
    Nov 01 09:57:06.655: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/2.6.30.7/misc/vmci.o
    Nov 01 09:57:07.049: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/2.6.30.7/misc/vmci.ko
    Nov 01 09:57:07.769: app| Extracting the sources of the vsock module.
    Nov 01 09:57:07.858: app| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vsock-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.30.7/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.3.2
    Nov 01 09:57:11.106: app| The vsock module loads perfectly in the running kernel.
    Nov 01 09:57:11.106: app| 
    Nov 01 09:57:11.114: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/2.6.30.7/misc/vsock.o
    Nov 01 09:57:11.445: app| Registering file: /usr/lib/vmware/installer/vmware-installer --register-file vmware-player regular /lib/modules/2.6.30.7/misc/vsock.ko
    Nov 01 09:57:43.476: app| Extracting the sources of the vmblock module.
    Nov 01 09:57:43.494: app| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmblock-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.30.7/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.3.2
    Any thoughts?

    Thank you
    "If it doesn't sleep, doesn't eat, doesn't take **** breaks and plays poker 24 hours a day - it's a bot!"

  5. #35
    Just burned his ISO
    Join Date
    Dec 2009
    Posts
    4

    Default

    Thanks a lot man

  6. #36
    Just burned his ISO
    Join Date
    Dec 2009
    Posts
    1

    Default

    Quote Originally Posted by admrt View Post
    I'll try to make it easy... (Everything as root from the shell)

    1. apt-get install linux-source-2.6.30.5
    2. cd /usr/src
    3. tar xvjf linux-source-2.6.30.5.tar.bz2
    4. cd linux-source-2.6.30.5
    5. zcat /proc/config.gz > .config
    6. make menuconfig
    7. In the menu choose: Processor type and features -> High Memory Support (4GB) -> 64GB, and then exit the program saving the changes when it asks for it
    8. make (And wait... Depending on your computer this may take something between 15 minutes to about an hour. This will create /usr/src/linux-source-2.6.30.5/arch/x86/boot/bzImage and /usr/src/linux-source-2.6.30.5/System.map that you will use with grub so copy them as /boot/vmlinuz-2.6.30.5 and /boot/System.map-2.6.30.5 respectively. You will have to make an entry for them in /boot/grub/menu.lst)
    9. make modules
    10. make modules_install
    11. mkinitramfs -o /boot/initrd.img-2.6.30.5 2.6.30.5
    12. reboot (assuming you made the correct entry for grub you will be able to boot from it)
    13. (from the shell as root) fix-splash

    And everything should be working...

    Check the memory with free, and it should report the amount of RAM you really have.

    Hope it helps
    How to made the correct entry for grub ?thanks very much!

  7. #37
    Member
    Join Date
    Feb 2007
    Posts
    229

    Default

    /usr/sbin/grub-update i believe, or update-grub will scan the system and set up menu.lst for you.


    However, i've found that the above procedure has an issue - i've been struggling with this most of the day. for some reason, mounting NTFS partitions ends badly to say the least. The system goes into a hard-lock, requiring a hard reboot. There's something about enabling PAE that causes problems.

    Does BT4pf still use ntfs-3g or the built in kernel support for NTFS? i went through the default config and it has ntfs read support enabled. i didnt change a thing except to enable PAE (64GB support) and every time i mount an ntfs partition, my system has that lock-up problem. Any ideas?

  8. #38
    Just burned his ISO
    Join Date
    Jan 2010
    Posts
    6

    Default

    tnx for the information.

  9. #39
    Junior Member
    Join Date
    Feb 2010
    Posts
    28

    Red face nice

    nice very nice

Page 4 of 4 FirstFirst ... 234

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •