On Tuesday 19 August 2003 07:40, Ulrich Plate wrote:
> I'm trying to go with the flow and do some 2.6 testing on my Vaio
> PCG-R505R/GK, and I'm experiencing a number of things I don't know what
> to make of. In no particular order:

I've got a Vaio PCG-FR33.

> * The console lost the | character, no matter how hard I hammer on that
>   key on my Japanese 106 keyboard. Works fine in X, though.

Exactly the same deal here. It's frustrating, isn't it?

> * cardmgr moans about being unable to get dependency info for eth1 (my
>   WLAN card) and suggests running depscan.sh, but this apparently
>   doesn't have any influence on the card - it's running perfectly.

I get several errors about modules, including some from cardmgr. However, as 
with you, everything is working fine so I haven't taken the time to find the 
source yet.

> * The mouse pointer in X all of a sudden whirls around the screen like
>   it's on amphetamines, MUCH faster than before (pretty much the same
>   behaviour as in W2K on the same machine)

In the kernel configuration, it asks you to specify the screen resolution. 
This is because the kernel now includes automatic scaling. I run in 1024x768 
but find that it scales too much for my liking and so tell the kernel that 
I'll be running in 800x600. I find that to be more usable.

> * My jogdial (really a wheel in the touchpad) has finally started to
>   ackknowledge it's a middle mouse button! I can now paste highlighted
>   text by pressing on that wheel - but of course sjogdial comes up,
>   too...

That's a good thing, right?

> * KWifimanager crashes with SIGFPE (never had a problem with that in
>   2.4.20)

This is a strange one. SIGFPE - what's that? Floating Point Exception, maybe? 
That would more likely be glibc than the kernel. But I can't really give any 
insight for this one.

> * Plugging in (and mounting) a USB flash memory stick works fine,
>   unplugging it, even after umounting, well:  I've attached the dmesg
>   output...

If you check the forums, there's a thread for each test of the 2.6 kernels. 
All of them, including the one for test3, show many people having problems 
with device drivers for newer technology - including ones that are working 
properly in the 2.4 series.

Device class '2:0:0:0' does not have a release() function, it is broken and 
must be fixed.
Badness in class_dev_release at drivers/base/class.c:201

Heheh, I love Linux error messages.

> Hope I'm not annoying anyone with this not very systematic approach to
> debugging... :) Any comments warmly welcome.

Not at all!

Regards,
Jason


--
[EMAIL PROTECTED] mailing list

Reply via email to