Marek Williams wrote: > Santa came while I was in class this morning!!!!!! > > OK, he arrived in a FedEx truck instead of a sleigh, but hey! Who's > complaining? > > So guess what I got? A shiny new Compaq R4000US! It has 1 Gb > RAM, an 80 Gb 5400 rpm hard disk and the ATI Radeon Xpress > 200, plus a bunch of other cool toys, including an Athlon 64 4000. > > So I have spent all afternoon installing Suse Linux 9.3 (64) from a > retail box. It found pretty much everything, including the Radeon > Xpress 200, but for video it installed vesa 1024 x 768 instead of 1280 > x 800 as I was hoping. > > YaST finds: > > Framebuffer device > MS48 > Bus: None > Class (spec): VESA Framebuffer > Class: Framebuffer > Device: MS48 > Model: ATI MOBILITY RADEON Xpress 200G Series MS48 > Old Unique Key: PxbD.Orxp2Ohjz55 > Resources (lots of stuff under framebuffer, mem and phys mem > Revision: 01.00 Sub Vendor: ATI MOBILITY RADEON Xpress 200G > Series Unique Key: rdCR.mrzO17txmKC Vendor: ATI Technologies > Inc. bus_hwcfg: None > > Unfortunately, I understood zero of the above. Elsewhere there is a > place to Add New Card, where it lists ATI as a vendor, but this card > is not listed. > > I know I have read somewhere (perhaps here, but I can't find it) where > someone with this video chip got it running at 1280 x 800. That's all > I want -- I don't need virtual screens and stuff. > > Please bear in mind that I know next to nothing about Linux. :( > > Any help will be gratefully received. > > -- > Bogus e-mail address, but I read this newsgroup regularly, so reply here. Actually this is a more general situation. I'm running FC2 on a box with a Matrox Millennium video card, and I can't get any more than 800x600 (or something like that) out of it. Is there a general approach to "force" FC (or any distro) into a different video mode?
2. NetBSD/amd64 2.0.2 on Compaq R4000 keyboard not working
3. FreeBSD on the Compaq R4000?
4. FreeBSD/amd64 install freezes on Compaq R4000 - FreeBSD
5. weird name resolution problem w/ bind
Newsgroup, I do have a strange behaviour of bind (version 9.2.3 running on SuSE 9.1, kernel 2.6.5-7.75-smp) as follows: ping hp8550 (hp8550 is a local networked printer) from a ssh window (putty) times out without resolving the name yielding an error message as follows: ping: unknown host hp8550 This is also the case if started with the FQDN (ping hp8550.xxxxx.local) to resolve for the IP address: ping: unknown host hp8550.xxxxx.local nslookup hp8550 from the same ssh console returns the correct FQDN together with the IP-number as follows: Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing. Server: 192.168.xx.1 Address: 192.168.xx.1#53 Name: hp8550.xxxxx.local Address: 192.168.xx.64 Same ping from a XP cmd window of a local PC connected to the local domain works without any problems: ping hp8550 resolves to the correct IP and pings. All external pings (i.e. hosts not in the local domain) with domain names resolve for the IP address and work as expected regardless whether from XP or ssh window. You can substitute bind with telnet, ftp, etc - all do not resolve correctly if executed from the ssh console. BTW the same is true for the linux console Setup is as follows: authoritative bind for the domain xxxxx.local with "forwarders ..." to the ISP's name servers with "forward first". Restricted to allow queries from the local subnet + loopback and listening on dedicated local subnet address (192.168.xx.1) plus loopback. At the moment I am clueless and would appreciate any suggestion. Many thanks and best regards, Klaus