Lighthouse 64 601 Beta (Closed, see first post)
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.edoc wrote:I took his post as humorous ... he just forgot the LOL ...
Here it is
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.
Life in a shrinking world ...
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.
Life in a shrinking world ...
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Can you disable UEFI in the BIOS? Some systems allow you to do that. (mine is one of them) There also maybe a non UEFI bios image you can flash, and then flash back the stock bios after 602 comes out.edoc wrote:
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 ...
Does the Fatdog64 with UEFI work for you?
HP made no provision in the Pavilion g7 for disabling the UEFI.
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 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.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
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.edoc wrote:HP made no provision in the Pavilion g7 for disabling the UEFI.
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.
OK, just downloaded Fatdog64-621 & burned a DVD.
Booted the HP Pavilion g7 from the DVD.
I interrupted the autoboot then chose the first EFI menu.
It ran through a "Device mapping table" then dropped to "Shell>"
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?
Booted the HP Pavilion g7 from the DVD.
I interrupted the autoboot then chose the first EFI menu.
It ran through a "Device mapping table" then dropped to "Shell>"
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?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
UEFI support
edoc,
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.
Installing FD or LH to a GPT (GUID Partition Table, UEFI standard) hard disk looks a bit difficult to me, and a mistake might keep Windows 8 from booting.
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.
TaZoC
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.
Installing FD or LH to a GPT (GUID Partition Table, UEFI standard) hard disk looks a bit difficult to me, and a mistake might keep Windows 8 from booting.
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.
TaZoC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
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"
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"
Thanks for the feedback ... and just for clarification ... we rolled-back the supplied nightmare that is the Microsoft #8 version of windows to #7 on both of our HP Pavilion g7's.
We have licenses for #7 for both machines so as to not risk any problems with MS.
Our son is actively using a highly-modified #7 on his, my version is there as a just-in-case but I never use it, and I hope to never need to.
I usually install Puppy in Frugal mode, though right now I'm testing from the DVD, I will locate a USB stick and try that as well.
Frugal on the HDD makes the most sense for the way that I use Puppy but a small USB stick is low-profile enough to be OK.
Thanks!
We have licenses for #7 for both machines so as to not risk any problems with MS.
Our son is actively using a highly-modified #7 on his, my version is there as a just-in-case but I never use it, and I hope to never need to.
I usually install Puppy in Frugal mode, though right now I'm testing from the DVD, I will locate a USB stick and try that as well.
Frugal on the HDD makes the most sense for the way that I use Puppy but a small USB stick is low-profile enough to be OK.
Thanks!
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Looks like I was right.gcmartin wrote: 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"
Or have you found a solution for your middle mouse button problem and can share its solution with the rest of the community?Q5sys wrote:But I guess him making a comment about me is more important than him wanting to find the solution to his problem.
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?Q5sys wrote: 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.
As usual I don't understand all that is behind the construction of the different Puplets ...
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
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.edoc wrote:Since Fatdog64-621 appears to have solved UEFI cannot their solution be ported to LH?Q5sys wrote: 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.
As usual I don't understand all that is behind the construction of the different Puplets ...
I always feel kinda dumb when it comes to these things.
While I worked in IT for a while I never was properly trained in coding and always mess up when I try to compile things ... sigh.
Standing by and praying for TazOC.
While I worked in IT for a while I never was properly trained in coding and always mess up when I try to compile things ... sigh.
Standing by and praying for TazOC.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Lighthouse 64 6.02 Beta 2
I've uploaded Lighthouse 64 602 Beta 2
The new thread is here: http://www.murga-linux.com/puppy/viewto ... 846#710846
Regards,
TaZoC
The new thread is here: http://www.murga-linux.com/puppy/viewto ... 846#710846
Regards,
TaZoC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]