Change Memory "chmem" Xorg - Minix

This is a discussion on Change Memory "chmem" Xorg - Minix ; I do this: chmem +100000000 /usr/X11R6/bin/Xorg This is returned: /usr/X11R6/bin/Xorg: Stack+malloc area changed from 0 to 100000000 bytes Xwindow refuses to start using "xdm" However, I do hear a small grunt from the cpu, but no real effort! What am ...

+ Reply to Thread
Results 1 to 7 of 7

Thread: Change Memory "chmem" Xorg

  1. Change Memory "chmem" Xorg

    I do this:

    chmem +100000000 /usr/X11R6/bin/Xorg

    This is returned:

    /usr/X11R6/bin/Xorg: Stack+malloc area changed from 0
    to 100000000 bytes

    Xwindow refuses to start using "xdm" However, I do hear a small
    grunt from the cpu, but no real effort!

    What am I doing wrong

    Regards:

    moose


  2. Re: Change Memory "chmem" Xorg



    "moose" writes:

    > I do this:
    >
    > chmem +100000000 /usr/X11R6/bin/Xorg
    >
    > This is returned:
    >
    > /usr/X11R6/bin/Xorg: Stack+malloc area changed from 0
    > to 100000000 bytes
    >
    > Xwindow refuses to start using "xdm" However, I do hear a small
    > grunt from the cpu, but no real effort!



    - Try startx, try X.
    - What's the error message?
    - Some cards need really much memory.

    - You need to have that memory as real physical memory (at least for
    now). Think about using an old VESA card.

    >
    > What am I doing wrong


    Something.

    This advice has been brought to you by the generic help service.

    Regards -- Markus

    PS: Please don't take my answer amiss, but you certainly don't give us
    much clues what you do, what the actual situation is (hardware
    config, error messages). My CPU doesn't grunt. And so we are left
    with giving generic advice you could also had from spenting 30
    minutes with the list archives.


  3. Re: Change Memory "chmem" Xorg


    Markus E Leypold wrote:
    > "moose" writes:
    >
    > > I do this:
    > >
    > > chmem +100000000 /usr/X11R6/bin/Xorg
    > >
    > > This is returned:
    > >
    > > /usr/X11R6/bin/Xorg: Stack+malloc area changed from 0
    > > to 100000000 bytes
    > >
    > > Xwindow refuses to start using "xdm" However, I do hear a small
    > > grunt from the cpu, but no real effort!

    >
    >
    > - Try startx, try X.
    > - What's the error message?
    > - Some cards need really much memory.
    >
    > - You need to have that memory as real physical memory (at least for
    > now). Think about using an old VESA card.
    >
    > >
    > > What am I doing wrong

    >
    > Something.
    >
    > This advice has been brought to you by the generic help service.
    >
    > Regards -- Markus
    >
    > PS: Please don't take my answer amiss, but you certainly don't give us
    > much clues what you do, what the actual situation is (hardware
    > config, error messages). My CPU doesn't grunt. And so we are left
    > with giving generic advice you could also had from spenting 30
    > minutes with the list archives.

    ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

    Entered "startx" the machine gives a little grunt The cursor moves
    down one line and blinks continously as though waiting for additional
    commands.

    Entered 'X' and received this message:

    Fatal server error: server is already active for display 0. If this
    server is no longer running, remove /tmp/.X0-lock and start again.

    Please consult The X.Org Foundation suport at http://wiki.X.Org for
    help.
    ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

    Intel (R) 82810E Graphics Controller
    Video Adapter: i752 (512KB)
    3d Accelerator: Intel i752 (Integrated 8086 / 712)
    Display Type: SVGA
    SVGA VESA supported
    SVGA VESA Version 2.00
    XGA VESA not supported
    Video Memory: 512KB
    SVGA VESA Memory: 512KB
    VESA Display Data Channel: Supported
    VESA Power Management: Supported
    VESA SVGA BIOS Extensions: Supported
    Video Bios Date 09/03/99
    System Memory 192 MB (SDRAM)

    Regards:

    moose


  4. Re: Change Memory "chmem" Xorg



    "moose" writes:

    > Markus E Leypold wrote:
    >> "moose" writes:
    >>
    >> > I do this:
    >> >
    >> > chmem +100000000 /usr/X11R6/bin/Xorg
    >> >
    >> > This is returned:
    >> >
    >> > /usr/X11R6/bin/Xorg: Stack+malloc area changed from 0
    >> > to 100000000 bytes
    >> >
    >> > Xwindow refuses to start using "xdm" However, I do hear a small
    >> > grunt from the cpu, but no real effort!

    >>
    >>
    >> - Try startx, try X.
    >> - What's the error message?
    >> - Some cards need really much memory.
    >>
    >> - You need to have that memory as real physical memory (at least for
    >> now). Think about using an old VESA card.
    >>
    >> >
    >> > What am I doing wrong

    >>
    >> Something.
    >>
    >> This advice has been brought to you by the generic help service.
    >>
    >> Regards -- Markus
    >>
    >> PS: Please don't take my answer amiss, but you certainly don't give us
    >> much clues what you do, what the actual situation is (hardware
    >> config, error messages). My CPU doesn't grunt. And so we are left
    >> with giving generic advice you could also had from spenting 30
    >> minutes with the list archives.

    > ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
    >
    > Entered "startx" the machine gives a little grunt The cursor moves
    > down one line and blinks continously as though waiting for additional
    > commands.


    But you don't get a shell prompt?

    > Entered 'X' and received this message:
    >
    > Fatal server error: server is already active for display 0. If this
    > server is no longer running, remove /tmp/.X0-lock and start again.
    >
    > Please consult The X.Org Foundation suport at http://wiki.X.Org for
    > help.


    Damn. Enter X _after_ deactivating xdm in /etc/rc* something and after
    starting the machine fresh. Either you started X after startx was
    still trying or after xdm was still trying (from the boot process).


    > Intel (R) 82810E Graphics Controller
    > Video Adapter: i752 (512KB)
    > 3d Accelerator: Intel i752 (Integrated 8086 / 712)
    > Display Type: SVGA
    > SVGA VESA supported
    > SVGA VESA Version 2.00
    > XGA VESA not supported
    > Video Memory: 512KB


    Can anybody tell me, wether I'm right that this means, 100M of memory
    for the Xserver should be enough -- or do I miss something?


    > SVGA VESA Memory: 512KB
    > VESA Display Data Channel: Supported
    > VESA Power Management: Supported
    > VESA SVGA BIOS Extensions: Supported
    > Video Bios Date 09/03/99
    > System Memory 192 MB (SDRAM)


    Nice.


    I have a theory that only console switching is not working in your
    case. Try to use the ALT-F1 ... ALT-F12 to find the virtual console
    with X in it.

    Regards -- Markus

  5. Re: Change Memory "chmem" Xorg

    OP: Do you have networking? X needs it or startup will, in the best
    case, take forever.

    Leslie


  6. Re: Change Memory "chmem" Xorg

    On Apr 11, 1:36 am, "Leslie P. Polzer" wrote:
    > OP: Do you have networking? X needs it or startup will, in the best
    > case, take forever.
    >
    > Leslie


    ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
    Leslie the machine has an 3com pci 3c905c network interface controller
    "NIC" which Minix doesn't support....therefore....no networking. As
    I write this post, I reboot Minix and again try "xdm" at the #
    prompt. The HD makes a small noise "GRUNT " probably just
    registering the command, and then the cursor drops down to a new #
    prompt line and continues its blinking. Fifteen minutes have now
    passed an still no appearence of the Xwindows GUI.

    This is really strange because when minix first installed and "xdm"
    entered the Xwindows GUI came up. However, it asked for an user name
    and password and I didn;t have the password. Also the mouse pointer
    was locked at the center of the Xwindows GUI. It was necessary to Ctl-
    Alt-Del to break out of the lock up, Since then, Xwindows GUI has not
    re-appeared.

    Thanks for your post.

    Regards:
    ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
    moose


  7. Re: Change Memory "chmem" Xorg

    On Apr 10, 3:20 pm, Markus E Leypold
    wrote:
    > "moose" writes:
    > > Markus E Leypold wrote:
    > >> "moose" writes:

    >
    > >> > I do this:

    >
    > >> > chmem +100000000 /usr/X11R6/bin/Xorg

    >
    > >> > This is returned:

    >
    > >> > /usr/X11R6/bin/Xorg: Stack+malloc area changed from 0
    > >> > to 100000000 bytes

    >
    > >> > Xwindow refuses to start using "xdm" However, I do hear a small
    > >> > grunt from the cpu, but no real effort!

    >
    > >> - Try startx, try X.
    > >> - What's the error message?
    > >> - Some cards need really much memory.

    >
    > >> - You need to have that memory as real physical memory (at least for
    > >> now). Think about using an old VESA card.

    >
    > >> > What am I doing wrong

    >
    > >> Something.

    >
    > >> This advice has been brought to you by the generic help service.

    >
    > >> Regards -- Markus

    >
    > >> PS: Please don't take my answer amiss, but you certainly don't give us
    > >> much clues what you do, what the actual situation is (hardware
    > >> config, error messages). My CPU doesn't grunt. And so we are left
    > >> with giving generic advice you could also had from spenting 30
    > >> minutes with the list archives.

    > > ///////////////////////////////////////////////////////////////////////////*////////////////////////////////////////////////////////

    >
    > > Entered "startx" the machine gives a little grunt The cursor moves
    > > down one line and blinks continously as though waiting for additional
    > > commands.

    >
    > But you don't get a shell prompt?
    >
    > > Entered 'X' and received this message:

    >
    > > Fatal server error: server is already active for display 0. If this
    > > server is no longer running, remove /tmp/.X0-lock and start again.

    >
    > > Please consult The X.Org Foundation suport athttp://wiki.X.Orgfor
    > > help.

    >
    > Damn. Enter X _after_ deactivating xdm in /etc/rc* something and after
    > starting the machine fresh. Either you started X after startx was
    > still trying or after xdm was still trying (from the boot process).
    >
    > > Intel (R) 82810E Graphics Controller
    > > Video Adapter: i752 (512KB)
    > > 3d Accelerator: Intel i752 (Integrated 8086 / 712)
    > > Display Type: SVGA
    > > SVGA VESA supported
    > > SVGA VESA Version 2.00
    > > XGA VESA not supported
    > > Video Memory: 512KB

    >
    > Can anybody tell me, wether I'm right that this means, 100M of memory
    > for the Xserver should be enough -- or do I miss something?
    >
    > > SVGA VESA Memory: 512KB
    > > VESA Display Data Channel: Supported
    > > VESA Power Management: Supported
    > > VESA SVGA BIOS Extensions: Supported
    > > Video Bios Date 09/03/99
    > > System Memory 192 MB (SDRAM)

    >
    > Nice.
    >
    > I have a theory that only console switching is not working in your
    > case. Try to use the ALT-F1 ... ALT-F12 to find the virtual console
    > with X in it.
    >
    > Regards -- Markus


    /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

    Hello Markus:

    The F keys produce different data but nothing that looks like a
    vertual screen. Damm; I tried xdm and startx and X at the #. xdm and
    startx do nothing. #X produces the error as noted in previous post.

    I'm having no luck deactivating XDM @ /etc/rc* something


    Regards

    moose



+ Reply to Thread