Adam Bower wrote:
I am usually on most evenings from about 8ish but if i don't reply immediatly don't
think I
won't see anything written there.
Oops, do you mean you've been reading all those terrible things I've been saying about you behind your back then? ;-) Jen.
On Monday, December 09, 2002 1:29 PM Jenny_Hopkins wrote;
Adam Bower wrote:
I am usually on most evenings from about 8ish but if i don't reply
immediatly don't think I won't see anything written there.
Oops, do you mean you've been reading all those terrible things I've been saying about you behind your back then? ;-) Jen.
Oh! Now I understand why we had the recent 'code of conduct' posting!! :oD
Keith ____________ MARRIAGE, n. The state or condition of a community consisting of a master, a mistress and two slaves, making in all, two. Ambrose Bierce - The Devil's Dictionary
HI everyone again. I had been trying to install Debian 3.0 on my new machine. Having succeeded on the old one I thought there would have been no problems at all installing it again. However this time I do have a major problem. After running dselect the installer asks for the first cdrom and then starts reading it but instead of installing from it fetches a few updated packages from http apt sources (that I added) and security updates. After that is done (about 30mins) it starts reading the cd again and throws an error:
status: 0x31 end_request: I/O error dev 16:00(hdc), sector 1173632 command error 0x54
and then keeps repeating the last four lines indefinetely until I reboot the machine and have to start all over again from base system configuration only to find out the same error again. Pretty frustrating. Does that mean the CD is somehow corrupted? The cdrom drive works fine, at least under Windows.. anyone can help? Thank you very much. This is very unfortunate, as it seems I am unable to install Debian again.. :(
Francesco.
I recently had a very similar problem. Under the guidance of Steve McIntyre, I went through the following sequence of attempted solutions, in increasing order of drastic-ness. Sadly, it was the last and most drastic one that worked.
1 Use a different set of CDs that were written more slowly. 2 Use a single DVD-ROM instead of the CD set. 3 Replace the IDE cable to the CD/DVD-ROM drive. 4 Replace the CD/DVD-ROM drive.
Oops. There I go advising someone to mess around inside their computer again. Please, if possible, make sure you back up all your valuable data before doing this.
Hi, solved the problem. For some strange reason commenting out the network apt sources in the sources.list file made the installer read packages from the cdrom again and not complaining anymore, I figured updates could be run later after uncommmenting those network sources. Now I have another problem, X window system does not start up (but it did start once after installation, using xdm) because of some IO error, it says it fails to lad some module, namely APM I think. Any one knows any possible solution? (Tried dpkg-reconfigure -xserver-xfree86 ... but it did not solve the problem.. uhm.. I seem to be messing with this thing more than I ought to.. but I want it oh so much to get working..) Thanks for any help/suggestions.
Francesco
On Mon, 16 Dec 2002 21:24:53 +0000 (GMT), "Dan Hatton" dan.hatton@btinternet.com said:
I recently had a very similar problem. Under the guidance of Steve McIntyre, I went through the following sequence of attempted solutions, in increasing order of drastic-ness. Sadly, it was the last and most drastic one that worked.
1 Use a different set of CDs that were written more slowly. 2 Use a single DVD-ROM instead of the CD set. 3 Replace the IDE cable to the CD/DVD-ROM drive. 4 Replace the CD/DVD-ROM drive.
Oops. There I go advising someone to mess around inside their computer again. Please, if possible, make sure you back up all your valuable data before doing this.
-- Dan Hatton http://www.bib.hatton.btinternet.co.uk/dan/
On Mon, 16 Dec 2002 franardia@the-fastest.net wrote:
HI everyone again. I had been trying to install Debian 3.0 on my new machine. Having succeeded on the old one I thought there would have been no problems at all installing it again. However this time I do have a major problem. After running dselect the installer asks for the first cdrom and then starts reading it but instead of installing from it fetches a few updated packages from http apt sources (that I added) and security updates. After that is done (about 30mins) it starts reading the cd again and throws an error:
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
franardia@the-fastest.net franardia@the-fastest.net wrote:
For some strange reason commenting out the network apt sources in the sources.list file made the installer read packages from the cdrom again and not complaining anymore, I figured updates could be run later after uncommmenting those network sources.
It might not be that strange a reason. From the sources.list manual page:
The source list is designed to support any number of active sources and a variety of source media. The file lists one source per line, with the most preferred source listed first. [...]
Did you add the network sources higher up the file than the cdrom ones?
Now I have another problem, X window system does not start up (but it did start once after installation, using xdm) because of some IO error, it says it fails to lad some module, namely APM I think. Any one knows any possible solution?
Wow, that's a strange one. Two possible attacks come to my mind instantly: make sure that APM is enabled in the kernel ("apm=on", without quotes, on the boot line); or purge xserver-xfree86, make sure that discover, mdetect, read-edid etc are installed and reinstall xserver-xfree86, but that's drastic.
If you want more ideas, you'll need to send the X server startup messages (especially errors) and probably the graphics card part of /etc/X11/XF86Config-4
Hands up all those who think Debian 3.0's X server installation process isn't quite as polished as it could be ;-) Thank $DEITY you only normally have to do it once.
On Wed, Dec 18, 2002 at 10:36:25AM +0000, MJ Ray wrote:
franardia@the-fastest.net franardia@the-fastest.net wrote:
Now I have another problem, X window system does not start up (but it did start once after installation, using xdm) because of some IO error, it says it fails to lad some module, namely APM I think. Any one knows any possible solution?
Wow, that's a strange one. Two possible attacks come to my mind instantly: make sure that APM is enabled in the kernel ("apm=on", without quotes, on the boot line); or purge xserver-xfree86, make sure that discover, mdetect, read-edid etc are installed and reinstall xserver-xfree86, but that's drastic.
the APM thing is usually a red herring, it will come up in the logs with a WW (warning) line as its not supported but it won't make a functional difference (not in my experience anyhow) to the actual X server drawing pretty pictures on you screen. Try looking at the very end of the file for what the problem is or warnings there.
Adam
Hi, thanks for your help with apt sources, that is not a problem now. X server does not start at system boot (although it did, twice, before this problem appeared). If I try to launch $startx from the shell it ends up with this error line after a few II and the WW failed to load apm:
XIO fatal IO error 104 (connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
I suspect this has something to do with my graphic card. I seem to recall that $lspci should give the PCI buses and the HW on them, it lists my card as well. In dpkg-reconfigure -xserver-xfree86 I listed it on the AGP bus (where it physically is). Is it the case some inconsistencies are in the system about HW configuration and actual status? As usual many thanks for your help. (Thanks to Mark and "quinophex" who respond always so unbelievably quickly.. :D )
Francesco
On Wed, 18 Dec 2002 10:36:25 GMT, "MJ Ray" markj+0111@cloaked.freeserve.co.uk said:
Now I have another problem, X window system does not start up (but it did start once after installation, using xdm) because of some IO error, it says it fails to lad some module, namely APM I think. Any one knows any possible solution?
Wow, that's a strange one. Two possible attacks come to my mind instantly: make sure that APM is enabled in the kernel ("apm=on", without quotes, on the boot line); or purge xserver-xfree86, make sure that discover, mdetect, read-edid etc are installed and reinstall xserver-xfree86, but that's drastic.
If you want more ideas, you'll need to send the X server startup messages (especially errors) and probably the graphics card part of /etc/X11/XF86Config-4
Hands up all those who think Debian 3.0's X server installation process isn't quite as polished as it could be ;-) Thank $DEITY you only normally have to do it once. -- MJR http://mjr.towers.org.uk/ IM: slef@jabber.at This is my home web site. This for Jabber Messaging.
How's my writing? Let me know via any of my contact details.
franardia@the-fastest.net franardia@the-fastest.net wrote: [...]
ends up with this error line after a few II and the WW failed to load apm:
XIO fatal IO error 104 (connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
I think that's startx complaining that the X server has died, rather than what actually killed the X server. What are the lines immediately before that? Feel free to email me the full log offlist and I'll summarise the interesting bits to the list.
In dpkg-reconfigure -xserver-xfree86 I listed it on the AGP bus (where it physically is). Is it the case some inconsistencies are in the system about HW configuration and actual status?
It *might* be. Another trick you can try is telling the config screen that you only have a standard VESA card. That should get you a working X, at least.
As usual many thanks for your help.
That's OK. As a favour in return, can you trim quoted material and reply beneath it please? Makes it a lot easier for us to follow. Thanks.
On Thu, Dec 19, 2002 at 02:37:21AM +0000, franardia@the-fastest.net wrote:
I suspect this has something to do with my graphic card. I seem to recall that $lspci should give the PCI buses and the HW on them, it lists my card as well. In dpkg-reconfigure -xserver-xfree86 I listed it on the AGP bus (where it physically is). Is it the case some inconsistencies are in the system about HW configuration and actual status?
The agp bus is just a seperate PCI bus (albeit one capable of faster data transfers etc.), so it shouldn't be a whole lot of problem about where the system "sees" it. Anyhow if you want to Cc: me on any email to Mark with the servers output I will try and help out too.
Adam
-
Adam Bower -
Dan Hatton -
franardia＠the-fastest.net -
Jenny_Hopkins＠toby-churchill.com -
Keith Watson -
MJ Ray -
MJ Ray