Closing the lid doesn't lead to a freeze, cause i configured it to only blank the screen (with gnome power manager). Normally closing the lid should proceed a suspend to ram, but this is (still) not working.

This is also what I did but the PC freezes anyway .

EDIT: I'm using KDE, Gnome and XFCE so I've setup the lid close event in /etc/acpi by using vbetool dpms off/on. I'll try using these desktop's facilities or just removing the ACPI event._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”

Ok, I can play dvd's now without any problem. My dvd-drive is recognised as /dev/sr0, and I don't have any problems with the video card. Seeing it like that, it seems that DMA works... But, I have a final test for you too: try running dvdshrink from wine. How much time does it take you to compress a dvd to a 4.7 dvd size? While in windows this takes about 40mins in my case, linux gives me an ETA of about 8 hours! :S So... do you think DMA is really working?
Please try that to see if I'm the only one with this problem...
Thnx!

How much time does it take you to compress a dvd to a 4.7 dvd size? While in windows this takes about 40mins in my case, linux gives me an ETA of about 8 hours! :S So... do you think DMA is really working?

Are you comparing dvdshrink under Wine and dvdshrink under Windows? If yes then I can relief you a bit: Wine introduces a large overhead when running native windows applications. It's just enough for you to notice this by resizing applications using the size grip. You'll see it's tremendously...sloooooowww...

I wouldn't worry that much if I were you but use an OSS to shrink a DVD. I don't know of any such software under Linux though - but I'm no expert._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”

I would like to be able to turn on and off the touchpad "on the fly", while i'm using the usb external mouse. Maybe with some hotkey configuration (could put it in fluxbox keys file)... Any ideas?
Some previous dell laptop models had a feature which let them to enter the bios or something similar to the bios at any time without the need for rebooting... Do you think this can be done with the inspiron e1505 (I know, this topic isn't about that laptop, but i'm guessing it's very similar since this thread has been really usefull in the whole "gentooing" process ) lol
About the touchpad, i'm thinking that maybe some sort of an xorg command may work (??)

The only thing I know about the touchpad is that it's handled and described in xorg.conf. So it would mean - using my own knowledge as of now - removing the lines about the touchpad in the ServerLayout section before running X. But I guess there's another way..._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”

Yeah, I thought of that too, but then you would have to restart X every time you want to use the touchpad (not to mention editing the xorg.conf file too). There should be a way to do it "on the fly", for example: even though the language of the keyboard is defined in the xorg.conf, you can switch between different languages from the command line too without any need of editing the conf file or restarting X.
Anyway, it isn't very important, it's just a comfortable feature to have, since sometimes I accidentally touch the touchpad and make a mess when I could just disable it when I'm not using it since I generally use an external mouse.

Last edited by dinsmore on Tue Aug 01, 2006 1:55 pm; edited 1 time in total

Anyway, it isn't very important, it's just a comfortable feature to have, since sometimes y accidentally touch the touchpad and make a mess when I could just disable it when I'm not using it since I generally use an external mouse.

I think there is an option to activate in xorg.conf, which sets the sensitivity level of the touchpad and prevents accidental taps like these. I don't know what option but I'm almost sure it is indicated in the driver readme._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”

Ok, I'll look into it. This feature, is it gonna reduce touchpad sensibility or it will turn off the tapping option, leaving just the buttons working for clicks?
By the way, (sorry for the ignorance), where can I find the driver readme??
Thanks for everything

Ok, I'll look into it. This feature, is it gonna reduce touchpad sensibility or it will turn off the tapping option, leaving just the buttons working for clicks?

No, it'll reduce sensibility only .

dinsmore wrote:

By the way, (sorry for the ignorance), where can I find the driver readme??

When I have to do that I usually locate synaptics and lookup in the results for any readme (can be all uppercase) in the files that end with .gz._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”

Thanks to this forum I've got my e1705 smostly working. However, while thesing my keyboard layout I hit the fn-end mute hotkey and now I have no pcm. any ideas on how to fix this. Ive tried everthing I can think of including re-emerging the alsa drivers but nothing works.

but i notice that the "subwoofer" on the downside on the laptop does not work, or at least i don't sense it's vibrations as i do when i used on windows, has anyone else have this problem, or its just my imagination??

SO, given the usb problems, I re-emerged udev and hotplug. usb working again, but no pcm[...]

Have you tried /etc/init.d/alsasound save after you have set the desired mixer level?_________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”

Have you tried /etc/init.d/alsasound save after you have set the desired mixer level?

Yeah, doesn't help. Starting xine is the only thing that seems to iniitialze the pcm, other audio apps I've tried don't work. It seems like something happend at bios level, like the problems with the wireless hotkey discused on the first page or two, except that reloading the modules doesn't work either.

It seems that I have also disabled my wireless card with the wireless hotkey. I have the dell1390 card and unloading and reloading the bcm43xx driver does not reactiveate the card. I have no Idea how to reactivate this stuff that has aparently been switched off by bios, any ideas?
thanks

It seems that I have also disabled my wireless card with the wireless hotkey. I have the dell1390 card and unloading and reloading the bcm43xx driver does not reactiveate the card. I have no Idea how to reactivate this stuff that has aparently been switched off by bios, any ideas?
thanks

The RF-Kill switch is purely BIOS and there's nothing loading/reloading the driver could do about it. You must re-activate the card using the RF-Kill switch again. It toggles the WiFi state between enabled/disabled each time it is pressed. On Dell Laptops it is Fn+F2._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”

Have you tried /etc/init.d/alsasound save after you have set the desired mixer level?

Yeah, doesn't help. Starting xine is the only thing that seems to iniitialze the pcm, other audio apps I've tried don't work. It seems like something happend at bios level, like the problems with the wireless hotkey discused on the first page or two, except that reloading the modules doesn't work either.

Then you can try deleting /etc/asound.state. It'll force ALSA drivers to re-create the state file when you either force /etc/init.d/alsasound save or reboot the computer. Set the appropriate mixer levels first then run the alsa script command._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”

Then you can try deleting /etc/asound.state. It'll force ALSA drivers to re-create the state file when you either force /etc/init.d/alsasound save or reboot the computer. Set the appropriate mixer levels first then run the alsa script command.

Thanks for the quick response. After deleting /etc/asoundd.state I saved and rebooted. same problem.

Quote:

The RF-Kill switch is purely BIOS and there's nothing loading/reloading the driver could do about it. You must re-activate the card using the RF-Kill switch again. It toggles the WiFi state between enabled/disabled each time it is pressed. On Dell Laptops it is Fn+F2

Great, then tis problem is with the patched version of the driverI'm using.

Normally yes. Anyway you can try patching. You may get slight differences (e.g. fuzz factor) but generally it should be Ok. And if it doesn't work you can rollback by either reverse patching (patch -R ... < patchfile) or cleaning and reinstalling your kernel sources._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763
“Wow! I feel root”