Re: Crossgrading Wheezy from 32bit to 64bit: Solving package dependency problems after kernel change.

Hi Sven, Thanks for that suggestion. I've quickly tried this on a test VM and indeed crossgrading seems to work much better in debian 9 compared to debian 7. Thanks, Pieter > On 16 Jan 2018, at 16:03, Sven Hartge wrote: > > Pieter Van Isacker wrote: > >> While testing change a Debian Wheezy

Re: Crossgrading Wheezy from 32bit to 64bit: Solving package dependency problems after kernel change.

Hi, On Tue, 16 Jan 2018 14:58:48 +0100 Pieter Van Isacker wrote: > Hi all, > > While testing change a Debian Wheezy from 32bit to 64bit I ran into an > issue. Following the guide on https://wiki.debian.org/CrossGrading > Once we've change to 64bit we > pla

Re: Crossgrading Wheezy from 32bit to 64bit: Solving package dependency problems after kernel change.

Sven Hartge wrote: > Still, there is no guarantee it will work and for production systems I > strongly advise you to just backup the data and reinstall from scratch > as 64bit system. +1 copy data (backup) dpkg --get-selections install 64 dpkg --set-selections migrate configurations 90% is plan

Re: Crossgrading Wheezy from 32bit to 64bit: Solving package dependency problems after kernel change.

Pieter Van Isacker wrote: > While testing change a Debian Wheezy from 32bit to 64bit I ran into an > issue. Following the guide on https://wiki.debian.org/CrossGrading > Once we've change to 64bit we > plan to update to Debian 8 and then possibly to Debian 9

Crossgrading Wheezy from 32bit to 64bit: Solving package dependency problems after kernel change.

Hi all, While testing change a Debian Wheezy from 32bit to 64bit I ran into an issue. Following the guide on https://wiki.debian.org/CrossGrading Once we've change to 64bit we plan to update to Debian 8 and then possibly to Debian 9 Changing the kernel to

Re: no cd/dvd devices detected after kernel change

Le mardi 29 juillet 2008, Joe Hickey a écrit : > On Tue, Jul 29, 2008 at 07:51:04PM +0100, Joe Hickey wrote: > > > > Using 2.6.24-1-686, my two IDE-connected cd/dvd drives are > > > > detected as /dev/sr0 and /dev/sr1, symlinked to cdrom0 and > > > > cdrom1, and work perfectly. When I boot 2.6.25-2

Re: no cd/dvd devices detected after kernel change

On Tue, Jul 29, 2008 at 07:51:04PM +0100, Joe Hickey wrote: > > > Using 2.6.24-1-686, my two IDE-connected cd/dvd drives are detected as > > > /dev/sr0 and /dev/sr1, symlinked to cdrom0 and cdrom1, and work perfectly. > > > When I boot 2.6.25-2-686-bigmem, no entries for these devices appear in > >

Re: no cd/dvd devices detected after kernel change

> > Using 2.6.24-1-686, my two IDE-connected cd/dvd drives are detected > > as /dev/sr0 and /dev/sr1, symlinked to cdrom0 and cdrom1, and work > > perfectly. When I boot 2.6.25-2-686-bigmem, no entries for these > > devices appear in /dev. > I'm not sure this is relevant but when I modinfo on id

Re: no cd/dvd devices detected after kernel change

Le dimanche 20 juillet 2008, Joe Hickey a écrit : > Hello, > > Using 2.6.24-1-686, my two IDE-connected cd/dvd drives are detected > as /dev/sr0 and /dev/sr1, symlinked to cdrom0 and cdrom1, and work > perfectly. When I boot 2.6.25-2-686-bigmem, no entries for these > devices appear in /dev. > > Wi

no cd/dvd devices detected after kernel change

Hello, Using 2.6.24-1-686, my two IDE-connected cd/dvd drives are detected as /dev/sr0 and /dev/sr1, symlinked to cdrom0 and cdrom1, and work perfectly. When I boot 2.6.25-2-686-bigmem, no entries for these devices appear in /dev. With the working kernel, the relevant part of dmesg is: scsi7 : S

Re: date/time problem since kernel change

Hi, > And is your hardware clock actually set to local time? How do you see that exactly (sorry if this a dummy question, but I'm quite lost with local/universal, UTC, CEST, etc.) ? -- Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [E

Re: date/time problem since kernel change

Hi, > And what is the content of "/etc/adjtime"? > I ask, because the behaviour of "hwclock" depends on the contents of > this file (man hwclock). The last line of /etc/adjtime is "LOCAL". In fact, after some Google searching, I wonder if the problem doesn't come from the way the kernel access /

Re: date/time problem since kernel change

Julien Barnier wrote: > | # Set UTC=yes if your system clock is set to UTC (GMT), and UTC=no if not. > | UTC=no And is your hardware clock actually set to local time? -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTE

Re: date/time problem since kernel change

Julien Barnier wrote: > Hi, > >> Are the packages "initscripts" and "tzdata" installed? > > Yes, they are. > >> What is the result of the command >> grep UTC /etc/default/rcS > > Here it is : > > , > | [EMAIL PROTECTED]:~$ grep UTC /etc/default/rcS > | # Set UTC=yes if your system clock

Re: date/time problem since kernel change

Hi, > Are the packages "initscripts" and "tzdata" installed? Yes, they are. > What is the result of the command > grep UTC /etc/default/rcS Here it is : , | [EMAIL PROTECTED]:~$ grep UTC /etc/default/rcS | # Set UTC=yes if your system clock is set to UTC (GMT), and UTC=no if not. | UTC=

Re: date/time problem since kernel change

Julien Barnier wrote: > Hi all, > > I recently switched from an own compiled 2.6.20 kernel to the debian > linux-image-2.6.22 one (I'm using Sid). > > And since I use this new kernel, I get a problem with the time on my > machine : at each reboot I get two hours more than the real time. I'm > qui

date/time problem since kernel change

Hi all, I recently switched from an own compiled 2.6.20 kernel to the debian linux-image-2.6.22 one (I'm using Sid). And since I use this new kernel, I get a problem with the time on my machine : at each reboot I get two hours more than the real time. I'm quite sure it is a problem with syncing s

Kernel change and RAID 1

Hi, I have a little big problem on my little server. There i have installed the 2.2.13 kernel now i want to change to the latest 2.2.x (2.2.18) due driver updates. I had compiled all like i do it all the time. But after i restarted my computer i raid resynchronisized my raid drives (software r

Kernel change

Okay - I have solved the xdm problem. I needed to link PS/2 mouse support into the kernel. I found this out by looking at the output of xdm. I have now configured ipchains as I want including running it automatically on reboot. Thanks for the help.

Kernel change

I have just built a new 2.0.36 kernel but, when I boot it, xdm does not work. I switch back to my standard kernel and everything is okay. Am I forgetting to select something related to X or something? Is there a web page detailing standard kernel things? I am looking at /usr/doc/HOWTO/Kernel-HO