Not really an issue, but I noticed that after installing the new towo kernel there was no grub entry for the previous kernel.  Is that resultant from installing with smxi?  Or is it by VastOne design?  Just curious...

@Hinto:  Does that mean you are using Siduction repos instead of Debian?  Or in conjunction?

Smxi'd up the latest towo kernel (3.8-0.towo-siduction-amd64).  Everything is purring like a cheetah kitten.  No issues to report.


System:    Host: vsido Kernel: 3.8-0.towo-siduction-amd64 x86_64 (64 bit) Desktop: Xfce 4.10.0 Distro: VSIDO
Machine:   Mobo: Dell model: 0P792H version: A04 Bios: Dell version: A04 date: 11/26/2008
CPU:       Dual core Intel Core2 Duo CPU T6400 (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3)
           Clock Speeds: 1: 1200.00 MHz 2: 1200.00 MHz
Graphics:  Card: Intel Mobile 4 Series Chipset Integrated Graphics Controller
           X.org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) tty size: 96x30 Advanced Data: N/A for root
Audio:     Card: Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture ver: k3.8-0.towo-siduction-amd64
Network:   Card-1: Broadcom BCM4322 802.11a/b/g/n Wireless LAN Controller driver: b43-pci-bridge
           IF: wlan0 state: up mac: <filter>
           Card-2: Broadcom NetLink BCM5784M Gigabit Ethernet PCIe driver: tg3
           IF: eth0 state: down mac: <filter>
Drives:    HDD Total Size: 320.1GB (24.0% used) 1: id: /dev/sda model: WDC_WD3200BEVT size: 320.1GB
Partition: ID: / size: 9.1G used: 7.1G (83%) fs: ext4 dev: /dev/sda8 label: N/A
           ID: /home size: 258G used: 65G (27%) fs: ext4 dev: /dev/sda7 label: N/A
           ID: swap-1 size: 7.97GB used: 0.00GB (0%) fs: swap dev: /dev/sda6 label: N/A
Sensors:   System Temperatures: cpu: 39.0C mobo: 39.0C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 128 Uptime: 1 min Memory: 145.6/3919.7MB Client: Shell (sudo) inxi: 1.8.38


Very nice "How To"!

Fyi, ceni can also be installed via smxi (without even leaving X).

Just start smxi like so...
sudo smxi -G

Then take the following options:
1 - package-install
3 - utilities
9 - ceni-sid

Profit!

^^^ Your avatar makes me think of toilet mints for some reason...  Meh, maybe I am teched like my better half claims.

I like it.  Particularly like the "hash marks" in the text entry fields.  Makes 'em easier on "old" eyes (not saying that pertains to me of course).

^^ Sage advice indeed!  And extra points for using keyboard instead of right click.   

Yeah, I do not entirely understand why it did not work "out of the box".  Your install places packages "b43-fwcutter" and "firmware-b43-installer" on the system.  Package "firmware-b43-installer" says in the description that it supports "BCM4322 (only 14e4:432b)".  According to lspci that is what I have.

tlinsleyvsido@vsido:~$ lspci -vnn -d 14e4:
04:00.0 Network controller [0280]: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)


Anyways, this is what I did:

• Downloaded the latest firmware from here: http://mirror2.openwrt.org/sources/broadcom-wl-5.10.56.27.3_mipsel.tar.bz2 to the "downloads" folder on my Waldorf partition.  Thumb drive would have worked just as well.
• Copied the VSIDO towo iso to a thumb drive per the how-to on this forum.
• Booted from usb into the iso.
• Ran the install, re-booted into the new desktop, and canceled out of the welcome script.
• Copied the previously downloaded firmware to my new VSIDO home directory.
• Executed these commands to install the firmware.

tar xfvj broadcom-wl-5.10.56.27.3_mipsel.tar.bz2
sudo b43-fwcutter -w /lib/firmware broadcom-wl-5.10.56.27.3/driver/wl_apsta/wl_prebuilt.o

• Restarted the system.  Could have done the modprobe dance here, but restart is cleaner.
• Upon login, wireless was detected and started by Wicd.
• Restarted the welcome script, which did the "dist-upgrade" and all the other magic.

All in all nothing too difficult.  Especially since I have done it hundreds of times in other distros.  For real fun, try making broadcom work in a Slackware distro.  Sheesh!


P.S.  Learned a valuable lesson in writing this post.  First write the post in Geany, then post it to forum.  Otherwise the dang forum expires the session and loses all you just wrote.  Grrrr. 


2013-10-24: Updated code box for b43-fwcutter to reflect latest driver name.  Instructions verified working on "vsido_raptor_64bit_2013_10_21.iso".

Installed VSIDO in a vbox guest at work and liked it so much that I decided to install it on a spare partition in my personal laptop also.  Which leads me to a couple of things to brag about.

• Since Sector 11 has been asking...  This install took only 9 minutes from clicking "Install" to rebooting into the fresh new desktop.  Probably could have done it in 8 had the television not been stealing my attention.
• We don't need no steenkin network cable!  That's right, did the whole install sans network cable.  Didn't expect that to work, since my laptop sports the dreaded Broadcom wireless.  But I just staged a copy of the latest firmware to my Waldorf partition, copied it to the new VSIDO partition post-install, ran fw-cutter against it, and Bob's your uncle.  Then I was able to do the post-install dist-upgrade across wireless.  Any distro that allows me to do a full install without getting up off my lazy butt to plug into my router, is a fine distro indeed!

Thanks again for the wonderful work VastOne!

Next up, I plan to abuse it with FluxBox.   
[/list]

Quote from: Sector11 on January 19, 2013, 05:02:31 PM

Quote from: falldown on January 19, 2013, 04:43:33 PM
Welcome tlinsley..
Hopefully someone brought some coffee for the donuts!!

Brewing a pot as I type ... milk? cream? sugar? sweetener?
Will that be small, medium, large or OMG!?

Just started my last work shift of the week.  I'll take a "OMG!" please.   

No issues downloading, pretty fast actually.  I chose the towo version.

For some reason, Wicd did not want to play well with eth0 at first.  Finally just doctored up the interfaces file and made it work.  Doesn't work flawlessly though, dhcp wants to be difficult just about every other startup.

Not ready to blame it on VSIDO though.  Could easily be company networking issues.  I have VSIDO installed as a vbox guest (bridged networking), so that adds another place to point the finger also.  I normally use Waldorf installed as a guest for my work.  Have not been having network issue with it.  But I typically fire it up at start of shift and don't shutdown till I leave.  Whereas I have been popping the VSIDO guest like a yoyo, so would have noticed network issue there first.

Anyways, other than that, the install went very smooth and fast.  Great work!

#$%^#$%^   Boy do I feel stoopid!  I looked everywhere but the logout dialogue.  Worst part is I knew better.

I shall mark it resolved.  Not even getting the xfce4-panel is in kiosk mode message anymore.

Thanks VastOne!  Very nice distro by the way.  If I can work through my intermittent dhcp issues, I will probably use it as my main for a while.  Thanks again.

Yeah I tried similar to what you did.  I vi'd the script and stuck an "exit 0" at the top.  But still conky defiantly stares back at me.

I almost think it is an authorization issue.  Because I also de-selected the script which kills the xcfe4-panel, then configured my own panel.  But I still see evidence of the script running every time I restart the system.  Almost like it is not really saving changes made through the gui (damn gui's!).

Pretty sure sure mine was over 10.  Had some network/dhcp challenges to work through.  Seems to be fine now.