On Sun, Oct 26, 2008 at 11:16 PM, Martin Bochnig <[EMAIL PROTECTED]> wrote: > Hello, just back at computer. > Here is the only onusual thing that I see so far, after the first two > minutes ... : > > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 139057 kern.info] > NOTICE: reprogram io-range on ppb[0/1c/0]: 0x4000 ~ 0x4fff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 139057 kern.info] > NOTICE: reprogram io-range on ppb[2/0/0]: 0x4000 ~ 0x4fff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 139057 kern.info] > NOTICE: reprogram io-range on ppb[0/1c/2]: 0x5000 ~ 0x5fff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 596873 kern.info] > NOTICE: reprogram mem-range on ppb[0/1c/2]: 0x80000000 ~ 0x802fffff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 139057 kern.info] > NOTICE: reprogram io-range on ppb[0/1c/3]: 0x6000 ~ 0x6fff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 596873 kern.info] > NOTICE: reprogram mem-range on ppb[0/1c/3]: 0x80300000 ~ 0x805fffff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 139057 kern.info] > NOTICE: reprogram io-range on ppb[0/1c/4]: 0x7000 ~ 0x7fff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 596873 kern.info] > NOTICE: reprogram mem-range on ppb[0/1c/4]: 0x80600000 ~ 0x808fffff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 139057 kern.info] > NOTICE: reprogram io-range on ppb[0/1c/5]: 0x8000 ~ 0x8fff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 596873 kern.info] > NOTICE: reprogram mem-range on ppb[0/1c/5]: 0x80900000 ~ 0x80dfffff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 139057 kern.info] > NOTICE: reprogram io-range on ppb[0/6/0]: 0x9000 ~ 0x9fff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 596873 kern.info] > NOTICE: reprogram mem-range on ppb[0/6/0]: 0x80e00000 ~ 0x810fffff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 139057 kern.info] > NOTICE: reprogram io-range on ppb[0/1/0]: 0xa000 ~ 0xafff > Oct 26 12:39:44 opensolaris pci_autoconfig: [ID 596873 kern.info] > NOTICE: reprogram mem-range on ppb[0/1/0]: 0x81100000 ~ 0x816fffff > > But afterwards the boot's seem to continue. > Wait a sec until I found (and back-checked) more. > > > %martin
Except for the lines above, your logs look better than mine. Only one odd thing in Xorg.0.log: W(II) RADEON(0): Total number of valid Screen mode(s) added: 0 (II) RADEON(0): Not using default mode "640x350" (vrefresh out of range) (II) RADEON(0): Not using default mode "640x400" (vrefresh out of range) (II) RADEON(0): Not using default mode "720x400" (vrefresh out of range) (II) RADEON(0): Not using default mode "640x480" (vrefresh out of range) (II) RADEON(0): Not using default mode "640x480" (vrefresh out of range) (II) RADEON(0): Not using default mode "640x480" (vrefresh out of range) (II) RADEON(0): Not using default mode "800x600" (vrefresh out of range) (II) RADEON(0): Not using default mode "800x600" (vrefresh out of range) (II) RADEON(0): Not using default mode "800x600" (vrefresh out of range) (II) RADEON(0): Not using default mode "800x600" (vrefresh out of range) (II) RADEON(0): Not using default mode "1024x768" (vrefresh out of range) (II) RADEON(0): Not using default mode "1024x768" (vrefresh out of range) (II) RADEON(0): Not using default mode "1024x768" (vrefresh out of range) (II) RADEON(0): Not using default mode "1152x864" (vrefresh out of range) (II) RADEON(0): Not using default mode "1280x960" (hsync out of range) (II) RADEON(0): Not using default mode "1280x960" (vrefresh out of range) (II) RADEON(0): Not using default mode "1280x1024" (hsync out of range) (II) RADEON(0): Not using default mode "1280x1024" (vrefresh out of range) (II) RADEON(0): Not using default mode "1280x1024" (vrefresh out of range) (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) (II) RADEON(0): Not using default mode "1600x1200" (vrefresh out of range) (II) RADEON(0): Not using default mode "1600x1200" (vrefresh out of range) (II) RADEON(0): Not using default mode "1600x1200" (vrefresh out of range) (II) RADEON(0): Not using default mode "1600x1200" (vrefresh out of range) (II) RADEON(0): Not using default mode "1792x1344" (height too large for virtual size) (II) RADEON(0): Not using default mode "1792x1344" (height too large for virtual size) (II) RADEON(0): Not using default mode "1856x1392" (height too large for virtual size) (II) RADEON(0): Not using default mode "1856x1392" (height too large for virtual size) (II) RADEON(0): Not using default mode "1920x1440" (height too large for virtual size) (II) RADEON(0): Not using default mode "1920x1440" (height too large for virtual size) (II) RADEON(0): Not using default mode "832x624" (vrefresh out of range) (II) RADEON(0): Not using default mode "1152x768" (vrefresh out of range) (II) RADEON(0): Not using default mode "1400x1050" (hsync out of range) (II) RADEON(0): Not using default mode "1400x1050" (vrefresh out of range) (II) RADEON(0): Not using default mode "1600x1024" (hsync out of range) (II) RADEON(0): Not using default mode "1920x1440" (height too large for virtual size) (II) RADEON(0): Not using default mode "2048x1536" (height too large for virtual size) (II) RADEON(0): Not using default mode "2048x1536" (height too large for virtual size) (II) RADEON(0): Not using default mode "2048x1536" (height too large for virtual size) (II) RADEON(0): Not using default mode "1920x1080" (hsync out of range) (II) RADEON(0): Not using default mode "1920x1200" (hsync out of range) (II) RADEON(0): Not using default mode "1920x1200" (vrefresh out of range) This looks a bit similar to what Edward O`Callaghan had reported a while back. In his case it seemed to be BIOS version related. Are you sure you flashed the latest BIOS for you system board? Did you check if there are known issues with this model vs. config? The fact that you cannot enter anything seems to be this: The xserver did start, but without establishing X11 mode / root window. It still _looks_ like you are being in text mode, but Xorg is running. Try Cntrl+Alt+Backspace to see if you can get control over the text console. The keys should be recognized, thanks to xkb. However, after killing the server it may happen, that the console got corrupt, and that the mappings don't work at all anymore, that you would instead get lots of crap, escape sequences and random stuff. But in your case it should not happen, because you would have instructed the server to kill itself, rather than killed its pid. What you can try in the interim, before you flash a new Bios, try out the vesa_drv.so ddx module and see what it can do. -- %martin _______________________________________________ opensolaris-discuss mailing list [email protected]
