[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

*** This bug is a duplicate of bug 581571 *** https://bugs.launchpad.net/bugs/581571 new bug is 581571 ** This bug has been marked a duplicate of bug 581571 Via Epia M6000 installs, but reboots when login attempted -- Epia-M6000 display problems & hang https://bugs.launchpad.net/bugs/357

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

Hm. I would recommend filing a bug with the instructions at so you can send the report on a stable computer. Use "xorg" for the package name. Then just make this bug a duplicate of the new one. Thanks! -- Epia-M600

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

I verified that python-launchpadlib was already installed. I tried again. Apparently, this is some form of text only browser. I was able to enter my e-mail address, and password, but the continue link remains inactive, my only choice is to cancel. What should I do? -- Epia-M6000 display problems

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

The only way I can execute that command on that computer is if I login to a text only window. Remember, the problem with this system is that it will reboot if I attempt to login to the GUI. When I did that and ran that command, some of the stuff that went buy implied that it expects a GUI interfac

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

OK, I'm sorry for all the confusion. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 357900 This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

I installed using the i386 disk. I did not see any option to select a different processor model, or I would have tried it. The messages that flash by when booting imply that the i686 stuff got installed. I would be happy to re-install on this machine if you can tell me how to force a different pr

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

OK, I just realized that you probably _are_ running a 386 kernel already, is that correct? Sorry, when you said "Ubuntu i386" I thought you were making a mistake and meant "Ubuntu x86". -- Epia-M6000 display problems & hang https://bugs.launchpad.net/bugs/357900 You received this bug notification

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

Oh, sorry about that, I'm running AMD64 so the -386 kernel wasn't listed on my box. Since I now see it is available for the x86 installs, could you try installing a 386 kernel and see if the problem goes away? Thanks. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- Epia-M6000 di

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

If it is a processor issue, all that would have to be done is reclassify the processor as a lower level processor. The install image is called i386, not i686, so one gets the impression that any intel like processor, i386 or above should work. If there is a way to force the installer to use a di

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

Well, if you hadn't said anything about cmov I would have thought this was definitely an xorg bug. It's slightly possible it could be a processor issue, but I think it's very unlikely that your computer would get as far as the desktop at all in that case. Anyway, if it really is a cmov issue, then

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

I am not sure that xorg is correct. My guess is that the installer is misidentifying the processor on this board. This computer uses a via processor (Samuel 2) that is one instruction (cmov) short of a 686 processor. It appears that every linux I have installed fails because the installer ident

[Ubuntu-x-swat] [Bug 357900] Re: Epia-M6000 display problems & hang

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bug