[KM400] openchrome driver unable to find video mode

[tiwaz]

Card: VIA VT8378 Integrated Video
module version: via 0.2.901
Linux version 2.6.24-19-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)

X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Ubuntu (xorg-server 2:1.4.1~git20080131-1ubuntu9.2)
Current Operating System: Linux ubuntu 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686
Build Date: 13 June 2008 01:08:21AM

I've tried to install Ubuntu 7.10 on 2 different laptops produced by MiTAC and both were unable to load Live CD: the computers froze after the Ubuntu logo + progress bar with a blank screen.

In the case of upgrading to Ubuntu 7.10 from 7.04 via Update Manager, the computers did it but were unable to boot: the progress bar stops loading at around 70% and the laptops' caps-lock led starts blinking. 1 out 5 reboot attempts are successful and make Ubuntu boot properly on the computers.

Both computers use VIA chipsets, this might be a driver or hardware compatibility issue. Ubuntu 7.04 worked perfectly on both computers earlier on.
[lspci]
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge [1106:3205]
     Subsystem: Mitac Unknown device [1071:8375]
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video [1106:7205] (rev 01) (prog-if 00 [VGA controller])
     Subsystem: Mitac Unknown device [1071:8375]

[tiwaz (ft1978)]

We've just received reports that also MiTAC produced machines with SiS chipsets make exactly the same symptoms. In the case of SiS chipsets, according to Ubuntu forum posts, the 6.10 version was the last one that supported them.

[James Collier (james-collier412)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[tiwaz (ft1978)]

Yeah, I've just tried 8.04.1 on my Mitac Laptop (/w VIA chipset) and
Live CD froze at:
"running local boot scripts (/etc/rc.local)"
We tried Ubuntu on a new Mitac-based SiS chipset laptop too and
install froze when the orange bar was loading.
So the problem definitely still persists, unfortunately.

On Sat, Aug 30, 2008 at 2:53 PM, James Collier
<email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in advance.
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> --
> Ubuntu 7.10 Gutsy doesn' t run on MiTAC laptops
> https://bugs.launchpad.net/bugs/158999
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[James Collier (james-collier412)]

Ok, thanks very much for your bug report.
I'm assigning this bug to the linux kernel package.
Could you provide some more information?
If possible:
* kernel version (probably (2.6.24-?)
* when it "freezes" press alt-F1 or ctrl+alt+F1, you should get a black screen with white text, can you record any messages printed there?
Thanks in advance!

[tiwaz (ft1978)]

Hi,
Attached please find the screenshot I've just taken. So it is kernel
package 2.6.24-19-generic.
Please note that up to version 7.04 Ubuntu worked on my MiTAC /w VIA
chipset notebook. The problem's begun since 7.10 came out.
Have no information about SiS chipset ones in this respect.
Best of luck to finding the bug.

On Sun, Aug 31, 2008 at 3:17 AM, James Collier
<email address hidden> wrote:
> Ok, thanks very much for your bug report.
> I'm assigning this bug to the linux kernel package.
> Could you provide some more information?
> If possible:
> * kernel version (probably (2.6.24-?)
> * when it "freezes" press alt-F1 or ctrl+alt+F1, you should get a black screen with white text, can you record any messages printed there?
> Thanks in advance!
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: None => linux
>
> --
> Ubuntu 7.10 Gutsy doesn' t run on MiTAC laptops
> https://bugs.launchpad.net/bugs/158999
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[James Collier (james-collier412)]

Reassigning to casper. This doesn't look like a kernel problem, probably just a configuration problem.
You might find it useful to do a google search such as "ubuntu laptop freezes at running local boot scripts"
and have a look around the forums at ubuntuforums.org

When you get to the stage of the screenshot taken below could you run the following commands ond post the output files here:
You may need to plug in a USB device (should auto-mount under /media/*)
- dmesg > dmesg.log (cp ~/dmesg.log /media/usb_key)
- sudo lspci -vvnn > lspci-vvnn.log (cp ~/lspci-wnn.log /media/usb_key)
- cat /var/log/Xorg.0.log > Xorg.log (cp ~/Xorg.log /media/usb_key)
You may also try running:
sudo dpkg-reconfigure xserver-xorg
sudo /etc/init.d/gdm restart

[tiwaz (ft1978)]

Hi,
I tried the commands after pressing ALT+F1 and it displays the
following error message after pressing enter for each of the three
commands given by you:

-bash: syntax error near unexpected token `('

so alas I cannot send you the log files.
What have I done wrong? what else should I try?

On Mon, Sep 1, 2008 at 2:42 AM, James Collier
<email address hidden> wrote:
> Reassigning to casper. This doesn't look like a kernel problem, probably just a configuration problem.
> You might find it useful to do a google search such as "ubuntu laptop freezes at running local boot scripts"
> and have a look around the forums at ubuntuforums.org
>
> When you get to the stage of the screenshot taken below could you run the following commands ond post the output files here:
> You may need to plug in a USB device (should auto-mount under /media/*)
> - dmesg > dmesg.log (cp ~/dmesg.log /media/usb_key)
> - sudo lspci -vvnn > lspci-vvnn.log (cp ~/lspci-wnn.log /media/usb_key)
> - cat /var/log/Xorg.0.log > Xorg.log (cp ~/Xorg.log /media/usb_key)
> You may also try running:
> sudo dpkg-reconfigure xserver-xorg
> sudo /etc/init.d/gdm restart
>
> ** Changed in: casper (Ubuntu)
> Sourcepackagename: None => casper
>
> --
> Ubuntu 7.10 Gutsy doesn' t run on MiTAC laptops
> https://bugs.launchpad.net/bugs/158999
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[James Collier (james-collier412)]

My apologies for not being clear.
Again I would _strongly_ advise you to ask for help at the forums: www.ubuntuforums.org
or on the ubuntu users mailing list, to sign up: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

I will ask you to again type the commands inside the following quotes (but don't type the quotes):
Everything outside the "" are comments to help you understand what you're doing.
- take care with case

Before gathering the information, we'll just check if we can get X going properly
"sudo dpkg-reconfigure xserver-xorg"
"sudo /etc/init.d/gdm restart"

If the above doesn't work:

STEP 1: Insert your usb "memory stick"
"sudo fdisk -l"
This will produce a lot of output, what you are looking for (probably at the end) is an entry like this:
   Device Boot Start End Blocks Id System
/dev/sdc1 1 126 1012063+ 6 FAT16
USB sticks are usually formated with vfat.
Record the information under the Device section i.e. /dev/sdc1 in my case

STEP 2:
"cd /mnt" *C*hange *D*irectory to /mnt (just a place to mount the disk)
"sudo mkdir usbdrv" making a directory to mount your disk
"sudo mount /dev/sdc1 /mnt/usbdrv" Linux will mount your drive

STEP 3:
"cd usbdrv" lets make sure it all worked
'ls" List the files again, the files on your usb stick should be listed. The following instructions will depend on this being ok

STEP 4: Gathering the information
"sudo dmesg > /mnt/usbdrv/dmesg.log"
"sudo lspci -vvnn > /mnt/usbdrv/lspci-vvnn.log"
"sudo cat /var/log/Xorg.0.log > /mnt/usbdrv/Xorg.log"

STEP 5:
"umount /mnt/usbdrv"

STEP 6:
Attach the saved files on your usb drive to this report

[James Collier (james-collier412)]

Sorry, I've left out a rather important instruction above:
In STEP 3, 1 more command needs to be added after the last mentioned one:
"cd .. ; sudo -s"

[tiwaz (ft1978)]

Hi James,
Thank you for your clear instructions. Needless to say I'm quite a
newbie at Ubuntu since I cannot use it on my laptop due to the
installation error.
Attached please find the 3 log files. And below please find my comments.

On Mon, Sep 1, 2008 at 11:55 AM, James Collier
<email address hidden> wrote:
> My apologies for not being clear.
> Again I would _strongly_ advise you to ask for help at the forums: www.ubuntuforums.org
> or on the ubuntu users mailing list, to sign up: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
> I will ask you to again type the commands inside the following quotes (but don't type the quotes):
> Everything outside the "" are comments to help you understand what you're doing.
> - take care with case
>
> Before gathering the information, we'll just check if we can get X going properly
> "sudo dpkg-reconfigure xserver-xorg"

This process always quits after
"Keyboard options:
  lv3:ralt_switch"
(I don't know if it's normal)

> "sudo /etc/init.d/gdm restart"

"
Stopping GNOME Display Manager [OK]
Starting GNOME Display Manager [fail]
"

>
> If the above doesn't work:
>
> STEP 1: Insert your usb "memory stick"
> "sudo fdisk -l"
> This will produce a lot of output, what you are looking for (probably at the end) is an entry like this:
> Device Boot Start End Blocks Id System
> /dev/sdc1 1 126 1012063+ 6 FAT16
> USB sticks are usually formated with vfat.
> Record the information under the Device section i.e. /dev/sdc1 in my case
>
> STEP 2:
> "cd /mnt" *C*hange *D*irectory to /mnt (just a place to mount the disk)
> "sudo mkdir usbdrv" making a directory to mount your disk
> "sudo mount /dev/sdc1 /mnt/usbdrv" Linux will mount your drive
>
> STEP 3:
> "cd usbdrv" lets make sure it all worked
> 'ls" List the files again, the files on your usb stick should be listed. The following instructions will depend on this being ok
> Sorry, I've left out a rather important instruction above:
> In STEP 3, 1 more command needs to be added after the last mentioned one:
> "cd .. ; sudo -s"

Following this last command it says: "bash: cd..: command not found"

>
> STEP 4: Gathering the information
> "sudo dmesg > /mnt/usbdrv/dmesg.log"
> "sudo lspci -vvnn > /mnt/usbdrv/lspci-vvnn.log"
> "sudo cat /var/log/Xorg.0.log > /mnt/usbdrv/Xorg.log"
>
> STEP 5:
> "umount /mnt/usbdrv"

After typing this it said:
"umount: /mnt/usbdrv: device is busy"

>
> STEP 6:
> Attach the saved files on your usb drive to this report

In spite of the minor error messages above, it seems to have managed
to save the log files I'm sending herewith.
Thanks again for taking this trouble.

[James Collier (james-collier412)]

Thanks, this tells us the the CHROME driver for your VIA card cannot find the correct video mode for your screen.
I would like to see your X configuration file.
Follow the same steps as above except when you type "cd .. ; sudo -s" in STEP 3 make sure you put the space between cd and ..
In STEP 4, all you have to do is:
"cat /etc/X11/xorg.conf > /mnt/usbdrv/xorg.conf"
and attach that file here

[James Collier (james-collier412)]

Assigning to the openchrome video driver: cannot find video mode.
Should this be assigned to xorg?

[James Collier (james-collier412)]

The following bugs have been assigned as duplicates of this bug:

    * Bug #96675
    * Bug #209360
    * Bug #209945
    * Bug #217002
    * Bug #221521

Could those who reported those bugs transfer attached files to this report?
Thank-you for your time and bug reports!

[tiwaz (ft1978)]

The xorg.conf file attached.

On Mon, Sep 1, 2008 at 3:12 PM, James Collier
<email address hidden> wrote:
> Thanks, this tells us the the CHROME driver for your VIA card cannot find the correct video mode for your screen.
> I would like to see your X configuration file.
> Follow the same steps as above except when you type "cd .. ; sudo -s" in STEP 3 make sure you put the space between cd and ..
> In STEP 4, all you have to do is:
> "cat /etc/X11/xorg.conf > /mnt/usbdrv/xorg.conf"
> and attach that file here
>
> --
> Ubuntu 7.10 Gutsy doesn' t run on MiTAC laptops
> https://bugs.launchpad.net/bugs/158999
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[thsths (thomas-steffen+ubuntu)]

Since I have been digging in the VIA driver, I have a few suggestions.

Is there any chance to get a stack trace?

Can you enable debug=1 for the drm kernel module? (as root: /etc/init.d/gdm stop ; rmmod via ; rmmod drm ; insmod /lib/module/linux-2.6.27-11-generic/drivers/gpu/drm/drm.o debug=1; modprobe via ; /etc/init.d/gdm start)

Can you try the patch attached to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/326583 ?

Can you try with a 64bit installation (Ubuntu 8.10/amd64)? I found that it magically nearly works under 64bit.

[tiwaz (ft1978)]

Hi there,
I don't really wanna use the AMD64bit installation coz the problem
appears with my friends VIA-chipset laptops too who happen to have
Intel CPUs. I really wouldn't tweak anything. All I wish is that
Ubuntu shall work with our VIA-chipset comps as it worked like a charm
in version 7.04. Since 7.10 was released we cannot do anything. I'm no
software engineer but have the impression that for the Ubuntu
proggramers it would be something like to change or add 2 or 3 lines
in/to the code, the little thing that version 7.04 had and since 7.10
it doesn't.
I just want Ubuntu to run smoothly and perfectly again on our puters
as it used to.

On Sat, Feb 7, 2009 at 4:22 PM, thsths <email address hidden> wrote:
> Since I have been digging in the VIA driver, I have a few suggestions.
>
> Is there any chance to get a stack trace?
>
> Can you enable debug=1 for the drm kernel module? (as root:
> /etc/init.d/gdm stop ; rmmod via ; rmmod drm ; insmod
> /lib/module/linux-2.6.27-11-generic/drivers/gpu/drm/drm.o debug=1;
> modprobe via ; /etc/init.d/gdm start)
>
> Can you try the patch attached to bug
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/326583 ?
>
> Can you try with a 64bit installation (Ubuntu 8.10/amd64)? I found that
> it magically nearly works under 64bit.
>
> --
> openchrome driver unable to find video mode
> https://bugs.launchpad.net/bugs/158999
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Bartosz Kosiorek (gang65)]

Hi.
Could you please check if this bug exist also in Ubuntu 9.04 Jaunty?

[tiwaz (ft1978)]

Hi, I've just installed 9.04 on a VIA chipset laptop and it works like a charm!
Thanks a lot for all your efforts. Well done! We're back to Linux-World.

On Mon, Jun 1, 2009 at 11:20 AM, Bartosz <email address hidden> wrote:
> Hi.
> Could you please check if this bug exist also in Ubuntu 9.04 Jaunty?
>
> ** Summary changed:
>
> - openchrome driver unable to find video mode
> + [KM400] openchrome driver unable to find video mode
>
> --
> [KM400] openchrome driver unable to find video mode
> https://bugs.launchpad.net/bugs/158999
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[tiwaz (ft1978)]

Sorry, i dont wanna be too picky but skype doesn't work with my USB
webcam, while Cheese does. 7.04 handled it perfectly. Is it a video
driver issue? If so is there a tweak to get the cam to work with
skype?

On Mon, Jun 1, 2009 at 4:12 PM, Bartosz <email address hidden> wrote:
> ** Changed in: xserver-xorg-video-openchrome (Ubuntu)
>       Status: Confirmed => Fix Released
>
> --
> [KM400] openchrome driver unable to find video mode
> https://bugs.launchpad.net/bugs/158999
> You received this bug notification because you are a direct subscriber
> of the bug.
>