Anyone else having problems with feisty since this morning's update?

[NoOp]

On 03/19/2007 04:13 PM, NoOp wrote:
> On 03/19/2007 10:06 AM, Ed Smits wrote:
>> I've had no problems through the various kernel updates until this
>> morning, installed
>> kernel 2.6.20-12-generic along with headers etc, can't boot into it,
>> had to choose the previous kernel to get up and running.
>> 
>> I won't be able to try and figure out what's up for a while, minor
>> emergency here, just wanted to know if others are seeing anything as
>> well
>> 
>> ED
>> 
> 
> Worked fine for me. Networking interfaces is still not fixed
> (https://launchpad.net/ubuntu/+source/network-manager/+bug/92085) so I
> have to physically connect a keyboard, monitor & mouse on boot then
> sudo /etc/init.d/networking restart
> to get neworking going. But other than that it booted following the
> updates just fine.
> 
> HW: 300Mhz PII 284Mb RAM old 6GB Quantum Fireball & 4Gb Samsung SV0432A
> hard drives, Winbond W89C940 NIC card, Trident 3DImage 9850 video card,
> MegaImage Vido monitor, Logitec C46 mouse.
> 
> 

I take that back. Yesterday I just rebooted. Last night I turned the
machine off and booted this morning to find that networking didn't even
work with sudo /etc/init.d/networking restart. Tried just about
everything I could think of; uninstalled network-manager (reinstalled
gedit after it gets removed from the meta uninstall... who'da thought
uninstalling network-manager would also uninstall gedit...) & rebooted,
same problem. Now here's the odd part: I plugged in the Airlink 101 USB
ethernet connector and all of sudden my Winbond NIC starts working.
Unplug the Airlink & the Winbond is still working. I'd file an added
comment to my bug report, but I'll be darned if I can figure out why
this worked, or what is actually causing the problems.