-
Heck, I would. :) Glad I could help - sorry I had a Sony...
2004-06-01 17:12:06 UTC in i810 Framebuffer Device Driver
-
After the second patch, dmesg reports:
i810-i2c: Probe DDC1 Bus
i810-i2c: Unable to read EDID block.
i810-i2c: Unable to read EDID block.
i810-i2c: Unable to read EDID block.
i810-i2c: Probe DDC2 Bus
i810-i2c: Unable to read EDID block.
i810-i2c: Unable to read EDID block.
i810-i2c: Unable to read EDID block.
i810fb_init_pci: I2C bus probing failed...
i810fb_init_pci: getting EDID...
2004-05-31 05:43:38 UTC in i810 Framebuffer Device Driver
-
Okay, here's the pertinent parts of dmesg after patching:
i810-i2c: Probe DDC1 Bus
i810-i2c: Unable to read EDID block.
i810-i2c: Unable to read EDID block.
i810-i2c: Unable to read EDID block.
i810fb_init_pci: DDC1 probe failed
i810-i2c: Probe DDC2 Bus
i810-i2c: Unable to read EDID block.
i810-i2c: Unable to read EDID block.
i810-i2c: Unable to read EDID block.
i810fb_init_pci: I2C...
2004-05-29 02:31:24 UTC in i810 Framebuffer Device Driver
-
Okay, no crash this time, but no output as you described either. The patch was successful, so I'm not sure what happened. I don't see any I2C or EDID information in the output of dmesg, sorry.
2004-05-27 23:38:21 UTC in i810 Framebuffer Device Driver
-
No problem - I'm a developer by trade, so I'm used to this sort of thing. :)
I'm running kernel 2.6.5 at the moment - Given that your first patch worked, I'm assuming this will as well. I think I'll try backing out the previous patch via -R first rather than patching over it with the i2c1 patch. I'll let you know how it goes.
2004-05-27 22:37:08 UTC in i810 Framebuffer Device Driver
-
Boom.
I added generic i2c support as well as i810 i2c support and bit-packing algorithm support. On boot I gota kernel panic. the call trace starts in i810_probe_i2c_connector+0x8a/0x140, from i810fb_init_pci. The kernel panic was 'attempted to kill init'. Unfortunately, I can't give you any more info at the moment - I need to grab a bootable CD and swap kernels. :)
2004-05-27 16:44:54 UTC in i810 Framebuffer Device Driver
-
Certainly. I've patched and am rebuilding now. What should I be looking for?.
2004-05-27 15:31:42 UTC in i810 Framebuffer Device Driver
-
Success!! I had an extra space in my kernel parameters. Once I removed it, all was well. Thanks for all your help!
I'd like to see this change make it into the next version of the driver, so eventually (assuming the bootsplash code I patched is updated as well) I won't have to edit kernel source when I want to update my kernel. Any chance of that happening?.
2004-05-27 02:35:49 UTC in i810 Framebuffer Device Driver
-
I guessed as much and have already tried that. I'm now getting i810 initialization errors ("Unable to initialize device") that may or may not be related to the changes - I'll check my kernal parameters when I get home tonight and try again.
2004-05-26 22:48:06 UTC in i810 Framebuffer Device Driver
-
Hmm. Well, after making the changes you recommended, I rebooted and the console switched... to a black screen. None of the vts showed any text or images. The machine continued to boot in the background. I was unable to reclaim any kind of vt during the boot process. NOt quite the 'silent' boot I was hoping for. :)
Once X started I was able to take a look at the output of dmesg and saw...
2004-05-26 17:39:34 UTC in i810 Framebuffer Device Driver
