kernel-2.4.22-1.2163.nptl

[Chuck Mead]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The emu10k1 driver will not load from the subject kernel. It bombs with
unresolved symbols:

[root@stealth root]# modprobe emu10k1
/lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o:
unresolved symbol sys_lseek
/lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o: insmod
/lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o failed
/lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o: insmod
emu10k1 failed


- --
csm
Lunar Linux Project Lead
Disclaimer: "I am not a curmudgeon! No... really..."
Addendum: "Bwahahaha! Fire up the orbital mind-control lasers!"
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFAEJBjq3bny/5+GAcRAvnPAKCopS3J8yWQpUhvuyjEv45UDpjYgACbBNbp
> RMBiiuBL62Jme+K33DPa2I8=
> =LwHU
> -----END PGP SIGNATURE-----

[Dave Jones]

On Fri, 2004-01-23 at 03:09, Chuck Mead wrote:
>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>  
>  The emu10k1 driver will not load from the subject kernel. It bombs with
>  unresolved symbols:
>  
>  [root@stealth root]# modprobe emu10k1
>  /lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o:
>  unresolved symbol sys_lseek
>  /lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o: insmod
>  /lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o failed
>  /lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o: insmod
>  emu10k1 failed 
Fixed locally, will be in the next build.

Thanks,

	Dave

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 23 Jan 2004, Dave Jones spewed into the bitstream:

DJ>On Fri, 2004-01-23 at 03:09, Chuck Mead wrote:
DJ>> -----BEGIN PGP SIGNED MESSAGE-----
DJ>> Hash: SHA1
DJ>> 
DJ>> The emu10k1 driver will not load from the subject kernel. It bombs with
DJ>> unresolved symbols:
DJ>> 
DJ>> [root@stealth root]# modprobe emu10k1
DJ>> /lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o:
DJ>> unresolved symbol sys_lseek
DJ>> /lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o: insmod
DJ>> /lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o failed
DJ>> /lib/modules/2.4.22-1.2163.nptl/kernel/drivers/sound/soundcore.o: insmod
DJ>> emu10k1 failed
DJ>
DJ>Fixed locally, will be in the next build.

I am rebuilding it locally... will that fix it or is there something more 
that must be done?

- --
csm
Lunar Linux Project Lead
Disclaimer: "I am not a curmudgeon! No... really..."
Addendum: "Bwahahaha! Fire up the orbital mind-control lasers!"
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFAEJfqq3bny/5+GAcRAhfGAJ9NFjwcSc3UDmFDUgtzRWqApmlVJwCgn2Vn
> nFhMFh5+giauy8Eq3V7V+Ao=
> =n1D4
> -----END PGP SIGNATURE-----

[Dave Jones]

On Fri, 2004-01-23 at 03:41, csm(a)Lunar-Linux.org wrote:

>  
>  I am rebuilding it locally... will that fix it or is there something more 
>  that must be done? 
Yeah, the tux patch deletes EXPORT_SYMBOL(sys_lseek) which it shouldn't.
Just re-add it to the file its patching. (arch/i386/kernel/i386_ksyms.c
from memory)

	Dave

[Daniel Roesen]

On Fri, Jan 23, 2004 at 03:19:26AM +0000, Dave Jones wrote:
>  Fixed locally, will be in the next build. 
Dave, is there any chance to get the Firmware Loader stuff into
the FC1 kernel? This one being missing is the only reason I (and
probably others) need to use a self-built kernel in order to use
the Prism (www.prism54.org) WLAN driver... one of the most (or if
not _the_ most used chip for 54mbps .11g WLAN cards).

Would be cool.


Best regards,
Daniel

[Dave Jones]

On Fri, 2004-01-23 at 15:54, Daniel Roesen wrote:
>  On Fri, Jan 23, 2004 at 03:19:26AM +0000, Dave Jones wrote:
>  > Fixed locally, will be in the next build.
>  
>  Dave, is there any chance to get the Firmware Loader stuff into
>  the FC1 kernel? This one being missing is the only reason I (and
>  probably others) need to use a self-built kernel in order to use
>  the Prism (www.prism54.org) WLAN driver... one of the most (or if
>  not _the_ most used chip for 54mbps .11g WLAN cards). 
> From memory, the changes weren't very invasive, so thats quite
> probable. 
I'll take a peek at it when I'm done with FC2 stuff.
(I'm buried under in other work right now).

	Dave

Dave Jones wrote:

> On Fri, 2004-01-23 at 15:54, Daniel Roesen wrote:
>   
>
> >On Fri, Jan 23, 2004 at 03:19:26AM +0000, Dave Jones wrote:
> >    
> >
> >>Fixed locally, will be in the next build.
> >>      
> >>
> >Dave, is there any chance to get the Firmware Loader stuff into
> >the FC1 kernel? This one being missing is the only reason I (and
> >probably others) need to use a self-built kernel in order to use
> >the Prism (www.prism54.org) WLAN driver... one of the most (or if
> >not _the_ most used chip for 54mbps .11g WLAN cards).
> >    
> >
>
> >From memory, the changes weren't very invasive, so thats quite probable.
> I'll take a peek at it when I'm done with FC2 stuff.
> (I'm buried under in other work right now).
>  

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=111615

-- 
shrek-m

[Pasi Pirhonen]

Hi,


On Fri, Jan 23, 2004 at 04:54:01PM +0100, Daniel Roesen wrote:
>  
>  Dave, is there any chance to get the Firmware Loader stuff into
>  the FC1 kernel? This one being missing is the only reason I (and
>  probably others) need to use a self-built kernel in order to use
>  the Prism (www.prism54.org) WLAN driver... one of the most (or if
>  not _the_ most used chip for 54mbps .11g WLAN cards).
>   
Umm? What's the problem?

Linux tc 2.4.22-1.2149.nptl.prism54 #1 Sat Jan 10 20:17:38 EET 2004 i686 i686 i386
GNU/Linux

I just dropped the prism54-patch in, rediffed and build the kernel SRPM
again.

That doesn't work with the automatic network config tho. The prism
driver is not happy if networking tries to treat it as 'Wireless'.
Should update the wireless-tools too tho.

Just loading the driver and ifconfig it manually and it's working.
Should really peek what is actually wrong with it as on debian it's
working 'out of the box', but then again it's just my tabletPC which
is used just to watch movies and it's powered all the time anyway ....


-- 
Pasi Pirhonen - upi(a)iki.fi - http://iki.fi/upi/

[Daniel Roesen]

On Fri, Jan 23, 2004 at 07:39:36PM +0200, Pasi Pirhonen wrote:
>  Umm? What's the problem? 
The the Prism54 driver needs the kernel firmware loader, which
isn't in 2.4.22.

>  Linux tc 2.4.22-1.2149.nptl.prism54 #1 Sat Jan 10 20:17:38 EET 2004
> i686 i686 i386 GNU/Linux
>  
>  I just dropped the prism54-patch in, rediffed and build the kernel SRPM
>  again. 
Actually, I wonder _how_ this works, given that at least my NetGear
WG511 needs the firmware loaded. The hotplug framework triggers
that upon insertion of the card.


Regards,
Daniel

[Pasi Pirhonen]

Hi,


On Sun, Jan 25, 2004 at 12:07:26AM +0100, Daniel Roesen wrote:
>  On Fri, Jan 23, 2004 at 07:39:36PM +0200, Pasi Pirhonen wrote:
>  > Umm? What's the problem?
>  
>  The the Prism54 driver needs the kernel firmware loader, which
>  isn't in 2.4.22.
>  
>  > Linux tc 2.4.22-1.2149.nptl.prism54 #1 Sat Jan 10 20:17:38 EET 2004 i686 i686 i386
> GNU/Linux
>  > 
>  > I just dropped the prism54-patch in, rediffed and build the kernel SRPM
>  > again.
>  
>  Actually, I wonder _how_ this works, given that at least my NetGear
>  WG511 needs the firmware loaded. The hotplug framework triggers
>  that upon insertion of the card.
>  
>   
I might have forgot to mention that i got the firmware.agent installed.
First just grabed the debian one, but later on tool it from
installing hotplug from fedora-devel 

[root@tc /]# rpm -qf /etc/hotplug/firmware.agent 
hotplug-2004_01_05-1

Insertion of the card triggers the firmware loading as expected. After
that it's accessible just by normal ifconfig. I don't use WEP on this
LAN. Only MAC-based access restrictions to keep lamest (l)users out :)



-- 
Pasi Pirhonen - upi(a)iki.fi - http://iki.fi/upi/

Pasi Pirhonen wrote:

> I might have forgot to mention that i got the firmware.agent
> installed.
> First just grabed the debian one, but later on tool it from
> installing hotplug from fedora-devel 
>
> [root@tc /]# rpm -qf /etc/hotplug/firmware.agent 
> hotplug-2004_01_05-1
>   
>  
http://cvs.sourceforge.net/viewcvs.py/linux-hotplug/admin/etc/hotplug/fir...

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112824

-- 
shrek-m

[Daniel Roesen]

On Sun, Jan 25, 2004 at 01:48:39AM +0200, Pasi Pirhonen wrote:
>  I might have forgot to mention that i got the firmware.agent
> installed. 
Sure, but this one just uses the kernel firmware loader - which
is (to my knowledge, and given Dave's comment) not in the current
FC1 kernel.


Regards,
Daniel

[Pasi Pirhonen]

Hi,


On Sun, Jan 25, 2004 at 06:39:05AM +0100, Daniel Roesen wrote:
>  On Sun, Jan 25, 2004 at 01:48:39AM +0200, Pasi Pirhonen wrote:
>  > I might have forgot to mention that i got the firmware.agent installed.
>  
>  Sure, but this one just uses the kernel firmware loader - which
>  is (to my knowledge, and given Dave's comment) not in the current
>  FC1 kernel.
>  
>   

I am lazy to dig the kernel code, but 

prism54                40524   1 
firmware_class          6060   0  [prism54]

What the heck is the 'fimware_class' then? And

eth1: islpci_open()
eth1: resetting device...
eth1: uploading firmware...
firmware_class.c:call_helper: firmware: /sbin/hotplug firmware add
eth1: firmware uploaded done, now triggering reset...
eth1: prism54_mib_init()
eth1: done with prism54_mib_init()! -- Client Managed mode

from dmesg very much seems me like the fiwnware gets loaded?

This kernel is pure 2.4.22-1.2149.nptl which i pached with 

patch-2.4-prism54-cvs-latest (Jan 10 on my disk)

and made rediff to include that to SRPM build process and rebuild the
kernel RPM.



-- 
Pasi Pirhonen - upi(a)iki.fi - http://iki.fi/upi/

[Daniel Roesen]

On Sun, Jan 25, 2004 at 04:40:39PM +0200, Pasi Pirhonen wrote:
>  eth1: uploading firmware...
>  firmware_class.c:call_helper: firmware: /sbin/hotplug firmware add
>  eth1: firmware uploaded done, now triggering reset...
>  eth1: prism54_mib_init()
>  eth1: done with prism54_mib_init()! -- Client Managed mode
>  
>  from dmesg very much seems me like the fiwnware gets loaded? 
Uhm.... you are totally right. The FC1 kernels DO include the
firmware loader... I have no idea how I managed to think that
it doesn't. I thougth that I have inspected the kernel-source
RPM, but when doing this now, I clearly find CONFIG_FW_LOADER.

Thanks for pushing me into verifying my findings. :-)

>  This kernel is pure 2.4.22-1.2149.nptl which i pached with 
>  
>  patch-2.4-prism54-cvs-latest (Jan 10 on my disk)
>  
>  and made rediff to include that to SRPM build process and rebuild the
>  kernel RPM. 
Will try to do this too, although building an external RPM just
for the prism54 module would be cool. Given that the firmware
loader is in the FC1 kernel, this should be possible without
modifying the FC1 kernel RPM.


Best regards,
Daniel