This one time, at band camp, Daniel Fabian said: > > Hi List, > > Sorry for the long post, but I have captured the log files from friday, when > it worked, and from today, when it didn't. Perhaps someone can help me > better with this data. Sorry I did not include it in the first post. > > Thanks, > daniel > Oct 18 00:20:58 lapdog kernel: Kernel command line: BOOT_IMAGE=Linux ro > root=307 video=vga16:off > Oct 18 00:20:58 lapdog kernel: Console: colour VGA+ 80x25
> Oct 18 00:20:58 lapdog kernel: PCI: Found IRQ 10 for device 00:01.1 > Oct 18 00:20:58 lapdog kernel: PCI: Sharing IRQ 10 with 00:01.6 > Oct 18 00:20:58 lapdog kernel: eth0: Realtek RTL8201 PHY transceiver found > at address 1. > Oct 18 00:20:58 lapdog kernel: eth0: Using transceiver found at address 1 as > default > ---> Mind the MAC Address! <--- Oct 18 00:20:58 lapdog kernel: eth0: SiS 900 > PCI Fast Ethernet at 0xd000, IRQ 10, 01:01:01:01:01:01. < a lot snipped> Not that here you're using plain color VGA console . . . > Oct 18 00:20:58 lapdog kernel: Linux agpgart interface v0.99 (c) Jeff > Hartmann > Oct 18 00:20:58 lapdog kernel: agpgart: Maximum main memory to use for agp > memory: 196M > Oct 18 00:20:58 lapdog kernel: agpgart: Detected SiS 630 chipset > Oct 18 00:20:58 lapdog kernel: agpgart: AGP aperture is 64M @ 0xe0000000 > Oct 18 00:20:58 lapdog kernel: eth0: Media Link On 10mbps half-duplex > Oct 18 00:20:58 lapdog kernel: eth0: Media Link On 10mbps half-duplex > Today: > Oct 22 17:12:38 lapdog kernel: Kernel command line: BOOT_IMAGE=Linux ro > root=307 > Oct 22 17:12:38 lapdog kernel: Console: colour dummy device 80x25 > Oct 22 17:12:38 lapdog kernel: vesafb: framebuffer at 0xd0000000, mapped to > 0xd001a000, size 8192k > Oct 22 17:12:38 lapdog kernel: vesafb: mode is 1024x768x16, linelength=2048, > pages=4 > Oct 22 17:12:38 lapdog kernel: vesafb: protected mode interface info at > cabc:0008 > Oct 22 17:12:38 lapdog kernel: vesafb: scrolling: redraw > Oct 22 17:12:38 lapdog kernel: vesafb: directcolor: size=0:5:6:5, > shift=0:11:5:0 > Oct 22 17:12:38 lapdog kernel: Console: switching to colour frame buffer > device 128x48 > Oct 22 17:12:38 lapdog kernel: fb0: VESA VGA frame buffer device > Oct 22 17:12:38 lapdog kernel: vga16fb: mapped to 0xc00a0000 > Oct 22 17:12:38 lapdog kernel: fb1: VGA16 VGA frame buffer device . . . and here you're using framebuffer. The NIC is sharing an interrupt, and perhaps that's what's confusing it. Don't know, but maybe you can reassign the NIC IRQ in the BIOS. > Oct 22 17:12:38 lapdog kernel: PCI: Found IRQ 10 for device 00:01.1 > Oct 22 17:12:38 lapdog kernel: PCI: Sharing IRQ 10 with 00:01.6 > Oct 22 17:12:38 lapdog kernel: eth0: Realtek RTL8201 PHY transceiver found > at address 1. > Oct 22 17:12:38 lapdog kernel: eth0: Using transceiver found at address 1 as > default > Oct 22 17:12:38 lapdog kernel: eth0: SiS 900 PCI Fast Ethernet at 0xd000, > IRQ 10, 00:a0:cc:c7:08:bd. It sounds like you don't have an X problem, exactly, as you get the login manager. If X was broken, you wouldn't get that far. It may be that you have some problem that is supposed to run when you login that barfs on the framebuffer. Try renaming your .kde directory out of the way, and rerunning it. HTH, Steve -- Write yourself a threatening letter and pen a defiant reply.
msg08454/pgp00000.pgp
Description: PGP signature
