Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
Interesting. my trunk 1945 runs perfectly.. however I compiled trunk 2005 and get a kernel panic during the actual astlinux image boot.. so now im compiling branch 0.6 to see if I get the same thing.. My panic occurs after it verifies the astlinux.run image then goes to boot then dies after it says 172k kernel memory freed.. Kernel panic - not syncing is all I get. This is running on a via 3R80 board.. I compile it as a generic i586 target.. Again trunk 1945 runs fine. trunk 2005 doesn't.. and im compiling branch now. -Christopher From: IT Services [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2008 10:31 AM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] 0.6.1 MODOPTS ignored ? Using physdiskwrite gives me a disk which results in a kernel panic on boot. Running astinstall from the livecd gives me an unbootable partition (though fdisk claims its bootable flag is set). Still failing to get Astlinux running ona single HD system. Tom On Wed, Oct 15, 2008 at 3:36 PM, Chris Abnett [EMAIL PROTECTED] wrote: You can install on a desktop using the physdiskwrite utility to a hard drive just like you would a CF card. so in effect your hard drive would just have a 1 gig image on it.. You can still select to use whichever file system method you want.. Keydisk or UnionFS... -Christopher - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
I have the same kernel panic at the same stage, after kernel memory freed. On Thu, Oct 16, 2008 at 3:51 PM, Chris Abnett [EMAIL PROTECTED] wrote: Interesting… my trunk 1945 runs perfectly.. however I compiled trunk 2005 and get a kernel panic during the actual astlinux image boot.. so now im compiling branch 0.6 to see if I get the same thing…. My panic occurs after it verifies the astlinux.run image then goes to boot then dies after it says 172k kernel memory freed.. Kernel panic – not syncing is all I get… This is running on a via 3R80 board.. I compile it as a generic i586 target…. Again trunk 1945 runs fine… trunk 2005 doesn't.. and im compiling branch now… - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
I was seeing that last night with # 2010. I figured that it was the fix I committed as 2009... but if you all were running 2005 and seeing it as well, then it clearly wasn't that. I'm running 2014 right now, and it's booting reliably. Can someone else give it a try? -Philip Tom Chadwin wrote: I have the same kernel panic at the same stage, after kernel memory freed. On Thu, Oct 16, 2008 at 3:51 PM, Chris Abnett [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Interesting… my trunk 1945 runs perfectly.. however I compiled trunk 2005 and get a kernel panic during the actual astlinux image boot.. so now im compiling branch 0.6 to see if I get the same thing…. My panic occurs after it verifies the astlinux.run image then goes to boot then dies after it says 172k kernel memory freed.. Kernel panic – not syncing is all I get… This is running on a via 3R80 board.. I compile it as a generic i586 target…. Again trunk 1945 runs fine… trunk 2005 doesn't.. and im compiling branch now… - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
Ok I compiled trunk 2014 and it runs fine, trunk 2005 kernel panics branch 0.6 kernel panics... at least in my environment which is a via 3R80 motherboard.. not sre what it does against other platforms... -Christopher -Original Message- From: Philip Prindeville [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2008 1:16 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] 0.6.1 MODOPTS ignored ? I was seeing that last night with # 2010. I figured that it was the fix I committed as 2009... but if you all were running 2005 and seeing it as well, then it clearly wasn't that. I'm running 2014 right now, and it's booting reliably. Can someone else give it a try? -Philip Tom Chadwin wrote: I have the same kernel panic at the same stage, after kernel memory freed. On Thu, Oct 16, 2008 at 3:51 PM, Chris Abnett [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Interesting. my trunk 1945 runs perfectly.. however I compiled trunk 2005 and get a kernel panic during the actual astlinux image boot.. so now im compiling branch 0.6 to see if I get the same thing.. My panic occurs after it verifies the astlinux.run image then goes to boot then dies after it says 172k kernel memory freed.. Kernel panic - not syncing is all I get. This is running on a via 3R80 board.. I compile it as a generic i586 target.. Again trunk 1945 runs fine. trunk 2005 doesn't.. and im compiling branch now. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
Darrick Hartman wrote: Martin Rogers wrote: Darrick thanks for the reply. I tried editing /etc/modprobe.conf originally (setting the filesystem to RW etc) but the changes do not make it past a reboot. I also tried storing one on the keydisk in case this could be used to replace the etc one - without success, it does not get copied over. Where is the fundamental copy of the file - it is probably this one I should be editing. With unionfs, you don't (and shouldn't) modify the read-write status of the system. That's why the changes don't make it past a reboot. If you edit a file, the changed file is written to the unionfs partition and when seen by the OS, that file is used instead of the file on the image. (so if /etc/modprobe.conf exists in the image AND /oldroot/mnt/asturw/etc/modprobe.conf exists, the latter will be used). Darrick Darrick, /oldroot/mnt/ does not exist on my system. Are you suggesting that I should create /oldroot/mnt/asturw/etc/modprobe.conf? What is the best practice way of adding to modprobe.conf. If I didn't know about this filesystem structuring (oldroot etc) how would I find out - e.g. is there any documentation which indicates how to create modprobe.conf settings on Astlinux, or details what files get overwritten from the keydisk. How for example should I kmow that some /etc files (e.g. rc.conf and zaptel.conf) are read from the keydisk and used by the system instead of the image ones but yet others (like /mnt/kd/etc/modprobe.conf) are not. Do you consider that the the problem with MODOPTS not being picked up is a bug which needs to be raised? Thanks Mart - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
Do you consider that the the problem with MODOPTS not being picked up is a bug which needs to be raised? It is a bug. Philip has committed a fix to trunk which I have not had time to pickup and use in the 0.6 branch. I know how busy people are, but is there any timescale on this? I still haven't managed to get this TDM410P working with Astlinux, and I think it might be because MODOPTS is not allowing me to set wctdm24xxp OPERMODE=UK. Is there any documentation on how I should go about installing 0.6.1 on a single HDD based machine with no second storage device? I have to show the TDM410P can work with Astlinux before we can buy some CF based hardware to run it, and at the moment, I am tying myself in knots trying to work out how to install on a generic i586 desktop. Thanks Tom PS Sent from alternate account to avoid corporate monstrous sig file. I forwarded the objections I received from this list to my boss, and our organization is now going to go back to our lawyers to sort something more suitable. So, thanks - it gave me the leverage to try to do something about the damned thing. Only worry is that this particular legal firm not only has large sig files itself, but also prepends legalese onto users' emails. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
Martin Rogers wrote: Darrick Hartman wrote: Martin Rogers wrote: Darrick thanks for the reply. I tried editing /etc/modprobe.conf originally (setting the filesystem to RW etc) but the changes do not make it past a reboot. I also tried storing one on the keydisk in case this could be used to replace the etc one - without success, it does not get copied over. Where is the fundamental copy of the file - it is probably this one I should be editing. With unionfs, you don't (and shouldn't) modify the read-write status of the system. That's why the changes don't make it past a reboot. If you edit a file, the changed file is written to the unionfs partition and when seen by the OS, that file is used instead of the file on the image. (so if /etc/modprobe.conf exists in the image AND /oldroot/mnt/asturw/etc/modprobe.conf exists, the latter will be used). Darrick Darrick, /oldroot/mnt/ does not exist on my system. Are you suggesting that I should create /oldroot/mnt/asturw/etc/modprobe.conf? What is the best practice way of adding to modprobe.conf. If /oldroot/mnt does not exist on your file system, then something is very wrong. You're either not using unionfs or something stranger than that. What do you see when you issue the 'mount' command? If I didn't know about this filesystem structuring (oldroot etc) how would I find out - e.g. is there any documentation which indicates how to create modprobe.conf settings on Astlinux, or details what files get overwritten from the keydisk. How for example should I kmow that some /etc files (e.g. rc.conf and zaptel.conf) are read from the keydisk and used by the system instead of the image ones but yet others (like /mnt/kd/etc/modprobe.conf) are not. There is some documentation on unionfs. All you really need to know about unionfs is you can have multiple mount points, 'unionized' into one mount point with a mix of read-only and read-write areas. For Astlinux, when using unionfs, you will see / as type unionfs mounted rw using the two different mount points for the union. The rw mount point is /oldroot/mnt/asturw. The ro mount point is one of two locations, depending on how much system ram you have. If there is less than 256mb of system ram OR if the noram flag is set in the KCMD line (in astlinux-xxx.run.conf), the read-only 'image' remain on a squashfs image mounted loopback on what should be /oldroot/image. If you have more than 256mb and noram is not set, the read-only 'image' is copied to a ramfs location mounted as /oldroot/mnt/asturo. If you look at the mount line for unionfs, it should show something similar: none on / type unionfs (rw,dirs=/oldroot/mnt/asturw=rw:/oldroot/mnt/asturo=ro) That would be all on one line, except it's being wrapped in the email client. Do you consider that the the problem with MODOPTS not being picked up is a bug which needs to be raised? It is a bug. Philip has committed a fix to trunk which I have not had time to pickup and use in the 0.6 branch. Darrick - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
Martin Rogers wrote: Darrick thanks for the reply. I tried editing /etc/modprobe.conf originally (setting the filesystem to RW etc) but the changes do not make it past a reboot. I also tried storing one on the keydisk in case this could be used to replace the etc one - without success, it does not get copied over. Where is the fundamental copy of the file - it is probably this one I should be editing. With unionfs, you don't (and shouldn't) modify the read-write status of the system. That's why the changes don't make it past a reboot. If you edit a file, the changed file is written to the unionfs partition and when seen by the OS, that file is used instead of the file on the image. (so if /etc/modprobe.conf exists in the image AND /oldroot/mnt/asturw/etc/modprobe.conf exists, the latter will be used). Darrick - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
[Astlinux-users] 0.6.1 MODOPTS ignored ?
Hi This is a followup to a recent thread on modprobe which did not conclude in any resolution. It appears that setting MODOPTS in /mnt/kd/rc.conf are ignored. I am using the astlinux-0.6.1-via.img.gz image. I have set the following line in the /mnt/kd/rc.conf to set the opermode to UK and to turn debugging for the module on. MODOPTS=wctdm:opermode=UK wctdm:debug=1 This line appears also in /etc/rc.conf after a restart indicating it was sucessfully soaked up from the keydisk. However, after a restart : /sys/module/wctdm/parameters/opermode =FCC /sys/module/wctdm/parameters/debug =0 which looks to me as if the two flags were not picked up in the startup processing. Using a single parameter such as MODOPTS=wctdm:debug=1 does not have any effect either. Is this a bug, or am I missing something. Thanks Mart - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
Mart, This isn't an area that I've had to use so we may need to adjust it. Kristian may need to shed a little light on this too. MODOPTS are supposedly set as follows: (from /etc/rc) if [ -n $MODOPTS ]; then for i in $MODOPTS; do MOD=`echo $i | cut -d: -f1` OPT=`echo $i | cut -d: -f2` echo options $MOD $OPT /tmp/etc/modprobe.conf done fi However, it doesn't look like that is ever used since /etc/modprobe.conf is hard coded. For your purposes, you could edit the existing modprobe.conf file and replace it with the options you want. The changes would be on unionfs and overwrite the other file. After we've determined the correct way to handle this, I'll walk you through reversing the process. Darrick Martin Rogers wrote: Hi This is a followup to a recent thread on modprobe which did not conclude in any resolution. It appears that setting MODOPTS in /mnt/kd/rc.conf are ignored. I am using the astlinux-0.6.1-via.img.gz image. I have set the following line in the /mnt/kd/rc.conf to set the opermode to UK and to turn debugging for the module on. MODOPTS=wctdm:opermode=UK wctdm:debug=1 This line appears also in /etc/rc.conf after a restart indicating it was sucessfully soaked up from the keydisk. However, after a restart : /sys/module/wctdm/parameters/opermode =FCC /sys/module/wctdm/parameters/debug =0 which looks to me as if the two flags were not picked up in the startup processing. Using a single parameter such as MODOPTS=wctdm:debug=1 does not have any effect either. Is this a bug, or am I missing something. Thanks Mart - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com Small Business IT Specialists - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
Seems like /etc/modprobe.conf should be a link to /tmp/etc/modprobe.conf ... Darrick Hartman wrote: Mart, This isn't an area that I've had to use so we may need to adjust it. Kristian may need to shed a little light on this too. MODOPTS are supposedly set as follows: (from /etc/rc) if [ -n $MODOPTS ]; then for i in $MODOPTS; do MOD=`echo $i | cut -d: -f1` OPT=`echo $i | cut -d: -f2` echo options $MOD $OPT /tmp/etc/modprobe.conf done fi However, it doesn't look like that is ever used since /etc/modprobe.conf is hard coded. For your purposes, you could edit the existing modprobe.conf file and replace it with the options you want. The changes would be on unionfs and overwrite the other file. After we've determined the correct way to handle this, I'll walk you through reversing the process. Darrick Martin Rogers wrote: Hi This is a followup to a recent thread on modprobe which did not conclude in any resolution. It appears that setting MODOPTS in /mnt/kd/rc.conf are ignored. I am using the astlinux-0.6.1-via.img.gz image. I have set the following line in the /mnt/kd/rc.conf to set the opermode to UK and to turn debugging for the module on. MODOPTS=wctdm:opermode=UK wctdm:debug=1 This line appears also in /etc/rc.conf after a restart indicating it was sucessfully soaked up from the keydisk. However, after a restart : /sys/module/wctdm/parameters/opermode =FCC /sys/module/wctdm/parameters/debug =0 which looks to me as if the two flags were not picked up in the startup processing. Using a single parameter such as MODOPTS=wctdm:debug=1 does not have any effect either. Is this a bug, or am I missing something. Thanks Mart - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] 0.6.1 MODOPTS ignored ?
Can someone please pick up commit # 2009 and test it? Thanks. Philip Prindeville wrote: Seems like /etc/modprobe.conf should be a link to /tmp/etc/modprobe.conf ... Darrick Hartman wrote: Mart, This isn't an area that I've had to use so we may need to adjust it. Kristian may need to shed a little light on this too. MODOPTS are supposedly set as follows: (from /etc/rc) if [ -n $MODOPTS ]; then for i in $MODOPTS; do MOD=`echo $i | cut -d: -f1` OPT=`echo $i | cut -d: -f2` echo options $MOD $OPT /tmp/etc/modprobe.conf done fi However, it doesn't look like that is ever used since /etc/modprobe.conf is hard coded. For your purposes, you could edit the existing modprobe.conf file and replace it with the options you want. The changes would be on unionfs and overwrite the other file. After we've determined the correct way to handle this, I'll walk you through reversing the process. Darrick Martin Rogers wrote: Hi This is a followup to a recent thread on modprobe which did not conclude in any resolution. It appears that setting MODOPTS in /mnt/kd/rc.conf are ignored. I am using the astlinux-0.6.1-via.img.gz image. I have set the following line in the /mnt/kd/rc.conf to set the opermode to UK and to turn debugging for the module on. MODOPTS=wctdm:opermode=UK wctdm:debug=1 This line appears also in /etc/rc.conf after a restart indicating it was sucessfully soaked up from the keydisk. However, after a restart : /sys/module/wctdm/parameters/opermode =FCC /sys/module/wctdm/parameters/debug =0 which looks to me as if the two flags were not picked up in the startup processing. Using a single parameter such as MODOPTS=wctdm:debug=1 does not have any effect either. Is this a bug, or am I missing something. Thanks Mart - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
