On 06/05/2015 02:16 AM, to...@tuxteam.de wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Jun 04, 2015 at 05:54:40PM -0500, Jose Martinez wrote:
I forgot to mention in my last post, when I attempted to install the
old driver from broadcom which I have used before, I get the
message:
insmod: ERROR: could not insert module wl.ko: Invalid module format
This has not happened in the past, it just installed and worked fine.]
This means that the module was compiled for a different version (or for a
significantly different configuration) of the kernel you're trying to
feed the module to. You can look int that with modinfo (lives in /sbin):
tomas@rasputin:~$ /sbin/modinfo
/lib/modules/3.2.0-3-amd64/kernel/drivers/net/ethernet/atheros/atlx/atl1.ko
filename:
/lib/modules/3.2.0-3-amd64/kernel/drivers/net/ethernet/atheros/atlx/atl1.ko
version: 2.1.3
license: GPL
author: Xiong Huang <xiong.hu...@atheros.com>, Chris Snook
<csn...@redhat.com>, Jay Cliburn <jclib...@gmail.com>
description: Atheros L1 Gigabit Ethernet Driver
srcversion: 21557C61B6BC6DA20309204
alias: pci:v00001969d00001048sv*sd*bc*sc*i*
depends: mii
intree: Y
vermagic: 3.2.0-3-amd64 SMP mod_unload modversions
parm: int_mod_timer:Interrupt moderator timer (array of int)
parm: debug:Message level (0=none,...,16=all) (int)
HTH
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlVxTL0ACgkQBcgs9XrR2kY2LgCfXE3YhQ+K5h7SkT3TzuWZP1TE
otQAnRNKAyY8DuXes+L0zaL656RsDvyV
=mXfq
-----END PGP SIGNATURE-----
I understand. It is true that this driver was compiled back in August
under Wheezy. What I do find interesting is that I know that this
driver was working on a system upgraded from Wheezy to Jessie. However,
with a clean install of Jessie, it does not.
Nevertheless, the problem was solved when I got the original Jessie
kernel, without my tramping around messing it up, and installed the
firmware-b43-install package. I didn't think that that had worked
because I forgot the necessary step of rebooting after the
installation. The driver automatically uploads the firmware to the chip
at boot up, and since I didn't reboot, the firmware did not get uploaded
and it did not work. Once I rebooted, everything came out fine. In
fact, this post is being sent through that BC4321 chip to my wireless
network. (I was wired yesterday.)
--
JM
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55721838.8080...@gmail.com
