Installation of bunsenlabs on old and exotic hardware (HP 2133)

jupp · 2018-06-16 17:24:37

Hi,

I always run into problems whenever I decide to give some linux installation on my HP 2133 MiniNote another try. The only Linux that ever worked porperly on this machine is a rather old version of Crunchbang.

The machine is an old netbook with a VIA C3-M and a (grrrrr) VIA Chrome 9-graphics adapter that defies every distribution I tried (like Debian, OpenSuSE, MX, Manjaro, Ubuntu and whatnot).

What puzzles me is that the live-system works fine for me using vga=ask and choosing 1280x768x16 (3ea, if I remember correctly), all subsystems relevant for me are working fine (even wifi out of the box); I don't need a proper graphics driver (like unichrome) but anything that produces a full-res surface.

After installation the graphics does not work, only a blinking cursor in the upper left corner remains after boot. I wonder if anyone has an idea why the graphics configuration from the live system does not get transferred into the installed system or how I can reproduce the configuration from the live system into the installed one.

Thanks for any advice or hint, maybe a nudge into the right direction. I'm not too familiar with current X11 (my knowledge originates from the mid 90s, after that graphics usually worked fine...)

hhh · 2018-06-16 18:19:55

Can you boot into the install using the same boot parameters you used to boot into the live session?

Changes made to the live session do not carry over to the install, unfortunately.

jupp · 2018-06-16 21:01:27

Thanks for the proposition! Yes, I tried several options for boot parameters, also vga=37a and vga=37b. For some reason this value does not seem to carry over.

I did not change anything during the live session; after setting the parameter it simply worked.

ohnonot · 2018-06-17 06:06:23

"doesn't work" is not a satisfactory description.

do you know how to append parameters to the linux command via grub menu?

jupp wrote:

What puzzles me is that the live-system works fine for me using vga=ask and choosing 1280x768x16

why don't you just add exactly that, i.e.

vga=ask

if you get a blank screen again, please try to switch to another tty, wirth e.g. Ctrl-Alt-F2, and do some troubleshooting.

not sure what the appropriate log files would be, my guess is /var/log/Xorg.0.log, /var/log/syslog, and

systemctl status lightdm
systemctl --all --state=failed

jupp · 2018-06-19 14:28:51

Hi,

ohnonot wrote:

"doesn't work" is not a satisfactory description.

sorry, that's true.

ohnonot wrote:

do you know how to append parameters to the linux command via grub menu?

yes, that is not a problem.

jupp wrote:

What puzzles me is that the live-system works fine for me using vga=ask and choosing 1280x768x16

ohnonot wrote:

why don't you just add exactly that, i.e.
vga=ask

I did but the parameter seems to be functionally ignored for the installed version of the kernel or - more preciseley - I get a warning telling me that this deprecated parameter will be ignored (not from the live but the installed kernel - I'am wondering if the parameter works in combination with some other boot parameter...)

ohnonot wrote:

if you get a blank screen again, please try to switch to another tty, wirth e.g. Ctrl-Alt-F2, and do some troubleshooting.

yeah, tried that, but the display seems to have reached a mode that does not allow any more the switch to another tty, it simply stays on the screen and keeps blinking...

ohnonot wrote:

not sure what the appropriate log files would be, my guess is /var/log/Xorg.0.log, /var/log/syslog, and
systemctl status lightdm
systemctl --all --state=failed

I might be able to gain some insights from booting into the live system and try evaluating the system logs of the installed system; hopefully, I will get to it tomorrow.

thanks up to here!

ohnonot · 2018-06-20 03:35:34

if it works in live, it's possible to install it.

try adding 'nomodeset' to the grub command line.

PS:
https://www.startpage.com/do/dsearch?qu … 3+MiniNote

Last edited by ohnonot (2018-06-20 03:35:59)

jupp · 2018-06-20 14:21:25

ohnonot wrote:

if it works in live, it's possible to install it.

yes, thought so myself, but seems to be tricky (tried a fair number of distributions and most seem to behave exactly that way)

ohnonot wrote:

try adding 'nomodeset' to the grub command line.

tried with and without modeset... the result is identical

ohnonot wrote:

PS:
https://www.startpage.com/do/dsearch?qu … 3+MiniNote

guess i've done my fair share of internet research and most of the pages refer to one of the Xchrome (openchrome, unichrome)-drivers which are no longer supported.

regarding the logs: syslog looks fine in both cases (live/installed). the X-log is a completely different matter (see below): "live" comes up with a workable fallback, "installed" does not.

the "installed"-output does show a number of failure determining the correct mode but (as to my interpretation) does not really come up with an error (at least none that I can see). it rather looks (at the end: "[25.890] (II) VESA(0): Attempting to use 60Hz refresh for mode "1024x768" (118)") that it settled with 1024x768 but the screen only contains a lonely blinking cursor. BUT: because I had to shutdown the machine hard (after 2 minutes or so) because I cannot launch any command at this point, it might be that the file is corrupt...

in "live"-output, there is a line: "Creating default Display subsection in Screen section 'Default Screen Section' for depth/fbbpp 24/32" followed by an output that resembles old X11-screen-parameters so I wonder if I somehow simply integrate the values determined there in the active X-config.

if this idea is not too dumb: I cannot find where or how to provide this information within the X-config.

thanks for any hint!

#######################################
"live" system
#######################################
[ 47.795]
X.Org X Server 1.19.2
Release Date: 2017-03-02
[ 47.795] X Protocol Version 11, Revision 0
[ 47.795] Build Operating System: Linux 4.9.0-4-amd64 i686 Debian
[ 47.795] Current Operating System: Linux debian 4.9.0-6-686-pae #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) i686
[ 47.795] Kernel command line: BOOT_IMAGE=/live/vmlinuz boot=live components nomodeset vga=ask initrd=/live/initrd.img
[ 47.795] Build Date: 16 October 2017 08:12:56AM
[ 47.795] xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support)
[ 47.795] Current version of pixman: 0.34.0
[ 47.795] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 47.795] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 47.795] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 20 13:13:59 2018
[ 47.810] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 47.850] (==) No Layout section. Using the first Screen section.
[ 47.850] (==) No screen section available. Using defaults.
[ 47.850] (**) |-->Screen "Default Screen Section" (0)
[ 47.850] (**) | |-->Monitor "<default monitor>"
[ 47.850] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 47.850] (==) Automatically adding devices
[ 47.850] (==) Automatically enabling devices
[ 47.850] (==) Automatically adding GPU devices
[ 47.851] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 47.859] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 47.859] Entry deleted from font path.
[ 47.883] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 47.883] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 47.883] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 47.883] (II) Loader magic: 0x707720
[ 47.883] (II) Module ABI versions:
[ 47.883] X.Org ANSI C Emulation: 0.4
[ 47.883] X.Org Video Driver: 23.0
[ 47.883] X.Org XInput driver : 24.1
[ 47.883] X.Org Server Extension : 10.0
[ 47.969] (++) using VT number 7

[ 47.969] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 47.974] (--) PCI:*(0:1:0:0) 1106:3371:103c:3030 rev 1, Mem @ 0xc0000000/268435456, 0xfc000000/16777216, BIOS @ 0x????????/131072
[ 47.974] (II) LoadModule: "glx"
[ 47.997] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 48.581] (II) Module glx: vendor="X.Org Foundation"
[ 48.581] compiled for 1.19.2, module version = 1.0.0
[ 48.581] ABI class: X.Org Server Extension, version 10.0
[ 48.581] (==) Matched openchrome as autoconfigured driver 0
[ 48.581] (==) Matched modesetting as autoconfigured driver 1
[ 48.581] (==) Matched fbdev as autoconfigured driver 2
[ 48.581] (==) Matched vesa as autoconfigured driver 3
[ 48.581] (==) Assigned the driver to the xf86ConfigLayout
[ 48.581] (II) LoadModule: "openchrome"
[ 48.587] (WW) Warning, couldn't open module openchrome
[ 48.587] (II) UnloadModule: "openchrome"
[ 48.587] (II) Unloading openchrome
[ 48.587] (EE) Failed to load module "openchrome" (module does not exist, 0)
[ 48.587] (II) LoadModule: "modesetting"
[ 48.587] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 48.612] (II) Module modesetting: vendor="X.Org Foundation"
[ 48.612] compiled for 1.19.2, module version = 1.19.2
[ 48.612] Module class: X.Org Video Driver
[ 48.612] ABI class: X.Org Video Driver, version 23.0
[ 48.612] (II) LoadModule: "fbdev"
[ 48.612] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 48.619] (II) Module fbdev: vendor="X.Org Foundation"
[ 48.619] compiled for 1.19.0, module version = 0.4.4
[ 48.619] Module class: X.Org Video Driver
[ 48.619] ABI class: X.Org Video Driver, version 23.0
[ 48.619] (II) LoadModule: "vesa"
[ 48.620] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 48.620] (II) Module vesa: vendor="X.Org Foundation"
[ 48.621] compiled for 1.19.0, module version = 2.3.4
[ 48.621] Module class: X.Org Video Driver
[ 48.621] ABI class: X.Org Video Driver, version 23.0
[ 48.621] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 48.621] (II) FBDEV: driver for framebuffer: fbdev
[ 48.621] (II) VESA: driver for VESA chipsets: vesa
[ 48.691] (EE) open /dev/dri/card0: No such file or directory
[ 48.691] (WW) Falling back to old probe method for modesetting
[ 48.691] (EE) open /dev/dri/card0: No such file or directory
[ 48.691] (II) Loading sub module "fbdevhw"
[ 48.691] (II) LoadModule: "fbdevhw"
[ 48.692] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 48.721] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 48.721] compiled for 1.19.2, module version = 0.0.2
[ 48.721] ABI class: X.Org Video Driver, version 23.0
[ 48.721] (**) FBDEV(1): claimed PCI slot 1@0:0:0
[ 48.721] (II) FBDEV(1): using default device
[ 48.721] (WW) Falling back to old probe method for vesa
[ 48.721] (EE) Screen 0 deleted because of no matching config section.
[ 48.721] (II) UnloadModule: "modesetting"
[ 48.721] (II) FBDEV(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 48.721] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[ 48.721] (==) FBDEV(0): RGB weight 888
[ 48.721] (==) FBDEV(0): Default visual is TrueColor
[ 48.721] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 48.721] (II) FBDEV(0): hardware: VESA VGA (video memory: 7680kB)
[ 48.721] (II) FBDEV(0): checking modes against framebuffer device...
[ 48.721] (II) FBDEV(0): checking modes against monitor...
[ 48.721] (--) FBDEV(0): Virtual size is 1280x768 (pitch 1280)
[ 48.722] (**) FBDEV(0): Built-in mode "current": 98.3 MHz, 60.2 kHz, 76.1 Hz
[ 48.722] (II) FBDEV(0): Modeline "current"x0.0 98.32 1280 1312 1472 1632 768 772 776 792 -hsync -vsync -csync (60.2 kHz b)
[ 48.722] (==) FBDEV(0): DPI set to (96, 96)
[ 48.722] (II) Loading sub module "fb"
[ 48.722] (II) LoadModule: "fb"
[ 48.722] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 48.784] (II) Module fb: vendor="X.Org Foundation"
[ 48.784] compiled for 1.19.2, module version = 1.0.0
[ 48.784] ABI class: X.Org ANSI C Emulation, version 0.4
[ 48.784] (**) FBDEV(0): using shadow framebuffer
[ 48.784] (II) Loading sub module "shadow"
[ 48.784] (II) LoadModule: "shadow"
[ 48.785] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 48.817] (II) Module shadow: vendor="X.Org Foundation"
[ 48.817] compiled for 1.19.2, module version = 1.1.0
[ 48.817] ABI class: X.Org ANSI C Emulation, version 0.4
[ 48.817] (II) UnloadModule: "vesa"
[ 48.817] (II) Unloading vesa
[ 48.817] (==) Depth 24 pixmap format is 32 bpp
[ 48.818] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
[ 49.083] (==) FBDEV(0): Backing store enabled
[ 49.084] (==) FBDEV(0): DPMS enabled
[ 49.084] (==) RandR enabled
[ 49.108] (II) SELinux: Disabled on system
[ 49.134] (II) AIGLX: Screen 0 is not DRI2 capable
[ 49.134] (EE) AIGLX: reverting to software rendering
[ 56.597] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[ 56.599] (II) IGLX: Loaded and initialized swrast
[ 56.599] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 57.265] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 57.265] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 57.265] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 57.265] (II) LoadModule: "libinput"
[ 57.267] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 57.365] (II) Module libinput: vendor="X.Org Foundation"
[ 57.365] compiled for 1.19.0, module version = 0.23.0
[ 57.365] Module class: X.Org XInput Driver
[ 57.365] ABI class: X.Org XInput driver, version 24.1
[ 57.366] (II) Using input driver 'libinput' for 'Power Button'
[ 57.366] (**) Power Button: always reports core events
[ 57.366] (**) Option "Device" "/dev/input/event5"
[ 57.366] (**) Option "_source" "server/udev"
[ 57.367] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
[ 57.368] (II) input device 'Power Button', /dev/input/event5 is a keyboard
[ 57.368] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input9/event5"
[ 57.368] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 57.368] (**) Option "xkb_model" "pc105"
[ 57.368] (**) Option "xkb_layout" "us"
[ 57.371] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
[ 57.371] (II) input device 'Power Button', /dev/input/event5 is a keyboard
[ 57.372] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 57.372] (II) No input driver specified, ignoring this device.
[ 57.372] (II) This device may have been added with another device file.
[ 57.374] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
[ 57.374] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 57.374] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[ 57.374] (II) Using input driver 'libinput' for 'Video Bus'
[ 57.374] (**) Video Bus: always reports core events
[ 57.374] (**) Option "Device" "/dev/input/event4"
[ 57.374] (**) Option "_source" "server/udev"
[ 57.376] (II) input device 'Video Bus', /dev/input/event4 is tagged by udev as: Keyboard
[ 57.376] (II) input device 'Video Bus', /dev/input/event4 is a keyboard
[ 57.376] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/LNXVIDEO:00/input/input8/event4"
[ 57.376] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 57.376] (**) Option "xkb_model" "pc105"
[ 57.376] (**) Option "xkb_layout" "us"
[ 57.378] (II) input device 'Video Bus', /dev/input/event4 is tagged by udev as: Keyboard
[ 57.378] (II) input device 'Video Bus', /dev/input/event4 is a keyboard
[ 57.380] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 57.380] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 57.380] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 57.380] (II) Using input driver 'libinput' for 'Power Button'
[ 57.380] (**) Power Button: always reports core events
[ 57.380] (**) Option "Device" "/dev/input/event3"
[ 57.380] (**) Option "_source" "server/udev"
[ 57.381] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
[ 57.381] (II) input device 'Power Button', /dev/input/event3 is a keyboard
[ 57.381] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7/event3"
[ 57.381] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 57.382] (**) Option "xkb_model" "pc105"
[ 57.382] (**) Option "xkb_layout" "us"
[ 57.383] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
[ 57.383] (II) input device 'Power Button', /dev/input/event3 is a keyboard
[ 57.385] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
[ 57.385] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 57.385] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[ 57.385] (II) Using input driver 'libinput' for 'Sleep Button'
[ 57.385] (**) Sleep Button: always reports core events
[ 57.385] (**) Option "Device" "/dev/input/event2"
[ 57.385] (**) Option "_source" "server/udev"
[ 57.387] (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard
[ 57.387] (II) input device 'Sleep Button', /dev/input/event2 is a keyboard
[ 57.387] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input6/event2"
[ 57.387] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 57.387] (**) Option "xkb_model" "pc105"
[ 57.387] (**) Option "xkb_layout" "us"
[ 57.389] (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard
[ 57.389] (II) input device 'Sleep Button', /dev/input/event2 is a keyboard
[ 57.390] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event10)
[ 57.390] (II) No input driver specified, ignoring this device.
[ 57.390] (II) This device may have been added with another device file.
[ 57.391] (II) config/udev: Adding input device HDA VIA VT82xx Mic (/dev/input/event11)
[ 57.391] (II) No input driver specified, ignoring this device.
[ 57.392] (II) This device may have been added with another device file.
[ 57.393] (II) config/udev: Adding input device HDA VIA VT82xx Front Headphone (/dev/input/event12)
[ 57.393] (II) No input driver specified, ignoring this device.
[ 57.393] (II) This device may have been added with another device file.
[ 57.394] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 57.394] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 57.394] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[ 57.395] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[ 57.395] (**) AT Translated Set 2 keyboard: always reports core events
[ 57.395] (**) Option "Device" "/dev/input/event0"
[ 57.395] (**) Option "_source" "server/udev"
[ 57.396] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
[ 57.396] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
[ 57.396] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 57.396] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 10)
[ 57.396] (**) Option "xkb_model" "pc105"
[ 57.397] (**) Option "xkb_layout" "us"
[ 57.399] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
[ 57.399] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
[ 57.400] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event6)
[ 57.400] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 57.400] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
[ 57.400] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 57.400] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[ 57.400] (II) LoadModule: "synaptics"
[ 57.403] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 57.416] (II) Module synaptics: vendor="X.Org Foundation"
[ 57.416] compiled for 1.19.0, module version = 1.9.0
[ 57.416] Module class: X.Org XInput Driver
[ 57.416] ABI class: X.Org XInput driver, version 24.1
[ 57.416] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 57.416] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 57.416] (**) Option "Device" "/dev/input/event6"
[ 57.416] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472 (res 96)
[ 57.416] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448 (res 213)
[ 57.417] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 57.417] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 57.417] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right
[ 57.417] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 57.417] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 57.417] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 57.417] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input13/event6"
[ 57.417] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 11)
[ 57.417] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 57.417] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 57.417] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.040
[ 57.418] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 57.418] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 57.418] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 57.418] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 57.418] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 57.419] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 57.419] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 57.421] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/event7)
[ 57.421] (II) No input driver specified, ignoring this device.
[ 57.421] (II) This device may have been added with another device file.
[ 57.422] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/js0)
[ 57.422] (II) No input driver specified, ignoring this device.
[ 57.422] (II) This device may have been added with another device file.
[ 57.423] (II) config/udev: Adding input device PC Speaker (/dev/input/event8)
[ 57.423] (II) No input driver specified, ignoring this device.
[ 57.423] (II) This device may have been added with another device file.
[ 57.425] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event9)
[ 57.425] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 57.425] (**) HP WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[ 57.425] (II) Using input driver 'libinput' for 'HP WMI hotkeys'
[ 57.425] (**) HP WMI hotkeys: always reports core events
[ 57.425] (**) Option "Device" "/dev/input/event9"
[ 57.425] (**) Option "_source" "server/udev"
[ 57.426] (II) input device 'HP WMI hotkeys', /dev/input/event9 is tagged by udev as: Keyboard
[ 57.426] (II) input device 'HP WMI hotkeys', /dev/input/event9 is a keyboard
[ 57.427] (**) Option "config_info" "udev:/sys/devices/virtual/input/input16/event9"
[ 57.427] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 12)
[ 57.427] (**) Option "xkb_model" "pc105"
[ 57.427] (**) Option "xkb_layout" "us"
[ 57.429] (II) input device 'HP WMI hotkeys', /dev/input/event9 is tagged by udev as: Keyboard
[ 57.429] (II) input device 'HP WMI hotkeys', /dev/input/event9 is a keyboard

#######################################
"installed" system
#######################################
[ 23.884]
X.Org X Server 1.19.2
Release Date: 2017-03-02
[ 23.884] X Protocol Version 11, Revision 0
[ 23.884] Build Operating System: Linux 4.9.0-4-amd64 i686 Debian
[ 23.884] Current Operating System: Linux hpmini 4.9.0-6-686-pae #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) i686
[ 23.884] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-686-pae root=/dev/sda2 ro nomodeset vga=37B
[ 23.884] Build Date: 16 October 2017 08:12:56AM
[ 23.884] xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support)
[ 23.884] Current version of pixman: 0.34.0
[ 23.884] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 23.884] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 23.885] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 20 15:04:31 2018
[ 23.935] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 24.021] (==) No Layout section. Using the first Screen section.
[ 24.021] (==) No screen section available. Using defaults.
[ 24.021] (**) |-->Screen "Default Screen Section" (0)
[ 24.021] (**) | |-->Monitor "<default monitor>"
[ 24.032] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 24.032] (==) Automatically adding devices
[ 24.032] (==) Automatically enabling devices
[ 24.032] (==) Automatically adding GPU devices
[ 24.032] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 24.384] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 24.385] Entry deleted from font path.
[ 24.389] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 24.389] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 24.389] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 24.389] (II) Loader magic: 0x6a2720
[ 24.389] (II) Module ABI versions:
[ 24.389] X.Org ANSI C Emulation: 0.4
[ 24.389] X.Org Video Driver: 23.0
[ 24.389] X.Org XInput driver : 24.1
[ 24.389] X.Org Server Extension : 10.0
[ 24.393] (++) using VT number 7

[ 24.393] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 24.405] (--) PCI:*(0:1:0:0) 1106:3371:103c:3030 rev 1, Mem @ 0xc0000000/268435456, 0xfc000000/16777216, BIOS @ 0x????????/131072
[ 24.417] (II) LoadModule: "glx"
[ 24.434] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 24.629] (II) Module glx: vendor="X.Org Foundation"
[ 24.630] compiled for 1.19.2, module version = 1.0.0
[ 24.630] ABI class: X.Org Server Extension, version 10.0
[ 24.630] (==) Matched openchrome as autoconfigured driver 0
[ 24.630] (==) Matched modesetting as autoconfigured driver 1
[ 24.630] (==) Matched fbdev as autoconfigured driver 2
[ 24.630] (==) Matched vesa as autoconfigured driver 3
[ 24.630] (==) Assigned the driver to the xf86ConfigLayout
[ 24.630] (II) LoadModule: "openchrome"
[ 24.631] (WW) Warning, couldn't open module openchrome
[ 24.631] (II) UnloadModule: "openchrome"
[ 24.631] (II) Unloading openchrome
[ 24.631] (EE) Failed to load module "openchrome" (module does not exist, 0)
[ 24.632] (II) LoadModule: "modesetting"
[ 24.632] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 24.648] (II) Module modesetting: vendor="X.Org Foundation"
[ 24.648] compiled for 1.19.2, module version = 1.19.2
[ 24.648] Module class: X.Org Video Driver
[ 24.648] ABI class: X.Org Video Driver, version 23.0
[ 24.648] (II) LoadModule: "fbdev"
[ 24.649] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 24.658] (II) Module fbdev: vendor="X.Org Foundation"
[ 24.659] compiled for 1.19.0, module version = 0.4.4
[ 24.659] Module class: X.Org Video Driver
[ 24.659] ABI class: X.Org Video Driver, version 23.0
[ 24.659] (II) LoadModule: "vesa"
[ 24.659] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 24.666] (II) Module vesa: vendor="X.Org Foundation"
[ 24.666] compiled for 1.19.0, module version = 2.3.4
[ 24.666] Module class: X.Org Video Driver
[ 24.666] ABI class: X.Org Video Driver, version 23.0
[ 24.666] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 24.666] (II) FBDEV: driver for framebuffer: fbdev
[ 24.667] (II) VESA: driver for VESA chipsets: vesa
[ 24.678] (EE) open /dev/dri/card0: No such file or directory
[ 24.678] (WW) Falling back to old probe method for modesetting
[ 24.678] (EE) open /dev/dri/card0: No such file or directory
[ 24.678] (II) Loading sub module "fbdevhw"
[ 24.678] (II) LoadModule: "fbdevhw"
[ 24.678] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 24.688] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 24.688] compiled for 1.19.2, module version = 0.0.2
[ 24.688] ABI class: X.Org Video Driver, version 23.0
[ 24.688] (EE) open /dev/fb0: No such file or directory
[ 24.688] (WW) Falling back to old probe method for fbdev
[ 24.688] (II) Loading sub module "fbdevhw"
[ 24.688] (II) LoadModule: "fbdevhw"
[ 24.688] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 24.689] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 24.689] compiled for 1.19.2, module version = 0.0.2
[ 24.689] ABI class: X.Org Video Driver, version 23.0
[ 24.689] (EE) open /dev/fb0: No such file or directory
[ 24.689] (EE) Screen 0 deleted because of no matching config section.
[ 24.689] (II) UnloadModule: "modesetting"
[ 24.689] (EE) Screen 0 deleted because of no matching config section.
[ 24.689] (II) UnloadModule: "fbdev"
[ 24.689] (II) UnloadSubModule: "fbdevhw"
[ 24.689] (II) Loading sub module "vbe"
[ 24.689] (II) LoadModule: "vbe"
[ 24.690] (II) Loading /usr/lib/xorg/modules/libvbe.so
[ 24.699] (II) Module vbe: vendor="X.Org Foundation"
[ 24.699] compiled for 1.19.2, module version = 1.1.0
[ 24.699] ABI class: X.Org Video Driver, version 23.0
[ 24.700] (II) Loading sub module "int10"
[ 24.700] (II) LoadModule: "int10"
[ 24.700] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 24.702] (II) Module int10: vendor="X.Org Foundation"
[ 24.702] compiled for 1.19.2, module version = 1.0.0
[ 24.702] ABI class: X.Org Video Driver, version 23.0
[ 24.702] (II) VESA(0): initializing int10
[ 24.711] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[ 24.713] (II) VESA(0): VESA BIOS detected
[ 24.713] (II) VESA(0): VESA VBE Version 3.0
[ 24.713] (II) VESA(0): VESA VBE Total Mem: 32768 kB
[ 24.713] (II) VESA(0): VESA VBE OEM: VIA N3364

[ 24.714] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
[ 24.714] (II) VESA(0): VESA VBE OEM Vendor:
[ 24.714] (II) VESA(0): VESA VBE OEM Product:
[ 24.714] (II) VESA(0): VESA VBE OEM Product Rev:
[ 24.899] (II) VESA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 24.899] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[ 24.900] (==) VESA(0): RGB weight 888
[ 24.900] (==) VESA(0): Default visual is TrueColor
[ 24.900] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 24.900] (II) Loading sub module "ddc"
[ 24.900] (II) LoadModule: "ddc"
[ 24.900] (II) Module "ddc" already built-in
[ 24.900] (II) VESA(0): VESA VBE DDC supported
[ 24.900] (II) VESA(0): VESA VBE DDC Level 2
[ 24.900] (II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
[ 25.534] (II) VESA(0): VESA VBE DDC read failed
[ 25.534] (II) VESA(0): VESA VBE PanelID invalid
[ 25.534] (II) VESA(0): Searching for matching VESA mode(s):
[ 25.537] Mode: 101 (640x480)
[ 25.537] ModeAttributes: 0x9f
[ 25.537] WinAAttributes: 0x7
[ 25.537] WinBAttributes: 0x0
[ 25.537] WinGranularity: 64
[ 25.537] WinSize: 64
[ 25.537] WinASegment: 0xa000
[ 25.537] WinBSegment: 0xa000
[ 25.537] WinFuncPtr: 0xc00080c7
[ 25.537] BytesPerScanline: 640
[ 25.537] XResolution: 640
[ 25.537] YResolution: 480
[ 25.537] XCharSize: 8
[ 25.537] YCharSize: 16
[ 25.537] NumberOfPlanes: 1
[ 25.537] BitsPerPixel: 8
[ 25.537] NumberOfBanks: 1
[ 25.537] MemoryModel: 4
[ 25.537] BankSize: 0
[ 25.537] NumberOfImages: 101
[ 25.537] RedMaskSize: 0
[ 25.537] RedFieldPosition: 0
[ 25.537] GreenMaskSize: 0
[ 25.537] GreenFieldPosition: 0
[ 25.538] BlueMaskSize: 0
[ 25.538] BlueFieldPosition: 0
[ 25.538] RsvdMaskSize: 0
[ 25.538] RsvdFieldPosition: 0
[ 25.538] DirectColorModeInfo: 2
[ 25.538] PhysBasePtr: 0xc0000000
[ 25.538] LinBytesPerScanLine: 640
[ 25.538] BnkNumberOfImagePages: 101
[ 25.538] LinNumberOfImagePages: 101
[ 25.538] LinRedMaskSize: 0
[ 25.538] LinRedFieldPosition: 0
[ 25.538] LinGreenMaskSize: 0
[ 25.538] LinGreenFieldPosition: 0
[ 25.538] LinBlueMaskSize: 0
[ 25.538] LinBlueFieldPosition: 0
[ 25.538] LinRsvdMaskSize: 0
[ 25.538] LinRsvdFieldPosition: 0
[ 25.538] MaxPixelClock: 0
[ 25.540] Mode: 111 (640x480)
[ 25.540] ModeAttributes: 0x9b
[ 25.540] WinAAttributes: 0x7

[... about 20 more similar "Mode: nnn"-entries

[ 25.886]
[ 25.886] (II) VESA(0): Total Memory: 512 64KB banks (32768kB)
[ 25.886] (II) VESA(0): <default monitor>: Using default hsync range of 31.50-48.00 kHz
[ 25.886] (II) VESA(0): <default monitor>: Using default vrefresh range of 50.00-70.00 Hz
[ 25.886] (II) VESA(0): <default monitor>: Using default maximum pixel clock of 65.00 MHz
[ 25.886] (WW) VESA(0): Unable to estimate virtual size
[ 25.886] (II) VESA(0): Not using built-in mode "1920x1200" (no mode of this name)
[ 25.886] (II) VESA(0): Not using built-in mode "1920x1080" (no mode of this name)
[ 25.886] (II) VESA(0): Not using built-in mode "1600x1200" (no mode of this name)
[ 25.886] (II) VESA(0): Not using built-in mode "1680x1050" (no mode of this name)
[ 25.886] (II) VESA(0): Not using built-in mode "1400x1050" (no mode of this name)
[ 25.886] (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
[ 25.886] (II) VESA(0): Not using built-in mode "1440x900" (no mode of this name)
[ 25.886] (II) VESA(0): Not using built-in mode "1280x960" (no mode of this name)
[ 25.886] (II) VESA(0): Not using built-in mode "1366x768" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "1280x800" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "1280x768" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "1280x720" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "1024x600" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "720x576" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "852x480" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "720x540" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "800x480" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "720x480" (no mode of this name)
[ 25.887] (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
[ 25.887] (WW) VESA(0): No valid modes left. Trying less strict filter...
[ 25.887] (II) VESA(0): <default monitor>: Using hsync range of 31.50-48.00 kHz
[ 25.887] (II) VESA(0): <default monitor>: Using vrefresh range of 50.00-70.00 Hz
[ 25.887] (II) VESA(0): <default monitor>: Using maximum pixel clock of 65.00 MHz
[ 25.887] (WW) VESA(0): Unable to estimate virtual size
[ 25.887] (II) VESA(0): Not using built-in mode "1920x1200" (hsync out of range)
[ 25.887] (II) VESA(0): Not using built-in mode "1920x1080" (hsync out of range)
[ 25.888] (II) VESA(0): Not using built-in mode "1600x1200" (hsync out of range)
[ 25.888] (II) VESA(0): Not using built-in mode "1680x1050" (hsync out of range)
[ 25.888] (II) VESA(0): Not using built-in mode "1400x1050" (hsync out of range)
[ 25.888] (II) VESA(0): Not using built-in mode "1280x1024" (hsync out of range)
[ 25.888] (II) VESA(0): Not using built-in mode "1440x900" (hsync out of range)
[ 25.888] (II) VESA(0): Not using built-in mode "1280x960" (hsync out of range)
[ 25.888] (II) VESA(0): Not using built-in mode "1366x768" (hsync out of range)
[ 25.889] (II) VESA(0): Not using built-in mode "1280x800" (hsync out of range)
[ 25.889] (II) VESA(0): Not using built-in mode "1280x768" (hsync out of range)
[ 25.889] (--) VESA(0): Virtual size is 1280x768 (pitch 1280)
[ 25.889] (**) VESA(0): *Built-in mode "1280x720"
[ 25.889] (**) VESA(0): *Built-in mode "1024x768"
[ 25.889] (**) VESA(0): *Built-in mode "1024x600"
[ 25.889] (**) VESA(0): *Built-in mode "800x600"
[ 25.889] (**) VESA(0): *Built-in mode "720x576"
[ 25.889] (**) VESA(0): *Built-in mode "852x480"
[ 25.889] (**) VESA(0): *Built-in mode "720x540"
[ 25.889] (**) VESA(0): *Built-in mode "800x480"
[ 25.889] (**) VESA(0): *Built-in mode "720x480"
[ 25.889] (**) VESA(0): *Built-in mode "640x480"
[ 25.889] (==) VESA(0): DPI set to (96, 96)
[ 25.890] (II) VESA(0): Attempting to use 60Hz refresh for mode "1024x768" (118)

sleekmason · 2018-06-20 19:07:00

Here are the default settings in the kernel that affect your Via Chrome 9.

Symbol: FB_VIA [=m]                                                     │  
  │ Type  : tristate                                                        │  
  │ Prompt: VIA UniChrome (Pro) and Chrome9 display support                 │  
  │   Location:                                                             │  
  │     -> Device Drivers                                                   │  
  │       -> Graphics support                                               │  
  │ (4)     -> Frame buffer Devices                                         │  
  │   Defined at drivers/video/fbdev/Kconfig:1441                           │  
  │   Depends on: HAS_IOMEM [=y] && FB [=y] && PCI [=y] && X86 [=y] && GPIO │  
  │   Selects: FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && FB_CFB_IMAGE │

│

 Symbol: FB_VIA_X_COMPATIBILITY [=y]                                     │  
  │ Type  : bool                                                            │  
  │ Prompt: X server compatibility                                          │  
  │   Location:                                                             │  
  │     -> Device Drivers                                                   │  
  │       -> Graphics support                                               │  
  │         -> Frame buffer Devices                                         │  
  │ (6)       -> VIA UniChrome (Pro) and Chrome9 display support (FB_VIA [= │  
  │   Defined at drivers/video/fbdev/Kconfig:1470                           │  
  │   Depends on: HAS_IOMEM [=y] && FB_VIA [=m]

Here is where I think your problem lies.

 Symbol: FB_VIA_DIRECT_PROCFS [=n]                                       │  
  │ Type  : bool                                                            │  
  │ Prompt: direct hardware access via procfs (DEPRECATED)(DANGEROUS)       │  
  │   Location:                                                             │  
  │     -> Device Drivers                                                   │  
  │       -> Graphics support                                               │  
  │         -> Frame buffer Devices                                         │  
  │ (5)       -> VIA UniChrome (Pro) and Chrome9 display support (FB_VIA [= │  
  │   Defined at drivers/video/fbdev/Kconfig:1460                           │  
  │   Depends on: HAS_IOMEM [=y] && FB_VIA [=m]

Here is a description of the above:

 CONFIG_FB_VIA_DIRECT_PROCFS:                                                  │  
  │                                                                               │  
  │ Allow direct hardware access to some output registers via procfs.             │  
  │ This is dangerous but may provide the only chance to get the                  │  
  │ correct output device configuration.                                          │  
  │ Its use is strongly discouraged.                                              │  
  │                                                                               │  
  │ Symbol: FB_VIA_DIRECT_PROCFS [=n]                                             │  
  │ Type  : bool                                                                  │  
  │ Prompt: direct hardware access via procfs (DEPRECATED)(DANGEROUS)             │  
  │   Location:                                                                   │  
  │     -> Device Drivers                                                         │  
  │       -> Graphics support                                                     │  
  │         -> Frame buffer Devices                                               │  
  │           -> VIA UniChrome (Pro) and Chrome9 display support (FB_VIA [=m])    │  
  │   Defined at drivers/video/fbdev/Kconfig:1460                                 │  
  │   Depends on: HAS_IOMEM [=y] && FB_VIA [=m]

So, is possible to enable the procfs at boot? I bet there's a cheat code for that:)

If not, you could do is recompile your kernel to include support. There is a guide in the forums. --HERE--

Last edited by sleekmason (2018-06-20 19:12:47)

ohnonot · 2018-06-21 05:58:45

^ i'm sure sleekmason has a point there, but it's a little over my head.

here are your two kernel command lines compared:

BOOT_IMAGE=/live/vmlinuz boot=live components nomodeset vga=ask initrd=/live/initrd.img

BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-686-pae root=/dev/sda2 ro nomodeset vga=37B

maybe you can glean something from the former?

firstly, i wouldn't use BOTH nomodeset and vga=37B. try ONLY nomodeset.
then, what is this "components" option? could be interesting.
then, the initrd seems to be different, maybe it can be re-used?
obviously i wouldn't use the boot=live option for an installed system...

btw, i think you should consider hard drive problems also.
dunno HOW you installed.
you could also try an offline install, in the hope that some older (kernel presumably) package works better.

also see here:
https://github.com/torvalds/linux/blob/ … meters.txt
https://wiki.archlinux.org/index.php/Via

Last edited by ohnonot (2018-06-21 06:01:46)

sleekmason · 2018-06-21 13:01:34

Sorry, should have been a little more clear in what I am talking about. When you open the kernel configuration file, you are presented with all the possible options currently in the Linux kernel. The codes I listed above are the direct settings for the Via Chrome 9 driver. The third one shows that one of the required items is not activated.

CONFIG_FB_VIA_DIRECT_PROCFS: │
│ │
│ Allow direct hardware access to some output registers via procfs. │
│ This is dangerous but may provide the only chance to get the │
│ correct output device configuration. │
│ Its use is strongly discouraged. │
│ │
│ Symbol: FB_VIA_DIRECT_PROCFS [=n]

This more than likely IS the problem, as the procfs is not activated in the default kernel. Because it is deprecated, the procfs isn't in any distro's kernel. This does not mean that it can't be used, but probably shouldn't be. That being said, If I had a box with the Via Chrome driver, I would recompile the kernel to my needs.

This is a lot easier than you would think, and I will be happy to help in any way I can.

My guess would be that the live CD activated the procfs to initiate drivers and such during discovery, but is then removed for final distribution to others. Seems like I remember a kernel update in BL-welcome.

I doubt anything is going to help unless the procfs has been enabled.

Last edited by sleekmason (2018-06-21 13:07:08)

jupp · 2018-06-29 07:57:36

sorry for the long delay... time didn't allow me to go on... thanks for the answers!

ohnonot wrote:

firstly, i wouldn't use BOTH nomodeset and vga=37B. try ONLY nomodeset.
then, what is this "components" option? could be interesting.
then, the initrd seems to be different, maybe it can be re-used?
obviously i wouldn't use the boot=live option for an installed system...

I know that especially this combination looks silly but I tried a number of combinations (also "modeset" alone), the result after booting is always the same.

ohnonot wrote:

btw, i think you should consider hard drive problems also.
dunno HOW you installed.
you could also try an offline install, in the hope that some older (kernel presumably) package works better.

I installed from the live system using a usb-stick initialized with the "bl-Helium_i386+build2.iso"-image. Until now I haven't realized any problems with the hard drive (but I will check the SMART-attributes of the HD, one never knows...)

sleekmason wrote:

Sorry, should have been a little more clear in what I am talking about. When you open the kernel configuration file, you are presented with all the possible options currently in the Linux kernel. The codes I listed above are the direct settings for the Via Chrome 9 driver. The third one shows that one of the required items is not activated.
CONFIG_FB_VIA_DIRECT_PROCFS: │
│ │
│ Allow direct hardware access to some output registers via procfs. │
│ This is dangerous but may provide the only chance to get the │
│ correct output device configuration. │
│ Its use is strongly discouraged. │
│ │
│ Symbol: FB_VIA_DIRECT_PROCFS [=n]
This more than likely IS the problem, as the procfs is not activated in the default kernel. Because it is deprecated, the procfs isn't in any distro's kernel. This does not mean that it can't be used, but probably shouldn't be. That being said, If I had a box with the Via Chrome driver, I would recompile the kernel to my needs.
This is a lot easier than you would think, and I will be happy to help in any way I can.
My guess would be that the live CD activated the procfs to initiate drivers and such during discovery, but is then removed for final distribution to others. Seems like I remember a kernel update in BL-welcome.
I doubt anything is going to help unless the procfs has been enabled.

This really sounds interesting and would explain the behavior of live vs. installed system. I hope that in the next couple of days I find the time to boot into text mode and try to configure and build the kernel (last time is a long time ago when duron-processors still roamed the land and needed cpufreq-support :-)

ohnonot · 2018-06-29 09:45:30

jupp wrote:

ohnonot wrote:
PS:
https://www.startpage.com/do/dsearch?qu … 3+MiniNote
guess i've done my fair share of internet research and most of the pages refer to one of the Xchrome (openchrome, unichrome)-drivers which are no longer supported.

let's get back to this.
why do say that?
xserver-xorg-video-openchrome is in stretch's repos.
going back to when you posted this, tehre was also two Xorg logs. try grepping both for openchrome - you can see it's clearly trying to load openchrome, which doesn't exist.
why couldn't you install openchrome - and set it up properly (might need to search debian forums for that)?

btw, the archlinux repositories have not only xf86-video-openchrome, but also unichrome-dri (which might provide some gl accelaration afaiu), so switching distros could also help.

edit:
i'm puzzled.
you said you cannot even switch to another tty on the installed system, yet you then provide a Xorg log from it.
how's that possible?

Last edited by ohnonot (2018-06-29 09:49:03)

sleekmason · 2018-06-29 12:12:53

https://lists.freedesktop.org/archives/ … 01753.html

If the procfs is not required for your hardware, there is a version that may provide fixes in either unstable or buster.

For kicks, I would update to sid and see if you can get it to work.

If you do, the preferred method is to enable testing first, apt dist-upgrade in testing, and then enable the sid repos and do it again. I don't know if the fix has made it into Buster yet, but it might have! I would try along the way.

#1 2018-06-16 17:24:37

Installation of bunsenlabs on old and exotic hardware (HP 2133)

#2 2018-06-16 18:19:55

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#3 2018-06-16 21:01:27

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#4 2018-06-17 06:06:23

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#5 2018-06-19 14:28:51

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#6 2018-06-20 03:35:34

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#7 2018-06-20 14:21:25

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#8 2018-06-20 19:07:00

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#9 2018-06-21 05:58:45

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#10 2018-06-21 13:01:34

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#11 2018-06-29 07:57:36

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#12 2018-06-29 09:45:30

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

#13 2018-06-29 12:12:53

Re: Installation of bunsenlabs on old and exotic hardware (HP 2133)

Board footer