Thanks for your help. Now I've got a bunch of stuff to do. I'll let you guys know how it turns out.
Ricky Munoz On 3/27/03 10:05 AM, "Dean Michael Berris" <[EMAIL PROTECTED]> wrote: > On Thu, 2003-03-27 at 06:52, Muddy Banks wrote: >> >> Anyway, dselect is now asking me if I want to download an additional 107MB >> of upgraded files. And little old me with my dial-up connection? Uh no >> thanks. >> > > methinks you're better off installing woody from the CD set. i know Mr. > Jijo Sevilla has the Debian 7 CD set and other distro's that he's > selling, so you could go check them out. > >> >> There, I did "strace XF86Setup" as root and I got this on the last four >> lines: >> >> read(4, "c)\n\nName S3 86C280 (generic)\nSEE"...,4096) = 4096 >> brk(0x80a6000) = 0x80a6000 >> --- SIGSEV (Segmantation fault) --- >> +++ killed by SIGSEV +++ >> >> Does that make any sense? >> > > well, to me it doesn't. you could try asking someone from the XFree86 > project dev team something about it, but i have a quick guess on this. > > notice the line that has "c)\n\nName S3 86C280 (generic)\bSEE"...,4096 > -- is a system call to read. you can do a 'man read' if you haven't > encountered this UNIX I/O system call yet to find out what it does. but > basically it reads from a file descriptor defined as 4 -- the default > file descriptors open to a file are from 1-3 (stdin, stdout, stderr, in > an order i am not sure about) > > now the next line with brk is the culprit. > > from doing a man brk: > > ... > brk sets the end of the data segment to the value speci- > fied by end_data_segment, when that value is reasonable, > the system does have enough memory and the process does > not exceed its max data size (see setrlimit(2)). > ... > On success, brk returns zero,... > ... > > but in your case, it didn't return zero -- it returned a hex number > other than zero. > > the error that could be present here has to do with the call to brk and > setting the end of the segment to an address where another program is > already at. this causes a segmentation fault because the part of memry > (segment) that you are trying to access is already out of the bounds of > the running process. > > in short, the process aint supposed to access a part of memery that it's > trying to access. this is a protection feature of linux, which you could > otherwise do without in windows -- that's why there are a lot of TSR and > memory resident applications that alter the operation of current > programs called viruses (or virii IIRC). > > now, WTF could you do about this? > > first off, you could reconfigure your x server using dpkg-reconfigure. > this will invoke dialogs (either ncurses, GNU Gettext, or GNOME UI > based) that will allow you to tweak the configuration from there. > > -OR- > > you could edit the configuration files by hand. > > -OR STILL- > > use the other available tools for configuring your X server. you can use > xf86config which will ask you about your hardware, or xf86cfg which will > try to automajically detect the settings for your hardware and create a > config file named ~/XF86Config.new containing these settings upon exit. > xf86cfg invokes a graphical UI once it detects the right settings for > your hardware, from which you may be able to tweak the settings > graphically. > > HTH. =) > >> BTW I did "man strace" >> > > good for you. =) _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
