From: Larry Gagnon on 24 Dec 2008 14:51 Am thinking of purcahsing one of these...has anyone any experience getting Slack on one? Larry -- For direct email remove fake.
From: JohnF on 25 Dec 2008 15:06 Davide Bianchi <davideyeahsure(a)onlyforfun.net> wrote: > Larry Gagnon <lggagnon(a)fakeuniserve.com> wrote: >> Am thinking of purcahsing one of these...has anyone any experience getting >> Slack on one? > > It seems from linux-laptop (http://www.linux-on-laptops.com/samsung.html) > that nobody ever tried with any linux distro, so I guess you'll be the > first one. Let us know how it goes. It's been installed with Ubuntu, see https://help.ubuntu.com/community/NC10 for details. I just bought one (terrific little box) and installed slackware 12.1 on it, using an external usb dvd... o First booted its default winxp and used the "advanced" partition option to shrink the "C drive" as much as possible (slide bar wouldn't go below 25GB), with remaining disk space (about 120GB) allocated to D. Note that /dev/hda1 is a "Compaq Diagnostics" (Id 12) partition for special Samsung restore functionality, so that C is /dev/hda2 and D is /dev/hda3 (both Id 7, HPFS/NTFS). o Then booted a gparted dvd (from the external drive) and shrank D to 8GB, leaving about 110GB unallocated. No problems with the gnu partition editor dvd. o Then booted and installed a slackware 12.1 dvd. Installed / on /dev/hda5, and made sure lilo ran against the root block in that boot partition (not against the mbr!!!). That was completely uneventful. Just like installing on any desktop. But, before rebooting... * Ran fdisk and deleted the D (/dev/hda3) partition, which had been Id 7 (HPFS/NTFS), unwritable by linux. Now made a n(ew) partition in those same blocks, but Id b (W95 FAT32), and ran mkdosfs against it, creating a partition read/writable by both linux and winxp. * Then mounted it and ran dd if=/dev/hda5 of=/fatdmountpoint/boothda5.lnx bs=512 count=1 to get a copy of that boot block so winxp could dual boot it. o Then rebooted, and the machine booted winxp as expected. Got a command prompt box, then cd c:\ to the root directory and then copy d:\boothda5.lnx * to get a copy on C:\ and then attrib -s -r -h boot.ini and edit boot.ini Then, add a line at the bottom of that file C:\boothda5.lnx="Slackware 12.1 on /dev/hda5" and save/exit the file (you made a backup copy first, right?). Finally, attrib +s +r +h boot.ini and you're all set. Reboot the machine, and you'll get a menu to select between booting windows and slackware. Note that you should make every effort to keep winxp, since it supports all the hardware perfectly, and that's real helpful for comparison when trying to get it all working under linux. Oh, yeah, and you paid for it anyway. Now, that page https://help.ubuntu.com/community/NC10 has instructions for an xorg.conf file that I very slightly modified for slackware, and which you can get from http://www.forkosh.com/xorg.conf-nc10 That's working fine for me. And, finally, here's where you all can help me out. Wired networking works fine for me, but I can't get that wireless Atheros ar242x working. It works fine under winxp. And the ubuntu help page mentions a madwifi workaround for ar242x on ubuntu, but I can't get anything like it to work for me on slackware. Any suggestions/ideas? Anybody got ar242x working under slackware on any box? Thanks, -- John Forkosh ( mailto: j(a)f.com where j=john and f=forkosh )
From: Martin Schmitz on 25 Dec 2008 21:58 JohnF wrote: > And, finally, here's where you all can help me out. > Wired networking works fine for me, but I can't get > that wireless Atheros ar242x working. You can find a message about not beeing able to load HAL on the device, right? You need a madwifi snapshot with the Atheros HAL from OpenWRT which is the only one which works on this device. But this one works perfectly well. If you manage to get it working, you have the best wifi hardware with the very best driver available. http://madwifi-project.org/wiki/news/20080829/new-hal-release-for-atheros-hardware Greetings, Martin
From: JohnF on 26 Dec 2008 08:13 Martin Schmitz wrote: > JohnF wrote: >> And, finally, here's where you all can help me out. >> Wired networking works fine for me, but I can't get >> that wireless Atheros ar242x working. > > You can find a message about not beeing able to load HAL on the device, > right? You need a madwifi snapshot with the Atheros HAL from OpenWRT > which is the only one which works on this device. But this one works > perfectly well. If you manage to get it working, you have the best wifi > hardware with the very best driver available. > > http://madwifi-project.org/wiki/news/20080829/new-hal-release-for-atheros-hardware > > Greetings, > Martin Thanks a lot, Martin. That worked perfectly. It builds with a simple make and make install , and then I added modprobe ath_pci to rc.modules , and it showed right up with iwconfig after rebooting. Couldn't have been easier (now that I got the right tarball). For the moment, I'm still configuring it manually, though. I'm clueless about (among many other things) wireless, and couldn't figure out how to modify the rc.scripts properly. rc.inet1 has a little MAXNICS loop, but that seems hard-coded for interfaces eth0, eth1, etc, whereas I want ath0. I guess I could add an IFDEFAULTNAME[0]="", etc, to rc.inet1.conf, and use it to set IFNAME[0], etc, in rc.inet1 (whenever the default name isn't ""). But I'm also guessing that shouldn't be necessary, since there already exists an rc.wireless script which suggests the scripts are already written to accommodate wireless interfaces. And the Slackware Linux Essentials book didn't clear that up for me -- pages 69-70 just say, for wireless, "Configure the Network: This is done in the exact same way as wired networks. Simply refer to earlier sections of this chapter." (Yeah, thanks.) Can you elaborate a bit on how that's actually supposed to be done for wireless? And one other item that probably reflects yet another cluelessness on my part: when manually configuring ath0, I had to disable security on my wap (a linksys wrt54g2 with routing stuff all disabled). I usually use wpa-psk, but iwconfig ath0 key efghijk complained about an "invalid argument", apparently because that key wasn't hex. Google only seemed to find wep related stuff for iwconfig. Is any other security supported? And how do I configure wpa, if I can? Thanks again, -- John Forkosh ( mailto: j(a)f.com where j=john and f=forkosh )
|
Pages: 1 Prev: Broken links libMagick in 12.2 Next: If Linux is a protected-memory OS... |