Re: [ibm-acpi-devel] Some information about setting brightness on X61 Tablet with 16 levels.
On Wed, 2007-09-12 at 18:00 +0200, Maik Broemme wrote:
> Hi,
>
> Maik Broemme <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Maik Broemme <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > i have a couple of small questions. :) I own an IBM ThinkPad X40 and a
> > > Lenovo ThinkPad X61 Tablet and just hacked somewhere around in the
> > > 'thinkpad-acpi-0.16-20070904' sources.
> > >
> > > I started my work on adding support for the brightness setup which has
> > > 16 level on the newer X61/X61s and X61 Tablet laptops. Well my problem
> > > is (or i am to stupid to understand) that setting the brightness level
> > > with TP_CMOS_BRIGHTNESS_UP did not set it until level 16. Is this a
> > > limitation of the thinkpad-acpi itself or somewhere inside the NVRAM?
> > >
> > > As notice: With brightness mode 1 (which reads data from EC via
> > > acpi_ec_read) the setting of any brightness level is not working.
> > >
> > > Maybe someone can give me a hint where i can start to track this issue
> > > and how to solve it. :)
> > >
> >
> > okay some other information, i am still able to set at least 15 of the
> > 16 levels via '/proc/acpi/video/VID/LCD0/brightness' It shows:
> >
> > [EMAIL PROTECTED]:~# cat /proc/acpi/video/VID/LCD0/brightness
> > levels: 100 100 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 100
> > current: 90
> >
> > If i count all values (and the 100 only one time) it are 16 levels.
> > Well the level 100 i can not set (kernel is stock 2.6.22.6) Well this
> > looks like an ACPI bug for me, or a broken firmware. If do the
> > following:
> >
> > [EMAIL PROTECTED]:~# for i in 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90
> > ; do sleep 1s ; echo "${i}" > /proc/acpi/video/VID/LCD0/brightness ; done
> >
> > i can set at least 15 brightness level. I think the best solution would
> > be to use the ACPI video driver to set the brightness, did anyone agree
> > or disagree? :)
> >
> > If i am correct thinkpad-acpi should trac the keypress event and then
> > trigger some acpi function to set the brightness level.
> >
>
> Sorry a last thing which should be mentioned. :) The ACPI video driver
> correctly updates the CMOS NVRAM, but thinkpad-acpi can only handle
> values until acpi-video value 55, for example:
>
> [EMAIL PROTECTED]:~# echo 20 > /proc/acpi/video/VID/LCD0/brightness
> [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> level: 0
> [EMAIL PROTECTED]:~# echo 25 > /proc/acpi/video/VID/LCD0/brightness
> [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> level: 1
> [EMAIL PROTECTED]:~# echo 30 > /proc/acpi/video/VID/LCD0/brightness
> [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> level: 2
> [EMAIL PROTECTED]:~# echo 35 > /proc/acpi/video/VID/LCD0/brightness
> [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> level: 3
> [EMAIL PROTECTED]:~# echo 40 > /proc/acpi/video/VID/LCD0/brightness
> [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> level: 4
> [EMAIL PROTECTED]:~# echo 45 > /proc/acpi/video/VID/LCD0/brightness
> [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> level: 5
> [EMAIL PROTECTED]:~# echo 50 > /proc/acpi/video/VID/LCD0/brightness
> [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> level: 6
> [EMAIL PROTECTED]:~# echo 55 > /proc/acpi/video/VID/LCD0/brightness
> [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> level: 7
> [EMAIL PROTECTED]:~# echo 60 > /proc/acpi/video/VID/LCD0/brightness
> [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> level: 0
> [EMAIL PROTECTED]:~# echo 65 > /proc/acpi/video/VID/LCD0/brightness
> [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> level: 1
But brightness is set correctly (not the value but the background
brightness itself)?
This is a thinkpad_acpi bug and the fact that it can only cope with 8
brightness levels.
I have two ideas on how the thinkpad_acpi driver could handle these
machines:
- set brightness levels from current up to max (until it does not
change anymore) -> disadvantage: unspecified values are written
and a SMI with a undefined value will be fired (e.g. a value of
8 for < X61/T61 and a value of 16 for X61/T61...)
- Use dmi decode again and set max brightness levels to 0-15 in
X61/T61/.. case.
Both are really ugly workarounds and should only be added if there is no
time for doing it right for the next bigger kernel release.
Doing it right is IMO, ripping out brightness control for *Lenovo*
ThinkPads only and let the video module do brightness control instead.
This should also be done for the video ThinkPad extensions or the
ThinkPad video extensions might interfere with the video driver.
Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vg
Re: [ibm-acpi-devel] Some information about setting brightness on X61 Tablet with 16 levels.
Hi,
Thomas Renninger <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-09-12 at 18:00 +0200, Maik Broemme wrote:
> > Hi,
> >
> > Maik Broemme <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > Maik Broemme <[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > >
> > > > i have a couple of small questions. :) I own an IBM ThinkPad X40 and a
> > > > Lenovo ThinkPad X61 Tablet and just hacked somewhere around in the
> > > > 'thinkpad-acpi-0.16-20070904' sources.
> > > >
> > > > I started my work on adding support for the brightness setup which has
> > > > 16 level on the newer X61/X61s and X61 Tablet laptops. Well my problem
> > > > is (or i am to stupid to understand) that setting the brightness level
> > > > with TP_CMOS_BRIGHTNESS_UP did not set it until level 16. Is this a
> > > > limitation of the thinkpad-acpi itself or somewhere inside the NVRAM?
> > > >
> > > > As notice: With brightness mode 1 (which reads data from EC via
> > > > acpi_ec_read) the setting of any brightness level is not working.
> > > >
> > > > Maybe someone can give me a hint where i can start to track this issue
> > > > and how to solve it. :)
> > > >
> > >
> > > okay some other information, i am still able to set at least 15 of the
> > > 16 levels via '/proc/acpi/video/VID/LCD0/brightness' It shows:
> > >
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/video/VID/LCD0/brightness
> > > levels: 100 100 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 100
> > > current: 90
> > >
> > > If i count all values (and the 100 only one time) it are 16 levels.
> > > Well the level 100 i can not set (kernel is stock 2.6.22.6) Well this
> > > looks like an ACPI bug for me, or a broken firmware. If do the
> > > following:
> > >
> > > [EMAIL PROTECTED]:~# for i in 20 25 30 35 40 45 50 55 60 65 70 75 80 85
> > > 90 ; do sleep 1s ; echo "${i}" > /proc/acpi/video/VID/LCD0/brightness ;
> > > done
> > >
> > > i can set at least 15 brightness level. I think the best solution would
> > > be to use the ACPI video driver to set the brightness, did anyone agree
> > > or disagree? :)
> > >
> > > If i am correct thinkpad-acpi should trac the keypress event and then
> > > trigger some acpi function to set the brightness level.
> > >
> >
> > Sorry a last thing which should be mentioned. :) The ACPI video driver
> > correctly updates the CMOS NVRAM, but thinkpad-acpi can only handle
> > values until acpi-video value 55, for example:
> >
> > [EMAIL PROTECTED]:~# echo 20 > /proc/acpi/video/VID/LCD0/brightness
> > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > level: 0
> > [EMAIL PROTECTED]:~# echo 25 > /proc/acpi/video/VID/LCD0/brightness
> > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > level: 1
> > [EMAIL PROTECTED]:~# echo 30 > /proc/acpi/video/VID/LCD0/brightness
> > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > level: 2
> > [EMAIL PROTECTED]:~# echo 35 > /proc/acpi/video/VID/LCD0/brightness
> > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > level: 3
> > [EMAIL PROTECTED]:~# echo 40 > /proc/acpi/video/VID/LCD0/brightness
> > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > level: 4
> > [EMAIL PROTECTED]:~# echo 45 > /proc/acpi/video/VID/LCD0/brightness
> > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > level: 5
> > [EMAIL PROTECTED]:~# echo 50 > /proc/acpi/video/VID/LCD0/brightness
> > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > level: 6
> > [EMAIL PROTECTED]:~# echo 55 > /proc/acpi/video/VID/LCD0/brightness
> > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > level: 7
> > [EMAIL PROTECTED]:~# echo 60 > /proc/acpi/video/VID/LCD0/brightness
> > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > level: 0
> > [EMAIL PROTECTED]:~# echo 65 > /proc/acpi/video/VID/LCD0/brightness
> > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > level: 1
>
> But brightness is set correctly (not the value but the background
> brightness itself)?
> This is a thinkpad_acpi bug and the fact that it can only cope with 8
> brightness levels.
>
The brightness is set correctly, i can set it in 16 steps. Anyway, the
/proc stuff from acpi video has still a bug with setting 100% brightness.
But i did not take a deeper look into this, because the sysfs stuff is
fully working and /proc is deprecated:
[EMAIL PROTECTED]:~$ cat /sys/class/backlight/acpi_video1/actual_brightness
20
[EMAIL PROTECTED]:~$ cat /sys/class/backlight/acpi_video1/max_brightness
100
There is some thing missing in the sysfs part, there is no export for the
valied values which can be used, actually on brightness up i make +5 and on
brightness down i make -5
The acpi video itself is not setting the backlight of the LCD (is this a bug
or a wanted behaviour, if it is normal can somebody explaing me why?) You
still ne
Re: [ibm-acpi-devel] Some information about setting brightness on X61 Tablet with 16 levels.
On Mon, 2007-09-17 at 17:12 +0200, Maik Broemme wrote:
> Hi,
>
> Thomas Renninger <[EMAIL PROTECTED]> wrote:
> > On Wed, 2007-09-12 at 18:00 +0200, Maik Broemme wrote:
> > > Hi,
> > >
> > > Maik Broemme <[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > >
> > > > Maik Broemme <[EMAIL PROTECTED]> wrote:
> > > > > Hi,
> > > > >
> > > > > i have a couple of small questions. :) I own an IBM ThinkPad X40 and a
> > > > > Lenovo ThinkPad X61 Tablet and just hacked somewhere around in the
> > > > > 'thinkpad-acpi-0.16-20070904' sources.
> > > > >
> > > > > I started my work on adding support for the brightness setup which has
> > > > > 16 level on the newer X61/X61s and X61 Tablet laptops. Well my problem
> > > > > is (or i am to stupid to understand) that setting the brightness level
> > > > > with TP_CMOS_BRIGHTNESS_UP did not set it until level 16. Is this a
> > > > > limitation of the thinkpad-acpi itself or somewhere inside the NVRAM?
> > > > >
> > > > > As notice: With brightness mode 1 (which reads data from EC via
> > > > > acpi_ec_read) the setting of any brightness level is not working.
> > > > >
> > > > > Maybe someone can give me a hint where i can start to track this issue
> > > > > and how to solve it. :)
> > > > >
> > > >
> > > > okay some other information, i am still able to set at least 15 of the
> > > > 16 levels via '/proc/acpi/video/VID/LCD0/brightness' It shows:
> > > >
> > > > [EMAIL PROTECTED]:~# cat /proc/acpi/video/VID/LCD0/brightness
> > > > levels: 100 100 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 100
> > > > current: 90
> > > >
> > > > If i count all values (and the 100 only one time) it are 16 levels.
> > > > Well the level 100 i can not set (kernel is stock 2.6.22.6) Well this
> > > > looks like an ACPI bug for me, or a broken firmware. If do the
> > > > following:
> > > >
> > > > [EMAIL PROTECTED]:~# for i in 20 25 30 35 40 45 50 55 60 65 70 75 80 85
> > > > 90 ; do sleep 1s ; echo "${i}" > /proc/acpi/video/VID/LCD0/brightness ;
> > > > done
> > > >
> > > > i can set at least 15 brightness level. I think the best solution would
> > > > be to use the ACPI video driver to set the brightness, did anyone agree
> > > > or disagree? :)
> > > >
> > > > If i am correct thinkpad-acpi should trac the keypress event and then
> > > > trigger some acpi function to set the brightness level.
> > > >
> > >
> > > Sorry a last thing which should be mentioned. :) The ACPI video driver
> > > correctly updates the CMOS NVRAM, but thinkpad-acpi can only handle
> > > values until acpi-video value 55, for example:
> > >
> > > [EMAIL PROTECTED]:~# echo 20 > /proc/acpi/video/VID/LCD0/brightness
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > > level: 0
> > > [EMAIL PROTECTED]:~# echo 25 > /proc/acpi/video/VID/LCD0/brightness
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > > level: 1
> > > [EMAIL PROTECTED]:~# echo 30 > /proc/acpi/video/VID/LCD0/brightness
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > > level: 2
> > > [EMAIL PROTECTED]:~# echo 35 > /proc/acpi/video/VID/LCD0/brightness
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > > level: 3
> > > [EMAIL PROTECTED]:~# echo 40 > /proc/acpi/video/VID/LCD0/brightness
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > > level: 4
> > > [EMAIL PROTECTED]:~# echo 45 > /proc/acpi/video/VID/LCD0/brightness
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > > level: 5
> > > [EMAIL PROTECTED]:~# echo 50 > /proc/acpi/video/VID/LCD0/brightness
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > > level: 6
> > > [EMAIL PROTECTED]:~# echo 55 > /proc/acpi/video/VID/LCD0/brightness
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > > level: 7
> > > [EMAIL PROTECTED]:~# echo 60 > /proc/acpi/video/VID/LCD0/brightness
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > > level: 0
> > > [EMAIL PROTECTED]:~# echo 65 > /proc/acpi/video/VID/LCD0/brightness
> > > [EMAIL PROTECTED]:~# cat /proc/acpi/ibm/brightness | grep level:
> > > level: 1
> >
> > But brightness is set correctly (not the value but the background
> > brightness itself)?
> > This is a thinkpad_acpi bug and the fact that it can only cope with 8
> > brightness levels.
> >
>
> The brightness is set correctly, i can set it in 16 steps. Anyway, the
> /proc stuff from acpi video has still a bug with setting 100% brightness.
> But i did not take a deeper look into this, because the sysfs stuff is
> fully working and /proc is deprecated:
Makes sense. The video module hopefully is used more (or at all...) in
future, but looking at /proc does not make much sense as the video
module has not been used much or even at all since now.
>
> [EMAIL PROTECTED]:~$ cat /sys/class/backlight/acp
[PATCH] sony-laptop/thinkpad-acpi: fix build error
sony-laptop and thinkpad-acpi make use of input-core functions. Hence you get link errors if those drivers are built but CONFIG_INPUT is not set. Attached patch fixes this minor issue. Regards, Andreas -- Build errors if CONFIG_SONY_LAPTOP && !INPUT or if CONFIG_THINKPAD_ACPI && !INPUT: LD vmlinux ... drivers/built-in.o: In function `sony_laptop_remove_input': sony-laptop.c:(.text+0x768fb): undefined reference to `input_unregister_device' ... drivers/built-in.o: In function `thinkpad_acpi_module_exit': thinkpad_acpi.c:(.text+0x78c1b): undefined reference to `input_free_device' ... I suggest to auto-select CONFIG_INPUT for both drivers. Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]> --- drivers/misc/Kconfig |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig index 73e248f..c077df8 100644 --- a/drivers/misc/Kconfig +++ b/drivers/misc/Kconfig @@ -134,6 +134,7 @@ config SONY_LAPTOP tristate "Sony Laptop Extras" depends on X86 && ACPI select BACKLIGHT_CLASS_DEVICE + select INPUT ---help--- This mini-driver drives the SNC and SPIC devices present in the ACPI BIOS of the Sony Vaio laptops. @@ -156,6 +157,7 @@ config THINKPAD_ACPI select BACKLIGHT_CLASS_DEVICE select HWMON select NVRAM + select INPUT ---help--- This is a driver for the IBM and Lenovo ThinkPad laptops. It adds support for Fn-Fx key combinations, Bluetooth control, video -- 1.5.3 - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] acpi_video: kernel build error if !INPUT
Commit e9dab1960ac9746fa34eff726b81635147615a79 exports ACPI video hotkey events via input layer. But this breaks kernel build if ACPI_VIDEO && !INPUT: LD .tmp_vmlinux1 drivers/built-in.o: In function `acpi_video_bus_remove': drivers/acpi/video.c:2007: undefined reference to `input_unregister_device' ... Add dependency to INPUT for ACPI_VIDEO to prevent this error. Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]> --- drivers/acpi/Kconfig |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index 4875f01..9685b75 100644 --- a/drivers/acpi/Kconfig +++ b/drivers/acpi/Kconfig @@ -117,6 +117,7 @@ config ACPI_BUTTON config ACPI_VIDEO tristate "Video" depends on X86 && BACKLIGHT_CLASS_DEVICE && VIDEO_OUTPUT_CONTROL + depends on INPUT help This driver implement the ACPI Extensions For Display Adapters for integrated graphics devices on motherboard, as specified in -- 1.5.3 - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] sony-laptop/thinkpad-acpi: fix build error
On Mon, 17 Sep 2007, Andreas Herrmann wrote: > sony-laptop and thinkpad-acpi make use of input-core functions. > Hence you get link errors if those drivers are built but CONFIG_INPUT > is not set. Attached patch fixes this minor issue. [...] > @@ -156,6 +157,7 @@ config THINKPAD_ACPI > select BACKLIGHT_CLASS_DEVICE > select HWMON > select NVRAM > + select INPUT > ---help--- > This is a driver for the IBM and Lenovo ThinkPad laptops. It adds > support for Fn-Fx key combinations, Bluetooth control, video Acked-by: Henrique de Moraes Holschuh <[EMAIL PROTECTED]> -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
git-acpi breaks resume-from-ram on the Vaio
It suspends OK, then during resume it gets partway through it, then everything just stops. Would prefer not to have to bisect this one - I've done enough bisecting this week to last a lifetime, and bisecting git-acpi is painful due to build bustage at various points (cpuidle). - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: git-acpi breaks resume-from-ram on the Vaio
On Mon, 17 Sep 2007 21:12:13 -0700 Andrew Morton <[EMAIL PROTECTED]> wrote: > > It suspends OK, then during resume it gets partway through it, then everything > just stops. > > Would prefer not to have to bisect this one - I've done enough bisecting this > week to last a lifetime, and bisecting git-acpi is painful due to build > bustage > at various points (cpuidle). And git-acpi breaks suspend-to-disk as well. It gets up to "Suspending console(s)" and then the cursor stops blinking at it wedges up. - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Please send dmidecode
Dear maintainers, Looking through the dmesg output I found a message asking me to send the dmidecode output to this address. I am not sure whether the ACPI on this laptop (a Dell Inspiron 1501) is causing trouble because I have installed the testing version of Ubuntu Gutsy, but it has acted up in the past, giving loads of [ 767.90] APIC error on CPU1: 40(40) messages. Hope this helps, Kind regards, MHB # dmidecode 2.9 SMBIOS 2.4 present. 37 structures occupying 1297 bytes. Table at 0x000F0880. Handle 0xDA00, DMI type 218, 131 bytes OEM-specific Type Header and Data: DA 83 00 DA B0 00 92 1B 07 02 00 7D 00 00 00 00 00 80 01 16 00 01 00 7F 01 16 00 00 00 75 01 75 01 01 00 76 01 76 01 01 00 2E 00 25 00 00 00 6E 00 25 00 01 00 2D 00 25 00 02 00 8A 01 48 00 01 00 89 01 48 00 00 00 9B 00 23 00 01 00 9C 00 23 00 00 00 14 01 46 00 00 00 15 01 46 00 01 00 16 01 46 00 02 00 94 01 47 00 01 00 93 01 47 00 00 00 EA 00 67 00 01 00 EB 00 67 00 00 00 FF FF 00 00 00 00 Handle 0x0001, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 2.1.0 Release Date: 12/18/2006 Address: 0xE5BB0 Runtime Size: 107600 bytes ROM Size: 1024 kB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/360 KB floppy services are supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 KB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported LS-120 boot is supported ATAPI Zip drive boot is supported BIOS boot specification is supported Targeted content distribution is supported Handle 0x0002, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: Inspiron 1501 Version: Not Specified Serial Number: HWYGR2J UUID: 44454C4C-5700-1059-8047-C8C04F52324A Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0003, DMI type 2, 8 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0UW744 Version: Serial Number: .HWYGR2J.CN486437125049. Handle 0x0004, DMI type 3, 17 bytes Chassis Information Manufacturer: Dell Inc. Type: Portable Lock: Not Present Version: Not Specified Serial Number: HWYGR2J Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x1234 Handle 0x0005, DMI type 4, 35 bytes Processor Information Socket Designation: Socket M2/S1G1 Type: Central Processor Family: Turion 64 Manufacturer: AMD ID: 82 0F 04 00 FF FB 8B 17 Signature: Family 15, Model 72, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) HTT (Hyper-threading technology) Version: Engineering Sample Voltage: 1.4 V External Clock: 200 MHz Max Speed: 4000 MHz Current Spe
