The Official Release of Lucid 5.25 (Lucid Five Twenty-Five)

[01micko]

James C

Yours looks identical to mine, in which I have no issues apart from small console fonts outside of X, but that could be because it doesn't know how to handle the newish widescreen.

Seems there are many different versions of 82845G!

[James C]

Curiouser and Curiouser.

01micko also has the same basic chipset as rerwin and James C.

James C and Cowboy, rerwin requests that you send the output of the command

Code: Select all

lspci -nn

That gives the device id#'s which might help. Thanks.

# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] (rev 01)
00:02.0 VGA compatible controller [0300]: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 01)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 81)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge [8086:24c0] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801DB (ICH4) IDE Controller [8086:24cb] (rev 01)
00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller [8086:24c3] (rev 01)
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 01)
01:0c.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet Controller [8086:100e] (rev 02)
#

[rerwin]

Thanks to all of you for jumping into this discussion of the 845 black screen issue. As a way to further sort out a way to determine which flavor of the card has the problem, could some of you with this card check for more info, by running this command:

grep '0x2562' /tmp/udevtrace.log

My NetVista has:

Code: Select all

add_0000:00:02.0_pci_0x8086_0x2562_pci:v00008086d00002562sv00001014sd00000267bc03sc00i00

I am hoping the ones that work have something different in the pci: modalias string. Thanks.
Richard

A thought I just had: When I looked at my BIOS setup yesterday, I noticed that the VGA aperture is set to 64, which seems small. I think it can go to 256, but that would use up half of my RAM - or is that KB, not MB. Could that be a factor in the black-screen issue? I will test. R

[01micko]

Hi Richard

Code: Select all

 grep '0x2562' /tmp/udevtrace.log
add_0000:00:02.0_pci_0x8086_0x2562_pci:v00008086d00002562sv00000E11sd000000BAbc03sc00i00
remove_i2c-2_i2c_0x8086_0x2562_pci:v00008086d00002562sv00000E11sd000000BAbc03sc00i00
remove_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00000E11sd000000BAbc03sc00i00
add_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00000E11sd000000BAbc03sc00i00
remove_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00000E11sd000000BAbc03sc00i00
add_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00000E11sd000000BAbc03sc00i00
remove_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00000E11sd000000BAbc03sc00i00

Greek to me!

James C, I suspect that wont work for you as the product ID is different to mine, weird.

Cheers

BTW, it's a compaq-EVO 500, one of those slimline desktops with mostly laptop parts. (circa 2002)

[James C]

# grep '0x2562' /tmp/udevtrace.log
add_0000:00:02.0_pci_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
remove_i2c-2_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
remove_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
remove_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
remove_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
#


udevtrace.log
add_LNXSYBUS:00_acpi___acpi:LNXSYBUS:
add_LNXCPU:01_acpi___acpi:LNXCPU:
add_LNXCPU:00_acpi___acpi:LNXCPU:
add_cooling_device0_thermal__LNXCPU:00_
add_processor_drivers___
add_processor_module___
add_button_module___
add_LNXPWRBN:00_acpi___acpi:LNXPWRBN:
add_button_drivers___
add_LNXSYSTM:00_acpi___acpi:LNXSYSTM:
add_PNP0200:00_acpi___acpi:PNP0200:
add_PNP0C01:00_acpi___acpi:PNP0C01:
add_PNP0303:00_acpi___acpi:PNP0303:
add_PNP0501:00_acpi___acpi:PNP0501:
add_PNP0000:00_acpi___acpi:PNP0000:
add_PNP0100:00_acpi___acpi:PNP0100:
add_PNP0800:00_acpi___acpi:PNP0800:
add_PNP0C0F:00_acpi___acpi:PNP0C0F:
add_PNP0C0F:01_acpi___acpi:PNP0C0F:
add_PNP0C0F:02_acpi___acpi:PNP0C0F:
add_PNP0C0F:03_acpi___acpi:PNP0C0F:
add_PNP0C0F:04_acpi___acpi:PNP0C0F:
add_PNP0C0F:05_acpi___acpi:PNP0C0F:
add_PNP0C0F:06_acpi___acpi:PNP0C0F:
add_PNP0C0F:07_acpi___acpi:PNP0C0F:
add_input2_input__PNP0C0C:00_input:b0019v0000p0001e0000-e0,1,k74,ramlsfw
add_event0_input__input0_input:b0011v0001p0001eAB41-e0,1,4,11,14,k71,72,73,74,75,76,77,79,7A,7B,7C,7D,7E,7F,80,8C,8E,8F,9B,9C,9D,9E,9F,A3,A4,A5,A6,AC,AD,B7,B8,B9,D9,E2,ram4,l0,1,2,sfw
add_event1_input__input1_input:b0011v0002p0005e0051-e0,1,2,k110,111,112,r0,1,8,amlsfw
add_parport_module___
add_evdev_module___
add_input3_input__LNXPWRBN:00_input:b0019v0000p0001e0000-e0,1,k74,ramlsfw
add_parport_pc_drivers___
add_parport_pc_module___
add_PNP0401:00_acpi___acpi:PNP0401:
add_event3_input__input3_input:b0019v0000p0001e0000-e0,1,k74,ramlsfw
add_parport_pc_drivers___
add_parport_pc_drivers___
add_0000:00:02.0_pci_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_LNXTHERM:00_acpi___acpi:LNXTHERM:
add_thermal_module___
add_thermal_drivers___
add_PNP0700:00_acpi___acpi:PNP0700:
add_parport_pc.956_platform___
add_parport_pc.632_platform___
add_parport_pc.888_platform___
remove_parport_pc.888_platform___
remove_parport_pc.956_platform___
remove_parport_pc.632_platform___
add_PNP0C0C:00_acpi___acpi:PNP0C0C:
add_0000:00:1f.0_pci_0x8086_0x24c0_pci:v00008086d000024C0sv00000000sd00000000bc06sc01i00
add_0000:00:1f.1_pci_0x8086_0x24cb_pci:v00008086d000024CBsv00001028sd00000126bc01sc01i8a
add_event2_input__input2_input:b0019v0000p0001e0000-e0,1,k74,ramlsfw
add_PNP0A03:00_acpi___acpi:PNP0A03:
add_floppy.0_platform___platform:floppy
add_i8042_platform___platform:i8042
add_0000:00:1d.0_pci_0x8086_0x24c2_pci:v00008086d000024C2sv00001028sd00000126bc0Csc03i00
add_serial8250_platform___platform:serial8250
add_device:02_acpi___acpi:device:
add_device:03_acpi___acpi:device:
add_PNP0C01:01_acpi___acpi:PNP0C01:
add_PNP0F13:00_acpi___acpi:PNP0F13:
add_PNP0C04:00_acpi___acpi:PNP0C04:
add_device:00_acpi___acpi:device:
add_device:01_acpi___acpi:device:
add_PNP0B00:00_acpi___acpi:PNP0B00:
add_0:0:0:0_scsi_ATA_0x24cb_scsi:t-0x00
add_vesafb.0_platform___platform:vesafb
add_1:0:0:0_scsi_SAMSUNG_0x24cb_scsi:t-0x05
add_device:04_acpi___acpi:device:
add_font_module___
add_tileblit_module___
add_bitblit_module___
add_softcursor_module___
add_fbcon_graphics___
add_fbcon_module___
add_0000:00:1d.1_pci_0x8086_0x24c4_pci:v00008086d000024C4sv00001028sd00000126bc0Csc03i00
add_0000:00:1d.2_pci_0x8086_0x24c7_pci:v00008086d000024C7sv00001028sd00000126bc0Csc03i00
add_agpgart_module___
add_agpgart_misc___
add_intel_agp_module___
add_0000:00:00.0_pci_0x8086_0x2560_pci:v00008086d00002560sv00001028sd00000126bc06sc00i00
add_agpgart-intel_drivers___
add_serio0_serio___serio:ty06pr00id00ex00
add_snd_page_alloc_module___
add_0000:00:1d.7_pci_0x8086_0x24cd_pci:v00008086d000024CDsv00001028sd00000126bc0Csc03i20
add_2-0:1.0_usb_0x8086_0x24c2_usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
add_sound_class___
add_soundcore_module___
add_pci_hotplug_module___
add_serio1_serio___serio:ty01pr00id00ex00
add_0000:00:1e.0_pci_0x8086_0x244e_pci:v00008086d0000244Esv00000000sd00000000bc06sc04i00
add_0000:00:1f.3_pci_0x8086_0x24c3_pci:v00008086d000024C3sv00001028sd00000126bc0Csc05i00
add_shpchp_drivers___
add_serio_raw_drivers___
add_serio_raw_module___
add_shpchp_module___
add_i2c_core_module___
add_i2c_bus___
add_i2c_i801_module___
add_i2c-0_i2c_0x8086_0000:00:1f.3_pci:v00008086d000024C3sv00001028sd00000126bc0Csc05i00
add_dummy_drivers___
add_i801_smbus_drivers___
add_snd_module___
add_4-0:1.0_usb_0x8086_0x24c7_usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
add_3-0:1.0_usb_0x8086_0x24c4_usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
add_timer_sound___
add_snd_timer_module___
add_snd_seq_device_module___
add_seq_sound___
add_snd_seq_module___
add_pcspkr_module___
add_pcspkr_drivers___
add_pcspkr_platform___platform:pcspkr
add_snd_rawmidi_module___
add_snd_seq_midi_event_module___
add_snd_seq_midi_module___
add_2-0:1.0_usb_0x8086_0x24c2_usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
add_snd_seq_oss_module___
add_sequencer2_sound___
add_sequencer_sound___
add_1-0:1.0_usb_0x8086_0x24cd_usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00
add_3-0:1.0_usb_0x8086_0x24c4_usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
add_battery_module___
add_snd_seq_dummy_module___
add_battery_drivers___
add_4-0:1.0_usb_0x8086_0x24c7_usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
remove_battery_drivers___
remove_battery_module___
add_input4_input__pcspkr_input:b0010v001Fp0001e0100-e0,12,kramls1,2,fw
add_event4_input__input4_input:b0010v001Fp0001e0100-e0,12,kramls1,2,fw
add_e1000_module___
add_snd_pcm_module___
add_1-0:1.0_usb_0x8086_0x24cd_usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00
add_snd_mixer_oss_module___
add_ac97_bus___
add_snd_pcm_oss_module___
add_ac97_bus_module___
add_snd_ac97_codec_module___
add_snd_intel8x0_module___
add_0000:01:0c.0_pci_0x8086_0x100e_pci:v00008086d0000100Esv00001028sd0000002Ebc02sc00i00
add_e1000_drivers___
add_eth0_net_0x8086_0000:01:0c.0_pci:v00008086d0000100Esv00001028sd0000002Ebc02sc00i00
add_0000:00:1f.5_pci_0x8086_0x24c5_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_Intel ICH_drivers___
add_0-0:AD1981B_ac97_0x8086_0x24c5_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_card0_sound_0x8086_0000:00:1f.5_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_pcmC0D0c_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_audio_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_dsp_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_adsp_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_pcmC0D1c_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_pcmC0D0p_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_mixer_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_controlC0_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_pcmC0D2c_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_pcmC0D3c_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_pcmC0D4p_sound_0x8086_card0_pci:v00008086d000024C5sv00001028sd00000126bc04sc01i00
add_vcs2_vc___
add_vcsa2_vc___
add_vcsa3_vc___
add_vcs3_vc___
add_vcs4_vc___
add_vcsa4_vc___
add_output_module___
add_i2c_algo_bit_module___
add_video_output_class___
add_video_drivers___
add_video_module___
add_drm_class___
add_drm_module___
add_drm_kms_helper_module___
add_i915_module___
add_controlD64_drm_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_card0_drm_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_i2c-2_i2c_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_i2c-3_i2c_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_i2c-1_i2c_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_card0-VGA-1_drm_0x8086_card0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
remove_i2c-3_i2c_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
change_card0_drm_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_i2c-3_i2c_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
remove_i2c-3_i2c_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_i2c-3_i2c_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
remove_i2c-2_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
remove_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
remove_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
remove_i2c-3_i2c_0x8086_0x2562_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_fb0_graphics_0x8086_0000:00:02.0_pci:v00008086d00002562sv00001028sd00000126bc03sc00i00
add_vtcon1_vtconsole___
add_i915_drivers___

Don't understand it,but there it is....

[rerwin]

Thanks for the udevtrace lines. Now we are getting somewhere! Let me explain.

The important stuff is:
For 01micko:
pci:v00008086d00002562 sv00000E11sd000000BA bc03sc00i00

For James C:
pci:v00008086d00002562 sv00001028sd00000126 bc03sc00i00

For rerwin:
pci:v00008086d00002562 sv00001014sd00000267 bc03sc00i00

That means subvendor (sv) and subdevice (sd). They seem to be good discriminators!

To override the default of modeset 1, I created the following rules file to briefly force it to 0 for only my type of PC:

Code: Select all

# For Intel graphic card driver intel-agp/i915, force mode for cards requiring it.
# The generated mode setting of zero will override a default of 1 produced by configuration file /etc/modprobe.d/i915.conf
#
# To create a new rule for a VGA compatible controller:
#  Obtain controller description by: lspci -nn
#  Locate the right 4 digits of [8086:dddd] for the graphics controller line and use them in place of the 2562, next.
#  Obtain subvendor/subdevice by: grep '2562' /tmp/udevtrace.log
#   and use rightmost 4 digits of sv0000nnnn and sd0000nnnn.
#  Copy and modify the  ATTR... line, below, and add a description for it.

SUBSYSTEM!="pci", GOTO="i915_end"
ACTION!="add", GOTO="i915_end"
ATTR{vendor}!="0x8086", GOTO="i915_end"

### Devices requiring modeset=0:

# IBM NetVista MT-M 8305-42U
# VGA compatible controller [0300]: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 01)
# Subvendor: 1014  Subdevice: 0267
ATTR{device}=="0x2562", ATTR{subsystem_vendor}=="0x1014", ATTR{subsystem_device}=="0x0267", GOTO="i915_modeset0"

### End of device-specific rules

GOTO="i915_end"
LABEL="i915_modeset0"
RUN+="/bin/sh -c 'echo options i915 modeset=0 > /etc/modprobe.d/i915_modeset0.conf'"
RUN+="/bin/sh -c 'sleep 30 && rm -f /etc/modprobe.d/i915_modeset0.conf &'"
LABEL="i915_end"

It does the job. Please feel free to suggest improvements to the file, but especially to identify other cases that need the override. I thought I saw someone else with the problem, so hope they will post the udevtrace entry so I can add it to the rules file. Thanks, again.
Richard

Edit: I have attached my completed rules file in a dotpet package and replaced the text above with the completed text. The package might be either included in Luci or added to the repository as a user option. Your call, playdayz. Thanks, all, for helping me with this. R

[rjbrewer]

Thanks to all of you for jumping into this discussion of the 845 black screen issue. As a way to further sort out a way to determine which flavor of the card has the problem, could some of you with this card check for more info, by running this command:

grep '0x2562' /tmp/udevtrace.log

My NetVista has:

Code: Select all

add_0000:00:02.0_pci_0x8086_0x2562_pci:v00008086d00002562sv00001014sd00000267bc03sc00i00

I am hoping the ones that work have something different in the pci: modalias string. Thanks.
Richard

A thought I just had: When I looked at my BIOS setup yesterday, I noticed that the VGA aperture is set to 64, which seems small. I think it can go to 256, but that would use up half of my RAM - or is that KB, not MB. Could that be a factor in the black-screen issue? I will test. R

Maximum allocation for the 845 (or my 855) chip is 64mb, if you
have 256 or more ram.

http://www.intel.com/support/graphics/sb/CS-010488.htm

With earlier Lupu I would get black screen and poweroff problems
It boots without black screen now, but it still has the tiny fonts on
shutdown.

i810 works best with my 855.

[01micko]

Richard

Just some proof reading..

At line 6 is there a missing quotation mark?

ATTR{vendor}!="0x8086", GOTO="i915_end (what you have)

ATTR{vendor}!="0x8086", GOTO="i915_end" (what should be?)

Cheers

[rerwin]

i915 was a rather poor work around with my intel 855gm graphics
with early luci.

I quickly found i810 instead of intel and eliminating i915 works great.

254 is really nice.

You sound like a candidate for my overriding rules file. Could you collect some info for me, to assess your situation? Please post the output of the following commands:

lspci -nn

grep '0x8086' /tmp/udevtrace.log

What trouble does the default use of the i915.conf file cause your PC? Does changing the value in /etc/modprobe.d/conf from "1" to "0" make any difference when you boot up?

Thanks for whatever you can provide.
Richard

Edit:
rjbrewer,
Just saw your post above. Disregard this if it makes no sense to do it.

01micko,
Thanks for the catch ("). Fixing it above.

[cowboy]

Curiouser and Curiouser.

01micko also has the same basic chipset as rerwin and James C.

James C and Cowboy, rerwin requests that you send the output of the command

Code: Select all

lspci -nn

00:00.0 Host bridge [0600]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 03)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 02)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 02)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 02)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 02)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 82)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge [8086:24c0] (rev 02)
00:1f.1 IDE interface [0101]: Intel Corporation 82801DB (ICH4) IDE Controller [8086:24cb] (rev 02)
00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller [8086:24c3] (rev 02)
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 02)
01:09.0 Ethernet controller [0200]: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller [100b:0020]
01:0a.0 Communication controller [0780]: Agere Systems LT WinModem [11c1:044e] (rev 02)
01:0c.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)
01:0d.0 FireWire (IEEE 1394) [0c00]: NEC Corporation uPD72874 IEEE1394 OHCI 1.1 3-port PHY-Link Ctrlr [1033:00f2] (rev 01)

[cowboy]

Booted Luci-254 from Live CD. Went straight to desktop, accepted default 1024x768* setting, had no difficulties that I could see.

Then ran Xorgwizard, choose 1024x768x24, got desktop without trouble. The xorg.conf files are different in these two instances, as you guys probably know.

As a reference, ran spup 099, first boot got black screen after choosing 1024x768x24 and "testing" setting. Rebooted, chose 1024x768x24 again, did not do test, and got desktop. Also get desktop when choosing either 1024x768x16 or vesa.

under Luci, usr/lib/xorg/modules/drivers-alternate there are entries for i810. These are NOT present in Spup. The i810 choice is also not available in Spup under xorg setup.

report-video for Luci 254 after running Xorgwizard. (Straight to desktop report is similar, except there is no entry for "driver" or "resolution", they are simply blank.

VIDEO REPORT: Lucid Puppy, version 254

Chip description:
Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device

Driver used by Xorg:
intel

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

[scsijon]

@cowboy, can you check what frequencies (xx khz/ xx.xhz) your screen is running for the two configurations, they may be different. You may need to use the test button with xorgwizard and drop your freq down to get a working one.

@Playdayz and co , although I don't have the 845 myself, (mine is the worse I915,) from my other linux OS links I have come across these:-

: The early 845G (v1) was considered experimental, it is also listed in their systems as using an "Experimental modesetting driver for Intel integrated graphics chipsets."

May I sugest for it you consider using the intel driver if you can, to intel's V6.1, the current known good one for v1 cards. The 14 feb 2008 release, (not the earlier 2006 one also called 6.1 which is known to be faulty with the 2.6 kernal,) although the system of course may not like it! That is if we are not already using it (@01micko do you know?). There is also a later note from 2010 pointing at http://intellinuxgraphics.org/ for later linux drivers and even in that they still seem to !not-like the chipset. Maybe what we really need to do is use intels own driver for 845(V1) and the intellinuxgraphics.org drivers for later versions.

Alternately, ?do we have a "driconf" pet somewhere, it allows setting dri separately to X, it may help fix the problems as on most of the systems the problems seem to relate to that. Maybe that would allow fixes without need to go through the driver/firmware feed, I don't know.

Having a look elsewhere, I do see that in most of the linux versions out there that there are multiple complaints against this chipset in their problem lists when dealing with the 2.6 kernals.

As a last note, I see that the Ubuntu system have a note or two as they seem to have chased it to a fix point.

1: This problem is well-known, and there is a patch being developed that will probably make it into Lucid-backports, or 10.04.1.
AND 2: SOLVED! Ubuntu 10.10 works great with my old Dimension 2400! Let it run for nearly a week (started it an restarted it, too) not one problem.

Hope this helps.

scsijon
\damn typos sorry

[Lobster]

Do we need a proxy connection utility - we have feature freeze?
OK just mention in case . . .
http://www.murga-linux.com/puppy/viewto ... 255#504255

[rjbrewer]

What trouble does the default use of the i915.conf file cause your PC? Does changing the value in /etc/modprobe.d/conf from "1" to "0" make any difference when you boot up?

Edit:
rjbrewer,
Just saw your post above. Disregard this if it makes no sense to do it.

I did a fresh (full) install of 254.
Changing i915 to modeset=0 caused immediate black screen on
reboot.
Changed back to modeset=1 from another install, got it to boot again.

Dropped to prompt and ran xorgwizard choosing i810 and
preferred resolution; rebooted.

Trashed and deleted the three i915 files......it works fine.

What works for me with i810 does not seem to help others
that have 845 graphics.

My Dell 700m with its' 855 graphics is a bit of an odd duck;
I love it though.

[scsijon]

finally had time to do a propper clean install on all my test boxes, all three came out ok on startup script, didn't have to use xorgwizard for once (4cheers).

did some basic install, via qp, ppm and direct, all ok

only comments we have (had a puppy newbie with me) are:

could you please put the Puppy Universal Installer in a prominent place, it use to be under a line, now it gets lost in the menu background.

also maybe make the reboot/create savefile step part of the install process?

well done all

scsijon
now to get back to lupt

[tempestuous]

playdayz, forum feedback regarding the new "rt2800usb" driver in Puppy 5.1/5.2 reveals that this driver requires the same firmware as the rt2870sta driver, so a fix is needed to automatically uncompress this firmware when the rt2800usb driver is first loaded. Thus in /etc/modules/firmware.dep.2.6.33.2
this line -

Code: Select all

rt2870sta-fw:rt2870sta.ko

needs to be changed to this

Code: Select all

rt2870sta-fw:rt2870sta.ko,rt2800usb.ko

[ICPUG]

All you guys having small fonts when coming out of X try the following as a boot code:

video=640x480

This was the original solution when the KMS / Intel driver / Xorg version change problems were solved.

Playdayz implemented the i915.modeset=1 automagically but the video bootcode was left as a user decision.

[playdayz]

Our friend smil99 (who fixes Openshot and Python for us) sent me the following.

Hi playdayz,
Never mentioned before but I live and work in Sendai Miyagi Japan, the worst hit in the March 11th earthquake. Fortunately, my family and I are safe but but we are still traumatized and life is still not back to normal. Just had electricity after 4 days of total blackout and there is still no water and gas. There is also radioactive leakage panic all around.

Will get back to you when everything is okay with us.

[playdayz]

playdayz, forum feedback regarding the new "rt2800usb" driver in Puppy 5.1/5.2 reveals that this driver requires the same firmware as the rt2870sta driver, so a fix is needed to automatically uncompress this firmware when the rt2800usb driver is first loaded. Thus in /etc/modules/firmware.dep.2.6.33.2
this line -
Code:
rt2870sta-fw:rt2870sta.ko

needs to be changed to this
Code:
rt2870sta-fw:rt2870sta.ko,rt2800usb.ko

rt2870sta-fw:rt2870sta.ko,rt2800usb.ko

Got it tempestuous. Thank you.

[nooby]

I hope smil99 look for real reliable info on the radiation leakage because on our version of Swedish NPR they told that some 400 MSievert and that is extremely dangerous levels. One are allowed to be in that environ only a few hours and then never again one get some ten time one the workers get in one whole year in dangerous parts of the power plant. So if he lives that close he need to rethink staying there or get his own instrument so he can monitor what winds bring his way.

The little fall out we had in Sweden from Tjernobyl from Ukraine was with us for decades and made eating the berry in the woods impossible for decades to follow and that was extremely far away from the nuclear plant.

Hope I don't sound too alarmistic but these are real things to worry about if it really is like they say on our radio.

Authorities in Japan may want to calm down to not create panic so them are not too willing to say it is dangerous.

so he need to find reliable knowledge about what the level are at places he lives and goes to.