Name and extension of the file to import, specified as a character vector or a string scalar.If importdata recognizes the file extension, it calls theMATLAB helper function designed to import the associated file format (suchas load for MAT-files or xlsread forspreadsheets). Otherwise, importdata interprets the file as adelimited ASCII file.For ASCII files and spreadsheets, importdata expectsto find numeric data in a rectangular form (that is, like a matrix).Text headers can appear above or to the left of the numeric data,as follows. Data from the file, returned as a matrix, multidimensional array,or scalar structure array, depending on the characteristics of thefile. Based on the file format of the input file, importdata callsa helper function to read the data.
When the helper function returnsmore than one nonempty output, importdata combinesthe outputs into a struct array.This table lists the file formats associated with helper functionsthat can return more than one output, and the possible fields in thestructure array, A. File FormatPossibleFieldsClassMAT-filesOne field for each variableAssociated with each variable.ASCII files and Spreadsheetsdata textdata colheaders rowheadersFor ASCII files, data contains a double array.Other fields contain cell arrays of character vectors. Textdata includesrow and column headers.For spreadsheets, each fieldcontains a struct, with one field for each worksheet.Imagescdata colormap alphaSee.Audio filesdata fsSee.The MATLAB helper functions for most other supported fileformats return one output. For more information about the class ofeach output, see the functions listed in.If the ASCII file or spreadsheet contains either column or rowheaders, but not both, importdata returns a colheaders or rowheaders fieldin the output structure, where.
I tried this and my system booted super fast. I followed this howto exactly, but something went horribly wrong. When I boot up, the GDM is loaded with like 16 bit color or something, and it looks all ugly. When I try to log in, I get an error message saying my 'session lasted less than 10 seconds, if I didn't log out then there could be an installation problem or I may be out of diskspace. Try logging in with the failsafe session. View details /.xsession-errors.' I tried logging in with the failsafe session, but the same message comes up.When I switch to terminal and cat.xsession-errors, I get some stuff/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp/etc/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w /var/log/wtmp - (bunch more stuff)Then it has a bunch of errors about IceTrans.IceTransTransNoListen: unable to find transport: tcpIceTransmkdir: ERROR: euid!= 0,directory /dev/X will not be created.And about 10 more lines of IceTrans errors.Help please!EDIT: I didn't see the end part about adding stuff to grub.
Will try that now.Ok I edited the boot stuff and it still happens. Maybe something else is wrong with my system?
1) Look at the content of /etc/initng/net/net.i2) Read the relevant socuments in /usr/share/initng3) Edit net.i file4) Runsudo ng-update add net/net default5) Post your net.i file here if you had success!Step 2 is deficient. No directory under /usr/share/ called initng. Must look under /usr/share/doc/initng.And wireless doesn't start up automatically. I need to issue the following command after startup to get it working:sudo ifup eth1and then it works. Will look at how to get this integrated in one of the.i files in a couple of weeks. I've gotta ask. How many times do you reboot your Linux box that you really need to shave 30-40 seconds off the boot time?'
Why does anyone climb a mountain? Because it's there!' 'Incoming missile! Is the linux computer still rebooting? I knew I should have followed that InitNG thread!' :pWe always want a faster boot!:p LOLSometimes it's very handy, when I've turned my pc off to go to bed, but I've forgotten to print some documents, it's faster;) I managed to get from grub to the login screen in 15-18 seconds, after logon, it takes 4-8 sec to load everything; the panel, nautilus, (gaim). I'm going to try and install this after upgrading to Breezy this afternoon, but first a question or two:1) What is Jackd and is it necessary?
I don't see it being used on my current Hoary install even though the binary for it is installed.2) What is coldplug? How/why is it different to hotplug?3) Can I leave ACPI enabled? Is it likely to work? I'm on a laptop.Thanks!1) Dunno. Didn't need to fiddle with this.
Sound works for me.2) Dunno3) Left it enabled on my laptop. Suspend to RAM works just as well as it did before INITNG. I've gotta ask. How many times do you reboot your Linux box that you really need to shave 30-40 seconds off the boot time?' Why does anyone climb a mountain?
Because it's there!' 'Incoming missile! Is the linux computer still rebooting? I knew I should have followed that InitNG thread!' :pI usually boot up several times a day, considering it's a laptop. On a server, or even a workstation, I wouldn't be too concerned, especially since InitNG still needs some work.
I can't wait to give this a try on my laptop though. Why do you need to boot up a laptop several times a day? Is ACPI not working for you?Pretty much. I fixed my DSDT so that I can get my battery status, and hibernate was working out of the box. Suspend to ram would suspend fine, but the screen stayed black after resuming, and when I tried to fix it, I broke hibernate as well.
I don't care too much about hibernate because it took almost as long to resume as a fresh boot. But yes, if I could get suspend to work properly then I wouldn't be shutting my laptop down very much, although a faster boot would still be welcome. How stable is this now? I'm on my like 6th install of breezy, more of hoary, and I've got what I want out of it finally, except for ripping and burning archival dvds. I don't want to set it to boot faster and loose anything.I wouldn't suggest putting InitNG on 'production' machines just yet. You'd better wait for it to enter stable status. Having everything working with no fuss is more important that cutting those 20-30 sec.
However, even if you installed it and something went wrong, you can always boot the traditional way - just use your normally chosen option in Grub menu. Hufff, to many steps. Can't do i think. Any alternatives?install InitNGJust one step.;););) If you run into trouble, you can try the original - I think temcats version is very nice, very detailed and pretty much works just because it's so detailed. Other alternative would be to wait until it gets included in the default install of Ubuntu (I believe making boot process faster was goal for Breezy, but didn't get included, not sure about Dapper, after all its main goal is stability).EDIT: Of course, unless someone packs this into single script / makes a deb package.
Thanks for your very well worded and easy-to-use howto, temcat. I've tried it in a virtual machine first, and it worked perfectly, turning a 53 second boottime into a 38 second one. This encouraged me to try it on my two physical machines (laptop and workstation)They were both largely successful, but it seems a few modules fail to load. On my laptop, my wireless card isn't loaded at all. (the device isn't initialized, I don't see it in network management or with 'ifconfig -a')On my workstation, there seems to be a problem with Portmapper. I have a couple of NFS shares in my fstab which I automatically mount at boottime.
With InitNG however, they don't. When I try to mount them manually, it takes a really, really long time (like 5 minutes per mount). This led me to conclude a problem with portmap. I tried to install this on mine. I'm on an amd64 machine so there wasn't a deb but I downloaded the latest source and created a deb by using checkinstall. Everything installed just fine but I get this when it boots.
'initngcommon.c', loadtoactive:08:05:46 - line:105 FAIL: loadtoactive(default): Can't get service!SEGFAULTED!Anyone have any dieas? I'm not expert, so I'm pretty stumped. Has anyone successfully used this on a 64 bit system? A comment here (sounds like people are using it on amd64. I got it working now. This is what I did.I downloaded-x initng0.3.3-1.dsccd initng-0.3.3/dpkg-buildpackage -rfakerootThat gave me a.deb file to install. Once I uninstalled my previous one and installed this one things came up just fine (except for wireless.
I will have to look at that). Excellent tutorial!, had nearly no troubles.The only thing that I am stuck on is getting my fglrx drivers to work. I have an ATI radeon 9600xt and followed this (tutorial to install the drivers which used the module-assistant.I don't know much about loading modules but when I booted in with init.d the drivers worked 100%, but with initNG fglrxinfo displays correct information, glxgears work fine too, but apps like fglglxgears and ppracer display FGL errors and try and process the graphics with the CPU and lags.Any help would be good. Booting with this method makes my sound break sometimes.
Sometimes there is no sound at all and sometimes everything that uses ALSA plays super fast. Like chipmunks talking kind of fast.Sound card is an onboard ESS Allegro card in my laptop.Btw is anybody else getting error messages when they have a terminal window open?
Thanks a lot for the great HOWTO. I need help with setting up InitNG to do one more thing that my normal boot does.I followed this HOWTO: order quiet down my PC.What I need to do now is adapt the init.d startup script given in that HOWTO to work with initNG.I tried to write a script 'daemon/fancontrol' and add it to InitNG but it didn't work. I'm sure one of you experts could write up an initNG script in seconds by looking at that init.d script.Any help is greatly appreciated. I've got still some problems with ACPI though.I get those errors on boot time:FATAL: Error inserting asusacpi (/lib/modules/2.6.12-9-386/kernel/drivers/acpi/asusacpi.ko): No such deviceFATAL: Error inserting toshibaacpi (/lib/modules/2.6.12-9-386/kernel/drivers/acpi/toshibaacpi.ko): No such deviceBut I don't know if these modules are really needed by my system anyway?The ibm module gets loaded.At least I encountered no misbehaviour so far.Neither have i, but i would like to remove those errors. I have an ibm and the module is loaded alright, but i just hate errors. And it would increase mu boot speed about a nano second.:DIdeas anyone?EDIT: GOT IT!
Matlab Read Files In Folder
Thax for this last post. I should of read all the posts. Hi guys!The alioth packages are created by me. It's nice to see that you are quite happy, but I have to mention something: If you write new scripts please send them to the Initng mailinglist (initng@initng.thinktux.net) and Initng will ship these scripts with the next release.If you find bugs, report them on and we will try to fix the bug upstream.If you want to talk to us, come to #initng on freenode.If you have a problem with the Debian package (not with Initng) you can drop me a mail if you want (but ask here first;) ). You'll find my address on the alioth site.You can drop me a comment in my blog anyway, if you want.ByeTriggerPS: I will release a package for 0.4.0 tonight.
Ok I think I understand how to edit the config files for this, but I can't work out which extra dependency is needed to fix things. My eth1 is not being brought up properly at the moment, requiring a:sudo ifup eth1after boot to get me on the net properly.
Can anyone suggest how I can work out what I need to add to the eth dependencies so that it will load correctly first time?Relevant info:eth0 is onboard network on nforce moboeth1 is add in intel card as the onboard tends to overheat during summer. I've gotta ask. How many times do you reboot your Linux box that you really need to shave 30-40 seconds off the boot time?' Why does anyone climb a mountain?
Because it's there!' 'Incoming missile! Is the linux computer still rebooting? I knew I should have followed that InitNG thread!' :pI'm not alone to getting tired of these twisted ideas that just because Linux is somewhat stable (or rather Was stable), then boot time is not an issue.There are those, like me, who actually turn off the computer while not using it (sleeping is one good reason), to save energy and money. Open your eyes. 24/7 usage was leet 10 years ago.But the fact is that a new init system can fix systematic problems that we've had for years now, by that, initng is truly one giant step ahead.
I'm quite susprised no one has replaced the old init long ago.To me, this is easily a nominee for lpoty - linux project of the year;)O. Thank you.Panasonic Toughbook CF-45266Mhz160MB RAMFrom Grub to LoginWithout InitNG 1:10with InitNG 0:48There's a newer version out that seems to work much better. It's available through SVNGet the latest versionsvn checkout to a bug in the 0.4.2 release tarball, it might be necessary to run./autogen.sh before you run./configure./configure is atomatically invoced by./autogen.sh, but if you want to passadditional oprions to configure eg -with-splash, you need to run configure again.To run autogen.sh, you need to have automake, autoconf, and libtool installed.To get it working on my laptop I had to:ng-update del daemon/acpid. Tried to install from svn and got an error:$ sudo dpkg -i initng0.42-1i386.debSelecting previously deselected package initng.(Reading database. 127505 files and directories currently installed.)Unpacking initng (from initng0.42-1i386.deb).dpkg: error processing initng0.42-1i386.deb (-install):trying to overwrite `/etc/hotplug/net.agent', which is also in package hotplugdpkg-deb: subprocess paste killed by signal (Broken pipe)Errors were encountered while processing:initng0.42-1i386.debany idea what this net.agent is? New version (of InitNG out. Trying it out now.
Here are the changes that need to be made with your initial post temcat:Point 1: New link location here (2: Update with this:sudo dpkg -i initng0.4.0-1i386.debPoint 3: Not needed anymorePoint 4: Should stay.Point 5: Kdm already setup (step unneeded)Point 6: Coldplug already setup (step unneeded)Point 7: Only checked 7.3: Still needed.Point 8: Still required.Point 9: Still the same.Can confirm that this worked. Ok guys, 0.4.4-2 is out - try this one. Maybe you should read my blog entry before installing: should now start Hal automatically (0.4.4-1 didn't do it) - please forgett the hald.i script and remove it from your runlevels.You slightly need to modify dbus.i. Open it and replace 'DAEMON=/usr/bin/dbus-daemon-1' with 'DAEMON=/usr/bin/dbus-daemon'.If you have problems with the nVidia/fglrx/.
Module add the following at the end of system/initial.i: '/sbin/lrm-manager -quick'Please tell me if my proposed fixes work - I'm on Debian Sid and not Ubuntu.If you have any other problems: Tell me here.If you have.i files which are not shipped by the package please mail them to mailinglistenATonline.de. I will add them upstream. In gdm.i and instant-gdm.i the path should be /usr/sbin/gdm instead of /usr/bin/gdm. In laptop-mode.i I put /usr/sbin/laptop-mode start instead of laptopmode.Gr, why can't Ubuntu use the Debian paths? I'll investigate if I can find a solution for this.hald seems to be running.:)That is what I needed to do.Still can't get hald to work though.Are you sure you have the latest dbus.i installed?It should contain these lines, which start hal:if -d $EVENTDIR ; thenrun-parts -arg=start $EVENTDIRfi. Doesn't seem to work on amd64.
I tried everything from compiling 0.3.3 0.3.5 and even 0.4.0. They all segfault. The deb magic posted some pages before doesn't work either. Is there something I do wrong or does initNG simply not work on my platform?Edit: Got it working, but reboot causes my BIOS to stop booting again without pushing the reset button.Now I got a package for AMD64 on Alioth - maybe you want to test it.If it doesn't work and you want the problem to be solved open a bug on http://bugzilla.initng.thinktux.net. Just tried that, and it fixed the hang with laptop-mode. Now everything seems to be started, but its still hanging.
Oddly enough, I can get to TTY2-6, but the first one just hangs there after everything is done-no prompt, no 'Runlevel default up in X seconds', nothing.:(You will never get a login on tty1 per default - but if ou have no 'Runlevel default up in X seconds' something is wrong.Which service fails? Login on tty2 and have a look at 'ngc -s'.also is it me or are shutdown times much faster as wellFor sure they are - Initng stops services parallel if possible. SysVinit doesn't. You will never get a login on tty1 per default - but if ou have no 'Runlevel default up in X seconds' something is wrong.Which service fails?
Login on tty2 and have a look at 'ngc -s'.Yes, but tty1 should be launching GDM, correct? It just hangs there. And I forgot to add to the previous post, I did just what you suggested and checked ngc -s, and didn't see anything that had failed to start.EDIT:OK, I was stupid and forgot to add GDM to the startup, which is why it wasnt starting. I did that, and it worked fine. Still lots of errors (CPU frequency scaling, HAL, and wireless not working), but I'll play with those a bit later and see what I can get going.
Don't forget to edit daemon/dbus.i as proposed above to get dbus/hal working.Got it, that fixed the HAL error.So, problems remaining:1) CPU Scaling. I did the fix mentioned in the HOWTO, and it now works, but is throwing all sorts of errors at the start and adding about 8-10 seconds to the boot time as it times out.
Has anyone gotten CPU scaling to work on 4.4?2) Wireless. Eth1 is my primary connection (wireless), and is static. I setup the eth1.i file as it was on the Gentoo forums (linked to in the post about setting up eth1 for DHCP), but it won't work. It's configured on boot, and when I open the network config tool, everything is as it should be (SSID, WEP key, IP address, gateway, DNS, etc), but it's still not working.
It's seeing the access point, but won't connect despite my tinkering. I also made sure that eth1 is set as the default gateway device, to no avail.
An ifconfig eth1 while in an InitNG boot is returning this:eth1 Link encap:UNSPEC HWaddr 00-02-8A-78-71-CF-00-00-00-00-00-00-00-00-00-00inet addr:192.168.7.63 Bcast:192.168.7.255 Mask:255.255.255.0UP BROADCAST RUNNING MULTICAST MTU:2312 Metric:1RX packets:153 errors:1975 dropped:0 overruns:0 frame:1975TX packets:0 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:100RX bytes:9753 (9.5 KiB) TX bytes:0 (0.0 b)Interrupt:11 Base address:0x8000Link encap should be Ethernet and the HW Address clearly shouldn't have all those extra zeroes on the end. Any idea whats going on?
Ok, I discovered the ngc command. Maybe you can get the splash working maybe not. I followed the directions for InitNG - it shaves off more than 10 secs off my startup time!!I have a strange problem though:Each time I start a console (konsole, gnome-terminal or even xterm), I get an error message 'Unable to launch child process'. KDE su complains 'the program su is not found' 'Please check your PATH'.In KDM/GDM, if I select the 'failsafe terminal' option, it immediately exits back to KDM/GDM.So, I'm basically unable to get the command line!!Has anyone else faced the same problems? Hi,I have finally found the time to try this out, however I have run into a problem and cannot boot using InitNG.
I have Ubuntu using 2 partitions: one partition for / and one partition for /home/. Both partitions are ReiserFS. Here is the error I get when booting:Target filesystem does not have /sbin/initngI don't understand this error because.YES IT DOES. I have checked and everything has been installed correctly according to this HowTo. My GRUB configuration for InitNG looks like this:title Ubuntu, kernel 2.6.12-10-k7 (InitNG)root (hd0,3)kernel /boot/vmlinuz-2.6.12-10-k7 root=/dev/hda4 ro nolapic quiet init=sbin/initnginitrd /boot/initrd.img-2.6.12-10-k7savedefaultbootWhere hda4 is the partition mounted as /. What have I done wrong? Frustrated with the long boot time in Breezy and want to do something about it?
Here comes the remedy! Meet InitNG - a new generation init program that is able to reduce your boot time by a third to a half. Below are step-by-step instructions how to do it on your system.IMPORTANT: InitNG is pretty much work in progress, and not all things may work. Currently it does everything I personally want, but it may not be the case for you - your success depends on the combination of hardware and software you use. Suggestions, fixes, hacks and workarounds offered by people will be incorporated in this HOWTO.snipHave Fun.Here's my experience using a Toshiba Satellite A25 laptop running Breezy.First, following the instructions is important ^-; I browsed Alioth and downloaded the most recent version of InitNG. Which didn't work (it stopped at 100%).The version linked from the instruction post did work though. From when I press Enter in the GRUB menu until all the applets are loaded in Gnome, the boot time went from 125 seconds down to 95; nice!I rebooted later and there was a glitch; Ubuntu was mounting my HD for the 30th time and so it did its little check.
Which ran, but the display was wacky; instead of nicely sitting at the bottom of the page, it took up the whole screen, displaying each percentage with the bar graph as a separate entry. When it finished, insetead of completing the boot, it tried to reboot; there was some sort of mention about a hot reboot (?) but it didn't work.
I manually powered down and then back up again and it worked fine again.So still a little rough around the edges, but wow, what speed! =DEdit: I also tried 0.4.0-1 as per the post (but it had the same problem as 0.4.4-2, even after modifying laptop-mode.i. I just tried 0.4.7-2, letting it overwrite the modifications in the.i files I had made for 0.3.3-2; it booted up beautifully without me needing to modify anything.
(hopefully this can be included on the Dapper disks:-)I wanted to go into the printer settings (System - Administration - Printing) using initng 0.3.3-2 but I got the error: The CUPS server could not be contacted. Rebooting without using initng worked fine.Just FYI, I still get this CUPS error after booting with InitNG. I followed the directions for InitNG - it shaves off more than 10 secs off my startup time!!I have a strange problem though:Each time I start a console (konsole, gnome-terminal or even xterm), I get an error message 'Unable to launch child process'. KDE su complains 'the program su is not found' 'Please check your PATH'.In KDM/GDM, if I select the 'failsafe terminal' option, it immediately exits back to KDM/GDM.So, I'm basically unable to get the command line!!Has anyone else faced the same problems?Yes! I have exactly the same problem, only with a kernel I compiled myself.
However, the same kernel works fine without initng. Does anyone know how to fix this? Installed 4.8. Thanks Trigger. However, I still can't get privoxy to work. I've just upgraded my computer to an Athlon64 system yesterday and have installed initng 0.4.8 on the new system.
On a fresh Xubuntu install, initng automatically wanted to start powernowd which caused a segment fault. Removing powernowd from the startup fixed that easy enough. However I am having troubles rebooting. When I hit the reboot button, Ubuntu logs off to and I get the login screen. So I hit the reboot button on the login screen (GDM), and I get 'Please wait, system now rebooting' or something along those lines, but nothing happens. I've just upgraded my computer to an Athlon64 system yesterday and have installed initng 0.4.8 on the new system.
On a fresh Xubuntu install, initng automatically wanted to start powernowd which caused a segment fault. Removing powernowd from the startup fixed that easy enough. However I am having troubles rebooting. When I hit the reboot button, Ubuntu logs off to and I get the login screen.
So I hit the reboot button on the login screen (GDM), and I get 'Please wait, system now rebooting' or something along those lines, but nothing happens.I tried it yesterday on my desktop and had a similar problem, though it is run on ordinary Athlon, not 64. I will try 0.47 which works perfiectly on my laptop to check if it is something to do with new version. How i can get initng to shutdown my USB devices in shutdown( in this case: my usb mouse)? When i shutdown,mouse stay on. Something to do with ACPI maybe? Thanks for nice howto btw:razz:edit: and Breezys default booter does shut it down.Could you (and all others) open bugs for issues like this in Initng's Bugzilla on please? This is the easiest way to have issues like this fixed upstream.It is very hard for me to fix bugs I can't reproduce - if you add it in Bugzilla you will reach a much wider audience.EDIT: Thanks for reporting the mouse issue (if it was you):).
Hi,Last time I tried initng gets stuck on dbus with Dapper Drake.I think this is due to the new releases of udev and possibily breakage of HAL and Dbus.I'll attempt to fix it when I get back to my main computer (With Dapper Drake)Edit: Now that I think about it, it probably is not an issue with Initng really. Probably just broken packages.Actually it boots up fine with the latest InitNG package, should of tried the latest first.Only little warnings, but that is due to a half working HAL and DBUS in Dapper (Correct me if I am wrong of course). I'm running Ubuntu 5.10 on AMD64. I've downloaded initng0.4.8-1amd64.deb from the original site and correctly installed it.
When I reboot I got a segmentation fault error on the Powernowd service. Has anyone solved or bypassed the amd64 version's bugs?Initng is unusable an AMD 64 with versions prior to 0.5.0 - the package for 0.5.0 is lying in svn (but I don't release it because of a littel bug with the environment files. If someone really want to have it: Build it out of this svn (I won't tell you how - you should know it if you want to try;)). Due to the many probelms I've had with the AMD64 version of Ubuntu (well not Ubuntu's fault but the fault of other software that isn't 64-bit ready), I've moved back to 32-bit Ubuntu.
By default, powernowd and nvidia-glx are started at boot. In the 64bit system, they caused a segment fault and I could not boot. On 32-bit they cause an error that whizzes by and I can't read it, but the computer does boot. Since I am not running a laptop, powernowd can be safely removed, and nvidia-glx doesn't seem to do anything, so I removed it as well from the startup routine.Due to a post on a local mailing list, I have come to the realization that speed stepping is not working with the latest version of InitNG. There is an error at boot about a file scalinggovernor that cannot be found when running the speedtep script. I have found that speed stepping works when booting normaly without InitNG.My processor is a Socket 939 Athlon64 3000+ (1.8GHz)Motherboard is a Asrock 939Dual-SATA2. So far all I've done is install InitNG-4.81, change my boot configuration, comment out GDM so I don't get two X sessions loading, and MAN.With init, my computer takes 2:50 (GRUB to KDM) to boot.
With initNG my computer takes 1:02 to boot. That's still too long, but there you go. (I'm not connected to a LAN, that's where most of the boot time seems to be)-I am concerned about the system apparently trying to find the /sbin/nvidia-glx-config program first thing, and giving nasty errors when it can't. I still get X with nVidia drivers, but should I change the order of something to get it to boot? I assume the error has to do with the mountvirtfs not being done by the time it tries to find something on a virtual FS? Hopefully SpeedStep will work with the next release too.Actually, I have a lot of odd errors like the system failing to load a couple modules for things I know I don't have; will commenting out things like the hwrandom and toshiba make anything go faster? Initng is great.
It definetly does reduce boot time.I found a sort of solution for the wireless problem.I dont like to be connected at boot. I like to activate my wireless card when I feel like it so I wrote a bash script. Initng fails to modprobe ndiswrapper so each time you want to get online you have to modprobe ndiswrapper and the go to network-admin andactivate it. So I wrote the following simple bash script:type nano filename then#!/bin/shsudo modprobe ndiswrappernetwork-adminexitthen chmod 555 filenameand whenever you want to activate your wireless card just right./filename and activate it in network-admin.I know this is not a fix but its better than having to modprobe each time you want to get online.
Does anyone have a better script? HelloI'm having some problem with initNG 0.5: I compiled the source on a Breezy amd64, everything went fine. I then followed the HOWTO, made the necessary changes in the files, etc.The system boots fine (apart from some errors which I can't see, they're printing too fast) but I'm stuck with X: I'm in console-mode, in tty6 (don't know why, not that it matters. I think), and X won't start.startx tells me no screen was detected. I'm using NVidia's 8178 driver on a GeForce4 MX 440, so I don't see why it doesn't work.Thanks in advance, hope you got an idea to drag me out of this.
I upgraded from 0.4.8-1 to 0.5.1-1; the first time I booted with it, when Ubuntu started, there was an error message about HAL not starting. So I rebooted with it and then I noticed that my Battery Charge Monitor wasn't working. Rebooting with the normal system, it worked fine.shrug.I'll file a bug in a moment.A curious note: when I uninstalled 0.5.1-1 and reinstalled 0.4.8-1, the latter didn't sart up like it had previously, even when I deleted /etc/initng first.I've got the same problem with battery monitor.