Opened 10 years ago

Closed 9 years ago

Last modified 6 years ago

#982 closed defect (obsolete)

Switch to nomodeset?

Reported by: CarolineM Owned by: sdz
Priority: Unspecified by Maintainer Milestone:
Component: Sugar on a Stick (SoaS) Version: Unspecified
Severity: Unspecified Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description

This fixes bugs on my IBM Thinkpad and makes it possible to use some Mac hardware.

Change History (14)

comment:1 Changed 10 years ago by sdz

  • Distribution/OS changed from Unspecified to SoaS
  • Milestone changed from Unspecified by Release Team to soas_v2
  • Resolution set to notsugar
  • Status changed from new to closed

As I've stated before on the mailing list, the following is still valid:

This is also a KMS issue, which means that it's upstream. Fedora 11 will most certainly have the
same issue. And obviously, we can't include the "nomodeset" parameter by default, as it would
mean that everybody gets the text boot screen and not our shiny new "Strawberry" SoaS boot
screen (the same goes for the Mac issues).

The KMS feature has been introduced in Fedora with F10 (see http://fedoraproject.org/wiki/Features/KernelModesetting) and been expanded for other hardware with F11 (see http://fedoraproject.org/wiki/Features/IntelKMS and http://fedoraproject.org/wiki/Features/NouveauModesetting).

This is certainly an upstream bug, while finally, we'd at least need to know what graphics hardware you're trying to run it on. Closing.

comment:2 Changed 10 years ago by CarolineM

  • Resolution notsugar deleted
  • Status changed from closed to reopened

Ok tell me how to tell you that and I'll get you the information.

comment:3 Changed 10 years ago by CarolineM

The MacBooks in Boston Public School need nomodeset. Thus this is a critical issue for our summer program at the LGF and for the fall at GPA.

I realize I have not provided enough information. I am requesting help on how to get the information we need to solve this problem whereever in the stream it maybe.

Thanks

comment:4 Changed 10 years ago by erikos

How about you create a custom spin, with the setting set?

comment:5 follow-up: Changed 10 years ago by CarolineM

This is for LGF. The kids will use their sticks on their MacBooks, the EVO and other old PCs in the Library and their EEPCs (or maybe its another brand of netbooks) at home.

If we create a custom spin will it work on all of these?

comment:6 Changed 10 years ago by erikos

What I meant is: We should start promoting custom spins - http://erikos.sweettimez.de/?p=697 Is is quite normal that one has to do customization you do not want to make on each machine (language, keyboard...). As described in the blog post doing custom builds is straight forward.

comment:7 in reply to: ↑ 5 Changed 10 years ago by erikos

Replying to CarolineM:

This is for LGF. The kids will use their sticks on their MacBooks, the EVO and other old PCs in the Library and their EEPCs (or maybe its another brand of netbooks) at home.

If we create a custom spin will it work on all of these?

see Sebastian's comment.

comment:8 Changed 10 years ago by sdz

To submit the hardware information, using the effort I started a month or so ago would be helpful (http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Hardware). But note that shipping with kernel mode setting has been a decision made by the Fedora folks upstream, so that it's really hard for us to revert it (and we'd also loose our boot screen). The best solution here would be to create a custom spin, either using the instructions I linked to in the release notes (http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Customization). Those are partly incomplete, so erikos' blog post from above might also be helpful. Maybe daveb knows where this would need to be added (sorry, there's some file which provides the kernel parameters, but I'm not sure which one it is)...

comment:9 Changed 10 years ago by CarolineM

Hi,

Any update on this issue? We are now creating the custom spin for GPA.

What is your advice? Should we try to set it for NOMODESET at all times or should we try to create different boot-helper CDs for those computers that need nomodeset?

Will we still have this problem in Blueberry?

comment:10 Changed 10 years ago by bogstad

As of the Soas-beta.iso from a couple of week ago, I would say
possibly worse problems actually. My test machine works with Strawberry, but won't even display graphics at all with the current SoaS beta. Nor will the Fedora 12 Alpha.

comment:11 Changed 10 years ago by bogstad

As suggested above, I've respun the CD boot helper to attempt to
force nomodeset all the time. It can be downloaded at:

http://people.sugarlabs.org/~bogstad/cd/soas-boot-nomodeset.iso

comment:12 Changed 9 years ago by sdz

  • Resolution set to obsolete
  • Status changed from reopened to closed

I'm closing this, hoping that the above linked boot helper works. As time goes by, hardware support should generally improve, especially concerning graphic cards.

comment:13 Changed 9 years ago by sascha_silbe

  • Distribution/OS changed from SoaS to Unspecified

Bulk change distribution=SoaS -> component=SoaS

comment:14 Changed 6 years ago by dnarvaez

  • Milestone Blueberry deleted

Milestone Blueberry deleted

Note: See TracTickets for help on using tickets.