updated Feb 2012
I started having an issue with my computer maybe back in May, where anytime I powered my machine off I had to reconfigure my Bios settings, as my primary Bios had failed, after several months of this I guess I just got tired [...]
updated Feb 2012
I started having an issue with my computer maybe back in May, where anytime I powered my machine off I had to reconfigure my Bios settings, as my primary Bios had failed, after several months of this I guess I just got tired of dealing with it, so I sold my android tablet (yes I did! and no I didn’t own more than one…) and bought a new Gigabyte Ga-990FX`-UD3 motherboard, which right now I am not very happy with, but I’ll get to that later, a new MD PhenomII x6 1090T CPU, a new XFX AMD Radeon 6850 Video Card, and 3 new Seagate 1.5TB HDDs. I have to reimburse myself for the hard drives however, as they were not paid for by selling my tablet. Hopefully selling my old Video Card, Motherboard, and CPU will cover their costs.
I’ve had all kinds of interesting episodes while trying to get this new hardware to work over the last, almost, 3 weeks. the good = back on linux, bye bye Microsoft. The bad=bye bye Google cloud print (kind of), possibility of getting Nuance Dragon Naturally Speaking to work (outside of a VM), possibility of getting my digital camera to work by just plugging it in the computer (for now). Here are a list of some of the issues I’ve run into, if they have lengthy resolutions, or attempted resolutions, I’ll link to another post (after I write it!) describing my efforts to get things working.
First up: Microsoft Windows 7 x64 Ultimate edition
- The only thing on the motherboard that works immediately after installation are the CPU, Ram, Keyboard, and Mouse.
- NIC, eSATA, on-board RAID, USB 3.0, none of it worked until after installing the drivers from the MB CD.
- One for the internal SATA ports 0-3.
- One for the internal SATA ports 4 and 5.
- Can only be enabled as RAID when ports 0-3 are also enabled as RAID.
- This seems a little bit backwards to me, as the only way to mirror your boot drive is to enable RAID on all ports… or lose ports 2&3 and mirror on 0&1, then not set RAID on 4&5 giving you only a mirror plus 2 drive slots on the MB. Else you are forced to RAID 0/1 on ports 0-3 and to use 4/5 for your boot mirror.
- One for the eSATA port
- When enabled and nothing is connected, it reports 2 available ports; however when the cable is connected I have gotten 3 drives (out of 4) in my external drive caddy to show up.
- It found the missing driver and also told me about 6 others were either out of date or had the wrong drivers installed. of the ones it wanted me to update, only one was free, the others were available after paying a $29.99 annual fee.
- The first link took me to the Gigabyte home page for the MB but did not list any driver that was not also included on the CD.
- The second link took me to a driver website download page for an Nvidia driver package!
- Well I gave it a shot, and sure enough it recognized the device and installed the driver, from an Nvidia driver package on my AMD chipset MB.
- After moving all my data around so I could setup a RAID5 5 drive array of 1.5TB drives, I had to undo it all and move data around to use them as normal disks, so I could disable the Marvell RAID in the BIOS (internal SATA ports 0-5) to prevent windows from loading the driver (which was the newest version from their website).
- This did indeed stop the BSOD for that DLL.
- I have not yet figured this one out, Gigabyte support wants me to disconnect all USB devices to test… (no mention of how I am to connect my KB or mouse) fyi no issues with the USB devices when my old MB was in the case, and no issue with the USB devices when booted to a linux live CD, nor any issues with random power offs at all, now that I am booting to Ubuntu 11.10 x64.
- What this means is if you are trying to get into the RAID BIOS controller setup, or the “change boot device” menu, or to get the GRUB menu to show up when hidden, or to start windows in safe mode, and you do not press the key/key combination one time at the exact time necessary, the system will hang and you cannot get in to that boot submenu
- It often takes me 10-30 boot attempts to get into what ever submenu I need to change the configuration.
Next up: Ubuntu 11.10 x64
- The network adapter will not work. I’ve tried many suggestions from forums, even downloaded the Realtek 8111e driver direct from realtek. It will not connect to anything (you may need to blacklist the wrong drivers, there are some 8 different models included in the linux driver package download).
- Current resolution, I installed a GB NIC PCI card, works great.
- Any changes to the AMDCCLE configuration disappears after closing the interface. even if I open it right back up, the settings are back the way they were. Help with manually configuring AMDCCCLE
- Any time I restart the computer it hangs after “checking battery state [ok]“.
- This is when it loads the graphical settings to launch X.
- As a note, I have a dual monitor setup, both on the two DVI ports; however because one DVI port is a DVI-d I have to have my right monitor connected as monitor0 and my left one connected as monitor1 (this makes things backwards, moving the mouse to the right puts it on the left screen and vice versa, unless you specify it in the configuration.
- Current resolution for this problem (short incomplete version):
- Reboot into Ubuntu recovery mode from GRUB (good luck!).
- Mount/remount all devices and read/write.
- Then press enter to exit that screen.
- Because the onboard NIC does not work, there is no point in selecting root command prompt with networking, as it won’t enable the PCI NIC.
apt-get purge -qq --no-download fglrx* xserver-xorg-video-ati xserver-xorg-video-radeon
- learn more about the xorg.conf settings
- Hopefully you have manually created the deb packages for your ati drivers, if not, you can reboot now and use the default drivers for xorg to download the drivers and put them in the /root/amd6xxx directory on your system (you will need to create the amd6xxx directory under /root). you may need to install two things before going back into the root recovery mode
sudo apt-get install execstack modaliases
those are required for the new AMD drivers, then follow these instructions after booting back in to the recovery mode root command prompt after remounting devices as read/write, instructions above.
- You either already had the files, or you just created them (only follow the creating .deb files section), so we can move on to install the AMD drivers for the Radeon 6xxx series card.
- This should run without much of an issue, might be a couple of mini errors (file not found, skipping), but nothing to prevent the installation from finishing.
- And to finish up:
- I am not 100% sure the “effective=startup” part is necessary or even works.
- You can now reboot and cross your fingers.
- I have to do this every time I restart my system, and sometimes it does not work and I have to do it 2-5 times before I can get back in. (no longer, with the new 12.1 drivers I have not been having this issue)
- There are also times when I boot and get 1 flickering screen and one working screen (both tinted like my background image).
- There are also times when I get one flickering screen and the other not, but both are nearly all white. Pressing CTRL+ALT+DEL initiates a reboot, so I know Ubuntu booted at least.
- There are some times when I get cloned displays in 1024×768 resolution (not my default or preferred).
./ati-driver-installer-11-9-x86.x86_64.run --buildpkg Ubuntu/oneiric
dpkg -i *.deb
aticonfig --initial=dual-head --screen-layout=right --xinerama=on --effective=startup --input=/etc/X11/xorg.conf
Any attempt at a total and complete resolution is still a work in progress…
So, I have gone through all my drivers for my wireless network card with the Realtek rtl8190p chipset, all but the windows XP driver will convert with ndisgen and all the ones that convert will load; however I never get a wlan0 or a ndis0 network interface in ifconfig. [...]
So, I have gone through all my drivers for my wireless network card with the Realtek rtl8190p chipset, all but the windows XP driver will convert with ndisgen and all the ones that convert will load; however I never get a wlan0 or a ndis0 network interface in ifconfig. So, having gotten at least a device identification while using the Kubuntu live CD, I went ahead and tried using ndiswrapper, well, it does not work when in a live CD, requires several packages (which also requires an inet connection). I went ahead and installed Kubuntu 9.10, still no wlan0 in ifconfig; however it correctly identifies the card and the chipset in “lspci -v” so I have been setting the OS up for use, I bridged the wireless network connection from my laptop (which makes the inet not work really well on the laptop, but does allow the desktop to get online).
Well, when I installed the ATI drivers for my video card (a must when intending on using VMs) I caught the invisible mouse bug that has been plaguing Ubuntu since at leas v6 (forum posts) and apparently happens in Fedora with NVidia drivers as well. as best I could tell, only with KDE. Since I am very well attached to my KDE I really do not want to switch. So, I have been working without a visible mouse. I got the ndiswrapper up and running, installed ndisgtk so I could have a UI for ndiswrapper, and added the most recent windows x64 driver for my wireless card to the ndisgtk interface and then my system decided it did not want to work anymore. I could open a terminal and do a “ps” or an “ls” but anything else would hang (including shutdown, reboot, kill, sudo, and ifconfig commands) the inet stopped working and my mouse was invisible, so I rebooted.
This time my display would not activate at all. I waited 20 mins for it to come up, and nothing. at this point I am about to decide that using VMWare is not worth the hassle of getting a computer to work with Linux. I should stick to Virtualbox and Win7 both work just as well, Virtualbox newer versions have advanced 3D support and allow as many processor cores as you physically have (VMWare was limiting me to 2 per VM). The thing I was looking forward to the most about VMWare was the memory pooling, so you could load VMs who’s total RAM assigned was greater than the physical RAM on the machine, since it only gave RAM to a VM when it was needed.
So, now I am in Slax (booted off my USB stick) and have to make emergency repairs to my xorg.conf file (I assume it is the culprit at this point), because I had Kubuntu setup with no bootloader, since I was planning on VMing not multi-booting. Further updates to come… if I get Kubuntu to work, I’ll try BSD again on another HDD and see if anything I learned from Kubuntu helped. If not, I still have my HDD with Win7 sitting on the shelf here next to me.
************update about an hour later…***********
so the Slax Module kndiswrapper (=ndisgtk) was able to load the win XP x64 driver and identify that the device was present. when I clicked the configure network button, it popped up a message “Can’t Start the Network Configureation! No Interface Found”. now… I am starting to wonder if it is not the rtl8190p chipset that is causing my problem, as I have found it correctly identified in Fedora 12, KUbuntu 9.10, and Slax, yet none of them can activate the device for networking. I did note on another page (check the tags for rtl8190p) that I found a website that I think has posted a linux rtl8190 driver, but I am not 100% on that, and have no idea how to add it to the kernel without building my own. AND if I am going to build my own Custom Linux kernel for my machine, I’m gonna need a LOT more time… (when I get up and running on some OS again, and I get back here to add links to this post, I’ll put the link in for that website too).
*******update – an hour after that…*******
Right, thoroughly upset with Ubuntu right now, will not even boot into single user mode, I tried removing the xorg.conf file and still nothing, normal or in single user mode. I can (depending on how my wife reacts to the Cat cable running from her laptop (read “used to be mine”) out of the bedroom, across the hall, and over to the other side of the livingroom…) keep my laptop in bridged mode, I’ve been tinkering and as long as I don’t reboot or touch anything on it (she does not have admin rights and is still in Win7) inet is working on both machines. I only have about 30 more days before I am moving into a new apt (I hope, they still have not called to tell me my application is approved, I don’t know any reason why it wouldn’t, but it normally takes them an hour or 2 when I have gone to other apts, but this place has had 5 days already…) and in the new apt, the router and computer will be side by side, or close enough that you’d never see the cable! so no more wireless needed, until I relocate again…
Anyway, the point of all that ^^^^^ is that I am going to kill KUbuntu and put FreeBSD 8.0 back on my machine…
(I’ll add links after I get a working/bootable computer again)