I ran apt-get upgrade today to get all of the new security updates, which installed a new kernel on my machine. I therefore rebooted, and now I can use my wireless nic.
This nic was configured perfectly by the installation wizard, so I've never had to touch it. Here's the important info:
* Chipsest: Marvel
* Location: eth2
In the past, I always assumed that the installation wizard installed ndiswrapper since it's my understanding that a native Linux driver for the wireless Marvel chipset does not exist. However, I then ran `dpkg -l` to see which version of ndiswrapper was installed, and it wasn't.
So I guess I have two questions:
* First, has anyone else had a networking problem after the kernel upgrade?
* Second, if there is a native driver for the wireless Marvel chipset, what's it called? I checked my modules directory, but didn't see anything with the word "marvel" in it.
Thanks in advance for any help you can give me!
Tom Purl
This nic was configured perfectly by the installation wizard, so I've never had to touch it. Here's the important info:
* Chipsest: Marvel
* Location: eth2
In the past, I always assumed that the installation wizard installed ndiswrapper since it's my understanding that a native Linux driver for the wireless Marvel chipset does not exist. However, I then ran `dpkg -l` to see which version of ndiswrapper was installed, and it wasn't.
So I guess I have two questions:
* First, has anyone else had a networking problem after the kernel upgrade?
* Second, if there is a native driver for the wireless Marvel chipset, what's it called? I checked my modules directory, but didn't see anything with the word "marvel" in it.
Thanks in advance for any help you can give me!
Tom Purl
Comment