LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Turn off hotplug, yet detect a mouse (https://www.linuxquestions.org/questions/linux-hardware-18/turn-off-hotplug-yet-detect-a-mouse-538645/)

davidguygc 03-19-2007 12:51 AM

Turn off hotplug, yet detect a mouse
 
I really hate having to sit through hotplug during startup, only for it to detect my mouse. How can I turn off hotplug, but still have Linux detect my mouse?

My mouse is a a USB mouse, uses the IMPS/2 driver.

Thanks,
David

GrapefruiTgirl 03-19-2007 08:08 PM

As long as you manually modprobe the kernel module(s) needed to run your mouse, you don't need to hotplug it.
Type LSMOD in a terminal to identify the mouse-driver-module(s) from the list of loaded kernel modules, and then locate that module in (or add it to) /etc/rc.d/rc.modules or /etc/rc.d/rc.modules.<kernel-name> or /etc/rc.d/rc.local with a statement like 'modprobe <module-name>' (or for a 2.4 kernel: insmod <module-name>).
Before eliminating hotplug, make sure it is not needed to load anything else either, particularly with the default 2.4 kernel. If it is, you must manually modprobe all things that hotplug does.

As for actually disabling the rc.hotplug script, just chmod it to non-executable (chmod -x /etc/rc.d/rc.hotplug)

EDIT: And actually, it's the /etc/xorg.conf which installs/chooses the mouse driver itself, so I stand to be slightly corrected regarding that one, but if hotplug is plugging the USB driver, you'll need that one for sure, if it isn't compiled into the kernel, which it may well be..

Hope this helps you :)

Electro 03-20-2007 01:17 AM

udev/HAL/dbus is going to replace or already replaces hotplug. In either /etc/modules.conf or /etc/modprobe.conf add the following.

alias char-major-13 mousedev
post-install mousedev modprobe usbhid

If the above is too confusing, place the lines in the files what GrapefruiTgirl provided. The utility insmod should only be used if there are no dependencies for other modules. I suggest using modprobe instead of insmod. Specify the full path to these utilities to make them predictable upon boot up.

Xorg 7 and above should load up USB mouse and USB keyboard modules automatically, but it may not do it always. Though it will not automatically load up the module for PS/2 mouse, so you have to do it manually load it through scripts and not through /etc/modules.conf or /etc/modprobe.conf.

FYI, IMPS/2 is a type of protocol a mouse uses not a driver.

Including noapic may make a USB mouse be detected faster.

davidguygc 03-20-2007 02:03 AM

man, there is so much stuff that is needing that hotplug, I couldn't possibly turn it off. I hear that there is a 2.6 kernal, I'm running 2.4.33.3 right now. How stable is the new kernal?

Does the new kernal also make what I'm trying to do easier?

Thanks,
David

davidguygc 03-20-2007 02:07 AM

I added that post w/o refreshing the browser, so I didnt see your post Electro. I got my mouse to work, but then turning off hotplug meant my ethernet and sound went out the window too. I got the ethernet to work, but there are just to many things for sound for me to care over. So is this udev with the new kernal, or would I have it now?

Thanks

GrapefruiTgirl 03-20-2007 05:25 AM

Udev is a tool which is not 'part' of the kernel, however, with the 2.6 kernels, UDEV is the method which replaces hotplug, and accomplishes the same task. And yes, Slackware 11 already has UDEV in its default configuration; it just is not used when the kernel is 2.4. If you switch to 2.6, udev will be used instead, and should require little or no configuration..
As for the new kernel making it easier to do what you're trying to do, the short answer, in my opinion, is YES. You don't have to wait for hotplug to work, and there's one less script to deal with/worry about as far as getting the needed stuff loaded.
If you felt adventurous, and compiled your own kernel, you could compile all the modules you need right into the kernel, and not need to load ANY modules :)
The same principle applies for the ethernet and for sound: either udev can do it, or you can compile the needed support right into the kernel, or you can use one of the rc.modules scripts to force-load them.
Oh, and finally- the 2.6 kernel is as stable as ever, in my experience, and has somewhat more functionality when one really gets down to details. As with any product, the newer and fresher it is, the more potential for undetected bugs; but I've been using the 2.6.20 kernel for close to a month now, and I'm delighted. Don't take it from me necessarily, there are lots of 2.6 kernels to choose from; do some reading.
The 2.6.17.13 I found to be VERY resilient and stable, easy to work with, and I **think** that's the 2.6 version also included with Slack 11.
For comparison, you could grab the 2.6 source-code for the kernel, compile it using the default configuration which would very likely include all necessary modules for your hardware, and install it as a second kernel, allowing you to choose which one to boot. This way, you can compare them, and see the difference. Nothing is stopping you from having a few different kernels to boot :) instead of "ONLY ONE".

davidguygc 03-20-2007 10:58 AM

Sounds good then, so where do I get the new kernal, and how do I compile and replace my old one?

Is my current kernal hidden somewhere impossible, or am I lucky, and it is the one in /boot?

And finally, would I only have to replace the kernal file, or would it also need new /etc files?

Thanks,

David

GrapefruiTgirl 03-20-2007 11:12 AM

OK, you're in the us, so go to us.kernel.org or Google 'Linux Kernel'. Kernel.org is the official kernel archives, where you can download all the kernel sources. There **might** be sources on your install disk, but as I recall there aren't.
You'll need to pick a kernel, maybe 2.6.18 or 2.6.17 or 2.6.20, whatever suits you. Remember, there are **potential** problems with super-new stuff, but these ones I suggest have been implemented for some time now, and seem pretty reliable. I have had zero problems with 2.6.20. Also, be sure to download the corresponding MD5 checksum file, so you can verify that your kernel source is untampered with.
The kernel file you will download will be an archive, about 40-50 MB

The kernel isn't hidden at all. It is the one in /boot. it's around 1.3 to 1.9 MB, I can't remember exactly, and is called linux-2.4.33.3-<whatever>. Just leave that there, never remove it, atleast until you have a firm grip on compiling your own. You should ALWAYS keep a known-working kernel and modules installed and bootable. So just ignore that one for the time being.

The majority of the files in /etc will not change, or will change very little, depending on any adjustments you need/decide to make after installing a new kernel. For example, you will eventually not need the rc.hotplug file, so you might choose to remove it, or disable it.
Ultimately, none of the files in /etc will change by themselves except perhaps one called 'kernel-version' but even that you may have to adjust yourself.
As far as changes to any files in /etc, it's up to you. Depends what needs to be done.

As for compiling your new kernel, there are millions of tutorials floating around. Check here on LQ, check in /usr/doc on your system, and use Google. I'll be happy to help along the way, but you should get acquainted with a tutorial first, and have a read. Also, I think the kernel comes with a basic README file: instructions on how to do it.

After compiling the kernel and modules, and installing the modules, you will have to set up the bootloader, so it can find and boot the kernel.
Assuming you are using LILO bootloader, I'd be happy to help you with it. If you use GRUB, I'm not familiar with that one, so you will have to check the man pages or browse some more ;)

davidguygc 03-20-2007 12:19 PM

Ok, so heres what I did:
-Downloaded 2.6.20.3 kernel
-did "make xconfig"
-did "make"
-did "make install"

rebooted

Now my sound is not working. How can I tell which kernel I'm running?

davidguygc 03-20-2007 12:22 PM

OK, nevermind, I figured out which kernel, I'm using 2.6.20.3 Sooooo I still have that sound problem.

Also... whenever I was booting, it didn't print out what it was doing like earlier, is there a way to get it to show me? (I am actually kinda learning stuff from looking at it lol)

GrapefruiTgirl 03-20-2007 01:00 PM

Uhhhh.. OK, Make xconfig is good.. And when done, did you SAVE the config you made?
Then 'make' next, that's fine.
But now , should have been make modules (though they probably got auto-made), and then make modules_install.
After that, you would move the fresh kernel to /boot, name it something if you like, and then configure the bootloader.
Typically one doesn't use 'make install', so I can't comment on what exactly that did, but... Are you actually running the new kernel? Possibly so, maybe not. Probably not, unless you configured the bootloader, and if you are, then the sound isn't working maybe because you didn't do make modules_install.
Let me know what's happening now. I was off having a nap :)
Oh, and if it isn't showing you stuff scrolling by during boot, it's likely you forgot to incorporate framebuffer support or support for your video hardware, when you made the kernel.
A good way to make your first kernel, is to use the previously existing .config file from the original kernel, which *should* perhaps be in the /boot directory maybe..

PS - you can also look at all the bootup messages by examining /var/log/dmesg and /var/log/messages

davidguygc 03-20-2007 01:16 PM

I did
Code:

uname -a
and it told me I was running this kernel

So I ran make modules_install. What should I rerun now, if anything?

GrapefruiTgirl 03-20-2007 01:23 PM

Well.. If it says you're running the new kernel, and you now have your modules installed, that's all good.
you don't need to re-run anything after installing the modules. But you may choose to reboot and see if anything gets plugged-in during boot, now that the modules are there.
However, when you boot the machine, you should get a choice of what to boot, either the 2.4 kernel, or your new one. If you don't, it makes me wonder how the machine is booting properly..
In any event, the key now is to find out if everything is working, or if you're missing modules (they aren't getting loaded for example) and to adjust anything you need to as far as the /etc/rc.d/rc.modules scripts.
You should type LSMOD in a terminal and see what modules are loaded.
If your sound isn't working, you may have to run alsamixer (type alsamixer in a root console) and make sure the sound settings are turned ON, and not muted. then if/when done that, escape and type 'alsactl save' and test out the sound system.

davidguygc 03-20-2007 01:35 PM

Well, I'm running LILO off of a floppy, that immediately boots to Slack. I went back and redid the xconfig. I'm right now redoing make, then after that I will do make modules_install for good measure, then make install

I wont be back till after 630PM CST, so I'll work with anything you give me.

Thanks for the help, I really appreciate it!

GrapefruiTgirl 03-20-2007 01:45 PM

Why are you using the floppy? Any particular reason?
Anyhow, , you seem to be getting a grip on this stuff very quickly :) Congrats on that!
I will likely be around this evening, that's about 830 pm my time, so I'll see ya back here.
And I should note, If you notice that stuff isnt working, like the sound, and you can't get it working (or anything else for that matter), You should take a few hours and go thru the entire xconfig, and get acquainted with all the options, especially as there's probably a lot of stuff you could adjust to make the kernel better suited to your needs, and your exact hardware configuration, as well as removing stuff you absolutely don't need. Plus, you can avoid modules entirely by compiling them right into the kernel, OR you can even completely modularize it (well, nearly completely). Lot's of fun to be had, and the satisfaction of knowing your OS and kernel inside out, unlike with some 'other' OS's ;)
I'll leave you to it, and chat later on!
Sasha
PS - You're welcome, any time.

davidguygc 03-20-2007 05:23 PM

I've installed Linux a couple times before, and something would always happen and I'd mess up the MBR to where I couldn't boot up my computer. So this time around, I'm not messing with the MBR and just going to go the safe route with booting through a floppy.

I recompiled the kernel by adding some sound support through xconfig (it actually says gconfig when it runs, who knows lol). When I do that, am I incorporating those modules into the kernal itself, or is it accessing something like /etc/rc.d/rc.modules and just adding modprobe lines?

And I'm assumming that putting modules into the kernel itself is faster than modprobe-ing them individually?

-David

GrapefruiTgirl 03-20-2007 06:47 PM

Correct, when you use x or g config, and select an item, most items can be selected either as 'M' for module, and usually a checkmark or something for 'compiled-in'. If the difference is either a dot or a check, then the dot means module, and the check means compiled in.
If you use make 'menuconfig' instead of make xconfig, then items with a < > beside them can be made as modules, as opposed to items with [ ] beside them, which can usually be modules OR be compiled right in.
With modules, the modules get compiled as little chunks, and will be put into /lib/modules/<kernel-name>/, and will be loaded either by script, manually, or by hotplug on 2.4 kernels, or by udev on 2.6 kernels.
When they are compiled in, they are actually built-into the kernel. No loading required.
If I had to guess, logically it would seem that having them compiled statically into the kernel would be the faster way of doing it, but probably not noticably faster to the naked eye, so to speak.

davidguygc 03-20-2007 07:15 PM

So, I've been going through qconf, I see this "Real Time Clock". It's not enabled, and my instinct says this should be enabled.

What should I do with this?

davidguygc 03-20-2007 07:20 PM

Also, everything that I want I'm just including into the kernel... What will slow down in this? Runtime? Booting? Loading LILO?

davidguygc 03-20-2007 07:45 PM

OK, hopefully this won't blow up my computer... I don't know how to attach my config file. lol I now have like 3 .config files, how does the make know which is which?

GrapefruiTgirl 03-20-2007 08:02 PM

OK, each option has a help, or a blurb about it, which *usually* can tell you if you need it, should have it, dont need it, etc.
the RTC is optional, but as I recall you can add it, and if your machine doesn't have a use for it, linux will default to not using it.

Installing everything you want into the kernel is not harmful, will not noticeably slow anything down, won't bother LILO, and is better than not loading enough stuff. I actually prefer loading everything into my kernel too. The main reason people make modules is to conserve space by making the kernel smaller, for example if they plan to install the kernel to a floppy, or run it on a machine with like no memory. Also, if you were to want this kernel to run on a variety of different machines, you would select loads of modules for everything, but compile in the absolutely needed ones. It is better to err on the side of caution, ie putting extra stuff in, rather than missing something.
NOTE: You MUST compile in the support for your IDE chipset, and the type of filesystem that your root is mounted on. So if you use IDE/ATA hard disk with the root system as an EXT2 filesystem, those things MUST be built in, because at the early stage of booting, the kernel has no modules in it yet, and cannot load modules, for a filesystem if it doesn't yet know how to read that filesystem. Get it? :).

LOL, it wont blow up your machine :) It will either run perfect, run not perfect, or not boot or work properly. But it wont blow up.
If you are using xconfig, the second option from the very top of it all, you can go into and 'name your kernel' with an extension to its release number. I usually tack on the date, with an additional hex character if I make more than one in the same day, so my current kernel for example is called 2.6.20-fe19-0e. The 0e tells me it is the 5th version of the kernel I made originally on Feb 19.
When you are all done, Select FILE at the top menu, and save the config as something you recognize. THEN, after that, press the little disk picture, to save the .config file.
Every time you run xconfig and save it when done, it will save a new version of the file .config, which is what 'Make' uses to build the kernel.
:)

GrapefruiTgirl 03-20-2007 08:11 PM

Something else you should research, is what sort of hardware monitoring sensor chips are present on your motherboard.
There is a tool called lm_sensors which can help do this. Alternatively, you can physically investigate the board, or get a data sheet/spec sheet for the boatd from the manufacturer.
This allows you to enable support for system temperature, fan speeds, CPU temperature, etc etc.. Could come in handy when one day the CPU fan dies and the CPU starts to overheat. The sensors monitors can warn you or shut the machine off.

davidguygc 03-20-2007 08:19 PM

I'm about to reboot, and this may or may not still be a problem, I just don't want to retype it lol.
Quote:

Originally Posted by Me
OK,well I booted up, all seems well. Except when I try to boot my jump drive (/dev/sda1), it says:
Code:

bash-3.1# mount /dev/sda1 /mnt/JumpDrive
mount: special device /dev/sda1 does not exist


Also, I still can't see the boot up text; and it took forever to load

GrapefruiTgirl 03-20-2007 08:26 PM

Hmm, I don't remember you posting that :D about the Jump drive.
What's a Jump drive anyways?
First, if it didn't mount the device, verify by reading /var/log/dmesg that the device was detected during boot.
Second, Verify that /etc/fstab lists the device correctly, ie that it has the correct name.
Third: Is that a USB device?
and Fourth: Did you get screen display this time during boot? If not, then you are missing either the module(s) needed by your video hardware, or a suitable frame-buffer device, in your configuration.

Sp.. How'd it go?
:P

davidguygc 03-20-2007 08:41 PM

lol yes I got the screen to boot, with two Tux's at the top! Woo!

yes, the Jump Drive is a USB Mass storage device

There is this "usbfs" and "sysfs" when I type "mount"

Here is everything from dmesg pertaining to USB:
Code:

ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 18, io mem 0xffa80800
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 16, io base 0x0000ff80
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000ff60
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 20, io base 0x0000ff40
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000ff20
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
usb 1-7: new high speed USB device using ehci_hcd and address 4
usb 1-7: configuration #1 chosen from 1 choice
usb 4-1: new low speed USB device using uhci_hcd and address 2
usb 4-1: configuration #1 chosen from 1 choice
usb 4-2: new low speed USB device using uhci_hcd and address 3
usb 4-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.

I disabled SCSI from the kernel, because I don't have anything SCSI, but now that I think about it, USB is SCSI isn't it?

GrapefruiTgirl 03-20-2007 09:13 PM

Umm.... USB is not SCSI, no. However, your drive may be SCSI protocol, but plugged into USB.
Not sure on that option. I have also disabled all SCSI stuff, but I don't have any USB things currently in use to test it out.
I think you are safe w/o SCSI, because the USB options are clearly specified in the config.
AND.. YOU GOT TWO TUXES!?!?!? Bwaahahahah I want 2 Tuxes :) :) How the heck you did that??
LOL

And from what I see in your dmesg, everything is detected properly, it looks very good ;) Nice job!
I see USP Mass storage device, and a USP printer (do you have one of them?)
And I see that it actually is using SCSI-emulation for the USB storage devices at scsi-0. interesting.

GrapefruiTgirl 03-20-2007 09:14 PM

There is this "usbfs" and "sysfs" when I type "mount"

Yup, USB-file-system, and SYStem filesystem.

...I want coffee :) Any takers? Linux and coffee go well, maybe that's where the debian-coffee-cup came from ! :P

davidguygc 03-20-2007 09:16 PM

Well, I still can't for the life of me mount my USB drive, it still gives that error. I see an error when its booting about how dma is off for my drive, but I can't find it in any of my logs.

GrapefruiTgirl 03-20-2007 09:22 PM

Hmmmmm.. I'm trynna think of what to do next for the USB drive, while the coffee boils..
Could you be missing something else from the .config, that might be needed to mount the drive?
Far as I can tell, the machine has no trouble seeing the drive.
And which device is claiming to have no DMA?
You can enable DMA manually if it isn't coming on by default. Also, there's BIOS settings for DMA usually too.
As for enabling DMA, in a console type 'hdparm' and you will get a list of settings you can apply to a drive or CD/DVD device. DMA=ON is one of them.
The format for hdparm is usually 'hdparm -X -# /dev/ds1' where X, # and ds1 are whatever command, number and device.

davidguygc 03-20-2007 09:25 PM

All I have to say for that dma thing is if it ain't broke, dont fix it. I don't see anything not drive working, other than the USB. does 2.6.20.3 not use /dev/sda for a usb drive? Did they switch it to that other one?

GrapefruiTgirl 03-20-2007 09:39 PM

I can't comment either way if they use /dev/sda or something totally different. You *should* be able to identify the device in the dmesg. However, it may be back to google for info on device names for USB drives.
You could also check the man pages for 'mount' and 'fstab' for options for USB drives and filesystems.
What filesystem actually IS on the drive? Any idea? Or is it actually a USBFS system?
You could look in /dev too, for clues.

davidguygc 03-20-2007 09:47 PM

OK, so I turned on like 10 SCSI things, and now I can mount it, so I'll just chalk that one up to bad magic.

It was a VFAT fs

P.S. I think I got the second Tux I think from Graphics support -> Logo Config and turned everything on.

So, I've had a checklist of stuff to fix, and lost it. But I do remember needing to fix my graphics card.

Do you know anything about AGP graphics cards?

If not, thanks for all your help, you're a lifesaver

GrapefruiTgirl 03-20-2007 09:52 PM

LMAO! LOL, Infact I do know some stuff about AGP cards. I have 2 screens plugged into mine as we speak. And also I am working with another user who is having a WICKED time trying to get her display working.
I definitely don't know everything, but depending on the card, and what you need to do, I will help if I can.

NOTE: in order to keep the threads atleast a little bit on topic, I recommend you start a new thread for your AGP issue, and then tell me where the thread is :)
Hehehehe

davidguygc 03-20-2007 09:54 PM

Well, I have a 512MB Nvidia Geforce 5800ish, and I cannot get the resolution past 1024x768. I tried setting xorg.conf to only load in 1280x1024, but it seems to just ignore it. What kind of driver do I need to be able to use that resolution?

GrapefruiTgirl 03-20-2007 10:01 PM

Ohhh this is perfect :)
I have an nVidia Geforce4 MX440 AGP8x, so you have come to the right place.
First things first: Go to the nVidia website and locate the correct proprietary nVidia driver for your card. Read carefully there, the supported-hardware list is rather obscure, and I had to try 2 or 3 of them before I found the one for my card. Incidentally, I have the 9631 driver.
So.. Go there, get the driver for your card, download it, follow the instructions carefully to install it, and at the last step of the driver installation, it will ask you if you want it to edit your xorg.conf file. SAY NO!!
This will all be done in init 3 level by the way; so before you go to install the driver, open a console with root priveleges, and type 'telinit 3'.
This will take you to the login text mode.
login as root, type 'mc' to start midnight commander. Navigate to where you saved the installer, exit MC, run the installer, when done go into MC again, navigate to your etc/X11/xorg.conf file, and change the 'nv' in the device section to 'nvidia', and then type 'telinit 4'
When you finish all this, or if you get stuck, start a new thread somewhere, and I will find it and join you.
:)
PS - It's probably nVidia.com, but don't quote me.

davidguygc 03-20-2007 10:06 PM

let me go ahead and post the pertinent info in the xorg.conf file
Code:

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync  31.5 - 50.0

#    HorizSync        30-64        # multisync
#    HorizSync        31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync        15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 40-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "VESA Framebuffer"
    Driver      "vesa"
    #VideoRam    4096
    # Insert Clocks lines here if appropriate
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "VESA Framebuffer"
    Monitor    "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

#  DefaultDepth 8
#  DefaultDepth 16
#  DefaultDepth 24
#  DefaultDepth 32

# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)
    Subsection "Display"
        Depth      32
        Modes "1280x1024"
    EndSubsection



EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection


GrapefruiTgirl 03-20-2007 10:10 PM

UGH! We have some work to do. But first, go and do the driver stuff, but don't let it change your file yet. When you come back in a new thread, I will post you a version of my file for you to start with, which should get you up and running.
:)
PS - for one thing you cannot use 32 as a depth. 24 is max, which in windows is written as 32.

davidguygc 03-20-2007 10:30 PM

Well, I can't get the driver to start to save my life, it wants me to accept a license, but it's screwed up, so I finally get it to accept it, then its just giving me option stuff, but wont let me actually choose them, how do you pass more than one option? just file -A -X or file -A, -X because this thing is being a pain about it

GrapefruiTgirl 03-20-2007 10:33 PM

OK, it is keyboard operated. So use left and right arrows and RETURN key ;)
And you dont need to download the kernel compiler thingy, it will make its own, so press NO for that option.

davidguygc 03-20-2007 10:35 PM

OK, i did telinit 2 and it worked, but I have to recompile my kernel before I can go any further, it is complaining about a module I put in it. So right now I'm doing that, then hopefully it'll all be said and done after that w/o too many hitches

GrapefruiTgirl 03-20-2007 10:36 PM

ok.. But use telinit 3, not 2

davidguygc 03-20-2007 10:39 PM

btw I've noticed that /sbin/ldconfig is friggin slow... what is that?

GrapefruiTgirl 03-20-2007 10:43 PM

It's the 'shared library updater'. There's debate about whether it must be ran on every boot, and I'm not sure, but I do know that if your shared libraries get out of whack, it is very bad, so I leave it alone.
It gets faster too, eventually. I dunno why, but mine takes like less than a second now.
Leave it for now, is my advice.

davidguygc 03-20-2007 10:52 PM

OK, so the only difference now is that the control panel gives me a grayed out bar for Settings for screen, and a refresh rate. It told me right at the end a README file, but I don't remember where it said it was, What should I do now?

GrapefruiTgirl 03-20-2007 11:05 PM

OK, for now I'll assume the greyed out bar is because the driver is not being used yet. Give me a few moments here, and my next post will be a new xorg.conf for you to try, You want 1280x1024x24bit color right? With only one monitor? OK, coming right up.. Few minutes.
Plus, I dunno what it said about README, but if you want the nVidia readme, I will email it to you.
OK, be right back :)

davidguygc 03-20-2007 11:09 PM

nevermind! got it to work, woot. Thanks yet again for this one.

The last couple things I can think of:

=Mounting files:
Here are the tiffs I have w/ it right now:
-Can't write to ntfs (even though 2.6 said something about it?)
-Does umask=0 mean everybody can access, write, execute, unmount, and mount drives w/o root access?
-Just the painfulness of mounting when I'm not root

=Can I pull the font files from Windows over to Linux and use them?
=That's it? It just may be! I never thought I'd see the day

GrapefruiTgirl 03-20-2007 11:15 PM

Code:

Section "ServerLayout"
    Identifier  "Davidguy"
    Screen 0    "Screen0"  0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
    RgbPath  "/usr/X11R6/lib/X11/rgb"
    FontPath "/usr/X11R6/lib/X11/fonts/misc/:unscaled"
    FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
    FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
    FontPath "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
    FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
EndSection

Section "Module"
    Load  "dbe"
    Load  "extmod"
    Load  "type1"
    Load  "freetype"
    Load  "glx"
    Load  "fbdevhw"
    Load  "record"
EndSection


Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "AutoRepeat" "500 30"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc104"
    Option "XkbLayout" "us"
EndSection

# Adjust mouse driver for your needs, David.
# Mine is IMPS/2, what's yours...
# also,you may want "dev/mouse"
Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "IMPS/2"
    Option "Device" "/dev/psaux"
    Option "ZAxisMapping" "4 5"
EndSection

# Monitor: CHANGE HORIZ and VERT RATES
# FOR YOUR MONITOR!!! OTHERWISE YOU
# MAY DAMAGE YOURS WITH THESE VALUES
Section "Monitor"
    Identifier "Monitor0"
    VendorName "ACME Silly-screen"
    ModelName  "Silliest"
    HorizSync  30.0 - 86.0
    VertRefresh 50.0 - 160.0
    Option "DPMS"
EndSection

# here is my onboard chipset; change this
# to match yours, but it's not used anyway
# in my setup. Maybe delete it?
Section "Device"
    Identifier "i810"
    Driver    "i810"
    VendorName "Intel"
    BoardName  "i854G/PE"
    BusID "PCI:00:10:0"
EndSection

# Your AGP BusID should be the same as this.
# type 'lspci' to verify this.
Section "Device"
    Identifier "Videocard0"
    Driver    "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName  "nVidia 5800-something"
    BusID      "PCI:01:00:0"
EndSection


Section "Screen"
    Identifier "Screen0"
    Device  "Videocard0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option  "XVideo" "On"
    Option  "RenderAccel" "On"
    Option  "HWcursor" "On"
    Option  "AllowGLXWithComposite" "True"
    Option  "DamageEvents" "True"
  SubSection "Display"
    Depth 24
    Modes "1280x1024" "1024x768" "800x600"
  EndSubSection
EndSection

OK, I think I got everything in here correct. Backup your current file, and put this in its place and give it a whirl AFTER you double check the settings here and change the horix and vert refresh rates to match your monitor Specs.

GrapefruiTgirl 03-20-2007 11:18 PM

LOL @ Woot!!
heheh well you may get better performance from this file, up to you..
Umm, NTFS writing *can be done* but is somewhat untested and not really perfect yet. You can search for info on it, but use at your own risk.

As far as I know, wndows TTF fonts and the like can be used, but dont quote me.
umask=0000 means everyone can access it, atleast for NTFS, as far as I know. There are other ways too, but I think that will work.

And there you go!! :)

davidguygc 03-20-2007 11:23 PM

Great, on that note, I've been wanting to go to bed for like an hour, but determination kept me up. Thanks for the help, Ill ttyl

--David

GrapefruiTgirl 03-20-2007 11:24 PM

Right on, have a good'un! And see ya 'round :)


All times are GMT -5. The time now is 09:49 AM.