Re: sarge->etch upgrade hits dependency hell
On Tue, Dec 12, 2006 at 10:58:33AM -0800, Andrew Sackville-West wrote:
> On Tue, Dec 12, 2006 at 11:54:24AM -0500, hendrik@topoi.pooq.com wrote:
> > On Mon, Dec 11, 2006 at 10:27:29AM -0800, Andrew Sackville-West wrote:
> > > On Mon, Dec 11, 2006 at 08:57:03AM -0500, hendrik@topoi.pooq.com wrote:
> > > > On Sun, Dec 10, 2006 at 07:38:37PM -0800, Andrew Sackville-West wrote:
> > > > >
> > > > > why don't you boot sarge, chroot into etch and install a kernel from
> > > > > inside the chroot? I think udev wants a kernel >= 2.6.15, IIRC.
> > > >
> > > > Actually, it turns out that aptitude *&had* managed to install the new
> > > > kernel -- it just hadn't put it into the boot menu -- a probelm easily
> > > > fixed from the sarge system.
> > >
> > > great!
> > >
> > > >
> > > > I now have an etch with networking, which I can use aptitude on, but
> > > > whose X doesn't come up properly. startx brings me to the black screen
> > > > of death, xdm permits me to enter username and password, blanks the
> > > > screen as if it is doing something, and then returns to its login
> > > > screen. gdm doesn't even get to login -- it just gives the black screen
> > > > of death.
> > > >
> > > > I looks as if I will have to investigate another day -- my regular users
> > > > are showing up.
> > >
> > > one step at a time eh? of course you nkow the drill, post the X logs.
> > >
> > > good luck
> >
> > I made no changes since my remarks quoted above. But when I booted this
> > morning, X did come up, XDM gave me a login window, and it allowed me
> > to log in and have access to my usual home directory. But it did give
> > me gnome instead of icewm (which was my default under gdm).
>
> well, that's weird.
>
This morning I updated everything -- there were now a number of upgraded
packages for etch -- and tried again. the xorg log file complained that
something was incompatible with the frame buffer, so I reconfigired xorg
telling it not to use the frame buffer when it asked me.
> >
> > So I now know that X works, that it recognises the screen, the keyboard,
> > the mouse, and so forth.
>
> cool.
>
> >
> > When I switched to the text-mode console using ctl-alt-F1, it gave me
> > that, and it worked properly too.
> >
> > But all was not well. When I switched back (using ctl-alt-F7) it gave
> > me a scrambled screen -- lots of horizontal streaks. The various
> > window decorations were present, but in multiple copies, and each
> > mostly obscured by the horizontal bars. Evidently the screen size in
> > its frame buffer did not match the screen size it was using.
>
> sounds like a driver issue for sure.
I removed the highest resolution from the list when dpkg-reconfigure xserver-xorg
asked me. Now the scrambled screen is gone.
>
> >
> > I could ctl-alt-F1 back to the text cosole, which worked, and kill a
> > carefully chosen process, and return to the X screen to be greeted by
> > another login window, which worked too.
> >
>
> hmmm.... which process did you kill? also, try killing xdm and then
> using startx and see if that gives you the same problems above when
> switching consoles.
>
> > sing gdm instead of xdm still gives the black screen of death instead of
> > a login window.
New problems, now that I' using xdm and gnome. After I log out, I get the
black screen of death.
>
> weird that gdm fails and xdm doesn't. Have you gone down the road of
> purging all of X and reinstalling it?
Not as such. Might there be something left from sarge's Xfree?
I've checked the logs - nothing suspicious, except:
in Xorg.0.log, there's one (EE) message, in context:
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Reloading /usr/lib/xorg/modules/libi2c.so
(II) RADEON(0): Using R200 i2c bus access method
(EE) RADEON(0): Failed to register i2c bus
(II) Loading sub module "fi1236"
(II) LoadModule: "fi1236"
(II) Reloading /usr/lib/xorg/modules/multimedia/fi1236_drv.so
(II) RADEON(0): I2C device "Radeon multimedia bus:FI12xx Tuner" registered at address 0xC0.
in the kern.log and sys.log, where there are many hundreds of
megabytes containing messages like
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong gconfd (h3-5391): Exiting
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -3
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -2
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 1, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 2, Code: 0, Value: -1
Dec 18 10:42:47 lovesong kernel: evbug.c: Event. Dev: isa0060/serio1/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:42:48 lovesong kernel: mtrr: 0xe0000000,0x8000000 overlaps existing 0xe0000000,0x4000000
Dec 18 10:42:48 lovesong kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
Dec 18 10:42:48 lovesong kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
Dec 18 10:42:48 lovesong kernel: agpgart: Putting AGP V2 device at 0000:02:00.0 into 1x mode
Dec 18 10:42:49 lovesong kernel: [drm] Setting GART location based on new memory map
Dec 18 10:42:49 lovesong kernel: [drm] Loading R200 Microcode
Dec 18 10:42:49 lovesong kernel: [drm] writeback test succeeded in 1 usecs
Dec 18 10:42:52 lovesong kernel: irq 201: nobody cared (try booting with the "irqpoll" option)
Dec 18 10:42:52 lovesong kernel: <b012f163> __report_bad_irq+0x2b/0x69 <b012f30b> note_interrupt+0x16a/0x197
Dec 18 10:42:52 lovesong kernel: <b012ed4a> handle_IRQ_event+0x23/0x4c <b012eddd> __do_IRQ+0x6a/0x91
Dec 18 10:42:52 lovesong kernel: <b0105149> do_IRQ+0x19/0x24 <b01039da> common_interrupt+0x1a/0x20
Dec 18 10:42:52 lovesong kernel: <b010a8c5> delay_pmtmr+0xd/0x13 <b01a84a9> __delay+0x9/0xa
Dec 18 10:42:52 lovesong kernel: <f1cda899> radeon_do_wait_for_idle+0x61/0x6f [radeon] <f1cdae4e> radeon_cp_idle+0x0/0x6c [radeon]
Dec 18 10:42:52 lovesong kernel: <f1c7e481> drm_ioctl+0x142/0x185 [drm] <f1c7e33f> drm_ioctl+0x0/0x185 [drm]
Dec 18 10:42:52 lovesong kernel: <b0153437> do_ioctl+0x37/0x42 <b0153625> vfs_ioctl+0x1e3/0x1f1
Dec 18 10:42:52 lovesong kernel: <b012ed4a> handle_IRQ_event+0x23/0x4c <b015367d> sys_ioctl+0x4a/0x61
Dec 18 10:42:52 lovesong kernel: <b0102977> syscall_call+0x7/0xb
Dec 18 10:42:52 lovesong kernel: handlers:
Dec 18 10:42:52 lovesong kernel: [<f08812c3>] (ohci_irq_handler+0x0/0x636 [ohci1394])
Dec 18 10:42:52 lovesong kernel: [<f1ce3407>] (radeon_driver_irq_handler+0x0/0x7f [radeon])
Dec 18 10:42:52 lovesong kernel: Disabling IRQ #201
Dec 18 10:43:10 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 42
Dec 18 10:43:10 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 42, Value: 1
Dec 18 10:43:10 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:43:10 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 42
Dec 18 10:43:10 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 42, Value: 0
Dec 18 10:43:10 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:43:15 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 42
Dec 18 10:43:15 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 42, Value: 1
Dec 18 10:43:15 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Dec 18 10:43:15 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 42
Dec 18 10:43:15 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 42, Value: 0
Dec 18 10:43:15 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Dec 18 11:38:48 lovesong kernel: klogd 1.4.1#18, log source = /proc/kmsg started.
Dec 18 11:38:48 lovesong kernel: 4, Code: 4, Value: 201
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 104, Value: 1
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 201
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 104, Value: 0
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 209
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 109, Value: 1
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 209
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 109, Value: 0
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 209
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 109, Value: 1
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 209
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 109, Value: 0
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 201
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 104, Value: 1
Dec 18 11:38:48 lovesong kernel: evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
Are there other logs I should be looking at? xdm.log was last written over a week ago, so is probablu not
relevant. Unless, of course, it's moved after an upgrade last week and I'm looking at the wrong place.
-- hendrik
Reply to: