Software :: Increase The Accuracy Of Function Get_rtc_time() - Get Time Of Wall Clock From Wireless Driver
Oct 24, 2010
I am trying to get the time of my wall clock from my wireless driver in form of "hh:mm:ss", so I used the function get_rtc_time() inside my driver to get that and it was done. My question: Is it possible to increase the accuracy of this function, for example if I want to get the milliseconds and the Microseconds in additional to the first output? If not, Is there any other function can do that?
It's an acer Aspire One D257-13478.Download the correct firmware and tar it into the appropriate dirctories and I'm still running a wall.I don't know how to get the b43/b43legacy in the lsmod list.I've also tried use the rfkill command and using yum to install it gives me this response:"cannot retrieve repository metadata" I also went into the F2 setup menu and couldn't find anything to alter the bios wireless.After installing Fedora 15 almost all the drivers remained intact including enumerators for usb mice.I don't know what's going on.
I am trying to install vmware server on CentOS: In vmware installation guide it says before intalling:
Before you begin, read the following notes and make adjustments to your host system: The realtime clock function must be compiled in your Linux kernel. The parallel port PCstyle hardware option (CONFIG_PARPORT_PC) must be built and loaded as a kernel module (that is, it must be set to m when the kernel is compiled).
I am using Debian linux. I have 100 timers running. If a timer expired which will generate a signal and it was mapped to a same function handler. All the timers are mapped to one function handler. The problem is if the timer expires one at a time, the function handler called at a time. But if the 2 timers expires at a time, the function handler is called one time only instead 2 times. Is it possible to invoke the function handler as many times based on timer expirary happens simultaneoulsy?
I've just installed Ubuntu on a new netbook, getting rid of windows in the process. I had tried it on another computer, installing it alongside Windows, and liked it enough to want to install it fully on my new netbook. I followed instructions, downloaded it to a USB stick, and then installed it as per the instructions on the Ubuntu website. All seemed fine until I tried to connect to my wireless network, when it appears there is no wireless driver. I tried plugging in the ethernet cable, but it just disconnects me every time I try to go online.
I followed the instructions that came with the 802 .11 Linux STA driver and was able to initialize my card and connect to a protected network! The instructions also tell me how to load the drivers at boot time, but I get an error when I try to run
Code:
# sh: for i in `find /lib /var -name wl.ko`; do mv $i ${i}.orig; done
The message returned is
Code:
bash: syntax error near unexpected token `do'
Upon restarting, my wireless is no longer active. My card is Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
When installing I perhaps mistakingly told Fedora it should use the BIOS clock and now it shows the wrong time, 1 hour ahead of my time-zone GMT+0. If I try and go to the preferences and set the time the 'Advanced Options' one of which I need are grayed out, I need the 'Use local time source' option to be unchecked. Could somebody tell me a workaround or the command-line commands to tell it not to do this anymore?
I am running Ubuntu 11.04 on a dual boot with Windows 7 Home Premium (32 bit) Dell Inspiron 560s.
As long as I am engaged in activity in Ubuntu all is well. However, if I leave my computer to get a cup of coffee I find on my return the computer screen is blank and when I activate it a window comes up asking me to enter my password to take it out of lockout, leave a message etc.
I can't seem to find the appropriate command to increase the time before I get locked out.
What steps can I take to increase the time the system stays active before I am kicked out and have enter my password again?
Trying to adjust my clock settings!I am running KDE 4.4.3 on Squeeze, on an 64bit laptop.(I used the AMD64 net install version)How can I fix the time settings so it shows 5:00pm instead of 17:00:00So far I have not been able to find a cure
When I boot into Debian (lenny) my clock is always 4 hours slow. Whether I set it manually, or set it to get it's time from the network, the next time I boot into debian, it's back to being 4 hours slow.
I have dual boot on my comp. Windows XP and Fedora 11 Now in both systems time zone is set to Belgrade ( which is my time zone), but when I setup clock in fedora to be, let's say 16.15h, then when I swich to windows it says time is 14.15h. When I setup in windows on 16.15h, and I swich to fedora, it says time is 18.15h. So I can't get accurate time on both systems in no way.
By default, Fedora 11 sets my clock to military time. For example it says 16:22. I would like it to show civilian time (or at least know how to do it) I logged into the clock settings and had to put in the root password, but couldn't find where you do this. If you scroll on the time for hours, it just goes from 0 to 23 and back, not to AM and PM like some others.
I done searches for "clock" and found similar threads, but no real fix that is working for me. My clock resets when I boot into linux. It does not happen in windows or bios even on cold boots. The battery is replaced and good** the old battery was by all measures dead (0.6v), but still seemed to have enough power for the clock, since windows tested fine with it.
I have tryed setting it to local time, UTC.. etc... My timezone is GMT (london). "sudo /sbin/hwclock --systohc" Although I have windows, I do not use it except the few times to test this, so no conflict.
Try as I might I cannot seem to get the system clock to display local time. It looks like it's stuck on GMT. In the System>Administration>Time and Date I have my local time zone set correctly and also set to update automatically with an appropriate time server selected. It still displays my local time +5 hours (I'm central time, USA).
I restored my .kde directory after changing some stuff unrelated to my clock and now all plasma clocks are exactly 5 hours faster than my system time (the correct time).I've set the time zone for Date&Time in System Settings properly and that's working well and I've ALSO gone into the time zone settings for the plasma widgets and switched between UTC and Local manually but that doesn't do anything.
I'm running windows 7 and the F12 Beta (although the same issue existed in my f11 distro) on an asus g71 bb. When ever I boot into windows my time is correct. If I boot into to F12 my time is wrong. Usually by 4 hours. If I change it in Linux when I boot into windows I end up switching the time on my windows partition. I tried searching the forum (rather casual I'll admit) and couldn't find any solutions.
I'd like to have two gnome clock applets, one with the regular default time and date in the upper right hand corner (the default) and another set to epoch time. However, I can't figure out how to set the second gnome clock applet to display the epoch time. I'm running FC12.
Dual boot system. Boot Linux Fedora 13 and the hardware clock is set to GMT. Boot Windows 7, time is wrong, as it expects the hardware clock to be set to the local time. reset the hardware clock each time I reboot in to the other O/S.
I have this problem for a while but didn't notice it until lately(i did reboot the machine for few months). Now that i reboot it frequently i notice that the clock is always not what is supposed to be. I'm in Toronto, Canada so it should be GMT -5:00. Sometimes it shows GMT-6, sometimes -10, now is GMT -11. Anyone would know why i have this issue? I'm running Suse11.1 on a 64 bit. My laptop which runs on 32 bit is working fine.(well probably different versions for kernel and kde.(whatever was in th repository to be updated i updated)
2.6.27.39-0.2-default Version 4.3.4 (KDE 4.3.4) "release 2"
In Kubuntu 10.10, the clock is set to military time. I shouldn't have to do the math just to look at the clock. There is no setting anywhere to change it to normal time.
