On Wed, Jan 16, 2013 at 10:50:36AM +1100, Rod Whitworth wrote: > On Tue, 15 Jan 2013 11:33:54 +0100, Stefan Sperling wrote: > >The dmesg you quoted is from 5.2. Please show the -current dmesg from > >the USB stick install which actually has the problem. > > I was not clear enough. I only ran the USB boot to see if the problem > with losing video on the Vcons was fixed. > > The problem is with the 5.2 release not running E. It works well with > several WMs but when X is running you have to work blind on the Vcons. > > I just wanted to see if X in a recent snapshot still hid the other > consoles and it doesn't so my new Tpad is on its way. Meanwhile I just > want to play with E as it comes with 5.2 release so that I can learn > how to config and use E. Then I'll be ready to do testing of your .17 > versions when the new Tpad is here.
The e17 port in 5.2 is an alpha release. So I suspect you are seeing a bug in that alpha release when you try to run e17 on 5.2. To try the e17 0.17.0 release, you have to run -current. > >I have another unrelated question about the machine: > > > >> "Realtek RTS5209 Card Reader" rev 0x01 at pci3 dev 0 function 0 not > >> configured > >> sdhc0 at pci3 dev 0 function 1 "Realtek RTS5209 Card Reader" rev 0x01: > >> apic 2 int 19 > >> sdmmc0 at sdhc0 > > > >Does the card reader work in 5.2? Does it work in -current? > > No. Same dmesg lines. Same dmesg lines in -current as in 5.2? I very much doubt that. Are you sure you were trying a -current kernel? I would expect -current to show something like: rtsx0 at pci3 dev 0 function 0 "Realtek RTS5209 Card Reader" rev 0x01: apic 0 int 18 sdmmc0 at rtsx0 "Realtek RTS5209 Card Reader" rev 0x01 at pci3 dev 0 function 1 not configured See http://marc.info/?l=openbsd-tech&m=135732675613607&w=2 (the diff has been committed)
