monitor incorrectly detected - bulletproofX fail

[doobydave]

My moitor, an Iiyama Vision Master Pro 510, has never been detected correctly since my foray into Ubuntu.

What has been a nuisance previously, is now a show-stopping fail, due to the implementation of 'bulletproofX' - and the removal of the very useful resolution-changing keyboard shortcuts.

On boot, with both the live and an installed version (using the alternate install cd), I get a flashing purple screen when the login screen should be displayed. I can login but to no avail as the desktop isn't displayed correctly.
I can also switch to the teminal, but usuage is made difficult by the fact that it is invisible.

Currently, Ubuntu is completely unusable for me.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: amd64
ArecordDevices: arecord: device_list:223: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
CurrentDmesg:
 [ 14.368516] [drm] nouveau 0000:01:00.0: Allocating FIFO number 2
 [ 14.370997] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 2
 [ 14.379090] ppdev: user-space parallel port driver
 [ 23.370003] eth0: no IPv6 routers present
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=7d4e2e03-66d0-4025-a6f3-52604932b74e
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P35-S3G
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=b0c75162-8faf-4a10-b40a-ff398b94f8a5 ro quiet splash
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34.1
Reproducible: Yes
RfKill:

Tags: lucid regression-potential needs-upstream-testing
Uname: Linux 2.6.32-24-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WifiSyslog:

dmi.bios.date: 12/28/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3a
dmi.board.name: P35-S3G
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3a:bd12/28/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-S3G:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-S3G:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-S3G
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[doobydave (dooby-dave)]

I have used another monitor to install all the updates, but still no joy.

Any ideas for a workaround, or fix, most welcome.

[Jeremy Foshee (jeremyfoshee)]

Hi doobydave,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 623880

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[doobydave (dooby-dave)]

After much guesswork and luck (due to the invisible terminal, mentioned above), I have installed ssh-server and ran the apport listed above. Could you confirm that it has arrived. There was a possibility that one of the machines may have terminated the process prematurely.

[doobydave (dooby-dave)]

Heeeellllllllllllllloooooooooooooooooooooooooooo.

[doobydave (dooby-dave)]

It would be nice if I could illicit some sort of reply here that wasn't bot generated.

[doobydave (dooby-dave)]

I've been retrying the apport command and come across the hurdle of being unable to log in to launchpad through w3m as per https://bugs.launchpad.net/launchpad/+bug/523229

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

apport information

[doobydave (dooby-dave)]

Hello.

I am sorry to say, but I am extremely disappointed by the way this bug report is (/isn't?) being dealt with. The lack of correspondence/support is woeful at best and downright rude at worst.

Just because a bug is found by a 'noob' rather than a dev, doesn't make it any less valid of a bug. A small amount of friendly support will go a long way in helping you achieve better bug reduction. Ignoring bugs until you no longer support that particular release is not an option if Ubuntu is ever to achieve it's goals.

I intend to make a complaint - assuming that is that possibility.

[doobydave (dooby-dave)]

I found a workaround to this bug. Installing a different OS seems to have fixed it for me.

[J. Greg Davidson (jgdubuntu)]

With Ubuntu 11.04 and the previous release my monitor reports "INPUT SIGNAL OUT OF RANGE" for all text consoles and after the initial boot sequence. X is fine. Ubuntu used to work fine on my text consoles as well as X.

Monitor: HANNS-G

With X I run at 60hz 1920x1200.

I tried adding nomodeset and that didn't help.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]