[kof94]

Quote

Anyway, what you seek is straight-fwd. Regarding NTFS-3g support, that's the easy part. You mite recognize a similar writing style in this thread. Not a coincidence. ph34r.gif

I did wonder, since you signed yourself off as Jet. I forgot to mention that bit in my last post.

I have one question about your update, why exactly do you need to update the kernel. Remember I am a Linux n00b although I am trying.

[kof94]

Nevermind I think I get it now. You know reading is useful .

I have one question then I'll drop this line of inquiry or make a new thread (I feel I may be quite responsible for taking this thread of on different tangents, sorry).

Have I got this right:

Download your ntfs-3g archive (killbill in this case)
Update the fuse + ntfs-3g drivers in said archive with new .mo's you have on the Slax site.
Then just over write /boot and /modules from modded archive.

I know I'm probably asking stupid questions, but I don't want to just go ahead thinking I've got it and end up nuking someones Windows install.

Thanks.

[jetman]

kof94, on Apr 29 2007, 04:12 AM, said:

Nevermind I think I get it now. You know reading is useful .

I have one question then I'll drop this line of inquiry or make a new thread (I feel I may be quite responsible for taking this thread of on different tangents, sorry).

Have I got this right:

Download your ntfs-3g archive (killbill in this case)
Update the fuse + ntfs-3g drivers in said archive with new .mo's you have on the Slax site.
Then just over write /boot and /modules from modded archive.

I know I'm probably asking stupid questions, but I don't want to just go ahead thinking I've got it and end up nuking someones Windows install.

Thanks.

You have it rite on all counts, exc the stupid part. If you have any probs, bring them rite here. My idea on this whole Super-Disc thing is to do more than simply illustrate how to make a multi-boot CD/DVD, but to get into customization (as you're doing), so it really is a Super disc.

Quick digression: last nite, on the Syslinux mail list, there was an inquiry about MEMDISK loading ISOs. I commented that an ISO-compatible MEMDISK isn't nec, if one knows a bit about hacking and invests some of one's own time to find a custom solution. Needless to say, I got a long-winded rationalization rite back, rife w/ talk about 'what avg users need', 'what avg users don't know', blah-blah-blah. I could've mentioned Super-Disc, but he/she didn't sound like the type that's interested in working for this stuf.

Bottom line: If someone GOOGLEs for info about ISOLINUX, multi-boot CDs, whatever, they'll get a lot more than they bargained for. I have some ideas for future Super-Disc extensions, including stuf involving Slax, Knoppix, maybe even Kubuntu (that's a def maybe.) That is, if you're interested in working for it. That is, if one reads thoroughly and follows instructions carefully.

Oh yes, in advance, PLEASE spare us all the long-winded explanations about what other folks/the market/Linux-in-general needs or wants ! Speak for yourself !!

Good luck. TTYL....Jet

[jetman]

jaclaz, on Apr 28 2007, 07:10 AM, said:

Just for the record, and to keep things together as possible, here is an interesting thread on 911CD about using parameters passed to memdisk into autoexec.bat, in case you are using DOS based floppy images:
http://www.911cd.net...?showtopic=5706

just a few days ago the thread was revamped:
http://www.911cd.net...showtopic=19634
with contributions (hopefully enhancements) by d4vr0s and yours truly.

jaclaz

Jaclaz: As always, your contributions are welcome and interesting. Thanx and expect to see you post more stuf RSN....Jet

[kof94]

I have to agree that the ability to directly boot a .iso image is useful and I say this is from experience with CDShell/Diskemu.

This doesn't mean you can just bung a load of your favorite .iso's on your disc and go 'there, I'm done'.

However, it does mean you can directly boot apps like say Super Grub Disk or chntpwd without having to decompile them or resort to an older floppy ver.

There are some other advantages as well.

I worked out a system that enabled me to use the original isolinux menu/display for any linux app/distro I liked by booting mini .iso's. These .iso's just contained the isolinux dir, kernel and ramdisk the rest of the disc i.e. .squashfs etc was then in a relevant location on my disc.

It worked quite well but I have to admit I did feel like a bit of a cheat.

I keep banging on about this but I would really like to see a switch for memdisk that enabled diskemu style image reading. So, instead of loading the whole floppy image in ram it just reads the contents of it from the disc. I believe this will solve a lot of problems with some images not booting.

This post has been edited by kof94: 29 April 2007 - 12:59 PM

[jetman]

kof94, on Apr 29 2007, 12:57 PM, said:

I have to agree that the ability to directly boot a .iso image is useful and I say this is from experience with CDShell/Diskemu.

This doesn't mean you can just bung a load of your favorite .iso's on your disc and go 'there, I'm done'.

<snip>

Kof: I don't care if Peter (user hpa) decides to enhance MEMDISK to read/boot large ISOs. If he provided said enhancement, I'd use it myself as it would be a real labor-saver. Having said that, I won't add my voice requesting this enhancement bec it really only benefits those who want to make multi-boot CDs/DVDs, when there are viable alternatives. Ultimately, he (and other OSS developers) enhance their offerings bec (1) it helps a significant portion of the user community at large or (2) it helps them on a paying job or (3) they like the challenge of implementing a particular capability. The principal user of SYSLINUX is the system builder, either the author of a distro or someone who needs a boot menu for a PC. SYSLINUX works very well in this role, as it is.

As a developer, I'm sympathetic to guys like Peter and dismissive of these characters who offer these long-winded, self-serving rationalizations of why someone else should invest their labor to make their lives a little easier (present company excluded.) SYSLINUX is a labor of love that he's chosen to share w/ the rest of us. There are many non-coders who have no clue about the complexity of developing and enhancing something like MEMDISK and think what they want is widely desirable. Yet they feel qualified to wax at length about what someone else's obligations are.

I find these diatribes esp annoying after one points out that the requester can realize comparable results w/ a some effort on their part. Yes, the developer should invest his/her labor (for free) to accommodate someone who's loathe to invest their own labor, to satisfy their own desires. Why ? Bec I don't know a shell script from a head of cabbage and don't want to learn about any of that. I just want what I want !

In summation, if you want to use Linux (or some other OSS offering), one should understand and respect the underlying do-it-yourself (DIY) philosophy behind this movement. BTW, have you noticed several topics posted in the last few weeks, that ask for help w/ issues covered (to some degree) right here in this thread ?

Diatribe-mode-off.....Jet

This post has been edited by jetman: 29 April 2007 - 02:47 PM

[kof94]

Wohhh, I really didn't mean to hit a nerve with this .

At the end of the day I am just an end user. I respect the fact that there are a lot of people around me that contribute a hell of a lot of time and effort into developing software that I use.

The least I can offer is ideas or suggestions that may enhance this software. I by no means expect or demand anything and/or wish to offend anyone by making these suggestions.

You may not have been trying to have ago at me, but I thought I better clear that up.

Please take this in good Jest, like all my other ramblings .

-kof94

This post has been edited by kof94: 29 April 2007 - 03:43 PM

[jetman]

kof94, on Apr 29 2007, 03:20 PM, said:

Wohhh, I really didn't mean to hit a nerve with this .

At the end of the day I am just an end user. I respect the fact that there are a lot of people around me that contribute a hell of a lot of time and effort into developing software that I use.

The least I can offer is ideas or suggestions that may enhance this software. I by no means expect or demand anything and/or wish to offend anyone by making these suggestions.

You may not have been trying to have ago at me, but I thought I better clear that up.

Please take this in good Jest, like all my other ramblings .

-kof94

In the past, I've been guilty of some of the things I deride. About a year ago, when I was putting my 1st disc together, just DSL/TRK/BartPE using BCDW, I sputtered, fumed, and was a mess. I didn't want to do the things I now present. With careful reflection, one has a change of heart. Those comments weren't aimed at you, but to let future participants know that no self-justifying crap is welcome. If you want to learn or offer your own constructive insights, go for it.

Anyway, how did you make out w/ your 1st Slax disc ? I'm esp interested in knowing whether KDE is working well for you. If not, then try this. KDE, or rather X, could be a little more helpful and the XCONF2 module is something I hacked together which has been very helpful, making X/KDE behave. Later....Jet

[kof94]

Quote

Those comments weren't aimed at you, but to let future participants know that no self-justifying crap is welcome.

Fair enough .

Quote

Anyway, how did you make out w/ your 1st Slax disc ? I'm esp interested in knowing whether KDE is working well for you. If not, then try this. KDE, or rather X, could be a little more helpful and the XCONF2 module is something I hacked together which has been very helpful, making X/KDE behave. Later....Jet

I been 50% playing with Slax and 50% trying to make a common sense menu for everything on my disc, which is a bit like moving into a new house. I can't stop moving the furniture around!

As far as Slax goes, I've only managed so far to put your ntfs-3g + fuse drivers in and test in VM to see if it works.

When I get back from work tomorrow I'm gonna burn a test build of my current disc inc Slax and give it a full outing. I'm also gonna install Ubuntu 7.04 on my Linux drive since I nuked my 6.10 install last week (don't ask cos I don't know ) and haven't got around to fixing it.

Once all that's done I'll get back to you.

-kof94

[kof94]

Ok, I only have one thing to say... SLAX ROCKS .

Your ntfs-3g driver + fuse (what is fuse by-the-way) works a treat.

I really pushed the boat out moving stuff around on my Win partitions and editing files. I admit this was probably stupid but hay 'no pain, no gain' .

Unlike previous encounters with ntfs-3g this time I didn't encounter chkdsk on reboot and as far as I'm aware I havn't killed anything. This is great!!!

Anyway, besides that, I was also very pleasantly surprised at the speed, especially since I was running everything from a DVD.

Bart/WinPE has a lot to live up to now with this kind of speed and access.

There are a couple of things I need to sort out though.

The first is wireless networking.

Since moving house I've had to stump for wireless networking. Needless to say on more than one occasion I've threatened to buy a long cat-5 and start drilling holes in the house just so I don't have to put up with it.

That aside... Slax was unable to config my wlan card. This may be my inexperience or just a lack of drivers, any ideas on how to solve either?

The second is, I was unable to view the contents of my boot DVD and I was unable to mount the drive via right click (You can tell I'm a Windows user ). I gather this might be because I'm actually running Slax from it but I wondered if this was normal behavior?

Apart from that though, quite a successful outing if you ask me. I'm now torn between going back and playing some more or doing what originally planned and install Ubuntu... life is so unfair sometimes .

This post has been edited by kof94: 30 April 2007 - 04:41 PM

[jetman]

kof94, on Apr 30 2007, 04:39 PM, said:

Ok, I only have one thing to say... SLAX ROCKS

Your ntfs-3g driver + fuse (what is fuse by-the-way) works a treat.

I just did the heavy lifting of putting the pieces together. Smart guys over in the UK did the real work on NTFS-3g. FUSE is a module that permits filesystem drivers to exist in userspace, as opposed to kernelspace. Bottom line is that a sophisticated driver like NTFS-3g can be developed+debugged like a regular program, no hassles w/ complicated schemes to test code inside the kernel itself. Much faster turnaround time in the development cycles and lots more mechanisms can be used as filesystems. NTFS-3g has had several revs in the last five months alone.

Quote

I really pushed the boat out moving stuff around on my Win partitions and editing files. I admit this was probably stupid but hay 'no pain, no gain' .

Unlike previous encounters with ntfs-3g this time I didn't encounter chkdsk on reboot and as far as I'm aware I havn't killed anything. This is great!!!

Anyway, besides that, I was also very pleasantly surprised at the speed, especially since I was running everything from a DVD.

Bart/WinPE has a lot to live up to now with this kind of speed and access.

There are a couple of things I need to sort out though.

The first is wireless networking.

Since moving house I've had to stump for wireless networking. Needless to say on more than one occasion I've threatened to buy a long cat-5 and start drilling holes in the house just so I don't have to put up with it.

That aside... Slax was unable to config my wlan card. This may be my inexperience or just a lack of drivers, any ideas on how to solve either?

Most wireless cards can be made to work using NDISWrapper, a cool hack to make Windows networking drivers work w/ Linux. As always, read the instruction carefully and you should be connected in a less than an hour. I don't think you have to add modules for that, exc if you need WPA encryption (wpa_supplicant.)

WRT BartPE, I'm putting less an less into that one, since discovering Slax. In fact, there are a couple of Linux AV pgms in the module section which are really viable bec of NTFS-3g. I haven't done a complete regen/rebuild of my BartPE config (just AV/spyware def updates) in almost a year. I periodically run CHKDSK just to be safe, but I haven't had a failure since I started using it on New Year's Eve. In fact, I run a swap file from a NTFS partition.

A custom Slax KillBill/Server is way smaller than BartPE, but has a full computing env including multimedia and a full-function office suite. Modules are way easier to put together than Bart plugins. All portable and extensible using multi-session CDs ! Experiment w/ diff modules using CD-Rs+Track-At-Once, multisession writes. Then, once you've got a system tweaked the way you want it, use those files to integrate into your DVD-R. Those are the words of a stingy guy who hates wasting media on one-off experiments !

Quote

The second is, I was unable to view the contents of my boot DVD and I was unable to mount the drive via right click (You can tell I'm a Windows user ). I gather this might be because I'm actually running Slax from it but I wondered if this was normal behavior?

Apart from that though, quite a successful outing if you ask me. I'm now torn between going back and playing some more or doing what originally planned and install Ubuntu... life is so unfair sometimes.

A dbl-click should work to display the contents of your boot (DVD) drive, but there should also be a Mount cmd on the context menu as well. BTW, when you mount it, you still have to open it, but a dbl-click does both. Other than having to explicitly mount partitions/drives, KDE is reasonably Windows-like. As least for folks like us....

[kof94]

Quote

I just did the heavy lifting of putting the pieces together. Smart guys over in the UK did the real work on NTFS-3g.

I realised that but without people willing put the pieces together where would we be!?

Quote

A dbl-click should work to display the contents of your boot (DVD) drive, but there should also be a Mount cmd on the context menu as well. BTW, when you mount it, you still have to open it, but a dbl-click does both. Other than having to explicitly mount partitions/drives, KDE is reasonably Windows-like. As least for folks like us....

I ran mount from right click after discovering an empty drive when I double-clicked my on my DVD but nothing happened! I'll take another look.

Quote

Most wireless cards can be made to work using NDISWrapper, a cool hack to make Windows networking drivers work w/ Linux. As always, read the instruction carefully and you should be connected in a less than an hour. I don't think you have to add modules for that, exc if you need WPA encryption (wpa_supplicant.)

I decided to install Ubuntu 7.04 a minute ago and had similar problems with no connection. Granted I do use a WEP key and I don't broadcast my ssid so this may be causing me some problems. Drilling holes in the house is starting to become more appealing by the minute though.

On the subject of Ubuntu I like some of the new features but what a pig to install.

During live boot up I had an error which I ignored and carried on cos it disappeared so quickly. Then at first boot, post-install, I was taken to some kind of disc check/filesystem check which failed and then rebooted the machine before I could read anything. Following that everything went fine but I'm still left with a nagging question 'is anything broken or not'. How frustrating...

All-in-all the rest of this week I'm probably gonna spend a lot more time with Slax and Ubuntu so I'm sure I'll get there in the end.

[jetman]

kof94, on Apr 30 2007, 06:31 PM, said:

<snip>

I decided to install Ubuntu 7.04 a minute ago and had similar problems with no connection. Granted I do use a WEP key and I don't broadcast my ssid so this may be causing me some problems. Drilling holes in the house is starting to become more appealing by the minute though.

<snip>

The Q-n-D WiFi/NDISWrapper Mini-HOWTO:

Look, once you have the .inf+.sys file for your WiFi card it's pretty much:

####   Let's say you have a Broadcom 43xx based Wi-Fi card like I do, just copy the bcmwl5.inf+bcmwl5.sys
####   into /root and run the following....
/usr/sbin/ndiswrapper -i bcmwl5.inf
####   The following displays whether the Windows driver installed correctly
/usr/sbin/ndiswrapper -l
####  You should see something like the following:
####  bcmwl5 : driver installed
####		device (14E4:4320) present (alternate driver: bcm43xx)
####  If not, try ndiswrapper -r bcmwl5  to remove the driver, then go back to the top for one more go
####
####  If you try a 'do over', do yourself a favor and remove ndiswrapper w/ 'modprobe -r ndiswrapper' after 
####  removing the driver.  If a do over doesn't boot WiFi, reboot and start at the top....
####
####  No one seems to recommend this exc the ndiswrapper people....  /sbin/depmod -a
/sbin/modprobe ndiswrapper
####  The following shows what the new device name is....
/sbin/iwconfig
/sbin/iwconfig eth1 channel 11
/sbin/iwconfig eth1 mode Managed
/sbin/iwconfig eth1 ap ap-mac-address
/sbin/iwconfig eth1 key restricted  <wep-string-in-hex>
####  /sbin/iwconfig eth1 commit
/sbin/iwconfig eth1 essid "your-ap-name"
/sbin/ifconfig eth1 inet 192.168.3.100 broadcast 192.168.3.255 netmask 255.255.255.0
/sbin/ifconfig eth1 up
/sbin/route add default gw 192.168.3.1
####  or you could use dhcpcd -d -t 30 wlan0 for an automatic IP and skip the 
####  1st ifconfig and the route stmts

Above is an extract from the 2nd-gen script I use to fire up my WiFi-Wired router, so it's perfected. Actually, it's almost a verbatim rip from the NDISWrapper wiki. I literally got my Moto WPCI810G going in under an hour. It took about another day or so til I found the formula for turning the box into a WiFi-Wired router (basically a high-perf ICS PC), which talks to a Netgear wireless router, then out to the Net via the landlord's cable modem. Under (my) Knoppix, the WiFi device is always eth1, but under Slax it's always wlan0, as it's supposed to be. What's happening is:

1) Install the Windows driver
2) Display the driver's installation status
3) Load the NDISWrapper kernel module
4) Display the newly installed wireless device's name and params
5) Configure the wireless device
6) Setup the IP settings (via ifconfig) for a new network device
7) Turn it on
8) Manually setup the default gateway for Internetworking, altho dhcpcd does all of the IP stuf, if you use an auto IP from the AP/router.

I manually set the IP and default route bec I use port forwarding (from the Netgear) for P2P/RDP/VNC apps. Just to get started, one can skip those commands and simply bring up the device and prime it via dhcpcd. I wanted to go w/ disabled SSID broadcasts too, but I had to get the router working very quickly and simply couldn't coax Windows into dealing w/o a SSID. But I was able to get WPA-PSK going under Windows+Knoppix+Slax, which is much more robust than WEP, so I could live w/ the SSID broadcasts.

Where do the .inf/.sys files come from ? From the driver disc for the device, of course. You do have the driver disc ? Well, assuming you don't, you can obviously go back to the card's vendor and d/l a driver kit or you can resort to digging into the bowels of the beast and extract them from Windows itself. The Windows Device Manager entry for the device has a Device tab w/ a Device Details button, which should give you the location of the .sys and .inf files. If the .inf isn't indicated, it's somewhere under \WINDOWS\INF.

For completeness sake, there are some built-in kernel modules that do WiFi directly. My bcm4306 is almost supported w/ the bcm43xx kernel module under Knoppix. Almost, as it requires a slightly illegal util which extracts (cuts) downloadable firmware from the .sys file of the Windows driver and loads it via the bcm43xx kernel module. It was great until the great WPA migration weekend, at which time the bcm43xx kernel module decided it didn't grok WPA. WPA means wpa_supplicant, which is a matter for another post.

Truth is, unless you have one of a handful of wireless cards (don't ask, as I don't know other than the Orinoco cards), no distro does universal turnkey WiFi. More WiFi drivers are coming out w/ every kernel update but NDISWrapper really is our friend....Jet

PS: Kof, this wasn't exclusively for your benefit, but once I started typing, I figured I go ahead and make this into a mini-HOWTO for everyone else....

PPS: The Code box w/ the script uses full paths for the programs as installed on Knoppix. Your mileage will vary, in order to use it on another distro. As always, copy+paste w/ brain engaged.

This post has been edited by jetman: 30 April 2007 - 09:07 PM

[kof94]

Well wireless networking in Linux sucks.

I cannot for the life of me get this to work in Ubuntu. I've now resorted to trailing a large cat-6 cable across the landing and downstairs to the router, much to my Wife's discussed. Actually that's not true she finds it bloody hilarious .

The drills coming out tomorrow along with some cable clips and a hammer. Shortest route is a straight line and all that!

As far as Ubuntu was concerned, it knew exactly what my wlan card was and assigned a driver to it, just didn't want to work. I've even gone as far as broadcasting my ssid and disabling all security, still no go.

Oh well, as least I'm on the net now. I'll probably return to this again but to be honest I was losing my patience with it and that doesn't help anyone.

This post has been edited by kof94: 01 May 2007 - 05:03 PM

[jetman]

kof94, on May 1 2007, 05:02 PM, said:

Well wireless networking in Linux sucks.

I cannot for the life of me get this to work in Ubuntu. I've now resorted to trailing a large cat-6 cable across the landing and downstairs to the router, much to my Wife's discussed. Actually that's not true she finds it bloody hilarious

Not true. You simply haven't relinquished "ready-to-wear" WiFi Windows drivers yet. When I did my 1st Unix (actually FreeBSD) WiFi project about four years ago, I had Orinoco/Agere cards and they worked almost instantly. I think they're the only company that has completely OSS driver support for Linux/BSD/Unix. I was spoiled too, but I got over that, as you will. But by your remarks, I probably would've found last nite's scene entertaining, as did your spouse.

Quote

The drills coming out tomorrow along with some cable clips and a hammer. Shortest route is a straight line and all that!

As far as Ubuntu was concerned, it knew exactly what my wlan card was and assigned a driver to it, just didn't want to work. I've even gone as far as broadcasting my ssid and disabling all security, still no go.

Go ahead and wire up a little Ethernet "security blanket", then when you've got your patience back, you'll see it wasn't that tough after all. I can share a couple more pointers:

1) The sequence of iwconfig cmds to setup WiFi seems to be sensitive to the order of each element (AP/SSID/WEP key/channel) is sent to the card. This was esp true, in order to enable WPA.

2) Since you can specifically choose an AP by MAC address, you should have no trouble disabling SSID again. I gave up on that bec Windows simply wouldn't cooperate.

3) Did you look the system or kernel logs for more init details about your WiFi cards ? My WPCI810G is detected (under Knoppix), but the bcm43xx driver doesn't know that to do w/ it, for lack of firmware. Which reqs human intervention.

Anyway, scarf a Guinness or something and relax....Jet

[kof94]

Quote

Go ahead and wire up a little Ethernet "security blanket", then when you've got your patience back, you'll see it wasn't that tough after all.

Exactly my thoughts. I went back to have another go and discovered NDISWrapper was actually unable to use the generic Broadcom driver I use or the bodged Belkin/Broadcom driver that came with the card.

Although it's probably only bodged under Windows cause it installs extra sortware that peaks the CPU to 100% after about half an hour on the net.

I'm gonna have another go tonight with a fresh sense of humour and see what happens.

I nearly forgot, I switched to WPA as well last night (after all of the above) is this a good idea now or am I just asking for trouble?

This post has been edited by kof94: 02 May 2007 - 02:59 AM

[jetman]

kof94, on May 2 2007, 02:54 AM, said:

[Exactly my thoughts. I went back to have another go and discovered NDISWrapper was actually unable to use the generic Broadcom driver I use or the bodged Belkin/Broadcom driver that came with the card.

Although it's probably only bodged under Windows cause it installs extra sortware that peaks the CPU to 100% after about half an hour on the net.

I'm gonna have another go tonight with a fresh sense of humour and see what happens.

I nearly forgot, I switched to WPA as well last night (after all of the above) is this a good idea now or am I just asking for trouble?

Hmmm. Not sure what you mean by generic Broadcom driver WRT to NDISWrapper. See, the generic Broadcom driver I know is the kernel module that comes w/ Ubuntu/Kubuntu. I think that's bcm43xx, at least that's what I know it to be under ZenWalk Live (Slax done better) and Knoppix 5.1. Isn't used with NDISWrapper. Now, referring back to my mini-HOWTO, check your kernel log for details about why the driver didn't like your card. OTOH, using the NDISWrapper and the Belkin files is more troubling. Just to see what success others have had w/ your gear, one can try LinuxQuestions HCL.

WPA ? Absolutely better than WEP. As I've been reading and hearing lately, WEP can be cracked so easily my grandmother could probably figure it out ! WPA isn't even hard to setup w/ Linux. Just another program to add to the mix. I can't call myself an expert on all of these subjects, but my PCs earn their keep daily under Windows and Linux. I'm even typing this from my mini-WiFi router via IceWeasel (what a lousy name !)

Anyway, TTYL....Jet

[kof94]

The first post I read on LinuxQuestions HCL about my card:

Quote

After much frustration trying to find native drivers and trying to get ndiswrapper working, I've given up on this card. My recommendation would be to avoid this device completely. It is extremely difficult to get working -- I have not found one review or tutorial anywhere that didn't say it was impossible. I'm on my way right now to exchange it for something made by Ralink... the non-Linux-compatible Broadcom chipset is a headache.

This guy was also running it under Ubuntu.

Hay-ho all is not lost, I'll have my wired connection in a tidy, permanent condition in a few days so none of this will matter so much. I wouldn't be so hasty if it wasn't such a necessity. Ubuntu without the internet is like cutting an arm off!

I'm gonna keep play with this though. I might be able to grab another card (not Belkin/Broadcom) of a work colleague to try out so I'll see what happens then.

At the end of the day this is all good practice. I'm determined to be less Windows dependent and more Linux savvy so the more I play with the better.

Thanks for your help Jet.

[jetman]

kof94, on May 2 2007, 03:42 PM, said:

The first post I read on LinuxQuestions HCL about my card:

<snip>

This guy was also running it under Ubuntu.

Hay-ho all is not lost, I'll have my wired connection in a tidy, permanent condition in a few days so none of this will matter so much. I wouldn't be so hasty if it wasn't such a necessity. Ubuntu without the internet is like cutting an arm off!

I'm gonna keep play with this though. I might be able to grab another card (not Belkin/Broadcom) of a work colleague to try out so I'll see what happens then.

At the end of the day this is all good practice. I'm determined to be less Windows dependent and more Linux savvy so the more I play with the better.

Thanks for your help Jet.

I'm shocked and amazed ! I've never had a single whisper of trouble from any Belkin offering. Guess there's a 1st time for everything. If at 1st you don't succeed and all that. The biggest prob and obstacle is what you pointed out: being disconnected. Nowadays, that's like taking drugs from the addict. At least when you're hooked on the 'Net, you're in the comfort of your own home and not hanging out w/ dirtbags in abndoned buildings.

Should have something really interesting going by next Thurs. Hope so anyway. Later....Jet

[kof94]

jetman, on May 3 2007, 12:30 AM, said:

I'm shocked and amazed ! I've never had a single whisper of trouble from any Belkin offering. Guess there's a 1st time for everything. If at 1st you don't succeed and all that. The biggest prob and obstacle is what you pointed out: being disconnected. Nowadays, that's like taking drugs from the addict. At least when you're hooked on the 'Net, you're in the comfort of your own home and not hanging out w/ dirtbags in abndoned buildings.

Ooooookay..... .

jetman, on May 3 2007, 12:30 AM, said:

Should have something really interesting going by next Thurs. Hope so anyway. Later....Jet

I'm intrigued... keep talkin'...