Getting Linux on the Acer Aspire 3023 was child's play. Almost.
Anything that goes wrong while following these instructions is your problem, not mine
Acer offer this level of support for Linux on their laptops.
The 3023WLMi is pretty nice for the price. I bought mine at technoworld.co.uk for just over £600 (sometimes Google posts an ad of theirs at the left there...), then chucked in an extra Gig of RAM (512 Mb just isn't enough for WinXP). Nice big screen, light feeling keyboard, wireless LAN, gigabit ethernet, sexy graphics card...
But!! There are some problems, mostly easily solved after a quick look around the internet (thanx google!)
If you're not so adventurous, you would have left the original OS(WinXP Home or Pro) installed and left all the hungry little applets running in the background
Being a bit masochistic and enjoying a pointless challenge, I thought getting Fedora Core 4 Linux co-habiting (dual-booting) with WinXP Pro could be interesting. I was right. Very interesting indeed. What follows is a collection of what I have found during the past few weeks of getting this little box to do what it oughta.
Actually, it's Acer (or whoever sold you the notebook) who should give you back your money. Having read this saga, it could be easier said than done. However, the Windows XP Pro EULA states:
YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA BY INSTALLING, COPYING, OR OTHERWISE USING THE PRODUCT. IF YOU DO NOT AGREE, DO NOT INSTALL OR USE THE PRODUCT; YOU MAY RETURN IT TO YOUR PLACE OF PURCHASE FOR A FULL REFUND.
Or words to that effect. Given that your Aspire 3023 has WinXP pre-installed, and does lots of irritating stuff on first boot, the best approach would be to power on, hit [F2], stick a Fedora Core 4 DVD or CD in the drive, change BIOS settings to boot from DVD/CD, repartition the hard drive and install Linux.
Good luck getting your cheque! It can be done...
LCD Screen, 3D acceleration, Synaptics touchpad, sound, wired networking, wireless networking, HotKeys, USB ports, DVD-RW, ACPI power management (in progress), CPU frequency scaling, PCMCIA slot, WinModem (reported), TV-out(reported).
FireWire (untested), infra-red port (untested), card reader(untested)
I've got my 3023 WLMi going with Fedora Core 4. It took a bit of tinkering, and I have a mostly-functional notebook. Some things are better than the Micros**t alternative, some things aren't so good. Other users have reported good success with SuSE 10.0 and moderate success with Ubuntu. Mandrake 10.0 is a bit of a lemon I'm afraid. These notes specifically pertain to my FC4 installation.
Tuomo Kalliokoski reported the following:
I just installed Debian testing package (etch), kernel 2.6.15-1, with noapic parameter and it seems to be working :) Debian stable (3.1r1 aka "sarge") didn't work, it had old kernel 2.6.8 iirc... It produced "spurious APIC interrupt on CPU#0, should never happen" errors with noapic or the pin parameter. Without them lots of APIC errors and sometimes freezes the system.
Fedora Core 5 (Bordeaux) was released on 20/03/2006. You can get it from the torrent, as I have. I'm about to find out how good these notes are by potentially wrecking my FC4 install, upgrading to FC5. Of course, I will let you know how it works out!
2006-04-05. Running an FC5 upgrade over a working FC4 is not a good idea. It doesn't work very well, mostly because of X. If you don't mind having a console-only login then by all means, go ahead. Otherwise I would advise that you don't touch FC5 unless a) you are really comfy with hacking xorg.conf or b) ati have released an updated installer that works for Xorg 7.0.0 or c) FC5 has something that you just gotta have! I also had a go at SuSE 10.0, which works OK I guess but I think I will stick with Fedora Core 4 and GNOME for now
2006-04-11. I just received an email from someone who has got FC5 going by taking my approach of entrusting all success to sheer dumb luck and persistence. It's probably a good idea then to put all your config files, webpages, home files and stuff on a flash drive or DVD or whatever, then reformat and start from scratch, rather than try the upgrade route. Otherwise, try nailing your xorg.conf by renaming it, then do an update. Let me know how you get on...
I started out with the stock FC4 kernel, which was enough to get most things going. Make sure whichever
kernel you use, you have the headers and/or the source so your compiler
can do its thing when you make the drivers you are going to need. Also run
]# yum update udev to get the latest hardware support. For
debugging purposes I started testing custom kernel configurations,
using linux-188.8.131.52. Kernel 2.6.13 and above appears to be necessary to get battery monitoring going.
More recently, I've tried some 2.6.16 kernels from the Fedora site and have noticed a couple of issues, including a failure of all network connectivity and a partial loss of Synaptics touchpad function (no tap-to-click). I'm not well enough informed on kernel programming to make a constructive comment on this - perhaps there's a proper programmer out there who might have something useful to add?
Kernel version 2.6.17 contains a new driver for the wireless LAN card, called bcm43xx. If you want kernel support for your wireless card then you will need to compile a custom kernel and follow the installation instructions posted here.
Fedora has released a version of kernel 2.6.17 that has support for the wireless LAN card (the bcm43xx is included as a module), and which seems to fix the problems that I noticed with the 2.6.16 kernels. I highly recommend that you upgrade to kernel 2.6.17.
Some Ubuntu users have noticed a strange kernel timing issue, which is solved with the noapictimer kernel option. It can cause a problem shutting down, as reported by Armando:
23/12/2005 20:40 Hi for timer problem on ubuntu/kubuntu: noapictimer cause no correct reboot/shutdown; this alternative parameter on grub is optimal for correct time problem: disable_timer_pin_1 tested on 2.6.14 vanilla kernel with kubuntu breezy
Can't remember how I did this, apart from downloading and burning the DVD-iso version of Fedora Core 4 from the bittorrent, using that to repartition the harddrive (the BIOS supports bootable DVDs and CDs) and installing a working Fedora Core 4 (FC4). I tried the DVD version of Fedora Core 3 but it didn't work. Some people have reported needing to use kernel options on boot while installing Fedora; I didn't know about that tricky stuff at the time. Your first install of FC4 may have very crusty graphics under X, because you need to tweak the xorg.conf file. Getting the ati driver to do 3D acceleration is a bit problematic, but very doable.
Credit to the boys and girls at Redmond, WinXP Pro behaves itself during installation.
Windows: Not much of an issue, just use the driver from Acer-Europe. ATI aren't especially helpful in this regard. Colin Mcrae Rally 2 and 04 run satisfactorily (depending on how easily satisfied you are). The driver crashes when on battery power and ATi's Powerplay is set to 'Optimise Battery Life'. I've contacted both Acer and ATi about the problem, but nothing has happened yet. In the meantime, leave Powerplay disabled.
FC4: You need to install xorg 6.8, then get the fglrx rpm and the ATI driver installer from ATI. I had trouble with old versions of the driver installer but ati-driver-installer-8.16.20-i386.run works perfectly on my new (2.6.13-1526_FC4) kernel. I've tried the newer ati-driver-installer-8.20.8-i386.run but it looks broken - PPRacer gave a seg fault :-( and glxgears looks rubbish. If you are having trouble getting a fully working driver, email me. Otherwise, just follow the instructions at ATI - to paraphrase,
]# chmod 777 ati-driver-installer-8.16.20-i386.run ]# ./ati-driver-installer-8.16.20-i386.run ]# fglrxconfig ]# gedit /etc/X11/xorg.conf
You need to edit the xorg.conf file generated by fglrxconfig to make use of the slightly unusual 1280x800 screen resolution of the Aspire 3023. There is a line called
Modes that is read left to right. The first functional resolution is used by the X server. So put as the first entry
"1280x800". You can disable
VirtualDesktop if you don't like it, by commenting it out. It's about two lines below the
Modes line. You'll have to restart your X server either by logging out and
or restarting the machine. Then test the driver by running in an X console
Wa-hey! 3700 frames per second! If you have PPRacer on your machine try that as well - I get 110-125 FPS (which is a tad excessive...). The new ATI drivers seem to be better than the old ones, giving a slightly easier install and full support for the Mobility Radeon X700.
I haven't tested this, however I received this email:
7/12/2005 16:58 Hey, Don't know whetever i did mention it before, but TV-out works. Nothing to do, just use the ATI software to do the job and your sweet laptop does it too. As usual, the bad thing is that X need to be restarted... But at last, who cares ! It does work anyway ;-) Aby Brolh
Windows: Use the driver from Synaptics. The one at Acer-Europe is old (v7) and doesn't support horizontal and vertical scrolling properly, and the middle button doesn't really work. Getting version 8 and above from Synaptics is recommended (by me) even though Synaptics refer you to 'Your notebook manufacturer'.
FC4: Fedora will install the synaptics RPM for you and you will get
intermittent useage. There is an option that you have to add to the
kernel options in the file
/boot/grub/menu.lst, which is
i8042.nomux. All my problems vanished after making this tweak. The
only thing remaining is a warning when you boot - Unable to query
Synaptics hardware - but who cares about that when their touchpad works
perfectly??? You may have to hack your
xorg.conf file as well. There is
advice out there on the web to issue the command
#] echo -n "psmouse" > /sys/devices/platform/i8042/serio0/drvctl
variant thereof) but I found that the
i8042.nomux tweak worked better
for me. This may have something to do with acpi options.
More recently, I've installed an updated
udev package, and hacked around in my xorg.conf. There's quite a detailed section on different tapping and scrolling behaviours, so I now have full scrolling and multi-fingered clicking in Gnome. Check the section of my xorg.conf that begins:
Section "InputDevice" Driver "synaptics" Identifier "TouchPad"
There's something funky going on with the TapButton1 and TapButton2 options, so I have them both set to 1 - otherwise a single tap is interpreted as a middle button click. (I'm using the latest RPM version of the synaptics driver - haven't tested the newest source version)
Not installed in my machine, so can't help you much. Bluetooth is a factory option that I didn't get :-(. I can tell you where it's located - at the back of the main case inbetween the Kensington lock and the AC power input. A bit of surgery is required if you want to install a Bluetooth module, and you have to acquire such a module from a spare-parts dealer. It's doable if you have a good set of screwdrivers and don't care too much if you break a couple of case-snaps ;-).
The hardware sits under the small panel with 2 screws in the bottom of the notebook. Two leads (black and grey) connect to the aerial, which goes up behind the LCD monitor. Wireless LAN (wlan) is software controlled!
Windows: You need Acer's Launch Manager app to turn on the card with the button on the front of the notebook, or via Broadcom's app from the Acer-Europe site. Launch Manager (running in Windows) detects the button press, then sends a command to the wlan card to switch on. The Broadcom app doesn't seem to be able to do this all by itself - you must have Launch Manager.
FC4: There are 2 ways to install wlan support. The old, ndiswrapper way (quite stable now) and the new, kernel driver way. Both sets of instructions are here. Since the release of kernel 2.6.17 with included bcm43xx module as a Fedora RPM, I recommend upgrading your kernel and using bcm43xx rather than ndiswrapper.
The ndiswrapper way requires you to download ndiswrapper, the WinXP driver (bcmwl5.inf and bcmwl5.sys) and acerhk. Follow the instructions at ndiswrapper, both general and specific to your distribution. I used the instructions out of the Redhat/Fedora section, and they were good. Only, you don't need to make an alias eth1 to point to wlan0, the default wlan0 works fine. I made an RPM (as root, tut-tut), and installed ndiswrapper that way. Compile and install acerhk according to instructions. If you have acerhk-0.5.27 or earlier use this command:
]# /sbin/modprobe acerhk autowlan=1 poll=0 force_series=5020 verbose=3 usedritek=1 ]# echo 1 > /proc/driver/acerhk/wirelessled
Later versions of acerhk autodetect the Aspire 3020 series notebooks, so the
force_series=5020 option is unnecessary.
You can put this command in /etc/rc.d/rc.local if you want wlan0 to be active on boot. Otherwise you have to run it from a command prompt each time you reboot. Actually starting wlan0 is easy: use the Network Configuration GUI tool, the /sbin/ifup command, or change your services to run NetworkManager rather than the old-school network service.
]# /sbin/service network stop ]# /sbin/service NetworkManager start ]# /sbin/service NetworkManagerDispatcher start
The Network Manager GUI is good at configuring interfaces, so let it do the work.
Pour les instructions en Français, s'il vous plaît visiter ce forum.
A recent development is the reverse-engineered bcm43xx driver for Linux, which purportedly supports the bcm4318 that is installed in the 3023 WLMi. I'm experimenting with this new driver and so far it seems pretty good (I'm using it to update this web page right now!). The Fedora kernel includes bcm43xx by default, and there is a 'Fedora Way' to get it to go using the 2.6.16 and 2.6.17 kernels (see this page for details). I've just completed the Fedora kernel way and it seems to be the easiest if you're on this GNU/Linux flavour. The only difference from the instructions given above is that I used Berke Viktor's version of fwcutter and firmware (see below). If you want to compile a kernel from source, follow these cross-distro instructions:
Hi Mr. Doube! I'm not from England so please excuse for my poor english ;-) . First of all, thank you very much for your site and your tutorial. It helped me very much, really. I hope you'll keep up the good work! ;-) I just wanna inform you that the bcm43xx driver included in the kernel 2.6.17 works fine for me. I use Slackware 10.2 for testing purposes but will use it as my main OS soon. I compiled a custom kernel with the bcm43xx driver. It was first weird that I didn't see the bcm43xx driver on the list in wireless section. But after taking a look at the Kconfig file of the bcm43xx folder I realized that it depends on IEEE80211_SOFTMAC, so you have to enable it in the Networking section: >>Software MAC add-on to the IEEE 802.11 networking stack
Please note that you also need to say yes to:
Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?]
or else the rest of the important Wireless and bcm43xx options won't be available.
Tah-dah, bcm43xx will appear in Device Drivers ;-) . Then downloaded the bcm43xx-fwcutter tool to extract the firmware. These two can be found here: fwcutter: http://download.berlios.de/bcm43xx/bcm43xx-fwcutter-004.tar.bz2 firmware: http://users.atw.hu/bervi/tmp/bcmwl5.tar.gz The firmware package contains two versions - the one by Acer (version 184.108.40.206) and another one from a URL in the fwcutter documentation (version 220.127.116.11).
We have both tested version 18.104.22.168 and it doesn't work. Stick with version 22.214.171.124.
To extract the firmware one should: 1. Download both files. 2. Unpack bcm43xx-fwcutter to anywhere, then enter the folder 3. Build the tool: # make 4. Unpack the firmware files (in the same folder is the simplest) 4. Print out firmware information in order to see whether the firmware is OK and is expected to work (and it should with 126.96.36.199): # bcm43xx-fwcutter -i FILE 5. If so, extract it: # bcm43xx-fwcutter FILE Then, I rebooted, because I didn't compile the kernel to include the bcm43xx driver as a module but to include in the base kernel (but next time surely will). Now bring up the interface (it's eth1 for me - eth0 is the rlt8169 NIC): # ifconfig eth1 up Now you all should be able to configure your wireless interface with iwconfig. Please note that ndiswrapper & acerhk is needles now. I noticed that the Wlan switching button doesn't lights all the time but only if traffic goes through. You should also configure your scripts to bring up the interface on boot, these are somewhat distro specific, I suppose, I done it through the /etc/rc.d/rc.inet1.conf file. Here's the according part of it: >># Config information for eth1: >>IFNAME="eth1" >>IPADDR="192.168.0.21" >>NETMASK="255.255.255.0" >>USE_DHCP="" >>DHCP_HOSTNAME="" >>WLAN_ESSID=HOME >>WLAN_RATE="54M auto" If you would like to switch the wlan card with the button, you'll probably need acerhk, I haven't tested this yet :-). I hope I didn't forget anything. You could contact me on the LinuxQuestions forum, my nick is berVi. I'm looking forward to see these infos on your site since this is a better way than using ndiswrapper IMHO. Cheers and all the best! Berke Viktor
Hi again! I forgot to mention that you also have to run: make installfw after extracting firmware. bye
Windows: Works fine, get the driver from Acer Europe.
FC4: Partial function - work in progress. It is a Conexant software controlled AC97 modem, so you will need the drivers from Linuxant. Good idea to check out linmodems.org as well for general background.
Unless there were major variations during the production run of the Aspire 3020 / 5020 machines, your modem should use a Conexant chipset. Use scanModem from linmodems.org to check. scanModem is pretty clever and will give you lots of useful information.
Find out what kernel and processor you have; for the Aspire 3023WLMi it's an i686.
]# uname -a
Go to linuxant.com and download the appropriate driver for your kernel, distro and processor.
I use Fedora Core 4, so got the rpm and installed it that way.
Check that the service hsf is running by starting it:
]# /sbin/service hsf start
Then make sure the modules are loaded:
ERROR: no device detected by hsf driver
Ok, so you need to download the driver source (hsfmodem-7.18.00.05full-1.i386.rpm.zip), and the newdev patch (hsf-7.18.00.05-newdev.patch).
Note - future releases of hsfmodem will probably integrate this patch, so you may only have to install the plain RPM
Remove the previous version of the hsfmodem RPM (I use Synaptic). Extract and install the hsfmodem source RPM. Copy the patch to
/usr/lib/hsfmodem. Patch the sources with
]# patch -p1 <hsf-7.18.00.05-newdev.patch
Compile the sources with
]# cd modules ]# make
Which will prompt you to remove the current modules and to compile / install some new ones. Press enter, the defaults should be fine.
(While figuring this out, I also ran
make install directly after
make, so if you are having trouble, try that.)
After this, I had a working modem. I used Fedora's Network
Configuration GUI to install a new device and enter my ISP's phone
number details. This information is stored in
Some of it is generic to the modem, some is specific to your ISP
settings. You can double click on ppp0 to get the modem to initialise,
just make sure that flow control is set to Software / XONXOFF. I am
having trouble maintaining a connection, but at least I can hear the
modem intialising and negotiating a connection with my ISP.
On the command line you initialise the modem like so
]# /sbin/ifup yourisp
/dev/modem as 'yourisp' does not work. You must use the Dialler ID from your
/etc/wvdial.conf, as in,
]# /sbin/ifconfig ppp0 Link encap:Point-to-Point Protocol inet addr:188.8.131.52 P-t-P:192.168.9.133 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:12 errors:1 dropped:0 overruns:0 frame:0 TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:210 (210.0 b) TX bytes:228 (228.0 b) ]# ping 192.168.9.133 PING 192.168.9.133 (192.168.9.133) 56(84) bytes of data. 64 bytes from 192.168.9.133: icmp_seq=0 ttl=255 time=13549 ms 64 bytes from 192.168.9.133: icmp_seq=1 ttl=255 time=12613 ms 64 bytes from 192.168.9.133: icmp_seq=2 ttl=255 time=11718 ms
So there is a bit of a problem here but at least the computers are talking to each other, albeit at a level not much higher than morse code. I will look into this and publish any solutions here shortly
The support team at Linuxant suggested trying
with a trial licence: This did not work for me at all, in fact it was
worse than the unlicensed, crippled version of the driver. My computer
locked up completely! I have tried compiling the driver with 4KSTACKS
disabled in the kernel, to no avail.
NEWSFLASH One user has reported success with the modem on their Aspire 3023. I received this email:
25/11/2005 22:21 Hi, Michael! I found the way how to make modem work under Linux so you can also try. You must download new hsf modem driver from linuxant, but download souce code, the name is hsfmodem-7.18.00.07full.tar.gz After untaring and unziping put in the hsfmodem directory file that is in this attachment and run it in shell. (this is a litle bit of cheating, but it is working :-) ) After that run make install, and after that hsfconfig. Put in the licence informations that is written in this .dat file. I use suse 9.3 and kpppd and my second init string must be AT&FW3+M5=V90 the init string that they suggest dos not work for me. Speed is just 14 000, but I will try to make it faster. Good Luck! dejan kuticic
And a few days later, this email:
30/11/2005 22:48 Now I changed first init string in:AT &FW3+MS=V92,1,28800,33600,28800,56000 and second init string in:ATX3 and I have full 52000 speed. The line is not stable too much, some times it disconnects but it is working, that is also something :) Cheers!
I haven't tried these instructions yet, due to having neither time nor a dial-up account to test with. I can pass on any questions you might have for Dejan if you need further assistance.
Windows: I thought that XP would be clever and do the power management automatically, but this is not the case. You need to go to AMD and download the CPU driver for your version of Windows. The driver at Acer Europe doesn't work on my machine (I detect a theme here...). Despite all the messages about the driver being for 64bit processors, it also works for the 32bit Sempron 3000+. The Desktop Dashboard from AMD is an interesting app if you like to monitor your power consumption, processor speed and temperature.
FC4: For testing I compiled a custom kernel using the 2.6.12 source
patched to 184.108.40.206, including powernow_k8 support as a module. Later I
realised that the vanilla Fedora kernels work just as well, so long as
the powernow_k8 module is installed. Check the ouput of lspci - you
will see that although the CPU is a Sempron (K7), a lot of the bus stuff
lists as K8. I guess this is so that Acer could easily make 32- and
64-bit versions of the Aspire 3000/5000 notebooks. Whatever, the
powernow_k8 kernel module works. You may need to turn on the 'advanced'
kernel configuration option - at the top of the list when running
- in order to see the powernow_k8 option. You should also configure the
kernel module to use the userspace CPU frequency control option, and
the conservative power useage model option.
The quick way to do this in FC4 is to use the cpuspeed daemon. Edit
/etc/cpuspeed.conf like so:
Then start the daemon
]# /sbin/service cpuspeed start
You can check how fast your processor is running by
]# cat /proc/cpuinfo
Alternatively, you can use the PowerNow Daemon, read the instructions, compile and install.
Start up the kernel module:
]#/sbin/modprobe powernow-k8 start
Start up the PowerNow Daemon:
Easy! PowerNowd/cpuspeed work in terms of saving battery power and allowing you to work without irritating fan noise. Incidentally, thermal fan control is part of the BIOS, so the fan will speed up and down independent of the OS. You can also install a little taskbar applet that shows your current CPU speed.
Thanks to Benjamin Larsson for this tip:
Upgrade your kernel to 2.6.13 or later; I used Fedora's RPM (for convenience, really...) 2.6.13-1.1526_FC4.i686.rpm, which you can get from fedora.redhat.com or one of the mirrors.
Now add the following to your kernel options in
Reboot into the new kernel, and install the Gnome (or kde) battery monitoring panel applet. Wa-hey, it works! Big thanks to the kernel developers!!
This is here for comparative purposes
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01) 00:02.0 PCI bridge: ATI Technologies Inc RS480 PCI-X Root Port 00:06.0 PCI bridge: ATI Technologies Inc: Unknown device 5a38 00:07.0 PCI bridge: ATI Technologies Inc: Unknown device 5a39 00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller 00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller 00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller 00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11) 00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI 00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge 00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge 00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02) 00:14.6 Modem: ATI Technologies Inc: Unknown device 4378 (rev 02) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X700 (PCIE) 06:05.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) 06:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 06:06.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller 06:06.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller 06:06.4 Class 0805: Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) Controller 06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
Now that you have read these brief instructions, here are my current, working config files to peruse. I highly recommend that you backup your old config files especially if they work!
xorg.conf from /etc/X11/
grub.conf from /boot/grub/
rc.local from /etc/rc.d/
Questions? email me
This file last modified 0803hrs 28 July 2011 © Michael Doube 2004-2013 :: Designed to be interoperable and standards-compliant. Looks best with Mozilla Firefox. Enforcing the Robots Exclusion Standard