Πρόβλημα φωτεινότητας σε laptop acer aspire 5745-DG

[pete-maister]

Δυστυχως φιλε δεν γινεται τιποτα.Τα κουμπια για τον ηχο ειναι μια χαρα για την φωτεινοτητα δεν δουλευουν...Ειχα ακουσει οτι μπορει να φταιει το bios μπορεις να μ πεις σε αυτην την περιπτωση τι κανω?

[Learner]

Δώσε το αποτέλεσμα της εντολής

Κώδικας: Επιλογή όλων

cat /etc/default/grub

[pete-maister]

Κώδικας: Επιλογή όλων

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX="acpi_osi=Linux"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

[pete-maister]

Αυτο μου εβγαλε...

[Learner]

Έτρεξες μετά

Κώδικας: Επιλογή όλων

sudo update-grub

;;

Άλλαξε τη γραμμή GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" σε GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux"
και την άλλη GRUB_CMDLINE_LINUX="acpi_osi=Linux" κάνε την όπως ήταν. Δηλαδή GRUB_CMDLINE_LINUX=""

Μην ξεχάσεις μετά τις αλλαγές sudo update-grub.
Επανεκκίνηση και βλέπουμε.

[pete-maister]

Το εκανα κι αυτο αλλα τιποτα..:/

[Learner]

Το εκανα κι αυτο αλλα τιποτα..:/

Μια τελευταία παράμετρο θα δοκιμάσουμε .

Κάνε κάτι άλλο . Κάνε μια επανεκκίνηση και μόλις φτάσεις στον grub, στη γραμμή που επιλέγεις να κάνει boot το Ubuntu, πάτα το πλήκτρο 'e' . Πλοηγήσου με τα βελάκια στην προ-τελευταία γραμμή και με το δεξί βελάκι πήγαινε μετά το 'ro' άσε ένα κενό και γράψε ακριβώς αυτό acpi_osi=\"!Windows 2006\" (γράψε το σε ένα χαρτί )
Πάτα το F10 για να κάνεις boot.
Αν δουλεύει , θα το κάνεις μετά μόνιμο. Ξέρεις πως. Απλά δεν το κάνουμε από τώρα μη τυχόν και δεν κάνει boot το σύστημα με αυτή την παράμετρο.

[simosx]

Δυστυχως φιλε δεν γινεται τιποτα.Τα κουμπια για τον ηχο ειναι μια χαρα για την φωτεινοτητα δεν δουλευουν...Ειχα ακουσει οτι μπορει να φταιει το bios μπορεις να μ πεις σε αυτην την περιπτωση τι κανω?

Δες το αρχείο /usr/share/doc/udev/README.keymap.txt.gz
όπου έχει οδηγίες για τη διαλεύκανση του προβλήματος. Ακολουθάς τα βήματα της ενότητας «Fixing broken keys».

[pete-maister]

Mπορείς να με βοηθήσεις λιγο με αυτο το README ?Το διαβασα αλλα δεν καταλαβα τιποτα;/Aν θες πες μου τι μπορω να κανω.Τo README λεει αυτο...

Κώδικας: Επιλογή όλων

= The udev keymap tool =

== Introduction ==

This udev extension configures computer model specific key mappings. This is
particularly necessary for the non-standard extra keys found on many laptops,
such as "brightness up", "next song", "www browser", or "suspend". Often these
are accessed with the Fn key.

Every key produces a "scan code", which is highly vendor/model specific for the
nonstandard keys. This tool maintains mappings for these scan codes to standard
"key codes", which denote the "meaning" of the key. The key codes are defined
in /usr/include/linux/input.h.

If some of your keys on your keyboard are not working at all, or produce the
wrong effect, then a very likely cause of this is that the scan code -> key
code mapping is incorrect on your computer.

== Structure ==

udev-keymap consists of the following parts:

keymaps/*:: mappings of scan codes to key code names

95-keymap.rules:: udev rules for mapping system vendor/product names and
input module names to one of the keymaps above

keymap:: manipulate an evdev input device:
* write a key map file into a device (used by udev rules)
* dump current scan → key code mapping
* interactively display scan and key codes of pressed keys

findkeyboards:: display evdev input devices which belong to actual keyboards,
i. e. those suitable for the keymap program

fdi2rules.py:: convert hal keymap FDIs into udev rules and key map files
(Please note that this is far from perfect, since the mapping between fdi and
udev rules is not straightforward, and impossible in some cases.)

== Fixing broken keys ==

In order to make a broken key work on your system and send it back to upstream
for inclusion you need to do the following steps:

1. Find the keyboard device.

Run /lib/udev/findkeyboards. This should always give you an "AT
keyboard" and possibly a "module". Some laptops (notably Thinkpads, Sonys, and
Acers) have multimedia/function keys on a separate input device instead of the
primary keyboard. The keyboard device should have a name like "input/event3".
In the following commands, the name will be written as "input/eventX" (replace
X with the appropriate number).

2. Find broken scan codes:

sudo /lib/udev/keymap -i input/eventX

Press all multimedia/function keys and check if the key name that gets printed
out is plausible. If it is unknown or wrong, write down the scan code (looks
like "0x1E") and the intended functionality of this key. Look in
/usr/include/linux/input.h for an available KEY_XXXXX constant which most
closely approximates this functionality and write it down as the new key code.

For example, you might press a key labeled "web browser" which currently
produces "unknown". Note down this:

0x1E www # Fn+F2 web browser

Repeat that for all other keys. Write the resulting list into a file. Look at
/lib/udev/keymaps/ for existing key map files and make sure that you use the
same structure.

If the key only ever works once and then your keyboard (or the entire desktop)
gets stuck for a long time, then it is likely that the BIOS fails to send a
corresponding "key release" event after the key press event. Please note down
this case as well, as it can be worked around in
/lib/udev/keymaps/95-keyboard-force-release.rules .

3. Find out your system vendor and product:

cat /sys/class/dmi/id/sys_vendor
cat /sys/class/dmi/id/product_name

4. Generate a device dump with "udevadm info --export-db > /tmp/udev-db.txt".

6. Send the system vendor/product names, the key mapping from step 2,
and /tmp/udev-db.txt from step 4 to the linux-hotplug@vger.kernel.org mailing
list, so that they can be included in the next release.

For local testing, copy your map file to /lib/udev/keymaps/ with an appropriate
name, and add an appropriate udev rule to /lib/udev/rules.d/95-keymap.rules:

* If you selected an "AT keyboard", add the rule to the section after
'LABEL="keyboard_vendorcheck"'.

* If you selected a "module", add the rule to the top section where the
"ThinkPad Extra Buttons" are.

== Author ==

keymap is written and maintained by Martin Pitt <martin.pitt@ubuntu.com>.

[simosx]

1. Find the keyboard device.

Run /lib/udev/findkeyboards. This should always give you an "AT
keyboard" and possibly a "module". Some laptops (notably Thinkpads, Sonys, and
Acers) have multimedia/function keys on a separate input device instead of the
primary keyboard. The keyboard device should have a name like "input/event3".
In the following commands, the name will be written as "input/eventX" (replace
X with the appropriate number).

2. Find broken scan codes:

sudo /lib/udev/keymap -i input/eventX

Press all multimedia/function keys and check if the key name that gets printed
out is plausible. If it is unknown or wrong, write down the scan code (looks
like "0x1E") and the intended functionality of this key. Look in
/usr/include/linux/input.h for an available KEY_XXXXX constant which most
closely approximates this functionality and write it down as the new key code.

For example, you might press a key labeled "web browser" which currently
produces "unknown". Note down this:

0x1E www # Fn+F2 web browser

Repeat that for all other keys. Write the resulting list into a file. Look at
/lib/udev/keymaps/ for existing key map files and make sure that you use the
same structure.

If the key only ever works once and then your keyboard (or the entire desktop)
gets stuck for a long time, then it is likely that the BIOS fails to send a
corresponding "key release" event after the key press event. Please note down
this case as well, as it can be worked around in
/lib/udev/keymaps/95-keyboard-force-release.rules .

3. Find out your system vendor and product:

cat /sys/class/dmi/id/sys_vendor
cat /sys/class/dmi/id/product_name

4. Generate a device dump with "udevadm info --export-db > /tmp/udev-db.txt".

6. Send the system vendor/product names, the key mapping from step 2,
and /tmp/udev-db.txt from step 4 to the linux-hotplug@vger.kernel.org mailing
list, so that they can be included in the next release.

For local testing, copy your map file to /lib/udev/keymaps/ with an appropriate
name, and add an appropriate udev rule to /lib/udev/rules.d/95-keymap.rules:

* If you selected an "AT keyboard", add the rule to the section after
'LABEL="keyboard_vendorcheck"'.

* If you selected a "module", add the rule to the top section where the
"ThinkPad Extra Buttons" are.

Αυτό είναι το κομμάτι που χρειάζεται να ακολουθήσεις.