Re: [elrepo] Intel VGA Controller
Hello Earl, It sounds like you have a PowerVR GMA3650 GPU from Imagination Technolgies. I have had many problems with this GPU in distribution kernels and had to upgrade (using EL Repo made it easy). Try appending video=LVDS-1:d to the kernel line in your grub.conf file. After that you should get a graphic boot screen and use the fbdev or vesa driver. I had no luck with the Intel driver and this GPU. Regards, Antonio On Tue, Jan 15, 2013 at 10:24 AM, Alan Bartlett wrote: > Hi Earl, > > On 15 January 2013 14:15, Earl A Ramirez wrote: > > > > I have booted into run level 3 and invoke startx, however I do not see > any > > errors because the screen goes blank with the dash on the top left > corner of > > the screen. > > O.k. So that definitely confirms a problem with the 'X' server > configuration or the drivers available for your video chipset. (Which > is not my area of expertise.) > > > Below is the content of the Xorg.5.log after I have booted with the stock > > CentOS kernel. > > That may show something useful . . . perhaps others would care to comment? > > What it does do is to give you a template for an xorg.conf file that > you could hand-craft and drop into the /etc/X11/xorg.conf.d/ > directory. > > [code] > > [44.640] Section "Device" > > [44.640] Identifier"Builtin Default intel Device 0" > > [44.640] Driver"intel" > > [44.640] EndSection > > [44.640] Section "Screen" > > [44.640] Identifier"Builtin Default intel Screen 0" > > [44.640] Device"Builtin Default intel Device 0" > > [44.640] EndSection > > [44.640] Section "Device" > > [44.640] Identifier"Builtin Default vesa Device 0" > > [44.641] Driver"vesa" > > [44.641] EndSection > > [44.641] Section "Screen" > > [44.641] Identifier"Builtin Default vesa Screen 0" > > [44.641] Device"Builtin Default vesa Device 0" > > [44.641] EndSection > > [44.641] Section "Device" > > [44.641] Identifier"Builtin Default fbdev Device 0" > > [44.641] Driver"fbdev" > > [44.641] EndSection > > [44.641] Section "Screen" > > [44.641] Identifier"Builtin Default fbdev Screen 0" > > [44.641] Device"Builtin Default fbdev Device 0" > > [44.641] EndSection > > [44.641] Section "ServerLayout" > > [44.641] Identifier"Builtin Default Layout" > > [44.641] Screen"Builtin Default intel Screen 0" > > [44.641] Screen"Builtin Default vesa Screen 0" > > [44.641] Screen"Builtin Default fbdev Screen 0" > > [44.641] EndSection > [/code] > > Copy / paste the above section into a file and the strip off the "> [ > 44.640] " or "> [44.641] " (as appropriate) that is at > the beginning of each line. That will then be your basic template > xorg.conf file. (Keep a pristine copy safe, somewhere else.) Hopefully > other subscribers to this list will be able to suggest lines to add to > or remove from your working copy. (/etc/X11/xord.conf.d/xorg.conf) It > should be possible to get that basic display to work in graphical mode > by that method. (I'm not the person able to assist you, > unfortunately.) > > > I am not too familiar with the RFE process can you shed some light on > this > > or point me in the right direction? > > As for opening an RFE (request for enhancement), just go to the ELRepo > bug tracker [1], open a ticket against the existing xorg-x11-drv-intel > package and ask for it to be updated to the latest version. Etc. :) > > There's no magic involved. By making the request that way, you will > ensure that it is seen by all the Admin staff and the current package > maintainer. > > @ELRepo Project community members -- Please join in if you feel you > can assist Earl with getting a working basic graphical interface with > his system > > Alan. > > [1] http://elrepo.org/bugs/main_page.php > ___ > elrepo mailing list > elrepo@lists.elrepo.org > http://lists.elrepo.org/mailman/listinfo/elrepo > ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
Re: [elrepo] problem building kmod-wl on Centos6.3 with Elrepo-kernel-ml.De
Hi Johan, On 14 January 2013 11:23, Johan Vermeulen wrote: > > I was able to build the wl-kmod with the latest Centos standard kernel > successfully, and I will follow your advise and use this kernel on our > machines. That is good news. Thank you for sharing. The wl-kmod*nosrc.rpm package that we provide (blame Broadcom for their ridiculous licensing of their source tarball) has generated the kmod-wl*rpm package which should now survive future kernel updates. > I did however first wanted to test the updated Elrepo-ml-kernel: > > Linux localhost.localdomain 3.7.2-1.el6.elrepo.x86_64 #1 SMP Fri Jan 11 > 21:38:01 EST 2013 x86_64 x86_64 x86_64 GNU/Linux > [root@localhost ~]# Understood. > I again tried building the wl kmod module with the same wl-kmod-nosrc.rpm > and the same hybrid-prtsrc...tar.gz ( that didn't change, did it? ) No change -- as far as I am aware, Broadcom have not released a newer source tarball. [1] Everything is fine up to this point: > CC [M] > /home/caw/rpmbuild/BUILD/wl-kmod-5_100_82_112/src/wl/sys/wl_linux.o > /home/caw/rpmbuild/BUILD/wl-kmod-5_100_82_112/src/wl/sys/wl_linux.c:43:24: > error: asm/system.h: No such file or directory I stop looking at the output once the first error message is seen. I have experimented . . . [quote] [ajb@Duo2 kernels]$ pwd /usr/src/kernels [ajb@Duo2 kernels]$ ls -1 2.6.32-279.19.1.el6.x86_64 3.0.58-1.el6.elrepo.x86_64 3.7.2-1.el6.elrepo.x86_64 [ajb@Duo2 kernels]$ find -type f -name system.h | sort ./2.6.32-279.19.1.el6.x86_64/arch/x86/include/asm/system.h ./2.6.32-279.19.1.el6.x86_64/include/asm-generic/system.h ./3.0.58-1.el6.elrepo.x86_64/arch/x86/include/asm/system.h ./3.0.58-1.el6.elrepo.x86_64/include/asm-generic/system.h [ajb@Duo2 kernels]$ [/quote] Hmm. A possible error in the kernel-ml-devel building process? The experiments continued . . . [quote] [ajb@Build64R6 tmp]$ ll total 81836 -rw-rw-r--. 1 ajb ajb 135396 Jan 14 21:16 config-3.7.2-x86_64 drwxrwxr-x. 24 ajb ajb 4096 Jan 14 21:32 linux-3.7.2 -rw-rw-r--. 1 ajb ajb 83625776 Jan 14 21:08 linux-3.7.2.tar.bz2 drwxrwxr-x. 5 ajb ajb 4096 Jan 14 21:35 v5_100_82_112 [ajb@Build64R6 tmp]$ [/quote] I had the extracted Linux kernel source into the 'linux-3.7.2' directory. The 'config-3.7.2-x86_64' file was copied into that directory as '.conf'. The following sequence was performed: 'make silentoldconfig; make bzImage; make prepare'. I had extracted the Broadcom sources into the 'v5_100_82_112' directory. The Broadcom 'Makefile' was edited, replacing all references to '/lib/modules/`uname -r`/build' with the explict full pathname to the 'linux-3.7.2' directory. Here follows what I subsequently observed . . . [quote] [ajb@Build64R6 v5_100_82_112]$ make clean KBUILD_NOPEDANTIC=1 make -C /home/ajb/tmp/linux-3.7.2 M=`pwd` clean make[1]: Entering directory `/home/ajb/tmp/linux-3.7.2' Wireless Extension is the only possible API for this kernel version Using Wireless Extension API make[1]: Leaving directory `/home/ajb/tmp/linux-3.7.2' [ajb@Build64R6 v5_100_82_112]$ make KBUILD_NOPEDANTIC=1 make -C /home/ajb/tmp/linux-3.7.2 M=`pwd` make[1]: Entering directory `/home/ajb/tmp/linux-3.7.2' Wireless Extension is the only possible API for this kernel version Using Wireless Extension API LD /home/ajb/tmp/v5_100_82_112/built-in.o CC [M] /home/ajb/tmp/v5_100_82_112/src/shared/linux_osl.o CC [M] /home/ajb/tmp/v5_100_82_112/src/wl/sys/wl_linux.o /home/ajb/tmp/v5_100_82_112/src/wl/sys/wl_linux.c:43:24: error: asm/system.h: No such file or directory /home/ajb/tmp/v5_100_82_112/src/wl/sys/wl_linux.c:388: error: unknown field ‘ndo_set_multicast_list’ specified in initializer /home/ajb/tmp/v5_100_82_112/src/wl/sys/wl_linux.c:388: warning: initialization from incompatible pointer type make[2]: *** [/home/ajb/tmp/v5_100_82_112/src/wl/sys/wl_linux.o] Error 1 make[1]: *** [_module_/home/ajb/tmp/v5_100_82_112] Error 2 make[1]: Leaving directory `/home/ajb/tmp/linux-3.7.2' make: *** [all] Error 2 [ajb@Build64R6 v5_100_82_112]$ [/quote] And there is the same error: "/home/ajb/tmp/v5_100_82_112/src/wl/sys/wl_linux.c:43:24: error: asm/system.h: No such file or directory" Which pleases me. For it confirms that there is no mishap in the building of the kernel-ml-devel package. Let's see what 'system.h' files exist in the Linux kernel source tree . . . [quote] [ajb@Build64R6 v5_100_82_112]$ cd ../linux-3.7.2 [ajb@Build64R6 linux-3.7.2]$ find -type f -name system.h | sort ./arch/arm/include/asm/system.h ./arch/arm/mach-gemini/include/mach/system.h ./arch/arm/mach-shmobile/include/mach/system.h ./arch/cris/include/arch-v10/arch/system.h ./arch/cris/include/arch-v32/arch/system.h ./arch/mips/include/asm/dec/system.h ./tools/perf/util/include/asm/system.h ./tools/power/cpupower/bench/system.h [ajb@Build64R6 linux-3.7.2]$ [/quote] A few. But none relevant to our x86 architecture. So my conclusion is that the kernel-ml package is too new for the Broadcom source package . . . which is another wa
Re: [elrepo] Intel VGA Controller
Hi Earl, On 15 January 2013 14:15, Earl A Ramirez wrote: > > I have booted into run level 3 and invoke startx, however I do not see any > errors because the screen goes blank with the dash on the top left corner of > the screen. O.k. So that definitely confirms a problem with the 'X' server configuration or the drivers available for your video chipset. (Which is not my area of expertise.) > Below is the content of the Xorg.5.log after I have booted with the stock > CentOS kernel. That may show something useful . . . perhaps others would care to comment? What it does do is to give you a template for an xorg.conf file that you could hand-craft and drop into the /etc/X11/xorg.conf.d/ directory. [code] > [44.640] Section "Device" > [44.640] Identifier"Builtin Default intel Device 0" > [44.640] Driver"intel" > [44.640] EndSection > [44.640] Section "Screen" > [44.640] Identifier"Builtin Default intel Screen 0" > [44.640] Device"Builtin Default intel Device 0" > [44.640] EndSection > [44.640] Section "Device" > [44.640] Identifier"Builtin Default vesa Device 0" > [44.641] Driver"vesa" > [44.641] EndSection > [44.641] Section "Screen" > [44.641] Identifier"Builtin Default vesa Screen 0" > [44.641] Device"Builtin Default vesa Device 0" > [44.641] EndSection > [44.641] Section "Device" > [44.641] Identifier"Builtin Default fbdev Device 0" > [44.641] Driver"fbdev" > [44.641] EndSection > [44.641] Section "Screen" > [44.641] Identifier"Builtin Default fbdev Screen 0" > [44.641] Device"Builtin Default fbdev Device 0" > [44.641] EndSection > [44.641] Section "ServerLayout" > [44.641] Identifier"Builtin Default Layout" > [44.641] Screen"Builtin Default intel Screen 0" > [44.641] Screen"Builtin Default vesa Screen 0" > [44.641] Screen"Builtin Default fbdev Screen 0" > [44.641] EndSection [/code] Copy / paste the above section into a file and the strip off the "> [ 44.640] " or "> [44.641] " (as appropriate) that is at the beginning of each line. That will then be your basic template xorg.conf file. (Keep a pristine copy safe, somewhere else.) Hopefully other subscribers to this list will be able to suggest lines to add to or remove from your working copy. (/etc/X11/xord.conf.d/xorg.conf) It should be possible to get that basic display to work in graphical mode by that method. (I'm not the person able to assist you, unfortunately.) > I am not too familiar with the RFE process can you shed some light on this > or point me in the right direction? As for opening an RFE (request for enhancement), just go to the ELRepo bug tracker [1], open a ticket against the existing xorg-x11-drv-intel package and ask for it to be updated to the latest version. Etc. :) There's no magic involved. By making the request that way, you will ensure that it is seen by all the Admin staff and the current package maintainer. @ELRepo Project community members -- Please join in if you feel you can assist Earl with getting a working basic graphical interface with his system Alan. [1] http://elrepo.org/bugs/main_page.php ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
Re: [elrepo] Intel VGA Controller
On 15 January 2013 01:00, wrote: > Send elrepo mailing list submissions to > elrepo@lists.elrepo.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.elrepo.org/mailman/listinfo/elrepo > or, via email, send a message with subject or body 'help' to > elrepo-requ...@lists.elrepo.org > > You can reach the person managing the list at > elrepo-ow...@lists.elrepo.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of elrepo digest..." > > > Today's Topics: > >1. Re: Intel VGA Controller (Alan Bartlett) >2. Re: problem building kmod-wl on Centos6.3 with > Elrepo-kernel-ml.De (Johan Vermeulen) > > > -- > > Message: 1 > Date: Sun, 13 Jan 2013 18:17:30 + > From: Alan Bartlett > To: EL Repo General Mailing List > Subject: Re: [elrepo] Intel VGA Controller > Message-ID: > r5p1...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On 13 January 2013 13:55, Earl A Ramirez wrote: > > Good Day All, > > > > I have installed CentOS 6.3 on an ASUS EeePc netbook and the only driver > > that I am missing is the VGA controllers for the following graphics card. > > > > [dev@netwarrior ~]$ lspci | grep -i VGA > > 00:02.0 VGA compatible controller: Intel Corporation Atom Processor > > D2xxx/N2xxx Integrated Graphics Controller (rev 09) > > > > The driver ID is as follow > > [dev@netwarrior ~]$ lspci -n | grep 00:02.0 > > 00:02.0 0300: 8086:0be1 (rev 09) > > > > I have checked ELRepo and it appears that the driver is not supported. I > > have checked intel's Linux site [0] and it appears that the drivers > should > > be in kernel 3.6.5 and above, therefore I installed kernel-ml "title > CentOS > > (3.7.2-1.el6.elrepo.i686)." Prior to getting the login prompt I just get > a > > blank screen. > > > > > > Currently the following intel drivers is installed. > > [dev@netwarrior ~]$ rpm -qa | grep intel > > xorg-x11-drv-intel-2.20.3-2.el6.elrepo.i686 > > [dev@netwarrior ~]$ rpm -qa | grep mesa > > mesa-libGLU-8.0.4-2.el6.elrepo.i686 > > mesa-dri-drivers-8.0.4-2.el6.elrepo.i686 > > > > Will there be a package available for the mention graphics card for the > > stock CentOS kernel > > 2.6.32-279.19.1.el6.i686 or shall I file a bug for the blank screen that > I > > am getting with kernel-ml 3.7.2-1.el6.elrepo.i686 > > > > [0] https://01.org/linuxgraphics/ > > I assume you are booting, by default, into runlevel 5. Have you tested > booting into runlevel 3 and then invoking 'startx' from the CLI, > noting any errors that may be displayed? > > With regards to the kernel-ml package, unless it is a packaging error > on our part, it will not be meaningful to open a bug report against > it. From what you have described, it reads as if you are experiencing > a problem with user-land software -- hence my suggestion, above, to > try booting to CLI mode. > > As for updating the Intel 'X' driver and associated software packages, > I am not sure who is currently maintaining them . . . perhaps the best > way forward would be for you to open an RFE against the > xorg-x11-drv-intel-2.20.3-2.el6.elrepo package and ask for it to be > updated. > > Alan. > > > -- > > Hi Alan, Thanks for your response, I have booted into run level 3 and invoke startx, however I do not see any errors because the screen goes blank with the dash on the top left corner of the screen. Below is the content of the Xorg.5.log after I have booted with the stock CentOS kernel. [44.636] X.Org X Server 1.10.6 Release Date: 2012-02-10 [44.636] X Protocol Version 11, Revision 0 [44.636] Build Operating System: c6b9 2.6.32-220.el6.x86_64 [44.636] Current Operating System: Linux netwarrior 3.7.2-1.el6.elrepo.i686 #1 SMP Fri Jan 11 22:23:11 EST 2013 i686 [44.636] Kernel command line: ro root=/dev/mapper/vg_netwarrior-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=vg_netwarrior/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_netwarrior/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet rdblacklist=nouveau nouveau.modeset=0 [44.636] Build Date: 22 June 2012 07:56:45PM [44.637] Build ID: xorg-x11-server 1.10.6-1.el6.centos [44.637] Current version of pixman: 0.18.4 [44.637] Before reporting problems, check https://www.redhat.com/apps/support/ to make sure that you have the latest version. [44.637] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [44.637] (==) Log file: "/var/log/Xorg.5.log", Time: Sun Jan 13 08:28:50 2013 [44.637] (II) Loader magic: 0x822c520 [44.637] (II) Module ABI versions: [44.637] X.Org ANSI C Emulation: 0.4 [44.638] X.Org Video Driver: 10.0 [44.638] X.Org XInput driver : 12.2 [
