Originally Posted by mike_w
Can I mix different versions (unstable/testing/stable etc..). What are all the different types of packages, Ill add them, if I should?#deb file:///cdrom/ etch main
deb http://ftp.ticklers.org/debian/ testing main
deb-src http://ftp.ticklers.org/debian/ testing main
deb http://security.debian.org/ testing/updates main
yes, but it's VERY important before you do to edit /etc/apt/apt.conf, and place the following line:
else apt-get dist-upgrade will transfer your entire system to unstable.Code:APT::Default-Release "VERSIONYOUWANTTOUSE";
you're likely to only ever need unstable & stable. i do.What are all the different types of packages, Ill add them, if I should?
I'm not sure if you're supposed to mix them, but I've done it and it's been fine - just change testing to unstable, and then change it back to testing once you've got the packages. It's probably safest to stick with just one though. If you want to keep with testing for everything else (I generally don't use unstable because it can be, unsurprisingly, unstable), just change it back to testing.
Different types of packages? You mean being able to access different ranges of packages? I would stick with one branch i.e. stable, testing or unstable, although there are is also contrib and non-free, besides main. The line in sources.list would be:
That way, you can get packages such as msttcorefonts, which installs fonts such as Arial.Code:deb http://ftp.ticklers.org/debian/ testing main contrib non-free
I also have:
That's where I get java from.Code:deb http://www.tux.org/pub/java/debian stable non-free
Last edited by mike_w; 08-08-2005 at 07:56 PM.
"Well, there was your Uncle Tiberius who died wrapped in cabbage leaves but we assumed that was a freak accident."
So my /etc/apt/apt.conf should look like:
Ive changed my /etc/apt/sources.list to:Code:APT::Default-Release "STABLE";
should I leave the last one as testing?Code:#deb file:///cdrom/ etch main #deb http://ftp.ticklers.org/debian/ testing main #deb-src http://ftp.ticklers.org/debian/ testing main #deb ftp://ftp.uk.debian.org/debian/ unstable main deb http://ftp.ticklers.org/debian/ stable main deb-src http://ftp.ticklers.org/debian/ stable main deb http://security.debian.org/ testing/updates main
This looks like the reson everything feels like 800*600:
As I only want to use a depth of 24bpp can I remove all of the others, and replace both low res modes with 1280x1024?Code:Section "Screen" Identifier "Default Screen" Device "Generic Video Card" Monitor "Generic Monitor" DefaultDepth 24 SubSection "Display" Depth 1 Modes "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "800x600" "640x480" EndSubSection EndSection
[edit]I didnt remove anything, only added "1280x1024" infront of the other res's and it works, and acctually hurts my eyes a bit (probably because I set the fonts as small as possible in 800*600[/edit]
Last edited by SilentDeath; 08-08-2005 at 08:51 PM.
This thread is getting stupidly long now
In a termpinal, if I do "su", how do I un-su myself after?
Nothing happensCode:kram@MPC5:/etc/init.d$ su Password: MPC5:/etc/init.d# gdm stop gdm already running. Aborting!
To stop being root, type exit. As for getting out of gdm, I think you need to type ./gdm stop if you're already in the directory.
"Well, there was your Uncle Tiberius who died wrapped in cabbage leaves but we assumed that was a freak accident."
Another problem - the ATI driver release notes say:
My cards pci-express, so do I still need agpgart?Code:Version 2.6 kernels require a second kernel module in addition to agpgart, which should be named similar to the manufacturer of your motherboard AGP chipset. This error message should occur if the other agp module is not loaded. This issue can be worked around as follows: 1. First make sure that agpgart is loading properly. 2. To find out which AGP controller your motherboard uses, issue the following command: lspci | grep AGP 3. To find a list of AGP related kernel modules installed on your machine, issue the following command and look for a module (*.ko file) that suits your AGP Controller: ls /lib/modules/`uname -r`/kernel/drivers/char/agp 4. Use the modprobe command (as root) to load the module. For example: On a motherboard using a VIA® AGP Controller, you would load the via-agp.ko using modprobe as follows (notice that the trailing .ko is omitted): modprobe via-agp
Does this driver support nforce4? http://www.nvidia.com/object/linux_nforce_1.0-0301.htmlCode:MPC5:/home/kram# lspci 0000:00:00.0 Memory controller: nVidia Corporation: Unknown device 005e (rev a3) 0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 0050 (rev a3) 0000:00:01.1 SMBus: nVidia Corporation: Unknown device 0052 (rev a2) 0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 005a (rev a2) 0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 005b (rev a3) 0000:00:04.0 Multimedia audio controller: nVidia Corporation: Unknown device 0059 (rev a2) 0000:00:06.0 IDE interface: nVidia Corporation: Unknown device 0053 (rev a2) 0000:00:07.0 IDE interface: nVidia Corporation: Unknown device 0054 (rev a3) 0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 0055 (rev a3) 0000:00:09.0 PCI bridge: nVidia Corporation: Unknown device 005c (rev a2) 0000:00:0a.0 Bridge: nVidia Corporation: Unknown device 0057 (rev a3) 0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3) 0000:00:0c.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3) 0000:00:0d.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3) 0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 005d (rev a3) 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:01:09.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 0000:01:0a.0 Ethernet controller: Marvell Technology Group Ltd. Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (rev 13) 0000:05:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5d4d 0000:05:00.1 Display controller: ATI Technologies Inc: Unknown device 5d6d
Last edited by SilentDeath; 08-08-2005 at 09:40 PM.
Sorry, antiquated hardware here - only nForce2 and AGP. That is one of the problems with Linux - there can be a delay between product releases and it being easily configured/used with Linux.
"Well, there was your Uncle Tiberius who died wrapped in cabbage leaves but we assumed that was a freak accident."
pciexpress doesn't have great linux support at the moment, and I'm not sure if the pciexpress components have made it into debian yet
This thread appears to be getting a little long and almost to a degree of hand holding.
It is Inevitable.....
I don't think so, so long as PCI-Express support is compiled in the kernel. You can check this by reading the kernel config file, i don't know about Debian, but a lot of distros have the config built into the kernel which you can access by /proc, typing: ls /proc/config.gz should reveal if that is the case, if the file exists, great, you can then extract it and check if PCI-E support is enabled:
cd ~
gzip -dc /proc/config.gz | grep PCIEPORTBUS
if grep returns nothing or CONFIG_PCIEPORTBUS=n, you'll have to go about compiling a new kernel.
Unfortunatly this is the price you pay for bleeding edge hardware on Linux.
Oh, I have another goodie for you, Mouse Support in X11R6.8.2, a decent configuration doc to help you get your mousewheel working, most of the stuff you need is in xorg.conf Options.
Last edited by aidanjt; 08-08-2005 at 11:28 PM.
my (PCIe) 6800GT worked from the word go on amd64 debian
i think the bigger question is how well fglrx, with its heavy focus on agp (and integrated agpgart replacements) copes with PCIe
directhex very interesting. Its good to know Debian do actually have support for PCI ready to go (I've not used debian on a PCI-E system hence me saying "I don't konw")
The PCI-E support in the kernel in general appears to be around %70/%30 in a work/fail balance from what I've seen (and to a degree read) as long as its big company asus/msi/abit boards though it seems to work ok. You very right about fglrx, plus a few other things are "expecting" AGP, surly work is in progress to move these apps to a more generic interface/handler for graphics cards.
It is Inevitable.....
Soltek K890Pro-939, Via K8T890 chipset.
Seems to be a possible kernel of gfx bios bug though, I can't use vesafb on one of my card outputs
Ive b0rked it.
In "/etc/X11/XFree86-4.conf" I changed mouse protocol from "ImPS/2" to "usb" expecting at worst,the mouse wouldnt work. Intead, when it gets to X, it just changes res a few times then the screen goes off.... Ill attempt to change it back
the "Auto" protocol will work fine for usb mice, read from /dev/input/mice, make sure you have those ZAxisMapping entries, might have to fiddle with it a bit to get the right 'button' Axis mappings to make sure down is down and up is up, instead of 'back button' being down or something silly lol.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote
