Bug 757209 - Fedora 16 unusable on Samsung N130 netbook
Summary: Fedora 16 unusable on Samsung N130 netbook
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-25 20:44 UTC by Konstantin Svist
Modified: 2011-12-07 22:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 22:27:35 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Konstantin Svist 2011-11-25 20:44:22 UTC 
Description of problem:
The intel video driver is broken. The only way to boot the live CD (XFCE) was to use alternative video mode, otherwise the computer froze completely. After it booted up with nomodeset, there's no way to set the proper resolution of 1024x600.
After a clean install from same live CD, I've tried combinations of i915.modeset=1 and i915.semaphores=1 - the computer refuses to boot to graphical interface in either case.


Version-Release number of selected component (if applicable):
xorg-x11-drv-intel.i686  2.17.0-1.fc16

How reproducible:
every time


Additional info:

# lspci -s00:00.0 -nnn -vvv
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac] (rev 03)
	Subsystem: Samsung Electronics Co Ltd Device [144d:c05d]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information: Len=09 <?>
	Kernel driver in use: agpgart-intel



Previously, I had Fedora 14 on this computer and video driver was working perfectly
Comment 1 Konstantin Svist 2011-11-30 19:04:32 UTC 
*PING*
Can someone at least find a workaround so I can use my computer?!?!
Comment 2 Konstantin Svist 2011-12-07 00:47:23 UTC 
After fucking around for a long time, I discovered that xorg.conf with vesa driver was created by the LiveCD. Thus, KMS worked until Xorg -- then vesa refused to touch the existing loaded driver and X wouldn't load.
After yum updates and removing xorg.conf, X loads fine and so far everything seems to work
Comment 3 Adam Jackson 2011-12-07 22:27:35 UTC 
Closing per comment #2.
Note You need to log in before you can comment on or make changes to this bug.