Bug#449116: linux-image-2.6.22-2-ixp4xx: The module rtc-dev is not included

2007-11-03 Thread Stefan Carslöv
Package: linux-image-2.6.22-2-ixp4xx
Version: 2.6.22-4~bpo40+1
Severity: normal

On my NSLU2 machine the script /etc/init.d/nslu2-rtc generates a
FATAL: Module rtc-dev not found.

A little investigation reveals that the module (and also others in 
the rtc directory) is not included in this kernel packages, but it
was in the linux-image-2.6.18-5-ixp4xx.

Here is the differens in the rtc directory between these two packages:

linux-image-2.6.22-2-ixp4xx
/lib/modules/2.6.22-2-ixp4xx/kernel/drivers/rtc/rtc-cmos.ko
/lib/modules/2.6.22-2-ixp4xx/kernel/drivers/rtc/rtc-ds1307.ko
/lib/modules/2.6.22-2-ixp4xx/kernel/drivers/rtc/rtc-ds1553.ko
/lib/modules/2.6.22-2-ixp4xx/kernel/drivers/rtc/rtc-ds1742.ko
/lib/modules/2.6.22-2-ixp4xx/kernel/drivers/rtc/rtc-isl1208.ko
/lib/modules/2.6.22-2-ixp4xx/kernel/drivers/rtc/rtc-max6900.ko
/lib/modules/2.6.22-2-ixp4xx/kernel/drivers/rtc/rtc-max6902.ko
/lib/modules/2.6.22-2-ixp4xx/kernel/drivers/rtc/rtc-pcf8583.ko
/lib/modules/2.6.22-2-ixp4xx/kernel/drivers/rtc/rtc-rs5c348.ko
/lib/modules/2.6.22-2-ixp4xx/kernel/drivers/rtc/rtc-v3020.ko

linux-image-2.6.18-5-ixp4xx
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-dev.ko
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-ds1307.ko
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-ds1553.ko
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-ds1742.ko
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-isl1208.ko
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-max6902.ko
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-pcf8583.ko
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-proc.ko
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-rs5c348.ko
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-sysfs.ko
/lib/modules/2.6.18-5-ixp4xx/kernel/drivers/rtc/rtc-v3020.ko

As you can see the rtc-dev.ko, rtc-proc.ko and rtc-sysfs.ko are
not built.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: arm (armv5tel)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.22-2-ixp4xx
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.22-2-ixp4xx depends on:
ii  coreutils 5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85h  tools for generating an initramfs
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo

linux-image-2.6.22-2-ixp4xx recommends no packages.

-- debconf information:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.22-2-ixp4xx/preinst/overwriting-modules-2.6.22-2-ixp4xx: true
  linux-image-2.6.22-2-ixp4xx/postinst/old-dir-initrd-link-2.6.22-2-ixp4xx: true
  linux-image-2.6.22-2-ixp4xx/preinst/lilo-has-ramdisk:
  linux-image-2.6.22-2-ixp4xx/postinst/depmod-error-initrd-2.6.22-2-ixp4xx: 
false
  linux-image-2.6.22-2-ixp4xx/postinst/create-kimage-link-2.6.22-2-ixp4xx: true
  linux-image-2.6.22-2-ixp4xx/preinst/abort-install-2.6.22-2-ixp4xx:
  linux-image-2.6.22-2-ixp4xx/prerm/removing-running-kernel-2.6.22-2-ixp4xx: 
true
  linux-image-2.6.22-2-ixp4xx/postinst/bootloader-test-error-2.6.22-2-ixp4xx:
  linux-image-2.6.22-2-ixp4xx/preinst/elilo-initrd-2.6.22-2-ixp4xx: true
  linux-image-2.6.22-2-ixp4xx/postinst/bootloader-error-2.6.22-2-ixp4xx:
  linux-image-2.6.22-2-ixp4xx/preinst/failed-to-move-modules-2.6.22-2-ixp4xx:
  linux-image-2.6.22-2-ixp4xx/postinst/old-system-map-link-2.6.22-2-ixp4xx: true
  linux-image-2.6.22-2-ixp4xx/preinst/bootloader-initrd-2.6.22-2-ixp4xx: true
  linux-image-2.6.22-2-ixp4xx/preinst/initrd-2.6.22-2-ixp4xx:
  linux-image-2.6.22-2-ixp4xx/preinst/abort-overwrite-2.6.22-2-ixp4xx:
  linux-image-2.6.22-2-ixp4xx/postinst/old-initrd-link-2.6.22-2-ixp4xx: true
  
linux-image-2.6.22-2-ixp4xx/prerm/would-invalidate-boot-loader-2.6.22-2-ixp4xx: 
true
* linux-image-2.6.22-2-ixp4xx/preinst/already-running-this-2.6.22-2-ixp4xx:
  linux-image-2.6.22-2-ixp4xx/postinst/kimage-is-a-directory:
  linux-image-2.6.22-2-ixp4xx/preinst/lilo-initrd-2.6.22-2-ixp4xx: true
  linux-image-2.6.22-2-ixp4xx/postinst/depmod-error-2.6.22-2-ixp4xx: false



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#449116: linux-image-2.6.22-2-ixp4xx: The module rtc-dev is not included

2008-06-10 Thread Martin Michlmayr
* Stefan Carslöv <[EMAIL PROTECTED]> [2007-11-03 10:07]:
> On my NSLU2 machine the script /etc/init.d/nslu2-rtc generates a
> FATAL: Module rtc-dev not found.
> 
> A little investigation reveals that the module (and also others in 
> the rtc directory) is not included in this kernel packages, but it
> was in the linux-image-2.6.18-5-ixp4xx.
> 
> Here is the differens in the rtc directory between these two packages:
...
> As you can see the rtc-dev.ko, rtc-proc.ko and rtc-sysfs.ko are
> not built.

Sorry for not responding earlier.  These modules are now built into
the kernel.

Do you have any problems with RTC or do things work correctly?

-- 
Martin Michlmayr
http://www.cyrius.com/



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#449116: linux-image-2.6.22-2-ixp4xx: The module rtc-dev is not included

2008-06-10 Thread Stefan
tisdagen den 10 juni 2008 skrev Martin Michlmayr:
> * Stefan Carslöv <[EMAIL PROTECTED]> [2007-11-03 10:07]:
> > On my NSLU2 machine the script /etc/init.d/nslu2-rtc generates a
> > FATAL: Module rtc-dev not found.
> >
> > A little investigation reveals that the module (and also others in
> > the rtc directory) is not included in this kernel packages, but it
> > was in the linux-image-2.6.18-5-ixp4xx.
> >
> > Here is the differens in the rtc directory between these two packages:
>
> ...
>
> > As you can see the rtc-dev.ko, rtc-proc.ko and rtc-sysfs.ko are
> > not built.
>
> Sorry for not responding earlier.  These modules are now built into
> the kernel.
>
> Do you have any problems with RTC or do things work correctly?

No, I havn't noticed anything else but the mentioned "FATAL" message. And I 
now see that the message no longer appears. So I think it's working OK.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]