Dell Inspiron 6000

[dschaus]

Well, I was so curious that I already tested it.

I've got everything to work as I needed it, but I'm sorry, I don't need gpm, so I can't tell you anything about that !
What is working now:
Touchpad is working as synaptics device, including scrolling
You can plug in an USB-mouse whenever you like to, both devices work just fine.
cat /dev/psaux gives output from the touchpad
cat /dev/input/event0 is the keyboard
cat /dev/input/event1 is sometimes the touchpad, but not always, can't tell why
cat /dev/input/event2 is the USB mouse,
cat /dev/input/mice is also the USB mouse, you have to use mice (not mouse0,1,2...) because the number changes when you unplug and replug the mouse
And (as you can see in the .config file) udev is active, so there is no problem with that !

Maybe the speed of the touchpad-cursor needs some tuning, it tages ages to get from left to right in a 1680 resolution
EDIT: For testing reasons I added Option "DynamicClocks" "on" in the graphics-card-part and it appears as if it really works (of course only with the radeon driver), because the laptop now needs about 2 Watts less ! This is not yet included in the file below !

I have uploaded the configs to my webserver, they are so big, I wouldn't want to post them here, but I guess I'll forget them there anyways so they'll be online quite a long time

www.topspritten.de/xorg.conf
www.topspritten.de/.config

@Everybody: Remember: DO NOT simply copy them onto your system if you don't have the ATI X300 graphics card ! Also: The xorg-file is REALLY messed up, I have only been changing the file for quite some computers with quite some different graphics cards etc. Also: I have just seen that acceleration is not enabled as I'm currently not using the fglrx file, don't know why that is, maybe I'll change that sometime.

Again I hope that this will help some people !
CU
Dave

EDIT2: Just stumbled over this page
http://www.geocities.com/stomljen/

It might help some people with the i915 graphics card, I have (of course) not tested it though !

[acidbrain]

I just wondered if it is safe to use gcc 3.4.3. Especially the masked glibc frightens me.

Did anyone experience any problems?

One idea about the SD-Reader (it still doesn't work, right?): If i remember right, if've read in a magazine (c't 9/2005, it's german), that the reader is not downwards compatible to MMC.

Greets,
acidbrain

[VinzC]

I just wondered if it is safe to use gcc 3.4.3. Especially the masked glibc frightens me. [...]

I've yet had several problems on other machines but none have been implied by using GCC 3.4.x. If you follow the guide at the beginning of this thread, there will be no problem. I've unmasked things as mentionned here and I've had no crash at all.

If you want your laptop to be fully optimized for Pentium-M then you'll have to unmask. If you're a bit reluctant at unmasking GLIBC, then you can safely stick to GCC 3.3.x and wait till GCC & co are unmasked.

[VinzC]

Well, I was so curious that I already tested it.

I've got everything to work as I needed it, but I'm sorry, I don't need gpm, so I can't tell you anything about that !
What is working now:
Touchpad is working as synaptics device, including scrolling
You can plug in an USB-mouse whenever you like to, both devices work just fine.
cat /dev/psaux gives output from the touchpad
cat /dev/input/event0 is the keyboard
cat /dev/input/event1 is sometimes the touchpad, but not always, can't tell why
cat /dev/input/event2 is the USB mouse,
cat /dev/input/mice is also the USB mouse, you have to use mice (not mouse0,1,2...) because the number changes when you unplug and replug the mouse
And (as you can see in the .config file) udev is active, so there is no problem with that !
[...]

I have finally found something: http://homepage.mac.com/felipe_alfaro/i ... 346338003/. I've followed what the guy says in his blog, i.e. manually loading synaptics driver in Xorg. I also removed the input declaration from the ServerLayout section. There was also an option "CorePointer" that I removed from the "Input" section too. Now it works.

Ok, I still have to find how to enable scrolling and tap/drag lock but at least I get no error and the touchpad is functional.

And - oh yes - I've tried a DVD after patching libata.h as mentionned above in this thread and it's more than satisfying, even in VESA mode. I'll try the DRI snapshot as it seems to fix bad kernel support for DRI. I've read that currently XOrg doesn't find matching DRI into the kernel module then switches to VESA - if I have understood; that's the reason why the latter must be patched using the snapshot.

FYI I'm using xorg-x11-6.8.99.5.

I'll try and post later if I succeed.

[VinzC]

Forget the DRI snapshot. I never succeeded in having it work properly. Most of all I get worse performance with glxgears than without the patch. After tuning all I could get was a system freeze when I closed X.

Patch removed. Still working in VESA mode but now I don't care.

[Sejam]

Forget the DRI snapshot. I never succeeded in having it work properly. Most of all I get worse performance with glxgears than without the patch. After tuning all I could get was a system freeze when I closed X.

Patch removed. Still working in VESA mode but now I don't care.

Great, now I read this after wondering what is happening. I was messing around with my system trying to see if I could get new things working. I had downloaded the lastest i915 drivers, and now my system is freezing when I close X. Guess I'll try one of the older dri drivers to see if that is the problem.

[VinzC]

Guess I'll try one of the older dri drivers to see if that is the problem.

I wouldn't if I were you...

[acidbrain]

Hi,

I've figured out the keyboard definitions of the quick access keys on the front for use with x11-misc/lineakd.
You can assign any commands to the keys, I use them for controlling xmms - and it rocks.

lineakd-0.7.2 did not compile, I installed the masked lineakd-0.8.3, which works fine for me.
As 0.7.2 compiled without problems with gcc version 3.3.5 on my desktop system, so this might fall into the category "why masked gcc/glibc is evil"

This should do the trick:

Code: Select all

# echo "x11-misc/lineakd ~x86" >> /etc/portage/package.keywords
# echo "x11-misc/lineak-defaultplugin ~x86" >> /etc/portage/package.keywords
# emerge lineakd lineak-defaultplugin

Now, for the configuration:

Insert this in /etc/lineakkb.def:

Code: Select all

[DI6000]
  brandname = "Dell"
    modelname = "Inspirion 6000 Notebook (Quickaccess keys)"
      [KEYS]
        Play        = 162
      	Previous    = 144
        Next        = 153
	Stop        = 164
	VolumeDown  = 174
	Mute        = 160
	VolumeUp    = 176
  [END KEYS]
[END DI6000]

Now enter "lineak -c DI6000" with your daily user account (=> not as root )

Then edit the configuration file ~/.lineakd/lineakd.conf and assign commands to the buttons.
Here is what i use:

Code: Select all

Mute = EAK_MUTE
Next = "xmms --fwd"
Play = "xmms --play-pause"
Previous = "xmms --rew"
Stop = "xmms --stop"
VolumeDown = EAK_VOLDOWN
VolumeUp = EAK_VOLUP

Now enter "lineakd -v" and check if it works.
If everthing is ok, you can start lineakd automatically everytime you start X.
With Gnome, you can use Applications -> Desktop Preferences -> Advanced -> Sessions, Startup Programs
Just add "/usr/bin/lineakd"
With KDE, you can add a symlink to ~/.kde/Autostart:
ln -s /usr/bin/lineakd ~/.kde/Autostart

Now you should be done! Have fun!

If this was to easy for you, then read on, because:

Unfortunately, I did not get any of the Fn-Keys to work.

I've assigned a keycode to the keys that cause an entry in
/var/log/messages if pressed.

Code: Select all

Key		Scancode	Assigned keycode
Fn+F1/Sleep*	e00a		231
Fn+F2/Wireless	e008		232
Fn+F3/Battery	e007		233
Fn+F8/CRT/LCD	e00b		238
Fn+F10/Eject	e009		240

*Note: My keyboard-layout is german, so the labels may be different on
other systems.

getkeycodes gives this output:

Code: Select all

d6k root # getkeycodes
Plain scancodes xx (hex) versus keycodes (dec)
for 1-83 (0x01-0x53) scancode equals keycode

 0x50:   80  81  82  83  99   0  86  87
 0x58:   88 117   0   0  95 183 184 185
 0x60:    0   0   0   0   0   0   0   0
 0x68:    0   0   0   0   0   0   0   0
 0x70:   93   0   0  89   0   0  85  91
 0x78:   90  92   0  94   0 124 121   0

Escaped scancodes e0 xx (hex)

e0 00:    0   0   0   0   0   0   0 233
e0 08:  232 240 231 238   0   0   0   0
e0 10:  165   0   0   0   0   0   0   0
e0 18:    0 163   0   0  96  97   0   0
e0 20:  113 140 164   0 166   0   0   0
e0 28:    0   0 255   0   0   0 114   0
e0 30:  115   0 150   0   0  98 255  99
e0 38:  100   0   0   0   0   0   0   0
e0 40:    0   0   0   0   0 119 119 102
e0 48:  103 104   0 105 112 106 118 107
e0 50:  108 109 110 111   0   0   0   0
e0 58:    0   0   0 125 126 127 116 142
e0 60:    0   0   0 143   0 217 156 173
e0 68:  128 159 158 157 155 226   0 112
e0 70:    0   0   0   0   0   0   0   0
e0 78:    0   0   0   0   0   0   0   0
d6k root #

I've tried this config:

Code: Select all

[DI6000-ALL]
  brandname = "Dell"
    modelname = "Inspirion 6000 Notebook (Fn + Quickaccess keys)"
      [KEYS]
        Play        = 162
      	Previous    = 144
        Next        = 153
	Stop        = 164
	VolumeDown  = 174
	Mute        = 160
	VolumeUp    = 176
	Sleep       = 231
	Wireless    = 232	
	Battery	    = 233	
	CrtLcd	    = 238
	Eject	    = 240

  [END KEYS]
[END DI6000]

Unfortunately, lineakd does not react on any of the Fn-keys.

If I start xev (after having defined the keycodes) and press Fn+F10
(Eject), nothing happens, but in /var/log/messages appears:

[...]
May 11 00:23:41 d6k keyboard.c: can't emulate rawmode for keycode 240
[...]

If I press any of the other Fn-keys, nothing at all happens.
Any ideas are welcome, I already wrote a mail to the lineakd-devel mailinglist.

Oops, this was more text than expected. I hope it is useful for someone.

CU,
acidbrain

[Sejam]

Forget the DRI snapshot. I never succeeded in having it work properly. Most of all I get worse performance with glxgears than without the patch. After tuning all I could get was a system freeze when I closed X.

Patch removed. Still working in VESA mode but now I don't care.

Great, now I read this after wondering what is happening. I was messing around with my system trying to see if I could get new things working. I had downloaded the lastest i915 drivers, and now my system is freezing when I close X. Guess I'll try one of the older dri drivers to see if that is the problem.

That was the problem I was having with the system freezing when I closed X. Used one of the older DRI snapshots that I knew worked and it fixed that problem.

Of course, I've now decided to try using the xorg-cvs and ran into problems. All modules loaded correctly, but I do not have DRI (no /dev/dri/card0) even though the kernel module did load correctly. The other thing is that since I've moved to the xorg-cvs, the system is requiring A LOT more ram to run. Not sure if anybody else noticed this. I'm talking about 300+ megs more than before I did an upgrade of xorg.

[VinzC]

Hi, acidbrain.

This is indeed quite interesting. I'll try it on my laptop. I've upgraded GCC/GLIBC to 3.4 so I'll tell you if I'm with the Dark Side of the Force or not

[PolarXL]

#2) I have the ATi X300 and it was a pain to try to find out what needs to be done in order to get DRI/DRM working. Finally with a little googling I found
a document that stated that in order to get fglrx to load and functional you need to have agpgart and intel_agp loaded first. So what I did was this

Code: Select all

Device Drivers ---> Character device ---> <M> /dev/agpgart (AGP Support)
Device Drivers ---> Character device ---> <M> /dev/agpgart (AGP Support) ---> <M> Intel 440LX/BX/GX, I8xx and E7x05 chipset support

make && make modules_install
modules-update

# echo "agpgart" >> /etc/modules.autoload.d/kernel-2.6
# echo "intel_agp" >> /etc/modules.autoload.d/kernel-2.6
# echo "fglrx" >> /etc/modules.autoload.d/kernel-2.6

After a nice reboot everything seemed to work just fine. I hope this helps some people.

Idle curiosity, what's the advantage of using "intel_agp" as opposed to "ati-agp"? Considering it's an ATI card.

The one problem I haven't managed to get around (I'm using ati-agp, but I'm more than willing to dump that in the name of progress), is that certain games (Supertux, Tuxracer, Quake 3) don't run fullscreen in fullscreen mode, they instead run in a window about the size of windowed mode, with black borders.

That, and Unreal Tournament seems to have no concept of framerate limit. Tapping forward launches me across the map.

Does the intel driver fix this stuff? Does the ATI X300 even classify as intel_agp?

-Alex

[VinzC]

www.topspritten.de/xorg.conf
www.topspritten.de/.config

Hi, dschauss. I must thank you for your xorg.conf for I copied all your config lines about Synaptics/Alps GlidePoint touchpad and it works. I don't have to load the driver as a separate module anymore. I think the "AlwaysCore" option did help. I had used "CorePointer" for both the touchpad and USB mouse, which probably conflicted.

Now I have a functional touchpad. Vertical scrolling works. Tap & Drag also works. I'll try tuning acceleration because, yes, it takes ages to cross the screen from left to right (and vice versa).

[dschaus]

Hi VinzC,
great to hear that, I'm also quite sure that the "AlwaysCore" Option does alot !
I got the cursor-speed working nicely by setting the minspeed and maxspeed Options a bit higher, tuning the acceleration did nothing good to me, the cursor just became racing around so I wouldn't suggest changing this value !

@PolarXL: Currently, again, I do not have much spare time, but I think in the next days I'll test the games you mentioned (all but quake3 or is there a demo-version around ? I'll check this), and tell you my results. The only thing I can currently tell you is that, afaik, ati-agp should be for ati-based-chipsets, in the I6000, there is an Intel Chipset, so I guess intel_agp is the right module. But I'm not really into this stuff and I could be wrong, so don't rely on this completely

I do have three more questions to all owners of an I6000:
1. Does the blue light in your media-buttons always work ? Even in windows mine sometimes do not light up, or only flash shortly, or sometimes they are just dimly lit. The buttons themself work all the time, and this doesn't really annoy me, but I'm curios if others have this problem, too.
2. Does your Bluetooth-LED light up completely when activated ? Mine only flashes on and off (long time off, very short time on), and I have the feeling (not yet checked) as if this only happens, when I deactivated the bluetooth in windows (by clicking the B -Icon in the Systray), went to hibernation and start gentoo after that. As far as I remember the light stays on if I don't deactivate bluetooth in windows...
3. Did you get the WLAN-Light to work under gentoo ? I'm currently using a very old version of the intel-driver (below 1.0) because I couldn't get the 1.02 to work and hadn't yet the time to check the newer ones.

CU in the next days,
Dave

[VinzC]

1. Does the blue light in your media-buttons always work ? Even in windows mine sometimes do not light up, or only flash shortly, or sometimes they are just dimly lit. The buttons themself work all the time, and this doesn't really annoy me, but I'm curios if others have this problem, too.

Not tried yet with Linux but in Wind-haze everything seems to work properly; the lights come up the same way for all buttons: they are lit brightly for 2-3 seconds when pushed. They don't blink nor are dimly lit. Something makes me think your lights might have sort of an electrical problem, connexion or whatever.

2. Does your Bluetooth-LED light up completely when activated ? Mine only flashes on and off (long time off, very short time on), and I have the feeling (not yet checked) as if this only happens, when I deactivated the bluetooth in windows (by clicking the B -Icon in the Systray), went to hibernation and start gentoo after that. As far as I remember the light stays on if I don't deactivate bluetooth in windows...

The bluetooth light seems to act like the battery beacon . I really think there's something wrong with wiring inside...

3. Did you get the WLAN-Light to work under gentoo ? I'm currently using a very old version of the intel-driver (below 1.0) because I couldn't get the 1.02 to work and hadn't yet the time to check the newer ones.

The latest updates (IIRC from memory as I'm not under Gentoo right now but at the dark side of the Force ) seem to support WiFi light. It's said to be experimental currently but I didn't succeed in having it work. Note I did only a rough try and that's all.

It's inside /etc/modules.d/ipw2200, IIRC. The led variable or setting would tell how to control the panel LED. You'll have to emerge the latest ipw2200 package.

[VinzC]

3. Did you get the WLAN-Light to work under gentoo ? I'm currently using a very old version of the intel-driver (below 1.0) because I couldn't get the 1.02 to work and hadn't yet the time to check the newer ones.

Aaaaah, news are coming. Ok, slowly but they are .

I've googled a bit and saw you can put the WiFi light On by echoing 1 to /sys/bus/pci/drivers/ipw2200/0000:03:03.0/led:

Code: Select all

echo 1 >> /sys/bus/pci/drivers/ipw2200/0000\:03\:03.0/led

.

USe the appropriate bus ID on your system. Now the trick is to do that each time the interface comes up... If anyone has got an idea? Is there an event that one could use to run a script that would turn on the light? Or should we directly modify net.xxx script? (omg! this script is a nightmare now )

Note it's pointless to echo 0 to the device to turn off the light (I've tried). The light shuts down with the module. But it's less than annoying, isn't it?

[cytux]

Is there an event that one could use to run a script that would turn on the light? Or should we directly modify net.xxx script? (omg! this script is a nightmare now )

Hi,

I put:

preup() {
echo 1 >> /sys/bus/pci/drivers/ipw2200/0000\:03\:03.0/led
return 0
}

in /etc/conf.d/net

You may put there any other statements you wish to get called on net startup like iwpriv, iwconfig, enc ...

[VinzC]

Is there an event that one could use to run a script that would turn on the light? Or should we directly modify net.xxx script? (omg! this script is a nightmare now )

Hi,

I put:

preup() {
echo 1 >> /sys/bus/pci/drivers/ipw2200/0000\:03\:03.0/led
return 0
}

in /etc/conf.d/net

You may put there any other statements you wish to get called on net startup like iwpriv, iwconfig, enc ...

Damn! It was so simple... I didn't even think of it! Thanks a million times .

[Sejam]

Is there an event that one could use to run a script that would turn on the light? Or should we directly modify net.xxx script? (omg! this script is a nightmare now )

Hi,

I put:

preup() {
echo 1 >> /sys/bus/pci/drivers/ipw2200/0000\:03\:03.0/led
return 0
}

in /etc/conf.d/net

You may put there any other statements you wish to get called on net startup like iwpriv, iwconfig, enc ...

Thanks. It's definitely a working solution. Not the perfect solution unfortunetly. The perfect solution would be for the led to really come on and off according to the radio being on/off using the <FN+FS> command. I have a feeling to really get that working though would require working with the ipw2200 project to integrate it into that code.

On an additional request, has anyone managed to get the mmc/sd-card reader to work? I always forget I have it but finally just got a digital camera that uses sd-card so it would be nice. Then again after I upgraded the windows os to pro (non-standard since I get a very cheap copy from school) I cannot seem to get it to work in windows either. Grrrrr.

[VinzC]

The perfect solution would be for the led to really come on and off according to the radio being on/off using the <FN+FS> command. I have a feeling to really get that working though would require working with the ipw2200 project to integrate it into that code.

Remember the LED support is still experimental so for now the driver can only enable it on your request. I think Windoze drivers do what you'd like I think, i.e. turn on the led as soon as the interface is activated.

[cytux]

Thanks a million times .

You're welcome! Thanks a lot for some cool postings from you and the others, too!

By the way: I am waiting for xorg new version 6.9.x, because this tricky stuff in the i915 thread is not the right thing for me. Is anyone here who knows when it will turn the corner? I got intel sonoma chipset with integrated graphics and UXGA. THX!

[dschaus]

@cytux: Maybe you overlooked this, at least the readme (or the link stating "you can also look here") looks very promising and easy ! Btw.: Thanks for the WLAN-LED-"Patch" !

EDIT2: Just stumbled over this page
http://www.geocities.com/stomljen/
It might help some people with the i915 graphics card, I have (of course) not tested it though !

@VinzC: I've got the ipw Version 1.04 up and running, but haven't yet tested the LED-stuff. I'll come back here when I finally had the time for this (and also the ATI-Problem by PolarXL). But thanks already for the info on the light in the media-buttons, I still have to take a deeper look at this though it doesn't annoy me at all --> I will not send the notebook back to dell, maybe short before the warranty is over or when any other Problems arise (which I do not hope !).

CU
Dave

[VinzC]

@VinzC: I've got the ipw Version 1.04 up and running, but haven't yet tested the LED-stuff. I'll come back here when I finally had the time for this

It works on my laptop with ipw2200 1.0.3 and ipw-firmware 2.2. Hope it will too on yours .

[seppelrockt]

Warning: New BIOS Version 06 will (probably) render your X unusable with i810 (black screen)!!!

At least that was the problem with my box. I updated the BIOS two days ago and yesterday my X didn't work with the i810 config anymore. I did a BIOS downgrade and things are OK again.

The BIOS 06 seems to downgrade the Video BIOS from Version 3412 (BIOS 05) to 1219 - and that makes problems. Can anybody confirm this - ähhh well you might not be interested to do so

With the old BIOS and vanilla sources finaly DRI works here without snapshots, glxinfos shows DRI enabled and glxgears gives me ~ 930fps (at 1280x800). That's OK for now.

Idea for the the wireless LED:

1. Would it be possible to use lineak or something to make LED dependent on press the wireless hotkeys. (On would of cause first need to find out the wireless state on boot)?

2. Is there any chance to use the output of iwconfig (radio=off) to set the LED status?

[seppelrockt]

I need some help with the Alps Touchpad:

1. Were did you found information about the xorg Options for synaptics - I used the infos from the above xorg.conf but want to know waht the options meen.

2. I can't find CONFIG_MOUSE_PS2_SYNAPTICS in my kernel config. How can I enable this in vanilla kernel 2.6.12rc4? Do I have to patch?

[cytux]

@cytux: Maybe you overlooked this, at least the readme (or the link stating "you can also look here") looks very promising and easy !

EDIT2: Just stumbled over this page
http://www.geocities.com/stomljen/
It might help some people with the i915 graphics card, I have (of course) not tested it though !

Thank you. Yes I got it but I haven't tried it yet. I need some time. Anyone selling time in barrels here?

@seppelrockt:

Thanks a lot for the bios-warning! I don't think it's possible to install an automatic LED script yet, because it's possible to turn the LED on but unfortunately not off. It will may be possible in the future, but I think it's not so important, because my WLAN is always activated.