Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Mame setup for mac mac.
Visit the following links: If you have any problems with the registration process or your account login, please. If you need to reset your password,. Having a problem logging in? Please visit to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. To receive this Complete Guide absolutely free. Same issue.when i switch on composite extension, it gets too slow,cpu eating.
Xorg.log X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: Linux 2.4.29 i686 ELF Current Operating System: Linux mella 2.6.11.6 #1 Thu May 26 23:50:42 EEST 2005 i686 Build Date: 13 February 2005 Before reporting problems, check to make sure that you have the latest version. Module Loader present Markers: (-) probed, (.) from config file, () default setting, () from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. I use Slackware 10.1 and i love it is it possible to run with Slackware? I'm not sure if anyone is still reading this old post, but I'm still replying in the hope that someone that was in the same situation as me can solve his problem. My i915GM (Dell Inspiron 6000) wasn't working at all with the i810 driver and I couldn't watch movies with the default vesa driver.
After much time and research, I finally got the DRM and i915 snapshots from dri.freedekstop.org and compiled them. Now everything works like a treat and I get 100+ fps with glxgear in fullscreen (The acceleration is buildin in the driver). Hope that helps someone, - R4cOOn. Doesn't work for me. I'm running Slackware 10.1 on an Acer Aspire 1690. Self compiled kernel 2.6.12.2 (with i915 selected as module) Xorg 6.8.2 Grabbed the snapshots for drm and i915 from dri.freedesktop.org and installed But I get no joy.
There are no errors in my Xorg.0.log file xdriinfo gives me the following Xlib: extension 'XFree86-DRI' missing on display '0.0'. Screen 0: Not direct rendering capable. Also, I've noticed that the Section 'DRI' Mode 0666 EndSection part of my xorg.conf file gets ignored since /dev/dri/card0 has 0660 permissions. Seems like udev might have been overriding stuff. I'm used to nvidia which is painless and simple to work with, by my old laptop got stollen and this seemed like a sweet deal. Turns out it's a lot of grief. I can't even watch a DVD on this thing right now.
I have problem with i915 too. Does dri change something in xvideo - (watching movies - xvinfo: X-Video Extension version 2.2 screen #0 no adaptors present In mplayer '-vo xv' etc. Are not working, only '-vo x11' is working, and if I want fullscreen I have to type mplayer -vo x11 -zoom, then I have fullscreen. I don't like this.; )? If yes then great, if not, what can I do to 'normally' watching movies? I'm trying to install dri.
I915 Linux Drivers For Macbook
I noticed a few weeks ago, when I tried to update the drm/i915 snapshots, that they were no longer working. Try using the last but one versions, or the ones before that.
As for the SUSE 9.3 question, I'm a 9.2 user myself, so you just need to compile the drm/i915 modules like everyone else. I noticed that sometimes the display gets slow for no apparent reasons, but I couldn't quite work out the reason why.
If anyone is interested I can post my fancy xorg.conf here (for an Inspiron 6000 with a 1280x800 display). Did anyone get it to work?
There are only post of people who didn't manage to make it work. Thanks for the tip R4cOOn, I downgraded back to the version from 050707. My frame-rates for glxgears and some of the gl hacks in xscreensaver have doubled. Still not great, but better. I can now watch DVDs. Boat-loads of dropped frames, and only works windowd, not full screen, but it much better than the absolutely nothing that I got before. Xdriinfo segfaults.
Not sure what's up with that. Basically, I think I'm half-way there, which is farther than I was. I downgraded to 050707 too but have still the same.;( FATAL: Error inserting i915 (/lib/modules/2.6.12.3/kernel/drivers/char/drm/i915.ko): Unknown symbol in module, or unknown parameter (see dmesg) and dmesg: kobjectregister failed for drm (-17) kobjectregister+0x6b/0x80 modsysfssetup+0x51/0xc0 loadmodule+0x962/0xa70 sysinitmodule+0x6b/0x1c0 syscallcall+0x7/0xb i915: Unknown symbol drmcleanuppci What should I do in Device Drivers - Character devices - Intel 830M, 845G, 852GM, 855GM, 865G (i915 driver) - exclude, include or in module 'i195'?
What to do else in kernel 2.6.12.3 for my i915 chipset (graphic card is most important of course)? Got stuff working. Not sure why.
Here's what I did. First off, it's an ACER Aspire 1690, just in case anyone needs to compare notes. Basically, I'd done so much tweaking with Xorg, CVS, kernel, ACPI, etc. That I couldn't figure out what was what anymore, so I backed up my personal data to my desktop and started fresh. Repartitioned the HD so I had a small windows partition so I could see what MS does (ACER suports MS, but only gives lip-service to Linux) 0) Installed XP on the first partition from the recovery disks and booted it up once to check out the hardware config that windows picks up. 1) Installed Slackware 10.1 2) Installed gcc-3.4.4 with the following config/compile options./gcc-3.4.4/configure -enable-shared -enable-threads=posix -enable-cxaatexit -enable-languages=c,c,f77,java,objc make profiledbootstrap 3) Compiled and installed 2.6.12.2 kernel with acpi patch (note, I still need to fix my dsdt) Make sure to have agpgart, i915 modules compiled in. 4) Install new version of hdparm so that I can get dma to work on my hard-drive/dvd-drive.
This wasn't working before either. 5) Install Xorg6.8.2 from source (full source, fonts and all since slackware 10.1 doesn't seem to have all the fonts) Note, I didn't play with host.def or any configs at all for the compile, just let it do it's thing. Note, I'm still using my xorg.conf file from before when I couldn't get dri to work. 6) Install the drivers i915 and dri drivers from freedesktop, the versions from 20050707 worked best for me before, so these are what I used now.
Now, for some magic reason, everything works. Glxgears gives me numbers 10 times higher than what I had before and xdriinfo finds screen0. The only real difference that I can think of are 1) I have windows installed and actually booted it up once. 2) I have dma working on the hard-drives. If anyone can tell me why everything suddenly works when it didn't before, that would be tres cool. I hate this black magic feeling I have right now. If anyone wants me to post my xorg.conf file or an Xorg.0.log file, let me know.
If anyone can tell me.
You may want to check out Johannes Berg's (mac80211 maintainer) slides here: They may be somewhat outdated but should give you a place to start. A high level description of the Linux WiFi kernel stack:. It's important to understand there are 2 paths in which userspace communicates with the kernel when we're talking about WiFi:. Data path: the data being received is passed from the wireless driver to the netdev core (usually using netifrx). From there the net core will pass it through the TCP/IP stack code and will queue it on the relevant sockets from which the userspace process will read it. On the Tx path packets will be sent from the netdev core to the wireless driver using the ndostartxmit callback.
The driver registers (like other netdevices such as an ethernet driver) a set of operations callbacks by using the struct netdeviceops. Control path: This path is how userspace controls the WiFi interface/device and performs operations like scan / authentication / association. The userspace interface is based on netlink and called nl80211 (see include/uapi/linux/nl80211.h). You can send commands and get events in response.
When you send an nl80211 command it gets initially handled by cfg80211 kernel module (it's code is under net/wireless and the handlers are in net/wireless/nl80211.c). Cfg80211 will usually call a lower level driver. In case of Full MAC hardware the specific HW driver is right below cfg80211.
The driver below cfg80211 registers a set of ops with cfg80211 by using cfg80211ops struct. For example see brcmfmac driver ( drivers/net/wireless/brcm80211/brcmfmac/wlcfg80211.c). For Soft MAC hardware there's mac80211 which is a kernel module implementing the 802.11 MAC layer.
In this case cfg80211 will talk to mac80211 which will in turn use the hardware specific lower level driver. An example of this is iwlwifi (For Intel chips). mac80211 registers itself with cfg80211 by using the cfg80211ops (see net/mac80211/cfg.c).
The specific HW driver registers itself with mac80211 by using the ieee80211ops struct (for example drivers/net/wireless/iwlwifi/mvm/mac80211.c). Initialization of a new NIC you've connected occurs from the bottom up the stack. The HW specific driver will call mac80211's ieee80211allowhw usually after probing the HW. Ieee80211allochw gets the size of private data struct used by the HW driver. It in turns calls cfg80211 wiphynew which does the actual allocation of space sufficient for the wiphy struct, the ieee80211local struct (which is used by mac80211) and the HW driver private data (the layering is seen in ieee80211allochw code).
I915 Linux Drivers For Mac Os
Ieee80211hw is an embedded struct within ieee80211local which is 'visible' to the the HW driver. All of these ( wiphy, ieee80211local, ieee80211hw) represent a single physical device connected. On top of a single physical device (also referred to as phy) you can set up multiple virtual interfaces. These are essentially what you know as wlan0 or wlan1 which you control with ifconfig. Each such virtual interface is represented by an ieee80211vif.
This struct also contains at the end private structs accessed by the HW driver. Multiple interfaces can be used to run something like a station on wlan0 and an AP on wlan1 (this is possible depending on the HW capabilities).