Can't boot Ubuntu, new install with GMA600 graphics

Farkuldi · 04-12-2013, 06:05 PM

I have a Viewsonic tablet with an Intel Oaktrail processor the GMA600 graphics processor. I read here that as of the 12.04 release, the driver for this processor would be included in Ubuntu, and it should work. However, after I installed 12.10, it will not boot.

First it gave me this error:

Code:

[   <bunch of numbers>] ieee80211 phy0: uap0: changing to 2 not supported
[   <bunch of numbers>] ieee80211 phy0: uap0: changing to 2 not supported
[   <bunch of numbers>] ieee80211 phy0: uap0: changing to 2 not supported
[   <bunch of numbers>] ieee80211 phy0: uap0: changing to 2 not supported

The only thing I was able to find through Google about this was a document I don't understand. It's here:

http://dev.laptop.org/ticket/12197

Then I tried to boot it in recovery mode, and it did the strange graphics thing which is described in the above document about the Poulsbo graphics where half the screen is distorted.

Thanks for any help.

syg00 · 04-12-2013, 10:02 PM

The GMA500 is junk but I managed to get it working (2D only) on prior versions of Ubuntu with the (then) new in-kernel support. Try adding the "console=tty1" to the boot line manually from the boot screen. Then if that fixes it, do the update mentioned in the Ubuntu wiki.
I can't find that old netbook at the moment, but if/when I find it I'll do some testing.

I suspect those messages are informational only - may be a problem with the network, or not. Sort the screen out and see what you get.

Edit: See this for how-to on grub2 - go down to the "Editing the GRUB 2 Menu During Boot" section.

Farkuldi · 04-13-2013, 09:04 AM

Quote:

Originally Posted by syg00

The GMA500 is junk but I managed to get it working (2D only) on prior versions of Ubuntu with the (then) new in-kernel support. Try adding the "console=tty1" to the boot line manually from the boot screen. Then if that fixes it, do the update mentioned in the Ubuntu wiki.
I can't find that old netbook at the moment, but if/when I find it I'll do some testing.

I suspect those messages are informational only - may be a problem with the network, or not. Sort the screen out and see what you get.

Edit: See this for how-to on grub2 - go down to the "Editing the GRUB 2 Menu During Boot" section.

Thanks for your reply. I'm sorry, I realized when I read your post that I listed the wrong GPU. It's the GMA600, not GMA500. I edited my post to correct this. From what I have read, though, I don't think there would be a difference.

I tried adding

Code:

console=tty1

to the grub menu, on a line of its own right between "setparams 'Ubuntu'" and "recordfail." I've never edited the grub boot menu before so I hope this is right. I read the link but I didn't see examples, just instructions that assume you know what you're doing.

Anyway, it didn't work. It is still telling me over and over about 80211 and changing to 2 not supported. I'm not sure it is informational, since it says it over and over and just hangs there. It will say

Code:

[   <bunch of numbers>] ieee80211 phy0: uap0: changing to 2 not supported
[   12.??????] ieee80211 phy0: uap0: changing to 2 not supported
[   14.??????] ieee80211 phy0: uap0: changing to 2 not supported
[   15.??????] ieee80211 phy0: uap0: changing to 2 not supported
. . .

about 25 times or so, and then it will hang for a while. If I let it be for about 3 or 4 minutes, it will start saying the same thing again, but this time with higher numbers, like 337.?????? . . . 360.??????. If I let it go even longer it will do the same thing again with 661.?????? + numbers.

Is there a way to disable the network adapter so it doesn't even try to load and maybe avoid the problem? Or does that not make sense?

Thanks.

syg00 · 04-13-2013, 06:25 PM

Quote:

Originally Posted by Farkuldi

I tried adding

Code:

console=tty1

to the grub menu, on a line of its own right between "setparams 'Ubuntu'" and "recordfail." I've never edited the grub boot menu before so I hope this is right. I read the link but I didn't see examples, just instructions that assume you know what you're doing.

That's a kernel parameter - simply add it to the end of the "kernel" line. While you're at it, remove the "quiet" and "splash". That should allow you to see (all) the boot messages, but didn't work on my only (old, 11.04) remaining Ubuntu system.

Quote:

Is there a way to disable the network adapter so it doesn't even try to load and maybe avoid the problem? Or does that not make sense?

It's not something the kernel support (yet) as the module loading is done as part of the init scripts - I think you can disable module loading in Ubuntu by adding "some-module-name.blacklist=yes" to the kernel line.
But of course you have to know "some-module-name" in advance.

Not much help.

Farkuldi · 04-13-2013, 07:32 PM

Quote:

Originally Posted by syg00

That's a kernel parameter - simply add it to the end of the "kernel" line. While you're at it, remove the "quiet" and "splash". That should allow you to see (all) the boot messages, but didn't work on my only (old, 11.04) remaining Ubuntu system.It's not something the kernel support (yet) as the module loading is done as part of the init scripts - I think you can disable module loading in Ubuntu by adding "some-module-name.blacklist=yes" to the kernel line.
But of course you have to know "some-module-name" in advance.

Not much help.

Sorry, I don't have a line that says "kernel." This is what I have:

Code:

setparams 'Ubuntu'

recordfail
	gfxmode	$linux_gfx_mode
	insmod gzio
	insmod part_msdos
	insmod ext2
	setroot='hd0,msdos7'
	if [ x$feature_platform_search_hint = xy ]; then
		search --no floppy --fs uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0, msdos7 --hint-baremetal=ahci\0, msdos 9cd0fc57-d63e-4cd4-bab4-d115ad639c07
	else
		search --no floppy --fs-uuid --set=root 9cd0fc57-d63e-4cd4-bab4-d115ad639c07
	fi
	linux	/boot/vmlinuz-3.5.0-17-generic root=UUID=9cd0fc57-d63e-4cd4-bab4-d115ad639c07 ro   quiet splash\
   $vt_handoff
	initrd	/boot/initrd.img-3.5.0-17-generic

Thanks for your help.

syg00 · 04-13-2013, 07:52 PM

Grub2 ... add it to the "linux" line after the "$vt_handoff.

Farkuldi · 04-25-2013, 08:46 AM

I'm sorry I went so long without updating. I am a student and this is the end of the semester, so I got rather caught up preparing for finals. But anyway, I was not able to make this work. I just haven't had time to write down all the error messages. I will revisit this thread when my finals are over and I have time to deal with the matter again.

Thank you very much for your assistance. I really appreciate it.