MX-19 Beta 3 Feedback

Message
Author
User avatar
dolphin_oracle
Developer
Posts: 22089
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-19 Beta 3 Feedback

#291 Post by dolphin_oracle »

bpr323 wrote: Wed Oct 09, 2019 8:58 pm
d) as above, let's create gpt partitions table (but no partitions) and format entire disk to Ext4 -> FAIL
e) let's create a new gpt partitions table and leave the disk unformatted - SUCCESS
I would love to see /var/log/minstall.log files for those 2 install cases.

BTW, if you formated the whole disk, you actually just made 1 big partition, so partition was involved, just not multiple partitions. This is an important distiction for the debugging, and it makes the difference between d and e interesting.

Also, what options did you use to create your LUM usb device? "Full-Featured" or "dd" mode.
Last edited by dolphin_oracle on Thu Oct 10, 2019 12:37 pm, edited 1 time in total.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
dolphin_oracle
Developer
Posts: 22089
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-19 Beta 3 Feedback

#292 Post by dolphin_oracle »

whoops double post
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#293 Post by bpr323 »

dolphin_oracle wrote: Thu Oct 10, 2019 11:48 am
SwampRabbit wrote: Thu Oct 10, 2019 11:16 am
dolphin_oracle wrote: Thu Oct 10, 2019 11:01 am doesn't surprise me necassirly with at TV, but you can use the Display settings app to turn off the "launch when connected" feature. I forget the exact name.
Thanks, I’ll try and hunt that down then. I just don’t remember it ever doing that before.
Defaults for the display app changed on beta 3.
Yeah, it screwed up my dual display - I have a 27" Dell attached to X1 g4 across HDMI, and it has been playing up since I installed 19b3.
Once I set up display app for both screens - it stays on. Once I reboot - the 27" doesn't get a signal at all until I set to mirror the screens, and then it changes res to crazy 1228 x 1444 or smth like that .. very erratic and unstable

User avatar
Eadwine Rose
Administrator
Posts: 14471
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Beta 3 Feedback

#294 Post by Eadwine Rose »

I had display off occur, solved it using xrandr:

Code: Select all

/usr/bin/xrandr --output VGA-0 --off --output DVI-D-0 --mode 1920x1080 --pos 1920x0 --rotate normal --output HDMI-0 --primary --mode 1920x1080 --pos 0x0 --rotate normal
For me the HDMI monitor turned off.

No issues so far in beta3 for me though.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#295 Post by bpr323 »

dolphin_oracle wrote: Thu Oct 10, 2019 12:34 pm
bpr323 wrote: Wed Oct 09, 2019 8:58 pm
d) as above, let's create gpt partitions table (but no partitions) and format entire disk to Ext4 -> FAIL
e) let's create a new gpt partitions table and leave the disk unformatted - SUCCESS
I would love to see /var/log/minstall.log files for those 2 install cases.

BTW, if you formated the whole disk, you actually just made 1 big partition, so partition was involved, just not multiple partitions. This is an important distiction for the debugging, and it makes the difference between d and e interesting.

Also, what options did you use to create your LUM usb device? "Full-Featured" or "dd" mode.
Sorry, I didn't keep the logs after the final try which ended with successful install - I was stoked it finally worked for me!
I assumed the "live" logs would have been blown away anyway. But it's really easy to replicate just following my use cases :)
For LUM I used full-featured + optionals ticked for force gpt and force ext4 even if it exists
I do have some photos I was taking of Gparted screen with (i)'s related to missing data in failed partitions - do you want them?
In essence, the only path that worked was to create a new gpt partitions table and leave it unformatted w/o creating any actual partitions.
I'm guessing you want to make Minstall to trap the errors and do some overriding steps to process them as exceptions?
The biggest problem is the use case where user installs side by side with to keep a Windows install - then my "whole-disk" workaround would be a disaster.
But I didn't try those scenarios with "custom" (manual partitioning) install - if I need Windows, I'll install it on a "free" VMware workstation Player/Pro.
I think it's a deathwish to try and install Linux side by side with Win on the same disk - unless you're a masochist, of course

User avatar
Eadwine Rose
Administrator
Posts: 14471
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Beta 3 Feedback

#296 Post by Eadwine Rose »

If you could redo it and then do save the logs. It would be most helpful.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
dolphin_oracle
Developer
Posts: 22089
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-19 Beta 3 Feedback

#297 Post by dolphin_oracle »

bpr323 wrote: Thu Oct 10, 2019 1:19 pm
dolphin_oracle wrote: Thu Oct 10, 2019 12:34 pm
bpr323 wrote: Wed Oct 09, 2019 8:58 pm
d) as above, let's create gpt partitions table (but no partitions) and format entire disk to Ext4 -> FAIL
e) let's create a new gpt partitions table and leave the disk unformatted - SUCCESS
I would love to see /var/log/minstall.log files for those 2 install cases.

BTW, if you formated the whole disk, you actually just made 1 big partition, so partition was involved, just not multiple partitions. This is an important distiction for the debugging, and it makes the difference between d and e interesting.

Also, what options did you use to create your LUM usb device? "Full-Featured" or "dd" mode.
Sorry, I didn't keep the logs after the final try which ended with successful install - I was stoked it finally worked for me!
I assumed the "live" logs would have been blown away anyway. But it's really easy to replicate just following my use cases :)
For LUM I used full-featured + optionals ticked for force gpt and force ext4 even if it exists
I do have some photos I was taking of Gparted screen with (i)'s related to missing data in failed partitions - do you want them?
In essence, the only path that worked was to create a new gpt partitions table and leave it unformatted w/o creating any actual partitions.
I'm guessing you want to make Minstall to trap the errors and do some overriding steps to process them as exceptions?
The biggest problem is the use case where user installs side by side with to keep a Windows install - then my "whole-disk" workaround would be a disaster.
But I didn't try those scenarios with "custom" (manual partitioning) install - if I need Windows, I'll install it on a "free" VMware workstation Player/Pro.
I think it's a deathwish to try and install Linux side by side with Win on the same disk - unless you're a masochist, of course
if any installs are still present, we copy it over to /var/log on installation.

I saw that only your one path worked, and the difference between the logs for d and e may tell us *why*. that's why the logs are so verbose. anything less than crazy amounts of output leaves us guessing to an extent.

I was working on a theory, but your stated method doesn't fit that theory 100%, so even the succesfull log will be useful.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
bpr323
Posts: 172
Joined: Thu Jun 20, 2019 10:17 am

Re: MX-19 Beta 3 Feedback

#298 Post by bpr323 »

Eadwine Rose wrote: Thu Oct 10, 2019 1:02 pm I had display off occur, solved it using xrandr:

Code: Select all

/usr/bin/xrandr --output VGA-0 --off --output DVI-D-0 --mode 1920x1080 --pos 1920x0 --rotate normal --output HDMI-0 --primary --mode 1920x1080 --pos 0x0 --rotate normal
For me the HDMI monitor turned off.

No issues so far in beta3 for me though.
Yes, it cut off the HDMI signal for me too.
Your code is Geek porn to me (and I say it very respectfully!)
I'm over trawling countless forums in search of ready answers, and I can't come up with s**t like "xandr" solutions - I don't even know what this is )))
Why change the display app and screw it up in the 1st place?? Why ?? :rolleyes:
negative ROI - whoever the genius who committed this code to trunk must roll it back and fix it asap, this is NOT some cosmetic fluffy dice like overlapping panel icons. DOH!

SwampRabbit
Posts: 3602
Joined: Tue Jun 14, 2016 2:02 pm

Re: MX-19 Beta 3 Feedback

#299 Post by SwampRabbit »

bpr323 wrote: Thu Oct 10, 2019 1:32 pm I'm over trawling countless forums in search of ready answers, and I can't come up with s**t like "xandr" solutions - I don't even know what this is )))
Why change the display app and screw it up in the 1st place?? Why ?? :rolleyes:
negative ROI - whoever the genius who committed this code to trunk must roll it back and fix it asap, this is NOT some cosmetic fluffy dice like overlapping panel icons. DOH!
There were a lot of changes to XFCE going from 4.12 and 4.14, especially when it comes to monitors and graphical related items. So it’s not always MX created specifically and not always something that is known until further testing of the beta and XFCE 4.14 is done.

Example: the XFCE 4.14.1 panel was released recently, this wasn’t created by the MX team, just repackaged for MX.

Just try and relax a bit :hug:
Your testing is great and appreciated, but let’s keep it cool.
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.

User avatar
Eadwine Rose
Administrator
Posts: 14471
Joined: Wed Jul 12, 2006 2:10 am

Re: MX-19 Beta 3 Feedback

#300 Post by Eadwine Rose »

bpr323 wrote: Thu Oct 10, 2019 1:32 pm Yes, it cut off the HDMI signal for me too.
Your code is Geek porn to me (and I say it very respectfully!)
That code is in my autostart in sessions and startup and makes sure the monitors are on and in the positions I want them to be.

arandr is software that you start where you can move your screens around and then when you are at a point you like them can save what is there in a line like my code right there so it automatically configures the screens when you run it in a terminal as a command.


negative ROI - whoever the genius who committed this code to trunk must roll it back and fix it asap, this is NOT some cosmetic fluffy dice like overlapping panel icons. DOH!
Please be a little more nice than this, people in the know might be inclined to be less helpful than they have been so far.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

Locked

Return to “General”