SliTaz SliTaz Forum

You are not logged in.

#1 2018-03-22 02:58:22

TraceE
Member
Registered: 2014-02-02
Posts: 112

3.16.55 problems

Upgraded to 3.16.55 and now I have no wifi (Ralink mt7601Usta) and cannot compile kernel module for it.

I have tried to use previous.gz and can boot it but upgrading to 3.16.55 has deleted all my previous kernel modules for 3.2.98 ... sad

Is there any way I can re-install 3.2.98 with it's associated modules?

Offline

#2 2018-03-22 03:10:29

aledie
Member
Registered: 2018-02-21
Posts: 58

Re: 3.16.55 problems

This is strange, in my case reverting to previous.gz worked (also to fix wifi).

If you have previous.gz at all, means you run your slitaz in live USB mode, not HD install. Which means your whole old root FS of 3.2.98 should be in this previous.gz, including kernel modules. The only folder likely got modified after the upgrade was your /home partition (which saves changes to USB) with personal configs saved in /home/tux... So wondering why using previous.gz doesn't work for you.

But I'm too new to slitaz cannot say for sure, just thinking

Offline

#3 2018-03-22 05:57:23

TraceE
Member
Registered: 2014-02-02
Posts: 112

Re: 3.16.55 problems

Yes ... that's a new one for me too ... previous.gz has always worked before here in the past but this time it didn't.

I run a Frugal install of Slitaz from inside a Full install of Slitaz on harddisk so it runs from Ram ... that's probably what makes the difference.

Anyway I've got 3.16.55 kind of working now with a different older (not great) wifi adapter but still can't compile a driver module for my favourite mt7601u adapter.

Offline

#4 2018-03-22 08:53:06

TraceE
Member
Registered: 2014-02-02
Posts: 112

Re: 3.16.55 problems

All fixed now ... smile

Just needed a newer driver to compile properly with the 3.16.55 kernel.

Not easy to find for mt7601u adapter ... thank goodness for Github!

Offline

#5 2018-03-22 11:58:11

shelleyfrank
Member
Registered: 2015-04-04
Posts: 10

Re: 3.16.55 problems

Hi, I am also affected by the latest update, and I would like to keep this topic open until it is resolved. I have upgraded my Slitaz packages, and I have a similar problem now. My bootscript shows the following:

[c]

Loading Kernel modules...

Loading module: i915                                                  modprobe: ERROR: ctx=0x8058008 path=/lib/modules/3.2.98-slitaz64/kernel/drivers/char/agp/intel-agp.ko.xz error=No such file or directory

modprobe: ERROR: ctx=0x8058008 path=/lib/modules/3.2.98-slitaz64/kernel/drivers/char/agp/intel-agp.ko.xz error=No such file or directory

modprobe: ERROR: could not insert 'i915': Unknown symbol in module, or unknown parameter (see dmesg)

                                                                      [ Failed ]

Loading module: intel_agp                                             modprobe: ERROR: ctx=0x8058008 path=/lib/modules/3.2.98-slitaz64/kernel/drivers/char/agp/intel-gtt.ko.xz error=No such file or directory

modprobe: ERROR: ctx=0x8058008 path=/lib/modules/3.2.98-slitaz64/kernel/drivers/char/agp/intel-gtt.ko.xz error=No such file or directory

modprobe: ERROR: could not insert 'intel_agp': Unknown symbol in module, or unknown parameter (see dmesg)

                                                                      [ Failed ]

Loading module: iwlwifi                                               modprobe: ERROR: ctx=0x8058008 path=/lib/modules/3.2.98-slitaz64/kernel/net/mac80211/mac80211.ko.xz error=No such file or directory

modprobe: ERROR: ctx=0x8058008 path=/lib/modules/3.2.98-slitaz64/kernel/net/mac80211/mac80211.ko.xz error=No such file or directory

modprobe: ERROR: could not insert 'iwlwifi': Unknown symbol in module, or unknown parameter (see dmesg)

                                                                      [ Failed ]

Loading module: snd_hda_intel                                         modprobe: ERROR: ctx=0x8058008 path=/lib/modules/3.2.98-slitaz64/kernel/sound/pci/hda/snd-hda-codec.ko.xz error=No such file or directory

modprobe: ERROR: ctx=0x8058008 path=/lib/modules/3.2.98-slitaz64/kernel/sound/pci/hda/snd-hda-codec.ko.xz error=No such file or directory

modprobe: ERROR: could not insert 'snd_hda_intel': Unknown symbol in module, or unknown parameter (see dmesg)

                                                                      [ Failed ]

[/c]

So, I don't have wifi and my screen driver doesn't load. All text is very large on screen, and mouse pointer flickers.

I am running Slitaz as a full HD installation, and I don't know how to make use of the above instructions regarding .gz archives. Can anyone please offer help to either roll back to previous linux64 kernel and modules, or provide a new build .tazpkg

Offline

#6 2018-03-22 19:52:44

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: 3.16.55 problems

@shelleyfrank

You could be booting into the old kernel vmlinuz-3.2.98-slitaz64

The 3.2.98 kernel is trying to load the 3.2.98 kernel modules that were removed in the update.

Loading module: i915 modprobe: ERROR: ctx=0x8058008 path=/lib/modules/3.2.98-slitaz64/kernel/drivers/char/agp/intel-agp.ko.xz error=No such file or directory

Check the running kernel version:

[c]uname -a[/c]

If it is booting into 3.2.98, verify the new 3.16.55 kernel and modules are on your system.

[c]ls /boot[/c]

vmlinuz-3.16.55-slitaz64

[c]ls /lib/modules[/c]

3.16.55-slitaz64

Edit your bootloader configuration to point to /boot/vmlinuz-3.16.55-slitaz64

The /home/boot/previous.gz is only on frugal installs where [c]tazusb writefs gz[/c] is used for persistence of updates to rootfs. Does not apply to full installs.

Offline

#7 2018-03-23 12:31:35

shelleyfrank
Member
Registered: 2015-04-04
Posts: 10

Re: 3.16.55 problems

@mojo

Thanks for your response. That is exactly what happened here. I booted into the old kernel. I updated grub from within a Linux Mint session, and I could boot into the new Slitaz kernel after reboot. Problem solved, thanks.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.023 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]