Hi Guido,
Your package tested out OK. I only have an Indy. So I only tried
"tip22".
Thanks!
Edwin
Guido Günther wrote:
On Thu, Jun 16, 2011 at 02:15:56AM -0700, Edwin Kwan wrote:
I don't know whether the "kernel" and "initrd&quo
ot; and "__rd_start", "__rd_end". I
actually modified "ld.script.IP22" by putting "0x89702000" in the start
address and built myself a netboot image using the extracted "kernel"
and "initrd". I got to the installer screen but I don'
Hi,
The screen shot in Attilio's bug report was done by me on my Indy. I
am not experienced in this beginning of the universe kind of code. But
I found the following clues which may be useful.
Please refer to bug 452798
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452798). Here is
Martin,
I think it is working now. I am keeping both rtc (10, 135), and rtc0
(254, 0), for now just in case I need to go back to an old kernel.
Thanks!
Martin Michlmayr wrote:
Edwin,
* Edwin Kwan [2009-06-24 02:48]:
No, I don't have "udev". This is an old SGI Indy works
"?
Thanks!
Martin Michlmayr wrote:
* Edwin Kwan [2009-06-24 01:58]:
The "/dev/rtc" file does exist, as seen below:
gundam:~> ls -l /dev/rtc*
crw-rw 1 root root 10, 135 Mar 15 2002 /dev/rtc
gundam:~>
Are you not using udev? It seems the device nodes are not correct
because
sk : disabled
wdog_alarm_mask : enabled
interrupt_mode : level
INTB_mode : high_active
interrupt_pins : swapped
gundam:~>
Martin Michlmayr wrote:
* Edwin Kwan [2009-06-21 04:27]:
During boot, I saw this error in syslog:
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Cons
Package: linux-image-2.6.26-2-r4k-ip22
Version: 2.6.26-15lenny3
Severity: important
During boot, I saw this error in syslog:
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Consequently "hwclock --test --debug" would fail.
After switching back to an older kernel (2.6.18-5-r4k-ip22),
7 matches
Mail list logo
