[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: util-linux: FTBFS on m68k



On Tue, 26 Oct 2010, Thorsten Glaser wrote:

> @debian-68k, what method do we use now, /dev/rtc or something other?

From memory, I'm pretty sure hwclock depends on the /dev/rtc interface on 
m68k. But it was some years ago that I looked through that source code.

> My ARAnyM systems don’t have a /dev/rtc but since there is no devfs any 
> more, I don’t know whether I need to do some- thing to make it have one, 
> or how to find out if it works…

Thankfully, Linux does have a sort of "devfs" again, only it is called 
"devtmpfs". It is completely different than the old one as it is derived 
from the device model.

If CONFIG_GEN_RTC was disabled at compile time, you need a new kernel. If 
it was enabled then perhaps you need to load the module.

/me goes looking at the kernel config...

debian-2.6-2.6.32-23-atari-dot-config:
CONFIG_DEVTMPFS=y
CONFIG_GEN_RTC=m

From drivers/char/Kconfig:

config GEN_RTC
        tristate "Generic /dev/rtc emulation"
        depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && 
!FRV && !S390 && !SUPERH && !AVR32 && !BLACKFIN
        ---help---
          If you say Y here and create a character special file /dev/rtc with
          major number 10 and minor number 135 using mknod ("man mknod"), you
          will get access to the real time clock (or hardware clock) built
          into your computer.

          It reports status information via the file /proc/driver/rtc and its
          behaviour is set by various ioctls on /dev/rtc. If you enable the
          "extended RTC operation" below it will also provide an emulation
          for RTC_UIE which is required by some programs and may improve
          precision in some cases.

          To compile this driver as a module, choose M here: the
          module will be called genrtc.


Try this:
# modprobe genrtc
# grep rtc /proc/devices

You should see "254 rtc".

# ls -l /dev/rtc*

(You may see a /dev/rtc -> /dev/rtc0 symlink.)

If the special file wasn't created automatically it is probably becuase 
either devtmpfs is not mounted on /dev or else because udev is not running 
(both are generally used together but either should work alone... I don't 
know how squeeze/sid does things.)

HTH
Finn

> 
> bye,
> //mirabilos
> 

Reply to: