MX-14 beta 2

[entropyfoe]

The beta2 booted into a live session (beta 1 did not) on my old A7N8X mother board.

OK, so I found an old PATA drive in the parts bin and installed it so I could install MX-14.
This old machine has a working XP installation on a SATA drive that I have disconnected the power on so it is undisturbed.

From the live session, I can see the new PATA drive and access the files. But I cannot launch GParted to repartition the drive.
I supply root credentials an d everything locks up, no mouse cursor nothing works until I Ctrl Shift SysRq REISUB.

So, then I tried to install, thinking I could partition as part of the install, but when I get to the part to modify partitions, same lock up.

Any ideas what to try?
Has anyone used GParted from the beta2 live session?

-Jay

[malspa]

Has anyone used GParted from the beta2 live session?

I have the live session booted up right now, but here GParted starts up just fine.

[muskt]

I am still not able to get Samba to work on MX-14 B2.
I have it installed on 2 machines and can't figure it out.
I used the meta-installer-more than once-and it tells me it completed successfully.
I went into Synaptic, and downloaded the Help for Samba--There is absolutely no way for me to know where it went--I cannot locate it.
I searched the web, & found numerous "instructions" for installing & configuring Samba--None of these appeared close to MX-14.

I have, in the past, been successful with getting Mepis to talk to Windows; however, not with MX.

Anyone feel like providing me a "walkthrough" to get this going?

Thanks,
Jerry in Anchorage

[mariel77]

Hi, it's great to see all of you working on a new distro. Congrats!

I'm trying it because I need something newer on my desktop.
(I can't get M12 beta to boot; just black screen. I tried all my usual boot codes, but nothing, so here I am.)

I can't login once I install; the login screen just refreshes over and over.

I downloaded the iso (13.98) , the md5sum matched. I first burned a DVD (4x speed). MX-14 booted fine with the default, found my wifi, looked great, so I installed. The first install I didn't check Auto login. Got the screen that just refreshed on Login.

Burned a CD (same iso). This time on install I checked Auto login, but the same thing happens.

Any suggestions? Thank you!!

Here is my $ inxi -F -f (on my Mepis11 install; do you need it for the live MX-14?)
System: Host: MarielAcer Kernel: 2.6.36-1-mepis-smp i686 (32 bit) Desktop: KDE 4.5.3 Distro: unknown
Machine: System: Acer product: Aspire T180 version: R01-A2
Mobo: Acer model: EM61SM/EM61PM Bios: Phoenix version: R01-A2 date: 09/14/2006
CPU: Dual core AMD Athlon 64 X2 3800+ (-MCP-) cache: 1024 KB
Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz
CPU Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx
fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow extd_apicid pni cx16 lahf_lm cmp_legacy svm
extapic cr8_legacy
Graphics: Card: nVidia C61 [GeForce 6100 nForce 405] X.Org: 1.7.7 driver: nvidia Resolution: 1600x900@50.0hz
GLX Renderer: GeForce 6100 nForce 405/PCI/SSE2/3DNOW! GLX Version: 2.1.2 NVIDIA 260.19.21
Audio: Card: nVidia MCP61 High Definition Audio driver: HDA Intel Sound: ALSA ver: 1.0.23
Network: Card-1: Marvell 88E8056 PCI-E Gigabit Ethernet Controller driver: sky2
IF: eth0 state: down mac: 00:19:21:55:b5:84
Card-2: 3Com 3c905C-TX/TX-M [Tornado] driver: 3c59x
IF: eth1 state: down mac: 00:01:02:6a:65:17
Card-3: Ralink RT2501/RT2573 Wireless Adapter driver: rt73usb
IF: wlan0 state: up mac: 00:0e:2e:e6:08:77
Drives: HDD Total Size: 750.2GB (15.0% used) 1: id: /dev/sda model: Hitachi_HDT72502 size: 250.1GB
2: id: /dev/sdb model: Hitachi_HDS72105 size: 500.1GB
Partition: ID: / size: 15G used: 6.4G (45%) fs: ext3 ID: /home size: 49G used: 8.3G (19%) fs: ext3
ID: swap-1 size: 2.10GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 40.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 189 Uptime: 12 min Memory: 690.6/3294.7MB Client: Shell (bash) inxi: 1.8.26

[afab4]

I am still not able to get Samba to work on MX-14 B2.
I have it installed on 2 machines and can't figure it out.
I used the meta-installer-more than once-and it tells me it completed successfully.
I went into Synaptic, and downloaded the Help for Samba--There is absolutely no way for me to know where it went--I cannot locate it.
I searched the web, & found numerous "instructions" for installing & configuring Samba--None of these appeared close to MX-14.

I have, in the past, been successful with getting Mepis to talk to Windows; however, not with MX.

Anyone feel like providing me a "walkthrough" to get this going?

Thanks,
Jerry in Anchorage

Jerry,
Are you trying to set up a server or simply trying to connect to a Windows shared printer?

[Jerry3904]

I am still not able to get Samba to work on MX-14 B2.
I have it installed on 2 machines and can't figure it out.
I used the meta-installer-more than once-and it tells me it completed successfully.
I went into Synaptic, and downloaded the Help for Samba--There is absolutely no way for me to know where it went--I cannot locate it.
I searched the web, & found numerous "instructions" for installing & configuring Samba--None of these appeared close to MX-14.

I have, in the past, been successful with getting Mepis to talk to Windows; however, not with MX.

Anyone feel like providing me a "walkthrough" to get this going?

Thanks,
Jerry in Anchorage

A full document has been worked out by the Development Team and is coming in the next couple of days. Here are the general guidelines.

Connecting to Samba Shares
If Samba is installed on other computers, MX can connect to shared folders (Samba Shares) on Windows, Mac, Linux computers and NAS (Network Attached Storage) devices. The easiest method is to use the file manager (Thunar) to connect.

• Open the Thunar file manager
• Selecting Browse Network in the left pane will show various networks including Windows Network (address bar shows: network:///)
• Selecting Windows Network will show available Windows Workgroups (often called WORKGROUP by default)
• Selecting a Workgroup will show the available Samba Servers
• Selecting a Server will show the available Samba Shares
• Selecting a Samba Share will show all the available folders and create a shortcut in the Network sidebar section for the Share

[BitJam]

Has anyone used GParted from the beta2 live session?

GParted works fine here in VirtualBox.

How much memory does your system have?

You could try killing X-windows and then doing a CLI install from one of the virtual consoles. Kill X-windows (as root) with:

Code: Select all

/etc/init.d/lightdm stop

First, I suggest you disable tumblerd but I don't know of a good or easy way to do that. The only two methods I've seen are:

1. apt-get remove tumbler, and
2. add a cron entry to periodically run "pkill tumblerd"

ISTM there is an outstanding issue of MX-14-beta-2 crashing or locking up on *some* older systems with 512 Meg of memory even though other people have no problem on similar systems. Maybe tumbler is responsible. IOW maybe tumbler is causing OOM errors on some older systems but not all, depending on usage patterns and/or on what files are on the hard drive for tumbler work on.

Even if tumbler is not the culprit, I am very concerned that there is not an easy and well-advertised way to disable it, especially given the history of problems it has caused in past. IMO tumbler should be disabled by default (at least on systems with limited RAM) and we need to have an easier way to turning it off. It is ridiculous that people feel they need to run a cron job that periodically kills off tumblerd.

[muskt]

All I want to do is be able to share files between computers on my home network.

I have played with Thunar.
If I select the network option. a new window opens that says something like "Network Shares"--I do not remember, cuz I'm in Windows right now. If I click on the "window" option, the whole mess disappears and goes back to the desktop.

I'll reboot into MX & get right back in a couple.

Jerry in Anchorage

[muskt]

I'm in MX now.

OK, Thunar open.
Click "Browse Network"
New Window -- shows what you said Jerry.
Click "Windows Network" -- Boom, back to desktop--even Thunar in Panel or Taskbar is gone.

As I said earlier, I located the Samba .conf file and inserted my Workgroup name there. Spelling was correct.

Although this isn't a really important thing for me, it could be a significant roadblock to others who may desire to adopt MX for their use.

Thanks,
Jerry in Anchoarge

PS--Where should I look to find the Samba Help that I "supposedly" installed from Synaptic?

[richb]

Just spent the better part of a week with some other users working on this. Different solutions exist depending on the mix of computers on your network. If Windows in the mix, samba can be used. If all Linux machines NFS can be used. (NFS can also be used with Windows). I am not the expert, but with help got both methods working on a purely Linux network. Since I am not the expert, and still not too confident with the Samba solution, I will leave it to someone else to respond with details. By the way NFS, in my opinion, is the more reliable with Linux networks, and quite easy to set up.

The docs for MX will be updated also with details, eventually.

(If you search for samba and NFS in the MX section you will see the thread on this. But it is easy to get lost in the posts.

EDIT: OK I will try.

You need to setup the shares on the server. As root they are added to the samba.conf file something like this for a folder called Documents.

Code: Select all

[Documents]
	path = /home/username/Documents
	force user = username
	force group = users
	read only = No
	guest ok = Yes
	case sensitive = No
	strict locking = No
	msdfs proxy = no

Then on the client I was able to access the shares by typing smb:/ip address of server/home/username/Documents) in the location bar of Thunar. Others were able to access Documents from Network in the Thunar Panel. For some reason I was not.

EDIT 2: It would be better to add to an existing samba thread or create a new one for your samba issues.