Hi Nooby,
nooby wrote:
Would that allow me to boot Lupu520 on my Acer D250 and D255?
Acer model numbers are very confusing - because those model has submodels, e.g. D255 can have either N450 or N550 CPU, depending on the submodels, and I'm quite sure the guts can be different also (wireless can use Atheros, Broadcomm, or Realtek etc). I know that EM350 is quite similar to one of the Acer AOA models, but can't remember exactly. Anyway, the point is there is no point comparing the model numbers - if we want to compare, we need to compare the guts rather than the model numbers.
Anyway, whether that allows you to boot Lupu520 or not, depends on what makes them fail to boot in the first place. There is no other way but trial and error ... I've downloaded Lupu520 but haven't played with it yet, so I can't say. What I can say is, in my case, Fluppy 010 and 011 failed to boot because of the brcm80211 wireless driver (the onboard wireless card on EM350 is broadcomm) froze the system during boot time. There are two drivers for this card - the open source (preferred) brcm80211 driver, and the closed-source (and older) wl driver. As shipped, Jemimah blacklisted wl driver and let brcm80211 takes over. I just swapped this configuration - I blacklisted brcm80211 and remove wl from the blacklist.
I fai lto get what " just activate wl and blacklist brcm" stand for.
This normally can be done through GUI (through the control panel), but of course you need to be able to boot first if you want to use the control panel --- so for me, I edited the SFS to change this. To "edit the SFS", I actually unpack the flp-011.sfs (using unsquashfs), edit the /etc/rc.d/MODULESCONFIG using geany (change the line that contains SKIPLIST), and the pack it back (using mksquashfs). I think there's a GUI somewhere to do this automatically - but again, you need to be able to boot first before you can use the GUI. You can do this for any recent puppies - including Lupu520.
White list and blacklist brcm ahh you mean broadcom ethernet or something.
Yes I'm referring to blacklisting and whitelisting the wireless driver for broadcomm.
So if I do that on all my puppies that fail to boot then they will boot?
As I said - we need to know what causes the failure to boot first ...
Sorry maybe should ahve sent you a PM.
It's ok. The comment may be useful for others also, and they may be able to help you more than mine.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]