antiX-17_386-base boots, but no graphical environment

Forum Forums Official Releases antiX-17 “Heather Heyer” antiX-17_386-base boots, but no graphical environment

  • This topic has 8 replies, 4 voices, and was last updated Jan 3-8:33 pm by rodgerrodger2k.
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #4668
    Member
    Avatarrodgerrodger2k

    So, I’ve been experimenting with Antix-17 on an old laptop, and I think it will be perfect for my old IBM NetVista 225732U. Notably, this machine has:

    *1300/100 Mhz Celeron Processor
    *256MB RAM
    *Intel(R) 8xx Chipset Video BI

    I burned the 32-bit antiX-17_386-base.iso image to a CD and booted up the machine. Immediately after loading the kernel, I am hit with this error:

    Undefined video mode number: 317
    Press <ENTER> to see video modes available, <SPACE> to continue, or wait 30 sec

    After multiple reboots I’ve tried all three; none of them seem to make a difference. The machine eventually begins to load antiX, scrolling through colorful lines of text, apparently without incident. However, when it reaches the point where every other machine I’ve tested it on loads the graphical desktop, the IBM freezes on a black screen. I have noticed that the IBM reacts similarly to almost any Debian/Ubuntu-based distro. It boots Q4OS and Slacko Puppy Linux without difficulty. It also used to boot Lucid Puppy, but booting Tahrpup results in the same screen blanking as soon as the machine tries to load the graphical environment.
    Is there anything I can do to load antiX properly. Could it be that this machine is just too far behind the times? Any, and I mean any feedback would be appreciated.

    #4670
    Forum Admin
    rokytnjirokytnji

    I’d bump the ram to max if me.
    Check out using cli installer I guess on 256MB of ram if you wanna stick with 256Mb.

    Sometimes I drive a crooked road to get my mind straight.
    Not all who Wander are Lost.
    I'm not outa place. I'm from outer space.

    Linux Registered User # 475019
    How to Search for AntiX solutions to your problems

    #4671
    Forum Admin
    rokytnjirokytnji

    I just wait for video modes instead of hitting enter or space key.

    Sometimes I drive a crooked road to get my mind straight.
    Not all who Wander are Lost.
    I'm not outa place. I'm from outer space.

    Linux Registered User # 475019
    How to Search for AntiX solutions to your problems

    #4672
    Member
    Avatarrodgerrodger2k

    Thank you for the suggestions.

    When I waited 30 seconds for the video modes, everything loaded normally, however, when preparing to display the graphical environment, there was a quick burst of black and white fuzz, then a back-lit black screen again, the same as all the other times.
    You mentioned RAM; since I don’t have any extra RAM sticks handy, I will probably try the cli-installer like you suggested. I’m beginning to suspect that 256 MB is insufficient for booting a live system; if I can manage to get antiX installed, things may work better.

    Thanks again. I will post an update as soon as I can.

    • This reply was modified 2 years, 7 months ago by rodgerrodger2k.
    #4704
    Member
    Avatarrodgerrodger2k

    So I’ve narrowed the problem down to the Linux kernel; all the Linux distros that have run well on the IBM run kernels from Linux 3.xx.xx. I installed antiX-17_386.iso to a USB drive, booted it on my main computer, and installed the following packages via Synaptic:

    *linux-headers-3.7.10-antix.5-486-smp:i386
    *linux-image-3.7.10-antix.5-486-smp:i386

    They installed without any errors. I then opened the terminal and ran the following command:

    sudo update-grub

    The command finished without errors. I powered off the machine, plugged the USB drive into the IBM, and booted from it. When I reached the GRUB menu, I chose “Advanced Options for antiX” and selected kernel 3.7.10. The computer returned the following errors:

    (See attatched image)

    I’m not sure if I missed a step, or if there’s some configuration file I need to edit (I’m not a coder, so editing files with root privileges makes me a bit nervous). Any ideas?

    • This reply was modified 2 years, 7 months ago by rodgerrodger2k.
    Attachments:
    #4707
    Member
    capreacaprea

    Did you update the kernel on the live-usb this way?
    https://mxlinux.org/wiki/help-files/help-live-usb-kernel-updater

    Its in the mx-wiki on 6.6.1
    https://mxlinux.org/user_manual_mx17/mxum.pdf

    I’m not really sure, if its a tool in controll-center on antix when running live, I never did.

    Edit: Booted my live-stick, it’s a tool in control-center under live

    • This reply was modified 2 years, 7 months ago by caprea.
    • This reply was modified 2 years, 7 months ago by caprea.
    #4716
    Member
    Avatarrodgerrodger2k

    Did you update the kernel on the live-usb this way?
    https://mxlinux.org/wiki/help-files/help-live-usb-kernel-updater

    I did not; I installed the kernel packages via Synaptic Package Manager, as I am trying to make modifications to an installed system stored on a USB pendrive.

    #4717
    Member
    Avatarskidoo

    top result of my quick websearch for “linux boot Undefined video mode number”
    https://www.linuxquestions.org/questions/slackware-14/undefined-video-mode-number-891916/
    suggested:

    try using a bootline parameter (value: hexadecimal equivalent to the reputedly “unknown” mode 317)
    vga=0x13D
    or try bootline parameter
    vga=normal

    If the above doesn’t solve, read about the further boot parameters which are avalable:
    http://download.tuxfamily.org/antix/docs-antiX-17/live-boot/alpha-index.html
    http://download.tuxfamily.org/antix/docs-antiX-17/live-boot/personalize.html#boot-options
    ——————

    edit:
    After websearching “linux boot run-init current directory on the same filesystem as the root”
    I’m not confident the suggestion above will solve this (run-init) problem.
    So, give it a few days… wait for other replies.

    • This reply was modified 2 years, 7 months ago by skidoo.
    #4719
    Member
    Avatarrodgerrodger2k

    Thanks, skidoo, for the advice. I’ll try those vga codes and also wait to see if an answer to the run-init issue presents itself.

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.