Download | Devuan.org | Git | Bugs | Packages

The officially official Devuan Forum!

You are not logged in.

Pages: 1

#1 Hardware & System Configuration » Probably missing nouveau driver » 2022-02-16 09:27:29

user9898
Replies: 2

Hello community,

My retro devuan 'chimaera' box is complaing about missing 'nouveau driver'

[   15.415139] nouveau 0000:02:00.0: firmware: failed to load nouveau/nv98_fuc084 (-2)
[   15.415147] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[   15.415150] nouveau 0000:02:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2
[   15.415161] nouveau 0000:02:00.0: firmware: failed to load nouveau/nv98_fuc084d (-2)
[   15.415162] nouveau 0000:02:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2
[   15.415165] nouveau 0000:02:00.0: msvld: unable to load firmware data
[   15.415167] nouveau 0000:02:00.0: msvld: init failed, -19

According to this link
https://ubuntu.pkgs.org/18.04/ubuntu-mu … l.deb.html

The missing package's name should be 'nouveau-firmware'

However when I do a apt search for such a package.
I get zero hits back.

The missing firmware files should be in
/lib/firmware/nouveau/

However when I check for a nouveau folder under /lib/firmware
There is no folder called nouveau #

Questions:

In which repo do I need to look for the missing file name ?
Also since I am debian sources as a refernce.
Are there any diferent package name differences, which could also a reason for the missing firmware ?

Here is copy of sources list file just in case, if we need to double check them

sudo cat /etc/apt/sources.list
## package repositories
deb http://deb.devuan.org/merged chimaera main contrib non-free
#deb http://deb.devuan.org/merged beowulf main  
deb http://deb.devuan.org/merged chimaera-updates main contrib non-free
#deb http://deb.devuan.org/merged beowulf-updates main  
deb http://deb.devuan.org/merged chimaera-security main contrib non-free  
#deb http://deb.devuan.org/merged beowulf-security main  

#deb http://deb.devuan.org/merged chimaera main non-free contrib

#deb http://deb.devuan.org/merged beowulf-backports main  
## source repositories
#deb-src http://deb.devuan.org/merged beowulf main  
#deb-src http://deb.devuan.org/merged beowulf-updates main  
#deb-src http://deb.devuan.org/merged beowulf-security main  
#deb-src http://deb.devuan.org/merged beowulf-backports main

#2 Re: ARM Builds » no ip address via DHCP » 2021-12-09 10:07:39

user9898

TTY4?
How do I please gain access to it ?
Is that via key combination such as 'ALT +F4" ?

the installer log for any relevant error messages

I am not sure if the installer generates any log files.
I guess this question is for someone, who is more in depth familiar with the installer 'under the hood'.

Have you tried assigning static addresses manually?

Yes, I also did try to set a static IP address - unfortunately also without any luck.

The actual URL from which you downloaded the "Net_boot image" would probably be useful. Ambiguity is almost always bad.

I downloaded the image from the this location
https://pkgmaster.devuan.org/devuan/dis … rd-images/
However I had to built my image from two separate components.

You need to get 2 files from http://deb.devuan.org/devuan/dists/beow … rd-images/ :
    firmware.Lamobo_R1.img.gz
    partition.img.gz

2) No, dont extract them separately just follow the section 'NETBOOT IMAGE CREATION' on  http://arm-files.devuan.org/README.txt:
    After you downloaded those files, you will create the final image following this command, in the order bellow:
    zcat firmware.Lamobo_R1.img.gz partition.img.gz > Lamobo_R1.img

#3 ARM Builds » no ip address via DHCP » 2021-12-08 10:47:28

user9898
Replies: 3

Hello community,

I am trying to install Chimaera on my Lamobo_R1  board with the Net_boot image.
However the clock in the top right hand corner shows January 1st which makes me assume that the clock might be again stuck at 1970.
When the installer dialog comes to the network setup section, the installer ends up unable to detect any ip address via DHCP.

I already tried a few different USB NICs, without any success. However if I do plug in a lan cable directly or to a USB NIC, each time the leds do come up. However the installer can not receive a IP address.
My personal guess is therefore the clock which is probably stuck at 1970.
Can anyone please advise me to how to resolve this problem?

thx,user9898

#4 Re: ARM Builds » DHCP client problems after upgrade to Chimaera » 2021-09-02 08:31:38

user9898

Thx alot for the link, about the switching interface. I take look at it once I have the time for it.

Right now, there are two last items of iritation left, concerning  the 'non-free contrib' entry in my sources lists.

if my source-list file looks like this 

 1 deb http://deb.devuan.org/merged chimaera main
 2 #deb-src http://deb.devuan.org/merged chimaera main
 3
 4 deb http://deb.devuan.org/merged chimaera-security main
 5 #deb-src http://deb.devuan.org/merged chimaera-security main
 6
 7 # beowulf-updates, previously known as 'volatile'
 8 deb http://deb.devuan.org/merged chimaera-updates main
 9 #deb-src http://deb.devuan.org/merged chimaera-updates main
10
11 deb http://deb.devuan.org/merged chimaera main non-free contrib
12

apt complains to me like so:

13 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-de_DE) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-de) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-de_DE) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-de) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11

I therefore disabled the first entry in line 1.

Hope that is correct.

The second one is, if it should say beowolf or chimaera in the last line.

#5 Re: ARM Builds » DHCP client problems after upgrade to Chimaera » 2021-08-28 16:24:57

user9898

Hello tuxd3v

How have you done the upgrade from beowulf to chimaera?

I upgraded to to chimaera by editing the sources.list.
to so

  GNU nano 5.4                           /etc/apt/sources.list                                     
# deb http://deb.devuan.org/merged beowulf main

deb http://deb.devuan.org/merged chimaera main
deb-src http://deb.devuan.org/merged chimaera main

deb http://deb.devuan.org/merged chimaera-security main
deb-src http://deb.devuan.org/merged chimaera-security main

# beowulf-updates, previously known as 'volatile'
deb http://deb.devuan.org/merged chimaera-updates main
deb-src http://deb.devuan.org/merged chimaera-updates main

What is your hardware board?

The name of the board is a Lamobo R1 by Leemaker

Some source's also call it BPI-R1 http://www.banana-pi.org/r1.html

I finally managed to establish some connectivity by using one of my old USB Nic interfaces, luckly I found one with a none Realtek chip.
Next I created a udev rule to give this new interface a custom name for  better control over it.

From there I kept missing add a extra entry into the interface file.
eg let's say I gave the new interface the name of 'eth-x' I than forgot to add a extra line for eth-x.

iface eth-x inet dhcp

Once I added that line, the service networking restart, finally picked the new interface up and included it in the DHCP process.

Also thank you for the hint about 

 main non-free contrib

I was actually missing that enty.
I added it like so

deb http://deb.devuan.org/merged beowulf main non-free contrib

Hopefully that is correct for Chimaera? Or should it say instead of Beowolf or Chimaera ?

#6 Re: ARM Builds » DHCP client problems after upgrade to Chimaera » 2021-08-27 14:27:25

user9898

Hello tuxd3v and community,
I am dealing with two parts of one problem here.
First is the RTC which is set to 1970 once the board boots up.
I am currently looking for ways to set it up manually and to store the time information in such a way that the RTC will be set to the correct time after a reboot.
Once the RTC problem is resolved the board should be able to receive IP Addresses via DHCP.

The second problem is the missing realtek driver.
Since the board, in it current state, can not communicative to the web, it therefore can not download any firmware updates.
Nor with a dynamic IP address or with a manually set one

One solution could be to download the driver it manually as a .deb file.
The problem here is that I do not know on which server and path to look for it.

Another solution could be to built the package myself,with debuild.
Her another problem would be the architecture.
Since I am not very experienced with debuild.

Thx,user9898

#7 Re: ARM Builds » DHCP client problems after upgrade to Chimaera » 2021-08-24 15:18:20

user9898
ralph.ronnquist wrote:

I think you should comment out that second eth0 configuration; if you need both ipv4 and ipv6 you'll need to combine them into a single configuration block, e.g. with "up" statements dealing with ipv6.

Do you have files in /etc/network/interfaces.d/ ? Where do the vlan adapters come from .. or what they are? Eg wan@eth0

EDIT: it looks like some kind of "openwrt" setup; could you post /etc/config/network if you have one?

No, I do not have any files in  /etc/network/interfaces.d/
I changed to the configurating to this.

cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#iface eth0 inet dhcp
iface eth0 inet static
address 192.168.178.37
netmask 255.255.255.0
gateway 192.168.178.1

#8 Re: ARM Builds » DHCP client problems after upgrade to Chimaera » 2021-08-24 15:10:19

user9898
Head_on_a_Stick wrote:

Have you tried removing the IPv6 configuration? Do you need IPv6?

I did not try to remove the IPv6, but I no problem removing it.
Since I can always add it back to the system.
Do static addresses work? My old router used to "run out" of DHCP slots so perhaps check that as well.

I usually tell my router to use DHCP and on top of that I tell it to, to always issue the same IPs to the devices, otherwise all of port-forward settings would end up in a major mess.

#9 Re: ARM Builds » DHCP client problems after upgrade to Chimaera » 2021-08-23 10:55:40

user9898

Yes, there is a cable pluged-in.

cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto
blub@r1-devuan/etc/network$

#10 ARM Builds » DHCP client problems after upgrade to Chimaera » 2021-08-23 09:09:56

user9898
Replies: 13

Hello community,

I upgraded my Devuan release from Beowolf to Chimaera.
and the DHCP client is having trouble receiving the IP address.
Here is my outpout.

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1504 qdisc mq state UP group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
    inet6 fe80::88:4ff:fe81:d20a/64 scope link 
       valid_lft forever preferred_lft forever
3: lan2@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
4: lan3@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
5: lan4@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
6: wan@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
7: lan1@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
8: wlx3c330047d226: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 3c:33:00:47:d2:26 brd ff:ff:ff:ff:ff:ff
blub@r1-devuan~$ sudo service networking restart
[sudo] Passwort für blub: 
Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning).
Reconfiguring network interfaces...Killed old client process
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/02:88:04:81:d2:0a
Sending on   LPF/eth0/02:88:04:81:d2:0a
Sending on   Socket/fallback
DHCPRELEASE of 192.168.178.37 on eth0 to 192.168.178.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
dhclient.c:2879: Failed to send 300 byte long packet over fallback interface.
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/02:88:04:81:d2:0a
Sending on   LPF/eth0/02:88:04:81:d2:0a
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
eDHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
blub@r1-devuan~$ e

Hopefully someone can please help.

Thx,user9898

#11 Re: ARM Builds » [SOLVED] rtl8192cu firmware problems » 2021-08-12 13:01:03

user9898

OH NO!!!
How could I miss that?!?
Yeah after installing ntp and ntpstat, the apt updates stopped complaining. And the 'apt search' also finally found the firmware-realtek package.

sudo dmesg | grep rtl
[sudo] Passwort für blub: 
[   14.608807] rtl8192cu: Chip version 0x11
[   14.693743] rtl8192cu: Board Type 0
[   14.693967] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[   14.694120] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[   14.699182] usb 2-1: firmware: direct-loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[   14.730992] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[   14.732495] usbcore: registered new interface driver rtl8192cu
[   14.751520] rtl8192cu 2-1:1.0 wlx3c330047d226: renamed from wlan0

Feeling like the idiot of the day here.aaarrghh!!!

#12 Re: ARM Builds » [SOLVED] rtl8192cu firmware problems » 2021-08-12 08:19:30

user9898

hi,
The ' / -maxdepth 4 -name rtl8192cufw_TMSC.bin -o -name rtl8192cufw.bin'
comes up with nothing.

And when I do a 'apt search' for the packag 'firmware-realtek' I also do get zero results back.

How should my 'sources list' look like

I changed to the following format.

# deb http://deb.devuan.org/merged beowulf main

deb http://deb.devuan.org/merged beowulf main contrib non-free
deb-src http://deb.devuan.org/merged beowulf main contrib non-free

deb http://deb.devuan.org/merged beowulf-security main contrib non-free
deb-src http://deb.devuan.org/merged beowulf-security main contrib non-free

# beowulf-updates, previously known as 'volatile'
deb http://deb.devuan.org/merged beowulf-updates main
deb-src http://deb.devuan.org/merged beowulf-updates main

Copying  the Debian format.
Hope that is correct.
But than I am also getting some strange error's when I am running a 'sudo apt update'

sudo apt update 
Holen:1 http://deb.devuan.org/merged beowulf InRelease [33,8 kB]
Holen:2 http://deb.devuan.org/merged beowulf-security InRelease [26,3 kB]
Holen:3 http://deb.devuan.org/merged beowulf-updates InRelease [26,7 kB]
Paketlisten werden gelesen... Fertig 
E: Release file for http://deb.devuan.org/merged/dists/beowulf/InRelease is not valid yet (invalid for another 18847 d 11 h 0 min 35 s). Updates for this repository will not be applied.
E: Release file for http://deb.devuan.org/merged/dists/beowulf-security/InRelease is not valid yet (invalid for another 18847 d 11 h 0 min 42 s). Updates for this repository will not be applied.
E: Release file for http://deb.devuan.org/merged/dists/beowulf-updates/InRelease is not valid yet (invalid for another 18847 d 11 h 0 min 42 s). Updates for this repository will not be applied.
blub@r1-devuan:~$

#13 Re: ARM Builds » [SOLVED] rtl8192cu firmware problems » 2021-08-11 14:51:35

user9898

Here is the request dmesg output

sudo dmesg | grep wifi
[   15.327210] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[   15.329000] usb 2-1: firmware: failed to load rtlwifi/rtl8192cufw_TMSC.bin (-2)
[   15.345792] usb 2-1: Direct firmware load for rtlwifi/rtl8192cufw_TMSC.bin failed with error -2
[   15.346165] usb 2-1: firmware: failed to load rtlwifi/rtl8192cufw.bin (-2)
[   15.353159] usb 2-1: Direct firmware load for rtlwifi/rtl8192cufw.bin failed with error -2
[   15.353182] rtlwifi: Loading alternative firmware rtlwifi/rtl8192cufw.bin

and here is the content of '/lib/firmware'

ls -al /lib/firmware/
insgesamt 60
drwxr-xr-x  7 root root  4096 Aug  8  2021 .
drwxr-xr-x 20 root root  4096 Aug  8  2021 ..
drwxr-xr-x  2 root root  4096 Aug  8  2021 av7110
-rw-r--r--  1 root root 13388 Aug 16  2015 carl9170-1.fw
drwxr-xr-x  2 root root  4096 Aug  8  2021 cis
drwxr-xr-x  2 root root  4096 Aug  8  2021 dsp56k
drwxr-xr-x  2 root root  4096 Aug  8  2021 isci
drwxr-xr-x  2 root root  4096 Aug  8  2021 keyspan_pda
-rw-r--r--  1 root root   999 Aug 16  2015 usbduxfast_firmware.bin
-rw-r--r--  1 root root  1770 Aug 16  2015 usbdux_firmware.bin
-rw-r--r--  1 root root  8192 Aug 16  2015 usbduxsigma_firmware.bin

and I did not yet compile any new firmware into this system.

#14 ARM Builds » [SOLVED] rtl8192cu firmware problems » 2021-08-10 09:58:35

user9898
Replies: 8

Hello community,

My bananapi-r1 with beowolf is currently complaing about wifi firmware issues.

[   15.327210] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[   15.329000] usb 2-1: firmware: failed to load rtlwifi/rtl8192cufw_TMSC.bin (-2)
[   15.345792] usb 2-1: Direct firmware load for rtlwifi/rtl8192cufw_TMSC.bin failed with error -2
[   15.346165] usb 2-1: firmware: failed to load rtlwifi/rtl8192cufw.bin (-2)
[   15.353159] usb 2-1: Direct firmware load for rtlwifi/rtl8192cufw.bin failed with error -2
[   15.353182] rtlwifi: Loading alternative firmware rtlwifi/rtl8192cufw.bin

First of all I would like to figure out which version the current firmware is.
Also I would like to know to which  package the firmware belongs to.

Usually this firmware should be part of the ' firmware-realtek' package, bur when I do a 'apt search for the package I get zero results for it.

Do I now need to compile a newer version of the firmware into my system ?

By using the 'make defconfig'  route ?

If yes, which version should I pick ?
Since the current kernel version is 

Linux r1-devuan 4.19.0-17-armmp-lpae #1 SMP Debian 4.19.194-3 (2021-07-18) armv7l GNU/Linux

And the archive does not list a exact match for this patch version.

Thx for any responses.

#15 Re: ARM Builds » [SOLVED] Banana Pi R1 Board - confused about SDcard bulding instructions » 2021-08-04 17:58:26

user9898

Thx for your answers guys.

If upgrading is too dangerous though, how about doing a clean install with chimaera from scratch ?
I already dug a bit through ftp server's directory's, however without any luck locating a installer for chimaera.

#16 Re: ARM Builds » [SOLVED] Banana Pi R1 Board - confused about SDcard bulding instructions » 2021-08-04 08:11:30

user9898

I used a USB FTTDI interface and TeraTerm.
I also could have used Linux and Minicom, but the other was just simpler for me.

Maybe I should use this oppotunity to add another question below my previous post.

After I got the 'beowulf' working I discovered some information about the next release eg 'chimaera'
I than rewrote the source.list file by replacing every every line where it said 'beowolf' with 'chimaera'

and the upgrade went through, however with some minor error's
Last the kernel was upgraded to 5.10
and there where some error msg's about missing drivers.
right now I am stuck in a situation, where the interface eht0 receives a ip address and still can not 'talk' to the rest of the NW.

Right now i am going back and forward if I should rebuilt the SD card or continue to try to fix it.

#17 Re: ARM Builds » [SOLVED] Banana Pi R1 Board - confused about SDcard bulding instructions » 2021-07-31 12:28:13

user9898

Hello and sorry for my late reply.

I had to ask for someone to tell what the 'zcat' tool was for.
From there one on it all went smooth.
Devuan is now running fine on my R1 Board.
Thx for the help.
user9898

#18 ARM Builds » [SOLVED] Banana Pi R1 Board - confused about SDcard bulding instructions » 2021-07-14 08:06:23

user9898
Replies: 9

Hello community,

I want to use Devuan on my Banana Pi1 R1 board and the instruction for the sdcard write process are confusing me a bit.

Here are my questions:
1. Which image do I need to use ?
    Do I need to use the u-boot image ?

2. Once I extracted both files, in which order do I need to write both files to my sdcard ?

thx for all answers,

user9898

#19 Hardware & System Configuration » BCM4312 on a old Acer AO751h » 2020-06-26 08:32:04

user9898
Replies: 6

Hello Community,

I installed Devuan on a old Acer Notebook AO751h which has a comes with a old Broadcom module (BCM4312)

During startup I get the following error message.

[   19.402445] b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
[   19.402660] b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
[   19.402897] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Dri … cefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

How do I please get it work ?

Do I need enable a special repository like on Debian by adding some special lines to my 

sources.list

or do I need to download some kind of archive ?

Thanks and regards

Pages: 1

Board footer

Forum Software