Author Topic: Cant boot straight into graphics & network mode (5)... 'elp  (Read 918 times)

Lennon

  • Member
  • **
  • Posts: 59
  • Kudos: 0
Hey guys, long time no see (if anyone remembers me).

I got a new hard drive and I installed window$ first and then Linux Mandrake 9.1 just like i did the last time i installed them both. Now I choose linux in the (LILO) boot menu and as it loads into graphics and network mode it shows the desktop for a second or two and then goes back to text mode and then shows the graphics again (I just see blue background and mouse) and back to text again. The screen changes a bit more, but I can see that it goes into graphics mode after "dm" is loaded (not sure what it stands for). Anyway, i booted failsafe and used linuxconf and all that to change everything like it was on the old one and I cant get it to boot properly. I had this problem before but what solved it last time doesnt work now. I remember I got many great advice, so I hope I get it now too.

BTW: As I'm posting from windwo$ I have a really weird problem as it is uploading at MAXIMUM speed to all IP ranges starting with 62.193. Go to my topic in the Lounge to help me figure that one out too!!
Peace out.

Lennon

  • Member
  • **
  • Posts: 59
  • Kudos: 0
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #1 on: 30 September 2003, 22:30 »
i'm dieing here :-S
Peace out.

mobrien_12

  • VIP
  • Member
  • ***
  • Posts: 2,138
  • Kudos: 711
    • http://www.geocities.com/mobrien_12
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #2 on: 30 September 2003, 23:14 »
If you boot into failsafe mode, can you start x manually from the console with startx, or does that show the same behavior?
In brightest day, in darkest night, no evil shall escape my sight....

Lennon

  • Member
  • **
  • Posts: 59
  • Kudos: 0
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #3 on: 30 September 2003, 23:34 »
hmm you see i didnt try that. not that clever am I. i'll get back to you in 5.
Peace out.

Lennon

  • Member
  • **
  • Posts: 59
  • Kudos: 0
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #4 on: 30 September 2003, 23:57 »
Here is exactly what I get:

..root]# startx

xauth:creating new authority file /root.Xauthority
xauth:creating new authority file /root.Xauthority
using authority file /root.Xauthority
writing authority file /root.Xauthority
using authority file /root.Xauthority
writing authority file /root.Xauthority

Xfree86 version 4.40
... (some version stuff)
build date: 12 march 2003
Module loader present
Markers: (--)Probed, (**)From config file,(==)default setting, ... (NI)not implemented, (??)unknown.
(==)Log file: "/var/log/Xfree86.0.log", time: Tue Sep 30 20:50:56 2003
(==)Using config file: "/etc/x11/xf86config-4"
Using vt 7

Waiting for X server to shut down

root]# _

:
Peace out.

Lennon

  • Member
  • **
  • Posts: 59
  • Kudos: 0
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #5 on: 1 October 2003, 00:00 »
Yeah maybe I should also mention that the first time i get X loading i see the cursor and the desktop for 2 seconds. Then black. Then It flickers FOUR times, and i end up at the text console. Might give you a clue about whats happening.
Peace out.

Lennon

  • Member
  • **
  • Posts: 59
  • Kudos: 0
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #6 on: 1 October 2003, 18:56 »
ok ill try other forums
or find someone with a similar problem  
Peace out.

insomnia

  • Member
  • **
  • Posts: 587
  • Kudos: 0
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #7 on: 1 October 2003, 23:20 »
quote:
Originally posted by Lennon:
Yeah maybe I should also mention that the first time i get X loading i see the cursor and the desktop for 2 seconds. Then black. Then It flickers FOUR times, and i end up at the text console. Might give you a clue about whats happening.


Wrong hardware detection (mem)?

To force  HW detection, boot:
#linux parameters

This should show you the same parameters as in Windows. Look for the detected mem.
If this isn't right, boot :
#linux mem=right mem size
(if this works, edit lilo)
Those who can make you believe absurdities can make you commit atrocities.
    Voltaire

Injustice is happening now; suffering is happening now. We have choices to make now. To insist on absolute certainty before starting to apply ethics to life decisions is a way of choosing to be amoral.
R. Stallman

http://www.pvda.be/


Lennon

  • Member
  • **
  • Posts: 59
  • Kudos: 0
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #8 on: 3 October 2003, 19:23 »
How do i boot "#linux parameters" ?
How do i know what the right "mem" is?
What is "mem"?
How do i edit lilo?

i tried XFdrake which was fairly simple and there was nothing wrong. I then went into xf86cfg but it was pretty complicated, but it still seemed everything was allright with the screen. In fact it got me into the highest resolution and graphical (safe) mode.

I have "vi" text editor installed and maybe i can edit lilo with that?
Peace out.

insomnia

  • Member
  • **
  • Posts: 587
  • Kudos: 0
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #9 on: 3 October 2003, 19:48 »
quote:
Originally posted by Lennon:
How do i boot "#linux parameters" ?
How do i know what the right "mem" is?
What is "mem"?
How do i edit lilo?

i tried XFdrake which was fairly simple and there was nothing wrong. I then went into xf86cfg but it was pretty complicated, but it still seemed everything was allright with the screen. In fact it got me into the highest resolution and graphical (safe) mode.

I have "vi" text editor installed and maybe i can edit lilo with that?



Starting from your installation medium,
simply boot: linux parameters.
You'll be presented with a huge list.
If one of these parameters isn't right(you can check this in windows if you don't know them), you'll better do the setup again.
If mandrake shows(parameters) a wrong size of ROM(=mem),adjust this by booting:
linux mem=your right ROM size (you can do this for all parameters)  
If you go true the installation again, just "update" and lilo should be adjusted.

[ October 03, 2003: Message edited by: insomnia ]

Those who can make you believe absurdities can make you commit atrocities.
    Voltaire

Injustice is happening now; suffering is happening now. We have choices to make now. To insist on absolute certainty before starting to apply ethics to life decisions is a way of choosing to be amoral.
R. Stallman

http://www.pvda.be/


Faust

  • Member
  • **
  • Posts: 1,223
  • Kudos: 0
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #10 on: 3 October 2003, 20:00 »
That flickering with X is what it normally does when it's being a turd.  :)  You said it adds "dm" before it works?  Is that a module or something?  Try "insmod dm" in textmode, then startx.  WHat happens?  Also maybe post the full message from startx?
Yesterday it worked
Today it is not working
Windows is like that
 -- http://www.gnu.org/fun/jokes/error-haiku.html

Oddzball

  • Newbie
  • *
  • Posts: 9
  • Kudos: 0
Cant boot straight into graphics & network mode (5)... 'elp
« Reply #11 on: 8 October 2003, 00:59 »
Aug I am having the same damn problem! It tries to go into graphics mode, flickers 4 tmes in and out from text to graphics, then goes to text mode.

(I should also not e i know next to nothng about linux in text mode)

But anyway i logged into the text mode and typed :kde Which loads the KDE desktop interface right?

Ok it tries to load it and flickers some, then goes back into text mode and i notice a buncha text saying it cant find certain files for KDE, so i think its a glitch with KDE personally. I definately feel better knowing someone else is having the same problem.

Anyone know how to fix this? I suppose i could load gnome up but i really dont want to have to install all this crap again.