Hi,
I am trying to install Anti X into my Old Desktop. Well, it has 256 MB RAM and Processor is Intel Pentium D with 2GHz frequency. Motherboard is of Asus. I tried to install Lubuntu 12.04 but live booting didn't work...Normal booting options came up and when Entered option "Try Lubuntu without Installation", loading screen came up and then suddenly...
Screen became blank and a small box with a message" Hz ?" is floating....
I initially thought it would be because i'm trying to install Lubuntu but SAME PROBLEM persist when i tried to install Anti X...
I am trying to dual boot...Windows XP is already running without any problem but I want to use Linux Distro.
....Please Help....
topic title: Couldnot Live Boot AntiX 13.1 in my old Desktop
9 posts
• Page 1 of 1
-
new2antiXPosts: 4
- Joined: 19 Jul 2013
-
rokytnjiPosts: 4,164
- Joined: 20 Feb 2009
#2
Watch the video and try again
^---- embedded YouTube-hosted video: https://www.youtube.com/9kCotJWcoiE
Pay special attention to using the F keys in the beginning and using boot cheat codes.
^---- embedded YouTube-hosted video: https://www.youtube.com/9kCotJWcoiE
Pay special attention to using the F keys in the beginning and using boot cheat codes.
-
dolphin_oraclePosts: 2,238
- Joined: 16 Dec 2007
#3
Do you know the model number of the motherboard and are you using onboard graphics?
My first suspicion is the graphics driver. You should try the alternative graphics options in the cheat code menus first and see if any of those help. Your RAM shouldn't be a problem.
My first suspicion is the graphics driver. You should try the alternative graphics options in the cheat code menus first and see if any of those help. Your RAM shouldn't be a problem.
-
new2antiXPosts: 4
- Joined: 19 Jul 2013
#4
@rokytnji :I watched that video twice before installing...since he didnt make any changes in that Boot Option Line, I also didnt do anything...Well as i am new to this i dont know what all codes combination should i use...I went through default settings...I tried to change video options but nothing was working...
Follow Daves advise first.
Me. I am not scared of using the help menu that D.O. shows in the beginning of the video and typing in the boot cheat codes.
Anticapitalistas words
Follow Daves advise first.
Me. I am not scared of using the help menu that D.O. shows in the beginning of the video and typing in the boot cheat codes.
Anticapitalistas words
so might as well use them.added more options to live fast boot cheats.
-
DavePosts: 1,062
- Joined: 20 Jan 2010
#5
If you boot into init 3 with the number 3 at the end of the grub line, does the moniter stay working?
If so, I would try logging in as root , password root, and running X -configure.
This should build an xorg.conf.new in /root/, you will need to copy that to /etc/X11/ by running
cp /root/xorg.conf.new /etc/X11/xorg.conf
Then boot to run level 5 / or start slim with service slim start (/etc/init.d/slim start).
If that does not work quite right, I would press"Control + ALT + F1" and then you should see the root prompt again.
Here type: service slim stop (/etc/init.d/slim stop)
and try running without the login manager. It will not work as root (which you would be logged in as) so
type: exit
And then log in as demo, password demo.
Then at demo's prompt type: startx to see if that brings up a desktop.
If that does not work you could try another Window manager.
At the prompt for demo (press Control + ALT + f1 if neccessary)
type: startx jwm
or
type: startx fluxbox
If all the above fail we may need to add a mode line to the xorg.conf as it might be trying to run outside of the usable resolution spectrum of the screen (my laptop does this).
If so, I would try logging in as root , password root, and running X -configure.
This should build an xorg.conf.new in /root/, you will need to copy that to /etc/X11/ by running
cp /root/xorg.conf.new /etc/X11/xorg.conf
Then boot to run level 5 / or start slim with service slim start (/etc/init.d/slim start).
If that does not work quite right, I would press"Control + ALT + F1" and then you should see the root prompt again.
Here type: service slim stop (/etc/init.d/slim stop)
and try running without the login manager. It will not work as root (which you would be logged in as) so
type: exit
And then log in as demo, password demo.
Then at demo's prompt type: startx to see if that brings up a desktop.
If that does not work you could try another Window manager.
At the prompt for demo (press Control + ALT + f1 if neccessary)
type: startx jwm
or
type: startx fluxbox
If all the above fail we may need to add a mode line to the xorg.conf as it might be trying to run outside of the usable resolution spectrum of the screen (my laptop does this).
-
new2antiXPosts: 4
- Joined: 19 Jul 2013
#6
Dave : nothing is working....I didnt understand add a mode line to xorg.conf ????
how to do that ????
how to do that ????
-
DavePosts: 1,062
- Joined: 20 Jan 2010
#7
Ok, if you open you xorg.conf
log in as root
type: nano /etc/X11/xorg.conf
find something that looks like the section below
The #choose the resolution line is the one that you probably need. Breaking this apart....
Modes"1024x768_75.00"
Modes = specifies a mode for the screen (leave it as Modes)
1024x768 = the screen resolution you would like
_75.00 = the frequency the moniter is to run at. Other comon frequencies are 59.00 and 60.00
You should add this line below every depth instance in this section, the lines are similar to below
Depth 8
Depth 16
Depth 24
Depth 32
Save and then try to start slim as root or run startx as demo again.
log in as root
type: nano /etc/X11/xorg.conf
find something that looks like the section below
Code: Select all
Section"Screen"
Identifier "Screen0" #Collapse Monitor and Device section to Screen section
Device "Device0"
Monitor "Monitor0"
DefaultDepth 16 #Choose the depth (16||24)
SubSection "Display"
Depth 16
Modes "1024x768_75.00" #Choose the resolution < this is the mode line
EndSubSection
EndSection
Modes"1024x768_75.00"
Modes = specifies a mode for the screen (leave it as Modes)
1024x768 = the screen resolution you would like
_75.00 = the frequency the moniter is to run at. Other comon frequencies are 59.00 and 60.00
You should add this line below every depth instance in this section, the lines are similar to below
Depth 8
Depth 16
Depth 24
Depth 32
Save and then try to start slim as root or run startx as demo again.
-
BitJamPosts: 1,308
- Joined: 31 Aug 2009
#8
Here are a few easy things to try to help debug this problem.
1) You could try using boot code"vga=792" to force the display to 1024x768 resolution or"vga=795" to force it to 1280x1024. This will allow more text to stay on the screen.
2) You should always select the"F5 Video Mode" -->"safe" option (or even"very safe"). This will prevent kernel mode switching. Sometimes on older hardware the screen will either lose sync or go blank because the kernel tries to default to the highest possible resolution. This happens about 1/5 through the boot process. I realize the term"1/5" can be rather meaningless if you never see all the boot process so I've attached a picture.
3) As Dave suggested, the bootcode"3" will keep you in command line mode. If this works then we know the problem is only with X-windows. IMO there is no point in debugging video drivers if you can't get to the command line first.
Also, it might help us if we knew the model of your ASUS motherboard. If you have a graphics card, it would help if we knew the make/model. This problem is likely related to your hardware so it sometimes helps us if we know what that hardware is.
I've uploaded a screenshot of almost the entire boot screen at 1280x1024 resolution. I chopped off some of the image on the right because it was all blank. I scrolled the text down to get the start of the boot process in the image so there are 5 lines missing from the bottom.
If the screen goes blank around the time it says"Waiting for /dev to be fully populated..." (the 11th line down) then the problem is almost certainly with kernel mode setting and should be fixed by using F5 -->"safe" video mode.
If the problem doesn't occur until closer to the bottom then it is likely just a problem with X-windows and the"3" boot option should get you to the command line and from there we can fix X windows.
If you don't even get to the 6th line which says"The /init bootstrap is done." then the problem is within the initrd.
It would help us a lot if we understood the"loading screen" in a bit more detail. That way we will know what part of the boot process is broken. I give instructions below showing different places in the boot process where there could be a problem.new2antiX wrote:live booting didn't work...Normal booting options came up and when Entered option"Try Lubuntu without Installation", loading screen came up and then suddenly... Screen became blank and a small box with a message" Hz ?" is floating.... I initially thought it would be because i'm trying to install Lubuntu but SAME PROBLEM persist when i tried to install Anti X...
Here are a few easy things to try to help debug this problem.
1) You could try using boot code"vga=792" to force the display to 1024x768 resolution or"vga=795" to force it to 1280x1024. This will allow more text to stay on the screen.
2) You should always select the"F5 Video Mode" -->"safe" option (or even"very safe"). This will prevent kernel mode switching. Sometimes on older hardware the screen will either lose sync or go blank because the kernel tries to default to the highest possible resolution. This happens about 1/5 through the boot process. I realize the term"1/5" can be rather meaningless if you never see all the boot process so I've attached a picture.
3) As Dave suggested, the bootcode"3" will keep you in command line mode. If this works then we know the problem is only with X-windows. IMO there is no point in debugging video drivers if you can't get to the command line first.
Also, it might help us if we knew the model of your ASUS motherboard. If you have a graphics card, it would help if we knew the make/model. This problem is likely related to your hardware so it sometimes helps us if we know what that hardware is.
I've uploaded a screenshot of almost the entire boot screen at 1280x1024 resolution. I chopped off some of the image on the right because it was all blank. I scrolled the text down to get the start of the boot process in the image so there are 5 lines missing from the bottom.
If the screen goes blank around the time it says"Waiting for /dev to be fully populated..." (the 11th line down) then the problem is almost certainly with kernel mode setting and should be fixed by using F5 -->"safe" video mode.
If the problem doesn't occur until closer to the bottom then it is likely just a problem with X-windows and the"3" boot option should get you to the command line and from there we can fix X windows.
If you don't even get to the 6th line which says"The /init bootstrap is done." then the problem is within the initrd.
Last edited by BitJam on 20 Jul 2013, 09:21, edited 1 time in total.
-
new2antiXPosts: 4
- Joined: 19 Jul 2013
#9
Thanks !!! I could live boot AntiX after opting Video Mode as Safe and using XLDM in boot option line...it worked....!!!
Thanks everyone...
Thanks everyone...