Re: Nvidia and X
On Wed, Feb 19, 2003 at 07:33:33AM +, Steve Webster wrote: I compiled a new kernel, 2.4.18, for ACPI and nvidia drivers. All went well, eventually. After updating my XF86Config-4 I tried re-starting x-windows. All I got was a black screen, no flashes of color, nothing. I couldn't see any consoles either and had to do a re-boot. I had this problem a long time ago. It turns out, the nvidia drivers do not like to share IRQs with other cards. I had this without ACPI, and when I disabled my sound card(what was using same IRQ) in the BIOS, the problem was fixed. ACPI tends to bunch alot of things onto 1 irq. As nvidia doesn't wish to open the source to their drivers, there is nothing that can be done to fix this, other than trying pci=noacpi on the kernel boot line, or moving your PCI cards to different slots. msg31701/pgp0.pgp Description: PGP signature
Re: cdrecord -scanbus - not working
On Thu, Jan 30, 2003 at 05:12:13PM -0200, Marcelo Chiapparini wrote: On 25.01.2003 19:33 Jonah Sherman wrote: Any ideas why `cdrecord` is not working for me. Debian Woody, kernel 2.4.18bf thanks. [snip] hdb: R/RW 4x4x24, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: 16514064 sectors (8455 MB) w/512KiB Cache, CHS=1092/240/63 hdb: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache Uniform CD-ROM driver Revision: 3.12 /snip You need ide-scsi emulation to use an IDE CDRW drive. Add SCSI(CONFIG_SCSI), SCSI Generic(CONFIG_CHR_DEV_SG), and SCSI CDRom(CONFIG_BLK_DEV_SR), and SCSI IDE Emulation(CONFIG_BLK_DEV_IDESCSI) to your kernel, then add: append=hdb=ide-scsi Is it really necessary the SCSI Generic(CONFIG_CHR_DEV_SG) option above? Yes. Read the IDE-SCSI help notes - In order to do this, say Y here and to SCSI support and SCSI generic support, below. msg27487/pgp0.pgp Description: PGP signature
Re: Nvidia problem ?
On Wed, Jan 29, 2003 at 10:34:06PM +0100, w-cool wrote: I have the following problem, I have transmitted from Slackware to Debian. I have problem with quake 3, I have installed drivers nvidia everything works well but when I start quake I can see the game only in a small part no on a full screan.While trying to change resolution it is rejected ... - Initializing Renderer --- - R_Init - ...loading libGL.so.1: Initializing OpenGL display ...setting mode 4: 800 600 Using XFree86-VidModeExtension Version 2.1 XF86DGA Mouse (Version 2.0) initialized XFree86-VidModeExtension Activated at 1024x768 Using 4/4/4 Color bits, 16 depth, 0 stencil display. Received signal 11, exiting... DOUBLE SIGNAL FAULT: Received signal 11, exiting... Shutdown tty console This is caused by libc2.3, there are 2 things you can do either: 1) ID Software released a Quake3 1.32b point-release to fix this problem, you can get it at ftp://ftp.idsoftware.com/idstuff/quake3/linux 2) Quick hack - Edit the q3 launcher script(/usr/local/bin/quake3), and insert this anywhere before the ./quake3.x86 $* : export __GL_SINGLE_THREADED=y and the problem will be fixed msg27334/pgp0.pgp Description: PGP signature
Re: cdrecord -scanbus - not working
Any ideas why `cdrecord` is not working for me. Debian Woody, kernel 2.4.18bf thanks. [snip] hdb: R/RW 4x4x24, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: 16514064 sectors (8455 MB) w/512KiB Cache, CHS=1092/240/63 hdb: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache Uniform CD-ROM driver Revision: 3.12 /snip You need ide-scsi emulation to use an IDE CDRW drive. Add SCSI(CONFIG_SCSI), SCSI Generic(CONFIG_CHR_DEV_SG), and SCSI CDRom(CONFIG_BLK_DEV_SR), and SCSI IDE Emulation(CONFIG_BLK_DEV_IDESCSI) to your kernel, then add: append=hdb=ide-scsi Your cdrom drive will now be /dev/scd0 instead of /dev/hdb, and cdrecord will work. msg26232/pgp0.pgp Description: PGP signature
Re: how launch Aterm 'as' root
$ aterm -e su On Sat, Jan 11, 2003 at 10:59:02PM +0100, willem wrote: What i want is when logged into X as a normal user...launch Aterm and have it ask for the root password straight away without me having to type 'su' firt after Aterm opens. It's a very small prob...but it's gettin on me nerves;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: restricting wireless access
MAC-based authentication is a joke. All it takes is for someone to sniff traffic, then clone your mac(ifconfig ethX hw ether [...]). The best way IMO to secure a small wireless network is with ipsec. You can do this very easily with freeswan and a good ipsec howto. Just create a encrypted/authenticated tunnel between your wireless machine and your router. On the router, set the policy of the wireless port to require encryption/auth. There are ofcourse other options...such as RADIUS... On Fri, Jan 10, 2003 at 11:56:13PM +0100, martin f krafft wrote: i have a cheap-ass wireless access point which doesn't even do MAC-based authentication, and neither can I get WEP64 to work between it (Addtron AWS-110) and the Orinoco Silver card. I would like to have wireless in my appartment, but I need to prevent folks on the street from linking into the network. The question is how. I want to prevent them from using my internet connection just as much as accessing local computers behind the firewall. Is there a tools that will send TCP resets to anything coming from an unknown MAC address? this isn't 100% secure, but it's better than nothing. Or is there a tool that uses a client program to establish the identity of the host (like they have in some internet cafes to prevent you from using the cables for laptops, even if you change the MAC), and if someone connects without the client program, then s/he is TCP reset for every packet sent? or is there a better solution? maybe someone can help me get WEP to work... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Limiting SU
On Tue, Dec 31, 2002 at 05:49:08AM -0500, Ludwig wrote: On Tue, 2002-12-31 at 05:34, Andrew Pritchard wrote: Is there a way of limiting who and SU to root? As root, chmod go-x /usr/bin/who This won't do anything. $ last -f /var/run/utmp will do the same thing as who What you need to do is chmod 600 /var/run/utmp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
