How do I fix messed up (accidentally) staging driver

Test and fix the Kernel 4.14 features
Post Reply
Enig123
Posts: 8
Joined: Mon Mar 09, 2020 12:13 pm
languages_spoken: english
ODROIDs: Odroid HC1
Has thanked: 0
Been thanked: 0
Contact:

How do I fix messed up (accidentally) staging driver

Post by Enig123 » Mon Apr 27, 2020 11:07 am

Unfortunately I messed up with the driver that's already in hardkernel's ubuntu 18.04, before my TP-Link TL-WN725N V2 arrived.

I might accidentally modified or deleted the staging driver. How I am suppose to get it back?

User avatar
odroid
Site Admin
Posts: 34195
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 701 times
Been thanked: 625 times
Contact:

Re: How do I fix messed up (accidentally) staging driver

Post by odroid » Mon Apr 27, 2020 11:48 am

Try reinstalling the XU4 kernel package.
sudo apt install --reinstall linux-odroid-5422

Enig123
Posts: 8
Joined: Mon Mar 09, 2020 12:13 pm
languages_spoken: english
ODROIDs: Odroid HC1
Has thanked: 0
Been thanked: 0
Contact:

Re: How do I fix messed up (accidentally) staging driver

Post by Enig123 » Mon Apr 27, 2020 12:40 pm

Thanks, but still the wifi interface cannot get up.

The dmesg related is as follow:
[ 11.415209] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
[ 11.453790] EEPROM ID = 0x8129
[ 11.456036] usbcore: registered new interface driver r8188eu
[ 11.496334] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 11.519075] r8188eu: module is from the staging directory, the quality is unknown, you have been warned.
[ 11.524064] Error: Driver 'r8188eu' is already registered, aborting...
Sorry to bother, that I believe someone has encountered similar errors. I have searched google for an answer, but I cannot tell which one is the solution.

In order to avoid I got things even worse, I desperately need your help here.

ip a showed the interface as:
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether xx:xx:xx:df:xx:92 brd ff:ff:ff:ff:ff:ff
inet 172.16.3.1/24 brd 172.16.3.255 scope global wlan0
valid_lft forever preferred_lft forever
It just cannot be putting to 'UP' state.

User avatar
odroid
Site Admin
Posts: 34195
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 701 times
Been thanked: 625 times
Contact:

Re: How do I fix messed up (accidentally) staging driver

Post by odroid » Mon Apr 27, 2020 2:20 pm

I have no idea.
I hope other experts can help you.

User avatar
rooted
Posts: 7642
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 680 times
Been thanked: 183 times
Contact:

Re: How do I fix messed up (accidentally) staging driver

Post by rooted » Mon Apr 27, 2020 2:35 pm

Is nothing showing in connection manager or are you trying to connect within a terminal?

Enig123
Posts: 8
Joined: Mon Mar 09, 2020 12:13 pm
languages_spoken: english
ODROIDs: Odroid HC1
Has thanked: 0
Been thanked: 0
Contact:

Re: How do I fix messed up (accidentally) staging driver

Post by Enig123 » Mon Apr 27, 2020 4:20 pm

rooted wrote:
Mon Apr 27, 2020 2:35 pm
Is nothing showing in connection manager or are you trying to connect within a terminal?
The device is identified but it just cannot be set 'UP' at all, thus no further steps can taken.

User avatar
rooted
Posts: 7642
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 680 times
Been thanked: 183 times
Contact:

Re: How do I fix messed up (accidentally) staging driver

Post by rooted » Mon Apr 27, 2020 4:40 pm

You can see your WiFi SSID but not connect?

Enig123
Posts: 8
Joined: Mon Mar 09, 2020 12:13 pm
languages_spoken: english
ODROIDs: Odroid HC1
Has thanked: 0
Been thanked: 0
Contact:

Re: How do I fix messed up (accidentally) staging driver

Post by Enig123 » Mon Apr 27, 2020 5:13 pm

Guys, I just noticed that this is a ver 3.8, which I am not sure if it's supported on Linux at all.

On one of my rock64 with ayufan's stable linux 4.4.x, this one can be set broadcasting SSID, however I failed to start a dhcp server that needed for the WiFi interface.

But with new installed ayufan linux 4.4.x, it also showed in 'ip a' command but cannot be powered up.

Post Reply

Return to “Linux Kernel 4.14 Debugging Party”

Who is online

Users browsing this forum: No registered users and 1 guest