General TC > Tiny Core Netbooks
Dell Mini 9
h-munster:
Thank you for the suggestions!
"ifconfig eth1 up" alone did the trick. It's now working in my bootlocal.sh.
Just curious, why does one now have to blacklist the Broadcom modules and manually start the wireless interface? -- I don't recall having to make these moves on earlier versions of TC.
The only thing left is to figure out why TC boots into the console, instead of Xvesa.
Thanks!
Juanito:
--- Quote from: h-munster on July 27, 2010, 03:20:53 PM ---Just curious, why does one now have to blacklist the Broadcom modules and manually start the wireless interface? -- I don't recall having to make these moves on earlier versions of TC.
--- End quote ---
You're not blacklisting the broadcom module, you're blacklisting the reverse engineered in-kernel module (b43) - wl is the broadcom module.
b43/ssb were not in earlier kernels/versions of tc, hence there was no need to blacklist them.
As mentioned elsewhere, you'd possibly get more functionality out of using b43 and firmware rather than wl.
h-munster:
--- Quote ---You're not blacklisting the broadcom module, you're blacklisting the reverse engineered in-kernel module (b43) - wl is the broadcom module.
--- End quote ---
Oh. That's correct. Thanks for the reminder.
--- Quote ---As mentioned elsewhere, you'd possibly get more functionality out of using b43 and firmware rather than wl.
--- End quote ---
Thank you for the suggestion. I might try it, but installing the firmware seems a little involved, and there are a few variables which are unknown to me.
It looks like I need to compile version 013 of b43-fwcutter. I don't think that I can use b43-fwcutter.tcz in the repository, because it is version 012. So, apparently I must have a compiler (which I guess means installing gcc.tcz) and headers for libc. Which extension contains the libc headers?
These seem to be the instructions for installing the firmware for my wireless card with kernel 2.6.33.3: http://linuxwireless.org/en/users/Drivers/b43#fw-b43-lp However, in TC, to which directory do I install the firmware? TC hasn't a "/lib/firmware" directory nor a "/usr/local/lib/firmware." I did find "/sys/firmware."
By the way, I solved the problem with TC booting into a console instead of Xvesa. I had cleaned out out all of the config files in the /home/tc directory, assuming that they would be automatically repopulated after booting TC 3.0. I had no ".profile" and no ".Xdefaults" (which explains why I wasn't seeing any transparent aterms). I am still not sure what caused the strange resolution behavior that I experienced.
tinypoodle:
It's /lib/firmware
You might temporarily want to load the firmware-*-tinycore.tcz extension to get the path structure, or alternatively just look at firmware-*-tinycore.tcz.files ;)
Juanito:
--- Quote from: h-munster on July 28, 2010, 04:27:22 AM ---Thank you for the suggestion. I might try it, but installing the firmware seems a little involved, and there are a few variables which are unknown to me.
It looks like I need to compile version 013 of b43-fwcutter. I don't think that I can use b43-fwcutter.tcz in the repository, because it is version 012. So, apparently I must have a compiler (which I guess means installing gcc.tcz) and headers for libc. Which extension contains the libc headers?
These seem to be the instructions for installing the firmware for my wireless card with kernel 2.6.33.3: http://linuxwireless.org/en/users/Drivers/b43#fw-b43-lp However, in TC, to which directory do I install the firmware? TC hasn't a "/lib/firmware" directory nor a "/usr/local/lib/firmware." I did find "/sys/firmware."
--- End quote ---
To compile, you just need to use the appbrowser to download/install compiletc - this will get all of the required extensions for you.
You can create /lib/firmware, copy the firmware files to there and make your own extension out of it. /usr/local/lib/firmware would probably also work, but I didn't try this myself.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version