Announcement
Collapse
No announcement yet.
ASRock Z68 Pro3
Collapse
X
-
If it helps anyone, with the matx pro3 version, if you set the IGP voltage to auto, kubuntu startup will switch off the machine. A fixed value does not have tis problem. This was the problem I was seeing when installing kubuntu. I upgraded the bios and think the upgrade put the default to a fixed value and not auto.
-
Originally posted by ak888 View PostI just built a core i7 using the matx version of this board and placed an old hdd which already had ubuntu server installed. The machine boots into this ok. However, I wanted to install kubuntu 11.04 - promptly created a bootable USB key with unetbootin and kicked it off. Kubuntu seems to start up the plymouth screen, the dots flash across showing progress then the machine just shutsdown.
Anyone seen this or experienced this with this board?
Kubuntu 11.04 seems to work most fine - early days yet.
Current issues I have seen:
limited lm-sensors support (as highlighted by the review)
cpu scaling - doesn't seem to be scaling. Always showing 3.4 GHz.
Wake On Lan doesn't seem to be working. When the PC is off I expect the see the lights flash indicating traffic (I have also added an upstart conf to execute ethtool on network start to set the wake-on-lan option)
Leave a comment:
-
I have the micro-atx version of this board and I had alot of trouble booting into linux at first, it would only work 1 out of every 3 boots. I updated to a 3.0 kernel in Ubuntu 11.04 and honestly that fixed all my problems. Boots like a charm. I'm running an i7 2600k and a Nvidia 450GT, I havent tried any of the onboard video connections.
Leave a comment:
-
Originally posted by puntarenas View PostI've read a lot of those bugreports when searching for a solution to my problem...
...but the symptoms were different to mine. For me the r8169 kernel driver always worked stable and without any problems when booting directly into Linux. With the AsRock Z68 Pro3 it now only worked reliable as long as Windows was not in between reboots, but besides that I have also nothing to complain. The ASUS P8P67 had no problems at all and that is why I still believe that there is something at least suboptimal within the AsRock UEFI.
I will send a short mail to AsRock again with a link to this discussion. Either they want to assist kernel developers, put some pressure on Realtek in doing so, fix their UEFI themselves or will again completely ignore my mail.
Leave a comment:
-
Originally posted by buzz View PostIt's a kernel driver issue. there are reports from other boards on kernel bugzilla with similar problems.
on kernels after .38 you get no connectivity at all. .38 sort of worked but disconnected constantly.
I will send a short mail to AsRock again with a link to this discussion. Either they want to assist kernel developers, put some pressure on Realtek in doing so, fix their UEFI themselves or will again completely ignore my mail.
Leave a comment:
-
Originally posted by puntarenas View PostNow I don't know who finally is to blame, AsRock or kernel developers?
on kernels after .38 you get no connectivity at all. .38 sort of worked but disconnected constantly.
Leave a comment:
-
Originally posted by buzz View Postyou need to use the driver from the vendor site, rather than the kernel one the in kernel 8169 doesn't work right.
On the other hand, I should not be forced to compile the vendors driver, as upstream drivers work fine as long as Windows is not involved in a reboot cycle. Using the Realtek driver also isn't an option with live media (like SysRescCD, Knoppix, or installation media e.g.) and as long as this mainboard (or the upstream kernel driver, fair enough...) doesn't properly reset the Realtek NIC on reboot, one always has to remember completely shutting down Windows before booting into any Linux with just the kernel driver availiable.
Now I don't know who finally is to blame, AsRock or kernel developers?
Leave a comment:
-
Originally posted by puntarenas View PostUnfortunately this mainboard has problems with dual boot setups using Linux besides Windows 7-x64, warmstarts result in networking problems. Whenever I boot into Windows, the NIC goes nuts in an "em1: link up" loop after rebooting into Linux, which makes it unusable. You always have to completely shutdown the system after using Windows, otherwise you will end up without reliable networking under Linux:
Hello everybody, my NIC drives me crazy and I need some help to gather all relevant informations to file a decent bug report. Maybe someone could guide me through this process. My mainboard is an AsRock Z68 Pro3 http://www.asrock.com/mb/overview.asp?Model=Z68%20Pro3&cat=Specifications I use a dual-boot setup with Windows7 installed in parallel to Fedora 15-x64. Whenever I had Windows in use and jjust reboot the system into Fedora, the NIC does not work as expected. Instead it goes in
I contacted AsRock support about the issue weeks ago but got no response yet and UEFI 1.60 didn't fix it either.
here's the one I use (same as vendor one with a minor change in the install script to work on new kernels
Leave a comment:
-
Originally posted by Kano View PostDid you try a Win driver update from http://www.realtek.com.tw ?
If needed you can activate wol in the driver options - or disable if active.
I would say, this is even worse, but one may argue it doesn't matter if the network is completely unreliable or doesn't work at all. Thanks for your input Kano, but I still believe AsRock should fix their UEFI and reset the RealteK NIC properly within reboot cycles.
BTW, I had an ASUS P8P67 with the same RTL8111E NIC before and no dual boot problems at all.
Leave a comment:
-
Did you try a Win driver update from http://www.realtek.com.tw ? If needed you can activate wol in the driver options - or disable if active.Last edited by Kano; 30 July 2011, 02:27 AM.
Leave a comment:
Leave a comment: