Re: Problems after upgrade to Jessie

Hi there Rob van der Putten wrote: How do I get cern_meta.load? Is compiling Apache myself the only option? And default mime type is no longer supported. Which is really annoying if you want to read compressed text files with a web browser. Regards, Rob

Problems after upgrade to Jessie

Hi there I run into the following problems after upgrading to Jessie; - logresolve segfaults. - Apache misses cern_meta.load - console-kit-daemon complains; console-kit-daemon[4676]: GLib-CRITICAL: Source ID 154 was not found when attempting to remove it How do I get cern_meta.load? Is compil

Various problems after upgrade to Jessie

So I had several systems running Wheezy, since Jessie went GA I've upgraded most of them. One got into an unbootable state and I haven't had a chance to try with a rescue disk yet. The rest are all switched over, "apt-get upgrade" says nothing remains to be done, but there are some remaining

Re: sound problems after upgrade

On Thursday, December 12, 2013 11:30:44 PM Kailash Kalyani wrote: > On Thursday 12 December 2013 09:12 PM, Christopher Judd wrote: > > Hi, > > > > I have a testing box, kernel 3.2.0-3-amd64, using KDE. After an upgrade > > earlier this week, I am having problems with sound. The system is an MSI >

Re: sound problems after upgrade

On Thursday 12 December 2013 09:12 PM, Christopher Judd wrote: Hi, I have a testing box, kernel 3.2.0-3-amd64, using KDE. After an upgrade earlier this week, I am having problems with sound. The system is an MSI 760GM-P23 motherboard with onboard RealTek ALC887, and sound has always worked fine

sound problems after upgrade

Hi, I have a testing box, kernel 3.2.0-3-amd64, using KDE. After an upgrade earlier this week, I am having problems with sound. The system is an MSI 760GM-P23 motherboard with onboard RealTek ALC887, and sound has always worked fine previously. The problem is that there is no

Re: Software RAID on external USB disk: boot problems after upgrade to squeeze

On Wed, Feb 23, 2011 at 8:11 AM, Panayiotis Karabassis wrote: > On 02/23/2011 03:10 PM, Tom H wrote: >> On Wed, Feb 23, 2011 at 8:01 AM, Panayiotis Karabassis >>  wrote: >>> >>> BTW, could someone explain the difference between >>> GRUB_CMDLINE_LINUX_DEFAULT >>> and GRUB_CMDLINE_LINUX in /etc/defa

Re: Software RAID on external USB disk: boot problems after upgrade to squeeze

On 02/23/2011 03:10 PM, Tom H wrote: On Wed, Feb 23, 2011 at 8:01 AM, Panayiotis Karabassis wrote: BTW, could someone explain the difference between GRUB_CMDLINE_LINUX_DEFAULT and GRUB_CMDLINE_LINUX in /etc/default/grub? For every vmlinuz... in /boot, GRUB_CMDLINE_LINUX_DEFAULT appli

Re: Software RAID on external USB disk: boot problems after upgrade to squeeze

On Wed, Feb 23, 2011 at 8:01 AM, Panayiotis Karabassis wrote: > > BTW, could someone explain the difference between GRUB_CMDLINE_LINUX_DEFAULT > and GRUB_CMDLINE_LINUX in /etc/default/grub? For every vmlinuz... in /boot, GRUB_CMDLINE_LINUX_DEFAULT applies to the runlevel 2 entry and GRUB_CMDLINE_

Re: Software RAID on external USB disk: boot problems after upgrade to squeeze

On 02/23/2011 02:22 PM, martin f krafft wrote: also sprach Panayiotis Karabassis [2011.02.23.1029 +0100]: I had solved this in lenny by using the following /usr/share/initramfs-tools/scripts/local-top/mdadm script: Set rootdelay=30 on the kernel command line. Your solution seem

Re: Software RAID on external USB disk: boot problems after upgrade to squeeze

also sprach Panayiotis Karabassis [2011.02.23.1029 +0100]: > I had solved this in lenny by using the following > /usr/share/initramfs-tools/scripts/local-top/mdadm script: Set rootdelay=30 on the kernel command line. > My solution is broken after the upgrade to squeeze and the problem > has regr

Software RAID on external USB disk: boot problems after upgrade to squeeze

Hi! To simplify things a little: I have an external USB disk (/dev/sdc1) that is part of an MD array (/dev/md0). During boot, I experienced the following problem: /dev/md0 was assembled with only 1 drive out of 2 (the internal one). This was due to /dev/sdc1 taking some time to be detected,

Re: nvidia problems after upgrade

> first, otherwise you may have todo: > #m-a -t clean,a-i nvidia-kernel-source > again! ;) I don't know about now but recently if you didn't do apt-get update and dist-upgrade after the compile you wouldn't get the glx updated drivers, maybe that step has been eliminated. Debian uncertain, my fa

Re: nvidia problems after upgrade

On Wed, Sep 16, 2009 at 08:35:55PM -0400, Charles Kroeger wrote: > > It is? How do you do that? > > Make sure you have installed: > > nvidia-glx > nvidia-glx-dev > > nvidia-kernel-source > > compile the source with the following command: > > #m-a -t clean,a-i nvidia-kernel-source > > enjoy th

Re: nvidia problems after upgrade

On 2009-09-17 21:05:15 -0400, Charles Kroeger wrote: > > the correct instructions (but I haven't tried yet). And I suppose > > that these are official instructions (as being on debian.org). > > Try these instructions: > > http://tinyplanet.ca/~lsorense/debian/debian-nvidia-dri-howto.html They w

Re: nvidia problems after upgrade

Paul Cartwright wrote: > Every time I boot up & GDM doesn't start, my network is broken too. Is it possible that you've got something within your GUI environment that configures the network? (Network Manager springs to mind. Ugh.) Chris -- To UNSUBSCRIBE, email to debian-user-requ...@lists.de

Re: nvidia problems after upgrade

On Fri September 18 2009, Jaime Tarrant wrote: > > >> Rebuilding and reinstalling the nvidia driver is almost always > > >> required after kernel or OpenGL library upgrades. > > > > marc wrote: > > > It is? How do you do that? > > > > Google for sgfxi and use that. > > Chris > >   > +1 for sgfxi.

Re: nvidia problems after upgrade

* Chris Davies (chris-use...@roaima.co.uk) wrote: > >> Rebuilding and reinstalling the nvidia driver is almost always required > >> after kernel or OpenGL library upgrades. > > marc wrote: > > It is? How do you do that? > > Google for sgfxi and use that. > Chris +1 for sgfxi. It works a treat

Re: nvidia problems after upgrade

> the correct instructions (but I haven't tried yet). And I suppose > that these are official instructions (as being on debian.org). Try these instructions: http://tinyplanet.ca/~lsorense/debian/debian-nvidia-dri-howto.html -- CK -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.

Re: nvidia problems after upgrade

>> Rebuilding and reinstalling the nvidia driver is almost always required >> after kernel or OpenGL library upgrades. marc wrote: > It is? How do you do that? Google for sgfxi and use that. Chris -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscrib

Re: nvidia problems after upgrade

On 2009-09-17 18:32 +0200, Vincent Lefevre wrote: > It seems that http://wiki.debian.org/NvidiaGraphicsDrivers contains > the correct instructions (but I haven't tried yet). And I suppose > that these are official instructions (as being on debian.org). The wiki is open for anyone, so content foun

Re: nvidia problems after upgrade

It seems that http://wiki.debian.org/NvidiaGraphicsDrivers contains the correct instructions (but I haven't tried yet). And I suppose that these are official instructions (as being on debian.org). -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Re: nvidia problems after upgrade

On 2009-09-16 17:08:58 -0400, Wayne Topa wrote: > marc wrote: > >It is? How do you do that? > > Another 'I can't be bothered to ask Google' user. > > These instructions seem to be buggy: The nvidia-* packages don't

Re: nvidia problems after upgrade

Wayne Topa wrote: > Another 'I can't be bothered to ask Google' user. > > > > Would be a start. -- Best, Marc "Change requires small steps." -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org

Re: nvidia problems after upgrade

> It is? How do you do that? Make sure you have installed: nvidia-glx nvidia-glx-dev nvidia-kernel-source compile the source with the following command: #m-a -t clean,a-i nvidia-kernel-source enjoy the show then: apt-get update apt-get dist-upgrade see what happens. -- CK "How we as co

Re: nvidia problems after upgrade

marc wrote: Kevin Ross wrote: From: Christopher Judd [mailto:j...@wadsworth.org] Sent: Wednesday, September 16, 2009 12:02 PM Hi, After some recent upgrades, I can no longer start the xserver using the nvidia driver. I get the following errors: -Chris Rebuilding and reinstalling the

RE: nvidia problems after upgrade

Kevin Ross wrote: >> From: Christopher Judd [mailto:j...@wadsworth.org] >> Sent: Wednesday, September 16, 2009 12:02 PM >> >> Hi, >> >> After some recent upgrades, I can no longer start the xserver >> using >> the nvidia driver. I get the following errors: >> >> (II) LoadModule: "nvidia"

RE: nvidia problems after upgrade

> From: Christopher Judd [mailto:j...@wadsworth.org] > Sent: Wednesday, September 16, 2009 12:02 PM > > Hi, > > After some recent upgrades, I can no longer start the xserver > using > the nvidia driver. I get the following errors: > > (II) LoadModule: "nvidia" > (WW) Warning, couldn't open

Re: nvidia problems after upgrade

On Wed, Sep 16, 2009 at 15:01:57 -0400, Christopher Judd wrote: > Hi, > > After some recent upgrades, I can no longer start the xserver using > the nvidia driver. I get the following errors: > > (II) LoadModule: "nvidia" > (WW) Warning, couldn't open module nvidia > (II) UnloadModule: "nvi

Re: nvidia problems after upgrade

On Wed, 16 Sep 2009 15:01:57 -0400 Christopher Judd wrote: Hello Christopher, > Any ideas what has happened? Thanks. Did this involve a kernel upgrade? Seems like classic kernel/driver mismatch to my less than expert eye. -- Regards _ / ) "The blindingly obvious is

nvidia problems after upgrade

Hi, After some recent upgrades, I can no longer start the xserver using the nvidia driver. I get the following errors: (II) LoadModule: "nvidia" (WW) Warning, couldn't open module nvidia (II) UnloadModule: "nvidia" (EE) Failed to load module "nvidia" (module does not exist, 0) (EE) No driv

Re: DNS lookup problems after upgrade from Etch to Lenny

Stackpole, Chris wrote: > Well I can't seem to find and fix this problem. So I guess my two > options are: 1) rebuild the system using Lenny 2) Install a DNS > caching utility. I would be inclined to try tracing with tcpdump and wireshark and trying to determine what names are being looked up. I

RE: Re: DNS lookup problems after upgrade from Etch to Lenny

Hi, Il giorno gio, 18/06/2009 alle 07.13 -0500, Stackpole, Chris ha scritto: [.] > I still have not been able to figure out what caused the problem, > however, I did get the DBNDNS caching to work. This has at least gotten > the network guys off my back, but it has added an extra layer for me t

RE: Re: DNS lookup problems after upgrade from Etch to Lenny

> From: news [mailto:n...@ger.gmane.org] On Behalf Of Jeffrey Cao > Sent: Thursday, June 18, 2009 2:43 AM > Subject: Re: DNS lookup problems after upgrade from Etch to Lenny > > On 2009-06-16, Stackpole, Chris wrote: > >> From: Adrian Levi [mailto:adrian.l...@gmail.com]

Re: DNS lookup problems after upgrade from Etch to Lenny

On 2009-06-16, Stackpole, Chris wrote: >> From: Adrian Levi [mailto:adrian.l...@gmail.com] >> Sent: Tuesday, June 16, 2009 1:19 AM >> Subject: Re: DNS lookup problems after upgrade from Etch to Lenny >> >> >> didn't have it before and on another syst

Re: DNS lookup problems after upgrade from Etch to Lenny

On Tue, Jun 16, 2009 at 10:24:05AM -0500, Stackpole, Chris wrote: > >From: Stackpole, Chris [mailto:cstackp...@barbnet.com] > >Sent: Monday, June 15, 2009 4:36 PM > >Subject: RE: DNS lookup problems after upgrade from Etch to Lenny > > > >> From: Stackpole, Chr

RE: DNS lookup problems after upgrade from Etch to Lenny

>From: Stackpole, Chris [mailto:cstackp...@barbnet.com] >Sent: Monday, June 15, 2009 4:36 PM >Subject: RE: DNS lookup problems after upgrade from Etch to Lenny > >> From: Stackpole, Chris [mailto:cstackp...@barbnet.com] >> Sent: Monday, June 15, 2009 4:30 PM >> Subj

RE: DNS lookup problems after upgrade from Etch to Lenny

> From: Adrian Levi [mailto:adrian.l...@gmail.com] > Sent: Tuesday, June 16, 2009 1:19 AM > Subject: Re: DNS lookup problems after upgrade from Etch to Lenny > > >> didn't have it before and on another system running a fresh build of > >> Lenny running the exa

Re: DNS lookup problems after upgrade from Etch to Lenny

>> didn't have it before and on another system running a fresh build of >> Lenny running the exact same software handling a similar load and its >> DNS ask rate is just as low as it was on this system running Etch. >> >> I am at a loss. I appreciate any help people can give. Silly question, did yo

RE: DNS lookup problems after upgrade from Etch to Lenny

> From: Stackpole, Chris [mailto:cstackp...@barbnet.com] > Sent: Monday, June 15, 2009 4:30 PM > Subject: DNS lookup problems after upgrade from Etch to Lenny > > Hey guys, > > I have been trying my best to figure this out recently but not having > much luck. I am hopi

DNS lookup problems after upgrade from Etch to Lenny

Hey guys, I have been trying my best to figure this out recently but not having much luck. I am hoping someone here might be able to help. We had an Etch box that had been running great for almost 2 years. When we decided that we really should upgrade to Lenny, the box had over 300 days of uptime

Re: nvidia problems after upgrade

Steven Demetrius wrote: Please list the full contents of the /etc/X11/xorg.conf file and the kernel version you are using. Ok, I've attached my xorg.conf file to this message, and my kernel version is 2.6.26-1-686 (as reported by "uname -r"). You can also get xorg to generate a xorg.conf file

Re: nvidia problems after upgrade

Aidan Gauland wrote: Hello, I just upgraded to lenny without any problems, except for one: I'm using the vesa xorg driver, because using the free nv driver causes the display to freeze after a few minutes of use (I can move the mouse, but I can't even switch to a virtual console). I was usi

Re: nvidia problems after upgrade

Hello, I just upgraded to lenny without any problems, except for one: I'm using the vesa xorg driver, because using the free nv driver causes the display to freeze after a few minutes of use (I can move the mouse, but I can't even switch to a virtual console). I was using the non-free nvi

nvidia problems after upgrade

Hello, I just upgraded to lenny without any problems, except for one: I'm using the vesa xorg driver, because using the free nv driver causes the display to freeze after a few minutes of use (I can move the mouse, but I can't even switch to a virtual console). I was using the non-free nvidia

Re: Bridging problems after Upgrade to Lenny

On Mon, Feb 23, 2009 at 01:25:30PM +0100, Udo Hortian wrote: > Hello all, > > I subscribed newly to this list, since I got an bridging problem > after an upgrade from Debian etch to Debian lenny (before > everything worked fine). > > The situation is as follows: > > # brctl show > bridge name

Bridging problems after Upgrade to Lenny

Hello all, I subscribed newly to this list, since I got an bridging problem after an upgrade from Debian etch to Debian lenny (before everything worked fine). The situation is as follows: # brctl show bridge name bridge id STP enabled interfaces br0 8000.0003477

Re: problems after upgrade

[Top posted, because reply is a mess.] i) You're still posting in HTML. Please stop. See above. ii) Your network works. ping finds debian.org fine. iii) What's "emacs -nw somefile" say? iv) What was the result of "dpkg-reconfigure xserver-xorg"? v) "dpkg-reconfigure xse

Re: problems after upgrade

"s. keeling" <[EMAIL PROTECTED]> wrote: Fred J. <[EMAIL PROTECTED]>:Please, don't post HTML. Plain ASCII text, thanks.>I am running debian/testing with kernel 2.6.15>In my /etc/sources.list I have basically 2 lines, >Deb http://http.us.debian.org/debian/ testing main contrib non-free>

Re: problems after upgrade

Fred J. <[EMAIL PROTECTED]>: Please, don't post HTML. Plain ASCII text, thanks. >I am running debian/testing with kernel 2.6.15 >In my /etc/sources.list I have basically 2 lines, >Deb http://http.us.debian.org/debian/ testing main contrib non-free >Deb http://secure-testing.debi

Re: problems after upgrade

Fred J. wrote: > Hi > I am running debian/testing with kernel 2.6.15 > In my /etc/sources.list I have basically 2 lines, > Deb http://http.us.debian.org/debian/ testing main contrib non-free > Deb http://secure-testing.debian.net/debian-secure-testing/ > testing/security-updates main contrib non-fr

problems after upgrade

Hi I am running debian/testing with kernel 2.6.15 In my /etc/sources.list I have basically 2 lines, Deb http://http.us.debian.org/debian/ testing main contrib non-free Deb http://secure-testing.debian.net/debian-secure-testing/ testing/security-updates main contrib non-free   The box ha

Acpi problems after upgrade to 2.6.15: computer doesn't poweroff anymore.

Hello everybody, I have recently updated my kernel building a 2.6.15 one from debian sources, and I ran into troubles. First problem I had was that battery was not anymore detected (/proc/acpi/battery was empty). I googled around and I found a solution adding "ec_burst=1" to boot parameters. The se

Re: Problems after upgrade to udev - can't start X

Hello Richard L. Halpert (<[EMAIL PROTECTED]>) wrote: > I recently upgraded from sarge to etch, and I ran into a problem that > seems to be related to udev. During the upgrade, hotplug was removed > and udev was installed. Then you also read the message that told you to purge the hotplug packa

Problems after upgrade to udev - can't start X

Hi all, I recently upgraded from sarge to etch, and I ran into a problem that seems to be related to udev.  During the upgrade, hotplug was removed and udev was installed.  Afterwards, I received the following error message when trying to log in (via gdm): Error creating the child process for this

problems after upgrade

Hi, after running dist-upgrade couple of days ago I get the error message when trying to set a new background picture with "fbsetbg": fbsetbg: Something went wrong while setting the wallpaper. Run 'display -geometry 1280x1024+0+0 -window root /home/chris/.fluxbox/backgrounds//picture.jpg' from an

Re: uw-imap and authentication problems after upgrade to sarge

--- Ritesh Raj Sarraf <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Mon, 19 Apr 2004 16:13:46 -0700 (PDT) > Pete RedHair <[EMAIL PROTECTED]> wrote: > > > I'm using uw-imapd on sarge and where i previously got a perfectly > > running system now i can't login

Re: uw-imap and authentication problems after upgrade to sarge

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 19 Apr 2004 16:13:46 -0700 (PDT) Pete RedHair <[EMAIL PROTECTED]> wrote: > I'm using uw-imapd on sarge and where i previously got a perfectly > running system now i can't login to my imap server. > > Here's what i get from syslog: > (did a cl

mouse wheel problems after upgrade to 2.6.5 kernel

it looks that after update to 2.6.5 kernel (debian source package) the mouse wheel does not work very well. *It doesn't seem to be X related* Here's the most basic/simple situation/symptoms: I stop X, read bytes from /dev/psaux (c program, using open and read). for each mouse action there

uw-imap and authentication problems after upgrade to sarge

I hope i'm not goofing on this one but after upgrading to sarge i got a lot of packages with broken configs, squid and imap are two of them. I'm using uw-imapd on sarge and where i previously got a perfectly running system now i can't login to my imap server. Here's what i get from syslog: (did a

Problems after upgrade to woody

Hi, I finally upgraded to woody and mostly everything went smoothly or I could solve them myself. But two problems I couldn't figure out myself: 1) I have my xserver up and running. But dpkg tells me that it isn't able to configure a bunch (12) of xservers. Just one server as an example: Settin

Re: DHCP networking problems after upgrade to woody

I wrote: > It's a Eicon Diva 2430. I found this on it: > > http://www.eicon.com/pubs/diva_2430/index.htm > > with lots of links for explanations and help. > > It says the modem has the IP 192.168.1.1 and that it can be > configured by pointing a web browser at that address. Can't wait > to

Re: DHCP networking problems after upgrade to woody

Nathan E Norman wrote: > > > > I got my ADSL line last night, ran '/etc/init.d/networking start' > > > > and proceeded to download 240MB in 28 minutes (!), and upgraded > > > > my Progeny to woody (I didn't change the kernel, running 2.2.18). > > Ah, this is the part I missed ... I didn't reali

Re: DHCP networking problems after upgrade to woody

I wrote: > > I got my ADSL line last night, ran '/etc/init.d/networking start' > > and proceeded to download 240MB in 28 minutes (!), and upgraded > > my Progeny to woody (I didn't change the kernel, running 2.2.18). > > > > Now the ADSL network won't work anymore. > > Running either pump or dh

Re: DHCP networking problems after upgrade to woody

On Tue, Oct 02, 2001 at 09:41:07PM -0400, Peter S Galbraith wrote: > I got my ADSL line last night, ran '/etc/init.d/networking start' > and proceeded to download 240MB in 28 minutes (!), and upgraded > my Progeny to woody (I didn't change the kernel, running 2.2.18). > > Now the ADSL network won

DHCP networking problems after upgrade to woody

I got my ADSL line last night, ran '/etc/init.d/networking start' and proceeded to download 240MB in 28 minutes (!), and upgraded my Progeny to woody (I didn't change the kernel, running 2.2.18). Now the ADSL network won't work anymore. Running either pump or dhclient now gives me the same IP: e

AW: X problems after upgrade

lled X-Server. Good luck and greetings Christoph Walther mailto:[EMAIL PROTECTED] -Ursprüngliche Nachricht- Von: Sven Gaerner [mailto:[EMAIL PROTECTED] Gesendet am: Dienstag, 27. Februar 2001 14:20 An: debian-user@lists.debian.org Betreff: Re: X problems after upgrade Hi, to solv

Re: X problems after upgrade

Quoting Sven Gaerner ([EMAIL PROTECTED]): > to solve the problem of the error message > > X: cannot stat /etc/X11/X (No such file or directory), aborting. > giving up. > xinit: Connection refused (errno 111): unable to connect to X server > xinit: No such process (errno 3): Server error. > >

Re: X problems after upgrade

Hi, to solve the problem of the error message X: cannot stat /etc/X11/X (No such file or directory), aborting. giving up. xinit: Connection refused (errno 111): unable to connect to X server xinit: No such process (errno 3): Server error. create a link to XFree86 in /etc/X11. $ cd /etc/X11

Re: X problems after upgrade

Nathan wrote: > I recently upgraded to 4.0.2 from 3.3.6 using dselect so all dependencies > should be OK and now X won't start at all. I ran xf86config and created the > new XF86Config-4 file in /etc/X11 and every time I try to run X, it gives me > this error msg: > > X: cannot stat /etc/X11/X (No

Re: X problems after upgrade

On Sun, 25 Feb 2001, Nathan wrote: ->I recently upgraded to 4.0.2 from 3.3.6 using dselect so all dependencies ->should be OK and now X won't start at all. I ran xf86config and created the ->new XF86Config-4 file in /etc/X11 and every time I try to run X, it gives me ->this error msg: -> ->X: can

Re: X problems after upgrade

See Mirek Kwasniak's message of 18 Feb. Weird: I did about the same upgrade, but never had this problem. Had a number of others. I did apt-get dist-upgrade; maybe it's because dselect brings in different packages. On Sun, Feb 25, 2001 at 04:17:47PM +1100, Nathan wrote: > I recently upgraded to

X problems after upgrade

I recently upgraded to 4.0.2 from 3.3.6 using dselect so all dependencies should be OK and now X won't start at all. I ran xf86config and created the new XF86Config-4 file in /etc/X11 and every time I try to run X, it gives me this error msg: X: cannot stat /etc/X11/X (No such file or directory),

Re: problems after upgrade to progeny

Erik Steffl <[EMAIL PROTECTED]> writes: > Andre Berger wrote: > > > > I've just upgraded my potato box to progeny. There's a problem with > > xserver-xfree86 (4.0.1-12), the mga driver, and geometry. Vertical > > window borders are partly gibberish, like waves, and the text of lines > > between t

Re: problems after upgrade to progeny

Andre Berger wrote: > > I've just upgraded my potato box to progeny. There's a problem with > xserver-xfree86 (4.0.1-12), the mga driver, and geometry. Vertical > window borders are partly gibberish, like waves, and the text of lines > between these parts is slanted to the right or left. This may

problems after upgrade to progeny

I've just upgraded my potato box to progeny. There's a problem with xserver-xfree86 (4.0.1-12), the mga driver, and geometry. Vertical window borders are partly gibberish, like waves, and the text of lines between these parts is slanted to the right or left. This may sound poetic, but makes things

X problems after upgrade to frozen!

I've noted a few messages from people with X problems after upgrading to potato. I'm having one also. I have upgraded from slink to potato (frozen) via apt-get and dselect after a lot of effort. All files are current according to apt-get. But I cannot run an X-terminal, with either xdm or wdm.

2 problems after upgrade

1. Debian menu under gnome is empty but in the enlightenment menu is well "visible". 2. cannot "xhost + ...": _X11TransSocketUNIXConnect: Can't connect: errno = 111 xhost: unable to open display ":0.0" any idea? a.

Problems after upgrade! Please help.

I'm in deep trouble. Yesterday I upgraded some packages from hamm to slink, and since then I've been unable to use my ppp link. I'm writing from a non-mantained win 95 I have in hand, because I can't do it under linux. pon stalls without dialing or returning the prompt, and at /var/log/messages th

Boot problems after upgrade 1.2.x -> 1.3.1

Hi, I have upgraded my 1.2.x (kernel 2.0.30), to 1.3.1. I have used the old kernel and modules (2.0.30) the boot process is "missing something" Modules are not loaded correctly for examples vfat is not loaded ( because it fails to recognize and load fat before vfat ). two lpd processes are start

Re: FIXED POST: Two problems after upgrade to Debian 1.3

On 3 Jun, Martin Bialasinski wrote: >On 3 Jun, Curtis L. Daugaard wrote: > >> 1) Irqtune was working for me under v.1.2, but though my configured >> hardware is the same I now get an error message. Here is the message at >> boot time: >>

Re: FIXED POST: Two problems after upgrade to Debian 1.3

On 3 Jun, Curtis L. Daugaard wrote: > > 1) Irqtune was working for me under v.1.2, but though my configured > hardware is the same I now get an error message. Here is the message at > boot time: > > " irqtune: setting system IRQ priority to 3/14 > irqtune: insmod failed on '/usr/lib/hwtools/i

FIXED POST: Two problems after upgrade to Debian 1.3

My apologies to the debian-user list for my faulty original post. I had just installed Netscape 4.0 and forgot to disable HTML in its mail package (which is enabled by default). Let me try again. Can someone enlighten me on the following, which I can't seem to solve with the available documentat

Re: Two problems after upgrade to Debian 1.3

In article <[EMAIL PROTECTED]> you wrote: > Can someone enlighten me on two problems?  I can't  seem to solve > them with the available documentation > 1) Irqtune was working for me under v.1.2, but though my configured > hardware is the same I now get an error message.  Here is the message >

Re: Two problems after upgrade to Debian 1.3

I don't have to check the headers to see that you're using Netscape 4 because I'm using Pine and HTML email doesn't look good here. There is something in the 'preferences' to disable it. I seem to remember that it defaults to HTML allowed when first installed. If they are serious about the new 'com

Two problems after upgrade to Debian 1.3

Can someone enlighten me on two problems?  I can't  seem to solve them with the available documentation 1) Irqtune was working for me under v.1.2, but though my configured hardware is the same I now get an error message.  Here is the message at boot time: "  irqtune: setting system IRQ priority