Debian Hardware :: DacMagicXS 2.0 - CA Clock Selector?
Sep 9, 2015
I have had my USB DAC, the aforementioned, working before in Ubuntu, Xubuntu, Fedora, Linux Mint 17.1 and Linux Mint 17.2. I've finally settled on Debian with i3wm as I feel I am now at a stage with Linux where I'm comfortable enough to use it.
It may be something to do with audio output being handled by Pulse, but this was the case in *buntu as well, as I used the Pulse config file to up the maximum bitrate output to take full advantage of the DAC.
On Debian (Stretch), I'm getting this when I select the device in AlsaMixer:
As can see, it is operating in USB 2.0 mode, which is correct.
I'm using a very simple conky script to diplay the date and time on my desktop. I've noticed that he conky clock is a few seconds early compared to the time displayed in the right hand side of the top panel (Natty). I guess both displays are based on the same "internal" time, so I'm left wondering how this could happen, and how to sync back the clocks.
It seems that Conky is in sync with the system date, while the panel clock is 2 seconds late (on my system). Checked with while true; do date; sleep 0.1; done
I had cloned a centos 5.6 installation from virtualbox virtual machine to physical box. Everything work fine. However, the time showing in os using date command differs from bios time by roughly 4 hours. I am running ntp services which sync the time with another centos server on the network. It appears that some services are using virtual clock and some use physical clock. How do I get rid of virtual clock and only use physical clock?
So I'm dual booting Windows 7 and Lucid. Thinking I might shorten the timeout for the bootloader (I apologize if my terminology's off), I ran bcdedit and changed the timeout to 0. Little did I know this would prevent my computer from booting into either operating system.
I've got Lucid running off a live cd now; does anyone know how I could change the timeout back from there (or any other way!) and get my laptop working again?
I installed Ubuntu 10.4 using wubi from XP. For some reason wubi didnt increase the countdown time on the windows os selector. My P.C. came with a recovery partition, so the os selector has always poped up on startup, but the timer was set to 5sec.(probably to avoid annoyance). Is there a way to edit this so I can have more time to select my option? This is the windows os selector and Ubuntu is on a separate(second) hard drive.Ubuntu version: 10.04 LTS- the Lucid LynxWindows version: Xp servicepack 2Machine: Hp Pavilion a1677c
I've upgraded to 11.04 and found out unity has no desktop window selector at all. After a quick google search it turned out that clicking the Ubuntu icon on the top left corner should bring out some kind of expo-like style selector but that turned out not to be the case for me.
This is all that happens when I click the icon: Doesn't matter how many windows are open. Is this some upgrade related error or am I missing something?
when ever i type int his command i do it twice because i have two cores to it looks like this: cpufreq-selector -c 0 -g powersave cpufreq-selector -c 1 -g powersave
when ever i type this it says that "you must be root" what does thsi mean
When I minimize any window, it does not appear in taskbar. So I cannot just minimize any window. I tried following thing. In Add Panel, I added "Window selector and other options. But of no use.
When I minimise windows, or have several open, I've lost the window selector at the bottom to be able to flip between them. I can go to "activities" and then select them there, or I can ctl-tab to them but I used to like the window selector at the bottom. Anybody located the missing window selector ?
I see from dumping executables that seg selector 0x10 is assigned to my stack segment and to my data segments (.bss .data COMMON). The code is using 0x08. My question - how can I control this? I've looked at all the command line options and don't see it. I have a different program that uses 0x10 for code and 0x18 for data. I note that the second program has i386 in the architecture field in the linker script, whereas the first one referenced has i686. Is this what causes the difference? I understand that this architecture field triggers something regarding a library named BFD - is this where I should look? If so, where do I find it? I am runnig fedora. Is there a way to control the association of sections in the linker script with segment registers? I can set up segments in the gdt and can asign them to segment registers. I can - when writing in assembler - assign code to a section. I can relate a segment in the gdt with a register.But I dont see how to tell the section which segment register it is associated with Finally I see that the gcc compiler decides - based on how I initialize a variable - whether to put it into bss or data or COMMON. Do I have any control over this?
When I google screenshots of Linux I often see that people have a clock directly on their desktop. How is this done?
I'm running Xfce on a Wheezy vm, but without xfce4-panel, so having a clock/date right on the wallpaper/desktop would be great..I don't want a clock in a window.
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.
The clock keeps changing back to UTC which is not so good. My local timezone is about UTC +7. It appears to be good until I reboot. I can change manually in the bios or enter the following command hwclock --systohc --localtime No matter what it goes back to UTC. I checked the timezone data is correctly recorded and it is...
The command hwclock returns Wed 23 Feb 2011 08:18:05 PM ICT The command date returns Wed Feb 23 20:19:25 ICT 2011 so this shows the system time and the hardware time are the same but they use the 12 and 24 hour clock which is strange since the bios supports only the 24 hour clock. I wonder if the time / date syntax has to be presented in the same way on both the system and the hardware? The time ICT zone appears to be correct.
If I have Dolphin up and running, I will activate a folder, hit Enter, and nothing happens unless my mouse is moving around the screen.I may have Chromium Browser or Firefox running with another app, and when I use Alt-Tab to switch tasks, the app selector window will not appear unless I'm moving the cursor. And once I have chosen the app to switch to, it will not actually make the switch unless the cursor is in motion across the screen.I am running Kubuntu 10.04, KDE 4.4.2
I'm 'trying' to dual boot WinXP and Ubuntu 10.10 from 2 separate HDD's. Currently I'm on attempt number 6 but my patience wore thin about 2 days ago - here's the current state of play: I have WinXP running fine (Was installed first) and I have Ubuntu running fine if I use a boot loader disc. I don't have any boot options at all - if I let the PC boot naturally then it just loads XP as normal. I followed this guide to the letter: [URL]
(For those that don't want to read the link: It get's you to create 4 partitions on a drive - 1: ntfs for winxp (not touched) 2: Linux partition 3: linux-swap partition 4: fat32 osshare partition) then if you get no boot options, it creates an ubuntu.bin file which you move to the C: and edit the boot.ini to include it in the options). But all the difference it makes is I get boot options, I press Ubuntu and my computer sits with a blinking cursor for as long as you let it.
During the installation the installer asked me if my clock was set to UTC. I didn't know what that meant so I said yes. Now whenever I boot into Lenny it messes up the time of day, and since I dual boot with puppy and knoppix on this machine, the time of day is messed up in those systems also. Any idea how to permanently undo the damage in Lenny?
I'm trying to sync my clock. I think I would like to do this by the "ntpd" daemon running. I think it should start up on boot, but it doesn't.
I have the following in my /var/log/syslog: Jul 18 23:44:14 neo ntpd[1780]: ntpd 4.2.6p2@1.2194-o Sun Oct 17 13:45:13 UTC 2010 (1) Jul 18 23:44:14 neo ntpd[1781]: proto: precision = 0.634 usec Jul 18 23:44:14 neo ntpd[1781]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Jul 18 23:44:14 neo ntpdate[1194]: step time server 72.26.125.125 offset -0.505108 sec
Other posts say if ntpd and ntpdate run too close together, they cause one to think the other is locking a resource. It works to type "ntpdate pool.ntp.org" to manually update the clock. My Debian version is squeeze (6.0.2)
It works to start the ntpd daemon manually: ... sudo /etc/init.d/ntp start ... Starting NTP server: ntpd.
I remember that 10 years ago or so, I used to have on a Debian desktop a clock which displayed the time on a custom level of approximation, e.g. quarter to five for 04:47 or even "morning/late evening/etc". I can't remember if it was a customization of the default clock or a separate program. I didn't have luck searching on the internet. Is it possible to get something similar with Gnome on Jessie?
I had to boot into my Windows 7 install on my laptop for the first time in a few months and I noticed that the Windows clock was 4 hours ahead. Windows sync'd its time with the internet, then I booted back into Debian (Lenny) and my clock was now 4 hours behind. Both OS's are set to the same time zone (EDT). The minutes were correct in both systems. Could the fact that EDT is UTC-0400 be relevant?
I have recently come across a Debian installation page for powerpc: viewtopic.php?t=20481. It got me motivated to fix the Debian I have on my iBook G4. I have a Debian Lenny installed on my iBook G4 -- but I have been having some sort of problem (mostly likely due to hardware) which causes the system to crash. After the latest crash, the clock on iBook has been readjusted. For this reason, I cannot reboot Debian completely.
Every time I turn on the computer it begins the booting process but before I get to my desktop I encounter numerous error messages concerning my clock. After either OK'ing or canceling these error messages, I get to my desktop but the system by then is either frozen or else not working at all. Worse, I can't even turn off the computer since the upper right corner of the desktop is completely blank and I have no menu to turn off or reboot the system.
It took this computer to a local Apple store and they ran many different hardware diagnostic tests on it. They concluded there's "technically" nothing wrong with the computer. But they said although the system has successfully passed all hardware tests, there may still remain some complicated but slight hardware glitch/es which the hardware diagnostics could not pick up.
I've Lenny with Gnome installed. Under System -> Administration -> Login Window -> Local, I have Industrial Ximian Gnome theme. How to change clock type from 12 to 24 in the Industrial Ximian Gnome window?
I added an ext4dev filesystem to my hard drive as /dev/sda3 and mounted at /share with the goal of putting all of my multimedia files on it and sharing it through NFS. I followed this guide: [url]
Of course, this was from lenny (hence the -dev). The partition was fine, and I mounted it numerous times. I also performed a dist-upgrade to squeeze. I shutdown that computer with the usual 'shutdown -h now' and disconnected the AC power cord from it, because I wasn't planning on using that machine for awhile. As far as I could determine, everything was fine before I unplugged it.
Every time that computer is powered off, the clock resets to 1999 because the battery is bad. So I am used to getting the "last mount time is in the future" error.
Three weeks after halting, I powered the computer back on. It was unplugged until this point. I got an error message when it attempted to mount /dev/sda3
I then removed its line from /etc/fstab, rebooted. and tried to check it, but I just keep getting the same error-- even with the '-b 8193' option.
The machine is still using the 2.6.26 kernel from lenny. I am building a new one right now (2.6.30), hoping that the problem is caused by the ext4dev/ext4 module. Otherwise I don't know what to do.
i set my clock with this command-/usr/sbin/ntpdate -v ntp-1.mcs.anl.gov ntp-2.mcs.anl.gov but my clock changes to incorrect time when i restart my system,how can i make it stable?
