Cannot connect to ethernet or Wireless

crunchbang_noob · 2012-08-11 17:08:40

Will post results.

crunchbang_noob · 2012-08-12 00:26:20

Sorry guys, I tried downloading the .iso about 10 different times.
Added it to USB with Unetbootin/dd and every time it said that the USB was not a bootable floppy/disc.

Thanks for all your help and contributions, hopefully this thread will help other people. As for me, sadly, i'll have to stick with Archbang.

Thanks again.

SabreWolfy · 2012-08-12 00:29:56

Did you check the hash of the iso? The dd method is the easiest. What dd command did you use?

pidsley · 2012-08-12 00:38:08

crunchbang_noob wrote:

Sorry guys, I tried downloading the .iso about 10 different times.
Added it to USB with Unetbootin/dd and every time it said that the USB was not a bootable floppy/disc.

What about trying eth1, as machinebacon suggested? The output from ifconfig said you were connected on eth1, not eth0. It's not an issue with your download.

You were so close, don't bail and go back to Archbang...

Do you have any files at /etc/udev/rules.d/*

ls /etc/udev/rules.d

?

crunchbang_noob · 2012-08-13 05:45:09

SabreWolfy wrote:

Did you check the hash of the iso? The dd method is the easiest. What dd command did you use?

I used dd if=/directory-iso-is in of=/where-usb-is

SabreWolfy · 2012-08-13 07:32:24

crunchbang_noob wrote:

I used dd if=/directory-iso-is in of=/where-usb-is

The correct format is:

$ sudo dd if=/directory/filename.iso of=/dev/sdX

where "X" is the letter of the USB drive; do not include a partition number (such as /dev/sdb1) -- just the letter, such as "/dev/sdb". Make sure you use the correct letter, or you will overwrite the wrong device.

You need to specify the actual ISO filename, not just the directory it is in.

Last edited by SabreWolfy (2012-08-13 07:33:43)

crunchbang_noob · 2012-08-14 02:36:28

Yes, I knew that. I just didn't want to be all that specific, but that is how I wrote it to the flash drive.

pidsley · 2012-08-14 02:39:24

If you have seriously given up, please mark this thread [Abandoned] (edit the title of your first post). If you'd like to continue, can you answer the questions I asked in post 29?

Last edited by pidsley (2012-08-14 02:39:42)

machinebacon · 2012-08-14 02:49:31

If somebody gives up at this step, he/she deserves a trip to archbang, including the first pacman -Syu wink

hhh · 2012-08-14 04:24:34

rickroll goes here

sqlpython · 2012-08-14 13:43:28

If somebody gives up at this step, he/she deserves a trip to archbang,

Yeah but for @crunchbang-noob's purposes ArchBang is a success. It simply connects his WiFi w/o configuration.
.......End of story.

I have had a load of laptops in the past 10 years which were BCM wifi machines.
I got them all to work in the beginning via NdisWrapper and later with the linux modules..
Don't know what @crunchbang-noob did to configure the wifi as that was not posted.
I found that You Must Blacklist particular driver/modules and particularly remove modules before
modprobing the pertinent BCM module. This is a Must.
As in the link @pvsage pointed to which in turn points to Debian Wifi Wiki the important lines are.

Blacklist offending module

# echo blacklist brcm80211 >> /etc/modprobe.d/broadcom-sta-common.conf

Rebuild your initial ramdisk, to blacklist modules defined at /etc/modprobe.d/broadcom-sta-common.conf within initramfs:

# update-initramfs -u -k $(uname -r)

Unload conflicting modules:

# modprobe -r b44 b43 b43legacy ssb brcm80211

Load the wl module:

# modprobe wl

Of Course Load Back in the ssb and the b44 for the NIC

# modeprobe ssb b44

in the end I wrote the instructions into a Bash script which can be placed in on several Dirs for boot.
Assuming that conflicting moudules like b43, b43legacy and brcm80211 are previously blacklisted.

 #!/bin/bash
 ifconfig eth0 down
 ifconfig eth1 down
 modprobe -r b44 ssb
 modprobe wl
 ifconfig eth1 up
 modeprobe ssb b44
 ifcofig eth0 up

Last edited by sqlpython (2012-08-14 14:11:19)

CrunchBang Linux

SEARCH

#26 2012-08-11 17:08:40

Re: Cannot connect to ethernet or Wireless

#27 2012-08-12 00:26:20

Re: Cannot connect to ethernet or Wireless

#28 2012-08-12 00:29:56

Re: Cannot connect to ethernet or Wireless

#29 2012-08-12 00:38:08

Re: Cannot connect to ethernet or Wireless

#30 2012-08-13 05:45:09

Re: Cannot connect to ethernet or Wireless

#31 2012-08-13 07:32:24

Re: Cannot connect to ethernet or Wireless

#32 2012-08-14 02:36:28

Re: Cannot connect to ethernet or Wireless

#33 2012-08-14 02:39:24

Re: Cannot connect to ethernet or Wireless

#34 2012-08-14 02:49:31

Re: Cannot connect to ethernet or Wireless

#35 2012-08-14 04:24:34

Re: Cannot connect to ethernet or Wireless

#36 2012-08-14 13:43:28

Re: Cannot connect to ethernet or Wireless

Board footer