Linux 2.6.10 -> partial success here...

[Joseph E. Sacco, Ph.D.]

Geert,

I don't have hardware that matches your system.  That being said, let me
make some suggestions that qualifies me to be "master of the obvious".
These may not help but might cause you to think about something that
would help.

(0) Watch the boot sequence message looking for surprises. Comb through
the boot and message logs looking for anything odd. [That is how I found
the change in file system name for the USB FS.]

(1) Check out the Documentation, which is usually out of date, and see
if there is anything new, novel, or stimulating about your network card
or frame buffer.

(2) Take a quick run through www.kernel.org to see what major changes
were made going from 2.6.9 to 2.6.10.

(3) State your hardware configuration so others with similar hardware
might be able to assistance.

(4) Start with a configuration that you know worked for 2.6.9.
[borrow the .config from the YDL source].

(5) Start with the default frame buffer.
If that works well you have a baseline by which to judge all others.

-Joseph

============================================================================


On Mon, 2004-12-27 at 12:44, Geert Janssens wrote:
> Encouraged by Joseph and Stephan, I also downloaded linux 2.6.10, to 
> give it a try.
> 
> After configuration, it compiled fine, but there are some problems 
> during boot:
> 
> 1. The framebuffer doesn't seem to work properly. With this I mean, log 
> messages are printed on screen but some characters seem to be distorted 
> and flickering.
> 
> 2. While loading the tulip driver for my PCI based PNIC-II network card, 
> I get a kernel oops:
> 
> kernel: Linux Tulip driver version 1.1.13 (May 11, 2002)
> kernel: PCI: Enabling device 0000:00:0e.0 (0084 -> 0087)
> kernel: Oops: kernel access of bad area, sig: 11 [#1]
> kernel: PREEMPT
> kernel: NIP: DB896828 LR: DB896788 SP: D95ABDB0 REGS: d95abd00 TRAP: 
> 0300    Not tainted
> kernel: MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
> kernel: DAR: 80800030, DSISR: 40000000
> kernel: TASK = d9cfcbb0[1067] 'modprobe' THREAD: d95aa000
> kernel: Last syscall: 128
> kernel: GPR00: DB899B54 D95ABDB0 D9CFCBB0 D4C13000 00000000 00000000 
> D4C139FC D95ABD98
> kernel: GPR08: DB89E884 80800030 01A08000 D96D6860 28442428 1004B7D8 
> 00000000 00000000
> kernel: GPR16: D95ABDB8 00000000 DB89BED0 00000018 C0A65C48 D96D6230 
> DB8A0000 D96D6220
> kernel: GPR24: 00000009 DB8A0000 80800000 C0A65C00 D96D6000 000000B4 
> 80800000 00000000
> kernel: NIP [db896828] tulip_init_one+0x2e0/0xd2c [tulip]
> kernel: LR [db896788] tulip_init_one+0x240/0xd2c [tulip]
> kernel: Call trace:
> kernel:  [c01646cc] pci_device_probe+0xc4/0x234
> kernel:  [c019e1f4] driver_probe_device+0x4c/0xa8
> kernel:  [c019e5c4] driver_attach+0x78/0xe0
> kernel:  [c019e6c4] bus_add_driver+0x98/0x184
> kernel:  [c019f028] driver_register+0x30/0x40
> kernel:  [c0164a68] pci_register_driver+0x70/0xc8
> kernel:  [db07b04c] tulip_init+0x4c/0xf0 [tulip]
> kernel:  [c00374c8] sys_init_module+0x288/0x3dc
> kernel:  [c0004420] ret_from_syscall+0x0/0x44
> 
> 
> This makes the system hangs later on while trying to initialize nmbd, 
> because no network is found.
> 
> 
> Any ideas ? Which options did I miss, or add too much ?
> 
> 
> Thanks,
> 
> Geert Jan
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general at lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try  '<keywords> site:terrasoftsolutions.com'
-- 
joseph_sacco[at]comcast[dot]net