Tiny Core Linux
General TC => Tiny Core Netbooks => Topic started by: rizzim3 on March 07, 2011, 07:38:58 PM
-
Just wondering if anyone can help or provide some guidance.
I recently purchased the latest Acer netbook with the AMD C50 chip and have two issues while running under TC3.5. The issues are;
1) No access to wired and wireless internet
I used ifconfig and I got a block of text for "dummy0" and another block of text for "lo". No info for atho or eth0 was returned. Unfortunately, I don't know how to get the cards recognized. Perhaps an updated driver is required?
2) No sound
I used VLC to watch a movie and all I got back was the video with no audio. I did have OSS installed. VLC did give me a warning message stating that if I were to update alsa-lib to version 1.0.23-2-g8d80d5f that it may help with the audio issue.
Perhaps there are no Linux drivers for these items yet?
Any solution to address these issues would be greatly appreciated. Thanks!
-
No access to wired and wireless internet
I used ifconfig and I got a block of text for "dummy0" and another block of text for "lo". No info for atho or eth0 was returned. Unfortunately, I don't know how to get the cards recognized. Perhaps an updated driver is required?
What wired and wireless network hardware do you have?
-
I believe I have the following:
1) Wired - Atheros Communications AR8152 v2.0
2) Wifi - Broadcom Corporation BCM4313
-
2) Wifi - Broadcom Corporation BCM4313
You'll probably need to double-check on http://linuxwireless.org/en/users/Drivers/b43
..but, either the b43 or the wl modules should work and failing that ndiswrapper.
There are plently of posts on these forums about getting broadcom wifi to work.
-
Juanito:
Thanks for the info. I tried the ndiswrapper method but without any success. I will try once again. If it doesn't work then I will wait for the next release of TC which I hope will have the correct drivers for my wired/wireless device.
I really enjoy working with TC (just started with Linux last week) but I do need access to the internet. So, it's back to Windows until I can resolve these network access issues.
Thanks again for your help...
-
Looks like the wired support for that went in to .37.
-
I'd give the wl extension a go first and if that doesn't work, there's a good chance that a working windows driver (inf and sys file) would work with ndiswrapper.
-
Juanito:
I did some further investigation. Read the following from the broadcom site:
http://www.broadcom.com/docs/linux_sta/README.txt
I believe that this is the solution but not sure if I have the skill set to actually do it. Sure, I can follow what they say but I doubt I would be able to assess any issues that may arise after. I will search the forum for some additional methodologies as well.
curaga:
I read that somewhere as well. Which makes me think I should just wait for the next build and just live with Windows in the mean time. Does anyone know when the next TC build is?
Thanks!
-
Juanito:
1) Wireless issue has been resolved.
I re-read your earlier post and I mis-understood what you meant about the wl module. Anyway, I loaded the wl and wifi-radar extensions and everything works. The card is recognized, put in my WEP key and now have access to the internet.
BTW, when I configure my WEP key via the configuration menu in Wifi Radar I lose this on shutdown. I tried looking for a configure file to add it to the backup/restore file but can't find it. Do you know if there is a configure file? If so, where?
2) Still do not have wired access with my atheros card.
Will tackle this issue next but for now I'm just enjoying the fact that I have wireless!
Thanks!
-
I just use a couple of iwconfig commands in bootlocal.sh.
-
gerald_clark:
I was thinking of something like that but then again I don't want any wireless starting up at boot. I prefer to have the applications I require installed on an "as needed basis". I guess I can just create a text file with the WEP key and just copy and paste when asked for the key. I just assumed that there would be a Wifi Radar config file somewhere that kept the information for each access point once they were set. Perhaps there is and I just can't find it...
Thanks!
-
FYI: I found the Wifi-Radar config file. If anyone is interested it is located here:
/usr/local/etc/wifi-radar/
This was from the extension Info page within AppBrowser.
I just added this to .filetool.lst and it works. No need to reenter the WEP key at next connect
-
BTW, when I configure my WEP key via the configuration menu in Wifi Radar I lose this on shutdown. I tried looking for a configure file to add it to the backup/restore file but can't find it. Do you know if there is a configure file? If so, where?
I don't use wifi radar, I just run a small script with all the required details when I need to connect using wifi: #!/bin/sh -e
#
tce-load -i /mnt/sda1/tce/optional/wl.tcz
tce-load -i /mnt/sda1/tce/optional/wireless_tools.tcz
#
sudo modprobe lib80211_crypt_tkip
sudo modprobe lib80211_crypt_wep
sudo modprobe lib80211_crypt_ccmp
#
sleep 5
sudo iwconfig eth1 essid "ssid"
sudo iwconfig eth1 key restricted 12:34:56:78:9A:BC:DE:F0:12:34:56:78:9A
#
sudo udhcpc -b -i eth1
#
# EOF
-
Juanito:
So, just run the script when required. I like that! Sounds much better then using my current method.
Quick question:
Why do you include the modprobe commands? Just asking because when I used the wl extension I did not need to do any of this. Is this required for your wireless card?
Thanks!
-
The script is quite old - the modprobe commands used to be required, but quite possibly they are no longer required - I never got around to checking :)
-
2) No sound
I used VLC to watch a movie and all I got back was the video with no audio. I did have OSS installed. VLC did give me a warning message stating that if I were to update alsa-lib to version 1.0.23-2-g8d80d5f that it may help with the audio issue.
Perhaps there are no Linux drivers for these items yet?
Any solution to address these issues would be greatly appreciated. Thanks!
Have you tried to particularly specify OSS audio output?
FWIW, Mplayer(-nodeps) works fine with OSS.
-
Juanito:
I ran the script without the modprobe code and it worked. However, I noticed that the first time I ran the script after I made the code change I did not get connect. Some error about "fork" and "no lease". I then re-ran the script right after and I got a connection. Any thoughts why this would happen? Perhaps a timeout issue?
Thanks!
-
tinypoodle:
No luck with MPlayer(-no deps) with OSS. Still no sound. I do get sound when watching videos on YouTube via Flash though so I know that it's not an issue with my sound card.
Thanks!
-
Hmm, Mplayer-nodeps always worked for me out of the box with OSS, while I could not say the same for flashplayer...
If you get neither sound with vlc nor mplayer, that might lead to conclusion that you might have more general issues with OSS...
Have you tried installing OSS_alsa.tcz ?
-
tinypoodle:
I tried downloading OSS_alsa extension earlier but I was getting a download error. I was connected to the internet at the time so I know it's not a connection issue. I will try downloading it again.
Thanks!
-
As OSS_alsa is a metaextension, you could alternatively just download all its deps as seen here:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/tcz/OSS_alsa.tcz.dep
-
tinypoodle:
Thanks for the link but it didn't work for me after I installed it. However, after playing around with some other extensions I was able to get sound. The extensions I used;
1) alsaconf.tcz
2) alsa-oss.tcz
Although it's great to have sound now, two more issues have come up;
1) When I use headphones the sound still comes out of my internal speaker
2) I have to run the alsaconf.tcz extension to reconfigure my sound card every time I reboot. A bit of a nuisance. I saved the /etc/modprobe.conf to my backup/restore but this did not help
Thanks!
-
Hi rizzim3
Open AppBrowser and select alsa.tcz, then read what's in the info tab, it tells you how to
make you settings persistent.
-
Rich:
Not having any luck as per the instructions in the alsa extension page. I ran alsaconf, saved all the necessary files for recovery/backup, created a script to run alsasound and upon next reboot, no sound. However, when I run alsaconf, go through the entire process then load alsa then it works. I will just stick with this process until I figure out a better way.
Thanks!
-
1) When I use headphones the sound still comes out of my internal speaker
Is that with OSS or alsa running?
-
tinypoodle:
That is with alsa running. The only way I was able to get any sound was via alsaconf and then loading alsa. OSS never worked for me.
-
However, I noticed that the first time I ran the script after I made the code change I did not get connect. Some error about "fork" and "no lease". I then re-ran the script right after and I got a connection. Any thoughts why this would happen?
The udhcpc daemon runs in the background, so if you need to run the script again, you would need to kill the daemon.
To kill the daemon you first need to find its PID, which can be then used to kill it: $ ps aux | grep udhcpc
[shows PID]
$ sudo kill PID
-
Hi rizzim3
These go in filetool.lst
etc/modprobe.conf
etc/asound.state
opt/alsa
and these go in bootlocal.sh
# Start the alsa sound driver
/usr/local/etc/init.d/alsasound start
# Restore the mixer volume levels
/usr/local/sbin/alsactl restore
After you have sound working execute this to create the /etc/asound.state file.
alsactl store
I think one or two of the above steps might be missing from the info tab.
[EDIT] I could never get OSS to work either.
-
tinypoodle:
That is with alsa running. The only way I was able to get any sound was via alsaconf and then loading alsa. OSS never worked for me.
I asked because there is a known issue with jacksensing under OSS, has always worked out of the box though with alsa for me.
-
tinypoodle:
I briefly read somewhere about this issue. Was hoping it wouldn't impact me. Oh well...
-
Juanito:
I noticed in my boot script there is the following code:
pkill udhcpc
udhcpc -H box -b -i eth0
Perhaps this is the reason why it fails to establish the wireless connection the first time I try via a script (similar to yours)? However, when I immediately rerun the script I get a wireless connection without having to kill anything.
Perhaps this is the code I need to edit in order to get my wired connection working? Your thoughts?
I've been researching the udhcpc command. What is the flag -b for? It's not listed in any documentation that I can find.
Thanks!
-
udhcpc --help
-
Rich:
Your instructions were similar to what I did. Instead of putting the code in bootlocal.sh I just kept it in another script to run on an "as need basis" (I did do another test with the code in bootlocal.sh, no success either). I would get errors complaining that the files as per the code;
/usr/local/etc/init.d/alsasound start
/usr/local/sbin/alsactl restore
could not be found. Before shutting down they were there, just lost on reboot. So I added them to the filetool.lst thinking that would save them. Well, they were saved but they were also empty and hence the code could not run. The other three files;
etc/modprobe.conf
etc/asound.state
opt/alsa
were there. Maybe I'm just missing something, who knows...
Thanks!
-
Hi rizzim3
Sounds like you may need to change alsa.tcz to OnBoot, possibly alsaconf.tcz too.
-
Rich:
You may be right. I will give that a try to test it out. My goal was to reduce the number of extensions from boot up to make the boot process quicker and to not load extensions if they weren't going to be used during a login session. Just trying to keep RAM use under control.
Thanks!
-
Hi rizzim3
You're welcome, and let us know how it works out.
-
pkill udhcpc
udhcpc -H box -b -i eth0
Perhaps this is the reason why it fails to establish the wireless connection the first time I try via a script (similar to yours)? However, when I immediately rerun the script I get a wireless connection without having to kill anything.
It would be better to make the pkill line conditional, i.e. if udhcpc is running, then pkill udhcpc, else go to next command
I've been researching the udhcpc command. What is the flag -b for? It's not listed in any documentation that I can find.
-b = backgrounded
-
Rich:
Just tested the OnBoot method... it didn't work. I guess for the next little while I will have to proceed with the manual alsaconf. Not a deal breaker though, just a bit of a nuisance but thankfully the process doesn't take long. Here's hoping that the next release will take care of this issue.
Thanks for all your help.
-
Juanito:
I will look at adding a conditional statement even though I'm not very familiar with Linux coding. Something new to learn! But first I need to get my wired connection up and running... still haven't figured that issue out. Frustrating.
Thanks!
-
Hi rizzim3
Try adding sleep 2 to bootlocal.sh right above the alsasound command.
Check the following
/opt/alsa/.alsaconf should contain the number 1
etc/asound.state should start out with state.PCI { followed by a bunch of control, comment, etc stuff.
Are the file not found errors gone?
-
Rich:
Still not working.
Added sleep 2 to bootlocal.sh
I did not see any of the "file not found" errors on boot up.
/opt/alsa/.alsaconf does contain the number 1
etc/asound.state starts out with state.Generic and then further down state.SB
When I ran my "as needed basis" script (not in bootlocal.sh but the code is similar) I get a bunch of modprobe errors such as;
modprobe: can't load module snd_mixer_oss (kernel.tclocal/sound/core/oss/snd-mixer-oss.ko.gz): Operation not permitted
I did not see these errors when running the code in bootlocal.sh
Maybe I need to start fresh again, go through the process one more time to make sure I haven't missed anything, whatever that may be.
Thanks!
-
When I ran my "as needed basis" script (not in bootlocal.sh but the code is similar) I get a bunch of modprobe errors such as;
modprobe: can't load module snd_mixer_oss (kernel.tclocal/sound/core/oss/snd-mixer-oss.ko.gz): Operation not permitted
bootlocal.sh runs as root, it is possible that your script is running as user tc, which does not have the appropriate permissions to modprobe. If this is the case, you can preface the modprobe command with "sudo" in your script.
-
Hi rizzim3
My machine has the following installed
alsa
alsa-modules-2.6.33.3-tinycore
alsa-plugins
alsaconf
Lose the OSS stuff, it caused me nothing but trouble.
Get sound working again, remember to run alsactl store and see if works.
I have to hit the sack, I'll pick it up tomorrow if you need more help.
-
Rich:
I went through the process one more time but still no luck. Maybe you can spot whether or not I'm missing a step. They are as follows;
1) run alsaconf to configure alsa
2) run alsactl store
3) verified that all the files were created
4) added lines to bootlocal.sh
/usr/local/etc/init.d/alsasound start
/usr/local/sbin/alsactl restore
5) exit system with backup/restore and reboot
6) reconfirm that all alsa files are there
7) load all alsa extensions
alsa
alsa-modules-2.6.33.3
alsa-plugins
alsaconf
Thanks!
-
Hi rizzim3
After you get the sound working you need to tell alsa to save it's configuration with
alsactl store
otherwise the /usr/local/sbin/alsactl restore command in your bootlocal.sh won't have anything
to restore.
-
Rich:
I do that in step 2. Does this have to be done more then once?
-
Hi rizzim3
My mistake, I read it twice and still managed to miss it.
In step 7, you mean the kernel loads them because they are OnBoot, right?
-
Rich:
No onboot for step 7... I just do the "Download + Load" option. Perhaps I should try OnBoot to see if it works.
Thanks!
-
Umm, there is no sense in doing 'alsasound start' & 'alsactl restore' unless alsa has been loaded first.
Does not really matter if that's on boot or at any later moment.
-
tinypoodle:
That was the issue, it works now. Thanks! In my script I just added a line to load alsa before any other command. I still have the issue of the internal speaker still being on when the headphones are plugged in but in time hopefully this issue will be resolved too.
Rich:
My script which I run on an "as need basis" (i.e not in bootlocal.sh) is as follows;
tce-load -i /mnt/sdb1/tce/optional/alsa.tcz
sleep 2
sudo /usr/local/etc/init.d/alsasound start
sudo /usr/local/sbin/alsactl restore
Since the start of this thread the issues solved;
1) sound via terminal script
2) wireless internet access via terminal script
Issue outstanding;
1) wired internet connection
2) sound from internal speaker when headphones are plugged in
-
I still have the issue of the internal speaker still being on when the headphones are plugged in but in time hopefully this issue will be resolved too.
That must be particular to your sound card or its driver then.
Also check in alsamixer if there is a way to mute speakers separately, as a potential workaround.
-
Hi rizzim3
I don't have headphones so I don't know how much I can help, though I would have thought that
plugging in headphones would disconnect the speakers.
Open a terminal and type in alsamixer. Click on the horizontal maximize button so that the terminal
is full screen width. Use the left/right arrows on the keyboard to change which controls to adjust,
use up/down/pgup/pgdn to adjust levels. If you want something more user friendly install alsagui.tcz.
-
tinypoodle/Rich:
Thanks for the alsamixer tip. I tried it out but it's not really responding to commands. For example when pressing the 'm' key to mute I do see the graphical effects but it doesn't mute the sound. Can't adjust volume either and I don't even get any graphical effects. I'm assuming that I would see the two bars increase/decrease when adjusting the volume. I am using VLC so maybe they are not communicating well. I also tried Mplayer without success too.
Thanks!
-
Either you are doing something wrong, or you are not describing right, or there is something wrong with alsa...
BTW you could use alsamixer without having any sound app open, if you want to be sure to exclude any (unlikely) interaction.
-
tinypoodle:
Maybe you're right in that I may just be doing something incorrectly. I will investigate at a later date. However, not having the speaker mute when I insert the headphones is not a pressing issue at the moment. I would like to tackle the next bigger issue of not getting wired access to the internet. I do get wireless access. Note that I get wired access when using Windows 7 Starter so the network card is working.
Could it be that all I need is to load a specific extension? Any suggestions?
Thanks!
-
I am also having sound and wireless problems on my Acer Aspire, as well. A partial solution for sound is to add a file .asoundrc to your home directory. Contents below. This allows playback. Not sure if it works with the microphone.
I have not been able to get wireless to work on this netbook with TC 4.0. wl.tcz does not appear in the 4.0 repository. Copying from another repository did not work. Perhaps I am missing something in the 4.0 release
.asoundrc contents:
pcm.!default {
type plug
slave.pcm "dmixer"
}
pcm.dmixer {
type dmix
ipc_key 1024
slave {
pcm "hw:1,0"
period_time 0
period_size 1024
buffer_size 4096
rate 44100
}
bindings {
0 0
1 1
}
}
ctl.dmixer {
type hw
card 0
}
best regards,
sci_fi
-
I have not been able to get wireless to work on this netbook with TC 4.0. wl.tcz does not appear in the 4.0 repository. Copying from another repository did not work.
I see broadcom have finally got around to saying this:
Problems with > 3.0 kernels
===========================
A problem has appeared with recent 3.X.X kernels where the wl.ko driver loads but is inoperable.
The issue is related to the new bcma driver which is incompatible with this driver. The bcma driver
is analogous to the old ssb driver and bcma needs to be removed and/or blacklisted before wl
can function properly:
See if any relevant drivers are loaded:
$ lsmod | grep 'b43 \| bcma \| wl'
If any of these are installed, remove them (as root):
# rmmod b43
# rmmod bcma
# rmmod wl
Now load the new wl driver:
# insmod wl.ko
wl.ko should now be functional.
To blacklist the bcma driver and prevent it from loading in the future:
# echo "blacklist bcma" > /etc/modprobe.d/blacklist.conf
I'll try to to have a look at it this weekend.
In the meantime, maybe b43 or ndiswrapper will work?
-
Hi juanito,
Thank you for the wireless advice. I will give it a try as soon as I can and report back.
Best regards,
sci_fi
-
wl uploaded to 4.x repo
..I needed to blacklist b43, bcma and ssb for it to work
even the latest version is outdated - there are many newer broadcom devices not included
-
Hi juanito,
Thank you for uploading wl.tcz. I am making some progress.
After manually removing ssb, bcma (this one is there) and b43, I modprobe wl. At this point I activate eth1 as a wireless interface and see wireless networks. I appear to be able to connect. This driver is flaky with this kernel but I am still experimenting.
I created a file /etc/modprobe.d/blacklist. Contents:
blacklist bcma
blacklist ssb
blacklist b43
This file apparently doesn't work as bcma is still loading. Can you advise me on this? Perhaps, the tiny core blacklist file is located someplace else.
Also, another question. The processor on this netbook is 64 bit. The wl driver is in the 3.0.3 directory, not the 3.0.3-64 directory. It seems to work, but should a 64 bit version be used instead.
More as I get a little further.
Thanks, again.
sci_fi
-
I created a file /etc/modprobe.d/blacklist. Contents:
blacklist bcma
blacklist ssb
blacklist b43
Use bootcodes blackist=b43 blacklist=bcma blacklist=ssb
Also, another question. The processor on this netbook is 64 bit. The wl driver is in the 3.0.3 directory, not the 3.0.3-64 directory. It seems to work, but should a 64 bit version be used instead.
It was build as a 32bit driver, if it works, then you're using 32bit
-
Hi juanito,
Thanks for the information. I will use the blacklist cheatcodes.
Regarding, the 64bit vs 32 bit. Interesting, perhaps the specs are misleading. See below. I will try using 32 bit versions of everything.
Using 64bit modules, the WL driver does not work acceptably. After blacklisting and modprobing as described earlier. I can find wireless networks. When I attempt to log onto my network, the pc hangs. Only recourse is to re-boot.
I have had better success using the 64bit version of Porteus. Sometimes it works perfectly. Sometimes hangs as above.
No problems using Windows 7, although I, obviously, prefer not to.
Thanks again for your help.
Best regards,
sci-fi
processor and pc info:
Series AMD C-Series
Codename Ontario
Clock Rate 1000 MHz
Level 1 Cache 128 KB
Level 2 Cache 1024 KB
Number of Cores / Threads 2 / 2
Max. Power Consumption (TDP = Thermal Design Power) 9 Watt
Manufacturing Technology 40 nm
Die Size 75 mm2
Socket FT1 BGA 413-Ball
Features MMX(+), SSE(1,2,3,3S,4A, AMD-V
64 Bit 64 Bit support **********************************************
Hardware Virtualization AMD-V
Technical Specifications
Acer Aspire One 722
Operating System MS Windows 7 Home Premium (64-bit) ***********************************************
RAM
4GB
RAM Upgradable to
4GB
Hard Drive Size
500GB
Hard Drive Speed
5,400rpm
Hard Drive Type
SATA Hard Drive
Display Size
11.6
Native Resolution
1366x768
Optical Drive
Optical Drive Speed
Graphics Card
ATI Radeon HD 6250 Graphics
Video Memory
256MB
Wi-Fi
802.11b/g/n
Wi-Fi Model Broadcom
Bluetooth
Mobile Broadband
Touchpad Size 3.4 x 2.0 inches
Ports (excluding USB)
Ethernet; HDMI; Headphone; Kensington Lock; Microphone; VGA
USB Ports
3
Card Slots
5-1 card reader
Warranty/Support One-year International Travelers Limited Warranty
Size 11.2 x 7.9 x 1.0 inches
Weight 3.0 pounds
-
Regarding, the 64bit vs 32 bit. Interesting, perhaps the specs are misleading. See below. I will try using 32 bit versions of everything.
Using 64bit modules, the WL driver does not work acceptably.
..there are two choices with tinycore:
tinycore/microcore: uses 32bit everything
microcore64: uses 32/64bit kernel, 64bit kernel modules and 32bit everything else.
The wl extension was compiled to use with tinycore/microcore, not microcore64.
-
Thanks, juanito.
Everything is working when I use my own script to connect using wpa. I have trouble with wicd carried over from tc 3.8.4. Seems to connect but then hangs. If/when wicd is available on 4.x, I will try again.
Thanks again for the help. Much appreciated.
sci_fi
-
You could use the wifi.tcz extension in the meantime?
-
Hi juanito,
Wifi.tcz is great. Small, fast, fewer dependencies. Works fine. Thanks for the suggestion.
sci_fi
-
Hi everyone:
I cannot connect to internet via wifi.tcz either. My netbook has a BCM4312 wi-fi card and I use a resticted wep. Have followed all of Juanito's recommendations, but with no luck so far. :-[
The wi-fi led is on and the modules: cfg80211, lib80211_crypt_tkip, lib80211_crypt_wep, lib80211_crypt_ccmp are loaded.
Also tried with:
sudo iwconfig eth1 essid "MYESSID" key MY_10_CHARACTER_HEX_KEY
and get the following error:
"SET Encode" (8B2A): Set failed on device eth1; Invalid argment.
the dmesg | tail -20 gives:
[size=10pt]lib80211_crypt: registered algorithm 'TKIP'
ACPI Error: [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS (20110413/dswload2-316)
ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20110413/psloop-231)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.WMID.WMBA] (Node f4c47470), AE_ALREADY_EXISTS (20110413/psparse-536)
intel_rng: FWH not detected
ACPI: Marking method WMBA as Serialized because of AE_ALREADY_EXISTS error
eth1: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.100.82.38
intel_rng: FWH not detected
intel_rng: FWH not detected
intel_rng: FWH not detected
lib80211_crypt: unregistered algorithm 'TKIP'
wl 0000:01:00.0: PCI INT A disabled
cfg80211: Calling CRDA to update world regulatory domain
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'
wl 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
wl 0000:01:00.0: setting latency timer to 64
lib80211_crypt: registered algorithm 'TKIP'
eth1: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.100.82.38
CE: hpet increased min_delta_ns to 20113 nsec
[/size]
I used wicd in the past (tc-2.3) and had no problems.
Has anyone had the same problem before?
Regards,
cefcom
-
Is the firmware loaded?
-
Thank you for your quick response!
Yes, it is.
-
cefcom: I assume you are now trying it with TC 4.x. According to this advice (http://linuxwireless.org/en/users/Drivers/b43#Caveats) there could be certain conflicts with your kind of hardware.
It might help if you would attach here the results of lsmod and lspci -vnn (of course that requires the installation of 'pci-utils.tcz'). Furthermore, I'm curious which exact firmware extension you've got installed.
-
dmesg should show whether or not the proper firmware is loaded by the driver.
-
dmesg should show whether or not the proper firmware is loaded by the driver.
Well, probably most of the time. But I'm pretty sure that I've experienced within the last 18 month at least once a situation where the fact that a firmware file was missing was not obvious (i.e. no warning in the 'dmesg' output). Unfortunately I don't recall the exact hardware combination, but I believe I ran a test with one of the more "bloated cousins" (e.g. Ubuntu, Fedora or Knoppix) and was able to identify what was wrong.
-
Maro:
cefcom: I assume you are now trying it with TC 4.x.
Yes. :)
According to this advice (http://linuxwireless.org/en/users/Drivers/b43#Caveats) there could be certain conflicts with your kind of hardware.
I've read this info and since my card is the BCM4312g, it is fully supported. :D
It might help if you would attach here the results of lsmod and lspci -vnn (of course that requires the installation of 'pci-utils.tcz'). Furthermore, I'm curious which exact firmware extension you've got installed.
Here is the info you request:
lsmod:
Module Size Used by Tainted: P
lib80211_crypt_tkip 12288 0
wl 2539520 0
lib80211_crypt_ccmp 12288 0
lib80211_crypt_wep 12288 0
lib80211 12288 4 lib80211_crypt_tkip,wl,lib80211_crypt_ccmp,lib80211_crypt_wep
cfg80211 94208 0
acpi_cpufreq 12288 1
mperf 12288 1 acpi_cpufreq
cpufreq_userspace 12288 0
cpufreq_powersave 12288 0
cpufreq_stats 12288 0
cpufreq_conservative 12288 0
squashfs 24576 31
scsi_wait_scan 12288 0
zcache 12288 0
acer_wmi 20480 0
zram 12288 1
loop 16384 62
sparse_keymap 12288 1 acer_wmi
pcspkr 12288 0
atl1e 24576 0
ac 12288 0
battery 12288 0
wmi 12288 1 acer_wmi
video 16384 0
backlight 12288 2 acer_wmi,video
and lspci -vnn:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at 96280000 (32-bit, non-prefetchable) [size=512K]
I/O ports at 50f0 [size=8]
Memory at 80000000 (32-bit, prefetchable) [size=256M]
Memory at 96300000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, fast devsel, latency 0
Memory at 96200000 (32-bit, non-prefetchable) [size=512K]
Capabilities: <access denied>
00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at 96340000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: 95100000-961fffff
Prefetchable memory behind bridge: 0000000090000000-0000000090ffffff
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: 94100000-950fffff
Prefetchable memory behind bridge: 0000000091000000-0000000091ffffff
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 3 [8086:27d4] (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 00001000-00002fff
Memory behind bridge: 93000000-940fffff
Prefetchable memory behind bridge: 0000000092000000-0000000092ffffff
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1d.0 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 02) (prog-if 00 [UHCI])
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at 50a0 [size=32]
Kernel driver in use: uhci_hcd
00:1d.1 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 02) (prog-if 00 [UHCI])
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, medium devsel, latency 0, IRQ 17
I/O ports at 5080 [size=32]
Kernel driver in use: uhci_hcd
00:1d.2 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 02) (prog-if 00 [UHCI])
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 5060 [size=32]
Kernel driver in use: uhci_hcd
00:1d.3 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 02) (prog-if 00 [UHCI])
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, medium devsel, latency 0, IRQ 19
I/O ports at 5040 [size=32]
Kernel driver in use: uhci_hcd
00:1d.7 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 02) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at 96344400 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=32
Capabilities: <access denied>
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at 50c0 [size=16]
Kernel driver in use: ata_piix
00:1f.2 SATA controller [0106]: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller [8086:27c5] (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 43
I/O ports at 50d8 [size=8]
I/O ports at 50fc [size=4]
I/O ports at 50d0 [size=8]
I/O ports at 50f8 [size=4]
I/O ports at 5020 [size=16]
Memory at 96344000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller [8086:27da] (rev 02)
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: medium devsel, IRQ 11
I/O ports at 5000 [size=32]
01:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
Subsystem: Foxconn International, Inc. Device [105b:e018]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at 95100000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: wl
03:00.0 Ethernet controller [0200]: Atheros Communications AR8121/AR8113/AR8114 Gigabit or Fast Ethernet [1969:1026] (rev b0)
Subsystem: Acer Incorporated [ALI] Device [1025:019c]
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at 93000000 (64-bit, non-prefetchable) [size=256K]
I/O ports at 1000 [size=128]
Capabilities: <access denied>
Kernel driver in use: ATL1E
Firmware: wl.
I hope it helps! Thanks.
Regards,
cefcom
-
Well, 'wl.tcz' is certainly not a firmware extension, but rather contains one of the two "competing" kernel modules. The other option is AFAIK the 'b43' kernel module that should be contained in the 'wireless-KERNEL.tcz' extension.
Now, I can't quite work out whether the former extension (which you have not managed to get going) needs firmware. But I'm pretty much convinced that the 'b43' one needs the 'firmware-openfwwf.tcz' extension to be installed. Furthermore the web page I had referenced in my earlier post is AFAICT predominantly referring to 'b43' (with some information of how to change things around between the two alternatives).
I'd therefore like to suggest you read the WHOLE page really carefully (keeping in mind this issue of this unfortunate competition). Following that you might want to give the 'b43' module a try.
-
Thank-you maro.
I'll try your suggestion this weekend.
regards,
cefcom
-
Hi maro:
I tried your suggestion: using b43 driver instead.
I used a vanilla installation, where firmware-openfwwf.tcz is default.
Unfortunately, it still does not work. :-\
Not even the wi-fi led is on!
Dmesg | tail -20 tells us why:
EXT4-fs (sdb1): mounting ext2 file system using the ext4 subsystem
EXT4-fs (sdb1): mounted filesystem without journal. Opts: (null)
Adding 2931824k swap on /dev/sda5. Priority:-2 extents:1 across:2931824k
cfg80211: Calling CRDA to update world regulatory domain
intel_rng: FWH not detected
b43-phy0: Broadcom 4312 WLAN found (core revision 15)
ieee80211 phy0: Selected rate control algorithm 'pid'
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PMNL, Firmware-ID: FW13 ]
intel_rng: FWH not detected
intel_rng: FWH not detected
intel_rng: FWH not detected
usb 3-2: new low speed USB device number 2 using uhci_hcd
input: Microsoft Microsoft Wireless Optical Mouse® 1.00 as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input8
generic-usb 0003:045E:00E1.0001: input: USB HID v1.11 Mouse [Microsoft Microsoft Wireless Optical Mouse® 1.00] on usb-0000:00:1d.1-2/input0
b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
]b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website .
I'm a little confused, so let me set the record straight:
- I thought that this firmware-openfwwf.tcz was the info obtained by the b43-fwcutter.tcz, right?
- If not so, then do I need to fetch additional info with b43-fwcutter-tools.tcz?
I've noticed, that there is another firmware-broadcom.tcz in the repos. Could that be used instead.? Are they mutually exclusive?
Your help will be highly appreciated.
cefcom.
-
If not so, then do I need to fetch additional info with b43-fwcutter-tools.tcz?
Yes - see the linux wireless b43 site for details if required
-
Hi everybody:
I'm still trying to install the correct firmware for the BCM4312. But now I feel I'm getting finally there!.
Managed to download and unpack the correct archive (broadcom-wl-4.150.10.5.tar.bz2) that corresponds to the b43-fwcutter (version 012).
But when I try to install the driver to "/usr/local/lib/firmware", I get the following error message:
failed to open file: Read-only file system.
Can I just install it to other directory ( i.e., /home/tc), and then just move all the files to the desired directory?
Then, once, I have all files in the correct directory, how can I keep them there after re-booting?
regards,
cefcom
-
Hi cefcom
failed to open file: Read-only file system.
The files in that location are just links to /tmp/tcloop/firmware which is read only. If the filenames
you are trying to copy over already exist there you will get that error.
-
Don't load the firmware extension if it does not contain the firmware you need.
-
I finally got it working. Thank-you all! :) :)
This is what I did:
- Deleted all links in /usr/local/lib/firmware/b43,
- Extracted all files into /home/tc/b43,
- Copied (as root) all files in there to the directory in step 1,
- Unloaded (as root) b43 and ssb from terminal,
- Re-loaded b43,
- Opened Wifi and led lighted up, selected network, entered wep-hex-key,
- That's it!
This is how Dmesg | tail -20 looks like now:
cfg80211: Calling CRDA to update world regulatory domain
b43-pci-bridge 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
b43-pci-bridge 0000:01:00.0: setting latency timer to 64
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243)
ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243)
ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243)
ssb: Sonics Silicon Backplane found on PCI device 0000:01:00.0
b43-phy0: Broadcom 4312 WLAN found (core revision 15)
ieee80211 phy0: Selected rate control algorithm 'pid'
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PMNL, Firmware-ID: FW13 ]
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
wlan0: authenticate with 00:24:17:92:c9:ec (try 1)
wlan0: authenticated
wlan0: associate with 00:24:17:92:c9:ec (try 1)
wlan0: RX AssocResp from 00:24:17:92:c9:ec (capab=0x411 status=0 aid=1)
wlan0: associated
The only thing left to do is an extension, to save settings. ::)
regards,
cefcom