I'm just wondering why my connection is flakey (wireless on the Pandora) when I connect from the kernel commandline string. Most of the time it doesn't connect at all, with the as mentioned earlier "disassociated" (reason 1) message after it was authenticated. Then when it does connect it only stays up a few minutes and then dies.

I made a simple script with the same commands that are in system-init script for wireless, using udhcpc, and it seems to work fine, as long as I kill wpa_supplicant before hand. It's been up a few hours now.

No big deal, just a bit perplexing, for me at least._________________Puppy Linux Blog - contact me for access

I'm just wondering why my connection is flakey (wireless on the Pandora) when I connect from the kernel commandline string. Most of the time it doesn't connect at all, with the as mentioned earlier "disassociated" (reason 1) message after it was authenticated. Then when it does connect it only stays up a few minutes and then dies.

Is the wlan0 a module, or do you built it in to the kernel? Either way, sometimes the driver needs more time to initialise (3 seconds of waitdev may not be enough). When you lost the connection does dmesg say anything about it?

Also - if it is certain kind of atheros, you may want to disable hardware encryption ...

Quote:

I made a simple script with the same commands that are in system-init script for wireless, using udhcpc, and it seems to work fine, as long as I kill wpa_supplicant before hand. It's been up a few hours now.

Is the wlan0 a module, or do you built it in to the kernel? Either way, sometimes the driver needs more time to initialise (3 seconds of waitdev may not be enough). When you lost the connection does dmesg say anything about it?

It's a module and I have waitdev=5, but that seems not the problem, I'm sure the device is ready, it's probably crappy code (either driver or firmware.. it is broadcom after all ).

The error in dmesg I get is that it is all good, associated, then deauthenticated (reason=1) , and this can happen when I try it from my script too. So, it's like I said crappy driver/firmware I believe._________________Puppy Linux Blog - contact me for access

Works fine
It needs better icons, and 10 more lines of code to update icons with "master" level (a la xo-battery monitor).
Though I can see jamesbond already compiled retrovol-08 for a2

BTW have you removed /etc/astate.conf from your build. Iy may cause trouble.

Edit: "funny" spelling _________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too Last edited by mavrothal on Tue 10 Sep 2013, 11:38; edited 1 time in total

I'm sure the device is ready, it's probably crappy code (either driver or firmware.. it is broadcom after all Rolling Eyes ).

Broadcom ... that explains

Quote:

I made this insanely simple volume control with the raspberry pi in mind a few months back. Doesn't work on Pandora as alsamixer reports no adjustments Confused

Anyway, take a look if you want here.

I grabbed in case I need it later. Alpha2 is almost ready (I've got that SM 2.20 to compile after more than 10 attempts ), if you check the tickets section you can see the changes, let me now if there is anything else you want to highlight.

EDIT: I compiled git too. If you want the gitk gui then install tcl/tk.

Noticed
I compile xserver 1.14-master now. It compiled OK (!) according to the BLFS instructions (not patched), tough saving to the save file in the stick I got ext4 errors so I recompile now.
BTW the resize savefile utility defaults to "fd64save.ext4" _________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

Works fine
It needs better icons, and 10 more lines of code to update icons with "master" level (a la xo-battery monitor).

Yeah I guess, then that would make a "status" icon , but then I have to poll the sound state, removing the simplicity! I did say it was insane.

mavrothal wrote:

BTW have you removed /etc/astate.conf from your build. Iy may cause trouble.

Yes (/etc/asound.conf).

Pandora has an analog physical volume wheel, may even be an analog pot! I'm not going to pull it apart to find out. I suppose this is easier given the intended audience is gamers._________________Puppy Linux Blog - contact me for access

I'm just posting this here because FD-Arm is using pkgtools and slapt-get for package management. I don't advise using it unless you are a developer. It may come in handy for jamesbond and mavrothal, possibly others until they become comfortable with pkgtools..

I'm just posting this here because FD-Arm is using pkgtools and slapt-get for package management. I don't advise using it unless you are a developer. It may come in handy for jamesbond and mavrothal, possibly others until they become comfortable with pkgtools..

Thanks Mick, I'll definitely throw this in for the next release.

One of the reasons I avoid PET packages is that I don't want people to download PETs from this forum and try to run it on FatdogArm (we had enough of that problems in Fatdog64 when we started ... )

FatdogArm has a bunch of package-making tools, other than pkgtools I also use paco. Combined together they are (I think) better than new2dir/dir2pet and friends. Pkgtools also makes it easy to add packages off-line (e.g. adding a new packages into an exploded squashfs-root - so one can easily "remaster" the base SFS). I really need to document that process later - perhaps in the article about FatdogArm adoption.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum