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

RE: hdclock ultra10



Hi Dave

Yep....thoughs are the errors, just surprised that I couldn't find any
other reports in the mailing list.


Cheers

Chris


-----Original Message-----
From: Dave Love [mailto:fx@albion.dl.ac.uk] On Behalf Of Dave Love
Sent: 23 July 2002 23:16
To: Chris Wren
Cc: debian-sparc@lists.debian.org
Subject: Re: hdclock ultra10


"Chris Wren" <chris@renegadez.net> writes:

> Hi,
> 
> Does anyone know of issues with woody and the hardware clock.....   I
> get errors on boot saying that the Hardware Clock can not be accessed 
> ???

Yes, I had meant to make a bug report about that after checking where it
was coming from.  This is from an Ultra 5:

  sys32_ioctl(hwclock:35): Unknown cmd fd(3) cmd(00004b50) arg(effff900)
  sys32_ioctl(hwclock:36): Unknown cmd fd(3) cmd(00004b50) arg(effff910)
  sys32_ioctl(hwclock:110): Unknown cmd fd(3) cmd(00004b50)
arg(effff910)


-- 
To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org



-- 
To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: