bashPenguin
Gawd
- Joined
- Jan 10, 2007
- Messages
- 607
Hey everyone,
I just got around to installing Arch Linux 0.8 with the 2.6.20 kernel onto my new build, and upon first use, I started getting problems when trying to install packages.
After downloading files, I end up with some corrupted files, and then my system gives me an error:
As well as
Now, I know my motherboard has some fairly new stuff like the Marvell NIC and the JMicron IDE controller, plus I run in AHCI mode with all my SATA drives. Right now I'm pointing to the driver for my Marvell NIC (the new sky2 module), so I was wondering if any of you ran a system that used a Marvell NIC that used the sky2 module?
System specs:
Gigabyte 965P DQ6
Core 2 Duo E6300
nVidia Geforce 8800GTS
2 GB RAM (5-5-5-15)
Onboard Marvel 8056 controller (sky2 module)
Realtek AL888DD onboard sound
The system is, as far as I can verify, not unstable. It is overclocked from 1.83 Ghz to 2.8 Ghz, it has survived overnight memtest86+ runs as well as a 12 hour Orthos testing of both cores, so I don't think it's a hardware problem - I really think it's driver related.
Thanks!
I just got around to installing Arch Linux 0.8 with the 2.6.20 kernel onto my new build, and upon first use, I started getting problems when trying to install packages.
After downloading files, I end up with some corrupted files, and then my system gives me an error:
Code:
Unable to handle kernel paging request at virtual address
As well as
Code:
Soft lockup detected on CPU #0!
Now, I know my motherboard has some fairly new stuff like the Marvell NIC and the JMicron IDE controller, plus I run in AHCI mode with all my SATA drives. Right now I'm pointing to the driver for my Marvell NIC (the new sky2 module), so I was wondering if any of you ran a system that used a Marvell NIC that used the sky2 module?
System specs:
Gigabyte 965P DQ6
Core 2 Duo E6300
nVidia Geforce 8800GTS
2 GB RAM (5-5-5-15)
Onboard Marvel 8056 controller (sky2 module)
Realtek AL888DD onboard sound
The system is, as far as I can verify, not unstable. It is overclocked from 1.83 Ghz to 2.8 Ghz, it has survived overnight memtest86+ runs as well as a 12 hour Orthos testing of both cores, so I don't think it's a hardware problem - I really think it's driver related.
Thanks!