DebianDog64 - 64 bit DebianDog-Jessie

[rcrsn51]

Did you pass the basic connection test?

[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

[rcrsn51]

I don't see all of the commands:

Code: Select all

ifconfig wlan0 up
ifconfig
iwlist wlan0 scan 

[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

[rcrsn51]

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.

[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

[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.

[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

[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

[rcrsn51]

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.

[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

[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

[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]

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 ?

[dancytron]

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.

[ocpaul20]

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.]

I think I am using Rox, but I have added items to Startup before so I can do that again now.

I will give it a whirl and see if that sorts it out. At least now I know the name of the program I can run if they disappear again in another lifetime (instance of Debiandog) !!

Thanks for all your help.

[ocpaul20]

It is strange, because I have added a link to /root/Startup and am sure it is executable. When I click on it as you suggested, it runs and shows the drive icons correctly.

However, after all that, when I reboot, expecting this to run as part of the startup routine, I get no drive icons but I get a message which tells me that I am using the default pinboard.

To test it all, I placed a line at the end of another shell script which runs at my startup.
nohup /root/Startup/desktop_drive_icons &

and nohup.out gives me a message
(desktop_drive_icons:3539): Gtk-WARNING **: cannot open display:

Maybe this is a total Red Herring and the real problem is to do with the lost pinboard and the nohup.out message above?

With linux, nothing is as simple as you think it is going to be, huh?

[dancytron]

Sorry, don't know. If Fred (posted the first message in this thread) doesn't see this in a day or two you might send him a pm.

[fredx181]

Hi ocpaul20,

It is strange, because I have added a link to /root/Startup and am sure it is executable. When I click on it as you suggested, it runs and shows the drive icons correctly.

However, after all that, when I reboot, expecting this to run as part of the startup routine, I get no drive icons but I get a message which tells me that I am using the default pinboard.

I tried to reproduce that (made symlink to /usr/local/bin/desktop_drive_icons in /root/Startup and reboot) , but couldn't, all is fine for me, and rox pinboard configuration should not have anything to do with desktop_drive_icons .
So it looks like that the problem is caused by something else you did.
You can try to restore to the original rox pinboard, from terminal:

Code: Select all

cp -af /mnt/live/memory/images/01-filesystem.squashfs/root/.config/rox.sourceforge.net/ROX-Filer/pinbd-OB /root/.config/rox.sourceforge.net/ROX-Filer/

Then restart X (Exit X and type startx from console)
If that doesn't help, just copy all the files inside /mnt/live/memory/images/01-filesystem.squashfs/root/.config/rox.sourceforge.net/ROX-Filer/ to:
/root/.config/rox.sourceforge.net/ROX-Filer/ and restart X.

Fred

[ocpaul20]

Hi Fred,
Thanks for your comment.

I have managed to get back my drive icons and the message about the default pinboard no longer shows on bootup. I am not sure what I did, but I did restore some stuff as you suggested so it was most probably that which sorted it out.

The only problem now I have is that I have lost some menu items which I thought would have been restored in the same series of operations when I restored the ROX-filer directory.

In particular, the JWM menu, Network item at bottom right has lost a few entries such as Deluge and Icedove etc. I can reinstall them and the menu items will probably be re-installed too.

Anyway, thanks for all the help on this everyone.

=====================
I found the missing menu items in a couple of files /root/.jwmrc & /root/.jwmrc-mjwm so I restored them too and everything is fine now.
======================