Closed GoogleCodeExporter closed 9 years ago
Just noticed that this exact error is addressed in the Troubleshooting
directory...
Let me give it a shot...
Original comment by cpmitc...@gmail.com
on 14 Aug 2009 at 7:27
Troubleshooting guide says:
NVIDIA: could not open the device file /dev/nvidiactl (No such file or
directory).
Ensure that the 'nvidia' module has been successfully loaded. Taking a look at
the
kernel ringbuffer may give more help:
modprobe nvidia
dmesg | tail
On my system, the modprobe nvidia command comes back with no error and no other
output other than the system prompt.
The next command dmesg | tail shows the last event to be related to the DHCP
address pulled:
EXT3 FS on hda1, internal journal
ip_tables: (C) 2000-2006 Netfilter Core Team
powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ processors
(2
cpu cores) (version 2.20.00)
[Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a
way
that Linux understands. Please report this to the Linux ACPI maintainers and
complain to your BIOS vendor.
[Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a
way
that Linux understands. Please report this to the Linux ACPI maintainers and
complain to your BIOS vendor.
eth1: no link during initialization.
eth1: link up.
And that's it.
Suggestions?
Original comment by cpmitc...@gmail.com
on 14 Aug 2009 at 7:38
Filter nvidia-related messages with "dmesg | grep nvidia" and post the results.
Original comment by lukas.l...@gmail.com
on 14 Aug 2009 at 7:50
Lukas,
Got it working. It may be related to non-root user doing the modprobe command.
Switched to root user, performed modprobe nvidia, dmesg | grep nvidia shows
related
output, and the card was recognizable once again. Thanks for your support!
Please
close the ticket.
Original comment by cpmitc...@gmail.com
on 14 Aug 2009 at 8:00
closed
Original comment by lukas.l...@gmail.com
on 14 Aug 2009 at 8:11
Original issue reported on code.google.com by
cpmitc...@gmail.com
on 14 Aug 2009 at 7:14