Error at bootup: modprobe: bad line 1: 1 tokens found, 2 needed

linustalman · 03-23-2017, 02:37 PM

Hi.

I get this error at bootup. I use LUKS.

Code:

modprobe: bad line 1: 1 tokens found, 2 needed

It does not seem to be causing any issue but I'd prefer it to be remedied.

Any tips?

Thanks.

cyent · 03-23-2017, 09:46 PM

Any clues on which line?

Probably something in /etc/modprobe.d/

Some more context from dmesg or journalctl may help

linustalman · 03-24-2017, 09:56 AM

Quote:

Originally Posted by cyent

Any clues on which line?

Probably something in /etc/modprobe.d/

Some more context from dmesg or journalctl may help

Hi cyent.

I ran dmesg & journalctl as root but they gave massive outputs.

In /etc/modprobe.d/dkms.conf I see 'modprobe' mentioned.

Contents:

Code:

# modprobe information used for DKMS modules
#
# This is a stub file, should be edited when needed,
# used by default by DKMS.

linustalman · 03-24-2017, 10:00 AM

I'm don't think the error has anything to do with LUKS but I see the error on the screen where I enter the LUKS passphrase.

cyent · 03-26-2017, 03:50 PM

journalctl usually feeds to a pager like less, so you can search for the error line.

/bad line

And then paste the couple of lines around that here and we might have something to work on.

linustalman · 03-28-2017, 08:26 AM

Here's a screen grab of the error.

linustalman · 03-28-2017, 08:29 AM

Quote:

Originally Posted by cyent

journalctl usually feeds to a pager like less, so you can search for the error line.

/bad line

And then paste the couple of lines around that here and we might have something to work on.

I ran sudo journalctl > 1.txt but found no "/bad line"

cyent · 03-28-2017, 03:00 PM

Also search the output of dmesg and journalctl for anything to do with modprobe.

linustalman · 03-29-2017, 02:39 PM

Quote:

Originally Posted by cyent

Also search the output of dmesg and journalctl for anything to do with modprobe.

Tried both - no mentions.

cyent · 03-29-2017, 03:34 PM

Ok.

lsmod

Then sudo modprobe XXXX

where XXXX is any module in the list.

Hopefully it will output that error message.

It it does give you the error message, but not a clue, try

sudo strace modprobe XXXX

Else let's hit it with a LARGE hammer.

lsmod | cut -d ' ' -f 1 | tail -n +2 | xargs -n 1 echo modprobe | sudo bash -x

That will hopefully force modprobe to try probe every module in your system

Hopefully something will trigger the error message.

linustalman · 03-30-2017, 02:03 PM

Quote:

Originally Posted by cyent

...

Else let's hit it with a LARGE hammer.

lsmod | cut -d ' ' -f 1 | tail -n +2 | xargs -n 1 echo modprobe | sudo bash -x

...

Could that line do harm?

linustalman · 03-30-2017, 02:05 PM

Quote:

Originally Posted by cyent

Ok.

lsmod

Then sudo modprobe XXXX

where XXXX is any module in the list.

...

What module? I'm confused. *_*

I might just let this thread go as I will switch to Debian 9 soon anyway.

cyent · 03-30-2017, 02:11 PM

The linux kernel has parts of it, called modules, that you can load and unload at runtime. (And this is true for whichever distro you use)

lsmod list the ones currently installed.

Loading a module you don't need is harmless, except in the sense it wastes ram.

Older versions of the kernel (and even current ones if you choose to configure it so) simply compiled in the modules at link time and left them there.

The module conf files just allow to set various parameters on the modules when you load them.

You can set those parameters explicitly when you use insmod to load a specific module.

modprobe will load a module AND EVERYTHING IT DEPENDS ON. ie. You can't put the parameters for all the modules it might load on the command line as you don't know what it will load.

linustalman · 03-31-2017, 08:33 AM

Thanks for sticking by Cyent.

Code:

lsmod | cut -d ' ' -f 1 | tail -n +2 | xargs -n 1 echo modprobe | sudo bash -x

Output:

Code:

+ modprobe rt73usb
+ modprobe rt2x00usb
+ modprobe rt2x00lib
+ modprobe crc_itu_t
+ modprobe ctr
+ modprobe ccm
+ modprobe cpufreq_userspace
+ modprobe cpufreq_powersave
+ modprobe cpufreq_conservative
+ modprobe binfmt_misc
+ modprobe ip6t_REJECT
+ modprobe nf_reject_ipv6
+ modprobe nf_log_ipv6
+ modprobe xt_hl
+ modprobe nfsd
+ modprobe auth_rpcgss
+ modprobe nfs_acl
+ modprobe ip6t_rt
+ modprobe nfs
+ modprobe lockd
+ modprobe grace
+ modprobe fscache
+ modprobe nf_conntrack_ipv6
+ modprobe nf_defrag_ipv6
+ modprobe sunrpc
+ modprobe ipt_REJECT
+ modprobe nf_reject_ipv4
+ modprobe nf_log_ipv4
+ modprobe nf_log_common
+ modprobe xt_LOG
+ modprobe xt_limit
+ modprobe xt_tcpudp
+ modprobe xt_addrtype
+ modprobe nf_conntrack_ipv4
+ modprobe nf_defrag_ipv4
+ modprobe xt_conntrack
+ modprobe ip6table_filter
+ modprobe ip6_tables
+ modprobe nf_conntrack_netbios_ns
+ modprobe nf_conntrack_broadcast
+ modprobe nf_nat_ftp
+ modprobe nf_nat
+ modprobe nf_conntrack_ftp
+ modprobe nf_conntrack
+ modprobe iptable_filter
+ modprobe ip_tables
+ modprobe x_tables
+ modprobe arc4
+ modprobe rtl8192cu
+ modprobe rtl_usb
+ modprobe rtl8192c_common
+ modprobe rtlwifi
+ modprobe mac80211
+ modprobe cfg80211
+ modprobe intel_rapl
+ modprobe snd_hda_codec_hdmi
+ modprobe x86_pkg_temp_thermal
+ modprobe intel_powerclamp
+ modprobe nouveau
+ modprobe coretemp
+ modprobe snd_hda_codec_realtek
+ modprobe snd_hda_codec_generic
+ modprobe kvm_intel
+ modprobe snd_hda_intel
+ modprobe snd_hda_codec
+ modprobe kvm
+ modprobe snd_hda_core
+ modprobe snd_hwdep
+ modprobe mxm_wmi
+ modprobe ttm
+ modprobe snd_pcm
+ modprobe snd_timer
+ modprobe drm_kms_helper
+ modprobe eeepc_wmi
+ modprobe asus_wmi
+ modprobe drm
+ modprobe snd
+ modprobe sparse_keymap
+ modprobe iTCO_wdt
+ modprobe irqbypass
+ modprobe intel_cstate
+ modprobe soundcore
+ modprobe i2c_algo_bit
+ modprobe rfkill
+ modprobe iTCO_vendor_support
+ modprobe intel_uncore
+ modprobe evdev
+ modprobe serio_raw
+ modprobe intel_rapl_perf
+ modprobe ie31200_edac
+ modprobe mei_me
+ modprobe pcspkr
+ modprobe edac_core
+ modprobe wmi
+ modprobe lpc_ich
+ modprobe mfd_core
+ modprobe battery
+ modprobe shpchp
+ modprobe video
+ modprobe mei
+ modprobe i2c_i801
+ modprobe i2c_smbus
+ modprobe button
+ modprobe tpm_tis
+ modprobe tpm_tis_core
+ modprobe tpm
+ modprobe fuse
+ modprobe parport_pc
+ modprobe ppdev
+ modprobe lp
+ modprobe parport
+ modprobe autofs4
+ modprobe ext4
+ modprobe crc16
+ modprobe jbd2
+ modprobe fscrypto
+ modprobe mbcache
+ modprobe algif_skcipher
+ modprobe af_alg
+ modprobe dm_crypt
+ modprobe dm_mod
+ modprobe sr_mod
+ modprobe cdrom
+ modprobe sg
+ modprobe sd_mod
+ modprobe hid_generic
+ modprobe usbhid
+ modprobe uas
+ modprobe ata_generic
+ modprobe hid
+ modprobe usb_storage
+ modprobe crct10dif_pclmul
+ modprobe crc32_pclmul
+ modprobe crc32c_intel
+ modprobe ghash_clmulni_intel
+ modprobe aesni_intel
+ modprobe aes_x86_64
+ modprobe lrw
+ modprobe gf128mul
+ modprobe glue_helper
+ modprobe ablk_helper
+ modprobe cryptd
+ modprobe ata_piix
+ modprobe libata
+ modprobe xhci_pci
+ modprobe ehci_pci
+ modprobe xhci_hcd
+ modprobe ehci_hcd
+ modprobe scsi_mod
+ modprobe usbcore
+ modprobe r8169
+ modprobe mii
+ modprobe usb_common
+ modprobe thermal
+ modprobe fan
+ modprobe fjes

cyent · 04-02-2017, 04:12 PM

Weird. No error message.

Anything generated by that command in either dmesg or journalctl?