Hi,
I installed Suse 10.1 and I don't get any sound in skype. I get an error
read error, res = -1 , handle = -1
and on the /var/log/messages:
May 22 17:01:50 laptopAir kernel: ALSA sound/core/pcm_lib.c:2534:
capture read error (DMA or IRQ trouble?)
Does somebody have a clue on how to fix this ?
Regards
Michele
Hello guys (and gals),
does anybody know if there is a (safe) way to force a SATA disk to enter
the lowest power consumption mode (causing it to shut down) while having
the possibility to reset it when needed? I'm looking for something similar
to the options provided by the hdparm utility in the case of IDE disks.
I plan to perform regular backups on two big SATA disks in an automated
way, turning them on just to perform an incremental backup and then
turning them off again. This may be a crazy idea, do you think it would
be safer to just force the disks to spin down/up or even keeping them in
full power mode?
- José Luis
We use Cadence here, and they compile parts of their software against a
horribly old glibc without tls. So far, that has been no problem, since
SuSE always provided a non-tls version of glibc, so the only thing to do
was to set up the LD_LIBRARY_PATH in a way that Cadence loads this version.
Now 10.1 drops the non-tls version, and certainly the non-tls glibc from
10.0 won't run on 10.1, either. Any ideas what to do (ok, issue a bug
report to Cadence, but you get what you pay for, when you pay too much:
arrogant assholes, driving Porsches and not caring about customers ;-).
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
Hi,
I *was* running SuSE 10 x86_64 with no problems up until this morning
when I installed the latest security patch (a new kernel). Now I have no
network connection, my system is running at a snail's pace, and I can't
even reboot the machine.
I'm used to having to recompile my Nvidia graphics driver, and
reconfigure vmware whenever I get a new kernel like this. Now the
problem I seem to have is with my on-board NIC. In the past I have used
Nvidia's nvnet kernel module to support the CK804 network interface, but
this now seems to be screwed. Has anyone else noticed this behaviour?
Anyone using an Nforce4 motherboard might think twice before applying
this update, rather than just accepting it as I did.
Any hints/tips on how I might fix this would be greatly appreciated.
Sys details:
Giga-byte Ultra9 Nforce4 mobo
Athlon64 X2 4400+
SuSE 10.0 x86_64
Yours,
Jon
--
Jonathan Brooks (Ph.D.) Research Fellow
PaIN Group, Department of Physiology Anatomy & Genetics
Le Gros Clark Place, University of Oxford,
South Parks Road, Oxford, OX1 3QX
tel: 01865-282654 fax: 01865-282656
I have been looking high and low for some good info on cross-compiling. I
have a x86 suse 10 box but need to compile/port a driver to a x64 target.
Anyone have some good howto links?
thanks
SUSE is not responsible for the video drivers, and
indeed cannot even make changes to them. The problem
is that the nVidia drivers do not correctly support
suspend/resume, and only nVidia can fix that.
It's unlikely that SL10.1 will improve your
suspend/resume experience.
-Mark Langsdorf
AMD, Inc.
> -----Original Message-----
> From: David [mailto:spotslayer@rgv.rr.com]
> Sent: Tuesday, May 30, 2006 5:27 PM
> To: suse-amd64(a)suse.com
> Subject: Re: [suse-amd64] 10.0 to10.1???
>
> Hi Mark, Power management in 10 I believe had to do with the
> NVIDIA drivers used. I have discovered many articles and
> posts in this and other forums describing the problems. In a
> nutshell several folks were able to get the laptop into
> suspend to ram or suspend to disk.
> Others were not. I am one that was not. The LT will start a
> suspend and when the screen shuts off the top line will
> display stopping service:.
> It will hang there. On a different forum I saw where several
> folks got new NVIDIA drivers from thier web site, recompiled
> them and wer able to get past this point. When it came time
> to resume the screen would stay dark. There were many
> suggestions as to how this could be corrected but I never saw
> anyone that said they had been 100% successful. The logic
> here is that in reality PM worked and the video drivers were
> failing. But in my thinking even if this is true, then PM is
> still not working out of the box. I would switch if it did,
> but if not I will just stay where I am for now.
>
> In Windows(spit) it works flawlessly on this same LT. I guess
> eventually it will get to where it works out of the box.
>
> David
>
> On Tuesday 30 May 2006 08:18, Langsdorf, Mark
> wrote:
> > > Hello, I have been using SuSE since version 9.0. I have
> skipped a
> > > couple of versions but I am currently using 10.0. My
> computer is a
> > > HP pavillion zv5000 laptop using nVidia chipset. The power
> > > management does not work properly. Has this been improved
> in 10.1? I
> > > would like to get power management working and would
> upgrade if PM
> > > will work without having to jump through hoops.
> > > Would there be any reason to switch from 10.0 to 10.1?
> Should I just
> > > skip this version and wait for the next one. Power
> management would
> > > be my main interest.
> >
> > There were no significant changes between 10.1 and 10.0 in the
> > PowerNow! driver, at least from the viewpoint of your
> laptop. There
> > may have been changes in the ACPI subsystem that could have
> affected
> > power management.
> >
> > Why didn't power management work in 10.0?
> >
> > -Mark Langsdorf
> > AMD, Inc.
>
> --
> Check the List-Unsubscribe header to unsubscribe For
> additional commands, email: suse-amd64-help(a)suse.com
>
>
>
> Hello, I have been using SuSE since version 9.0.
> I have skipped a couple of versions but I am currently using
> 10.0. My computer is a HP pavillion zv5000 laptop using
> nVidia chipset. The power management does not work properly.
> Has this been improved in 10.1? I would like to get power
> management working and would upgrade if PM will work without
> having to jump through hoops.
> Would there be any reason to switch from 10.0 to 10.1? Should
> I just skip this version and wait for the next one. Power
> management would be my main interest.
There were no significant changes between 10.1 and
10.0 in the PowerNow! driver, at least from the
viewpoint of your laptop. There may have been
changes in the ACPI subsystem that could have
affected power management.
Why didn't power management work in 10.0?
-Mark Langsdorf
AMD, Inc.
Strange behavior with pinentry-qt in SuSE 10.1: It opens all right, but when
I move the cursor into the window, it crashes instantly. Trying pinentry-qt
directly with a dummy query doesn't display this behavior. Strange, since I
now don't know how to
Replacing pinentry-qt with pinentry-gtk-2 is a suitable workaround (this
doesn't crash).
BTW: gpgsm still has a 64 bit problem (can't verify signatures), which I
have reported to the maintainer of gpgsm, but he can't fix it, since he
doesn't have access to a 64 bit machine. Workaround here: Install the 32
bit version of gpgsm.
--
Bernd Paysan
Zetex GmbH
http://www.zetex.com/
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
Hello, I have been using SuSE since version 9.0.
I have skipped a couple of versions but I am
currently using 10.0. My computer is a HP
pavillion zv5000 laptop using nVidia chipset. The
power management does not work properly. Has this
been improved in 10.1? I would like to get power
management working and would upgrade if PM will
work without having to jump through hoops.
Would there be any reason to switch from 10.0 to
10.1? Should I just skip this version and wait
for the next one. Power management would be my
main interest.
David
Hi,
Hmmm, but why should a soft reboot *not* allow new modules to be loaded
(as I did a reboot after the kernel update), and a hard reboot do the
business? Actually I think this is a bit of red herring, I think this is
a problem relating to the CK804 chipset. It gets into a state whereby it
is switching itself on and off - looking at the 3com switch the link
status indicator was going on and off every 2 seconds or so. Hence it
looked like there was no network connection. And the hard reboot "fixed"
this.
As a general point what do people recommend as the kernel module for the
NICs on the Nforce4 chipset (most mobos have a CK804 chipset and a
Marvell gigabit chipset) are there more/less reliability issues with one
or other of these two?
Best wishes,
Jon
John E. Perry wrote:
> Jonathan Brooks wrote:
>> Okay please ignore my previous email - a hard reboot fixed it(?). God
>> know why.
>>
>
> I had the same experience last year when a security update to my 9.3
> system included a kernel upgrade.
>
> The problem, I think, was that the modules got moved into the active
> directory when I upgraded the kernel, and it took a while for me to
> notice that some services were dying when they restarted. I had
> forgotten to reboot my computer, and the old kernel was trying to load
> the new modules.
>
> A reboot loaded and started the new kernel, and everything worked fine
> after that.
>
> John Perry
>
--
Jonathan Brooks (Ph.D.) Research Fellow
PaIN Group, Department of Physiology Anatomy & Genetics
Le Gros Clark Place, University of Oxford,
South Parks Road, Oxford, OX1 3QX
tel: 01865-282654 fax: 01865-282656