If you undestand german, then this help you. http://www.vdr-portal.de/board/thread.php?threadid=40130&hilight=nvram daliman
Am Freitag, 19. Mai 2006 14:07 schrieb Joerg Riechardt:
With Suse 10.1 /dev/nvram is gone after every reboot. What´s the right way to create /dev/nvram under Suse 10.1? Jörg
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hello, If you can not understand german: Here is what they wrote in the mentioned article.
edit the file /etc/udev/static_devices.txt and add the following line: nvram c 10 144
Best regards Halim
daliman schrieb:
If you undestand german, then this help you. http://www.vdr-portal.de/board/thread.php?threadid=40130&hilight=nvram daliman
Am Freitag, 19. Mai 2006 14:07 schrieb Joerg Riechardt:
With Suse 10.1 /dev/nvram is gone after every reboot. What´s the right way to create /dev/nvram under Suse 10.1? Jörg
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Well that IS what I do, but it´s only a workaround. The Suse installer moved my static_devices.txt to static_devices.txt.rpmsave, probably there is a reason for that, I wonder how the "correct" udev solution looks. Jörg
On Fri, 19 May 2006, Joerg Riechardt (JR) wrote:
Well that IS what I do, but it´s only a workaround. The Suse installer moved my static_devices.txt to static_devices.txt.rpmsave, probably there is a reason for that, I wonder how the "correct" udev solution looks.
shouldn't the device be automatically created when you load the module nvram?
Sergei
Sergei Haller schrieb:
On Fri, 19 May 2006, Joerg Riechardt (JR) wrote:
Well that IS what I do, but it´s only a workaround. The Suse installer moved my static_devices.txt to static_devices.txt.rpmsave, probably there is a reason for that, I wonder how the "correct" udev solution looks.
shouldn't the device be automatically created when you load the module nvram?
Sergei
Yes, when I load nvram.ko /dev/nvram is created. But with Suse 10.0. I did not had to load nvram.ko, but /dev/nvram was created by the entry in static_devices.txt, and that was sufficient. Should nvram be loaded by some automatism, or do I have to put it in boot.local? Jörg
On Sat, May 20, 2006 at 04:46:03PM +0200, Joerg Riechardt wrote:
Sergei Haller schrieb:
On Fri, 19 May 2006, Joerg Riechardt (JR) wrote:
Well that IS what I do, but it´s only a workaround. The Suse installer moved my static_devices.txt to static_devices.txt.rpmsave, probably there is a reason for that, I wonder how the "correct" udev solution looks.
shouldn't the device be automatically created when you load the module nvram?
SergeiYes, when I load nvram.ko /dev/nvram is created. But with Suse 10.0. I did not had to load nvram.ko, but /dev/nvram was created by the entry in static_devices.txt, and that was sufficient. Should nvram be loaded by some automatism, or do I have to put it in boot.local? Jörg
Run
vi +/MODULES_LOADED_ON_BOOT /etc/sysconfig/kernel
read the text above and just do what you've read:)
Werner
Dr. Werner Fink schrieb:
On Sat, May 20, 2006 at 04:46:03PM +0200, Joerg Riechardt wrote:
Sergei Haller schrieb:
On Fri, 19 May 2006, Joerg Riechardt (JR) wrote:
Well that IS what I do, but it´s only a workaround. The Suse installer moved my static_devices.txt to static_devices.txt.rpmsave, probably there is a reason for that, I wonder how the "correct" udev solution looks.
shouldn't the device be automatically created when you load the module nvram?
SergeiYes, when I load nvram.ko /dev/nvram is created. But with Suse 10.0. I did not had to load nvram.ko, but /dev/nvram was created by the entry in static_devices.txt, and that was sufficient. Should nvram be loaded by some automatism, or do I have to put it in boot.local? Jörg
Run
vi +/MODULES_LOADED_ON_BOOT /etc/sysconfig/kernel
read the text above and just do what you've read:)
Werner
thanks, Jörg
-
daliman -
Dr. Werner Fink -
Halim Sahin -
Joerg Riechardt -
Sergei Haller