Problems after Kernel update
Hi
I updated my Kernel to version 4.6.9 and it seemed to work just as it should.... Until I tried to connect to the internet. I have to networking devices, and my realtec is detected as it should, but my onboard intel gigabit isn't detected in the new Kernel. What can I do to make this work. I got some graphics problems too, but we can discouss those when the first problem is solved. Best regards Rohde |
ups 2.6.9
Went a little fast writing... *blushes* |
please post the results of these run as root:
Code:
ifconfig |
I presume you wanted the results for my new kerned, so here they are:
ifconfig eth0 Link encap:Ethernet HWaddr 00:50:8D:F5:24:77 inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1662 (1.6 Kb) TX bytes:2798 (2.7 Kb) Base address:0xa000 Memory:fc000000-fc020000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lsmod | grep e1 // no results modprobe e1000 FATAL: Module e1000 not found. |
It seems that the e1000 isn't installed, so I found it on intels page, and I'll try if I can figure e1000 out ;)
|
Ok I finallly got the e1000 module installed, and modprobe e1000 doesn't give any error any more, but the lsmod | grep e1 doesn't give any results, and the ifconfig still doesn't give any information about eth1.
To me it seems everything is set up correctly, any ideas what went wrong? |
Ok, don't ask me how, but now the internet works :D
Next problem. I got an radeon 9600pro, and I want to be able to use openGL-graphics. I got the fglrx driver installed, and that part seems to work fine, except it seems like my motherboard and the graphics-card wont cooporate the right way. I had a problem in windows too, because it tried to run in AGP 8x (whith should be supported), but after manually setting it to 4x in the driver settings it worked fine. I think it is the same problem again, but I'm not sure. Any ideas how to fix that? |
All times are GMT -5. The time now is 05:04 PM. |