Topic: [SOLVED]Initial problems experienced in Statler

Hello,

These are various problems I have experienced in my installation of Statler Alpha 2 so far that I am attempting to work through or around.  I am listing them in case anyone else has experienced them and if anyone can offer any help.  I am a newbie.

Version: crunchbang-10-alpha-02-openbox-i686.iso via unetbootin

In semi-chronological order:

1.  LVM
I attempted to install LVM with the guided partitioner.  However, on installation it did not load (mount?) after grub.  I got around this by going without LVM for now.  I have noticed an unanswered post about this.

2.  Sudo
I found on installation I was not on the sudoers list (this may be intentional?)  I used su to login as root and change this.

3.  cb-welcome script
I think the cb-welcome script is great, however, it does not appear to work for me, even after fixing sudo (see above).  It processes through, but does not actually install anything.

4.  Networking
Wired networking is working fine.  However, wireless networking is not.  While network manager recognises my wireless network it stalls at the connecting stage with the spinning whatnots, or connects, but does not actually connect to the internet.  I am guessing this is related to dhcp?  I believe other people have experienced this, but I am unsure how they fixed it (but I am presently looking!).  Any help directing me to the solution would be much appreciated.

Cheers

Last edited by babeuf (2010-08-27 13:42:44)

Re: [SOLVED]Initial problems experienced in Statler

Aha...

Found out what is probably making cb-welcome not work; the sources list only has the 'live cd' as its sources....

Is there a handy copy of the crunchbang repository list available?

Re: [SOLVED]Initial problems experienced in Statler

Yup, cb-welcome now works wonderfully with an updated sources list.  Just need to sort the wifi now...

Re: [SOLVED]Initial problems experienced in Statler

Okay.

I can't seem to get my wifi to work.  I have tried updating to debian sid, but this has not solved the problem.

This is my ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:23:ae:27:ca:67  
          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::223:aeff:fe27:ca67/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7640 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6934 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7974148 (7.6 MiB)  TX bytes:1035646 (1011.3 KiB)
          Interrupt:18 

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:16436  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:280 (280.0 B)  TX bytes:280 (280.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:24:2c:10:64:f5  
          inet6 addr: fe80::224:2cff:fe10:64f5/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:5147 (5.0 KiB)

From this, may I assume that my wlan0 = wifi is actually connected in some way?

Re: [SOLVED]Initial problems experienced in Statler

How are you trying to connect?
you seem to get only IPV6 address on your wlan.

a.

Re: [SOLVED]Initial problems experienced in Statler

Hi,

I'm trying to connect by wifi on a "Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)" using network manager.

It seems to be the same problem(s) stated here: http://crunchbanglinux.org/forums/topic … er-alpha1/ .  I've similarly gone through the debian squeeze guide here: http://wiki.debian.org/wl#Squeeze with no success....  hmm  Seems to be similar to the bug stated here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580354 .

In going through the squeeze guide I lost the ability to scan for available networks altogether it would seem.

Starting to look like I won't be able to use statler until squeeze stable comes out. sad

Last edited by babeuf (2010-08-27 00:03:08)

Re: [SOLVED]Initial problems experienced in Statler

try installing "firmware-b43-installer"

a.

Re: [SOLVED]Initial problems experienced in Statler

you just need to find out what driver you use and manually install it
it took me about 3 whole days to find out which one it was and now after every fresh install i must manually compile it but now it's not so much of a big deal i can get it working in like 5 minutes at most
if i were to wait till my drivers were included in the linux kernel its safe to say that i wouldnt of had internet not even now

Re: [SOLVED]Initial problems experienced in Statler

Yup, I thought I'd done everything and I was in fact using the wrong firmware - guide here far better: http://wiki.debian.org/bcm43xx  smile   It's firmware-b43-lpphy-installer as opposed to good old firmware-b43.

Anyway, I now have a successful connection, but no internet.  However, this should be easier...

Re: [SOLVED]Initial problems experienced in Statler

Yay!  Disabled IPV6 and it seems to work. big_smile

Re: [SOLVED]Initial problems experienced in Statler

Conclusion:

1.  LVM
Live without.

2.  Sudo
Simply add yourself to the sudoers list in /etc/sudoers.

3.  cb-welcome script
Works after you:
i.  Add yourself to the sudoers list above
ii. Add repositories to the sources list found here: /etc/apt/sources.list .  Repository lists for debian can be generated here: http://debgen.simplylinux.ch/

4.  Networking
Wired is fine.
Broadcom B43 wireless cards can be 'fixed' by manually installing the firmware by reading the instructions here: http://wiki.debian.org/bcm43xx and then connect/configure as normal with network manager.
If you still cannot connect to the internet try disabling IPV6 in iceweasel about:config.