Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded
Hi, I've installed udev 0.125 from unstable on testing and it seems to fix the issue. The rtc-cmos module is automatically loaded. If udev 0.125 enters testing, it should not be a problem (for me). i had the same problem, fixed installing new udev version. The rtc-cmos is automatically loaded regardless of udev version but in the new rtc infrastructure the device files are named /dev/rtc0,/dev/rtc1,...,/dev/rtcn. What the new version of udev do, starting from version 0.124-1, is to automatically create a symlink /dev/rtc - /dev/rtc0 as explained in changelog: * udev.rules: added a rtc symlink to rtc0. Regards, Andrea. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-1 Severity: normal Hi, When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. When I look in /dev, the /dev/rtc* device is not there. The device was working OK with the 2.6.25 kernel. It seems CONFIG_RTC is no longer set in the 2.6.26 config? It seems is was unset to fix #476970 to allow more specific modules to load. When I loaded the rtc_cmos driver, hwclock worked OK. Should the kernel/udev not load this/the correct module automatically? Regards, Rik -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Jul 30 18:46:19 UTC 2008 ** Command line: root=/dev/mapper/vg00-root ro vga=791 quiet ** Tainted: P (1) ** Kernel log: [ 14.328154] ACPI: Power Button (CM) [PBTN] [ 14.331011] input: Sleep Button (CM) as /class/input/input5 [ 14.360464] ACPI: PCI Interrupt :00:1f.3[B] - GSI 17 (level, low) - IRQ 17 [ 14.394842] ACPI: Sleep Button (CM) [SBTN] [ 14.736027] ACPI: AC Adapter [AC] (off-line) [ 14.740446] ACPI: WMI: Mapper loaded [ 14.749216] ACPI: device:2f is registered as cooling_device2 [ 14.749941] input: Video Bus as /class/input/input6 [ 14.807051] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [ 14.868341] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks [ 14.868839] iwl3945: Copyright(c) 2003-2008 Intel Corporation [ 14.868839] ACPI: PCI Interrupt :0c:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 14.868839] PCI: Setting latency timer of device :0c:00.0 to 64 [ 14.868839] iwl3945: Detected Intel Wireless WiFi Link 3945ABG [ 14.944843] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels [ 14.956259] phy0: Selected rate control algorithm 'iwl-3945-rs' [ 14.970388] Synaptics Touchpad, model: 1, fw: 6.2, id: 0xfa0b1, caps: 0xa04713/0x20 [ 15.007498] input: SynPS/2 Synaptics TouchPad as /class/input/input7 [ 15.096096] ACPI: PCI interrupt for device :0c:00.0 disabled [ 15.348674] ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 21 [ 15.360525] PCI: Setting latency timer of device :00:1b.0 to 64 [ 15.369837] Error: Driver 'pcspkr' is already registered, aborting... [ 17.355844] EXT3 FS on dm-1, internal journal [ 17.644038] loop: module loaded [ 19.447922] fuse init (API version 7.9) [ 19.536452] kjournald starting. Commit interval 5 seconds [ 19.551061] EXT3 FS on sda5, internal journal [ 19.562835] EXT3-fs: mounted filesystem with ordered data mode. [ 19.611771] kjournald starting. Commit interval 5 seconds [ 19.621836] EXT3 FS on dm-3, internal journal [ 19.633572] EXT3-fs: mounted filesystem with ordered data mode. [ 19.699688] Adding 4194296k swap on /dev/mapper/vg00-swap. Priority:-1 extents:1 across:4194296k [ 21.069599] ip_tables: (C) 2000-2006 Netfilter Core Team [ 21.751955] ACPI: PCI Interrupt :0c:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 21.763920] PM: Writing back config space on device :0c:00.0 at offset 1 (was 100102, writing 100106) [ 21.764196] firmware: requesting iwlwifi-3945-1.ucode [ 22.011728] Registered led device: iwl-phy0:radio [ 22.025107] Registered led device: iwl-phy0:assoc [ 22.036883] Registered led device: iwl-phy0:RX [ 22.048419] Registered led device: iwl-phy0:TX [ 22.123235] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 24.589087] NET: Registered protocol family 10 [ 24.589087] lo: Disabled Privacy Extensions [ 24.589087] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 24.589397] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 27.891554] wlan0: Initial auth_alg=0 [ 27.891554] wlan0: authenticate with AP 00:0f:cb:fc:04:ea [ 27.893034] wlan0: RX authentication from 00:0f:cb:fc:04:ea (alg=0 transaction=2 status=0) [ 27.893034] wlan0: authenticated [ 27.893034] wlan0: associate with AP 00:0f:cb:fc:04:ea [ 27.980019] wlan0: RX AssocResp from 00:0f:cb:fc:04:ea (capab=0x431 status=0 aid=1) [ 27.980019] wlan0: associated [ 27.980555] wlan0: switched to short barker preamble (BSSID=00:0f:cb:fc:04:ea) [ 27.980555] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 31.549631] pnp: the driver 'parport_pc' has been registered [ 31.550257] lp: driver loaded but no devices found [ 31.594146] ppdev: user-space parallel port driver [ 37.385590] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use) [ 38.829547] wlan0: no IPv6 routers present [ 39.959410] Bluetooth: Core ver 2.11 [ 39.975411] NET: Registered protocol family 31 [ 39.988073] Bluetooth: HCI device and connection manager initialized [ 39.998087] Bluetooth: HCI socket layer initialized [ 40.055994] Bluetooth: L2CAP ver 2.9 [ 40.067295] Bluetooth: L2CAP socket layer initialized
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
notfixed 476970 2.6.26-1 reopen 476970 tags 476970 - pending found 476970 2.6.26-1 severity 493567 important merge 476970 493567 tags 493567 + confirmed kthxbye On Sun, Aug 3, 2008 at 1:00 PM, Rik Theys [EMAIL PROTECTED] wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. piti:~# hwclock --debug --show hwclock from util-linux-ng 2.13.1.1 hwclock: Open of /dev/rtc failed, errno=2: No such file or directory. No usable clock interface found. Cannot access the Hardware Clock via any known method. It seems CONFIG_RTC is no longer set in the 2.6.26 config? It seems is was unset to fix #476970 to allow more specific modules to load. In 2.6.25 we have CONFIG_RTC=y, but on 2.6.26 this is not even selected as a module. Please select both CONFIG_RTC and CONFIG_GEN_RTC as modules. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
unmerge 476970 fixed 476970 2.6.26-1 tags 476970 pending severity 493567 normal tags 493567 - confirmed thanks On Sun, Aug 03, 2008 at 02:26:56PM +0300, Teodor wrote: notfixed 476970 2.6.26-1 reopen 476970 tags 476970 - pending found 476970 2.6.26-1 severity 493567 important merge 476970 493567 tags 493567 + confirmed kthxbye _STOP_ messing with bugs. The original bug was fixed. You are neither a maintainer of the kernel nor a submitter of any of this bugs. Bastian -- It is a human characteristic to love little animals, especially if they're attractive in some way. -- McCoy, The Trouble with Tribbles, stardate 4525.6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. I see it. The oldstyle rtc is disabled if the new infrastructure is enabled. To make this work the following changes seems to be needed: - RTC_CLASS=y - RTC_HCTOSYS=y - RTC_DRV_CMOS=y Bastian -- Conquest is easy. Control is not. -- Kirk, Mirror, Mirror, stardate unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
On Sun, Aug 3, 2008 at 3:21 PM, Bastian Blank [EMAIL PROTECTED] wrote: _STOP_ messing with bugs. The original bug was fixed. You are neither a maintainer of the kernel nor a submitter of any of this bugs. Ok, I stand corrected since you know better. I apologize for any trouble created, it wasn't my intention. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote: On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. I see it. The oldstyle rtc is disabled if the new infrastructure is enabled. To make this work the following changes seems to be needed: Can you please test if this image fixes the problem? It includes the changes. http://194.39.182.225/debian/linux-2.6/linux-image-2.6.26-1-686_2.6.26-2_i386.deb The checksum is ae34a0ecad891c76a4ec8ee7c086d2e3eb2e0f6d67247b42a90dd673288b88e3 Bastian -- We fight only when there is no other choice. We prefer the ways of peaceful contact. -- Kirk, Spectre of the Gun, stardate 4385.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
Hi, On Sunday 03 August 2008 16:08:18 Bastian Blank wrote: On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote: On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. I see it. The oldstyle rtc is disabled if the new infrastructure is enabled. To make this work the following changes seems to be needed: Can you please test if this image fixes the problem? It includes the changes. http://194.39.182.225/debian/linux-2.6/linux-image-2.6.26-1-686_2.6.26-2_i3 86.deb The checksum is ae34a0ecad891c76a4ec8ee7c086d2e3eb2e0f6d67247b42a90dd673288b88e3 Thanks for your quick reply. Do you also have an amd64 image? Don't have any i386 systems running lenny/sid right now. Greetings, Rik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
On Sunday 03 August 2008 16:08:18 Bastian Blank wrote: On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote: On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. I see it. The oldstyle rtc is disabled if the new infrastructure is enabled. To make this work the following changes seems to be needed: Can you please test if this image fixes the problem? It includes the changes. http://194.39.182.225/debian/linux-2.6/linux-image-2.6.26-1-686_2.6.26-2_i3 86.deb The checksum is ae34a0ecad891c76a4ec8ee7c086d2e3eb2e0f6d67247b42a90dd673288b88e3 Bastian Hi, Could this be related to #452181? It was fixed in udev 0.124-3, but testing still has 0.114-2. Regards, Rik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26, rtc_cmos module must be manually loaded.
Hi, On Sunday 03 August 2008 16:08:18 Bastian Blank wrote: On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote: On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote: When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains during boot that it can not read the hardware clock using any known methods. I see it. The oldstyle rtc is disabled if the new infrastructure is enabled. To make this work the following changes seems to be needed: Can you please test if this image fixes the problem? It includes the changes. http://194.39.182.225/debian/linux-2.6/linux-image-2.6.26-1-686_2.6.26-2_i3 86.deb The checksum is ae34a0ecad891c76a4ec8ee7c086d2e3eb2e0f6d67247b42a90dd673288b88e3 I've installed udev 0.125 from unstable on testing and it seems to fix the issue. The rtc-cmos module is automatically loaded. If udev 0.125 enters testing, it should not be a problem (for me). Regards, Rik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
