Can IBM ThinkPad 600X have color depth 24?

[kjellinux]

I have an IBM ThinkPad 600X running antiX Linux 23.1 full version. I found and installed a lightweight presentation program called sent from suckless.org. The program works the way it's supposed to with one exception - if I try to display an image it returns an error message saying Display color depths < 24 not supported. I have tried the program on another old computer running Debian 12 Linux and on that computer images display without problems. My question now is if it is possible to set color depth to 24 on the IBM ThinkPad 600X, and if so, how to do it?

[SMA]

600x does support 24 bit color on the built in lcd.
Screen mode 118x is 1024x768 24 bit.
What screen mode is actually set, is up to the operating system and the program running.

[kjellinux]

From https://www.antixforum.com/forums/topic ... ost-152967 came the following advice:

"Do you have any display related file in /etc/X11/xorg.conf.d as wildstar84 mentioned? If not, you will have to create one with the correct information. In this reddit topic the explain how to create a file named “99screen.conf”. It could look something like:

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
SubSection "Display"
Modes "1024x768" "800x600"
EndSubSection
EndSection

I created a file with exactly the same name and content in the /etc/X11/xorg.conf.d directory, but when I tried to reboot, the booot ended up with terminal style login prompt. Once logged in, it was possible to start X manually.

Apparently the file should not look quite like this. What should be different? Does it need another name? Should it be in another location?

Grateful for any help.

[axur-delmeria]

I don't have a machine this old, but I'd first run xrandr on a terminal window to see what display resolution and color settings are currently available.

[kjellinux]

I'd first run xrandr on a terminal window to see what display resolution and color settings are currently available.

Code: Select all

xrandr

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768       0.00* 
   800x600        0.00  
   640x480        0.00

[axur-delmeria]

Aagh. My mistake. xrandr is for screen resolution and refresh rates only.

I'll try figuring this out somehow.

[kjellinux]

I'll try figuring this out somehow.

I don't know if it is of any help, but this is what the current section in xorg.conf.in in directory /etc/X11 looks like. I tried changing DefaultColorDepth 16 to DefaultColorDepth 24, but Color Depth stayed at16.

Code: Select all

Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    DefaultColorDepth 16
    
    SubSection "Display"
    Depth 8
    @@MODES@@
    EndSubSection
    SubSection "Display"
    Depth 15
    @@MODES@@
    EndSubSection
    SubSection "Display"
    Depth 16
    @@MODES@@
    EndSubSection
    SubSection "Display"
    Depth 24
    @@MODES@@
    EndSubSection
    SubSection "Display"
    Depth 32
    @@MODES@@
    EndSubSection
    
    # Only the official NVIDIA driver supports twinview
    # these setting are an example
    Option "TwinView" "false"
    Option "SecondMonitorVendorName" "unknown"
    Option "SecondMonitorModelName" "unknown"
    Option "SecondMonitorHorizSync" "30-75"
    Option "SecondMonitorVertRefresh" "55-70"
   #Option "MetaModes" "1024x768, 1024x768"
    Option "TwinViewOrientation" "RightOf"
    Option "ConnectedMonitor" "dfp,dfp"
EndSection

[axur-delmeria]

It's been years since I've had to tangle with xorg.conf, but I remember there's a way to force Xorg to use the neomagic driver.

Does lspci show "NeoMagic MagicGraph256ZX"?

[kjellinux]

Does lspci show "NeoMagic MagicGraph256ZX"?

I couldn't find lspci, so I include the full system information. If I need to look somewhere else, please let me know.

Code: Select all

inxi -zrv7

System:
  Kernel: 5.10.197-antix.1-486-smp arch: i686 bits: 32 compiler: gcc v: 12.2.0
    clocksource: acpi_pm Desktop: IceWM v: 3.4.5 dm: slimski v: 1.5.0
    Distro: antiX-23.1_386-full Arditi del Popolo 21 February 2024 base: Debian
    GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: IBM product: 26453EG v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: IBM model: 26453EG serial: <superuser required> BIOS: IBM
    v: ITET55WW date: 11/30/1999
Battery:
  ID-1: BAT0 charge: 14.1 Wh (100.0%) condition: 14.1/34.6 Wh (40.7%)
    volts: 11.8 min: 10.8 model: IBM Corporation ThinkPad Battery type: Li-ion
    serial: N/A status: N/A
Memory:
  System RAM: total: N/A available: 554.4 MiB used: 405.1 MiB (73.1%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges
    required.
CPU:
  Info: single core model: Pentium III (Coppermine) bits: 32
    arch: P6 III Coppermine rev: 1 cache: 256 KiB note: check
  Speed (MHz): 448 min/max: N/A core: 1: 448 bogomips: 896
  Flags: cmov cpuid cx8 de fpu fxsr mca mce mmx msr mtrr pae pge pse pse36
    sep sse tsc vme
Graphics:
  Device-1: Neomagic NM2360 [MagicMedia 256ZX] vendor: IBM ThinkPad 600X
    driver: N/A bus-ID: 01:00.0 chip-ID: 10c8:0006 class-ID: 0300
  Display: server: X.Org v: 1.21.1.7 driver: X: loaded: vesa dri: swrast
    gpu: N/A display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.67x7.99")
    s-diag: 339mm (13.33")
  Monitor-1: default res: 1024x768 size: N/A modes: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
    x11: drv: swrast inactive: gbm,wayland
  API: OpenGL v: 4.5 vendor: x.org mesa v: 22.3.6 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: llvmpipe (LLVM 15.0.6 128 bits)
    device-ID: ffffffff:ffffffff
Audio:
  Device-1: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio
    Accelerator] vendor: IBM ThinkPad 600X/A20m driver: N/A bus-ID: 00:06.0
    chip-ID: 1013:6003 class-ID: 0401
  API: ALSA v: k5.10.197-antix.1-486-smp status: kernel-api with: apulse
    type: pulse-emulator
  Server-1: PipeWire v: 1.2.1 status: off with: 1: pipewire-pulse
    status: off 2: wireplumber status: off 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel 82371AB/EB/MB PIIX4 ISA type: network bridge driver: N/A
    port: N/A bus-ID: 00:07.0 chip-ID: 8086:7110 class-ID: 0680
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: N/A
    port: N/A bus-ID: 00:07.3 chip-ID: 8086:7113 class-ID: 0680
  Device-3: Realtek RTL8188EUS 802.11n Wireless Network Adapter
    driver: r8188eu type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-1:2
    chip-ID: 0bda:8179 class-ID: 0000 serial: <filter>
  IF: wlan0 state: up mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> scope: link
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 37.26 GiB used: 5.81 GiB (15.6%)
  ID-1: /dev/sda vendor: Hitachi model: DK23EB-40 size: 37.26 GiB
    speed: <unknown> tech: N/A serial: <filter> fw-rev: A0C0 scheme: MBR
  Floppy-1: /dev/fd0
  Optical-1: /dev/sr0 vendor: TOSHIBA model: CD-ROM XM-1702BC rev: 1566
    dev-links: cdrom
  Features: speed: 24 multisession: yes audio: yes dvd: no rw: none
    state: running
Partition:
  ID-1: / size: 36.38 GiB used: 5.81 GiB (16.0%) fs: ext4 dev: /dev/sda1
    label: rootantiX23 uuid: fa18cd2b-e7f1-4bc7-8a39-9d9b4a84153d
Swap:
  ID-1: swap-1 type: file size: 554 MiB used: 5.5 MiB (1.0%) priority: -2
    file: /swap/swap
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s
    lanes: 1 chip-ID: 1d6b:0001 class-ID: 0900
  Device-1: 1-1:2 info: Realtek RTL8188EUS 802.11n Wireless Network Adapter
    type: Network driver: r8188eu interfaces: 1 rev: 2.0 speed: 12 Mb/s lanes: 1
    power: 500mA chip-ID: 0bda:8179 class-ID: 0000 serial: <filter>
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon
    or lm-sensors.
Repos:
  Packages: pm: dpkg pkgs: 1785
  Active apt repos in: /etc/apt/sources.list.d/antix.list
    1: deb [signed-by=/etc/apt/keyrings/antix-archive-keyring.gpg] http://ftp.acc.umu.se/mirror
/mxlinux.org/packages/antix/bookworm bookworm main nonfree nosystemd
  Active apt repos in: /etc/apt/sources.list.d/bookworm-backports.list
    1: deb http://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://ftp.se.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://ftp.se.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/ bookworm-security main contrib non-free non-free-firmware
  No active apt repos in: /etc/apt/sources.list.d/librewolf.list
  No active apt repos in: /etc/apt/sources.list.d/liquorix.list
Info:
  Processes: 111 Uptime: 20m wakeups: 0 Init: SysVinit v: 3.06 runlevel: 2
  default: 2 Compilers: gcc: 12.2.0 alt: 12 Shell: Bash v: 5.2.15
  running-in: roxterm inxi: 3.3.31

[axur-delmeria]

This is the relevant part:

Code: Select all

Graphics:
  Device-1: Neomagic NM2360 [MagicMedia 256ZX] vendor: IBM ThinkPad 600X
    driver: N/A bus-ID: 01:00.0 chip-ID: 10c8:0006 class-ID: 0300
  Display: server: X.Org v: 1.21.1.7 driver: X: loaded: vesa dri: swrast
    gpu: N/A display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.67x7.99")
    s-diag: 339mm (13.33")
  Monitor-1: default res: 1024x768 size: N/A modes: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
    x11: drv: swrast inactive: gbm,wayland
  API: OpenGL v: 4.5 vendor: x.org mesa v: 22.3.6 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: llvmpipe (LLVM 15.0.6 128 bits)
    device-ID: ffffffff:ffffffff

It tells me you're using the vesa driver. IIRC there's a neomagic driver for Xorg. Use your package manager to check if it's installed; if not, search for it. On Debian, it's named xserver-xorg-video-neomagic.

Try this: see if there's a directory named /etc/X11/xorg.conf.d/

If yes, create a text file named /etc/X11/xorg.conf.d/20-neomagic.conf with the following contents:

Code: Select all

Section "Device"
  Identifier "Neomagic"
  Driver "neomagic"
EndSection

Note that you'll need root privileges to create this file.
You may have to tweak the Identifier line (replace the text in quotes), as I don't have a laptop with this GPU to test with.

If you have an existing xorg.conf file, it's best to move it to a different location (like your /home directory) so the two config files don't conflict with each other.

Reboot and hopefully it sorts itself afterwards.

[kjellinux]

The xserver-xorg-video-neomagic is installed.

There is a directory named /etc/X11/xorg.conf.d/

There is an existing xorg.conf file

Code: Select all

pwd
/etc/X11

ls
app-defaults             xinit         xorg.conf.in.old  Xsession.options
default-display-manager  xkb           Xreset            xsm
fluxbox                  Xloadimage    Xreset.d          XvMCConfig
fonts                    xorg.conf     Xresources
icewm                    xorg.conf.d   Xsession
rgb.txt                  xorg.conf.in  Xsession.d

cat xorg.conf
#-----------------------------------------------------------------------------
# xorg.conf file
#
# Generated by make-xorg-conf sometime around Thu Aug 15 15:56:00 CEST 2024
#
# If you want to save customizations, delete the line above or this
# file will get automatically deleted on the next live boot.
#
# Command line parameters: --output=/etc/X11/xorg.conf vesa
#-----------------------------------------------------------------------------

Section "Device"
    Identifier "Device0"
    Driver     "vesa"
EndSection

Should I use "Device0" as Identifier instead of "Neomagic"?

Will the old xorg.conf still be read if I move it to my home directory? Can I just rename it instead?

[axur-delmeria]

The old xorg.conf file won't be read if you move it to your home directory. It's being moved so that it won't conflict with the new one you're making. You could rename it tor xorg.conf.old or something, though personally I create a /home/user/etc folder, and move files and create subdirectories as needed. This way I know exactly where the files I moved there were originally from.

Creating a new, mostly empty xorg.conf file will free the system from constraints that came with the old, system-generated config file.

"Device0" should be fine, if that's how it was detected by make-xorg-conf.

[kjellinux]

@axur-delmeria

I created a /home/kjellinux/etc folder, and moved xorg.conf there. I also edited xorg.conf.in and changed DefaultColorDept from 16 to 24.

Next I created a file named 20-neomagic.conf in directory /etc/X11/xorg.conf.d/ with exactly the content you suggested. I also tried changing Identifier from "Neomagic" to "Device0".

For booth versions of 20-neomagic.conf reboot worked without problems, but likewise, for booth versions xwininfo -root | grep Depth returned Depth: 16.

So, the question now is if the color depth is not set by xorg.conf.in or 20-neomagic.conf, where is it set, and how?

[RealBlackStuff]

Have you ever considered that the LCD itself might only do 16?
Find out exactly what LCD you have.

[axur-delmeria]

Now that's weird. The Neomagic 256ZX has 4MB RAM and has enough RAM to work at 1024x768 at 24-bit color. (1024 x 768 pixels x 3 bytes/pixel = 2,359,296 bytes); I was -expecting the vesa driver being the cause, not being able to properly initialize the graphics.

Unless something is really wrong, like the graphics only seeing half the RAM due to some other issue.
A bit of web searching led me to this page: https://www.cyberciti.biz/faq/howto-fin ... -card-ram/ which presents some methods to check the amount of video RAM detected by Linux:

Method 1: searching Xorg.0.log

Code: Select all

grep -i --color memory /var/log/Xorg.0.log

Method 2: using lspci

Based on your previous posts, we know the bus ID of the Neomagic graphics:

Code: Select all

 Device-1: Neomagic NM2360 [MagicMedia 256ZX] vendor: IBM ThinkPad 600X
    driver: N/A bus-ID: 01:00.0 chip-ID: 10c8:0006 class-ID: 0300

So we feed that to lspci:

Code: Select all

lspci -v -s 01:00.0

If it sees 4MB yet doesn't let you do 24-bit color, I'm out of ideas.

Testing it on DOS and/or Windows would be my next step.

[kjellinux]

The way I interpret the result, there is indeed 4 MB of memory available.

I find it quite confusing that there are so many terms used that could actually refer to the actual display that I'm looking at, screen, device, monitor, etc., and that the display seems to be affected by section Device as well as section Screen and that it is spread over more than one file. I try to find the one line where it is actually determined what the color depth is supposed to be, but I fail to find such a line. The closest so far would be DefaultColorDepth, but changing it from 16 to 24 made no difference.

Code: Select all

grep -i --color memory /var/log/Xorg.0.log

[   105.037] 	MemoryModel: 4
[   105.042] 	MemoryModel: 4
[   105.056] 	MemoryModel: 3
[   105.060] 	MemoryModel: 4
[   105.063] 	MemoryModel: 3
[   105.068] 	MemoryModel: 4
[   105.073] 	MemoryModel: 4
[   105.078] 	MemoryModel: 6
[   105.092] 	MemoryModel: 6
[   105.096] 	MemoryModel: 6
[   105.100] 	MemoryModel: 6
[   105.105] 	MemoryModel: 6
[   105.110] 	MemoryModel: 6
[   105.115] 	MemoryModel: 6
[   105.120] 	MemoryModel: 6
[   105.125] 	MemoryModel: 6
[   105.129] 	MemoryModel: 6
[   105.134] 	MemoryModel: 6
[   105.139] 	MemoryModel: 6
[   105.144] 	MemoryModel: 6
[   105.149] 	MemoryModel: 4
[   105.163] 	MemoryModel: 6
[   105.167] 	MemoryModel: 4
[   105.171] 	MemoryModel: 6
[   105.176] 	MemoryModel: 4
[   105.181] 	MemoryModel: 6
[   105.182] (II) VESA(0): Total Memory: 63 64KB banks (4032kB)

lspci -v -s 01:00.0

01:00.0 VGA compatible controller: Neomagic Corporation NM2360 [MagicMedia 256ZX] (prog-if 00 [VGA controller])
	Subsystem: IBM ThinkPad 600X
	Flags: bus master, medium devsel, latency 128, IRQ 11
	Memory at e0000000 (32-bit, prefetchable) [size=32M]
	Memory at 70000000 (32-bit, non-prefetchable) [size=4M]
	Memory at 70400000 (32-bit, non-prefetchable) [size=1M]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel modules: neofb

[axur-delmeria]

I'm officially out of ideas.

[RealBlackStuff]

I'll ask this again, exactly WHICH LCD is in that machine?
It may not be capable of colour depth 24.

[kjellinux]

exactly WHICH LCD is in that machine?
It may not be capable of colour depth 24.

How can I find out? I have tried Google, but the specifications I found don't go into such great detail.

[RealBlackStuff]

Use a program like HWINFO or lshw or inxi.
Or take the lid apart and look on the back of the LCD.

[kjellinux]

I'm officially out of ideas.

while searching the web I came across the command xdpyinfo. When I ran it, the initial part was as shown below. In particular, under number of supported pixmap formats, I found

Code: Select all

depth 24, bits_per_pixel 32, scanline_pad 32

If i understand this right, depth 24 uses 32 bits per pixel. If that is correct, then 4 MB would not be sufficient. Am I completely wrong here?

Code: Select all

xdpyinfo

name of display:    :0.0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    12101007
X.Org version: 1.21.1.7
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    7
C:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  window 0x600004, revert to None
number of extensions:    27

[kjellinux]

Use a program like HWINFO or lshw or inxi.

I tried HWINFO and it produced massive amounts of information. What would I be looking for?

[rumbero]

I tried HWINFO and it produced massive amounts of information. What would I be looking for?

How about being curious and examining the output for relevant information? It's your hardware and your research.

Keywords to search for would be "monitor", "LCD", "display", etc.

As an example, on a T480, searching the hwinfo output for "LCD" shows the details for "Model", "Vendor", "Year of Manufacture", and much more.

[axur-delmeria]

while searching the web I came across the command xdpyinfo. When I ran it, the initial part was as shown below. In particular, under number of supported pixmap formats, I found

Code: Select all

depth 24, bits_per_pixel 32, scanline_pad 32

If i understand this right, depth 24 uses 32 bits per pixel. If that is correct, then 4 MB would not be sufficient. Am I completely wrong here?

1024 * 768 * 32 bits per pixel / 8 bits per byte = 3,145,728 bytes, which is still below 4MB.

[kjellinux]

It's been som time since I last posted. This does not in any way mean that I've been inactive. I have sought help in 4 different forums.

antiX-forum
thinkpads.com Support Community
LinuxQuestions.org
Q4OS Forum

I have tried countless ways to set Color Depth to 24, but so far without success. I have tried another distribution, Q4OS, I have created a large number of configuration files with varying content and different names placed in different directories. I have tried countless search phrases on Google to find the right information. I have read countless articles.

One article in particular, How to set desktop color depth?, has convinced me that it should be possible to set Color Depth to 24. Using xdpyinfo produced the result below (I left out a large number of repetitions at the end). In particular, i think the following part suggests that it should be possible.

Code: Select all

supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32

One possible obstacle could be limitations in the hardware. According to Wikipedia on IBM ThinkPad 600 the IBM ThinkPad 600X Video Controller has 4 MB video memory. Even if, as the output from xdpyinfo suggests, Color Depth 24 uses 32 bits per pixel, the video memory should be sufficient (1024 * 768 * 32 bits per pixel / 8 bits per byte = 3,145,728 bytes, which is still below 4MB). It's been suggested that the there could be limitations in the actual LCD. I have run hwinfo with various hardware item options, including none at all, and searched through the output using grep with various options and search terms like "monitor", "LCD", "display", etc. without finding any information on the LCD.

Regardless of possible limitations of the hardware, the present value of the Color Depth, 16, must be set in some way, at som point in the start up process. There must be a line of code, a command, or something else, somewhere, in some file, in some directory where it takes place. I have made countless attempts to find this point, but so far without success. It can't happen all by itself, so the point must exist. Unfortunately, my lack of skills have prevented me from finding it so far. I find it very confusing that there are so many terms used that can refer to the actual display that I look at when I'm using the computer.

My hope now is that someone much more skilled than me will read the information I've put togeter and realize that "I know that" and share that knowledge.


Beginning of output from xdpyinfo:

Code: Select all

xdpyinfo

name of display:    :0.0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    12101007
X.Org version: 1.21.1.7
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    7
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  window 0x2200004, revert to None
number of extensions:    27
    BIG-REQUESTS
    Composite
    DAMAGE
    DOUBLE-BUFFER
    DPMS
    DRI2
    GLX
    Generic Event Extension
    MIT-SCREEN-SAVER
    MIT-SHM
    Present
    RANDR
    RECORD
    RENDER
    SECURITY
    SHAPE
    SYNC
    X-Resource
    XC-MISC
    XFIXES
    XFree86-DGA
    XFree86-VidModeExtension
    XINERAMA
    XInputExtension
    XKEYBOARD
    XTEST
    XVideo
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    1024x768 pixels (271x203 millimeters)
  resolution:    96x96 dots per inch
  depths (7):    16, 1, 4, 8, 15, 24, 32
  root window id:    0x400
  depth of root window:    16 planes
  number of colormaps:    minimum 1, maximum 1
  default colormap:    0x20
  default number of colormap cells:    64
  preallocated pixels:    black 0, white 65535
  options:    backing-store WHEN MAPPED, save-unders NO
  largest cursor:    1024x768
  current input event mask:    0xfa200f
    KeyPressMask             KeyReleaseMask           ButtonPressMask          
    ButtonReleaseMask        ButtonMotionMask         StructureNotifyMask      
    SubstructureNotifyMask   SubstructureRedirectMask FocusChangeMask          
    PropertyChangeMask       ColormapChangeMask       
  number of visuals:    120
  default visual id:  0x21
  visual:
    visual id:    0x21
    class:    TrueColor
    depth:    16 planes
    available colormap entries:    64 per subfield
    red, green, blue masks:    0xf800, 0x7e0, 0x1f
    significant bits in color specification:    6 bits
  visual:
    visual id:    0x389
    class:    TrueColor
    depth:    16 planes
    available colormap entries:    64 per subfield
    red, green, blue masks:    0xf800, 0x7e0, 0x1f
    significant bits in color specification:    6 bits
...

[RealBlackStuff]

Unless you come up with the exact make and model of the LCD in your laptop, this topic will be CLOSED.
You have 24 hours.

[kjellinux]

Unless you come up with the exact make and model of the LCD in your laptop, this topic will be CLOSED.
You have 24 hours.

The irony! I have long since lost count how many different search phrases I have used to try to find the information about my LCD. Only when I use more or less exactly your words, "how do i find the exact make and model of the LCD in my laptop", do I find How do I find out monitor make / model? from Ask Ubuntu.

The first suggestion is to install HardInfo application and and see info via GUI.

Code: Select all

-Display-
Resolution		: 1024x768 pixels
Vendor		: The X.Org Foundation
Version		: 1.21.1.7
Current Display Name		: :0.0
-Monitors-
Monitor 0		: 1024x768 pixels
-OpenGL-
Vendor		: Mesa/X.org
Renderer		: llvmpipe (LLVM 15.0.6, 128 bits)
Version		: 4.5 (Compatibility Profile) Mesa 22.3.6
Direct Rendering		: Yes

Somehow, this doesn't appear to be the LCD.

The second suggestion was "Try running lspci. Your monitor should be listed there somewhere.

Code: Select all

lspci

00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:03.0 Communication controller: LSI Corporation L56xM+S [Mars-2] WinModem 56k (rev 01)
00:06.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
01:00.0 VGA compatible controller: Neomagic Corporation NM2360 [MagicMedia 256ZX]

I'm not sure I agree that my monitor is "listed there somewhere".

The third suggestion.

Code: Select all

sudo get-edid | parse-edid

This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Looks like no busses have an EDID. Sorry!
Attempting to use the classical VBE interface

	Performing real mode VBE call
	Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
	Function supported
	Call successful

	VBE version 200
	VBE string at 0x11120 "MagicMedia 256ZX  48K"

VBE/DDC service about to be called
	Report DDC capabilities

	Performing real mode VBE call
	Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
	Function supported
	Call successful

	Monitor and video card combination does not support DDC1 transfers
	Monitor and video card combination does not support DDC2 transfers
	0 seconds per 128 byte EDID block transfer
	Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
	Read EDID

	Performing real mode VBE call
	Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
	Function supported
	Call failed

The EDID data should not be trusted as the VBE call failed
Error: output block unchanged
I'm sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.
Partial Read... Try again

Apart from "MagicMedia 256ZX 48K", I don't know if there's anything useful.

The fourth suggestion.

Code: Select all

xrandr -q --verbose | less

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 (0x410) normal (normal) 0mm x 0mm
        Identifier: 0x40f
        Timestamp:  2977352
        Subpixel:   unknown
        Clones:    
        CRTC:       0
        CRTCs:      0
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter: 
        non-desktop: 0 
                supported: 0, 1
  1024x768 (0x410)  0.000MHz *current
        h: width  1024 start    0 end    0 total 1024 skew    0 clock   0.00KHz
        v: height  768 start    0 end    0 total  768           clock   0.00Hz
  800x600 (0x411)  0.000MHz
        h: width   800 start    0 end    0 total  800 skew    0 clock   0.00KHz
        v: height  600 start    0 end    0 total  600           clock   0.00Hz
  640x480 (0x412)  0.000MHz
        h: width   640 start    0 end    0 total  640 skew    0 clock   0.00KHz
        v: height  480 start    0 end    0 total  480           clock   0.00Hz
(END)

No EDID string to decode. No LCD hiding in there.

The fifth suggestion. Relevant part of the output.

Code: Select all

*-display UNCLAIMED
                description: VGA compatible controller
                product: NM2360 [MagicMedia 256ZX]
                vendor: Neomagic Corporation
                physical id: 0
                bus info: pci@0000:01:00.0
                version: 00
                width: 32 bits
                clock: 33MHz
                capabilities: pm vga_controller bus_master cap_list
                configuration: latency=128 maxlatency=255 mingnt=16
                resources: memory:e0000000-e1ffffff memory:70000000-703fffff memory:70400000-704fffff

Good information, only, if I understand right, this is the chip that controls the LCD, not the actual LCD.

The sixth suggestion.

Code: Select all

for file in `ls -1 /sys/class/drm/*/edid`; do text=$(tr -d '\0' <"$file"); if [ -n "$text" ]; 
then edid-decode "$file" | grep -e Manufacturer: -e Product; sleep 0.0001; fi done

ls: can not access '/sys/class/drm/*/edid': File or catalogue does not exist

No LCD there either.

The seventh suggestion.

Produced a massive output, much too large to copy here. I searched for LCD, monitor, display, screen, vendor, manufacturer, supplier. Again information about the control chip, but no LCD.

I'm not about to take the screen apart. I fear if I do, I will not be able to put it back together in working condition.

So, I guess the big bad moderator will just have to close the thread down...

[axur-delmeria]

I'm just wondering: Have you tried Windows on that laptop? If you do get 24-bit colors on Windows, then it's a Linux driver issue (AFAIK the neomagic driver hasn't been worked on for years).

[RealBlackStuff]

I'm not about to take the screen apart.

None of your "searches" has even come up with the LCD manufacturer's name!
Have you ever looked in the HMM of the 600X?
In there are 2 LCDs listed: (Samsung) 05K9546 and (LG) 05K9547.
A simple search on Google will find:
05K9546 = Samsung LT133X8-122, which has 262k colours (6-bit RGB = depth 18)
05K9547 = LG LP133X5-A2IB, which has 262k colours (6-bit RGB = depth 18)
Which means, neither of those screens has enough colours (16.7M) to have (8-bit RGB = depth 24).

So unless your 600X has a different LCD, the answer to your question is: NO.

You could have saved yourself (and us) a whole lot of hassle...

[axur-delmeria]

05K9546 = Samsung LT133X8-122, which has 262k colours (6-bit RGB = depth 18)
05K9547 = LG LP133X5-A2IB, which has 262k colours (6-bit RGB = depth 18)
Which means, neither of those screens has enough colours (16.7M) to have (8-bit RGB = depth 24).

Are you sure about that? Because I just checked my X61, and it has an LTN121XJ-L07, which only supports 262K colors according to the datasheet. But it can be set to 24- or 32-bit color just fine. I know it has much more video RAM (shared with system RAM), but it seems that the native color depth of the panel is not directly equivalent to what can be set in the operating system.

In any case, I don't think resolving this Neomagic issue will progress any further without an "out of the box" (or more like "out of Linux") approach. LCDs of this vintage generally don't have EDID (heck, not even the much later T43 had them), so that's a dead end. The X.org neomagic driver hasn't been seriously looked at in at least a decade, so we don't know if it's still 100% good.

If DOS or Windows allows 1024x768 24/32-bit but Linux won't, it's obviously a software/driver issue. But if all are stuck at 16-bit, then it's due to hardware limitations.