ubuntu 10.10 or above not support sis chipset(not the video card)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| linux (Ubuntu) |
Medium
|
Unassigned |
Bug Description
ubuntu 10.04 with a kernel 2.6 or lower works well on my SIS motherboard, but using ubuntu 10.10 or higher I cannot boot into Ubuntu. I'm now using ubuntu 12.04 on an ASUS F81SE notebook with SIS motherboard,and I can't boot it normally.
Mainline kernel version bisect revealed:
v2.6.34-rc1/:well
v2.6.34.
WORKAROUND: Add:
acpi=off
to the grub line.
WORKAROUND: Disable wlan in bios.
WORKAROUND: Download kernel 2.6.34 or lower (used by ubuntu 10.04) from http://
So i guess ubuntu must have removed sis motherboard acpi support from kernel 2.6 or higher(perhaps linux kernel team should be responsible for it).Please give me an a explanation about it .
Something has to be pointed out that this bug has nothing to do with the video card or video driver!
This bug exists in ALL computers based on SIS motherboard running ubuntu 10.10 or above.
---
AcpiTables:
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu13
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: SIS966 [HDA SIS966], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
Card0.Amixer.info:
Card hw:0 'SIS966'/'HDA SIS966 at 0xfddf4000 irq 18'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,
Controls : 18
Simple ctrls : 10
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdeec000 irq 40'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 6
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MachineType: ASUSTeK Computer Inc. F81Se
NonfreeKernelMo
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.79.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: precise running-unity
Uname: Linux 3.2.0-32-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/12/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 217
dmi.board.
dmi.board.name: F81Se
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: F81Se
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
affects: | xserver-xorg-video-sis (Ubuntu) → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
tags: | added: maverick |
prcxjb (prcxjb) wrote : ProcEnviron.txt | #2 |
apport information
tags: | added: apport-collected precise running-unity |
description: | updated |
Joseph Salisbury (jsalisbury) wrote : | #3 |
Would it be possible for you to test the latest upstream kernel? Refer to https:/
Once you've tested the upstream kernel, please remove the 'needs-
If this bug is fixed in the mainline kernel, please add the following tag 'kernel-
If the mainline kernel does not fix this bug, please add the tag: 'kernel-
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
[0] http://
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: needs-upstream-testing |
tags: |
added: kernel-bug-exists-upstream removed: needs-upstream-testing |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Christopher M. Penalver (penalvch) wrote : | #4 |
prcxjb, could you please utilize your WORKAROUND, boot into a Ubuntu kernel that came with Precise, and execute the following in a terminal:
apport-collect 1066524
tags: |
added: kernel-bug-exists-upstream-v3.6.2-quantal needs-kernel-logs removed: apport-collected |
description: | updated |
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
prcxjb (prcxjb) wrote : AlsaDevices.txt | #5 |
apport information
tags: | added: apport-collected |
description: | updated |
prcxjb (prcxjb) wrote : AplayDevices.txt | #6 |
apport information
prcxjb (prcxjb) wrote : BootDmesg.txt | #7 |
apport information
prcxjb (prcxjb) wrote : CRDA.txt | #8 |
apport information
prcxjb (prcxjb) wrote : Card0.Amixer.values.txt | #9 |
apport information
apport information
apport information
prcxjb (prcxjb) wrote : CurrentDmesg.txt | #12 |
apport information
prcxjb (prcxjb) wrote : IwConfig.txt | #13 |
apport information
prcxjb (prcxjb) wrote : Lspci.txt | #14 |
apport information
prcxjb (prcxjb) wrote : Lsusb.txt | #15 |
apport information
prcxjb (prcxjb) wrote : PciMultimedia.txt | #16 |
apport information
prcxjb (prcxjb) wrote : ProcCpuinfo.txt | #17 |
apport information
prcxjb (prcxjb) wrote : ProcEnviron.txt | #18 |
apport information
prcxjb (prcxjb) wrote : ProcInterrupts.txt | #19 |
apport information
prcxjb (prcxjb) wrote : ProcModules.txt | #20 |
apport information
prcxjb (prcxjb) wrote : PulseList.txt | #21 |
apport information
prcxjb (prcxjb) wrote : UdevDb.txt | #22 |
apport information
prcxjb (prcxjb) wrote : UdevLog.txt | #23 |
apport information
prcxjb (prcxjb) wrote : WifiSyslog.txt | #24 |
apport information
tags: | added: regression-release |
description: | updated |
prcxjb, thank you for performing the apport-collect.
Regarding your three WORKAROUNDs, do you have to use all 3 simultaneously in Precise, or just any one of them?
As well, the next step is to perform a mainline kernel bisect from v2.6.34-lucid to v2.6.35.
v2.6.34-lucid/
v2.6.34-rc1/
v2.6.34.1-maverick/
v2.6.34.2-maverick/
v2.6.34.3-maverick/
v2.6.34.4-maverick/
v2.6.34.5-maverick/
v2.6.34.6-maverick/
v2.6.34.7-maverick/
v2.6.34.8-maverick/
v2.6.34.9-maverick/
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.35-maverick/
v2.6.35-rc1-lucid/
v2.6.35-
v2.6.35-
v2.6.35-
v2.6.35-
v2.6.35-
v2.6.35.1-maverick/
v2.6.35.2-maverick/
v2.6.35.3-maverick/
v2.6.35.4-maverick/
v2.6.35.5-maverick/
v2.6.35.6-maverick/
v2.6.35.7-maverick/
v2.6.35.8-maverick/
v2.6.35.9-maverick/
v2.6.35.
v2.6.35.
v2.6.35.
v2.6.35.
v2.6.35.
v2.6.35.
Hence, could you please test http://
Thank you for your understanding.
Helpful Bug Reporting Tips:
https:/
tags: | removed: needs-kernel-logs |
prcxjb (prcxjb) wrote : | #26 |
If i use a ubuntu kernel lower than 2.6.34,there is no need for me to disable wlan in bios or add "acpi=off" to the grub line.Each of the 3 WORKAROUNDs works well independently.
I have tesetd almost all the kernels you listed.It's really a big job.
v2.6.34-lucid/:well
v2.6.34-rc1/:well
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.34.
v2.6.35-
v2.6.35-
v2.6.35-
v2.6.35-
v2.6.35-
v2.6.35-
v2.6.35-
v2.6.35.
We can see that kernels made for lucid work well."v2.
prcxjb, thank you for performing the upstream kernel bisection. In order to further limit the work necessary to bisect this problem, for now, let us not focus on the results for:
v2.6.35-
Instead, let us focus on:
v2.6.34-rc1/:well
v2.6.34.
The next step is to perform a commit bisect from upstream v2.6.34-rc1 to v2.6.34.1-maverick, in order to identify the offending commit(s). Could you please do this following https:/
Thank you for your understanding.
Helpful Bug Reporting Tips:
https:/
tags: | added: needs-bisect |
prcxjb (prcxjb) wrote : | #28 |
I notice that there are some kernels made for maverick lower than kernel v2.6.34-rc1:
v2.6.33.6-maverick/
v2.6.33.7-maverick/
v2.6.33.
Do I need to test them as well?
prcxjb, regarding your comments https:/
>"I notice that there are some kernels made for maverick lower than kernel v2.6.34-rc1:
v2.6.33.6-maverick/
v2.6.33.7-maverick/
v2.6.33.
Do I need to test them as well?"
No.
prcxjb (prcxjb) wrote : | #30 |
I have done it following the instructions
"Build Upstream Test Kernel
The next step is to run the mainline-build-one script. This script will build an upstream kernel that will be able to install and run on a Ubuntu system. Run the mainline-build-one script as follows (assuming you've added kteam-tools/
mainline-build-one fe10e6f4b24ef8c
This will generate a bunch of .debs one directory level above. One of the debs will be something like:
linux-image-
This is the deb you will want to test and see if the bug exists or not."
But I cannot find the .deb files anywhere .It cost only several minutes to generate the kernel,so i doubt if there was something wrong.This is the output information.
"prcxjb@
*** BUILDING: commit:
full_version<
version<2.6.34>
long<v2.
abinum<020634rc2>
remote: Counting objects: 41323, done.
remote: Compressing objects: 100% (8820/8820), done.
remote: Total 35921 (delta 28211), reused 34324 (delta 26743)
Receiving objects: 100% (35921/35921), 43.01 MiB | 1.33 MiB/s, done.
Resolving deltas: 100% (28211/28211), completed with 2882 local objects.
From git://kernel.
* [new branch] day-0 -> precise/day-0
* [new branch] lts-backport-
* [new branch] master -> precise/master
* [new branch] master-next -> precise/master-next
* [new branch] ti-omap4 -> precise/ti-omap4
* [new tag] Ubuntu-
* [new tag] Ubuntu-3.2.0-24.37 -> Ubuntu-3.2.0-24.37
* [new tag] Ubuntu-3.2.0-33.52 -> Ubuntu-3.2.0-33.52
* [new tag] Ubuntu-Q-sync -> Ubuntu-Q-sync
* [new tag] Ubuntu-
From git://kernel.
* [new tag] Ubuntu-3.2.0-22.35 -> Ubuntu-3.2.0-22.35
* [new tag] Ubuntu-3.2.0-23.36 -> Ubuntu-3.2.0-23.36
* [new tag] Ubuntu-3.2.0-24.38 -> Ubuntu-3.2.0-24.38
* [new tag] Ubuntu-3.2.0-24.39 -> Ubuntu-3.2.0-24.39
* [new tag] Ubuntu-3.2.0-25.40 -> Ubuntu-3.2.0-25.40
* [new tag] Ubuntu-3.2.0-26.41 -> Ubuntu-3.2.0-26.41
* [new tag] Ubuntu-3.2.0-27.42 -> Ubuntu-3.2.0-27.42
* [new tag] Ubuntu-3.2.0-27.43 -> Ubuntu-3.2.0-27.43
* [new tag] Ubuntu-3.2.0-28.44 -> Ubuntu-3.2.0-28.44
* [new tag] Ubuntu-3.2.0-29.45 -> Ubuntu-3.2.0-29.45
* [new tag] Ubuntu-3.2.0-29.46 -> Ubuntu-3.2.0-29.46
* [new tag] Ubuntu-3.2.0-30.47 -> Ubuntu-3.2.0-30.47
* [new tag] Ubuntu-3.2.0-30.48 -> Ubuntu-3.2.0-30.48
* [new tag] Ubuntu-3.2.0-31.49 -> Ubuntu-3.2.0-31.49
* [new tag] Ubuntu-3.2.0-31.50 -> Ubuntu-3.2.0-31.50
* [new tag] Ubuntu-3.2.0-32.51 -> Ubuntu-3.2.0-32.51
Checking out files: 100% (31414/31414), done.
Previous H...
prcxjb, if you need more granular support on bisecting, please contact the Ubuntu Kernel Team via https:/
Launchpad Janitor (janitor) wrote : | #32 |
[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
Changed in linux (Ubuntu): | |
status: | Incomplete → Expired |
Changed in linux (Ubuntu): | |
status: | Expired → Confirmed |
prcxjb, as per http://
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
prcxjb (prcxjb) wrote : | #34 |
My computer's bios has been updated before I submitted the bug.The bug still exists.
prcxjb, as per your Bug Description:
dmi.bios.version: 217
your BIOS is not updated to the latest version (218).
Launchpad Janitor (janitor) wrote : | #36 |
[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
Changed in linux (Ubuntu): | |
status: | Incomplete → Expired |
prcxjb (prcxjb) wrote : | #37 |
I have updated the bios to the latest version 218 and ubuntu 13.04,but the bug still exists.
It seems that i can't run sudo apport-collect 1066524 in the terminal of ubuntu 13.04.It said "ERROR: The launchpadlib Python module is not installed. This functionality is not available."But the python-apport has been installed.
prcxjb, thank you for updating to the newest BIOS and Raring. Could you please test the latest upstream kernel available (v3.9-saucy) following https:/
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-
This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-
If the mainline kernel does not fix this bug, please add the following tags:
kernel-
kernel-
As well, please remove the tag:
needs-upstream-
If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-
kernel-
Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.
tags: |
added: latest-bios-218 needs-upstream-testing removed: kernel-bug-exists-upstream |
tags: | added: raring |
Changed in linux (Ubuntu): | |
status: | Expired → Incomplete |
prcxjb (prcxjb) wrote : | #39 |
I have tested the upstream kernel v3.9.1,but the bug still exists.
tags: |
added: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.9.1 removed: needs-upstream-testing |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | removed: kernel-bug-exists-upstream-v3.6.2-quantal |
description: | updated |
description: | updated |
prcxjb, thank you for testing the newest mainline kernel. The next step is to commit bisect the mainline kernel from v2.6.34-rc1 (GOOD) to v2.6.34.1-maverick (BAD) in order to identify the offending commit. Following mainline kernel bisect instructions noted in https:/
git clone git://git.
This will post:
Bisecting: 1899 revisions left to test after this (roughly 11 steps)
[fd218cf9557b9b
Next you need to run the following to build the mainline kernel up to this commit:
git checkout fd218cf9557b9bf
Restart into this built kernel and please advise on the results. Thank you for your understanding.
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
prcxjb (prcxjb) wrote : | #41 |
I have tried the steps above,but after building the kernel it said "make: *** [debian/
A message was showed many times when building the kernel "warning: variable ‘pao_tmp__’ is set but never used [-Wunused-
prcxjb, thank you for performing the requested terminal command. I beg your pardon as I should have run this command before requesting you to do so, as I would have seen this error. Despite this, I've requested the help of the Ubuntu Kernel Team via their mailing list at https:/
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1066524
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.