I'm not planning on running X at all (yet) but would like to get framebuffer to work. Have tried 2.20 and 2.24, but don't really know much about "how" frame buffer works or what and why. What is strange is that noone else I know with one of these boards has registered any trouble with installing.

tbh. if this is too much hastle im not going to worry as I've got too much other shit going on in Real Life at the moment to worry about little bits of non-essential graphics. Might tackle this again in > 6 months.

Did I mention this was VIA: you couldn't have guessed:

jt@moe:/home/cpins$ lspci 00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3123 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. OHCI Compliant IEEE 1394 Host Controller (rev 80) 00:10.0 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc.: Unknown device 3104 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc.: Unknown device 3177 00:11.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio Controller (rev 50) 00:12.0 Ethernet controller: VIA Technologies, Inc. Ethernet Controller (rev 74) 01:00.0 VGA compatible controller: VIA Technologies, Inc.: Unknown device 3122 (rev 03)

/proc/pci/

PCI devices found: Bus 0, device 0, function 0: Host bridge: VIA Technologies Unknown device (rev 0). Vendor id=1106. Device id=3123. Medium devsel. Master Capable. Latency=8. Prefetchable 32 bit memory at 0xd0000000 [0xd0000008]. Bus 0, device 1, function 0: PCI bridge: VIA Technologies Unknown device (rev 0). Vendor id=1106. Device id=b091. Medium devsel. Master Capable. No bursts. Min Gnt=12. Bus 0, device 13, function 0: FireWire (IEEE 1394): VIA Technologies Unknown device (rev 128). Vendor id=1106. Device id=3044. Medium devsel. IRQ 12. Master Capable. Latency=32. Max Lat=32. Non-prefetchable 32 bit memory at 0xde000000 [0xde000000]. I/O at 0xd000 [0xd001]. Bus 0, device 16, function 0: USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 128). Medium devsel. IRQ 11. Master Capable. Latency=32. I/O at 0xd400 [0xd401]. Bus 0, device 16, function 1: USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 128). Medium devsel. IRQ 12. Master Capable. Latency=32. I/O at 0xd800 [0xd801]. Bus 0, device 16, function 2: USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 128). Medium devsel. IRQ 10. Master Capable. Latency=32. I/O at 0xdc00 [0xdc01]. Bus 0, device 16, function 3: USB Controller: VIA Technologies Unknown device (rev 130). Vendor id=1106. Device id=3104. Medium devsel. IRQ 5. Master Capable. Latency=32. Non-prefetchable 32 bit memory at 0xde001000 [0xde001000]. Bus 0, device 17, function 0: ISA bridge: VIA Technologies Unknown device (rev 0). Vendor id=1106. Device id=3177. Medium devsel. Master Capable. No bursts. Bus 0, device 17, function 1: IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6). Medium devsel. Fast back-to-back capable. Master Capable. Latency=32. I/O at 0xe000 [0xe001]. Bus 0, device 17, function 5: Multimedia audio controller: VIA Technologies Unknown device (rev 80). Vendor id=1106. Device id=3059. Medium devsel. IRQ 10. I/O at 0xe400 [0xe401]. Bus 0, device 18, function 0: Ethernet controller: VIA Technologies Unknown device (rev 116). Vendor id=1106. Device id=3065. Medium devsel. IRQ 11. Master Capable. Latency=32. Min Gnt=3.Max Lat=8 I/O at 0xec00 [0xec01]. Non-prefetchable 32 bit memory at 0xde002000 [0xde002000]. Bus 1, device 0, function 0: VGA compatible controller: VIA Technologies Unknown device (rev 3). Vendor id=1106. Device id=3122. Medium devsel. IRQ 11. Master Capable. Latency=32. Min Gnt=2. Prefetchable 32 bit memory at 0xd8000000 [0xd8000008]. Non-prefetchable 32 bit memory at 0xdc000000 [0xdc000000].

From: Tim Green timothy.j.green@gmail.com Reply-To: Tim Green timothy.j.green@gmail.com To: main@lists.alug.org.uk Subject: Re: [ALUG] epia via motherboards & frame buffer Date: Sat, 5 Mar 2005 09:52:49 +0000

On Fri, 4 Mar 2005 23:27:49 -0000 (GMT), J Taylor jt@imen.org.uk wrote:

...

I get really garbled screens once the frame buffering module kicks in. I have a M class mboard with Nemiah 1gig proccies.. suggestions / proposals / jokes or insults welcome...

I probably don't know any specific solutions, but I'd start with the output of lspci and cat /proc/pci

Which kernel versions have you tried? Do you want X to work and, if so, which version?

Good luck! Tim.

---

main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!

_________________________________________________________________ Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo

On Tuesday 08 March 2005 10:30, Brett Parker wrote:

...

I'm not planning on running X at all (yet) but would like to get framebuffer to work. Have tried 2.20 and 2.24, but don't really know much about "how" frame buffer works or what and why. What is strange is that noone else I know with one of these boards has registered any trouble with installing.

A 2.2.20? a 2.4.20? If it's not 2.4.x, try 2.4.x, you'll also need to load the correct framebuffer module, and add an append to the kernel params, fwicr. This is off of the top of my head, though, without looking at the docs. I'll look properly post work.

Some good news:   Bus  1, device   0, function  0:     VGA compatible controller: VIA Technologies Unknown device (rev 3).       Vendor id=1106. Device id=3122.

This identifies the graphics controller as a Via CLE266 CastleRock integrated chip set.

Some bad news: I don't think you will find a kernel frame buffer driver in even the latest 2.6 kernel.. On the other hand, the latest XFree86 *might* have some support for it.

Regards, Paul.