• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / Kernel / Re: sheeva/dream 3.6.6 new kernel available on: March 22, 2013, 07:14:54 AM
I just downloaded your 3.8.4 kernel, which behaves much better on the guruplug server plus with the SD8686 wireless. I can now load the libertas_sdio module without errors. Alas, this gives me client mode only.

Any chance you can enable the LIBERTAS_THINFIRM module in the next builds ? I think that with this module enable, we might be able (with the appropriate thin firmware, and hostapd) to use the SD8686 equipped machines as APs (how well, I cannot say, but it seems to work for the XO project)...

Thanks.
2  Linux Stuff / Kernel / Re: sheeva/dream 3.6.6 new kernel available on: December 14, 2012, 09:22:50 PM
I'm a bit lost now. I'm attempting to get wifi working (station preferably, but I'll take client mode) on my guruplug server plus. Up until 3.5.3 (using cbxbiker61 kernels), this all worked without problems. Seems that as of 3.6, the LIBERTAS_UAP driver is just gone. Alas, after unblacklisting the libertas_sdio driver, even that fails to load the firmware (yes, I do have it in both /lib/firmware/mrvl and lib/firmware/libertas) on 3.6.10.

So, does the mwifiex driver work on the guruplug server plus, or is there some other way to get the wifi working  again ?

Or should I just forget about my guruplug and concentrate on my Raspi ?

TIA
3  Linux Stuff / Kernel / Re: 2.6.35.11 new kernel available on: February 14, 2011, 06:24:41 AM
How 'bout enabling support for CONFIG_DVB_USB and associated USB Tuners ?
4  Linux Stuff / Kernel / Re: NFS booting suddenly stops working (mount.nfs an incorrect mount option.....) on: July 13, 2010, 10:09:08 PM
Just in case anyone runs into this oddity, I've "solved" the problem. I rebuilt my NFS root filesystem with debootstrap, and everything worked again. At least until I altered the client /etc/fstab file with the following entry:

amanita:/usr/virtimages/plugroot       /       nfs     rw,nolock 0 0

Bam, same error again. When I comment out this line, everything works as expected. This used to work just fine, so I'm sort of wondering what changed in the handling of mounting filesystems at boot that  made this stop working. After all, this is same as given on the command line boot and delivered via DHCP. It just seems that the boot process is confused by this. Its a bit ugly without it, but luckily there are only a couple of fileservers here at home whcih could possibly hold the root filesystem for this "box"..
5  Linux Stuff / Kernel / NFS booting suddenly stops working (mount.nfs an incorrect mount option.....) on: July 09, 2010, 02:58:25 AM
I've been booting via NFS without troubles for some time. Now however, I'm unable to NFS boot *ANY* kernel, even previously working ones (ie the ones from sheeva.with-linux.com). I'm running Debian Sid/Squeeze. Now, no matter which kernel I'm NFS booting, I'm getting the following:

Code:
[    8.214746] scsi1 : usb-storage 1-1.1:1.0
[    8.220043] usbcore: registered new interface driver usb-storage
[    8.226117] USB Mass Storage support registered.
done.
Activating swap...done.
mount.nfs: an incorrect mount option was specified
Checking root file system...fsck from util-linux-ng 2.17.2
done.
mount.nfs: an incorrect mount option was specified
Loading kernel modules...done.
/etc/init.d/mtab.sh: 178: cannot create /etc/mtab: Read-only file system
Cleaning up ifupdown....
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux-ng 2.17.2
done.
Setting up networking....
Mounting local filesystems...can't create lock file /etc/mtab~343: Read-only file system (use -n flag to override)
failed.
Activating swapfile swap...done.
Cleaning up temporary files.../lib/init/bootclean.sh: 186: cannot create /tmp/.clean: Read-only file system
[    9.247259] scsi 1:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9909 PQ: 0 ANSI: 0
df: Warning: cannot read table of mounted file systems: No such [    9.262021] scsi 1:0:0:1: Direct-Access     Generic  STORAGE DEVICE   9909 PQ: 0 ANSI: 0
file or directory
Setting kernel variables ...done.
Configuring network interfaces...[    9.382591] sd 1:0:0:0: [sda] Attached SCSI removable disk
[    9.389365] sd 1:0:0:1: [sdb] 3964928 512-byte logical blocks: (2.03 GB/1.89 GiB)
[    9.398855] sd 1:0:0:1: [sdb] Write Protect is off
[    9.403734] sd 1:0:0:1: [sdb] Assuming drive cache: write through                       
[    9.416813] sd 1:0:0:1: [sdb] Assuming drive cache: write through                       
[    9.422954]  sdb: sdb1                                                                 
[    9.435062] sd 1:0:0:1: [sdb] Assuming drive cache: write through                       
[    9.441271] sd 1:0:0:1: [sdb] Attached SCSI removable disk                             
done.
Starting portmap daemon....
Starting NFS common utilities: statd failed!
Cleaning up temporary files.../lib/init/bootclean.sh: 186: cannot create /tmp/.clean: Read-only file system
/etc/init.d/bootmisc.sh: 63: cannot create /var/run/utmp: Read-only file system
startpar: service(s) returned failure: mtab.sh mountall-bootclean.sh nfs-common mountnfs-bootclean.sh bootmisc.sh ... failed!

I have no problem mounting the root filesystem R/W when booted from NAND+SD, so its not a server problem. I've even went as far as making an entirely new NFS root, with the same result.

I'm wondering if anyone has seen this, or if somehow there's somekind of bug in some underlying package in Sid/Squeeze that affects NFS root....
6  Linux Stuff / Kernel / Re: NFS booting hangs on firmware load on: July 05, 2010, 01:20:55 AM
Thanks, this works. In the meantime, I've managed to (re)build a 2.6.34 kernel from which I can NFS boot. But there's still something very strange going on. I've had the same problem with your kernel, and at first I thought it was something wrong in the kernel, but now I'm wondering.

I can only NFS boot on every other (i.e. 2nd) reboot. My  boot environment variables look like this:

Code:
nfsrootpath=/usr/virtimages/plugroot
nfsimage_name=guru/sheeva-2.6.34-uImage
filesize=29E148
fileaddr=2000000
ipaddr=192.168.141.152
serverip=192.168.141.22
nfsrootsrv=192.168.141.2
console_nfs=console=ttyS0,115200 mtdparts=:0x100000@0x000000(u-boot),0x300000@0x100000(uImage),0x1fc00000@0x400000(rootfs)rw
bootargs_nfs=root=/dev/nfs rw nfsroot=192.168.141.2:/usr/virtimages/plugroot
nfsinitrd_name=guru/uInitrd-2.6.34
initrdtftp=tftpboot 0x01100000 guru/uInitrd-2.6.34                                                                                                                 
bootcmd_nfs=run boottftp;run initrdtftp;setenv bootargs $(console_nfs) $(bootargs_nfs) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm 0x00800000 0x01100000         
boottftp=tftpboot 0x00800000 guru/uImage-2.6.34 
           

When I reset the plug, and type "run bootcmd_nfs" it will only reboot properly every second reboot/reset. Its getting the proper information via DHCP, but then somehow hangs in the middle of the boot process, trying to mount /.

 
Code:
eth0: link up, 100 Mb/s, full duplex, flow control disabled                                                                                                       
. OK                                                                                                                                                               
IP-Config: Got DHCP answer from 192.168.141.30, my address is 192.168.141.152                                                                                     
IP-Config: Complete:                                                                                                                                               
     device=eth0, addr=192.168.141.152, mask=255.255.255.0, gw=192.168.141.253,                                                                                   
     host=guruplug, domain=(none), nis-domain=(none),                                                                                                         
     bootserver=192.168.141.30, rootserver=192.168.141.2, rootpath=/usr/virtimages/plugroot                                                                       
Freeing init memory: 140K                                                                                                                                         
Loading, please wait...                                                                                                                                           
mount: mounting none on /dev failed: No such device
               sata_mv sata_mv.0: version 1.28                                                                                                                                   
sata_mv sata_mv.0: slots 32 ports 1                                                                                                                               
scsi1 : sata_mv                                                                                                                                                   
ata1: SATA max UDMA/133 irq 21                                                                                                                                     
ata1: SATA link down (SStatus 0 SControl F300)                                                                                                                     
Begin: Loading essential drivers ... done.                                                                                                                         
Begin: Running /scripts/init-premount ... done.                                                                                                                   
Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done.                                                                                     
IP-Config: eth0 hardware address 02:50:43:2e:7c:cf mtu 1500 DHCP RARP                                                                                             
IP-Config: eth0 guessed netmask 255.255.255.0                                                                                                                     
IP-Config: eth0 guessed broadcast address 192.168.141.255                                                                                                         
IP-Config: eth0 guessed nameserver address 192.168.141.22                                                                                                         
IP-Config: eth0 complete (from 192.168.141.22):                                                                                                                   
 address: 192.168.141.152  broadcast: 192.168.141.255  netmask: 255.255.255.0                                                                                     
 gateway: 0.0.0.0          dns0     : 192.168.141.22   dns1   : 0.0.0.0                                                                                           
 rootserver: 192.168.141.22 rootpath:                                                                                                                             
 filename  :                                                                                                                                                       
IP-Config: eth1 hardware address 02:50:43:51:7e:82 mtu 1500 DHCP RARP                                                                                             
IP-Config: eth1 guessed netmask 255.255.255.0                                                                                                                     
IP-Config: eth1 guessed broadcast address 192.168.141.255                                                                                                         
IP-Config: eth1 guessed nameserver address 192.168.141.22                                                                                                         
IP-Config: eth1 complete (from 192.168.141.22):                                                                                                                   
 address: 192.168.141.152  broadcast: 192.168.141.255  netmask: 255.255.255.0                                                                                     
 gateway: 0.0.0.0          dns0     : 192.168.141.22   dns1   : 0.0.0.0                                                                                           
 rootserver: 192.168.141.22 rootpath:                                                                                                                             
 filename  :                                                                                                                                                       
Begin: Running /scripts/nfs-premount ... done.                                                                                                                     
done.                                                                                                                                                             
Begin: Running /scripts/nfs-bottom ... done.                                                                                                                       
done.                                                                                                                                                             
Begin: Running /scripts/init-bottom ... done.                                                                                                                     
INIT: version 2.88 booting                                                                                                                                         
Using makefile-style concurrent boot in runlevel S.                                                                                                               
Starting the hotplug events dispatcher: udevdudev: starting version 157
     .                                                                                                                                                                 
Synthesizing the initial hotplug events...done.                                                                                                                   
Waiting for /dev to be fully populated...Bluetooth: Core ver 2.15                                                                                                 
NET: Registered protocol family 31                                                                                                                                 
Bluetooth: HCI device and connection manager initialized                                                                                                           
Bluetooth: HCI socket layer initialized                                                                                                                           
uap_probe: vendor=0x02DF device=0x9104 class=0 function=1                                                                                                         
uap_sdio mmc0:0001:1: firmware: requesting mrvl/helper_sd.bin                                                                                                     
uap_sdio mmc0:0001:1: firmware: requesting mrvl/sd8688_ap.bin                                                                                                     
dib0700: loaded with support for 14 different device-types                                                                                                         
dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware                                                                               
usb 1-1.3: firmware: requesting dvb-usb-dib0700-1.20.fw                                                                                                           
UAP FW is active                                                                                                                                                   
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2                                                                                                           
nfs: server 192.168.141.2 not responding, still trying                                                                                                             
nfs: server 192.168.141.2 not responding, still trying                                                                                                             
nfs: server 192.168.141.2 not responding, still trying                                                                                                                                                                                                                                                                             

If I then do a SysRq reboot, and run bootcmd_nfs again, it will boot properly. This behavior is reproducable. Any ideas ?
7  Linux Stuff / Kernel / Re: I can't load wifi driver on: July 01, 2010, 10:54:57 PM
I've been hitting this also. I've actually downloaded and unpacked a "virgin" source (2.6.34), applied the Marvell Kirkwood patches, and then built a kernel and modules (I cross compiled;  I dont think that matters, but maybe it does). Everything appeared to go fine, and I can boot (via TFTP/NFS) the kernel, but it seems pretty unhappy with all of the modules, because on each and every module load it spits out:

2.6.34 mod_unload modversions ARMv5 ' should be '2.6.34 preempt mod_unload ARMv5

Granted, uname -a returns:

Linux guruplug 2.6.34 #1 PREEMPT Thu Jul 1 09:47:26 CEST 2010 armv5tel GNU/Linux

I started out with a virgin kernel source, and there is no LOCALVERSION defined in the kernel configuration, so something is being done without our knowledge!
8  Linux Stuff / Kernel / Re: NFS booting hangs on firmware load on: June 30, 2010, 02:20:26 AM
The problem is not with NFS booting per se -- as you can see that works just fine (thanks to all the information in the posts). The problem is this:

Code:
uap_probe: vendor=0x02DF device=0x9104 class=0 function=1                                                                                                                                                                                       
uap_sdio mmc0:0001:1: firmware: requesting mrvl/helper_sd.bin                                                                                                                                                                                   
uap_sdio: probe of mmc0:0001:1 failed with error -1                                                                                 

I'm pretty sure that this is because the LIBERTAS_SDIO  is compiled into this particular kernel, and I'm normally blacklisting it, and using the uap8xxx loadable module.

I was really hoping I wasn't going to have to compile my own kernels, but it looks as though I would have to. The standard debian sid/squeeze kernel does not have CONFIG_IP_PNP set, so its not possible to NFS boot it.

The problem above is that the kernel just hangs at this point, and never continues.....
9  Linux Stuff / Kernel / NFS booting hangs on firmware load on: June 29, 2010, 10:09:18 PM
I've managed to get my GPS+ to boot via NFS, but its hanging after it actually mounts its root file system at the stage where its attempting to load firmware:

Code:
eth0: link up, 100 Mb/s, full duplex, flow control disabled                                                                                     
. OK                                                                                                                                           
IP-Config: Got DHCP answer from 192.168.141.30, my address is 192.168.141.152                                                                   
IP-Config: Complete:                                                                                                                           
     device=eth0, addr=192.168.141.152, mask=255.255.255.0, gw=192.168.141.253,                                                                 
     host=guruplug, domain=whack.me, nis-domain=(none),                                                                                       
     bootserver=192.168.141.30, rootserver=192.168.141.2, rootpath=/usr/virtimages/plugroot                                                     
libertas: can't load helper firmware                                                                                                           
libertas: failed to load helper firmware                                                                                                       
libertas_sdio: probe of mmc0:0001:1 failed with error -2                                                                                       
Looking up port of RPC 100003/2 on 192.168.141.2                                                                                               
Looking up port of RPC 100005/1 on 192.168.141.2                                                                                               
VFS: Mounted root (nfs filesystem) on device 0:12.                                                                                             
Freeing init memory: 140K                                                                                                                       
NET: Registered protocol family 10                                                                                                             
NET: Registered protocol family 5                                                                                                               
uap_probe: vendor=0x02DF device=0x9104 class=0 function=1                                                                                       
uap_sdio mmc0:0001:1: firmware: requesting mrvl/helper_sd.bin                                                                                   
uap_sdio: probe of mmc0:0001:1 failed with error -1                                                                                             

The root filesystem is a copy of whats currently installed and working (Debian SID kernel 2.6.32-5-kirkwood) on the sd card (I'm normally booting via NAND, with the root filesystem on the SD). I'd really like to get this working, as this would allow me to easily test new kernels before trying to flash them....

This is with the 2.6.34 kernel from http://sheeva.with-linux.com/sheeva/
Pages: [1]