Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 17 of 17
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux Newbie beachboy's Avatar
    Join Date
    Apr 2005
    Location
    Rockford, MI 49341
    Posts
    125

    Thank You to everybody that help out changing that file worked great.

    again thank you

  2. #12
    Linux Guru
    Join Date
    May 2004
    Location
    forums.gentoo.org
    Posts
    1,817
    Quote Originally Posted by beachboy
    Thank You to everybody that help out changing that file worked great.
    That's great, beachboy. Was the problem with the "root=/dev/hdxn" or with "###disk=100000" like Riqz85 had?
    /IMHO
    //got nothin'
    ///this use to look better

  3. #13
    Linux Guru budman7's Avatar
    Join Date
    Oct 2004
    Location
    Knee deep in Grand Rapids, Michigan
    Posts
    3,901
    Beachboy told me that it was the #s in there.
    The # sign was in 3 different locations. They all had to be taken out.

    For those of you wondering, beachboy lives about 25 miles from my house and works with me in my computer repair business.
    If you want to learn more about linux take a linux journey
    https://linuxjourney.com/
    Use CODE tags when posting output of commands. Thank you.
    https://www.linuxcounter.net/cert/608410.png

  4. $spacer_open
    $spacer_close
  5. #14
    Linux Guru
    Join Date
    May 2004
    Location
    forums.gentoo.org
    Posts
    1,817
    Quote Originally Posted by budman7
    For those of you wondering, beachboy lives about 25 miles from my house and works with me in my computer repair business.
    Cool. Linux pals. So what's with the #'s? Any clue?
    /IMHO
    //got nothin'
    ///this use to look better

  6. #15
    Linux Newbie beachboy's Avatar
    Join Date
    Apr 2005
    Location
    Rockford, MI 49341
    Posts
    125
    Yes it was drakebasher

    Was the problem with the "root=/dev/hdxn" or with "###disk=100000" like Riqz85 had?

    I changed the ### to ram and it worked fine

  7. #16
    Quote Originally Posted by beachboy
    Yes it was drakebasher

    Was the problem with the "root=/dev/hdxn" or with "###disk=100000" like Riqz85 had?

    I changed the ### to ram and it worked fine
    HOLY CRAP!!

    Well this was the identical same issue I JUST had, actually, this thread came up when I searched the error message.

    mine said "### isk" on the line, changed it to ramdisk, viola!

    Works now!

  8. #17
    Quote Originally Posted by Riqz85
    ii think linux is really all trial and error. But trial and error actually works on linux...unlike windows where trial and error brings to doom and death
    Can't agree better.I am a noob in Linux and already learning at good speed.Have also learnt to build own kernel too....Will be shifting more to Linux as i simply hate the BSOD.

Posting Permissions

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