| Author |
Message |
|
|
Post subject: madwifi
 Posted: Jul 26, 2008 - 02:47 PM
|
|
Joined: Dec 30, 2007
Posts: 108
Status: Offline
|
|
I ran smxi this morning and the madwifi stuff just dissapeared. I had another card and was able to reinstall it however just wondering if anyone else had problems. I'm not going to always have the availability of a "back-up" card.
Thanks |
|
|
| |
|
|
|
 |
|
|
|
Post subject:
Posted: Jul 26, 2008 - 03:28 PM
|
|
Joined: Jan 12, 2008
Posts: 289
Location: Ohio/USA
Status: Offline
|
|
If you installed a new kernel, that will always leave you with no madwifi driver -- you have to install it on the new kernel.
I ran d-u last night on my Eee PC which uses the madwifi driver (but not a new kernel) and it is working fine on wireless.  |
_________________
Intel X6800 on Intel D975XBX2, Nvidia 9600GT
sidux 2008-02 "Έρεβος" 64-bit on JFS filesystem
Asus Eee PC 4G / 701, sidux 2008-03 "Ουρέα"
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 26, 2008 - 04:15 PM
|
|
Joined: Nov 28, 2006
Posts: 4302
Status: Offline
|
|
smxi is supposed to rebuild the madwifi stuff, as long as you aren't using kernel metapackages. If you are, it's too complicated to try to automate that part, but if you are using the use initiated kernel install, it's always supposed to rebuild or reinstall all your currently installed kernel modules as part of the process.
To change metapackage status, start smxi with -N, and then select manual option, then continue. |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
Last edited by h2 on Jul 26, 2008 - 04:16 PM; edited 1 time in total
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 26, 2008 - 04:16 PM
|
|
Joined: Mar 29, 2007
Posts: 228
Location: München
Status: Offline
|
|
|
dibl wrote:
-- you have to install it on the new kernel
after a new kernel just :
Code:
m-a a-i madwifi
thats it. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 26, 2008 - 04:18 PM
|
|
Joined: Nov 28, 2006
Posts: 4302
Status: Offline
|
|
| actually, it's not it, because once you reboot, you've lost the connection, so you need to send the kernel to install to as well to m-a a-i. This is all automated in smxi, and of course users who want to learn all these little gotchas generally do so. |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 26, 2008 - 05:02 PM
|
|
Joined: Dec 02, 2006
Posts: 1909
Status: Offline
|
|
|
h2 wrote:
actually, it's not it, because once you reboot, you've lost the connection, so you need to send the kernel to install to as well to m-a a-i. This is all automated in smxi, and of course users who want to learn all these little gotchas generally do so.
I use madwifi and when I update the kernel, I use the smxi to automate all these things |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 26, 2008 - 08:29 PM
|
|
Joined: Jan 12, 2008
Posts: 289
Location: Ohio/USA
Status: Offline
|
|
|
h2 wrote:
This is all automated in smxi, and of course users who want to learn all these little gotchas generally do so.
Wow -- yes it is well-automated! I just updated to the new -12 kernel, and when I rebooted VOILA! there was wireless already working. Nice! Nothing for me to do but run vmware-config to rebuild the VMware Player module, and I'm 100% functional again. Marvelous! |
_________________
Intel X6800 on Intel D975XBX2, Nvidia 9600GT
sidux 2008-02 "Έρεβος" 64-bit on JFS filesystem
Asus Eee PC 4G / 701, sidux 2008-03 "Ουρέα"
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 26, 2008 - 09:03 PM
|
|
Joined: Dec 30, 2007
Posts: 108
Status: Offline
|
|
|
MucRonin wrote:
dibl wrote:
-- you have to install it on the new kernel
after a new kernel just :
Code:
m-a a-i madwifi
thats it.
Yes that's what I did but as h2 said I lost connection. I did have a backup card this time but I'm am going to re-configure some things to try to avoid it from happening again. Thanks. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 27, 2008 - 01:15 AM
|
|
Joined: Nov 28, 2006
Posts: 4302
Status: Offline
|
|
You need to build this in the old kernel, building the module to the new kernel, that's what is automated in smxi, and for that very reason, it does you no good after you reboot, it needs to do it all pre reboot.
Now if you use the manual kernel install (Not meta) method, and madwifi fails to build when you install the new kernel, to the new kernel, that's a bug, and you should report it in the smxi bug reports thread.
slh solved a lot of the major issues with modules though, most now are installed with the new kernel, whether or not you use metapackages, but some aren't, madwifi specifically, non free nvidia/fglrx, and vmware. Of these, vmware is the only one we (latino solved the fglrx/nvidia issue) haven't figured out how to get running from old kernel to new kernel while in old kernel. |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 27, 2008 - 05:14 AM
|
|
Joined: Dec 30, 2007
Posts: 108
Status: Offline
|
|
| OK I'll see what happens the next time. Thanks. |
|
|
| |
|
|
|
|
|
|
