DebianDog64 - 64 bit DebianDog-Jessie

A home for all kinds of Puppy related projects
Message
Author
User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#521 Post by rcrsn51 »

Max Headroom wrote:But I don't know How 2 Fix it
The first thing you do is identify the make and model of the adapter.

Then run: lsusb and identify the vendor:product ID codes.

Run: dmesg and look for error messages about wifi.

In XenialDog, run: lsmod and identify the kernel module that was loaded.

User avatar
Max Headroom
Posts: 421
Joined: Wed 28 Jun 2006, 07:17
Location: GodZone Kiwi
Contact:

#522 Post by Max Headroom »

Thanx rcrsn51 for your timely reply, M$ Virus Bait 7 Pro 64-bit identifies the Nano USB Wireless Network Adapter as a Realtek RTL8188ETV

[ 6.188929] usb 1-4: Product: 802.11n NIC
[ 6.188931] usb 1-4: Manufacturer: Realtek
[ 6.188933] usb 1-4: SerialNumber: CCD29BD929D2
[ 6.273728] random: ntfs-3g urandom read with 60 bits of entropy available
[ 6.408063] Switched to clocksource tsc
[ 6.412032] usb 2-2: new high-speed USB device number 2 using ehci-pci
[ 6.529988] EXT4-fs (loop0): couldn't mount as ext3 due to feature incompatibilities
[ 6.530048] EXT4-fs (loop0): couldn't mount as ext2 due to feature incompatibilities

[ 16.151706] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 16.265603] r8188eu: module is from the staging directory, the quality is unknown, you have been warned.
[ 16.267802] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)

root@jessie64:~# lsmod
Module Size Used by

r8188eu 654537 0

Wot Now then Please?
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!

User avatar
Max Headroom
Posts: 421
Joined: Wed 28 Jun 2006, 07:17
Location: GodZone Kiwi
Contact:

#523 Post by Max Headroom »

Btw Fred, I just Noticed that this is Using 3.16.0.4 Ke*nel & there's no Upgrade Kernel Tool in Menu > System > Upgrade Ke*nel or Anywhere that I can find?

Thanx 4 your Help!

:oops: K
Last edited by Max Headroom on Mon 22 Jan 2018, 20:56, edited 1 time in total.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#524 Post by rcrsn51 »

I installed DebianDog64-Jessie-openbox-2016-03-20 and plugged in an 8188eu wifi adapter.

The driver installed correctly and the firmware is present.

It passed the basic connection test.

Code: Select all

iwconfig
ifconfig wlan0 up
iwlist wlan0 scan
I don't use frisbee, but I installed PeasyWiFi and it worked OK.

User avatar
Max Headroom
Posts: 421
Joined: Wed 28 Jun 2006, 07:17
Location: GodZone Kiwi
Contact:

#525 Post by Max Headroom »

Thanx 4 Helping me rcrsn51, I've uninstalled Frisbee & Wicd, & Mounted the PeasyWifi.sfs File or a Green window told me so, But there's no icon in the System Tray or Network Menu.

I Tried Starting it from the Command Line in Rox, But just got command not found

I'm out of ideas again, Sorry....

:? K
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#526 Post by rcrsn51 »

Did you pass the basic connection test?

User avatar
Max Headroom
Posts: 421
Joined: Wed 28 Jun 2006, 07:17
Location: GodZone Kiwi
Contact:

#527 Post by Max Headroom »

Alas No, it seems...

root@jessie64:~# iwconfig
eth0 no wireless extensions.

wlan0 unassociated Nickname:"<WIFI@REALTEK>"
Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

lo no wireless extensions.

root@jessie64:~# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 B) TX bytes:100 (100.0 B)

root@jessie64:~# iwlist wlan0 scan
wlan0 No scan results

root@jessie64:~#

:? K
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#528 Post by rcrsn51 »

I don't see all of the commands:

Code: Select all

ifconfig wlan0 up
ifconfig
iwlist wlan0 scan 

User avatar
Max Headroom
Posts: 421
Joined: Wed 28 Jun 2006, 07:17
Location: GodZone Kiwi
Contact:

#529 Post by Max Headroom »

root@jessie64:~# ifconfig wlan0 up
SIOCSIFFLAGS: Operation not permitted
root@jessie64:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1c:c0:ed:3f:25
inet addr:192.168.178.56 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::21c:c0ff:feed:3f25/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6690 errors:0 dropped:0 overruns:0 frame:0
TX packets:5636 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5618321 (5.3 MiB) TX bytes:902625 (881.4 KiB)
Interrupt:20 Memory:e0200000-e0220000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 B) TX bytes:100 (100.0 B)

root@jessie64:~# iwlist wlan0 scan
wlan0 No scan results

Like this?

:? K
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#530 Post by rcrsn51 »

Max Headroom wrote:root@jessie64:~# ifconfig wlan0 up
SIOCSIFFLAGS: Operation not permitted
That command works in my setup.

If it doesn't work for you, then changing connection apps won't fix anything.

User avatar
Max Headroom
Posts: 421
Joined: Wed 28 Jun 2006, 07:17
Location: GodZone Kiwi
Contact:

#531 Post by Max Headroom »

rcrsn51, I've Confirmed that We're Both Using the eXact same Release, so I don't understand whY We get Different Results?

Any other Suggestions Please?

:? K
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#532 Post by rcrsn51 »

Have you posted the results of "lsusb" and identified the vendor/product ID codes?

Your next step is a temporary clean install with no "changes" folder.

User avatar
Max Headroom
Posts: 421
Joined: Wed 28 Jun 2006, 07:17
Location: GodZone Kiwi
Contact:

#533 Post by Max Headroom »

I Thought i did...

root@jessie64:~# lsusb
Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0bda:0179 Realtek Semiconductor Corp.
Bus 001 Device 005: ID 1005:b128 Apacer Technology, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 0458:0037 KYE Systems Corp. (Mouse Systems)
Bus 005 Device 002: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I Guess ReBooting as Always Fresh, should be the same...

:)K
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!

User avatar
Max Headroom
Posts: 421
Joined: Wed 28 Jun 2006, 07:17
Location: GodZone Kiwi
Contact:

#534 Post by Max Headroom »

So as it's Booting as Always Fresh, I Can See....

SIOCSIFFLAGS: Operation not permitted
Failed to connect to non-global ctrl_ifname: wlan0 error: No such file or directory

I don't understand the Meaning of the Error? or How 2 Fix it!...

:? K
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#535 Post by rcrsn51 »

Max Headroom wrote:Bus 001 Device 002: ID 0bda:0179 Realtek Semiconductor Corp.
My device is 0bda:8179.

Maybe there is some slight difference that is causing the driver to fail.

User avatar
Max Headroom
Posts: 421
Joined: Wed 28 Jun 2006, 07:17
Location: GodZone Kiwi
Contact:

#536 Post by Max Headroom »

I'm being Challenged 2 understand whY this same Nano USB Wireless Network Adapter Worked in this same PC Previously when it had as its Base OS 32-bit XenialDog, that had a 4.4 Ke*nel & Now No Go w/ 3.16.0 Ke*nel, Debi'Dog 64-bit.

Maybe a Ke*nel issue?

How 2 Update?

:? K
PC is Not Political Correctness :P , it's a Personal Computer! Boycott the Evil M$ & Google!

ocpaul20
Posts: 260
Joined: Thu 31 Jan 2008, 08:00
Location: PRC

#537 Post by ocpaul20 »

Hi,
I posted this in General but it seems there is something which is more of a DebianDog thing than a Puppy thing. Hope someone can help me.

I tried all kinds of search terms "drive and icons", "drive icons" but nothing obvious came up in a title.

I am using Debian Dog (maybe not 64 one?) The other thread closed then reopened and last post was june 2017.

Anyway, I rebooted and the drive icons were gone along with the Pinboard I was using. That means I get to use the Default Pinboard and missing all my drive icons at the bottom of the screen. Thankfully I had copied the contents of /root/.config/rox.sourceforge.net/ROX-Filer so I think I have the pinboard back...

Is there a program I can run to regenerate these drive icons at the base of the screen please?
Or.. can anyone suggest how I can get them back?

Thanks.
Paul
==================
Running DebianDog Jessie Frugal with /live and maybe with changes or savefile or.., who knows?

dancytron
Posts: 1519
Joined: Wed 18 Jul 2012, 19:20

#538 Post by dancytron »

In my Debian Dog, the drive icons are created by a program
/usr/local/bin/desktop_drive_icons

First, see if it is installed by running by running "desktop_drive_icons" from the terminal.
Assuming that works, then you need to set that to run automatically at bootup.

Several different ways to do that, one of which would be to create a link from /usr/local/bin/desktop_drive_icons to /root/startup.

If you don't have a /usr/local/bin/desktop_drive_icons file, then search for it and install it with apt-get or synaptic.

If you need more to figure it out, let us know.

ocpaul20
Posts: 260
Joined: Thu 31 Jan 2008, 08:00
Location: PRC

#539 Post by ocpaul20 »

Thats marvellous, thanks. I now have my drive icons back.

I have the program but it does not return cleanly to the command line so I have to Ctrl+C to finish it. It does generate my drive icons though which is good. I wonder what it is trying to do? If I can find that out, I can fix that so that it finishes properly.

Ahh.. I see. When I Ctrl+C to stop it, the drive icons disappear from the bottom of the screen, so do I have to run it as part of the startup ?
Last edited by ocpaul20 on Fri 02 Feb 2018, 03:05, edited 1 time in total.
==================
Running DebianDog Jessie Frugal with /live and maybe with changes or savefile or.., who knows?

dancytron
Posts: 1519
Joined: Wed 18 Jul 2012, 19:20

#540 Post by dancytron »

ocpaul20 wrote:Thats marvellous, thanks. I now have my drive icons back.

I have the program but it does not return cleanly to the command line so I have to Ctrl+C to finish it. It does generate my drive icons though which is good. I wonder what it is trying to do? If I can find that out, I can fix that so that it finishes properly.
Running from terminal was just a test. It doesn't "finish", it keeps running so it keeps showing you the icons. If you go to /usr/local/bin/desktop_drive_icons and just click on it, it should keep running in the background.

Are you using pcmanfm or thunar as your file manager? If so, select /usr/local/bin/desktop_drive_icons, to to menu edit-create link, and put a link in /root/startup. That should start it up automatically every time.

Post Reply