You are not logged in.

Pages: 1

#1 2018-05-03 20:27:59

diederick76
Member
Registered: 2010-02-14
Posts: 169

ERROR: module not found: `uvesafb' [SOLVED]

Hi, I'm attempting to get a splash screen by following the steps on https://wiki.archlinux.org/index.php/Uvesafb, but when I get to the part where I regenerate the initramfs images of the kernel, that fails:

me@archbox ~> sudo mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.16.5-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [v86d]
==> ERROR: module not found: `uvesafb'
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.16.5-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [v86d]
==> ERROR: module not found: `uvesafb'
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.

Indeed, a find on uvesafb returns nothing:

me@archbox /u/l/m/4.16.5-1-ARCH> find . -name "*uvesafb*"
me@archbox /u/l/m/4.16.5-1-ARCH>

Even though most posts on this forum on this subject are about a decade old, the page itself was updated only this year. Is the uvesafb module not longer in the stock kernel?

Last edited by diederick76 (2018-05-03 20:58:08)

Offline

#2 2018-05-03 20:30:53

loqs
Member
Registered: 2014-03-06
Posts: 19,113

Re: ERROR: module not found: `uvesafb' [SOLVED]

Did you perform Uvesafb#Installation?

Offline

#3 2018-05-03 20:31:36

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 13,718
Website

Re: ERROR: module not found: `uvesafb' [SOLVED]

Please post the output of

dkms status

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#4 2018-05-03 20:36:01

diederick76
Member
Registered: 2010-02-14
Posts: 169

Re: ERROR: module not found: `uvesafb' [SOLVED]

Wow. You guys are fast!

Anyway,

loqs wrote:

Did you perform Uvesafb#Installation?

Yes.

WorMzy wrote:

Please post the output of

dkms status

Nothing:

me@archbox ~> dkms status
me@archbox ~>

Offline

#5 2018-05-03 20:41:27

loqs
Member
Registered: 2014-03-06
Posts: 19,113

Re: ERROR: module not found: `uvesafb' [SOLVED]

When you installed uvesafb-dkms did the module build successfully?
What is the output of `pacman -Q uvesafb-dkms`
Edit:
Also the output of `# dkms autoinstall`

Last edited by loqs (2018-05-03 20:43:56)

Offline

#6 2018-05-03 20:44:02

diederick76
Member
Registered: 2010-02-14
Posts: 169

Re: ERROR: module not found: `uvesafb' [SOLVED]

loqs wrote:

When you installed uvesafb-dkms did the module build successfully?

Yes.

loqs wrote:

What is the output of `pacman -Q uvesafb-dkms`

me@archbox ~> pacman -Q uvesafb-dkms
uvesafb-dkms 1.0.0-7

Offline

#7 2018-05-03 20:48:02

loqs
Member
Registered: 2014-03-06
Posts: 19,113

Re: ERROR: module not found: `uvesafb' [SOLVED]

In addition to the output of `# dkms autoinstall` what was the pacman.log contents for the last update including a kernel package?

Offline

#8 2018-05-03 20:48:54

diederick76
Member
Registered: 2010-02-14
Posts: 169

Re: ERROR: module not found: `uvesafb' [SOLVED]

Building uversafb-dkms:

me@archbox ~> yaourt -S uvesafb-dkms

==> Bezig met downloaden van de PKGBUILD van uvesafb-dkms uit AUR...
x .SRCINFO
x PKGBUILD
x dkms.conf
x modprobe.uvesafb
x v86d_hook
x v86d_install
karl_gerh commented on 2018-03-31 18:40			 

jghodd commented on 2018-03-31 19:22			 

jghodd commented on 2018-03-31 21:07			 

karl_gerh commented on 2018-04-01 20:02			 

Eschwartz commented on 2018-04-17 23:04			 

uvesafb-dkms 1.0.0-7  (2018-03-31 20:59)
( Niet-ondersteund pakket: mogelijk gevaarlijk ! )
==> PKGBUILD bewerken? [J/n] ("A" om af te breken)
==> ----------------------------------------------
==> n

==> uvesafb-dkms-afhankelijkheden:
 - glibc (reeds geïnstalleerd)
 - dkms>=2.2.0.3+git151023-5 (reeds geïnstalleerd)
 - git (reeds geïnstalleerd) [makedepend]


==> Wilt u doorgaan met het bouwen van uvesafb-dkms?[J/n]
==> -----------------------------------------------------
==> 

==> Bezig met bouwen en installeren van het pakket
==> Pakket uvesafb-dkms 1.0.0-7 (do  3 mei 2018 22:45:23 CEST) wordt gemaakt
==> Uitvoerafhankelijkheden controleren...
==> Afhankelijkheden voor creatie controleren
==> Bronnen ophalen...
  -> uvesafb-dkms git repo klonen...
Cloning into bare repository '/tmp/yaourt-tmp-me/aur-uvesafb-dkms/uvesafb-dkms'...
remote: Counting objects: 21, done.
remote: Compressing objects: 100% (17/17), done.
remote: Total 21 (delta 4), reused 6 (delta 2), pack-reused 0
Receiving objects: 100% (21/21), 24.77 KiB | 8.26 MiB/s, done.
Resolving deltas: 100% (4/4), done.
  -> v86d git repo klonen...
Cloning into bare repository '/tmp/yaourt-tmp-me/aur-uvesafb-dkms/v86d'...
remote: Counting objects: 414, done.
remote: Total 414 (delta 0), reused 0 (delta 0), pack-reused 414
Receiving objects: 100% (414/414), 206.13 KiB | 594.00 KiB/s, done.
Resolving deltas: 100% (244/244), done.
  -> v86d_install is gevonden
  -> v86d_hook is gevonden
  -> dkms.conf is gevonden
  -> modprobe.uvesafb is gevonden
==> Valideren van source bestanden met md5sums...
    uvesafb-dkms ... Overgeslaan
    v86d ... Overgeslaan
    v86d_install ... Geslaagd
    v86d_hook ... Geslaagd
    dkms.conf ... Geslaagd
    modprobe.uvesafb ... Geslaagd
==> Bronnen uitpakken...
  -> Een werkkopie van pakketlijst uvesafb-dkms git aan het aanmaken...
Cloning into 'uvesafb-dkms'...
done.
Switched to a new branch 'makepkg'
  -> Een werkkopie van pakketlijst v86d git aan het aanmaken...
Cloning into 'v86d'...
done.
Switched to a new branch 'makepkg'
==> Bezig met het uitvoeren van build()...
config.h successfully created.
You can run `make` now.
make -w -C libs/x86emu
make[1]: Map '/tmp/yaourt-tmp-me/aur-uvesafb-dkms/src/v86d/libs/x86emu' wordt binnengegaan
cc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -I/usr/include -Ilibs/x86emu -I. -I../../include -I../../include/x86emu -o decode.o decode.c
cc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -I/usr/include -Ilibs/x86emu -I. -I../../include -I../../include/x86emu -o fpu.o fpu.c
cc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -I/usr/include -Ilibs/x86emu -I. -I../../include -I../../include/x86emu -o ops.o ops.c
cc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -I/usr/include -Ilibs/x86emu -I. -I../../include -I../../include/x86emu -o ops2.o ops2.c
ops2.c: In functie ‘x86emuOp2_cpuid’:
ops2.c:393:5: let op: impliciete declaratie van functie ‘cpuid’ [-Wimplicit-function-declaration]
     cpuid();
     ^~~~~
cc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -I/usr/include -Ilibs/x86emu -I. -I../../include -I../../include/x86emu -o prim_ops.o prim_ops.c
cc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -I/usr/include -Ilibs/x86emu -I. -I../../include -I../../include/x86emu -o sys.o sys.c
ar rv libx86emu.a decode.o fpu.o ops.o ops2.o prim_ops.o sys.o
ar: creating libx86emu.a
a - decode.o
a - fpu.o
a - ops.o
a - ops2.o
a - prim_ops.o
a - sys.o
make[1]: Map '/tmp/yaourt-tmp-me/aur-uvesafb-dkms/src/v86d/libs/x86emu' wordt verlaten
cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -I/usr/include -Ilibs/x86emu -c -o v86_x86emu.o v86_x86emu.c
cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -I/usr/include -Ilibs/x86emu -c -o v86_mem.o v86_mem.c
cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -I/usr/include -Ilibs/x86emu -c -o v86_common.o v86_common.c
cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -I/usr/include -Ilibs/x86emu -c -o v86.o v86.c
cc -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Llibs/x86emu v86_x86emu.o v86_mem.o v86_common.o  v86.o -lx86emu -o v86d
==> Binnengaan van omgeving fakeroot...
==> Bezig met het uitvoeren van package()...
install -D v86d /tmp/yaourt-tmp-me/aur-uvesafb-dkms/pkg/uvesafb-dkms/sbin/v86d
==> Installatie opschonen...
  -> Verwijderen van libtool bestanden...
  -> Verwijderen van ongewenste bestanden...
  -> Bezig met het verwijderen van statische bibliotheekbestanden...
  -> Strippen van onnodige symbolen van uitvoerbare bestanden en bibliotheken...
  -> Comprimeren van man en info pagina's...
==> Controleren op probleem met pakketcreatie...
==> Pakket "uvesafb-dkms" aanmaken...
  -> Genereren van .PKGINFO bestand...
  -> Genereren van .BUILDINFO bestand...
  -> .MTREE bestand genereren...
  -> Pakket comprimeren...
==> fakeroot omgeving verlaten.
==> Klaar met het maken van: uvesafb-dkms 1.0.0-7 (do  3 mei 2018 22:45:29 CEST)
==> Opruimen...

==> Wilt u doorgaan met het installeren van uvesafb-dkms? [J/n]
==> [v]pakketinhoud weergeven [c]pakket controleren met namcap
==> ----------------------------------------------------------
==> 

pakketten laden...
waarschuwing:uvesafb-dkms-1.0.0-7 is up to date -- opnieuw installeren
afhankelijkheden oplossen...
zoeken naar conflicterende pakketten...

Pakketten (1) uvesafb-dkms-1.0.0-7

Totale Geïnstalleerde Grootte:   0,17 MiB
Netto Upgrade Grootte:           0,00 MiB

:: Doorgaan met de installatie? [J/n] 
(1/1) sleutels in sleutelbos controleren                        [##################################] 100%
(1/1) pakketintegriteit controleren                             [##################################] 100%
(1/1) pakketbestanden laden                                     [##################################] 100%
(1/1) controleren van conflicterende bestanden                  [##################################] 100%
(1/1) beschikbare schijfruimte controleren                      [##################################] 100%
:: Uitvoeren pre-transactie hooks...
(1/1) Remove DKMS modules
==> No kernel 4.16.5-1-ARCH headers. You must install them to use DKMS!
:: Pakketveranderingen verwerken...
(1/1) herinstalleren uvesafb-dkms                               [##################################] 100%
:: Uitvoeren na-transactie hooks...
(1/3) Install DKMS modules
==> No kernel 4.16.5-1-ARCH headers. You must install them to use DKMS!
(2/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.16.5-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.16.5-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
(3/3) Arming ConditionNeedsUpdate...
me@archbox ~>

Offline

#9 2018-05-03 20:50:26

diederick76
Member
Registered: 2010-02-14
Posts: 169

Re: ERROR: module not found: `uvesafb' [SOLVED]

loqs wrote:

In addition to the output of `# dkms autoinstall` what was the pacman.log contents for the last update including a kernel package?

This is a new installation. I have not done a kernel update yet.

# dkms autoinstall doesn't return anything either.

Last edited by diederick76 (2018-05-03 20:53:21)

Offline

#10 2018-05-03 20:52:04

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 13,718
Website

Re: ERROR: module not found: `uvesafb' [SOLVED]

==> No kernel 4.16.5-1-ARCH headers. You must install them to use DKMS!

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#11 2018-05-03 20:52:31

loqs
Member
Registered: 2014-03-06
Posts: 19,113

Re: ERROR: module not found: `uvesafb' [SOLVED]

==> No kernel 4.16.5-1-ARCH headers. You must install them to use DKMS!

DKMS built nothing as there were no headers provided so you have no module.
edit:
too slow beaten by WorMzy

Last edited by loqs (2018-05-03 20:53:39)

Offline

#12 2018-05-03 20:57:54

diederick76
Member
Registered: 2010-02-14
Posts: 169

Re: ERROR: module not found: `uvesafb' [SOLVED]

Thanks both of you! That helped. Perhaps I should learn to read ;-)

Offline

Pages: 1

Board footer

Powered by FluxBB