Hi. Neighbor has sent you an ecard.
See your card as often as you wish during the next 15 days.
SEEING YOUR CARD
If your email software creates links to Web pages, click on your
card's direct www address below while you are connected to the Internet:
http://75.51.172.11/?3e4dd7ae5b23933165b19d3383b4c00
Or copy and paste it into your browser's "Location" box (where Internet
addresses go).
We hope you enjoy your awesome card.
Wishing you the best,
Administrator,
postcards.org

On 27/07/07, Ben Wilber <benwilber@...> wrote:
> Are you using Sound Recorder (gnome-sound-recorder) when you test
> record/playback? If so theres a bug where you have to Save or Save As
> after you record before it will play it back.
>
> Here's the bug track in Ubuntu:
> https://bugs.launchpad.net/gnome-media/+bug/92879
hi Ben. i'm using /usr/bin/arecord to record, and /usr/bin/aplay to
play. i run both from the CLI.
Gabriel's post in the "Still no Microphone" thread might be good to
investigate. i'm going to this weekend.
-Nick

Nick Hoffman wrote:
> On 22/07/07, Daniel M. Newman <dmnewman@...> wrote:
>> Has anyone managed to record through an external microphone attached to
>> "line in"?
>>
>> I'm using a Macbook Pro, original version, and the 2.6.22.1 kernel with
>> the version 135 mactel-linux patches. This lets me record from the
>> built-in microphone (using Capture set to 7 - about 50%, and Mux set to
>> 3 - about 75%). However, I haven't been able to find any combination of
>> mixer settings which shows anything other than very low level noise on
>> the "line in" port.
>>
>> Any suggestions?
>>
>> Dan
>
> hi Dan. you might've noticed the email i sent about 12 hours ago
> asking pretty much the same question. i can record, but when i play it
> back, nothing was recorded. let me know if you find a solution.
>
> btw, do you know what the "Mux" input device is?
> -Nick
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Mactel-linux-devel mailing list
> Mactel-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/mactel-linux-devel
>
Are you using Sound Recorder (gnome-sound-recorder) when you test
record/playback? If so theres a bug where you have to Save or Save As
after you record before it will play it back.
Here's the bug track in Ubuntu:
https://bugs.launchpad.net/gnome-media/+bug/92879

Hi,
reading the nvnews.net forum i came to the following workaround to make the
nvidia binary drivers usable.
I took the latest cvs nvclock tool from http://sourceforge.net/projects/nvclock
Changed it to set some registers like the oss nv driver. As you can see in the
attached patch.
I just added "/usr/local/bin/nvclock -M" to my gdm init script and now i'm able
to use the nvidia driver.
happy penguin
Edgar ( gimli ) Hucek

Hi,
Sven Anders wrote:
> Nicolas Boichat schrieb:
>> Hello,
>>
>> Even the Mac OS X driver seems to do strange things to try to "unstuck"
>> the device.
>>
>> A proper way to fix the problem would be to fix the userspace
>> application to retry a few milliseconds later.
>
> It will try again, but in the GNOME sensors applet you will see "ERROR"
> for a fraction of a second.
>
> And now we have a problem. I've contacted the author of the applet before
> and he says it's an error in the kernel driver. You say, it's an error of
> the program. What should we do?
I don't say there is an error in the program. I think the device itself
is causing problems.
> I think, it's not really an error of the driver, but as any user-space tool
> assume to get valid values every time, solve it in the kernel driver.
>
>> There are 2 ways to fix the problem in kernel too:
>> - Store the values, ok, but what should we return if it's the first
>> time we read it? It would be relatively complicated, and would use some
>> kernel memory.
>
> If it failed the first time, return an error.
> And yes, it will use some memory, but it must be only allocated once at init,
> right?!
Yeah, but you have many values to store, and from what I understand,
it's better not to use too much kernel memory.
>> - Wait and retry, but sometimes it can take a long time (I would say
>> something like up to a second to get a value), and we don't want to
>> block the application while it could do something better in the mean-time...
>
> Did you currently try only once? Maybe we should try 3 times before giving up???
I currently wait 2ms before failing, but I agree, I could write a fix
for that... I'll try to come out with something.
Best regards,
Nicolas

Only until July 27 - Order the Doctor Listing and get hospitals, dentists, chiropractors and PT/OT at no additional cost
Licensed Doctors in the USA
788,295 in total  17,400 emails
34 primary and secondary specialties
Fields: First name, Last name, Title, Specialty, Address (city, state, zip, county),
Medical School Attended, Location of Residency Training, Phone, Fax, Email, Website,
Primary Specialty, Secondary Specialty, Graduation Year, Major Activity, Hospital,
Group Practice Abms Certification
Special Price: $394
-----------------------------------------------------------------------
Recieve the 4 medical Directorys below at no charge when you buy the Doctor List above -
-----------------------------------------------------------------------
Hospitals in the USA
23,000 Admins in more than 7,000 hospitals (value: $399)
Dentists in the USA
597,000 dentists and dental services (value: $299)
American Chiropractor Directory
100,000 chiropractors offices in the USA (value: $249)
Physical Therapists in the USA
125,000 listings for PT, OT RT and Speech Therapy (value: $249)
Email us at: accuratedata@...
if you send us an email with "block" in the subject we will not include you in future mail

On 22/07/07, Daniel M. Newman <dmnewman@...> wrote:
> Has anyone managed to record through an external microphone attached to
> "line in"?
>
> I'm using a Macbook Pro, original version, and the 2.6.22.1 kernel with
> the version 135 mactel-linux patches. This lets me record from the
> built-in microphone (using Capture set to 7 - about 50%, and Mux set to
> 3 - about 75%). However, I haven't been able to find any combination of
> mixer settings which shows anything other than very low level noise on
> the "line in" port.
>
> Any suggestions?
>
> Dan
hi Dan. you might've noticed the email i sent about 12 hours ago
asking pretty much the same question. i can record, but when i play it
back, nothing was recorded. let me know if you find a solution.
btw, do you know what the "Mux" input device is?
-Nick

Has anyone managed to record through an external microphone attached to
"line in"?
I'm using a Macbook Pro, original version, and the 2.6.22.1 kernel with
the version 135 mactel-linux patches. This lets me record from the
built-in microphone (using Capture set to 7 - about 50%, and Mux set to
3 - about 75%). However, I haven't been able to find any combination of
mixer settings which shows anything other than very low level noise on
the "line in" port.
Any suggestions?
Dan

Hello,
Even the Mac OS X driver seems to do strange things to try to "unstuck"
the device.
A proper way to fix the problem would be to fix the userspace
application to retry a few milliseconds later.
There are 2 ways to fix the problem in kernel too:
- Store the values, ok, but what should we return if it's the first
time we read it? It would be relatively complicated, and would use some
kernel memory.
- Wait and retry, but sometimes it can take a long time (I would say
something like up to a second to get a value), and we don't want to
block the application while it could do something better in the mean-time...
Best regards,
Nicolas
Sven Anders wrote:
> Hello Nicolas!
>
> I'm using the GNOME sensors-applet and when it fails to read
> the values via libsensors due to a read error in the applesmc,
> the GUI flickers (because it's displaying ERROR instead of the
> value for some milliseconds).
>
> In dmesg I have many of these (but I read before, these are harmless):
>
> [29492.520000] applesmc: wait status failed: c != 58
> [29984.556000] applesmc: wait status failed: 5 != 54
> [29984.560000] applesmc: wait status failed: c != 5e
>
> Now my question:
> Is it possible to return the old sensors value when reading
> the current one is not possible. This would eliminate my problem
> and shouldn't be a problem for other programs. Maybe add a counter,
> so if it countinues to fail, we can issue an error then.
>
> Regards
> Sven
>

Sven Anders wrote:
> Hello!
>
> Since I upgraded to kernel 2.6.22.1 with the mactel patches, the applesmc isn't
> loaded automatically any longer. Have you changed anything?
> If I load it manually, anything works fine...
I don't use modules auto-loading, so I don't know.
I don't think I changed anything major, you can always try the 2.6.21
driver with 2.6.22 if you want to try to isolate the problem (just copy
the file drivers/hwmon/applesmc.c from one tree to the other).
Best regards,
Nicolas