WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: GUI will not start  (Read 32170 times)

Offline testman

  • Newbie
  • *
  • Posts: 9
GUI will not start
« on: August 30, 2012, 01:02:03 PM »
Hi

I am using HP Pavillion G6-1225ev (Intel HD 3000 and AMD Radeon 6470m) and not metter from where I boot (Hard disk, USB, LiveCD), I always get command line instead of GUI.
I tried Xvesa setup but it shows me no options, i can just quit.
Only after I installed Xorg.tcz and few packages so that I was actually able to run command "startx", only after that i got to desktop image. But that is that. No mouse, no icons, no menu bar, just desktop.

edit: I am using latest TinyCore Linux, 4.6 that is.

Does anyone have any suggestions for me, how to solve my problem?
Thank you.

Offline ananix

  • Full Member
  • ***
  • Posts: 174
Re: GUI will not start
« Reply #1 on: August 30, 2012, 01:13:28 PM »
far from a bug.

sounds like you got a hold of micro core instead of tiny core or what ever core you expected.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11573
Re: GUI will not start
« Reply #2 on: August 30, 2012, 01:42:27 PM »
Hi testman
First, compare the size of the ISO you downloaded to the sizes of the ISOs on the download page and verify which
file you actually downloaded. If you want a GUI, you should use the Tinycore ISO. If you used the Coreplus ISO,
make sure the  X/GUI option was checked as shown in step 5 here:
http://distro.ibiblio.org/tinycorelinux/install.html

This sounds like operator error so I'm moving this thread to Q&A.

Offline testman

  • Newbie
  • *
  • Posts: 9
Re: GUI will not start
« Reply #3 on: August 30, 2012, 02:18:42 PM »
Firstly, excuse me for posting in wrong subforum.

I am using .iso I downloaded from official page, named "TinyCore-current.iso", it has size of 12,6 MB.
I also tried CorePlus ("CorePlus-4.6.iso", 68,2 BM) and every option in boot menu gives me CLI, none of them starts GUI.

Offline ananix

  • Full Member
  • ***
  • Posts: 174
Re: GUI will not start
« Reply #4 on: August 30, 2012, 03:54:02 PM »
Maybe there is something wrong with your tce dir maybe more specific ./optional maybe some tce cde confusion at boot or in dir name, maybe permission rights, maybe in another dir like /usr/bin or just bin or what ever, it all starts to sound a bit intriguing consider it comes straight from iso. Sorry for my first trivial response.
No error messages? Did you try pausing the console with ctrl+q (ctrl+s to start) before it clears screen.
I have heard about problems with different iso to media converters and tcl, how did you transfer the iso?
« Last Edit: August 30, 2012, 03:56:44 PM by ananix »

Offline testman

  • Newbie
  • *
  • Posts: 9
Re: GUI will not start
« Reply #5 on: August 30, 2012, 04:21:30 PM »

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11573
Re: GUI will not start
« Reply #6 on: August 30, 2012, 04:36:14 PM »
Hi testman
What happens if you remove that  cde  bootcode you are using?

Offline testman

  • Newbie
  • *
  • Posts: 9
Re: GUI will not start
« Reply #7 on: August 30, 2012, 05:44:27 PM »
I still get CLI.
I tried many combinations of bootcodes, none of them makes GUI work.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: GUI will not start
« Reply #8 on: August 30, 2012, 06:00:45 PM »
What is the output of "Xvesa -listmodes" ?   
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline testman

  • Newbie
  • *
  • Posts: 9
Re: GUI will not start
« Reply #9 on: August 31, 2012, 05:56:42 AM »
Xvesa -listmodes gives me this error output:
Code: [Select]
Unexpected result code 0xFFFFFFFF from vm86
eax=0x00004F00 ebx=0x00000000 ecx=0x00000000 edx=0x00000000
esi=0x00000000 edi=0x00000000 ebp=0x00000000
eip=0x00000014 esp=0x00000FFA eflags=0x00003200
cs=0xC000      ds=0x0000      es=0x1101      fs=0x0000      gs=0x0000
 30 30 30 30 30 B4 22 ->E9 CD 21 26 40 00 B0 0A
vm86 failed (errno 38)
Unexpected result code 0xFFFFFFFF from vm86
eax=0x00004F00 ebx=0x00000000 ecx=0x00000000 edx=0x00000000
esi=0x00000000 edi=0x00000000 ebp=0x00000000
eip=0x00000014 esp=0x00000FFA eflags=0x00003200
cs=0xC000      ds=0x0000      es=0x1101      fs=0x0000      gs=0x0000
 30 30 30 30 30 B4 22 ->E9 CD 21 26 40 00 B0 0A
vm86 failed (errno 38)
0x0006: 640x200x1 (monochrome) Planar (1 planes)
0x000D: 320x200x4 Planar (4 planes) (no linear framebuffer)
0x000E: 640x200x4 Planar (4 planes) (no linear framebuffer)
0x0010: 640x350x4 Planar (4 planes) (no linear framebuffer)
0x0011: 640x480x1 (monochrome) Planar (1 planes)
0x0012: 640x480x4 Planar (4 planes) (no linear framebuffer)
0x0013: 320x200x8 PseudoColor

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: GUI will not start
« Reply #10 on: August 31, 2012, 06:30:54 AM »
Well, that could explain why xsetup fails...

What do
"uname -a"
&
"cat /proc/cpuinfo"
output?
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline testman

  • Newbie
  • *
  • Posts: 9
Re: GUI will not start
« Reply #11 on: August 31, 2012, 06:49:59 AM »
uname -a
Code: [Select]
Linux box 3.0.21-tinycore64 #6446 SMP Sat Feb 18 13:20:23 EET 2012 x86_64 GNU/Linux

cat /proc/cpuinfo
Code: [Select]
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz
stepping : 7
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid
bogomips : 4791.13
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz
stepping : 7
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid
bogomips : 4791.71
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz
stepping : 7
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid
bogomips : 4791.74
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz
stepping : 7
cpu MHz : 800.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid
bogomips : 4791.75
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11041
Re: GUI will not start
« Reply #12 on: August 31, 2012, 07:01:36 AM »
You're running the 64-bit edition, Xvesa does not work on 64. It's mentioned in several places, use Xfbdev or Xorg instead.

But you also said you used our isos - we don't ship 64-bit isos. Is this a remaster or not?
The only barriers that can stop you are the ones you create yourself.

Offline testman

  • Newbie
  • *
  • Posts: 9
Re: GUI will not start
« Reply #13 on: August 31, 2012, 07:13:48 AM »
But as I see, in distribution files on your FTP server, there are 64 bit version of vmlinuz and core.
http://distro.ibiblio.org/tinycorelinux/4.x/x86/release/distribution_files/
I changed kernel after original ISO didn't work in hope of solution.

OK, i will install Xorg then. Thank you for all your help :)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11041
Re: GUI will not start
« Reply #14 on: August 31, 2012, 07:16:06 AM »
Yeah, the files are available, it's just that you should have said you used them.
The only barriers that can stop you are the ones you create yourself.