Semme wrote:You mean this original?
Kernel drivers are SPECIFIC. Skami I'm sure simply forgot to include the 64 bit after amd.
Saturdays was Slacko. Yesterday, Bionic.
Nowhere did I suggest using a cmdline.
I realize that issue is on me, as I used the cli, however a new user makes certain assumptions, based on past experience. For me, using a netbook is a bit fiddly as is, so I try to use the cli and an app launcher as much as possible so as not having to rotate through the app menu constantly.
I have no idea where the .pet package came from, just that it was default for the system when I used pkg.
At this point the best thing to do is to reinstall the system, as I also discovered that there isn't any active power management, so this way, I can skip the cruft and just install the .pet file you suggest.
I hope that you aren't taking my questions and comments as criticism. However, it is important for me to "think out loud", both to document the reactions of a new user, but also speculate about the structure, robustness and features (or lack thereof) of the system in question and try to put it in context. Any questions I ask are exactly because there isn't that much documentation (and some of what there is are made up of dead links) and I need to learn someway.
To be honest, if I can get this working, I might become a huge fan, because I can see a lot of nice things with Puppy Linux, but when you bump into obstacles, questions need to be asked. I am definitely not dissing Puppy, just trying to understand, though I do admit that some frustration creeps in from time to time.
OK, the driver works. On a reboot however, wlan has to be reconfigured with loading a profile that I have setup and then running auto dhcp before an actual, functioning connection to the wireless network is functioning. Not sure what the default behavior is on this...