[SOLVED]startx didn't start, but now it does in 7.2 fromiso

Posts: 22
Richard
Joined: 15 Jan 2008
#1
<SOLVED>
Just a note to advise that the new 7.2 solves this problem for me.
And to thank Anticapitalista for all the tweaks.

The desktop is neat,
but I will have to import my old Icewm menu file.

And it sets

Thanks,
Richard.

</SOLVED>

I've burned 4 different cd-rw disks with antiX-M7.01.
DAO, auto, etc.
All boot to directly to console.
Login as demo.

and so far have been unable to get X to run.

Must be something I'm overlooking.

The previous version booted directly to the wallpaper screen.

Appreciate any ideas. Want to try this on a troublesome P2.

regards,
Richard.
Last edited by Richard on 22 Apr 2008, 19:35, edited 2 times in total.
anticapitalista
Posts: 5,959
Site Admin
Joined: 11 Sep 2007
#2
Hello Richard.

The usual suggestions.

Burn at slow speed
Use cd r
Check md5sum
Try other boot options ie failsafe
Try using the cheatcode nogui (avoids slim login manager)
Use boot fromhd rather than cd
Any messages in /var/log from xorg?
Posts: 22
Richard
Joined: 15 Jan 2008
#3
anticapitalista wrote: Burn at slow speed: yes, but on cd-rw?
Use cd r: I'll try this at slowest speed,
Check md5sum: Verified.
Try other boot options ie failsafe : will try some.

Try using the cheatcode nogui (avoids slim login manager): Will try next attempt. Will advise.

Use boot fromhd rather than cd -> Tried fromiso but think my path needs tweaking. Will try fromhd.

Any messages in /var/log from xorg? -> I'll check next boot.
Thanks AC,
I'll try a cd-r, dao, slowest, boot with nogui, then fromhd.
Something should work. Might even be my cd unit?

saludos,
Richard.
Posts: 1,520
eriefisher
Joined: 07 Oct 2007
#4
When you get to a login prompt and login su to root and try"slim". This should get you to a graphical login to see if it works or you will at least get an error message. It could be a driver issue. You may have to reconfigure xorg.

eriefisher
Posts: 22
Richard
Joined: 15 Jan 2008
#5
Booted fromiso but still get the same result.
md5 checks OK.
I guess it just doesn't like my mundane hardware. __{{emoticon}}__

Or something I'm doing is wrong:

This is from sidux, up-to-date:
Host/Kernel/OS"erosbox" running Linux 2.6.24-rc7-git7-slh-smp-1 i686 [ sidux 2007-04 - Έρως - kde-full - (200711210243) ]
CPU Info Intel Pentium 4 1024 KB cache flags( sse3 ) clocked at [ 2800.206 MHz ]
Videocard VIA , S3 Unichrome Pro VGA Adapter X.Org 1.4.0.90 [ 1440x900@60.0hz ]
Network cards VIA VT6102 [Rhine-II], at port: d400
Processes 122 | Uptime 5min | Memory 261.8/440.0MB | HDD ATA Maxtor 6E040L0,ATA WDC WD800BB-00JH Size 121GB (55%used) | Client Shell wrapper | Infobash v3.01

I'll try again later. Maybe it really is the CD-RW, but the ISO does the same. Strange but not unheard of. I'll try these disks on the P2 just in case.

saludos,
Richard.
anticapitalista
Posts: 5,959
Site Admin
Joined: 11 Sep 2007
#6
At boot grub menu, hit F3 and set your screen specs.
Have you tried the nogui cheat option?
Posts: 22
Richard
Joined: 15 Jan 2008
#7
I tried the failsafe and the nogui cheatcodes with the cds.

I'll give them a try from the iso later today.
Just doesn't want to startfluxbox or x.

Thought it might be the LG L192WS
but Mepis 7 boots and runs OK on it.
Richard
Joined: 15 Jan 2008
#8
booting fromiso with nogui,
I get this after logging in as demo:
$ startfluxbox
...
logfile var/log/X.org.log
EE) failed to load module"type 1" (module does not exist, 0)
" module already built-in.
VESA(0) no matching mode
Screen found but none hava a usable configuration.

Fatal server error: No screens found: IO error 104


I'll download it again, just in case and see if that helps.
Curious.
Last edited by Richard on 18 Jan 2008, 22:20, edited 1 time in total.
anticapitalista
Posts: 5,959
Site Admin
Joined: 11 Sep 2007
#9
Sorry that antiX is causing you a bit of a headache Richard.
Boot with the nogui option again, and after logging in as demo/demo
type startx rather than startfluxbox.
If you get the same error (and I think you will), then try using as root
dpkg-reconfigure xorg-xserver

It seems that antiX doesn't like your monitor and cannot set xorg.conf correctly.

You could use the sidux xorg.conf (if it works) and add the important bits to the xorg.conf in antiX.