From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <82c890d00703290158p301d0827w44c2542101f1945b@mail.gmail.com> Date: Thu, 29 Mar 2007 10:58:13 +0200 From: "Gabriel Diaz" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] pcmcia/cardbus rtl8139 support In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <82c890d00703280154k1e9f1795o692e7aa967f1436@mail.gmail.com> Topicbox-Message-UUID: 3519f63a-ead2-11e9-9d60-3106f5b1d025 hello thanks for the encouragement. I compiled a new kernel without pccard support, and now it boots, even the sdata wiht the new ids and the hd dma. I'm pretty sure i will get used to the dma speed quickly :) I added the DEBUG param in devpccard and got: #Y0: Ricoh 476 PCI/Cardbus bridge, B0000000 intl 11 engine(0): SlotFull(CardPowered) configuring slot 0 (SLotPowered) engine(0): SloptPowered(CardConfigured) that is with the card plugged and the kernel hanging, without the card, the kernel has started to work (before wasn't, the *nopcirouting seems to be unrelated as i tested with and without and get the same results, i suppose i'm the guilty of that previous failure) so i suppose the problem is between devpccard and rtl8139 driver. that was the only pccard i have, i will look into rtl8139 to see if i can get a conclusion. thanks all, gabi btw: the card is "Conceptronic CSP100TCL 10/100Mbps LAN SnapPort Card for notebooks" On 3/28/07, erik quanstrom wrote: > On Wed Mar 28 04:54:47 EDT 2007, gabidiaz@gmail.com wrote: > > hello > > > > i'm still trying to get this notebook work. (ibm z60t) > > > > Any ideas why the 9pcf kernel provided with the install cdrom is able > > to boot the system while a local compiled version (with the sources > > from the cdrom and the configuration untouched) hangs after the memory > > line is printed (1015M memory: 256 kernel data, 758 user, 1383 swap) ? > > /386/9pc* are not regenerated each time a change is made to > the kernel sources. with the date of 9pc from the cd in hand > and sources, you should be able to work out what changed. > > one possibility is that it's an interrupt coming when a device > is partially configured and the old kernel also had the bug, > but it was hidden. sdata.c is somewhat notorious for this. > > > i added to pci.c the id 8086/2641 of the intel southbridge ich6 mobile > > (with the original kernels, the one that boots, and the one that > > doesn't boot, both, prints the line about not finding southbridge). > > And added too the sdata disk id to the dma switch as commented on a > > recent thread. > > > > The modified kernel also does not boot and hangs in the same point. > > i think you'll have better luck first isolating exactly the > function/functions and line numbers where you're stuck. are you > sure you're getting ata interrupts? > > the standard kernel prints are a very inexact way of determining > what has happeend and what hasn't. sometimes the best > way is to do a binary search with print statements. > > > i added debug codes in sdata.c but i've to much output to see > > anything, i saw the last command returns a timeout (i suppose was a > > probe command and is not an error). > > unfortunately, i don't know of a usb console. > > > this notebook has no serial and no network (broadcom 57x, rtl8139 > > card), should i give up? > > heck, no. you're doing the right things and it seems like you are > making quite a bit of progress. > > since you can boot from the cd, you have a lot of options. you > could try rebuilding from sources history on the day the kernel > on the cd was built and adding newer bits until it breaks. > (kernel work is so unglamorous.) also, if you have a fileserver, > you can try compiling a kernel without sd in the configuration. > > - erik >