Bug#342164: Sarge Installer Bug Report: Kernel Module Fails To Load

2005-12-07 Thread Lennart Sorensen
On Tue, Dec 06, 2005 at 10:23:13PM -0800, O. Sharp wrote:
> Well, if so the installer is as ignorant of it as I am.  :)  lspci reports 
> the PCMCIA bridge as a Cirrus Logic CL 6729 (rev ee). I haven't found 
> any definitive list of which driver is used for which types of 
> controllers, but I did come across a Red Hat posting saying the CL 6729 
> was driven by i82365 and not yentl:
> 
>   https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=34301#c5
> 
> Does this seem correct for Debian as well?

Quite likely, although I believe debian 2.4 kernels use pcmcia-cs
drivers, in which case sarge with 2.4 kernel should install.  I may
remember wrong though.

> That poster also offers a solution for their situation which (if I'm 
> reading it right) suggests making some changes in /etc/pcmcia.conf, but 
> since the installer didn't _create_ any /etc/pcmcia.conf here it doesn't 
> help me much, whether it's correct for my hardware or not.  :)
> 
> Here's the PCMCIA-oriented stuff from lspci -v:
> 
> :00:0d.0 PCMCIA bridge: Cirrus Logic CL 6729 (rev ee)
> Flags: stepping, slow level
> I/O ports at fcfc [disabled] [size=4]
> 
> ...And here's something: I found a posting about CL 6729 drivers on a 
> Debian help list which looks pretty relevant, evidently a quote from the 
> author of the i82365 module:
>   (http://lists.debian.org/debian-user/2005/01/msg00066.html)
> 
> "
> This is sort of a historical accident. Prior to 2.4 kernels, there
> were only the pcmcia-cs driver modules. With 2.4, PCMCIA drivers
> became part of the kernel tree but they were not 100% the same as the
> pcmcia-cs drivers. One of the differences was that the CL 6729 bridge
> was not supported by the kernel drivers. There is a CL 6729 driver
> for the current 2.6 kernels but I think it is recent enough that it
> probably is not in most current Linux distributions.
> 
> It is possible to use the pcmcia-cs drivers with 2.4 (but not 2.6)
> kernels.  You would need to remove the kernel PCMCIA driver modules,
> and then compile the pcmcia-cs package.
> "
> 
> S... would I be right in guessing the updated CL 6729 drivers haven't 
> yet made it into the Debian installs I've tried (sarge and etch beta-1)? 
> If so, can you suggest an alternative?

Install sarge using 2.4 kernel?  Then upgrade to debian version you
want, keeping the kernel, and then get kernel-source package for kernel
you want and find patch for the cl 6729 driver and apply and build a new
kernel to use.

Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#342164: Sarge Installer Bug Report: Kernel Module Fails To Load

2005-12-06 Thread O. Sharp
On Tue, 6 Dec 2005, Lennart Sorensen wrote:
> On Tue, Dec 06, 2005 at 11:49:46AM -0800, O. Sharp wrote:
> > I've downloaded and tried it, and unfortunately it doesn't solve the 
> > problem. The 'modprobe -v i82365' failure showed up again early on, and 
> > then reappeared whenever an attempt to access network hardware was made.
> 
> Any chance your laptop does NOT have an i82365 pcmcia controller?  Maybe
> it is yenta or one of the other options instead.

Well, if so the installer is as ignorant of it as I am.  :)  lspci reports 
the PCMCIA bridge as a Cirrus Logic CL 6729 (rev ee). I haven't found 
any definitive list of which driver is used for which types of 
controllers, but I did come across a Red Hat posting saying the CL 6729 
was driven by i82365 and not yentl:

  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=34301#c5

Does this seem correct for Debian as well?

That poster also offers a solution for their situation which (if I'm 
reading it right) suggests making some changes in /etc/pcmcia.conf, but 
since the installer didn't _create_ any /etc/pcmcia.conf here it doesn't 
help me much, whether it's correct for my hardware or not.  :)

> Anything in lspci that might give a clue?

Here's the PCMCIA-oriented stuff from lspci -v:

:00:0d.0 PCMCIA bridge: Cirrus Logic CL 6729 (rev ee)
Flags: stepping, slow level
I/O ports at fcfc [disabled] [size=4]

...And here's something: I found a posting about CL 6729 drivers on a 
Debian help list which looks pretty relevant, evidently a quote from the 
author of the i82365 module:
  (http://lists.debian.org/debian-user/2005/01/msg00066.html)

"
This is sort of a historical accident. Prior to 2.4 kernels, there
were only the pcmcia-cs driver modules. With 2.4, PCMCIA drivers
became part of the kernel tree but they were not 100% the same as the
pcmcia-cs drivers. One of the differences was that the CL 6729 bridge
was not supported by the kernel drivers. There is a CL 6729 driver
for the current 2.6 kernels but I think it is recent enough that it
probably is not in most current Linux distributions.

It is possible to use the pcmcia-cs drivers with 2.4 (but not 2.6)
kernels.  You would need to remove the kernel PCMCIA driver modules,
and then compile the pcmcia-cs package.
"

S... would I be right in guessing the updated CL 6729 drivers haven't 
yet made it into the Debian installs I've tried (sarge and etch beta-1)? 
If so, can you suggest an alternative?

...So far I'm enjoying learning Linux, but I didn't realize what the 
learning-curve was going to be like.  :) :)  Thanks!

 -O.-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#342164: Sarge Installer Bug Report: Kernel Module Fails To Load

2005-12-06 Thread Lennart Sorensen
On Tue, Dec 06, 2005 at 11:49:46AM -0800, O. Sharp wrote:
> I've downloaded and tried it, and unfortunately it doesn't solve the 
> problem. The 'modprobe -v i82365' failure showed up again early on, and 
> then reappeared whenever an attempt to access network hardware was made.

Any chance your laptop does NOT have an i82365 pcmcia controller?  Maybe
it is yenta or one of the other options instead.

Anything in lspci that might give a clue?

Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#342164: Sarge Installer Bug Report: Kernel Module Fails To Load

2005-12-06 Thread O. Sharp

Hi! Thanks for the quick response:

> Quoting O. Sharp ([EMAIL PROTECTED]):
> > Can't get any PCMCIA card services or recognition. Everything else 
> > seems to be doing okay.
> > 
> > The Gateway Solo 2200 is an older laptop, with no built-in network or 
> > modem connections, so it's reliant on PCMCIA cards for this. Unfortunately 
> > the installer was unable to load the 'i82365' module, and every subsequent 
> > attempt to find the network card or modem resulted in a 'modprobe -v 
> > i82365' failure.
[...]
> 
> Could you try with the Etch installer beta1 which you can get from
> http://www.debian.org/devel/debian-installer? I suggest downloading
> the "netinst" CD image.

I've downloaded and tried it, and unfortunately it doesn't solve the 
problem. The 'modprobe -v i82365' failure showed up again early on, and 
then reappeared whenever an attempt to access network hardware was made.

When the problem first appeared I had a look at the virtual consoles. 
Virtual console #3 remained blank throughout - possibly because the 
installer was running in low-memory mode? - but virtual console #4 
showed the following after the first 'modprobe' error (hopefully with no 
typos on my part; some tabs added for readability):

Dec  6 10:28:16 kernel:  [] kobject_cleanup+0x3c/0x6c
Dec  6 10:28:16 kernel:  [] kobject_release+0x0/0xc
Dec  6 10:28:16 kernel:  [] kref_put+0x27/0x54
Dec  6 10:28:16 kernel:  [] kobject_put+0x16/0x1c
Dec  6 10:28:16 kernel:  [] kobject_release+0x0/0xc
Dec  6 10:28:16 kernel:  [] init_i82365+0x177/0x18e [i82365]
Dec  6 10:28:16 kernel:  [] sys_init_module+0xa9/0x180
Dec  6 10:28:16 kernel:  [] syscall_call+0x7/0xb
Dec  6 10:28:16 hw-detect: Using /lib/modules/2.6.12-1-386/kernel/drivers/
pcmcia/i82365.ko
Dec  6 10:28:16 hw-detect: insmod:
Dec  6 10:28:16 hw-detect: cannot insert 'lib/modules/2.6.12-1-386/kernel/
drivers/pcmcia/i82365.ko': No such device (-1)
Dec  6 10:28:16 hw-detect: No such device
Dec  6 10:28:16 hw-detect: insmod /lib/modules/2.6.12-1-386/kernel/drivers/
pcmcia/pcmcia_core.ko
Dec  6 10:28:16 hw-detect: insmod /lib/modules/2.6.12-1-386/kernel/drivers/
pcmcia/rsrc_nonstatic.ko
Dec  6 10:28:16 hw-detect: insmod /lib/modules/2.6.12-1-386/kernel/drivers/
pcmcia/i82365.ko
Dec  6 10:28:16 hw-detect: modprobe:
Dec  6 10:28:16 hw-detect: failed to load module i82365
Dec  6 10:28:16 hw-detect: 
Dec  6 10:28:16 hw-detect: Error loading 'i82365'

I continued on to see if the situation might change later, and when it 
reached the network hardware detection it again hit another red screen of 
'modprobe -v i82365'. A look at terminal 4 revealed another set of reports 
from hw-detect about failing to load i82365, and about nine lines before 
the failure there were a few other lines which may or may not be relevant:

Dec  6 10:48:50 kernel: Intel ISA PCIC probe: not found.
Dec  6 10:48:50 kernel: Device 'i82365.0' does not have a release() 
function, it is broken and must be fixed.
Dec  6 10:48:50 kernel: Badness in device_release at 
drivers/base/core.c:83

(For clarity, the second line "Device 'i82365.0'...": that is a zero, not 
an o or O or ko or any other alphabetic manifestation.)

The install program then brought up a screen saying, "No Ethernet card was 
detected, but a FireWire interface is present"; it then asked if I had 
some exotic FireWire-to-Ethernet setup it should be looking for. My laptop 
is an old 133 MHz Pentium, and certainly has no FireWire interface, but 
hopefully this is a clue about what the installer is thinking.  :)

After a couple unsuccessful attempts to get the network card recognized, I 
aborted the install.

Any suggestions? Any other information which may be relevant or helpful? 
Is there a way to install the i82365 module after the fact? Any help or 
pointers appreciated.  :)  Thanks!

  -O.-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#342164: Sarge Installer Bug Report: Kernel Module Fails To Load

2005-12-05 Thread Christian Perrier
Quoting O. Sharp ([EMAIL PROTECTED]):
> Can't get any PCMCIA card services or recognition. Everything else 
> seems to be doing okay.
> 
> The Gateway Solo 2200 is an older laptop, with no built-in network or 
> modem connections, so it's reliant on PCMCIA cards for this. Unfortunately 
> the installer was unable to load the 'i82365' module, and every subsequent 
> attempt to find the network card or modem resulted in a 'modprobe -v 
> i82365' failure.
> 
> The problem first appears very early in the install process. I looked at 
> the output on virtual terminal 3 (e.g., Alt-F3 - is "virtual terminal 3" 
> the right term to describe it?) when it first happened, and at that point 
> there were only eight lines of text present:


Could you try with the Etch installer beta1 which you can get from
http://www.debian.org/devel/debian-installer? I suggest downloading
the "netinst" CD image.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#342164: Sarge Installer Bug Report: Kernel Module Fails To Load

2005-12-05 Thread O. Sharp

Package: installation-reports

Boot method: boot floppy; also tried SMB floppy to boot directly from CD
Image version: Debian sarge, 3.1r0, date unknown - CD set from 
aboutdebian.com
Date: 1 December 2005, another attempt on 4 Dec 2005, a third on 5 Dec 
2005

Machine: Gateway Solo 2200 laptop
Processor: Pentium, 133MHz
Memory: 48Mb
Partitions:
  filesystem  type  1K blocks   used available %used mountpoint
  /dev/hda2   ext3  2869932   456664   2267480  17%  /
  tmpfs  tmpfs232040 23204   0%  /dev/shm


Output of lspci and lspci -n:

lscpi:
:00:00.0 Host bridge: Intel Corp. 430MX - 82437MX Mob. System Ctrlr 
(MTSC) & 82438MX Data Path (MTDP) (rev 02)
:00:01.0 Bridge: Intel Corp. 430MX - 82371MX Mobile PCI I/O IDE 
Xcelerator (MPIIX) (rev 03)
:00:0d.0 PCMCIA Bridge: Cirrus Logic CL 6729 (rev ee)
:00:14.0 VGA compatible controller: Chips and Technologies F65554 (rev 
c2)

lscpi -n:
:00:00.0 0600: 8086:1235 (rev 02)
:00:01.0 0680: 8086:1234 (rev 03)
:00:0d.0 0605: 1013:1100 (rev ee)
:00:14.0 0300: 102c:00e4 (rev c2)


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [E]
Config network: [ ]
Detect CD:  [O]
Load installer modules: [E]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]


Comments/Problems:

Can't get any PCMCIA card services or recognition. Everything else 
seems to be doing okay.

The Gateway Solo 2200 is an older laptop, with no built-in network or 
modem connections, so it's reliant on PCMCIA cards for this. Unfortunately 
the installer was unable to load the 'i82365' module, and every subsequent 
attempt to find the network card or modem resulted in a 'modprobe -v 
i82365' failure.

The problem first appears very early in the install process. I looked at 
the output on virtual terminal 3 (e.g., Alt-F3 - is "virtual terminal 3" 
the right term to describe it?) when it first happened, and at that point 
there were only eight lines of text present:

"
Using /lib/modules/2.4.27-2-386/kernel/drivers/pnp/isa-pnp.o
Using /lib/modules/2.4.27-2-386/kernel/drivers/pcmcia/pcmcia_core.o
Using /lib/modules/2.4.27-2-386/kernel/drivers/pcmcia/i82365.o
insmod: init_module: i82365: No such device
insmodisa-pnp
insmodpcmcia_core
insmodi82365
modprobe: failed to load module i82365
"

The rest of the Linux install seems to go okay, though obviously there's 
no network or modem support present.

I suspect it doesn't matter, but for what it's worth the card I'm trying 
to use is a Xircom XEM5600 network and modem combo card; the PCMCIA HOWTO 
says the card uses the xirc2ps_cs driver, and the installer gamely 
attempted to load it till it got the inevitable 'modprobe -v i82365' 
error.

...Unfortunately I'm still howlingly new to Linux, and haven't yet 
learned little things like "is there a way to install the module after 
the initial system installation" and "if there is, how do I go about it".  
:)  I've tried going through HOWTOs, but so far no luck. Can you offer a 
newbie some help?

Thanks!  :)

   -O.-
   O. Sharp <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]