Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok so this is my latest project. I have Dell gx620 with Pentium D dual core, SATA drive, 2GB RAM and the integrated intel 945 chipset. I loaded Slack 10.2 with using the full install option. I am having several problems so far. But I'll start a thread for each so as to not confuse everyone.
For this thread, I have a problem with the graphics. X will only start up if I use the VESA framebuffer device. If i specify the i810 (thich is my understanding of the device I should use for this chipset), X exits with the error no screens found.
Here are the pertinent sections from the xorg.conf that doesn't work:
Section "Device"
Identifier "IntelDell"
Driver "i810"
BusID "PCI:0:2:0"
VideoRam 16384
# Insert Clocks lines here if appropriate
EndSection
# The Identifier line must be present
Identifier "Simple Layout"
Screen "Screen_1"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
And the output of lspci
00:02.0 VGA compatible controller: Intel Corporation 945G Integrated Graphics Controller (rev 02)
00:02.1 Display controller: Intel Corporation 945G Integrated Graphics Controller (rev 02)
I ran xorgsetup with excellent results. (Thanks for the tip) I'm now running at 1280x1024 and it looks good. My only question is whether I should care that I'm running the vesa driver still.
Xorg.0.log:
(II) VESA(0): initializing int10
(WW) VESA(0): Bad V_BIOS checksum
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 7872 kB
(II) VESA(0): VESA VBE OEM: Intel(r)Lakeport-G Graphics Chip Accelerated VGA BIOS
(II) VESA(0): VESA VBE OEM Software Rev: 1.0
(II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
(II) VESA(0): VESA VBE OEM Product: Intel(r)Lakeport-G Graphics Controller
(II) VESA(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(**) VESA(0): Depth 24, (--) framebuffer bpp 32
(==) VESA(0): RGB weight 888
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
If it works well, I wouldn't worry. I havn't read cwwilsons thread, so I don't know if it talks about DRI on an intel graphics chip... But it might be worth a look (I know I'm about to.)
I think there was a problem with the i810 xorg driver in that version. I could never get it to work on my laptop, had to use vesa, until I upgraded to -current which is using a newer xorg.
vesa works fine for general use so unless you seriously need the acceleration, I wouldn't worry about it.
Probably not. there are some new packages in current, some things have been split up and moved around. the way that worked for me is noted HERE, though your mileage may vary.
The difference for most users would be that after rsyncing -current you would simply cd to the slackware directory (the one containing a/ ap/... xap/ & y/ and maybe following 10.2s UPGRADE.TXT
followed by fixing your kernel (make sure the symlinks are all good and run /sbin/lilo) and re-implementing any custom scripts. making sure the system boots to runlevel 3 just in case X got hooped.... the general drill when making a major system change.
err on the side of caution.
Last edited by truthfatal; 08-06-2006 at 02:09 PM.
If it works well, I wouldn't worry. I havn't read cwwilsons thread, so I don't know if it talks about DRI on an intel graphics chip... But it might be worth a look (I know I'm about to.)
It was written SPECIFICALLY for Intel, and later expanded to Nvidia and ATI and others...
Quote:
Originally Posted by gmartin
and the best way to -current? Will shilo's swaret entry do?
DO NOT USE SWARET TO 'UPGRADE' TO -current!!!!
Shilo even admits in another thread that the swaret deal is wrong.
-current is so far away from 10.2, things will break. Either find a premade iso image of -current, make your own, or find a script that will mirror -current for you and make one.
Quote:
Originally Posted by gmartin
My only question is whether I should care that I'm running the vesa driver still.
vesa is fine. Leave it in, because if all else fails, you can use that to get into X.
Quote:
Originally Posted by masonm
I think there was a problem with the i810 xorg driver in that version. I could never get it to work on my laptop, had to use vesa, until I upgraded to -current which is using a newer xorg.
What are you talking about? Xorg in 10.2 never failed on Intels. There were issues with ATI, but not Intel. You just had a bad configuration, or a chip that was made long after Xorg was written. Did you read my guide and recompile your kernel?
Last edited by cwwilson721; 08-06-2006 at 02:11 PM.
DO NOT USE SWARET TO 'UPGRADE' TO -current!!!!
Shilo even admits in another thread that the swaret deal is wrong.
-current is so far away from 10.2, things will break. Either find a premade iso image of -current, make your own, or find a script that will mirror -current for you and make one.
rsyncing now... I'll try the 10.2 upgrade instructions. I used the to get from 10.1 to 10.2 on another box so that should be straight forward enough. Thanks for the help everyone.
Now, how about a good guide for recompiling? The thread on this site is now 30 pages long. Is there a good synopsis somewhere?
I have my LCD plugged into the DVI riser card on this GX620. While on DVI, the contrast function is disabled using the on screen controls. When this was running windows, the contrast could be set using the advabced desktop properties. Any idea how I do that now?
Just wanted to stop back and let you know how it went. I configured the new kernel with sata, smp & himem support. I had to compile twice because i didn't know which sata driver to compile in the kernel. Got it the second time. We're not booting 2.6.17.7. Linux sees both cores, 2GB RAM and the sata without initrd. Very nice.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.