Search options (Page 1 of 3)

That was worryingly easy. Thanks!

I was also looking for a new email service and after a bit of research signed up for Lavabit last week. Just thought I'd see if anyone on here was using it and it looks like it gets the #! community thumbs-up!

Registered via Launchpad with no problems (plus I get a simpler username!)

The first suggestion didn't help - I just lost the mention of "Wireless networks" in the NetworkManager window.

I am using NetworkManager, and have already tried wicd with no luck.

Here are the outputs of the two commands:

:~$ sudo cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

:~$ dmesg | egrep -A 4 'phy0|rt28'
rt2800pci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
rt2800pci 0000:02:00.0: setting latency timer to 64
phy0: Selected rate control algorithm 'minstrel_ht'
Registered led device: rt2800pci-phy0::radio
Registered led device: rt2800pci-phy0::assoc
Registered led device: rt2800pci-phy0::quality
rt2860sta: module is from the staging directory, the quality is unknown, you have been warned.
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:01:00.0: setting latency timer to 64
--
phy0 -> rt2800_load_firmware: Error - PBF system register not ready.
r8169 0000:05:00.0: eth0: link up
r8169 0000:05:00.0: eth0: link up
NET: Registered protocol family 17
phy0 -> rt2800_load_firmware: Error - PBF system register not ready.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
--
phy0 -> rt2800_load_firmware: Error - PBF system register not ready.
phy0 -> rt2800_load_firmware: Error - PBF system register not ready.
rt2800pci 0000:02:00.0: PCI INT A disabled
rt2800pci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
rt2800pci 0000:02:00.0: setting latency timer to 64
phy1: Selected rate control algorithm 'minstrel_ht'
Registered led device: rt2800pci-phy1::radio
Registered led device: rt2800pci-phy1::assoc
Registered led device: rt2800pci-phy1::quality
phy1 -> rt2800_load_firmware: Error - PBF system register not ready.
phy1 -> rt2800_load_firmware: Error - PBF system register not ready.

I won't have access to my linux box until later today, but I know the wireless device is the Ralink RT2860.

It worked perfectly with the live CD and the initial #! install and I assume that it's now broken because I updated to the Liquorix kernel. Is this normal?

I found this fix on the Debian wiki: http://wiki.debian.org/rt2860sta#Squeeze - do you think this will work? In addition, it looks like I may need to use wicd instead of NetworkManager.

I'll report back later. Apologies for this new problem not having much to do with the thread title. I'll start a new thread if necessary...

Thanks for the replies. I tried the solution described by xaos52 and it did complain about the gcc version, which I overruled. However I then got another error message, "Unable to find the kernel source tree for the currently running kernel".

I have now done another fresh install and this time chose to use the Liquorix kernel (without trying to install the Nvidia driver). After a reboot, the display is much better with resolution at 1920x1080.

So unless I run into problems with games or videos, I think I'll give up on the 285.05.09 driver.

Incidentally, if it's from Scotland it's called whisky, if it's from Ireland or the USA it's whiskey.

I ended up installing the Liquorix kernel, which has solved the problem.

Having done some research, I found this Debian bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619019

Seems to be a problem with the kernel, and downgrading the kernel should fix the problem. I don't know how to do this though...

As a very rough fix, you can suspend or hibernate then log back in and the cursor should appear.

Yesterday it wasn't working, today it shows up straight away. Thanks for the reply, I'm saying this is solved as I guess it's a problem with my DVD drive.