Find the answer to your Linux question:
Page 10 of 10 FirstFirst ... 6 7 8 9 10
Results 91 to 94 of 94
Resolution is small darkstar is still there but I got the kernel updated...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #91
    Linux Engineer cheetahman's Avatar
    Join Date
    Dec 2004
    Location
    New York
    Posts
    1,130

    Resolution is small darkstar is still there but I got the kernel updated
    \"TTFN Taa Taa For Now\" by Tigger in Winnie the Pooh
    http://www.distrowatch.com Linux Distros
    We Live in a Windows World but there is Linux to save the day

  2. #92
    Banned
    Join Date
    Nov 2004
    Location
    Belgium
    Posts
    1,120
    Quote Originally Posted by cheetahman
    Resolution is small darkstar is still there but I got the kernel updated
    So did you try running xorgsetup (either as root or the way Dapper Dan posted)?
    This will ask you only one question, pick 24 and it should give you a better resolution.

    PS: xorgconfig can be a little hard if you don't fully know your hardware(mostly the monitor and video card)

  3. #93
    Just Joined!
    Join Date
    Oct 2005
    Posts
    1
    Quote Originally Posted by jens
    Their's a 2.6.13 kernel on the 2nd CD.
    You can try it like this:

    Insert your 2nd CD.
    #mount /dev/cdrom /mnt/cdrom
    #installpkg /mnt/cdrom/linux-2.6.13/kernel-source-2.6.13-noarch-1.tgz
    #installpkg /mnt/cdrom/linux-2.6.13/kernel-modules-2.6.13-i486-1.tgz
    #installpkg /mnt/cdrom/linux-2.6.13/kernel-headers-2.6.13-i386-1.tgz
    #installpkg /mnt/cdrom/linux-2.6.13/kernel-generic-2.6.13-i486-1.tgz
    #installpkg /mnt/cdrom/linux-2.6.13/alsa-driver-1.0.9b_2.6.13-i486.1.tgz
    #umount /dev/cdrom /mnt/cdrom

    If you're not using ext3, you'll also need the mkinitrd package from your first CD to make an initrd image.

    Add your new kernel in Lilo, run lilo, reboot...

    PS: ... and the 2nd CD doesn't unclude GNOME anymore.
    Since I prefere having GNOME installed (even if you don't like it, just for it's libs),
    I installed Freerock GNOME (this is very easy using slapt-get):
    http://gsb.freerock.org/installation/#slapt-get
    I tried to follow these instructions, but how do I install the mkinitrd package from my first CD to make an initrd image?

    I'm not sure that is my problem, but when I try to boot the new kernel I get this error message: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,2)

    Could it be something else?

  4. #94
    Trusted Penguin Dapper Dan's Avatar
    Join Date
    Oct 2004
    Location
    The Sovereign State of South Carolina
    Posts
    4,630
    Look on the second CD. There is a file - README.initrd. Here is its contents for your convenience...
    Code:
    Slackware initrd mini HOWTO
    by Patrick Volkerding, volkerdi@slackware.com
    Sat Sep  3 22:20:13 PDT 2005
    
    This document describes how to create and install an initrd, which may be 
    required to use the 2.6 kernel.  Also see "man mkinitrd".
    
    1.  What is an initrd?
    2.  Why to I need an initrd?
    3.  How do I build the initrd?
    4.  Now that I've built an initrd, how do I use it?
    
    
    1.  What is an initrd?
    
    Initrd stands for "initial ramdisk".  An initial ramdisk is a very small 
    Linux filesystem that is loaded into RAM and mounted as the kernel boots, 
    and before the main root filesystem is mounted.
    
    2.  Why do I need an initrd?
    
    The usual reason to use an initrd is because you need to load kernel 
    modules before mounting the root partition.  Usually these modules are 
    required to support the filesystem used by the root partition (ext3, 
    reiserfs, xfs), or perhaps the controller that the hard drive is attached 
    to (SCSI, RAID, etc).  Essentially, there are so many different options 
    available in modern Linux kernels that it isn't practical to try to ship 
    many different kernels to try to cover everyone's needs.  It's a lot more 
    flexible to ship a generic kernel and a set of kernel modules for it.  The 
    generic 2.6 kernel in Slackware supports the ext2 filesystem (which is 
    used by the initrd), and also supports most IDE controllers (much like the 
    old bare.i kernel).  So, if you have an IDE based system that uses the 
    ext2 filesystem, then you will not need to use an initrd to boot.  
    Otherwise, read on.
    
    3.  How do I build the initrd?
    
    The easiest way to make the initrd is to use the mkinitrd script included 
    in Slackware's mkinitrd package.  We'll walk through the process of 
    upgrading to the 2.6.13 Linux kernel using the packages found in 
    Slackware's testing/packages/linux-2.6.13/ directory.
    
    First, make sure the kernel, kernel modules, and mkinitrd package are 
    installed (the current version numbers might be a little different, so 
    this is just an example):
    
      installpkg kernel-generic-2.6.13-i486-1.tgz
      installpkg kernel-modules-2.6.13-i486-1.tgz
      installpkg mkinitrd-1.0.1-i486-1.tgz
    
    Change into the /boot directory:
    
      cd /boot
    
    Now you'll want to run "mkinitrd".  I'm using reiserfs for my root
    filesystem, and since it's an IDE system the reiserfs module will be
    the only one I need to load:
    
      mkinitrd -c -k 2.6.13 -m reiserfs
    
    This should do two things.  First, it will create a directory
    /boot/initrd-tree containing the initrd's filesystem.  Then it will
    create an initrd (/boot/initrd.gz) from this tree.  If you wanted to,
    you could make some additional changes in /boot/initrd-tree/ and
    then run mkinitrd again without options to rebuild the image.  That's
    optional, though, and only advanced users will need to think about that.
    
    Here's another example:  Build an initrd image using Linux 2.6.13
    kernel modules for a system with an ext3 root partition on /dev/hdb3.
    Note that you need both the jbd and ext3 modules to use ext3:
    
      mkinitrd -c -k 2.6.13 -m jbd:ext3 -f ext3 -r /dev/hdb3
    
    
    4.  Now that I've built an initrd, how do I use it?
    
    Now that you've got an initrd (/boot/initrd.gz), you'll want to load
    it along with the kernel at boot time.  If you use LILO for your boot
    loader you'll need to edit /etc/lilo.conf and add a line to load the
    initrd.  Here's an example section of lilo.conf showing how this is
    done:
    
    # Linux bootable partition config begins
    image = /boot/vmlinuz-generic-2.6.13
      initrd = /boot/initrd.gz
      root = /dev/hda6
      label = Lnx2613
      read-only
    # Linux bootable partition config ends
    
    The initrd is loaded by the "initrd = /boot/initrd.gz" line.
    Just add the line right below the line for the kernel image you use.
    Save the file, and then run LILO again ('lilo' at the command line).
    You'll need to run lilo every time you edit lilo.conf or rebuild the
    initrd.
    
    Other bootloaders such as syslinux also support the use of an initrd.
    See the documentation for those programs for details on using an
    initrd with them.
    
    
    ---------
    
    Have fun!
    You are receiving that error message because you have not yet created the intird. Making it, according to Pat's easy to follow instructions, will solve the problem.
    Linux Mint + IceWM Registered: #371367 New Members: click here

Page 10 of 10 FirstFirst ... 6 7 8 9 10

Posting Permissions

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