RTNETLINK answers: No such device

Actually I have the same problem Brent Goldberg reported on 7th of april.

The answer he got was not helping him and me a lot. First of all why
should anyone set it's default route to the wlan??? I want to access to my
network and beyond not to my localmachine. Maybe I am misinterpreting what
was really meant in that answer???

Second, the answer mentions an option in YAST to set a default route??
Where is that and how should one make one???

In my case I got the driverloader to work and have worked wireless for
some time. I did have to put the eth0 in manual mode or it would fail too.
Until I had to work wired at my office because there was no wireless
facility at that time. Once back home my wlan never came up again. The
only thing I receive is:

Jul  7 22:47:36 Hymir kernel: driverloader: stack=8192/60/0 REGPARM SMP
Jul  7 22:47:36 Hymir kernel: usbcore: registered new driver driverloader
Jul  7 22:47:37 Hymir kernel: driverloader: bcmwl5.sys:
0xf8e81000..0xf8edb180 entry = f8e8cdd2 (pbase = 0x1
0000)
Jul  7 22:47:37 Hymir kernel: ACPI: PCI interrupt 0000:02:03.0[A] -> GSI
17 (level, low) -> IRQ 201
Jul  7 22:47:37 Hymir kernel: 0000:02:03.0: cache line size not set;
forcing 32
Jul  7 22:47:37 Hymir kernel: wlan0: New link status: Disconnected (0002)
Jul  7 22:47:38 Hymir kernel: wlan0: WPA, AES, TKIP, WEP128, WEP64 supported
Jul  7 22:47:38 Hymir kernel: wlan0: at 0000:02:03.0 (MAC address MY MAC
ADDRESS) ready
Jul  7 22:47:39 Hymir dhcpcd[16229]: terminating on signal 15
Jul  7 22:47:39 Hymir dhcpcd-hook: Skipping 'ifdown $INTERFACE -o dhcp' call
Jul  7 22:47:39 Hymir kernel: usbcore: deregistering driver driverloader
Jul  7 22:47:40 Hymir kernel: driverloader: stack=8192/60/0 REGPARM SMP
Jul  7 22:47:40 Hymir kernel: usbcore: registered new driver driverloader
Jul  7 22:47:40 Hymir kernel: driverloader: bcmwl5.sys:
0xf8e81000..0xf8edb180 entry = f8e8cdd2 (pbase = 0x1
0000)
Jul  7 22:47:40 Hymir kernel: ACPI: PCI interrupt 0000:02:03.0[A] -> GSI
17 (level, low) -> IRQ 201
Jul  7 22:47:40 Hymir kernel: 0000:02:03.0: cache line size not set;
forcing 32
Jul  7 22:47:41 Hymir kernel: wlan0: New link status: Disconnected (0002)
Jul  7 22:47:42 Hymir kernel: wlan0: WPA, AES, TKIP, WEP128, WEP64 supported
Jul  7 22:47:42 Hymir kernel: wlan0: at 0000:02:03.0 (MAC address MY MAC
ADDRESS) ready
Jul  7 22:47:44 Hymir ifup-route: Error while executing:
Jul  7 22:47:44 Hymir ifup-route: Command 'ip route replace to
169.254.0.0/16 dev wlan0' returned:
Jul  7 22:47:44 Hymir ifup-route: RTNETLINK answers: No such device
Jul  7 22:47:44 Hymir ifup-route: Configuration line: 169.254.0.0 -
255.255.0.0 wlan0
Jul  7 22:47:44 Hymir kernel: wlan0: New link status: Connected (0001)
Jul  7 22:47:45 Hymir kernel: wlan0: New link status: Disconnected (0002)

Somehow I suspect that the eth0 and the wlan0 cannot coexist and the
routing gets confused. Iwconfig, iwlist all show that the driver works and
the access point is recognized .... I hope you can help me with this
problem.

Regards,
Siebe