LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-27-2019, 08:31 AM   #31
poetgrant
Member
 
Registered: Feb 2019
Distribution: Slackware
Posts: 90

Original Poster
Rep: Reputation: 22

Quote:
Originally Posted by hazel View Post
It's certainly nothing to do with lilo. This has to be a kernel issue. I looked up GMBUS and found this. You seem to have a rather unusual video bus. And it looks like the kernel drm driver doesn't like it.
Would you think there is a kernel mod to fix this? I wonder if when I installed the new kernel, it unloaded the mods being used?
 
Old 10-27-2019, 08:36 AM   #32
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Ubuntu, Debian, Slackware
Posts: 2,178
Blog Entries: 6

Rep: Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470Reputation: 2470
Quote:
Originally Posted by poetgrant View Post
Would you think there is a kernel mod to fix this? I wonder if when I installed the new kernel, it unloaded the mods being used?
This is one of those occasions whereby uploading your computer info to https://linux-hardware.org/ would probably be a big help, since it would tell you where the incompatibilities were with all your hardware and it will offer fixes where available.

Have a look at this thread:

https://www.linuxquestions.org/quest...rg-4175662855/

You could do all this at the command line [i.e. downloading hw-probe and its depends, making the package, installing it and uploading your info], as long as you are able to get to work in the command line once your computer has booted and you can connect to your network.

To make it easier, I've uploaded my own Slackware-compatible binary, so all you would have to do would be

Code:
wget https://filebin.net/3e6x7fhvmk84688r/hwprobe.txz
to get it, and then just install it and run the commands as given on the website.

EDIT: You may need hwinfo/libx86emu from SBo too.

Last edited by Lysander666; 10-27-2019 at 08:45 AM.
 
1 members found this post helpful.
Old 10-27-2019, 08:50 AM   #33
0XBF
Member
 
Registered: Nov 2018
Distribution: Slackware
Posts: 795

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
FWIW I get the same types of errors in my dmesg log on the 1000H:

Code:
[   13.903546] cfg80211: World regulatory domain updated:
[   13.907737] cfg80211:  DFS Master region: unset
[   13.907851] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   13.916307] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   13.920864] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   13.925424] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   13.929879] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   13.934413] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   13.938982] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[   13.943585] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   13.948162] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[   13.979392] cfg80211: Regulatory domain changed to country: BM
[   13.984067] cfg80211:  DFS Master region: FCC
[   13.984191] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   13.993467] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
[   13.998093] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2400 mBm), (N/A)
[   14.002827] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2400 mBm), (0 s)
[   14.007632] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2400 mBm), (0 s)
[   14.012375] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
[   14.227106] Linux video capture interface: v2.00
[   14.392218] uvcvideo: Found UVC 1.00 device CNF7129 (04f2:b071)
[   14.414224] input: CNF7129 as /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/input/input11
[   14.419675] usbcore: registered new interface driver uvcvideo
[   14.424703] USB Video Class driver (1.1.1)
[   14.866184] [drm] GMBUS [i915 gmbus dpd] timed out, falling back to bit banging on pin 6
[   14.939167] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
[   15.003136] [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
[   15.352179] Adding 1127420k swap on /dev/sda3.  Priority:-1 extents:1 across:1127420k 
[   15.448862] fuse init (API version 7.23)
[   15.982953] EXT4-fs (sda2): re-mounted. Opts: (null)
[   23.838093] intel_rng: FWH not detected
[   23.850671] leds_ss4200: no LED devices found
[   33.050500] NET: Registered protocol family 10
[   43.966839] wlan0: authenticate with 48:f8:b3:67:32:4f
[   43.972067] wlan0: send auth to 48:f8:b3:67:32:4f (try 1/3)
[   43.973758] wlan0: authenticated
[   43.976088] wlan0: associate with 48:f8:b3:67:32:4f (try 1/3)
[   43.999672] wlan0: RX AssocResp from 48:f8:b3:67:32:4f (capab=0x411 status=0 aid=4)
[   43.999844] wlan0: associated
[   45.770065] FS-Cache: Loaded
[   45.782048] FS-Cache: Netfs 'cifs' registered for caching
So I'm not so sure the issue lies there. Did you note any other errors further up the log?
 
1 members found this post helpful.
Old 10-27-2019, 08:58 AM   #34
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,382

Rep: Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760
I do not think it is a kernel issue.
I looked up "[drm] GMBUS [i915 gmbus dpd] timed out, falling back to bit banging" and found this.
Quote:
[ 29.862689] NET: Registered protocol family 10
[ 36.586965] wlan0: authenticate with 60:38:e0:db:ad:7a
[ 36.623144] wlan0: send auth to 60:38:e0:db:ad:7a (try 1/3)
[ 36.646214] wlan0: authenticated
[ 36.647322] wlan0: associate with 60:38:e0:db:ad:7a (try 1/3)
[ 36.676289] wlan0: RX AssocResp from 60:38:e0:db:ad:7a (capab=0x411 status=0 aid=7)
[ 36.676460] wlan0: associated`
This shows that your wireless device has been connected. This suggests that /etc/rc.d/rc.M is running. After networking is started, /etc/rc.d/rc.inet2 is run, which tries to start NFS. The OP mentions a main machine. Perhaps there is an issue with NFS. If you can SSH in, and /etc/rc.nfsd and /etc/rc.d/rc.rpc are executable, then I suggest chmod -x both those files and rebooting.
 
1 members found this post helpful.
Old 10-27-2019, 09:08 AM   #35
poetgrant
Member
 
Registered: Feb 2019
Distribution: Slackware
Posts: 90

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by allend View Post
I do not think it is a kernel issue.
I looked up "[drm] GMBUS [i915 gmbus dpd] timed out, falling back to bit banging" and found this.

This shows that your wireless device has been connected. This suggests that /etc/rc.d/rc.M is running. After networking is started, /etc/rc.d/rc.inet2 is run, which tries to start NFS. The OP mentions a main machine. Perhaps there is an issue with NFS. If you can SSH in, and /etc/rc.nfsd and /etc/rc.d/rc.rpc are executable, then I suggest chmod -x both those files and rebooting.
Okay, so would it be bad if there is no `/etc/rc.nfsd` file?
 
Old 10-27-2019, 09:12 AM   #36
0XBF
Member
 
Registered: Nov 2018
Distribution: Slackware
Posts: 795

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
Check in /etc/rc.d/rc.nfsd
 
1 members found this post helpful.
Old 10-27-2019, 09:18 AM   #37
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,382

Rep: Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760Reputation: 2760
If you can SSH in, then the sshd daemon has been started. The nfsd daemon is started after that. If you have been using NFS with NFS mounts specified in /etc/fstab, but there is no /etc/rc.nfsd script, then yes, bad.
 
Old 10-27-2019, 09:20 AM   #38
0XBF
Member
 
Registered: Nov 2018
Distribution: Slackware
Posts: 795

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
Is there any chance your machine is booting into runlevel 4 and X is hanging there with a black screen? Maybe do a quick check of /etc/inittab for the line:
Code:
# Default runlevel. (Do not set to 0 or 6)
id:3:initdefault:
If its set to 4, you could change it back to 3 and try a reboot. Not sure if this was suggested yet.
 
Old 10-27-2019, 09:41 AM   #39
poetgrant
Member
 
Registered: Feb 2019
Distribution: Slackware
Posts: 90

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by 0XBF View Post
FWIW I get the same types of errors in my dmesg log on the 1000H:

Code:
[   13.903546] cfg80211: World regulatory domain updated:
[   13.907737] cfg80211:  DFS Master region: unset
[   13.907851] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   13.916307] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   13.920864] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   13.925424] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   13.929879] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   13.934413] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   13.938982] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[   13.943585] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   13.948162] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[   13.979392] cfg80211: Regulatory domain changed to country: BM
[   13.984067] cfg80211:  DFS Master region: FCC
[   13.984191] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   13.993467] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
[   13.998093] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2400 mBm), (N/A)
[   14.002827] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2400 mBm), (0 s)
[   14.007632] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2400 mBm), (0 s)
[   14.012375] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
[   14.227106] Linux video capture interface: v2.00
[   14.392218] uvcvideo: Found UVC 1.00 device CNF7129 (04f2:b071)
[   14.414224] input: CNF7129 as /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/input/input11
[   14.419675] usbcore: registered new interface driver uvcvideo
[   14.424703] USB Video Class driver (1.1.1)
[   14.866184] [drm] GMBUS [i915 gmbus dpd] timed out, falling back to bit banging on pin 6
[   14.939167] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
[   15.003136] [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
[   15.352179] Adding 1127420k swap on /dev/sda3.  Priority:-1 extents:1 across:1127420k 
[   15.448862] fuse init (API version 7.23)
[   15.982953] EXT4-fs (sda2): re-mounted. Opts: (null)
[   23.838093] intel_rng: FWH not detected
[   23.850671] leds_ss4200: no LED devices found
[   33.050500] NET: Registered protocol family 10
[   43.966839] wlan0: authenticate with 48:f8:b3:67:32:4f
[   43.972067] wlan0: send auth to 48:f8:b3:67:32:4f (try 1/3)
[   43.973758] wlan0: authenticated
[   43.976088] wlan0: associate with 48:f8:b3:67:32:4f (try 1/3)
[   43.999672] wlan0: RX AssocResp from 48:f8:b3:67:32:4f (capab=0x411 status=0 aid=4)
[   43.999844] wlan0: associated
[   45.770065] FS-Cache: Loaded
[   45.782048] FS-Cache: Netfs 'cifs' registered for caching
So I'm not so sure the issue lies there. Did you note any other errors further up the log?
Here's the full report from dmesg:

Code:
ct=1, SerialNumber=3
[    8.050190] usb 1-2: Product: USB 2.0 Camera
[    8.050334] usb 1-2: Manufacturer: Sonix Technology Co.,
Ltd.
[    8.050476] usb 1-2: SerialNumber: SN0001
[    8.061062] leds_ss4200: no LED devices found
[    8.124117] [drm] Memory usable by graphics device = 256M
[    8.124256] [drm] Replacing VGA console driver
[    8.125716] Console: switching to colour dummy device 80x
25
[    8.127378] [drm] Supports vblank timestamp caching Rev 2
 (21.10.2013).
[    8.127408] [drm] Driver supports precise vblank timestam
p query.
[    8.128898] vgaarb: device changed decodes: PCI:0000:00:0
2.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    8.162077] atl1c 0000:01:00.0: version 1.0.1.1-NAPI
[    8.163755] [drm] initialized overlay support
[    8.188756] fbcon: inteldrmfb (fb0) is primary device
[    8.192531] thermal LNXTHERM:00: registered as thermal_zo
ne0
[    8.192536] ACPI: Thermal Zone [TZ00] (62 C)
[    8.350817] snd_hda_codec_realtek hdaudioC0D0: autoconfig
 for ALC269: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[    8.350825] snd_hda_codec_realtek hdaudioC0D0:    speaker
_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    8.350831] snd_hda_codec_realtek hdaudioC0D0:    hp_outs
=1 (0x15/0x0/0x0/0x0/0x0)
[    8.350836] snd_hda_codec_realtek hdaudioC0D0:    mono: m
ono_out=0x0
[    8.350840] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[    8.350847] snd_hda_codec_realtek hdaudioC0D0:      Mic=0
x18
[    8.350853] snd_hda_codec_realtek hdaudioC0D0:      Inter
nal Mic=0x12
[    8.373958] input: HDA Intel Mic as /devices/pci0000:00/0
000:00:1b.0/sound/card0/input9
[    8.374386] input: HDA Intel Headphone as /devices/pci000
0:00/0000:00:1b.0/sound/card0/input10
[    8.884578] ath: phy0: ASPM enabled: 0x42
[    8.884585] ath: EEPROM regdomain: 0x60
[    8.884587] ath: EEPROM indicates we should expect a dire
ct regpair map
[    8.884593] ath: Country alpha2 being used: 00
[    8.884594] ath: Regpair used: 0x60
[    8.912219] ieee80211 phy0: Selected rate control algorit
hm 'minstrel_ht'
[    8.913414] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xf9
a20000, irq=17
[    8.972524] [drm] Initialized i915 1.6.0 20151010 for 000
0:00:02.0 on minor 0
[    8.972760] Console: switching to colour frame buffer dev
ice 128x37
[    9.031074] i915 0000:00:02.0: fb0: inteldrmfb frame buff
er device
[    9.189517] psmouse serio1: synaptics: queried max coordi
nates: x [..5808], y [..4842]
[    9.330782] psmouse serio1: synaptics: Touchpad model: 1,
 fw: 7.2, id: 0x1a0b1, caps: 0xd04733/0xa40000/0xa0000/0x0,
board id: 0, fw id: 570166
[    9.467856] input: SynPS/2 Synaptics TouchPad as /devices
/platform/i8042/serio1/input/input8
[   10.051904] asus_wmi: ASUS WMI generic driver loaded
[   10.161477] asus_wmi: Initialization: 0x0
[   10.165986] asus_wmi: BIOS WMI version: 0.5
[   10.170486] asus_wmi: SFUN value: 0x0
[   10.175776] i2c /dev entries driver
[   10.202844] input: Eee PC WMI hotkeys as /devices/platfor
m/eeepc-wmi/input/input11
[   10.208404] asus_wmi: Number of fans: 1
[   10.859221] cfg80211: World regulatory domain updated:
[   10.863631] cfg80211:  DFS Master region: unset
[   10.863746] cfg80211:   (start_freq - end_freq @ bandwidt
h), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   10.872599] cfg80211:   (2402000 KHz - 2472000 KHz @ 4000
0 KHz), (N/A, 2000 mBm), (N/A)
[   10.877197] cfg80211:   (2457000 KHz - 2482000 KHz @ 2000
0 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   10.881770] cfg80211:   (2474000 KHz - 2494000 KHz @ 2000
0 KHz), (N/A, 2000 mBm), (N/A)
[   10.886308] cfg80211:   (5170000 KHz - 5250000 KHz @ 8000
0 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   10.890821] cfg80211:   (5250000 KHz - 5330000 KHz @ 8000
0 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   10.895310] cfg80211:   (5490000 KHz - 5730000 KHz @ 1600
00 KHz), (N/A, 2000 mBm), (0 s)
[   10.899715] cfg80211:   (5735000 KHz - 5835000 KHz @ 8000
0 KHz), (N/A, 2000 mBm), (N/A)
[   10.904115] cfg80211:   (57240000 KHz - 63720000 KHz @ 21
60000 KHz), (N/A, 0 mBm), (N/A)
[   11.370190] Linux video capture interface: v2.00
[   11.608171] uvcvideo: Found UVC 1.00 device USB 2.0 Camer
a (13d3:5108)
[   11.621286] input: USB 2.0 Camera as /devices/pci0000:00/
0000:00:1d.7/usb1/1-2/1-2:1.0/input/input12
[   11.626212] usbcore: registered new interface driver uvcv
ideo
[   11.631060] USB Video Class driver (1.1.1)
[   11.876174] [drm] GMBUS [i915 gmbus dpd] timed out, falli
ng back to bit banging on pin 6
[   11.950162] [drm] GMBUS [i915 gmbus dpc] timed out, falli
ng back to bit banging on pin 4
[   12.302000] Adding 1100628k swap on /dev/sda2.  Priority:
-1 extents:1 across:1100628k
[   12.430685] fuse init (API version 7.23)
[   13.415582] EXT4-fs (sda1): re-mounted. Opts: (null)
[   21.710822] intel_rng: FWH not detected
[   21.730853] leds_ss4200: no LED devices found
[   29.862689] NET: Registered protocol family 10
[   36.586965] wlan0: authenticate with 60:38:e0:db:ad:7a
[   36.623144] wlan0: send auth to 60:38:e0:db:ad:7a (try 1/
3)
[   36.646214] wlan0: authenticated
[   36.647322] wlan0: associate with 60:38:e0:db:ad:7a (try
1/3)
[   36.676289] wlan0: RX AssocResp from 60:38:e0:db:ad:7a (c
apab=0x411 status=0 aid=7)
[   36.676460] wlan0: associated
[ 1257.628378] asus_wmi: Unknown key 57 pressed
[ 1288.351991] asus_wmi: Unknown key 58 pressed
root@eeewriter:/home/grant#
 
Old 10-27-2019, 11:53 AM   #40
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,634

Rep: Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929
@poetgrant

Nothing extraordinary in your kernel log and I believe it's worth trying to disable the framebuffer console.

Either try what enorbet suggested in #7:
- in /etc/lilo.conf modify the append line and add nomodeset:
Code:
append="vt.default_utf8=0 nomodeset"
- then, as root, run /sbin/lilo to update the bootloader
- & restart the system

Or, provide the i915 driver the modeset=0 parameter:
- create /etc/modprobe.d/i915.conf with the following content:
Code:
options i915 modeset=0
- & restart the system
 
1 members found this post helpful.
Old 10-27-2019, 02:31 PM   #41
poetgrant
Member
 
Registered: Feb 2019
Distribution: Slackware
Posts: 90

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by abga View Post
@poetgrant

Nothing extraordinary in your kernel log and I believe it's worth trying to disable the framebuffer console.

Either try what enorbet suggested in #7:
- in /etc/lilo.conf modify the append line and add nomodeset:
Code:
append="vt.default_utf8=0 nomodeset"
- then, as root, run /sbin/lilo to update the bootloader
- & restart the system

Or, provide the i915 driver the modeset=0 parameter:
- create /etc/modprobe.d/i915.conf with the following content:
Code:
options i915 modeset=0
- & restart the system
Oh dang... I want to try this. As soon as I get off work I'll try this... Man I hope this fixes it....


Also I did check, I'm not booting into runlevel 4. I never changed away from 3.

I'm going to try the modprobe first.
 
Old 10-27-2019, 06:26 PM   #42
0XBF
Member
 
Registered: Nov 2018
Distribution: Slackware
Posts: 795

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
Quote:
Originally Posted by Lysander666 View Post
This is one of those occasions whereby uploading your computer info to https://linux-hardware.org/ would probably be a big help, since it would tell you where the incompatibilities were with all your hardware and it will offer fixes where available.

Have a look at this thread:

https://www.linuxquestions.org/quest...rg-4175662855/

You could do all this at the command line [i.e. downloading hw-probe and its depends, making the package, installing it and uploading your info], as long as you are able to get to work in the command line once your computer has booted and you can connect to your network.

To make it easier, I've uploaded my own Slackware-compatible binary, so all you would have to do would be

Code:
wget https://filebin.net/3e6x7fhvmk84688r/hwprobe.txz
to get it, and then just install it and run the commands as given on the website.

EDIT: You may need hwinfo/libx86emu from SBo too.
I get "File format not recognized" and "corrupt archive" errors from that file you linked. I just got it from the github source instead and can confirm you need the hwinfo/libx86emu deps to make it work.

I also uploaded a probe of the 1000H if anyone wants to see the hardware on it. https://linux-hardware.org/index.php?probe=50da35c0d0

This also made me remember that I put a different wifi card in the eee back in 2009. Didn't recall that until I looked at this.
 
Old 10-27-2019, 06:47 PM   #43
poetgrant
Member
 
Registered: Feb 2019
Distribution: Slackware
Posts: 90

Original Poster
Rep: Reputation: 22
Quote:
Originally Posted by abga View Post
@poetgrant

Nothing extraordinary in your kernel log and I believe it's worth trying to disable the framebuffer console.

Either try what enorbet suggested in #7:
- in /etc/lilo.conf modify the append line and add nomodeset:
Code:
append="vt.default_utf8=0 nomodeset"
- then, as root, run /sbin/lilo to update the bootloader
- & restart the system

Or, provide the i915 driver the modeset=0 parameter:
- create /etc/modprobe.d/i915.conf with the following content:
Code:
options i915 modeset=0
- & restart the system
So I tried both options here and it didn't change anything. I really want to fix this before I decide to just reinstall from the USB drive I have. I'm installing hw-probe and all that, just in case.

One thing though... when I run /sbin/lilo it returns saying there was one warning. Do you know where those warnings are stored? Maybe that is a clue?
 
Old 10-27-2019, 07:20 PM   #44
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,634

Rep: Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929
Sorry to hear that the nomodeset workaround didn't work.

AFAIK, lilo warnings are only displayed and not stored, you should pay attention to them. You can reissue /sbin/lilo any times you like and focus on the warning.

If you want the older Slackware 14.2 kernel, the one you said it worked before, you don't need to reinstall the whole system. Just grab the kernel and the kernel modules from here (get the kernel-huge-smp-* and kernel-modules-smp-*):
https://mirror.de.leaseweb.net/slack...2/slackware/a/
(or any other mirror you prefer)
Install them and modify your lilo.conf to point to the old kernel.

But then, maybe you'd like to try a newer kernel, the one from -current, again, the kernel-huge-smp-* & kernel-modules-smp-* from:
https://mirror.de.leaseweb.net/slack...t/slackware/a/
 
Old 10-29-2019, 12:04 AM   #45
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,810

Rep: Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447
FWIW Lilo is pretty picky. It will generally fail even on fairly non serious errors. Warnings like "LBA32 is assumed" are generally inconsequential but easily solved. AFAIK they are not stored so just run /sbin/lilo again if you miss any for any reason.
 
  


Reply

Tags
boot failure, slackware 14.2



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Everytime I try to screen share, on both Skype and zoom my screen goes black joezero Linux - Newbie 3 07-31-2016 07:21 AM
[SOLVED] KDE crashes after splash screen, screen goes black juju Slackware 3 02-22-2013 03:33 PM
Booting CentOS 5, logo screen appears, stuff initializes, then screen goes black ctman Linux - Newbie 6 09-22-2007 08:36 AM
Screen goes to "grub>" black screen after trying to merge 2 drives Planet-Zhar Linux - General 4 06-20-2007 04:46 AM
screen saver goes off and screen goes black Doug.Gentry SUSE / openSUSE 2 03-26-2005 05:08 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:19 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration