Hi,
I just installed and fully updated Centos 5.2 on my laptop. Unfortunately, this one need at least the version 6.8.0 of the xorg-x11-drv-ati (available in Fedora 9), and this driver need xorg-x11-server-Xorg >= 1.4.99.1 :-(
So, I need to rebuild many things if I want to use centos on my laptop, and I want to use it!
As this is the first time I use Centos, could you tell me which tools I need and how I have to do to rebuild packages that I'll probably take on Fedora 9 mirrors?
Regards, Alain
On Sat, 2008-12-20 at 22:47 +0100, Alain PORTAL wrote:
Hi,
I just installed and fully updated Centos 5.2 on my laptop. Unfortunately, this one need at least the version 6.8.0 of the xorg-x11-drv-ati (available in Fedora 9), and this driver need xorg-x11-server-Xorg >= 1.4.99.1 :-(
Are you sure about that? Most video cards have a VGA compatible mode? Have you tried that? About the only loss is some of the higher resolutions and maybe some performance. The current X11 might be OK if you can use and live with the VGA compatible mode.
So, I need to rebuild many things if I want to use centos on my laptop, and I want to use it!
Might be more work thatn you expect. Will you have to use/build later versions of Gnome/KDE libraries, apps, etc. when the new X11 is installed? Will that require more changes in more underlying things?
My guess would be there's a lot of work there.
As this is the first time I use Centos, could you tell me which tools I need and how I have to do to rebuild packages that I'll probably take on Fedora 9 mirrors?
I don't have the technical knowledge to help you with that. But whenever certain "core" pieces are changed, there's a lot of potential for breakage.
Since CentOS is "enterprise", i.e. stable, not supporting the latest hardware, gets mostly security patches back-ported, CentOS may not be appropriate if you need is for the "latest and greatest".
The more knowledgeable folks on the list suggest another distro for those that do need the "latest and greatest" without as much need for the "enterprise class" stability.
Regards, Alain
<snip sig stuff>
Sorry I can't be more help that that.
Le samedi 20 décembre 2008, William L. Maltby a écrit :
On Sat, 2008-12-20 at 22:47 +0100, Alain PORTAL wrote:
Hi,
I just installed and fully updated Centos 5.2 on my laptop. Unfortunately, this one need at least the version 6.8.0 of the xorg-x11-drv-ati (available in Fedora 9), and this driver need xorg-x11-server-Xorg >= 1.4.99.1 :-(
Are you sure about that?
Unfortunately yes. I was unable to use the graphical install. After installation, I wanted to start X but I got a grey screen, I was unable to switch between ttys using Alt F[1-7], unable to kill X server with Alt-Ctrl-Back and I had to restart the laptop with Ctrl-Alt-Del.
And I got the same grey screen and freeze when I tried to use system-config-display.
Most video cards have a VGA compatible mode? Have you tried that?
Not with centos, but some months ago, I tried even vesa mode with Fedora 9.
About the only loss is some of the higher resolutions and maybe some performance. The current X11 might be OK if you can use and live with the VGA compatible mode.
I can accept lower resolution if I can use X server...
So, I need to rebuild many things if I want to use centos on my laptop, and I want to use it!
Might be more work thatn you expect. Will you have to use/build later versions of Gnome/KDE libraries, apps, etc. when the new X11 is installed?
Current Centos desktops and libraries are enough for me if they can be ran on a new X server.
Will that require more changes in more underlying things?
I don't know.
My guess would be there's a lot of work there.
Sure, if the X server rebuilt imply a near full rebuilt of Centos, this isn't really serious...
As this is the first time I use Centos, could you tell me which tools I need and how I have to do to rebuild packages that I'll probably take on Fedora 9 mirrors?
I don't have the technical knowledge to help you with that. But whenever certain "core" pieces are changed, there's a lot of potential for breakage.
Since CentOS is "enterprise", i.e. stable, not supporting the latest hardware, gets mostly security patches back-ported, CentOS may not be appropriate if you need is for the "latest and greatest".
I don't want the latest and greatest. At home as at the office, I'm under FC6, which isn't supported since more than one year. I tried Fedora 9 (whith difficulties) on my laptop when I buy it, and I could see that I didn't like it (particulary Kde4).
The more knowledgeable folks on the list suggest another distro for those that do need the "latest and greatest" without as much need for the "enterprise class" stability.
I decided to leave Fedora for several reasons, a big one is its too short time life: 13 months is now unacceptable to me;
Sorry I can't be more help that that.
Thanks for yours answers. But I hope I'll get answers about tools and how to build or rebuild from scratch or srpms on Centos because even if I can't install Centos on my laptop, I want to install it on two older computers.
Regards, Alain
Le samedi 20 décembre 2008, William L. Maltby a écrit :
On Sat, 2008-12-20 at 22:47 +0100, Alain PORTAL wrote:
Hi,
I just installed and fully updated Centos 5.2 on my laptop. Unfortunately, this one need at least the version 6.8.0 of the xorg-x11-drv-ati (available in Fedora 9), and this driver need xorg-x11-server-Xorg >= 1.4.99.1 :-(
I reported a bug for people who want to check xorg.conf and Xorg.0.log http://bugs.centos.org/view.php?id=3309
Are you sure about that? Most video cards have a VGA compatible mode? Have you tried that? About the only loss is some of the higher resolutions and maybe some performance. The current X11 might be OK if you can use and live with the VGA compatible mode.
I tried to use the vga driver but the only mode that succeded to run is 320x200.... I can accept low resolution but not a such one ;-)
In the Xorg.0.log, I get many lines as: (II) VGA(0): Not using default mode "800x600" (insufficient memory for mode) (II) VGA(0): Not using default mode "400x300" (insufficient memory for mode)
for a lot of modes, and finally: (II) VGA(0): Not using default mode "1280x800" (insufficient memory for mode) (WW) VGA(0): Mode pool is empty (==) VGA(0): Virtual size is 320x200 (pitch 320) (**) VGA(0): Built-in mode "Generic 320x200 default mode": 12.6 MHz (scaled from 25.2 MHz), 31.5 kHz, 70.2 Hz (VScan) (II) VGA(0): Modeline "Generic 320x200 default mode" 12.59 320 336 384 400 200 206 207 224 vscan 2 -hsync +vsync
Regards, Alain
On Sun, 2008-12-21 at 14:26 +0100, Alain PORTAL wrote:
<snip>
I tried to use the vga driver but the only mode that succeded to run is 320x200.... I can accept low resolution but not a such one ;-)
You ought to be able to get at least VESA stuff.
As root, from a console in run level 3 (telinit 3), try
system-config-display
That _ought_ to get you going.
<snip>
HTH
2008/12/21 William L. Maltby CentOS4Bill@triad.rr.com
On Sun, 2008-12-21 at 14:26 +0100, Alain PORTAL wrote:
<snip>
I tried to use the vga driver but the only mode that succeded to run is 320x200.... I can accept low resolution but not a such one ;-)
You ought to be able to get at least VESA stuff.
As root, from a console in run level 3 (telinit 3), try
system-config-display
That _ought_ to get you going.
<snip>
Alain,
Whilst you are at runlevel 3, please copy & post the output of both /sbin/lspci and /sbin/lspci -n commands that relate to your video card. Apologies if you've already posted this information -- have I missed it?
There should not be any big issue in getting your card operating in VESA mode, as Bill has mentioned.
Alan.
Le dimanche 21 décembre 2008, Alan Bartlett a écrit :
2008/12/21 William L. Maltby CentOS4Bill@triad.rr.com
On Sun, 2008-12-21 at 14:26 +0100, Alain PORTAL wrote:
<snip>
I tried to use the vga driver but the only mode that succeded to run is 320x200.... I can accept low resolution but not a such one ;-)
You ought to be able to get at least VESA stuff.
As root, from a console in run level 3 (telinit 3), try
system-config-display
That _ought_ to get you going.
<snip>
Alain,
Whilst you are at runlevel 3, please copy & post the output of both /sbin/lspci and /sbin/lspci -n commands that relate to your video card. Apologies if you've already posted this information -- have I missed it?
On bug I reported (http://bugs.centos.org/view.php?id=3309) I joined a lspci.txt which is the result of "lspci -s 01:00.0 -vv".
"lspci -s 01:00.0" output: 01:00.0 VGA compatible controller: ATI Technologies Inc M71 [Mobility Radeon X2100] (rev ce)
"lspci -s 01:00.0 -n" output: 01.00.0 0300: 1002:7210 (rev ce)
Regards, Alain
2008/12/21 Alain PORTAL alain.portal@free.fr
Le dimanche 21 décembre 2008, Alan Bartlett a écrit :
Whilst you are at runlevel 3, please copy & post the output of both /sbin/lspci and /sbin/lspci -n commands that relate to your video card. Apologies if you've already posted this information -- have I missed it?
On bug I reported (http://bugs.centos.org/view.php?id=3309) I joined a lspci.txt which is the result of "lspci -s 01:00.0 -vv".
"lspci -s 01:00.0" output: 01:00.0 VGA compatible controller: ATI Technologies Inc M71 [Mobility Radeon X2100] (rev ce)
"lspci -s 01:00.0 -n" output: 01.00.0 0300: 1002:7210 (rev ce)
As I'm not at my home system (and have don't currently have remote access to it), I'll see what I can find out about that device tomorrow. Now the following is from memory -- from a CLI, you could try this command (IIRC):
system-config-display --reconfig --set-resolution=1024x768 --set-depth=24 --set-driver=vesa
You might prefer to boot the system into single-user mode before invoking the above command.
Alan.
Le dimanche 21 décembre 2008, Alan Bartlett a écrit :
As I'm not at my home system (and have don't currently have remote access to it), I'll see what I can find out about that device tomorrow. Now the following is from memory -- from a CLI, you could try this command (IIRC):
system-config-display --reconfig --set-resolution=1024x768 --set-depth=24 --set-driver=vesa
You might prefer to boot the system into single-user mode before invoking the above command.
Change inittab and reboot before typing your s-c-d command. startx failed with this error:
(EE) VESA(0): No matching modes (EE) Screen(s) found, but none have a usable configuration.
It seems that for using the vesa module, I have to build an old style xorg.conf (XFree86.conf ?) with a Section "Monitor" that hold HorizSync and VertRefresh options and that define several ModeLine options, and several Modes options in SubSection "Display" of the Section "Screen".
Like the attachement file of the bug 1862 http://bugs.centos.org/file_download.php?file_id=205&type=bug
However, I don't know how to create these ModeLines, since the XFree86 Video Timings seems very old.
regards, Alain
On Sun, 2008-12-21 at 20:00 +0100, Alain PORTAL wrote:
<snip>
Le dimanche 21 décembre 2008, Alan Bartlett a écrit :
<snip> > following is from memory -- from a CLI, you could try this command (IIRC): > > system-config-display --reconfig --set-resolution=1024x768 --set-depth=24 > --set-driver=vesa > > You might prefer to boot the system into single-user mode before invoking > the above command.
The vga= stuff (if you need to use it) should get you get a virtual screen that you can use for command line stuff. Just remember to convert to decimal if you code a value on you grub menu boot. If you use "vga=ask" (no quotes) you shouldn't need to do it IIRC - it's been a long time since I used it.
OK. Let's try some basics. Get into single-user mode (e.g. telinit 1) or when you boot, grub edit the kernel= line and add a space and a "1" (no quotes) to the end of the line.
If you get to single-user with a boot (adding the " 1" in grub edit mode), alternate consoles will have some stuff of possible value. <CTRL>-<ALT>-<Fx> (where the Fx is function key F1, F2, F3, ...) should switch you to other screens. Also, <ALT>-<RIGHT> or <ALT>-<LEFT> can be used to cycle through. If X has not been started, the <CTRL> can be omitted from that first set I mentioned.
Once you are at the root prompt, do the system-config-display with no parameters. Looking at the alternate consoles while the config is running might be helpful.
If the system finds _any_ driver it can use - e.g. vga, svga, vesa - it should bring up a graphical screen that has a computer icon and some tabs for display, multi-head, etc. There's a couple drop-down menus that let you select resolution, color depth, etc.
Select something not too "heavy" and save the settings and exit.
If only part of the screen is visible, maybe the screen is scrollable? Try moving the mouse off the edge (Hmm. Is the mouse working during this process? I forgot to test that).
1) Can you get/see what I described at all? 2) If you can, and if you make and save changes, you should be able to get to a graphical screen later. BUT FIRST ... 3) At a root prompt, type dmesg | less and look for any messages that might give clues. This might be useful regardless of the results of 2).
Also, there might be useful messages in /var/log/messages and /var/log/Xorg.*.
I don't recall what card you have - nvidia? There might be a solution for that in rpmforge (I don't know how new his latest is - but we can investigate that later if we get a basic operation going for you. Also, nvidia usually has drivers for linux on their site but they don't work as we want for an "enterprise class" system. No rpms, IIRC).
Anyway, back to the main task. If step 2) above seems to have worked, try
telinit 5
if you have anything at all that is working, you should get a graphical login screen running in an X environment. That will give you a working environment, at least, and you can pursue other things.
<snip>
Le dimanche 21 décembre 2008, William L. Maltby a écrit :
If you get to single-user with a boot (adding the " 1" in grub edit mode), alternate consoles will have some stuff of possible value. <CTRL>-<ALT>-<Fx> (where the Fx is function key F1, F2, F3, ...) should switch you to other screens. Also, <ALT>-<RIGHT> or <ALT>-<LEFT> can be used to cycle through. If X has not been started, the <CTRL> can be omitted from that first set I mentioned.
If I start up in single user mode, I get only one console. No switch possible. So I start in run-level 3.
Once you are at the root prompt, do the system-config-display with no parameters. Looking at the alternate consoles while the config is running might be helpful.
If I run system-config-display in, saying tty1, it start successfully. If I switch to tty2, then back to tty1, I don't see the system-config-display dialog any more, just the command I typed before.
If the system finds _any_ driver it can use - e.g. vga, svga, vesa - it should bring up a graphical screen that has a computer icon and some tabs for display, multi-head, etc. There's a couple drop-down menus that let you select resolution, color depth, etc.
Unfortunately, resolution is too low (320x200), so, I can't see the "Cancel" and "Valid" or "OK" button of the system-config-display dialog.
Select something not too "heavy" and save the settings and exit.
If only part of the screen is visible, maybe the screen is scrollable?
Unfortunately not.
Try moving the mouse off the edge (Hmm. Is the mouse working during this process? I forgot to test that).
Mouse is working.
- Can you get/see what I described at all?
- If you can, and if you make and save changes, you should be able to
get to a graphical screen later. BUT FIRST ... 3) At a root prompt, type dmesg | less and look for any messages that might give clues. This might be useful regardless of the results of 2).
Also, there might be useful messages in /var/log/messages and /var/log/Xorg.*.
I don't know if I can post such heavy files here... This is a devel list, not a user one. Xorg.0.log is 38Kb and messages is 435Kb !
I don't recall what card you have - nvidia?
VGA compatible controller: ATI Technologies Inc M71 [Mobility Radeon X2100] (rev ce) (prog-if 00 [VGA controller])
I think now it's a X server problem as it can't compute modelines for vga module. I get, in Xorg.0.log, many lines as: (II) VGA(0): Not using default mode "320x240" (insufficient memory for mode)
Lines differs in mode value
(II) VGA(0): Not using default mode "1920x1200" (insufficient memory for mode)
I know that the 1920x1200 mode is doable.
Regards Alain
Le dimanche 21 décembre 2008, William L. Maltby a écrit :
You ought to be able to get at least VESA stuff.
In xorg.conf, if I replace vga by vesa for driver, and if I try to startx, it failed and I get the following (incomplette) message:
(EE) VESA(0): No matching modes (EE) Screen(s) found, but none have a usable configuration.
As my default xorg.conf was created with pyxf86config, there is no mode neither modelines defined.
As root, from a console in run level 3 (telinit 3), try
I'm in this run level since installation.
system-config-display
I tried this, but as it is running in a 320x200 vga mode, I can't see a lot of things. I think I see less than a quarter of the dialog window.
Regards.
On Sun, 2008-12-21 at 17:11 +0100, Alain PORTAL wrote:
Le dimanche 21 décembre 2008, William L. Maltby a écrit :
You ought to be able to get at least VESA stuff.
In xorg.conf, if I replace vga by vesa for driver, and if I try to startx, it failed and I get the following (incomplette) message:
(EE) VESA(0): No matching modes (EE) Screen(s) found, but none have a usable configuration.
As my default xorg.conf was created with pyxf86config, there is no mode neither modelines defined.
As root, from a console in run level 3 (telinit 3), try
I'm in this run level since installation.
system-config-displayI tried this, but as it is running in a 320x200 vga mode, I can't see a lot of things. I think I see less than a quarter of the dialog window.
Time for extreme measures. At boot prompt, add to the end of the kernel line, via the grub edit facility "vga=ask", IIRC.
I can't find the kernel parameters docs on my system ATM, so this is a guess from memory. Maybe I need kernel development to get those notes?
Anyway, that should give you a list of pre-defined modes, numeric. Google before you do this and get a list of possible ones. I would pick the 1024x768 as a first try. IIRC another is 800x640. There's a 1240x1076(?) I think too.
Regards.
<snip sig stuff>
HTH
On 12/21/08, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Sun, 2008-12-21 at 17:11 +0100, Alain PORTAL wrote:
Le dimanche 21 décembre 2008, William L. Maltby a écrit :
You ought to be able to get at least VESA stuff.
In xorg.conf, if I replace vga by vesa for driver, and if I try to startx, it failed and I get the following (incomplette) message:
(EE) VESA(0): No matching modes (EE) Screen(s) found, but none have a usable configuration.
As my default xorg.conf was created with pyxf86config, there is no mode neither modelines defined.
As root, from a console in run level 3 (telinit 3), try
I'm in this run level since installation.
system-config-displayI tried this, but as it is running in a 320x200 vga mode, I can't see a lot of things. I think I see less than a quarter of the dialog window.
Time for extreme measures. At boot prompt, add to the end of the kernel line, via the grub edit facility "vga=ask", IIRC.
I can't find the kernel parameters docs on my system ATM, so this is a guess from memory. Maybe I need kernel development to get those notes?
Anyway, that should give you a list of pre-defined modes, numeric. Google before you do this and get a list of possible ones. I would pick the 1024x768 as a first try. IIRC another is 800x640. There's a 1240x1076(?) I think too.
IIRC, vga=ask will do it, otherwise pick one like vga=0x317, and it will prompt if invalid. http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
jerry
Le dimanche 21 décembre 2008, Jerry Amundson a écrit :
IIRC, vga=ask will do it, otherwise pick one like vga=0x317, and it will prompt if invalid. http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
Work fine during startup, but same problem (graphical only 1/10 height at the top of the screen) when I startx;
Regards, Alain
On Sun, 2008-12-21 at 19:14 +0100, Alain PORTAL wrote:
Le dimanche 21 décembre 2008, Jerry Amundson a écrit :
IIRC, vga=ask will do it, otherwise pick one like vga=0x317, and it will prompt if invalid. http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
Work fine during startup, but same problem (graphical only 1/10 height at the top of the screen) when I startx;
Decimal value s/b 791 I think.
Regards, Alain
On Sun, 2008-12-21 at 11:55 -0500, William L. Maltby wrote:
<snip>
Time for extreme measures. At boot prompt, add to the end of the kernel line, via the grub edit facility "vga=ask", IIRC.
I can't find the kernel parameters docs on my system ATM, so this is a guess from memory. Maybe I need kernel development to get those notes?
Anyway, that should give you a list of pre-defined modes, numeric. Google before you do this and get a list of possible ones. I would pick the 1024x768 as a first try. IIRC another is 800x640. There's a 1240x1076(?) I think too.
I did a little googling. One post said that you should be able to go into BIOS setup and set a default set of values that will get you going.
Another, http://www.mepis.org/node/2992 , has a small table of the standard codes.
<snip>
On Sun, 2008-12-21 at 12:16 -0500, William L. Maltby wrote:
<snip>
Another, http://www.mepis.org/node/2992 , has a small table of the standard codes.
This one http://wiki.antlinux.com/pmwiki.php?n=HowTos.VgaModes looks more useful to me.
Le dimanche 21 décembre 2008, William L. Maltby a écrit :
I tried this, but as it is running in a 320x200 vga mode, I can't see a lot of things. I think I see less than a quarter of the dialog window.
Time for extreme measures.
Perhaps I didn't speak english well and I don't know if I was understood for that. I wanted to say I saw 1/4 of the size of the s-c-d window; Or you did a joke I didn't understood
At boot prompt, add to the end of the kernel line, via the grub edit facility "vga=ask", IIRC.
I can't find the kernel parameters docs on my system ATM, so this is a guess from memory. Maybe I need kernel development to get those notes?
Anyway, that should give you a list of pre-defined modes, numeric. Google before you do this and get a list of possible ones. I would pick the 1024x768 as a first try. IIRC another is 800x640. There's a 1240x1076(?) I think too.
I did what you said, but it seems I didn't get the expected results:
Video adapter: VESA VGA Mode: COLSxROWS: 0 0F00 80x25 1 0F01 80x50 2 0F02 80x43 3 0F03 80x28 4 0F05 80x30 5 0F06 80x34 6 0F07 80x60
So, no graphic mode as I could find by googling http://tldp.org/HOWTO/Framebuffer-HOWTO-5.html
If I use, as an example, vga=0x307, when I startx, I can see saying 4 desktops on the width of the screen and height of these desktop are only 1/10 height on the screen, at the top of it So, 9/10 of the screen is black.
Regards, Alain
On Sun, 2008-12-21 at 19:02 +0100, Alain PORTAL wrote:
Le dimanche 21 décembre 2008, William L. Maltby a écrit :
I tried this, but as it is running in a 320x200 vga mode, I can't see a lot of things. I think I see less than a quarter of the dialog window.
Time for extreme measures.
Perhaps I didn't speak english well and I don't know if I was understood for that. I wanted to say I saw 1/4 of the size of the s-c-d window; Or you did a joke I didn't understood
No joke meant. I understood you - you're doing fine with the English.
At boot prompt, add to the end of the kernel line, via the grub edit facility "vga=ask", IIRC.
I can't find the kernel parameters docs on my system ATM, so this is a guess from memory. Maybe I need kernel development to get those notes?
Anyway, that should give you a list of pre-defined modes, numeric. Google before you do this and get a list of possible ones. I would pick the 1024x768 as a first try. IIRC another is 800x640. There's a 1240x1076(?) I think too.
I did what you said, but it seems I didn't get the expected results:
Video adapter: VESA VGA Mode: COLSxROWS: 0 0F00 80x25 1 0F01 80x50 2 0F02 80x43 3 0F03 80x28 4 0F05 80x30 5 0F06 80x34 6 0F07 80x60
Those are good. But now that I see them I remember that they are for virtual consoles. I don't recall that they would affect the system-config-display actions.
Regardless, you can pick one at boot time if "vga=ask" (without the quotes) and you'll see different character sizes. If you code "vga=xxx", where the "xxx" is one of those codes, they must be converted to decimal first. One of those links I posted later has a link to how to do that.
But, as I mentioned, I now don't think this will affect the X setup.
So, no graphic mode as I could find by googling http://tldp.org/HOWTO/Framebuffer-HOWTO-5.html
This link only has effect if you're using framebuffer. That's (IIRC) optional - I have it on my 4.x system, but I set it up a long time ago and would have to research to recall the details. It gave a nice speed improvement.
Anyway, it's not mandatory. If you want to use it, more setup steps are needed. I would skip it now and continue what you're doing - get a basic acceptable setup running.
If I use, as an example, vga=0x307, when I startx, I can see saying 4 desktops
As I mention above, I think the hexadecimal needs to be converted to decimal. It's been a _long_ time, but I _think_ 0x307 = 775 decimal. But I don't remember if that value is big-endian or little-endian. Big, I think.
on the width of the screen and height of these desktop are only 1/10 height on the screen, at the top of it So, 9/10 of the screen is black.
Regards, Alain
I saw that another posted some parameters to try with system-config-display. I'm going to peek at that and see what else I might offer.
I might save my configs and play with system-config-display a bit and see if any clues pop up.
Le dimanche 21 décembre 2008, William L. Maltby a écrit :
I did what you said, but it seems I didn't get the expected results:
Video adapter: VESA VGA Mode: COLSxROWS: 0 0F00 80x25 1 0F01 80x50 2 0F02 80x43 3 0F03 80x28 4 0F05 80x30 5 0F06 80x34 6 0F07 80x60
Those are good. But now that I see them I remember that they are for virtual consoles. I don't recall that they would affect the system-config-display actions.
Regardless, you can pick one at boot time if "vga=ask" (without the quotes) and you'll see different character sizes. If you code "vga=xxx", where the "xxx" is one of those codes, they must be converted to decimal first. One of those links I posted later has a link to how to do that.
But, as I mentioned, I now don't think this will affect the X setup.
No, it don't affect.
So, no graphic mode as I could find by googling http://tldp.org/HOWTO/Framebuffer-HOWTO-5.html
This link only has effect if you're using framebuffer. That's (IIRC) optional - I have it on my 4.x system, but I set it up a long time ago and would have to research to recall the details. It gave a nice speed improvement.
I found several links: http://www.tkk.fi/Misc/Electronics/faq/vga2rgb/calc.html http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
Unfortunately, I can't find the dot clock for the driver as I can't find the video controller model "ATI Technologies Inc M71 [Mobility Radeon X2100]" on the ATI website :-(
Anyway, it's not mandatory. If you want to use it, more setup steps are needed. I would skip it now and continue what you're doing - get a basic acceptable setup running.
If I use, as an example, vga=0x307, when I startx, I can see saying 4 desktops
As I mention above, I think the hexadecimal needs to be converted to decimal. It's been a _long_ time, but I _think_ 0x307 = 775 decimal. But I don't remember if that value is big-endian or little-endian. Big, I think.
Both notations, decimal and hexadecimal, are allowed.
on the width of the screen and height of these desktop are only 1/10 height on the screen, at the top of it So, 9/10 of the screen is black.
Regards, Alain
I saw that another posted some parameters to try with system-config-display. I'm going to peek at that and see what else I might offer.
I might save my configs and play with system-config-display a bit and see if any clues pop up.
Thanks!
Alain
Le dimanche 21 décembre 2008, Matej Cepl a écrit :
On 2008-12-21, 16:11 GMT, Alain PORTAL wrote:
In xorg.conf, if I replace vga by vesa for driver, and if I try to startx, =
Just remove xorg.conf and restart X. What happens?
X failed to start. Here is some piece of Xorg.0.log
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 22 18:46:20 2008 (EE) Unable to locate/open config file
(II) PCI: 01:00:0: chip 1002,7210 card 10f7,8338 rev ce class 03,00,00 hdr 00
(--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x7210) rev 206, Mem @ 0xe0000000/28, 0xd7ef0000/16, I/O @ 0x2000/8 New driver is "ati" (==) Using default built-in configuration (55 lines) (==) --- Start of built-in configuration --- Section "Module" Load "extmod" Load "dbe" Load "glx" Load "freetype" Load "type1" Load "record" Load "dri" EndSection Section "Monitor" Identifier "Builtin Default Monitor" EndSection Section "Device" Identifier "Builtin Default ati Device 0" Driver "ati" EndSection Section "Screen" Identifier "Builtin Default ati Screen 0" Device "Builtin Default ati Device 0" Monitor "Builtin Default Monitor" EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" Monitor "Builtin Default Monitor" EndSection Section "Device" Identifier "Builtin Default vesa Device 0" Driver "vesa" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 0" Device "Builtin Default vesa Device 0" Monitor "Builtin Default Monitor" EndSection Section "Device" Identifier "Builtin Default vga Device 0" Driver "vga" EndSection Section "Screen" Identifier "Builtin Default vga Screen 0" Device "Builtin Default vga Device 0" Monitor "Builtin Default Monitor" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default ati Screen 0" Screen "Builtin Default fbdev Screen 0" Screen "Builtin Default vesa Screen 0" Screen "Builtin Default vga Screen 0" EndSection (==) --- End of built-in configuration --- (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default ati Screen 0" (0) (**) | |-->Monitor "Builtin Default Monitor" (**) | |-->Device "Builtin Default ati Device 0" (**) |-->Screen "Builtin Default fbdev Screen 0" (1) (**) | |-->Monitor "Builtin Default Monitor" (**) | |-->Device "Builtin Default fbdev Device 0" (**) |-->Screen "Builtin Default vesa Screen 0" (2) (**) | |-->Monitor "Builtin Default Monitor" (**) | |-->Device "Builtin Default vesa Device 0" (**) |-->Screen "Builtin Default vga Screen 0" (3) (**) | |-->Monitor "Builtin Default Monitor" (**) | |-->Device "Builtin Default vga Device 0" (==) |-->Input Device "<default pointer>" (==) |-->Input Device "<default keyboard>"
(II) LoadModule: "dri" (II) Loading /usr/lib64/xorg/modules/extensions/libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/lib64/xorg/modules/linux/libdrm.so (II) Module drm: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) Loading extension XFree86-DRI (II) LoadModule: "ati" (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so (II) Module ati: vendor="X.Org Foundation" compiled for 7.1.1, module version = 6.6.3 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.0 (II) LoadModule: "fbdev" (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so (II) Module fbdev: vendor="X.Org Foundation" compiled for 7.1.1, module version = 0.3.0 ABI class: X.Org Video Driver, version 1.0 (II) LoadModule: "vesa" (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so (II) Module vesa: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.3.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.0 (II) LoadModule: "vga" (II) Loading /usr/lib64/xorg/modules/drivers/vga_drv.so (II) Module vga: vendor="X.Org Foundation" compiled for 7.1.1, module version = 4.1.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.0
(II) ATI: ATI driver (version 6.6.3) for chipsets: ati, ativga
(II) FBDEV: driver for framebuffer: fbdev (II) VESA: driver for VESA chipsets: vesa (II) VGA: Generic VGA driver (version 4.1) for chipsets: generic (II) Primary Device is: PCI 01:00:0 (II) ATI: Candidate "Device" section "Builtin Default ati Device 0". (--) Assigning device section with no busID to primary device (--) Assigning device section with no busID to primary device (II) Loading sub module "fbdevhw" (II) LoadModule: "fbdevhw" (II) Loading /usr/lib64/xorg/modules/linux/libfbdevhw.so (II) Module fbdevhw: vendor="X.Org Foundation" compiled for 7.1.1, module version = 0.0.2 ABI class: X.Org Video Driver, version 1.0 (EE) open /dev/fb0: No such file or directory (--) Assigning device section with no busID to primary device (--) Chipset vesa found (II) resource ranges after xf86ClaimFixedResources() call:
(--) Assigning device section with no busID to primary device (--) Chipset generic found (II) resource ranges after probing:
(II) Setting vga for screen 0. (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/lib64/xorg/modules/libvbe.so (II) Module vbe: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.1.0 ABI class: X.Org Video Driver, version 1.0 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/lib64/xorg/modules/libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (II) VESA(0): initializing int10 (II) VESA(0): Primary V_BIOS segment is: 0xc000 (II) VESA(0): VESA BIOS detected (II) VESA(0): VESA VBE Version 3.0 (II) VESA(0): VESA VBE Total Mem: 16384 kB (II) VESA(0): VESA VBE OEM: ATI ATOMBIOS (II) VESA(0): VESA VBE OEM Software Rev: 9.13 (II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc. (II) VESA(0): VESA VBE OEM Product: M71M (II) VESA(0): VESA VBE OEM Product Rev: 01.00 (II) VESA(0): Creating default Display subsection in Screen section "Builtin Default vesa Screen 0" for depth/fbbpp 16/16 (==) VESA(0): Depth 16, (--) framebuffer bpp 16 (==) VESA(0): RGB weight 565 (==) VESA(0): Default visual is TrueColor (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0) (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/lib64/xorg/modules/libddc.so (II) Module ddc: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (II) VESA(0): VESA VBE DDC unkown failure 768 (II) VESA(0): Searching for matching VESA mode(s): Mode: 100 (640x400) .... A long list of modes .... Mode: 1e6 (1920x1440)
(II) VESA(0): Total Memory: 256 64KB banks (16384kB) (EE) VESA(0): No matching modes (II) UnloadModule: "vesa" (II) UnloadModule: "ddc" (II) Unloading /usr/lib64/xorg/modules/libddc.so (II) UnloadModule: "int10" (II) Unloading /usr/lib64/xorg/modules/libint10.so (II) UnloadModule: "vbe" (II) Unloading /usr/lib64/xorg/modules/libvbe.so (EE) Screen(s) found, but none have a usable configuration.
Fatal server error: no screens found
Regards, Alain
On 2008-12-22, 18:24 GMT, Alain PORTAL wrote:
Just remove xorg.conf and restart X. What happens?
X failed to start. Here is some piece of Xorg.0.log
(=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 22 18:46:20 2008 (EE) Unable to locate/open config file
This is weird ... isn't there something weird about your configuration? NFS, SELinux, screwed up rights on /var/log -- I have never seen the error like this.
(--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x7210) rev 206, Mem
I talked with Dave Airlie about this and his conclusion was that most likely RHEL/CentOS 5.2 won't work with your card, but 5.3 should. If you are willing to try Beta, then it should be available from ftp://ftp.redhat.com/pub/redhat/linux/beta/RHEL5.3/
(of course, there is no support, it is beta, no upgrades, yadayadayada). For more information see announcement at https://www.redhat.com/archives/rhelv5-announce/2008-October/msg00000.html (it should be released January 2009).
Best,
Matěj Cepl
Le lundi 22 décembre 2008, Matej Cepl a écrit :
On 2008-12-22, 18:24 GMT, Alain PORTAL wrote:
Just remove xorg.conf and restart X. What happens?
X failed to start. Here is some piece of Xorg.0.log
(=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 22 18:46:20 2008 (EE) Unable to locate/open config file
This is weird ...
Why? It seems to me meanful. X server don't find xorg.conf, so, it build one in the fly
isn't there something weird about your configuration? NFS, SELinux, screwed up rights on /var/log --
Nothing special as I just did a basic install, update via yum, and try to start X. No more setup.
I have never seen the error like this.
All happens ;-)
(--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x7210) rev 206, Mem
I talked with Dave Airlie about this and his conclusion was that most likely RHEL/CentOS 5.2 won't work with your card, but 5.3 should. If you are willing to try Beta, then it should be available from ftp://ftp.redhat.com/pub/redhat/linux/beta/RHEL5.3/
Yes, of course, but how do I do to install?
Regards, Alain
Alain PORTAL wrote:
Why? It seems to me meanful. X server don't find xorg.conf, so, it build one in the fly
This conversation is very offtopic here, please take it to the centos@centos.org list. There is no centos development related issue here at all.
On 2008-12-22, 21:56 GMT, Alain PORTAL wrote:
I talked with Dave Airlie about this and his conclusion was that most likely RHEL/CentOS 5.2 won't work with your card, but 5.3 should. If you are willing to try Beta, then it should be available from ftp://ftp.redhat.com/pub/redhat/linux/beta/RHEL5.3/
Yes, of course, but how do I do to install?
I am sorry, silly me, I have never dealt with our public beta offerings (of course, having access to the internal servers, I haven't needed to), so I didn't even know, that this beta is not public.
Sorry,
Matěj
Matej Cepl wrote:
I am sorry, silly me, I have never dealt with our public beta offerings (of course, having access to the internal servers, I haven't needed to), so I didn't even know, that this beta is not public.
( this is not personally about you or something for you - but a more general statement about policy as it exists these days )
Since the beta is not available, the product is, in this case, potentially loosing a willing and motivated tester :/
But, thanks for looking into centos-devel list.
- KB
On 12/23/08, Karanbir Singh mail-lists@karan.org wrote:
Matej Cepl wrote:
I am sorry, silly me, I have never dealt with our public beta offerings (of course, having access to the internal servers, I haven't needed to), so I didn't even know, that this beta is not public.
( this is not personally about you or something for you - but a more general statement about policy as it exists these days )
Since the beta is not available, the product is, in this case, potentially loosing a willing and motivated tester :/
I'd go so far as stating *is* loosing *many* testers.
But, thanks for looking into centos-devel list.
ditto.
jerry
Le mardi 23 décembre 2008, Matej Cepl a écrit :
I am sorry, silly me, I have never dealt with our public beta offerings (of course, having access to the internal servers, I haven't needed to), so I didn't even know, that this beta is not public.
There is no problem ;-) This is just too bad that I can test it before official release.
Regards, Alain
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alain PORTAL wrote:
So, I need to rebuild many things if I want to use centos on my laptop, and I want to use it!
Getting Centos to support all the weird hardware in my laptop was too much trouble with Centos. So the laptop runs Fedora. But all other systems run Centos 4 or 5.
Hugo.
- -- hvdkooij@vanderkooij.org http://hugo.vanderkooij.org/ PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc
A: Yes. >Q: Are you sure? >>A: Because it reverses the logical flow of conversation. >>>Q: Why is top posting frowned upon?
Bored? Click on http://spamornot.org/ and rate those images.
Nid wyf yn y swyddfa ar hyn o bryd. Anfonwch unrhyw waith i'w gyfieithu.
On Sun, 21 Dec 2008, Hugo van der Kooij wrote:
Alain PORTAL wrote:
So, I need to rebuild many things if I want to use centos on my laptop, and I want to use it!
Getting Centos to support all the weird hardware in my laptop was too much trouble with Centos. So the laptop runs Fedora. But all other systems run Centos 4 or 5.
I have a very recent laptop (Thinkpad X200s) and I noticed that Red Hat backports video drivers from newer Xorg versions to the one they ship. So even if web-pages say you need at least version Y, it is possible that you can still make it work with version X.
You also have the possibility to make it work in VESA or framebuffer mode until the support is added in the future. For a list of things that are coming up in CentOS 5.3, see:
https://www.redhat.com/archives/rhelv5-announce/2008-October/msg00000.html
As an example all websites say that my very recent wireless card (IWL AGN5300) is only supported by kernel 2.6.26+, but in the upcoming CentOS 5.3 it works on a 2.6.18-210.el5 or newer kernel thanks to the efforts of Red Hat.
My built-in camera requires the uvcvideo driver which is also part of 2.6.24+, while Red Hat backported the driver to the 2.6.18-210.el5 or newer kernel.
What I can say is that CentOS 5.3 (due in roughly 2 months) will have a lot of new driver support for recent hardware. And you can already test the upcoming kernels from:
http://people.redhat.com/dzickus/el5/
Also, if you have Red Hat Network access, you can download the RHEL 5.3 Beta Xorg drivers to test your hardware.
You can see my experience installing CentOS 5 on this laptop from the following wiki page:
http://wiki.centos.org/HowTos/Laptops/Lenovo/Thinkpad-X200s
BTW What video chipset do you have exactly ?
Good luck,
On 2008-12-20, 21:47 GMT, Alain PORTAL wrote:
I just installed and fully updated Centos 5.2 on my laptop. Unfortunately, this one need at least the version 6.8.0 of the=20 xorg-x11-drv-ati (available in Fedora 9), and this driver need=20 xorg-x11-server-Xorg >=3D 1.4.99.1 :-(
I think basically you need to rebuild all xorg-x11* packages plus whatever they depend on (mainly from lib* packages). And you would need to stay with F9 packages, because for F10 you would also need new kernel. It is a huge undertaking and I am not sure whether it is worthy of the effort.
So, I need to rebuild many things if I want to use centos on my laptop, and I want to use it!
Strictly speaking that's not correct. You have two more options:
a) To stick with CentOS and when on CentOS do as CentOS people do -- that is use vesa driver (system-config-display and set vesa driver). Of course, you won't have 3D, compiz and similar shiny stuff, but it should work pretty reliably for applications which don't need this (which is most of them).
Actually, what happens when you move /etc/X11/xorg.conf away and restart X? At least since Fedora 6 (i.e., pre-RHEL5 days) it is considered a bug when Xorg without xorg.conf won't start in a working state.
b) Of course, least painful solution is probably to try Fedora 10 -- I fully understand that you want to have CentOS for stability, but well, this is a desktop, and you should be able to get support until (hopefully) RHEL6 will be out.
Best,
Matěj
Le dimanche 21 décembre 2008, Matej Cepl a écrit :
Strictly speaking that's not correct. You have two more options:
a) To stick with CentOS and when on CentOS do as CentOS people do -- that is use vesa driver (system-config-display and set vesa driver).
As you probably see in the discussion, only vga 320x200 mode work.
Of course, you won't have 3D, compiz and similar shiny stuff, but it should work pretty reliably for applications which don't need this (which is most of them).
I don't need all theses stuffs.
Actually, what happens when you move /etc/X11/xorg.conf away and restart X? At least since Fedora 6 (i.e., pre-RHEL5 days) it is considered a bug when Xorg without xorg.conf won't start in a working state.
X try to start but failed.
b) Of course, least painful solution is probably to try Fedora 10 -- I fully understand that you want to have CentOS for stability, but well, this is a desktop, and you should be able to get support until (hopefully) RHEL6 will be out.
After some bug reports and fixes, I succeed to use Fedora 9
Do you know when RHEL6 release is planned?
Regards, Alain
-
Alain PORTAL -
Alan Bartlett -
Dag Wieers -
Hugo van der Kooij -
Jerry Amundson -
Karanbir Singh -
Karanbir Singh -
Matej Cepl -
William L. Maltby