Re: X.Org using Intel 915GM on Dell Latitude D610

[Ismael Valladolid Torres]

Alexandre Rossi escribe:
> Another message in the thread you found tells us a bit more on the
> modular and built-in versions of framebuffer drivers. It also brings
> in initrd wich is a good alternative of built-in drivers.

Using kernel-package, initrd support is more or less
straightforward. I suspect that BIOS on this computer is not allowing
switching video modes on boot, as neither intelfb nor vesafb are
working, but I can't confirm.

Cordially, Ismael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Touchpad device changing from event1 to event0

[Michelasso]

I have notice today that the touchpad of my Acer Aspire 5024 wasn't
recognized  anymore by the x server as a synaptics one, even if the
kernel says (according to dmesg) that it is a synaptics one. After
investigating for a while I have noticed that the device associated to
it has changed from /dev/input/event1 to /dev/input/event0 according
to /proc/bus/input/devices. Since in my xorg.con I have the line

Option  "Device""/dev/input/event1" 

of course the server couldn't recognize it. My question is: why has it changed?
(I am sure that before it was event1, I had checked it in
/proc/bus/input/devices and it worked)
Could it be due to the installation of a new kernel?

Re: Touchpad device changing from event1 to event0

[Mattia Dongili]

On Mon, August 29, 2005 2:59 pm, Michelasso said:
> I have notice today that the touchpad of my Acer Aspire 5024 wasn't
> recognized  anymore by the x server as a synaptics one, even if the
> kernel says (according to dmesg) that it is a synaptics one. After
> investigating for a while I have noticed that the device associated to
> it has changed from /dev/input/event1 to /dev/input/event0 according
> to /proc/bus/input/devices. Since in my xorg.con I have the line
>
> Option  "Device""/dev/input/event1"
>
> of course the server couldn't recognize it. My question is: why has it
> changed?
> (I am sure that before it was event1, I had checked it in
> /proc/bus/input/devices and it worked)
> Could it be due to the installation of a new kernel?

Yes, something might have changed in the input susbsystem probing routine.
To avoid this issue in the future it's advisable to use

Option  "Device""/dev/psaux"
Option  "Protocol"  "auto-dev"

in your synaptics touchpad InputDevice section, as explained in
/usr/share/doc/xfree86-driver-synaptics.

hth
-- 
mattia
:wq!



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: gnome CPU scaling monitor

[Matthew]

You need to set cpufreq-selector as suid root.  To do that run (as
root):
chown root:root /usr/bin/cpufreq-selector
chmod +s /usr/bin/cpufreq-selector.

Then retart gnome-cpufreq-applet.
Note, though, that this can be a security risk because anyone who runs
it runs it as root and can change your cpu frequency easily, and any
bugs will do more damage (I run it with the suid bit set and have no
problems, just warning you though.)

MJD

On 8/22/05, Alejandro Bonilla Beeche <[EMAIL PROTECTED]>
wrote: 
Hi,

   I have Debian Sid with gnome 2.10 and basically cannot
change the speed
of the CPU as a user, the CPU Freq monitor always allows to
change the 
CPU speed, but as root.

   Anyone has given a user the permissions to change this
from the user
and not with root?

.Alejandro


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]




signature.asc
Description: This is a digitally signed message part

Re: Touchpad device changing from event1 to event0

[Michelasso]

On 8/29/05, Mattia Dongili <[EMAIL PROTECTED]> wrote:

> Yes, something might have changed in the input susbsystem probing routine.
> To avoid this issue in the future it's advisable to use
> 
> Option  "Device""/dev/psaux"
> Option  "Protocol"  "auto-dev"
> 
> in your synaptics touchpad InputDevice section, as explained in
> /usr/share/doc/xfree86-driver-synaptics.
> 

Thanks a lot for your answer; I try to ask you for some suggestion for
some minor problems I have with the touchpad. When I use it with the
synaptics xfree86 drivers loaded often it happens that even if I am
moving the finger on the touchpad the cursor doesn't move, and I have
to release the finger from the touchpad and to tap again to make it to
move. Or some other times instead of moving the cursor, it scrolls up
and down the window is it above, as if I was tapping above the
vertical scroll bar of it, while I am not doing this. Or when I double
tap on the firefox url form it doesn't select all the url it is
currently inside it.
This problems don't appear when instead the synaptics driver it is not used.
I am using the same configuration of the readme you suggested, and in
the boot options of the kernel I have "noapic nolapic i8042.nomux
noapictimer" that I have read somewhere are supposed to improve the
behaviour of the touchpad.
Any suggestion will be appreciated.

unsubscribe

[Fredo Strüber]

-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

cpu throttling--what is it?

[Luca Pireddu]

Could someone explain to me (or point me to where I can find an answer) what 
CPU throttling is?  My sony vaio has 8 CPU throttling levels:

$ cat /proc/acpi/processor/CPU0/throttling
state count: 8
active state:T0
states:
   *T0:  00%
T1:  12%
T2:  25%
T3:  37%
T4:  50%
T5:  62%
T6:  75%
T7:  87%

I see that varying the setting has a big effect on performance (and presumably 
battery life).  However, the throttling setting doesn't seem to affect my CPU 
clock.  So how does it work?

Thanks

Luca


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Netgear wg511, 2.6/Sarge - weird?

[Florian Gossin]

Rusty Carruth a écrit :
> I got a lot of helpful replies from folks, I'll use the last one as the
> pulpit from
> which I'll speak ;-)
> 
> Thanks to all for their help, here's what I've found:
> 
> 
> Jordan Smith wrote:
> 
>> I was running this card on Sarge when it was still Testing.  Did you
>> install the wireless-tools package?
>>  
>>
> 
> Yep.
> 
>> If so, do an iwconfig and see if the card is detected with wireless
>> extensions.  
>>
>> If you see wireless extensions in the output, try an "iwlist
>> eth1(interface) scan" to see if it picks up the AP
>>
>> If the card is up and the module loaded then the green light should be
>> on.  When the interface is routing traffic, the yellow light will be
>> flashing.
>> Also, you might try a lsmod to see if the prism54 and the Yenta modules
>> are loaded before you scan.  
>>
> # iwconfig
> lono wireless extensions.
> 
> eth0  no wireless extensions.
> 
> eth1  NOT READY!  ESSID:off/any
>  Mode:Managed  Channel:6  Access Point: 00:00:00:00:00:00
>  Tx-Power=31 dBm   Sensitivity=0/200
>  Retry min limit:0   RTS thr=0 B   Fragment thr=0 B
>  Encryption key:off
>  Link Quality:0  Signal level:0  Noise level:0
>  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>  Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> eth2  no wireless extensions.
> 
> sit0  no wireless extensions.
> 
> doclap:~# lsmod|egrep prism
> prism5454812  0
> firmware_class 10176  1 prism54

It can be a hotplug problem. Do you have the firmware located in
/usr/lib/hotplug/firmware directory ?

What is written in the logs ?

 kernel: Loaded prism54 driver, version 1.2
 kernel: eth0: resetting device...
 kernel: eth0: uploading firmware...
 kernel: eth0: firmware version: 1.0.4.3
 kernel: eth0: firmware upload complete
 kernel: eth0: interface reset complete

> doclap:~# iwlist eth1(interface) scan
> -su: syntax error near unexpected token `('
> doclap:~# iwlist 'eth1(interface)' scan
> eth1(interface)  Interface doesn't support scanning.
> 
> doclap:~# iwlist 'eth1' scan
> eth1  No scan results
> doclap:~# iwlist 'eth1' scan
> eth1  No scan results
> doclap:~# lsmod|egrep -i yenta
> yenta_socket   21728  1
> pcmcia_core70868  2 ds,yenta_socket
> doclap:~#
> 
> During all the above the green light never let a peep of greenness out.
> 
> Now, do remember that I don't have an AP here - I'll have to go try the
> things that require an AP handy somewhere that has one.
> 
> one thing thats not very helpful (in addition to the fact that the vendors
> like to switch parts inside without ANY way for folks to tell!), is that
> the card itself has NO information about what's inside, and in fact
> doesn't even say where it was made!  (Jochen asked where it was
> made - there's no hint at all.  All it says is the usual 'This device
> complies ...blah...blah...blah", then FCC ID: PY3WG511, and
> Canada ID: 4054A-WG511, then the MAC address (00:09:5b:45:51:aa)
> and serial (WG51A33AH021946).  thats all on the back.  On
> the front is even less useful info :-)
> 
> So, what I need to do, it appears, is get next to a REAL AP and
> see what happens when I do the above iwlist eth1 scan...
> 
> I'll report back when I finally get a chance to do that.
> 
> Thanks again to all who responded!  (That iwlist thing I've not seen
> before, and I can tell you I've been looking!)
> 
> Oh - Will asked what kernel I was running.  Its 2.6.8-2-686
> (I'd not heard about iwconfig to monitor mode either, so that's something
> else for me to try, if I remember)
> 
> rc
> 
> 

-- 

Flo

Re: cpu throttling--what is it?

[Jochen Schulz]

Luca Pireddu:
> Could someone explain to me (or point me to where I can find an answer) what 
> CPU throttling is?  My sony vaio has 8 CPU throttling levels:

It is a cheap replacement for real performance states (and probably
doesn't give you much additional battery lifetime, if at all). If you
throttle your CPU down by 50%, you can think of it as if your CPU does a
NOOP at every second cycle. So you just lose speed, but your CPU's
temperature may drop a bit. It won't save much power because you still
have the same CPU voltage and you still have the same instructions to
compute. It just takes longer and you need less power to cool your
system.

J.
-- 
I am on the payroll of a company to whom I owe my undying gratitude.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: Netgear wg511, 2.6/Sarge - weird?

[Rusty Carruth]

Jochen Schulz wrote:


Rusty Carruth:
 


eth1  NOT READY!  ESSID:off/any
   



This is bad. You can try do 'iwconfig mode monitor' or 'iwconfig mode
managed' and see whether the output still stays the same.

 


well, the 'NOT READY' stays the same, but Mode does change from
managed to monitor and back.  I have played with changing the power,
and iwconfig reports the change.  I can also set the essid to an
arbitrary string, and it reports same in the iwconfig.

It all seems to work, other than the 'NOT READY!' part...


During all the above the green light never let a peep of greenness out.
   



This is also bad. What does 'cardctl status' tell you?
 


Socket 0:
 3.3V CardBus card
  function 0: [ready]
Socket 1:
 no card

Which is probably right - one slot is empty, one has the netgear
in it.

Stranger and stranger.  I lean toward the 'it ain't gonna work', but
it seems like it _almost_ works...

Oh - someone asked if I'd said 'ifconfig eth1 up', so I tried it (after
all the fooling above) and got:

   SIOCSIFFLAGS: No such file or directory

Thanks to all for the help thus far!

rc


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Touchpad device changing from event1 to event0

[Mattia Dongili]

On Mon, Aug 29, 2005 at 04:20:36PM +0200, Michelasso wrote:
[...]
> some minor problems I have with the touchpad. When I use it with the
> synaptics xfree86 drivers loaded often it happens that even if I am
> moving the finger on the touchpad the cursor doesn't move, and I have
> to release the finger from the touchpad and to tap again to make it to
> move. Or some other times instead of moving the cursor, it scrolls up
> and down the window is it above, as if I was tapping above the

this is a feature actually :)
It's mentioned in the package description as:
  * Vertical scrolling (button four and five events) through moving the
finger on the right side of the touchpad

Take a look at man 5 synaptics where an excellent explanation is
provided. If believe this feature is annoying you can play with
LeftEdge, RightEdge, TopEdge, BottomEdge values in order to make the
"scroll area" smaller or disabling it at all.
Try first using synclient in order to change values on the fly and the
make them persistent updating your xorg.conf
Also, quoting the manpage:
"A good way to find appropriate edge parameters is to enable the
SHMConfig option and run "synclient -m 1" to see the x/y coordinates
corresponding to different positions on the touchpad."

Ah, note that the manpage is only availble from 0.14.3.

> vertical scroll bar of it, while I am not doing this. Or when I double
> tap on the firefox url form it doesn't select all the url it is
> currently inside it.

and this might be due to inappropriate FingerHigh, FingerLow,
MaxDoubleTapTime. Same suggestions as above apply :) but one more quote:
"The MaxDoubleTapTime... If you can't perform double clicks fast enough
(for example, xmms depends on fast double clicks), try reducing this
parameter.  If you  can't  get  word  selection to work in xterm (ie
button down, button up, button down, move mouse), try increasing this
parameter."

> This problems don't appear when instead the synaptics driver it is not used.

Of course because all the above features are missing!

-- 
mattia
:wq!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re:Cisco 350 with WEP - SOLVED

[Patrick Wiseman]

In-Reply-To:<[EMAIL PROTECTED]>

(Apologies, but my mail clients won't let me set the In-Reply-To
header, so I'm resorting to the above, and cc'ing the OP.  And I'm
not on this list, so please CC me with any replies.)
 
I was having extraordinary difficulty getting my Cisco Aironet 350 to
connect to my WEP-encrypted wireless network.  I Googled, and
found, among other things, this thread - but no solution.  I have
finally succeeded, and am so connected even as I speak.

I've described the process at http://ul451.gsu.edu/~pwiseman/airo350.html, but here's a condensed version:

Set your access point to use a "Shared Key".

Then write a shell script to connect to your wireless network, along the following lines:

#!/bin/sh
/sbin/iwconfig eth0 essid "YourNetworkID"
echo 0 XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX: > /proc/driver/aironet/eth0/WepKey
iwconfig eth0 key restricted [1]
/sbin/ifup eth0

For the life of me, I could not get iwconfig to set the key, but that
echo command does it.  The script needs to be run as 'root' as
mere mortals can't set parameters with iwconfig (or so it seems by me,
anyway).  I haven't tried setting the script SUID root, but
presumably that would work.

HTH someone
Patrick

Re: Wireless network card

[Alan Ianson]

On Thu August 25 2005 06:52 am, RAZEK wrote:
> El mié, 24-08-2005 a las 09:27 -0700, Alan Ianson escribió:
> > Hello List,
> >
> > I would like to get wireless access working on my laptop, an hp pavilion
> > ze4400. When I bought the laptop it was running windows with a 3com
> > 3crshpw196 that was working, but now I have debian Sarge (stable)
> > installed and I'm not sure but I don't think this card is supported.
> > LSPCI doesn't show anything different when I put the card in, but this is
> > a cardbus card. Will lspci list a cardbus card?
> >
> > I have my eye on a d-link dwl-g630 card
>
> I already have that wireless card (dwl-g630 / chipset atheros), the only
> thing that i did  was  :
> make kernel compilation (debian-style)
> compile madwifi driver
> ifconfig ath0 up
> and it works fine

Thanks for the tip. I did go buy this card and built the madwifi package and 
it seems to work quite well. Looking back I think the 3com card was also 
working, I just didn't know how to configure debian to get it up and running. 
I have an open unencrypted linkup to the ap right now so I need to set it up 
with a bit more security. Can you give me any pointers on how to set that up? 
Where do I put that config? Does it go under ath0 in /etc/network/interfaces?

I need to get straight in my head how to configure wireless in debian. I seem 
to have it working now, but I'm not sure if I can do it again.. ;)

Re: Wireless network card

[Luca Pireddu]

On Monday 29 August 2005 21:19, Alan Ianson wrote:

>
> Thanks for the tip. I did go buy this card and built the madwifi package
> and it seems to work quite well. Looking back I think the 3com card was
> also working, I just didn't know how to configure debian to get it up and
> running. I have an open unencrypted linkup to the ap right now so I need to
> set it up with a bit more security. Can you give me any pointers on how to
> set that up? Where do I put that config? Does it go under ath0 in
> /etc/network/interfaces?
>
> I need to get straight in my head how to configure wireless in debian. I
> seem to have it working now, but I'm not sure if I can do it again.. ;)

Yes, you can put it in /etc/network/interfaces.  The stanza might look 
something like

iface home-wireless inet dhcp
  wireless-essid your essid
  wireless-mode managed
  wireless-channel 2
  wireless-key ------CC

Don't put quotes around your ESSID.  You'll need the 'wireless-key' if you're 
using WEP.  See man iwconfig for the full list of wireless configuration 
options.  All the options defined in there go preceded by a "wireless-" if 
they're used in the interfaces file.

To bring the adapter up using that particular configuration run as root
$ ifup ath0=home-wireless

where ath0 is your device's name.  You can also have alternate configurations.  
For instance

iface work-wireless inet static
  address 192.168.1.5
  netmask 255.255.255.0
  gateway 192.168.1.1
  wireless-essid work
  wireless-mode managed
  wireless-channel 2
  wireless-key off

and use it with $ ifup ath0=work-wireless for more details check man 
interfaces and man iwconfig.

If you move around a bit and really want to get fancy look here:  
http://arstechnica.com/columns/linux/linux-20040413.ars/2
You can apparently set up your laptop to automatically detect which network is 
available and choose the appropriate adapter configuration.  I haven't tried 
it myself (yet!).

Hope that helps.

Luca


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Help, Asus W3 laptop

[Rony]

Hi,

I've tried to install Debian, Ubuntu, SUSE on this Asus W3 wide screen
laptop. When in graphic mode, i only get vertical stripes. When
installing SUSE, it goes to graphic mode during installation, but after
finish the installation and reboot, also display vertical stripes.
On WindowsXp i use resolution 1280x768 for that.

Thanks in advance for the advises.


Regards,
Rony


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Wireless network card

[Freddie Cash]

> On Thu August 25 2005 06:52 am, RAZEK wrote:
> Thanks for the tip. I did go buy this card and built the madwifi
> package and it seems to work quite well. Looking back I think the
> 3com card was also working, I just didn't know how to configure
> debian to get it up and running. I have an open unencrypted linkup
> to the ap right now so I need to set it up with a bit more security.
> Can you give me any pointers on how to set that up? Where do I put
> that config? Does it go under ath0 in /etc/network/interfaces?

> I need to get straight in my head how to configure wireless in
> debian. I seem to have it working now, but I'm not sure if I can do
> it again.. ;)

Install the WPA Supplicant.  Gives you a single config file for
configuring unencrypted, WEP-encrypted, or WPA encrypted network
connections.

WPA Supplicant handles the connection between the wireless card and
the access point.  Then you just run DHCP to handle the IP
configuration.

Works like a hot damn.  And so much simpler than using shell scripts
and the /etc/network/* config files to manage the interface.

Even better, it's portable across OSes.  I've used the same
wpa_supplicant.conf file on FreeBSD 5.3, 5.4, and 6.0, as well as
Debian 3.1, and testing.
-- 
Freddie Cash, CCNT CCLPHelpdesk / Network Support Tech.
School District 73 (250) 377-HELP [377-4357]
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel decision

[Tobias Krais]

Hi Koen,

>>I was planning on getting the vanilla 2.6.13 as soon as it is out and apply 
>>the MM patchset (good idea for laptops?).
> 
> Enlighten me: What does the 2.6.13 kernel and/or the mm patches
> specifically add for laptop users? 

Kernel 2.6.13 has better ACPI support (Suspent to disk, suspend to RAM)
- that is what I read.
And the mm patches has drivers that didn't succeed to come with in
2.6.13, e.g. Reiser4.

So I would say: Kernel 2.6.13 is good, but mm Patches are not nessecary
if you don't need the drivers.

Greetings, Tobias


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kernel decision

[Koen Vermeer]

On Tue, 2005-08-30 at 08:30 +0200, Tobias Krais wrote:
> Kernel 2.6.13 has better ACPI support (Suspent to disk, suspend to RAM)
> - that is what I read.

I have S3 and S4 working with 2.6.12 as well, with suspend2 (for S4). So
there's not much to gain for me in that area :-)

> And the mm patches has drivers that didn't succeed to come with in
> 2.6.13, e.g. Reiser4.
> So I would say: Kernel 2.6.13 is good, but mm Patches are not nessecary
> if you don't need the drivers.

I agree! I plan on going to 2.6.13 anyway, but I'll just wait for the
source to be packaged.

Koen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]