Thanks Q5Sys for the disruption...again. Of course, I'm sure you will try to defend it as helpful. Shame, though. Your behavior does NOT help the thread or the perceptions others will get.

Peace be with you_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engineor use DogPile

It was both serious and factual. If he wants answers, he's going to have to go to the people who wrote the driver. Taz admitted he doesnt have that information. The source for that information: Upstream.

Even if we wanted to do the work for him and find out the answer for him so he didnt have to apply any effort, we cant because we dont know what driver he's using and what touch hardware he's got. So the ball is in his court. (or anyone else who has this problem)

But I guess him making a comment about me is more important than him wanting to find the solution to his problem. _________________

I have misunderstood the complexities and relationships between the various elements of Puppy, and the associated apps, and have been reminded more than once which is managed by Puppy volunteers and which are controlled elsewhere.

I've also struggled with various specific elements, esp. CUPS, though that one has been relatively trouble-free for quite a while.

Now I'm looking for new trouble as I unintentionally bought a laptop that is hobbled by the UEFI nonsense and am awaiting the BETA 602-UEFI so I can test and break something ...

Puppy is a great family but sometimes we have little squabbles and sometimes things don't translate well across cultures and languages.

My son has reminded me that Aussies especially have a manner of speaking that is rather different than Americans & I recall an international student from Germany sharing that her style of speech was often misunderstood as angry/confrontational when such was not her intent.

I have not tried Fatdog, not sure why (I think I didn't like the default selection of apps), perhaps I should while I await a UEFI release of LH 602._________________Thanks! DavidHome page: http://nevils-station.comDon't googleSearch!http://duckduckgo.com
Puppy Carolina 1.3 & Lighthouse64-b602 & JL64-603

I have not tried Fatdog, not sure why (I think I didn't like the default selection of apps), perhaps I should while I await a UEFI release of LH 602.

i asked about fatdog becuase I believe lhp602's UEFI is from that. So you can check now to see if it might work for you. Once lhp602 is released, it may be different enough to negate any tests you've done with Fatdog... but its at least a reference point for you to start with._________________

I entered "exit" to return to the menu, chose Reboot then allowed Fatdog to do its thing.

It popped up a couple of screens, one including text re. "Activating radeon workaround" which too a while, then generated a badly garbled screen.

I'm guessing that I'll need to force generic video parameters at Fatdog64-612 boot so that I may get to where I can get them to set up correctly?_________________Thanks! DavidHome page: http://nevils-station.comDon't googleSearch!http://duckduckgo.com
Puppy Carolina 1.3 & Lighthouse64-b602 & JL64-603

Q5sys is right, the UEFI support I'm working on is based on FD621. As I understand it, the recommended method for booting with UEFI is to 'dd' the FD ISO to a USB Flash drive, then boot from that. That is faster than booting from an optical drive and is ideal for booting on more than one machine. It does, however require careful entry of a couple of commands in a terminal, and a flash drive that can be completely erased, i.e., not being used for something else.

On my notebook (with Nvidia graphics) I found that booting with UEFI stalled X and eventually dropped to a command prompt. However when I changed to the fbdev Xorg driver I could start X although the resolutions were very limited. Then I installed the proprietary Nvidia driver and that seems to work better. I had to upgrade the kernel to 3.8.7 for the Nvidia driver, which took me a week or so, including recompiling kernel, kernel modules and proprietary drivers, initrd, DevX, etc.

I'm also working on the documentation and adding a preliminary dialog to the Universal Installer which directs UEFI/Win 8 usage to the above UEFI Flash drive method.

I believe Ted Dog may have posted his experiences in UEFI and Live media use.

But, whether Live media or USB, as TaZoC explains, there is the possibility of drop-out to a prompt leaving any user wondering what to do next to get desktop.

Several members have had this problem and it impacts the acceptance level because the FATDOG version-600+ ISO's latest boot process is an order of magnitude different from the old methods present in past PUPs.

As we go forward, it may be prudent to have a document somewhere which describes this initial boot issue and trusty methods to overcome issues that occur trying to get to the initial desktop. In fact, it might be, also, an idea to have a boot entry at the VERY TOP of the menu which intends to be a "if you're new to FD64/LH64, start HERE!" which produces a less than optimal desktop to build/add/improve upon. But, there are other ideas, too, which could be helpful for those new.

Here to help

Q5Sys, sorry forgot, "LOL"
In case others are wondering, this refers "to the fact that I have posted that using HP equipment, I have had success in using LH64 to navigate the deskop using touch...without a mouse". What happens is that Q5Sys intentionally reframes the experience into something akin to a request for change. I make no request on ANY developer for that in this thread. I continue to report finding and experiences so that others who may see results and what they can expect.
Again, for Q5sys, I say "stop reframing anything I say into your own words as if it some request from me" I am a big enough boy to fashion my own request when those needs arise. Nowhere in your comment did you share any useful findings. Instead your attempt appears to diminish what others may find of value.

But, I sure you will follow this with one of your reframings....again. So stop, don't re-frame and for heavens sake stop repeating yourself. And use your other ID more.

"Peace be with you"_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engineor use DogPile

In case others are wondering, this refers "to the fact that I have posted that using HP equipment, I have had success in using LH64 to navigate the deskop using touch...without a mouse". What happens is that Q5Sys intentionally reframes the experience into something akin to a request for change. I make no request on ANY developer for that in this thread. I continue to report finding and experiences so that others who may see results and what they can expect.
Again, for Q5sys, I say "stop reframing anything I say into your own words as if it some request from me" I am a big enough boy to fashion my own request when those needs arise. Nowhere in your comment did you share any useful findings. Instead your attempt appears to diminish what others may find of value.

But, I sure you will follow this with one of your reframings....again. So stop, don't re-frame and for heavens sake stop repeating yourself. And use your other ID more.

"Peace be with you"

Looks like I was right.

Q5sys wrote:

But I guess him making a comment about me is more important than him wanting to find the solution to his problem.

Or have you found a solution for your middle mouse button problem and can share its solution with the rest of the community?

Edoc,
Once the next version of LHP is released, I can test it on my machine, since I can turn UEFI on and off as needed. I have a feeling though that UEFI will be a difficult task for us to tackle at first. It seems that while the Specification is firm, different vendors are implementing it in slightly different ways which is causing some issues on the user level.
Hopefully we will resolve this without too much headache though._________________

Edoc,
Once the next version of LHP is released, I can test it on my machine, since I can turn UEFI on and off as needed. I have a feeling though that UEFI will be a difficult task for us to tackle at first. It seems that while the Specification is firm, different vendors are implementing it in slightly different ways which is causing some issues on the user level.
Hopefully we will resolve this without too much headache though.

Since Fatdog64-621 appears to have solved UEFI cannot their solution be ported to LH?

As usual I don't understand all that is behind the construction of the different Puplets ... _________________Thanks! DavidHome page: http://nevils-station.comDon't googleSearch!http://duckduckgo.com
Puppy Carolina 1.3 & Lighthouse64-b602 & JL64-603

Edoc,
Once the next version of LHP is released, I can test it on my machine, since I can turn UEFI on and off as needed. I have a feeling though that UEFI will be a difficult task for us to tackle at first. It seems that while the Specification is firm, different vendors are implementing it in slightly different ways which is causing some issues on the user level.
Hopefully we will resolve this without too much headache though.

Since Fatdog64-621 appears to have solved UEFI cannot their solution be ported to LH?

As usual I don't understand all that is behind the construction of the different Puplets ...

Well i think that's the difference between 'Theory' and 'Reality'. In Theory it should be interchangeable. If TazOC is having troubles with it... then it isnt. Why that's the case, I have no clue._________________

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