did you try:bark_bark_bark wrote:I need Broadcom Drivers for ArchPup 12.12.2. If there were drivers built-in, they're not supporting my wifi device.
Code: Select all
modprobe b43
did you try:bark_bark_bark wrote:I need Broadcom Drivers for ArchPup 12.12.2. If there were drivers built-in, they're not supporting my wifi device.
Code: Select all
modprobe b43
Code: Select all
modprobe -D synaptics_i2c
Actually, you are totally wrongstifiling wrote:mav, you're not overjoyed about the adrv idea are you? you don't feel as if the points brought up, as the reasons for using it, are strong points?.
Yes, but still no luck.stifiling wrote:did you try:
Code: Select all
modprobe b43
If you are trying to use Pwireless2 suggest you edit /etc/rc.d/MODULESCONFIG to put b43 into the 'addlist' (don't forget the spaces) and reboot....bark_bark_bark wrote:Yes, but still no luck.stifiling wrote:did you try:
Code: Select all
modprobe b43
Absolutely so, and here's the reasons why:mavrothal wrote:Now about those hard core Arch users... Are you seriously targeting these guys with Archpup?...
I've tried compiling the Broadcom wl driver - it compiles OK - but doesn't load properly to create wlan0 and doesn't generate any error messages to give clues why not - so I'm currently stumped.bark_bark_bark wrote:That didn't work either. I think the b43 module doesn't support my device. Somebody could compile a better b43 module though.
this should be a step in the right direction towards getting it compiled and working:bark_bark_bark wrote:yes, but b43 is a folder (if that is what you want to know). I know almost nothing about it. All I know is that it is a Broadcom device. Neither lina-lite 005 or ArchPup 12.12.2 has hardinfo (and that are all the puppies I have).
EDIT: Chipset is BCM4313
I said it from the beginning, is your baby.stifiling wrote:mavrothal wrote: Based on that comment though....this is probably an audience we'd be better off just ignoring, right?
If there's a better solution it a be nice to hear, but presently it's sounding like the solution is to "just ignore them".
I worked my way through this. I must say pipes and redirectionmavrothal wrote:Scooby, nooby, et all,
But you have to learn. Right? so here we go.Make sure you know what to do and how to boot your system if you get a "kernel panic", "can not find files", etc...Code: Select all
mkdir initramfs cd initramfs gunzip -c /path/to/initrd.gz | cpio -i # apply patches/modify initramfs mv /path/to/initrd.gz /path/to/initrd.gz.orig find . -print | cpio -H newc -o | gzip -9 > /path/to/initrd.gz
Yes. If you want a CD, you must rebuild the ISO with the new initrd.gz and burn it.Scooby wrote: In the last command do you write the initrd.gz straight into ISO?
Or do you have another script that creates ISO?
I get "bash: /mnt/testdisk/initrd.gz: cannot overwrite existing file"
Maybe cause ISO is mounted read-only?
No. "gzip" doesScooby wrote:Does newc ad any compression?
I agree that the archapps.sfs should also be included on the iso as the ydrv. and the wm.sfs as the adrv....and the main.sfs as 'base'.mavrothal wrote:And if you want to offer a no-apps ISO so Arch users will customize their sticks, while the rest will just pass (without even a GUI package manager), is your choice.
I just never figured out why the picky Arch users can not just skip the apps SFSs if included?... But that's probably because I'm not an Arch user.
Code: Select all
pacman -S xfce4
Code: Select all
pacman -Sf xfce4