Quote from: PackRat on June 29, 2015, 07:27:56 PM
The message last maybe 10 seconds after logging  in then clears.

Wicd wasn't working at all. I logged in expecting wireless - as usual - and no connectivity. Plugged in a cable and rebooted - nothing, logged out and back in to see if it picked up wired - nothing.

The new version of Ceni found and configured both cards though.

Edit - wicd had the cards listed as wlan0 and enp3s0. I manually changed them to enp2s0 and wlp3s0 and have connectivity via wicd; wired and wireless

Hi everyone,
   I got the latest ISO a few hours ago and went through the install process like I am usually used to. I can confirm, I got the same message/behaviour as PackRat. Since there is already a thread with this ongoing discussion, I wanted to chime in. If you need, I'll check up on the names sometime later and let you know.

Ciao.

So, brcm80211 package for Broadcom wifi didn't make it for this release?

Given this bumped thread is about Broadcom, I want to pitch in with my experience as well.

I have Broadcom 4313 and I had to resort to ethernet/networking cable during install as well as for some time post install before getting wifi to work.

I checked the packages list of VSIDO and see that this package (brcmsmac) is not present. It would be a good addition for augmenting existing wifi driver support in VSIDO.

Quote from: VastOne on September 12, 2013, 05:47:30 PM
I think there is less people who want / need geany than there are that do demand it... Honestly, I do not know why I included it to begin with on the original design and install

Let's call it "the crunchbang effect", eh?

Quote from: VastOne on September 12, 2013, 05:47:30 PM
I have already included the package list in a post above...

which probably got "clobbered in the melee". I shall give it a once over............. after locating it first

Quote from: VastOne on September 12, 2013, 05:47:30 PM
In a nutshell it is this:

Removed Xfce 4.10 but kept some parts (application finder, notifyd, task-manager)
Placed Thunar and Geany in vsido-welcome
removal of uget
removal of gFTP
removal of aptosid kernel-remover (because smxi does the same thing)
added pulseaudio

I also removed two icon sets that were not needed... That significantly reduced the ISO size..
This started out because the 64 bit is growing out of control (717 Mib) now...

This is pretty good, I would say. Thanks.

Quote from: VastOne on September 12, 2013, 05:47:30 PM
And gdebi has not been removed, where are you seeing that?

If you didn't implement this thread, well, thank you.

Last but not least,  This thread made for intriguing reading. We, the existing users also need to do this?

sudo rm -rf /lib/live/mount

Cheerio

Oh, and I just realised, gdebi is also gone ! But, I used to use it regularly too :-/

I already have VSIDO installed, so geany is already on my m/c. I take it, future ISO releases won't come bundled with geany? Getting relegated to the welcome script... oh the ignominy!  

GNOME-dependencies? in or out? If your ISO is under 670 MB or so with gnome-dependencies inside, I would still suggest that you include GNOME dependencies... It future proofs the installation against later app installs, specially if people don't have "autobahn internet" all the time.


@Vastone,
   if it is not too much of a bother, can you write a small summary post by collating all the developments so far, as to what the "new look" VSIDO will be made of?

As I mentioned previously, antiX and salixOS are both dedicated fluxbox distros. But neither of these are "sid" based, effectively leaving that claim to fame as VSIDO's of course.   

Oh, and like someone mentioned, I do hope we're still init based rather than systemd based.

Quote from: VastOne on September 10, 2013, 03:39:04 PM
I think keeping with the SID kernel is the way to go <snip>

OB is so tiny as to not really matter keeping it or not... but by being a FluxBox only distro has certain advantages

I will not maintain two different ISO builds... that is too much to bite off and chew

@VastOne,
I knew 2 separate ISOs is overkill, but OTOH, if we're going to remain up-to-date/sid based all the way, then I'm one happy chappie. 

I've grown to like openbox and do use fluxbox distros as well (salix and antiX). But, I am keen to understand what you mean by "being a FluxBox only distro has certain advantages"?

Ciao for now.

Well, I am a #! IRC regular. I help out in whatever way that I can in that room, and based my own personal experience as well as fielding ad-hoc support requests,  kernel 3.2.0.4 is getting a bit long in the tooth, and the stable libraries are getting stale, even for die hard #!-ers as well as debian stable proponents.

I bit the bullet and jumped ship to VSIDO from #! because of the library dependencies lagging behind for every application, and big problems with wifi (broadcom) with the stable kernel. Ubuntu, which uses testing version, did not suffer these issues, and so I knew moving to unstable is just one more necessary step for my config. Basically, Broadcom will be a big bug bear with 3.2 and your IRC/forums support overhead will go up disproportionately to the momory savings   I have rarely, if ever, noticed increased memory consumption as an overhead in my time spent with vsido (it is my no.1 go to debian session these days), and frankly it has proven to be so good, I've not logged into a #! session in months. The last time I did log into #!, I installed smxi and upgraded to 3.10.2 aptosid kernel. It was not easy, as I had to upgrade many libs/apps to unstable in order to bring the kernel forward, but since my #! upgrade, #! never had wifi dropping every 5 mins on me. All my ubuntu spins now sport 3.8+ kernels, and work smashingly well on my config. 

The gist of all this is that, I hadn't noticed a spike in memory in my constant VSIDO usage over the last 5 months or so. On the other hand, the newer kernels and libs have been so good in playing with my hardware and providing me with good service (which debian stable kernel and libs did not), I have upgraded all my other debians to unstable repos! Ha.

@Vastone, out of interest, by what proportion has the newer kernels increased the memory consumption?

Re: XFCE, I only use a few aspects of XFCE, the ones you mention anyway. If someone wants to go full XFCE, there's always siduction or aptosid XFCE isos...

Re: Openbox, please don't remove it completely. I do log into OB regularly and find it just as nimble as fluxbox.

If it is not too much trouble for you, please run this "small and stable ISO" separately to the regular ISOs that you roll out. The SID in VSIDO stands for sid -- debian unstable (I hope), and personally, I would prefer to have a sid based vsido humming on my machine -- willing to live with the additional memory usage trade off. Because the alternative (for me at least) is constant fiddling with wifi and other things to make it work (which I am frankly fed up of)

Re: geany isn't too bad, and as such I would advice against removing it. I use geany:medit 50:50. They are tools for different occasions.

Re: GNOME dependencies, I've installed a few additional apps on my VSIDO after installation (Vim and some image app), and your GNOME dependencies have saved the day for me, in keeping my download sizes and download times much more manageable. It is a one time overhead for people with poor net connections to download a somewhat larger ISO, but have the dependencies as a "future-proofing" for future.

Let me know what you think of these points I made. If I recall anything, I'll drop by again.

Nitrogen is the GUI used in VSIDO for setting up wallpapers in VSIDO. It can be accessed via Right-Click-> Menu -> Settings -> Wallpaper on a VSIDO session.

You can add your own images dir to Nitrogen by choosing "Preferences"  and adding dirs. You must press "Apply" and the images will be populated in Nitrogen for you to choose.

Sometimes, Nitrogen will misbehave, and you won't be able to see your images, and also the dir containing images, will be grayed out.

In these circumstances, open Nitrogen, Preferences, delete the dir that you originally added, "Apply" and reboot. Repeat the earlier steps of adding the dir of images again.

Et Voila! You get your images back.

Hope that helps someone else.

Ah pure joy on that face!  We celebrated our's first birthday in June.

Happy Birthday to your dear daughter. Our best wishes: "May she grow up well and be successful in life".

@PackRat, @VastOne, @jedi/@JedsDesk

Thanks to you all.

Permanent solution to all those fellow Broadcom sufferers (oops!  ) users is to uninstall ceni and install wicd (along with all the wicd tools).

It works beautifully, and dareisay, out-of-the-box! Whoop-de-doo!

No dropped calls, no tearing your hairs, no rising blood pressures

Again, thanks to those that helped.

Ciao for now.
surio o/

I had an eerie sense of deja vu reading this thread: http://vsido.org/index.php/topic,425.0.html

It kind of mirrors my own sid experience as well. But (and it is a big one ), VSIDO worked for me. And love the way it is engineered.

I have a BCM 4313 wifi, and  it's always been touch-and-go since installation date. Installed kernel-firmware, and got wifi working.

The connections are always temperamental at best though. If I lose the connection from wifi, I end up not being able to simply plug and use the wired connection. No matter how many times I run ceni, I cannot get it to reconnect it either with eth0 or wlan0 if it loses connection (which it does all the time). The only way out is a reboot. I see a message at boot time that "binds" my gateway (router) IP to either eth0 (if cable is attached) or wlan0 (if no cable attached). And somehow this becomes "binding and final" for that session, I think.   

I have removed dhcp/auto for eth0 and explicitly specified IP/Subnet/gateway for eth0. Still no joy. Somehow ceni cannot seem to re-attch the gateway ip as and when required

I have used wicd on slackware and I am able to do this without problems for the same laptop. The laptop connects to wired on login, and if I choose wifi instead, the wired is disconnected. FWIW, I have explicitly specified IP/Subnet/gateway for eth0 and dhcp for wifi in slack, and that works fine.

I installed wicd on VSIDO but now I am not able to figure out how to replace ceni with wicd, to test things out. As of now, both of them, i.e., ceni and wicd start up, and wicd is shut down by the system (I think)....

I do not have a preference for either ceni or wicd. TBH, I am interested in learning how to use ceni correctly for configuring the system, as I already understand wicd.

I have used the ceni tutorial provided in the forums by @jedi already.

I am on a slackware session now, and I will provide you with system inputs for VSIDO in a while.

thanks,
surio.

I like Muse too.. 

Listening to Caro Emerald now:

http://grooveshark.com/#!/album/A+Night+Like+This/3736808

Easy listening weekends, FTW