WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: 800x480 resolution for EEEPC  (Read 11569 times)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10040
Re: 800x480 resolution for EEEPC
« Reply #15 on: May 21, 2010, 11:57:52 AM »
So, Xfbdev works with the kms fb emulation? Good news.

The "nomodeset" boot code is another way to get Xorg 7.4 running on intel/tc3.
The only barriers that can stop you are the ones you create yourself.

Offline mwoodruff

  • WikiUser
  • *
  • Posts: 12
Re: 800x480 resolution for EEEPC
« Reply #16 on: May 21, 2010, 02:50:52 PM »
At Juanito's suggestion, I tried the adding the modeset=0 line to xorg.conf before loading graphics-2.6.33.3.  This definitely had an effect -- I didn't get a high-resolution text mode like I had been getting before when I loaded graphics-2.6.33.3.  When I tried to load Xorg, though, still a black screen.  Do I need to add a modeline to xorg.conf? 


Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7003
    • My Community Forum
Re: 800x480 resolution for EEEPC
« Reply #17 on: May 21, 2010, 03:02:44 PM »
At Juanito's suggestion, I tried the adding the modeset=0 line to xorg.conf before loading graphics-2.6.33.3. 

How did you add it? On the already running system and backup or modified in initrd?
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11018
Re: 800x480 resolution for EEEPC
« Reply #18 on: May 21, 2010, 10:13:23 PM »
At Juanito's suggestion, I tried the adding the modeset=0 line to xorg.conf before loading graphics-2.6.33.3. 

eh?

My suggestion was:
Quote
This might be because you need "options i915 modeset=0" in /etc/modprobe.conf before loading the graphics-2.6.33.3-tinycore extension

Offline mwoodruff

  • WikiUser
  • *
  • Posts: 12
Re: 800x480 resolution for EEEPC
« Reply #19 on: May 22, 2010, 08:09:10 AM »
Yes, I beg your pardon... I did in fact add it to modprobe.conf and not xorg.conf.  This was a lapse of my brain when typing the post:) 

What I did was this: 

I booted into text mode with no extensions loaded and without restoring the backup (boot codes text, base, norestore). 

I added "options i915 modeset=0" to /etc/modprobe.conf then loaded the graphics extension.  When I did this, the screen remained 80 columns wide instead of going into a higher resolution text mode, as it had without the extra line in modprobe.conf. 

Then I loaded Xorg, ran Xorg -configure, copied the resulting configuration file over to /etc/X11/xorg.conf.  I checked it over and it contained the line driver="intel", which I took as a good sign.

Without making any modifications to xorg.conf, I then ran startx and got an unresponsive black screen.

At any rate, I'm very happy with Xfbdev since it gives me my native resolution, but I enjoy tinkering and it would be neat if I could figure out how to get Xorg up and running.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10040
Re: 800x480 resolution for EEEPC
« Reply #20 on: May 22, 2010, 08:33:02 AM »
Could be the chip is too new for the Intel driver in 7.4.
The only barriers that can stop you are the ones you create yourself.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11018
Re: 800x480 resolution for EEEPC
« Reply #21 on: May 22, 2010, 09:02:55 AM »
I haven't managed to get intel graphics chips to work with Xorg confless or with the suggested configuration on three different machines - it might be worth googling on your graphics chipset name and xorg.conf

Edit: if you look in /var/log/Xorg.0.log it says what devices are supported when it loads the intel driver:
Code: [Select]
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, IGD_GM, IGD_G, 965G, G35,
965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
Mobile Intel® GM45 Express Chipset,
Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41
« Last Edit: May 22, 2010, 09:06:44 AM by Juanito »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10040
Re: 800x480 resolution for EEEPC
« Reply #22 on: May 22, 2010, 09:49:55 AM »
Intel does add support to chips before they ship, 3150 was called IDG_G at that point. Maybe support for it was not finished yet at 2.7, though.
The only barriers that can stop you are the ones you create yourself.

Offline jur

  • Hero Member
  • *****
  • Posts: 863
    • cycling photo essays
Re: 800x480 resolution for EEEPC
« Reply #23 on: May 22, 2010, 06:51:25 PM »
If I may suggest, install puppeee with xorg, that will generate the xorg.conf file probably correctly. The copy the file over to tinycore and see if it will run like that. That's how I got mine going as confless has not been successful with mine with the external monitor attached.

Offline mwoodruff

  • WikiUser
  • *
  • Posts: 12
Re: 800x480 resolution for EEEPC
« Reply #24 on: May 23, 2010, 09:55:25 AM »
I went over to the intellinuxgraphics website, and it looks like the 3150 has been supported only since  2.10.  Or maybe 2.9: IDGNG was supported in 2.9, then disappeared in 2.10 when support for the 3150 was added.  So it looks like Xorg7.5 might support my graphics chipset, but not Xorg7.4. 

Offline mwoodruff

  • WikiUser
  • *
  • Posts: 12
Re: 800x480 resolution for EEEPC
« Reply #25 on: May 24, 2010, 06:55:53 AM »
And here are the relevant lines from /var/log/Xorg.0.log:

(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
   i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
   E7221 (i915), 915GM, 945G, 945GM, 945GME, IGD_GM, IGD_G, 965G, G35,
   965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
   Mobile Intel® GM45 Express Chipset,
   Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41

IDG_G is not present, nor is the 3150. 

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10040
Re: 800x480 resolution for EEEPC
« Reply #26 on: May 24, 2010, 01:30:30 PM »
My typo, I meant IGD_G.
The only barriers that can stop you are the ones you create yourself.