On Fri, Nov 6, 2009 at 2:43 PM, Guido Grazioli <guido.grazioli@xxxxxxxxx> wrote: > 2009/11/6 Peter Robinson <pbrobinson@xxxxxxxxx>: >>> * Just before graphical boot screen, for some seconds i can see: >>> -- >>> render error detected, EIR: 0x00000010 >>> page table error >>> PGTBL_ER: 0x00000100 >>> [drm:i915_handle_error] *ERROR* EIR stuck: 0x0000010, masking >>> render error detected, EIR: 0x00000010 >>> page table error >>> PGTBL_ER: 0x00000100 >>> -- >>> however, everything seems to run just right after that. >> >> Is it recorded in dmesg. It might be worth reporting a bug with all >> the details. >> > > Yep i can see it in dmesg; which component should i report the bug against? Start with xorg-x11-drv-intel and we'll take it from there. Let me know what the bug number is. >>> * Where's wifi configuration? isn't there a graphical tool >>> to configure it? asking my gf to get it up on a shell is a no-no. >> >> It should be in the top right corner of the top panel. Just to the >> left of the volume control. From memory the eeePC 900 has an atheros >> card so it should work OK. >> > > I can see NetworkManager running with top, but i have no icon in the toolbar; > wifi devices are present and atheros module loaded correctly. Can you try running from a terminal "network-manager-netbook -s" and see what you get. You should get the gui but not embedded in the main bar. >>> * I mounted a touchscreen in my eeepc, and moblin gui looks >>> much more friendly to that interface. However i couldnt install >>> the manufacturer software (eGalax), because i think >>> an autoloaded module interferes with it (generic-usb?). >>> On F11 nothing get autoloaded and touchscreen works fine. >>> I need some more testing to figure this out. >> >> Do they have an open driver? Maybe its supported in F-12 and I just >> need to make sure the right package is included to support it. >> > > The driver is here: > http://210.64.17.162/web20/eGalaxTouchDriver/linuxDriver.htm > > A kernel module is actually needed only if > the touchscreen uses serial connection; installation of their > driver for usb only modifies xorg.conf and launches a > calibration utility. Will try again in the weekend, as i can have made > something wrong, and will report back to you. Sounds like the X input guys should be able to detect the USB device and autoconfigure it. > Just forgot to report yesterday: if i open cheese and take a > picture from the webcam (default setting are ok), the > image goes to the first "rolling" screen. If i click on the picture > a program is opened (media viewer?) but after half a second > it closes with no error. Then the background image is > replaced with a grey background. That's a known bug. Some issue in mesa/driver. See https://bugzilla.redhat.com/show_bug.cgi?id=529372 Cheers, Peter -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
